Version 2.0.13B 11 400HD Series for Skype for Business
400HD Series for Skype for Business
Notice
This manual shows administrators how to set up and configure AudioCodes' 400HD Series IP
Phones for Microsoft Skype for Business in the enterprise network environment.
Information contained in this document is believed to be accurate and reliable at the time of
printing. However, due to ongoing product improvements and revisions, AudioCodes cannot
guarantee accuracy of printed material after the Date Published nor can it accept
responsibility for errors or omissions. Updates to this document and other documents can be
viewed by registered customers at http://www.audiocodes.com/downloads.
This document is subject to change without notice.
Date Published: Feb-02-2016
Trademarks
AudioCodes, AC, HD VoIP, HD VoIP Sounds Better, IPmedia, Mediant, MediaPack, What’s
Inside Matters, OSN, SmartTAP, VMAS, VoIPerfect, VoIPerfectHD, Your Gateway To
VoIP, 3GX, VocaNOM and CloudBond 365 are trademarks or registered trademarks of
AudioCodes Limited All other products or trademarks are property of their respective
owners. Product specifications are subject to change without notice.
WEEE EU Directive
Pursuant to the WEEE EU Directive, electronic and electrical waste must not be disposed
of with unsorted waste. Please contact your local recycling authority for disposal of this
product.
Customer Support
Customer technical support and services are provided by AudioCodes or by an authorized
AudioCodes Service Partner. For more information on how to buy technical support for
AudioCodes products and for contact information, please visit our Web site at
www.audiocodes.com/support.
Abbreviations and Terminology
Each abbreviation, unless widely used, is spelled out in full when first used.
Documentation Feedback
AudioCodes continually strives to produce high quality documentation. If you have any
comments (suggestions or errors) regarding this document, please fill out the
Documentation Feedback form on our Web site at http://www.audiocodes.com/downloads.
Your valuable feedback is highly appreciated.
Administrator's Manual 12 Document #: LTRT-09940
Administrator's Manual Notices
Related Documentation
Document Name
420HD IP Phone User’s Manual
430HD and 440HD IP Phone User’s Manual
420HD IP Phone Quick Guide
430HD IP Phone Quick Guide
440HD IP Phone Quick Guide
IP Phone Management Server Administrator's Manual
EMS and SEM Server IOM Manual
EMS User's Manual
One Voice Resiliency Configuration Note
Regulatory Information
Compliancy and Regulatory Information can be viewed at:
http://www.audiocodes.com/library.
Note: Throughout this document, where features can be configured using the Web
interface or configuration file, the Web parameter is displayed in the regular font above
its corresponding configuration file parameter, which is enclosed in square brackets in
bold font type.
Version 2.0.13B 13 400HD Series for Skype for Business
400HD Series for Skype for Business
This page is intentionally left blank.
Administrator's Manual 14 Document #: LTRT-09940
Administrator's Manual 1. Introduction
1 Introduction
This Administrator's Manual is intended for administrators responsible for provisioning
AudioCodes' 400HD Series of IP Phones deployed with Microsoft Skype for Business in an
enterprise network.
Note: Microsoft rebranded Lync as Skype for Business so whenever the term
Skype for Business appears in this document, it applies also to Microsoft Lync.
AudioCodes IP phones are based on AudioCodes' proprietary High Definition (HD) voice
technology, providing clarity and a rich audio experience in Voice-over-IP (VoIP) calls.
The phones are fully-featured telephones that provide voice communication over an IP
network, allowing you to place and receive phone calls, put calls on hold, transfer calls, etc.
The phones offer different automatic provisioning options.
This manual shows how to automatically provision a mass deployment of AudioCodes IP
phones using DHCP.
Version 2.0.13B 15 400HD Series for Skype for Business
400HD Series for Skype for Business
This page is intentionally left blank.
Administrator's Manual 16 Document #: LTRT-09940
Administrator's Manual 2. Automatic Mass Provisioning of IP Phones using DHCP
2 Automatic Mass Provisioning of IP
Phones using DHCP
This section shows how to automatically provision a mass deployment of AudioCodes IP
phones in a Microsoft Skype for Business environment.
Note: Instead of using DHCP as the automatic provisioning method, you can
alternatively use Static DNS Record or SIP SUBSCRIBE and NOTIFY messages (see
Appendix A).
As DHCP clients, AudioCodes IP phones can be automatically provisioned with the
following files:
Configuration file (.cfg)
Firmware file (.img)
These files can be placed on any of these three provisioning server types:
HTTP/S server
TFTP server FTP server
Figure 2-1 summarizes the steps required for setting up mass provisioning of IP phones in
the Microsoft Skype for Business environment.
These steps are described in detail in the following sections.
Note: Automatic mass provisioning of IP phones using the DHCP provisioning method
can alternatively be performed from the AudioCodes EMS Provisioning Server in the IP
Phones Management Server. For detailed information, see the IP Phone Management Server Administrator's Manual.
Version 2.0.13B 17 400HD Series for Skype for Business
400HD Series for Skype for Business
Prepare the Microsoft Skype for Business environment for
IP phones, e.g., configure the DHCP server with DHCP
Option 160 to point to the provisioning server’s URL
Without signing in, save a single phone’s default
configuration as a .cfg file, using the Web interface
1
2
3
Configure this single phone to perform according to your
specific performance requirements in the enterprise
4
Save the phone’s newly configured settings as a .cfg file
5
Create a configuration .cfg file containing only the delta
between the default .cfg and the newly configured
enterprise-specific .cfg file
6
7
Place the delta .cfg file on the provisioning server
Load this delta .cfg file to another phone. Sign in.
Test performance to see if it matches requirements.
Connect all IP phones to the network and power up.
Phones are automatically provisioned
8
Figure 2-1: Setting up Automatic Provisioning
Administrator's Manual 18 Document #: LTRT-09940
Administrator's Manual 2. Automatic Mass Provisioning of IP Phones using DHCP
2.1 Preparing the Microsoft Skype for Business
Environment for IP Phones
Before plugging in and playing the IP phones in an enterprise's Microsoft Skype for
Business environment, make sure that the environment is ready for them.
To prepare it for IP phones, you must set up:
1. Front End Skype for Business Server
2. Domain Controller, including:
a. Active Directory, LDAP service
b. DNS service
c. DHCP service
d. NTP service (optional)
Version 2.0.13B 19 400HD Series for Skype for Business
400HD Series for Skype for Business
2.1.1 Making Sure DHCP Server Options are Correctly Configured
This section shows how to ensure that your enterprise's DHCP server options are correctly
configured and that the network environment is ready for deployment of IP phones.
For detailed Microsoft instructions on setting up DHCP for the IP phone, see:
DHCP Option 43 (comprising 001-005 in the figure above) is correctly configured
(see Section 2.1.1.1 on page 20below)
DHCP Option 120 is correctly configured (see Section 2.1.1.3 on page 21below)
DHCP Option 42 is correctly configured (see Section 2.1.1.4 on page 21below)
Correct configuration of these three is critically important. The other DHCP options shown
in the figure above are also important but are less susceptible to inaccuracies than these.
2.1.1.1 DHCP Option 43
Option 43 comprises the five sub-options 001-005 shown in the figure above and in the
table below. These point the phone to the location of the Certificate Provisioning service on
the Skype for Business server. Use the table as a reference to make sure that each suboption is correctly configured. Sub-option 010 is shown in the next section (VLAN
Discovery via DHCP).
Refer also to http://technet.microsoft.com/en-us/library/gg398088(v=ocs.14).aspx
Table 2-1: DHCP Option 43 Configuration Reference
Sub-Option Number Sub-Option Name ASCII Value (example)
Administrator's Manual 2. Automatic Mass Provisioning of IP Phones using DHCP
2.1.1.2 VLAN Discovery via DHCP Option 43
Option 43 comprises the five sub-options 001-005 shown in the previous section, as well
as sub-option 010, shown in the table below. Sub-option 010 is used to specify a voice
VLAN. It is not mandatory.
Refer also to http://technet.microsoft.com/en-us/library/gg398088(v=ocs.14).aspx
Sub-Option Number Sub-Option Name ASCII Value (example)
010 VoiceVLAN Valid values: 1-4094
2.1.1.3 DHCP Option 120
Option 120, which includes the Skype for Business Server’s fully qualified domain name
(FQDN) as shown in the table below, is required for the certification authority (CA) pool
Registrar.
Use the table as reference to make sure Option 120 is correctly configured.
Option 42 specifies the servers that provide NTP /SNTP for the network. Make sure that
NTP server IP addresses are correct, as shown in the table below.
Use a DHCP Scope Option if vendor phones other than those of AudioCodes are deployed
in the same enterprise as AudioCodes' phones and a DHCP Option cohabitation issue
consequently occurs.
This section shows how to configure provisioning of AudioCodes phones using a DHCP
Scope Option when other vendor phones in the enterprise point to the same DHCP server
and use one of the standard DHCP Options described in the previous sections.
To configure provisioning of AudioCodes phones using a DHCP Scope
Option:
1. Determine the DHCP server hosting the phones.
2. Determine if DHCP Options are assigned to IPv4 or IPv6 addresses.
Note:
• The examples below show DHCP server acrtplab-ad.audiocodes.local
• The examples below show IPv4 addresses
Version 2.0.13B 21 400HD Series for Skype for Business
400HD Series for Skype for Business
Figure 2-3: DHCP Options Assigned to IPv4 Addresses
3. Define a separate User Class for each AudioCodes phone model deployed (420HD,
430HD and 440HD phone models): Right-click the IPv4 server icon and from the
popup menu, select Define User Classes…
Figure 2-4: Defining User Classes
The DHCP User Classes screen opens.
Figure 2-5: DHCP User Classes
4. Click the Add… button.
Administrator's Manual 22 Document #: LTRT-09940
Administrator's Manual 2. Automatic Mass Provisioning of IP Phones using DHCP
Figure 2-6: New Class
5. In the New Class screen, enter Display name and Description as shown in the figure
above, and then in the ASCII field, enter the User Class Phone Type (see the Packet
Bytes window in Wireshark below for an example of the 420HD phone, and see the
table below for the other AudioCodes phone models) to be sent from the phone during
DHCP Discover via Option 77 (supported by DHCP Server 2008). Do this for each
AudioCodes phone model so that a User Class entry for each model deployed will
exist when completed.
Figure 2-7: Packet Bytes Window
6. Make sure one DHCP User Class entry exists for each AudioCodes phone model
deployed in the enterprise.
Version 2.0.13B 23 400HD Series for Skype for Business
400HD Series for Skype for Business
Figure 2-8: DHCP User Classes
Table 2-5: DHCP User Class Entry for Each AudioCodes Phone Model Deployed
Display Name Description ASCII
420HD AudioCodes 420HD IP Phone 420HD
430HD AudioCodes 430HD IP Phone 430HD
440HD AudioCodes 440HD IP Phone 440HD
7. Configure Scope Option 160. This is not a standard Scope Option, so it needs to be
created. To create it on the server, select the IP version (IPv4) and select Set
Predefined Options…
Figure 2-9: Set Predefined Options
Administrator's Manual 24 Document #: LTRT-09940
Administrator's Manual 2. Automatic Mass Provisioning of IP Phones using DHCP
8. From the 'Option class' dropdown, select DHCP Standard Options, and then click the
Add… button.
Figure 2-10: Predefined Options and Values
9. Add the AudioCodes 160 Option as shown below, and then click OK.
Figure 2-11: Option Type – Add AudioCodes 160 Option
10. Add the IP Phone Management Server location using HTTP. In the figure below, it's
http://<EMS IP address>/firmwarefiles;ipp/dhcpoption160.cfg. See the IP Phone
Management Server Administrator’s Manual for detailed information.
Version 2.0.13B 25 400HD Series for Skype for Business
400HD Series for Skype for Business
Figure 2-12: Predefined Options and Values – Add IP Phone Management Server Location
Note: Ensure you defined http://<EMS IP address>/firmwarefiles;ipp/dhcpoption160.cfg
for DHCP Option 160 in the enterprise's DHCP server.
11. Decide if the DHCP Scope Option needs to be assigned to phones in a specific VLAN
(Scope), or to the entire server (acrtplab-ad.audiocodes.local) for IPv4 addresses.
VLAN Scope
12. Assign to a specific VLAN (Scope of IP addresses such as the Scope below
172.17.0.0, or to multiple Scopes, to be performed separately on each Scope).
a. If selecting a VLAN, expand the 'Scope Leased' folder, select 'Scope Options',
and then select Configure Options from the popup menu.
Administrator's Manual 2. Automatic Mass Provisioning of IP Phones using DHCP
-OR-
b. Select the collapsed folder 'Scope Leased' and in the main screen, right-click
'Scope Options' and select Configure Options…
Figure 2-14: Configure Options 1
-OR Server Option
13. If assigning to the entire server (acrtplab-ad.audiocodes.local), select the 'Server
Options' folder under server IPv4, right-click 'Server Options' and select Configure
Options...
Figure 2-15: Configure Options 2
14. In the Server Options page (or Scope Options page) that opens, select the Advanced
tab, ensure that DHCP Standard Options remains selected, and select 420HD User
Class for the first phone model to be defined. Scroll through the Available Options (all
are cleared) and select only 160 AudioCodes 160 Option.
The figure below shows the Server Options page. The Scope Options page is
identical. Note that the String value you defined for Scope Option 160 is automatically
populated, so it's unnecessary to change it. Note also that if additional DHCP Options
are required (such as DNS or time server) that are different from the Servers Options
for the rest of the Scopes on the server, they can also be selected, but this is typically
not needed.
Version 2.0.13B 27 400HD Series for Skype for Business
400HD Series for Skype for Business
Figure 2-16: Server Options
15. Click Apply and then follow the same procedure to add the 430HD and 440HD user
classes. After adding them, click the OK button.
You have successfully created three separate Scope Options that will only allow
AudioCodes phones to connect to the IP Phone Manager when they boot up and will
not allow other vendor phones from receiving AudioCodes' IP Phone Management
Server as their configuration server.
Figure 2-17: Three Scope Options Created
Administrator's Manual 28 Document #: LTRT-09940
Administrator's Manual 2. Automatic Mass Provisioning of IP Phones using DHCP
2.1.2 Making Sure the DHCP Server is Correctly Configured for Auto
Provisioning
After creating a .cfg configuration file (see Section 2.2), place it - and the software file (img)
and other files such as tone files - on a provisioning server from where the IP phones can
download and install it.
To get the URLs to this provisioning server, the IP phones use DHCP. The provisioning
server can be HTTP/S, TFTP or FTP server.
The phone features automatic update capability to update the configuration and the
software. Checks for newer configuration files and software versions are routinely
automatically performed. Manual checks can also be performed.
To make sure the feature functions correctly:
1. Verify that the provisioning server is running and that the configuration and firmware
files are located in the correct location on it.
2. Connect the phone to the IP network and then to power.
3. On the DHCP server, configure DHCP Option 160 with the URL to the provisioning
server where the configuration and firmware files are located.
By default, the IP phone uses Option 160 which has highest priority.
If absent, the IP phone uses Options 66/67 for TFTP.
The following syntax is available for DHCP option 160:
•<protocol>://<server IP address or host name>/<firmware file
name>;<configuration file name>
• <protocol>://<server IP address or host name>
• <protocol>://<server IP address or host name>/<firmware file name>
• <protocol>://<server IP address or host name>/;<configuration file name>
Where <protocol> can be "ftp", "tftp", "http" or "https"
4. During DHCP negotiation, the phone requests DHCP options 66/67/160 to receive
provisioning information. The DHCP server responds with Option 160 providing the
provisioning URL, or Options 66 and 67 providing the TFTP IP address and firmware
file name respectively.
5. The phone then checks whether new firmware is available by checking the firmware
file header. If the version is different from the one currently running on it, the phone
downloads the complete image and burns it to its flash memory.
6. If new firmware is unavailable, the phone checks whether a new configuration file is
available on the server. If available, the phone downloads it and updates the phone’s
configuration after verifying that the configuration file is related to the phone model.
When a configuration update is needed, the phone might reboot.
Note:
• Only img (firmware) and cfg (configuration) files can be used.
• In the DHCP Discover message, the phone publishes its model name in Option
fields 60 and 77 (e.g., 420HD). To provide different provisioning information to
different models, set up a policy in the DHCP server according to phone model
name.
•If the phone is powered off during provisioning, it becomes unusable; perform a
recovery process (see Section 5 on page 133).
Version 2.0.13B 29 400HD Series for Skype for Business
400HD Series for Skype for Business
2.2 Creating a Configuration File for Auto Provisioning
Most phones deployed in an enterprise typically require identical configuration settings.
Best practice for creating a configuration file for auto provisioning is to:
1. Without signing in, use the Web interface to save a single phone’s default
configuration (factory settings) as a .cfg file.
2. Configure that single phone to perform according to your specific performance
requirements in the enterprise.
3. Save the phone’s newly configured settings as a .cfg file.
4. Create a configuration .cfg file containing only the delta between the default .cfg and
the newly configured enterprise-specific .cfg file.
5. Load this delta .cfg file to another phone, sign in, and test that phone’s performance to
see if it matches requirements.
6. Use this delta configuration .cfg file to automatically provision all IP phones through
DHCP.
2.2.1 Saving a Single Phone’s Default Configuration as a .cfg File
To save a single phone’s default configuration as a .cfg file:
1. Get the phone's IP address (MENU key > Status > Network Status> IP Address)
and point your Web browser to it; the phone's Web interface login page opens.
2. Enter the login credentials (default user name is admin; get Windows credentials from
IT); the Home page of the Web interface is displayed.
3. Open the Configuration File page (Management tab > Manual Update menu >
Configuration File).
Figure 2-18: Web Interface - Configuration File
4. Click the Save Current Configuration File button and save the .cfg file in a folder on
your PC.
Administrator's Manual 30 Document #: LTRT-09940
Loading...
+ 146 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.