Converse call placement

Last Updated : Sep 08, 2012 |

The converse-on step delivers the call to the converse split. The caller does not hear the ringback tone. Any audible feedback supplied by vector processing remains until the VRU answers the call and all digits have been outpulsed to the VRU. Vector processing is suspended. Callers remain in any non converse split queues and retain their position in queue while the converse session is active.

If a Call Prompting TTR is allocated to the call, the TTR is released. Any dial-ahead digits are discarded. However, any digits collected prior to the converse-on step are retained.

Calls to busy converse splits are allowed to queue. The priority of the call in queue is administrable within the converse-on step. Again, any audible feedback supplied by vector processing continues until the call is answered by the VRU and any data is outpulsed. Calls to busy converse splits have either no queue or a full queue fail. For this scenario, a vector event is logged and vector processing continues at the next vector step.

Whenever a converse-on step places a call to an auto-available split whose agents are all logged out, the call is not queued. Instead, the converse-on step fails, a vector event is logged, and vector processing continues at the next vector step.

Note:

Usually, the scenario occurs whenever the Voice Response Unit (VRU) goes down, the ports are members of an Auto-Available Split (AAS) and the Redirection on No Answer (RONA) feature has taken all the ports out of service.

The display is not changed by the terminating or answering of a converse call. Also, whenever a call is delivered to a display station using a converse-on step, the station displays the following information: Originator Name to VDN Name. Conventional Call Vectoring rules for Override are in effect.

Valid destinations for converse calls must be vector-controlled and include the following:

  • Hunt groups

  • ACD including Auto-Available splits

  • Agent including Auto-Available skill groups

  • AUDIX hunt groups

Note:

AUDIX hunt groups are valid destinations for converse calls and do not have to be vector-controlled.

Undefined and non vector-controlled hunt group, split or skill numbers are rejected at administration time.

Any attempt to remove a hunt group, split or skill administered within a converse-on vector step is denied until the vector has been changed. Also, any attempt to make a hunt group, split, or skill non vector-controlled is denied if the hunt group, split, or skill is called by a converse-on step.