Overview
This guide explains how multicast paging works and how to configure paging on supported phones and paging devices in Persona Connect. Paging allows an authorized user to make an announcement to one or more phones or paging devices at the same time.
This article includes configuration examples for:
- Avaya JSeries phones
- Grandstream GRP phones
- Yealink T-Series phones
- Algo paging devices
- Multi-Site Paging for organizations that need to page multiple locations
Who Is This Guide For?
This guide is intended for users with administrative access, including:
- Administrators
- Office Managers
- Resellers
- Other users responsible for phone or device configuration
Before You Begin
- Determine how many paging zones are required.
- Determine which phones or devices should receive each paging zone.
- Determine how users will start a page, such as a phone button or a dedicated paging device.
- Choose a multicast IP address and port for each paging zone.
- Confirm multicast traffic is allowed between the devices that need to participate in paging.
Important: Multicast paging settings are vendor-specific. Domain-level settings should only be applied when the affected phones use compatible paging configuration. Do not assume the same paging overrides will work across Avaya, Grandstream, Yealink, and other manufacturers.
How Multicast Paging Works
Multicast paging uses a multicast IP address and port to identify a paging zone. A device sending a page transmits audio to that address and port. Phones or paging devices configured to listen to the same address and port receive the page.
A basic paging configuration contains three parts:
- Paging Zone: A multicast IP address and port combination identifies the group.
- Sending Device: A phone button or paging device sends audio to the paging zone.
- Receiving Devices: Phones or paging devices listen for audio sent to the paging zone.
For example, a company could configure:
| Paging Zone | Multicast Address | Port | Example Purpose |
|---|---|---|---|
| Page All | 224.0.1.116 |
6001 |
All supported phones |
| Warehouse | 224.0.1.116 |
6002 |
Warehouse phones or speakers |
| Office | 224.0.1.116 |
6003 |
Office phones |
The sending device and receiving devices must reference the correct multicast address and port for the intended zone.
Multicast and Network Boundaries
Multicast paging normally remains within the local network or subnet. Multicast traffic does not typically cross routers, VLAN boundaries, separate subnets, or separate physical locations unless the network has been specifically configured to route multicast traffic.
Network environments vary, and configuring multicast routing is outside the scope of this guide. If the same page needs to reach devices at multiple locations or across separate networks, consider Multi-Site Paging.
Multi-Site Paging
Multi-Site Paging is designed for organizations that need the same page delivered to multiple physical locations or separate networks at the same time.
Standard multicast paging is best suited for devices located on the same local network. When multiple sites are involved, a Multi-Site Conference Bridge can distribute the page to a paging device at each participating location. Each site's paging device then rebroadcasts the audio as multicast on its local LAN.
When Should I Use Multi-Site Paging?
Multi-Site Paging is a good fit when:
- The same page needs to reach two or more physical locations.
- Each location has its own LAN, subnet, or network.
- Multicast paging is already being used locally at each site.
- You do not want to rely on multicast traffic being routed between locations.
- Each location has a compatible SIP-to-multicast paging device, such as an Algo 8180 or similar device.
How Multi-Site Paging Works
- A user dials the extension or phone number assigned to the Multi-Site Conference Bridge.
- The conference bridge answers the call and connects the paging devices configured as participants.
- A compatible paging device at each participating site receives the conference audio.
- Each site's paging device converts the received audio into a local multicast page.
- Phones, speakers, and other devices listening to that site's multicast paging group play the announcement.
This design allows the conference audio to travel between sites while keeping the multicast portion of the page local to each site's LAN.
Example: If an organization has three offices, one compatible SIP-to-multicast paging device can be configured at each office. The Multi-Site Conference Bridge sends the page to all three paging devices, and each device broadcasts the page to its own local multicast group.
Multi-Site Paging Requires Allegiant Setup
Multi-Site Paging requires configuration by Allegiant. Open a support ticket if you need Multi-Site Paging configured for your organization.
When opening the ticket, include:
- The locations that should participate in the page.
- The preferred paging extension, if one has already been selected.
- The paging device that will be used at each location, if known.
- The local multicast paging zones that should receive the page at each location.
Understanding Paging Priorities
Some phones allow paging traffic to interrupt, or barge into, an active phone call. Paging priority determines how a phone handles a page when the user is already on a call.
Priority behavior varies by manufacturer. Review the settings for the specific device type before enabling paging barge.
A high-priority page may place an active call on hold while the page is played. Configure paging priorities carefully when pages should not interrupt normal calls.
Configure Paging by Device Type
Avaya JSeries
Avaya Paging Settings
Avaya JSeries phones support multicast paging using the following parameters:
| Setting | Purpose |
|---|---|
MP_ENABLED |
Enables or disables multicast paging. |
MP_CODEC |
Controls the multicast paging codec. The existing Allegiant configuration uses value 2 for PCMU. |
MP_GROUPS_TO_LISTEN |
Defines paging groups the phone receives. |
MP_GROUPS_TO_SEND |
Defines paging groups the phone can send to. |
Step 1: Enable Multicast Paging
Add the following device override:
MP_ENABLED="1"Step 2: Configure Paging Groups the Phone Receives
The format is:
IP:port:priority:labelSeparate multiple paging groups with commas.
Example:
MP_GROUPS_TO_LISTEN="239.0.0.0:1208:16:Page All,239.0.0.0:1209:16:Sales"Avaya supports up to 10 multicast groups. Priority values range from 1 through 16.
A normal call uses priority 3 in the existing configuration. A page configured with a higher paging precedence, such as priority 2, can interrupt an active call. Allegiant's current paging configuration recommends using priority 16 when pages should not take precedence over normal phone calls.
Step 3: Configure Paging Groups the Phone Can Send To
The sending format is:
IP:port:labelExample:
MP_GROUPS_TO_SEND="239.0.0.0:1208:Page All,239.0.0.0:1209:Sales"Step 4: Add a Paging Button
Paging buttons are configured through device overrides.
Example for phone key 9:
PHONEKEY9="Key=9;Type=feature;Name=SendMpage;attr1=239.0.0.0;attr2=1208;Label=Page All"| Field | Description |
|---|---|
PHONEKEY |
The phone button being assigned. |
Key |
The same physical key number. |
Type |
Feature. |
Name |
SendMpage |
attr1 |
Multicast IP address. |
attr2 |
Multicast port. |
Label |
Text displayed on the phone button. |
Grandstream GRP
Grandstream Paging Settings
Grandstream GRP phones support multicast addresses from 224.0.0.0 through 239.255.255.255. Use a port that is not already in use by another service on the phone or network.
Paging Barge
Paging barge controls whether a paging priority can interrupt an active call.
P1566="0"The default value is 0, which disables paging barge.
| Value | Behavior |
|---|---|
| 0 | Disabled |
| 1 | Priority 1 |
| 2 | Priority 2 |
| 3 | Priority 3 |
| 4 | Priority 4 |
| 5 | Priority 5 |
| 6 | Priority 6 |
| 7 | Priority 7 |
| 8 | Priority 8 |
| 9 | Priority 9 |
| 10 | Priority 10 |
Multicast Paging Codec
| Value | Codec |
|---|---|
| 18 | G.729A/B |
| 0 | PCMU |
| 8 | PCMA |
| 2 | G.726-32 |
| 9 | G.722 |
| 98 | iLBC |
| 4 | G.723.1 |
The documented default value is 9.
P1568="9"Allow Paging While in Do Not Disturb
The following setting determines whether pages are allowed while the phone is in DND:
P8381="0"-
0= No -
1= Yes
Configure Paging Groups the Phone Receives
Grandstream phones support up to 10 paging groups. Each group is configured with a listening address and a corresponding label.
| Priority | Listening Address Override | Example | Label Override |
|---|---|---|---|
| 1 | P1569 |
224.0.1.116:6001 |
P1570 |
| 2 | P1571 |
224.0.1.116:6002 |
P1572 |
| 3 | P1573 |
224.0.1.116:6003 |
P1574 |
| 4 | P1575 |
224.0.1.116:6004 |
P1576 |
| 5 | P1577 |
224.0.1.116:6005 |
P1578 |
| 6 | P1579 |
224.0.1.116:6006 |
P1580 |
| 7 | P1581 |
224.0.1.116:6007 |
P1582 |
| 8 | P1583 |
224.0.1.116:6008 |
P1584 |
| 9 | P1585 |
224.0.1.116:6009 |
P1586 |
| 10 | P1587 |
224.0.1.116:6010 |
P1588 |
Example:
P1569="224.0.1.116:6001"
P1570="Page All"Configure a Paging Button
The following settings define a multicast paging key:
- Mode: Multicast feature
- Account: Registered account
- Description: Paging zone name
- Value: Multicast IP address and port
- Locked: Determines whether the feature key overrides an assigned key
| Key | Mode | Account | Description | Multicast Value | Locked |
|---|---|---|---|---|---|
| 1 | P1363="13" |
P1364="1" |
P1465="Label" |
P1466="224.0.1.116:6001" |
P23968="1" |
| 2 | P1365="13" |
P1366="1" |
P1467="Label" |
P1468="224.0.1.116:6002" |
P23969="1" |
| 3 | P1367="13" |
P1368="1" |
P1469="Label" |
P1470="224.0.1.116:6003" |
P23970="1" |
| 4 | P1369="13" |
P1370="1" |
P1471="Label" |
P1472="224.0.1.116:6004" |
P23971="1" |
| 5 | P1371="13" |
P1372="1" |
P1473="Label" |
P1474="224.0.1.116:6005" |
P23972="1" |
| 6 | P1373="13" |
P1374="1" |
P1475="Label" |
P1476="224.0.1.116:6006" |
P23973="1" |
| 7 | P23800="13" |
P23801="1" |
P23802="Label" |
P23803="224.0.1.116:6007" |
P23974="1" |
| 8 | P23804="13" |
P23805="1" |
P23806="Label" |
P23807="224.0.1.116:6008" |
P23975="1" |
Yealink T-Series
Yealink Paging Settings
Yealink multicast paging addresses can use multicast IP addresses from 224.0.0.0 through 239.255.255.255 and ports from 0 through 65535.
Yealink supports 31 multicast priorities. Priority 1 is the highest priority and priority 31 is the lowest.
When Yealink phones are used with an Algo paging device, the Yealink multicast channel must correspond to the Algo paging zone being used.
Allow Paging While in Do Not Disturb
The following override controls whether multicast paging can override DND based on priority:
multicast.receive.ignore_dnd.priority="0"The default value is 0, which disables this behavior. Valid configured priorities are 1 through 31.
Configure Paging Groups the Phone Receives
Yealink phones support up to 10 configured paging groups.
Each listening group uses:
multicast.listen_address.X.channel
multicast.listen_address.X.ip_address
multicast.listen_address.X.labelExample:
multicast.listen_address.1.channel="1"
multicast.listen_address.1.ip_address="224.0.1.116:6005"
multicast.listen_address.1.label="All Page"-
channel= paging priority/channel -
ip_address= multicast address and port -
label= text displayed when the phone receives the page
Configure a Paging Button
The following settings create a multicast paging button:
linekey.X.extension
linekey.X.label
linekey.X.line
linekey.X.type
linekey.X.valueExample for key 8:
linekey.8.extension="1"
linekey.8.label="Page All"
linekey.8.line="0"
linekey.8.type="24"
linekey.8.value="224.0.1.116:6005"In this example, pressing key 8 sends a multicast page to 224.0.1.116:6005.
Configure a Paging List
A paging list is useful when users need access to multiple paging zones from a single phone button.
Create the Paging Zones
multicast.paging_address.1.channel="1"
multicast.paging_address.1.ip_address="224.0.1.116:6001"
multicast.paging_address.1.label="Page All"
multicast.paging_address.2.channel="2"
multicast.paging_address.2.ip_address="224.0.1.116:6002"
multicast.paging_address.2.label="Warehouse"
multicast.paging_address.3.channel="3"
multicast.paging_address.3.ip_address="224.0.1.116:6003"
multicast.paging_address.3.label="Office"Create the Paging List Button
Example for key 8:
linekey.8.label="Page List"
linekey.8.line="0"
linekey.8.type="66"Pressing the Paging List button allows the user to select from the configured paging zones.
Algo Paging Devices
Using an Algo with Multicast Paging
An Algo paging device can be configured to receive multicast pages or act as a paging source that transmits multicast audio.
- Multicast IP range:
224.0.0.0through239.255.255.255 - Port range:
1through65535 - Documented Algo default multicast address:
224.0.2.60 - Documented default ports:
50000through50008
Ensure the multicast address and port do not conflict with other services or devices on the network.
Step 1: Configure Algo Paging Zones
Example configuration for two zones:
mcast.zone1="239.0.0.0:1208"
mcast.zone2="239.0.0.0:1209"Up to 10 zones can be configured using this method.
Configure the Algo to Receive Pages
mcast.mode="2"
mcast.rx.zones="1,2,3,4,5,6,7,8,9,10,"mcast.mode="2" enables multicast receive mode. The mcast.rx.zones setting identifies the paging zones the Algo should monitor.
When multicast audio is received on one of the configured zones, the Algo plays the page through the paging device.
Configure the Algo to Send Pages
mcast.mode="1"
mcast.tx.zones="1,2,3,4,5,6,7,8,9,10,"mcast.mode="1" enables multicast transmit mode. The mcast.tx.zones setting identifies the zones available for transmission.
An Algo can be assigned an extension for individual paging zones. Another option is to use DTMF input to allow the caller to select a paging zone after dialing the paging extension.
Change the Algo Paging Tone
The notification tone used when an Algo receives a multicast page can be changed per zone.
mcast.rxtoneX="None"Replace X with the appropriate zone number.
Available values documented for this setting include:
NoneDefaultbell-na.wavbell-uk.wavbuzzer.wavchimes.wavdogs.wavgong.wavpage-notif.wavspeech-test.wavtone-1kHz-max.wavworble1-low.wavworble2-med.wavworble3-high.wavworble4-thrill.wav
The documented default is None.
Test the Paging Configuration
After configuring the required devices, test each paging zone before deploying it to users.
- Confirm the sending device has the correct paging zone or paging button configured.
- Confirm the receiving phones or paging devices are configured for the same multicast address and port.
- Start a page from the sending device.
- Confirm all expected devices receive the announcement.
- Test each paging zone individually.
- If paging barge is configured, test the behavior while a receiving phone is already on a call.
- If DND paging is required, test the page while the receiving phone is in Do Not Disturb mode.
Troubleshooting
No devices receive the page
- Verify that the sender and receivers are using the same multicast IP address and port.
- Confirm multicast paging is enabled on the receiving phones.
- Verify that the receiving devices are configured to listen to the intended paging zone.
- Confirm the device configuration has been applied to the phones.
- Verify that the network allows multicast traffic between the sending and receiving devices.
Some phones receive the page, but others do not
- Verify that each affected phone is configured for the correct paging group.
- Confirm the multicast address and port match on every receiving phone.
- Check whether the affected phones are a different manufacturer or model.
- Do not use a vendor-specific domain-level multicast configuration across incompatible phone manufacturers.
- If multiple paging zones exist, confirm the affected phone is assigned to the intended zone.
Multi-Site Paging works at one location but not another
- Confirm the affected site's paging device is registered and included as a participant in the Multi-Site Conference Bridge.
- Confirm the paging device automatically answers the conference call.
- Confirm the paging device is receiving conference audio.
- Verify the site's paging device is configured to transmit to the correct local multicast address and port.
- Verify the phones or speakers at the affected site are listening to the same multicast address and port.
- If the conference participant itself is not connecting, contact Allegiant Support.
A page interrupts active phone calls
Review the paging priority or paging barge configuration for the affected phone model.
- Avaya paging priority can determine whether the page takes precedence over an active call.
- Grandstream uses
P1566to configure paging barge. - Yealink uses channel priority, where 1 is the highest priority and 31 is the lowest.
Phones in Do Not Disturb do not receive pages
Review the DND paging settings for the phone manufacturer.
- Grandstream:
P8381 - Yealink:
multicast.receive.ignore_dnd.priority
The paging button does not appear on the phone
- Verify the correct physical key number was used.
- Confirm the paging key override has been applied to the device.
- Confirm another configuration is not using the same key.
- For supported configurations, multicast paging keys may require device overrides instead of the standard visual phone-button configuration.
A Yealink phone does not work with an Algo paging zone
Verify that the multicast address and port are identical and that the Yealink paging channel corresponds to the intended Algo zone.
Frequently Asked Questions
Can a phone listen to more than one paging zone?
Yes. The supported configurations in this guide allow multiple multicast listening groups. The exact number and configuration method depend on the phone manufacturer.
Can different phone manufacturers use the same paging zone?
Different manufacturers can reference the same multicast address and port, but each manufacturer must be configured using its own supported multicast paging settings. Do not apply one manufacturer's device overrides to another manufacturer's phones.
What is the difference between a paging zone and a paging button?
A paging zone defines the multicast destination used by a group of devices. A paging button gives a user a convenient way to send a page to that destination.
When should I use Multi-Site Paging?
Use Multi-Site Paging when the same announcement needs to reach multiple locations or separate networks at the same time. A paging device at each location receives the page from the Multi-Site Conference Bridge and rebroadcasts it as multicast on that site's local network.
Multi-Site Paging requires Allegiant configuration through a support ticket.
Can an Algo be used to send pages?
Yes. An Algo can be configured in multicast transmit mode using mcast.mode="1". It can also be configured in receive mode using mcast.mode="2".
Need More Help?
If you need further assistance, contact our support team at support@allegiantnow.com / (913) 599-6900 or select the button below to visit our portal: