Hello, Seems like the rr params value is not set properly. I looked in rr module and such case can happen indeed, but for the case when uri in rr does not match myself. Is this also in your case? I wonder anyhow why the callbacks are executed in route header uri is not local address...
I will make a patch for this case soon. Btw, were all hops in the signaling performing loose routing or some did strict routing? Cheers, Daniel On Sep 13, 2011, at 11:06 PM, Andreas Granig <agra...@sipwise.com> wrote: > Hi, > > On 08/29/2011 10:27 PM, Daniel-Constantin Mierla wrote: >> No clue yet since I am not calling loose_route() for initial requests, >> like in the default config, so if there is an issue just with the case >> of pre-loaded Route, I couldn't spot it so far. Having the value of the >> parameters it tries to parse (maybe it starts too early/late in the >> header, or something else) should give some hints... > > I was finally able to deploy a version with debug messages, and it looks > like this, when it works as expected: > > /usr/sbin/kamailio[23936]: INFO: path [path.c:213]: parsing route > parameters 'lr;received=sip:1.2.3.4:52091' > > And the other cases where it fails, it look like this: > > /usr/sbin/kamailio[23927]: INFO: path [path.c:213]: parsing route > parameters 'te: <sip:my.domain.com;lr>#015#012Max-Forwards: 69#015#012F' > /usr/sbin/kamailio[23927]: ERROR: path [path.c:215]: failed to parse > route parameters '<sip:my.domain.com;lr>#015#012Max-Forwards: 69#015#012F' > > The content of "str *r_param" differs a lot, e.g. sometimes it's "ntact: > <sip:431234566@1.2.3.4:41994;" or any other random part of the SIP message. > > No idea how this could happen. The sip message itself looks perfectly > fine for cases where this occurs. > > Andreas > _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
