At the outset I will state that I accept this will be unsupported, but I am appealing to those with greater knowledge as to whether this would be problematic.
The senario is that I have 2 separate entities, each with instances of 3CX (V18 self hosted on Azure) - each of the offices' phones connect via a router phone at both sites so there won't be any upgrading issues there. However, remotely I connect to both accounts via a Yealink router phone (1 account via the onboard SBC and the other account set up manually).
I am just about to move both accounts across to V20 Hosted and I notice that remote IP phones must connect via an SBC unless they are a router phone. As I want to use a single ip phone for two accounts can I just check whether I can set up the phone (Yealink router phone) so that one account uses onboard SBC and the second account uses a standalone SBC (probably a raspberry pi 5) to effectively get back what I currently have working.
I appreciate I will need to turn off autoprovisioning to stop the manual settings of the 2nd account from being overwritten, but as V20 has this restriction I can't see any other workaround (yes I accept this is overkill for a multi-account router phone to have to also use a separate SBC when we are looking at a single extension on each account but there we are).
Using the app is not an option as it too does not allow multi account setups so as I have my pc set up with different windows users for each of the entities, when using entity A windows user I will not be able to receive entity B calls and I am switching between both many times during the day.
Briding the two 3CX instances is also not an option as both entities are separate and are not anything to do with each other - I simply work for both.
Does anyone have any thoughts on this ?
Many thanks in advance.
Steve
The senario is that I have 2 separate entities, each with instances of 3CX (V18 self hosted on Azure) - each of the offices' phones connect via a router phone at both sites so there won't be any upgrading issues there. However, remotely I connect to both accounts via a Yealink router phone (1 account via the onboard SBC and the other account set up manually).
I am just about to move both accounts across to V20 Hosted and I notice that remote IP phones must connect via an SBC unless they are a router phone. As I want to use a single ip phone for two accounts can I just check whether I can set up the phone (Yealink router phone) so that one account uses onboard SBC and the second account uses a standalone SBC (probably a raspberry pi 5) to effectively get back what I currently have working.
I appreciate I will need to turn off autoprovisioning to stop the manual settings of the 2nd account from being overwritten, but as V20 has this restriction I can't see any other workaround (yes I accept this is overkill for a multi-account router phone to have to also use a separate SBC when we are looking at a single extension on each account but there we are).
Using the app is not an option as it too does not allow multi account setups so as I have my pc set up with different windows users for each of the entities, when using entity A windows user I will not be able to receive entity B calls and I am switching between both many times during the day.
Briding the two 3CX instances is also not an option as both entities are separate and are not anything to do with each other - I simply work for both.
Does anyone have any thoughts on this ?
Many thanks in advance.
Steve
Last edited:
