Connect. Communicate. Collaborate. Securely.

Home » Kerio User Forums » Kerio Operator » No SIP trunk reconnection when rebooting the server
  •  
topsecret

Messages: 2
Karma: 0
Send a private message to this user
Hi,

I have found a nasty bug in version 2.4.0 beta 1 of Kerio operator.
In my case I'm using various external numbers provided by two different SIP trunk providers.
When I reboot the Kerio operator server, I can see in the log files that the SIP trunk is not being brought up.
The warning logs are filled with these errors:

[11/Apr/2015 21:00:43] asterisk[1688]: WARNING[1800]: acl.c:590 in resolve_first: Unable to lookup 'sip1.budxxxxxxxxxx.nl'
[11/Apr/2015 21:00:43] asterisk[1688]: WARNING[1800]: acl.c:719 in ast_ouraddrfor: Cannot connect
[11/Apr/2015 21:00:43] asterisk[1688]: WARNING[1800]: chan_sip.c:3563 in __sip_xmit: sip_xmit of 0xb5a0eed0 (len 412) to (null) returned -1: Invalid argument
[11/Apr/2015 21:00:44] asterisk[1688]: WARNING[1800]: chan_sip.c:3563 in __sip_xmit: sip_xmit of 0x92745d8 (len 390) to (null) returned -1: Invalid argument
[11/Apr/2015 21:00:44] asterisk[1688]: WARNING[1800]: chan_sip.c:3563 in __sip_xmit: sip_xmit of 0xb5a00690 (len 390) to (null) returned -1: Invalid argument
[11/Apr/2015 21:00:44] asterisk[1688]: WARNING[1800]: chan_sip.c:3563 in __sip_xmit: sip_xmit of 0xb5a0fc58 (len 390) to (null) returned -1: Invalid argument
[11/Apr/2015 21:00:44] asterisk[1688]: WARNING[1800]: chan_sip.c:3563 in __sip_xmit: sip_xmit of 0xb5a10f18 (len 390) to (null) returned -1: Invalid argument
[11/Apr/2015 21:00:44] asterisk[1688]: WARNING[1800]: chan_sip.c:3563 in __sip_xmit: sip_xmit of 0xb5a0eed0 (len 412) to (null) returned -1: Invalid argument
[11/Apr/2015 21:00:45] asterisk[1688]: WARNING[1800]: chan_sip.c:3563 in __sip_xmit: sip_xmit of 0x92745d8 (len 390) to (null) returned -1: Invalid argument

The workaround to reconnect the sip trunks, is by changing the DNS server ip in the Network configuration of Kerio Operator. Once I change the DNS server ip from my internal dns server to 8.8.8.8, the sip trunks are brought online.

After I reboot the kerio operator server, the same problem happens (the sip trunk is not being brought up, because kerio can't resolve the dns record of the sip provider). In this case I need to change the DNS server from 8.8.8.8 to my internal dns server (192.168.1.x).

Please fix this issue in the next release of Kerio 2.4.0
  •  
Filip Jenicek (Kerio)

Messages: 1050
Karma: 76
Send a private message to this user
Hi,

it sounds like you are having some issues with the network.

What is the second domain that doesn't get resolved over google DNS servers?

Filip
  •  
topsecret

Messages: 2
Karma: 0
Send a private message to this user
Hi Filip,

The two domains that we are using are:
sip.mtsip.nl and sip1.budgetphone.nl

Even if I use the IP addres of the domains above, I still receive the error.
Will it be a possibility to capture some logs of this behaviour?
I want to make sure that this is a bug in the beta version of Kerio Operator and not a problem with our network setup.

  •  
Filip Jenicek (Kerio)

Messages: 1050
Karma: 76
Send a private message to this user
Please contact me on <fjenicek<_at_>kerio.com>, I will give you further instructions.

Thank you
  •  
jackl

Messages: 35
Karma: 0
Send a private message to this user
Hi Filip,

Did you resolve this issue? I have the same issue right now. Any idea?

Thanks

Jack
  •  
Filip Jenicek (Kerio)

Messages: 1050
Karma: 76
Send a private message to this user
Hi,

I don't remember exactly, but I think it was a network issue. The switch/router had spanning tree enabled.

If you replace domain names by IP addresses, does it help?

Is there anything in the logs - warning/error?

Filip
  •  
jackl

Messages: 35
Karma: 0
Send a private message to this user
Yes, i tried everything i could and just like the creator of this thread.

Once change the IP, it come back to register. Once reboot it can't register.

The attachment is the log i sent to one of tech support (Morgan).

i got same thing like this creator got.

Please advise.

Thanks

  • Attachment: Downloads.7z
    (Size: 924.29KB, Downloaded 24 times)
  •  
Filip Jenicek (Kerio)

Messages: 1050
Karma: 76
Send a private message to this user
Your Operator is sending the packets to megapath, but is not getting any replies. At the same time other communication works fine. So it is either a network issue, or the provider is not responding.

Operator sends REGISTER requests to ca01-siptrunk.megapathvoice.net. The domain was resolved as 67.103.60.53.

If I resolve the domain now (using SRV records), I get two addresses:
lsancagb-siptrunk01.megapathvoice.net. 1149 IN A 67.103.60.53
asbnvacz-siptrunk01-fo.megapathvoice.net. 1149 IN A 67.102.144.105

Perhaps one of them is replying while the other is not.

Please contact megapath for further advice, as from our side it looks fine.
  •  
Vladimir Toncar (Kerio)

Messages: 1696
Karma: 39
Send a private message to this user
Also, check your router/firewall. Quite often, the "SIP ALG" in the router is causing problems like this.
  •  
jackl

Messages: 35
Karma: 0
Send a private message to this user
I checked with MegaPath yesterday. They are saying my packets doesn't come with an authorization information, please see below:

Successful Registration Summary:
Request: Register
Request URI: sip:626709xxxx<_at_>megapathvoice.com
From: <sip:626709xxxx<_at_>megapathvoice.com>;tag=SDvkfv801-as6f719c5f
To: <sip:626709xxxx<_at_>megapathvoice.com>
Call-ID: SDvkfv801-4e7ce06712f840cce20a30c787a37e95-v3000v3
CSeq: 150 REGISTER
Authorization: Digest username="626709xxxx", realm="BroadWorks", algorithm=MD5, uri="sip:67.103.60.53", nonce="BroadWorksXiokavmbdTqodi55BW", response="c1ead3efc1a5ba80e17b45ec157c6b58", qop=auth, cnonce="0618c211", nc=00000030
Expires: 300
Contact: <sip:626709xxxx-srr1vtb4vhub2<_at_>67.103.60.180:5060;transport=udp >;expires=300


Failed Registration Summary:
Request: Register
Request URI: sip:626709xxxx<_at_>megapathvoice.com
From: <sip:626709xxxx<_at_>megapathvoice.com>;tag=SDblkn901-as41fd403a
To: <sip:626709xxxx<_at_>megapathvoice.com>
Call-ID: SDblkn901-43a1162a3e198473240ac9a2e5a8d933-v3000v3
CSeq: 102 REGISTER
Expires: 300
Contact: <sip:626709xxxx-srr1vtb4vhub2<_at_>67.103.60.180:5060;transport=udp >;expires=300


Moreover, we noticed that every time the internal ip address changed, Kerio sends a SIP packet to MegaPath. However, every time we restart the server, Kerio never sends a SIP packet to MegaPath. I think it's a asterisk cache issue or something else. Please advise.
  •  
Filip Jenicek (Kerio)

Messages: 1050
Karma: 76
Send a private message to this user
That is a correct behavior. The first REGISTER packet should not contain Authorization information. The provider is supposed to reply Unauthorized with a nonce value. Only then Operator can use the nonce value to calculate the Authorization header and send a second REGISTER request.

Unfortunately, Operator doesn't receive any responses from the provider.

What do you mean by "every time the internal ip address changed"?
  •  
jackl

Messages: 35
Karma: 0
Send a private message to this user
if you saying the first register packet should not contain authorization information, then how come it can come back after several hours?

When kerio can't register, we change the internal ip address then it come back to register.
then i reboot the server again it can't register either with the new ip address. after i change the internal ip address to the old one then it come back to register again.
  •  
Vladimir Toncar (Kerio)

Messages: 1696
Karma: 39
Send a private message to this user
SIP is using the challenge-response authentication scheme borrowed from HTTP (RFC 2617).

If it happens to register once in a few hours, all it means is that the responses from Megapath make it back once in a few hours.

Please do check your network infrastructure, especially your router/firewall.
Previous Topic: Kerio Operator 2.4.8
Next Topic: new users are unable to transfer anonymus calls
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: Sat Dec 03 22:50:26 CET 2016

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