[SR-Users] parse errors in rr-callback of path module

[Andreas Granig]

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 at 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20110913/f7698730/attachment.pgp>