> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dean > Willis > > The problem is we're talking about TWO service providers, and reaching > the wrong one's gateway.
I'm not sure I understand the problem. Service providers decide whether they want to send a call to the PSTN or not for another domain, and that decision is based on their peering relationship and regulatory restrictions. If the peering relationship is such that b.com will try the PSTN (e.g., because a.com pays b.com to be its provider), then it will, else not. So it's not reaching the wrong one's gateway. A.com calls b.com, b.com can forward the call to the pstn if it has that type of relationship with a.com, else it sends the 302 redirect back upstream. What's the "wrong one's" gateway? > > I guess you are worried about [EMAIL PROTECTED] phoning [EMAIL PROTECTED] > > and b.com > > doesn't have > > a gateway but wants to forward to PSTN (and wants the originating to > > fork > > the bill). So it sends tel URI instead. Sure, but again, I doubt it > > will > > work very well. > > It has the potential to work well, whereas what we have now doesn't. Well, it seems to be working. There's plenty of bilateral peering already happening, and the 302's seem to work across the providers. It's just that the contact URI in them is not what I would call the "right" one, but it's working. Really, in the long list of interop issues, this one's pretty low on the totem pole, imho. People are having trouble getting basic calls to work without the aid of a middle-box. That's a bit higher on the list to me. :) > > Again, don't shoot the messenger: it makes sense to me to use Tel > > URI for > > this. I am just saying it may cause interop problems. Maybe that's > > ok, and > > maybe implementations will start implementing tel URI. > > I've no doubt that there will be interop problems. That's what happens > when you specify something that has previously been unspecified and > left to whim or caprice. OK, but failing calls will not give it a high chance of being adopted. Maybe we can figure out how to get a sip: uri to work as well - there's more than one way to skin a cat, even with a potato peeler. ;) -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
