Re: [SR-Users] Enum module and parallel branching

2016-05-17 Thread Loic Chabert
Hello Juha, Thanks for your help, these functions help me to achieve round-robin invite requests. Calls these functions in failure_route permit to move one branch to the next one. Regards. 2016-05-16 15:59 GMT+02:00 Juha Heinanen : > Loic Chabert writes: > > > Q value follow DNS NAPTER respons

Re: [SR-Users] Enum module and parallel branching

2016-05-16 Thread Juha Heinanen
Loic Chabert writes: > Q value follow DNS NAPTER response order. > > Any ideas why my invite request has been sent at the same time, and not one > after another ? Special parameter needed in tm module ? perhaps you should try t_load_contacts()/next_contacts() calls. -- juha ___

Re: [SR-Users] Enum module and parallel branching

2016-05-16 Thread Loic Chabert
Hello guys, After 3 days of tests, same result. As describe in TM module, Q parameter ordering request transmission. When i check Q value, each branch have a different value: branch_route[MANAGE_BRANCH] { xlog("L_INFO", "new [$T_branch_idx] $(branch(q)[$T_branch_idx]) to $bf $ru\n"); }

[SR-Users] Enum module and parallel branching

2016-05-12 Thread Loic Chabert
Hello, I'm trying to use enum module at core level to route my numbers to end-point asterisk servers. As i read (and validated by tests), when a phone number has two DNS NAPTER entries, enum module create two branch, one for each entries, and send request to asterisk servers (in the same time). D