for overhead paging w/ multiple units, snom pa1 in page group?

[dandenson]

Anyone know if I can configure a few snom PA1 to work in a page group? I found this:
https://www.3cx.com/docs/ip-phone-configuration/#h.waok7g2d0ljw

but it doesn't mention the PA1 and I don't know if it's like one of the listed models.

I have a large campus that needs some page groups and some of those need to cover multiple paging units. I really like the PA1 unit, I'm hoping I can use that and even better if multicast paging works!

If not, any suggestions?

 

[VoIPTools]

A Snom PA1 is essentially just a phone with a different case. It will work fine in a paging group.

 

[dandenson]

@voiptoys, have you tested this? have you tested with multicast paging? I don't want to buy 10 units to find out I can only call it directly to page.

 

[Shawn]

i have a pa1 but have not put it in operation yet however, my understanding of the pa1 is that it's just configured as an extension and when that extension is called, the callers voice is sent to the speaker via the pa1.

with that said, everything that applies to extensions would apply to pa1.

i would add the pa1's under different extensions then add a paging group and add put those extensions in that group (that would be your zone). i think that should achieve what you're looking for

 

[craigreilly]

The PA1 can do multicast as well - with multiple listeners (where needed for Zone paging vs. Building paging)

 

[dandenson]

The PA1 is *basically* just a snom phone that auto-answers inbound calls and wires the earpiece to the speaker. What I don't know is if it takes in paging announcements also, and if it takes the multicast paging too. That's the unknown.

I have a number of PA1 in production but they are at clients and I'm not interested in testing on them. I don't have any sites with multiple units.

 

[dandenson]

@craigreilly - so I just need to create paging groups and assign each snom to the group or groups it needs to be in? provisioning will handle the multicast page setup?

 

[craigreilly]

The PA1 is a manual setup...
But if you create the "Multicast Group" in 3cx (Ring Groups) - you can also assign the regular handsets to listen to the Multicast address (which is a specific set of IP's that are also not on the same subnet as the lan, ie: 224.0.1.75:50001)... on supported phones. Also Multicast needs to be on the same physical lan segment. No server in the cloud... Although, if doing Site-to-Site VPN's I think it will. Not 100% sure there.

 

[dandenson]

@craigreilly - the snom pa1 is supported in 15.5 for auto provisioning. Are you saying that provisioning just doesn't support the paging configuration?

This would be an on-prem system. Large number of phones, paging, best to keep that local.

 

[craigreilly]

Yes auto provision would work as an extension only.... not the Mcast setup. Sorry for not being clearer.

 

[dandenson]

ok, thanks. If I do direct paging (not multicast), then that's just traveling over the sip registration so that should work right?

 

[giwm]

@dandenson: Realize that paging groups (non-multicast) will take licenses. Though full support for multicasting isn't baked into 3CX yet, it's still fully achievable through custom templates. You'll have to do that to support multiple listening addresses or to program BLFs.

 

[giwm]

Although, if doing Site-to-Site VPN's I think it will. Not 100% sure there.

That depends largely on how granular your Security Appliances get when it comes to VPN support. Most of the light touch ones will not. Full blown solutions like a Cisco ASA does allow for that functionality.