Troubleshooting guide

Troubleshooting Guide
124
IP Trunking (IP Networking)
Table 37: IP Trunk Troubleshooting
Symptom Possible Cause Corrective Action
IP trunk does not recover
after router crash.
ICMP redirect is enabled. 1. On the RTC shell, use routeShow to identify
the addition RouteHost entries, then use
routeDelete to remove the entry.
2. For a permanent solution:
• Make sure that the route has a “permanent”
static route to the remote IP trunk network.
• Turn IP redirect off.
• Turn on the routing protocol between local
router and ISP router.
Unable to place calls
between systems via IP
trunks in a clustered,
redirected, or resilient
environment.
PBX Number in the ICP/PBX
Assignment forms of the
systems are programmed
incorrectly.
For each system in the cluster, ensure that the
system’s PBX Number matches its CEID Index
Number as defined in the Cluster Elements form.
Cannot Group Page across
IP trunks.
If one system has pre- 3300
Release 5.2.4.4 software
and the other system has
post-Release 5.2.4.4, the
remote group page will fail
due to incompatible
signalling.
Upgrade all systems to Release 5.2.4.4 software
or higher.
Receive “out of service” tone
while dialing across IP trunks
to a remote element
Congested trunks at remote
node. Note: this is not a local
trunk congestion issue, the
congestion is at the remote
site. The remote site will
have less trunks
programmed than the
originating site.
1. Launch the System Administration tool on the
remote element.
2. Access the XNET ICP/PBX Networking form.
3. Increase Max Number of VOIP calls.