Cisco 7941-7961-7971 SIP

Status
Not open for further replies.

bthomas09

Joined
Dec 14, 2010
Messages
2
Reaction score
0
Sorry if I have missed something but I have read every post I can find on this forum and I seem to be stuck. I have several Cisco phones but I will limit this to just the 7941. I have upgraded to the lateset SIP version from Cisco and the phone seems to work fine. I have set up the TFTP server and created the SEP<MACAddress>.cnf.xml files, etc. and everything loads on the phone fine. The phone comes up, registers (shows regestering on the phone) then shows "Your current options" with lines labeled correctly.
The thing that doesn't happen is that the phone doesn't show up on 3CX. I have tried bringing up a phone without configuring the extension and then another with the extension already added in 3CX. In both cases, the phone do not show up in 3CX and the extensions show as "Not Registered". What am I missing? Any help will be appreciated. Thanks.
 
Here is my SEP<MACAddress>.cnf.xml file contents.

<device>
<deviceProtocol>SIP</deviceProtocol>
<sshUserId>sshusername</sshUserId>
<sshPassword>sshpassword</sshPassword>
<devicePool>
<dateTimeSetting>
<dateTemplate>D-M-Y</dateTemplate>
<timeZone>Central 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>192.168.1.9</processNodeName>
</callManager>
</member>
</members>
</callManagerGroup>
</devicePool>
<sipProfile>
<sipProxies>
<registerWithProxy>true</registerWithProxy>
</sipProxies>
<enableVad>false</enableVad>
<preferredCodec>g711</preferredCodec>
<natEnabled></natEnabled>
<phoneLabel>Cisco_Phone</phoneLabel>
<sipLines>
<line button="1">
<featureID>9</featureID>
<featureLabel>200</featureLabel>
<proxy>192.168.1.9</proxy>
<port>5060</port>
<name>100</name>
<displayName>200</displayName>
<autoAnswer>
<autoAnswerEnabled>2</autoAnswerEnabled>
</autoAnswer>
<callWaiting>3</callWaiting>
<authName>200</authName>
<authPassword>1234</authPassword>
<sharedLine>false</sharedLine>
<messageWaitingLampPolicy>3</messageWaitingLampPolicy>
<messagesNumber>800</messagesNumber>
<ringSettingIdle>4</ringSettingIdle>
<ringSettingActive>5</ringSettingActive>
<contact>200</contact>
<forwardCallInfoDisplay>
<callerName>true</callerName>
<callerNumber>false</callerNumber>
<redirectedNumber>false</redirectedNumber>
<dialedNumber>true</dialedNumber>
</forwardCallInfoDisplay>
</line>
<line button="2">
<featureID>9</featureID>
<featureLabel>200</featureLabel>
<proxy>192.168.1.9</proxy>
<port>5060</port>
<name>603</name>
<displayName>200</displayName>
<autoAnswer>
<autoAnswerEnabled>2</autoAnswerEnabled>
</autoAnswer>
<callWaiting>3</callWaiting>
<authName>200</authName>
<authPassword>1234</authPassword>
<sharedLine>false</sharedLine>
<messageWaitingLampPolicy>3</messageWaitingLampPolicy>
<messagesNumber>800</messagesNumber>
<ringSettingIdle>4</ringSettingIdle>
<ringSettingActive>5</ringSettingActive>
<contact>200</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>
 
Pretty sure the answer is that the current SIP firmware does not work well with 3rd party IP PBX systems. Cisco is trying to stop this practice. You may have to go back a few versions in order to get the phones to work. Personally, while I know many people like those phones, they are such a pain to use I don't think they are worth it and you will never get 100% functionality working.
 
Bthomas 09,
The Cisco firmware V9 works fine with 3CX. I see one problem with your configuration. Under line Button 1 section, you need to change the proxy line to "<proxy>USECALLMANAGER</proxy>. Once you make this change your phone will register with 3CX.
One feature that is broken in version 9 is the redial soft botton. Other than that everything else seems to work fine.

Jorge
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
112,018
Messages
590,316
Members
164,964
Latest member
Tomski