Page History

...

The following 

• SBC SWe LiteEdge, in both enterprise on-premises and Microsoft Azure-based deployments
• All SBC 1000 hardware permutations
• All SBC 2000 hardware permutations

...

1. Initial setup is complete.

   • SBC 1000 and SBC 2000 initial setup steps

   • SBC SWe Lite 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 Working with Licenses Node-Locked Licensing - SBC 1000/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 Working with Licenses Node-Locked Licensing - SBC 1000/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 Lite 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

     
     

...