# MSDN Release Link Trunk Operation

### Incoming Calls

When an attendant answers an incoming RLT call, the IP Console application(MiVoice Business Console) displays the incoming call information. Selection of the Non-RLT softkey changes the softkey display. The source (SRC) window display remains unchanged.

Selecting the Non-RLT softkey will have the following effect:

- The incoming RLT will not be re-used to extend the call.

- Certain features, such as SET SERIAL CALL, are made available. These features can only be selected if the incoming RLT is not reused.

- The RLT softkey replaces the Non-RLT softkey.

Selection of the RLT softkey will change the softkey display. The source (SRC) window display remains unchanged.

Selecting the RLT softkey will have the following effect:

- The incoming RLT will be reused to extend the call.

- Certain features, such as SET SERIAL CALL, are not available.

- The Non-RLT softkey replaces the RLT softkey.

The attendant extends the call by dialing the digits and pressing the RELEASE hard key or the + key on the numeric keypad (MiVoice Business Console). Once the first digit is dialed the softkey appearances go out (see figure). The SRC and DEST window displays are cleared when the RELEASE/+ key is pressed.

### Recalls

The attendant may be recalled after extending a call on an RLT. The reason given is either "Recall - Busy" or "Recall - No Answer". If an extended call has been camped-on to a busy destination for a predetermined time and not retrieved, then the call is returned to the attendant with the reason "Recall - Busy". "Recall - No Answer" is displayed for all other types of transfer failures, such as the destination in Do Not Disturb.

### Public Switch Telephone Network (PSTN) Barring

The Release Link Trunk feature interacts with PSTN barring when an enquiry call, dialed by the attendant, originates from a transit System. A description of the following terms is provided to facilitate explanation:

- Caller PBX - If an attendant is connected to a caller via an incoming RLT, then the system where the call originated is the caller system.

- Transit PBX - This is the intermediate system that processes a call from the caller system and sends it to the destination system. If a system does not exist between the caller system and the destination system, then a transit system is not involved for that call.

- Attendant PBX - This is the system that has the centralized attendant in a system network that supports centralized attendant service.

- RLT Gateway PBX - This is the system from which the RLT enquiry call originates. The system can be either a transit system or a Caller PBX.

- RLT Enquiry Call - This is an enquiry call that is dialed by the attendant on the attendant PBX, but the call actually originates on the RLT Gateway PBX.

Various recall timers are maintained by systems involved in an RLT call. In a station-to-attendant network call, the recall timer of the caller system is controlled by the DPNSS redirection feature. The RLT feature controls the recall timer of the RLT gateway system. If the timers expire at the same time they may both try to recall the attendant simultaneously. To avoid this interaction, the DPNSS redirection feature can be disabled, or the timer of the caller system can be set to a value much higher than that of the RLT gateway PBX.

Related Topics

- MSDN Release Link Trunk

- MSDN Release Link Trunk Conditions

- MSDN Release Link Trunk Programming