I'm just saying what I've seen. I'm not endorsing it by any means. I'm just saying is has a better chance of working in the real world today than putting a Tel URI on the wire.
On Apr12 2008 21:25 , "Paul Kyzivat" <[EMAIL PROTECTED]> wrote: > So you are telling me that you SHOULD forward someone to your own domain > to reach a phone number even when you know that your domain would not be > willing to route the resulting request from the forwardee. Instead you > are *counting* on the forwardee to *ignore* the domain and the 3263 > routing rules and instead use its own logic to reach the number??? > > So in effect you are suggesting that we should revise 3263 regarding sip > URIs with user=phone, and get the result widely adopted rather than get > tel widely adopted. > > Paul > > Hadriel Kaplan wrote: >>> -----Original Message----- >>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Juha >>> Heinanen >>> >>> Francois Audet writes: >>> >>>> Insisting on Tel URI seems kind of out of touch with reality. >>> >>> then PSTN is out of touch with 302. please tell me, how can i write a >>> sip uri in my phone that redirects the caller in another domain to my >>> cell phone? >> >> Well a 302 with a tel may work, or may not. Alternatively you could use a >> sip URI in the 302. For the domain portion of that 302's contact: if you >> don't know a SIP-PSTN provider which will send it to your cell, then you >> could try setting it to your provider's domain (if you have one), or the >> domain which sent the request. And since a 3xx can have multiple contact >> URIs, you can try all these at the same time, including Tel, but I suggest >> making the first one the most likely to succeed, because I've been told some >> devices can't handle multiple contacts either (ya, it's friggin nuts - don't >> shoot the messenger). >> >> It's nasty, but it should work in many cases I think. (though honestly most >> cases I've seen just set it to sip and their provider's domain and it >> works... but that could easily be because I mostly only see traces from >> providers) >> >> -hadriel >> _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
