Registration Issues

Asterisk Asterisk Support
1

Hey guys -

I’m having some minor issues and I need your help. First off, here is my setup - I have Asterisk 1.8.11 installed with 20 extensions and three SIP trunk registrations. 9 extensions are local, the other extensions cross over site-to-site VPN connections - All phones are Cisco 7960 with SIP firmware installed. My firewall is a Cisco ASA 5505 with SIP and h323 inspection disabled and my box has an AMD A4-5300 CPU, 8GB RAM and a MSI FM2-A55M-E33 motherboard.

My problem is that sometimes (quite often), out of nowhere, all of my Extensions become UNREACHABLE, and my SIP trunks have to re-register. I see nothing in the CLI indicating that this is happening. I’m seeing some weird behavior in the log (below), and I have no idea what is going on.

I have tried adding ignoreregexpire=yes and rtcachefriends=yes to sip.conf, with no change.

Please help me resolve this. Let me know if I didn’t provide enough info - I will respond quickly. =)

Thanks in advance
-Jason

[2013-02-09 05:11:50] VERBOSE[3584] dnsmgr.c: > doing dnsmgr_lookup for ‘atlanta.voip.ms’
[2013-02-09 05:11:55] NOTICE[3584] chan_sip.c: – Registration for '151xxx@atlanta.voip.ms’ timed out, trying again (Attempt #5)
[2013-02-09 05:11:55] VERBOSE[3584] dnsmgr.c: > doing dnsmgr_lookup for ‘newyork.voip.ms’
[2013-02-09 05:12:00] NOTICE[3584] chan_sip.c: – Registration for '151xxx@newyork.voip.ms’ timed out, trying again (Attempt #5)
[2013-02-09 05:12:00] VERBOSE[3584] dnsmgr.c: > doing dnsmgr_lookup for ‘sip.flowroute.com’
[2013-02-09 05:12:05] NOTICE[3584] chan_sip.c: – Registration for '22xxxxxx@sip.flowroute.com’ timed out, trying again (Attempt #3)
[2013-02-09 05:12:05] VERBOSE[3584] chan_sip.c: – Registered SIP ‘9224’ at 192.168.189.107:5060
[2013-02-09 05:12:05] VERBOSE[3584] chan_sip.c: – Registered SIP ‘9201’ at 192.168.189.105:5060
[2013-02-09 05:12:05] VERBOSE[3584] chan_sip.c: – Registered SIP ‘9223’ at 192.168.189.110:5060
[2013-02-09 05:12:05] VERBOSE[3584] chan_sip.c: – Registered SIP ‘9222’ at 192.168.189.102:5060
[2013-02-09 05:12:05] VERBOSE[3584] chan_sip.c: – Registered SIP ‘9203’ at 192.168.189.106:5060
[2013-02-09 05:12:05] VERBOSE[3584] chan_sip.c: – Registered SIP ‘9221’ at 192.168.189.108:5060
[2013-02-09 05:12:05] VERBOSE[3584] chan_sip.c: – Registered SIP ‘9202’ at 192.168.189.100:5060
[2013-02-09 05:12:05] VERBOSE[3584] chan_sip.c: – Registered SIP ‘9264’ at 192.168.157.102:5060
[2013-02-09 05:12:05] VERBOSE[3584] chan_sip.c: – Registered SIP ‘9243’ at 192.168.97.31:5060
[2013-02-09 05:12:05] VERBOSE[3584] chan_sip.c: – Registered SIP ‘9261’ at 192.168.157.101:5060
[2013-02-09 05:12:05] VERBOSE[3584] chan_sip.c: – Registered SIP ‘9263’ at 192.168.157.104:5060
[2013-02-09 05:12:05] VERBOSE[3584] chan_sip.c: – Registered SIP ‘9265’ at 192.168.157.106:5060
[2013-02-09 05:12:05] VERBOSE[3584] chan_sip.c: – Registered SIP ‘9242’ at 192.168.97.29:5060
[2013-02-09 05:12:05] VERBOSE[3584] chan_sip.c: – Registered SIP ‘9241’ at 192.168.97.28:5060
[2013-02-09 05:12:05] VERBOSE[3584] chan_sip.c: – Registered SIP ‘9262’ at 192.168.157.105:5060
[2013-02-09 05:12:05] NOTICE[3584] chan_sip.c: Error parsing sipfrag in NOTIFY in response to REFER.
[2013-02-09 05:12:05] NOTICE[3584] chan_sip.c: Transfer failed. Sorry. Nothing further to do with this call
[2013-02-09 05:12:05] NOTICE[3584] chan_sip.c: Error parsing sipfrag in NOTIFY in response to REFER.
[2013-02-09 05:12:05] NOTICE[3584] chan_sip.c: Transfer failed. Sorry. Nothing further to do with this call
[2013-02-09 05:12:05] VERBOSE[3584] dnsmgr.c: > doing dnsmgr_lookup for ‘newyork.voip.ms’
[2013-02-09 05:12:10] NOTICE[3584] chan_sip.c: Peer ‘9224’ is now UNREACHABLE! Last qualify: 0
[2013-02-09 05:12:10] NOTICE[3584] chan_sip.c: Peer ‘9201’ is now UNREACHABLE! Last qualify: 0
[2013-02-09 05:12:10] NOTICE[3584] chan_sip.c: Peer ‘9223’ is now UNREACHABLE! Last qualify: 0
[2013-02-09 05:12:10] NOTICE[3584] chan_sip.c: Peer ‘9222’ is now UNREACHABLE! Last qualify: 0
[2013-02-09 05:12:10] NOTICE[3584] chan_sip.c: Peer ‘9203’ is now UNREACHABLE! Last qualify: 0
[2013-02-09 05:12:10] NOTICE[3584] chan_sip.c: Peer ‘9221’ is now UNREACHABLE! Last qualify: 0
[2013-02-09 05:12:10] NOTICE[3584] chan_sip.c: Peer ‘9202’ is now UNREACHABLE! Last qualify: 0
[2013-02-09 05:12:10] NOTICE[3584] chan_sip.c: Peer ‘9264’ is now UNREACHABLE! Last qualify: 0
[2013-02-09 05:12:10] NOTICE[3584] chan_sip.c: Peer ‘9243’ is now UNREACHABLE! Last qualify: 0
[2013-02-09 05:12:10] NOTICE[3584] chan_sip.c: Peer ‘9261’ is now UNREACHABLE! Last qualify: 0
[2013-02-09 05:12:10] NOTICE[3584] chan_sip.c: Peer ‘9263’ is now UNREACHABLE! Last qualify: 0
[2013-02-09 05:12:10] NOTICE[3584] chan_sip.c: Peer ‘9265’ is now UNREACHABLE! Last qualify: 0
[2013-02-09 05:12:10] NOTICE[3584] chan_sip.c: Peer ‘9242’ is now UNREACHABLE! Last qualify: 0
[2013-02-09 05:12:10] NOTICE[3584] chan_sip.c: Peer ‘9241’ is now UNREACHABLE! Last qualify: 0
[2013-02-09 05:12:10] NOTICE[3584] chan_sip.c: Peer ‘9262’ is now UNREACHABLE! Last qualify: 0
[2013-02-09 05:12:10] VERBOSE[3584] dnsmgr.c: > doing dnsmgr_lookup for ‘atlanta.voip.ms’
[2013-02-09 05:12:15] VERBOSE[3584] dnsmgr.c: > doing dnsmgr_lookup for ‘atlanta.voip.ms’
[2013-02-09 05:12:20] NOTICE[3584] chan_sip.c: – Registration for '151xxx@atlanta.voip.ms’ timed out, trying again (Attempt #7)
[2013-02-09 05:12:20] VERBOSE[3584] dnsmgr.c: > doing dnsmgr_lookup for ‘newyork.voip.ms’
[2013-02-09 05:12:25] NOTICE[3584] chan_sip.c: – Registration for '151xxx@newyork.voip.ms’ timed out, trying again (Attempt #7)
[2013-02-09 05:12:25] NOTICE[3584] chan_sip.c: Error parsing sipfrag in NOTIFY in response to REFER.
[2013-02-09 05:12:25] NOTICE[3584] chan_sip.c: Transfer failed. Sorry. Nothing further to do with this call
2013-02-09 05:12:25] VERBOSE[3584] dnsmgr.c: > doing dnsmgr_lookup for ‘sip.flowroute.com’
[2013-02-09 05:12:30] NOTICE[3584] chan_sip.c: – Registration for '22xxxxxx@sip.flowroute.com’ timed out, trying again (Attempt #4)
[2013-02-09 05:12:30] NOTICE[3584] chan_sip.c: Error parsing sipfrag in NOTIFY in response to REFER.
[2013-02-09 05:12:30] NOTICE[3584] chan_sip.c: Transfer failed. Sorry. Nothing further to do with this call
[2013-02-09 05:12:30] VERBOSE[3584] dnsmgr.c: > doing dnsmgr_lookup for ‘atlanta.voip.ms’
[2013-02-09 05:12:35] VERBOSE[3584] dnsmgr.c: > doing dnsmgr_lookup for ‘sip.flowroute.com’
[2013-02-09 05:12:40] VERBOSE[3584] dnsmgr.c: > doing dnsmgr_lookup for ‘atlanta.voip.ms’
[2013-02-09 05:12:45] NOTICE[3584] chan_sip.c: – Registration for '151xxx@atlanta.voip.ms’ timed out, trying again (Attempt #9)
[2013-02-09 05:12:45] VERBOSE[3584] dnsmgr.c: > doing dnsmgr_lookup for ‘newyork.voip.ms’
[2013-02-09 05:12:50] NOTICE[3584] chan_sip.c: – Registration for '151xxx@newyork.voip.ms’ timed out, trying again (Attempt #8)
[2013-02-09 05:12:50] VERBOSE[3584] dnsmgr.c: > doing dnsmgr_lookup for ‘sip.flowroute.com’
[2013-02-09 05:12:55] NOTICE[3584] chan_sip.c: – Registration for '22xxxxxx@sip.flowroute.com’ timed out, trying again (Attempt #6)
[2013-02-09 05:12:55] NOTICE[3584] chan_sip.c: Error parsing sipfrag in NOTIFY in response to REFER.
[2013-02-09 05:12:55] NOTICE[3584] chan_sip.c: Transfer failed. Sorry. Nothing further to do with this call
[2013-02-09 05:12:55] NOTICE[3584] chan_sip.c: Error parsing sipfrag in NOTIFY in response to REFER.
[2013-02-09 05:12:55] NOTICE[3584] chan_sip.c: Transfer failed. Sorry. Nothing further to do with this call
[2013-02-09 05:12:55] NOTICE[3584] chan_sip.c: Error parsing sipfrag in NOTIFY in response to REFER.
[2013-02-09 05:12:55] NOTICE[3584] chan_sip.c: Transfer failed. Sorry. Nothing further to do with this call
[2013-02-09 05:12:55] NOTICE[3584] chan_sip.c: Error parsing sipfrag in NOTIFY in response to REFER.
[2013-02-09 05:12:55] NOTICE[3584] chan_sip.c: Transfer failed. Sorry. Nothing further to do with this call
[2013-02-09 05:12:55] VERBOSE[3584] dnsmgr.c: > doing dnsmgr_lookup for ‘atlanta.voip.ms’
[2013-02-09 05:13:00] VERBOSE[3584] dnsmgr.c: > doing dnsmgr_lookup for ‘newyork.voip.ms’
[2013-02-09 05:13:05] VERBOSE[3584] dnsmgr.c: > doing dnsmgr_lookup for ‘atlanta.voip.ms’
[2013-02-09 05:13:10] NOTICE[3584] chan_sip.c: – Registration for '151xxx@atlanta.voip.ms’ timed out, trying again (Attempt #11)
[2013-02-09 05:13:10] VERBOSE[3584] dnsmgr.c: > doing dnsmgr_lookup for ‘newyork.voip.ms’
[2013-02-09 05:13:15] NOTICE[3584] chan_sip.c: – Registration for '151xxx@newyork.voip.ms’ timed out, trying again (Attempt #10)
[2013-02-09 05:13:15] VERBOSE[3584] dnsmgr.c: > doing dnsmgr_lookup for ‘sip.flowroute.com’
[2013-02-09 05:13:20] NOTICE[3584] chan_sip.c: – Registration for '22xxxxxx@sip.flowroute.com’ timed out, trying again (Attempt #7)
[2013-02-09 05:13:20] NOTICE[3584] chan_sip.c: Error parsing sipfrag in NOTIFY in response to REFER.
[2013-02-09 05:13:20] NOTICE[3584] chan_sip.c: Transfer failed. Sorry. Nothing further to do with this call
[2013-02-09 05:13:20] NOTICE[3584] chan_sip.c: Error parsing sipfrag in NOTIFY in response to REFER.
[2013-02-09 05:13:20] NOTICE[3584] chan_sip.c: Transfer failed. Sorry. Nothing further to do with this call
[2013-02-09 05:13:20] NOTICE[3584] chan_sip.c: Error parsing sipfrag in NOTIFY in response to REFER.
[2013-02-09 05:13:20] NOTICE[3584] chan_sip.c: Transfer failed. Sorry. Nothing further to do with this call
[2013-02-09 05:13:20] NOTICE[3584] chan_sip.c: Error parsing sipfrag in NOTIFY in response to REFER.
[2013-02-09 05:13:20] NOTICE[3584] chan_sip.c: Transfer failed. Sorry. Nothing further to do with this call
[2013-02-09 05:13:20] VERBOSE[3584] dnsmgr.c: > doing dnsmgr_lookup for ‘atlanta.voip.ms’
[2013-02-09 05:13:25] VERBOSE[3584] dnsmgr.c: > doing dnsmgr_lookup for ‘newyork.voip.ms’
[2013-02-09 05:13:30] VERBOSE[3584] dnsmgr.c: > doing dnsmgr_lookup for ‘atlanta.voip.ms’
[2013-02-09 05:13:35] NOTICE[3584] chan_sip.c: – Registration for '151xxx@atlanta.voip.ms’ timed out, trying again (Attempt #13)
[2013-02-09 05:13:35] VERBOSE[3584] dnsmgr.c: > doing dnsmgr_lookup for ‘newyork.voip.ms’
[2013-02-09 05:13:40] NOTICE[3584] chan_sip.c: – Registration for '151xxx@newyork.voip.ms’ timed out, trying again (Attempt #12)
[2013-02-09 05:13:40] NOTICE[3584] chan_sip.c: Error parsing sipfrag in NOTIFY in response to REFER.
[2013-02-09 05:13:40] NOTICE[3584] chan_sip.c: Transfer failed. Sorry. Nothing further to do with this call
[2013-02-09 05:13:40] VERBOSE[3584] dnsmgr.c: > doing dnsmgr_lookup for ‘atlanta.voip.ms’
[2013-02-09 05:13:45] VERBOSE[3584] dnsmgr.c: > doing dnsmgr_lookup for ‘newyork.voip.ms’
[2013-02-09 05:13:50] NOTICE[3584] chan_sip.c: Error parsing sipfrag in NOTIFY in response to REFER.
[2013-02-09 05:13:50] NOTICE[3584] chan_sip.c: Transfer failed. Sorry. Nothing further to do with this call
[2013-02-09 05:13:50] NOTICE[3584] chan_sip.c: Peer ‘voipms-nyc’ is now Reachable. (24ms / 2000ms)
[2013-02-09 05:13:51] NOTICE[3584] chan_sip.c: Peer ‘9224’ is now Reachable. (245ms / 2000ms)
[2013-02-09 05:13:51] NOTICE[3584] chan_sip.c: Peer ‘9222’ is now Reachable. (240ms / 2000ms)
[2013-02-09 05:13:51] NOTICE[3584] chan_sip.c: Peer ‘9201’ is now Reachable. (258ms / 2000ms)
[2013-02-09 05:13:51] NOTICE[3584] chan_sip.c: Peer ‘9202’ is now Reachable. (250ms / 2000ms)
[2013-02-09 05:13:51] NOTICE[3584] chan_sip.c: Peer ‘9221’ is now Reachable. (262ms / 2000ms)
[2013-02-09 05:13:51] NOTICE[3584] chan_sip.c: Peer ‘9263’ is now Reachable. (224ms / 2000ms)
[2013-02-09 05:13:51] NOTICE[3584] chan_sip.c: Peer ‘9265’ is now Reachable. (226ms / 2000ms)
[2013-02-09 05:13:51] NOTICE[3584] chan_sip.c: Peer ‘9264’ is now Reachable. (225ms / 2000ms)
[2013-02-09 05:13:51] NOTICE[3584] chan_sip.c: Peer ‘voipms_atl’ is now Reachable. (379ms / 2000ms)
[2013-02-09 05:13:51] NOTICE[3584] chan_sip.c: Peer ‘9243’ is now Reachable. (226ms / 2000ms)
[2013-02-09 05:13:51] NOTICE[3584] chan_sip.c: Peer ‘9223’ is now Reachable. (272ms / 2000ms)
[2013-02-09 05:13:51] NOTICE[3584] chan_sip.c: Peer ‘9203’ is now Reachable. (274ms / 2000ms)
[2013-02-09 05:13:51] NOTICE[3584] chan_sip.c: Peer ‘9242’ is now Reachable. (230ms / 2000ms)
[2013-02-09 05:13:51] NOTICE[3584] chan_sip.c: Peer ‘9241’ is now Reachable. (225ms / 2000ms)
[2013-02-09 05:13:51] NOTICE[3584] chan_sip.c: Peer ‘9262’ is now Reachable. (237ms / 2000ms)
[2013-02-09 05:13:51] NOTICE[3584] chan_sip.c: Error parsing sipfrag in NOTIFY in response to REFER.
[2013-02-09 05:13:51] NOTICE[3584] chan_sip.c: Transfer failed. Sorry. Nothing further to do with this call
[2013-02-09 05:13:55] NOTICE[3584] chan_sip.c: Error parsing sipfrag in NOTIFY in response to REFER.
[2013-02-09 05:13:55] NOTICE[3584] chan_sip.c: Transfer failed. Sorry. Nothing further to do with this call
[2013-02-09 05:14:00] NOTICE[3584] chan_sip.c: Error parsing sipfrag in NOTIFY in response to REFER.
[2013-02-09 05:14:00] NOTICE[3584] chan_sip.c: Transfer failed. Sorry. Nothing further to do with this call
[2013-02-09 05:14:01] NOTICE[3584] chan_sip.c: Error parsing sipfrag in NOTIFY in response to REFER.
[2013-02-09 05:14:01] NOTICE[3584] chan_sip.c: Transfer failed. Sorry. Nothing further to do with this call
[2013-02-09 05:14:03] NOTICE[3584] chan_sip.c: Error parsing sipfrag in NOTIFY in response to REFER.
[2013-02-09 05:14:03] NOTICE[3584] chan_sip.c: Transfer failed. Sorry. Nothing further to do with this call
[2013-02-09 05:14:07] NOTICE[3584] chan_sip.c: Error parsing sipfrag in NOTIFY in response to REFER.
[2013-02-09 05:14:07] NOTICE[3584] chan_sip.c: Transfer failed. Sorry. Nothing further to do with this call
[2013-02-09 05:14:11] NOTICE[3584] chan_sip.c: Error parsing sipfrag in NOTIFY in response to REFER.
[2013-02-09 05:14:11] NOTICE[3584] chan_sip.c: Transfer failed. Sorry. Nothing further to do with this call
[2013-02-09 05:14:15] NOTICE[3584] chan_sip.c: Error parsing sipfrag in NOTIFY in response to REFER.
[2013-02-09 05:14:15] NOTICE[3584] chan_sip.c: Transfer failed. Sorry. Nothing further to do with this call
[2013-02-09 05:14:19] NOTICE[3584] chan_sip.c: Error parsing sipfrag in NOTIFY in response to REFER.
[2013-02-09 05:14:19] NOTICE[3584] chan_sip.c: Transfer failed. Sorry. Nothing further to do with this call
[2013-02-09 05:14:23] NOTICE[3584] chan_sip.c: Error parsing sipfrag in NOTIFY in response to REFER.

2

I have more information on this:

I ended up installing another Ethernet card in the box and connected directly to the outside. This resolves any issues with external registration. For the extensions, I was able to relieve the UNREACHABLE issues by turning off qualify for each extension. I suppose * could not reach the phones and would put them into this state.

This being the case, I’m sure the problem is with the firewalls. All traffic is permitted between all sites, so I’m not sure what the problem with the firewalls could be. Any ideas on this? I would really like to have qualify turned on, if possible. I’m used to seeing the latency of the phone on the CLI instead of unmonitored.

Any help is appreciated.
-Jason

3

Hi,
I had the same issues and was not able to register the trunk. It was all due to firewall rules.
Make sure your IPtables are not blocking the required ports on asterisk server.

4

Are you using VPN connections between sites (Cisco routers on all sites doing VPN connections)?

Turning off qualify does not fix the problem, it only avoids the logs that show a problem with the connectivity. The “UNREACHABLE” messages appear because Asterisk does not receive a response to a SIP Options message that it is sending as a keepallive. Apparently the router or ISP blocks those UDP messages from time to time. But this definitly is a connectivity issue.

5

Thanks for the response, guys.

[quote=“numan82”]Hi,
I had the same issues and was not able to register the trunk. It was all due to firewall rules.
Make sure your IPtables are not blocking the required ports on asterisk server.
[/quote]
I tried turning off the firewall on the box with no change. The trunk registration issue was caused by the hardware firewall, however it had problems registering regardless of if ports were forwarded (5060, 10000-20000) and SIP Inspect was on or off. Currently, it is outside of the hardware firewall, only running IPTables.

[quote=“dejanst”]Are you using VPN connections between sites (Cisco routers on all sites doing VPN connections)?

Turning off qualify does not fix the problem, it only avoids the logs that show a problem with the connectivity. The “UNREACHABLE” messages appear because Asterisk does not receive a response to a SIP Options message that it is sending as a keepallive. Apparently the router or ISP blocks those UDP messages from time to time. But this definitly is a connectivity issue.[/quote]

I agree, this definitely doesn’t fix the problem, it just keeps Asterisk from report the extension as UNREACHABLE, and continues sending calls to it.

Cisco routers and ASA’s are doing all site-to-site VPN connections. Main office has a Cisco ASA 5505, running software version 8.2, one remote office has another Cisco ASA 5505 with the same software and the third office has a Cisco 851 Router with IOS 12.4.

The part I find very strange, is that, as you can see in the log, it would happen for ALL extensions at the same time, including the phones that are in the same location as the system. I don’t think the issue would be the switch (basic 10/100 24 port, unmanaged) but I could be wrong.

I had read somewhere that if the phones are behind a NAT, then the UDP timeout may be too low. Correct me if I’m wrong, but I believe that traffic over a site-to-site connection is not considered natted.

I really wonder if SIP inspection has anything to do with it. I noticed that even after turning it off on the ASA in the main office, my trunks were still registering on another port, other than 5060, with the carrier. This shouldn’t happen if SIP ALG isn’t happening. I have found that this is a huge problem with Cisco ASA software. I haven’t found a version that handles SIP properly. However, would SIP inspection be taking place over the VPN?

6

I know of a similar scenario with Cisco routers (central location and couple of remote locations where Cisco ASA devices are doing VPN connections between the sites) where the same thing is happening. Phones on remote locations are becomming “Unavailable” from time to time for about a minute or two. I am also blaiming this on the Cisco routers, but the admin disagrees with me. There we are also battling occasional voice issues, so keep an eye out on that also.