Just to be sure we are on the same page. The RURI is 90127X2XX9. I don't want this number to have a $du. The one that needs to have a $du is 9014XX7XX9. And correct me if I am wrong but this shows that it does have $du set as
<br />•Jul 13 10:26:17 proxy02 /usr/local/sbin/opensips[2917]: DBG:core:serialize_branches: Branch information <sip:9014XX7XX9@64.136.174.30:5060,sip:9014XX7XX9@173.203.82.88:5060,,1000,0>
<br />
<br />Right?
<br />
<br />
<br />
<br />On Aug 8, 2011 3:13pm, Bogdan-Andrei Iancu <bogdan@opensips.org> wrote:
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> Hi Duane,
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> Looking in the logs:
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> Jul 13 10:26:17 proxy02
<br />>
<br />> /usr/local/sbin/opensips[2917]: DBG:core:serialize_branches: Msg
<br />>
<br />> information 122:53404,,,70,0>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> Jul 13 10:26:17 proxy02
<br />>
<br />> /usr/local/sbin/opensips[2917]: DBG:core:serialize_branches:
<br />>
<br />> Branch information
<br />>
<br />> 5060,sip:9014XX7XX9@173.203.82.88:5060,,1000,0>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> As you can see, the RURI branch has no $du, just $ru.
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> So, after appending the branch, when setting the new one, you have
<br />>
<br />> to set both ru and du again.
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> Regards,
<br />>
<br />>
<br />> Bogdan
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> On 07/13/2011 07:59 PM, Duane Larson wrote:
<br />>
<br />>
<br />>
<br />> This week just isn't my week when it comes to
<br />>
<br />> serialize_branch. I just noticed that when I set $ru then $du
<br />>
<br />> then append_branch and then set $ru again with a different uri
<br />>
<br />> and serialize the call that should be forwarded to the $du isn't
<br />>
<br />> being forwarded. Instead the call goes directly to the ip that
<br />>
<br />> is in $ru. This can be seen in the following debugs that I
<br />>
<br />> already posted to Saul for my Mediaproxy issue.
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> Syslog Debug
<br />>
<br />>
<br />> http://pastebin.com/ZpsR5WG8
<br />>
<br />>
<br />> Do a search for "serialize_branches: Branch information" and
<br />>
<br />> you will see that the branch uri and duri are all set.
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> Then in this siptrace you see that opensips doesn't send it
<br />>
<br />> to the $du destination but instead sends it directly to the uri
<br />>
<br />> in $ru.
<br />>
<br />>
<br />> http://pastebin.com/Rvg6nNGa
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> U 2011/07/13 10:49:04.650882
<br />>
<br />> 173.XXX.XXX.107:5060 -> 64.136.174.30:5060
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> INVITE sip:9014XX7XX9@64.136.174.30:5060
<br />>
<br />> SIP/2.0.
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> Record-Route:
<br />>
<br />> ca22d05c94774292b9249854dada78de;did=3b5.b8577b82>.
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> Via: SIP/2.0/UDP
<br />>
<br />> 173.XXX.XXX.107;branch=z9hG4bK34d7.0f26b417.0.
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> Via: SIP/2.0/UDP
<br />>
<br />> 64.132.245.122:53383;received=64.132.245.122;rport=53383;branch=z9hG4bKPj26a970ba1b3f44f9b823cbbe4c063bd6.
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> Max-Forwards: 69.
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> From: "SecondDell" sip:90133XXX18@irock.com>;tag=ca22d05c94774292b9249854dada78de.
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> To: sip:90127X2XX9@irock.com>.
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> Contact: sip:zdcrgabl@64.132.245.122:53383>.
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> Call-ID: a46fcbf5977c40c6aa23bac44aa05ff4.
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> CSeq: 3377 INVITE.
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> Allow: SUBSCRIBE, NOTIFY, PRACK, INVITE, ACK,
<br />>
<br />> BYE, CANCEL, UPDATE, MESSAGE, REFER.
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> Supported: 100rel, norefersub.
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> User-Agent: Blink 0.2.7 (Windows).
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> Content-Type: application/sdp.
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> Content-Length: 693.
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> P-hint: inbound->inbound .
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> P-hint: Route[6]: mediaproxy .
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> I just upgraded to 1.7 and that didn't matter.
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> _______________________________________________
<br />>
<br />> Users mailing list
<br />>
<br />> Users@lists.opensips.org
<br />>
<br />> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />> --
<br />>
<br />> Bogdan-Andrei Iancu
<br />>
<br />> OpenSIPS eBootcamp - 19th of September 2011
<br />>
<br />> OpenSIPS solutions and "know-how"
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>
<br />>