AT&T 585-350-812 manual

Page 88

ASAI Script Builder Actions

(null string) is returned. If A_Event is reporting a route request (the Return Field returns a value of ‘R’), a string of length 0 (null value) is returned. The value returned can be up to 20 characters in length.

The “Calling Party Number” field stores up to 20 characters. If the A_Event action is successful, this field contains the calling party number. If the calling party num- ber is not known or the call was routed from a non-ISDN trunk, a string of length 0 (null value) is returned. If the value returned from the Other Call Id field is not 0, then the Calling Party Number returns the number of the original calling party.

The “Called Party Number” field stores the called party number. The value returned in the Called Party Number field can be up to 20 characters in length. If the Called Party Number is not known, a string of length 0 (null value) is returned. If the value returned from the Other Call Id field is not 0, then the Called Party Number returns the number that was originally dialed.

The “Switch Data” field stores up to 16 characters. If the switch prompts the caller for touch-tone digits, the digits are returned in the Switch Data field. If no digits are collected by the switch, a string of ength 0 (null value) is returned.

The “Trunk Group Id” field indicates whether the incoming call was routed from a non-ISDN trunk on the switch. If the call was not placed through a trunk the value returned is 0.

The “Call Id” field stores the Call Id (assigned by the switch) that identifies the incoming call. If the Call Id is not known, the value returned is 0. The “Other Call Id” field returns a number (assigned by the switch) that identifies the original call that was transferred. The script developer may use this field to associate subse- quent events that occur from a previous call. If the field is 0, then A_Event cannot relate this event with any other call. If the call is a new incoming call to a moni- tored domain, then the field is always 0. If it is a transfer call, the field value depends on the type of transfer that was completed. A consult transfer returns a non-zero value only when the transfer call is directed to a non-monitored domain. A blind transfer always returns a non-zero value. Refer to the information on agent-to-agent transfers in Chapter 2, "ASAI Application Planning and Design" for additional information.

The “LAI Display Info” field returns the Look Ahead Interflow (LAI) display informa- tion for the call. The value returned in this field depends on the call flow and whether or not the LAI feature (a PBX feature) is used. When the LAI feature is used to connect calls from one call center to another, this information can be used to determine which call center application was handling the caller on the originat- ing switch. The originating switch can be administered such that the LAI Display Info field will contain the originally dialed number the caller used at the originating switch. If the LAI feature is not used to connect calls from one switch to another, then a string of length 0 (null value) is returned.

6-6

Image 88
Contents Conversant VIS Adjunct Switch Application Interface Blank Contents Asai Administration Asai Script Builder Actions Vi Issue 1 October Asai Overview System Monitor Voice Channels Asai Voice Response ApplicationsPage Routing Applications Asai Routing Application route.picData Screen Delivery Applications Data Screen Delivery Applications gateway.pic Page Advantages Using the VIS Asai Feature Enhanced Customer ServiceReduced Cost of Doing Business Asai Overview Asai Application Planning Design Overview Asai Application Planning DesignVIS Script Design Asai Voice Script Design Page Routing Script Design Page Monitoring Script Design Page VIS-to-Agent Transfers Page Agent-to-Agent Transfers Page Blind Transfer Page Consult Transfer Page Page Host Application Planning and Design Asai Voice Response Application Considerations Routing Application ConsiderationsData Screen Delivery Application Considerations Page Communications System Planning Call Center Operations Planning Page Asai Installation Installation OverviewPrerequisites for Asai Installation Asai Hardware Architecture Typical Hardware ArchitectureInstalling Asai Hardware Base RAM Address Selection SwitchesIpci Switch Settings Installing Asai Software Conversant VISControl and ALT Removing the Asai Software Asai Administration Asai Administration OverviewVoice System Administration Feature Packages Asai Administration Screen Channel Administration Change a Channel EntryPage Page Add Channel Entry Add Channel Entry Screen achannel.psChange Channel Entry Change Channel Entry ScreenVirtual Channel Administration Remove Channel EntryPage Page Diagnose Ipci Board Diagnose Ipci Board ScreenDomain Administration Domain AdministrationPage Page Page Add Domain Entry 10. Add Domain Entry ScreenChange Domain Entry Remove Domain EntryInitialize Ipci Board Initialize Ipci BoardParameter Administration Asai ParametersPage Trace Detail Display Show Asai Software Version 14. Show Asai Software Version Screen version.psShow Status Asai Link Show Status of Asai LinkShow Status Asai Link Displays Take Ipci Board Off-line Take Ipci Board Off-lineAsai Administration Administering Asai Administering the Lines Administering the VIS ACD Split DomainPage Administering the VIS Agent Lines Page Administering Asai Asai Script Builder Actions Asai Script Builder Actions OverviewDefining ACallinfo Define ACallinfo Form Screen defacall.psPage Defining AEvent Define AEvent From Screen Page Page Page AEvent Return Field Value Meaning Return Value Explanation Connect Route Abnormal Abandon Request Route END Defining ARouteSel AEvent Fields Input/Output Required? Field Type Field SizeDefine ARouteSel Form Screen defroute.ps Page Defining ATran Deind ATran Form Screen deftran.ps Page Page ATran Fields Input/Output Required? Field Type Field Size Sample Scripts Sample Scripts OverviewSample Asai Voice Script Page Sample Routing Script Modify Table Sample Monitoring Script Page Page Asai Performance Performance Overview Voice Response Integration Data Screen Delivery