3CX SBC - DNS + multiple Proxy entries

[yesss-de]

Hi,

i have a few questions about SBC and maybe even a feature request.

We are using Yealink phones so i only can speak for those phones.
We are planning to move to cloud and are preparing our phones to connect to SBC or directly as Router Phones (we have 220 devices in 31 branches, of which there are 46 newer yealink router capable phones)

what i saw is that the non-router-phones are implementing the SBC IP as a outbound proxy and the router phones are implementing their own IP (their real IP not 127.0.0.1) as outbound proxy

My 2 questions:

• Is it possible to let 3CX type the DNS name instead of the IP as outbound proxy?
  • i already saw the SBC HA option, but the requirement of 2 IPs on the same subnet doesn't make sense for us (would have to be in the same location which we want to avoid)
• Is it possible to configure more 2 Outbound Proxy (SBC/Router Phone) so that there's a fallback option?

If not i would like to request those as a functionality

SBC HA is not the correct solution for us as it requires 2 IP Addresses on the same subnet which would mean for us to host them in the same datacenter, but we want to separate them in case of a power outage
in this case SBC HA would still mean a single point of failiure in the current form (even if i do a location swap the SBC gets a new IP and all those phones have to be reprovisioned again to be able to work again.)

Maybe im missing someting here

 

[Alphabetic]

1. You can do what you like with a custom phone template.
2. no, make a few SBCs and spread the load. An SBC virtualised is very unlikely to go down.

 

[yesss-de]

1. You can do what you like with a custom phone template.
2. no, make a few SBCs and spread the load. An SBC virtualised is very unlikely to go down.

1. Custom phone templates always create more problems than they solve, so i see not supported
2. ok, not really what i was hoping for but still a solution

Thank you

 

[NicholasP_3CX]

Maybe im missing someting here

The SBC is located at the remote site where the phones are, NOT the data centre.

The SBCs job is to establish a secure connection back to the PBX. It essentially replicates what the 3CX Apps do with the tunnel.

So you will need 3 (not 2) IP addresses on the subnet where the phones are. The IP Address for each of the SBC devices as well as the floating IP address the phones will see. The phones will NOT see the individual IP Addresses of the SBCs.