04 · Network and QoS
64 kbit/s is the payload. The link carries headers too.
G.711 at 20 milliseconds is 160 bytes of payload. Add 40 bytes of IP, UDP, and RTP and the call is 80 kbit/s per direction at layer 3. Add an 18-byte Ethernet header and it is 87.2 kbit/s. G.729 at the same interval is 20 bytes of payload, 24 kbit/s at layer 3.
Silence suppression and a different packet interval change the average. Size the busy hour at the packetization you actually configure, in both directions, for the concurrent calls you actually expect. A yearly average divided by eight is not a busy hour.
Count headers. G.711 at 20 milliseconds is 80 kilobits per second at layer 3, 87.2 with Ethernet.
G.711 at 20 ms is 80 kbit/s at layer 3 and 87.2 with a typical Ethernet header.
If it fails: Thirty calls were planned at 64 kbit/s and the policer drops the rest.
A colleague reports: A branch hairpins through HQ and then out, adding hops and delay. Where do you start?
A branch hairpins through HQ and then out, adding hops and delay. Draw the path before you buy bandwidth. Source: https://learn.microsoft.com/en-us/microsoftteams/qos-in-teams accessed 2026-10-14.
Which description of Layer-3 G.711 is accurate?
G.711 at 20 ms is 160 bytes of payload plus 40 bytes of IP, UDP, and RTP. That is 80 kbit/s per direction. People quote 64 kbit/s and under-size the link. Source: https://learn.microsoft.com/en-us/microsoftteams/qos-in-teams accessed 2026-10-14.
A colleague reports: Thirty calls were planned at 64 kbit/s and the link saturated. Where do you start?
Thirty calls were planned at 64 kbit/s and the link saturated. Multiply by concurrent calls and by two directions when both ways are busy. Source: https://learn.microsoft.com/en-us/microsoftteams/qos-in-teams accessed 2026-10-14.
Around the call: compliance recording, workforce management, emergency location, analytics, CRM screen pop, and an agent with a human escape. Each one has its own failure.
Thirty calls were planned at 64 kbit/s and the policer drops the rest.
Cisco CUBE is one of the SBC families named in this lab’s certification lesson. A certified release can be the Direct Routing SBC between Unified CM and Teams.
The tenant still needs a verified domain on the SBC FQDN, and the user still needs Teams Phone. The studio translator does not open a live AXL session. Confirm the current certified release before you build.
Teams Phone and Webex Calling are separate clouds. This lab does not describe a feature that registers a Webex Calling user into a Teams tenant.
A number move is usually a carrier port, a certified SBC, or a meetings interop product. Confirm before relying.
Unified CCE stays the ACD until you migrate it. Microsoft’s contact-center articles name Connect, Extend, and Unify. They do not name a UCCE connector in the notes this lab cites.
Voice into Teams is still Direct Routing or Operator Connect. The routing script stays on the contact-center product you bought. Confirm the vendor’s current model. Source: https://learn.microsoft.com/en-us/microsoftteams/teams-contact-center.
Copilot Studio, Azure Communication Services, and Graph are later tracks in this lab. Treat any uncited limit as confirm before relying.
Opened 2026-10. A row marked confirm did not open. Wikipedia is background. The Teams blog row is the community index.
