Troubleshooting guide

Troubleshooting Guide
122
XNET
Table 36: XNET Troubleshooting
Symptom Probable Cause Corrective Action
Caller reports reorder tone
when calling to another
system.
Errors in the XNET
ARS programming.
1. Ensure that the ARS Leading Digit Assignment and
ARS Digits Dialed Assignment forms translate the
dialed digits to an XNET route. Either the digits do
not resolve to a route, or the route does not have the
XNET Trunk Group Number field programmed.
2. Ensure that the PBX Number field in the IP/XNET
Trunk Groups form contains a system number which
exists in the XNET network.
3. Ensure that the PBX Number field in the IP/XNET
Trunk Groups form contains a System number which
is programmed correctly on the Local PBX:
• The outgoing signaling DID number at the Local PBX
must match the correct remote incoming list.
• The outgoing voice DID number at the Local PBX
must match the correct remote incoming list.
• Interconnect restrictions must be set up incorrectly in
the IP/XNET Trunk Profiles form on the Local PBX
(the profile number must agree with the correct
remote profile number, and must have the correct
profile setting).
4. Ensure that the PBX Number field in the IP/XNET
Trunk Groups form contains a PBX number that is
correctly programmed on the Remote PBX:
• The incoming signaling DID number at the Remote
PBX may not match the correct local outgoing list.
• The incoming voice DID number at the Remote PBX
may not match the correct local outgoing list.
• Interconnect restrictions may be set up incorrectly in
the IP/XNET Trunk Profiles form at the Remote PBX
(the remote profile number may not agree with the
correct local profile number, or may be the wrong
setting for the profile).
Caller reports busy tone
when calling to another
system.
Insufficient DID
numbers allocated in
the XNET ICP/PBX
Networking form to set
up voice channels to
another PBX.
Allocate additional DID numbers.
Page 1 of 2