AT&T 585-350-812 manual

Page 89

ASAI Script Builder Actions

The “VIS Data” field returns a value previously saved in the VIS Data field of the A_Tran action in a voice script. If the call was not previously transferred using A_Tran, then a string of length 0 (null value) is returned. For example, a voice script which responds to an incoming call to the VIS (on a channel administered for ASAI) collects information from the caller and saves information in the VIS Data field of the A_Tran action and then uses A_Tran to transfer the call to a domain administered on the VIS. When A_Event reports the Abandon, Connect, or End events (Return Field contains ‘A’, ‘C’, or ‘E’) for that call, this field returns the saved information.

The “Routing ID” field contains a unique number that identifies the route request if A_Event is indicating a route request (that is, the Return Field contains an ‘R’). This number is needed if the A_RouteSel action is used to respond to the route request. If the Routing ID is not known, the value returned is 0.

The “Cause Value” field returns an error cause from the switch if the request to route the call is not successful. Note that the error cause is returned if the Return Field contains a value of “r” or 114 (indicating an ABNORMAL ROUTE END event). Possible error causes include the following:

“0” — The Destination Number provided in the A_RouteSel action is invalid and does not exist on the switch.

“1” — The switch is unable to route the call to the Destination Number because the destination is busy (that is, the destination currently has an active call).

“8” — The call dropped while waiting for a routing response. The caller probably hung up before the call has been routed.

“12” — The vector processing on the switch encountered steps other than wait, announcement, goto, or stop after the adjunct routing command.

“13” — Upon routing to the Destination Number (for direct agent call), the Destination Number is not logged in to the specified Split Extension.

“14” — The Destination Number (for direct agent call) is not a member of the specified Split Extension in the A_RouteSel action.

The “Return Field” contains a return code indicating what type of event (if any) is being reported. If the A_Event action is successful, it returns a number greater than or equal to zero. Refer to Table 6-4for additional information. If A_Event is unsuccessful, it returns one of the following values.

-1 — A_Event could not send the request for call information. Check the Message Log Report for system errors. Refer to Chapter 4, “Reports Administration” in the CONVERSANT Voice Information System Opera- tions for additional information.

-2 — A_Event did not receive a response from the ASAI for the request for information. Check to see if the ASAI system is running.

6-7

Image 89
Contents Conversant VIS Adjunct Switch Application Interface Blank Contents Asai Administration Asai Script Builder Actions Vi Issue 1 October Asai Overview Asai Voice Response Applications System Monitor Voice ChannelsPage Asai Routing Application route.pic Routing ApplicationsData Screen Delivery Applications Data Screen Delivery Applications gateway.pic Page Enhanced Customer Service Advantages Using the VIS Asai FeatureReduced Cost of Doing Business Asai Overview Asai Application Planning Design Asai Application Planning Design OverviewVIS 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 Routing Application Considerations Asai Voice Response Application ConsiderationsData Screen Delivery Application Considerations Page Communications System Planning Call Center Operations Planning Page Installation Overview Asai InstallationPrerequisites for Asai Installation Typical Hardware Architecture Asai Hardware ArchitectureBase RAM Address Selection Switches Installing Asai HardwareIpci Switch Settings Conversant VIS Installing Asai SoftwareControl and ALT Removing the Asai Software Asai Administration Overview Asai AdministrationVoice System Administration Feature Packages Asai Administration Screen Change a Channel Entry Channel AdministrationPage Page Add Channel Entry Screen achannel.ps Add Channel EntryChange Channel Entry Screen Change Channel EntryRemove Channel Entry Virtual Channel AdministrationPage Page Diagnose Ipci Board Screen Diagnose Ipci BoardDomain Administration Domain AdministrationPage Page Page 10. Add Domain Entry Screen Add Domain EntryRemove Domain Entry Change Domain EntryInitialize Ipci Board Initialize Ipci BoardAsai Parameters Parameter AdministrationPage Trace Detail Display 14. Show Asai Software Version Screen version.ps Show Asai Software VersionShow Status of Asai Link Show Status Asai LinkShow Status Asai Link Displays Take Ipci Board Off-line Take Ipci Board Off-lineAsai Administration Administering Asai Administering the VIS ACD Split Domain Administering the LinesPage Administering the VIS Agent Lines Page Administering Asai Asai Script Builder Actions Overview Asai Script Builder ActionsDefine ACallinfo Form Screen defacall.ps Defining ACallinfoPage Defining AEvent Define AEvent From Screen Page Page Page AEvent Return Field Value Meaning Return Value Explanation Connect Route Abnormal Abandon Request Route END AEvent Fields Input/Output Required? Field Type Field Size Defining ARouteSelDefine 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 Overview Sample ScriptsSample Asai Voice Script Page Sample Routing Script Modify Table Sample Monitoring Script Page Page Asai Performance Performance Overview Data Screen Delivery Voice Response Integration