Carrier compatibility

LAI works with several major carriers. To find out if the LAI capabilities work with your carrier, check with your account team for current information. If testing has not been done to verify operation over the public networks involved with the preferred specific configuration, use private ISDN trunking between the nodes until successful testing is complete.

ISDN routing with LAI enabled: All calls routed over ISDN facilities by a route-to number with cov n or route-to digits with cov n vector command on a communication server where LAI is enabled are treated as LAI call attempts.

A vector can route a call over an ISDN facility to a destination that is not a VDN. The sending communication server processes this call as an LAI call even if the call is not an LAI call. ISDN processing at the receiving communication server causes the call to always be accepted. However, the DNIS and any other information in the LAI information forwarded with the call are ignored.

Interim call handling before LAI is accepted by receiving communication server: Until the LAI attempt is accepted by the receiving communication server, the caller continues to hear any feedback applied by the sending communication server vector and remains in any split or skill queue.

Call handling with Route-to number or Route-to digits handling with coverage

Route-to number with cov y or route-to digits with cov y commands does not result in an LAI call attempt. The commands always complete the call. Do not use the command if the vector at the receiving communication server can deny the call, since the caller in this case hears a busy signal. Use this command with coverage y only when you want unconditional interflow with LAI active and the terminating communication server is set up accordingly.

Continuity during call transfer between communication servers

Audible feedback can be provided to the caller before interflow is attempted. Therefore, another audible feedback from the receiving communication server can confuse the caller. For example, a caller hearing ringback on the sending communication server can be confused if music is applied suddenly when the call interflows to the receiving communication server.

Backward compatibility of LAI applications

For backward compatibility of LAI applications between Avaya communication servers, leave the Send Codeset 6/7 LAI IE field on the Trunk Group screen to the default y. Existing LAI applications continue to operate as before, even after you upgrade.

You can use enhanced LAI available in the communication server without any network or trunk administration changes, by adding the interflow-qpos conditional to original LAI vectors.

AAR/ARS

ISDN facilities used to provide LAI to a VDN on another communication server in a private network can use the AAR feature if private facilities are to be used for call routing.

Agent Telephone Display

If collected digits are forwarded with an interflowed call, the forwarded digits are displayed to the answering agent on the telephone display.

Attendant Control of Trunk Group Access

Calls do not route over a trunk with Attendant Control of Trunk Group Access set.

Authorization Codes

Authorization codes are not required for interflow routing. Assign a high enough FRL to the VDN so that the route desired for routing interflow calls can be used without requiring an authorization code entry. If a route choice is encountered that requires a higher FRL, the interflow is an invalid destination, rejected for LAI or not available for standard interflow, without the application of recall dial tone.

BCMS

Neither does BCMS log LAI attempts nor does BCMS report accumulated in-VDN time.

Call Detail Recording - Sending Server

No ineffective call attempt or outgoing call CDR records are generated for vector route-to commands that are unsuccessful including denied LAI attempts.

If a local call to a VDN generates an LAI call attempt that is accepted and answer supervision is returned from the receiving communication server, one outgoing call CDR record is generated with the originating extension as the calling number.

If an incoming call to a VDN generates an LAI call attempt that is accepted, and no answer supervision is returned from the receiving communication server, one incoming CDR record is generated. The VDN is the called number and the duration is from the time answer supervision was provided to the incoming trunk.

If an incoming call to a VDN generates an LAI call attempt that is accepted and answer supervision is returned from the receiving communication server, two incoming CDR records are generated:

• An incoming record with the VDN as the called number and the duration as the time since answer supervision was provided to the incoming trunk. This is generated if the call is initially answered in the sending communication server before interflow takes place.

• An outgoing record containing the incoming trunk information as the calling number and the dialed digits and the outgoing trunk information as the called number.

Call Detail Recording - Receiving Server

On the receiving communication server, an incoming LAI call is treated like any other incoming vector call.

If answer supervision is returned by the vector and the call does not terminate to another destination, the VDN extension is recorded as the called number in the CDR record.

If the call terminates to a hunt group, the VDN, hunt group, or agent extension is recorded as the called number. If the Record VDN in Record field on the Feature-Related System Parameters screen is y, the VDN extension overrides the Call to Hunt Group - Record field entry for vector calls.

Call Prompting

Digits collected at the sending Communication Manager, no matter how the digits are collected (caller-entered, ASAI provided, CINFO provided) are forwarded with interflowed calls and available at the remote Communication Manager using Information Forwarding.

Centralized Attendant Service

A centralized attendant can be an LAI destination.

VDN Name Display

The VDN name, part of the LAI information forwarded with calls, can be up to 27 characters long. Any characters over this limit is dropped. On Communication Manager, a VDN name can be administered with as many as 27 characters.

Distributed Networking - Manufacturers Specific Information (MSI)

LAI, whether enhanced or no, does not function with systems from other vendors unless that vendor develops a corresponding capability that works with the Avaya communication server.

Facilities Restriction Level and Traveling Class Marks

The FRL for interflow over ARS/AAR route choices is assigned to the original VDN used for the incoming call.

Incoming Call Management

You can use the adjunct routing capabilities of vectoring at the sending communication server to determine if a call must be interflowed. You can use the adjunct routing at the receiving communication server to tandem the call to a far-end communication server.

If the call terminates to a tandem trunk, two CDR records are generated:

• An incoming record with the VDN as the called number and the duration as the time since answer supervision was provided to the incoming trunk.

• An outgoing record containing the incoming trunk information as the calling number and the dialed digits and the outgoing trunk information as the called number.

Network Access

LAI operates over public, private, or virtual private networks. ISDN-BRI and -PRI networks that meet minimum network requirements.

The sending of an LAI codeset 6/7 information element is counted toward Message Associated User-to-User Information (MA-UUI) counts.

Path replacement for QSIG/DCS ISDN calls

For calls that are waiting in queue or in vector processing, even if the call is not connected to an answering user, path replacement using QSIG can be attempted to find a more optimal path for this call. This results in more efficient use of the trunk facilities.

The QSIG ISDN or DCS ISDN trunk path replacement operation can be triggered for ACD calls by the LAI route-to number vector step, BSR queue-to best vector step, and the adjunct routing vector steps.

QSIG

LAI and information forwarding function over QSIG trunk facilities if the remote locations are Avaya communication servers. You can get LAI call control functionality with other vendors if an Avaya communication server is the starting point.

RONA

Calls redirected to a VDN by RONA can subsequently be processed and routed by LAI applications.

Service Observing

You can observe a call in LAI processing using VDN observing throughout the life of the call as long as the call is still connected through the local communication server. All current restrictions on Service Observing still apply. Incoming calls can be service observed at the remote communication server.

Trunk-to-Trunk Transfer

Interflowed calls can be transferred by a receiving communication server to another trunk connection.

VDN Override

The name of the active VDN for a call is displayed at the remote answering agent.