Panasonic Door Intercom kx-ntv160 wil not register

RobG · January 14, 2019, 4:43pm

Panasonic kx-ntv160 will not register with Asterisk
My system works fine with softphones and desk phone but I can not get the Intercom to register
I have tried pjsip and chan_sip
I using 5060 and 5160 as the port
When I set the port to 5160 I get “no matching endpoint found” error
With port 5060 there is no error, but still not connected.
What diagnostics can I use to see why the registration is being refused?

Thanks
Rob

jcolp · January 14, 2019, 5:00pm

Either “sip set debug on” or “pjsip set logger on” will show the SIP traffic, depending on which you are actively using at the time. It sounds, though, that the problem may be the configuration in the device itself if neither work.

RobG · January 14, 2019, 5:32pm

<— SIP read from UDP:192.168.0.56:5060 —>

REGISTER sip:192.168.0.55 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.56;rport;branch=z9hG4bKU010TwQRgFEQTk6nLEvWzW

Max-Forwards: 70

From: <sip:1005@192.168.0.55>;tag=16R0aZDI

To: <sip:1005@192.168.0.55>

Call-ID: gFnMWtvN3aZe.vdsGUfrpXpakQ

CSeq: 1 REGISTER

Contact: <sip:1005@192.168.0.56:5060;transport=UDP>;+g.3gpp.smsip;+g.3gpp.icsi-ref=“urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel”;+g.gsma.rcs.telephony=“cs,volte”

Allow: INVITE,ACK,CANCEL,BYE,PRACK,INFO,UPDATE,OPTIONS,MESSAGE,NOTIFY,REFER

Expires: 3600

Supported: path

User-Agent: Panasonic-KX-NTV160/0101i (0002D13F1079)

Content-Length: 0

<------------->

— (13 headers 0 lines) —

Sending to 192.168.0.56:5060 (NAT)

<— Transmitting (no NAT) to 192.168.0.56:5060 —>

SIP/2.0 401 Unauthorized

Via: SIP/2.0/UDP 192.168.0.56;branch=z9hG4bKU010TwQRgFEQTk6nLEvWzW;received=192.168.0.56;rport=5060

From: <sip:1005@192.168.0.55>;tag=16R0aZDI

To: <sip:1005@192.168.0.55>;tag=as0f270309

Call-ID: gFnMWtvN3aZe.vdsGUfrpXpakQ

CSeq: 1 REGISTER

Server: FPBX-14.0.5.9(13.24.1)

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE

Supported: replaces, timer

WWW-Authenticate: Digest algorithm=MD5, realm=“asterisk”, nonce=“3e14dd01”

Content-Length: 0

<------------>

Scheduling destruction of SIP dialog ‘gFnMWtvN3aZe.vdsGUfrpXpakQ’ in 32000 ms (Method: REGISTER)

Really destroying SIP dialog ‘92rclwFecnEjMLvW.djpimDxjcZR8JH’ Method: REGISTER

jcolp · January 14, 2019, 5:33pm

That trace shows the device attempting to register, Asterisk challenging for authentication, and then nothing further.

RobG · January 14, 2019, 5:44pm

Thanks I have sent the debug, but my message needs to be approved by a moderator

jcolp · January 14, 2019, 5:47pm

What debug? The debug above with the SIP trace? That is what I mentioned. The problem appears to be with the device, as it should then send a second INVITE with credentials. The information you’ve provided does not show that.

RobG · January 14, 2019, 5:48pm

<— SIP read from UDP:192.168.0.56:5060 —>

REGISTER sip:192.168.0.55 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.56;rport;branch=z9hG4bKU010TwQRgFEQTk6nLEvWzW

Max-Forwards: 70

From: <sip:1005@192.168.0.55>;tag=16R0aZDI

To: <sip:1005@192.168.0.55>

Call-ID: gFnMWtvN3aZe.vdsGUfrpXpakQ

CSeq: 1 REGISTER

Contact: <sip:1005@192.168.0.56:5060;transport=UDP>;+g.3gpp.smsip;+g.3gpp.icsi-ref=“urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel”;+g.gsma.rcs.telephony=“cs,volte”

Allow: INVITE,ACK,CANCEL,BYE,PRACK,INFO,UPDATE,OPTIONS,MESSAGE,NOTIFY,REFER

Expires: 3600

Supported: path

User-Agent: Panasonic-KX-NTV160/0101i (0002D13F1079)

Content-Length: 0

RobG · January 14, 2019, 5:48pm

------------>

— (13 headers 0 lines) —

Sending to 192.168.0.56:5060 (NAT)

<— Transmitting (no NAT) to 192.168.0.56:5060 —>

SIP/2.0 401 Unauthorized

Via: SIP/2.0/UDP 192.168.0.56;branch=z9hG4bKU010TwQRgFEQTk6nLEvWzW;received=192.168.0.56;rport=5060

From: <sip:1005@192.168.0.55>;tag=16R0aZDI

To: <sip:1005@192.168.0.55>;tag=as0f270309

Call-ID: gFnMWtvN3aZe.vdsGUfrpXpakQ

CSeq: 1 REGISTER

Server: FPBX-14.0.5.9(13.24.1)

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE

Supported: replaces, timer

WWW-Authenticate: Digest algorithm=MD5, realm=“asterisk”, nonce=“3e14dd01”

Content-Length: 0

RobG · January 14, 2019, 5:49pm

192.168.0.55 is the pbx and 192.168.56 is the sip intercom

ambiorixg12 · January 14, 2019, 5:50pm

After the 401 authentication challenge, the UA need to send a registration request again with a valid username and password, if after the 401 message nothing happen it seems the UA doesnt know that it has to authenticate the REGISTER request against the Asterisk server

RobG · January 14, 2019, 5:58pm

This is the config on the Intercom :

Phone Number
1005
Registrar Server Address
192.168.0.55
Registrar Server Port
5060
Proxy Server Address
192.168.0.55
Proxy Server Port
5060
Service Domain
192.168.0.55
Authentication ID
1005
Authentication Password

david551 · January 14, 2019, 6:15pm

Authentication Password should not be empty. It should match that configured in Asterisk, i.e. the value of the secret parameter.

RobG · January 14, 2019, 6:19pm

The password is the same as the secret, it did not copy into the post

RobG · January 14, 2019, 6:25pm

I have found the config file for sip parameters on the intercom

sip_useragent=’’
sip_timemode_type=‘basic’
sip_timemode_basicphonenumber=‘1002’
sip_timemode_day_phonenumber=’’
sip_timemode_day_start=’’
sip_timemode_lunch_phonenumber=’’
sip_timemode_lunch_start=’’
sip_timemode_break_phonenumber=’’
sip_timemode_break_start=’’
sip_timemode_break_end=’’
sip_timemode_day2_start=’’
sip_timemode_night_phonenumber=’’
sip_timemode_night_start=’’
sip_i0_phonenumber=‘1005’
sip_i0_uri=’’
sip_i0_rgstr_addr=‘192.168.0.55’
sip_i0_rgstr_port=‘5060’
sip_i0_prxy_addr=‘192.168.0.55’
sip_i0_prxy_port=‘5060’
sip_i0_svcdomain=‘192.168.0.55’
sip_i0_authid=‘1005’
sip_panda_answersetting=‘0’
sip_panda_callingcontinuesetting=‘0’
sip_panda_confirmationtonesetting=‘0’
sip_panda_timer_conversation=‘60’
sip_panda_timer_callingcontinue=‘30’
sip_panda_timer_dooropen=‘5’
sip_panda_timer_reregister=‘10’

csabka · February 12, 2019, 2:57pm

Hi,

You can check it in the manual… Unfortunately only Panasonic SIP capable PBXes are supported:

“1.6.6 Registering to a PBX”:
(The KX-NTV150/KX-NTV160 cannot be used with third-party PBXs, SIP servers or other Panasonic
PBXs such as KX-NCP PBXs.).

I had the same issue, I think they do some extra challenge checks during authentication, that is why it is not compatible with other products. (there are several sip capable Panasonic device which configuration almost similar but not “vendor locked”).

It would be better to say it is NOT a SIP device. They’ve just copied the open standard and extend it wrong way (I think just evil companies doing something like this).

tubercel · May 3, 2019, 3:35pm

In sip.conf you need

global section:
useragent=Panasonic-KX-NS1000
context=default
allowguest=yes

define peer:
[90]
callerid=“KX-Vt150” <90>
host=dynamic
type=peer
context=doorsip
canreinvite=yes
disallow=all
allow=alaw
allow=g722

and it works fine.