Cisco 7940G - "Phone Unprovisioned"

Discussion in '3CX Phone System - General' started by ciscouser, Oct 26, 2007.

  1. ciscouser

    Joined:
    Oct 26, 2007
    Messages:
    4
    Likes Received:
    0
    Hi,

    I have properly modified my Cisco 7940G to SIP and am using Pumpkin as a TFTP Server. Everything seems fine, but I get a message "Phone Unprovisioned."

    In my log files the only issues I notice is that the .cnf.xml and .tlv are not found. Are these files required for this phone to function with 3CX? If so does anybody have examples of these files and/or experience setting up 7940G's with 3CX version 3.1?

    Best Regards.
     
  2. dyntech

    dyntech New Member

    Joined:
    Mar 28, 2007
    Messages:
    160
    Likes Received:
    0
    Yes, these files basically are the configuration for your phone so you do need at least one form of them.

    Where do you get the "Phone Unprovisioned" message from? Is it on the phone display?

    There is a pretty good explanation of how to setup a Cisco to work with 3CX in the forum. Have you done a search?
     
  3. ciscouser

    Joined:
    Oct 26, 2007
    Messages:
    4
    Likes Received:
    0
    Cisco 7940G - "Phone Unprovisioned" / Configuratio

    Yes, I have done a search on the forums but still can't get past the "Phone Unprovisioned" issue. Also, I can't find any info on the .tlv file.

    Below is a log of my phone connecting to the TFTP server:
    ----
    10/26/07 20:42:16] 'CTLSEP<<MAC_ADDRESS>>.tlv' of type 'octet' is requested from 10.0.5.224
    [10/26/07 20:42:16] >> 1: File not found
    [10/26/07 20:42:16] 'SEP<<MAC_ADDRESS>>.cnf.xml' of type 'octet' is requested from 10.0.5.224
    [10/26/07 20:42:16] Transfer of 'SEP<<MAC_ADDRESS>>.cnf.xml' has successfully completed
    [10/26/07 20:42:30] 'SIPDefault.cnf' of type 'octet' is requested from 10.0.5.224
    [10/26/07 20:42:30] Transfer of 'SIPDefault.cnf' has successfully completed
    [10/26/07 20:42:30] 'SIP<<MAC_ADDRESS>>.cnf' of type 'octet' is requested from 10.0.5.224
    [10/26/07 20:42:30] Transfer of 'SIP<<MAC_ADDRESS>>.cnf' has successfully completed



    Below is my SIP<<MAC_ADDRESSS>>.cnf:
    ---
    image_version: P0S3-07-5-00

    line1_name: 101

    line1_authname: 101

    line1_password: 101line1_password: <<pass>>



    Below is my SEP<<MAC_ADDRESS>>.cnf.xml:
    ----
    <device>
    <deviceProtocol>SIP</deviceProtocol>
    <sshUserId>ssh_username</sshUserId>
    <sshPassword>sshpassword</sshPassword>
    <devicePool>
    <dateTimeSetting>
    <dateTemplate>D-M-YA</dateTemplate>
    <timeZone>Pacific Standard/Daylight Time</timeZone>
    <ntps>
    <ntp><name>north-america.pool.ntp.org</name>
    <ntpMode>Unicast</ntpMode>
    </ntp>
    </ntps>
    </dateTimeSetting>
    <callManagerGroup>
    <members>
    <member priority="0">
    <callManager>
    <ports>
    <ethernetPhonePort>2000</ethernetPhonePort>
    <sipPort>5060</sipPort>
    <securedSipPort>5061</securedSipPort>
    </ports>
    <processNodeName>10.0.5.10</processNodeName>
    </callManager>
    </member>
    </members>
    </callManagerGroup>
    </devicePool>
    <sipProfile>
    <sipProxies>
    <backupProxy></backupProxy>
    <backupProxyPort></backupProxyPort>
    <emergencyProxy></emergencyProxy>
    <emergencyProxyPort></emergencyProxyPort>
    <outboundProxy></outboundProxy>
    <outboundProxyPort></outboundProxyPort>
    <registerWithProxy>true</registerWithProxy>
    </sipProxies>
    <enableVad>false</enableVad>
    <preferredCodec>g711</preferredCodec>
    <natEnabled></natEnabled>
    <phoneLabel>101</phoneLabel>
    <sipLines>
    <line button="1">
    <featureID>9</featureID>
    <featureLabel>101</featureLabel>
    <proxy>10.0.5.10</proxy>
    <name>101</name>
    <displayName>MyName</displayName>
    <authName>101</authName>
    <authPassword>password</authPassword>
    <messagesNumber>999</messagesNumber>
    </line>
    <line button="2">
    <featureID>21</featureID>
    <featureLabel>SpeedDial</featureLabel>
    <speedDialNumber></speedDialNumber>
    </line>
    </sipLines>
    <!-- tried removing dialtemplate xml -->
    <dialTemplate>DRdialplan.xml</dialTemplate>
    </sipProfile>
    <commonProfile>
    <phonePassword></phonePassword>
    </commonProfile>
    <loadInformation></loadInformation>
    <versionStamp></versionStamp>
    <directoryURL></directoryURL>
    <servicesURL></servicesURL>
    </device>
     
  4. ITWorks

    ITWorks New Member

    Joined:
    Apr 7, 2007
    Messages:
    121
    Likes Received:
    0
    cisco 7940 unprovisioned

    These files provide for secure configuration transfer and are not required for the phones to work with 3CX.

    The unprovisioned message on the phone indicates it has not loaded a valid configuration file. The most common cause of unprovisioned I have experienced is a syntax error in the configuration file. You can http into the phone IP address and check its latest log. You should see an indication of the line in the configuration file that failed to load and correct it.

    Mark
     
  5. ITWorks

    ITWorks New Member

    Joined:
    Apr 7, 2007
    Messages:
    121
    Likes Received:
    0
    cisco 7940 unprovisioned

    Just a second thought on the unprovisioned. I did not think the cnf.xml files worked on the 7940 phones but instead used the .cnf files configured as documented on the 3CX Support page. I use the xml files on the 7941s and 7961s but on the 7940s the much simpler .cnf files as described on the Support page and they worked very well.

    Mark
     
  6. dyntech

    dyntech New Member

    Joined:
    Mar 28, 2007
    Messages:
    160
    Likes Received:
    0
    For my 7960 I only use the .cnf file.

    I would try a newer firmware version also. It looks like you have version 7.5, and I know version 8.6 is out.
     
  7. ciscouser

    Joined:
    Oct 26, 2007
    Messages:
    4
    Likes Received:
    0
    Firmware Upgrade

    As suggested I attempted to update the firmware to 8.6 but this fails.

    [10/29/07 11:03:11] 'P003-08-6-00.loads' of type 'octet' is requested from 10.0.x.x
    [10/29/07 11:03:11] >> 1: File not found

    It appears to be looking for "P003-08-6-00.loads" when the filename in the firmware upgrade package is "P0S3-08-6-00.loads"

    Any idea why the newer firmware is looking for the wrong file?
     
  8. ciscouser

    Joined:
    Oct 26, 2007
    Messages:
    4
    Likes Received:
    0
    7940G Authentication

    So, I was able to get the upgrade to 8.6 completed successfully. However, now I am faced with the issue of the phone not registering:


    The simple <<MAC>>.cnf
    line1_name: 101
    line1_authname: 101
    line1_password: 101

    As are the settings in 3CX Extension for 101 and on the device (101/101).

    AuthMgr::eek:nAuthFailure
    [CM101000] Registration request from sip:101@10.0.x.10 failed. Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
     
  9. ITWorks

    ITWorks New Member

    Joined:
    Apr 7, 2007
    Messages:
    121
    Likes Received:
    0
    Create a OS79XX.TXT file or modify the current one if it exists. Put one line in the text file as follows. Place the file in your TFTP route directory.

    P0S3-08-6-00

    Mark
     
  10. dyntech

    dyntech New Member

    Joined:
    Mar 28, 2007
    Messages:
    160
    Likes Received:
    0
    Here is what my SIPxxxx.cnf file looks like:


    # SIP Default Generic Configuration File



    # Image Version

    image_version: P0S3-08-6-00

    # Line 1 appearance
    line1_name: 100

    # Line 1 Registration Authentication
    line1_authname: 100

    # Line 1 Registration Password
    line1_password: 1234

    # voicemail dialing
    messages_uri: 999


    And yes, I forgot you need the OS79XX.TXT file to tell the phone what version of firmware to expect.
     

Share This Page