Re: [OpenSIPS-Users] failed to decode uri

2010-10-13 Thread 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

Re: [OpenSIPS-Users] failed to decode uri

2010-10-13 Thread Bogdan-Andrei Iancu
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

Re: [OpenSIPS-Users] failed to decode uri

2010-10-13 Thread Bogdan-Andrei Iancu
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

[OpenSIPS-Users] failed to decode uri

2010-10-12 Thread 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 stringAAUECAEIAwUHCQsip:12.24.48.96 /usr/local/sbin/opensips[30336]:

Re: [OpenSIPS-Users] failed to decode uri

2010-10-12 Thread 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