Versions Compared

Old Version 2

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH2UserResourceIdentifier{userKey=8a00a0c86e0abd6d016e13214f5c0005, userName='null'}
AUTH1UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
JIRAIDAUTHCHOR-5789
REV5UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cef30cd0, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a0c86a61778d016a7d0876df0017, userName='null'}

Panel

In this section:

Table of Contents
maxLevel4


Overview

The 

Spacevars
0series3
includes the Easy Configuration option to add a partially configured signaling group with a new single end-point scenario for Microsoft On Premises.

Info

The Configure Single Leg Wizard for Microsoft On Premises option applies to 

Spacevars
0series3
only.

The SBC Easy Configuration interface includes a built-in, step-by-step setup configuration wizard to enable quick and easy deployment of a partially configured signaling group with a new single end-point scenario for a Microsoft On Premises.

For the single endpoint configuration, since the peer end if not known/configured, in the Easy Configuration Wizard, the Transformation and Routing entries for the endpoint being configured are created independent of the peer end. If you have two endpoints connected and use the Single Leg Wizard to add the third endpoint, you'll need to create/modify the Transformation and Routing entries to complete routing.

Info
titleEasy Configuration Wizard - Single Leg Configuration Notes
  • Use the single leg wizard to add a 3rd, 4th, or 5th peer to a device, when at least two legs are already configured via the standard Easy Configuration Wizard.
  • Emergency configuration is not supported for single end scenarios.

Procedure

Step 1: Select Microsoft On Premises Connection

Easy Configuration Step 1 includes configuration for scenario parameters.

  1. In the WebUI, click the Tasks tab.
  2. In the left navigation panel, go to SBC Easy Setup > Easy Config Wizard.

  3. From the Application drop down list, select Microsoft On Premises.

  4. Configure per the field definitions below and click Next.


    Configure Scenario Parameters - Field Definitions

    FieldDescription
    ApplicationConfiguration template used: Microsoft on Premises.
    Scenario DescriptionName to describe the setup.
    Telephone CountryCountry in which Microsoft On Premises is setup.
    SIP SessionsNumber of simultaneous SIP Sessions. Valid entry: 1 - 960.
    Version

    The Teams connection type used for the network. Valid selections:

    • Skype for Business
    • Lync 2013/2010


Step 2: Configure Microsoft on Premises for Endpoint

Easy Configuration Step 2 includes configuration for the Microsoft on Premises endpoint. The configuration items displayed in Step 2 depend on the version of Microsoft On Premises you configured in Step 1. See below for each type. 

  1. Configure the provider information.
  2. Click. Next.

Skype for Business

The fields below are displayed if you select Skype for Business from the Version drop down list in Step 1. 

Configure Skype for Business

FieldDescription
Server Pool HostThe Pool name of the Skype for Business Server (FQDN).
ProtocolThe IP protocol to use for sending and receiving SIP messages between SBC and the Server Pool Host. Valid entry: TLS or TCP.
Port NumberThe Port Number (via TLS or TCP) used for sending and receiving SIP messages between SBC and the Server Pool Host.

Lync 2013/2010

The fields below are displayed if you select Lync 2013/2010 from the Version drop down list in Step 1. 

Configure Lync 2013/2010

FieldDescription
Server Pool HostThe Pool name of the Lync Server (FQDN).
ProtocolThe IP protocol to use for sending and receiving SIP messages between SBC and the Server Pool Host. Valid entry: TLS or TCP.
Port NumberThe Port Number (via TLS or TCP) used for sending and receiving SIP messages between SBC and the Server Pool Host.


Step 3: Summary

Easy Configuration Step 3 includes a summary of the information configured in Step 1 and Step 3.

Review the information and click Finish.

See below for an example: