Treating digits as a destination

Last Updated : Sep 08, 2012 |

With Call Prompting, you can route calls according to the digits collected from the caller. Once the digits are collected by the collect digits command, the route-to digits command attempts to route the call to the destination that the digits represent. The command always routes the call to the destination indicated by the digits processed by the most recent collect digits command.

The digits can represent any of the following destinations:

  • Internal (local) extension, for example split or hunt group, station, and announcement

  • VDN extension

  • Attendant

  • Remote access extension

  • External number such as a Trunk Access Code (TAC) or an Automatic Alternate Route/Automatic Route Selection (AAR/ARS) FAC followed by a public network number, for example 7-digit Electronic Tandem Network (ETN), 10-digit DDD.

The following example shows how a call is routed by digits that are collected from a caller.

Using Call Prompting to route by collected digits

1. wait-time 0 seconds hearing ringback
2. collect 5 digits after announcement 300 [You have reached Redux Electric in Glenrock. Please dial a 5-digit extension or wait for the attendant.]
3. route-to digits with coverage y
4. route-to number 0 with cov n if unconditionally
5. stop

In this vector, the caller is prompted to enter the destination extension of the party that the caller wants to reach (step 2). The extension in this vector can contain up to 5 digits. The vector collects the digits and routes to the destination by the route-to digits command in step 3.

If the route-to digits command fails because the caller fails to enter any digits, or because the extension number entered is invalid, the route-to number command in step 4 routes the call to the attendant, which is the default routing option. However, as long as the destination is a valid extension, the route-to digits command succeeds, coverage applies, and vector processing terminates. If the destination is busy, vector processing terminates because coverage call processing takes effect.

Note:

Occasionally, all of the system’s TTRs can be in use. As a result, when you are collecting digits from a caller, do not start your main vector with a collect digits command, since the caller in this case receives no audible feedback if the caller has to wait for a TTR to become available. Include some treatment, for example wait-time 0 seconds hearing ringback, before the initial collect digits step.

In addition, if calls are to be transferred to this vector, add a wait-time step of sufficient length before the collect step to allow the transferring party time to complete the transfer.