S8700 Media Server With G650/Mcc1/Scc1/G600 Media Gateway And G700 Media Gateway -Ip Endpoints And Pri Trunks; S8700 Media Server With G650/Mcc1/Scc1/G600 Media Gateway And G700 Media Gateway Contact Center-Low Usage - Avaya S8700 Overview Manual

Overview
High-level capabilities
S8700 Media Server with
G650/MCC1/SCC1/G600 Media Gateway
and G700 Media Gateway —IP endpoints
and PRI trunks
•
90% G650/MCC1/SCC1/G600 Media Gateway processing and 10% G700 processing—94,000
BHCC (90,000 G650/MCC1/SCC1/G600 Media Gateway BHCC and 4,000 G700 Media
Gateway BHCC).
•
50% G650/MCC1/SCC1/G600 Media Gateway processing and 50% G700 processing—70,000
BHCC 50,000 G650/MCC1/SCC1/G600 Media Gateway BHCC and 20,000 G700 Media
Gateway BHCC).
S8700 Media Server with
G650/MCC1/SCC1/G600 Media Gateway
and G700 Media Gateway
contact center—low usage
•
90% G650/MCC1/SCC1/G600 Media Gateway processing and 10% G700 processing—71,000
BHCC (68,000 G650/MCC1/SCC1/G600 Media Gateway BHCC and 3,000 G700 Media
Gateway BHCC).
•
50% G650/MCC1/SCC1/G600 Media Gateway processing and 50% G700 processing—50,000
BHCC (37,000 G650/MCC1/SCC1/G600 Media Gateway BHCC and 13,000 G700 Media
Gateway BHCC).
NOTE:
Any configuration that includes IP Solutions applications such as Road Warrior,
Telecommuter, or H.322 trunking, affects the BHCCs and processor capacity. If a
customer uses these applications in a high traffic solution, it is recommended that the
Avaya Technology and Consulting (ATAC) team be involved to review any potential
impact on traffic.
The information in this table represents the maximum number of calls the S8700 Media Server could
execute, assuming it was unconstrained by other factors such as:
•
TDM bus limitations
•
Call duration
•
Small number of telephones
We assume processor occupancy of 0.90, at which various delay criteria such as cut through is preserved,
and is just at the threshold where call could no longer be processed.
28 Overview for S8700 Media Server
November 2003