Resource Allocation Across E1/T1 Lines; About Peer-To-Peer Connectivity - LifeSize Gateway-PRI User Manual

R
ESOURCE
A
LLOCATION ACROSS
E1/T1 L
INES
A P - -P
BOUT EER TO EER
C
ONNECTIVITY
For example, a call at 384 Kbps actually has only 363 Kbps available to it.
Control and error correction account for the remaining 21 Kbps.
The LifeSize Gateway can allocate bandwidth resources to calls across separate
E1 or T1 connections to maximize bandwidth capacity in cases where there is
not enough capacity for a call on a single E1 or T1 connection, but where
sufficient capacity does exist when remaining capacity on both E1/T1 lines is
combined.
For example, a LifeSize Gateway using two T1 lines can support three 6B calls
on each T1 line, with 320 Kbps spare capacity per line:
Each T1 line provides 23 B channels.
Each B channel supports 64 Kbps
Each T1 line supports 23 x 64 = 1472 Kbps
Each 6B call requires 6 x 64 = 384 Kbps
Each T1 line supports 1472/384 = 3 6B calls + 320 Kbps spare
The LifeSize Gateway processes an additional 6B call requiring a further 384
Kbps by taking bandwidth resources from each of the two T1 lines, both of
which have 320 Kbps available. In this way, the LifeSize Gateway spreads the
call over both T1 lines.
The LifeSize Gateway supports the following types of connectivity to the IP
network
Through a gatekeeper
Directly to a peer device such as Cisco Unified CallManager without
the need for a gatekeeper.
About LifeSize Gateway Functionality
Functionality 17