Connect. Communicate. Collaborate. Securely.

Home » Kerio User Forums » Kerio Operator » All SIP lines down, wont register,
  •  
itriver

Messages: 3
Karma: 0
Send a private message to this user
We had some phone troubles so a member of staff ran the 2.4.1 update. After the update, none of our VOIP lines would register. We tried a softphone to make sure the voip accounts were OK and we could access the SIP server from in our network and it worked fine. Even registered a new line with a new SIP provider, still can not register from Kerio.

It so happens we had another PC ready so I loaded 2.4.1 direct from disk onto it and restored our backup. That seemed to have loaded ok although now the SIP lines still dont work

Does anyone have any idea how to troubleshoot the SIP registration failure. I have heard some poeple talking about SIP debugging but I see nowhere to turn it on?

I am in quite a state here at the moment because we are struggling to exist on just our PSTN line and mobile phones so any help muchly appreciated.
  •  
itriver

Messages: 3
Karma: 0
Send a private message to this user
It wont let me copy and paste logs to the forum, saying that I cannot use links intil I have posted 5 times. So i removed the links from the warning log

Event Log:
15/Jul/2015 20:30:25] Kerio Operator 2.4.1 build 4587 is running.
[15/Jul/2015 20:30:28] Extension "10" is registered (online).
[15/Jul/2015 20:30:30] Extension "13" is registered (online).
[15/Jul/2015 20:30:34] Extension "12" is registered (online).
[15/Jul/2015 20:30:48] Extension "11" is registered (online).
[15/Jul/2015 20:31:27] Extension "14" is registered (online).
[15/Jul/2015 20:31:28] SIP interface "Exetel3" is not registered (offline).
[15/Jul/2015 20:31:28] SIP interface "Exetel2" is not registered (offline).
[15/Jul/2015 20:31:28] SIP interface "Exetel1" is not registered (offline).



Warning log: (ignore times, the clock wasnt reset after reloading to new hardware)
[15/Jul/2015 09:08:23] asterisk[11722]: WARNING[11774]: chan_dahdi.c:7914 in handle_alarms: Detected alarm on channel 1: Red Alarm
[15/Jul/2015 09:09:21] asterisk[11722]: WARNING[11773]: chan_sip.c:3832 in retrans_pkt: Retransmission timeout reached on transmission 259b069866e3deeb787fc543029bc8af<_at_>sip.nsw.iinet.net.au for seqno 102 (Critical Request) -- See (link removed)
[15/Jul/2015 09:12:06] asterisk[11722]: WARNING[11773]: chan_sip.c:3832 in retrans_pkt: Retransmission timeout reached on transmission 72e40bce22d0e85b0541104f50a1740b<_at_>sip.nsw.iinet.net.au for seqno 102 (Critical Request) -- See (link removed)
[15/Jul/2015 09:14:12] asterisk[16729]: WARNING[16783]: chan_sip.c:3832 in retrans_pkt: Retransmission timeout reached on transmission 6cbddeeb591920806744790315b5f6b5<_at_>sip.nsw.iinet.net.au for seqno 102 (Critical Request) -- See (link removed)
[15/Jul/2015 20:03:23] asterisk[1873]: WARNING[1873]: chan_dahdi.c:7914 in handle_alarms: Detected alarm on channel 1: Red Alarm
[15/Jul/2015 20:07:52] API call security issue (-32001): Invalid token. Value of the token is: 00c31a599cef785d498b16721f30e19489d46f920a078e55b080b0c536fa 01c39cbc56b6ade45d01db408d7ae07e9bf8623e43a2887f86653e9042c8 67c5bfc
[15/Jul/2015 20:12:45] asterisk[1901]: WARNING[1901]: chan_dahdi.c:7914 in handle_alarms: Detected alarm on channel 1: Red Alarm
  •  
Filip Jenicek (Kerio)

Messages: 1094
Karma: 80
Send a private message to this user
Hi,

The warning log you posted indicates that there was no reply to the SIP packets sent to the provider. Just as if they were sent to a different address. Please double check the interface configuration, especially the Domain, Proxy and Registrar addresses.

I'll need some more information in order to tell you more

Could I ask you to contact our technical support and provide them with the following data:
1. Enable debug logs: asterisk, asterisk(detailed)
2. Start packet sniffer
3. Go to the "System Health" screen and click "Restart Telephony". This will trigger the registration
4. Make a test call (inbound+outbound) to demonstrate that it doesn't work
5. Stop the packet sniffer
6. Generate a support info file (link at the bottom of the System Health screen)
7. Send the debug log, packet dump and supportinfo back to us

Thank you,
Filip
  •  
itriver

Messages: 3
Karma: 0
Send a private message to this user
Filip I will contact tech support, however keep in mind this all worked until the upgrade (no config was changed) and I cannot even get a new provider to work either.
  •  
Filip Jenicek (Kerio)

Messages: 1094
Karma: 80
Send a private message to this user
I understand that. Our support team should be able to help you.

Previous Topic: Phone calls stutter since last Kerio Operator update
Next Topic: Called Number from custom header
Goto Forum:
  


Disclaimer:
Kerio discussion forums are intended for open communication between forum members and may contain information and material posted by members which may be useful in learning about Kerio products. The discussion forums are not intended to provide technical support for any specific product. Any information implied or expressed in the discussion forums is that of the posting member. Kerio is in no way responsible for the information posted in the forums, or its accuracy. Kerio employees may participate in the discussions, but their postings do not represent an offical position of the company on any issues raised or discussed. Kerio reserves the right to monitor and maintain the forums to promote free and accurate exchange of information.

Current Time: Mon Feb 27 00:34:15 CET 2017

Total time taken to generate the page: 0.01201 seconds
.:: Contact :: Home ::.
Powered by: FUDforum 3.0.4.