nicky,
So is this a chicken-egg thing? 3cx won't expand their provisioning capability (which I suspect will apply to more phones in the future) until 3cx complies with Plug and Play?
Yealink must comply with plug and play. If you want to help out, send them a support email.
How can I explain to users that The T2X can do this and the newer T3X cannot?
If you want to buy them - no problem - but take care of configuring them yourself. If you have a problem go to yealink.
I implemented 70 T38g units last month. Pretty easy to do using DHCP option 66. Phone just pops up on the Phone list and assign or create a new extension.
Yes - thats exactly whats NOT Working. The phone pops up and if you right click and assign an extension to it, the phone does not accept the prov file. You deployed them via option 66 NOT via plug and play. Plug and play is impossible.
The problem is the provisioning interface in 3cx. Only BLF options - and limited choices on those.
We've modified the template to do most everything we need but we have to modify the template rather than making choices on the phones provisioning tab.
We have codecs, languages, blf speeddials, parking. Those satisfy 90% of all companies nearly.
We are looking to improve. Tell us what you think is missing and if it is acceptable and highly in demand we can consider it.
Do not personally find the provisioning options "limited". There is room for improvement yes, but Ive seen huge companies deploy 3CX and work with those same options. And then yes - if you want you can simply modify the template. No big deal. Nothing is hardcoded and everything is exposed.
It is impossible that the 3CX template designer makes one template that is suitable for all 3CX Users worldwide. Of course some defaults have to take place. Those defaults happen to satisfy the majority I must say.