Phones
525
Phantoms consume the same software resources as a regular phone or IP phone, with the exception
of the voice paths. Therefore, they can have an impact on system performance.
Phantoms in DB Programming are defaulted to the not-in-DND status. When upgrading an old
database, if there were phantom devices in the old database, their DND statuses will not be changed
after the conversion.
The following scenarios describe phantom configuration uses:
• A phantom can be configured as a stand-alone device. An employee could have a cell phone
to use when they are not in the office but still need to be on the office switch. The administrator
could program a phantom for them and the employee (or administrator) could forward the phan
-
tom to the cell phone, using UC. That way, callers could still call an extension on the office switch
and be able to get the employee 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.
• A phantom can be configured as a monitoring device. For instance, a user may put a phantom
device in a hunt group and program a phone button to map to that phantom extension. Therefore,
a user can monitor when the phantom is ringing, etc., and even answer the call either via a
reverse transfer or a secondary extension key.
• A phantom can be configured as a call-park extension. The user may want to set up one or two
(or more) phantoms to be extensions at which a call can be parked.
• A phantom can be configured as a general mailbox because 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 unassociated mailbox, with the exception that a phantom mailbox can be
accessed off-node (whereas an unassociated mailbox cannot). Note that unassociated mailbox
-
es can be accessed off-node, if a caller calls the appropriate voice mail application and enters
the unassociated mailbox extension.
For programming instructions, refer to the “Phones and Devices” and “Troubleshooting” chapters in
the
MiVoice Office 250 Features and Programming Guide
.
• Group Listen On/Off
• Reverse Transfer
• Handsfree On/Off
• Seize Device
• Headset Off
• Steal
• Headset On
• System Hold
• Headset On/Off
• Transfer
• Hookflash [Recall]
• Transfer To Hold
• Music
•
Содержание MIVOICE OFFICE 250
Страница 1: ...MiVoice Office 250 INSTALLATION AND ADMINISTRATION GUIDE RELEASE 6 3 SP3 ...
Страница 24: ...MiVoice Office 250 Installation and Administration Guide xxiv ...
Страница 29: ...Chapter 1 MiVoice Office 250 New Features ...
Страница 41: ...MiVoice Office 250 New Features 13 Other Enhancements MiVoice Office 250 Release 6 2 supports Exchange 2016 ...
Страница 54: ...MiVoice Office 250 Installation and Administration Guide 26 ...
Страница 55: ...Chapter 2 Document Overview ...
Страница 62: ...MiVoice Office 250 Installation and Administration Guide 34 ...
Страница 63: ...Chapter 3 Product Description ...
Страница 86: ...MiVoice Office 250 Installation and Administration Guide 58 ...
Страница 87: ...Chapter 4 Specifications ...
Страница 157: ...Chapter 5 Installation ...
Страница 251: ...Installation 223 ...
Страница 274: ...MiVoice Office 250 Installation and Administration Guide 246 4 Test for quality ...
Страница 396: ...MiVoice Office 250 Installation and Administration Guide 368 ...
Страница 397: ...Chapter 6 Reference ...
Страница 416: ...MiVoice Office 250 Installation and Administration Guide 388 ...
Страница 417: ...Appendix A Private Networking ...
Страница 445: ...Appendix B Network IP Topology ...
Страница 486: ...MiVoice Office 250 Installation and Administration Guide 458 ...
Страница 487: ...Appendix C Open Source License Agreements ...
Страница 506: ...MiVoice Office 250 Installation and Administration Guide 478 ...
Страница 507: ...Appendix D Phones ...