Merged Databases; Merged Items - Inter-Tel AXXESS Manual

Hide thumbs Also See for AXXESS:
Table of Contents

Advertisement

Programming
®
®
INTER-TEL
AXXESS
NOTE:
Extensions table before starting the merge process.

Merged Databases

5.6
and be programmed for the same product type and country. You should also run DB Test to
ensure there is no corrupted information. In addition, you should run an import/export between
all databases that will be merged to ensure all off-node extensions are current.
NOTE:
the data is merged. This may require some manual adjustment of the route groups.

Merged Items

5.7
Page 6-24
MANUAL VERSION 11.0 – May 2008
If the application detects this numbering plan, the listed devices and the entries in
the Device Baseline Extension table are automatically converted to the values
associated with the Option 2 plan (see below).
Option 2: Consists of the following defaults:
Trunk Groups - 92001
Node Trunk Groups - 97501
Node Route Groups - 97001
Trunks - 94000
ARS - 92000
NOTE:
This option conforms to the v6.0 and later numbering plan.
Regardless of the plan detected, all trunk extensions will be recalculated to optimize the
available range. The extensions for the node and CO trunk groups in the merging data-
bases will also be updated to the new extension plan.
You should set the device extensions to match the values in the Device Baseline
To successfully merge multiple databases, each database must be Version 6.0 (or later)
The merged database node information is automatically deleted from the master once
The following items are merged into the master database:
Nodes: The specific node number information for the merged nodes is removed from
the master database. For example, if merging node 2 with node 1 (master) on a 20-node
system, node 2 information is removed from the master database (not the information
on the other 18 nodes). All merged devices are then updated to reflect the master node
as the devices' local node.
Boards: Networked PRI cards that connect the nodes being merged are deleted from
the master database and are not merged into the master. This occurs because the physi-
cal connection between the nodes no longer exists, and these cards are not needed. The
list of boards and their associated devices that are merged is as follows:
EVMC
T1 - OPX, Ground Start, Loop Start, DID [DDI in Europe], E&M Trunks
T1 PRI/E1 PRI - B-Channel Trunks
LSC/LSC-D - Loop Start Trunks
LGCG/LGC-D - Loop Start, Ground Start Trunks
Merged Databases

Advertisement

Table of Contents
loading

Table of Contents