Add_workflow_for_techpubs |
---|
AUTH1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb41059c, userName='null'} |
---|
JIRAIDAUTH | SYM-27914 |
---|
REV5 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
REV6 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
REV3 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cef30cd0, userName='null'} |
---|
REV4 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c91d01f9, userName='null'} |
---|
REV1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca2f03d1, userName='null'} |
---|
REV2 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cabc04c3, userName='null'} |
---|
|
Available_since |
---|
Type | Available Since |
---|
Release | 8.1.5 |
---|
|
Note |
---|
|
When the is deployed in Azure, the does not support Local Media Optimization. Local Media Optimization is available only in on-premises deployments. |
Info |
---|
|
This best practice uses the term Microsoft Teams Direct Routing, which is also known as Phone System Direct Routing. |
This best practice outlines how to use the
to configure Local Media Optimization for Microsoft Teams Direct Routing. Local Media Optimization allows the Microsoft Teams Direct Routing media flow to always use the shortest path to improve the
's media quality and bandwidth usage. The Microsoft Teams Direct Routing media flow can be directly established between the Teams client and the
, even if the
does not have Microsoft Teams Direct Routing connectivity. The
,
, and
support the Proxy and Downstream SBCs. For more details about this feature, refer to
Local Media Optimization for Direct Routing.
Caption |
---|
0 | Figure |
---|
1 | Microsoft Teams Direct Routing Media Flow |
---|
|
![OverView2.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
This best practice describes greenfield and migration deployments and explains the requirements for each case. This best practice includes cautions to specify the deployment scenarios.
Though the
,
, and
support all Local Media Optimization roles for Microsoft Teams Direct Routing, this best practice uses the following configurations as examples:
the
as a Proxy in the central site- the as a Downstream in a local branch office
Info |
---|
|
For the Proxy , recommends that you use the because it has higher CPS (up to 10 CPS) and higher session density (up to 1200 simultaneous Direct Routing calls).Make sure the licensed quantity of sessions on the accommodates the maximum number of Local Media Optimization calls that the subtended (attached behind the Proxy ) Downstream s carry. |
Microsoft does not support Music on Hold. You should disable Music on Hold for all users that use Local Media Optimization. To disable Music on Hold, refer to Set-CsTeamsCallingPolicy.
Microsoft does not support Early 183. You should disable Early 183 for all
signaling groups that use Local Media Optimization. For information about Early 183, refer to the Early 183 section in
Creating and Modifying SIP Signaling Groups.
This section outlines the prerequisites for Local Media Optimization for Microsoft Teams Direct Routing.
Capacity
When deploying Local Media Optimization, the Proxy
has to handle its usual local traffic plus all traffic from the Downstream
. You must make sure the Proxy
has the capacity and the license to handle the load. See the following load impacts:
- Call made to and from a Teams client that is internal to the customer network:
- The Proxy consumes the Proxy Media Mode with Encryption resource.
- The Downstream consumes the SIP with corresponding RTP Media resource.
- Call made to and from a Teams client that is external to the customer network:
- The Proxy consumes the SIP with corresponding RTP Media resource.
- The Downstream consumes the SIP with corresponding RTP Media resource.
When using LMO for a Proxy Downstream SBC Deployment, all endpoints must be Microsoft compliant/certified.
The Proxy
requires the following firmware:
- : Release 8.1.5 Build 239 and later, or Release 9.0.0 and later.
- : Release 9.0.x latest GA build.
recommends the following versions for the Downstream
for an easier configuration:- : Release 8.1.5 Build 239 and later, or Release 9.0.0 and later.
- : Release 9.0 latest GA build.
Info |
---|
|
This document outlines only the recommended firmware. |
You must configure the following for Microsoft Teams Direct Routing:
- You must plan the Microsoft Teams tenant for Local Media Optimization usage according to the Local Media Optimization for Direct Routing document.
- You must configure the Microsoft Teams tenant for Local Media Optimization usage according to the Configure Local Media Optimization for Direct Routing document. When you configure the Microsoft Teams Direct Routing, you must also configure the following items:
CsTenantTrustedIPAddress
CsTenantNetworkRegion
CsTenantNetworkSite
CsTenantNetworkSubnet
CSOnlinePSTNGateway
CsOnlineVoiceRoute
The Proxy requires a certificate signed by a public certificate authority.
The Downstream requires a certificate to support the encrypted media. This certificate can be signed by a private or public certificate authority.
Info |
---|
|
Since the Proxy and Downstream use the same domain in this best practice, the reuses the wildcard certificate from the Proxy on each Downstream . |
The public certificate must be issued by one of the supported certification authorities (CAs). Wildcard certificates are supported.
Domain Name
For the
to pair with Microsoft Teams, the
FQDN domain name must match a name registered in both the
Domains and
DomainUrlMap fields of the Tenant.
Verify the correct domain name is configured for the Tenant as follows:
- On the Microsoft Teams Tenant side, execute Get-CsTenant.
- Review the output.
- Verify that the Domain Name configured is listed in the Domains and DomainUrlMap attributes for the Tenant. If the Domain Name is incorrect or missing, the will not pair with Microsoft Teams.
Users may be from any SIP domain registered for the tenant. For example, you can configure user user@SonusMS01.com with the
FQDN name
sbc1.hybridvoice.org, as long as both names are registered for the tenant.
Caption |
---|
0 | Table |
---|
1 | Domain Name Examples |
---|
|
Domain Name* | | FQDN Names - Examples |
---|
SonusMS01.com | ![(tick)](/s/ac9bgu/9012/1d0vx1s/_/images/icons/emoticons/check.svg) | Valid names: | hybridvoice.org | ![(tick)](/s/ac9bgu/9012/1d0vx1s/_/images/icons/emoticons/check.svg) | Valid names: - sbc1. hybridvoice.org
- ussbcs15. hybridvoice.org
- europe. hybridvoice.org
Non-Valid name: sbc1.europe.hybridvoice.org (requires registering domain name europe. hybridvoice.org in “Domains” first) |
*Do not use the *.onmicrosoft.com tenant for the domain name. |
Caption |
---|
0 | Figure |
---|
1 | Configure Domain Names - Example |
---|
|
![Domain.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2) |
The Proxy
FQDN needs to be resolved in a publicly accessible DNS.
The Proxy
and Downstream
can resolve each other's FQDN with their private IP through using one of the following architectures:
Info |
---|
|
This best practice uses host entries. |
- host entries
- The Proxy has a host entry resolve each Downstream FQDN.
- The Downstream has a host entry resolve the Proxy FQDN to its private IP address.
- private DNS
- The Proxy and Downstream use a split DNS to resolve each other's FQDN with their private IP address.
This best practice uses the FQDN and ports illustrated in the following figure.
Caption |
---|
0 | Figure |
---|
1 | FQDN and Port Usage |
---|
|
![Design.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
Prepare Proxy
This section outlines how to prepare the Proxy
.
and Perform Initial Setup
Note |
---|
|
Perform this procedure only if you are creating a new for the Proxy role (a greenfield scenario). |
Use the following procedure to install the
and perform the initial setup:
Installing SBC SWe EdgeOnce your
is up and running, you must configure the
to connect to the Microsoft Teams Direct Routing Server and allow the Downstream
connection.
- Access a compatible web browser.
- In the browser, enter the IP address of the in the URL address bar. The Welcome to screen is displayed.
- Review the Pre-Login message.
- Enter the administrator User Name and Password configured during initial setup.
- If the Acknowledge Pre-Login Message checkbox is displayed, click on it to acknowledge you have reviewed the pre-login information above. After initial login, this checkbox can be enabled and disabled via the Global Security Options. By default, this checkbox is configured as disabled.
Click Login. The main screen provides all WebUI functions, including tabbed options, menu tree, device name, and the last login date and time of the system.
Select Tasks > SBC Easy Setup > Easy Config Wizard.
Caption |
---|
0 | Figure |
---|
1 | Easy Config Wizard |
---|
|
![SBCEasySetup_EasyConfigWizard.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
In the Application field, select your application. This best practice configures the SIP Trunk ↔ Microsoft Teams.
Caption |
---|
0 | Figure |
---|
1 | Easy Configuration Step 1 |
---|
|
![EasyConfigWizard_Step1_TeamsDirectRouting.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
- Configure the other fields in Step 1 and click Next.
In the SIP Trunk section, enter the information for the central SIP Trunk provider.
In the Teams Connection Type field, select Local Media Optimization.
Caption |
---|
0 | Figure |
---|
1 | Easy Configuration Step 2 |
---|
|
![EasyConfigWizard_Step2_TeamsDirectRouting.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
Configure the other fields in the Microsoft Teams section and click Next.
Review your configuration information in Step 3 and click Finish.
Caption |
---|
0 | Figure |
---|
1 | Easy Configuration Step 3 |
---|
|
![EasyConfigWizard_Step3_TeamsDirectRouting.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
This section outlines how to import a certificate on the Proxy
.
Anchor |
---|
| config_certificate |
---|
| config_certificate |
---|
|
Configure and Generate Certificates on the
Expand |
---|
title | Click here to expand for how to generate Certificates on the SBC |
---|
|
Warning |
---|
title | Warning: Common Encryption Certificate Issues Arise from Missing Root Certificates |
---|
| - Did you only install the CA-signed certificate, along with the intermediate certificate(s) sent by your issuing CA?
- Did you get the following error message from the ?
![Certificate_Error.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
If so, the likely reason is a missing CA Root Certificate. The does not have any pre-installed CA root X.509 certificates, unlike typical browsers found on your PC. Ensure the entire certificate chain of trust is installed on the , including the root certificate. Acquire the CA root certificate as follows:- Contact your system administrator or certificate vendor to acquire the root, and any further missing intermediate certificate(s) to provision the entire certificate chain of trust within the ;
- Load the root certificate, along with the intermediate and certificates, according to Importing Trusted Root CA Certificates.
NOTE: Root certificates are easily acquired from the certificate authorities. For example, the root certificate for the GoDaddy Class 2 Certification Authority may be found at https://ssl-ccp.godaddy.com/repository?origin=CALLISTO . For more information about root certificates, intermediate certificates, and the server (“leaf”) certificates, refer to this tutorial.For other certificate-related errors, refer to Common Troubleshooting Issues with Certificates in SBC Edge Portfolio. |
Microsoft Teams Direct Routing allows only TLS connections from the for SIP traffic with a certificate signed by one of the trusted certification authorities.Request a certificate for the External interface and configure it based on the example using GlobalSign as follows:- Generate a Certificate Signing Request (CSR) and obtain the certificate from a supported Certification Authority.
- Import the Public CA Root/Intermediate Certificate on the .
- Import the Microsoft CA Certificate on the .
- Import the Certificate.
Info |
---|
| The certificate is obtained through the Certificate Signing Request (instructions below). The Trusted Root and Intermediary Signing Certificates are obtained from your certification authority. |
Many CA's do not support a private key with a length of 1024 bits. Validate with your CA requirements and select the appropriate length of the key. - Access a compatible web browser.
- In the browser, enter the IP address of the in the URL address bar. The Welcome to screen is displayed.
- Review the Pre-Login message.
- Enter the administrator User Name and Password configured during initial setup.
- If the Acknowledge Pre-Login Message checkbox is displayed, click on it to acknowledge you have reviewed the pre-login information above. After initial login, this checkbox can be enabled and disabled via the Global Security Options. By default, this checkbox is configured as disabled.
Click Login. The main screen provides all WebUI functions, including tabbed options, menu tree, device name, and the last login date and time of the system. - Access Settings > Security > SBC Certificates.
Click Generate CSR. Enter data in the required fields. Click OK. After the Certificate Signing request finishes generating, copy the result to the clipboard. Caption |
---|
0 | Figure |
---|
1 | Generate Certificate Signing Request |
---|
| ![GenerateCSR.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
- Use the generated CSR text from the clipboard to obtain the certificate.
and Root/Intermediate Certificates on the After receiving the certificates from the certification authority, install the Certificate and Root/Intermediate Certificates as follows:- Obtain Trusted Root and Intermediary signing certificates from your certification authority.
- Access a compatible web browser.
- In the browser, enter the IP address of the in the URL address bar. The Welcome to screen is displayed.
- Review the Pre-Login message.
- Enter the administrator User Name and Password configured during initial setup.
- If the Acknowledge Pre-Login Message checkbox is displayed, click on it to acknowledge you have reviewed the pre-login information above. After initial login, this checkbox can be enabled and disabled via the Global Security Options. By default, this checkbox is configured as disabled.
Click Login. The main screen provides all WebUI functions, including tabbed options, menu tree, device name, and the last login date and time of the system. - To install Trusted Root Certificates, click Settings > Security > SBC Certificates > Trusted Root Certificates.
- Click Import and select the trusted root certificates.
- To install the certificate, open Settings > Security > SBC Certificates > SBC Primary Certificate.
Validate the certificate is installed correctly. Caption |
---|
0 | Figure |
---|
1 | Validate Certificate |
---|
| ![Trusted_Certificates.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
- Click Import and select X.509 Signed Certificate.
Validate the certificate is installed correctly. Caption |
---|
0 | Figure |
---|
1 | Validate Certificate |
---|
| ![Validate_SBCEdgeCertificate.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
|
Note |
---|
|
Perform this procedure only if you are using a node that is already configured with another signaling group (a migration scenario). |
If this is not a newly deployed
and you have already configured one of the following, follow the corresponding instructions:
If you configured a SIP Trunk or PSTN Access on this
, you must perform the following procedure to select the previously created signaling group in the From Microsoft Teams Direct Routing table (see the following example call flow). Caption |
---|
0 | Figure |
---|
1 | Call Routing Setup to old PSTN - Proxy SBC |
---|
|
![HubToOldPSTN_CallFlow.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
Select Settings > Call Routing > Call Routing Table.
- Select the call routing table for Microsoft Teams Direct Routing.
Select the To Outside (Passthrough) route entry.
In the Destination Signaling Groups field, select the Border Element signaling group and click Remove.
Caption |
---|
0 | Figure |
---|
1 | Remove Border Element for Teams Direct Routing |
---|
|
![CallRouting_CallRoutingTable_FromMicrosoftTeamsDR_BorderElement.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
In the Destination Signaling Groups field, click Add and add your previously created SIP Trunk or PSTN Access.
Caption |
---|
0 | Figure |
---|
1 | Add SIP Trunk or PSTN Access for Teams Direct Routing |
---|
|
![CallRouting_CallRoutingTable_FromMicrosoftTeamsDR_AddSG.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
In the Audio Stream Mode field, select Direct Preferred over DSP.
Caption |
---|
0 | Figure |
---|
1 | Audio Stream Mode for Teams Direct Routing |
---|
|
![CallRouting_CallRoutingTable_FromMicrosoftTeamsDR_DirectPreferredOverDSP.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
Click Apply.
- Click Signaling Groups.
- Delete the Border Element signaling group.
If you configured a connection to Teams Direct Routing or Skype for Business, you must remove the previously created signaling group (see the following example call flow).
Caption |
---|
0 | Figure |
---|
1 | Call Routing Setup to new Teams - Proxy SBC |
---|
|
![HubToNewTeams_CallFlow.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
Info |
---|
|
This section applies to only the Proxy SBC. |
Use the following procedure to disable the Validate Server FQDN in the TLS Profile.
- Access a compatible web browser.
- In the browser, enter the IP address of the in the URL address bar. The Welcome to screen is displayed.
- Review the Pre-Login message.
- Enter the administrator User Name and Password configured during initial setup.
- If the Acknowledge Pre-Login Message checkbox is displayed, click on it to acknowledge you have reviewed the pre-login information above. After initial login, this checkbox can be enabled and disabled via the Global Security Options. By default, this checkbox is configured as disabled.
Click Login. The main screen provides all WebUI functions, including tabbed options, menu tree, device name, and the last login date and time of the system.
Select Settings > Security.
- From the TLS Profiles drop-down menu, select the TLS profile for the Teams Direct Routing TLS.
- In the Validate Server FQDN field, select Disabled.
After you configure the Proxy
, use the following procedure to verify that the
works properly.
- Access a compatible web browser.
- In the browser, enter the IP address of the in the URL address bar. The Welcome to screen is displayed.
- Review the Pre-Login message.
- Enter the administrator User Name and Password configured during initial setup.
- If the Acknowledge Pre-Login Message checkbox is displayed, click on it to acknowledge you have reviewed the pre-login information above. After initial login, this checkbox can be enabled and disabled via the Global Security Options. By default, this checkbox is configured as disabled.
Click Login. The main screen provides all WebUI functions, including tabbed options, menu tree, device name, and the last login date and time of the system.
Select Settings > Signaling Groups.
Make sure the Service Status for all signaling groups is Up.
Caption |
---|
0 | Figure |
---|
1 | Signaling Group Verification |
---|
|
![image2020-4-16_12-26-27.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
- If the Service Status for the Teams Direct Routing signaling group is Down, refer to Best Practice - Troubleshoot Issues with Microsoft Teams Direct Routing.
You must perform the procedures in this section for each Downstream
you must add. Make sure the FQDN for each Downstream
is different.
Info |
---|
|
The information to prepare a Downstream SBC applies to both the and unless otherwise stated. |
Info |
---|
When the is acting as the Downstream SBC and interacting with the SBC Core, the Key Identifier Length in the SRTP should be configured as "0". The SBC Core does not support MKI and ignores the Crypto lines which has the MKI parameter. |
and Perform Initial Setup
Note |
---|
|
Perform this procedure only if you are creating a new for the Downstream role (a greenfield scenario). |
Use the following procedure to install the
and perform the initial setup:
Installing SBC 1000/2000Once your
is up and running, you must configure the
to connect to the Proxy
.
- Access a compatible web browser.
- In the browser, enter the IP address of the in the URL address bar. The Welcome to screen is displayed.
- Review the Pre-Login message.
- Enter the administrator User Name and Password configured during initial setup.
- If the Acknowledge Pre-Login Message checkbox is displayed, click on it to acknowledge you have reviewed the pre-login information above. After initial login, this checkbox can be enabled and disabled via the Global Security Options. By default, this checkbox is configured as disabled.
Click Login. The main screen provides all WebUI functions, including tabbed options, menu tree, device name, and the last login date and time of the system.
Select Tasks > SBC Easy Setup > Easy Config Wizard.
In the Application field, select your application. This best practice configures SIP Trunk ↔ Microsoft Teams.
In the Teams Connection field, select Teams Downstream SBC.
Caption |
---|
0 | Figure |
---|
1 | Easy Configuration for Teams Downstream SBC |
---|
|
![EasyConfigWizard_Step1_TeamsDownstreamSBC.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
- Configure the other fields in Step 1 and click Next.
In the SIP Trunk section, enter the information for the Branch 1 SIP Trunk provider.
Note |
---|
|
You must target the Proxy with an FQDN for the TLS to properly establish. |
Caption |
---|
0 | Figure |
---|
1 | Easy Configuration Step 2 for Teams Downstream SBC |
---|
|
![EasyConfigWizard_Step2_TeamsDownstreamSBC.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
- Configure the other fields in the Microsoft Teams section and click Next.
Review your configuration information in Step 3 and click Finish.
Caption |
---|
0 | Figure |
---|
1 | Easy Configuration Step 3 for Teams Downstream SBC |
---|
|
![EasyConfigWizard_Step3_TeamsDownstreamSBC.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
Since the Proxy
and Downstream
use the same domain in this best practice, the
reuses the wildcard certificate from the Proxy
on each Downstream
.
If your deployment requires a different certificate for the Downstream
, see
Configure and Generate Certificates on the SBC.
- Access a compatible web browser.
- In the browser, enter the IP address of the in the URL address bar. The Welcome to screen is displayed.
- Review the Pre-Login message.
- Enter the administrator User Name and Password configured during initial setup.
- If the Acknowledge Pre-Login Message checkbox is displayed, click on it to acknowledge you have reviewed the pre-login information above. After initial login, this checkbox can be enabled and disabled via the Global Security Options. By default, this checkbox is configured as disabled.
Click Login. The main screen provides all WebUI functions, including tabbed options, menu tree, device name, and the last login date and time of the system.
Select Settings > Protocols > DNS > Hosts.
Caption |
---|
|
![Protocols_DNS_Hosts.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
Click the + icon to create a host entry.
Enter the FQDN and IP address for the Proxy
. Caption |
---|
0 | Figure |
---|
1 | Create Host Entry for Proxy SBC |
---|
|
![Protocols_DNS_Hosts_Proxy.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
- Access a compatible web browser.
- In the browser, enter the IP address of the in the URL address bar. The Welcome to screen is displayed.
- Review the Pre-Login message.
- Enter the administrator User Name and Password configured during initial setup.
- If the Acknowledge Pre-Login Message checkbox is displayed, click on it to acknowledge you have reviewed the pre-login information above. After initial login, this checkbox can be enabled and disabled via the Global Security Options. By default, this checkbox is configured as disabled.
Click Login. The main screen provides all WebUI functions, including tabbed options, menu tree, device name, and the last login date and time of the system.
Select Settings > Protocols > DNS > Hosts.
Click the + icon to create a host entry.
Enter the FQDN and IP address for the Downstream
. Caption |
---|
0 | Figure |
---|
1 | Create Host Entry for Downstream SBC |
---|
|
![Protocols_DNS_Hosts_Downstream.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
Note |
---|
|
Perform this procedure only if you are using a node that is already configured with another signaling group (a migration scenario). |
If this is not a newly deployed
and you have already configured one of the following, follow the corresponding instructions:
If you configured a SIP Trunk or PSTN Access on this
, you must perform the following procedure to select the previously created signaling group in the From as Teams Downstream table (see the following example call flow). Caption |
---|
0 | Figure |
---|
1 | Call Routing Setup to old PSTN - Downstream SBC |
---|
|
![HubToOldPSTN_CallFlow.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
Select Settings > Call Routing > Call Routing Table.
- Select the call routing table for the as Teams Downstream.
Select the To Outside (Passthrough) route entry.
In the Destination Signaling Groups field, select the Border Element signaling group and click Remove.
Caption |
---|
0 | Figure |
---|
1 | Remove Border Element for Downstream SBC |
---|
|
![CallRouting_CallRoutingTable_FromSBCTeamsSpoke_BorderElement.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
In the Destination Signaling Groups field, click Add and add your previously created SIP Trunk or PSTN Access.
- Click Apply.
- Click Signaling Groups.
- Delete the Border Element signaling group.
If you configured a connection to Teams Direct Routing or Skype for Business, you must remove the previously created signaling group (see the following example call flow).
Caption |
---|
0 | Figure |
---|
1 | Call Routing Setup to new Teams - Downstream SBC |
---|
|
![HubToNewTeams_CallFlow.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
After you configure the Downstream
, use the following procedure to verify that the
works properly.
- Access a compatible web browser.
- In the browser, enter the IP address of the in the URL address bar. The Welcome to screen is displayed.
- Review the Pre-Login message.
- Enter the administrator User Name and Password configured during initial setup.
- If the Acknowledge Pre-Login Message checkbox is displayed, click on it to acknowledge you have reviewed the pre-login information above. After initial login, this checkbox can be enabled and disabled via the Global Security Options. By default, this checkbox is configured as disabled.
Click Login. The main screen provides all WebUI functions, including tabbed options, menu tree, device name, and the last login date and time of the system.
Select Settings > Signaling Groups.
Make sure the Service Status for all signaling groups is Up.
Caption |
---|
0 | Figure |
---|
1 | Signaling Group Verification for Downstream SBC |
---|
|
![image2020-4-16_13-19-23.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
Use the following procedure to place a test call.
- Access a compatible web browser.
- In the browser, enter the IP address of the in the URL address bar. The Welcome to screen is displayed.
- Review the Pre-Login message.
- Enter the administrator User Name and Password configured during initial setup.
- If the Acknowledge Pre-Login Message checkbox is displayed, click on it to acknowledge you have reviewed the pre-login information above. After initial login, this checkbox can be enabled and disabled via the Global Security Options. By default, this checkbox is configured as disabled.
Click Login. The main screen provides all WebUI functions, including tabbed options, menu tree, device name, and the last login date and time of the system.
In the WebUI, click the Diagnostics tab.
In the left navigation pane, click Test a Call.
Configure the parameters according to your SBC.
Use the following table to configure the parameters for a Proxy SBC.
Caption |
---|
0 | Table |
---|
1 | Test Call for a Proxy SBC - Parameters |
---|
|
Parameter | Value |
---|
Destination Number | Number assigned to a Teams user. | Origination/Calling Number | Number assigned to a Local user. | Call Routing Table | The routing table that handles the call from the Proxy . |
|
See the following example configuration of testing a call for a Proxy SBC.
Caption |
---|
0 | Figure |
---|
1 | Test Call for a Proxy SBC - Configuration |
---|
|
![TestaCall_ProxySBC.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
Use the following table to configure the parameters for a Downstream SBC.
Caption |
---|
0 | Table |
---|
1 | Test Call for a Downstream SBC - Parameters |
---|
|
Parameter | Value |
---|
Destination Number | Number assigned to a Teams user. | Origination/Calling Number | Number assigned to a Local user. | Call Routing Table | The routing table that handles the call from the Downstream . |
|
See the following example configuration of testing a call for a Downstream SBC.
Caption |
---|
0 | Figure |
---|
1 | Test Call for a Downstream SBC - Configuration |
---|
|
![TestaCall_DownstreamSBC.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|
Click OK.
Caption |
---|
0 | Figure |
---|
1 | Place a Test Call - Example |
---|
|
![Calling_Example.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
|