Using a Cisco 7941/7961 phone with 3CX

[runge]

Hi Guys,

Did any of you solve the incorrect time issue?

Thanks,

Jonathon

[Garrett]

Although this tutorial is more for Asterick, would it be possible to use this tutorial to set up a Cisco 7960G for use with a 3CX system?

[runge]

Although this tutorial is more for Asterick, would it be possible to use this tutorial to set up a Cisco 7960G for use with a 3CX system?

Hi Garrett,

We have the 79x1 series working on 3CX. You can use the same tutorial. The only difference is you will not have the correct time/date. Asterisk systems return the date/time in the SIP 200 reply information while 3CX doesn't. I have asked for a feature inclusion, but was told by a number of staff (both via forum http://www.3cx.com/forums/time-provisioning-via-sip-200-ok-reply-12895.html and over the phone) that they had an agreement with Cisco to only support the SPA models.

The only way to change the date/time is to SSH into each phone every time it is booted as there is no root access to permanently write the time.

We are now looking around at alternatives as we believe this to be a critical feature. The majority of our clients have Cisco Phones or prefer them over others.

The following is our config for the 7941s:

Code: Select all


<device>
<deviceProtocol>SIP</deviceProtocol>
<sshUserId>sshusername</sshUserId>
<sshPassword>sshpassword</sshPassword>
<devicePool>
<dateTimeSetting>
<dateTemplate>D-M-Y</dateTemplate>
<timeZone>E. Australia Standard Time</timeZone>
<ntps>
<ntp>
<name>172.20.0.2</name>
</ntp>
</ntps>
</dateTimeSetting>
<callManagerGroup>
<members>
<member priority="0">
<callManager>
<ports>
<ethernetPhonePort>2000</ethernetPhonePort>
<sipPort>5060</sipPort>
<securedSipPort>5061</securedSipPort>
</ports>
<processNodeName>172.20.0.2</processNodeName>
</callManager>
</member>
</members>
</callManagerGroup>
</devicePool>
<sipProfile>
<sipProxies>
<registerWithProxy>true</registerWithProxy>
</sipProxies>
<enableVad>false</enableVad>
<preferredCodec>g711alaw</preferredCodec>
<natEnabled></natEnabled>
<phoneLabel>Cisco_Phone</phoneLabel>
<sipLines>
<line button="1">
<featureID>9</featureID>
<featureLabel>100</featureLabel>
<proxy>172.20.0.2</proxy>
<port>5060</port>
<name>100</name>
<displayName>100</displayName>
<autoAnswer>
<autoAnswerEnabled>2</autoAnswerEnabled>
</autoAnswer>
<callWaiting>3</callWaiting>
<authName>100</authName>
<authPassword>1234</authPassword>
<sharedLine>false</sharedLine>
<messageWaitingLampPolicy>3</messageWaitingLampPolicy>
<messagesNumber>800</messagesNumber>
<ringSettingIdle>4</ringSettingIdle>
<ringSettingActive>5</ringSettingActive>
<contact>100</contact>
<forwardCallInfoDisplay>
<callerName>true</callerName>
<callerNumber>false</callerNumber>
<redirectedNumber>false</redirectedNumber>
<dialedNumber>true</dialedNumber>
</forwardCallInfoDisplay>
</line>
<line button="2">
<featureID>9</featureID>
<featureLabel>100</featureLabel>
<proxy>172.20.0.2</proxy>
<port>5060</port>
<name>603</name>
<displayName>100</displayName>
<autoAnswer>
<autoAnswerEnabled>2</autoAnswerEnabled>
</autoAnswer>
<callWaiting>3</callWaiting>
<authName>100</authName>
<authPassword>1234</authPassword>
<sharedLine>false</sharedLine>
<messageWaitingLampPolicy>3</messageWaitingLampPolicy>
<messagesNumber>800</messagesNumber>
<ringSettingIdle>4</ringSettingIdle>
<ringSettingActive>5</ringSettingActive>
<contact>100</contact>
<forwardCallInfoDisplay>
<callerName>true</callerName>
<callerNumber>false</callerNumber>
<redirectedNumber>false</redirectedNumber>
<dialedNumber>true</dialedNumber>
</forwardCallInfoDisplay>
</line>
</sipLines>
<dialTemplate>dialplan.xml</dialTemplate>
</sipProfile>
<userLocale>
<name>English_United_States</name>
<langCode>en</langCode>
</userLocale>
<networkLocale>United_States</networkLocale>
<networkLocaleInfo>
<name>United_States</name>
</networkLocaleInfo>
<commonProfile>
<phonePassword></phonePassword>
</commonProfile>
<directoryURL></directoryURL>
<servicesURL></servicesURL>
</device>



We use G.711a instead of G.711u. Also the latest Cisco SIP firmware has a call termination bug with 3CX and any missed calls will leave the call ringing on the phone. Downgrade to an earlier firmware to solve the issue.

Thanks,

Jonathon

[comresource]

Cant you just set an NTP server in the provisioning file?

[runge]

Doesn't work as NTP only applies when the Locate files can be found.

Locate files are only available on CCM. You can download the files on cisco.com, but SIP files are not available. TAC support gave me the SIP files, but it still doesn't work even though it finds the files. TAC Support can't help out as they don't support SIP.

[comresource]

I had a 7961G set up for SIP at work for a while and I do not recall having any time issues. If I get time tomorrow I will flash another spare phone for SIP and see if I can find a solution.

[runge]

That would be great. The cnf.xml config is above, with some minor particulars altered.

[comresource]

I did a quick google and I think this is what I did before.

Code: Select all

<devicePool>
     <dateTimeSetting>
        <dateTemplate>D-M-YA</dateTemplate>
        <timeZone>UTC Standard/Daylight Time</timeZone> *change this as needed*
        <ntps>
             <ntp>
                 <name>YOURNTPSERVERIPADDRESS</name>
                 <ntpMode>Unicast</ntpMode>
             </ntp>
        </ntps>
     </dateTimeSetting>

[runge]

No luck. Had also already tried both unicast and mulicast settings. Still 9:11a 25-05-07

Voip-info.org talks about it:

Date display & NTP

The phone appears to support NTP for setting the date and time, though it apparently ignores the settings unless it is able to download locale configuration files from the TFTP server. The locale files are part of Cisco CallManager, so the phone reports an "Error Updating Locale" at startup if you aren't using a CallManager SIP proxy.

Fortunately the phone will set its clock based on the Date header returned as part of the SIP proxy's registration response (200 OK). Asterisk sends the Date header during registration, but some VOIP providers to not. Hopefully future firmware revisions will enable NTP when CallManager locale files are not available.

In the meantime, some localizations are available at Cisco Online (CCO-login required).

But the files don't help and future firmware isn't available with NTP included.
Have tried 8.1 - 8.5.3 including all 8.X. releases, with the closest being:

Release 8.5(2)

Identifier
Headline and Bug Toolkit
CSCso40588

Fixed: Cisco Unified IP Phone 7941G/G-GE (SIP) cannot sync to NTP server

Which still did not fix the issue.

[comresource]

Just reflashed a 7961G and put the NTP server in. It worked just fine.

Here is what I used.

Code: Select all

<dateTimeSetting>
        <dateTemplate>M/D/Y</dateTemplate>
        <timeZone>Eastern Standard/Daylight Time</timeZone>
        <ntps>
             <ntp>
                 <name>pool.ntp.org</name>
                 <ntpMode>Unicast</ntpMode>
             </ntp>
        </ntps>
     </dateTimeSetting>

EDIT..Used SIP41.8-5-3S load

[amoss]

Thanks for this excellent post - i've been able to follow it to convert my new 7941G to sip and provision with 3cx. My issue is really strange. When I pick up the handset nothing - i have to press headset to get a dial tone. From then onwards it is fine. Same with answering I have to press the line button to answer the call.

Any help / direction would be great.

Cheers

AM

[dandee]

Hi kevin,

Not long ago I got a batch of these phones already used on one of that auction selling off the remainder of the Dell Limerick factory. In order to use them with 3CX or Asterisk I needed to change the firmware from Cisco Call Manager (SCCP aka Skinny) to SIP. There is plenty of documentation out there on how to do this, but basically you need a Cisco Smart Net license stuff to download the files (or failing that, Google is your friend…) and host them on your TFTP server. There are a lot of services out there that’ll help with this issue. A great resource that I suggest, because it’s free and gets some of the issues out of the way, is Firebrand Training’s CCNA related resources site. For more information and general guidelines check out their CCNA training.

[Cardinal]

Hello.

My first post on these forums and I'm about to stick my neck out

This does work on the Cisco 7941G using the SIP SIP41.8-5-3S

<dateTimeSetting>

<dateTemplate>Y/M/D</dateTemplate>

<timeZone>W. Europe Standard/Daylight Time</timeZone>

<ntps>

<ntp>

<name>38.117.195.101</name>

<ntpMode>Unicast</ntpMode>

</ntp>

</ntps>

</dateTimeSetting>

I get the correct time and date for Sweden so this should work.

I've tried and tried, it seems the Cisco do NOT handle FQDN with SIP/3CX and NTP, you have to use IP Address.

I have to say, sadly WAY to many guides are in error and what people say works most of the time don't.

I got my hands on a Cisco 7941G that had SCCP, I almost bricked it trying to get it to work in the first place, then days and countless google hours and reading, now finaly, I'm getting there.

I for one skiped the "guide" how to's, solved mine by trial and error.

Now, all I have left is to find a mock up / Template of service.xml and I'm almost there.

But for this thread, I've tried many ways to get the time and date to show correct, and this is one I know working correct.

Then I post this the phone says, 10:53 11/02/14, since I live in sweden we show date and time a tad different

Regards

Niclas / Sweden

[alfaivo]

We use G.711a instead of G.711u. Also the latest Cisco SIP firmware has a call termination bug with 3CX and any missed calls will leave the call ringing on the phone. Downgrade to an earlier firmware to solve the issue.

Thanks,

Jonathon

I'm experiencing this issue on 7941/7961 with SIP41.8-5-3S, missed calls are not placed into missed calls but stay on screen like when the phone is ringing. How can this be resolved? Is it firmware related as quoted above, or SEP.cnf.xml needs editing?

If firmware, which version would work correctly?

Thank you