Avaya R300 用户手册
DEFINITY Enterprise Communication Server Release 9
Getting Started with the Avaya R300 Remote Office Communicator
Getting Started with the Avaya R300 Remote Office Communicator
Issue 1
November 2000
Avaya R300 Specifications and Network Design
21
Bandwidth engineering considerations
2
Bandwidth engineering considerations
The bandwidth available for communication between the main DEFINITY ECS host and
the Avaya R300 is dependent on several factors. The following gives a high level
overview of the items for consideration. The Remote Office has three principle forms of
traffic back to the host site (See
the Avaya R300 is dependent on several factors. The following gives a high level
overview of the items for consideration. The Remote Office has three principle forms of
traffic back to the host site (See
■
Voice bearer traffic (carried on IP streams, over WAN network channels)
■
H.323V2 call signaling/registration traffic (carried on IP streams, over WAN
network channels) and tunneled maintenance
network channels) and tunneled maintenance
■
IP routed data network traffic (carried on PPP streams, over WAN network
channels)
channels)
Figure 9.
Bandwidth engineering for the Avaya R300
Analog Trunk
#2
Analog Trunk #1
ISDN/FR
WAN
LOCAL
CO
(p/o WAN)
1st T1/E1
2nd T1/E1
TSS
DCP
24
RAC
Connection
Routing
Remote
Angel
2
Analog
Combo
Blade
DEFINITY Remote MAX
Definity
Call Processing
Line
Circuits
TDM
Bus
DEFINITY
DOLAN
IP Mgmt
IP Mgmt
CLAN
PROWLER
(VOIP
Resources)
Data
Routing
& WAN
Equipment
(Could be
UNM)
Trunk Ckts
BRI, PRI,
ATM, Analog
Ether
VOI
P
Denotes Voice Bearer
Denotes Call Signalling
Host
LAN
Denotes Data Bearer
LOCAL
LAN
Denotes Data Bearer Resources
Denotes Voice Bearer Resources