AT&T 585-350-812 manual

Page 95

ASAI Script Builder Actions

The “Split Extension” field is used only for direct agent calls. This field contains either a number or the name of a field which contains a number identifying a valid ACD split. The Split Extension may be up to 5 digits in length. If the Split Exten- sion field is used, the call is treated as a direct agent call and routed to the agent identified in the Destination Number field via the split identified in the Split Exten- sion field. If the Split Extension field contains no digits (null value), then the call is treated as a normal call rather than a direct agent call. An empty split extension is entered by leaving the field blank as opposed to entering “ “.

The “Priority Call” field indicates whether the call is to be delivered as a regular or priority call. This field must contain either “Yes” or “No” or a field name which may contain either of these two values. Enter “Yes” if you want the call delivered as a priority call. Enter “No” if you want the call delivered as a regular call. If “Yes” is not specified in this field, the call is delivered as a regular call.

The “Routing ID” field contains a unique number which identifies the call being routed. The Routing ID must match the Routing ID previously retrieved in the A_Event action.

The “Cause Value” field returns an error cause if the route select is not successful. Note that the error cause is returned if the Return Field contains a value of -3. Refer to VIS column in Table D-6 in Appendix D, “Troubleshooting ASAI” for a complete listing of values.

The “Return Field” contains a return code indicating whether the action was suc- cessful. If the A_RouteSel action is successful, it returns a number greater than or equal to zero. If A_RouteSel is unsuccessful, it returns one of the following val- ues:

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

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

-4 — ASAI Link is down and route select information cannot be received from the switch. Refer to Appendix D, “Troubleshooting ASAI” for informa- tion on troubleshooting the ASAI digital link.

-5 — Illegal request. The channel using A_RouteSel is not for a RTE domain. A_RouteSel is being used in a script that has not been assigned to an RTE domain. Refer to Chapter 4, "ASAI Administration" for informa- tion on assigning A_RouteSel to a domain.

-6 — Switch did not respond after receiving the route select information.

“53” — Bad Routing ID. The Routing ID specified in A_RouteSel is invalid. Check to make sure that the same Routing ID received from ROUTE REQUEST Event is used in the A_RouteSel action.

6-13

Image 95
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