Ringing Group Feature
From Zenitel Wiki
The ringing group feature is based on call request to group. <br\>
Contents
Description
Compared to the Call Request feature the Ringing Group system has the following differences:
- If the caller terminate the call/hangs up, the ringing group call is automatically removed from all station within the ringing group.
- Private ringing tone is used for stations receiving a ringing group call.
- The caller can be answered from any member of the ringing group by "M-key" or "OFF HOOK"
- The private ringing tone can individually be muted by pressing "C-key" at a station in the ringing group
- The first caller in a queue for a ringing group is displayed in idle ringing group members station displays. (Mail in idle)
- When a new call to a Ringing Group is made, notification of new priority mail is avoided.
- The private ringing timeout time is by default 30 minutes. The timeout is controlled by the "Call Requester Reminder Time" timer.
- Any number of stations can be member of a ringing group
AlphaCom factory default directory numbers 6701 to 6710 are predefined as Ringing Groups related to station groups 51 to 60. <br\>
The Ringing Group feature default configuration
Feature as configured after AutoLoad/Factory default.
Feature: FEATURE_CALL_REQ_GROUP 109
Directory numbers: 6701 to 6710
Param 1: Related to station group 51 to 60.
Currently not configurable:
Param 2: Mail flags defined MAIL_FLAG_ALL_CREQ_DEL + MAIL_FLAG_IDLE_SHOW + MAIL_FLAG_CALL_REQUEST
Param 3: 6701 - 6705: Priority level 155
6706: Priority level 156
6707: Priority level 157
6708: Priority level 158
6709: Priority level 159
6710: Priority level 160
AlphaCom factory default is set to automatic UK style private ringing tone on a ringing group if the call originating from SIP/trunk. <br\>
AlphaNet Configuration
AlphaNet Configuration (10.50 and later)
From AMC 10.50 the Ringing group feature is by default global. The activation of a ringing group call is sent as broadcast to all nodes in AlphaNet. This implies that the same local (ringing) group number is activated in all nodes. (For standalone nodes the global behavior has no effect) To manage failure situations the Ringing Group mail has a 30 seconds timeout. While the initiator of the ringing group is in call requester mode the mail timeout is globally updated every 10 seconds. This means that if the data communication to the initiator node fails the ringing group calls on remote nodes will be terminated withing 30 seconds. (For regular call request the timeout is 7.5 days)
From AMC 10.50 no configuration for AlphaNet ringing group is required. <br\> If global behaviour is unwanted the feature can be turned off by the nvram setting:
ex_profile.glob_const.glob_ring_gr = 0 (default 1)
AlphaNet Configuration (10.42 and earlier)
The groups configured used for the RingingGroup feature are local. To activate a ringing group from a remote node the ringing group should be activated by a $SEND_MAIL message with the ringing group parameters set. Canceling of a ringing group also needs an event string to synchronize the nodes. <br\>
Example 1
A 2 node system with ringing group in Node 2<br\>
- In node 1 there is no ringing group, the stations only activate the ringing group in node 2.
- In node 2 the Ringing group is configured with number "6701" related to station group 51. <br\>
Activate ringing group in node 1 dialing 6701: <br\>
This is based on the standard autoload "6701" <br\>
Activate ringing group in node 2 from node 1, dialing 6701: <br\>
Node 1 configuration. Directory number 6701 configured as 52-event trigger without tone, ID 0 15-Event Trigger Feature (owner udp 8 for access from all stations) When change to: ON Related to: Directory Number, ID 6701 Event: @2 $SM %1.ref NG51 U160 NM18 GV U13
Global reset of ringing group call.
Node 1 configuration: 11-Call requester mode (owner udp 8 for all stations) When change to: OFF When related to: All Event: @2 $CANM %1.ref LV
Example 2
A 2 node system with common ringing group with members in both nodes.<br\>
- Ringing group "6701" related to station group 51
Activating ringing group by dialing 6701 from both nodes <br\>
Common configuration in both nodes.
Directory number 6701 configured as 52-event trigger without tone, ID 0
15-Event Trigger Feature (owner udp 8 for access from all stations)
When change to: ON
Related to: Directory Number, ID 6701
Event: @01 $SM %1.ref NG51 U160 NM18 GV U13
@02 $SM %1.ref NG51 U160 NM18 GV U13
Global reset of ringing group call.
Configuration: 11-Call requester mode (owner udp 8 for all stations) When change to: OFF When related to: All Node 1: Event: @02 $CANM %1.ref LV Node 2: Event: @01 $CANM %1.ref LV
Example 3
A multi node system with common ringing group with members in all nodes.<br\> This configuration can also be used for Example 2,(even example 1 without any ringing group members in node 1)
Activating ringing group by dialing 6701 from any exchange: <br\>
Common configuration in both nodes. Directory number 6701 configured as 52-event trigger without tone, ID 0 15-Event Trigger Feature (owner udp 8 for access from all stations) When change to: ON Related to: Directory Number, ID 6701 Event: @FF $SM %1.ref NG51 U160 NM18 GV U13
Global reset of ringing group call.
Common Configuration: 11-Call requester mode (owner udp 8 for all stations) When change to: OFF When Related to: All Event: @FF $CANM %1.ref LV
Events Trigged
Station Events<br\>
1-Audio - Private Ringing And Incoming Call
Audio <br\> This events are trigged for stations in the ringing group when the group is called and private ringing tone is active.<br\>
- ON/OFF will toggle with the ringing tone
%1 = station with private ringing<br\> %2 = unavailable
11-Call Requester Mode
Call Requester Mode<br\>
- ON Initiating Ringing Group Call.<br\>
- OFF Call is canceled/answered
%1 = Initiator<br\> %2 = Ringing group called. ("6701", "RingGroup 1") <br\> <br\> Mail Events<br\> Mail events will be trigged when ringing group calls is in the station queue.<br\> (Mail Event will also trig on regular priority mail presence)
6-Priority Mail Present
- ON when ringing group mail(s) are present in station queue.
- OFF when no mails present.
%1 = station with mail present<br\> %2 = unavailable
10-Received Mail
Received Mail<br\>
- ON when a new ringing group mail arrives.
- OFF when the caller is answered.
%1 = Ringing Group mail receiver.<br\> %2 = Ringing group caller.<br\>
12-Priority Mail In Idle
- ON when ringing group mail(s) are present in station queue and station is idle.
- OFF when no mails present or station busy.
%1 = station with mail present<br\> %2 = unavailable
23-New Current Mail In Station Queue
See event description: New Current Mail<br\>
24-New First Mail In Station Queue
See event description: New First Mail<br\>
Special Adjustments
To disable different ringing tone from external calls currently the TST console nvram function must be used to set the following parameter:
Nvram: ex_profile.flags.trunk_call_req_ringing = 0
The tone-pitch used for UK private ringing can be selected by
Nvram: ex_profile.glob_const.alt_priv_ring_tone = 1
- 0 = 500HZ TONE
- 1 = 400HZ TONE
- 2 = PRIVATE RING TONE
- 3 = ATTENTION TONE (muted)
- 4 = ATTENTION TONE
- 5 = BUSY TONE (muted)
- 6 = BUSY TONE
- 7 = DIAL TONE
- 9-20 = DTMF TONES
Forward a ringing group to a telephone number or other ringing group after a selectable time out if no answer. <br\> This is done by forwarding of call request by using search strings. The search strings for ONE of the stations in the ringing group can be used for programming of behavior after a configurable timeout in private ringing mode. <br\>
Call Request forward by search strings <br\>
Back to Feature description