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 <thriller...@gmail.com> 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 Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
