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

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

Appendix A: Inter-Tel Private Networking
Node Programming
Inter-Tel
®
5000 Installation Manual – Issue 2.4, May 2008
Page A-17
Node Programming
Each node is programmed individually and contains its own database. Only one DB
Programming session—including administrator database programming—may be active on any
single node at a time. However, several nodes can have DB Programming sessions active
throughout the system.
Simultaneous sessions on different nodes can cause conflicting database changes, but they
also allow the flexibility of easier system administration.
Each node is given a unique identification number. Node numbers 1–63 apply if the 99 Nodes
capability is not available. If the main node is an Axxess Converged Communications Platform
running v10.0 or later, nodes may be numbered 1–99
.
The programmer is responsible for
ensuring that each node’s identification number is unique and that all of the nodes agree with
respect to their node identification numbers.
A node contains a list of node trunk groups used to access other nodes. For each node in the
network, you must define the routes to every other node. For example, in a network with four
nodes, you would define three routes for each node (one to each of the other three nodes).
Each node contains:
•
An optional username
•
An optional description
•
The identification number of the remote node
•
A list of the node trunk groups used to establish calls and communications to the node
•
A search algorithm that determines whether the node trunk groups are accessed in linear
or distributed order:
o
Linear : The node first attempts to route through the first node trunk group listed in the
route. If the node is unable to route through that node trunk group, it attempts to route
through the second node trunk group listed in the route. The node continues to attempt
to route through subsequent node trunk groups listed in the route until it successfully
routes or exhausts all node trunk groups listed in the route.
o
Distributed : The node shifts the first node trunk group it attempts to use. For example,
if the node routed the previous call or communication through the first node trunk
group listed in the route, the node routes the second call or communication through the
second node trunk group listed in the route.
If an off-node device is not programmed on the local node for a endpoint on a remote node,
users can still call that device by first dialing the node number for the endpoint node and then
the endpoint extension number. For example, in Figure A-3 on
page A-18 , a caller on Node 1,
calling extension 1100 on Node 2, could dial Node 97002 and then 1100 to reach the endpoint
on Node 2.
IMPORTANT
If desired, you can assign the same node trunk group to multiple nodes.
This is a common setup when using IP or frame relay devices, such as
the IP Networking Module. However, each node trunk group can have
up to 23 trunks (T1/PRI) or 30 trunks (E1/PRI), thus limiting the number
of incoming and outgoing calls. Make sure you have enough T1M or
T1M-2 modules to support the customer’s call load.