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?







= = = = = = = = = = = =

 From: "jorma h" <jorma.jj at gmail.com
<https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors>>

   When a proxy receives a message (e.g. INVITE) with a SIP URI containing an
   embedded tel URI, and that embedded tel URI has parameters, how is this
   handled when:

Strictly speaking, a SIP URI cannot contain any other URI.  But I
assume you mean "a SIP URI whose user-part looks like an E.164
number", or using the syntax of RFC 3261 section 25.1, when the
"userinfo" may be a "telephone-subscriber".  (The user-part cannot look
like a URI because all URIs contain ':', but ':' is not allowed in
user-parts.)

   1. The proxy DOES NOT serve the domain in the SIP URI?
   I think the answer has to be that it simply routes on the domain, and
   completely ignores the left hand side of the URI. I.e. it does not even look
   at the embedded tel URI nor its parameters.

You're quite correct there:  If the proxy does not serve the domain,
it has no knowledge of the user-parts in that domain's URIs.  On the
other hand, RFC 3263 tells the proxy how to send the message to a
proxy that *does* serve the domain.

Dale
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to