Review all conditions listed in this topic.
Create a numbering scheme to provide each system with a unique ID number (valid numbers are from 1 to 999). The numbers are used to distinguish between systems when entering information in the forms.
(TDM XNET only) Estimate the expected XNET traffic rate to each system to determine how many B-channel DID numbers are required. Each DID number remains busy throughout the call set-up until the B-channel and signaling calls are synchronized. Other XNET real calls that try to use the same B-channel DID number during this time will receive busy tone.
(TDM XNET only) Acquire the DID numbers and determine how they will be modified by outgoing and incoming system digit modification and by the CO.
(TDM XNET only) Create an IP Address for the designated PRI card. The address should be entered in the following format "xxx.xxx.xxx.xxx", where each "xxx" can be between 1 and 255.
Note: If you plan to program both IP Networking and XNET, keep in mind that they use the same IP addresses and that XNET requires IP addresses to be at least 64 numbers apart. (The PRI card ignores the last 6 binary digits and cannot distinguish between two IP addresses within a 64 number range.) If IP addresses on the network do not meet this requirement, you'll need to re-configure IP addresses before enabling XNET.
Each system must be assigned a unique ID.
For IP Trunking, real IP addresses must be assigned.
Devices on a network of systems
using IP Networking or XNET must have unique IP addresses.
If only TDM XNET is used, you do not have to ensure that IP addresses
differ from those on the data network. IP addresses are not exposed to
the internet or the customer's intranet.
If IP trunking is used, ensure that the IP addresses differ from those
on the data network. With IP trunking, these IP addresses are exposed
and will cause conflicts if not unique. IP trunking and TDM XNET use the
same IP addresses,
If both IP Trunking and TDM XNET are programmed, the programmed IP addresses will be used for both. Note that TDM XNET requires that IP addresses be at least 64 numbers apart.
Maintenance support is provided for the Message, Resources, Rmessage, Busy, Return to Service, and State commands.
The total number of both real and virtual IP trunking and conventional (PSTN B-channel) XNET calls that can be concurrently supported on an ICP is 2000.
IP addresses must be at least 64 numbers apart. (The PRI card ignores the last 6 binary digits.)
Each system must have at least one
ISDN PRI T1 or E1 card installed and programmed.
This card provides:
the voice call or B-channel path (unless the voice call is hosted on another PRI card or a different DID/DDI capable trunk type)
the signaling call or D-channel path
HDLC PPP resources.
If there is more than one PRI card, the ISDN signaling PLID can be programmed on one card, and the trunks can be programmed on one or more of the others.
The PRI card providing the HDLC PPP resources requires a unique IP Address.
Simultaneous signaling connections for XNET are supported to a maximum of 8 systems (as long as HDLC and PRI trunk resources are available).
Requires ISDN Called Party Number (DID/DDI) service and Bearer Capability supplementary services (ISDN 56K or 64K data service must be available for the PRI trunks that carry the signal channels).
Customers must lease and program at least 2 DID/DDI numbers per signaling link, and ensure programming is consistent between systems. One outgoing DID number that is to be used for signaling must be programmed for each link to a Remote system, while only one incoming DID number that is to be used for signaling is required for all of these remote connections (it can be shared).
B-channel DID numbers are programmed in the XNET ICP/PBX Networking form and signaling DID numbers are programmed in the ICP/PBX Networking form. The number of B-channel DID numbers assigned to a list depends on the anticipated XNET real call traffic volume between two systems. The outgoing list at one system should match the incoming list at the Remote system.
Only the ISDN data call supporting the MSDN signaling link must be answered for calls to busy, out of service, or ring no answer MSDN destinations.
Telephone sets will display the XNET trunk label "XNET" and consoles will display "Xnnnn" (where nnnn is an XNET trunk number) when XNET resources are unavailable to make a call.
When a D-channel over PRI B-channel is used to carry DPNSS signaling, the number of simultaneous point-to-point signaling paths between systems are constrained by the number of available HDLC controllers.
