Hi Liviu
On Wed, 21 Jul 2021 at 16:45, Liviu Chircu wrote:
>
> > 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
>
> ...Which scenario of the two below would you
> say we are in, and with
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
Hi Liviu - thanks for getting back to me.
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
On 20.07.2021 13:26, Mark Allen wrote:
On registration add_path_received() works but the received address is
not formatted correctly. I am seeing '%%3b' instead of a semicolon,
and '%%3d' instead of an equals sign.
Hi Mark,
How exactly is this peculiar formatting breaking your logic?
Hmm - not sure what went wrong with my post. It seemed to add some unwanted
formatting. Here's the failing example again...
Path:
Path:
On Tue, 20 Jul 2021 at 10:49, Mark Allen wrote:
> I'm seeing a strange problem when using add_path_received() for
> registration of NATed UAC using
