Trouble shooting tips on DHCP option 66

Discussion in '3CX Phone System - General' started by ClayGoss, May 1, 2015.

Thread Status:
Not open for further replies.
  1. ClayGoss

    Joined:
    Oct 4, 2012
    Messages:
    12
    Likes Received:
    0
    I have just installed 3CX, licensed 12.5 system. I have Cisco SPA5xx IP phones. I've read and re-read the documentation on setting option 66. I found a DHCP testing utility and it shows what I have put in for option 66 is being returned, which is:

    http://10.10.1.7:5000/provisioning/y2j1i57kn0/$MA.xml

    I have checked out what is in Settings > Phone Provisioning and on the extension I am trying to put up.

    The phone had firmware 7.5.2 which I updated first to 7.5.2b and then to 7.5.5. I even tried the 7.5.7s version, but no joy.

    I've factory reset the phone. I have used this phone on earlier versions of 3CX, but don't remember having such trouble.

    It is as though 3CX is not returning anything when the phone tries to make connection to the URL.

    One twist is that the phone is on a different subnet connected via VPN, but the connectivity is very good and DNS and various protocols work fine site to site.

    Thank you for any assistance.
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,582
    Likes Received:
    249
    And you have a tftp server installed and running?
     
  3. ClayGoss

    Joined:
    Oct 4, 2012
    Messages:
    12
    Likes Received:
    0
    Thank you for the response. I didn't catch in the documentation that a TFTP server was required for phone provisioning and with the http:// reference in the URL, it appeared the Abyss web server was dishing the provisioning out.

    So, with a TFTP server, running on port 69, what should option 66 be set to?
     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,582
    Likes Received:
    249
    This is pretty much what I followed for configuring some Cisco sets, so I used a tftp server.

    http://www.3cx.com/sip-phones/cisco-7940g-7960g/

    there is also this link...

    http://www.3cx.com/sip-phones/dhcp-option-66/
     
  5. ClayGoss

    Joined:
    Oct 4, 2012
    Messages:
    12
    Likes Received:
    0
    Again, thanks for the response. I have been on the second link you offered many times, and many others. The first link doesn't apply because I have SPA 5 series phones. I have been referring to: http://www.3cx.com/sip-phones/cisco-spa/ While the link you provided indicates a TFTP server is needed, the one for SPA's makes no mention of one.

    Still looking...
     
  6. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,582
    Likes Received:
    249
    I had always used devices that allowed for manual provisioning, until I got my hands on some Cisco 79XX sets. that required the addition of a tftp server following the instructions in the first link. Reading through the second link does mention that Option 66 Is sent to the sets to indicate where the tftp server "resides" on the network, but then really doesn't talk about it other than calling it a "boot server".

    This either assumes that you already have deployed a tftp server, or that one is not necessary as 3CX acts as one. Given that in point 8, in the last few lines of the article, they have Cisco SPA sets, 79XX sets and SNOM sets provisioned in the same manner, along with the information in the previous link, I ,for one, would assume that a tftp server was needed.

    I may be wrong here, and hopefully someone else can provide some clarification, but given the ease of installing the Pumpkin tftp server as described in the first link, it would take little time to prove one way or the other. I found that the Pumpkin server, showing the activity, (what file was being requested, and uploaded), helped in some initial troubleshooting.
     
  7. ClayGoss

    Joined:
    Oct 4, 2012
    Messages:
    12
    Likes Received:
    0
    I have sorted this out. No TFTP server needed. The problem was the permissions on the randomly named provisioning folder. I added everyone with defaults an I now have found joy!

    Thank you for the assistance.
     
  8. ClayGoss

    Joined:
    Oct 4, 2012
    Messages:
    12
    Likes Received:
    0
    After working with this a while, I have decided to use PumpKIN TFTP as the HTTP approach was hit and miss. Might be the security package or firewalls, but TFTP works good. I made option 66 "<3CX IP>/$ MA.xml"
     
  9. briankayser

    Joined:
    Jul 19, 2016
    Messages:
    49
    Likes Received:
    5
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.