Vector steps that terminate an ASAI call route request

Last Updated : Sep 08, 2012 |

If an adjunct routing link step is followed by a wait-time or announcement treatment and the treatment completes before an ASAI call route request is returned by the adjunct, call processing continues for any vector steps that follow the treatment. In this case, certain vector commands terminate the ASAI call route request after being executed. Vector commands that terminate an active ASAI call route request include:

  • busy

  • check split

  • converse-on split

  • queue-to split

  • collect digits

  • disconnect

  • messaging split

  • route-to

If Communication Manager receives a valid ASAI call route message before one of the listed vector commands can execute, Communication Manager routes the call to the destination specified by the adjunct route. Otherwise, the ASAI route request is terminated.

Note:

The adjunct can also reject a call request by negatively acknowledging the route request sent by Communication Manager. When Communication Manager receives a route request rejection message from the adjunct, Communication Manager terminates any announcement or wait-time step being executed. Call processing then continues with the next vector step.