Network Operation Of System Features - Inter-Tel AXXESS Manual

Appendix A — Networking
® ®
INTER-TEL AXXESS
•
•
•
•
•
•
•
•
Page A-26
MANUAL VERSION 11.0 – May 2008
Network Primary Attendant: There can be a network primary attendant programmed
on each node. (There is usually one Network Primary Attendant shared by all of the
nodes.) When the network needs to direct a call to an attendant, it attempts to direct the
call to the network primary attendant first. If the network primary attendant is unavail-
able because the network is unable to route the call, it directs the call to the attendant on
the node where it originated. (See
tions.)
Extension Numbers: When an extension number is changed or deleted, the network
broadcasts the extension change to the other nodes in the network, and the network
updates all off-node device lists appropriately. If the network is unable to export or
import an extension because there is an active programming session on that node, the
node is unable to communicate with its Voice Processing port, the node is down, or the
links to the node are down, the new extension will not be added to or changed on that
node. You must manually change or delete the extension from the node's database.
Extension Lists: Extension lists are limited to the stations or trunks on a single node.
(See page 5-30 for an explanation of extension lists.)
Hunt Groups: UCD hunt group members can be off-node devices. ACD hunt group
members can also span nodes. Supervisors, however, cannot span nodes. All versions
support supervisors, recall destinations, announcement stations, and overflow stations
on other nodes. (See page 5-32
Station Monitor: Because supervisors must reside on the same node as the hunt group,
station monitoring can not occur across nodes. (See
about hunt group supervisors and station monitoring.)
Trunk Groups: See page 5-87
for trunk group information.
— Trunk Lists: All trunks in a trunk group must reside on the same node as the
trunk group.
— Outgoing Access: Because the network does not allow users to directly access
trunks on other nodes, each trunk group's Outgoing Access must contain only sta-
tions on the local node. Users must use ARS to access trunks on other nodes. After
an ARS call leaves the originating node, the network ignores outgoing access
restrictions.
— Ring-In Assignment: A trunk can ring in to a station or Voice Processing applica-
tion on another node.
— Allowed-Answer Assignment: Stations cannot have allowed-answer assignment
for trunk groups on other nodes.
Caller ID [CLIP], DNIS, and ANI: The network retains trunk and outside party infor-
mation and passes that information along when a call is routed from node to node. (See
page 5-72 for a complete description of this feature.)
Call Routing Tables: Call routing tables can be used on a network. (See
FEATURES and page 6-237
— You cannot route a call from one Call Routing Table to a Call Routing Table on
another node. When a Call Routing Table sends a call to another node, it cannot be
routed to any additional nodes.
— Trunks that ring in to call routing tables can only ring in to tables that are located
on their local node. They cannot ring in to a call routing table on another node.
page 5-27 for a detailed description of attendant sta-
for a description of hunt groups.)
page 5-40
in FEATURES and page 6-237
in PROGRAMMING for more information.)

Network Operation of System Features

for more information
in PROGRAMMING
page 5-89 in