12-25-2012 04:31 AM - edited 03-16-2019 02:52 PM
Hi Guys,
I have a problem on our deployment. Here's the scenario:
We have deployed VOIP using SIP with 7962, 7942 and 6921 phones. We using 2N Netstar to act as our Call Manager. For addressing, we use DHCP which also gives the TFTP server address. Every configuration text file and things needed on the default loads file are on the TFTP server on a CentOS VM. Aside from the issues on NTP and Corporate Directory on 6921 phones, everything is working fine.
Our client has set up a CentOS and Windows VM to be the NTP server. But the phones are unable to sync the date and time with it. The 6921 does not display any date and time, while the 79xx series phones consistently displays "5/16/2012 5:30" every reboot. I don't know where the 79xx phones get this.
As a work around, I tried pointing the Netstar as the phone's NTP server. I changed the NTP settings on the xml file as shown below.
<devicePool>
<revertPriority>0</revertPriority>
<name>Default</name>
<dateTimeSetting>
<name>CMLocal</name>
<dateTemplate>M/D/Y</dateTemplate>
<timeZone>Taipei Standard Time</timeZone>
<ntps>
<ntp>
<name>192.168.4.1</name>
<ntpMode>Directed Broadcast</ntpMode>
</ntp>
</ntps>
</dateTimeSetting>
<callManagerGroup>
<name>Default</name>
<tftpDefault>true</tftpDefault>
<members>
<member priority="0">
<callManager>
<ports>
<ethernetPhonePort>2000</ethernetPhonePort>
<sipPort>5060</sipPort>
<securedSipPort>5061</securedSipPort>
</ports>
<processNodeName>192.168.4.1</processNodeName>
</callManager>
</member>
</members>
</callManagerGroup>
</devicePool>
Although the Netstar does not have a dedicated NTP server function, the 6921 phones are able to sync its date and time with the Netstar. However the 79xx phones are unable to sync.
I am using firmware 9-2-2-7 for the 6921 phones and 9-3-1 for the 79xx phones.
The default load file of the 79xx phones contain these files:
jar42sip.9-3-1TH2-5.sbn
cnu42.9-3-1TH2-5.sbn
apps42.9-3-1TH2-5.sbn
dsp42.9-3-1TH2-5.sbn
cvm42sip.9-3-1TH2-5.sbn
Any help regarding the matter is greatly appreciated.
Thanks,
Pai
.
12-25-2012 11:48 AM
Using cisco phone with third party call control is not much discussed here.
You can have better luck on websites like voip-info.org.
12-25-2012 02:53 PM
But the issues are not on call control. This is merely a Cisco Phone having trouble with Date and Time synchronization.
01-01-2013 06:12 PM
But the issues are not on call control. This is merely a Cisco Phone having trouble with Date and Time synchronization.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide