Daniel-Constantin Mierla writes:
> It was not clear from your previous statement that your experience with
> other cases when there was no schema was the right or wrong way. Because
> the patch adds schema to entity in an xml doc constructed by
> presence_dialoginfo module. Therefore seems to b
On 7/12/13 2:20 PM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
the question is which format is the correct one (entity value with uri
shcema (sip:) or without)? Or maybe both formats are ok?!?
as it was mentioned by the author, all examples in standards include uri
scheme and in th
Daniel-Constantin Mierla writes:
> the question is which format is the correct one (entity value with uri
> shcema (sip:) or without)? Or maybe both formats are ok?!?
as it was mentioned by the author, all examples in standards include uri
scheme and in the document syntax specify uri. uri alway
On 7/12/13 12:28 PM, Juha Heinanen wrote:
sip-router writes:
Details - Hi. We had a small problem with polycom phones to realize
blf functionality. On yealink, cisco, aastra etc works like a
charm. We discover that in xml body of NOTIFY, entity uri doesn't
contain a "sip:" value. In RFC 4235 h
sip-router writes:
> Details - Hi. We had a small problem with polycom phones to realize
> blf functionality. On yealink, cisco, aastra etc works like a
> charm. We discover that in xml body of NOTIFY, entity uri doesn't
> contain a "sip:" value. In RFC 4235 however in xml body "sip:" is on
> ever
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Pawel Sternal (Sternik)
Attached to Project - sip-router
Summary - Entity URI in NOTIFY XML body
Task Type - Improvement
Category - Module
Status - Unconfirmed
Assigned To -
