Given the following SRV records: _sip._udp.tollfree.sip-happens.com. 38400 IN SRV 10 0 5060 sometimes.sip-happens.com. _sip._udp.tollfree.sip-happens.com. 38400 IN SRV 20 0 5070 ares.sip-happens.com.
Why is asterisk (1.4.17) not honouring the priority and not failing over
to using other records when a connection fails?
For a given call to tollfree.sip-happens.com ares.sip-happens.com was
chosen and tried before sometimes.sip-happens.com and additionally, when
the connection to ares.sip-happens.com was being refused there was no
roll-over to sometimes.sip-happens. Here's what asterisk did:
-- Executing [EMAIL PROTECTED]:23] Dial("SIP/anonymous-b5e02fd0",
"SIP/[EMAIL PROTECTED]||") in new stack
-- ast_get_srv: SRV lookup for '_sip._udp.tollfree.sip-happens.com.' mapped
to host ares.sip-happens.com, port 5070
-- Called [EMAIL PROTECTED]
[Oct 17 10:15:46] NOTICE[4973]: chan_sip.c:2920 auto_congest: Auto-congesting
SIP/tollfree.sip-happens.com.-081ddc28
-- SIP/tollfree.sip-happens.com.-081ddc28 is circuit-busy
== Everyone is busy/congested at this time (1:0/1/0)
And here's the packet trace:
10:15:16.612062 IP 67.193.213.184.5060 > 209.9.237.93.5070: SIP, length: 855
10:15:16.652721 IP 209.9.237.93 > 67.193.213.184: ICMP 209.9.237.93 udp port
5070 unreachable, length 556
10:15:17.613997 IP 67.193.213.184.5060 > 209.9.237.93.5070: SIP, length: 855
10:15:17.654697 IP 209.9.237.93 > 67.193.213.184: ICMP 209.9.237.93 udp port
5070 unreachable, length 556
10:15:18.611068 IP 67.193.213.184.5060 > 209.9.237.93.5070: SIP, length: 855
10:15:18.652786 IP 209.9.237.93 > 67.193.213.184: ICMP 209.9.237.93 udp port
5070 unreachable, length 556
10:15:20.614106 IP 67.193.213.184.5060 > 209.9.237.93.5070: SIP, length: 855
10:15:20.654785 IP 209.9.237.93 > 67.193.213.184: ICMP 209.9.237.93 udp port
5070 unreachable, length 556
10:15:24.614115 IP 67.193.213.184.5060 > 209.9.237.93.5070: SIP, length: 855
10:15:24.658934 IP 209.9.237.93 > 67.193.213.184: ICMP 209.9.237.93 udp port
5070 unreachable, length 556
10:15:32.615275 IP 67.193.213.184.5060 > 209.9.237.93.5070: SIP, length: 855
10:15:32.668930 IP 209.9.237.93 > 67.193.213.184: ICMP 209.9.237.93 udp port
5070 unreachable, length 556
10:15:48.614675 IP 67.193.213.184.5060 > 209.9.237.93.5070: SIP, length: 855
10:15:48.655403 IP 209.9.237.93 > 67.193.213.184: ICMP 209.9.237.93 udp port
5070 unreachable, length 556
So, as you can see, the priority was not honoured, nor was the alternate
SRV record used when there was a connection failure. Maybe that's
because it was looking for a lower priority. Is SRV handling in
Asterisk just broken? Or is this a known and fixed bug?
b.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
