Carrier compatibility: LAI has been tested with several major carriers. To find out if these capabilities work with your carrier, check with your account team for the most current
information. If testing has not been done to verify operation over the public networks involved with the preferred specific configuration, use of private ISDN trunking between the nodes should be assumed until successful testing has been completed.
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
Look-Ahead Interflow is enabled are treated as Look-Ahead Interflow call attempts.
ISDN Numbering - Public/
Unknown ●
Ext Len
● Ext Code
● CPN Prefix
Call Vector Complete a form for each Look-Ahead Interflow vector
Form Field
ACD contact center features
186 Avaya Call Center ACD Guide February 2006
A vector may route a call over an ISDN facility to a destination that is not a VDN. The sending communication server processes this call as a Look-Ahead Interflow call even though it is not.
ISDN processing at the receiving communication server causes the call to always be accepted.
However, the DNIS and any other information in the Look-Ahead Interflow information forwarded with the call are ignored.
Interim call handling before LAI is accepted by receiving communication server: Until the look-ahead attempt is accepted by the receiving communication server, the caller continues to hear any feedback applied by the sending communication server vector and will remain in any split/skill queues.
Call handling with Route-to number or Route-to digits handling with coverage : Route-to number with coverage y or route-to digits with coverage y commands never result in a
Look-Ahead Interflow call attempt. The sending end assumes the call is always going to be accepted. This command always completes the call. Moreover, the command should not be used if the vector at the receiving communication server might deny the call, since the caller in this case would be given a busy signal or would be disconnected. Use this command with coverage y only when you want unconditional interflow (with Look-Ahead Interflow active) and the terminating communication server is set up accordingly.
Continuity during call transfer between communication servers: Audible feedback may be provided to the caller before interflow is attempted. Therefore, another audible feedback from the receiving communication server may confuse the caller. For example, a caller hearing ringback on the sending communication server may 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 option on the Trunk Group form set to its default y. Existing LAI applications will 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 (the conditional applies only to calls in queue). Interactions
AAR/ARS: ISDN facilities used to provide Look-Ahead Interflow 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 (unless they’re overridden with newly collected digits) on the telephone display.
Attendant Control of Trunk Group Access: Calls will not route over a trunk with Attendant Control of Trunk Group Access set.
Look-Ahead Interflow
Authorization Codes: Authorization Codes must not be 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 considered an invalid destination (rejected for Look-Ahead Interflow or not available for standard interflow) without the application of recall dial tone.
BCMS: BCMS does not log LAI attempts, nor does it 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 Look-Ahead Interflow attempts.
If a local (on-communication server) call to a VDN generates a Look-Ahead Interflow call attempt that is accepted, and answer supervision is returned from the receiving communication server, then one Outgoing Call CDR record is generated with the originating extension as the calling number.
If an incoming (off-communication server) call to a VDN generates a Look-Ahead Interflow call attempt that is accepted, and no answer supervision is returned from the receiving
communication server, then 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 (off-communication server) call to a VDN generates a Look-Ahead Interflow call attempt that is accepted, and answer supervision is returned from the receiving communication server, then 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 Look-Ahead Interflow call is treated like any other incoming vector call.
If answer supervision is returned by the vector, and the call is never terminated to another destination, then the VDN extension is recorded as the called number in the CDR record.
If the call terminates to a hunt group, then the VDN, hunt group, or agent extension is recorded as the called number. If the Record VDN in Record field of the Feature Related System Parameters is y, then the VDN extension overrides the Call to Hunt Group - Record administration option for vector calls.
Call Prompting: Digits collected at the sending communication server, no matter how they are collected (caller-entered, ASAI provided, CINFO provided, etc.) are forwarded with interflowed calls and available at the remote communication server using information forwarding. For more information, see Information Forwardingon page 167.
ACD contact center features
188 Avaya Call Center ACD Guide February 2006
Note:
Note: Dial-ahead digits are not forwarded with the call. There is a maximum of 16
forwarded digits.
Centralized Attendant Service: A centralized attendant can be a Look-Ahead Interflow destination.
Display - 27 Character: The VDN name (part of the LAI information forwarded with calls) can be up to 15 characters long. Any characters over this limit will be dropped.
Distributed Networking - Manufacturers Specific Information (MSI): LAI (whether enhanced or not) may 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: The adjunct routing capabilities of vectoring can be used at the sending communication server to determine if a call should be interflowed. Adjunct routing at the receiving communication server can be used 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 (for example, SDN) ISDN-BRI and -PRI networks that meet minimum network requirements.
The sending of a Look-Ahead Interflow 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 Look-Ahead Interflow route-to number vector step, BSR queue-to best vector step, and the Adjunct Routing vector steps.
The ability to track a measured ACD call after a path replacement has taken place is available for CMS versions r3v9ai.o or later. Starting with the r3v12ba.x release, CMS reports a path replacement as a rename operation rather than a path replacement. The rename operation properly reports scenarios where a path replacement takes place from a measured to an unmeasured trunk facility. Avaya recommends that you upgrade CMS to r3v12a.x or later and administer all trunks associated with path replacement as measured by CMS to ensure better CMS tracking of path-replaced calls.
Look-Ahead Interflow
QSIG: LAI and information forwarding function over QSIG trunk facilities if the remote locations are Avaya communication servers. You may get LAI call control functionality with other vendors if an Avaya communication server is the starting point.
Redirect on No Answer (RONA): Calls redirected to a VDN by RONA can be subsequently 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 may 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.
ACD contact center features
190 Avaya Call Center ACD Guide February 2006