[OpenSIPS-Users] serialize_branch breaking $du

Bogdan-Andrei Iancu bogdan at opensips.org
Mon Aug 8 22:13:06 CEST 2011


Hi Duane,

Looking in the logs:

#
Jul 13 10:26:17 proxy02 /usr/local/sbin/opensips[2917]: 
DBG:core:serialize_branches: Msg information 
<sip:90127X2XX9 at 64.132.245.122:53404,,,70,0>
#
Jul 13 10:26:17 proxy02 /usr/local/sbin/opensips[2917]: 
DBG:core:serialize_branches: Branch information 
<sip:9014XX7XX9 at 64.136.174.30:5060,sip:9014XX7XX9 at 173.203.82.88:5060,,1000,0>


As you can see, the RURI branch has no $du, just $ru.

So, after appending the branch, when setting the new one, you have to 
set both ru and du again.

Regards,
Bogdan

On 07/13/2011 07:59 PM, Duane Larson wrote:
> This week just isn't my week when it comes to serialize_branch.  I 
> just noticed that when I set $ru then $du then append_branch and then 
> set $ru again with a different uri and serialize the call that should 
> be forwarded to the $du isn't being forwarded.  Instead the call goes 
> directly to the ip that is in $ru.  This can be seen in the following 
> debugs that I already posted to Saul for my Mediaproxy issue.
> Syslog Debug
> http://pastebin.com/ZpsR5WG8
> Do a search for "serialize_branches: Branch information" and you will 
> see that the branch uri and duri are all set.
> Then in this siptrace you see that opensips doesn't send it to the $du 
> destination but instead sends it directly to the uri in $ru.
> http://pastebin.com/Rvg6nNGa
>
>   1.
>       U 2011/07/13 10:49:04.650882 173.XXX.XXX.107:5060 ->
>       64.136.174.30:5060 <http://64.136.174.30:5060>
>   2.
>       INVITE sip:9014XX7XX9 at 64.136.174.30:5060
>       <http://sip:9014XX7XX9@64.136.174.30:5060> SIP/2.0.
>   3.
>       Record-Route:
>       <sip:173.XXX.XXX.107;lr;ftag=ca22d05c94774292b9249854dada78de;did=3b5.b8577b82>.
>   4.
>       Via: SIP/2.0/UDP 173.XXX.XXX.107;branch=z9hG4bK34d7.0f26b417.0.
>   5.
>       Via: SIP/2.0/UDP
>       64.132.245.122:53383;received=64.132.245.122;rport=53383;branch=z9hG4bKPj26a970ba1b3f44f9b823cbbe4c063bd6.
>   6.
>       Max-Forwards: 69.
>   7.
>       From: "SecondDell" <sip:90133XXX18 at irock.com
>       <mailto:sip%3A90133XXX18 at irock.com>>;tag=ca22d05c94774292b9249854dada78de.
>   8.
>       To: <sip:90127X2XX9 at irock.com <mailto:sip%3A90127X2XX9 at irock.com>>.
>   9.
>       Contact: <sip:zdcrgabl at 64.132.245.122:53383
>       <http://sip:zdcrgabl@64.132.245.122:53383>>.
>  10.
>       Call-ID: a46fcbf5977c40c6aa23bac44aa05ff4.
>  11.
>       CSeq: 3377 INVITE.
>  12.
>       Allow: SUBSCRIBE, NOTIFY, PRACK, INVITE, ACK, BYE, CANCEL,
>       UPDATE, MESSAGE, REFER.
>  13.
>       Supported: 100rel, norefersub.
>  14.
>       User-Agent: Blink 0.2.7 (Windows).
>  15.
>       Content-Type: application/sdp.
>  16.
>       Content-Length: 693.
>  17.
>       P-hint: inbound->inbound .
>  18.
>       P-hint: Route[6]: mediaproxy .
>
> I just upgraded to 1.7 and that didn't matter.
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users


-- 
Bogdan-Andrei Iancu
OpenSIPS eBootcamp - 19th of September 2011
OpenSIPS solutions and "know-how"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20110808/5ee92b00/attachment-0001.htm>


More information about the Users mailing list