MS-721: Collaboration Communications Systems EngineerDemo

Group call pickup shares incoming calls for an individual user with colleagues; it does not provide call-queue history or shared voicemail. Microsoft Teams shared call history for call queues enables agents to view queue activity and shared voicemails, including voicemail-related records, when configured for the call queue.

A shared voicemail destination provides group access to voicemail messages and transcriptions, but it does not by itself provide call queue history. Queue agents can view shared call history only when a shared call-history template is configured for the call queue; this exposes queue call records and shared voicemails to the permitted agents.

Attendant routing is a call-distribution setting and does not provide agents with shared call-queue history or configure shared transcribed voicemail. Shared call history must be enabled through a shared call-history template, and shared voicemail must be configured as a call-queue exception destination.

A Direct Routing deployment connects Teams Phone to existing PSTN and PBX infrastructure through a certified Session Border Controller (SBC). An E1/T1 PRI is a physical digital trunk, so retaining that service requires an SBC with a physical PRI interface to terminate and route the trunk. An ATA supports analog telephony rather than PRI, and virtual or Azure-hosted SBCs cannot directly terminate the on-premises PRI circuit.

For a Direct Routing call transfer in which the SBC receives a SIP REFER, the SBC must process the REFER and initiate a new INVITE back to the Microsoft SIP proxy using the transfer information. Accepting the REFER and sending NOTIFY messages without correctly performing that transfer flow causes the transfer to fail; this indicates that REFER handling on the SBC is misconfigured.

During an internet outage, Teams clients operating through a local Survivable Branch Appliance can make PSTN calls, receive PSTN calls, and place PSTN calls on hold and resume them. Dynamic emergency calling depends on location information services and is not available in SBA offline mode; emergency calls can still be placed, but location information is not shared. Microsoft documents blind transfer specifically rather than unrestricted PSTN call transfer.

Teams Direct Routing media bypass uses ICE between the Teams client and the SBC. The SBC must support the ICE Lite protocol so it can participate in ICE connectivity checks and establish the direct media path.

The Device state rule in the Teams admin center proactively monitors Teams devices for an offline state. It can target devices associated with selected signed-in users and generate alerts when those handsets go offline.

Teams webinars provide presenter bios, attendee registration, and registration-management capabilities. Teams events policies control the availability of webinars and event-specific registration settings, while meeting policies control core meeting and organizer scheduling/registration behavior. Customization policies govern meeting branding and visuals, and legacy live-events policies do not provide the webinar registration-management experience.

Teams Phone Mobile makes a user’s SIM-enabled, company-owned mobile number also their Teams number. Calls to that number ring the smartphone and active Teams clients, and the number can be used on Teams endpoints such as desk phones. Using one operator-provided number for these endpoints minimizes the number of purchased phone numbers.

A voice routing policy is assigned to Direct Routing users and contains PSTN usages that link to voice routes. Configure the applicable PSTN usage and voice route for the international number pattern, then assign the voice routing policy to the user.

Enabling External location lookup mode in a Teams emergency calling policy allows users to add, edit, or confirm their emergency address from the Teams Calls client, including for remote locations.

Shared Calling uses the phone number of a resource account associated with an Auto attendant for inbound and outbound PSTN calls, so individual users do not require dedicated phone numbers. The Auto attendant can route calls to a call queue, which does not need its own dedicated number for this deployment.

An SBA maintains local PSTN calling during an internet outage, including media bypass and basic local call handling. SBA mode does not support dynamic emergency-calling capabilities such as sharing E911 location information or Emergency Call Routing Policies. The cloud-managed call-forwarding feature requires connectivity for its full Teams service behavior.

Teams dial plans use normalization rules to translate abbreviated internal dial strings, such as five-digit extensions, into standardized numbers, typically in E.164 format, before routing. Review the applicable dial plan and its normalization rules when that translation does not occur.

Hotline (also called PLAR) is enabled in the Microsoft Teams admin center from a configuration profile assigned to Teams phones. The profile’s Call settings include the Enable hotline option, which can then be applied to the target devices.

For Direct Routing, the SBC’s configured SIP signaling port is its TLS listening port. Microsoft’s SIP proxy must be able to reach that port on the SBC. Blocking traffic on port 5067 prevents the TLS/SIP connection from being established, leaving TLS connectivity inactive and preventing calls.

Teams Audio Conferencing policies manage the toll and toll-free numbers displayed in meeting invitations. Create or configure a policy with the Adelaide toll number and assign it to the Adelaide users; numbers in an assigned policy take precedence over individually configured conferencing numbers and avoid changing the organization-wide default.

Teams custom meeting backgrounds are configured in a meeting customization policy. The policy can contain uploaded organization background images and can subsequently be assigned to users or groups such as Group1; Teams Premium licensing is required for users to use those organization-provided backgrounds.