Biamp’s Tesira VoIP products allow Biamp Tesira digital signal processors to make and receive phone calls over a Voice-over-IP (VoIP) system that adheres to the Session Initiation Protocol (SIP) standard. Microsoft Lync or Microsoft Skype for Business systems make use of an expanded version of SIP called MS-SIP or Microsoft SIP Extension. This document details the steps required to configure Biamp’s Tesira VoIP products to connect to a Microsoft Lync system.
The Tesira SVC-2 and TesiraFORTÉ endpoints have been tested against the following versions from Microsoft:
- Microsoft Lync 2010
- Microsoft Lync 2013
- Microsoft Skype for Business (SFB)
It should be noted that the screenshots used in this tech note were take from a SFB server. While older Lync versions use the same setup process the user interface layout may vary slightly.
Microsoft license requirements
While full support for 3rd party endpoints is available in SFB / Lync out of the box, using these services requires you to purchase Microsoft license agreements for each line in use. The following is a list of Client Access Licenses (Cal's) that are required per line of the SVC-2 or TesiraFORTE. Note that each Tesira VoIP endpoint can support up to two individual lines. Each line being used requires a set of the three licenses listed below:
- Standard User Cal
- A base license for all SFB/Lync clients
- Enterprise User Cal
- A license required for all VoIP endpoints
- Plus User Cal
- A license to access some advanced features of SFB/Lync.
There are no licenses required on the Tesira side of the exchange.
First, we'll focus on setting up the Microsoft Lync / Skype for Business software.
Active Directory settings
Skype for Business Server settings
SFB and Lync support three different mechanisms for device authentication, however Tesira supports only one of these three. The following steps ensure that a mutually support service is enabled.
Next, we'll focus on setting up the Tesira configuration to match the settings that were used in SFB / Lync.
Note: TLS is the default transport protocol for SFB / Lync and will likely be used because of its encryption support for SIP. TCP is a supported alternative to TLS in Lync, but it must be manually enabled. If registration issues occur between SFB / Lync and Tesira, temporarily configuring the system in TCP mode would allow a Wireshark trace to capture unencrypted data for troubleshooting. Additional troubleshooting can be done by downloading the Lync Logs and saving them in the default .uccapilog format. These logs can be sent to Biamp Technical Support for review.
- Under the Protocol SIP category in the Control Status block's Properties Sheet, click on the "..." symbol next to Line Properties. This will open the VoIP Line Properties window.
- Select the Protocol Tab
- In the SIP User Name field, enter the SIP User Name portion of the SIP URI created in SFB/Lync User Dialog page.
- In the SIP Domain field enter the Domain portion of the SIP URI used in the SFB/Lync User Dialog page. Note that the @ symbol does not need to be entered.
- In the Authentication User Name field enter the "User Log In Name (Pre Windows 2000)" created in the Active Directory User Page.
- In the Authentication Password field enter the Password used in the Active Directory Password Page .
- In the netBIOS filed enter the netBios Domain located in the Active Directory User Page. Note that the "/" symbol should be omitted from the Tesira configuration.
- Set the Proxy Vendor to Lync
- Enter the Proxy Address for the SFB/Lync server. There are two methods that can be used to set the Proxy Address:
The Tesira device will try each method in order and the first to receive a response will be used. Note that in order to make use of these settings the Proxy Port must be set to 0.
- Send the Tesira configuration to the system to complete the setup.