Paging - Admin Guide

RTP multicast and SIP paging

Paging makes phones of users present in the selected Paging group answer automatically in speaker mode enabling the caller to talk to the users without their intervention. In this way you can quickly broadcast an urgent message or an important announcement to the group of listeners. Wildix system supports paging over RTP multicast and SIP calls:

• Paging over RTP multicast means that PBX sends only one RTP stream to the multicast address on which devices are listening. This greatly reduces the workload placed on the PBX, especially when a large number of devices are involved

• Paging over SIP calls means that the PBX sends a single SIP call to each device of user who is present in the Paging group

The paging method is selected automatically by the system, no special configuration is required - the PBX administrator must only create a Paging group, as described in Chapter Paging group. Paging over RTP is preferred (if possible based on network configuration and available devices), if it is not available, paging is sent via SIP calls. 

Requirements and supported devices

RTP multicast

• Works only as long as the PBX and the devices are in the same network
• Is supported by the following Wildix devices: W-PA, WP4X0, WP600AXX, Vision, SuperVision, WelcomeConsole

Paging over SIP calls

Limitation on the number of paging calls:

• New PBXs can receive 15 SIP paging calls + RTP multicast 

• Pre 2010 PBXs can receive 6 SIP paging calls + RTP multicast

cat /proc/cpuinfo

Devices are called in the following priority (if there are 2 registered devices with the same priority, only 1 device will receive a call):

• • WP4X0, WelcomeConsole desk phones
  • WP600AXX, Vision/ SuperVision desk phones
  • W-AIR handsets
  • Web (Chrome)
  • Others

RTP multicast paging for Cloud PBX in WMS Network

In case you have a Cloud PBX and:

• you need more than 15 users in a paging group 
• you don't have enough bandwidth available to ensure SIP call paging 

there is a way to increase SIP paging limits of Cloud PBXs by turning it to RTP multicast stream:

• Create a WMS Network between a local Hardware and Cloud PBXs 

• Route over Diaplan the paging feature code (default 91) followed by paging group ID through the local Hardware PBX using Dialplan application "Call through remote PBX"
  

Example: 

• on Cloud PBX: edit procedure used for outgoing calls ("users" by default, if another procedure is used, make sure "pbxinternal" is added to Included procedures)
• add 91[paging_group_id] as called number, where 91 is Paging group Feature Code, example: 912, where 2 is paging group ID
• select to route calls through local PBX (in our example, "pbx-146-local" is HW PBX), "users" context
• edit "called number" (click "Set") and tick "Remove" (by default the tick is set on "Custom" → "default" destination)
• on local PBX: make sure the paging group with this ID is present and the context has "pbxinternal" in "Included procedures" (in our example call is routed through "users" context on local PBX, where "pbxinternal" is present by default)
• as a result: when dialing a paging group on Cloud PBX, call is routed to the paging group present on local PBX

Paging is now generated locally as RTP multicast and there are no limits to broadcast announcements.

Paging group

To start using Paging, first of all you need to create a Paging group:

Now you can use Feature Code (91 by default) to call this Paging group and pick up a Paging call, more information in Feature Codes Admin Guide.

Or you can use Paging in a Dialplan context, more information in Dialplan applications Admin Guide. 

Delayed Paging

Record a message and have it delivered as a page. Read the document: Delayed Paging