RAD Data comm IPmux-11 Frequently Asked Questions, TDM side alarms, Ethernet Side Alarms

Chapter 6 Troubleshooting and Diagnostics		Installation and Operation Manual
Diagnostics>Trace route
1.	Destination IP address	... (0.0.0.0)
2.	VLAN tagging	(Enable)
3.	VLAN ID[1 - 4095]	... (1)
4.	VLAN priority tag [0 - 7]	... (0)
5.	Trace route send

>
Please select item <1 to 5>	1 Mngr/s
ESC-prev.menu; !-main menu; &-exit

Figure 6-18. Trace route Menu

6.6 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.

All other alarms sent from the near-end TDM device (including information on timeslot 0), will be propagated transparently by the local IPmux, to the remote end TDM device (over the IP connection).

Framed mode:

In case of LOS/LOF/AIS detected on the local IPmux side, a user-configurable conditioning pattern (00 to FF) will be sent on the relevant timeslots (over the IP connection), to the far-end TDM device. A user-configurable conditioning pattern can also be applied on the ABCD bits (CAS signaling 1 to F) going towards the remote PBX.

The frame synch on the E1/T1 level is maintained in favor of the end TDM devices.

Ethernet Side Alarms

Unframed mode:

In case of local failure on the IPmux, or a situation of jitter buffer underflow/overflow, an (unframed) AIS will be sent towards the near-end TDM side.

6-22 Frequently Asked Questions IPmux-11 Ver. 2.00