Page A-28
Appendix A — Networking
INTER-TEL
®
AXXESS
®
MANUAL VERSION 11.0 – May 2008
Network Operation of System Features
• Camp On: A user can camp on to busy resources on another node. When the system
has several routing options for a call, it tries to use each route, in order, until it finds a
free route. If it is unable to find a free route, the system tries once again to use the first
route. If the first route is still busy, the system camps on to the first route. (See page 5-
177 for details.)
• Queue: A user cannot queue onto busy resources on another node. (See page 5-177 for
details.)
• Inter-Station Messages: The network allows users to leave messages for, and respond
to messages from, users on a different node. A station’s message center or alternate
message source does not need to be on the same node as the station. It can be a station,
hunt group, Voice Processing application, or any off-node device.
• Off-Hook Voice Announce (OHVA): The network allows intercom callers to establish
OHVA calls to phones on other nodes. (See page 5-190 for more information about this
feature.)
• Account Codes: The network validates account codes against the account code table on
the same node as the caller. The account code follows the call as it moves from node to
node and appears on every SMDR record associated with the call. (See page 5-198 for
an explanation of account codes.) However, if an optional account code is entered dur-
ing the call, that account code will be used in the SMDR report.
• System Hold: When a user puts a trunk on system hold, only that user and users on the
same node as the trunk can access the call. (See page 5-203 for a description of the sys-
tem hold feature.)
• Transfer Recall Destination: A station’s transfer recall destination can be an off-node
device. (See page 5-210 for an explanation of transfer recall destinations.)
• Call Screening: In a network setting, the Voice Processing can provide call screening
for a destination extension on another node. However, the node where the Voice Pro-
cessing is connected must have an off-node device programmed for the destination
extension and access to the remote node. (See page 5-211 for a complete description of
this feature.)
• Conference Calls: A user can build a conference with party members (stations and/or
trunks) on other nodes. The conference circuits used to build the conference will be
allocated from the originating party’s node. Any party, not just the originating party, can
add a party member to the conference. (See page 5-213 for more information about con-
ference calls.)
— If the party who adds the new member is on the originating party’s node, the party
will be added to the conference circuit already allocated. This conference is still
restricted to the four party limit.
— If the party who adds the new member is not on the originating party’s node, a
new conference circuit is allocated from the second node. Because this allows
more than four parties in a conference, users should be warned that voice levels
can be degraded if more than four parties are on a conference.
• Reverse Transfer:
A user can reverse transfer a call from a station or a hunt group on
another node. (See page 5-212 for details.)
• Record-A-Call: The Record-A-Call destination does not have to be on the same node
as the station, but the Voice Processing Unit must have a mailbox for that station. (See
page 5-218 for a complete explanation of this feature.)
• Agent Help: The Agent Help Extension does not need to reside on the same node as
the user requesting Agent Help. (See page 5-220 for an explanation of this feature.)
To Next Page
Loading...
