Phantom Dns - Nortel Meridian 1000 Configuration Manual

CallPilot and CS 1000 connectivity overview

Phantom DNs

Introduction
Instead of using phonesets or dummy ACD DNs to route calls, CallPilot can use
"virtual telephones" that exist only in software and have no associated hardware.
The DN associated with one of these phantom phones is called a phantom DN.
Creating a Phantom DN
To create a phantom DN, you first create a phantom loop, and then you define a TN
within that loop. The system recognizes that any TN defined within that loop is a
phantom TN. Each phantom TN is assigned a DN (the phantom DN). When the DN
is entered in the CallPilot Service Directory Number page, it becomes the dialable
number of a CallPilot service.
Phantom DNs forward to a CDN queue
Incoming calls cannot queue up in the phantom TN as they arrive. When a call
arrives at a phantom DN, the system forwards it to a CDN queue before it is routed
to a multimedia channel for further call handling. However, the system remembers
the phantom DN to keep track of the requested service.
Services that should use phantom DNs
Nortel strongly recommends that you use either phantom DNs or dummy ACD DNs
(see "Configuring ACD agents" on page 81) for the following services:
all services created with Application Builder that are directly dialable by callers
Speech Activated Messaging
Paced Speech Messaging
Voice Item Maintenance
Fax Item Maintenance
Express Voice Messaging
Express Fax Messaging
Networking services
The following Networking services can either have a unique phantom DN
configured on the CS 1000 system, or they can share the phantom DN (and SDN) of
another service:
Enterprise Networking
AMIS Networking
Integrated AMIS Networking
28
Standard 1.16
CallPilot