Page History

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'}

Panel
Table of Contents

Available_since
Type Available Since Release 8.1.5

Overview

Note
title Caution
When the  Spacevars 0 product3 is deployed in Azure, the  Spacevars 0 product3 does not support Local Media Optimization. Local Media Optimization is available only in on-premises deployments.

Info
title Note
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 

Spacevars
0 company

 

Spacevars
0 product

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

Spacevars
0 product

's media quality and bandwidth usage. The Microsoft Teams Direct Routing media flow can be directly established between the Teams client and the

Spacevars
0 product2

, even if the 

Spacevars
0 product2

does not have Microsoft Teams Direct Routing connectivity. The

Spacevars
0 series

,

Spacevars
0 series2

, and 

Spacevars
0 product3

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

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

Spacevars
0 series

,

Spacevars
0 series2

, and 

Spacevars
0 product3

support all Local Media Optimization roles for Microsoft Teams Direct Routing, this best practice uses the following configurations as examples:

• the 

  Spacevars
  0 product3

  as a Proxy 

  Spacevars
  0 product2

  in the central site

• the

  Spacevars
  0 series

  as a Downstream 

  Spacevars
  0 product2

  in a local branch office

Info
title Note
For the Proxy Spacevars 0 product2 ,  Spacevars 0 company recommends that you use the Spacevars 0 product3 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  Spacevars 0 product3 accommodates the maximum number of Local Media Optimization calls that the subtended (attached behind the Proxy Spacevars 0 product2 ) Downstream Spacevars 0 product2 s carry.

Microsoft Limitations

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 

Spacevars
0 product2

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.

Prerequisites

This section outlines the prerequisites for Local Media Optimization for Microsoft Teams Direct Routing.

Spacevars
0 product2

 Capacity

When deploying Local Media Optimization, the Proxy 

Spacevars
0 product2

has to handle its usual local traffic plus all traffic from the Downstream

Spacevars
0 product2

. You must make sure the Proxy 

Spacevars
0 product2

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 

    Spacevars
    0 product2

    consumes the Proxy Media Mode with Encryption resource.
    
  • The Downstream 

    Spacevars
    0 product2

    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 

    Spacevars
    0 product2

    consumes the SIP with corresponding RTP Media resource.
    
  • The Downstream 

    Spacevars
    0 product2

    consumes the SIP with corresponding RTP Media resource.
    

Microsoft Certified Endpoints

When using LMO for a Proxy Downstream SBC Deployment, all endpoints must be Microsoft compliant/certified.

Firmware Requirement

The Proxy 

Spacevars
0 product2

requires the following firmware:

• Spacevars
  0 product3

  : Release 8.1.5 Build 239 and later, or Release 9.0.0 and later.

• Spacevars
  0 product

  : Release 9.0.x latest GA build.

Spacevars
0 company

 recommends the following versions for the Downstream 

Spacevars
0 product2

for an easier configuration:

• Spacevars
  0 product3

  : Release 8.1.5 Build 239 and later, or Release 9.0.0 and later.

• Spacevars
  0 product

  : Release 9.0 latest GA build.

Info
title Note
This document outlines only the recommended firmware.

Microsoft Direct Routing Configuration

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

Certificate Usage

The Proxy 

Spacevars
0 product2

requires a certificate signed by a public certificate authority.

The Downstream 

Spacevars
0 product2

requires a certificate to support the encrypted media. This certificate can be signed by a private or public certificate authority.

Info
title Note
Since the Proxy  Spacevars 0 product2 and Downstream  Spacevars 0 product2 use the same domain in this best practice, the  Spacevars 0 product reuses the wildcard certificate from the Proxy  Spacevars 0 product2 on each Downstream Spacevars 0 product2 .

Public Certificate

The public certificate must be issued by one of the supported certification authorities (CAs). Wildcard certificates are supported.

• Refer to Microsoft documentation for the supported CAs.

• See Domain Name for certificate formats.

Anchor
domain domain

Domain Name

For the 

Spacevars
0 product

to pair with Microsoft Teams, the 

Spacevars
0 product2

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:

1. On the Microsoft Teams Tenant side, execute Get-CsTenant.
2. Review the output.
3. 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 

   Spacevars
   0 product2

   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 

Spacevars
0 product2

FQDN name sbc1.hybridvoice.org, as long as both names are registered for the tenant.

Caption
0 Table 1 Domain Name Examples
Domain Name* Use for  Spacevars 0 product2 FQDN? FQDN Names - Examples SonusMS01.com Valid names: aepsite6.SonusMS01.com hybridvoice.org 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

Name Resolution

The Proxy 

Spacevars
0 product2

FQDN needs to be resolved in a publicly accessible DNS.

The Proxy 

Spacevars
0 product2

and Downstream 

Spacevars
0 product2

can resolve each other's FQDN with their private IP through using one of the following architectures:

Info
title Note
This best practice uses host entries.

• host entries
  
  • The Proxy 

    Spacevars
    0 product2

    has a host entry resolve each Downstream 

    Spacevars
    0 product2

    FQDN.
  • The Downstream 

    Spacevars
    0 product2

    has a host entry resolve the Proxy 

    Spacevars
    0 product2

    FQDN to its private IP address.
• private DNS
  • The Proxy 

    Spacevars
    0 product2

    and Downstream

    Spacevars
    0 product2

    use a split DNS to resolve each other's FQDN with their private IP address.

Implementation

This best practice uses the FQDN and ports illustrated in the following figure.

Caption
0 Figure 1 FQDN and Port Usage

Anchor
proxy_sbc proxy_sbc

Prepare Proxy

Spacevars
0 product2

This section outlines how to prepare the Proxy

Spacevars
0 product2

.

Install 

Spacevars
0 product2

and Perform Initial Setup

Note
title Caution
Perform this procedure only if you are creating a new  Spacevars 0 product2 for the Proxy role (a greenfield scenario).

Use the following procedure to install the 

Spacevars
0 product2

and perform the initial setup: Installing SBC SWe Edge

Run Easy Config Wizard on Proxy

Spacevars
0 product2

Once your 

Spacevars
0 product2

is up and running, you must configure the 

Spacevars
0 product2

to connect to the Microsoft Teams Direct Routing Server and allow the Downstream 

Spacevars
0 product2

connection.

1. Access a compatible web browser.
2. In the browser, enter the IP address of the 

   Spacevars
   0 product

   in the URL address bar. The Welcome to

   Spacevars
   0 company

   screen is displayed.
3. Review the Pre-Login message.
4. Enter the administrator User Name and Password configured during initial setup.
5. 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.

6. 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.

7. Select Tasks > SBC Easy Setup > Easy Config Wizard.

   Caption
   0 Figure 1 Easy Config Wizard

   
   

8.  In the Application field, select your application. This best practice configures the SIP Trunk ↔ Microsoft Teams.

   Caption
   0 Figure 1 Easy Configuration Step 1

   
   

9. Configure the other fields in Step 1 and click Next.

10. In the SIP Trunk section, enter the information for the central SIP Trunk provider.

11. In the Teams Connection Type field, select Local Media Optimization.

    Caption
    0 Figure 1 Easy Configuration Step 2

    
    

12. Configure the other fields in the Microsoft Teams section and click Next.

13. Review your configuration information in Step 3 and click Finish.

    Caption
    0 Figure 1 Easy Configuration Step 3

    
    

Import Certificate on Proxy

Spacevars
0 product2

This section outlines how to import a certificate on the Proxy

Spacevars
0 product2

.

Anchor
config_certificate config_certificate

Configure and Generate Certificates on the

Spacevars
0 product2

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  Spacevars 0 product2 certificate, along with the intermediate certificate(s) sent by your issuing CA? Did you get the following error message from the Spacevars 0 product2 ? If so, the likely reason is a missing CA Root Certificate. The  Spacevars 0 product2 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 Spacevars 0 product2 , 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 Spacevars 0 product2 ; Load the root certificate, along with the intermediate and  Spacevars 0 product2 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  Spacevars 0 product2 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  Spacevars 0 product2 for SIP traffic with a certificate signed by one of the trusted certification authorities. Request a certificate for the  Spacevars 0 product2 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 Spacevars 0 product2 . Import the Microsoft CA Certificate on the Spacevars 0 product2 . Import the  Spacevars 0 product2 Certificate. Info title Note The certificate is obtained through the Certificate Signing Request (instructions below). The Trusted Root and Intermediary Signing Certificates are obtained from your certification authority. Step 1: Generate a Certificate Signing Request and obtain the certificate from a supported Certification Authority (CA) 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  Spacevars 0 product in the URL address bar. The Welcome to Spacevars 0 company 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  Spacevars 0 product 1 bold 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 Use the generated CSR text from the clipboard to obtain the certificate.  Step 2: Deploy the  Spacevars 0 product2 and Root/Intermediate Certificates on the Spacevars 0 product2 After receiving the certificates from the certification authority, install the  Spacevars 0 product2 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  Spacevars 0 product in the URL address bar. The Welcome to Spacevars 0 company 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  Spacevars 0 product2 certificate, open Settings > Security > SBC Certificates > SBC Primary Certificate. Validate the certificate is installed correctly. Caption 0 Figure 1 Validate Certificate Click Import  and select X.509 Signed Certificate. Validate the certificate is installed correctly. Caption 0 Figure 1 Validate Certificate

Update the Current Call Routing

Note
title Caution
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 

Spacevars
0 product2

and you have already configured one of the following, follow the corresponding instructions:

• If you configured a SIP Trunk or PSTN Access on this

  Spacevars
  0 product2

  , 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

  
  

  1. Select Settings > Call Routing > Call Routing Table.

  2. Select the call routing table for Microsoft Teams Direct Routing.

  3. Select the To Outside (Passthrough) route entry.

  4. 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

     
     

  5. 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

     
     

  6. In the Audio Stream Mode field, select Direct Preferred over DSP.

     Caption
     0 Figure 1 Audio Stream Mode for Teams Direct Routing

     
     

  7. Click Apply.

  8. Click Signaling Groups.
  9. 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

  
  

Disable Validate Server FQDN in TLS Profile

Info
title Note
This section applies to only the Proxy SBC.

Use the following procedure to disable the Validate Server FQDN in the TLS Profile.

1. Access a compatible web browser.
2. In the browser, enter the IP address of the 

   Spacevars
   0 product

   in the URL address bar. The Welcome to

   Spacevars
   0 company

   screen is displayed.
3. Review the Pre-Login message.
4. Enter the administrator User Name and Password configured during initial setup.
5. 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.

6. 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.

7. Select Settings > Security.

8. From the TLS Profiles drop-down menu, select the TLS profile for the Teams Direct Routing TLS.
9. In the Validate Server FQDN field, select Disabled.

Verify the Deployment

After you configure the Proxy

Spacevars
0 product2

, use the following procedure to verify that the 

Spacevars
0 product2

works properly.

1. Access a compatible web browser.
2. In the browser, enter the IP address of the 

   Spacevars
   0 product

   in the URL address bar. The Welcome to

   Spacevars
   0 company

   screen is displayed.
3. Review the Pre-Login message.
4. Enter the administrator User Name and Password configured during initial setup.
5. 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.

6. 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.

7. Select Settings > Signaling Groups.

8. Make sure the Service Status for all signaling groups is Up.

   Caption
   0 Figure 1 Signaling Group Verification

   
   

9. 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

Spacevars
0 product2

You must perform the procedures in this section for each Downstream 

Spacevars
0 product2

you must add. Make sure the FQDN for each Downstream 

Spacevars
0 product2

is different.

Info
title Note
The information to prepare a Downstream SBC applies to both the Spacevars 0 longproduct and Spacevars 0 product3 unless otherwise stated.

Info
When the  Spacevars 0 product 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 

Spacevars
0 product2

and Perform Initial Setup

Note
title Caution
Perform this procedure only if you are creating a new  Spacevars 0 product2 for the Downstream role (a greenfield scenario).

Use the following procedure to install the 

Spacevars
0 product2

and perform the initial setup: Installing SBC 1000/2000

Info
title Note
For the Spacevars 0 product3 , use the following procedure to install the  Spacevars 0 product2 and perform the initial setup: Installing SBC SWe Edge

Run Easy Config Wizard on Downstream

Spacevars
0 product2

Once your 

Spacevars
0 product2

is up and running, you must configure the

Spacevars
0 product2

to connect to the Proxy

Spacevars
0 product2

.

1. Access a compatible web browser.
2. In the browser, enter the IP address of the 

   Spacevars
   0 product

   in the URL address bar. The Welcome to

   Spacevars
   0 company

   screen is displayed.
3. Review the Pre-Login message.
4. Enter the administrator User Name and Password configured during initial setup.
5. 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.

6. 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.

7. Select Tasks > SBC Easy Setup > Easy Config Wizard.

8. In the Application field, select your application. This best practice configures SIP Trunk ↔ Microsoft Teams.

9. In the Teams Connection field, select Teams Downstream SBC.

   Caption
   0 Figure 1 Easy Configuration for Teams Downstream SBC

   
   

10. Configure the other fields in Step 1 and click Next.

11. In the SIP Trunk section, enter the information for the Branch 1 SIP Trunk provider.

    Note
    title Caution
    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

    
    

12. Configure the other fields in the Microsoft Teams section and click Next.

13. Review your configuration information in Step 3 and click Finish.

    Caption
    0 Figure 1 Easy Configuration Step 3 for Teams Downstream SBC

    
    

Import Certificate on Downstream

Spacevars
0 product2

Since the Proxy 

Spacevars
0 product2

and Downstream 

Spacevars
0 product2

use the same domain in this best practice, the 

Spacevars
0 product

reuses the wildcard certificate from the Proxy 

Spacevars
0 product2

on each Downstream

Spacevars
0 product2

.

If your deployment requires a different certificate for the Downstream

Spacevars
0 product2

, see Configure and Generate Certificates on the SBC.

Configure Proxy FQDN Resolution on Downstream

Spacevars
0 product2

1. Access a compatible web browser.
2. In the browser, enter the IP address of the 

   Spacevars
   0 product

   in the URL address bar. The Welcome to

   Spacevars
   0 company

   screen is displayed.
3. Review the Pre-Login message.
4. Enter the administrator User Name and Password configured during initial setup.
5. 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.

6. 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.

7. Select Settings > Protocols > DNS > Hosts.

   Caption
   0 Figure 1 Hosts Settings

   
   

8. Click the + icon to create a host entry.

9. Enter the FQDN and IP address for the Proxy

   Spacevars
   0 product2

   .

   Caption
   0 Figure 1 Create Host Entry for Proxy SBC

   
   

Configure Downstream FQDN Resolution on Proxy

Spacevars
0 product2

1. Access a compatible web browser.
2. In the browser, enter the IP address of the 

   Spacevars
   0 product

   in the URL address bar. The Welcome to

   Spacevars
   0 company

   screen is displayed.
3. Review the Pre-Login message.
4. Enter the administrator User Name and Password configured during initial setup.
5. 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.

6. 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.

7. Select Settings > Protocols > DNS > Hosts.

8. Click the + icon to create a host entry.

9. Enter the FQDN and IP address for the Downstream

   Spacevars
   0 product2

   .

   Caption
   0 Figure 1 Create Host Entry for Downstream SBC

   
   

Update the Current Call Routing

Note
title Caution
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 

Spacevars
0 product2

and you have already configured one of the following, follow the corresponding instructions:

• If you configured a SIP Trunk or PSTN Access on this

  Spacevars
  0 product2

  , you must perform the following procedure to select the previously created signaling group in the From 

  Spacevars
  0 product2

  as Teams Downstream table (see the following example call flow).

  Caption
  0 Figure 1 Call Routing Setup to old PSTN - Downstream SBC

  
  

  1. Select Settings > Call Routing > Call Routing Table.

  2. Select the call routing table for the 

     Spacevars
     0 product2

     as Teams Downstream.

  3. Select the To Outside (Passthrough) route entry.

  4. 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

     
     

  5. In the Destination Signaling Groups field, click Add and add your previously created SIP Trunk or PSTN Access.

  6. Click Apply.
  7. Click Signaling Groups.
  8. 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

  
  

Verify the deployment

After you configure the Downstream

Spacevars
0 product2

, use the following procedure to verify that the 

Spacevars
0 product2

works properly.

1. Access a compatible web browser.
2. In the browser, enter the IP address of the 

   Spacevars
   0 product

   in the URL address bar. The Welcome to

   Spacevars
   0 company

   screen is displayed.
3. Review the Pre-Login message.
4. Enter the administrator User Name and Password configured during initial setup.
5. 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.

6. 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.

7. Select Settings > Signaling Groups.

8. Make sure the Service Status for all signaling groups is Up.

   Caption
   0 Figure 1 Signaling Group Verification for Downstream SBC

   
   

Place a Test Call

Use the following procedure to place a test call.

1. Access a compatible web browser.
2. In the browser, enter the IP address of the 

   Spacevars
   0 product

   in the URL address bar. The Welcome to

   Spacevars
   0 company

   screen is displayed.
3. Review the Pre-Login message.
4. Enter the administrator User Name and Password configured during initial setup.
5. 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.

6. 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.

7. In the WebUI, click the Diagnostics tab.

8. In the left navigation pane, click Test a Call.

9. 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 Spacevars 0 product2 .

     See the following example configuration of testing a call for a Proxy SBC.

     Caption
     0 Figure 1 Test Call for a Proxy SBC - Configuration

     
     

   • 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 Spacevars 0 product2 .

     See the following example configuration of testing a call for a Downstream SBC.

     Caption
     0 Figure 1 Test Call for a Downstream SBC - Configuration

     
     

10. Click OK.

    Caption
    0 Figure 1 Place a Test Call - Example