Connect. Communicate. Collaborate. Securely.

Home » Kerio User Forums » Kerio Operator » Problem re-registered extensions numbers
  •  
depeche

Messages: 1
Karma: 0
Send a private message to this user
Hi!
Sorry for my bad English.
I am testing a 30 day version of Kerio Operator 2.1.0 Beta 3 with a VoIP gateway D-Link DVG-2032S (32 FXS ports). And I have a problem with it.
After different times, different extensions numbers are not re-registered on Kerio Operator and therefore no longer work. Over time, more extensions to fail. Corrects this reboot the gateway or Kerio Operator, then all the extensions registered. After that, all over again.
Help in solving this problem.

Log Kerio Operator
[19/Dec/2012 14:02:38] {sip} asterisk[1755]: VERBOSE[1837]: chan_sip.c:25669 in handle_request_do: #012<--- SIP read from UDP:192.168.1.58:5060 --->#012REGISTER sip:192.168.1.21 SIP/2.0#012Via: SIP/2.0/UDP 192.168.1.58:5060;branch=z9hG4bK82b6cf5191b9b3da#012From: "267" <sip:267@192.168.1.21>;tag=ed24527e-13458#012To: "267" <sip:267@192.168.1.21>#012Call-ID: D1B9-124B-00000029A121B3AC38C1-008@SipHost#012CSeq: 687 REGISTER#012Contact: <sip:267<_at_>192.168.1.58:5060>#012Expires:600#012Max-Forwards:70#012Authorization:Digest username="267",realm="asterisk",nonce="75a5771f",uri="sip:192.168.1.21",response="eebfcd5ce021ad44b95b2144971421c5",algorithm=MD5#012User-Agent: dlink 12-3890-3520-1.2.6.2710-IXP_SP1700#012Content-Length: 0#012#012<------------->

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: chan_sip.c:8651 in parse_request:  Header  0 [ 33]: REGISTER sip:192.168.1.21 SIP/2.0

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: chan_sip.c:8651 in parse_request:  Header  1 [ 65]: Via: SIP/2.0/UDP 192.168.1.58:5060;branch=z9hG4bK82b6cf5191b9b3da

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: chan_sip.c:8651 in parse_request:  Header  2 [ 53]: From: "267" <sip:267<_at_>192.168.1.21>;tag=ed24527e-13458

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: chan_sip.c:8651 in parse_request:  Header  3 [ 32]: To: "267" <sip:267<_at_>192.168.1.21>

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: chan_sip.c:8651 in parse_request:  Header  4 [ 51]: Call-ID: D1B9-124B-00000029A121B3AC38C1-008@SipHost

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: chan_sip.c:8651 in parse_request:  Header  5 [ 18]: CSeq: 687 REGISTER

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: chan_sip.c:8651 in parse_request:  Header  6 [ 36]: Contact: <sip:267<_at_>192.168.1.58:5060>

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: chan_sip.c:8651 in parse_request:  Header  7 [ 11]: Expires:600

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: chan_sip.c:8651 in parse_request:  Header  8 [ 15]: Max-Forwards:70

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: chan_sip.c:8651 in parse_request:  Header  9 [150]: Authorization:Digest username="267",realm="asterisk",nonce="75a5771f",uri="sip:192.168.1.21",response="eebfcd5ce021ad44b95b2144971421c5",algorithm=MD5

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: chan_sip.c:8651 in parse_request:  Header 10 [ 52]: User-Agent: dlink 12-3890-3520-1.2.6.2710-IXP_SP1700

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: chan_sip.c:8651 in parse_request:  Header 11 [ 17]: Content-Length: 0

[19/Dec/2012 14:02:38] {sip} asterisk[1755]: VERBOSE[1837]: chan_sip.c:25679 in handle_request_do: --- (12 headers 0 lines) ---

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: chan_sip.c:8242 in find_call: = Looking for  Call ID: D1B9-124B-00000029A121B3AC38C1-008@SipHost (Checking From) --From tag ed24527e-13458 --To-tag   

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: netsock2.c:138 in ast_sockaddr_split_hostport: Splitting '192.168.1.21' into...

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: netsock2.c:192 in ast_sockaddr_split_hostport: ...host '192.168.1.21' and port ''.

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: netsock2.c:138 in ast_sockaddr_split_hostport: Splitting '192.168.1.21' into...

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: netsock2.c:192 in ast_sockaddr_split_hostport: ...host '192.168.1.21' and port ''.
19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: chan_sip.c:25435 in handle_incoming: **** Received REGISTER (2) - Command in SIP REGISTER

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: chan_sip.c:25264 in handle_request_register: Initializing initreq for method REGISTER - callid D1B9-124B-00000029A121B3AC38C1-008@SipHost

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: netsock2.c:138 in ast_sockaddr_split_hostport: Splitting '192.168.1.58:5060' into...

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: netsock2.c:192 in ast_sockaddr_split_hostport: ...host '192.168.1.58' and port '5060'.

[19/Dec/2012 14:02:38] {sip} asterisk[1755]: VERBOSE[1837]: chan_sip.c:16140 in check_via: Sending to 192.168.1.58:5060 (no NAT)

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: Security.cpp:189 in int Security::authCheck(const sockaddr_in*, const char*): KerioSecurity check 192.168.1.58 (uri:"267" <sip:267<_at_>192.168.1.21>).

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: netsock2.c:138 in ast_sockaddr_split_hostport: Splitting '192.168.1.21' into...

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: netsock2.c:192 in ast_sockaddr_split_hostport: ...host '192.168.1.21' and port ''.

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: NOTICE[1837]: chan_sip.c:14674 in check_auth: Correct auth, but based on stale nonce received from '"267" <sip:267<_at_>192.168.1.21>;tag=ed24527e-13458'

[19/Dec/2012 14:02:38] {sip} asterisk[1755]: VERBOSE[1837]: chan_sip.c:4239 in send_response: #012<--- Transmitting (no NAT) to 192.168.1.58:5060 --->#012SIP/2.0 401 Unauthorized#015#012Via: SIP/2.0/UDP 192.168.1.58:5060;branch=z9hG4bK82b6cf5191b9b3da;received=192.168.1.58#015#012From: "267" <sip:267@192.168.1.21>;tag=ed24527e-13458#015#012To: "267" <sip:267<_at_>192.168.1.21>;tag=as0b976edd#015#012Call-ID: D1B9-124B-00000029A121B3AC38C1-008@SipHost#015#012CSeq: 687 REGISTER#015#012Server: Asterisk PBX#015#012Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH#015#012Supported: replaces, timer#015#012WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="545bc586", stale=true#015#012Content-Length: 0#015#012#015#012#012<------------>

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: chan_sip.c:3411 in __sip_xmit: Trying to put 'SIP/2.0 401' onto UDP socket destined for 192.168.1.58:5060

[19/Dec/2012 14:02:38] {sip} asterisk[1755]: VERBOSE[1837]: chan_sip.c:3999 in sip_scheddestroy: Scheduling destruction of SIP dialog 'D1B9-124B-00000029A121B3AC38C1-008@SipHost' in 32000 ms (Method: REGISTER)

[19/Dec/2012 14:02:38] {asterisk} asterisk[1755]: DEBUG[1837]: chan_sip.c:31084 in securityPostAuth: Kerio security: securityPostAuth - AUTH_CHALLENGE_SENT.

[Updated on: Thu, 24 January 2013 12:01]

  •  
Vladimir Toncar (Kerio)

Messages: 1696
Karma: 39
Send a private message to this user
Hi,

Could you send us a packet dump that shows the registration communication between Operator and the VoIP gateway? You can use Operator's built-in packet sniffer (Network > Packet Sniffer). Please e-mail the packet dump to vtoncar at kerio dot com.

Vladimir
Previous Topic: AMI Setup
Next Topic: 2.1 RC1 Faxing
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: Fri Nov 24 23:15:42 CET 2017

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