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 •Jul 13 10:26:17 proxy02 /usr/local/sbin/opensips[2917]: DBG:core:serialize_branches: Branch information <sip:[email protected]:5060,sip:[email protected]:5060,,1000,0>

Right?



On Aug 8, 2011 3:13pm, Bogdan-Andrei Iancu <[email protected]> wrote:












Hi Duane,





Looking in the logs:







Jul 13 10:26:17 proxy02

/usr/local/sbin/opensips[2917]: DBG:core:serialize_branches: Msg

information 122:53404,,,70,0>






Jul 13 10:26:17 proxy02

/usr/local/sbin/opensips[2917]: DBG:core:serialize_branches:

Branch information

5060,sip:[email protected]: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









U 2011/07/13 10:49:04.650882

173.XXX.XXX.107:5060 -> 64.136.174.30:5060






INVITE sip:[email protected]:5060

SIP/2.0.






Record-Route:

ca22d05c94774292b9249854dada78de;did=3b5.b8577b82>.






Via: SIP/2.0/UDP

173.XXX.XXX.107;branch=z9hG4bK34d7.0f26b417.0.






Via: SIP/2.0/UDP

64.132.245.122:53383;received=64.132.245.122;rport=53383;branch=z9hG4bKPj26a970ba1b3f44f9b823cbbe4c063bd6.






Max-Forwards: 69.






From: "SecondDell" sip:[email protected]>;tag=ca22d05c94774292b9249854dada78de.






To: sip:[email protected]>.






Contact: sip:[email protected]:53383>.






Call-ID: a46fcbf5977c40c6aa23bac44aa05ff4.






CSeq: 3377 INVITE.






Allow: SUBSCRIBE, NOTIFY, PRACK, INVITE, ACK,

BYE, CANCEL, UPDATE, MESSAGE, REFER.






Supported: 100rel, norefersub.






User-Agent: Blink 0.2.7 (Windows).






Content-Type: application/sdp.






Content-Length: 693.






P-hint: inbound->inbound .






P-hint: Route[6]: mediaproxy .







I just upgraded to 1.7 and that didn't matter.





_______________________________________________

Users mailing list

[email protected]

http://lists.opensips.org/cgi-bin/mailman/listinfo/users











--

Bogdan-Andrei Iancu

OpenSIPS eBootcamp - 19th of September 2011

OpenSIPS solutions and "know-how"







_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to