[OpenSIPS-Users] uac_replace_from corruption

[Brett Nemeroff]

Razvan,
I'm using the new dialog based method. If I remember right the old way was
with vsf/vst headers and I'm definitely not using that anymore.

The version I'm using is a svn pull from 1.6.3 (7919), which I think is how
I'm doing the dialog based version. I'm not quite ready to move to 1.7 but
I'm close.

These servers I'm having this issue on have quite a bit of load on them;
but I can try to isolate the issue. Here's some entries that are in my log
that might help you out:

Dec 15 21:28:07 lcr02 /usr/local/sbin/opensips[1433]:
ERROR:core:parse_from_header: bad msg or missing FROM header
Dec 15 21:28:07 lcr02 /usr/local/sbin/opensips[1433]:
ERROR:uac:restore_uris_reply: failed to find/parse FROM hdr
Dec 15 21:30:55 lcr02 /usr/local/sbin/opensips[1432]: ERROR:core:parse_to:
unexpected char [>] in status 10: <<<sip:4056807913 at 38.123.240.1>>> .
Dec 15 21:30:55 lcr02 /usr/local/sbin/opensips[1432]:
ERROR:core:parse_from_header: bad from header
Dec 15 21:30:55 lcr02 /usr/local/sbin/opensips[1432]:
ERROR:uac:restore_uris_reply: failed to find/parse FROM hdr

What kind of debug would you need? I may be able to replace it on a smaller
scale.

Thanks!
-Brett

On Thu, Dec 15, 2011 at 4:25 AM, Razvan Crainea
<razvancrainea at opensips.org>wrote:

>  Hi, Brett!
>
> Are you using uac_replace_from function with dialog support or the old
> approach with route parameters? Would it be possible to increase OpenSIPS
> debugging level and paste some extra information?
>
> Regards,
>
> --
> Răzvan Crainea
> OpenSIPS Developer
>
>
> On 12/15/2011 12:41 AM, Brett Nemeroff wrote:
>
> Hello List,
> I'm sure I brought this up sometime before, but I'm still having this
> issue. I have to imagine that some of you out there are having it as well.
> Running OpenSIP-1.6.4
>
> I perform a uac_replace_from. It works just fine, But on subsequent
> transactions within the dialog, like a BYE that comes from the destination,
> the restored From is corrupted IF there was a port in the original From.
> This appears to be isolated to cases where the URI has a port in it.
>
> For example, here's the From from the original INVITE
> From: "8005551212" <sip:8005551212 at 1.2.3.4:5070>;tag=as3371c611.
>
> And then the far end sends a BYE later on:
> From: "18705551313" <sip:18705551313 at 2.3.4.5>;tag=SDsjh0f99-eb402829
>
> And I relay the BYE:
> From: "18705551313" <sip:18705551313 at 14.5
> <4)2$6:^E7>;tag=SDsjh0f99-eb402829
>
> So aside from getting the client to stop sending the port in the From
> header, is there another fix for this?
>
> Thanks!
> -Brett
>
>
>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20111215/0515e26b/attachment.htm>