Time blinking on Polycom IP 331 phones

Hello. We are having this issues with time blinking on our Polycom IP 331 phones. We had an Asterisk server that broke down, so we have to build another one from scratch, we configured asterisk 13 over centos7. Several configurations were taken from previous server that worked properly. We managed for the clock from server and harware clock get syncronized, and it is important to mention that we live in Venezuela, South America, so we need for our server to get the correct hour and display it on the Polycom phones.

Thanks in advance.

Keeping this alive. Please help.

Are you provisioning the phone’s through EPM?

No, I’m not, because I think I have to pay for it.

So you provision your phones, or you set them up manually?

No, not manually, but this is what we have done so far:

1-This what I have on “nano /etc/ntp.conf”, there are some server that we have after “#”

For more information about this file, see the man pages

ntp.conf(5), ntp_acc(5), ntp_auth(5), ntp_clock(5), ntp_misc(5), ntp_mon(5).

driftfile /var/lib/ntp/drift

Permit time synchronization with our time source, but do not

permit the source to query or modify the service on this system.

restrict default kod nomodify notrap nopeer noquery
restrict -6 default kod nomodify notrap nopeer noquery

Permit all access over the loopback interface. This could

be tightened as well, but to do so would effect some of

the administrative functions.

restrict 127.0.0.1
restrict -6::1

Hosts on local network are less restricted.

#restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap

Use public servers from the pool.ntp.org project.

Please consider joining the pool (http://www.pool.ntp.org/join.html).

#server 0.centos.pool.ntp.org
#server 1.centos.pool.ntp.org
#server 2.centos.pool.ntp.org
#server 3.centos.pool.ntp.org
#server 0.south-america.pool.ntp.org
#server 1.south-america.pool.ntp.org
#server 2.south-america.pool.ntp.org
#server 3.south-america.pool.ntp.org
server 0.rhel.pool.ntp.org
server 1.rhel.pool.ntp.org
server 2.rhel.pool.ntp.org
server 172.16.25.9
#broadcast 192.168.1.255 autokey # broadcast server
#broadcastclient # broadcast client
#broadcast 224.0.1.1 autokey # multicast server
#multicastclient 224.0.1.1 # multicast client
#manycastserver 239.255.254.254 # manycast server
#manycastclient 239.255.254.254 autokey # manycast client

Undisciplined Local Clock. This is a fake driver intended for backup

and when no outside source of synchronized time is available.

server 127.127.1.0 #local clock
fudge 127.127.1.0 stratum 10

Drift file. Put this in a directory which the daemon can write to.

No symbolic links allowed, either, since the daemon updates the file

driftfile /var/lib/ntp/drift

Enable public key cryptography.

#crypto

includefile /etc/ntp/crypto/pw

Key file containing the keys and key identifiers used when operating

with symmetric key cryptography.

keys /etc/ntp/keys

Specify the key identifiers which are trusted.

#trustedkey 4 8 42

Specify the key identifier to use with the ntpdc utility.

#requestkey 8

Specify the key identifier to use with the ntpq utility.

#controlkey 8

Enable writing of statistics records.

#statistics clockstats cryptostats loopstats peerstats

Disable the monitoring facility to prevent amplification attacks using ntpdc

monlist command when default restrict does not include the noquery flag. See

CVE-2013-5211 for more details.

Note: Monitoring will not be disabled with the limited restriction flag.

disable monitor

2-Now on “nano /etc/asterisk/indicacionts.conf” I have this (what is after “#” is what was before)

[general]

country=ve

[ve]
description = Venezuela / South America
; Tone definition source for ve found on
; Reference: http://www.itu.int/ITU-T/inr/forms/files/tones-0203.pdf
ringcadence = 1000,4000
dial = 425
busy = 425/500,0/500
ring = 425/1000,0/4000
congestion = 425/250,0/250
callwaiting = 400+450/300,0/6000
dialrecall = 425
record = 1400/500,0/15000
info = !950/330,!1440/330,!1800/330,0/1000

#ESTO ESTABA ANTIGUAMENTE CONFIGURADO

#country=us

#[us]
#description = United States / North America
#ringcadence = 2000,4000
#dial = 350+440
#busy = 480+620/500,0/500
#ring = 440+480/2000,0/4000
#congestion = 480+620/250,0/250
#callwaiting = 440/300,0/10000
#dialrecall = !350+440/100,!0/100,!350+440/100,!0/100,!350+440/100,!0/100,350+440
#record = 1400/500,0/15000
#info = !950/330,!1400/330,!1800/330,0
#stutter = !350+440/100,!0/100,!350+440/100,!0/100,!350+440/100,!0/100,!350+440/100,!0/100,!350+440/100,!0/100,!350+440/100,!0/100,350+440

3-On “nano /etc/asterisk/extensions_additional.conf”, we added these lines

TIMEFORMAT = kM
TONEZONE = ve

4-We ran the command “ln -sf /usr/share/zoneinfo/America/Caracas /etc/localtime”

5-Checking “nano /etc/php.ini” on we wrote "date.timezone = America/Caracas

Hope this gives you a good idea of what we have done.

if your local network is 192.168.1.0/24 then

#restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap

might better be

restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap

My local voice network is 172.16.26.0

That’s not a network but just try 172.16.0.0/12 which is and includes whatever real network you chose

restrict 172.16.0.0 subnet 255.255.240.0 nomodify notrap

Yes it is my voice network 171.16.26.0/24, but I will uncomment that line as you have suggested. Issue is that I am not able to access my server right now. Would it be then

restrict 172.16.0.0 subnet 255.255.240.0 nomodify notrap or
restrict 172.16.0.0 mask 255.255.240.0 nomodify notrap

restrict 172.16.26.0 mask 255.255.255.0 nomodify notrap

There is always an issue with time :slight_smile:

watch the interactions with

tcpdump -nnvv port 123

Tried the line above, and none, time is still blinking on my phones :frowning:

tcpdump -nnvv port 123

?

I’ve missed this. I’ll do and I’ll let you know

Keeping this thread alive. I’m on a holiday from work. At the moment o get back into work, I’ll do that.

Keeping the thread alive

Hi, just able to get back to work now. See, there is what shows me when inputting “tcpdump -nnvv port 123”.

tcpdump -nnvv port 123
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 262144 byt es
10:42:07.127653 IP (tos 0x0, ttl 64, id 644, offset 0, flags [none], proto UDP ( 17), length 76)
172.16.26.197.4120 > 172.16.26.6.123: [udp sum ok] NTPv3, length 48
Client, Leap indicator: (0), Stratum 0 (unspecified), poll 8 (256s), pr ecision 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
10:42:10.215108 IP (tos 0x0, ttl 64, id 1411, offset 0, flags [none], proto UDP (17), length 76)
172.16.26.153.1063 > 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
10:42:16.543250 IP (tos 0x0, ttl 64, id 1458, offset 0, flags [none], proto UDP (17), length 76)
172.16.26.142.1065 > 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
10:43:32.048619 IP (tos 0x0, ttl 64, id 1498, offset 0, flags [none], proto UDP (17), length 76)
172.16.26.161.1067 > 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
10:43:35.248285 IP (tos 0x0, ttl 64, id 1411, offset 0, flags [none], proto UDP (17), length 76)
172.16.26.195.1063 > 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
10:44:11.110460 IP (tos 0x0, ttl 64, id 671, offset 0, flags [none], proto UDP (17), length 76)
172.16.26.197.4121 > 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
10:44:14.215417 IP (tos 0x0, ttl 64, id 1436, offset 0, flags [none], proto UDP (17), length 76)
172.16.26.153.1064 > 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

And it keeps on and on, showing those 172.16.26.XXX that are my voice VLAN phones.

What should I do now?. Thanks.

Your x.x.x.6 server isn’t replying, so the firewall would be the place I start. TCPDUMP sees the packets before they hit the firewall, so it’s either the FW getting in the way or your NTP Service isn’t responding on port 123.

My 172.16.26.6 is my eth0, so my polycom phones are able to connect with my server, all my polycom phones are on 172.16.26.XX voice vlan. I’ve got this 172.16.26.6/24 ip interface on freepbx web GUI firewall labeled as LOCAL (LOCAL TRUSTED TRAFFIC). What should I do then?.

172.16.26.6/24

Is not a valid network.
172.16.26.6 is a valid host address and 172.16.26.0/24 is a valid network.