Specifications

Installation and Operation Manual Chapter 1 Introduction
IPmux-8/16 Ver. 6.00 Functional Description 1-19
Where:
N =
48
ebytes/framTDM
TS = number of assigned timeslots (in unframed mode= 32 for E1, 24 for T1)
For a bundle that contains a few timeslots (i.e. 1 to 3), the recommended number
of TDM bytes/frame is 48 in order to prevent excessive packetization delay.
Round Trip Delay
The voice path round-trip delay introduced by IPmux-8/16 is calculated as follows:
Maximum Round Trip Delay (μs)
= 2 × [
NTS
n48
×
( x 125 μs) × 2 + PDVT buffer (μs) +1 msec]
Where n =
48
ebytes/fram TDM
For framed E1/T1 NTS = number of assigned timeslots
For unframed:
E1: NTS = 32
T1: NTS = 24
E3: NTS = 537
T3: NTS = 699
•
NTS
n48×
x 125 μ s is packetization delay
• 1 msec is end-to-end internal processing delay introduced by IPmux-8/16
(Rx – 0.5 msec, Tx – 0.5 msec)
• In real-life applications the PSN always introduce some delay that must be added
to the RTD calculations. There is no network delay when IPmux-8/16 devices
operate back-to-back.
Ethernet
OAM
OAM is used to detect validity of the endpoint configuration and connection
between them.
When IPmux-8/16 is powered up or a connection is opened/enabled, TDMoIP
traffic is not sent immediately. First, a TDMoIP echo request packet is sent once
every five seconds. This continues until a valid echo reply arrives. The remote
IPmux receives the echo request packet, checks or answers it only if the
destination bundle of the echo request message exists in the receiving end, and
the connection is enabled. The remote IPmux sends a valid echo reply only if all
parameters in the echo request match its local configuration. When a valid echo
reply arrives, the transmitting echo request message stops, and TDMoIP flow
begins at full rate. If there is a break in the connection, the initialization process
begins again.
Note
Not
e