Before you begin
This page describes the final deployment step produced by the Lync 2010 wizard for a UX in a Lync 2010 environment with a SIP Trunk Provider. Before you proceed, ensure you have completed the prerequisites.
Using a SIP Trunk is a popular alternative to PSTN connectivity via PRI. The UX can be configured to connect an Enterprise's Lync environment to a SIP trunk using the automatic setup wizard as described in the section below.
Usage of the deployment wizard to configure the UX does not modify existing configuration. The wizard will simply add the new configuration elements to the UX.
Lync 2010 Setup Field Configuration
Enter the scenario configuration details based on your deployment settings:
When you click the Apply on this final step, it may take up to 15 seconds before you receive a final confirmation status screen. During this time, no progress indicator will be shown, and it is recommended that you wait until the operation completes. This issue will be resolved in the upcoming revision of the UX software — SYM-8453
Scenario Information - Field Definitions
Name describing the Lync setup.
This value entered will be prefixed on all the UX configuration elements created by the Setup Wizard pertaining to this deployment.
SIP Trunking for this deployment
SIP Properties - Field Definitions
No. of Channels
The number of SIP channels you would like the wizard to allocated in the SIP Signalling Group.
Make sure you have enough SIP licenses to account for the entered value.
Server Pool Host
The Pool name of the Lync Server 2010 (FQDN)
The SIP Server Port number (via TLS) to use for sending and receiving SIP messages between UX and the Server Pool Host
Border Element Server
The FQDN or IP address of the Session Border Controller service provider
The IP protocol to use for sending and receiving SIP messages between UX and the Server Pool Host
The SIP Server Port number to use for sending and receiving SIP messages between UX and the Server Pool Host
Use Secondary Border Element Server
Select enable if you wish to have a secondary Session Border Controller service provider configured