There is no need for multicast or a ring group if trying to page using a Paging loudspeaker system. The multicast and ring group is when there is a desire to page multiple extensions all at once and then relying upon the number of extension within the multicast group internal speaker capability to aurally announce your message.

The problem you seemingly have with your set-up is that the setting you published indicates that a registration to the system is not required. The problem with this is that without a registration, 3CX does not perceive that extension 205 is connected and able to take calls and therefor the forwarding rules regarding busy or not registered come into play. You should have the extension register to 3CX and its corresponding indicator should be green.

Additionally, as this is a paging gateway, you should only need to dial the extension directly (205) whereupon it will/should then auto-answer your call and allow your voice message to be passed directly output to the amplifiers and speakers of the paging system. It should not need the *9 dial code that the standard phones need. However, you could still try *9 to see once registered as a test.

You could include the extension in a ring group and use multicast if the device supports it. This would allow you to use both loudspeaker based paging systems along with a multitude of speaker phones should the situation call for it, but a registration is needed for 205 regardless.

May I ask why are you even considering multicasting? All you need is for IT to register against 3CX as the extension chosen (205) and for the user to dial it when needed. Am I missing something here? BTW, both radio buttons on YES.

3CX Promotions link http://www.sigmavoip.com/siptrunk.htm

Stop hovering to collapse...Click to collapse...Hover to expand...Click to expand...

Glad it worked BUT set both to yes, you want the PA to unregister when rebooting so that it will show as unavailible to the system while down.

Click to expand...

If the device rebooting, which should not be happening that often, or just unregistered, a call to it, is going to fail one way or another. So... in the big scheme of things it really doesn't make much of a difference, unless, for some unexplained reason it is constantly up and down. If that is the case, well...you've got bigger problems to solve.

Why allow 3CX to think that the device is online when it isn't? Why not, that's what it's for and 3CX supports the feature...

PS, that ONLY kicks in when the device is rebooted via the web interface/telnet or controlled. It will not unregister in case of a power issue, so this will likely happen when you reboot it, perform maintenance (config or FW).

3CX Promotions link http://www.sigmavoip.com/siptrunk.htm

Stop hovering to collapse...Click to collapse...Hover to expand...Click to expand...