> -----Original Message----- > From: Paul Kyzivat [mailto:[EMAIL PROTECTED] > > As I've said elsewhere it doesn't upset me to have pstn routing used as > a fallback. But the common behavior we've been discussing has never > stated the sip routing will be preferentially tried.
Ah. Well, in my world it's not a black-white thing. I always like to think sip end-end is preferential, but there are cases due to least-cost-routing or regulatory requirements that the PSTN is used when there was a sip path. But anyway, if you think it's ok to use PSTN as a fallback for a sip: request, then I'm not sure what the problem is? I mean that effectively weakens the scheme to be basically what we have now, no? > Well, with the semantics we are trying to sort out, it would be entirely > appropriate for the GW to use a tel uri for To-, From-, and R-URIs. > Since the incoming call is from the PSTN it has no data to suggest that > the caller can be reached any other way. I suppose it could use a sip > URI identifying itself, if it *wants* to take responsibility for any > return calls, but that is an unlikely scenario. Totally, but it's not what they're doing. (some are good about this, some ain't) And Dean is currently proposing a GW uses a sip: From URI, with a user=phone, so it can be signed. But that is another of the many issue threads. :) > I'm proposing what I think is a more sensible and functional arrangement > if everybody followed it. Obviously everybody doesn't follow it now, we > need to figure out if there is a feasible migration path. But its not > like everything that should work does work today (or we wouldn't be > having this conversation), so there is need to figure stuff out in any > case. I'm trying to remember how we got on this topic, because things are working fine with-respect-to sip as a default scheme, afaik. I think it's architecturally ugly, and will cause us grief later, but I can't seem to recall what current "problem" drove this particular topic.(?) -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
