Time blinking on Polycom IP 331 phones


(Dave Burgess) #45

It might be - he could be in Kentucky.

There’s a way to configure your NTP program so that it doesn’t use an upstream time provider. It’s not normally useful or recommended, but it can be done if that’s a requirement for you.


#46

Recommend you read up on the firewall here: https://wiki.freepbx.org/display/FPG/Firewall

The section on Zones will help you figure out what to set.


(6 Taylor) #47

Is there any chance for me to “force” to take today’s date?, I mean, is there a way for the NTP to take the correct time on my server?

[root@freepbx ~]# clock
hThu 19 Dec 2019 10:26:30 AM UTC -0.750415 seconds
[root@freepbx ~]# hwclock
Thu 19 Dec 2019 10:26:32 AM UTC -0.531658 seconds

This is my correct time in here Venezuela.


(6 Taylor) #48

Right, I’ve checked that early, so I chose Local because it states that for use on internal networks that do not have traffic from non-trusted hosts. and also allows access to most services.


#49

Thu 19 Dec 2019 10:26:32 AM UTC -0.531658 seconds

If that’s your correct time, then may I ask "How did the last three months go for Maduro and the rest of you guys? " :wink:


(Dave Burgess) #50

Unless you’re calling from the future, your time isn’t right. If nothing else, it’s Wednesday for most of the rest of the Western Hemisphere. Reset your hardware clock to the “more or less” correct time and use your Local setting and you should be OK.


(6 Taylor) #51

Ah!, right, last week time was ok. Got it right again. I’ll reboot and see what happens.

Now when tcpdump -nnvv port 123:

11:04:16.510700 IP (tos 0x0, ttl 64, id 55453, offset 0, flags [DF], proto UDP (17), length 76)
172.16.26.6.123 > 172.16.26.145.1090: [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: 3775374256.510568267 (2019/08/21 11:04:16)
Transmit Timestamp: 3775374256.510679489 (2019/08/21 11:04:16)
Originator - Receive Timestamp: 3775374256.510568267 (2019/08/21 11:04:16)
Originator - Transmit Timestamp: 3775374256.510679489 (2019/08/21 11:04:16)


(6 Taylor) #52

Nothing, phones are not getting time… :frowning:


(6 Taylor) #53

[root@freepbx ~]# clock
Wed 21 Aug 2019 11:23:23 AM UTC -0.469195 seconds
[root@freepbx ~]# hwclock
Wed 21 Aug 2019 11:23:25 AM UTC -0.031665 seconds

Phones sitll not getting time…


(6 Taylor) #54

Hehe :smile:


#55

Maybe you could just go and work on it a little bit instead of filling up this forum with updates telling us it doesn’t work.

As a reminder, this STILL does not have anything to do with FreePBX or Asterisk and is off-topic for the forum. You were shown (with pictures) how to set up your firewall rules and given documentation. Now your issue is configuring NTP, which is out of scope here.


#56

Try

man ntpq

ntpq -p

should show available servers and state, when its working the you should see both a packet from 172.16.26.6 , the server, to 172.16.26.145 , the phone and then a reply from 172.16.26.145 to 172.16.26.6 wityh confirmation of the time stamps , as to connecting the server to upline servers, that’s a configurion/firewall issue.


(6 Taylor) #57

I’m sorry, if I’m here asking and posting results, is because I have done everything I’ve could on my end, I have installed THE WHOLE SYSTEM on my own, couldn’t solve this last issue yet, everything but the time on my phones is working, and I really don’t know how to fix it. Don’t think I’m a fool that doesn’t know what he’s doing.

Thanks anyway for your help.


(6 Taylor) #58

I’ll try, I’m now out of the office. Thanks. I’ll post results here.


(6 Taylor) #59

[root@freepbx ~]# ntpq -p
localhost: timed out, nothing received
***Request timed out


(Dave Burgess) #60

That tells me that ntpd isn’t running or the firewall is blocking access to it.

tcpdump -nnvv port 123 from the FreePBX server should show you what the traffic is on the port and should give you some more info. If you see the traffic going back and forth, it’s the firewall (tcpdump is network promiscuous) and if you only see traffic in one direction, it could be the ntpd service or the firewall.


#61

Indicatative of no ntp server running

lsof -i :123


(6 Taylor) #62

Yes, and I have started to look into the matter about firewall possibly blocking ntp service, because I know it is installed on my server but service isn’t running…


(6 Taylor) #63

Yes, I’ve started to search about possibly firewall blockade


#64

Lets get some clarity, so please fill in the blamks

the ip of my PBX server is ?
the ip of my phone is ?
the ip of my ntp server is ?
the ip of my dhcp server is ?