First off, I am aware that Multicast Paging behind an SBC is not possible without extra hardware.
We have insurance mandates at our primary location that require a proper alerting system in case of an emergency.
We have been using multicast with everything (200+ phones in 4 buildings) flawlessly and without issue since our setup is a local install. Due to a couple rather problematic extended power outages that left all of our remote sites (numerous other small satellite offices connected via VPN and SBC) without a phone system for many hours, we are switching to a cloud based server and need to convert our primary location to an SBC as well.
I know it's possible to use ring groups and concurrent calls for a "good enough" paging group, but this really won't work for us due to the layouts of the buildings and ability to only have 24 active calls.
After picking up a few Algo horn speakers (SUPER AWESOME, by the way!!!), we saw the Algo 8301 paging adapter that looks like it will work perfectly for what we need. We will call the Algo with a local 3CX extension, the Algo will send out that multicast message to EVERY available phone that is configured to listen correctly.
Multicast was so mindlessly easy to set up in 3CX before our phones were on an SBC, why can't the admin console just keep the phone setup the exact same when selecting SBC for your phone and simply add a warning that multicast paging will not work on any SBC-based phones without proper local paging hardware and configuration.
It would be AWESOME to just add a new phone and select Building 1, 2, 3, 4, etc. from the dropdown like normal with a little warning message saying that it will not work unless you have all of your ducks in a row.
Creating new templates for EVERY model of phone for EVERY building in EVERY city is definitely a bummer and is pretty messy.
I know this is such a niche request, but it sounds like it would be an easy one.
We have insurance mandates at our primary location that require a proper alerting system in case of an emergency.
We have been using multicast with everything (200+ phones in 4 buildings) flawlessly and without issue since our setup is a local install. Due to a couple rather problematic extended power outages that left all of our remote sites (numerous other small satellite offices connected via VPN and SBC) without a phone system for many hours, we are switching to a cloud based server and need to convert our primary location to an SBC as well.
I know it's possible to use ring groups and concurrent calls for a "good enough" paging group, but this really won't work for us due to the layouts of the buildings and ability to only have 24 active calls.
After picking up a few Algo horn speakers (SUPER AWESOME, by the way!!!), we saw the Algo 8301 paging adapter that looks like it will work perfectly for what we need. We will call the Algo with a local 3CX extension, the Algo will send out that multicast message to EVERY available phone that is configured to listen correctly.
Multicast was so mindlessly easy to set up in 3CX before our phones were on an SBC, why can't the admin console just keep the phone setup the exact same when selecting SBC for your phone and simply add a warning that multicast paging will not work on any SBC-based phones without proper local paging hardware and configuration.
It would be AWESOME to just add a new phone and select Building 1, 2, 3, 4, etc. from the dropdown like normal with a little warning message saying that it will not work unless you have all of your ducks in a row.
Creating new templates for EVERY model of phone for EVERY building in EVERY city is definitely a bummer and is pretty messy.
I know this is such a niche request, but it sounds like it would be an easy one.
