Add_workflow_for_techpubs AUTH1 UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb41059c, userName='null'} JIRAIDAUTH SYM-27516 REV5 UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} REV6 UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} REV3 UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cdb40a89, userName='null'} REV4 UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f0, userName='null'} REV1 UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c7f0006a, userName='null'} REV2 UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca2f03d1, userName='null'}
Panel | ||||||
---|---|---|---|---|---|---|
In this section:
|
CSS Stylesheet |
---|
img.confluence-embedded-image { display: inline-block !important; } |
The SBC Edge is certified to offer Microsoft Teams Direct Routing services, and used to connect any Teams client to:
These instructions detail how to connect the SBC Edge (SBC 1000/2000 and SBC SWe Lite) for Enterprise's migration from Skype for Business Cloud Connector Edition with Phone System in Office 365 (Cloud PBX) to Microsoft Phone System (Teams).
Info |
---|
The Cloud Connector Edition (CCE) application may be physically hosted within the Ribbon SBC (SBC 1000 or SBC 2000 Cloud Link device) or within an external server. These instructions apply to both CCE deployment scenarios. |
An enterprise may choose to deploy Microsoft Phone System services (Teams Direct Routing) to clients presently receiving Skype for Business Cloud Connector Edition (CCE) with Phone System in Office 365 (Cloud PBX). The instructions below detail how to migrate services from Cloud Connector Edition (CCE) to Microsoft Phone System (Teams Direct Routing) services.
In the following example, it is assumed a Ribbon SBC Edge device qualified for Skype for Business is already deployed on the customer premises.
Pagebreak
Caption | ||||
---|---|---|---|---|
| ||||
Caption | ||||
---|---|---|---|---|
| ||||
Pagebreak |
---|
Multiexcerpt include | ||||
---|---|---|---|---|
|
Pagebreak |
---|
Note |
---|
If you plan a Big Bang migration, some Prerequisites (such as Public IP, FQDN, and Certificates) are unnecessary if existing CCE resources are being re-used. |
Include Page | ||||
---|---|---|---|---|
|
Info |
---|
Calls from the PTSN to an Office 365 user can be sent via Teams Direct Routing before the user is moved to Teams. Calls will go via Teams Direct Routing and reach the Skype client. |
Info |
---|
Before configuring the Tenant, wait at least ten minutes before the call Tab appears on the Team client. |
These instructions configure the Tenant to connect (pair) the SBC to the Microsoft Direct Routing Interface.
Configure Microsoft Phone system Voice routing. As part of this process, use the following command to create an Online PSTN Gateway that points to the SBC:
Code Block |
---|
New-CsOnlinePSTNGateway -Fqdn <SBC Public FQDN> -SipSignallingPort <SBC SIP Port> -MaxConcurrentSessions <Max Concurrent Session which SBC capable handling> -Enabled $true |
Configure Teams usage for the user:
Code Block |
---|
#### USER CCE -> Teams Get-CsOnlineUser -Identity user1@domain.com | Select-Object -Property UserPrincipalName,EnterpriseVoiceEnabled,HostedVoiceMail,OnPremLineURI,TeamsInteropPolicy,TeamsCallingPolicy,OnlineVoiceRoutingPolicy Grant-CsVoicePolicy -PolicyName "" -Identity user1@domain.com Set-CsUserPstnSettings -HybridPSTNSite "" -Identity user1@domain.com Grant-CsTeamsUpgradePolicy -PolicyName UpgradeToTeams -Identity user1@domain.com Grant-CsTeamsCallingPolicy -PolicyName AllowCalling -Identity user1@domain.com Grant-CsOnlineVoiceRoutingPolicy -PolicyName "GeneralVRP" -Identity user1@domain.com |
This can be reverted at any time with the following command:
Code Block |
---|
#### USER Teams -> CCE Grant-CsTeamsUpgradePolicy -PolicyName SfBOnly -Identity user1@domain.com Grant-CsTeamsCallingPolicy -PolicyName "" -Identity user1@domain.com Grant-CsOnlineVoiceRoutingPolicy -PolicyName "" -Identity user1@domain.com Grant-CsVoicePolicy -PolicyName Tag:HybridVoice -Identity user1@domain.com Set-CsUserPstnSettings -HybridPSTNSite aepsite1 -Identity user1@domain.com |
Info |
---|
Wait at least ten minutes before the call is sent to the Skype client. |
Pagebreak |
---|
This section provides details on how to configure certificates for TCP and TLS between the SBC and Cloud Connector Edition (CCE).
Info | ||
---|---|---|
| ||
|
Follow instructions posted below for basic Teams configuration (Step 5).
There are two types of migration from CCE To Microsoft Teams to Direct Routing:
Smooth Migration. Resources are not re-assigned from the CCE to Direct Routing. After this migration, CCE functionality continues to remain available for select clients. Enterprises may choose a smooth migration when some level of Direct Routing testing is still required prior to CCE shutdown.
Note | ||
---|---|---|
| ||
One TLS port can be attached to only one TLS profile. If your CCE deployment uses TLS 5061 as the Federated port, you must modify this Federated port to use a port other than 5061. To modify the Federated port, you must update the Online PSTN Gateway of the CCE topology and the Federated port of the CCE signaling group. If you cannot modify your CCE topology, you can modify the port that Microsoft Teams Direct Routing uses. Make sure you update the Firewall, ACL, and Federated port of the Teams Signaling Group and Online PSTN Gateway. |
For a "big bang" migration:
From the left side menu, import the file via Certificates > Trusted CAs > Import Trusted CA certificate.
From the left side menu, import the file via Certificates > SBC Edge Certificate > Import > PKCS12 certificate and key.
For a "smooth" migration:
From the left side menu, import the CA certificate via SBC Easy Setup > Certificates >Trusted CAs > Import Trusted CA certificate.
From the left side menu, import the new certificate via Certificates > SBC Edge Certificate > Import > PKCS12 certificate and key.
Exchange the root certificate between the SBC and CCE via Tasks > Office 365 > SBC Easy Setup > CCE Private Certificate > Synchronize CCE/SBC CA Certificate. For details, refer to Managing Cloud Connector Edition Private Certificates.
For details on certificates, refer to: Importing an SBC Edge Server Certificate and Managing Trusted CA Certificates.
Do not modify the node Hostname, but use the public name of SBC in the SIP profile.
Include Page | ||||
---|---|---|---|---|
|
Pagebreak |
---|
Expand | |||||||
---|---|---|---|---|---|---|---|
| |||||||
Non-Media Bypass vs. Media Bypass Deployment Non-Media Bypass Non-Media Bypass is Microsoft Teams Direct Routing related deployment where all media flows between Teams clients in the enterprise and the SBC transit the Teams Phone System based in the Azure cloud.
Media Bypass Media Bypass is a Microsoft Teams Direct Routing deployment where all media flows between Teams clients in the enterprise connect directly to the SBC without transiting the Teams Phone System. |
Include Page | ||||
---|---|---|---|---|
|
Pagebreak |
---|
Caption | ||||
---|---|---|---|---|
| ||||
Pagebreak |
---|
Multiexcerpt include | ||||
---|---|---|---|---|
|
Pagebreak |
---|