Time blinking on Polycom IP 331 phones


(Dave Burgess) #21

Hey there - I’m supposed to be the pedantic one.

In CIDR rules, 172.16.26.6/24 is a valid IP address description and since it includes a netmask, could be considered a network. It’s the same as listing it with the 255.255.240.0 netmask. Now, the catch in here is that the address isn’t the only thing that needs to be there. You also need the VLAN tags to be recognized, so you need to make sure the VLAN for the …26.6 interface is set up correctly. That fact that it’s listed in the firewall is required, but not completely sufficient.


(6 Taylor) #22

Of course it is not a network, but an IP from an interface… As of “networks” listed on freepbx web GUI, there is 172.16.26.0/24 listed, so on “interfaces” field, should I list 172.16.26.6/32 then?


(Dave Burgess) #24

No, IIRC it would be listed as 172.16.26.6/24 (IP address and netmask).


(6 Taylor) #25

Yes, and that’s exactly how the IP is listed


#28

Sorry, I don’t use nor have any knowledge of how this firewall needs to be configured.


(6 Taylor) #29


(6 Taylor) #31


#32

I keep seeing this thread pop up to the top and thinking to myself, “I’d just put a strip of black tape over it and call it done.”


(6 Taylor) #33

Not easy, I still got this issue with time… Besides, this is for solve issues of this kind, right?..


#34

You’re doing custom provisioning that is not related to Asterisk or FreePBX at all. So if you are having problems you should ask Polycom.


#35

And you can confirm that you do actually have an ntp server running on .6

lsof -i :123


(6 Taylor) #36

I’ve once thought on doing that, but I focused mainly on FreePBX.


(6 Taylor) #37

Should I then disable the firewall feature on FreePBX web GUI?


#38


(6 Taylor) #39

I’ve missed that field. And did not know I was able to create “services” over there. I’ll try it this week when going work. Should this do the job then, and I will see traffic in Port 113 after doing “tcpdump - nnvv port 123” as Mr. Dicko suggested?. Hope this solve my issue. Thanks.


(6 Taylor) #40

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

Does it mean that I have a running NTP server on my 172.16.26.6 interface?.


(6 Taylor) #41

When creating, should I input it as, Internet, Local or Other?


(6 Taylor) #42

Good mornign Mr. Dicko. See, when crested service NTP on FreePBX web GUI as BILLSIMON suggested, this is what now sends result of “tcpdump -nnvv port 123”

09:34:57.358440 IP (tos 0x0, ttl 64, id 901, offset 0, flags [none], proto UDP (17), length 76)
172.16.26.188.1044 > 172.16.26.6.123: [udp sum ok] NTPv3, length 48
Client, Leap indicator: (0), Stratum 0 (unspecified), poll 8 (256s), precision 0
Root Delay: 0.000000, Root dispersion: 0.000000, Reference-ID: (unspec)
Reference Timestamp: 0.000000000
Originator Timestamp: 0.000000000
Receive Timestamp: 0.000000000
Transmit Timestamp: 0.000000000
Originator - Receive Timestamp: 0.000000000
Originator - Transmit Timestamp: 0.000000000
09:34:57.358588 IP (tos 0x0, ttl 64, id 6573, offset 0, flags [DF], proto UDP (17), length 76)
172.16.26.6.123 > 172.16.26.188.1044: [udp sum ok] NTPv3, length 48
Server, Leap indicator: clock unsynchronized (192), Stratum 0 (unspecified), poll 8 (256s), precision -21
Root Delay: 1.000000, Root dispersion: 1.000000, Reference-ID: (unspec)
Reference Timestamp: 0.000000000
Originator Timestamp: 0.000000000
Receive Timestamp: 3785736897.358440813 (2019/12/19 09:34:57)
Transmit Timestamp: 3785736897.358557045 (2019/12/19 09:34:57)
Originator - Receive Timestamp: 3785736897.358440813 (2019/12/19 09:34:57)
Originator - Transmit Timestamp: 3785736897.358557045 (2019/12/19 09:34:57)
09:34:57.686016 IP (tos 0x0, ttl 64, id 1100, offset 0, flags [none], proto UDP (17), length 76)
172.16.26.190.1044 > 172.16.26.6.123: [udp sum ok] NTPv3, length 48
Client, Leap indicator: (0), Stratum 0 (unspecified), poll 8 (256s), precision 0
Root Delay: 0.000000, Root dispersion: 0.000000, Reference-ID: (unspec)
Reference Timestamp: 0.000000000
Originator Timestamp: 0.000000000
Receive Timestamp: 0.000000000
Transmit Timestamp: 0.000000000
Originator - Receive Timestamp: 0.000000000
Originator - Transmit Timestamp: 0.000000000
09:34:57.686148 IP (tos 0x0, ttl 64, id 62458, offset 0, flags [DF], proto UDP (17), length 76)
172.16.26.6.123 > 172.16.26.190.1044: [udp sum ok] NTPv3, length 48
Server, Leap indicator: clock unsynchronized (192), Stratum 0 (unspecified), poll 8 (256s), precision -21
Root Delay: 1.000000, Root dispersion: 1.000000, Reference-ID: (unspec)
Reference Timestamp: 0.000000000
Originator Timestamp: 0.000000000
Receive Timestamp: 3785736897.686016607 (2019/12/19 09:34:57)
Transmit Timestamp: 3785736897.686121651 (2019/12/19 09:34:57)
Originator - Receive Timestamp: 3785736897.686016607 (2019/12/19 09:34:57)
Originator - Transmit Timestamp: 3785736897.686121651 (2019/12/19 09:34:57)

The “Receive Timestamp”, “Transmit Timestamp”, “Originator - Receive Timestamp” and “Originator - Transmit Timestamp” are getting some data, is it good???


(6 Taylor) #43

Still phones not getting time… :frowning:


#44

That’s because your chronyd daemon is not being able to connect to any configured upline time servers as it apparently thinks it’s December the nineteenth