| Html |
|---|
<div id="fb-root"></div>
<script>(function(d, s, id) {
var js, fjs = d.getElementsByTagName(s)[0];
if (d.getElementById(id)) return;
js = d.createElement(s); js.id = id;
js.src = 'https://connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.11';
fjs.parentNode.insertBefore(js, fjs);
}(document, 'script', 'facebook-jssdk'));</script> |
...
| Info |
|---|
This guide explains how to use paging on a Wildix system. Created: March 2018 Updated: February 2019 Permalink: https://confluence.wildix.com/x/vAc8AQ |
| Table of Contents |
|---|
RTP multicast and SIP paging
...
- 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
...
- New PBXs can receive 15 SIP paging calls + RTP multicast
Pre 2010 PBXs can receive 6 SIP paging calls + RTP multicast
| Note | ||
|---|---|---|
Note: For Cloud / Virtual PBXs: Limitation on the number of calls is based on CPU capabilities, if CPU MHz value is higher than 700, then 15 SIP calls are allowed. You can check CPU information via SSH using the command:
|
...
| Note |
|---|
Note:
|
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 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"
- After the setup, sync all devices on the Server PBX (Cloud) by clicking Configure/ Sync device in WMS -> Devices so that the device are synced to the Client PBX (Hardware)
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:
...