Extension Numbers; Programming Off-Node Extension Numbers - Inter-Tel AXXESS Manual

Appendix A — Networking
® ®
INTER-TEL AXXESS

5. EXTENSION NUMBERS

5.1
should have a universal numbering plan so that extension numbers on the various nodes do not
overlap and do not conflict with feature codes. That is, when planning the extension numbers
for each of the nodes in the network, set aside a block of extension numbers (for stations, hunt
groups, Voice Processing applications, etc.) for each node.
A. PROGRAMMING OFF-NODE EXTENSION NUMBERS
5.2
port extensions on other nodes in two ways:
•
•
5.3
has been reached, new devices received through network broadcasts cannot be added to the
node's database. You can make room in the database for new extensions by setting up wildcard
extensions as described below.
5.4
broadcasts that extension change to the entire network and updates any existing off-node
devices on the other nodes. 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 exten-
sion will not be added to or changed on that node. You must manually add or change the new
extension in the node's database. You may want to check each node to verify that their off-
node device lists are programmed properly to allow access between the nodes.
5.5
not programmed as off-node devices on their node. Also, if the same extension number exists
on two nodes, the only way a user can call the extension on the other node is to dial a node
number before dialing the extension number. For example, if extension 1200 exists on both
Node 1 and Node 2, users on Node 1 must first dial the node number for Node 2 to before dial-
ing extension 1200 on Node 2. (Note that each node trunk group also has an extension, but the
number cannot be dialed by users.)
Page A-16
MANUAL VERSION 11.0 – May 2008
Each node has its own extension and feature code programming. However, the network
You can give users access to station, hunt group, Voice Processing application, and page
You can manually program off-node devices (extensions from other nodes) into the
database of the node you are programming. To give a node access to an off-node
device, program the extension number, username, description, device type (station, hunt
group, Voice Processing application, or page port), and node identification number. The
network uses the username and descriptions for directory features only. If you define an
extension conflict, DB Programming does not allow you to exit the screen until you
correct the conflict.
You can import and export new extensions as you create them. When you add a new
extension, DB Programming automatically makes the new extension visible to the other
nodes in the network. Or you can manually export local devices to other nodes (or
import devices from other nodes) using the Export/Import option in DB Programming.
The network broadcasts the new extension number (along with the username, descrip-
tion, device type, and node identification number) to the other nodes in the network and
places it in their off-node device lists. If there is an extension conflict on another node,
the node with the conflict ignores the new extension in favor of the previous extension
number. Also note that if the network is unable to route the broadcast message to a
node, that node will not be able to receive and re-broadcast the new information and it
must be entered manually. (If Message Print is enabled, error messages will indicate
any unsuccessful broadcasts.)
Each node can have only 8000 off-node device entries in its database. After that limit
If you change a device's extension, username, or description, the network automatically
Nodes are assigned extension numbers that users can dial to reach stations which are
Extension Numbers