Page History

...

1. Devices must be configured and supporting Phone System voice services. To confirm support, please place a call from the Teams client UI to another Teams client within the enterprise. If such a call successfully completes, the device is configured to successfully offer Phone System services.
2. Devices must be configured with a firmware release that supports survivability for Teams deployments.
   

3. As an optionOptionally, Yealink devices may be configured to communicate with the the

   Spacevars
   0 product 1 bold

   using TLS (Transport Layer Security, used for SIP signaling encryption) and SRTP (Secure Real-time Transport Protocol, used for media encryption).

   Anchor
   Azure encryption Azure encryption

   Note
   title Use of Signaling and Media Encryption Strongly Recommended for Azure-based SBC Deployments
   Ribbon Communications and Yealink strongly recommend the use of TLS and SRTP for secure encrypted communication between the Yealink devices and the SBC, especially when the latter is deployed in the Azure public cloud. When the SBC is deployed in Azure, the use of encryption safeguards the communication that transits the public Internet. Please refer to the following links to configure the Yealink devices and the SBC for secure communication: For the Yealink devices, refer to the relevant administrator guide, and undertake the configuration as a prerequisite step (now). An example administrator guide with encryption configuration instructions (for the desk Phone T58A) is available at support.yealink.com. For the Ribbon Spacevars 0 product , configure TLS & SRTP encryption later, within the SIP Local Registrar step and the Signaling Group configuration step. Note the following: The  Spacevars 0 product should possess an X.509 certificate that is acquired during the Teams Direct Routing prerequisite step, including the CA (Certificate Authority) chain of trust. Refer to Configure a Certificate for the SBC Direct Routing Interface for more information regarding the assignment of the certificate during Teams Direct Routing setup.  The  Spacevars 0 product X.509 certificate, exchanged during the TLS handshake with the Yealink device, must be signed by a CA that the Yealink devices will trust for successful communication.  The list of recognized CAs are found in the relevant Yealink device administrator guide posted at support.yealink.com; If the certificate is signed by an unrecognized CA, you must load the relevant sections of the certificate's chain of trust from the SBC into the Yealink devices so that the certificate is subsequently trusted. Refer to Working with Certificates for certificate chains within the SBC.

   
   

...

1. Initial setup is complete.

   • SBC 1000 and SBC 2000 initial setup steps

   • SBC SWe Edge on-premise deployment initial steps

     Note
     title SBC SWe Lite Deployed On-Premises Initial Setup Clarifications
     The  Spacevars 0 series3 initial setup instructions include content related to feature licensing, trials, and easy configuration. Note the following: You can choose to undertake feature licensing under the initial setup instructions, please ensure the minimum licensing requirements listed in step 2 are addressed; You can choose to configure the  Spacevars 0 series3 for Yealink Teams Client Local Survivability with a trial license and as such, temporarily disregard the instructions in step 2; however, there are considerations: Note the number of registered Yealink devices and session capacity will be limited to the capabilities of the trial license; Ribbon does not support the use of trial licenses for live traffic (production) deployments. Please do not undertake any Easy Configuration Wizard actions at this time; the easy configuration actions in a Teams-related deployment has additional considerations, as defined in step 3

     
     

2. Anchor
   Licensing Licensing

   Licensing has been acquired and properly assigned.

   • The following SIP registration license(s) are required for registering Yealink devices:

     • SBC 1000 and SBC 2000 registration licenses

     • Spacevars
       0 series3

        licenses for on-premises deployments
   • The following SIP session licenses may be required if the 

     Spacevars
     0 product

     connects the IP-based SIP signaling and RTP media to and from subtended Yealink clients to an IP-based client (for example, a SIP trunk or a SIP-based IP PBX) instead of a legacy TDM connection (for example, a PRI/BRI trunk or an analog FXS/FXO destination):

     • SBC 1000 and SBC 2000 SIP session licenses;

     • Spacevars
       0 series3

        licenses for on-premises deployments.

       Info
       For instructions on how to obtain and apply licenses, refer to Node-Locked Licensing - SBC 1000 /and 2000 and SBC SWe Edge.

       
       

3. Anchor
   Teams configuration Teams configuration

   Teams Direct Routing (DR) basic configuration has been undertaken. Teams DR basic configuration is documented in the on-premises best practice. Please ensure all instructions are executed as documented in the following sections of that best practice:

   • Configuration Prerequisites

   • Configure Direct Routing For Greenfield Deployment, including the execution of one of the following easy configuration wizard scenarios related to Teams DR, such as:
     • SIP trunks ↔ Microsoft Phone System Direct Routing
     • ISDN PSTN ↔ Microsoft Phone System Direct Routing
     • IP PBX ↔ Microsoft Phone System Direct Routing
   • Refer to the Teams Direct Routing troubleshooting details for final review and testing of the Teams Direct Routing capable 

     Spacevars
     0 product

     device.
4. Networking device updates have been applied to permit 

   Spacevars
   0 product 1 bold

    ↔ subtended registered Yealink client device communication. The 

   Spacevars
   0 product

   and the Yealink clients that will attempt to register may not be in the same office/LAN; they may be located in different offices accessible through the enterprise's WAN, or may only be accessible through the internet. As such, the following devices must be configured to ensure successful communication between the parties:

...

1. Initial setup is complete per the instructions applicable for an Azure deployment.

   Note
   title SBC SWe Edge Deployed in Azure Initial Setup Clarifications
   The  Spacevars 0 series3 initial setup instructions include content related to feature licensing, trials, and easy configuration. Note the following: You can choose to undertake feature licensing under the initial setup instructions, please ensure the minimum licensing requirements listed in step 2 are addressed. You can choose to configure the  Spacevars 0 series3 for Yealink Teams Client Local Survivability with a trial license and as such, temporarily disregard the instructions in step 2; however, there are considerations: Note the number of registered Yealink devices and session capacity will be limited to the capabilities of the trial license. Ribbon does not support the use of trial licenses for live traffic (production) deployments. Please do not undertake any Easy Configuration Wizard actions at this time; the easy configuration actions in a Teams-related deployment has additional considerations, as defined below in step 3.

   
   

2. Anchor
   Azure Licensing Azure Licensing

   Licensing has been acquired and properly assigned.

   • SIP registration license(s) (namely one or more instances of the SBC-SWELITE-LIC-RG -CLOUD) are absolutely required, to enable the registration of Yealink devices. 

   • SIP session licenses are required, as the IP-based SIP signaling and RTP media to/from the subtended Yealink clients is connected by the 

     Spacevars
     0 series3

     to an IP-based client (e.g. a SIP trunk, a SIP-based IP PBX, etc.)

     Info
     title SBC Edge Portfolio License Acquisition
     For instructions on how to obtain and apply licenses, refer to Node-Locked Licensing - SBC 1000 /and 2000 and SBC SWe Edge.

     
     

3. Anchor
   Azure Teams configuration Azure Teams configuration

   Teams Direct Routing (DR) basic configuration has been undertaken. Teams Direct Routing basic configuration is documented in the Azure-related best practice. Please ensure all instructions are executed as documented in the following sections of that best practice:

1. • Configuration Prerequisites

   • Configure Azure for Microsoft Teams Direct Routing
   • Run Easy Configuration Wizard for Microsoft Teams Direct Routing
   • Complete SBC SWe Edge Configuration for Microsoft Teams Direct Routing in Azure
   • Place a Test Call.
4. Networking device updates have been applied to permit Azure-based 

   Spacevars
   0 product 1 bold

    ↔ enterprise premises-based Yealink client device communication.  The 

   Spacevars
   0 product

   and the Yealink clients that will attempt to register will likely communicate across the Internet; as such, the following devices/constructs must be configured to ensure successful communication between the parties:

1. • Any enterprise premises-based routers undertaking LAN ↔ WAN addressing conversions, such as those related to NAT;

   • Any enterprise premises-based firewalls undertaking network traffic filtering actions.

   • The Azure-based virtual network and VM (virtual machine) hosting the

     Spacevars
     0 series3

     , especially the network security group (NSG) security rules.

     Note
     title Contact Enterprise IT to Facilitate IP-based Communications
     Please contact your IT administrator to ensure communication can be undertaken between the network segments hosting the Yealink Teams client devices and the  Spacevars 0 product hosted in the Azure cloud. The IT administrator should be knowledgeable regarding the private & public IP addresses assigned to all devices, along with the required routing to achieve inter-device communications.

     
     

     Info
     title Azure Virtual Networking Supplementary Information
     Refer to the following sources of information for basic Azure virtual networking concepts, features and deployment: Azure Products Azure networking Internet Connectivity On-premises connectivity Virtual Network Documentation Security groups Tutorial: Route network traffic with a route table using the Azure portal Tutorial: Filter network traffic with a network security group using the Azure portal Diagnose a virtual machine network traffic filter problem

     
     

...

Update Yealink Teams Client Devices to Register with the 

Spacevars
0 product 1 bold

for Survivability

Prerequisites

This section assumes the following actions are complete:

1. Yealink client device prerequisites for Phone System Integration;

2. Spacevars
   0 product

    Teams DR prerequisites and configuration.

Yealink Teams Client Device Configuration Commands

CLI (Command Line Interface) Instructions

...

Confirm Call Completion via Phone System From SBC

Access the WebUI, and then click the  Monitor  tab. 

1. Expand the three signaling groups (that pertain to the survivability scenario) so all channels become visible. For our example deployment, the three signaling groups identifiers are  LocalReg  (the signaling group to which the Yealink devices are  registered),  IMS (the PSTN-related signaling group), and Microsoft Teams.

2. Review the channel states for each signaling group, and confirm correct operation:

   1. One channel is seized ( blue ) in the PSTN-related signaling group (for our example deployment, the  IMS signaling group).  Double-click the seized channel to ensure consistency between the channel details and the call placed from the Yealink device (e.g. call direction is incoming, called party number has the same phone number as the Yealink device, calling party number is the PSTN number from which you made the call, etc.).

   2. One channel is seized ( blue ) in the Phone System-related signaling group (for our example deployment, the  Microsoft Teams signaling group).   Double-click the seized channel to ensure consistency between the channel details and the call placed from the Yealink device.

   3. All channels remain idle ( light green ) in the SIP local registrar-related signaling group (for our example deployment, the   LocalReg  signaling group). 

      Caption
      0 Figure 1 SBC Displaying (from the Monitor) an Active Call Between Yealink Client (in Teams Mode of Operation) with PSTN Client via the SIP Trunk

      
      

...