Polycom HDA50 Administrator Guide

3.3.0 | September 2019 | 3725-86015-001B

ADMINISTRATOR GUIDE

Polycom

®

HDA50

2

Copyright

©

language or format, or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the

express written permission of Polycom, Inc.

6001 America Center Drive

San Jose, CA 95002

USA

Trademarks Polycom

®

, the Polycom logo and the names and marks associated with Polycom products are trademarks

and/or service marks of Polycom, Inc. and are registered and/or common law marks in the United States and various

other countries.

All other trademarks are property of their respective owners. No portion hereof may be reproduced or transmitted in any

form or by any means, for any purpose other than the recipient's personal use, without the express written permission

of Polycom.

Disclaimer While Polycom uses reasonable efforts to include accurate and up-to-date information in this document,

Polycom makes no warranties or representations as to its accuracy. Polycom assumes no liability or responsibility for

any typographical or other errors or omissions in the content of this document.

Limitation of Liability Polycom and/or its respective suppliers make no representations about the suitability of the

information contained in this document for any purpose. Information is provided "as is" without warranty of any kind and

is subject to change without notice. The entire risk arising out of its use remains with the recipient. In no event shall

Polycom and/or its respective suppliers be liable for any direct, consequential, incidental, special, punitive or other

damages whatsoever (including without limitation, damages for loss of business profits, business interruption, or loss of

business information), even if Polycom has been advised of the possibility of such damages.

End User License Agreement BY USING THIS PRODUCT, YOU ARE AGREEING TO THE TERMS OF THE END

USER LICENSE AGREEMENT (EULA) AT: http://documents.polycom.com/indexes/licenses. IF YOU DO NOT AGREE

TO THE TERMS OF THE EULA, DO NOT USE THE PRODUCT, AND YOU MAY RETURN IT IN THE ORIGINAL

PACKAGING TO THE SELLER FROM WHOM YOU PURCHASED THE PRODUCT.

Patent Information The accompanying product may be protected by one or more U.S. and foreign patents and/or

pending patent applications held by Polycom, Inc.

Open Source Software Used in this Product This product may contain open source software. You may receive the

open source software from Polycom up to three (3) years after the distribution date of the applicable product or software

at a charge not greater than the cost to Polycom of shipping or distributing the software to you. To receive software

information, as well as the open source software code used in this product, contact Polycom by email at

[email protected].

Customer Feedback We are striving to improve our documentation quality and we appreciate your feedback. Email

your opinions and comments to Docume[email protected]m.

Polycom Support Visit the Polycom Support for End User License Agreements, software downloads, product

documents, product licenses, troubleshooting tips, service requ

ests, and more.

Polycom, Inc. 1

Contents

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Audience, Purpose, and Required Skills . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Polycom and Partner Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

The Polycom Community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Notational Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Canonical Fashion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Literal Fashion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Boolean Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Multiple Choice Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Parameter Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Port Setup and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Configuration and Management Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Web Server-Based Local Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Local Device Update and Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Firmware Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Customized AA Prompts Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Backup Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Restore Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Reset Configuration Locally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Reset Configuration Remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Device Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Headset Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Phone Port Setup and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Use the Device as a Paging System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Available Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Contents

Polycom, Inc. 2

IP Routing and LAN Switching Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

IP Routing Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

LAN Switching Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

802.1X Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Status Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

WAN Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Product Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

USB Headset Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

SPn Service Status (n = 1, 2, 3, 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

OBiTALK Service Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

LAN Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Call Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Call History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Services, Phone, and Line Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Device Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Codec Profile Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Tone and Ring Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Tone Profile Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Field-1 Composition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Field-2 Composition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Field-3 to Field-6 Composition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Tone Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Ring Profile A & B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Ring Profile Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Field-1 Composition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Field-2 to Field-5 Composition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Call Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Inbound Call Route Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Outbound Call Route Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Trunks, Endpoints, and Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Service Providers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

SIP Service Provider Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

SIP Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

ITSP Driven Distinctive Ringing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

RTP Statistics – the X-RTP-Stat Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Media Loopback Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Contents

Polycom, Inc. 3

Using SPn as a Proxy for a SIP IP Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Automated Attendant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Customizing AA Prompt Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Trunk Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Parameter Reference Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Phone Port Setup and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Possible Error Messages on Firmware Update Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Polycom, Inc. 4

Before You Begin

This guide describes how to administer, configure, and provision Polycom

®

HDA50 devices.

Audience, Purpose, and Required Skills

This guide is for a technical audience. You must be familiar with the following concepts before beginning:

● Current telecommunications practices, protocols, and principles

● Telecommunication basics, video teleconferencing, and voice or data equipment

● Open SIP networks and VoIP endpoint environments

Related Documentation

For more information on HDA50, refer to the following documents on Polycom Support. These documents

are written for service providers and system administrators.

● Polycom

®

HDA50 Setup Sheet: Includes information about cable connections, package contents,

front panel LEDs, and safety and regulatory information.

● Polycom

®

HDA50 Deployment Guide: Includes information about configuration, device settings,

initial configuration setup, and a provisioning parameter reference guide.

Getting Help

For more information about installing, configuring, and administering Polycom products, see Documents &

Software at Polycom Support.

Polycom and Partner Resources

In addition to this guide, the following documents and other resources provide details and resources:

● For Polycom Software releases and documentation, see Polycom Voice Support.

● For user guides for Polycom voice products, refer to the product support page for your phone at

Polycom Voice Support.

● You can find Request for Comments (RFC) documents by entering the RFC number at

https://www.ietf.org/rfc/.

● For information on IP PBX and softswitch vendors, see Polycom Desktop Phone Compatibility.

● For information on Polycom Device Management Service for Service Providers (PDMS-SP), refer to

the documentation on Polycom Support.

Before You Begin

Polycom, Inc. 5

To find all Polycom partner solutions, see Strategic Global Partner Solutions.

The Polycom

Community

The Polycom Community gives you access to the latest developer and support information. Participate in

discussion forums to share ideas and solve problems with your colleagues. To register with the Polycom

Community, simply create a Polycom Online account. When logged in, you can access Polycom support

personnel and participate in developer and support forums to find the latest information on hardware,

software, and partner solutions topics.

Documentation Feedback

We welcome your feedback to improve the quality of Polycom documentation.

You can email Documentation Feedback for any important queries or suggestions related to this

documentation.

Notational Conventions

This guide provides device configuration parameters and their values in the following formats:

● Canonical fashion

● Literal fashion

Both notational conventions point to the same parameters, but their appearances are different.

The canonical fashion simplifies locating parameters on the device’s native web portal or on OBiTALK at

https://www1.obitalk.com.

The literal fashion is required when provisioning or writing OBIPhoneXML apps.

Canonical Fashion

This example shows the format of the canonical fashion.

● Parameter Group Name::ParameterName = Parameter Value {replace with actual

value}

The Parameter Group Name is the heading of the parameter group on the left side panel of the device local

configuration or OBiTALK Configuration web page. This string may contain spaces. When a group heading

has more than one level, each level is separated with a –, such as:

● Services Providers - ITSP Profile A – SIP:

The ParameterName is the name of the parameter as shown on the web page and MUST NOT CONTAIN

ANY SPACES. Parameter Group Name and ParameterName are separated by two colons (::),as shown

in the first example above.

The Parameter Value is the literal value to assign to the named parameter and may contain spaces. You

can omit Parameter Group Name or its top-level headings when the context is clear. For example:

● SP1 Service::AuthUserName = 4082224312

● ITSP Profile A - SIP::ProxyServer = sip.myserviceprovider.com

Before You Begin

Polycom, Inc. 6

● ProxyServerPort = 5082

Literal Fashion

These examples show the format of the literal fashion. The literal fashion is used when provisioning or

writing OBIPhoneXML apps.

● ParameterGroupName.ParameterName.Parameter Value

{replace-with-actual-value}

● Parameter.Group.Name.ParameterGroupName.ParameterName.Parameter Value

The ParameterGroupName. is the name of the first parameter group in literal fashion. This string MUST

NOT CONTAIN ANY SPACES, and always is terminated with a period, as shown. More than one

ParameterGroupName. may be used. The ParameterGroupName. is case-sensitive.

The ParameterName. is the name of the parameter, and always is terminated with a period, as shown. This

string MUST NOT CONTAIN ANY SPACES. The ParameterName. is case-sensitive.

The Parameter Value is the literal value to assign to the named parameter and may contain spaces. The

Parameter Value is not case-sensitive, but it MUST EXACTLY MATCH the value when one or more

choices are available.

When using the literal fashion in your XML, you need to exactly match the text string for

ParameterGroupName.ParameterName.Parameter Value, but text formatting such as bold face is not

required and will be removed when your script or app is processed.

Boolean Values

You can identify parameters that take a Boolean value on your device’s configuration web pages by a check

box next to the parameter name. Throughout the document, we may loosely refer to a Boolean value as

“enable/disable” or “yes/no”, but the only valid Boolean parameter values to use in a device configuration

file is either true/false or True/False (case-sensitive). This is equivalent to selecting or clearing the

check box on the configuration web pages.

Multiple Choice Values

You must provision parameters that take one of several valid options from a drop-down list on the device

message with string values that match exactly one of those choices. Otherwise, the device uses the default

choice. Matching the provisioned value against valid strings is case-sensitive and doesn’t allow extra

spaces.

When a choice must be selected, the device web page provides a drop-down menu for that parameter. Copy

that value into your provisioning script.

Parameter Values

When entering a parameter value from the web page or via provisioning, avoid adding extra white spaces

before or after the parameter value. If the value is a comma-separated list of strings or contains attributes

after a comma or semicolon, avoid adding extra white space before and after the delimiter.

For example: CertainParameter = 1,2,3,4;a;b;c

Before You Begin

Polycom, Inc. 7

If a parameter value can include white spaces, such as X_DisplayLabel, use just a single space and no

extra space before and after the value.

For example: X_DisplayLabel = My New Service

Polycom, Inc. 8

Getting Started

The HDA50 is a VoIP adapter for USB headsets. It offers audio reliability in instances when you prefer to

use a soft client for call management and control. Similar to a desk phone, it ensures that audio traffic is

separated and prioritized.

You can manage the HDA50 configuration and network interaction directly through the device, the native

device web interface, or the PDMS-SP portal at https://www1.obitalk.com.

Product Overview

The Polycom HDA50 is an Open SIP USB headset adapter with the following features:

● SIP service provider or local system administrator support for up to four SIP accounts

● USB headset connectivity optimized for Plantronics headsets

● Aggregation and bridging of SIP services

● Automatic Attendant (AA) for simplified call routing

● High-quality voice encoding using G.711, G.7.22, G.726, G.729, Opus, and iLBC algorithms

● Recursive digit maps and associated call routing (outbound and inbound)

Port Setup and Configuration

Make the following connections to use your device. For details, see the HDA50 Setup Sheet.

● Power Connection - Connect the supplied 12-volt power adapter to the device and the wall outlet or

working power strip. Only use the power adapter supplied with the original packaging to power the

device. Use of any power adapter other than what was provided with the device voids the warranty

and may cause the unit to not function at all or cause undesired operation.

● Internet Connection Setup and Configuration - Connect an Ethernet cable from an available switch

port to the Internet port. By default, the device requests IP, DNS, and Internet (WAN) Gateway IP

addressing via DHCP.

Polycom, Inc. 9

Configuration and Management

Interfaces

The HDA50 provides these interfaces for local configuration and management:

● Device web page

● Remote configuration and management using PDMS-SP at https://www1.obitalk.com

Web Server-Based Local Configuration

You can access the HDA50 device configuration web page using the IP address and default account

credentials:

● For user access, the default user name and password are user and user.

● For administrator access, the default user name and password are admin and admin.

Access the Device Management Web Page

Each device has its own built-in portal site at http://{ip-address} where {ip-address} is the IP

address of the device. The native web portal offers configurable options and status information organized

into a number of web pages.

If the device is already bootstrapped into your assigned PDMS-SP account, follow the procedure below to

find the device’s IP address.

Procedure

1 Log in to PDMS-SP.

2 Go to the Manage Device page and select the device by OBi number, MAC Address, or Serial

Number.

3 Go to the Configuration tab and select Local Configuration.

4 You can find the IP address at System Status > WAN Status > IPAddress.

5 Enter the device IP address in the address field of your web browser.

6 When prompted, enter the user name and password.

Use the collapsible menu on the left side of the page to easily go to the various configuration parameter

sections of the device.

In the PDMS-SP interface, Polycom recommends that you claim your device before you connect it

to the internet. Use this method instead of adding the device. After you claim it, the device is

associated with your account.

Configuration and Management Interfaces

Polycom, Inc. 10

Submit every configuration page individually after changes are made on the page. Otherwise changes are

discarded once you go to another page. Most changes require a reboot of the unit (by clicking the Reboot

button) to take effect. However, you may reboot the unit just once after you have made and submitted all the

necessary changes on all the pages.

For more information on using the PDMS-SP interface, refer to the Polycom Device Management Service

for Service Providers Administrator Guide at Polycom Support.

Local Device Update and Management

You can manually update and manage your device.

Firmware Update

You can upgrade the firmware for your device from the device management web page. Store the firmware

file locally on a computer that you can access a web browser.

Procedure

1 Select the System Management – Device Update menu on the side panel of the web page.

2 Click the Browse button in the Firmware Update section of the page. In a file browser window,

select the firmware file.

3 Click the Update button to start the upgrade process.

The process takes about 30 seconds to complete.

To perform a multiple device upgrade, refer to the PDMS-SP procedure at

https://documents.polycom.com/bundle/pdms-sp-ag-current/page/t2733076.html

For step 3, use the HDA50 firmware link http://fw.obihai.com/HDA50-x-x-x-xxxx.fw.

Customized AA Prompts Backup and Restore

To restore an Automated Attendant (AA) prompt file, proceed exactly like a firmware upgrade via the web

browser, but provide the device with the prompt file instead of a firmware file.

When the device is operating in router mode, access the built-in web server from the LAN side or

the WAN side. LAN side access is always allowed. For security reasons, the access from the WAN

side can be disabled by configuration. WAN side access to the web server is disabled by default.

You can enable this option on the device web page (from the LAN side).

Don’t disconnect the power from the device during this procedure. If the new firmware is upgraded

successfully, the device reboots automatically to start running the new firmware. Otherwise, the

web page shows an error message explaining why the upgrade failed.

Configuration and Management Interfaces

Polycom, Inc. 11

Procedure

1 Select the System Management – Device Update menu on the side panel of the web page.

2 Click the Browse button in the Firmware Update section of the page. In a file browser window,

select the prompt file.

3 Click the Update button to start the upgrade process.

Backup Configuration

You can backup and store the current configuration of the device as a file in XML format at a specified

location. The default name of the file is

backupxxxxxxxxxxxx.xml

, where the xxxxxxxxxxxxxx

represents the MAC address of unit.

Procedure

1 In the Web UI, go to System Management > Device Update.

2 Choose backup options. Refer to the table for more information on backup options.

3 Select Backup to start the process.

4 When prompted, save the.xml file.

Restore Configuration

When restoring the configuration to a previous backup copy, you need to specify the backup file you want

to restore to.

All the existing prompts in the device are removed first when applying the backup file. This process

cannot be undone.

Different web browsers might handle this differently. If the operation is blocked due to the security

setting of the web browser, you should change the security setting temporarily to allow this

operation to complete.

Backup Options

Option Description Default Setting

Incl. Running Status If checked, the values of all status parameters are included in backup

file. Otherwise, status parameters are excluded from the backup.

No

Incl. Default Value If checked, the default values of parameters are included in the backup

file. Otherwise, default values are excluded from the backup.

No

Use OBi Version If not checked, the backup file uses XML tags that are compliant with

TR-104 standard. Otherwise, the backup file is stored in an OBi

proprietary format where the XML tags aren’t compliant with TR-104,

but the file size is smaller and the file is more readable.

No

Configuration and Management Interfaces

Polycom, Inc. 12

Procedure

1 Click the Browse button in the Restore Configuration section of the web page.

2 Select the Restore button to start the process.

The device automatically reboots after the restoration is complete.

Reset Configuration Locally

The Reset Configuration function resets the device to its factory default condition. Call history and various

statistical information are removed at the same time. Use the device reset with extreme caution as the

operation cannot be undone.

Procedure

1 Click Reset on the Reset Configuration web page. A confirmation window displays.

2 Click OK to confirm. The phone resets its configuration to its factory default condition.

The device automatically reboots after the factory reset process completes.

By default, the hardware reset button located via an opening on the underside of the device resets all

settings. You can change reset behavior via configuration.

Reset Configuration Remotely

You can reset the device configuration to its factory default condition remotely.

Procedure

1 Enter the following parameter into an XML configuration file:

2 In the PDMS-SP interface, use base profiles to push the XML file to the device. You can also go to

Restore Configuration on the local web page.

All passwords and PINs are excluded from the backup file. Hence they aren’t available to restore.

Call history is excluded from the backup, but can be saved as an XML formatted file separately

from the Call History web page.

Reset Configuration Options

Option Description Default Setting

Router Configuration When checked, click Reset to restore all your router

configuration parameters to the factory defaults.

Yes

All Settings When checked, click Reset to restore all configuration

parameters to the factory defaults.

Polycom, Inc. 13

Device Interface

The HDA50 contains a number of configurable device interface ports. These provide connections for a

headset, LAN, and computer connections.

Headset Connection

Use the USB port on your HDA50 to connect a supported headset.

To configure headset settings, go to Physical Interfaces > USB Port > USB Headset Settings on the

device web portal.

Phone Port Setup and Configuration

A phone has a very basic interface for I/O of signaling or control messages.

The device Phone port supports input signaling and control messages comprising:

● On Hook

● Off Hook

● Hook Flash

● DTMF tones

The device Phone port supports output signaling and control messages comprising:

● Caller ID/CWCID

● MWI

● DTMF/Tone

● Ring

● Polarity Reversal

● CPC

● Power Denial

The device Phone port has a Maximum Sessions capacity of two. This isn’t configurable. The device Phone

port replies BUSY to a new incoming call when:

● The Phone port already has two calls in session.

● The Phone port is ringing the phone.

● The phone is in a dialing or fast busy state.

● The device is already in a fax call.

The device Phone port supports Call Waiting when a second call is an inbound call:

Device Interface

Polycom, Inc. 14

● Hook-Flash or press the Flash button to switch between calls.

● When the device Phone port goes On-Hook, this ends the current call and invokes a ring for the

holding call. The device Phone port supports 3-way Calling when the second call is an outbound call.

On the first Hook-Flash during an active call, the device can make a second outbound call.

On the second Hook-Flash, the first call and the second outbound call are placed in a conference. To remove

the second conferenced party, invoke a third Hook-Flash.

When the device goes On-Hook during a 3-way Call, this becomes a transfer when the second (outbound)

call is ringing or connected. If the second call doesn’t succeed, then the Phone port goes to an On Hook

state and rings as the holding call is still on the line, or Hook-Flash to resume the first call.

The device Phone port can select from the following services to which it can complete a call:

● SP1 Service (SP1)

● SP2 Service (SP2)

● SP3 Service (SP3)

● SP4 Service (SP4)

Use the Device as a Paging System

The device may be used as a paging system to allow the device to automatically answer incoming calls, but

not accept calls waiting.

Procedure

» Connect the device Phone port to an external PA system using an RJ11-to-line-out-connector, and

enable the UseForPagingOnly parameter.

Available Features

The HDA50 supports many IP routing, LAN and Auto Answer features.

IP Routing and LAN Switching Features

The HDA50 has two Ethernet ports labeled as the Internet port and the LAN port. The device works as a

router by default. All the native voice services and features use the WAN port only when the HDA50 is in

router mode. To use the device as a 3-port switch (in Bridge mode) change its OperationMode parameter

from Router to Bridge. One of the switch ports is for internal use only.

IP Routing Features

In router mode, the network connected to the Internet Port is the WAN side of the device, and the network

connected to the LAN Port is the LAN side. You can connect the WAN side to another Ethernet switch or

directory to an access device, such as a modem. The HDA50 routes traffic between the LAN side and the

WAN side, allowing devices (such as PCs) attached to the LAN side to share Internet access. The HDA50

supports subnet masks as large as 255.255.255.0 to accommodate as many as 253 IP addresses on its

LAN side subnet.

Device Interface

Polycom, Inc. 15

In addition to being a NAT (Network Address Translation) router, the HDA50 includes a DHCP server, a DNS

forwarder, and a basic firewall. It supports port forwarding, DMZ, QoS, and VLAN (802.1Q). The maximum

routing throughput between the WAN and the LAN side is approximately 30 Mbps. This speed can be

achieved when there are no active calls in the system. Otherwise, speed is limited to accommodate the

voice processing load. If the WAN side is connected to an Internet access device, the speed could be further

limited by the Internet uplink and downlink.

The HDA50 acquires its WAN side IP address using one of the following methods:

● Static Address Assignment

● DHCP

● PPPoE

The HDA50 acquires its WAN side IP address using DHCP by default. Also by default, the HDA50’s own

DHCP server is enabled to support LAN side clients such as PCs. The default LAN side IP address of the

router is 192.168.10.1.

Incoming packets received from the WAN side are forwarded by the router according to the following flow:

● If the firewall is enabled, discard the packet if it’s rejected by any one of the active firewall

components.

● If the sending host address matches a valid entry in an internal host binding table, queue the packet

for local processing. The router updates the binding table.

● If the sending host address matches a valid entry in an internal NAT binding table, forward the packet

to the corresponding LAN IP address. The router updates the NAT binding table.

● If the receiving port and protocol match a reserved pair to support an internal process, queue the

packet for local processing.

● If the receiving port and protocol match a port forwarding rule, forward the packet to the LAN IP

address according to that rule.

● If a DMZ host is configured, forward the packet to that LAN IP address.

● Queue the packet for internal processing.

DHCP Server

By default, the built-in DHCP server is enabled on the HDA50. It assigns IP address, network mask, DNS

server, and default gateway address to the DHCP clients on the LAN side. The default gateway and DNS

server have the same IP address as the LAN side IP address of the router. In the DHCP server configuration,

you can select the range of client IP addresses to give out the Lease Time and the Local Domain Name.

Furthermore, by using the DHCP reservation feature, you can reserve specific IP addresses for some

devices with specific MAC addresses. See the LAN Settings Parameter Guide and DHCP Reservation

Parameter Guide sections for more details.

Firewall

The firewall protects local processes and LAN side clients against certain basic threats from the WAN side

(or the Internet), such as port scanning and a DOS (Denial of Service) attack. Use the firewall settings to

turn on or off the following features:

●NATRedirection – If enabled, supports NAT Redirection, also known as NAT Loopback or Hairpin.

The default is disabled.

● DRDOSAttackProtection – If enabled, protects against DOS attack. The default is disabled.

Device Interface

Polycom, Inc. 16

● VPNPassThrough – If disabled, blocks all VPN traffic. The default is enabled.

These features take effect if the firewall is enabled. Otherwise, they’ll take on their respective default values.

Port Forwarding

You can define as many as 20 port forwarding rules on the device. For each rule, specify a range of ports

and designate receiving LAN IP address. You can also specify a rule for each that specifies if it should only

apply to packets transported over UDP, TCP, or both.

DMZ

The DMZ host is the default LAN client address that a packet received from the WAN side is forwarded to

when the router fails to find a matching LAN IP address or matching local process. If the firewall is enabled,

the packet is still subject to firewall inspection before forwarding to the DMZ host.

QoS

QoS (Quality of Service) refers to the prioritization of network traffic based on traffic type. On the HDA50,

QoS policy applies to upstream traffic (LAN-to-WAN) only. Downstream QoS is up to the ISP / upstream

routers and switches. The upstream traffic is prioritized according to its type of service as indicated by the

DiffServ/TOS bits in the IP header of each packet. In the QoS settings, you can map the 64 possible types

of service to one of the three priority classes: High, Medium, or Low. You also can specify the guaranteed

minimum upstream bandwidth for each priority class. LAN side clients indicate the desired priority class of

their outbound packets to the router by marking the DiffServ/TOS bits of their packets. See the QoS

Parameter Guide section for more details.

In addition to the three priority classes, a fourth priority class known as the Restricted class is available. The

Restricted class has the highest priority among the four classes. The guaranteed bandwidth for the

Restricted class is set separately with its own parameter in the configuration.

The total guaranteed bandwidth allocated to all the four priority classes is equal to the total available

bandwidth, specified in UpStreamBandwidth parameter in the QoS settings.

VLAN Support in Router Mode

In router mode, the HDA50 can support VLAN (802.1Q) on the WAN side. If you enable VLAN, the incoming

packets on WAN that don’t belong to the same VLAN are dropped. All outgoing packets on WAN are tagged

with the VLAN ID. The VLAN support is transparent to the devices on the LAN side. The router removes the

VLAN tag when forwarding packets to the LAN side.

LAN Switching Features

You can set the HDA50 to act as a 3-port switch. One of the ports is internal, while the two external ports

(labeled as Internet and LAN) connect to other devices. This is the Bridge mode. In this mode, all the router

features, such DHCP server, firewall, and port forwarding, won’t take effect. In this case, the QoS policy

provides native voice traffic the highest priority (this behavior isn’t configurable).

Device Interface

Polycom, Inc. 17

VLAN Support in Bridge Mode

If you enable VLAN in Bridge mode, incoming packets that don’t belong to the same VLAN are dropped. All

outgoing packets are tagged with the configured VLAN ID. The packets switched directly between the

external ports are not modified by the device.

Auto Answer

The HDA50 headset adapter supports three methods to signal to the called device to auto-answer the call:

● Call-Info: The phone receives an answer-after=0 parameter in a Call-Info header in the INVITE

request.

● Alert-Info: The phone receives info=alert-autoanswer;delay=0 parameters in an Alert-Info header in

the INVITE request.

● Talk Event: The phone receives an in-dialog NOTIFY with event: Talk while a call is offering.

For incoming calls, your phone proc

esses the “answer-after” parameter in a Call-Info header or the “info”

and “delay” parameters in an Alert-Info header, whichever is present in the inbound INVITE. It automatically

answers the call after ringing for the number of seconds specified in those parameters (usually 0).

When the phone automatically answers the call, all other ongoing calls are interrupted the standard way as

this is a new call added to the foreground.

For the talk event, the phone answers immediately after receiving the talk event. Timing is therefore

controlled by the system sending the event, which is usually driven by a user choosing to answer the call

from their soft client.

Turn off Auto Answer

You can also turn off the auto-answer feature.

» Disable the Physical Interfaces > USB Port > USB Headset Settings::AutoAnswerEnable option.

Auto-Answer Incoming Call Based on Inbound Call Routing

Rules

The HDA50 can auto answer certain incoming calls based on inbound call routing rules by specifying a rule

that routes the call to hs(autoans). You may autoanswer all calls or by using a rule to match specific digits,

target only certain numbers for auto-answer.

Routing rules applied here will supersede any rules for auto-answer that may be received as part of

Alert-Info or Call-Info headers. For example:

{hs(autoans;nobeep)},{(@.4089991234):hs(antoans;delay=2)},{hs}

The autoans syntax supports two optional semi-colon separated attributes:

●nobeep: Not to play a beep tone on answering. Default is to play the beep tone according to user

preference setting.

● delay={value in seconds}: The number of seconds to ring before auto-answering the call. Default is

0.

Device Interface

Polycom, Inc. 18

802.1X Authentication

The device supports the following 802.1X authentication modes:

● Disable

● MD5

● TLS

● TTLS/MSCHAPv2

● PEAP-MSCHAPv2 (optional for all parameters)

You can set the authentication mode using the parameter WAN Settings - Internet

Settings::802_1XMode. Depending on the selected mode, you have to configure the additional

authentication parameters listed in the following table.

802_1X Authentication

Parameter Description

(EAP)

MD5

(EAP)

TLS1.0

TTLS/

MSCHAPv2

802_1XIdentity A user name. If the value isn’t needed,

set the value as an empty string.

Required Required Required

802_1XPassword A password or passphrase. If a

password or passphrase isn’t needed,

set the value as an empty string.

Required Required Required

802_1XAnonymousID When empty, anonymous identity is

used in authentication.

Required Required

802_1XTLSSecurityProfile Security profile for the 802.1x

authentication.

Required

Page is loading ...

Polycom HDA50 Administrator Guide

Polycom HDA50 Administrator Guide

Related papers

Other documents