From: "jorma h" <[EMAIL PROTECTED]>
I am referring to a tel URI, with parameters, which has been converted to a
SIP URI.
For example, the URI described at the end of section 5 of RFC 4904:
tel:+16305550100;tgrp=TG-1;trunk-context=+1-630
Transforming this tel URI to a sip URI yields:
sip:+16305550100;tgrp=TG-1;
[EMAIL PROTECTED];user=phone
Does this change anything?
No, it's still a SIP URI.
It's true that the RFCs do not state clearly that only an element with
authoritative knowledge of a SIP domain can place an interpretation on
the user-part of a URI within that domain. But that principle is
expressed implicitly in various places. Consider RFC 3261 section
19.1.3:
sip:alice;[EMAIL PROTECTED]
The last sample URI above has a user field value of
"alice;day=tuesday". The escaping rules defined above allow a
semicolon to appear unescaped in this field. For the purposes of
this protocol, the field is opaque. The structure of that value is
only useful to the SIP element responsible for the resource.
Dale
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
