Example 2: Wireless 802.11b/g Ethernet Bridge as in Figure 2.
1. Check the physical hookup for correctness: The G1600 requires an E1/T1 cross
cable in its connection to the E1/T1source. A pair of 802.11b/g Wireless
Ethernet bridge is also required for two G1600s to connect with as in Figure 2.
A PC or dumb terminal connection to the console port must use a null modem
(RS232) cross cable with settings of 115200, N, 8, 1.
2. Check that the Ethernet configuration parameters are correct.
Minimal
header
must be selected, and a large payload per packet (say 1492 bytes) is recommended.
Also, it is recommended to select 10M/Half for 802.11b Ethernet Bridge.
Selection of Auto-Negotiation may result in longer time for synchronization.
3. It is recommended to set one G1600 as Loopback-Master and the other as
Recovered-Slave. If the Tx clocks on both G1600s are configured as
Loopback-Master, make sure that the clock source driving both units is stable.
4. Use an E1 tester to perform the remote loopback test.
Table 5-3 lists
performance
observations and
problem
suggested causes and
corrections for G1600.
Observations
Possible Cause
Corrections
Jitter overflow and underflow
is occurring on both G1600s
The maximum jitter setting is
too low.
Look at the ping round-trip time on the
CES GetStatus display. This is an indication
of the network delay. The maximum jitter
should be at least this long.
Wide variation between
maximum and minimum jitter
levels but no occurrence of
jitter overflow or underflow
The jitter buffer is operating
correctly. There is variability
in the packet network possibly
due to congestion.
If the minimum is close to zero or the
maximum close to twice the maximum jitter
setting, increase the maximum jitter setting
to avoid future overflow or underflow.
**
For more details about the operational theory and configuration, please read through Chap 1 and 2
of the G1600 user manual. Chapter 3, and 5 provide the details for CLI commands, testing and
troubleshooting.
5
