# Attendant Recall

## Description

Attendant Recall automatically alerts the attendant when a trunk call has been extended to an idle station (including Hunt, Ring, and Pickup groups) and not answered within a specified time-out period, or when a call on Hold at the console has not been answered within a selected time.

By default, unanswered stations stop ringing when the no-answer recall occurs— that is, when the No Answer Recall Timer in the COS
Class of Service assigned to the incoming trunk expires. Alternatively, the system can be programmed to continue ringing the station until the attendant answers the recall or the station is answered.

In an attendant group where the DN of each attendant console appears as a softkey on the other consoles, recalls are presented only to attendants from the same tenant as the attendant who originally handled the call. By enabling "Recall If Transferred to Original Call Destination" in the attendant Class of Service, recalls are presented only to the attendant who originally handled the call. This behaviour applies to DID calls to extensions that are rerouted to attendants (or sets) using Call Rerouting.

## Conditions and Feature Interactions

Attendant Recall does not apply when the console is in night service mode unless that console is the night answer point and the console attendant is set to Operator Present.

## Programming

- Class of Service Options form

- Set the Call Hold Timer (10-600 s), Camp-on Recall Timer (0-180 s), and No Answer Recall Timer (0-45 s) in the COS of the incoming trunk. For cluster or network environments, ensure that the No Answer Recall Timer value on incoming PRI trunks is set higher than the same timer on IP trunks between switches. Otherwise, the console shows the route label in the name field instead of the Tel Dir name when a non-answered call from a remote switch recalls.

- The "Recall If Transferred to Original Call Destination COS" option requires the following additional programming to work in a cluster or network environment:

A) Cluster Programming

Normal cluster programming rules must be followed. In particular:

- Primary node IDs (PNIs) must either be left blank (not programmed) on all switches in a cluster or must be set to the same value on all switches in the cluster.

- The Cluster Elements form ( ) must be programmed consistently between all switches in the cluster. Each cluster element (switch) must have a unique value programmed. The Cluster Element ID digits must be unique for each switch in the cluster and the number of digits must be the same for all switches in the cluster

- The Cluster Element ID digits are used as ARS to select the route to the target switch.

B) Network Programming

The ARS to access a network switch must either use the Primary Node ID (PNI) digits or the Remote Node Leading Digits field must be programmed for the PNI in the ARS Node Identities form ( ) and those digits used as the ARS to route the call. Other ARS routing schemes are not supported by this feature.

If the remote switch is another vendor's switch, it must prepend the DN in OLI fields with the same routing digits that our switch uses to reach it. For example, if the DN on the remote switch is 1234 and our switch routes the call to the network switch as 9991234 then the other vendor's switch must provide 9991234 as the OLI in incoming ISRM/SSRM DPNSS messages.

- Enable option "Maintain Ringing Party During Recall" in the COS of the attendant to allow recalls to ring on both the console and the called extension until either answers the call. See Attendant Maintain Ringing Party During Recall for details.

## Device Support

All consoles

## Operation

#### 5540 IP Console

To handle a recall:

1. Select Recall or Answer

2. Do one of the following:

3. Press Redial Dest to redial the same destination

4. Dial a new destination, and then press Release.

5. Press Cancel to disconnect the Source party.

#### MiVoice Business Console

To handle a recall:

1. Select Recall or press Enter on the numeric keypad.

2. Do one of the following:

3. Press Redial Dest if the call want to continue waiting.

4. Dial another destination

5. Press the + key on the numeric keypad to disconnect the Source party.

6. Select the Voice Mail toolbar button to transfer the caller to the extension's voice mail box