IPmux-1/1E Installation and Operation Manual Chapter 4 Troubleshooting and Diagnostics
Diagnostic Tests 4-3
4.2 Troubleshooting
Table 4-2 presents the event types as they appear on the Event Log File and lists
the actions required to correct the event (alarm) indication.
Table 4-2. IPmux-1 Troubleshooting Chart
Fault Probable Cause Remedial Action
E1/T1 equipment connected to
IPmux-1 is not synchronized
with IPmux-1/1E.
Configuration problems
Physical layer problems
1. Check cables and physical connectivity.
2. Check IPmux-1 E1/T1 configuration and,
if necessary, other IPmux-1 parameters.
3. Check E1/T1 physical connection (use
loopbacks).
Slips and errors in E1/T1/BRI/FXS
equipment
Ethernet port in switch and
IPmux-1 are not in the same rate or
duplex mode
Ethernet port is set to work in half
duplex mode (may cause extreme
PDV because of collisions and
backoffs)
Timing configuration is not properly
set (periodic buffer under/overflows
shown on IP channel status menu)
Deactivation employed by NT
when IPmux is TE and in loopback
timing mode
Network PDV or lost frames
1. Check E1/T1 physical connection (use
loopbacks).
2. Check timing settings according to
explanation in this manual.
3. Check switch and IPmux-1 port
configuration (negotiation, rate, duplex
mode)
4. Check PDV introduced by the network,
and, if necessary, increase PDVT jitter
buffer setting.
5. Check NT deactivation (BRI).
Echo in voice High delay in voice path 1. Check network delay and try to
decrease it.
2. Try to decrease PDVT (jitter) buffer.
4.3 Diagnostic Tests
Maintenance capabilities include external and internal loopbacks.

E1/T1

External Loop

IPmux-1 can be set to an external loop to test the connection between the E1/T1
port and the PBX (refer to Chapter 3). In this mode, data coming from the PBX is
both looped back to the PBX and transmitted forward to the IP network (see
Figure 4-1).
This mode can also be achieved by a T1 FDL line loopback command.
Order from: Cutter Networks
Ph:727-398-5252/Fax:727-397-9610
www.bestdatasource.com