Page History

...

Introduction to Yealink Teams Client Local Survivability

Ribbon Communications and Yealink® support Communications and Yealink® support uninterrupted voice services if a connectivity loss occurs between occurs between an enterprise site hosting Yealink hosting Yealink Teams, voice-related clients and clients, and the Microsoft® Phone System hosted in the Microsoft Azure™ Azure™ cloud.

Support for Teams Client Survivability

The benefits of voice service survivability between enterprise sites hosting Yealink hosting Yealink Teams voice-related clients and clients and Phone System Systems hosted in the Azure cloud include the following:

...

Anchor
Yealink Teams Clients Yealink Teams Clients

Yealink Teams Clients

...

Yealink Teams Clients - Conference and Desk Phones

Image Modified

For details about devices that support Teams voice services, refer to the Yealink Teams client products page for the latest feature descriptions and specifications for available models. 

...

The survivability capabilities available to Teams clients vary based on the accessibility of the Phone System and the deployment type (on-premises or Azure).

Anchor
Teams OK Teams OK

Network Operation when the Phone System is Accessible

When the Phone System is accessible, the Yealink Teams and 

...

• Both the Yealink Teams clients and the 

  Spacevars
  0 product

  have continued Phone System access for signaling and media control.
• Yealink Teams clients use the Phone System (the "Primary Call Server") to establish intra-office, inter-office, and calls into the PSTN.

• Spacevars
  0 product

   acts as a Teams Direct Routing certified SBC in support of Teams client access to the PSTN or to third-party, non-Teams voice infrastructure.
• As a supplement to the Teams Phone System call services, the Yealink Teams clients register with the 

  Spacevars
  0 product

  (the "Secondary Call Server") via SIP signaling.
  

  Pagebreak

...

Normal Operation when Teams Phone System is Accessible (SBC on enterprise premises)

Image Modified

Anchor
Azure OK Azure OK

 

Spacevars
0 series3

 in Azure

...

• Both the Yealink Teams clients and the 

  Spacevars
  0 series3

  access Phone System in Azure for signaling and media control.
• The Yealink Teams clients use Phone use the Phone System ("Primary Call Server") to establish intra-office, inter-office , and calls into the PSTN.
• The 

  Spacevars
  0 series3

  acts as a Teams Direct Routing certified SBC in support of Teams client access to the PSTN or third-party non-Teams voice infrastructure.
• As a supplement to Phone System call services, the Yealink Teams clients register with the 

  Spacevars
  0 series3

  ("Secondary Call Server") via SIP signaling. 

...

Normal Operation when Teams Phone System is Accessible (SBC SWe Edge) in Azure)

Image Modified

Anchor
Teams Survivability Teams Survivability

Network Operation when the Phone System is Not Accessible

Spacevars
0 product

 on Enterprise Premises

...

• The Phone System in Azure is no longer accessible for signaling and media control to the Yealink Teams clients and the

  Spacevars
  0 product

  ;.
• The Yealink Teams clients use the services of the 

  Spacevars
  0 product

  ("Secondary Call Server") via SIP signaling to establish intra-office, inter-office, and public calls into the PSTN.

...

Operation when Teams Phone System is Not Accessible (SBC on enterprise premises)

Image Modified

...

...

Operation when Teams Phone System is Not Accessible (SBC on enterprise premises)

Image Modified

Initiating Survivability Operation From Yealink Devices

Outgoing Calls

To place outgoing calls using the 

...

...

"Quick Ball"-enabled Survivability on Yealink Teams Devices

Image Modified

...

• When incoming calls (intended for a Teams client) from the PSTN or a non-Teams Team client arrives arrive at the SBC, the SBC validates the availability of the Phone System (the latter being of the highest priority within the route list). If the Teams System is recognized as being unavailable, the SBC routes the call directly to the subtended registered Yealink Teams client via via SIP, as opposed to the Phone System. For such an action to occur, the intended call recipient (the Yealink Teams client) must be mapped by the SBC as having a resolvable SIP-based client address. This resolution is possible through the subsequent SBC provisioning instructions.
• Incoming SIP-based calls that arrive from the subtended Yealink Teams client are are routed by the SBC as a standard SIP-based registered endpoint. These calls will be routed either to another subtended Yealink client or into the PSTN, provided such routes are active and available. If no route is found, the SBC routes the call to the appropriate configured treatment.

...

1. Devices must be configured and supporting support 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 is successfully completescompleted, the device is configured to successfully offer Phone System phone system services.
2. Devices must be configured with a firmware release that supports survivability for Teams deployments.
   

3. Optionally, Yealink devices may be configured to communicate with 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 Xan X.509 certificate 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 certificate assignment of during the certificate during Teams Direct Routing setup.  The  Spacevars 0 product X.509 certificate, exchanged during the TLS 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 is found in the relevant Yealink device administrator guide posted at at support.yealink.com; If the certificate is signed by an unrecognized CA, you must load the relevant sections of the certificatethe 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.

   
   

Assuming the conditions are fulfilled, the Yealink devices are ready for Teams-related survivability configuration , and should be updated only after the the

...

For 

1. Initial The 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 have additional considerations, as defined in step 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.

       
       

3. Anchor
   Teams configuration Teams configuration

   Teams Direct Routing (DR) basic configuration has been undertaken. Teams DR basic configuration is documented in the 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 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 have additional considerations, as defined below in step 3.

   
   

2. Anchor
   Azure Licensing Azure Licensing

   Licensing has been acquired and properly assigned.

   • SIP 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.

     
     

3. Anchor
   Azure Teams configuration Azure Teams configuration

   Teams Direct Routing Routing (DR) basic configuration has been undertaken.  The basic configuration of 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

     
     

...

The following instructions detail how to configure the Ribbon SBC to accept Yealink Teams Yealink Teams client devices device registrations and to route calls properly between the devices and the PSTN. Please note the following context prior to the configuration being undertaken:

1. Create a new SIP Local Registrar instance to which the Yealink devices register via SIP, including client registration authentication and potentially a new TLS Profile ID; 

2. Create new call routing for use whenever a Yealink device needs to place calls via the SBC. 

   1. Create a new Call Routing Table instance.

   2. Create two new Transformation Table instances (one for intra-office calling and one for PSTN access), each with an entry to pass the user-dialed digits through for digits through for routing purposes;

   3. Specify two new call routing entries to identify the final instructions for intra-office and PSTN routing for a Yealink device-originated call.

      Info
      title Intra-Office and PSTN Routing Clarifications
      ● A specific call route entry is required to be configured for intra-office calling between one Yealink device and another Yealink device registered with the same SIP Local Registrar instance. ●  The PSTN-related signaling group will already have been created through the Easy Configuration wizard undertaken in the prerequisites of , which is undertaken as a prerequisite for the SBC setup.

      
      

3. Create a new Signaling Group instance that will be associated with the new local registrar instance you just created;

4. Update the pre-existing Call Routing Table instance (associated with the incoming PSTN trunk) to include updated routing for call processing that uses the newly created Signaling Group instance when the Phone System is unavailable:

   1. Create a new Transformation Table instance and entries to modify the incoming dialed digits received from the PSTN for local routing to the newly created SIP local registrar instance.

   2. Specify a new call routing entry to identify the final instructions for routing to an SBC-subtended Yealink device.

      Info
      title Pre-Existing Call Route Table Instance Clarifications
      ● The pre-existing Call Routing Table instance associated with the incoming PSTN trunk was initially created through the use of the Easy Configuration wizard template undertaken in the prerequisites of the SBC setup. This Call Routing Table instance already has a routing entry to support the routing of an incoming call to the Phone System. Refer to to Using the Easy Configuration Wizard. ●  The soon-to-be-added new routing entry will be prioritized below the Teams-related call routing entry; this new routing entry will only be referenced in the event the Phone System is unavailable (i.e., the Yealink Teams Client Local Survivability scenario ).

      
      

5. Confirm the new Signaling Group instance associated with the new SIP Local Registrar instance is active.

To aid in the comprehension of the subsequent configuration instructions, please refer to the example network presenting pre-existing attribute values and device identifiers, along with soon-to-be-added (identified in green italic  green italic font) attributes and values. Note  Note select values (denoted with an X) are redacted for privacy purposes.

...

Sample Configuration Attribute Values for Example SBC Network Topology

Image Modified

SBC Configuration

1. Anchor
   Step 1 Step 1

   Access the WebUI, and click the Settings tab.

   1. In the left navigation page, access SIP > Local Registrars Table.

      1. Click the (Plus icon) to add a row.

      2. In the Create SIP Local Registrar dialog box, type the desired identifier name and maximum number of registering clients for your new SIP local registrar instance. For our example deployment, the entered name is is LocalReg.

         Info
         title Registrar Provisioning Reference Information
         For details on SIP local registrar configuration, refer to Creating and Modifying SIP Local Registrars.

         
         

      3. Click OK.

         Caption0Figure1Newly Created Example SIP Local Registrar Instance "LocalReg", to Which Yealink Devices Will Register as SIP Endpoints

         Image Modified

         
         

   2. In the left navigation page, access SIP > Local/Pass-thru Auth Tables

      1. Click the (Plus icon) to add a local pass-through authorization table.
         

      2. In the the Description dialog box, type the desired desired Local Pass-through Authorization Table  name. For For our example deployment, the name specified is is Local registration table .

      3. Click OK.

         Caption0Figure1Newly Created Example Local Pass-through Authorization Table instance "Local Registration table", that will shortly define acceptable credentials for successful registration

         Image Modified

         
         

         Info
         title Local Pass-through Authorization Tables Provisioning Reference Information
         For details on the configuration of Local Pass-through Authorization Tables configuration, refer to to Managing Local Pass-through Authorization Tables.

         
         

      4. Anchor
         Client Authorization Client Authorization

         In the left navigation page, access SIP > Local/Pass-thru Auth Tables, and select (click) the new Local Pass-through Authorization Table just created. In  For example, in deployment, the entered name is is the Local registration table. The  The table displays under the tabs, with the note:   --  Table is empty --

         1. Anchor
            Step 123 Authorization Step 123 Authorization

            Click the Create Local Pass-through Authorization Entry (Plus icon)

         2. Specify the following values for fields:

            Caption
            0 Table 1 Local Pass-through Authorization Entry Attributes
            Field Required Entry Type of Address of Record Local, to signify the SBC is the registrant of record. Address of Record URI Specify the acceptable Address of Record (AOR) URI from a potential potentially valid registering endpoint. In the example deployment, one such AOR URI is  sip:30001. User Name Specify the acceptable user name from the registering endpoint. In the example deployment, one acceptable User Name is  30001  is 30001. Enter Password Specify the password the registering endpoint must submit for successful registration. Confirm Password Type the same password as entered above for confirmation.

            
            

            Info
            title Local Pass-through Authorization Table Entries Provisioning Reference Information
            For details on Local Pass-through Authorization Table Entry configuration, refer to Creating and Modifying Entries to Local Pass-through Authorization Tables.

            
            

         3. Click OK.

            captionImage Added0

         4. Pagebreak

            Figure1Highlighted Example New Local Pass-through Authorization Entry

            Image Removed

            Pagebreak

            Repeat steps 1, 2, Repeat steps 1, 2, and 3 for each remaining possible valid registering endpoints. In the example deployment, steps 2 and 3 are repeated for Yealink device device 30003.

            Note
            title Use of Local Pass-through Authorization Table is Strongly Recommended
            Ribbon and Yealink strongly recommend the use of the optional Local Passthrough Authorization Table, especially for Azure-based SBC deployments. The use of the Local Passthrough Authorization Table deters the fraudulent use of unauthorized users from fraudulently using your enterprise's SIP trunking services by unauthorized users.

            
            

      5. Anchor
         TLS Profile TLS Profile

         Optional Step for encrypted SIP signaling: Create the  TLS profile to define the cryptographic parameters for the SIP signaling between the subtended Yealink devices and the SBC.
         1. In the WebUI, click the Settings tab.

         2. In the left navigation pane, go to Security > TLS Profiles.

         3. Click the CreateTLS Profile (Plus icon) at the top of the TLS Profile page.

         4. Configure the parameters shown below. Leave all other parameters as default.

            Caption
            0 Table 1 New TLS Profile Entry Attributes for Registered Yealink SIP Clients ↔ SBC Communication
            Field Required Entry Description Specify a descriptive name for the entry. A sample name may be Yealink SIP Client SBC Signaling. TLS Protocol Set the administrative state to TLS 1.0 - 1.2. Mutual Authentication Specify the authentication as Disabled. Client Cipher List Select a cipher value (this value must be supported by the subtended registered Yealink clients). See above for guidelines. Ribbon recommends TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384.  Validate Server FQDN Specify the validation as Disabled. All other fields Please leave all default values as-is for basic SIP signaling encryption purposes.

            
            

         5. Click OK, and confirm the presence of the new TLS Profile entry. 

            Note
            title Use of Signaling and Media Encryption Strongly Recommended for Azure-based SBC Deployments
            While optional, 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. For more information, please refer above.

            
            

            Info
            title TLS Profile Provisioning Reference Information
            For more information about creating new TLS Profile entries, refer to Managing TLS Profiles.

            
            

2. Anchor
   Step 2 Step 2

   Access To access the WebUI, click the Settings tab.

   1. Anchor
      new call route table new call route table

      In the left navigation pane, go to Call Routing > Call Routing Table. 

      1. Click the (Plus icon).

      2. Enter a descriptive name in the Description text field; for this deployment example, the value is is From Local SIP EP.

      3. Click OK.

         Caption0Figure1Highlighted Example New Call Routing Table for Registered SIP Client-Initiated Call Processing

         Image Modified

         
         

         Info
         title Call Routing Table Provisioning Reference Information
         For more information about creating call routing tables, refer to Managing Call Routing Tables.

         
         

   2. Anchor
      Transformation Table Transformation Table

      In the WebUI, click the Settings tab.

      1. In the left navigation pane, go to Call Routing - > Transformation .

      2. Click the Create (Plus icon).

      3. In the the Description dialog  dialog box, enter the desired Transformation desired Transformation Table name identifier for calling to the PSTN. For our For our example deployment, the entered name is is from SIP to IMS.

      4. Click OK.

         Caption0Figure1

         Highlighted New Transformation Table for Registered SIP Clients to Call the PSTN

         Image Modified

         Info
         title Transformation Table Provisioning Reference Information
         For details on Transformation Table configuration, refer to Managing Transformation Tables.

         
         

      5. Anchor
         Transformation Table Entry Transformation Table Entry

         Pagebreak

         In the left navigation page, go to Transformation, and select (click) the new Transformation Table just created. In  For example, in deployment, the entered name is  is from SIP to IMS. The  The table displays under the tabs, with the note:  --  Table is empty --

         1. Click the Create (Plus icon).

         2. Type or select the following values to specify the passthrough of dialed digits from the subtended registered Yealink Survivability (SIP) client to the PSTN:

            Caption
            0 Table 1 New Transformation Table Entry Attributes for Registered SIP Clients to Reach the PSTN
            Field Required Entry Description Specify a descriptive name for the entry. In the example deployment, the entered name is  SIP to PSTN . Admin State Set the administrative state to Enabled. Type (Input Field) Specify the type for input as Called Address/Number. Value (Input Field) Specify an asterisk (.*) to indicate acceptance of any digits. Type (Output Field) Specify the type for output as Called Address/Number. Value (Output Field) Specify the value of output as \1 to indicate that digits received will be passed through to the outbound route without any change made.

            
            

            Info
            title Transformation Table Entries and Digit Manipulation Provisioning Reference Information
            For details on Transformation Table Entry configuration, refer to Creating and Modifying Entries to Transformation Tables. For call digit matching and manipulation through the use of regular expressions, please reference Creating Call Routing Logic with Regular Expressions.

            
            

         3. Click OK.

            captionImage Added

            0	Figure
            1	Highlighted New Transformation Table Entry for Registered SIP Clients to Call the PSTN

            Image Removed

            
            

   3. Anchor
      Transformation Table
      Anchor
      Transformation Table 2 Transformation Table 2

      In the WebUI, click the Settings tab.

      1. In the left navigation pane, go to Call Routing > Transformation.

      2. Click the  Create (Plus icon).

      3. In the  Description dialog box, enter the desired Transformation Table name identifier for intra-office calling. For our example deployment, the entered name is is from SIP to SIP.

      4. Click OK.

         Caption0Figure1

         Highlighted New Transformation Table for Registered SIP Clients to Call Other SIP Clients in the Office

         Image Modified

         Info
         title Transformation Table Provisioning Reference Information
         For details on Transformation Table configuration, refer to  Managing Transformation Tables.

         
         

      5. Anchor
         Transformation Table Entry 2 Transformation Table Entry 2

         In the left navigation page, go to Transformation, and select (click) the new Transformation Table just created for intra-office calling. In example deployment, the entered name is  is from SIP to SIP . The table will appear under the tabs, with a note stating  – Table is empty --

         1. Click the Create (Plus icon).

         2. Enter or select the following values into the pop-up window , to specify the pass-through of dialed digits from the subtended registered Yealink Survivability (SIP) client to another subtended another subtended registered Yealink Survivability (SIP) client.

            Caption
            0 Table 1 Transformation Table Entry Attributes for Intra-Office Calling
            Field Required Entry Description Please use a descriptive name for the entry. In the example deployment, the entered name is  SIP to SIP . Admin State Enabled Type (Input Field) Called Address/Number Value (Input Field) Please enter a regular expression to confirm a private dial plan number that conforms to the private dial plan assigned to the registered SIP clients. In the example deployment, the entered expression is ^(3\d{4})$, signifying the called digits must be 5 characters in length, and must start with a 3. Type (Output Field) Called Address/Number Value (Output Field)  \1 , signifying matching digits received will be passed through to the outbound route without change.

            
            

            Info
            title Transformation Table Entries and Digit Manipulation Provisioning Reference Information
            For details on Transformation Table Entry configuration, refer to Creating and Modifying Entries to Transformation Tables. For call digit matching and manipulation through the use of regular expressions, please reference Creating Call Routing Logic with Regular Expressions.

            
            

         3. Click OK .

            Caption0Figure1

            Highlighted New Transformation Table Entry for Registered SIP Clients to Call Other Registered SIP Clients

            Image Modified

   4. Anchor
      anchorname100 anchorname100

      In the WebUI, click the Settings tab.

      1. In the left navigation pane, go to Call Routing > Call Routing Table and select the newly created Call Routing Table; for our example deployment, the newly created table is is From Local SIP EP. 

         1. Click the  Create Routing Entry (Plus icon) to create the route for calling into the PSTN.

            1. Enter the following values into the pop-up window:

               Caption
               0 Table 1 Call Routing Entry Attributes for Calling from Registered Yealink Devices to the PSTN
               Field Required Entry Description Enter an informative name in the text field; for our example deployment, the value is  to IMS Admin State Select Enabled Number/Name Transformation Table Select the newly created Transformation Table instance to which calls from a subtended registered Yealink device will be routed to the PSTN. For the example deployment, the value is  from SIP to IMS . Destination Type Select Normal Destination Signaling Groups Select the PSTN-related Signaling Group. For the example deployment, the value is  IMS All other fields Please leave all default values as-is for basic configuration purposes.

               
               

               Info
               title Call Routing Table Entry Provisioning Reference Information
               For details on call routing table entry configuration, including modification of fields with default values, refer to to Creating and Modifying Entries to Call Routing Tables.

               
               

            2. Click OK.

               Caption0Figure1

               Example Call Routing Entry Attributes for Calling from Registered Yealink Devices to the PSTN

               Image Modified

         2. Click the Create Routing Entry (Plus icon) once again to create the route entry for intra-office calling.

            1. Type or choose the following values:

               Caption
               0 Table 1 Call Routing Entry Attributes for Calling from Registered Yealink Devices to Other Registered Yealink Devices
               Field Required Entry Description Type a descriptive name in the text field; for the example deployment, the value is  SIP TO SIP. Admin State Select Enabled. Number/Name Transformation Table Select the the newly created Transformation Table instance to which calls from a subtended registered Yealink device will be routed when attempting to reach another subtended registered Yealink device. For the example deployment, the value is is from SIP to SIP. Destination Type Select Registrar Table. Destination Signaling Groups Select the newly created SIP Local Registrar-related Signaling Group to which the subtended registered Yealink devices are associated. For the example deployment, the value is is LocalReg. All other fields Leave all other default values as-is for basic configuration purposes.

               
               

            2. Click OK.

               Caption0Figure

               1Example Call Routing Entry Attributes for Calling from Registered Yealink Devices to Other Registered Yealink Devices Image Modified

               
               

      2. Review and confirm the two new Call Routing Table entries in the newly created Call Routing Table.

         Caption0Figure1

         New Priority Call Routing Table Entry

         Image Modified

3. Anchor
   Step 3 Step 3

   Access the WebUI, click the  Settings tab tab.

   1. In the left navigation pane, go to Signaling Groups.

   2. From the top menu bar, click Create Signaling Group and select SIP Signaling Group (note: for the

      Spacevars
      0 series3

      , select Add SIP SG)

   3. Create the SIP Signaling Group using the following configuration:

      Caption
      0 Table 1 SIP Signaling Group Attribute Values for Registered Yealink Devices
      Field Required Entry Description Enter an informative name in the the Description  text text field; for the the example deployment, the value is  LocalReg. Admin State Select Enabled. Call Routing Table Select the recently created Call Routing Table Instance that will define routing for calls that originate from the subtended registered Yealink devices. For the example deployment, the value is is from Local SIP EP. SIP Mode Select the Local Registrar value. Registrar Select the recently created SIP Local Registrar instance to which subtended Yealink devices will advertise their presence. For the   example deployment, the value is is LocalReg. Challenge Request Select Enable Local/Pass-thru Auth Table Select the recently created Local Pass-through Authorization Table that defines the credentials the subtended Yealink devices must present to the SBC to be successfully recognized (registered). For the   example deployment, the value is is the Local registration table. Media List ID (Optional Step for encrypted media) If you specified a new new  TLS Profile ID, please select the Media List ID value associated with the Phone System Signaling Group for SRTP communication with the registered subtended Yealink client devices. The value to be selected should be be  MS Teams Media List, originally created through the use of the Teams DR-related easy configuration wizard during the SBC setup. The contains SRTP cryptographic settings that can be used for Spacevars 0 product  ↔ subtended registered Yealink client device encrypted media exchange. NOTE: For details on Media List-ID configuration, including the setup of attributes related to media encryption, please refer to to Managing Media Lists and  and Managing SDES-SRTP Profiles. Listen Port Click the (Plus icon) to create a new instance of the SIP Listen Port, and update as follows: Option 1: For unencrypted Spacevars 0 product  ↔ subtended registered Yealink client device communication, please enter the Port value as 5060, the Protocol value as UDP, and the TLS Profile ID as N/A. Option 2: For encrypted  ↔ subtended registered Yealink client device communication (you must have specified a new TLS Profile ID entry earlier), please enter the Port value as 5061, the Protocol value as TLS, and the TLS Profile ID as the new entry created earlier (e.g. Yealink SIP Client SBC Signaling ) . Federated IP/FQDN Click the (Plus icon)  to to create a new instance of the Federated IP/FQDN, and specify as follows to identify the networking IP addresses of your Yealink Teams Yealink Teams client devices, supplied by the enterprise IT administrator. For our   example deployment, the IP/FQDN is entered as XXX .0.0.0, with the Netmask/Prefix as 255.0.0.0, meaning the signaling group will accept communication with any host (i.e. Yealink device) that presents a host IP of anywhere from XXX.0.0.1 → XXX.255.255.254 All other fields Please leave all default values as-is for basic configuration purposes.

      
      

      Info
      title Signaling Group Provisioning Reference Information
      For details on Signaling Group configuration attributes described above, including modification of fields with default values, refer to Creating and Modifying SIP Signaling Groups.

      
      

   4. Click OK . The  The new SIP Signaling Group (in the the example deployment, named named LocalReg) may be expanded to present the following sample attributes.

      Caption0Figure1

      Example SIP Signaling Group Configuration for Connection to Registered Yealink Teams Devices; Key User-Supplied values HighlightedImage Modified

      
      

4. Anchor
   Step 4 Step 4

   In the WebUI, click the Settings tab.

   1. Anchor
      Transformation Table 3 Transformation Table 3

      In the left navigation pane, Call Routing -> Transformation Transformation.

      1. Click the Create (Plus icon).

      2. In the the Description dialog dialog box, enter the desired Transformation Table name identifier for calls received from the PSTN and destined for a subtended Yealink device. For our example deployment, the entered name is is from IMS to SIP.

      3. Click OK .

         Caption0Figure1Highlighted New Transformation Table for PSTN Call Routing to Registered Yealink Devices

         Image Modified

         
         

         Info
         title Transformation Table Provisioning Reference Information
         For details on Transformation Table configuration, refer to Managing Transformation Tables.

         
         

      4. Anchor
         Transformation Entry 3 Transformation Entry 3

         In the left navigation page, go to Transformation, and select (click) the new Transformation Table just created. In  For example, in deployment, the entered name is  is from IMS to SIP. The  The table will appear under the tabs, with a note stating  – Table is empty --

         1. Anchor
            New 1 2 3 New 1 2 3

            Click the Create (Plus icon).

         2. Enter or select the following values into the pop-up window, to specify the modification of dialed digits from the PSTN to reach a subtended registered Yealink Survivability (SIP) client:

            Caption
            0 Table 1 New Transformation Table Entry Attributes for a PSTN Call to Reach a Specific Registered Yealink Device
            Field Required Entry Description Please use a descriptive name for the entry. In the example deployment, the entered name is is Entry ID 1. Admin State Enabled Type (Input Field) Called Address/Number Value (Input Field) Please enter a regular expression to define the Teams Phone Number assigned to the Yealink device with the survivability. In the example deployment, the entered expression is \+86XXXX604392, the Teams Phone Number assigned to the Yealink device that also carries the SIP phone number 30001 (latter later used in the Survivability UI). Type (Output Field) Called Address/Number   Value (Output Field) Enter a regular expression to replace the Teams Phone Number dialed by the PSTN user to the assigned to with the SIP phone number assigned to the Yealink device with the survivability. In the example deployment, the entered expression is 30001, the Teams Phone Number assigned to the Yealink device that also carries the Teams Phone Number +86XXXX604392 (latter used in the Teams client UI).

            
            

            Info
            title Transformation Table Entries and Digit Manipulation Provisioning Reference Information
            For details on Transformation Table Entry configuration, refer to Creating and Modifying Entries to Transformation Tables. For call digit matching and manipulation through the use of regular expressions, please reference Creating Call Routing Logic with Regular Expressions.

            
            

         3. Click OK.

            Caption0Figure1New Transformation Table Entry for PSTN Calls to Reach Registered Yealink Device

            Image Modified

         4. Repeat  Repeat steps 1, 2 & 3  for each remaining possible possible registered  Yealink device with both the Teams client and the Survivability (SIP) client. In the example deployment, steps 1, 2, and 3 are repeated for the Yealink device with the SIP phone number number 30003.

            Caption0Figure1Completed Example New Transformation Table for PSTN Calls to Reach Registered Yealink Devices

            Image Modified

   2. Anchor
      updated route entry 100 updated route entry 100

      In the left navigation pane, go to Call Routing > Call Routing Table and select the Call Routing Table originally created through the use of the Easy Configuration wizard (refer to Using the Easy Configuration Wizard) template for processing calls originating from the PSTN. For our example deployment, the table requiring the new entry is is From IMS .

      1. Click the Create Routing Entry (Plus icon).

      2. Enter the following values into the pop-up window:

         caption

         Caption
         0 Table 1 Key Call Routing Entry Attribute Values That Must be Explicitly Submitted by User
         Field Required Entry Description Enter an informative name in the text field; for our example deployment, the value is is from IMS TO SIP. Admin State Select Enabled Number/Name Transformation Table Select the newly created Transformation Table instance to which calls from the PSTN will be routed during survivability scenarios (i.e., when the Phone System is unavailable). For the example deployment, the value is  from IMS to SIP. Destination Type Select Registrar Table Destination Signaling Groups Select the newly created SIP Local Registrar-related Signaling Group to which the subtended Yealink devices are associated. For the example deployment, the value is is LocalReg. All other fields Leave all default values as-is for basic configuration purposes.

         
         

         Image Added

         0

         Info
         Figure
         1	Call Route Entry Attributes for Example Teams Survivability-Related Call Route Entry
         Image Removed
         title Call
         Info
         title Call Routing Table Entry Provisioning Reference Information
         For details on call routing table entry configuration, including modification of fields with default values, refer to to Creating and Modifying Entries to Call Routing Tables.

         
         

      3. Click OK and review the new Call Routing Table Entry related to survivability in the updated PSTN-related Call Routing Table from the left navigation pane.

         Caption0Figure1

         Newly Created Teams Survivability Call Routing Entry in PSTN-Originated Call Routing Table

         Image Modified

5. Anchor
   Step 5 Step 5

   Access the WebUI, click the Monitor  tab. Confirm the new SIP Signaling Group instance associated with the new SIP Local Registrar instance is active. For our   our example deployment, the new SIP Signaling Group instance is is LocalReg .
   Caption0Figure1

   Example SIP Signaling Group Linked to Registered Yealink Devices Shows ActiveImage Modified

   
   

Update Yealink Teams Client Devices to Register with the 

features.hybrid_mode.enable=1
account.X.sip_server.1.address = <SBC IP Address>
account.X.user_name = <Username>
account.X.password = <Password>     [X ranges from 1 to 16]
features.hybrid_mode.quick_ball.enable=1     [This item is optional]