×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Timeouts to SIP provider ...

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. :)
Replies continue below

Recommended for you

RE: Timeouts to SIP provider ...

in trunk peer details
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 ...

(OP)
Thanks for the quick reply islandtech. This is what I have for trunk settings:

username=xxx
type=friend
secret=xxx
qualify=no
insecure=invite,port
host=xxx.megapathvoice.net
dtmfmode=rfc2833
context=from-trunk
 

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 ...

I always use qualify-yes

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 ...

(OP)
Thanks islandtech. I changed the settings you suggested ... we'll see what happens.

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 ...

I've never used Megapath so I would leave it like they suggest. The SRV record contains additional info like port,priority,and target IP

RE: Timeouts to SIP provider ...

(OP)
OK. Will do. If I continue to have problems, this can be something I can explore. Appreciate all the help!

RE: Timeouts to SIP provider ...

(OP)
We lost phone service again sometime yesterday. I didn't discover it until today. I went into the system log, and I had the following entries:

Packet timed out after 31999ms with no response
[2018-11-25 04:02:48.490] NOTICE[32672] chan_sip.c: -- Registration for 'xxx@wi01-siptrunk.megapathvoice.net' timed out, trying again (Attempt #793)
[2018-11-25 04:02:49.496] NOTICE[32672] chan_sip.c: -- Registration for 'xxx@wi01-siptrunk.megapathvoice.net' timed out, trying again (Attempt #793)
[2018-11-25 04:03:20.490] WARNING[32672] chan_sip.c: Retransmission timeout reached on transmission 72978bb50eb57b0a5be3aec02af6bd63@[::1] for seqno 28899 (Critical Request) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 31999ms with no response
[2018-11-25 04:03:21.496] WARNING[32672] chan_sip.c: Retransmission timeout reached on transmission 0a6bc3fa75d5122a59b9913752f6dfed@[::1] for seqno 28899 (Critical Request) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 32000ms with no response
[2018-11-25 04:03:43.491] NOTICE[32672] chan_sip.c: -- Registration for 'xxx@wi01-siptrunk.megapathvoice.net' timed out, trying again (Attempt #794)
[2018-11-25 04:03:44.497] NOTICE[32672] chan_sip.c: -- Registration for 'xxx@wi01-siptrunk.megapathvoice.net' timed out, trying again (Attempt #794)
[2018-11-25 04:04:15.490] WARNING[32672] chan_sip.c: Retransmission timeout reached on transmission 72978bb50eb57b0a5be3aec02af6bd63@[::1] for seqno 28900 (Critical Request) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 31999ms with no response
[2018-11-25 04:04:16.498] WARNING[32672] chan_sip.c: Retransmission timeout reached on transmission 0a6bc3fa75d5122a59b9913752f6dfed@[::1] for seqno 28900 (Critical Request) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 32001ms with no response
[2018-11-25 04:04:38.491] NOTICE[32672] chan_sip.c: -- Registration for 'xxx@wi01-siptrunk.megapathvoice.net' timed out, trying again (Attempt #795)
[2018-11-25 04:04:39.497] NOTICE[32672] chan_sip.c: -- Registration for 'xxx@wi01-siptrunk.megapathvoice.net' timed out, trying again (Attempt #795)
[2018-11-25 04:05:01.703] VERBOSE[32603] asterisk.c: Remote UNIX connection
[2018-11-25 04:05:01.703] VERBOSE[19534] asterisk.c: Remote UNIX connection disconnected
[2018-11-25 04:05:10.491] WARNING[32672] chan_sip.c: Retransmission timeout reached on transmission 72978bb50eb57b0a5be3aec02af6bd63@[::1] for seqno 28901 (Critical Request) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 32000ms with no response
[2018-11-25 04:05:11.498] WARNING[32672] chan_sip.c: Retransmission timeout reached on transmission 0a6bc3fa75d5122a59b9913752f6dfed@[::1] for seqno 28901 (Critical Request) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
 

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 ...

Did you get your peer details from Megapath or did you just try stuff until it worked? Here is a Megapath configuration guide for Free PBX which is pretty much the same for a UCX. This is where I would start. It does state that your registration timer should be set to 55 seconds as well.

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 ...

(OP)
Thanks for the link telcodog. There were a few peer items missing, so I added them in. Registrations in SIP settings is set to 55 seconds. I did not change registration times, however. It's still set at 60, 3600 and 120.

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 ...

(OP)
Hi everyone: I'm continuing to struggle with this. Our trunks are configured to Megapath specs. We can be up for 7-8 days without any problems, and then all of a sudden, the SIP service just drops, and there's no reason why. We lost service this morning again. This is what I'm seeing in the log:

[2018-12-31 08:52:40.358] NOTICE[2453] chan_sip.c: Peer 'SIP25558' is now UNREACHABLE! Last qualify: 138
[2018-12-31 08:53:03.153] WARNING[2453] chan_sip.c: Retransmission timeout reached on transmission 56f66afd79b6a5481fbb2441187a0f62@[::1] for seqno 18830 (Critical Request) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 32001ms with no response
[2018-12-31 08:53:04.753] WARNING[2453] chan_sip.c: Retransmission timeout reached on transmission 7394c6671142d6a8149c1781679556a6@[::1] for seqno 18828 (Critical Request) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 32000ms with no response
[2018-12-31 08:53:05.910] ERROR[2358] netsock2.c: getaddrinfo("wi01-siptrunk.megapathvoice.net", "(null)", ...): Name or service not known
[2018-12-31 08:53:05.910] WARNING[2358] acl.c: Unable to lookup 'wi01-siptrunk.megapathvoice.net'
[2018-12-31 08:53:09.914] ERROR[2358] netsock2.c: getaddrinfo("wi01-siptrunk.megapathvoice.net", "(null)", ...): Name or service not known
[2018-12-31 08:53:09.914] WARNING[2358] acl.c: Unable to lookup 'wi01-siptrunk.megapathvoice.net'
[2018-12-31 08:53:13.919] ERROR[2358] netsock2.c: getaddrinfo("wi01-siptrunk.megapathvoice.net", "(null)", ...): Name or service not known
[2018-12-31 08:53:13.919] WARNING[2358] acl.c: Unable to lookup 'wi01-siptrunk.megapathvoice.net'
[2018-12-31 08:53:17.922] ERROR[2358] netsock2.c: getaddrinfo("wi01-siptrunk.megapathvoice.net", "(null)", ...): Name or service not known
[2018-12-31 08:53:17.922] WARNING[2358] acl.c: Unable to lookup 'wi01-siptrunk.megapathvoice.net'
[2018-12-31 08:53:26.153] NOTICE[2453] chan_sip.c: -- Registration for 'xxx@wi01-siptrunk.megapathvoice.net' timed out, trying again (Attempt #2)
[2018-12-31 08:53:27.753] NOTICE[2453] chan_sip.c: -- Registration for 'xxx@wi01-siptrunk.megapathvoice.net' timed out, trying again (Attempt #2)
[2018-12-31 08:53:58.153] WARNING[2453] chan_sip.c: Retransmission timeout reached on transmission 56f66afd79b6a5481fbb2441187a0f62@[::1] for seqno 18831 (Critical Request) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 32000ms with no response
[2018-12-31 08:53:59.754] WARNING[2453] chan_sip.c: Retransmission timeout reached on transmission 7394c6671142d6a8149c1781679556a6@[::1] for seqno 18829 (Critical Request) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 32001ms with no response
[2018-12-31 08:54:21.154] NOTICE[2453] chan_sip.c: -- Registration for 'xxx@wi01-siptrunk.megapathvoice.net' timed out, trying again (Attempt #3)
[2018-12-31 08:54:22.753] NOTICE[2453] chan_sip.c: -- Registration for 'xxx@wi01-siptrunk.megapathvoice.net' timed out, trying again (Attempt #3)
[2018-12-31 08:54:53.154] WARNING[2453] chan_sip.c: Retransmission timeout reached on transmission 56f66afd79b6a5481fbb2441187a0f62@[::1] for seqno 18832 (Critical Request) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 31999ms with no response
[2018-12-31 08:54:54.754] WARNING[2453] chan_sip.c: Retransmission timeout reached on transmission 7394c6671142d6a8149c1781679556a6@[::1] for seqno 18830 (Critical Request) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 32001ms with no response
 

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 ...

(OP)
Update: They had us disable connection to their servers by SRV record and switch to a DNS Type A record. We'll see if that does anything ...

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login


Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close