Mitel Inter-Tel Specifications Page 139

  • Download
  • Add to my manuals
  • Print
  • Page
    / 352
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 138
System Features
INTER-TEL
®
CS-5200/5400 ADMINISTRATOR GUIDE, ISSUE 1.0 April 2005
Enabling the Send Camp-On Notifications to Members in DND Flag
Page 121
node will contain the old Agent ID in its removed list, because this ID still exists
on that node.
During a database restore on a node containing ACD hunt groups that use Agents IDs,
all Agents IDs are placed into each hunt group’s removed list. All endpoints will be
logged out during the restore.
When the extension number of a logged-in endpoint is changed, the new extension will
be logged in with the same Agent ID and will not be disconnected. This applies to end-
points logged in both remotely and locally.
Enabling the Send Camp-On Notifications to Members in DND Flag
The Send Camp-On Notifications to Members in DND flag is located under System\Devices
and Feature Codes\Hunt Groups\Local\<Hunt Group>. This flag indicates whether or not
camp-on burst tones are sent to hunt group members that are in DND or that are logged out.
When sent to display endpoints, the display also indicates
N CALLS WAITING FOR <HUNT
GROUP>
, where N is the number of calls that are currently camped on to the hunt group. This
allows hunt group members to see the hunt group queue in real-time.
If this flag is enabled:
UCD hunt group members that are in DND will receive camp-on notifications.
ACD hunt group members that do NOT use agent IDs will receive camp-on notifica-
tions when the members are NOT logged in to the hunt group. This, in effect, is the
same as being in DND from the hunt group perspective.
ACD hunt group members that use agent IDs will receive camp-on notifications only
when the agent is logged in to the hunt group and in DND. Agents also receive notifica-
tions while in wrap-up.
If the flag is disabled, which is the default setting, camp-on notifications are not sent to hunt
group members.
Trunk Features
This section explains the trunk functions and programmable features.
Caller ID, DNIS, and ANI
The system supports Caller ID, ANI, and DNIS to data about the source of the call.
Caller ID: Caller ID information gives the callers phone number and/or name.
CAUTION
Possible trunk misuse. While this system is designed to be reasonably secure against CO
trunk misuse by outside callers, there is no implied warranty that it is not vulnerable to unau-
thorized intrusions and toll fraud. If the central office does not provide supervision it will not
disconnect the call when one party hangs up; it is possible for a caller to remain connected
to a CO trunk circuit. If this happens, and the caller begins dialing, the call could be placed
through the system and would then be billed to the system’s owner. The system cannot
check this type of call for toll restriction and may not register the call in SMDR. This problem
could arise when a call is connected to an endpoint or when a call is in an unsupervised
conference.
NOTE
The standard Advanced CO Interfaces feature is required to use the following
features.
Page view 138
1 2 ... 134 135 136 137 138 139 140 141 142 143 144 ... 351 352

Comments to this Manuals

No comments