For what it's worth...I've ran across tons of providers that don't like the To URI not matching the R-URI. And yes, it's ridiculous and it means they don't have a clue what they are doing.
You can use an actual B2BUA (sippy for example) to get around these restrictions if you can't otherwise make them route things properly. I wonder if the B2BUA module thats been discussed will accommodate this need. Rather than dismiss the broken carrier and saying to leave them, I'd like to find a way to address this issue. Of course, that simply enables carriers to continue to operate their broken switches without fixing them.. So I'm not sure what's better. ;) -Brett On Wed, Jul 29, 2009 at 11:02 AM, Julien Chavanton <[email protected]>wrote: > Thank you for the clarification, maybe this partner does not support SIP > Proxy, unfortunatly we will have to deal with them, we can not drop them. > > not sure how to deal with this, diaplan ? :-( > > ------------------------------ > *From:* [email protected] on behalf of Iñaki Baz Castillo > *Sent:* Wed 29/07/2009 4:58 PM > *Cc:* [email protected] > *Subject:* Re: [OpenSIPS-Users] Prefix and "To:" header field > > 2009/7/29 Julien Chavanton <[email protected]>: > > Drouting module do_routing(), does not modify the "To:" header field, > > according to my reading this is ok, but it seems most softphone and sip > node > > modify both > > > > I have tested EyeBeam/X-Lite (dialplan prefixing) > > When an *UA* generates an INVITE, both To URI and request URI must be > equal. > When a proxy *routes* an INVITE, it can modify the request URI, but > *never* the To URI. > > > > Our partner does not llike when the "To:" header field is different then > the > > SIP INVITE, what is the suggested way of dealing with this ? > > "Drop" your partner as it has no idea of SIP. > > > -- > Iñaki Baz Castillo > <[email protected]> > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
