Notes:
Previous completed XNET programming will be restored (on upgrade) to the various fields in the ICP/PBX Networking and XNET ICP/PBX Networking forms; however, if XNET was only partially programmed, the data may not be restored correctly.
Set the system date and time on each system in the network, through the System Administration Tool writedatetime command or through the Group Administration Tool - Change Date and Time, to take full advantage of XNET functionality.
TDM XNET is not available on embedded T1 framer modules. XNET (not IP trunking), requires HDLC resources which exist on the PRI card and the NSU. There are no HDLC resources available on the T1 framer module.
To program XNET trunks
Ensure the XNET Networking option has been purchased and enabled on the system (see the License and Option Selection form).
Note: In a configuration environment where XNET and IP Networking licensing options have been purchased, the number of simultaneous or concurrent remote ICPs supported for XNET calls from any ICP is limited to 8, though more ICPs can be configured.
System
Options form:
Set the DPNSS/QSIG Diversion Enabled option to "Yes".
Ensure that IP Networking/XNET Planning has been completed.
Initial ARS programming (in the ARS Leading Digits, ARS Digits Dialed, ARS Routes, ARS Route Lists, ARS Route Plans, and ARS Digit Modification Plans forms) must be completed for DID calls to ensure a proper ARS path is created for XNET setup calls (this must be completed for both the signaling and voice calls).
Note: If you are using the ISDN Call-by-Call feature, the ARS Digit Modification Plans and ARS Routes forms must be configured to ensure that the D-channel calls will be handled as data calls (see the Outgoing Call Characteristics topics in the IMAT online Help for more information on ISDN features).
ICP/PBX Networking form:
Assign the unique PBX Numbers, decided on during the Planning steps, to each system. Program the Local system first (Local ICP/PBX field = "Yes"), and then the remote systems.
Enter the unique IP address of the system in the Network IP Address field. When only PPP signaling over ISDN PRI B-channel will be used, the IP address does not have to be "real" but should be unique in the system. When programming both IP Networking and XNET, all XNET IP addresses must be at least 64 numbers apart (see IP Networking/XNET Planning).
Enter the PLID of the NSU (or FD PRI card) which supports the XNET PPP signaling in the ISDN Network Signaling Location ID field.
Enter the digits to be dialed to make an ISDN PRI call to support PPP signaling to this system (the system represented by this instance of the form) in the ISDN Network Signaling Digits to Dial field. If this is the Local system (Local ICP/PBX field = "Yes"), this field is only required if loopback calls are desired.
Enter the Answer Point of the incoming DID number that is used to set up PPP signaling to this system in the ISDN Network Signaling Answer Point Digits field. Only program this field if this is the Local system (Local ICP/PBX field = "Yes").
Set the ISDN Network Inactivity Timer to indicate how long the signaling link will be held after the last signaling session has finished. The same value should be programmed for this timer on both sides of the link. If not, the longest time is used.
XNET ICP/PBX Networking
form:
Repeat the steps below for each ICP/PBX.
Enter the ICP/PBX Number as defined in the ICP/PBX Networking form.
Enter the number of IP trunking calls that can be supported concurrently between the remote system and this system in the "Max Number of VoIP Calls" field. Note: This value must be the same for the local and remote systems.
Enter the number of TDM trunking calls that can be supported concurrently between the remote system and this system in the "Max Number of VoTDM Calls" field. Note: This value must be the same for the local and remote systems.
Enter the digits to be dialed from an originating system in the Outgoing Call Digits to Dial field. These digits may be modified by digit modification at the originating system, the CO, or at the terminating system.
Enter the Answer Point of the outgoing DID numbers to be used when setting up MSDN/DPNSS B-channel calls to Remote systems in the network in the Outgoing Call Answer Point Digits field.
Enter the Answer Point of the DID numbers to be used by Remote systems in the network when setting up MSDN/DPNSS B-channel calls to this system in the Incoming Call Answer Point Digits field.
Trunk
Attributes form:
Use this form to assign a trunk service number (required for the Trunk
Profile form). Select an unused Trunk Service Number:
Assign a Class of Service
Assign a Class of Restriction
Set incoming trunks to a "Non-Dial-In Trunks Answer Point" or set the "Dial-In Trunks Incoming Digit Modification Absorb" field to '0'.
If specifying an answer point, enter a directory number as the answer point for Day Service, Night Service 1, and Night Service 2.
(Optional) Assign a Trunk Label to appear on display telephones and attendant consoles during incoming and outgoing calls.
IP/XNET
Trunk Profiles form:
Program the trunk service number and interconnect restriction parameters
specific to IP Networking/XNET. The Remote Profile Number field must be
filled with the Local Profile Number of the Remote system.
IP/XNET
Trunk Groups form:
Set up the desired IP/XNET trunk groups. The Remote system number is
the unique number previously assigned.
ARS
Routes form:
Set up the IP/XNET Trunk Groups using the numbers assigned in the IP/XNET
Trunk Groups form. Ensure that no Trunk Group numbers are assigned, only
IP/XNET Trunk Group numbers. The Compression field does not apply.
Complete normal ARS programming
for the destination numbers on each Remote system.
ARS Leading Digits and the ARS
Digits Dialed forms, program the destination numbers using the Route
Number.
