Tapi Route Points; Redirect Behaviors - 3Com 3C10402B Administrator's Manual

TAPI Route Points

Redirect Behaviors

A TAPI Route Point is a virtual device within the system where calls are
held pending action by an external TAPI application. Route points are
typically used by call center applications to redirect calls. A redirected call
is one that is sent from its original destination (the route point) without
being answered, to a new location specified in the external application.
A TAPI Route Point in the system is an extension with a voice mailbox in
the normal extension range:
V3000, V3001R, V5000 systems: 1000 – 3999
■
NBX 100 systems: 100 – 449
■
You create the TAPI Route Point, configure the system to route calls to it,
and then configure the external application to monitor it. For example,
you can configure a line card port to send all incoming calls on that line
to a specific TAPI Route Point. When a call arrives at the route point
extension, it is queued until the external application examines it and then
instructs the Call Processor to redirect the call to a destination specified in
the external application. Typically, the redirect action is based on the caller
ID information of the incoming call.
Table 64 describes the behavior of TAPI Route Points and redirected calls
within the system.
Table 64 TAPI Route Points and System Features
Call Redirected to
Internal extension
Description
If the internal extension has activated Do Not Disturb, a call
redirected to that extension goes immediately to the
extension's Call Forwarding setting.
If the TAPI Line Redirect Timeout is set to a value greater
than the extension's Call Forwarding setting and the call is
not answered, the redirected call will be managed by the
extension's Call Forwarding setting. The system will log a
successful redirect. If the TAPI Line Redirect Timeout is set
to a value less than the extension's Call Forwarding setting
and the call is not answered, the call will return to the
route point. For more information, see
Line Redirect Timeout"
TAPI Route Points
"Specifying TAPI
on page 354.
351