FL4+ User Guide v070109

Flanger4Plus
User Guide
Part Number: 9100-7002
Revision 070109
For Build 62209 and later

Copyright
No part of this publication, or any software included with it, may be reproduced, stored in a
retrieval system, or transmitted in any form or by any means, including photocopying,
electronic, mechanical, recording or otherwise.
This document contains proprietary and confidential information. The disclosure of its
contents to any third party is strictly prohibited without the prior written consent. This
document is provided “AS IS”, without warranty of any kind, either expressed or implied,
including, but not limited to, the implied warranty of merchantability or fitness for a
particular purpose. The equipment, software, or specifications described in this document
may be changed or improved at any time and without notice.
Revision History
Updated: August 12, 2010
For build 62209 and later 2

Contents
1. Introduction................................................................................... 7
About The Product .................................................................................................... 8
Benefits And Uses ..................................................................................................... 8
Flanger4Plus Gets Smarter Over Time ..................................................................... 8
Designed For Wireless .............................................................................................. 8
Easy Setup and Configuration................................................................................... 9
Network Connectivity ............................................................................................... 9
Typical Deployments .............................................................................................. 10
2. Getting Started ........................................................................... 11

Identifying Your Flanger4Plus................................................................................ 12
Supported Radios for Power over CAT5 ................................................................ 12
Understanding the Front Panel................................................................................ 12
Understanding the Back Panel ................................................................................ 13
Making Connections ............................................................................................... 14
LAN Port........................................................................................................ 16
Local Port ...................................................................................................... 16
Flanger4Plus User Interface ......................................................................... 17
MAC Addresses.............................................................................................. 17
IP Defaults ..................................................................................................... 17
DS1 Timing Control....................................................................................... 17
Profiles........................................................................................................... 18
DS1 Defaults.................................................................................................. 18
Features and Specifications ..................................................................................... 19
Product Support....................................................................................................... 20
3. Configuration Considerations ..................................................... 21

Network Settings ..................................................................................................... 22
Setting Flanger4Plus Addresses .............................................................................. 22
Selecting the DS1 Clock Mode ............................................................................... 23
Clock Recovery ....................................................................................................... 24
Mode 3 ........................................................................................................... 24
3 For build 62209 and later
Mode 4 ........................................................................................................... 24
When to use Mode 2 to Mode 3 Pairs............................................................ 25
When to use Mode 2 Pairs ............................................................................. 25
When to use Mode 3 Pairs ............................................................................. 26
Using Equalizer Control Settings............................................................................ 26
Optimizing Reliability for Various Networks ......................................................... 26
Making a Packet ............................................................................................ 26
Pointer Calculation ....................................................................................... 27
The Buffering Mechanism.............................................................................. 28
Optimizing Performance for Various Networks ..................................................... 29
Flanger4Plus Logic ....................................................................................... 29
Packetizing Delay .......................................................................................... 29
Link Delay...................................................................................................... 29
Wire Delay ..................................................................................................... 30
“In the Air” Delay ......................................................................................... 30
Protocol Delay............................................................................................... 30
Delay Variation ............................................................................................. 31
Link Verification ............................................................................................ 31
Example Link Delay Measurements .............................................................. 32
Overall Link Delay Budget ............................................................................ 34
Bandwidth Considerations ...................................................................................... 34
Flanger4Plus’s Unique FEC ......................................................................... 34
Profile Considerations ............................................................................................. 34
4. Configuring Flanger4Plus........................................................... 36
Accessing the Flanger4Plus Unit ............................................................................ 37
Using the Menu to Navigate .......................................................................... 39
Login to the Web Server ................................................................................ 40
Using the System Reset and Recover page ............................................................. 41
Using the TDM Configuration page .............................................................. 43
Individual Channel Settings........................................................................... 44
T1/E1 Remote Target..................................................................................... 45
TDM FEC ...................................................................................................... 46

Using the Ethernet Configuration page......................................................... 48
Using the Radio Configuration page............................................................. 49
Using the TOS Configuration page ............................................................... 50
Using the Profile Configuration page ........................................................... 51
Managing Profiles ................................................................................................... 52
Copying a Profile........................................................................................... 52
Creating a Profile .......................................................................................... 52
Deleting a Profile .......................................................................................... 52
Using SNMP .................................................................................................. 54
Updating your Flanger4Plus ............................................................. 56
Understanding Flanger4Plus Reports .............................................. 57

Description of Interface Reports ............................................................................. 57
Understanding DS1 Reports .......................................................................... 58
Understanding WAN Reports ........................................................................ 61
Understanding WAN Reports ........................................................................ 61
Description of IP Reports ........................................................................................ 63
Understanding IP Reports ............................................................................. 63
Understanding ICMP Reports ....................................................................... 65
Understanding ARP Table Reports ............................................................... 67
Description of TCP/UDP Reports ........................................................................... 70
Understanding UDP Reports......................................................................... 70
Understanding TCP Connection Reports ...................................................... 71
Understanding TCP Receive Reports ............................................................ 74
Understanding TCP Transmit Reports .......................................................... 76
Description of System Reports................................................................................ 77
Understanding Packet Queue Reports........................................................... 77
Understanding Problems Reports.................................................................. 80
Understanding SNMP Reports ...................................................................... 81
Understanding Web Server Reports .............................................................. 86
5. Cabling Requirements................................................................ 88
CAT5 Ethernet ........................................................................................................ 88

Pin-outs with Power over CAT5 .................................................................... 88
Pin-outs without Power over CAT5............................................................... 88
Ethernet with Power over CAT5.................................................................... 88
DS1 with RJ-45 ....................................................................................................... 89
6. Appendix .................................................................................... 90

1. Introduction
This guide is intended for installers and support personnel of your Memorylink
Flanger4Plus™. It assumes a working knowledge of DS1 telecommunications lines and IP
networks.
Section Contents
About the Product
Benefits and Uses
FLANGER4PLUS Gets Smarter Over Time
Designed for Wireless
Easy Setup and Configuration
Network Connectivity
Typical Deployments

About The Product
Flanger4Plus™ enables point-to-point tunneling of T1 or E1 traffic across wireless
Ethernet devices. This small, simple-to-use unit provides seamless transport of T1 or E1
across an Ethernet link, thereby providing dramatic cost savings over the cost of
conventional leased lines.
Benefits and Uses

Eliminates monthly leased line changes
Ideal for PBXs in campus environments
Great for Cellular Backhaul
Protects legacy equipment investments
Provides Disaster Recovery capability
Ideal for providing broadband for special events
Flanger4Plus Gets Smarter Over Time

With it’s exclusive Malachi™ architecture, Flanger4Plus’s hardware becomes interactive,
reprogrammable and reshapable, providing scalability and greater dimensionality. The
Flanger4Plus defies competitive technologies that have built-in obsolescence and delivers a
far greater value than silicon-based circuitry.
Designed For Wireless

The Flanger4Plus uses a unique algorithm optimized for wireless Ethernet transport of T1
and E1 data streams. Because of the potential for changing conditions that could affect
wireless network throughput, the Flanger4Plus unit provides the capability for recovering
from data loss, without propagating the errors to following frames. This is accomplished
with Channel Look-Ahead™ and Programmable Channel Optimization™ features.

Easy Setup and Configuration
Because Flanger4Plus provides physical pass-through of the T1 and E1 link, no special
configuration or setup is required, regardless of the format (e.g. fractional, channelized,
clear channel, checksum on/off, etc.). T1 and E1 signals are precisely repeated using a
clock locked to the incoming line. In case of signal interruption at the source, no additional
resynchronization is required at the Flanger4Plus device level. No special setup is needed
to enable such things as fractional T1; whatever is impressed upon the T1 connection at
one end appears unchanged at the other.
Network Connectivity
Flanger4Plus can be deployed across a networked environment using wireless broadband,
wired Ethernet, or a combination, as long as the requirement for MAC-layer transparency
is met, and there are no competing bandwidth demands. This is most easily met by a
private, dedicated radio system, or by a private LAN. Channel LookAhead continuously
estimates the variation of arrival time; in conjunction with the Programmable Channel
Optimization feature, the Flanger4Plus system can deliver optimum reliability under
changing network conditions.
Flanger4Plus transports the full DS1 bandwidth (1.544 Mbps T1 or 2.048 E1) plus 256
Kbps of overhead in each direction constantly, thus occupying a total of 3.4 Mbps per T1
and 4.3 MB over E1.
When used with a wireless IP system, the Flanger4Plus provides T1or E1 transport across
distances limited only by the wireless system. It is an ideal, affordable solution for
connecting PBX systems in remote office and campus environments. The Flanger4Plus
can also supplant wire-line backhaul connections to cellular towers, eliminating monthly
leased landline charges as well as the associated problems.

Typical Deployments
One common application involves the interconnection of Private Branch Exchanges
(PBXs) in multiple locations. Connected as shown in the figure below, Flanger4Plus links
can provide excellent service and reliability at a fraction of the cost of leased DS1 circuits.
Figure 1 Remote PBX
Another application, shown in the figure below, is that of connecting cellular telephone
base station sites to the Mobile Telephone Switching Office. In this situation,
Flanger4Plus units can be the key not only to substantial cost savings, but in enabling a
completely independent and maintainable network.
Figure 2 Cellular Backhaul

2. Getting Started
Your Flanger4Plus set is pre-configured by the factory to work without requiring any
installation configuration. The Flanger4Plus set contains the following items:
Two (2) Flanger4Plus units pre-configured as pair, with one unit set to
determine DS1 clock from the telecommunications equipment connected to
port 1 (‘Mode 2’), and the other to determine clock from its partner (‘Mode
3’).
Two (2) external power supplies with Power Blockers
Two (2) Flanger4Plus Power Supplies
Two (2) Flanger4Plus Power Cords
Flanger4Plus Quick Start Manual
License Agreement
Section Contents
Identifying Your Flanger4Plus
Supported Radios for Power over CAT5
Understanding the Front Panel
Understanding the Back Panel
Making Connections
Understanding Factory Default Configurations
Product Support

Identifying Your Flanger4Plus
A Flanger4Plus unit can be identified by the product label attached to the bottom of the
unit. The label identifies the type of Flanger4Plus unit and its serial number, as illustrated
below:
Flanger4Plus serial numbers use hexadecimal

numbers. The values correspond to the assigned
MAC address for the WAN port for your unit.
Supported Radios for Power over CAT5

Radios Power
Alvarion Radios 56V
Pins: 4 & 7 Power (+) 5 & 8 Power (-)
Motorola Canopy Radios 24V
Pins: 4 & 5 Power (+) 7 & 8 Power (-)
Understanding the Front Panel

The front panel has one status indicator light.
The status indicator LED is used to display the overall condition of the Flanger4Plus unit
as follows:
Front Panel LED Meaning
Blinking Orange WAN Link down
Alternating Orange and Red Partner not found
Alternating Orange and DS1 line error – not receiving from
Green remote
Solid Green Very Good to Excellent System
Performance
Blinking Green Acceptable to Good System Performance
Alternating Red and Green Poor System Performance
Blinking Red Very Poor System Performance
Solid Red Hardware Fault
Off No Power

Understanding the Back Panel
WAN Connects Flanger4Plus to the dedicated network used for

(Power Out) communications between a pair of Flanger4Plus units.
LINK – Link is present. Blink indicates activity.
100 – Ethernet port operating speed. OFF indicates 10 MB, ON
indicates 100 MB.
Caution – This port supplies power output via Power over CAT5.
If the device you are connecting to the WAN port is not
supported or you don’t need power, you must use the supplied
power blocker to remove power from the port, or make custom
cables removing wires 4, 5, 7 and 8.
ATTENTION- Cette prise fournit une sortie de courent via POWER
sur CAT5. Si l’equipment que vous connectez à la prise WAN n’est
pas conforme ou vous n’avez pas besoin de courent, Vous devez
employer le bloque courent pour eliminer tout courent de la prise, ou
employez le cables particuliers en enlevant les cables 4,5,7,et 8.
LAN Allows a locally connected PC to access the Flanger 4Plus and connected
equipment. It is possible that large amounts of traffic through this port can
interfere with proper operation.
SPEED – Ethernet port operating speed. OFF indicates 10 MB,
ON indicates 100 MB.
DS1 Up to four DS1 lines may be connected to these ports. Note that there
may be unused ports for your configuration.
LINK – Lit when a DS1 signal is present and the port is enabled.
ACTIVITY – Blinks when the signal represents valid DS1 data.
Local Connects Flanger4Plus to a local area network via the Flanger4Plus power
(Power In) supply.
100 – Ethernet port operating speed. OFF indicates 10 MB, ON
indicates 100 Mb.

Making Connections
1. Locate each Flanger4Plus unit in an area where AC power, the Ethernet connection
to the external dedicated wide area network (WAN), and the local equipment DS1
connections are all available.
2. Use a CAT5 Ethernet cable (blue shown) and connect the external power supply to
each Flanger4Plus unit’s Local port. Plug in the Flanger4Plus power supply to an AC
power outlet. The front panel status indicator will light as described on the previous
page.
Note that the power supply’s male CAT5 connector DOES NOT have
Power over CAT5 and can be connected directly into other equipment.
3. (Optional) Connect the Flanger4Plus to your company’s LAN Ethernet network or to

a local PC via the male Ethernet cable. The Local Port Link indicator will light when
there is active Ethernet signaling.
4. Connect the WAN Ethernet network via a CAT5 Ethernet cable to each Flanger4Plus
unit’s WAN port. The WAN LINK indicator will light when there is active Ethernet
signaling.
Equipment connected to the WAN port WILL BE damaged if the device does
not support Power over CAT5. Use the supplied power blocker or custom
cables to prevent trouble!
L’equipment connente` au WAN sera endommage` s’il n’est pas conforme à
POWER sur CAT5. Employez le bloque courent fourni ou es cables particuliers
pour prevenir des problèmes.
5. Connect each local equipment DS1 port to an equipped Telco port on the
Flanger4Plus. In most cases the DS1 cable needs to be a cross-over. The port’s
ACTIVITY indicator will light when there is DS1 link activity and the port is
enabled.
Note that a DS1 crossover cable is DIFFERENT than an Ethernet

crossover cable. Refer to the DS1 with RJ-45 Cable Diagrams section
for details.

15
t
t
ou
ou
r
Example Interconnections
we
we
Po
Po
Power in
LAN LAN
Flanger4Plus Flanger4Plus
Power Supply Power Supply
For build 62209 and later

Understanding the Power Supply
Flanger4Plus uses Power over CAT5 to supply power to the Flanger4Plus and WAN-
connected equipment such as a wireless broadband modem.
WAN Port Power Out: Wires 4, 5, 7 and 8 are carrying power from the
Flanger4Plus to power the radio.
LAN Port No Power: The LAN port is a standard 10/100 ethernet port.
Local Port Power In: Wires 4, 5, 7 and 8 are carrying power from the power
supply to power the Flanger4Plus. Observe the warning tag on the
power supply when connecting.
Equipment connected to the WAN port WILL BE damaged if the device

does not support Power over CAT5. Use the supplied power blocker or
custom cables to prevent trouble!
L’equipment connecte` a la prise Wan SERA ENDOMMAGE` s’il ne
tolere pas POWER sur CAT5. Employez le bloque courent fourni ou les
cables particuliers pour prevenir des problèmes.
The supplied power blocker is a CAT5 coupler that internally has the wires connecting
pins 4, 5, 7 and 8 removed so that power is not supplied when it is installed.

Understanding Factory Default Configuration
Note that Flanger4Plus units are always shipped in pairs. The units are intended to be
connected together at their Wide Area Network (WAN) ports via dedicated Ethernet, such
as wireless broadband.
A managed “wayside data” path is available between the two units LAN ports using
available bandwidth on the interconnecting link over and above that needed for DS1
transport.
Flanger4Plus User Interface

Configuration and device status can be accessed via HTTP (Web interface) or Telnet, via a
PC connected to any port of the 2 devices.
Telnet login: admin Default Password: admin
MAC Addresses
Each Flanger4Plus ships with two MAC addresses. One MAC address is for the Local
port, which is listed on the product label, and a second is for the WAN port. The WAN
MAC address is of the form 000C9E-07-xxxx, while the Local MAC address is 000C9E-
06-xxxx, where the xxxx is the same for both the WAN and LAN ports.
IP Defaults
Flanger4Plus units are shipped in pairs and although they may sometimes have sequential
serial numbers, there is no requirement they do. The table below lists the default factory
configuration for IP.
Unit with lower serial # Unit with higher serial #
Local WAN Local WAN
IP 192.168.1.1 169.254.1.50 192.168.2.1 169.254.1.60
Subnet 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0

Gateway 0.0.0.0 169.254.1.50 0.0.0.0 169.254.1.60
Remote IP 169.254.1.60 169.254.1.50
Speed/Duplex 100 MB / Auto 100 MB / Auto
DS1 Timing Control

The Flanger4Plus supports five DS1 clock modes on a per-channel basis.
Mode 0 – Derive clock from this DS1 line
Mode 1 – Flanger4Plus generates clock internally
Mode 2 – Derive clock from local DS1 line #1
Mode 3 – Derive clock from remote DS1 line #1
Mode 4 – Derive clock from remote this DS1 line

Profiles
The TDM CONFIGURATION area includes programmable profiles that set the
operational parameters for the Flanger4Plus. These parameters are used to achieve optimal
performance for the link used. The Flanger4Plus ships with a pre-loaded profile for
Ethernet networks. Additional custom profiles may be created by the user. .
DS1 Defaults
Unit with lower serial # Unit with higher serial #
Bit Clock Mode 2 – DS1 Line Mode 3 – Remote Global Sync

Source
Encoding B8ZS/HDB3
Method
Transmit As ordered: E1 Short Haul
Template
Profile ETHERNET-100
Safety Factor = 10%
Max Rate = 100 MB MTU = 800
Wayside Timeout = 5 secs Timing Pulse = No
FEC = No Jitter Buffer = 8192
Payload Size = 1024 Min Gain = 0.2000
Jitter Window = 75 Stability Factor = 100
Max Step = 0.050 Integrator = Yes
Loops = 240 Final Sample Size = 1
Wayside TOS = 0 Flanger4Plus - Flanger4Plus
Channel 1 TOS = 16 TOS = 0
Channel 2-4 TOS = 0 Channel 1 Alt TOS = 0
Channel 2-4 Alt TOS = 16

Features and Specifications
Communications Ports
Three 10/100base T; meets IEEE 802.3
Four T1/E1: RJ-45; meets ANSI T1.403, ITU-T G.703; AT&T TR-62411
Visual Status Indicators (LED)

Front Panel: STATUS (front panel for overall unit operating condition)
Back Panel: Local, LAN and WAN Ethernet Link Speed (10/100)
Local, LAN and WAN Connection / Link Activity
DS1 (1,2,3,4) Signal Present
DS1 (1,2,3,4) Activity
Physical
5.5 in x 7 in x 2.3 in ; 14 cm x 18 cm x 5.9 cm
0.8 lb; 0.36 kg
Power Input
In-line “brick” power supply provides 56 VDC to unit; requires 100 to 260 VAC, 47 to 63
Hz, 24 Watts
Environmental
Operation: ETS 300 019 part 2-3 class 3.2E
Transportation: ETS 300 019-2-2 class 2.3
Storage: ETS 300 019-2-1 class 1.2E
EMC
FCC approval Title 47 Part 15, subpart B
ETSI EN 301 489-1 class B
Safety
CE approved
Contact your provider for the latest copies of documentation and utilities.

Product Support
We suggest you take the following steps in the order given to obtain the quickest and
highest quality support and service you need.
1. Contact the support staff of our Partner from whom you originally bought our
equipment for more information as well as any updates.

3. Configuration Considerations
Your Flanger4Plus unit is pre-configured by the factory to default settings appropriate for
TI or E1 short haul applications across both wireless and wired networks.
For other applications, you can change the Flanger4Plus configuration by either changing
board switch settings or using the Flanger4Plus Utility.
Section Contents
Setting Destination Flanger4Plus Addresses
Standard Clock Configuration
Special Clock Configurations
Using Equalizer Control Settings
Optimizing Performance for Various Networks

Network Settings
The default IP settings for Flanger4Plus are listed in the ‘Quick Start’ section earlier. If
your network design requires other addresses, they may be changed from the control web
page. The following section is an example of one such change.
Setting Flanger4Plus Addresses

Flanger4Plus units are pre-configured as a pair at the factory and sold bundled together.
Flanger4Plus units are factory configured to pass any DS1 line data over a WAN Ethernet
link.
If you want to configure a different Flanger4Plus unit to replace an existing unit in your
network, you need to reconfigure both units’ WAN Destination IP Address.
Step 1: Configure computer network settings to allow communication with the Flanger4Plus
LAN port.
Step 2: Connect a CAT-5 Ethernet cable from the Flanger4Plus unit’s Local port to the
computer’s Ethernet port.
Step 3: Open the Flanger4Plus unit’s webpage by typing the unit’s Local port IP into a web
browser.
Step 4: Mouse-over Configurations and select Ethernet.
Step 5: In the Destination IP Address field, type the paired unit’s WAN IP.
Step 6: Left-click on “Save Settings”
Step 7: Repeat steps 1-6 for the paired unit.

Selecting the DS1 Clock Mode
The clock used to send bits out the DS1 interface (from the Flanger4Plus to the connected
telecommunications equipment) comes from one of 5 choices:
Mode 0. The clock recovered from the local DS1 used in the packetizing sequence
is also used to transmit the bits that the Flanger4Plus receivers from the other end
of the system (from its partner Flanger4Plus). In this way, the Flanger4Plus that is
located at the timing source point presents consistent information to the DS1
system.
Mode 1. The Flanger4Plus’s internal clock is used as the reference.
Mode 2. The clock recovered from the local DS1 line #1 used in the packetizing
sequence is also used to transmit the bits that the Flanger4Plus receives from the
other end of the system (from its partner Flanger4Plus). In this way, the
Flanger4Plus that is located at the timing source point presents consistent
information to the DS1 system.
Mode 3. In this mode, the Flanger4Plus synchronizes its clock to the clock in use
at the transmitting end from remote DS1 line #1, by using a sophisticated digital
filtering process and information gained from the level of the jitter buffer.
Mode 4. In Mode 4, the Flanger4Plus synchronizes its clock to the clock in use at
the transmitting end from the remote DS1 on a per channel basis, by using a
sophisticated digital filtering process and information gained from the level of the
jitter buffer.

Clock Recovery
Mode 3
In Mode 3, the Flanger4Plus incorporates a series of unique mechanisms. As each DS1
packet is received, the level of the jitter buffer instantaneously is recorded. This
measurement then is inspected and valued to lie within the ‘expected’ or ‘normal’ range for
the Ethernet path in use. If the value is outside the ‘expected’ range (i.e. an ‘outlier’), it is
not used in the timing calculation. If the value is in the ‘expected’ range, its value is added
to the averaging register.
When the register collects enough timing samples to satisfy the next-stage filter algorithm,
this ‘sample estimator’ is passed to the oscillator adjustment routine.
This scheme delivers an estimate of the ‘most probable’ buffer level. Because it is not an
average, the system is insensitive to packets that take much longer to arrive; thus, delays
from congestion or radio error do not cause significant variation in the recovered clock
rate.
All channels in Mode 3 derive their timing from the remote unit’s first channel. In this
mode, all channels are expected to operate from the same clock reference.
Mode 4
In Mode 4, the Flanger4Plus operates as in Mode 3, but each channel is independent of
each other allowing each channel to operate at independent clock rates.

When to use Mode 2 to Mode 3 Pairs
Use a Flanger4Plus Mode 2 / Mode 3 pair when connecting network equipment that
provides its own stable timing source to remote equipment that recovers timing from the
received DS1 signal.
The Flanger4Plus Mode2 unit is connected to the network equipment and the Flanger4Plus
Mode 3 unit is connected to the remote equipment.
( Note: This is the factory default configuration for a Flanger4Plus pair.
When to use Mode 2 Pairs

Use a Flanger4Plus Mode 3 pair configuration when connecting between network
equipment that is timed from a mutual source.
Clock
Clock

When to use Mode 3 Pairs
Use a Flanger4Plus Mode 3/Mode 3 pair when connecting between network equipment
that has its own stable timing source.
Using Equalizer Control Settings

Equalization settings are used to match the DS1 analog front end to the length and
characteristics of the cabling connected between the Flanger4Plus unit and other TDM
equipment.
Short haul settings are used in an intra-office installation. For short haul T1 installations,
the EQ settings are directly determined by the cabling distance between the Flanger4Plus
and other equipment. For short haul E1 installations, there is only one EQ setting choice.
Long haul settings are used in an interoffice installation. For long haul T1 applications, the
EQ settings are based on the amount of cable attenuation between the Flanger4Plus and
other equipment. For long haul E1 installations, the “120 Twisted Pair” setting should be
used.
Optimizing Reliability for Various Networks

Making a Packet
The LIU sends bits to the packetizing buffer, where these bits will remain until there are
enough bits to fill the configured DS1 packet size. When enough bits are collected, the
buffer prepares a packet header, buffer pointers, and line indicators. After this preparation,
the checksums are added, the packet is formed, and the packet is presented to the WAN.

Pointer Calculation
Pointers are included in the header of each DS1 packet. They are created by the
transmitting side and read by the receiving. Pointers are models of the receiving end’s
buffers that present directions to where transmitted packets should be received. In
Flanger4Plus, they are calculated in one of two ways, depending if Forward Error
Correction (FEC) is enabled.
If FEC is not enabled, each packet begins immediately following the previous packet’s last
received byte. If FEC is enabled, each packet begins at the midpoint of the previous packet.
In effect, two copies of each DS1 data bit are transmitted – the packet is duplicated: half in
the preceding packet and half in the following packet.
Note that using FEC, in combination with the ‘pointer passing’ mechanism, makes the DS1
system independent of packet order changes, lost packets, or extreme delay of any one
packet (in a sequence of 3). Thus, enabling FEC makes the system much less sensitive to
channel errors and widely varying channel delays, allowing for much smaller delays.
However, greater data throughput is also required.

The Buffering Mechanism
The Ethernet channel delivers DS1 data packets to the receiving Flanger4Plus. There, the
depacketizer verifies the packet header, reads the buffer pointer, and places the packet into
the jitter buffer beginning at the place specified in the pointer.
In addition to the packet header, buffer pointer, and jitter buffer, there are three additional
key registers in the receiver.
Jitter Buffer Size
Read Pointer – Tells the DS1 output system where to get the next byte to
convert to DS1.
Level Counter – Indicates how many data bytes have been received since
system reset. This counter is only valid during the startup sequence (i.e. from
reset to DS1 data flow out the Flanger4Plus).
On a more specific level, the start sequence is the following:
1. The user resets the receiver system.
2. The first packet is received from the Ethernet interface;
3. The first packet’s ‘read pointer’ is set to its own pointer address. The packet is
frozen;
4. The bytes in the packet are put into the jitter buffer as defined by the pointer. The
‘level counter’ records the increments as the bytes are put into the buffer;
5. When the packet’s last byte in put into the buffer, the ‘level counter’ is checked to
see if ½ or more of the ‘buffer size’ is used. If there is less than ½ used, the receiver
will keep the ‘read pointer’ frozen (from step 3) and return to step 4 for the next
packet.
6. When the ‘level counter’ reads as ½ or more full of the ‘buffer size,’ the ‘read
pointer’ is freed and the DS1 output is turned on.
Note that this process always results in an integer number of packets in the
buffer at the start of the DS1 output.
When FEC is enabled, the ‘level counter’ increments once every received 2
bytes.

Optimizing Performance for Various Networks
Delay consists of 4 components.
1. Flanger4Plus Logic – The delay due to the inherent processing delay in
Flanger4Plus (i.e. how long the Flanger4Plus logic takes).
2. Packetizing Delay – The time the Transmitting Flanger4Plus takes to assemble a
full DS1 data packet.
3. Link Delay – The time it takes to transmit the packet from the Transmitting
Flanger4Plus to the remote Flanger4Plus via the WAN link.
4. Buffering Delay – The time allowance for variations in the WAN link.
Flanger4Plus Logic
This delay is less than 10 microseconds, an insignificant delay when compared to other
wireless broadband system elements.
Packetizing Delay
Packetizing Delay is computed as follows:
Packetizing Delay = Bytes per packet * 8 ÷ DS1 bits per second.
The following table shows some examples of packet delay by packet size.
Line Rate Packet Size Packetizing
Delay (ms.)
1,544,000 T1 1024 5.31
2,048,000 E1 1024 4.00
1,544,000 T1 724 3.75 Recommended
2,048,000 E1 960 3.75 Recommended
Link Delay
The link delay is dependent on the WAN’s wireless link. It has three components.
Ethernet wire (multiplied by two to account for both ends)
“In the Air” delay; i.e. propagation time
Wireless Protocol delay

Wire Delay
This delay is given by:
Wire Delay = (TCP/IP overhead bits + DS1 payload bits) / line rate
The following table shows some examples of wire delay at various packet sizes.
DS1 Packet Overhead Link Speed
Size Bytes Mbps delay ms
1024 66 10 0.872
724 66 10 0.632 Recommended for Canopy and T1
960 66 10 0.8208 Recommended for Canopy and E1
1024 66 100 0.0872
724 66 100 0.0632
960 66 100 0.08208
Wire Delays for Various Packet Sizes
“In the Air” Delay

Propagation time is due to the speed light -- about 5.5 microseconds per mile (3.4
microseconds per kilometer) of path length, an insignificant delay when compared to the
other delay elements.
Protocol Delay
The protocol delay must really be separated into two more components – the average
delay, and the delay variation. In fact, it is this delay variation that we must consider most
carefully when the final calculation s made – that of buffering delay (commonly called
jitter buffering, but properly de-jitter buffering). First and simplest, the average protocol
delay is usually well understood by the manufacturer of the wireless equipment. Some
typical values are given in the table below.
Equipment Type Average Protocol Delay in ms
Canopy Backhaul 20 3.75
Canopy Backhaul 20 3.75
Canopy Advantage Multipoint Downstream 3.75
Canopy Advantage Multipoint Upstream 5.5
Orthogon 60 4.5
Orthogon 300 5
Average Protocol Delays for Various Equipment Types

Delay Variation
Delay Variation is the most complex item to evaluate in a TDMoIP network. In a wireless
network in particular, there is a substantial coupling between delay variation and link
reliability; the way the link responds to transmission impairments has a large effect on
delay, and characteristic of that effect depends on the error mitigation strategy
implemented on the link. There are basically 3 strategies in common use today, as follows:
1. Fragmentation and reassembly, with Automatic Repeat-reQuest (ARQ) covering
each of the fragments. This may be implemented with or without Forward Error
Correcting (FEC) coding on the fragments.
2. Internal Repeat of the entire packet, again with or without FEC. In this case, the
wireless equipment itself repeats the packet if it is not received correctly.
3. Reliance on the retry mechanism of TCP/IP, usually with FEC on the packet. In this
case, the (on the order of seconds) retry mechanism of IP is relied upon to provide
any link reliability improvement over that of the raw radio channel, although the use
of FEC (as in WiFi and WiMax) can make that fairly good.
Link Verification
In order to make the problem of evaluating any particular link more tractable, Flanger4Plus
includes a special tool for measuring the statistics of the link delay variation. During
normal operation, Flanger4Plus in Mode 3 or 4 takes a sample of the instantaneous link
delay every 100 ms, and compiles a histogram. This histogram is available at the console
port a TelNet connection to a PC, and is used by the Flanger4Plus itself in making clock
synchronization decisions. The data in the next section was taken with the aid of this tool.

Example Link Delay Measurements
For the first example, a type ‘a’ system will be examined. Below is a histogram of the
measured values on a particular 10Mbps radio link. Note that horizontal (x) axis is
normalized, where “0” represents the ‘average’ delay of 3.75 ms. Notice the fairly slow
dropoff as times get longer – at .001% probability, the normalized delay is about 3.5 ms.
This is a very good link.
100
10
1
Probability, %
percent
0.1
cumulative
0.01
0.001
0.0001
-2 -1 0 1 2 3 4
Normalized Delay, ms
Delay Histogram for Radio Link ‘A’
In this case, an arriving fragment with errors at the receiver is retransmitted 1 or 2 frames
later. This affects (64 byte) fragments by delaying the entire Ethernet packet by the delay
of the frames (2.5 ms / frame). Very occasionally, the retransmission itself may be lost. In
this situation, another 2.5 or 5 ms may be added to the delay.
There also is a uniformly-distributed delay due to framing. The delay varies (with a
constant incremental probability) from 0.2 to 2.7 ms. This yields an average value of about
1.5 ms. It is these two values added together than make the ‘average’ delay of 3.75 ms used
in the example above.
In the next example, the same radios are examined with a poor link. Again, a histogram is
created in similar fashion to the previous example. In this case, normalized delays extend
out to 20 ms, raising suspicion that a significant number of packets were lost.

100
10
1
Probability, %
0.1
Cumulative
0.01
0.001
0.0001
0.00001
-5 0 5 10 15 20 25
Normalized Delay, ms
Delay Histogram for Radio Link ‘B’
How then, does this affect the DS1 link? Given that the average packet rate is about 200
packets per second (pps), the event rate is a rate of .001% (i.e. one packet per million,
about one packet exceeding this delay every 1 ⅓ hours, or 17 errored seconds per day as
long as the delay causes only a packet’s worth of bit errors), which is 20 ms on this chart.
This is why the way Flanger4Plus uses pointers is so beneficial. The pointer to each piece
of data is embedded in the transmitted packet. Then, if a packet is not received in time, the
receiver will keep sending. It will of course send errors bits for as long as the proper packet
doesn’t arrive; however, it will not lose clock information. As soon as the new packet
arrives, the proper information will be extracted and sent.

Overall Link Delay Budget
The figure below shows typical numbers for the Radio backhaul link in our example.
T1 E1
Avg Avg
Packets Bytes ms Packets Bytes ms
Processing Delay 0.01 0.01
Packetizing Delay 730 3.78 960 3.75
Ethernet Delay 730 0.64 960 0.82
Delay 3.75 3.75
Propagation Time 0.10 0.10
Ethernet Delay 730 0.64 960 0.82
Jitter Buffer 4 5110 15.13 3 4800 11.35
Processing Delay 0.01 0.01
Net Delay 24.06 20.61
Overall Delay for Example Radio Backhaul Link
Bandwidth Considerations
Flanger4Plus’s Unique FEC
If FEC is activated, each bit is sent in two different packets. The probability of two
packets in sequence being delayed or lost is much lower than in the normal case.
Note: If you are using FEC you should be sure to set the Payload Size specified in your
profile to 720 bytes or less.
Profile Considerations
The purpose of profiles is to provide a means for Flanger4Plus to know how to best utilize
the WAN connection. Profiles optimize DS1 bi-directional data transfer performance for
the connected WAN. They also set Flanger4Plus system-wide operating parameters,
influencing the DS1 accuracy tolerance and available network bandwidth that Flanger4Plus
will utilize.
With the vast market of T1 / E1 radios available, there is a large variation as to how each
radio performs best. Flanger4Plus solves this problem through the use of “profiles.”
Correct and effective profile use allows for matching the behavior of the radio to that of
Flanger4Plus.
For your convenience, the Flanger4Plus has been tested and have some factory-defined
profiles. These profiles can be identified by their names, which describe the Make,
Bandwidth, and Operating Path. These profiles can be found in the DS1 Configuration web
page. For information on how to use the web pages, refer to Using the Profiles page
located in this document.
If you are using a radio different than any described in Flanger4Plus’s factory-defined
profiles, you will need to determine the radio’s optimal settings on your own. It is a time-
consuming process, yet it is vital that you properly test operability at different profile
values to determine the best profile for your radios. Radios are sensitive to slight variances
in how they receive and transmit data. The slightest difference between radios and
Flanger4Plus operation can build over time to produce an unreliable network.

When experimenting with different profiles, keep the following considerations in mind:
1. Name – Name your profiles so that you can easily distinguish how one profile
differs from others... Profile names can use any ASCII character except space.
2. Maximum WAN Rate – This number is the bandwidth capability of your radio, or
it is the amount of bandwidth you want to make available to the Flanger4Plus.
3. FEC – (Forward Error Correction) FEC is a highly reliable method of transferring
DS1 streams because it compensates for transfer errors. FEC doubles the
bandwidth requirements on the network, so only use FEC if the WAN can support
it.
4. Safety Percentage – No network actually operates at the bandwidth it theoretically
can handle. The safety percentage allows you to compensate for this by
discounting a percentage of the Maximum WAN Rate from the amount of
bandwidth available for Wayside Data.
5. Wayside Timeout – This number is the maximum time in seconds that a wayside
packet will remain queued for the WAN. When a queue times out (expires), the
packet will be dropped (i.e. it will not be sent).
6. Payload Size – Defines the size in bytes of packets that will be sent through the
WAN.
7. Jitter Buffer Size – Defines the size in bytes of the buffer used to store T1/E1 data
received from the WAN. As jitter buffer size increases, the latency increases, and
the tolerance to jitter increases.
8. Jitter Window Size – Used by the clock recovery algorithm in the unit.
9. Queue Timeout – Determines the amount of time in seconds before the equipment
drops or discards a queued packet and reports it as an error.
10. Maximum Transmission Unit – (MTU) Sets the largest packet size the equipment
will introduce to the network. Ideal MTU is the smallest packet size the network
equipment will send reliably.
11. Minimum Clock Recovery Gain – Used by the clock recovery algorithm of the
unit.

4. Configuring Flanger4Plus
Although your Flanger4Plus unit is pre-configured to defaults appropriate for most
applications, for special circumstances, your Flanger4Plus unit can be configured to set the
following values:
Destination IP Address
Clock Mode
Optimization Settings
Equalizer Control Settings
Section Contents
Accessing the Flanger4Plus Unit
Viewing Unit Information
Changing Configuration
Managing Profiles
System Reset

Accessing the Flanger4Plus Unit
In order to configure a Flanger4Plus unit, use your favorite Web browser program to
access the Flanger4Plus’s web site by typing the IP address of either the Flanger4Plus
Local or WAN Ethernet port to that your computer’s Ethernet port is connected.
The Flanger4Plus front page is the System Status page that is illustrated below. The
System Status page provides an indication about the current operational status of the
Flanger4Plus.
System Status
Flanger 4 Plus Displays the current front panel status LED state for the
(local) connected Flanger 4 Plus.
Flanger 4 Plus Displays the current front panel status LED state for the
(remote) connected remote Flanger 4 Plus.

WAN Displays the WAN port link information.
LAN Displays the LAN port link information.
Local Port Displays the Management port link information.
Wayside Displays the calculated wayside data capacity.
Throughput
TDM Channels Displays LOS and activity information for each of the DS1 ports
of the unit. When each channel attains clock synchronization,
the internal color of the connector changes from gray to green.
By default the System Status page is configured to automatically refresh so that accurate
information is always displayed. The refresh timer is shown in the upper right corner of
the status frame.
The following fields are display only and contain Flanger4Plus unit information. Each field
and its use is described below.
Build Display-only field containing the release build revision number.
Software Display-only field containing the Software revision number.
Version
Shapeware Display-only field containing the FPGA revision number.
Version
CPLD Version Display-only field containing the CPLD revision number.
Hardware Display-only field containing the printed circuit board revision number.
Revision
Serial Number This is the MAC address of the Local port on the Flanger4Plus.

Using the Menu to Navigate
The Flanger4Plus Web Site has a main menu that can be used to:
Access the HOME PAGE
View the unit information
Configure the Flanger4Plus unit
View Reports
Some menus have additional details below the top-level designator. These details are listed
below.
System Status
System System Reset
System Update
System Upgrade
WAN Radio
DS1 Operation
Configuration DS1 Remote Target
DS1 FEC
DS1 Diagnostics
Ethernet
Radio
TOS
Profiles
SNMP
Error Reporting
DS1 Statistics
Interface Reports Wan Statistics
Management Port Statistics
Configuration
System Reports System Status
Problems
Profiles
ARP Statistics
Misc Reports ICMP Messages
IP Statistics
IP Routes
Packet Queue
Sockets
SNMP Statistics
TCP Connect
TCP Receive
TCP Transmit
UDP Statistics
Web Server

Login to the Web Server
The User name is “admin” the default password is “admin”.

Using the System Reset and Recover page
You may choose to reboot the Flanger4Plus after configuring or for other reasons. Reboot
will temporarily stop communication between Flanger4Plus units. A person at either end
will loose service at this time period. The reboot takes 20 seconds or less.
( If you power off your radios alongside rebooting the Flanger4Plus, recover may take
longer (because the radio may take longer to reboot).
To reboot the Flanger 4 Plus, left-click “Reboot the Flanger 4 Plus.” The Flanger 4 Plus
will now reboot and recover in 20 seconds or less. Wait until the home page loads to make
any other changes or look at new things.
To recover default settings while either keeping or discarding custom profiles and the
current username and password, left-click the “Recover default settings on the Flanger 4
Plus.

System Upgrade
To enable additional ports and features of the Flanger 4 Plus units, the upgrade key
provided by your reseller must be input in the dialog box.

Changing Configuration
Using the DS1 Configuration page
Global Settings
The Global Configuration settings apply to how the Flanger4Plus unit operates.
Line Type This field selects the DS1 line type (T1 or E1).

Individual Channel Settings
Individual Channel Configuration settings apply to each Flanger4Plus DS1 channel
operates. Refer to the Changing Equalizer Control Setting section for information on
changing the values of these fields.
Channel The channel number (1…4). This is a display-only field.
Enabled Selects whether the channel is enabled.
Clock Source Selects the bit clock source being used for the channel.
Mode
Encoding Selects the DS1 encoding method being used for the channel.
Method
Transmit Selects the DS1 Transmit Template being used for the channel.
Template See table below for possible selections.
Function Pulse Cable Gain

T1 Short Haul 0-133 ft. 0.6 dB 100 TP 12 dB (default)
T1 Short Haul 133-266 ft. 1.2 dB 100 TP 12 dB
T1 Long Haul 0.0 d 100 TP 36 dB
T1 Long Haul -7.5 dB 100 TP 36 dB
T1 Long Haul -15 dB 100 TP 36 dB
T1 Long Haul 0.0 dB 100 TP 26 dB
T1 Long Haul -16 dB 100 TP 26 dB
E1 Short Haul ITU G.703 120 TP and 75 CX 12 dB (default)
E1 Long Haul ITU G.703 120 TP 43 dB
E1 Long Haul ITU G.703 120 TP and 75 CX 43 dB
Flanger4Plus Equalizer Control Settings

DS1 Remote Target
The IP information for the remote Flanger4Plus target is entered on this web
page. This is the target for the T1/E1 data as transmitted by the Flanger4Plus.
By default this is set to the partner unit.
DS1 Remote Target (Multipoint)
The IP information for the remote Flanger 4 Plus targets are entered on this web
page. This is the target for the T1/E1 data as transmitted by the Flanger 4 Plus.
By default this is set to the partner unit. The remote target channel can also be
programmed here.

DS1 FEC
If so equipped, the Forward-Error-Correction feature of the Flanger 4 Plus can be

enabled and disabled through this web page. Additionally the FEC data stream
can use a different profile.

DS1 Diagnostics
Each individual DS1 Channel of the Flanger 4 Plus can be programmed to

generate PRBS or QRSS patterns and to have a loopback feature enabled.
These features are meant for diagnostic purposes and can be monitored through
this web page. Rebooting the unit will clear all of the enabled diagnostic
features.

Using the Ethernet Configuration page
WAN Selects the maximum data packet size for the data passed between two
Management Flanger4Plus units.
Data MTU
IP Address Sets the WAN port address of the Flanger4Plus.
Netmask Selects the WAN port’s IP Netmask.
Gateway Selects the WAN port’s IP Gateway.

Using the Radio Configuration page
Max Rate Selects the Maximum Rate supported by the WAN link.
Safety Factor Percentage of the Max Rate number that is reserved for WAN link
variation
IP Address Selects the WAN port target IP range
Speed Duplex Selects the LAN port’s Speed / Duplex options.

Using the TOS Configuration page
This web page is used to set the IP TOS priority for the Flanger4Plus management data, wayside
data, and each TDM channel.
Management Data This field specifies the IP header TOS value to use for
TOS Flanger4Plus -to- Flanger4Plus management data across the
WAN.
Wayside Data TOS This field specifies the IP header TOS value to use for all
wayside data across the WAN.
Channel 1 TOS This field specifies the IP header TOS value to use for all
standard Channel 1 DS1 traffic.
Channel 1 Alt TOS This field specifies the IP header TOS value to use for all
alternate Channel 1 DS1 traffic. Note, alternate traffic is
only used when FEC is enabled.
Channel 2-4 TOS This field specifies the IP header TOS value to use for all
standard Channel 2, 3 and 4 DS1 traffic.
Channel 2-4 Alt TOS This field specifies the IP header TOS value to use for all
alternate Channel 2, 3 and 4 DS1 traffic. Note, alternate
traffic is only used when FEC is enabled.

Using the Profile Configuration page
This web page is used to create the profile that is applied to the TDM data stream.
Profile Name This field designates a profile by its name.

Payload Size This field specifies the number of octets to send as DS1 data
payload within an Ethernet packet.
Jitter Buffer Size This field specifies the size of the receive buffer. Refer to the
Optimizing Performance For Various Network section for
detailed information.
Jitter Window Size This setting is used by the Flanger4Plus clock recovery
software. Unless a custom profile has been developed for
you, it is recommended that this be left at its default value.
Minimum Gain This setting is used by the Flanger4Plus clock recovery
Max Step This setting is used by the Flanger4Plus clock recovery
Stability Factor This setting is used by the Flanger4Plus clock recovery

Loops per Gain This setting is used by the Flanger4Plus clock recovery
Cycle software. Unless a custom profile has been developed for
Use Integrator This setting is used by the Flanger4Plus clock recovery
Final Sample Size This setting is used by the Flanger4Plus clock recovery
Filter Length This setting is used by the Flanger4Plus clock recovery
Filter Width This setting is used by the Flanger4Plus clock recovery
Managing Profiles
A profile is a named combination of Packet Size and Buffer Depth values. Profiles are
provided for different tested network equipment. Users may also define their own profiles.
It is recommended that a profile be created for any optimized settings used in a production
environment.
Choosing the Custom profile selection allows the user to set the Packet Size and Buffer
Depth values directly. This is used primarily to test custom settings before adding a new
profile.
Copying a Profile
Select the profile to copy from the pull-down list.
Change the Profile Name to save as the copy.
Select Save Changes and the new profile will be added to your Flanger4Plus.
Creating a Profile
Select “< New Profile >” from the pull-down list.
Enter at least a new Profile Name. All other parameters are defaulted for you.
Change any other profile variables you want.
Select Add Profile and the new profile will be added to your Flanger4Plus.
Deleting a Profile
Select the profile to delete from the pull-down list.
Select Delete Profile and this profile will be removed from your Flanger4Plus.

Using the SNMP Configuration page
Get Community This is the name of the community that is allowed to perform get
commands from the unit
Set Community This is the name of the community that is allowed to perform set
commands from the unit
System Contact This is the name of who should be contacted about the unit
System Name This is the name of the unit as seen by the Network Management
System
System Location This sis a text field that can be used to describe the location of
the equipment to the Network Management System
Trap Target # Up to 5 traps can be targeted to different NMS addresses.
Trap Enabled Individual traps can be enabled or disabled.
Trap IP Address This is the target IP address that an individual trap message is
sent to.

Trap Community This can set whether the community that the unit is connected to
is read-only or read-write.
Using SNMP
Simple Network Management Protocol (SNMP) is used by network management systems to
monitor equipment for conditions that warrant administrative attention. SNMP consists of a set
of standards for network management, including an Application Layer protocol, a database
schema, and a set of data objects. SNMP exposes management data in the form of variables on
the managed systems, which describe the system configuration/status. These variables can then
be queried by a network management system.
The Flanger4Plus supports SNMP v1.0 and V2.C ‘get’ and ‘trap’ functionality only.
SNMP traps enable the SNMP agent firmware running in a Flanger4Plus to alert an SNMP
management station of pre-selected events by way of an unsolicited (asynchronous) SNMP
message. Selection of these trap events is accomplished via the SNMP Configuration page of the
unit’s web interface. The Flanger4Plus supports five different SNMP traps which can send trap
alerts to up to five different IP addresses.

Using the Error Reporting Configuration page
This web page is used to configure the manner and types of errors reported.
Track Out-of- When enabled the Flanger4Plus will track incoming Out-of-
Order Packets Order packets meant for the TDM processing engine. This
can be helpful when determining the quality of the link
between two Flanger4Plus units.
Use Remote When enabled, two Flanger4Plus units will communicate with
Flanger4Plus each other for status reporting.
Status
Report Automatic This time is used to determine the rate at which reports are
Refresh Rate automatically refreshed when a report web page is accessed.
Report Automatic This setting determines the number of times that a report web
Regeneration page will automatically refresh once it is accessed.
Channel Reporting This setting is used to determine the number of calculated
SES Limit Seriously Errored Seconds that will be allowed prior to
declaring a degraded operating condition.

Updating your Flanger4Plus
To update your Flanger4Plus units, follow the procedure that accompanies the upgrade files.

Understanding Flanger4Plus Reports
Description of Interface Reports
The Interface Reports show status and statistical data for the DS1, WAN, and LAN. They
help define the exact status of the system at any given moment. The reports are
automatically updated 10 times every 10 seconds. The interface statistics can be reset to
zero by pressing the corresponding interface RESET button.

Understanding DS1 Reports

Interface Status
Defines if the WAN / LAN interface is working. Values
Operation are either “up” or “down.”
Defines if the 46Mhz & 61Mhz clocks are working.
Values are either “Detected” or “Loss for X Sec,” where x
Clock Signals represents the number of seconds down.
Interrupts
Total number of packets completely received from the
Receive Ethernet port.
Total number of packets completely sent out of the
Transmit Ethernet port.
Received Packets from DS1

Good Packets Total number of packets the unit collected successful.
Dropped Packets Total number of packets the unit collected and discarded.
Packets with errors Total number of faulty packets the unit collected.
Missed Packets Total number of packets the unit failed to collect.
Missed Bytes Total number of bytes the unit failed to collect.
Transmitted Packets from DS1

Packets Total number of packets the unit sent.

Channel Status
Channel Defines the channel the values to the right are describing.
Defines if the line is active. Values are either “Yes” or
Signal Present “No.”
Equalizer in Range Reports the equalizer status of each T1/E1 line.
Timeclock Which source of clock is used by the Line Interface Unit.
Line Driver Reports the transmitter status of each T1/E1 line.
AIS Alarm Reports the reception of AIS alarms.
The number of errors reported from the Line Interface
Error Count Unit, per T1/E1 channel
DS1 packet errors from either the jitter buffer or FIFO that
Jitter Underflow result from queues released too early.
FIFO Underflow
Jitter Overflow result from queues released too late.
A queue that sends the packets it in the order it was
FIFO Overflow queued.
The estimated Error-Free-Seconds of up-time on each
Estimated EFS T1/E1 channel.
Estimated ES The estimated Errored-Seconds on each T1/E1 channel
The estimated percentage of Errored-Seconds to Error-
Estimated %ES Free-Seconds
Clock Var The calculated clock variation on a per channel basis.

Understanding WAN Reports

Interface Status
Defines if the WAN / LAN interface is working. Values are
Operation
either “up” or “down.”
Defines if the Master and Slave are communicating. Values
Ethernet Interface
are either “Established”, “Auto-Negotiated” or “Not
Status
Established.”
Defines at what speed and duplex the WAN is
communicating. Duplex values are “half” or “full.” If the
Speed / Duplex
speed / duplex is determined automatically, “Auto-negotiated”
will print on the top of the screen.
Interrupts
Receive Total number of packets received from the Ethernet port.
Transmit Total number of packets sent out of the Ethernet port.
Transmit Queuing
Total number of packets sent out of the Ethernet port and into
Current in queue the FIFO. This number is a snapshot of the moment the report
was taken.
Displays the largest historical value the queue ever was since
Maximum reached
last reboot.
Dropped due to Total number of packets dropped because they exceeded the
timeout (WAN only) configured time in the queue.
Packets
Received Total number of packets the unit received.
Received and
Total number of packets the unit received and discarded.
Dropped
Received with
Total number of faulty packets the unit received.
Errors
Received Unknown Total number of packets the unit received that could not be
Type identified.
Transmitted Total number of packets the unit sent.
Transmitted and Total number of packets queued to be sent and later discarded
Dropped for reasons other than errors.
Transmitted with
Total number of packets sent that failed in their transmission.
Errors

Description of IP Reports
IP reports show statistical data for each of the IP based protocols used by Flanger4Plus.
Reports are automatically updated 10 times every 10 seconds.
Understanding IP Reports
IP MIB Settings
Gateway Records if IP data is enabled to travel across the network.
Default TTL Records the maximum time a packet can stay on the network.

Receive
Total Total number of IP packets the Flanger4Plus unit has received.
Total number of IP packets received with errors in the beginning
Header Errors part of the IP packet’s frame.
Total number of IP packets received wrongfully due to wrong
Address Errors address.
Unknown Total number of IP packets received whose data format is not
Protocols recognizable.
Delivered Information only. No Company Support.
Send
Total number of IP packets that connected Flanger4Plus unit has
Total
sent.
Discarded Total number of IP packets dropped for any reason.
Total number of IP packets discarded because Flanger4Plus did
No Routes
not know how to deliver the IP datagram.
Routing
Total number of IP packets continued through the router toward
Forwarded
the destination address in the network.
Total number of IP packets dropped in the router instead of
Discarded
forwarding toward the destination address.
Segmentation and Reassembly

Received Total number of times IP packets that are sent in parts are
Fragments received.
Reassembled Total number of times IP packet fragments are received and

Complete pieced together to form a complete packet successfully.
Fragmented
Total number of times IP packets are divided into parts.
Complete
Total number of times an IP packet fragment is sent into the
Fragments Sent
network.
Fragments Total number of IP packet fragments that are not sent into the
Dropped network.
Reassemble Total number of times IP packet fragments are received and

Failures pieced together to form a complete packet without success.

Understanding ICMP Reports
Messages Total number of any ICMP messages (including errors).
Errors Total number of ICMP packets received in error.
Destination Total number of sent ICMP packets not received because the
Unreachable destination address cannot be found, is full, or is busy.
Total number of ICMP packet that exceeded the allowed

Time Exceeded
duration to stay in the network without delivery.
Total number of ICMP messages that indicate a lost datagram
Parameter Problem
due to incorrect packet parameters.
Total number of ICMP messages that indicate a discarded
datagram due to insufficient buffer space for queuing, receiving
Source Quench
a datagram too fast to be processed, or a host or gateway
approaching capacity.
Total number of ICMP messages that indicate a shorter pathway

Redirected is available for datagrams whose source routes and gateways are
not defined in the destination address.
Echo (ping) Total number of ICMP request messages that must be returned.
Echo Replies Total number of ICMP responses to an echo.

Total number of ICMP messages that indicate when data was
Time Stamps
last handled upon receipt.

Time Stamp Total number of ICMP messages that indicate when data was
Replied last handled before transmission.
Total number of ICMP messages requesting IP information via
Address Masks differentiating the subnet part of the IP address from the other
parts.
Address Mask Total number of ICMP messages responding to an address mask
Replies request.

Understanding ARP Table Reports
Total number of times Flanger4Plus processed an ARP request

Requests
message.
Total number of times Flanger4Plus processed an ARP reply
Replies
message.
Total number of times an ARP request times out because no reply
Request Retries
was received. A request times out after 3 seconds without a reply.
Total number of times an ARP request fails to receive a reply after
Request Failed
three attempts.
Total number of times an ARP reply was generated from the ARP
Cache Hits
table entry that is cached.
Total number of times an ARP reply was generated from the ARP
Cache Misses
table entry that is not cached.
Total number of times an ARP request is satisfied by an entry in the
Table Hits
ARP table.
Total number of times the table has filled with information. No
Table Full
additional entries can be saved while the table is full.

Total number of ARP table entries that exceeded their time limit in
Table Timeouts
the table. Entries timeout after 15 minutes of no usage.
Packets Total number of ARP requests that do not generate a reply. This
Dropped statistics is all-inclusive for any message processing errors.

ARP Table
On the bottom of the ARP Statistics Page lies an ARP table
describing all requests and where the response information is stored.
[c] Only unique entries are recorded. If a “c” precedes any of the
listings on the table, it is stored in the cache. If a “c” is missing, the
listing is stored in the table.
IP Address Displays the IP address for which an ARP request was made.
Displays the MAC address in any given ARP request as
MAC Address
synonymous to a given IP address.
Displays the Interface designation that describes an IP or MAC
Interface
address during an ARP request.
Displays the number of ARP requests referring to the table or cache
Pending
without known success or failure.
Displays the amount of time an ARP reply has been stored in the
Age (sec)
table or cache.
Updated
Displays the last time the ARP table values were updated.
(sec ago)
Total number of ARP packets in the ARP table and the total number
Summary
of pending ARP packets.

Description of TCP/UDP Reports
Understanding UDP Reports
Datagrams In Total number of UDP datagrams delivered to UDP users.

Total number of received UDP datagrams for which there was no
No Port
application at the destination port.
Total number of received UDP datagrams that could not be
Datagram Errors delivered for reasons other than the lack of an application at the
destination port.
Datagrams Out Total number of UDP datagrams sent from the connected unit.

Understanding TCP Connection Reports
Connections
Initiated Total number of TCP links started.
Accepted Total number of TCP links known as valid.
Total number of TCP connection for which the current state is
Established
either Established or Close- Wait.
Total number of TCP Acknowledgement messages sent later
Delayed Acks Sent
than expected.
Dropped Total number of TCP initiations that failed.
Total number of failed TCP connections before connection
Dropped Embryonic
timeout.
Total number of TCP connections stopped for those that
Closed (inc. drops)
succeeded and failed in transporting a packet.
Round Trip Time

Total number of times the unit tried to record the roundtrip time
Attempts to measure (i.e. Transmitter to Radio Master to Radio Slave to Receiver to
Radio Slave to Radio Master to Transmitter).

Counts the number of times a round-trip time recording was
Successful Attempts
made successfully.

Timeout
Total number of times a previously dropped TCP connection is
Dropped Retransmit
attempted again.
Total number of times a failed TCP connection is attempted
Retransmit
again.
Persistent Information only. No Company Support.
Keepalive Information only. No Company Support.
Keepalive Probes Sent Information only. No Company Support.
Keepalive Dropped Information only. No Company Support.

Understanding TCP Receive Reports
Received
Total Packets Total number of TCP packets collected.
Total number of packets received in the order that the TCP
Packets in Sequence
sent them.
Total number of bytes received in the order that the TCP
Bytes in Sequence
sent them.

Total number of packets received in a different order than
Out-of Order Packets
that that the TCP sent them.
Total number of bytes received in a different order than that
Out-of Order Bytes
that the TCP sent them.
Total number of packets received after the maximum
Packets After Window
receive load.
Total number of bytes received after the maximum receive
Bytes After Window
load.
Total number of TCP packets received after a connection is
Packets After Close
closed.
Total number of packets sent to determine the size of the
Window Probe Packets
window before receiver overload.
Window Update Packets Information only. No Company Support.
Received With Errors

Total number of times the amount of TCP packets received
Bad Checksum Packets
was not the same as what was sent.
Total number of TCP packets that were too far apart from its
Bad Offset Packets
intended space in the sequence to recover.
Total number TCP packets received that were missing some
Short Packets
data.
Duplicate
Packets Total number of identical packets received.
Packet Bytes Total number of identical bytes received.
Partial Packets Total number of identical partial packets received.
ACK
Total Packets Total number of acknowledgment packets received.
Bytes Received Total number of acknowledgement bytes received.
Duplicates Total number of identical acknowledgment received.
For Unsent Data Information only. No Company Support.
Predictive Header Hits

Acks Information only. No Company Support.
Data Information only. No Company Support.

Understanding TCP Transmit Reports
Transmitted
Total Packets Total number of TCP packets sent.
Data Packets Total number of TCP Data packets sent.
Data Bytes Total number of TCP Data Bytes sent.
Total number of TCP packets sent that verified the TCP
Ack-only Packets
connection.
Total number of TCP packets sent to determine how many
Window Probes more packets could be sent to the Receiver without
overload.
Window Update-only Information only. No Company Support.
(SYNC|FIN|RST) Packets Information only. No Company Support.
URG only Packets Total number of TCP packets to be received with urgency.
Retransmitted
Total number of times any data packet is sent more than
Data Packets
once.
Total number of times any data bytes are sent more than
Data Bytes
once.

Description of System Reports
System Reports provide statistical data at the Flanger4Plus system level and overall system
health (status and problems). Reports are automatically updated 10 times every 10 seconds.
Understanding Packet Queue Reports
Packet Queues
Information about the system walking through each
Queue Walk Test
event in the Packet Queue.
Total number of Queues that can ever be handled by the
Total
system.
The number of Queues that are available at the time if
Available
the report.
Low Water Mark The lowest number of Queues that have been available

to the system.
Times Empty The times that the Queues have been empty.

Reassembly Buffers
The number of buffers reserved by the system for
Total
reassembly of packets.
The amount of time that the system allows for a packet
Timeout
to be held awaiting reassembly before it is discarded
Currently Used The number of reassembly buffers presently in use.
The largest number of reassembly buffers as seen by the

Maximum Used
system.
Stack Queue
The results of the system being able to service every
Queue Walk Test
Queue meant for the system.
The number of queues currently used and awaiting the
Currently Queued
system.
The maximum number of queues used and awaiting the
Maximum Queued
system.
WAN Packets
Pending Receive The number of WAN packets pending receipt.
Pending Transmit The number of WAN packets pending transmit.
The results of the system being able to service the

Queue Walk Test
entirety of the WAN queue.
Wayside Queued The number of Wayside packets queued by the system.
The maximum number of Wayside packets queued by

Wayside Max Queued
the system
LAN Packets
Pending Receive The number of LAN packets pending receipt.
Pending Transmit The number of LAN packets pending transmit.

Understanding Problems Reports
This report lists only conditions that are problems similar to the problems report. An
example is show below.
Problem Report
An overall system status report. Used as a
Status
troubleshooting aid.
DS1 Interface The status of the T1/E1 interface.
WAN Interface The status of the WAN interface.
Whether or not the remote unit can be communicated

Remote Unit
with.

Understanding SNMP Reports
This report lists the SNMP statistics as defined in RFC 1213.
The total number of messages delivered to SNMP

snmpInPkts
from the transport service.
The total number of SNMP messages which were
snmpOutPkts
passed from SNMP o the transport service.
The total number of SNMP messages which were
snmpInBadVersions delivered to the SNMP and were for an
unsupported SNMP version.
The total number of SNMP messages delivered to
snmpInBadCommunityNames SNMP which used an unknown SNMP
community name.
The total number of SNMP messages delivered to
SNMP which represented an SNMP operation
snmpInBadCommunityUses
which was not allowed by the SNMP community
named in the message.
The total number of ASN.1 or BER errors
snmpInASNParseErrs encountered by SNMP when decoding received
SNMP Messages.
The total number of SNMP PDUs which were
snmpInTooBigs delivered to SNMP and the value of the error-
status field is “toobig”.
snmpInNoSuchNames delivered to SNMP and the value of the error-
status field is “noSuchName”.
snmpInBadValues delivered to SNMP and the value of the error-
status field is “badValue”.

The total number of valid SNMP PDUs which were
delivered to the SNMP protocol entity and for which the
value of the error-status field is “readonly”. It should be
snmpInReadOnlys noted that it is a protocol error to generate an SNMP
PDU which contains the value “readonly” in the error-
status field, as such this object is provided as a means of
detecting incorrect implementations of SNMP.
The total number of SNMP PDUs delivered to SNMP
snmpInGenErrs and for which the value of the error-status field is
“genErr”.
The total number of MIB Objects which have been
retrieved successfully by the SNMP protocol entity as
snmpInTotalReqVars
the result of receiving valid SNMP Get-Request and
Get-Next PDUs.
The total number of MIB objects which have been
snmpInTotalSetVars altered successfully by the SNMP protocol entity as a
result of receiving valid SNMP Set-Request PDUs.
The total number of SNMP Get-Next PDUs which have
snmpInGetRequests
been accepted and processed by SNMP.
The total number of SNMP Get-Response PDUs which
snmpInGetResponses
have been accepted and processed by the SNMP.
The total number of SNMP Trap PDUs which have been
snmpInTraps
accepted and processed by the SNMP protocol entity.
The total number of SNMP generated PDUs for which
snmpOutTooBigs
the value of the error-status field is “tooBig”.
snmpOutNoSuchNames
the value of the error-status field is “noSuchName”.
snmpOutBadValues
the value of the error-status field is “badValue”.
snmpOutGenErrs
the value of the error-status field is “genErr”.
The total number of SNMP generated Get-Request
snmpOutGetRequests
PDUs.
The total number of SNMP generated Get-Response
snmpOutGetResponses
PDUs.
snmpOutTraps The total number of SNMP generated Trap PDUs.
Indicates whether the SNMP agent process is permitted
to generate authentication-failure traps. The value of this
snmpEnableAuthenTraps object overrides any configuration information; as such,
it provides a means whereby all authentication-failure
traps may be disabled.

Understanding Status Reports
System Status Indicates the operational status of the Flanger4Plus unit.

Indicates the interface operational status.
DS1 Interface
Values are either "Operational" or "Down".
WAN Interface
LAN Interface
Indicates the Ethernet communication status for the
WAN Link
WAN.
Indicates the Ethernet communication status for the
LAN Link
LAN.
Wayside Data Indicates the status of wayside data processing.

Packet Queues
Information about the system walking through each
Queue Walk Test
event in the Packet Queue.
Total number of Queues that can ever be handled by the
Total
system.
The number of Queues that are available at the time if
Available
the report.
The lowest number of Queues that have been available
Low Water Mark
to the system.
Times Empty The times that the Queues have been empty.
Reassembly Buffers
The number of buffers reserved by the system for
Total
reassembly of packets.
The amount of time that the system allows for a packet
Timeout
to be held awaiting reassembly before it is discarded
Currently Used The number of reassembly buffers presently in use.
Maximum Used The largest number of reassembly buffers as seen by the

system.
Stack Queue
The results of the system being able to service every
Queue Walk Test
Queue meant for the system.
The number of queues currently used and awaiting the
Currently Queued
system.
Maximum Queued The maximum number of queues used and awaiting the
system.
WAN Packets
Pending Receive The number of WAN packets pending receipt.
Pending Transmit The number of WAN packets pending transmit.
The results of the system being able to service the

Queue Walk Test
entirety of the WAN queue.
Wayside Queued The number of Wayside packets queued by the system.
Wayside Max Queued The maximum number of Wayside packets queued by

the system

LAN Packets
Pending Receive The number of LAN packets pending receipt.
Pending Transmit The number of LAN packets pending transmit.
DS1 Interface
Remote
Flanger4Plus Defines the status of the remote unit.
Defines if the 46Mhz & 61Mhz clocks are working.
Clock Signals
Values are either “Detected” or “Loss for X Sec,” where x
represents the number of seconds down.
Channel Defines the channel the values to the right are describing.
Signal Present
Defines if the line is active. Values are either “Yes” or
“No.”
Equalizer in Range Reports the equalizer status of each T1/E1 line.
Timeclock Which source of clock is used by the Line Interface Unit.
Line Driver Reports the transmitter status of each T1/E1 line.
AIS Alarm Reports the reception of AIS alarms.
The number of errors reported from the Line Interface
Error Count Unit, per T1/E1 channel
Jitter Underflow result from queues released too early.
FIFO Underflow
Jitter Overflow result from queues released too late.
A queue that sends the packets it in the order it was
FIFO Overflow queued.
The estimated Error-Free-Seconds of up-time on each
Estimated EFS T1/E1 channel.
Estimated ES The estimated Errored-Seconds on each T1/E1 channel
The estimated percentage of Errored-Seconds to Error-
Estimated %ES Free-Seconds
Clock Var The calculated clock variation on a per channel basis.

Understanding Web Server Reports
Web Server Statistics

Total number of available of endpoints in a server / client
Open Sockets configuration where communication between two devices
can happen.
Total the number of errors within web server
Errors
communication.
Total number of requests to access a part of the web server
received from a user input (e.g. accessing the home page
Get Requests
yields multiple requests from the web server’s index in order
to see the home page).
Total number of packet headers from the web server to the
Headers Sent
browser.
Total number of user submissions that change configurations
Form Posts from the browser to the device (e.g. changing the WAN IP
and clicking “Save WAN Settings”).
Total number of terminated sockets that were previously
Sockets Closed (peer)
open due to intentional action (e.g. closing the browser).

Total number of terminated sockets that were previously
Sockets Closed (timeout)
open due to inactivity.
Total time in seconds that a form has to submit its
information to the web serve in seconds. If a form
Timeout
submission takes longer than the timeout, then the save will
stop and the saving will not be kept.
Idle Timeout Total time in seconds that an inactive socket was kept open.
Persistence
Sockets Total number of reusable keepAlive sockets.
Total Request Information only. No Company Support.
Maximum Request Information only. No Company Support.
Rejected Information only. No Company Support.
Pipelines
Sockets Information only. No Company Support.
Total Requests Information only. No Company Support.

5. Cabling Requirements
CAT5 Ethernet
Pin-outs with Power over CAT5
Pin-outs without Power over CAT5
Ethernet with Power over CAT5

Used by cable from your provider power supply into LAN port and out of WAN port.
( Note: Although the Flanger4Plus unit supports reversed polarity on its power leads,
other equipment powered by the Flanger4Plus may not.
( NOTE: Même que le Flanger4Plus accepte la polarite inverse sur se cables, des autres
equipments, meme si connecte` au Flanger4Plus, peuvent ne pas l’accepter,
( Note: The Ethernet cable should be limited to a maximum of 100 meters or approx. 328
feet.

DS1 with RJ-45
The TELCO port(s) normally require a T1/E1 cross-over cable between it and the CPE
(Customer Premise Equipment.) These cables can be made with a standard CAT5 Ethernet
cable using the pin out drawings below. You can use a loop back plug in the Slave unit to
do bench testing.
T1 Crossover Cable T1 Loop-Back Plug

6. Appendix
Min
packets Min Max
in buffer bytes in buffered
Actual at buffer at buffer delay
DS1 rate, payload average average spec variation Round-trip
bps bytes Frames delay delay bytes starts at ms delay ms
1544000 724 1.5005 1 724 2172 1448 3.751 25.07
1544000 724 1.5005 2 1448 3620 2172 7.503 32.57
1544000 724 1.5005 3 2172 5068 2896 11.254 40.07
1544000 724 1.5005 4 2896 6516 3620 15.005 47.57
1544000 724 1.5005 5 3620 7964 4344 18.756 55.08
1544000 724 1.5005 6 4344 9412 5068 22.508 62.58
1544000 724 1.5005 7 5068 10860 5792 26.259 70.08
1544000 724 1.5005 8 5792 12308 6516 30.010 77.58
1544000 724 1.5005 9 6516 13756 7240 33.762 85.09
1544000 724 1.5005 10 7240 15204 7964 37.513 92.59
1544000 724 1.5005 11 7964 16652 8688 41.264 100.09
1544000 724 1.5005 12 8688 18100 9412 45.016 107.60
1544000 724 1.5005 13 9412 19548 10136 48.767 115.10
1544000 724 1.5005 14 10136 20996 10860 52.518 122.60
1544000 724 1.5005 15 10860 22444 11584 56.269 130.10
1544000 724 1.5005 16 11584 23892 12308 60.021 137.61
1544000 724 1.5005 17 12308 25340 13032 63.772 145.11
1544000 724 1.5005 18 13032 26788 13756 67.523 152.61
1544000 724 1.5005 19 13756 28236 14480 71.275 160.11
1544000 724 1.5005 20 14480 29684 15204 75.026 167.62
1544000 724 1.5005 21 15204 31132 15928 78.777 175.12
1544000 724 1.5005 22 15928 32580 16652 82.528 182.62
1544000 804 1.6663 1 804 2412 1608 4.166 26.98
1544000 804 1.6663 2 1608 4020 2412 8.332 35.31
1544000 804 1.6663 3 2412 5628 3216 12.497 43.64
1544000 804 1.6663 4 3216 7236 4020 16.663 51.98
1544000 804 1.6663 5 4020 8844 4824 20.829 60.31
1544000 804 1.6663 6 4824 10452 5628 24.995 68.64
1544000 804 1.6663 7 5628 12060 6432 29.161 76.97
1544000 804 1.6663 8 6432 13668 7236 33.326 85.30
1544000 804 1.6663 9 7236 15276 8040 37.492 93.63
1544000 804 1.6663 10 8040 16884 8844 41.658 101.97
1544000 804 1.6663 11 8844 18492 9648 45.824 110.30
1544000 804 1.6663 12 9648 20100 10452 49.990 118.63
1544000 804 1.6663 13 10452 21708 11256 54.155 126.96
1544000 804 1.6663 14 11256 23316 12060 58.321 135.29
1544000 804 1.6663 15 12060 24924 12864 62.487 143.62
1544000 804 1.6663 16 12864 26532 13668 66.653 151.95
1544000 804 1.6663 17 13668 28140 14472 70.819 160.29
1544000 804 1.6663 18 14472 29748 15276 74.984 168.62
1544000 804 1.6663 19 15276 31356 16080 79.150 176.95
1544000 804 1.6663 20 16080 32964 16884 83.316 185.28
1544000 1024 2.1223 1 1024 3072 2048 5.306 32.24
1544000 1024 2.1223 2 2048 5120 3072 10.611 42.86
1544000 1024 2.1223 3 3072 7168 4096 15.917 53.47
1544000 1024 2.1223 4 4096 9216 5120 21.223 64.08
1544000 1024 2.1223 5 5120 11264 6144 26.528 74.69
1544000 1024 2.1223 6 6144 13312 7168 31.834 85.30
1544000 1024 2.1223 7 7168 15360 8192 37.140 95.91
1544000 1024 2.1223 8 8192 17408 9216 42.446 106.52
1544000 1024 2.1223 9 9216 19456 10240 47.751 117.14
1544000 1024 2.1223 10 10240 21504 11264 53.057 127.75
1544000 1024 2.1223 11 11264 23552 12288 58.363 138.36
1544000 1024 2.1223 12 12288 25600 13312 63.668 148.97
1544000 1024 2.1223 13 13312 27648 14336 68.974 159.58
1544000 1024 2.1223 14 14336 29696 15360 74.280 170.19
1544000 1024 2.1223 15 15360 31744 16384 79.585 180.80

Min
packets Min Max
in buffer bytes in buffered
Actual at buffer at buffer delay
DS1 rate, payload average average spec variation Round-trip
bps bytes Frames delay delay bytes starts at ms delay ms
2048000 960 1.5000 1 960 2880 1920 3.750 25.82
2048000 960 1.5000 2 1920 4800 2880 7.500 33.32
2048000 960 1.5000 3 2880 6720 3840 11.250 40.82
2048000 960 1.5000 4 3840 8640 4800 15.000 48.32
2048000 960 1.5000 5 4800 10560 5760 18.750 55.82
2048000 960 1.5000 6 5760 12480 6720 22.500 63.32
2048000 960 1.5000 7 6720 14400 7680 26.250 70.82
2048000 960 1.5000 8 7680 16320 8640 30.000 78.32
2048000 960 1.5000 9 8640 18240 9600 33.750 85.82
2048000 960 1.5000 10 9600 20160 10560 37.500 93.32
2048000 960 1.5000 11 10560 22080 11520 41.250 100.82
2048000 960 1.5000 12 11520 24000 12480 45.000 108.32
2048000 960 1.5000 13 12480 25920 13440 48.750 115.82
2048000 960 1.5000 14 13440 27840 14400 52.500 123.32
2048000 960 1.5000 15 14400 29760 15360 56.250 130.82
2048000 960 1.5000 16 15360 31680 16320 60.000 138.32
2048000 1066 1.6656 1 1066 3198 2132 4.164 27.81
2048000 1066 1.6656 2 2132 5330 3198 8.328 36.14
2048000 1066 1.6656 3 3198 7462 4264 12.492 44.47
2048000 1066 1.6656 4 4264 9594 5330 16.656 52.80
2048000 1066 1.6656 5 5330 11726 6396 20.820 61.12
2048000 1066 1.6656 6 6396 13858 7462 24.984 69.45
2048000 1066 1.6656 7 7462 15990 8528 29.148 77.78
2048000 1066 1.6656 8 8528 18122 9594 33.313 86.11
2048000 1066 1.6656 9 9594 20254 10660 37.477 94.44
2048000 1066 1.6656 10 10660 22386 11726 41.641 102.77
2048000 1066 1.6656 11 11726 24518 12792 45.805 111.09
2048000 1066 1.6656 12 12792 26650 13858 49.969 119.42
2048000 1066 1.6656 13 13858 28782 14924 54.133 127.75
2048000 1066 1.6656 14 14924 30914 15990 58.297 136.08
Payload and Buffer Depth impact on Delay

FL4+ User Guide v070109

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FL4+ User Guide v070109

Uploaded by

Copyright:

Available Formats

Flanger4Plus

For Build 62209 and later

For build 62209 and later 2

2. Getting Started ........................................................................... 11

3. Configuration Considerations ..................................................... 21

For build 62209 and later 4

Updating your Flanger4Plus ............................................................. 56

Understanding Flanger4Plus Reports .............................................. 57

5 For build 62209 and later

For build 62209 and later 6

7 For build 62209 and later

Benefits and Uses

Flanger4Plus Gets Smarter Over Time

Designed For Wireless

For build 62209 and later 8

9 For build 62209 and later

Figure 1 Remote PBX

Figure 2 Cellular Backhaul

For build 62209 and later 10

11 For build 62209 and later

Flanger4Plus serial numbers use hexadecimal

Supported Radios for Power over CAT5

Understanding the Front Panel

For build 62209 and later 12

WAN Connects Flanger4Plus to the dedicated network used for

13 For build 62209 and later

3. (Optional) Connect the Flanger4Plus to your company’s LAN Ethernet network or to

Note that a DS1 crossover cable is DIFFERENT than an Ethernet

For build 62209 and later 14

For build 62209 and later

Equipment connected to the WAN port WILL BE damaged if the device

For build 62209 and later 16

Flanger4Plus User Interface

Subnet 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0

Remote IP 169.254.1.60 169.254.1.50

Speed/Duplex 100 MB / Auto 100 MB / Auto

DS1 Timing Control

17 For build 62209 and later

Bit Clock Mode 2 – DS1 Line Mode 3 – Remote Global Sync

For build 62209 and later 18

Visual Status Indicators (LED)

19 For build 62209 and later

For build 62209 and later 20

21 For build 62209 and later

Setting Flanger4Plus Addresses

For build 62209 and later 22

23 For build 62209 and later

For build 62209 and later 24

( Note: This is the factory default configuration for a Flanger4Plus pair.

When to use Mode 2 Pairs

25 For build 62209 and later

Using Equalizer Control Settings

Optimizing Reliability for Various Networks

For build 62209 and later 26

27 For build 62209 and later

For build 62209 and later 28

29 For build 62209 and later

Wire Delays for Various Packet Sizes

“In the Air” Delay

Average Protocol Delays for Various Equipment Types

For build 62209 and later 30

31 For build 62209 and later

Delay Histogram for Radio Link ‘A’