THIS WIKI HAS BEEN UPDATED FOR VERSION 13 OF YOUR PBX GUI.
This module is for specific phones that are capable of paging or intercom. In the Paging and Intercom module, you can configure groups of phones that will auto-answer and play the page over their speakers when called from the page group. This module will work with most SIP phones that are supported by the PBX.
- In the top menu click Applications
- In the drop down click Paging and Intercom
Click the Settings tab to set global settings for page groups.
This is the announcement to be played to the remote party when their phone answers a page. The default is a beep. You can also select a system recording. Select None if you do not want to play a beep or other sound.
Click the Submit button, then click the Apply Config button.
Click the New Page Group button to add a new page group, or click the pencil icon
Standard Module Options
The extension number for this page group. Users can dial this number to page this group. The number can be any number from 3 to 11 digits as long as it doesn't match an existing extension or feature code.
The name of the page group and/or a short description to help you identify it.
Selected vs. Not Selected: Choose which extension(s) to include in the page group by dragging the desired extensions to the Selected bin. These will be included in the page group.
We do not recommend having more than 25 phones in a single page group. You can set the maximum number of phones that can be included in any page group by visiting the Advanced Settings module and changing the limit under the Max Paging Participants section.
The announcement to be played to the remote party. Select a system recording, None, or Default. If set to Default, it will use the Auto-Answer Default global setting found in the Settings tab of the Paging and Intercom module. (If that setting is not defined, it will default to a beep).
Skip/Force/Whisper: How to handle paging if an extension is busy (such as on a call).
- Skip: A busy extension will not receive the page. All other extensions will be paged as usual.
- Force: A busy extension will receive the page. The system will not check if the device is in use before paging it. Conversations can be interrupted by the page, depending upon how the device handles the page. In most cases, the phone will ring instead of auto-answering if it is on another call, but some phones will put the caller on hold and play the page. This is not usually a desirable outcome unless you are setting up a page group for emergencies, and you want all extensions to hear the page regardless of whether they are already on a call.
- Whisper: The system will attempt to use the ChanSpy capability on SIP channels, resulting in the page being sent to the busy device's earpiece. The page is "whispered" to the user but not heard by the remote party. If ChanSpy is not supported on the device or otherwise fails, no page will get through. It probably does not make too much sense to choose duplex below, if using Whisper mode.
Yes/No: This option controls whether the extension receiving the page is muted by default. If you enable duplex, the extensions that are called in the page group will not be muted, which will allow anyone to talk in the page group. Usually this will be set to No.
Paging is typically used for one-way announcements. If Duplex is set to Yes, all participants in the page group can talk to each other and hear each other, similar to a conference room.
Any user can dial *1 to un-mute themselves at any time, regardless of whether Duplex is enabled here.
Default Page Group
Yes/No: Whether to consider this page group a "default" page group. You can create one or more default page groups. This can help you save time when creating extensions in the Extensions module. There, you are given the option of whether to include an extension in the default page group(s), preventing the need to re-visit the Paging & Intercom module to add an extension to the group.