Time blinking on Polycom IP 331 phones


(6 Taylor) #65

the ip of my PBX server is ?
eth0 is 172.16.26.6 (IP on VLAN 26 where phones have taken IP from network 171.16.26.0/24 with DHCP)
Eth1 is 171.16.52.187 (IP for the Freepbx web GUI)
the ip of my phone is ?
For example, my Phone’s IP is 172.16.26.150
the ip of my ntp server is ?
IP for my ntp server is pointed to 172.16.26.6
the ip of my dhcp server is ?
The IP range for my DHCP server is 172.16.26.100 to 172.16.26.200

Just to clarify, the first asterisk server we provisioned four years ago had same values, and phones were working OK taking time from server.


#67

On that older machine you had an ntp service running, apparently not so on this one, you have yet to post

lsof -i :123

Run on 26.6


(Dave Burgess) #68

This is looking more and more like a VLAN problem. Just having everything on the right IP addresses isn’t enough. You also have to make sure that everything is using the VLAN tags. Without that, it will look like a firewall is in the way.


(6 Taylor) #69

I will take a look on the FW


(6 Taylor) #70

Last Wednesday I’ve ran this command, result was
lsof -i:123
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
chronyd 797 chrony 3u IPv4 18075 0t0 UDP *:ntp
chronyd 797 chrony 5u IPv6 18076 0t0 UDP *:ntp


#71

If you have vlans involved then your ntp daemon (chrony) will need to broadcast on those networks also.

I suspect (as others also have) that you don’t fully understand the vlan(s) you have deployed or why and what needs to be done, none of this is pertinent to these fora which are about FreePBX and google is really full of answers for your deployment :slight_smile:


#72

This thread is ridiculous – 67 posts for a simple problem, not yet resolved.

I suspect that we were misled by an incorrect observation and suggest that we start over.

On the PBX, capture traffic on the 172.16.26.x interface and have the phone request the time. There are three plausible results:

  1. No NTP request comes in.
  2. Requests come in but no replies are sent.
  3. Requests come in and valid responses are sent.

If it’s (2), it’s a problem on the PBX. Briefly disable the firewall to see whether that’s the culprit. Then, fix the firewall or the NTP server, as appropriate.

If it’s (1), use port mirroring on the switch to capture traffic at the phone. If the phone is sending requests properly (correct IP address, port, VLAN tag), you’ve got a simple network issue. If it’s sending improperly or not at all, it’s a provisioning or DHCP issue (for example, phone is getting NTP address from DHCP server that is handing out the address of the old PBX).

If it’s (3), use port mirroring on the switch to capture traffic at the phone. If the phone is receiving NTP responses properly, a provisioning or firmware issue. If the responses are missing or corrupted, a simple network issue.


(6 Taylor) #73

Yes, it seems kind-of risita, but wasn’t an easy issue either. See, I’ve tried number 3,butno results. I’ll try other options you suggested. Thanks.


(6 Taylor) #74

Believe me Mr. Dicko, Google is my Bible. I’ll check on firewall first.


(6 Taylor) #75

Got solution of this issue. Have to execute commands every time I reboot server, but it does work. It was firewall. Thanks to everyone who gave support in this issue.