Call Prompting interactions

Last Updated : Sep 08, 2012 |

The following interactions apply specifically to Call Prompting. For general Call Vectoring interactions that affect Call Prompting applications, see Call Vectoring.

Authorization Codes

If authorization codes are enabled, and a route-to command in a prompting vector accesses AAR or ARS, if the VDN’s FRL does not have the permission to use the chosen routing preference, then the system does not prompt for an authorization code and the route-to command fails.

CallVisor ASAI

ASAI-provided digits can be collected by the Call Vectoring feature using the collect vector command as dial-ahead digits. CINFO is passed to CallVisor ASAI.

Hold

With the exception of CINFO, if a call is put on hold during the processing of a collect command, the command restarts, beginning with the announcement prompt, when the call is taken off hold. All dialed-ahead digits are lost. Similarly, if a call to a vector is put on hold, vector processing is suspended when a collect command is encountered. When the call becomes active, the collect command resumes.

Inbound Call Management (ICM)

You can use Call Prompting to collect information that can be used by an adjunct to handle a call.

Transfer

If a call to a VDN is transferred during a collect command, the collect command restarts when the transfer is complete, and all dialed-ahead digits are lost. Similarly, if a call to a vector is transferred, vector processing is suspended when a collect command is encountered. When the transfer is complete, the collect command resumes. This is not true when a collect command collects CINFO digits. In this case vector processing is not suspended. Attendant extended calls do suspend vector processing in the same way as transferred calls.