Yealink, Option 66 and Godaddy Certificates

Discussion in '3CX Phone System - General' started by Wendelspanswick, Mar 28, 2017.

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

    Joined:
    Jan 11, 2016
    Messages:
    94
    Likes Received:
    2
    We have never been able to get Option 66 to work before, meaning that every time we set up a new system the Yealink phones either have to be assigned to the corresponding extension when they appear in the Phones tab or even worse having to web browse into each phones interface and manually enter the account details, no fun when your doing 250 phones at a time.
    With an even larger install coming up we decided to try and get to the bottom of it and it looks to be a problem with the Trusted Certificates on the Yealink Phones. It seems that Godaddy, who we use to generate the SSL certificates, are not on the list of supported certificate suppliers so the only way we can get Option 66 to work is by browsing into the phone and disabling the Use Trusted Certificates tab which is going to be a pain on over 300 phones.
    Hopefully someone has encountered this problem before and come up with a solution?
     
  2. 3CXDude

    3CXDude New Member

    Joined:
    Oct 1, 2015
    Messages:
    105
    Likes Received:
    27
    Are these local phones ?
     
  3. Wendelspanswick

    Joined:
    Jan 11, 2016
    Messages:
    94
    Likes Received:
    2
    Yes, all on the same site and on the same voice LAN.
     
  4. CentrexJ

    CentrexJ Member

    Joined:
    May 5, 2009
    Messages:
    443
    Likes Received:
    73
    Local phones can connect to 3CX with HTTP, so set your DHCP66 to your HTTP provision path to 3CX not the HTTPS.

    We use DHCP66 all the time. Our suppliers give us a list of MAC addresses when they ship out the phones and we add the MAC to the text file we import to create the extensions, import the file, put the phone on the appropriate desk and away it goes.

    On customers with VLANS, some need to have the provision path in DHCP66 on the office VLAN/LAN DHCP options as well as the Voice VLAN DHCP. Somehow even though the Yealink picks the correct vlan info it looked for the dhcp66 on the office VLAN/LAN prior to switching to the correct vlan. Putting DHCP option 66 in both places seems to have solved this.

    Yealink T4x series (P/G/S).
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    Wendelspanswick likes this.
  5. Wendelspanswick

    Joined:
    Jan 11, 2016
    Messages:
    94
    Likes Received:
    2
    Cheers for that, doing more research it seems that Yealinks with firmware 81.0.15 or later include Godaddy by default so hopefully the new phones on order should self provision with Option 66.
     
  6. 3CXDude

    3CXDude New Member

    Joined:
    Oct 1, 2015
    Messages:
    105
    Likes Received:
    27
    I'll second CentrexJ's recommendation. We use http for local provisioning too.
     
Thread Status:
Not open for further replies.