[Sip-implementors] Proper dialog matching - URI vs. tag

2010-08-20 Thread Mikko Lehto
Hello implementators Recently we ran into following dialog matching issue with new SS7 GW device: our customers proxy modified from URI in initial INVITE, but did not do the same anymore for in-dialog BYE. This caused our new GW to not match the dialog and sessions we're only terminated once GW

Re: [Sip-implementors] Proper dialog matching - URI vs. tag

2010-08-20 Thread Iñaki Baz Castillo
2010/8/20 Mikko Lehto msle...@gmail.com: Hello implementators Recently we ran into following dialog matching issue with new SS7 GW device: our customers proxy modified from URI in initial INVITE, but did not do the same anymore for in-dialog BYE. This caused our new GW to not match the

Re: [Sip-implementors] Proper dialog matching - URI vs. tag

2010-08-20 Thread Brett Tate
RFC 3261 does not allow the To/From uri matching values to change within a dialog. RFC 4916 provides the ability to alter To/From uri matching values; however it requires the support/use of option-tag “from-change”. Except per RFC 4916, I’m not aware of an RFC which has officially deprecated

Re: [Sip-implementors] Proper dialog matching - URI vs. tag

2010-08-20 Thread Paul Kyzivat
Brett, Yes, 3261 has all those MUSTs in it. But it was there for 2543 compatibility. AFAIK there is nothing that calls for checking that the URIs remain unchanged as a requirement for recognizing that the request is an in-dialog request. So I think it might be within the letter of the law to