Timeouts to SIP provider ...
Timeouts to SIP provider ...
(OP)
Hi everyone:
This is somewhat connected to my last post, but not entirely. When our SIP service died last week, I attributed it to the flood of requests we were getting with port 5060 being open. The port has been closed for several days now, and this morning, we lost service again. At 5:40am, the asterisk/full log indicated that the registration request had timed out to the SIP provider. I saw about 600 instances of re-register attempts. During this time, calls weren't going out or coming in. I rebooted the UCx and after everything came up, calls are coming through normally again.
I've spoken to our SIP provider, and they claim there's nothing on their end that's causing the problem, and it must be on our end. Would you have any wisdom or things I could check? I suppose it's possible that we may have had an interruption with our ISP and service may have been interrupted campus-wide, but one would think that the SIP trunk would simply re-register. Not understanding why re-register attempts keep timing out until we do a reboot.
I'm happy to post log entries if you need them.
Thanks for any wisdom you might be able to provide. :)
This is somewhat connected to my last post, but not entirely. When our SIP service died last week, I attributed it to the flood of requests we were getting with port 5060 being open. The port has been closed for several days now, and this morning, we lost service again. At 5:40am, the asterisk/full log indicated that the registration request had timed out to the SIP provider. I saw about 600 instances of re-register attempts. During this time, calls weren't going out or coming in. I rebooted the UCx and after everything came up, calls are coming through normally again.
I've spoken to our SIP provider, and they claim there's nothing on their end that's causing the problem, and it must be on our end. Would you have any wisdom or things I could check? I suppose it's possible that we may have had an interruption with our ISP and service may have been interrupted campus-wide, but one would think that the SIP trunk would simply re-register. Not understanding why re-register attempts keep timing out until we do a reboot.
I'm happy to post log entries if you need them.
Thanks for any wisdom you might be able to provide. :)
RE: Timeouts to SIP provider ...
Do you have qualify=yes
host= FQDN or ip address?
Instead of a hard reboot, you could have tried sip reload from the cli
or bring up the trunk configuration then save and apply without making changes
RE: Timeouts to SIP provider ...
It looks like the qualify= is set to no. Should I change to yes? The host we have in host= has a SRV record, and is not pingable. Not sure how to get an IP address for that particular hostname. Anything else I should put into the trunk settings?
RE: Timeouts to SIP provider ...
you can try changing PBX configuration -> Settings -> SIP Settings
Registrations (registertimeout) from 20 to 55
from the cli you can try running traceroute to that host name or nslookup, host, or dig
RE: Timeouts to SIP provider ...
I was able to finally see the srv records for the hostname. I forgot to set my type in nslookup to srv!
What I'm getting back is the hostname that's located in our trunk configuration. The SVR hostname is different, however. I do get an ip address for that entry (svr hostname = ). If I do nslookup with the ip address provided, I get a still different hostname.
Would it be better to use that IP address that's being returned in svr hostname = ?
RE: Timeouts to SIP provider ...
RE: Timeouts to SIP provider ...
RE: Timeouts to SIP provider ...
I thought that maybe our internet modem went offline, but after checking with our provider, it's been online for 47 days without interruption. I can't figure out how to view more than 9999 lines of the system log, so I can't figure out exactly when it went offline.
How do you reload sip from the cli? What's the syntax?
The provider claims it's not their end that's causing the problem. Internet provider isn't the issue, either. I guess I can understand a timeout, but why isn't the connection restored? It was on attempt #1246 before I checked to see if the phones were down. We went alomost 2.5 weeks from the time the trunks died the last time. Any clue as to why this might be happening?
RE: Timeouts to SIP provider ...
https://www.megapath.com/megapath2016/assets/file/...
Ask them to send you how they want the peer details set up for an Asterisk based system.
RE: Timeouts to SIP provider ...
I originally set the peer details with a Megapath tech support person - apparently they don't follow their own documentation!
Will try it now and see how long it stays up. Thanks for the continued help.
RE: Timeouts to SIP provider ...
Megapath doesn't seem to have a clue what's going on. They say it's on our end. We didn't lose internet connectivity, we had no interruptions in network service, so it's not that. I don't understand how it can work fine for a week and then stop working all of a sudden.
One item to note in the log above is that when it goes down, it looks as though the PBX is having trouble locating the host name for our provider's SRV record. It never recovers after that.
Does anyone have any words of wisdom as to what might be happening, and whose end the problem is on? Thanks for the continued help with this.
RE: Timeouts to SIP provider ...