# Ring Groups

## Description

When Ring Groups are programmed, calls ring multiple telephones, stopping when any one of them picks up. The following ring modes are available for programming:

Ring All - rings all members of the group in unison. Second caller is in a queue until the first call is answered.

Terminal Ring - searching always from the top of the member list, each call rings the first available member of the group. If not answered before the Call Ringing Timer expires, the call is redirected away from the group. If the search finds no available member, the call is placed in a queue; then, after the Call Queued Timer expires, it is sent to an overflow or rerouting destination.

Terminal Cascade Ring - starting the hunt from the top of the member list, each new call rings the first available member for the duration of the Cascade Ring Timer. When the timer expires, the hunt continues down the list for the next available member, and so on. When the initial starting position (top of the list) is reached, hunting proceeds until either a member answers the call or the Call Ringing Timer expires and the call is redirected to an overflow or alternate destination. If the initial hunt finds no available member, the call queues; then, after the Call Queued Timer expires, it is sent to an overflow or rerouting destination.

Circular Ring - searching begins at the member after the last one to receive a call and stops to ring the first available member. If not answered before the Call Ringing Timer expires, the call is redirected away from the group. If the hunt finds no available member, the call is placed in a queue; then, after the Call Queued Timer expires, it is sent to an overflow or rerouting destination.

Circular Cascade Ring - using the circular search method rings the first available group member after the last one to receive a call. Ringing lasts for the duration of the Cascade Ring Timer. When the timer expires, the search continues down the list for the next available member, and so on. When the hunt starting position is reached, the search continues until either a member answers the call or the Call Ringing Timer expires and the call is redirected to an overflow or alternate destination. If the initial search finds no available member, the call queues; then, after the Call Queued Timer expires, it is sent to an overflow or rerouting destination.

Member availability which determines whether calls queue to the ring group or overflow to an alternate answer point is defined as follows:

Available | Unavailable
If a single member is in one of these states, calls will queue: Idle and Present Busy and Present Make Busy Reseize Timer running for remote member (see Note) | If all the members are in the any of the following states, calls immediately overflow: Do Not Disturb Out of Service (immediate overflow applies only if all members are local non-resilient; see Note for details) Absent

Other features of Ring Groups:

- The Last Group Member Routing (LGMR) feature connects a call to the same agent that previously attended the call, if the caller calls the same ring group using the same Calling Party Number (CgPN or ANI(Automatic Number Identification)) number within the duration specified by Last Group Member Routing - Caller Callback Time. The feature is enabled by specifying a value in the Last Group Member Routing - Caller Callback Time field.

- When a call is made to a ring group, the system records the following feature data: the CgPN or ANI(Automatic Number Identification), the ring group, and the ring group member's number that answered the call. The system queries incoming calls with the CgPN or ANI(Automatic Number Identification) recorded in the feature data, and if a match is found, routes the calls to the associated ring group member.

- LGMR calls to ring group members are indicated by an on-screen "Calling Back" text followed by the calling party's name and number on the 69xx series IP phones. On 53xx series IP phones, the first line displays the called number and name. The second line displays the "CALLBACK" text followed by the ring group name (if configured) or number.

NOTE: The display is restricted for other telephone models.

- Ring groups (including Emergency Response groups) can contain local, resilient and remote DNs (RDN).

NOTES

- To be "valid", a remote member must be Present and idle (available). Busy, Do Not Disturb (DND), Make Busy or Out of Service state will cause a Reseize Timer to start on the remote member and the member cannot be seized until the timer expires. If the remote member continues to be busy, in DND, Make Busy or Out of Service, then the Reseize Timer is started again.

- For resilient ring groups, resilient members are remote members. When local members are present and out-of-server, the system diverts the calls to remote members and applies the Call Queued Timer when attempting calls to remote members.

- To reduce trunk traffic, it is recommended that the ring group is hosted by the controller on which most local members reside.

- Calls to rings groups can be rerouted for any of the following reasons:

- Out Of Service - When all group members are unavailable, calls are immediately redirected to an overflow or rerouting destination. If no overflow or reroute destination is programmed, then any provisioned exception handling is applied.

NOTE: When all members are Out Of Service, the immediate overflow is applied only if all members are local non-resilient. If there are any RDN or resilient members in that group, callers will be placed in the ringing queue, then the waiting queue, and the overflow will not take place until the timer expires.

- Predictive overflow - Predictive overflow can be configured for the group allowing the system to calculate whether a call should be queued or immediately redirected to an overflow or rerouting destination. The calculation is based on the following formula: average call duration (as provisioned for the group) multiplied by the number of waiting calls, divided by the number of active valid group members. If the result is greater than the Call Queued timer provisioned for the group, the new call will immediately be redirected to an overflow (if configured) or rerouting destination. A member is considered active when it is

- In Service

- Not in DND

- Not in Make Busy

- Present

- No Reseize Timer running

- Unanswered calls - Calls unanswered within a specified period are sent to the group's designated overflow destination, if provisioned; otherwise, they go to the call rerouting destination. See Timer Interactions for details.

- When calls to a Ring Group triggers an overflow or reroute operation and an overflow destination has been programmed against the Ring Group, the caller is forwarded to the programmed destination. If no overflow exists, but rerouting is programmed, then the system checks the following in the order listed:

- The system first checks whether "This" is programmed under either "Busy/DND" or "No Answer". If yes, then the caller is forwarded to the programmed destination.

- The system then checks whether "Last" is programmed under either "Busy/DND" or "No Answer". If yes, then the system proceeds to check the Second Alternative Routing form. If the corresponding entry in the form contains any heading not set to "Normal", then the caller is forwarded to the programmed destination.

- While in a queue, the caller can listen to as many as two announcements provisioned through the Call Coverage Services form and played at predefined intervals. The last played recording can be repeated for as long as the caller is queued. Between the announcements, the system's Music on Hold (MOH) is played. See Group Announcements for details.

- Member phones (local or remote) with large displays show both the ring group information and the caller's name and number when the group is ringing. Small-display phones show either the ring group information OR the caller name/number, depending on the COS option "Display ANI/ISDN Calling Number Only" (see Programming). When the call is answered, the caller's name and/or number are displayed on the member's set.

NOTES

- For incoming Alpha Tagging of the caller to the ring group, the Alpha Tag System Option must be enabled and the Alpha Tag Telephone Directory name must be programmed (or shared) on the ring group remote member's controller.

- If the "Name Suppression on Outgoing Trunk Calls" option is enabled on the caller's COS, only the caller's number will be provided to the remote member.

- If the "Suppress Delivery of Caller ID Display between Sets" option is enabled on the caller's COS, "Private" will be displayed on the remote member's set. Note that the System Option "Send Traveling Class Marks" on the caller's controller is not required to suppress the caller's ID on the Ring Group remote member's display.

- The ring group's name and/or number are transported only over IP, Digital DPNSS or XNET trunks.

IMPORTANT: It is strongly recommended to use DPNSS trunks (IP, XNET, Digital DPNSS) to access Ring Group remote members. If non-DPNSS trunks are used, features that rely on DPNSS, such as override forwarding, will not function.

## Conditions and Feature Interactions

- For resilient ring groups that contain RDN members, an SDS synchronization from the primary controller is required after the upgrade to Mitel MiVoice Business Release 7.0 or higher. Otherwise, the number of remote member's on the ring group's primary and secondary controller may be different.

- The behavior of a resilient ring group is different from a non-resilient ring group.

- When a call comes to a Ring Group that supports the use of multi-colored LED functionality (to indicate the activity status of calls), the line key LED indicator will flash, and then extinguish on the other members appearances when the call is answered.

- Users cannot place callbacks or camp on to a ring group.

- Messaging Callbacks to a ring group are allowed if the first member is local.

- Ring Group capacities are as follows:

  Specification | Maximum
  Maximum number of ring groups | 2000 on server-based MiVoice Business for Industry Standard Server, MiVoice Business Virtual MiVoice Business platforms; 176 on all other platforms.
  Maximum number of members per group | 64 on server-based MiVoice Business for Industry Standard Server, MiVoice Business Virtual MiVoice Business platforms; 32 on all other platforms
  Maximum number of ring groups in which a device can be programmed | unlimited (for MiVoice Business Release 7.0 and up)
  Maximum number of simultaneously ringing members Single-line IP Sets Multiline appearances | 172 200 (see Note)
  Maximum number of calls that can be queued to any or all ring groups | 270 on server-based MXe Server, MiVoice Business for Industry Standard Server, MiVoice Business Virtual MiVoice Business platforms; 84 on all other platforms.

NOTE: The system can ring a maximum of 80 broadcast group
A directory number programmed to appear on multiple devices constitutes a broadcast group. There are two types of broadcast groups: Non-Prime Line and Prime Line. A Non-Prime Line group is a directory number programmed on one or more devices that is not the prime line on any device. A Prime Line group is a directory number programmed on button 0 of a phone. Server-based variants of MiVoice Business that use x86 processors, MiVoice Business for Industry Standard Servers MCD-ISS), Multi-instance MiVoice Business, and Virtual MiVoice Business, up to 250 appearances of the directory number can appear on one or more devices. For all other 3300 ICP/MiVoice Business call control platforms, up to 32 appearances of the directory number may appear on one or more devices.'s in unison. The maximum number of appearances in all 80 groups that it can ring is 172. Of the 172, up to 80 single-line appearances can be rung with the remaining appearances being multiline sets. Devices in excess of these limits will not ring. Error logs may also be generated during the call.

- The following directory numbers can be programmed as a ring group's overflow destination:

- station DNs

- broadcast group DNs

- attendant console DNs

- system speed call number

- hunt group DN

- ring group pilot DN

NOTE: The system does not check for invalid destinations.

- The following Call Coverage Services can be assigned to a ring group: Announcements, Direct Transfer to Voice Mail and Post Call Destination.

NOTE: When a call to a ring group is terminated by the group's member, the member's - not the group's - call coverage number is used to identify the post call destination.

- Ring group calls that go to an overflow point will follow call forwarding but not system rerouting programmed for the overflow point.

- When all group members are unavailable, calls are immediately redirected to an overflow or rerouting destination. If no overflow or reroute destination is programmed, then any provisioned exception handling is applied.

NOTE: When all members are Out Of Service, the immediate overflow is applied only if all members are local non-resilient. If there are any RDN or resilient members in that group, callers will be placed in the ringing queue, then the waiting queue, and the overflow will not take place until the timer expires.

- Call handling when the overflow or rerouting destination is unavailable (or not programmed) depends on the state of the call:

- If ring group member(s) are ringing, the call continues to ring until the caller hangs up or a member answers, or until the applicable COS
  Class of Service ringing timer expires.

- if the call is queued to a ring group, the call remains queued until the caller hangs up, member(s) start to ring, or a timer (Call Queued, caller's Ringing timer, Call Overflow) expires—whichever happens first.

- Calls transferred to a ring group that go unanswered either recall back to the transferring party or go to the group's overflow or rerouting destination. The timer that expires first— the caller's Recall timer or the ring group's Call Overflow timer— determines the behavior.

- Call Forwarding Always can be programmed against a ring group pilot number to forward group call anywhere within the DPNSS network. Set-up is done using Forwarding Profile form or from a set or console using the Call Forwarding - Follow Me - Third Party FAC. Other types of forwarding are not supported.

- Call forwarding on a ring group pilot number takes precedence over both overflow handling and call rerouting.

- A ring group can be a call forward or reroute destination.

- Call forwarding or reroute programming against ring group members is ignored for ring group calls.

- Calls forwarded or rerouted to a Ring Group displays the Call Forwarding/Rerouting information instead of Ring Group information on a members display while ringing if the Ring Group’s COS Prefer Call Forwarding/Rerouting Information is enabled.

NOTE: The following privacy features are not supported when a call is forwarded to a remote group member: Telephone Directory "Privacy" option, COS option "Name Suppression on outgoing trunk calls", and COS option "Suppress Delivery of Caller ID Display between Sets". The forwarding party number and, for the 5140 and 5240 sets, the name are displayed on the remote member's set, even if these options are enabled on the forwarding party. This behavior does not apply to calls forwarded to local members of a ring group.

- Phones that support the Call History application (5x30 IP Phone and 5x40 IP Phone) accumulate logs for ALL ring group calls offered to the device. To avoid this, program a non-prime line appearance on the phone, and then program the non-prime line to the ring group. The following scenarios will generate missed call logs on devices that support the Call History:

- ring group caller abandons (hangs-up)

- Ring All group caller calls the phone and is answered by another member

NOTE: Missed call logs will not be generated if an RDN is programmed as the prime member of a ring group. It is recommended that you do not program an RDN as the prime member if the Call History is required for the ring group.

- RDN members programmed as the prime member of a ring group do not support the message waiting indicator (MWI) lamp activation and deactivation. It is recommended that you do not program an RDN as the prime member if the MWI is required for the ring group.

- When there are calls ringing or queued to a ring group, the first member to become available is offered the oldest ringing or waiting call. If a member belongs to more than one group when it becomes available, it will get the call waiting longest of all groups.

- If remote and local members answer a call at the same time, the local member will most likely be connected to the caller due to latency on the remote member.

- Calls queued to a ring group and calls ringing a ring group will not survive a failover. However, queued and ringing calls to a ring group may survive a failback.

- Calls can be parked to a ring group pilot number. Parked calls do not ring the members of a ring group.

- SIP devices capable of Call Reject and are local or remote members of a Ring Group can reject a Ring Group call. The Call Reject will be ignored from the forwarding operation, the SIP device performing the reject will stop ringing, but the caller will continue to either ring all available members or the next available member of the group depending on the ring mode. The SIP device is removed from the list of ringing members for the call in progress but is available for new calls to the Ring Group.

- Ring groups are not supported by the Group Administration tool.

- Ring Groups can function as answering points for emergency calls and trigger notifications on Mitel Emergency Response Adviser. However, they cannot belong to an emergency type hunt group.

- Ring group's RDN members can be resilient based on their primary and secondary controller.

- When a ring group fails over to its secondary controller, that controller routes calls to the RDN member based on the member's resiliency.

- If a resilient RDN group member fails over to its secondary controller that is also the ring group's controller, then no remote routing will be applied; calls to that RDN member will be routed on the ring group's controller.

- If a resilient ring group member is active on the secondary controller, it can be reached through the ring group, even if the ring group is not active on the secondary controller.

- The following conditions and feature interactions apply if the Last Group Member Routing (LGMR) feature is enabled for a ring group:

- The feature supports a maximum of 20 digits for the CgPN or ANI(Automatic Number Identification).

- The feature data(CgPN or ANI of the caller, ring group to which the call was made, and the ring group member's number that answered the call) is cleared on a system restart.

- The feature data(CgPN or ANI of the caller, ring group to which the call was made, and the ring group member's number that answered the call) for the CgPN or ANI(Automatic Number Identification) is cleared when Last Group Member Routing - Caller Callback Time expires.

- The Last Group Member Routing (LGMR) feature data is not shared with the ring group on the secondary controller.

- If a ring group member associated with a feature data(CgPN or ANI of the caller, ring group to which the call was made, and the ring group member's number that answered the call) is deleted from the ring group, then the call is routed to the next available ring group member, and the feature data(CgPN or ANI of the caller, ring group to which the call was made, and the ring group member's number that answered the call) for the CgPN or ANI(Automatic Number Identification) is updated with the new ring group member's number.

- If a ring group associated with a feature data(CgPN or ANI of the caller, ring group to which the call was made, and the ring group member's number that answered the call) is deleted, then the feature data(CgPN or ANI of the caller, ring group to which the call was made, and the ring group member's number that answered the call) for that ring group is deleted.

- The feature supports both internal and external numbers, provided the numbers have CgPN or ANI(Automatic Number Identification).

- If the caller is an External Hot Desk User (EHDU), then the feature uses the EHDU's system DN as the CgPN or ANI(Automatic Number Identification) for the feature data(CgPN or ANI of the caller, ring group to which the call was made, and the ring group member's number that answered the call).

- If the caller is a Personal Ring Group (PRG) or a Hotel suite member, then the feature uses the PRG prime or hotel suite pilot number as the CgPN or ANI(Automatic Number Identification) for the feature data(CgPN or ANI of the caller, ring group to which the call was made, and the ring group member's number that answered the call).

- The feature is not applied to private numbers.

- The feature is applied to calls that are forwarded to a ring group that has the Last Group Member Routing (LGMR) feature enabled. The feature uses the original caller's CgPN or ANI(Automatic Number Identification) for the feature data(CgPN or ANI of the caller, ring group to which the call was made, and the ring group member's number that answered the call), not the transferred party's number.

- If you want the system to record soft held party's number in the feature data(CgPN or ANI of the caller, ring group to which the call was made, and the ring group member's number that answered the call), then enable the Display Held Call ID on Transfer COS for the transferring party.

- When an unsupervised transfer is made to a ring group, then the feature uses the transferred party's number for the feature data(CgPN or ANI of the caller, ring group to which the call was made, and the ring group member's number that answered the call).

- When a supervised transferred is made to a ring group, then the feature updates the feature data(CgPN or ANI of the caller, ring group to which the call was made, and the ring group member's number that answered the call) with the transferred party's number.

- If a ring group member is busy or inactive, or an attempted seize fails, the call is routed to the next available ring group member. The feature data(CgPN or ANI of the caller, ring group to which the call was made, and the ring group member's number that answered the call) for the CgPN or ANI(Automatic Number Identification) is updated with the new ring group member's number.

- If a ring group is busy or an attempted seize of its members fail, and the rest of group members are busy, then the call is queued and the Call Queued Timer - Minutes or Call Queued Timer - Seconds is started. The feature data(CgPN or ANI of the caller, ring group to which the call was made, and the ring group member's number that answered the call) for the call is not updated. If the call is answered after being in the queue, then the feature data(CgPN or ANI of the caller, ring group to which the call was made, and the ring group member's number that answered the call) is updated with the answering ring group member.

- If a call to a ring group is not answered or cancelled before the Call Ringer Timer expires, then the system routes the call to the configured overflow point or reroute destination. If an overflow point or reroute destination is not configured, then the call continues to ring until the call is answered, or hung by the caller, or the Call Ringer Timer expires. If the call is queued to the ring group, then the call remains in the queue until the caller hangs up, or the call is connected to a group member, or the Call Queued Timer - Minutes or Call Queued Timer - Seconds expires. If the call is not answered by a ring group member, the feature data(CgPN or ANI of the caller, ring group to which the call was made, and the ring group member's number that answered the call) for the call is not saved.

- If a caller is on an active call with an ring group member, and then transfers a previously held call to a ring group member, the feature data(CgPN or ANI of the caller, ring group to which the call was made, and the ring group member's number that answered the call) is updated with the held call's number.

- If a caller places an active call with an ring group member on hold, and then calls another party and transfers the call to the ring group member, then the feature data(CgPN or ANI of the caller, ring group to which the call was made, and the ring group member's number that answered the call) is updated with the transferred party's number.

- If a caller in on active call with an ring group member, sets up a conference call with another party, then the feature data(CgPN or ANI of the caller, ring group to which the call was made, and the ring group member's number that answered the call) uses the original caller's number. If the original caller leaves the conference call, then the feature data(CgPN or ANI of the caller, ring group to which the call was made, and the ring group member's number that answered the call) is updated with the new caller's number. If the ring group member leaves the conference call, the feature data uses the original caller's number.

- If an ring group member on an active call with a caller, sets up a conference call with another party, then the feature data(CgPN or ANI of the caller, ring group to which the call was made, and the ring group member's number that answered the call) uses the original caller's number. If the ring group member, or the original caller, or the third party leaves the conference call, then the feature data(CgPN or ANI of the caller, ring group to which the call was made, and the ring group member's number that answered the call) is not updated, that is, uses the original caller's number.

- If the Route optimization feature is enabled on the Ring Group cluster controllers, route optimization will be applied when

- a Ring Group call is answered by a remote member, then transferred to another party on a different controller, and then answered;

- a Ring Group call is answered by a remote member, then transferred to another party on the same controller as the caller, and then answered;

- an external DPNSS call is transferred to a Ring Group on a different controller and answered by the remote member;

- an external DPNSS call is transferred to a Ring Group on a different controller and answered by the remote member who is on the same controller as the caller.

### Ring Group Timer Interactions

Depending on the scenario, the following timers may be applied to unanswered ring group calls.

Form | Timer | Description | Notes
Ring Groups | Call Ringing | The length of time a call rings a ring group member before being redirected away from the ring group. | Strongly recommended to be smaller than either system "Call Rerouting Timer" or COS option "Answer Plus System Reroute Timer". In the worst case scenario, a call rings for the duration of both timers before being redirected to an overflow or rerouting destination. See the Examples below for details.
Call Queued | The length of time a caller is waiting in a queue before being redirected to an overflow (if configured) or 1st-alternative rerouting destination.
System Options | Call Rerouting | The length of time a call rings a station before being rerouted to the station's 2nd alternative number. | Strongly recommended to be greater than any ring group timer (Call Ringing and Call Queued) and the CFNA timer.
Class of Service (COS) Options | Call Forward - No Answer (CFNA) of the Overflow station | The length of time a call rings a station before being rerouted to the 1st-alternative rerouting destination. This timer is reset each time a call is forwarded. | Strongly recommended to be smaller than either Call Rerouting (System Options) or COS Answer Plus System Reroute timer.
Answer Plus System Reroute of a Ring Group | The length of time a call rings a station before being rerouted from the 1st to the 2nd-alternative rerouting destination. | Strongly recommended to be greater than any ring group timer (Call Ringing or Call Queued) and the CFNA timer. If configured, it overrides the system Call Rerouting Timer.
Ringing Timer of the caller | The length of time a station rings another station. | Will determine the length of time an internal call rings the last configured overflow or rerouting destination. The default values is 180 s. This timer is reset each time a call is redirected to the next alternative destination. NOTE: For external calls, the last destination will ring until the caller ends the call.

#### Example Scenario 1: Overflow, 1st, and 2nd Call Rerouting Alternative destinations are configured

- The following timers are programmed for the Ring Group:

- Call Ringing: 30 s

- Call Queued: 30 s

- COS option Answer Plus System Reroute: 0 -- therefore, the system Call Rerouting Timer will be used

- System Call Rerouting Timer: 90 s

In this scenario, it is recommended that the system Call Rerouting Timer for the ring group be configured based on the following formula:

Ringing Timer + Queued Timer + CFNA Timer + some additional time for the 1st Alternative destination to answer the call before rerouting to the 2nd Alternative.

In this example: 30 s + 30 s + 17 s +13 s = 90 s

- COS option CFNA for the Overflow destination: 17 s

- COS option Ringing Timer for the caller is: 180 s.

Call Processing Algorithm

- An incoming call immediately rings a ring group member. Two timers are activated: ring group Call Ringing Timer and system Call Rerouting Timer.

- Ring group member rings for 30 s (Call Ringing Timer) and if not answered, the call is redirected to the Overflow destination and the CFNA timer starts (17 s).

- When the CFNA timer expires, the call is redirected to the 1st Alternative destination, which rings for the duration of the system Call Rerouting Timer minus the ring group Call Ringing and the CFNA timers:

90 - 30 - 17 = 43s.

- After 43 seconds (when the system Call Rerouting Timer expires), the 1st Alternative destination stops ringing and the call is redirected to the 2nd Alternative destination.

For internal calls, the 2nd Alternative rings until the COS option Ringing Timer for the caller expires (default 180 s).

For external calls, the 2nd Alternative rings until the caller clears the call.

The following diagram illustrates the above scenario.

Ring Group Member Rings | Overflow Destination Rings | 1st Alternative Destination Rings | 2nd Alternative Destination Rings
0 s 30 s | 17 s |  |
|-----------------------------------------> | ------------------------------------> |  |
(Ring Group Call Ringing Timer) | (CFNA Timer) | 43 s | 180 s (internal call)
|  | (90 - 30 - 17)) | (COS option Ringing Timer)
|--------------------------------------------------------------------------------------------------------------------------------> | -------------------------------------------->
(System Call Rerouting Timer: 90 s) |

Worst Case Scenario

- An incoming call is placed in queue (all ring group members are busy). Two timers are activated: Called Queued Timer (30 s) and system Call Rerouting Timer (90 s).

- Just before the Called Queued Timer expires, a group member becomes available and starts ringing. The Call Ringing Timer (30 s) is activated.

- The ring group member does not answer before the Ringing Timer expires and the call is rerouted to the Overflow destination. The CFNA timer (17 s) starts.

- When the CFNA timer expires, the call is redirected to the 1st Alternative destination, which rings for the duration of: system Call Rerouting Timer minus the ring group Call Queued, Call Ringing and CFNA timers:

90 - 30 - 30 - 17 = 13 s.

- After 13 seconds, the 1st Alternative destination stops ringing and the call is redirected to the 2nd Alternative destination.

For internal calls, the 2nd Alternative rings until the caller's COS option Ringing Timer expires (default 180 s).

For external calls, the 2nd Alternative rings until the caller clears the call.

In this scenario, an internal call rings for the total of 270 seconds: 30 + 30 + 17 + 13 + 180. An external call rings until the caller ends the call.

#### Example Scenario 2: No Overflow, only 1st and 2nd Call Rerouting Alternative destinations are configured

- The following timers are programmed for the Ring Group:

- Call Ringing: 30 s

- Call Queued: 30 s

- COS option Answer Plus System Reroute: 0 -- therefore, the system Call Rerouting Timer will be used

- System Call Rerouting Timer: 75 s

In this scenario, it is recommended that the system Call Rerouting Timer for the ring group be configured based on the following formula:

Ringing Timer + Queued Timer + some additional time for the 1st Alternative Destination to answer the call before rerouting to the 2nd Alternative.

In this example: 30 s + 30 s +15 s = 75 s

- COS option CFNA for the Overflow destination: 17 s; however, this value will be ignored since the overflow is not programmed

- COS option Ringing Timer for the caller is: 180 s.

Call Processing Algorithm

- An incoming call immediately rings a ring group member. Two timers are activated: ring group Call Ringing Timer and system Call Rerouting Timer.

- Ring group member rings for 30 s (Call Ringing Timer) and if not answered, the call is redirected to the 1st Alternative destination, which rings for the duration of the system Call Rerouting Timer minus the ring group Call Ringing Timer: 75 - 30 = 45 s.

- After 45 seconds (when the system Call Rerouting Timer expires), the 1st Alternative destination stops ringing and the call is redirected to the 2nd Alternative destination.

For internal calls, the 2nd Alternative rings until the caller's COS option Ringing Timer expires (default 180 s).

For external calls, the 2nd Alternative rings until the caller clears the call.

The following diagram illustrates the above scenario.

Ring Group Member Rings | 1st Alternative Destination Rings | 2nd Alternative Destination Rings
0 s 30 s |  |
|-----------------------------------------> |  |
(Ring Group Call Ringing Timer) | 45 s | 180 s (internal call)
| (75 - 30) | (COS option Ringing Timer)
|------------------------------------------------------------------------------------------> | -------------------------------------------->
(System Call Rerouting Timer: 75 s) |

Worst Case Scenario

- An incoming call is placed in queue (all ring group members are busy). Two timers are activated: Called Queued Timer (30 s) and system Call Rerouting Timer (75 s).

- Just before the Called Queued Timer expires, a group member becomes available and starts ringing. The Call Ringing Timer (30 s) is activated.

- The ring group member does not answer before the Ringing Timer expires and the call is rerouted to the 1st Alternative destination, which rings for the duration of: system Call Rerouting Timer minus the ring group Call Queued and Call Ringing timers: 75 - 30 - 30 = 15 s.

- After 15 seconds, the 1st Alternative destination stops ringing and the call is redirected to the 2nd Alternative destination.

For internal calls, the 2nd Alternative rings until the caller's COS option Ringing Timer expires (default 180 s).

For external calls, the 2nd Alternative rings until the caller clears the call.

In this scenario, an internal call rings for the total of 255 seconds: 30 + 30 + 15 + 180. An external call rings until the caller ends the call.

## Programming

1. Ring Groups form

- Enter the Pilot Number, Ring Group Mode, Call Coverage Service index, Overflow destination, and other information as required.

- Enter the Directory Number of each member in the Ring Group Members section of the form.

- (Optional) To enable the Last Group Member Routing (LGMR) feature, enter the duration (range 10 to 480 minutes) in the Last Group Member Routing - Caller Callback Time field.

- Enter the duration (range 10 to 180 seconds) in the Last Group Member Routing - Wait for Member Time field.

NOTES

- Members (except for Ring All groups) are hunted in the order in which they are entered in the group.

- Remote members of terminal and terminal cascade ring groups should be programmed at the end of the group to avoid excessive trunk resources being used and Reseize Timerss continually running for those members due to the hunting mode.

2. Call Coverage Services form

- Under the Announcements tab, configure one or two recordings to be played to the caller while queued to the group. If required, enable and configure the Repeat Last Recording option.

- Enter the voice mail destination directory number for the the Direct Transfer to Voice Mail feature. (optional)

- Enter the Post Call Destination directory number. (optional)

3. (Optional) Call Rerouting form

- Configure the call rerouting destinations for the ring group.

4. Class of Service Options form

- For small-display sets (e.g., 5020, 5220, 5224, 5010, 5207, 5212, 5312, and 5215, 5304, 5324 IP Phones), set the Display ANI/ISDN Calling Number Only option to display either the ring group or calling party name and number when calls from ring group are ringing.

- To display forward from information on the members' phone display when a call is forwarded to a ring group, set the Prefer Call Forwarding/Rerouting Information option to Yes in the COS assigned to the ring group.

- To record soft held party's number in the Last Group Member Routing (LGMR) feature data(CgPN or ANI of the caller, ring group to which the call was made, and the ring group member's number that answered the call), set the Display Held Call ID on Transfer option to Yes for the transferring party.

## Device Support

- The following types of numbers or devices can be programmed as a ring group member:

- Any type of broadcast group
  A directory number programmed to appear on multiple devices constitutes a broadcast group. There are two types of broadcast groups: Non-Prime Line and Prime Line. A Non-Prime Line group is a directory number programmed on one or more devices that is not the prime line on any device. A Prime Line group is a directory number programmed on button 0 of a phone. Server-based variants of MiVoice Business that use x86 processors, MiVoice Business for Industry Standard Servers MCD-ISS), Multi-instance MiVoice Business, and Virtual MiVoice Business, up to 250 appearances of the directory number can appear on one or more devices. For all other 3300 ICP/MiVoice Business call control platforms, up to 32 appearances of the directory number may appear on one or more devices.. This includes:

- - multiline set prime number

  - non-prime line numbers

  - key system numbers

  - multicall numbers

- single line sets

- a night bell

- Personal Ring Groups (PRG)

- Multi-device User Groups (MdUG)

- SIP endpoints

- internal and external Hot Desk users

- Remote Directory Numbers

- The following directory numbers are invalid as a member of a ring group and will be blocked at call processing time (some will be blocked at programming time):

- extensions with the "voice mail port" COS
  Class of Service option

- extensions with the "Recorded Announcement Device" COS
  Class of Service option.

- attendant consoles and console LDN numbers

- Hunt group, Agent group, Path, Ring Group, Suite and Linked Suite pilot numbers

- ACD Agent IDs and ACD set DNs

- ARS digits

- a pilot number of another ring group

- MdUG non-prime member

- page groups

Ring Groups functioning as answering points for ER Adviser emergency calls cannot have the following DNs as members:

- extensions with a Multi-Device
  This Service Level indicates that the directory number (DN) is assigned to a user that has only basic telephony functionality (e.g., emergency or attendant calls) until programmed as a member of a Multi-Device user group or suite. The DN does not use an IP User License. However, the group or suite has a Multi-device Users or Multi-device Suites license which one person can use at a time in order to receive full telephony service. service level that is NOT in an Multi-device User Group.

- extensions with an IP Device Only
  This Service Level indicates that the directory number (DN) is assigned to an unlicensed device that has only basic telephony functionality (emergency or attendant calls). The device becomes functional when a hot desk user or hot desk ACD agent logs into it. service level.

NOTE: The system does not prevent you from programming the above numbers as remote members of a ring group. However, those invalid members will be blocked and marked absent at call processing time (a log will be generated).

## Operation

None

Related Topics

- Hunt Groups

- Personal Ring Groups