› VitalPBX Community Support › General Discussion › Previously Registered Trunk now unable to register
- This topic has 9 replies, 6 voices, and was last updated 2 months, 3 weeks ago by
voipnowpbx.
- Post
-
- April 20, 2020 at 3:43 am
This is a CISCO SPA400, up until today it was registered and working, however as of today vitalpbx just keeps reporting timed out:
[2020-04-20 11:17:05] NOTICE[1714]: chan_sip.c:15982 sip_reg_timeout: -- Registration for 'SPA400@x.x.x.x' timed out, trying again (Attempt #3)
[2020-04-20 11:17:25] NOTICE[1714]: chan_sip.c:15982 sip_reg_timeout: -- Registration for 'SPA400@x.x.x.x' timed out, trying again (Attempt #4)
[2020-04-20 11:17:45] NOTICE[1714]: chan_sip.c:15982 sip_reg_timeout: -- Registration for 'SPA400@x.x.x.x' timed out, trying again (Attempt #5)
[2020-04-20 11:18:05] NOTICE[1714]: chan_sip.c:15982 sip_reg_timeout: -- Registration for 'SPA400@x.x.x.x' timed out, trying again (Attempt #6)
[2020-04-20 11:18:25] NOTICE[1714]: chan_sip.c:15982 sip_reg_timeout: -- Registration for 'SPA400@x.x.x.x' timed out, trying again (Attempt #7)However from the console I can sucessfully connect to port 5060 so it does not look like a firewall issue.
nc -z -v x.x.x.x 5060
Ncat: Version 7.50 ( https://nmap.org/ncat )
Ncat: Connected to x.x.x.x:5060.
Ncat: 0 bytes sent, 0 bytes received in 0.01 seconds.This same SPA400 can also be registered using an old TRIXBOX within the LAN, however vitalpbx now seems unable to communicate.
Ports 5060 and 10000 are opened and as above, the connection succeeds using nc.
If I enable sip debugging in asterisk I get this:
—
Retransmitting #6 (no NAT) to 158.140.x.x:5060:
REGISTER sip:158.140.140.220 SIP/2.0
Via: SIP/2.0/UDP 206.189.x.x:5060;branch=z9hG4bK5526118a
Max-Forwards: 70
From: <sip:SPA400@158.140.x.x>;tag=as0d5ad621
To: <sip:SPA400@158.140.x.x>
Call-ID: 44602a980e5b5e460c7d7ff01447b4f9@206.189.38.78
CSeq: 105 REGISTER
Supported: replaces, timer
User-Agent: VitalPBX
Expires: 120
Contact: <sip:SPA400@206.189.x.x:5060>
Content-Length: 0I have spent the best part of today on this and made no progress whatsoever, I have also tried disabling firewall and intrusion on virtual PBX and that seems to make no difference.
0
- Replies
-
- April 20, 2020 at 4:38 am
- April 20, 2020 at 10:48 am
- April 20, 2020 at 2:31 pm
- April 20, 2020 at 2:39 pm
- April 20, 2020 at 11:55 pm
I disabled the trunk, waited a few minutes and enabled it again and everything was back to normal.
So without making any changes, by just disabling and re-enabling again, the timeout errors shown in the first post disappeared and the trunk worked again.
Version : 2.4.1-3
Asterisk : Asterisk 16.6.2
Linux Version : CentOS Linux release 7.7.1908 (Core)0- April 21, 2020 at 12:45 am
I remember having issues like this with Cisco Sipura devices back in the day. Do you have qualify turned on for the peer so it periodically sends Options packets to keep the connection alive?
To me, from my experience, seems like the router end at the Cisco side is timing out UDP packets. You may want to adjust further your registration values. Are any other non-Cisco terminals having the same issue?
0- April 25, 2020 at 10:52 pm
- April 27, 2020 at 1:49 pm
- October 30, 2020 at 3:33 am
- You must be logged in to reply to this topic.