22 Feb
2013
22 Feb
'13
7:30 p.m.
Hi!
I might have missed something, but I fail to see how to set up this scenario:
I have an AOR with two registred phones. Two reg-id's per phone, four contacts in
all.
I call the AOR and one phone starts ringing, the other call leg gets a 430 Flow Failed
from the edge proxy.
How to I retry the next flow? We're not hitting the failure route, since one phone is
ringing.
Do we need a BRANCH_FAILURE_ROUTE to handle retargeting in a branch while we're in an
open transaction?
/O
28 Feb
28 Feb
3:35 p.m.
Hi,
I don't understand how this will work either?
Can anyone with more experience of the t_???_contact() functions help?
Regards,
Peter
On 22/02/13 18:30, Olle E. Johansson wrote:
Hi!
I might have missed something, but I fail to see how to set up this scenario:
I have an AOR with two registred phones. Two reg-id's per phone, four contacts in
all.
I call the AOR and one phone starts ringing, the other call leg gets a 430 Flow Failed
from the edge proxy.
How to I retry the next flow? We're not hitting the failure route, since one phone is
ringing.
Do we need a BRANCH_FAILURE_ROUTE to handle retargeting in a branch while we're in an
open transaction?
/O
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
8:11 p.m.
Peter Dunkley writes:
I don't understand how this will work either?
Can anyone with more experience of the t_???_contact() functions help?
t_next_contact_flows() would add the working flow to the destination
set, but, as olle wrote, it cannot be called because failure route is
not triggered yet. looks like the current tm architecture would need to
enhanced to support this scenario.
-- juha
4083
days inactive
4089
days old
2 comments
3 participants
participants (3)
-
Juha Heinanen -
Olle E. Johansson -
Peter Dunkley