Hi, path module calls register_rrcb when "use_received" is set to 1 to extract the "received=" param and set its content as dst-uri if present. Now I've noticed that when e.g. a message has a pre-loaded route like "Route:<sip:mydomain.com;lr>", then kamailio (at least 3.1.3) spits the following error message: /usr/sbin/kamailio[23953]: ERROR:<core> [parser/parse_param.c:481]: parse_params(): Invalid character, ; expected /usr/sbin/kamailio[23953]: ERROR: path [path.c:213]: failed to parse route parametes

I was trying to reproduce this but without much success, it sometimes happens and sometimes not, but I can't yet put the finger on the reason. Any ideas?

Hi, On 08/29/2011 10:27 PM, Daniel-Constantin Mierla wrote: 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

Hi Daniel, On 09/14/2011 08:30 AM, Daniel-Constantine Mierla wrote: Indeed it happens when it doesn't match itself.

Well, the use-case is this: REGISTER sip:mydomain.com:5060 Route:<sip:mydomain.com;lr> To:<sip:myuser@mydomain.com> So it's an initial REGISTER with no to-tag but with a Route header (e.g. pjsip loves to do that for some reason for every initial request). We're using Kamailio as a load-balancer (this is where the error occurs) in the SPCE, and we don't set any "alias" parameter there, so the Route is not considered local. Instead, we're doing something like this: if(loose_route()) { if(!has_totag()) { $du = $null; # send off to proxy using dispatcher } else { t_relay(); } } Then on the proxy we check again after loose_route() using is_domain_local("$dd") to either silently consume routes which are in our domain table or to reject them if not. Thanks, Andreas _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Hi, On 09/14/2011 10:42 AM, Daniel-Constantin Mierla wrote: That'd be great! At least for path, it's only relevant for extracting information for Routes pointing to itself. E.g. for a REGISTER, the lb puts itself into the Path, like "Path: <sip:own-ip:own-port;lr;received=sip:remote-ip:remote-port>", and in a subsequent INVITE that would convert into a Route, and the lb can then extract the "received=" information from it in the rr-callback and set it as $du..