Capacity Planning - Microsoft Office Communications Server 2007

By -

Microsoft Office Communications Server 2007

Capacity Planning

The following requirements are based on the following user model and assumes that each deployment supports IM, Web conferencing, and audio-video and voice.

Table 32 Maximum Supported Users for each Topology

Topology

Servers Required

Maximum Users Supported

Standard Edition Server

1 Standard Edition server

(Optional) Archiving Server collocated

5,000

Enterprise pool: Consolidated Configuration

4 Enterprise Edition Front-End servers running all server roles

1 Backend SQL Server

(Optional) 1 Archiving Server

30,000

Enterprise pool: Expanded configuration

With Mid-Range Performance SQL Backend

4 Front-End Servers

2 Web Conferencing Servers

2 A/V Conferencing Servers

2 IIS Servers

1 Backend SQL Server

(Optional) 1 Archiving Server

50,000

Enterprise pool: Expanded configuration

With High Performance SQL Backend

8 Front-End Servers

4 Web Conferencing Servers

4 A/V Conferencing Servers

2 IIS Servers

1 Backend SQL Server

(Optional)2 Archiving Servers

125,000

 

Bb870396.note(en-us,office.12).gifNote:

Two IIS Servers are recommended for improved availability in the Expanded Configurations.

Edge server topologies assume 10 percent of the total user base will be connected from outside the intranet. The following table shows the maximum number of client connections supported by each of the following edge server roles and topologies.

Table  SEQ Table \* ARABIC 33 Maximum Supported Users for each Topology

Topology

Supported Performance

Stand-alone Access Edge Server

15,000 client connections

Stand-alone Web Conferencing Edge Server

3,000 client connections

Stand-alone A/V Edge Server

1,500 concurrent audio/video sessions

Collocated Access Edge & Web Conferencing Edge Server

Access Edge Server: 5,000 client connections

Web Conferencing Edge Server: 1,500 client connections

Collocated Access Edge, Web Conferencing Edge & A/V Edge Servers (Consolidated Edge Topology)

Access Edge Server: 5,000 client connections

Web Conferencing Edge Server: 1,000 client connections

A/V Edge Server 500 concurrent audio/video sessions

Bb870396.note(en-us,office.12).gifNote:

A/V experience may be degraded if sessions approach the maximum limit. We recommend that you deploy a separate A/V Edge Server for the optimal A/V experience.

Deployment of a Director is recommended for external access. An array of Standard Edition Directors with at least two servers is recommended for topologies with up to 125,000 users. Additional servers may be added to the array for increased performance.

http://i.technet.microsoft.com/Global/Images/clear.gif Audio/Video Capacity Planning Model

This section summarizes the model used as a basic of our hardware recommendations for audio and video. Our capacity planning model is based on the following assumptions:

  • In meeting with more than five participants, five users have active bidirectional (send/receive) media streams at a time. All other users are muted (receive only).
  • All media streams are encrypted using SRTP.
  • Audio Talking profile is based on the following:

·         80 percent of the time 1 user talks

·         7 percent of the time 2 users talk

·         13 percent of the time nobody talks

All video streams assumed are 244 Kbps with 15 fps.

When running on the recommended hardware (see Hardware for A/V Conferencing Servers and A/V Edge Servers, in Server Platform Requirements), the following table summarizes the Audio/Video Conferencing Server capacity in different scenarios based on this audio/video model.

Table 34 Audio Video Conferencing Scale Numbers on Recommended Hardware

Scenario

Description

Total Number of Users

Bandwidth Consumption

Small Conferences

65 conferences x 3(Audio +Video) users

454

143 Mbps

 

35 conferences x 3(Audio-Only) users

 

 

 

21 conferences x 5 (Audio+Video ) users

 

 

 

11 conferences x 5 (Audio-Only) users

 

 

Large Conferences

8 conferences x 250(Audio+Video) users

3,000

555 Mbps

 

4 conferences x 250 (Audio-Only) users

 

 

Small, Medium and Large Mixture

32 conferences x 3 (Audio+Video) users

1,190

253 Mbps

 

13 conferences x 3 (Audio) users

 

 

 

23 conferences x 5 (Audio +Video) users

 

 

 

9 conferences x 5 (Audio) users

 

 

 

5 conferences x 15 (Audio + Video) users

 

 

 

4 conferences x 15 (Audio) users

 

 

 

4 conferences x 50 (Audio + Video) users

 

 

 

2 conferences x 50 (Audio) users

 

 

 

2 conferences x 105 (Audio) users

 

 

 

1 conferences x 250 (Audio + Video) users

 

 

Small, Medium Mixture

35 conferences x 3 (Audio + Video) users

889

210 Mbps

 

18 conferences x 3 (Audio) user

 

 

 

19 conferences x 5 (Audio + Video) users

 

 

 

16 conferences x 5 (Audio) users

 

 

 

8 conferences x10 (Audio + Video) users

 

 

 

5 conferences x 10 (Audio) users

 

 

 

8 conferences x 25 (Audio + Video) users

 

 

 

3 conferences x 25 (Audio) users

 

 

 

2 conferences x 50 (Audio+ Video) users

 

 

 

1 conferences x 50 (Audio) users

 

 

 


Comments

Post a Comment

Popular posts from this blog

Teams Device Health Monitoring and Reporting

By -
Image
 Microsoft have snuck in a nice new feature into the Teams Admin Center (TAC). We now see a new Notifications and Alerts  menu tree and below this Rules. When we go in here, we find only a single Default  Device State Rule with no option to create any new rules (yet at least...) When we edit this rule, we can see that we now have an option to monitor specific devices (think meeting room devices, collaboration bars etc.. here) Under Device users  we click on +ADD  then enter the name of the account, or accounts if you are monitoring multiple devices, associated with the device, such as the resource account. Then under Actions  we can choose either Channel alert  - to have a nice alert sent to our Teams Channel   OR Webhook  to use webhooks for alerting. Finally ensure to select Active  then Save. Once set up this will take maybe 15 mins to replicate and set up. Then once a device has gone offline, the alert will be sent "Immediately", how...
Read more

Unassigned Numbers in Microsoft Teams using Audiocodes SBC

By -
Image
Unlike Skype for Business, Microsoft Teams does not natively support the handling of Unassigned numbers in the system. So if someone leaves your organisation and you remove the number from them and someone tries to call it, the call will drop. Technically, Teams will return a "404 Not Found" back to the SBC and back on to the telco. What we can do here is to then assign the 404 error to a Route, change the Destination Number (to a call queue or to your main Reception number for example) and route it back to Teams. To do this there are a few simple steps: Step 1 – Create an Alternative Reasons Set Step 2 – Configure existing Teams IP Group to use the SBC Alternative Routing Reason Set Step 3 - Create new IPG Step 4 – Create a new route in IP-to-IP Routing Step 5 - Manipulate Numbers Step 6 – Test  Step 1 – Create an Alternative Reasons Set The first thing we need to do is create an " Alternative Routing Set ", we find this under Setup >> Signaling & Media ...
Read more

Skype for Business Edge Server replication troubleshooter

By -
Image
Many times in Skype for Business/Lync the main issue I come across is the deployment is that the edge server(s) fails to replicate. We see this when we run the command in Skype for Business Management Shell : Get-CsManagementStoreReplicationStatus and we see that the edge servers have False and no LastStatusReport or ProductVersion is shown as below. There are a number of things which can cause this and I am going to list them here. Try them in order here as this will contain the most common to the least common issues I found. Ø   Routing Ø   Firewall rules Ø   DNS suffix Ø   DNS (Local and LAN) Ø   Registry entries for SCHANNEL Ø   Certificates A check we can use to see if the replication is working can be done by trying to connect to the following URL from the Front End Server whish hosts the CMS: https://edgeinternalfqdn.domain.ie:4443/Replicationwebservice You should get the following screen: Without thi...
Read more