[OpenSIPS-Users] add_path_received and TLS - received address problem

Liviu Chircu liviu at opensips.org
Wed Jul 21 15:44:58 EST 2021

On 21.07.2021 17:47, Mark Allen wrote:
> I'm seeing errors for pinger OPTIONS and Asterisk NOTIFY SIP messages 
> going out to the NATed TLS UAC...
> ERROR:core:unescape_user: invalid hex digit <37>
> ERROR:path:path_rr_callback: failed to unescape 
> received=sip:35.x.x.x:60026%%3btransport%%3dtls

The core problem seem to be those doubled '%%' strings, which are not 
supposed to work that way.  Which scenario of the two below would you 
say we are in, and with what degree of certainty? (i.e. if you could 
share a .pcap with me via email, that would be great!)

A.  OpenSIPS generates those erroneous '%%' strings right from the 
beginning, when building the Path headers and passing through the 

B.  The Path headers are okay when generated by OpenSIPS (containing 
just '%3b' and '%3d'), but the issue is on the backend side, which 
originates ping messages with doubled '%%' strings in Route headers, 
which OpenSIPS is obviously having a hard time parsing/routing?


Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2021 Distributed | www.opensips.org/events

More information about the Users mailing list