Specifications

Chapter 6 Troubleshooting and Diagnostics Installation and Operation Manual
6-30 Frequently Asked Questions IPmux-8/16 Ver. 6.00
6.4 Troubleshooting
Table 6-9 lists faults and describes the actions required to correct the event (alarm)
indication.
Table 6-9. Troubleshooting Chart
Fault Probable Cause Remedial Action
The E1/T1 equipment connected
to IPmux-8/16 is not synchronized
(E1/T1 level) with IPmux-8/16
Configuration problems 1. Check IPmux-8/16 port
configuration and, if necessary,
other
IPmux-8/16 parameters.
2. Check E1/T1 physical
connection (use loopbacks).
Slips and errors in E1/T1
equipment
• Ethernet port in switch and
IPmux-8/16 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 – bundle
connection status menu)
• Network PDV or Lost Frames
1. Check E1/T1 physical
connection (use loopbacks) and
E1/T1 statistics.
2. Check timing settings according
to explanation in this manual.
3. Check switch and
IPmux-8/16 port configuration
(negotiation, rate, duplex mode)
and check Ethernet statistics.
4. Check PDV introduced by the
network, and, if necessary,
increase PDVT jitter buffer
setting.
Echo in voice 1. Check network delay and try to
decrease it.
2. Try to decrease PDVT (jitter)
buffer.
6.5 Frequently Asked Questions
Q: How does the IPmux handle/propagate alarms on the TDM and Ethernet side?
A: The IPmux handles alarms on the TDM and Ethernet side in the following
manner:
TDM side alarms:
Unframed mode:
 In case of LOS (Loss Of Signal) on the local IPmux side, AIS will be sent
towards the IP side, and will then be transferred over the E1/T1 to the
remote TDM device.