Hi!
Gaurav.Kheterpal wrote: ...
2. Besides 'Request URI' and 'To:' header fields, can the TEL URI be present in any other INVITE header values (e.g. Via, Route Header, Contact etc). In other words, which fields in the INVITE request does the proxy scan for possible tel->sip translation using ENUM/ any other mechanism ? In case, there is no other field which contains this information, how is the TEL URI information propagated across intermediate proxies when the UA is configured with a outbound proxy having a defined route set. If the defined route set is proxy 1-> proxy 2 in the below diagram, the request will be formed using:
INVITE sip:proxy1 Route: <sip:proxy2> To: <tel:1234>
this is a message in old style (RFC2???) with strict routers. According to 3261 (loose routers) the request URI contains always the final destination, e.g. the tel-uri.
I think the message should look like this (not sure if the second route header is necessary):
INVITE <tel:1234> Route: <sip:proxy1> Route: <sip:proxy2> To: <tel:1234>
Intermediate proxies should forward the request according to the Route headers without any need to interpret the request URI. Only the final proxy has to interpret the request URI (tel uri).
regards, klaus
User A Proxy 1 Proxy 2 User B | | | | | INVITE F1 | | | |--------------->| | |
Does this mean that in such a case, the only parameter which contains the TEL URI is the 'To' field. As I understand, this field is never processed by the proxies unless they implement privacy/ RFC 3324(5) ??
I am current not aware of any proxy which is capable of handling TEL URI's, any information/ links regarding the same will be highly useful.
Thanks in advance for your help.
regards,
Gaurav
_______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
