Page 5-120
System Features
INTER-TEL
®
AXXESS
®
MANUAL VERSION 11.0 – May 2008
Phantom Devices
11. PHANTOM DEVICES
11.1 Phantom device functionality has been enhanced in v11.0. The new phantoms are fully
functional virtual devices on the system. The following scenarios describe phantom configura-
tion uses. You can configure a phantom device as a:
• Call-Park Extension: You may set up one or two (or more) phantoms to be extensions
at which a call can be parked.
• Stand-Alone Device: Users could have a cell phone to use when they are not in the
office but still need to be on the office switch. You could program a phantom for them
and the user (or you) could forward the phantom to the cell phone, using Unified Com-
municator
®
(UC). That way, callers could still call an extension on the office switch and
be able to get the user on his or her cell phone. In the extreme case, all devices on the
switch could be phantoms for users with cell or other phones that are not physically
connected to the switch.
• Monitoring Device: You may put a phantom device in a hunt group and program an
endpoint button to map to that phantom extension. Therefore, a user can monitor when
the phantom is ringing, etc., and even answer the call either through a reverse transfer
or a secondary extension key.
• General Mailbox: Phantoms can have associated mailboxes. When a caller calls the
phantom, if the phantom is set up to go to voice mail, the caller can leave a message in
this “general” mailbox. However, this configuration is not much different from an unas-
sociated mailbox, with the exception that a phantom mailbox can be accessed off-node
(whereas an unassociated mailbox cannot). Note that unassociated mailboxes can be
accessed off-node, if a caller calls the appropriate voice mail application and enters the
unassociated mailbox extension.
11.2 Phantoms can function with UC to perform advanced call routing tasks without the
need for a real desk phone. They can also have a true status, such as idle, Do-Not-Disturb
(DND), ringing, etc. so that they could be placed in hunt groups and actually ring. The statuses
that do not apply to phantom devices are as follows:
• Unplugged (phantoms have no hardware and will always be online)
• Busy/Permanently Busy (phantoms cannot answer a call)
11.3 The user must have UC or another OAI application (for example, Contact Center Suite
or Attendant Console) to use the phantom feature. Because the phantoms do not have corre-
sponding hardware devices, all programming that cannot be done in DB Programming must be
done from OAI/UC.
11.4 An OAI application can have phantoms perform almost all operations as an endpoint.
The exceptions are listed below. These exceptions must be enforced because phantoms do not
have voice paths. Phantoms cannot:
• Answer calls from an OAI application.
• Make calls from an OAI application.
• Be in a conference.
• Reverse-transfer calls.
To Next Page
Loading...
