Hi all,
after a patch from one of our providers ACKs started to come with R-URI looking like: ACK sip:192.168.0.1;lr=on;ftag=507454020 SIP/2.0 instead of: ACK sip:192.168.0.1;lr=on;ftag=507454020 SIP/2.0 like it did before the patch.
The new ACK format gives an error in OpenSER: Jul 6 11:35:55 ser1 /sbin/openser[9634]: ERROR: parse_uri: bad uri, state 0 parsed: <<sip> (4) / <sip:192.168.0.1;lr=on;ftag=507454020> (38) Jul 6 11:35:55 ser1 /sbin/openser[9634]: ERROR: parse_sip_msg_uri: bad uri <sip:192.168.0.1;lr=on;ftag=507454020> Jul 6 11:35:55 ser1 /sbin/openser[9634]: loose_route: Error while parsing Request URI
Are the new format of the ACKs valid? With the "<>"? If they are valid, the problem lies in OpenSER?
Br, /Tobias
Hi Tobias,
not the format is not valid for the RURI.
regards, bogdan
Tobias Lindgren wrote:
Hi all,
after a patch from one of our providers ACKs started to come with R-URI looking like: ACK sip:192.168.0.1;lr=on;ftag=507454020 SIP/2.0 instead of: ACK sip:192.168.0.1;lr=on;ftag=507454020 SIP/2.0 like it did before the patch.
The new ACK format gives an error in OpenSER: Jul 6 11:35:55 ser1 /sbin/openser[9634]: ERROR: parse_uri: bad uri, state 0 parsed: <<sip> (4) / <sip:192.168.0.1;lr=on;ftag=507454020> (38) Jul 6 11:35:55 ser1 /sbin/openser[9634]: ERROR: parse_sip_msg_uri: bad uri <sip:192.168.0.1;lr=on;ftag=507454020> Jul 6 11:35:55 ser1 /sbin/openser[9634]: loose_route: Error while parsing Request URI
Are the new format of the ACKs valid? With the "<>"? If they are valid, the problem lies in OpenSER?
Br, /Tobias
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users