Add_workflow_for_techpubs |
---|
AUTH1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb41059c8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
JIRAIDAUTH | SYM-2791428481 |
---|
REV5 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
REV6 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
REV3 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cef30cd08a00a02355cd1c2f0155cd26c7f0006a, userName='null'} |
---|
REV4 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c91d01f98a00a02355cd1c2f0155cd26ccd308e6, userName='null'} |
---|
REV1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca2f03d1, userName='null'} |
---|
REV2 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cabc04c3, userName='null'} |
---|
|
...
Overview
Note |
---|
|
When the is deployed in Azure, the does not support Local Media Optimization. Local Media Optimization is available only in on-premises deployments. |
...
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
, Central, 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 |
---|
|
![](/download/attachments/229480520/OverView2.png?version=1&modificationDate=1595008212000&api=v2)
|
This best practice uses describes greenfield and migration deployments and explains the requirements for each case. This best practice includes cautions to specify the deployment scenarios.
...
the
as a Proxy in the central site- the as a Downstream in a local branch office
Info |
---|
|
For the Proxy You can use the Prepare Proxy SBC procedure to configure the as a Central , .The Proxy recommends that you use the information in this best practice applies to a Central configuration unless otherwise stated. |
Info |
---|
|
because it has 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. |
...
- 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.
Firmware Requirement
Microsoft Certified Endpoints
When using LMO for a Proxy Downstream SBC deployment, all endpoints must be Microsoft compliant/certified.
Firmware Requirement
The Proxy
The Proxy requires the following firmware:
- : Release 8.1.5 Build 239 and later, or Release 9.0.0 and later
- : TEAMS_MEDIAOP build 13 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
- : TEAMS_MEDIAOP build 13Release 9.0 latest GA build
Info |
---|
|
This document outlines only the recommended firmware. |
...
- 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
Certificate Usage
Licensing Requirements
The LMO functionality requires the Downstream SBCs to use a Proxy/Central SBC as a registrar, hence this requires the Proxy/Central SBC to have SIP Registration licenses. This applies for both 1000/2000 and SBC SWe Lite.
Certificate Usage
The Proxy The Proxy requires a certificate signed by a public certificate authority.
...
The public certificate must be issued by one of the supported certification authorities (CAs). Wildcard certificates are supported.
...
This section outlines how to prepare the Proxy
.
Install
and Perform Initial Setup Noteinfo |
---|
|
Perform this procedure only if you are creating a new You can use the procedures in this section if you want to configure a Central . Note that the screen captures in this section are not examples of Central for the Proxy role (a greenfield scenario). |
Use the following procedure to install the
...
and perform the initial setup: Installing SBC SWe Lite
...
Run Easy Config Wizard on Proxy
...
...
Once 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 |
---|
|
Image Added
|
In the Application field, select your application. This best practice configures the SIP Trunk ↔ Microsoft Teams.
Caption |
---|
0 | Figure |
---|
1 | Easy Configuration Step 1 |
---|
|
Image Added
|
- 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.
Once 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 |
---|
|
Image Removed
|
|
Image Added
|
Configure the other fields in the Microsoft Teams section and click Next.
Review your configuration information in Step 3 and click Finish.
In the Application field, select your application. This best practice configures the SIP Trunk ↔ Microsoft Teams.
Caption |
---|
0 | Figure |
---|
1 | Easy Configuration Step 13 |
---|
|
Image Removed
|
- Configure the other fields in Step 1 and click Next.
In the SIP Trunk section, enter the information for the central SIP Trunk provider.
Info |
---|
|
For a Central Image Added
|
Import Certificate on Proxy
...
This section outlines how to import a certificate on the Proxy
. Anchor |
---|
| config_certificate |
---|
| config_certificate |
---|
|
Configure and Generate Certificates on the In the Teams Connection Type field, select Local Media Optimization.
Caption |
---|
0 | Figure |
---|
1 | Easy Configuration Step 2 |
---|
|
Image Removed
|
Configure the other fields in the Microsoft Teams section and click Next.
Note |
---|
|
The will not support the Outbound NAT Traversal field until the 9.0.0 release. |
Review your configuration information in Step 3 and click Finish.
Caption |
---|
0 | Figure |
---|
1 | Easy Configuration Step 3 |
---|
|
Image Removed
|
Import Certificate on Proxy
...
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
|
|
...
...
Image Added
If so, the likely reason is a missing CA Root Certificate. The |
|
Warning |
---|
title | Warning: Common Encryption Certificate Issues Arise from Missing Root Certificates |
---|
| Did you only install the CA-signed |
|
Expand |
---|
title | Click here to expand for how to generate Certificates on the SBC |
---|
|
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 certificate, along with including the intermediate certificate(s) sent by your issuing CA?Did you get the following error message from 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
? Image Removed If so, the likely reason is a missing CA Root Certificate. 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 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 server (“leaf”) certificates, refer to this tutorial. For other certificate-related errors, refer to Common Troubleshooting Issues with Certificates in SBC Edge. |
Microsoft Teams Direct Routing allows only TLS connections from the ; for SIP traffic with a certificate signed by one of the trusted certification authorities. Load the root certificate, along with the intermediate and Request a certificate for the 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 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
server (“leaf”) certificates, refer to this tutorial.- .
- Import the Microsoft CA Certificate on the .
- Import
For other certificate-related errors, refer to Common Troubleshooting Issues with Certificates in SBC Edge. Microsoft Teams Direct Routing allows only TLS connections from for SIP traffic with a certificate signed by one of the trusted certification authorities. 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. |
Request a certificate for the External interface and configure it based on the example using GlobalSign as follows: (CSR) .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. Import the Public CA Root/Intermediate Certificate on the .Import the Microsoft CA Certificate on the - Access a compatible web browser.
- In the browser, enter the IP address of the
product2- in the URL address bar. The Welcome to
Import the product2 Certificate- screen is displayed.
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 SBC Edge 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 |
---|
| Image Removed
| Use the generated CSR text from the clipboard to obtain the certificate. - 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 SBC Edge 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 |
---|
| Image Added
|
- 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
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- certificate, open Settings > Security > SBC Certificates > SBC Primary Certificate.
Validate the certificate is installed correctly. Caption |
---|
0 | Figure |
---|
1 | Validate Certificate |
---|
| Image Added
|
- Click Import and select X.509 Signed Certificate.
Validate the certificate is installed correctly. Caption |
---|
0 | Figure |
---|
1 | Validate Certificate |
---|
| Image Added
|
|
Update the Current Call Routing
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:Validate the certificate is installed correctly.
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 |
---|
|
Image Added
|
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.
...
Image Removed
...
Remove Border Element for Teams Direct Routing |
|
Image Added
|
In the Destination Signaling Groups field, click Add and add your previously created SIP Trunk or PSTN Access.
...
Add SIP Trunk or PSTN Access for Teams Direct Routing |
|
Image Added
|
In the Audio Stream Mode field, select Direct Preferred over DSP.
Caption |
---|
0 | Figure |
---|
1 | Audio Stream Mode for Teams Direct Routing |
---|
|
Image Added
|
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
...
Image Removed
Update the Current Call Routing
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 new Teams - Proxy SBC |
---|
|
Image Removed
|
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 |
---|
|
Image Removed
|
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 |
---|
|
Image Removed
|
In the Audio Stream Mode field, select Direct Preferred over DSP.
Caption |
---|
0 | Figure |
---|
1 | Audio Stream Mode for Teams Direct Routing |
---|
|
Image Removed
|
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 |
---|
|
Image Removed
|
Disable Validate Server FQDN in TLS Profile
Info |
---|
|
This section applies to only the Proxy SBC for the Release 8.1.5. |
Use the following procedure to disable the Validate Server FQDN in the TLS Profile.
Image Added
|
Disable Validate Server FQDN in TLS Profile
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.
Verify the Deployment
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 > SecuritySignaling Groups.
- 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.
Verify the Deployment
...
Make sure the Service Status for all signaling groups is Up.
Caption |
---|
0 | Figure |
---|
1 | Signaling Group Verification |
---|
|
Image Added
|
- If the Service Status for the Teams Direct Routing signaling group is Down, refer to Best Practice - Troubleshoot Issues with Microsoft Teams Direct Routing.
Prepare Downstream
You must perform the procedures in this section for each Downstream , use the following procedure to verify that the
works properly....
you must add. Make sure the FQDN for each Downstream
is different....
Info |
---|
|
The information to prepare a Downstream SBC applies to both the |
...
...
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 |
---|
|
Image Removed
|
...
Info |
---|
When the SBC Edge 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. |
Install
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/2000 Info |
---|
|
For the , use the following procedure to install the and perform the initial setup: Installing SBC SWe Lite |
Run Easy Config Wizard on Downstream
Prepare Downstream
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. |
Install
and Perform Initial Setup...
...
Once your
is up and running, you must configure the ...
to connect to the Proxy
Use the following procedure to install the and perform the initial setup: Installing SBC 1000/2000...
...
.
- 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 |
---|
|
Image Added
|
- 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. |
Run Easy Config Wizard on Downstream
Once 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 Step 2 for Teams Downstream SBC |
---|
|
Image Removed Image Added
|
- 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 |
---|
|
Image Removed
|
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 |
---|
|
![](/download/attachments/229480520/EasyConfigWizard_Step3_TeamsDownstreamSBC.png?version=1&modificationDate=1595008211000&api=v2)
|
...
- 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.
.
In the WebUI, click the Diagnostics tab.
In the left navigation pane, click Test a Call.
Configure the parameters according to your SBC.
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 |
---|
|
Image Removed
|
Use the following table to configure the parameters for a
Central Proxy SBC.
Caption |
---|
0 | Table |
---|
1 | Test Call for a Central 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 | Central
|
See the following example configuration of testing a call for a Central Proxy SBC.
Caption |
---|
0 | Figure |
---|
1 | Test Call for a Central Proxy SBC - Configuration |
---|
|
Image Removed Image Added
|
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 |
---|
|
![](/download/attachments/229480520/TestaCall_DownstreamSBC.png?version=1&modificationDate=1595008213000&api=v2)
|
Click OK.
Caption |
---|
0 | Figure |
---|
1 | Place a Test Call - Example |
---|
|
![](/download/thumbnails/229480520/Calling_Example.png?version=1&modificationDate=1595008213000&api=v2)
|
...