Ringing Group Feature

The ringing group feature is based on call request to group. <br\>

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)

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: FEATURE_CALL_REQ_GROUP 109  
 Directory numbers: 6701 to 6705, Visible in alphabetic search
 Param 1: Related to station group 51 to 55.
Currently not configurable:
 Param 2: Mail flags defined MAIL_FLAG_ALL_CREQ_DEL + MAIL_FLAG_IDLE_SHOW + MAIL_FLAG_CALL_REQUEST
 Param 3: Priority level 155

 Feature: FEATURE_CALL_REQ_GROUP 109  
 Directory numbers: 6706 to 6710, Invisible in alphabetic search, this gives display text of the 
 ringing group name when.
 Param 1: Related to station group 56 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: Priority level 156 to 160 (6706 = 156, 6710 = 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

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 bye a $SEND_MAIL message with the ringing group parameters set. Canceling of a ringing group also needs an event string. <br\> Example 1:<br\> A 2 node system.<br\> Node 1<br\>

• In node 1 there is no ringing group, the stations only activate the ringing group 1 in node 2.

Node 2<br\>

• Ringing group 1 configured with number "6701" related to station group 51. <br\>

Activate ringing group 1 in node 2 from node 1, dialing 6701: <br\>

Node 1 configuration.
Directory number 6701 configured as 52-event trigger without tone
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 U140 NM18 GV U9 

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

Node 2 configuration:
11-Call requester mode (owner udp 8 for all stations)
When change to OFF
When Related To All
Event: @1 $CANM %1.ref LV

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