For the past 8 years we have happily been using 3CX version 3.1 (yes, you read that right - version 3.1) And it's worked just fine. Yes, we have hardly any features, but it just works. But for the past 7 years or so I've been thinking that we should upgrade. Looking at 3CX now there are a lot of great features - and the cost seems entirely reasonable. We have 20 users, so I'm thinking that Pro edition 8 SC should suit just fine (we use Exchange 2013). But the problem would appear to be our hardware - in the intervening years all our hardware has gone from being subject to 'strategic partnership' to being unsupported. Our current hardware is - Vega Europa 50 BRI ISDN gateways Vega Europa 50 POTS gateway Mostly Grand.stream handsets - GXP2000, 2010, 2020, 2140, 2160. A couple of old Linksys. A Grand.stream TA for an analogue conference phone. Now of course with v3.1 there was no provisioning, and so we have configured all these devices manually, and are happy to carry on doing so. Obviously if we have to replace all our hardware, then that makes the overall cost rather untenable, especially as the supported Snom and Yealink handsets cost (almost) exactly twice as much as the Grand.stream equivalents. So my questions are - 1. if we upgrade to v14, can we continue to use our unsupported hardware with manual configuration? But it would be nice to use some provisioning, so... 2. Does v14 still include the provisioning support for the older Grand.stream handsets that appeared to exist up to about v12? 3. If not, should we just use an older version (v10?, v12?) instead? 4. Would it be feasible for us to devise our own provisioning templates for the GXP21xx phones? (although we've got very few, as it happens) And assuming that we start buying different handsets... 5. What is your support timeline for the Handsets that you currently support? (i.e. how many years into the future will you support the handsets that you say you support right now?) I'm assuming that we will carry on with manual configuration of our Vega gateways. Thanks, Steve.