Hi All,
As per the RFC quote from section 12.2.1.1, this section deals
with generation mid-dialog request by UAC.
" The URI in the To field of the request MUST be set to the remote URI
from the dialog state. The tag in the To header field of the request
MUST be set to the remote tag of the dialog ID. The From URI of the
request MUST be set to the local URI from the dialog state. The tag
in the From header field of the request MUST be set to the local tag
of the dialog ID. If the value of the remote or local tags is null,
the tag parameter MUST be omitted from the To or From header fields,
respectively.
Usage of the URI from the To and From fields in the original
request within subsequent requests is done for backwards
compatibility with RFC 2543, which used the URI for dialog
identification. In this specification, only the tags are used for
dialog identification. It is expected that mandatory reflection
of the original To and From URI in mid-dialog requests will be
deprecated in a subsequent revision of this specification."
I noticed a line if the value of the remote or "LOCAL" tags is
null. UAC is the one which generates dialog creating request which
conforms to RFC 3261. So, I think there is no question of local tag to
be null, I think there MUST be special handling instead of omitting the
value, if local tag is found null.
Please let me know if I misunderstood something.
Regards,
Manju
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
