Update 6 Alpha - The Next Generation 3CX!

[rotim]

When testing a few Yealink phones today I've noticed that every configured phone (from the Admin portal) creates a unique identifier in the provisioning Link.
For exacmple: https://FQDN:5001/provisioning/UNIQUEIDENTIFIER

This removes the possibility of using our own Yealink Provisioning Server.
You now have to manually create a Server and Device PER phone. This will add so much work to configuring and deployment.
Why is this changed in update 6? Will this be reverted to what it has been the last years?

 

[BrenttG]

When testing a few Yealink phones today I've noticed that every configured phone (from the Admin portal) creates a unique identifier in the provisioning Link.
For exacmple: https://FQDN:5001/provisioning/UNIQUEIDENTIFIER

This removes the possibility of using our own Yealink Provisioning Server.
You now have to manually create a Server and Device PER phone. This will add so much work to configuring and deployment.
Why is this changed in update 6? Will this be reverted to what it has been the last years?

This probably explains why i was having trouble provisioning a phone on friday, we have option 66 setup on our office network so i changed the name and such of an extension, and then had someone onsite factory reset the phone, and it never would come back online and provision itself, our in office server is running U6 so we could test out some of the new functionality.

We use option 66 provisioning and have phones drop shipped to the install sites (the supplier sends us their mac addresses in an excel file when they ship) on almost every deal we do, and rely heavily on option 66 to have the phones auto-configure on boot, we graciously appeal for this to be made possible again, please and thank you guys. Also, many firewalls do not support creation of more than one option 66 setting, and those that do, usually require you to setup DHCP reservations for every device to have its own option 66 value, this further complicates on-site deployments.

Thank you in advance for your consideration guys, you are always awesome to work with!

 

[LAvoip]

So as of today are we still in a testing version or are 18.0 Update 6 (Build 880) or (Build 861) production versions?

 

[Sparky Bear]

You mean STUN? Yes its in the management console and it will work for a long time. You are supporting 200 remote phones on STUN? I would think that a few SBCs will reduce your support time big time though.

surprisingly the support is not as high as anticipated (though we are not setting the port forward rules as per the guide)
the phones are working though it is about 5-10 per site for 1 client, SBC was considered for ISO requirements but now we will wait for Update 6

Can't wait for the full release =)

 

[MannyL]

This probably explains why i was having trouble provisioning a phone on friday, we have option 66 setup on our office network so i changed the name and such of an extension, and then had someone onsite factory reset the phone, and it never would come back online and provision itself, our in office server is running U6 so we could test out some of the new functionality.

We use option 66 provisioning and have phones drop shipped to the install sites (the supplier sends us their mac addresses in an excel file when they ship) on almost every deal we do, and rely heavily on option 66 to have the phones auto-configure on boot, we graciously appeal for this to be made possible again, please and thank you guys. Also, many firewalls do not support creation of more than one option 66 setting, and those that do, usually require you to setup DHCP reservations for every device to have its own option 66 value, this further complicates on-site deployments.

Thank you in advance for your consideration guys, you are always awesome to work with!

This is something we use as well

 

[Sparky Bear]

This is something we use as well

it would be super useful if the provisioning URL was specific per PBX not per user with the MAC address designating SBC phones

That said I can see why this is going this way as the SBC phone would be the only device provisioned hands-on with the remaining going through that phone.


A preferred solution if possible is to assign the SBC ahead of time and to link the phones via the SBC with only the MAC and a single Provisioning URL that way the admin side, especially for MSP's/Telso operators is easier to drop ship, we just need to ensure that the SBC device(s) is/are online first.

 

[N_G]

@Sparky Bear @rotim @BrenttG @StanM

Sorry guys but you have to use the 3CX provisioning server, not the Yealink one. We are working on a method that you can mass deploy phones via MAC and PnP behind a 3CX SBC or on local LAN. And this absolutely compatible with drop shipping phones, no DHCP 66 needed for remote deploys on hosted.

Note use of yealink prov server, 3rd party SBC, STUN is not supported with 3CX. Auth ID will stay long and complex, we can not allow our PBX to be compromised in terms of security. DHCP 66 for cloud deploys no chance I am afraid for same security reasons.

 

[Gbot@Okam]

Dear @Nick Galea
Just tried the router phone with a Yealink T57W, work like charm when entering extention number and PIN code in the phone itself !
But is it possible to provision the phone using only the web interface of the phone ? can't make it work using the autoprovisionning configuration on the web interface..
Thanks.

 

[JohnS_3CX]

Dear @Nick Galea
Just tried the router phone with a Yealink T57W, work like charm when entering extention number and PIN code in the phone itself !
But is it possible to provision the phone using only the web interface of the phone ? can't make it work using the autoprovisionning configuration on the web interface..
Thanks.

This still works as before, nothing has changed in that regard. If you do it the exact same way as before it will work.

1. Find your provisioning URL from your extension

2. Paste it under Autoprovision > Server URL, then "Confirm" to save and then click Auto Provision Now.

 

[Gbot@Okam]

This still works as before, nothing has changed in that regard. If you do it the exact same way as before it will work.

1. Find your provisioning URL from your extension

2. Paste it under Autoprovision > Server URL, then "Confirm" to save and then click Auto Provision Now.

well i've done this, copy paste the ID and Password (tried with extention number and PIN too) in the username/password field of the web admin page of the phone but autoprov never succeed. thanks for your help.

 

[JohnS_3CX]

well i've done this, copy paste the ID and Password (tried with extention number and PIN too) in the username/password field of the web admin page of the phone but autoprov never succeed. thanks for your help.

Try doing what I described above instead.

 

[Gbot@Okam]

Try doing what I described above instead.

i've done this too, phone stays stuck at configuration updating and that's all !

 

[JohnS_3CX]

i've done this too, phone stays stuck at configuration updating and that's all !

Just checked, this happens if the login prompt of the phone LCD is waiting for input. Cancel the login prompt, then click Autoprovision Now in your web UI and it will go through as expected.

If this is a remote phone and you cannot cancel the prompt in person, then just save the URL as we said above, and reboot the phone from the "Upgrade" tab. The phone will restart and reprovision itself automatically using the URL we provided it with.

 

[Gbot@Okam]

Just checked, this happens if the login prompt of the phone LCD is waiting for input. Cancel the login prompt, then click Autoprovision Now in your web UI and it will go through as expected.

If this is a remote phone and you cannot cancel the prompt in person, then just save the URL as we said above, and reboot the phone from the "Upgrade" tab. The phone will restart and reprovision itself automatically using the URL we provided it with.

yes that is working ! (insert the URL, confirm, restart the phone)
That is perfect !
One last question, if IP of the phone change due to DHCP, will the Proxy IP be refresh in accordance ?

 

[JohnS_3CX]

One last question, if IP of the phone change due to DHCP, will the Proxy IP be refresh in accordance ?

Yes, if this is a router phone and the IP changes, the proxy IP will be updated in less than a minute and you phone will be back online shortly.

 

[Gbot@Okam]

Yes, if this is a router phone and the IP changes, the proxy IP will be updated in less than a minute and you phone will be back online shortly.

Confirmed, that is sooooooooooo great Many thanks for the help provided

 

[LAvoip]

Are we still having to use test versions or are we on production versions yet?

 

[JohnS_3CX]

Are we still having to use test versions or are we on production versions yet?

U6 is not released for production yet, but it's getting very close.

Keep an eye on our blog posts and you will be informed.

 

[jamestalmage]

U6 is not released for production yet, but it's getting very close.

Keep an eye on our blog posts and you will be informed.

I've got a customer with a bunch of Yealink T29G's, that should be fixed by U6. The biggest complaint the customer has currently is history not working.

What's 3CX's recommendation here? Is there a list somewhere or what hurdles U6 needs to clear before it's moved to beta or production?

I'm really hesitant to push an alpha build to production, but when it means bringing 90%+ of their phones back into the "supported" category, it's very tempting.

 

[pmterp]

@Sparky Bear @rotim @BrenttG @StanM

Sorry guys but you have to use the 3CX provisioning server, not the Yealink one. We are working on a method that you can mass deploy phones via MAC and PnP behind a 3CX SBC or on local LAN. And this absolutely compatible with drop shipping phones, no DHCP 66 needed for remote deploys on hosted.

Is this something that will be addressed prior to the official release of update 6?
I think what I understand is at the moment, there is no way to drop ship deployments in a pre-provisioned manner, is that correct?
Our current model is the phones arrive, the customer is guided through plugging them in and then they are done. Will we need to have the customer enter the user/password for each phone for now? (assuming we do not have remote access to the customer's network to access the web UI of the phones)