Continuing with Teams summaries i wanted to provide a summary of the latest video available on the success with teams academy which is “How to use the Bandwidth Calculator”. Thanks to Tom Arbuthnot for pointing out the new video as well.
Critically important to teams as it uses real time media is your network and also ensuring enough bandwidth is always available so before your deployment preferably check this tool out.
Plan before you deploy !
Calculator Link below to check it out.
Information on presenter Korneel Bullens
Calculating Bandwidth is IMPORTANT !
a well prepared network delivered great quality!
calculator tool to help guide you but note tool is based on typical value and assumptions so calculations must be monitoring and confirmed during deployment.
Usual disclaimer with Cloud sessions this is the April 2017 recording and content is subject to change.
Why calculate bandwidth?
- help prepare for possible impact of adding Microsoft Teams to your network
- quality is critically important !
- User experience is key!
- fundamental for a successful deployment !
- not preparing network will lead to issues and poor user experience and adoption !
- More return on ROI and more people will use it !
- Don’t want to scare people from using it
- MANDATORY when using Microsoft teams to calculate bandwidth and impact to network!
- The quality and bandwidth available on the network is KEY ! Plan, Plan, Plan
Also from me with experience on SfB side when you look at networks and bandwidth consider the different types of network people will connect to, use and how media will flow. For example, LAN, WiFi, Internet, MPLS, IP VPNs, connect to Office 365. IPSec VPN encryption impact to media traffic. Will users use Desktop or mobile clients will desktops be connected to Lan or WiFi or ive even seen both ! Is the network ready for real time media / communications. Just because you can quickly enable and deploy teams doesn’t mean you want to skip planning phase and network is critical.
What is calculated with the tool ?
- Uses averages and typical values (NOT MAXIMUM by default)
- 60% of time people speak and 40% people are silent
- Number is based on expected usage when number of users is entered in the tools
- Monitoring and adjusted may be requirements as there could be peaks for example all users after lunch all jump in meetings.
- Great for guidance, keep monitoring and adjust as needed
- Typical NOT maximum values
- keep these in mind these are typical !
- QoS may need to use maximum numbers
- guidance available on maximum numbers below
- Best practice no more than 30% being used by real time traffic
- Based on average usage
- For max values multiple by 1.4 mentioned roughly here
- For max 1.4 is based not on all users making calls at the same time, calculates based on the 60% people speak and 40% silence and making them 100% speaking.
Where to find it ?
How to use ?
- Add up to 10 rows
- Site names
- user counts
- remote percentage – how many working remotely from home / road. 20% good starting numbers
- Teams usage – will it be used heavily
- P2P – peer to peer (one to one)
- Conferencing – how much will it be used for conferencing
- if you set one conferencing value to low then all the other should be set to low
- Medium and 20% remote is default and typical Microsoft find
Sites added as shown above – note video for one set to none as users dont have video cameras in this example.
WAN Impact usually means MPLS (Maybe VPN) between sites
O365 Impact – usually internet connection to Office 365 (Maybe ExpressRoute)
Notice above Houten has huge difference in WAN and O365 impact due to no video camera. Video consumed the most bandwidth.
Export button available as well to export to excel
- recommended for new site please revisit the bandwidth calculator as formulas may get updated.
Important to understand these !
- Based on typical bandwidth (max can be used using multiple value by 1.4)
- Monitoring of usage after deployment is required
- Based on assumed usage
- Calculate before you deploy !
- be prepared before you deploy!