Hi Brett Brett Nemeroff wrote: > Bogdan / Jeff, > Thanks for the replies. I got it working now with serialize_branches. > Just goes to show that sometimes the magic is "up to you". :) > > Question tho. I know serialize_branches order branches by q-value. > However, does it smartly handle q-values that are the same to be > parallel branches?
yes, it does - after serialize, all the branches with the same q will be used in the same time -> a combination of serial and parallel forking Regards, Bogdan > Unfortunately I don't have a simple way to test > that out. > > Thanks, > Brett > > > > On Thu, Mar 25, 2010 at 5:38 AM, Bogdan-Andrei Iancu > <[email protected]> wrote: > >> Hi Brett, >> >> As Jeff already pointed out (and I'm making it official ;) ), the >> get_redirects() creates parallel branches. If you want to use them in a >> serial approach, you need to use the serialize_branches() function right >> after the get_redirects() -> it will order the branches according to q >> value and prepare them for serial forking. >> >> Regards, >> Bogdan >> >> Brett Nemeroff wrote: >> >>> Hello All, >>> I have a question about 302 redirects.Maybe I'm just misunderstanding >>> how it's supposed to work.. >>> >>> I get the following redirect: >>> >>> SIP/2.0 302 Moved temporarily. >>> >>> Via:SIP/2.0/UDP >>> 192.168.21.10;branch=z9hG4bK6cd5.ae1f6c43.0,SIP/2.0/UDP >>> 10.10.10.11:5060;branch=z9hG4bK-a96e3-4baac9a7-8c685c67-5898d54b. >>> >>> From:<sip:[email protected]:5060 >>> <http://sip:[email protected]:5060>>;tag=a9d5ed0-13c4-4baac9a7-8c685c67-19c2a61a. >>> >>> To:<sip:[email protected]:5060 >>> <http://sip:[email protected]:5060>>;tag=100063687-1269483944267. >>> >>> Call-ID:cxc-410-65762490-a9d5ed0-13c4-4baac9a7-8c685c67-17d58...@10.10.10.11 >>> <mailto:call-id%3acxc-410-65762490-a9d5ed0-13c4-4baac9a7-8c685c67-17d58...@10.10.10.11>. >>> >>> CSeq:1 INVITE. >>> >>> Record-Route:<sip:192.168.21.10;lr=on;did=f8d.623e93f6>. >>> >>> Contact:<sip:[email protected]:5060;user=phone>;q=0.5,<sip:[email protected]:5060;user=phone>;q=0.25. >>> >>> Content-Length:0. >>> >>> >>> And in my failure route I have: >>> >>> if (t_check_status("302")) { >>> >>> get_redirects("*"); >>> >>> t_relay(); >>> >>> exit; >>> >>> } >>> >>> >>> Now when I watch a sip trace, right after the 302, an INVITE fires off >>> to BOTH 192.168.50.10 and 192.168.30.10 at the exact same time. The q >>> values are different, shouldn't they be serial? >>> >>> I'm not entirely sure how much "magic" is handled in the q-value and >>> how much needs to be scripted.. But I was under the impression that >>> this magic was "fully automatic" >>> >>> Thanks! >>> -Brett >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Users mailing list >>> [email protected] >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >>> >> -- >> Bogdan-Andrei Iancu >> www.voice-system.ro >> >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -- Bogdan-Andrei Iancu www.voice-system.ro _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
