OCS 2007 R2 Bandwidth Calculations

By -

Medium

Min

High Quality

Data

56kbps

56kbps

Voice

50kbps

80kbps

Video

50kbps

350kbps

RoundTable (Conference video phone)

50kbps

350kbps

Note that the requirements are cumulative –

Data + Voice + Video =

56 + 50 + 50 = 156kbps (Minimum Quality)

or

56 + 80 + 250 = 386kbps (High Quality)”

Here are some calculations I have used. however the 300KBps is only video stream single direction.  Bidirectional video consists of two streams..

The following formula can provide rough bandwidth consumption estimates for conferencing with Audio / Video.

Note:  Calculation results will be displayed in Mbps

CC = Concurrent Conferences

PPC = Participants Per Conference

 

Conference Type

Bandwidth Consumption Mbps

Audio with Application Sharing

(((CC * PPC)*14KBps)+((CC *PPC)*90KBps))*10^-3

Audio and Video

(((CC * PPC)*14KBps)+((CC *PPC)*600KBps))*10^-3

Another OCS 2007 Audio Bandwidth Calculation

Audio Codec

Frame Size [ms]

Codec payload bit rate

[bits / sec]

Total payload bit rate

[bits / sec]

Actual bit rate

[bits / sec]

Without

redundancy

With

redundancy

RTAudio@16KHz

20

24000

29000

45000

74000

RTAudio@16KHz

40

24000

26500

34500

61000

RTAudio@16KHz

60

24000

25666

31000

56667

RTAudio@16KHz

20

18000

21000

37000

58000

RTAudio@16KHz

40

18000

19500

27500

47000

RTAudio@16KHz

60

18000

19000

24333

43333

RTAudio@8KHz

20

8800

11800

27800

39600

RTAudio@8KHz

40

8800

10300

18300

28600

RTAudio@8KHz

60

8800

9800

15133

24933

 

You can also limit the bandwidth used through the registry, this registry key set is available through group policy when you update the group policy with the new OCS 2007 group policy objects.

(How to Specifies the maximum bandwidth for audio and video)

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\LiveMeeting\MaxAudioVideoBitrate

 

 

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", however it seems to take between 5-10 mins
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 this response there is an issue,
Read more