Biamp’s Tesira VoIP products allow Biamp Tesira digital signal processors to make and receive phone calls over many different Voice-over-IP (VoIP) systems that adheres to the Session Initiation Protocol (SIP) standard. 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 Skype for Business (SFB) system using SageVue management software
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.
Note: Office 365 implementations of Skype for Business are not supported by Tesira VoIP endpoints.
Microsoft license requirements
While full support for 3rd party endpoints is available in SFB 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 a Tesira VoIP endpoint. 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 clients
- Enterprise User Cal
- A license required for all VoIP endpoints
- Plus User Cal
- A license to access some advanced features of SFB.
There are no licenses required on the Tesira side of the exchange.
First, we'll focus on setting up the Microsoft Skype for Business software.
Active Directory settings
Skype for Business Server settings
SFB supports 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.
Accessing VoIP settings in SageVue
- Open a browser and login to your Sagevue webpage.
- Navigate to "Devices" on the right side of your browser.
- Click on the device description of a device running a configuration that has a VoIP interface
- Navigate to the VoIP configuration tab. (If you cannot access the VoIP settings make sure your account has read/write permissions for VoIP settings. More information on user roles can be found on the online SageVue help page.)
- Select the correct interface that adjustments are going to be made on.
- If you'd like to set the same settings on all VoIP interfaces within this device, enable the "Configure all VoIP cards in this device" option. Note that only fields highlighted in yellow can be updated on multiple endpoints at once.
- Under the Network region of the screen, set “VLAN Tagging” to “Enabled” if your VoIP network uses a tagged VLAN. If the network uses an untagged VLAN or no VLAN, leave this value as “Disabled”. If VLAN is enabled, enter the correct VLAN ID.
- Leave “DHCP” set to “Enabled” if the Tesira endpoint will obtain an IP address automatically from a DHCP server. Otherwise, set “DHCP” to “Disabled”, and manually enter an appropriate static IP Address, Subnet Mask, and Gateway for the Tesira.
- Select your line, Line 1 shows up in a dropdown box, each slectcable VoIP card can use up to two lines.
- Set your Proxy Vendor field to "Lync"
- In the SIP User Name field, enter the SIP User Name portion of the SIP URI created in SFB User Dialog page.
- In the SIP Domain field enter the Domain portion of the SIP URI used in the SFB User Dialog page. Note that the @ symbol does not need to be entered.
- Enter the "User Log In Name (Pre Windows 2000)" created in the Active Directory User Page. (Note that this field must be 20 characters or less. This is a Windows limitation.)
- In the User Logon Password field enter the Password used in the Active Directory Password Page .
- In the NetBIOS field, enter the NetBios Domain located in the Active Directory User Page (the field is located to the left of the "User logon name (pre-Windows 2000)" field). Note that the "\" (backslash) symbol should be omitted from the Tesira configuration.
- Enter the Front End Address for the SFB 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 Front End Server Port must be set to 0.
When changing the proxy vendor to "Lync" in SageVue the transport type is changed to TLS. TLS is the default transport protocol for SFB and will likely be used because of its encryption support for SIP
The default setting for TLS in Tesira will encrypt all SIP data, but accept verification of any server certificate received. If you need to edit this transport type to TCP or change the certificate settings then the VoIP webpage needs to be used. Changing the transport type is not possible through SageVue
Note: TCP is a supported alternative to TLS in SFB, but it must be manually enabled. If registration issues occur between SFB 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 Logs and saving them in the default .uccapilog format. These logs can be sent to Biamp Technical Support for review.
- If you are configuring a second line, switch to "Line 2 Setup" and repeat steps 2-8
- All other settings can remain at their default values in most cases.
- Once all settings have been added, save the changes by clicking "Update". A window will pop up indicating that the changes will be written to the Tesira VoIP endpoint