We manage loads of 3CX tennants, The move to V20 we have tried to embrace. But we seem to always get stuck with the same problem.
This is the lack of connectivity options for remote workers and remote sites.
So it would seem we need a router phone or an SBC at every site. So huge expense. Especially for small systems.
This expense is something the customer an not understand. It used to work just fine, It works on my Mobile and my Laptop App. so Why do we need a router phone or an SBC.
One customer had three sites and only DECT phones at each site. - Only viable solution was to enable Stun via Custom Template. Something that is not supported by 3CX.
Other customers we have had to purchase Router Phones at our expense.
The next Customer our Largest are gearing up for the V20 switch. They have 5 remote Users out of 150. All have been working fine on v18 - We suggested they buy Router phones, which they have.
But now the router phones will not work for 3 of the 5 because they were using WiFi (and WiFi will not work with router phones fanvil x5u-v2) - and before you say it I know 3CX dont support WiFi - but this does not help us. As the solution that worked great under V18 now does not work and the customer has come back to us saying 'I am reading this as 3CX are no longer able to offer remote phones.'
This is 2025 and there needs to be a supported method of connectivity for phones that operate remotely without the need for SBC's, We cant be installing SBC's in customers houses - Its not supportable and in all honesty crazy that we would have too. I know i could use the STUN method via custom template but this particular customer does not like seeing unsupported in the dashboard.
I ask that 3CX review this with the end customer and your MSP's in mind. On reading other threads this is clearly an issue for many.
This is the lack of connectivity options for remote workers and remote sites.
So it would seem we need a router phone or an SBC at every site. So huge expense. Especially for small systems.
This expense is something the customer an not understand. It used to work just fine, It works on my Mobile and my Laptop App. so Why do we need a router phone or an SBC.
One customer had three sites and only DECT phones at each site. - Only viable solution was to enable Stun via Custom Template. Something that is not supported by 3CX.
Other customers we have had to purchase Router Phones at our expense.
The next Customer our Largest are gearing up for the V20 switch. They have 5 remote Users out of 150. All have been working fine on v18 - We suggested they buy Router phones, which they have.
But now the router phones will not work for 3 of the 5 because they were using WiFi (and WiFi will not work with router phones fanvil x5u-v2) - and before you say it I know 3CX dont support WiFi - but this does not help us. As the solution that worked great under V18 now does not work and the customer has come back to us saying 'I am reading this as 3CX are no longer able to offer remote phones.'
This is 2025 and there needs to be a supported method of connectivity for phones that operate remotely without the need for SBC's, We cant be installing SBC's in customers houses - Its not supportable and in all honesty crazy that we would have too. I know i could use the STUN method via custom template but this particular customer does not like seeing unsupported in the dashboard.
I ask that 3CX review this with the end customer and your MSP's in mind. On reading other threads this is clearly an issue for many.
