Hello, I am currently implementing support for <tel:> URI's in our User Agent as per RFC 3966/ RFC 2806-bis standards. I had the following doubts regarding the same. Any inputs will be highly appreciated.
1. Contact Header: As per RFC 3261 Section 8.1.1.8, it mentions that this URI must be in either SIP/ SIPS format. In Section 10.2.1, it is mentioned that for registrations, the Contact header field can contain any URI Scheme (e.g the tel URL, RFC 2806 [9]) or email addresses (with a mailto URL, RFC 2368 [32]) as Contacts for an address-of-record. Does this mean that the 'Contact' field in an INVITE message must always be a SIP/SIPS URI while in a REGISTER message, it can be a SIP/SIPS/TEL/Mailto URI ? 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> 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
