Mitel Inter-Tel 5000, Руководство по установке и обслуживанию

Страница: 389 / 468

Appendix A: Inter-Tel Private Networking
Network Operation of System Features
Inter-Tel
®
5000 Installation Manual – Issue 2.4, May 2008
Page A-23
•
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 unavailable because
the network is unable to route the call, it directs the call to the attendant on the node
where it originated.
•
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 database.
•
Extension Lists: Extension lists are limited to the endpoints or trunks on a single node.
•
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 endpoints, and overflow endpoints
on other nodes.
•
Endpoint Monitor: Because supervisors must reside on the same node as the hunt
group, endpoint monitoring can not occur across nodes.
•
Trunk Group s :
o
Trunk Lists : All trunks in a trunk group must reside on the same node as the trunk
group.
o
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 endpoints on
the local node. Users must use ARS to access trunks on other nodes. Once an ARS
call leaves the originating node, the network ignores outgoing access restrictions.
o
Ring-In Assignment : A trunk can ring in to a endpoint or Voice Processing application
on another node.
o
Allowed-Answer Assignment : Endpoints cannot have allowed-answer assignment for
trunk groups on other nodes.
•
Caller ID, DNIS, and ANI : The network retains trunk and outside party information and
passes that information along when a call is routed from node to node.
•
Call Routing Tables : Call routing tables can be used on a network.
o
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.
o
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.
o
The network attempts to optimize routes so that calls do not route through a node
more than one time (looping). However, the network does not have the ability to
dynamically reroute. That is, if a node trunk group that was previously unavailable
becomes available after the network has already chosen another route, the network
does not reroute using that node trunk group.
o
The network will try to optimize routes when calls have been transferred or reverse
transferred across several nodes (possibly forming loops).