16 May
2016
16 May
'16
3:47 p.m.
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");
}
May 16 14:45:02 kamailio-rt /usr/sbin/kamailio[22138]: INFO: <script>: new
[0] 980 to 0 sip:+33970720973@vgw-master.local
May 16 14:45:02 kamailio-rt /usr/sbin/kamailio[22138]: INFO: <script>: new
[1] 970 to 0 sip:+33970720973@vgw-backup.local
May 16 14:45:02 kamailio-rt /usr/sbin/kamailio[22138]: INFO: <script>: new
[2] <null> to 0 sip:+33970720973@vgw3.local
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 ?
Regards.
2016-05-12 14:48 GMT+02:00 Loic Chabert <chabert.loic.74(a)gmail.com>om>:
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).
Do you know any tricks or functions to disable parallel branching, and
make serial branching instead (following responses returned by asterisk) ?
I have also change preference and order in dns config file, same results.
Thanks in advance.
Regards.