Panasonic NS700 & getting P-SIP phone working
Discussion
Bit of a shot in the dark this, in case anyone has any ideas..
I'm trying to get a Panasonic KX-HDV230 SIP phone working with an on-premises Panasonic NS700, as a bit of a proof of concept.
The idea ultimately is to replace the mobiles the customer services team are currently using to field calls when they are not in the office, as this solution is not very "on brand".
I have managed to get the phone working in the sense that it registers remotely, I can make and receive calls, etc.
Where I am struggling is on two fronts..
Thanks in advance!
I'm trying to get a Panasonic KX-HDV230 SIP phone working with an on-premises Panasonic NS700, as a bit of a proof of concept.
The idea ultimately is to replace the mobiles the customer services team are currently using to field calls when they are not in the office, as this solution is not very "on brand".
I have managed to get the phone working in the sense that it registers remotely, I can make and receive calls, etc.
Where I am struggling is on two fronts..
- I currently have the "Registrar Server Address", "Proxy Server Address", "Presence Server Address" set to the external IP of the PBX. If I change this to a FQDN (so I can do split DNS and take the phone in to work and not have to reconfigure it) it does not register, and if it is already registered when I make the settings change - the display changes to "Error 003: Not registered". I have created an A record for the FQDN that points to the external IP that I already know works. I've verified the phone has DNS servers set up so should be able to resolve it. It's almost as if when you specify a FQDN instead of an IP it needs something else?
- I have set up the flexible buttons on the phone as "BLF" numbers, which I'm led to believe are supposed to let me know (via LEDs) when someone has lifted the handset, etc. This works perfectly well in the office with our KX-DT phones, but none of the LEDs show any sign of life.
Thanks in advance!
To clarify:
1) When the phone is outside the office and pointing to an external/public IP (at the office), it registers fine?
2) When the phone is outside the office and pointing to an FQDN - what happens?
3) When the phone is inside the office and pointing to an FQDN, it doesn't register?
4) What does the FQDN resolve to inside and outside the office? The same external/public IP?
1) When the phone is outside the office and pointing to an external/public IP (at the office), it registers fine?
2) When the phone is outside the office and pointing to an FQDN - what happens?
3) When the phone is inside the office and pointing to an FQDN, it doesn't register?
4) What does the FQDN resolve to inside and outside the office? The same external/public IP?
Thanks for your help
Harpoon said:
To clarify:
1) When the phone is outside the office and pointing to an external/public IP (at the office), it registers fine?
It registers fine both inside of the office (configuring the phone with the internal PBX IP) and outside (using a public IP address that is mapped to the internal PBX, with the relevant ports forwarded). It works in the sense that it registers and I can make and receive calls, but only if I use an IP address - not a FQDN, even though the FQDN points (A) to the same IP.1) When the phone is outside the office and pointing to an external/public IP (at the office), it registers fine?
Harpoon said:
2) When the phone is outside the office and pointing to an FQDN - what happens?
It either sits on "Registering.." indefinitely, or if it is already registered (e.g. it previously had the IP address in the settings for the servers) then it changes to "Error 003: Not registered", and stops working. I have left it several hours after I made the DNS change, so I don't think name resolution is the problem.Harpoon said:
3) When the phone is inside the office and pointing to an FQDN, it doesn't register?
Havent't tried that yet to be honest. I am mostly working from home, yesterday I took the phone in to the office to try and diagnose why I couldn't get it working externally at all (turned out I didn't have some ports mapped properly).Harpoon said:
4) What does the FQDN resolve to inside and outside the office? The same external/public IP?
Externally it resolves to the same IP that works if I use that instead. Internally it resolves to the internal PBX IP. The objective of me using a FQDN on the phone instead of hardcoding an IP address was to enable me to take the phone in and out of the office without having to reconfigure it each time.Thanks. With #4 I was wondering if you had NAT loopback or split DNS in place inside the office (which you do).
I've just found an Admin guide here:
https://www.phone-master.nl/VOIP/Panasonic/PANASON...
Page 121 says you can use an IP or FQDN for the SIP registrar and other servers.
What DNS does the phone have? I think my next step would to see if I could verify the phone is able to access the configured DNS and resolve the FQDN. With a decent firewall, I'd put a packet capture on that to watch for DNS traffic to/from the phone (assuming it's using public DNS). Alternatively, P161 in the admin guide suggests you can download an event log from the phone (P311 says there are 7 levels of DNS logging) - not sure how easy it is to enable/setup the logging though.
I've just found an Admin guide here:
https://www.phone-master.nl/VOIP/Panasonic/PANASON...
Page 121 says you can use an IP or FQDN for the SIP registrar and other servers.
What DNS does the phone have? I think my next step would to see if I could verify the phone is able to access the configured DNS and resolve the FQDN. With a decent firewall, I'd put a packet capture on that to watch for DNS traffic to/from the phone (assuming it's using public DNS). Alternatively, P161 in the admin guide suggests you can download an event log from the phone (P311 says there are 7 levels of DNS logging) - not sure how easy it is to enable/setup the logging though.
Currently the phone has a DNS of my Sky router for the first server, and 8.8.8.8 for the other. I have tried using just 8.8.8.8, and OpenDNS servers, etc with no apparent effect.
I haven't set up any SRV records for the FQDN, if that matters. In this scenario I didn't think I would need to? (there's only one SIP server in the mix)
The event log on the phone doesn't show anything obvious relating to DNS resolution (it did a while ago, when I was first settings it up). The error it shows in there when I change the servers to FQDN is:
I haven't set up any SRV records for the FQDN, if that matters. In this scenario I didn't think I would need to? (there's only one SIP server in the mix)
The event log on the phone doesn't show anything obvious relating to DNS resolution (it did a while ago, when I was first settings it up). The error it shows in there when I change the servers to FQDN is:
Jun 9 16:18:35 KX-HDV230X local3.emerg SIP(L0)[515]: mac:BCC342A886F3 <0> [SIP(L1)]Registration failure by (403)
Jun 9 17:22:49 KX-HDV230X local3.emerg SIP(L0)[515]: mac:BCC342A886F3 <0> [SIP(L1)]Registration failure by (403)
Jun 9 17:40:19 KX-HDV230X local3.emerg SIP(L0)[513]: mac:BCC342A886F3 <0> [SIP(L1)]Registration failure by (403)
Edited by Durzel on Wednesday 9th June 17:41
Apologies if any of these sound like dumb / insulting questions!
If you change from the static IP to FQDN, does a power cycle help at all?
Is the phone on the latest firmware?
I'd still be leaning towards the phone not resolving the DNS properly. Could you setup a local DNS server that logs request for you to review (eg PiHole)? Alternative, do you have a dumb hub or managed switch that can port mirror? I'd then have Wireshark running on a laptop and power on the phone, capture all the traffic and start by filtering it down to DNS to see what happens. If the DNS looks okay, you can then filter down to SIP and review that.
If you change from the static IP to FQDN, does a power cycle help at all?
Is the phone on the latest firmware?
I'd still be leaning towards the phone not resolving the DNS properly. Could you setup a local DNS server that logs request for you to review (eg PiHole)? Alternative, do you have a dumb hub or managed switch that can port mirror? I'd then have Wireshark running on a laptop and power on the phone, capture all the traffic and start by filtering it down to DNS to see what happens. If the DNS looks okay, you can then filter down to SIP and review that.
I appreciate the help, so no offence taken
Have power cycled it at various points with settings changes. If I change it to the IP, it tends to re-register itself and go back to normal within a few seconds. Likewise if I change the IP to the FQDN, within a few seconds it'll say it is "Not registered". Rebooting the phone with the FQDN setting will mean it just stays on "Registering" forever.
It is very curious, and as you suggest perhaps setting up a local DNS server with logging would help to see if the phone is actually trying to resolve it.
The only other thing I can think is that the phone passes across the contents of the setting "as is" as a string, or something, so there is actually a practical difference between the "10.0.0.1" and "sip.domain.com" setting, and the PBX doesn't like it for some reason. That seems a bit illogical to me though, I can't see why the phone wouldn't just resolve the FQDN and connect to wherever it points to.
Have power cycled it at various points with settings changes. If I change it to the IP, it tends to re-register itself and go back to normal within a few seconds. Likewise if I change the IP to the FQDN, within a few seconds it'll say it is "Not registered". Rebooting the phone with the FQDN setting will mean it just stays on "Registering" forever.
It is very curious, and as you suggest perhaps setting up a local DNS server with logging would help to see if the phone is actually trying to resolve it.
The only other thing I can think is that the phone passes across the contents of the setting "as is" as a string, or something, so there is actually a practical difference between the "10.0.0.1" and "sip.domain.com" setting, and the PBX doesn't like it for some reason. That seems a bit illogical to me though, I can't see why the phone wouldn't just resolve the FQDN and connect to wherever it points to.
It is an odd. In my last job we sold NEC and Siemens PBXs, so often setup SIP though I generally didn't do anything with the handsets but got dragged into getting SIP trunks through firewalls (which could be a real pain at times).
I'd go down the Wireshark route now I think. Ubquiti say the USW Flew Mini switch can port mirror if you don't have anything suitable already.
https://community.ui.com/questions/Switch-with-por...
Linitx have them in-stock for £33 (+ delivery?)
https://linitx.com/product/ubiquiti-unifi-5-port-g...
I'd go down the Wireshark route now I think. Ubquiti say the USW Flew Mini switch can port mirror if you don't have anything suitable already.
https://community.ui.com/questions/Switch-with-por...
Linitx have them in-stock for £33 (+ delivery?)
https://linitx.com/product/ubiquiti-unifi-5-port-g...
Bit of a mini update. Haven't had chance to set up an test DNS server etc yet, but I did bring the phone in to work to test it on the LAN with nothing impeding it, and it wouldn't work with a local FQDN - e.g. sip.domain.local - which resolves to the PBX IP. Same problem as when doing it from home. Quite bizarre.
CarCrazyDad said:
Haven't read the whole thread, so sorry if it's obvious
Can the phone reach the DNS server?
Can the phone run a PING command? can you try pinging by domain name
Hi,Can the phone reach the DNS server?
Can the phone run a PING command? can you try pinging by domain name
Phone is getting DNS servers from DHCP (verified on the handset, and in the embedded web UI). There is nothing between the phone and the PBX in the office, it is on the same switch.
Phone can only ping an IP address, no option to ping a FQDN.
Can you ping the IP of the DNS? Can you ping the phone controller IP?
Is the switch port the phone is patched into got any weird configuration on it, different vlan or perhaps a default security policy?
It sounds as someone else mentioned like the phone doesn't want to work with DNS
As someone has said it might be worth checking on Wireshark, are SIP registrations handled on the NS700? Is there some way to check logging on this device, can you potentially install Wireshark on the unit or set up a mirror port and see if you can see the phone registration hit the controller?
I used to always get stuff working by IP first and then move onto DNS if the customer required it just so troubleshooting was easier.
Is the switch port the phone is patched into got any weird configuration on it, different vlan or perhaps a default security policy?
It sounds as someone else mentioned like the phone doesn't want to work with DNS
As someone has said it might be worth checking on Wireshark, are SIP registrations handled on the NS700? Is there some way to check logging on this device, can you potentially install Wireshark on the unit or set up a mirror port and see if you can see the phone registration hit the controller?
I used to always get stuff working by IP first and then move onto DNS if the customer required it just so troubleshooting was easier.
CarCrazyDad said:
Can you ping the IP of the DNS?
Yup.CarCrazyDad said:
Is the switch port the phone is patched into got any weird configuration on it, different vlan or perhaps a default security policy?
Nothing esoteric. While I'm trying to get it working the phone is in the same VLAN as the PBX. It is on a managed Cisco switch, but it was behaving exactly the same when the phone was remote and it was hitting the PBX via the internet, so I don't think it's that.CarCrazyDad said:
It sounds as someone else mentioned like the phone doesn't want to work with DNS
As someone has said it might be worth checking on Wireshark, are SIP registrations handled on the NS700? Is there some way to check logging on this device, can you potentially install Wireshark on the unit or set up a mirror port and see if you can see the phone registration hit the controller?
Don't think there's any way of installing Wireshack on the PBX. As was suggested above I can (and will at some point when I get chance) set up a dummy DNS server with full logging to see if the handset actually makes any query on it.As someone has said it might be worth checking on Wireshark, are SIP registrations handled on the NS700? Is there some way to check logging on this device, can you potentially install Wireshark on the unit or set up a mirror port and see if you can see the phone registration hit the controller?
Also, I don't know if it's relevant but I haven't set up any of the "_sip._udp." stuff in DNS. "sip.domain.local" is a straight A record that points to internal PBX IP. I didn't think it was required since I only have one PBX servicing SIP requests, etc. I also turned off "Enable DNS SRV lookup" on the phone UI.
CarCrazyDad said:
set up a mirror port and see if you can see the phone registration hit the controller?
Harpoon said:
I think I'd skip the time spent setting up a local DNS now and go straight for Wireshark-ing the traffic coming out of the phone. Then you know exactly what is going on.
The above advice is sound and I would also suggest be your next course of action.Durzel said:
managed Cisco switch
It should be easy for your network admin(s) to setup a mirror/SPAN of the port the phone is connected into (for you to then use Wireshark).Irrespective of what a black box tells you it's doing (or should be), a packet capture (i.e. Wireshark) will show you what it is (or, not) doing from a network perspective.
I suspect you will find your answer when looking at the packet captures (e.g. "why is it trying, and failing, to resolve X/Y/Z")...
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff