failed to decode uri

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

failed to decode uri

thrillerbee
I have dialogs getting stuck because my origination gateway (OpenSIPS proxy) fails to proxy 200 OKs to some INVITEs.  In the logs, I see:
/usr/local/sbin/opensips[30336]: ERROR:uac:decode_uri: invalid base64 string"AAAAAAUECAEIAwUHCQ<sip:12.24.48.96"
/usr/local/sbin/opensips[30336]: ERROR:uac:restore_uri: failed to decode uri
/usr/local/sbin/opensips[30337]: ERROR:uac:decode_uri: invalid base64 string"AAAAAAUECAEIAwUHCQ<sip:12.24.48.96"
/usr/local/sbin/opensips[30337]: ERROR:uac:restore_uri: failed to decode uri

I am doing some normalization of the from uri with uac_replace_from.  What could cause this?

Thanks.

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: failed to decode uri

thrillerbee
To add a little more detail, after doing some from uri normalization, this is eventually passed on to an OpenSIPS instance running b2bua for top hiding.  I'm assuming this error indicates that the header param that is used to rebuild the original from uri is different than expected, but I don't see any discernible differences in a trace between the headers in the 200 OK (to the INVITE) and the provisional responses received right before it.  The provisional responses are proxied; the 200 OK is not.

Any help would be most appreciated.

Thanks.

On Tue, Oct 12, 2010 at 6:13 PM, thrillerbee <[hidden email]> wrote:
I have dialogs getting stuck because my origination gateway (OpenSIPS proxy) fails to proxy 200 OKs to some INVITEs.  In the logs, I see:
/usr/local/sbin/opensips[30336]: ERROR:uac:decode_uri: invalid base64 string"AAAAAAUECAEIAwUHCQ<sip:12.24.48.96"
/usr/local/sbin/opensips[30336]: ERROR:uac:restore_uri: failed to decode uri
/usr/local/sbin/opensips[30337]: ERROR:uac:decode_uri: invalid base64 string"AAAAAAUECAEIAwUHCQ<sip:12.24.48.96"
/usr/local/sbin/opensips[30337]: ERROR:uac:restore_uri: failed to decode uri

I am doing some normalization of the from uri with uac_replace_from.  What could cause this?

Thanks.


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: failed to decode uri

thrillerbee
I was forced to remove the OpenSIPS b2bua as it seems it was causing the origination gateway to choke on these 200 OKs.  Dialogs are no longer hanging, but I still see errors on the origination gateway that are concerning:

/usr/local/sbin/opensips[4399]: ERROR:core:parse_from_header: bad from header
/usr/local/sbin/opensips[4399]: ERROR:rr:record_route: From parsing failed
/usr/local/sbin/opensips[4402]: ERROR:core:parse_to: unexpected char [#000] in status 6: <<"2345678910"<sip:2345678910@6.12.24.48:5060

I can't find anything out of the ordinary in traces.  What should I be looking for?
Again, any help would be appreciated.

Thanks.

On Tue, Oct 12, 2010 at 9:15 PM, thrillerbee <[hidden email]> wrote:
To add a little more detail, after doing some from uri normalization, this is eventually passed on to an OpenSIPS instance running b2bua for top hiding.  I'm assuming this error indicates that the header param that is used to rebuild the original from uri is different than expected, but I don't see any discernible differences in a trace between the headers in the 200 OK (to the INVITE) and the provisional responses received right before it.  The provisional responses are proxied; the 200 OK is not.

Any help would be most appreciated.

Thanks.


On Tue, Oct 12, 2010 at 6:13 PM, thrillerbee <[hidden email]> wrote:
I have dialogs getting stuck because my origination gateway (OpenSIPS proxy) fails to proxy 200 OKs to some INVITEs.  In the logs, I see:
/usr/local/sbin/opensips[30336]: ERROR:uac:decode_uri: invalid base64 string"AAAAAAUECAEIAwUHCQ<sip:12.24.48.96"
/usr/local/sbin/opensips[30336]: ERROR:uac:restore_uri: failed to decode uri
/usr/local/sbin/opensips[30337]: ERROR:uac:decode_uri: invalid base64 string"AAAAAAUECAEIAwUHCQ<sip:12.24.48.96"
/usr/local/sbin/opensips[30337]: ERROR:uac:restore_uri: failed to decode uri

I am doing some normalization of the from uri with uac_replace_from.  What could cause this?

Thanks.



_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: failed to decode uri

Bogdan-Andrei Iancu
In reply to this post by thrillerbee
Hi,

regarding the decode_uri issue : the uac module stores a cookie in the
RR header, so at Route time it will be able to restore the original FROM
/ TO hdr. I suspect that the one of the parties (caller or callee) is
messing around with this RR parameter (vsf , vst), most probably with
the case sensitiveness (switching from lower to upper case).

If you post a SIP trace on proxy, I can point you to the bogus party.

Regards,
Bogdan

thrillerbee wrote:

> To add a little more detail, after doing some from uri normalization,
> this is eventually passed on to an OpenSIPS instance running b2bua for
> top hiding.  I'm assuming this error indicates that the header param
> that is used to rebuild the original from uri is different than
> expected, but I don't see any discernible differences in a trace
> between the headers in the 200 OK (to the INVITE) and the provisional
> responses received right before it.  The provisional responses are
> proxied; the 200 OK is not.
>
> Any help would be most appreciated.
>
> Thanks.
>
> On Tue, Oct 12, 2010 at 6:13 PM, thrillerbee <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     I have dialogs getting stuck because my origination gateway
>     (OpenSIPS proxy) fails to proxy 200 OKs to some INVITEs.  In the
>     logs, I see:
>     /usr/local/sbin/opensips[30336]: ERROR:uac:decode_uri: invalid
>     base64 string"AAAAAAUECAEIAwUHCQ<sip:12.24.48.96"
>     /usr/local/sbin/opensips[30336]: ERROR:uac:restore_uri: failed to
>     decode uri
>     /usr/local/sbin/opensips[30337]: ERROR:uac:decode_uri: invalid
>     base64 string"AAAAAAUECAEIAwUHCQ<sip:12.24.48.96"
>     /usr/local/sbin/opensips[30337]: ERROR:uac:restore_uri: failed to
>     decode uri
>
>     I am doing some normalization of the from uri with
>     uac_replace_from.  What could cause this?
>
>     Thanks.
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>  


--
Bogdan-Andrei Iancu
OpenSIPS Bootcamp
15 - 19 November 2010, Edison, New Jersey, USA
www.voice-system.ro


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: failed to decode uri

Bogdan-Andrei Iancu
In reply to this post by thrillerbee
Again, can you post a trace of the message causing the error?

Regards,
Bogdan

thrillerbee wrote:

> I was forced to remove the OpenSIPS b2bua as it seems it was causing
> the origination gateway to choke on these 200 OKs.  Dialogs are no
> longer hanging, but I still see errors on the origination gateway that
> are concerning:
>
> /usr/local/sbin/opensips[4399]: ERROR:core:parse_from_header: bad from
> header
> /usr/local/sbin/opensips[4399]: ERROR:rr:record_route: From parsing failed
> /usr/local/sbin/opensips[4402]: ERROR:core:parse_to: unexpected char
> [#000] in status 6: <<"2345678910"<sip:2345678910@6.12.24.48:5060
> <http://sip:2345678910@6.12.24.48:5060>
>
> I can't find anything out of the ordinary in traces.  What should I be
> looking for?
> Again, any help would be appreciated.
>
> Thanks.
>
> On Tue, Oct 12, 2010 at 9:15 PM, thrillerbee <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     To add a little more detail, after doing some from uri
>     normalization, this is eventually passed on to an OpenSIPS
>     instance running b2bua for top hiding.  I'm assuming this error
>     indicates that the header param that is used to rebuild the
>     original from uri is different than expected, but I don't see any
>     discernible differences in a trace between the headers in the 200
>     OK (to the INVITE) and the provisional responses received right
>     before it.  The provisional responses are proxied; the 200 OK is not.
>
>     Any help would be most appreciated.
>
>     Thanks.
>
>
>     On Tue, Oct 12, 2010 at 6:13 PM, thrillerbee
>     <[hidden email] <mailto:[hidden email]>> wrote:
>
>         I have dialogs getting stuck because my origination gateway
>         (OpenSIPS proxy) fails to proxy 200 OKs to some INVITEs.  In
>         the logs, I see:
>         /usr/local/sbin/opensips[30336]: ERROR:uac:decode_uri: invalid
>         base64 string"AAAAAAUECAEIAwUHCQ<sip:12.24.48.96"
>         /usr/local/sbin/opensips[30336]: ERROR:uac:restore_uri: failed
>         to decode uri
>         /usr/local/sbin/opensips[30337]: ERROR:uac:decode_uri: invalid
>         base64 string"AAAAAAUECAEIAwUHCQ<sip:12.24.48.96"
>         /usr/local/sbin/opensips[30337]: ERROR:uac:restore_uri: failed
>         to decode uri
>
>         I am doing some normalization of the from uri with
>         uac_replace_from.  What could cause this?
>
>         Thanks.
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>  


--
Bogdan-Andrei Iancu
OpenSIPS Bootcamp
15 - 19 November 2010, Edison, New Jersey, USA
www.voice-system.ro


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users