system
September 9, 2011, 3:14pm
1
Hi!
Issue: inbound calls to the SIP Trunk are, intermittently, not coming through to the Asterisk server. I believe due to some weird trunk state.
When using ‘sip set debug on’ I notice the SIP Trunk does a REGISTER to the VoIP provider and getting a 200 OK. At this state, the Asterisk server properly receives inbound calls.
A couple of seconds later, Asterisk does an OPTIONS to the VoIP provider. It receives a 401 Unauthorized. At THIS state, the Asterisk server CAN NOT receive inbound calls.
The Asterisk server cycles between these states: REGISTER + OK, then OPTIONS + Unauthorized. In order for the Asterisk to see an inbound call from the VoIP provider, it needs to be in the REGISTER + OK state.
Is there some configuration missing? The server is non-NAT.
I also notice a couple of seconds after the SIP Trunk has registered that Asterisk debug is telling me it is “Scheduling destruction of SIP dialog X”, where X is the trunk REGISTER dialog. Perhaps this is normal behavior?
Regards,
david55
September 9, 2011, 3:23pm
2
Looks like there is a nice DoS vulnerability with that service provider!
The sending of OPTIONS is controlled by the qualify option in sip.conf.
system
September 9, 2011, 4:11pm
3
Ah! So simply setting ‘qualify=no’ should do it?
/ Ulf
system
September 9, 2011, 4:21pm
4
I tried using qualify=no. If used, the SIP trunk availabiliy dies immediately after the SIP dialog has been scheduled&destroyed.
Is this rather an issue with the VoIP provider? Should qualify=yes work, e.g. responding with something more useful than 401 Unauthorized?
Regards,
system
September 9, 2011, 4:29pm
5
Here is the actual output when using qualify=no:
170CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>sip:MY.SIP.TRUNK.USER@VOIP-PROVIDER.ADDRESS ;tag=as253b2b62sip:MY.SIP.TRUNK.USER@VOIP-PROVIDER.ADDRESS 1ed3625f0411691e51697d10060798f2@MY.ASTERISK.IP -ADDRESSsip:s@MY.ASTERISK.IP-ADDRESS:5060
<— SIP read from UDP:VOIP-PROVIDER.IP-ADDRESS:5060 —>sip:s@MY.ROUTER.IP:64789 ;expires=180sip:s@MY.ROUTER.IP:3071 ;expires=180sip:MY.SIP.TRUNK.USER@VOIP-PROVIDER.ADDRESS ;tag=6a6ce505sip:MY.SIP.TRUNK.USER@VOIP-PROVIDER.ADDRESS ;tag=as253b2b621ed3625f0411691e51697d10060798f2@MY.ASTERISK.IP -ADDRESS
<------------->'1ed3625f0411691e51697d10060798f2@MY.ASTERISK.IP -ADDRESS’ in 32000 ms (Method: REGISTER)CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI> ------ so, here inbound works ------------CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>'1ed3625f0411691e51697d10060798f2@MY.ASTERISK.IP -ADDRESS’ Method: REGISTERCLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> ------- here inbound does NOT work --------------- CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>sip:MY.SIP.TRUNK.USER@VOIP-PROVIDER.ADDRESS ;tag=as14b019e0sip:MY.SIP.TRUNK.USER@VOIP-PROVIDER.ADDRESS 1ed3625f0411691e51697d10060798f2@MY.ASTERISK.IP -ADDRESSsip:s@MY.ASTERISK.IP-ADDRESS:5060
<— SIP read from UDP:VOIP-PROVIDER.IP-ADDRESS:5060 —>sip:s@MY.ROUTER.IP:3071 ;expires=180sip:s@MY.ROUTER.IP:12881 ;expires=180sip:MY.SIP.TRUNK.USER@VOIP-PROVIDER.ADDRESS ;tag=87e45325sip:MY.SIP.TRUNK.USER@VOIP-PROVIDER.ADDRESS ;tag=as14b019e01ed3625f0411691e51697d10060798f2@MY.ASTERISK.IP -ADDRESS
<------------->'1ed3625f0411691e51697d10060798f2@MY.ASTERISK.IP -ADDRESS’ in 32000 ms (Method: REGISTER)CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> ---- and we’re up again, it keeps cycling like this -------- CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>CLI> CLI>
system
September 9, 2011, 4:31pm
6
Interesting - I notice the IP of my non-NAT firewall/router is seen in the SIP messages. Could this be a reason for things failing? I woulda thought my public-IP Asterisk server would be the one visible.
Regards,
Hi
Have you got the localnet and externip set correctly ?
also has the router got a sip alg option ? I have seen this if enabled cause very odd problems.
Ian
system
September 10, 2011, 2:21pm
8
Update: it was indeed the NAT translation that caused havoc. Disabling NAT solved the issue!
/ Ulf