Broadcasts (Zenitel Connect Pro)
From Zenitel Wiki
A Broadcast call provides one‑way audio distribution to multiple recipients simultaneously. Users can initiate a Broadcast call by dialing the designated number to deliver live audio to receiving devices, such as for public announcements. Pre‑recorded Audio Messages can also be sent to a Broadcast group.
Function
Live Broadcast
To do announcement from an intercom device:
- Dial the broadcast number
- A chime signal is heard in all member devices
- As soon as the chime signal is finished the microphone will open (no need to press any PTT button), and the operator can speak
- End the broadcast by pressing the C-key or by replacing the handset
To trigger announcement via Zenitel Link:
- Link API: POST /api/calls “from_dirno”: <source device> “to_dirno”: <Broadcast call>
Dispatch pre-recorded message
- From an intercom device: *9*<message>*<broadcast>#
- From Zenitel Link: Link API: POST /api/calls “from_dirno”: <message> “to_dirno”: <Broadcast call>
For more details, see Audio Messages
Configuration
Create Broadcast groups
From the Zenitel Connect Pro web interface, navigate to Features > Broadcasts. By default there are no broadcast calls defined. To add a new broadcast , click and define a directory number, name, priority and call time out. Click
to accept the entry.
| A system configured with 4 broadcast groups |
- Directory Number: Any number (Recommended numbers are 840 - 859)
- Name: The SIP display name
- Priority: 1-250. Default is 70
- Call Timeout: Max duration of call before automatic hang-up, 0 means no timeout
- Members: A list of receiving devices
- Multicast Address is a read-only value, visible only when there is at least one ITSV video phone or Generic SIP device included as member.
| ITSV devices can be added as member of a broadcast call, and receive broadcast call audio. However the full set of features described below is only available for native Zenitel devices as receivers. |
- The Answer Timeout in the Devices and Connections > Global Parameters setting controls how long a Broadcast call will be queued on busy.
Broadcast membership
- Select the broadcast group by clicking on the radio button to the left.
- Select members from the list of available devices in the list to the left.
- Click
to move selected devices to the section Members. Use the
to remove a device from the group.
| Adding members to a broadcast group |
Relay Activation During Broadcast
A set of device GPOs/relays can be associated with a broadcast call number through configuration. These GPOs will activate when the broadcast call becomes active. If the broadcast call is queued due to a busy state, the GPOs will not activate until the call transitions to the in‑call state.
Intended use case: Selecting zones on external amplifiers during broadcast. The IP-LCM unit can typically be used as an audio interface towards an external amplifier, and by activating a combination of relays the appropriate zone can be activated.
Configuration:
- Select the Broadcast group by clicking the checkbox next to the group
- Click the GPO Control icon in the top left corner
- In the window pane to the right, add the device with relays/GPOs (e.g. IP-LCM)
- Add which relays/GPO to be activated during the broadcast
| Dialing the Broadcast number 842 will trigger relays 2, 5 and 6 on IP-LCM 301 |
Priorities and Permissions
Broadcast Call Setup priority
Before setting up a Broadcast call, Zenitel Connect Pro will check if the broadcast overlaps with any other active broadcast calls.
- If there are conflicting calls, the Broadcast call will be queued with busy tone to caller.
- If all conflicting calls have lower priority (a higher priority value 1 -250), the conflicting calls are cancelled, and the new call is connected.
- Otherwise the call will stay in queue, and will be connected if the conflicting call hangs up. Max duration in queue is controlled by global “Answer Timeout” setting.
Offline member devices do not block Broadcast call setup.
When the Broadcast call is connected, Zenitel Connect Pro will play a “ding-dong” chime (hard coded) to all parties as attention signal.
The callers microphone is connected to the Broadcast call immediately after the attention signal. There is no support for PTT (Press To Talk).
Broadcast received while in a Regular call
The Broadcast call priority controls the interaction between Broadcast audio and regular call audio.
- Priority 1-20 (Alarm): Regular call audio is muted. Only broadcast audio is played. Volume and handset override is activated.
- Priority 21-40 (High): The Broadcast audio is mixed with the regular call
- Priority 41-250 (Normal / Low): The Broadcast audio is not played
If the device have Do-Not-Disturb(DnD) activated, the device receive Broadcast calls with priority high or alarm (40 or lower) only. ITSV and 3rd-party phones still receive all broadcast calls even if DnD is active.
|
Permissions
By default all users can initiate a broadcast. Often there is a need to set access restrictions, and allow selected users only to initiate broadcast. To configure restrictions navigate to Devices and Connections > Call Services and cofigure restrictions on "Broadcast numbers".
Networking
Broadcast call audio is distributed on multicast, 239.192.0.0/14 IPv4 (Organization Local Scope). If there are devices on different IP subnets than the Zenitel Connect Pro, intervening routers have to be configured for multicast.
UDP ports between 61080 and 61700 are used on devices for Broadcast call audio reception.
Characteristics
| Parameter | Value | Comment |
| Max receivers in broadcast call | - | No limit, as many as supported devices. |
| Max broadcast call numbers including ITSV or Generic SIP devices | 50 | Limited by multicast address/port range |
| Max simultaneous broadcast calls | 250 | Limited by multicast address/port range |
| Max broadcast memberships for ITSV | 10 | Limited by the maximum number of multicast addresses the ITSV supports |
| Max membership for Generic SIP devices | No specific limit | Depends on the maximum number of multicast addresses the SIP device supports |
Fault finding and limitations
If it takes several seconds before the chime is heard in the calling device, there is a problem with setting up the call to all online native device members.
Zenitel Connect Pro sends requests to all online native member devices in a tight loop, and then collects responses from the devices.
- If a device does not receive audio there is a 2 second timeout in the device before sending a response
- When all devices have responded, the broadcast call starts
- If some devices are not responding at all there is a 3 second timeout in the server, before starting the broadcast call
Offline devices are skipped in the setup, and will not contribute to delay.
Check the System log for device_status message with status_type: broadcast_call.
