Catalina, catalina oancea wrote: > From what I know the record-route header is not compulsory, and > dialog-matching can also be done using rfc dialog-matching instead of > the did parameter in record-route (modparam("dialog", > "dlg_match_mode", 2)). This is what I am trying to use, I don't want > to use the record-route header at all. > > It is true that you do not have to use the dialog fast-matching cookie parameter in the Record-Route header. However, you need the Record-Route header in order for the proxy to have visibility into subsequent sequential requests within the dialog, so you might as well use the parameter for faster matching. In other words, if you don't add Record-Route, your proxy won't see BYEs, re-INVITEs, etc. See RFC 3261 20.30 (http://www.ietf.org/rfc/rfc3261.txt): 20.30 Record-Route The Record-Route header field is inserted by proxies in a request to force future requests in the dialog to be routed through the proxy. -- Alex -- Alex Balashov Evariste Systems Web : http://www.evaristesys.com/ Tel : (+1) (678) 954-0670 Direct : (+1) (678) 954-0671 Mobile : (+1) (678) 237-1775

Hello, On 05/27/2009 06:44 PM, catalina oancea wrote: > Yeah ok, but this is not the issue here. > > Even if I use record-routing, if I don't use the fast-matching cookie, > the problem I described still remains. > > > as I got from the diagram in your first email, second call, coming after 407, preserves the call-id and from tag? According to RFC, this is a completely new dialog and should use different values. Anyhow, after you send back the challenge, can you print with xlog $dlg(ref) and paste it here? Is the ended dialog staying for long time (you can use mi to list dlgs)? Cheers, Daniel > 2009/5/27 Alex Balashov <abalashov(a)evaristesys.com>om>: > > > >> Catalina, >> >> catalina oancea wrote: >> >> >> >> >>> From what I know the record-route header is not compulsory, and >>> dialog-matching can also be done using rfc dialog-matching instead of >>> the did parameter in record-route (modparam("dialog", >>> "dlg_match_mode", 2)). This is what I am trying to use, I don't want >>> to use the record-route header at all. >>> >>> >>> >> It is true that you do not have to use the dialog fast-matching cookie >> parameter in the Record-Route header. >> >> However, you need the Record-Route header in order for the proxy to >> have >> visibility into subsequent sequential requests within the dialog, so >> you >> might as well use the parameter for faster matching. >> >> In other words, if you don't add Record-Route, your proxy won't see >> BYEs, >> re-INVITEs, etc. See RFC 3261 20.30 >> (http://www.ietf.org/rfc/rfc3261.txt): >> >> 20.30 Record-Route >> >> The Record-Route header field is inserted by proxies in a request to >> force future requests in the dialog to be routed through the proxy. >> >> >> -- Alex >> >> >> >> >> -- >> Alex Balashov >> Evariste Systems >> Web : http://www.evaristesys.com/ >> Tel : (+1) (678) 954-0670 >> Direct : (+1) (678) 954-0671 >> Mobile : (+1) (678) 237-1775 >> >> >> >> > _______________________________________________ > Kamailio (OpenSER) - Users mailing list > Users(a)lists.kamailio.org > http://lists.kamailio.org/cgi-bin/mailman/listinfo/users > http://lists.openser-project.org/cgi-bin/mailman/listinfo/users > > > > -- Daniel-Constantin Mierla http://www.asipto.com/