Desperate help needed with Cisco 7911 phone

Nice one Scott - OK, failing SEP.cnf.xml attached, I can't work out why it won't work but then Cisco aren't trying to make life easy for me here, are they??

- ADDENDUM -

Just tried the <code> tags and I must be doing something daft, as they don't seem to work for me in any of the three edit styles. However not to be beaten, I've put the file on my web server and it can be accessed here: http://213.208.115.115/SEP00215552FB4B.cnf.xml - I'd be interested to see what anyone in the know makes of it, I have no idea why it doesn't work.

To reiterate the problem, when I boot the phone with no CTLSEP00215552FB4B.tlv file in the tftp directory, the phone boots to UNPROVISIONED, I can see it request SEP00215552FB4B.cnf.xml and CTLSEP00215552FB4B.tlv every 30 secs. If I add a blank file of the same name to the tftpboot directory (as specified on a number of sites around the web) then the phone never starts up and continuously requests CTLSEP00215552FB4B.tlv.

Any help/comments/commiserations appreciated!

I am still convinced the 7911's use the same special format as the 7912. The only difference is standards based PoE support.

The 79x1 info is not relevant.

Can you access the web browser on the phone?

Scott

John, well done, I made the change that you suggested and it worked a treat. Changed all instances of "asterisk" (the DNS name of the server, which was put in the file automatically by the Trixbox endpoint manager) with the IP address of the server, and it worked first time.

Very well done, and thanks to everyone else for their contributions.

George

Hmmmm, very strange, I though I posted the resolution to this thread already, but on checking it's not there! Right here it is again, for the benefit of anyone who runs into the same issue.

The 7911 phones seem to run the same config files as the 794x and 796x devices despite being physically similar to the 7912s. The way I got this phone (which originally shipped with SCCP firmware) to work is as follows:

- downloaded the latest SIP firmware from Cisco.com
- placed firmware files in /tftpboot on Trixbox (TFTP server address is specified in our DHCP scope so the phone knew where to get it from)
- installed new firmware on 7911 phone by hard booting the device holding down # - firmware upgrade happened automatically
- used Trixbox endpoint manager to create SEP.cnf.xml using the MAC address of the phone - this file was automatically created in /tftpboot on the Trixbox
- at this point, the phone came back as UNPROVISIONED and kept trying to download CTLSEP.tlv - I erroneously thought that this was the problem (but it wasn't)
- edited SEP.cnf.xml and changed all references to the Trixbox from name ("asterisk" in this case) to its IP address
- rebooted phone - voilla!

Hope this helps someone - would have helped me no end!

George

Turns out the extension I was testing with had a fwdall rule pointing to a mobile! doh!

So the only problem that persists is the default US locale. I can see the settings in SEP.cnf.xml so it's just a case of working out what they should be.

Brian,

That is what I was trying to establish.

I have never seen a 7911 and was basing my info on a 7912.

7912's are completely different than any other model series and I don't know if any other models use the compiled configurations and code base.

Basically not counting the 7912's you have the 7940 and 7960 which use the pre-XML configuration syntax and then everything else that uses XML configs. There are minor variants in XML tags however the basics are the same.

Does this jive with your experience?

Scott

Although not confirmed, i have heard that the 7911 works on the same basis that all 79x1 phones are working.

The issue you(George Mason) are facing regarding the locale shouldnt matter. You should be able to find the locale info on cisco's website if you really want to change that. The timezone is easily adjustable and i believe the locale adjusts certain ringout tones and busy signals specific to certain regions and needs to be downloaded to server - but im not sure. The phone will work in any location under the standard: English_US.

Actually regarding cisco, most of the information needed for programming is really published by them. Try this useful link:

http://www.cisco.com/en/US/products/hw/phones/ps379/prod_maintena...

you should reference a 7961 or 7941 for relevant info for the 7911 (presuming what i've heard is correct and you are using an sep.{macaddress}.cnf.xml file in your tftp server)

hope this helps
wtodd

Would someone please email me a working SEPxxxx.cfg.xml and dialplan.xml for the 7911 phone? I am pulling out my hair trying to get this to work with asterisk and trixbox.

Many thanks in advance!
Paige

paige.galway at gmail.com

can you please also send me a working config?
Thanks a lot.

I urgently need anyone with knowledge to help me and I really appreciate your help, I have not had any sleep for straight 36 hours trying to solve this, I just purchased a brand new out of the box Cisco 7911 with SCCP that I am trying to convert to SIP Firmware and that’s when my troubles began. Here is what I did:
1- I factory reset to prepare for upgrading using “123456789*0#”
2- I installed DHCP server for WinXP with options “66,150” using “Alax.info” tool
3- I installed TFTPD32 by PH. Jounin for WinXP on the same PC.
4- I unzipped the SIP Firmware package that includes the following files:
a. apps11.8-2-2ES6.sbn
b. cnu11.8-2-2ES6.sbn
c. cvm11sip.8-2-2ES6.sbn
d. dsp11.8-2-2ES6.sbn
e. jar11sip.8-2-2ES6.sbn
f. term06.default.loads
g. term11.default.loads

5- I connected the phone to the WinXP PC and it received an IP successfully from my DHCP
6- I monitored the TFTP logs and the phone sees it fine or so I think
7- The phone requestes the file “term11.default.loads”
8- The TFTP shows that it was sent
9- The same things keeps happening forever I think the phone restarts and keeps asking and getting the same exact file “term11.default.loads” in an endless loop for as long as I keep it connected and never gets pass that point or request another file.
10- TFTP logs don’t show any errors or that files requested are not found.

I would really appreciate anyone with knowledge to help me get this to work before I get admitted to the hospital for stress and no sleep……
Please let me know if I am missing any files, any steps, or what am doing wrong?? I understood that I can complete this process of conversion without need for Cisco Call Manager which I can’t afford, but if my understanding is wrong, also please let me know so that I can stop trying…….

In advance I thank you all for helping me..
Max

Thank you very much for your quick reply, i edited the SEPmacCNFxml and put the correct .
but no luck, i agree with you its strange the phone is not looking for SEpmac. what's even sreanger is when the phone keps looking for term11...., it actually creats a new file and puts it into my tftp folder which called "term11.default.loads.md5" i never seen that before.. and then it keeps repeating the same thing forvever even if i leave the phone for 10 hours.

here is what my tftp logs view say:
"Connection received from 192.168.1.50 on port 49152 [28/02 17:00:18.515]
Read request for file . Mode octet [28/02 17:00:18.531]
Using local port 2300 [28/02 17:00:18.531]
MD5 written into [28/02 17:00:18.593]
: sent 2 blks, 660 bytes in 0 s. 0 blk resent [28/02 17:00:18.593]
Connection received from 192.168.1.50 on port 49152 [28/02 17:01:51.140]
Read request for file . Mode octet [28/02 17:01:51.140]
Using local port 2308 [28/02 17:01:51.140]
MD5 written into [28/02 17:01:51.203]
: sent 2 blks, 660 bytes in 0 s. 0 blk resent [28/02 17:01:51.203]
Connection received from 192.168.1.50 on port 49152 [28/02 17:03:23.765]
Read request for file . Mode octet [28/02 17:03:23.781]
Using local port 2309 [28/02 17:03:23.781]
MD5 written into [28/02 17:03:23.828]
: sent 2 blks, 660 bytes in 0 s. 0 blk resent [28/02 17:03:23.828]
Connection received from 192.168.1.50 on port 49152 [28/02 17:04:56.437]
Read request for file . Mode octet [28/02 17:04:56.453]
Using local port 2312 [28/02 17:04:56.453]
MD5 written into [28/02 17:04:56.500]
: sent 2 blks, 660 bytes in 0 s. 0 blk resent [28/02 17:04:56.500]"

i purchased 6 of these and am just ready to kill myself LOL:) if i have to use them as "paperwaits" :)

you mentioned that i can have better luck if i tftp to Trixbox, i don't mind but i am new here and i don't know how... i started by downloading trixbox-2.6.2.2. i am assuming i have to install that on a linux machine not windows.. can you please tell me the steps to do this on trixbox or windows tftp if am doing something wrong.. thanx a billion

thank you very much for the helpfull info.
i took your advise and installed trixbox on a new PC. everthing went fine and i followed all the instructions. i was able to access it from internet explorer from my main winxp machine. i could not register the software though, says no internet conn, so i think it connects to dhcp and get ip, but no internet, tried manually editing dns but still. also i created extension 200 as instructed, but when i add the phone no 7911 in the list, i remember reading in posts that i can simulate by selecting 7941, so i did. but could not edit confg or don't know what to do from here in endpoint manager to load firmware on phone. thank you in advance for your help

Where the phones bought as new? Do you have any dealer recourse?

<device xsi:type="axl:XIPPhone" ctiid="1566023366">
<deviceProtocol>SIP</deviceProtocol>
<sshUserId>cisco</sshUserId>
<sshPassword>cisco</sshPassword>
<devicePool>
    <dateTimeSetting>
       <dateTemplate>D-M-YA</dateTemplate>
       <timeZone>UTC Standard/Daylight Time</timeZone>
    </dateTimeSetting>
    <callManagerGroup>
       <members>
          <member priority="0">
             <callManager>
                <ports>
                   <ethernetPhonePort>2000</ethernetPhonePort>
                   <sipPort>5060</sipPort>
                   <securedSipPort>5061</securedSipPort>
                </ports>
                <processNodeName>10.7.1.80</processNodeName>
             </callManager>
          </member>
       </members>
    </callManagerGroup>
 </devicePool>
<sipProfile>
    <sipProxies>
       <backupProxy></backupProxy>
       <backupProxyPort></backupProxyPort>
       <emergencyProxy></emergencyProxy>
       <emergencyProxyPort></emergencyProxyPort>
       <outboundProxy></outboundProxy>
       <outboundProxyPort></outboundProxyPort>
       <registerWithProxy>true</registerWithProxy>
   </sipProxies>
   <sipCallFeatures>
       <cnfJoinEnabled>true</cnfJoinEnabled>
       <callForwardURI>x--serviceuri-cfwdall</callForwardURI>
       <callPickupURI>x-cisco-serviceuri-pickup</callPickupURI>
       <callPickupListURI>x-cisco-serviceuri-opickup</callPickupListURI>
       <callPickupGroupURI>x-cisco-serviceuri-gpickup</callPickupGroupURI>
       <meetMeServiceURI>x-cisco-serviceuri-meetme</meetMeServiceURI>
       <abbreviatedDialURI>x-cisco-serviceuri-abbrdial</abbreviatedDialURI>
       <rfc2543Hold>false</rfc2543Hold>
       <callHoldRingback>2</callHoldRingback>
       <localCfwdEnable>true</localCfwdEnable>
       <semiAttendedTransfer>true</semiAttendedTransfer>
       <anonymousCallBlock>2</anonymousCallBlock>
       <callerIdBlocking>2</callerIdBlocking>
       <dndControl>0</dndControl>
       <remoteCcEnable>true</remoteCcEnable>
   </sipCallFeatures>
   <sipStack>
       <sipInviteRetx>6</sipInviteRetx>
       <sipRetx>10</sipRetx>
       <timerInviteExpires>180</timerInviteExpires>
       <timerRegisterExpires>3600</timerRegisterExpires>
       <timerRegisterDelta>5</timerRegisterDelta>
       <timerKeepAliveExpires>120</timerKeepAliveExpires>
       <timerSubscribeExpires>120</timerSubscribeExpires>
       <timerSubscribeDelta>5</timerSubscribeDelta>
       <timerT1>500</timerT1>
       <timerT2>4000</timerT2>
       <maxRedirects>70</maxRedirects>
       <remotePartyID>false</remotePartyID>
       <userInfo>None</userInfo>
   </sipStack>
   <autoAnswerTimer>1</autoAnswerTimer>
    <autoAnswerAltBehavior>false</autoAnswerAltBehavior>
    <autoAnswerOverride>true</autoAnswerOverride>
    <transferOnhookEnabled>false</transferOnhookEnabled>
    <enableVad>false</enableVad>
     <dtmfAvtPayload>101</dtmfAvtPayload>
    <dtmfDbLevel>3</dtmfDbLevel>
    <dtmfOutofBand>avt</dtmfOutofBand>
    <alwaysUsePrimeLine>false</alwaysUsePrimeLine>
    <alwaysUsePrimeLineVoiceMail>false</alwaysUsePrimeLineVoiceMail>
    <kpml>3</kpml>
    <phoneLabel>5906</phoneLabel>
    <stutterMsgWaiting>1</stutterMsgWaiting>
    <callStats>false</callStats>
    <silentPeriodBetweenCallWaitingBursts>10</silentPeriodBetweenCallWaitingBursts>
    <disableLocalSpeedDialConfig>false</disableLocalSpeedDialConfig>
    <startMediaPort>16384</startMediaPort>
    <stopMediaPort>32766</stopMediaPort>
    <sipLines>
       <line
        button="1">
          <featureID>9</featureID>
          <featureLabel>5906</featureLabel>
          <proxy>10.7.1.80</proxy>
          <port>5060</port>
          <name>5906</name>

          <displayName>Klimov</displayName>
          <autoAnswer>
             <autoAnswerEnabled>2</autoAnswerEnabled>
         </autoAnswer>
         <callWaiting>3</callWaiting>
         <authName>5906</authName>
          <authPassword>123</authPassword>

          <sharedLine>false</sharedLine>
          <messageWaitingLampPolicy>1</messageWaitingLampPolicy>
          <messagesNumber>*97</messagesNumber>
          <ringSettingIdle>4</ringSettingIdle>
          <ringSettingActive>5</ringSettingActive>
          <contact>5906</contact>
          <forwardCallInfoDisplay>
             <callerName>true</callerName>
             <callerNumber>false</callerNumber>
             <redirectedNumber>false</redirectedNumber>
             <dialedNumber>true</dialedNumber>
          </forwardCallInfoDisplay>
      </line>
      <line
        button="2">
          <featureID>21</featureID>
          <featureLabel>speed dial name goes here</featureLabel>
          <speedDialNumber>speed dial actual number goes in here</speedDialNumber>
       </line>
   </sipLines>
   <voipControlPort>5060</voipControlPort>
    <dscpForAudio>184</dscpForAudio>
    <ringSettingBusyStationPolicy>0</ringSettingBusyStationPolicy>
    <dialTemplate>dialplan.xml</dialTemplate>
</sipProfile>
<commonProfile>
    <phonePassword>123</phonePassword>
    <backgroundImageAccess>true</backgroundImageAccess>
    <callLogBlfEnabled>2</callLogBlfEnabled>
</commonProfile>
<loadInformation>SIP11.8-4-3S</loadInformation>

<vendorConfig>
    <disableSpeaker>false</disableSpeaker>
    <disableSpeakerAndHeadset>false</disableSpeakerAndHeadset>
    <pcPort>0</pcPort>
    <settingsAccess>1</settingsAccess>
    <garp>0</garp>
    <voiceVlanAccess>0</voiceVlanAccess>
    <videoCapability>0</videoCapability>
    <autoSelectLineEnable>0</autoSelectLineEnable>
    <webAccess>1</webAccess>
    <daysDisplayNotActive>1,2,3,4,5,6,7</daysDisplayNotActive>
    <displayOnTime>00:00</displayOnTime>
    <displayOnDuration>00:00</displayOnDuration>
    <displayIdleTimeout>00:00</displayIdleTimeout>
    <spanToPCPort>1</spanToPCPort>
    <loggingDisplay>1</loggingDisplay>
    <loadServer></loadServer>
</vendorConfig>
<versionStamp>1143565489-a3cbf294-7526-4c29-8791-c4fce4ce4c37</versionStamp>
<networkLocale>New_Zealand</networkLocale>

 <networkLocaleInfo>
    <name>New_Zealand</name>
    <version>5.0(2)</version>
 </networkLocaleInfo>

 <deviceSecurityMode>1</deviceSecurityMode>
 <authenticationURL>http://www/ipphone/authenticate.php</authenticationURL>
 <directoryURL>http://www/ipphone/directory.xml</directoryURL>
 <idleURL></idleURL>
 <informationURL>http://www/ipphone/GetTelecasterHelpText.jsp</informationURL>
 <messagesURL></messagesURL>
 <proxyServerURL>proxy:3128</proxyServerURL>
 <servicesURL>http://www/ipphone/services.xml</servicesURL>
 <dscpForSCCPPhoneConfig>96</dscpForSCCPPhoneConfig>
 <dscpForSCCPPhoneServices>0</dscpForSCCPPhoneServices>
 <dscpForCm2Dvce>96</dscpForCm2Dvce>
 <transportLayerProtocol>4</transportLayerProtocol>
 <capfAuthMode>0</capfAuthMode>
 <capfList>
    <capf>
       <phonePort>3804</phonePort>
    </capf>
 </capfList>

 <certHash></certHash>
 <encrConfig>false</encrConfig>

</device>

I am having the same issue with 7941 & 7970. My firmeware is 8-3-5S.