Problems with PnP and Yealink T19E2 Phone

[CeeEmm]

I'm having problems with the auto-discovery / auto-provisioning via PnP of a Yealink T19E2 phone. I don't have any other phones brands to test with. I have 2 of these phones for testing purposes and both have the same issue.

3CX Version: 16.0.676
Yealink T19 E2 Firmware: 53.84.0.35

If I create an extension and assign the phone with MAC Address, it works just fine. However, if I want to do a PnP setup, then assign an extension to it, the 3CX system does not see the phone.

I performed a packet capture and saw the flow within Wireshark, and here's what it does:

SRC "T19E2 IP" to DEST "3CX Server IP" — HTTP GET to /provisioning/<string>/<T19E2 MAC>.boot
SRC "3CX Server IP" to DEST "T19E2 IP" — HTTP 404 Not Found
SRC "T19E2 IP" to DEST "3CX Server IP" — HTTP GET to /provisioning/<string>/y000000000000.boot
SRC "3CX Server IP" to DEST "T19E2 IP" — HTTP 404 Not Found
SRC "T19E2 IP" to DEST "3CX Server IP" — HTTP GET to /provisioning/<string>/y000000000053.cfg
SRC "3CX Server IP" to DEST "T19E2 IP" — HTTP 200 OK
SRC "T19E2 IP" to DEST "3CX Server IP" — HTTP GET to /provisioning/<string>/<T19E2 MAC>.cfg
SRC "3CX Server IP" to DEST "T19E2 IP" — HTTP 404 Not Found

So what it seems like here is that at some point in the communication flow, the 3CX server positively responds to the Yealink T19E2 phone, however, when the 3CX tries to serve the phone a MAC specific cfg file, it fails.

Please help in what I can try to get PnP discovery/provisioning work properly.

Thank you!

 

[Saqqara]

Explain your network setup, need more info

Is the 3CX server and the phones on the same network ?

Do you have any settings in your DHCP scope, i.e. dhcp option 66. As you mentioned if you enter the mac address into the 3CX management console it works.

 

[CeeEmm]

3CX server and phone are on the same network.

Yes there is a DHCP option 66. It's set to http://<serverip>:5000/provisioning/<string>

 

[Saqqara]

Yes there is a DHCP option 66. It's set to http://<serverip>:5000/provisioning/<string>

If this why PnP is not working, when the phone connects to the network it detects the dhcp option 66 and provisions the phone with the setup already entered into 3CX

You can not have both PnP and option 66 working on the same network - if you want PnP setup disable dhcp option 66.

 

[CeeEmm]

Unfortunately, that suggestion did not work.

I took off Option 66 from our DHCP Server, removed the phone and associated extension from our 3CX Server, and factory reset the phone. I then packet captured the Yealink on during it's boot process.

The same flows I indicated in my OP still occur in the same fashion.