Académique Documents
Professionnel Documents
Culture Documents
Polycom® SoundPoint®
IP/SoundStation® IP/ VVX™
Family
Patent Information
The accompanying product is protected by one or more U.S. and foreign patents and/or pending patent applications
held by Polycom, Inc.
Disclaimer
Some countries, states, or provinces do not allow the exclusion or limitation of implied warranties or the limitation of
incidental or consequential damages for certain products supplied to consumers, or the limitation of liability for personal
injury, so the above limitations and exclusions may be limited in their application to you. When the implied warranties
are not allowed to be excluded in their entirety, they will be limited to the duration of the applicable written warranty. This
warranty gives you specific legal rights which may vary depending on local law.
Copyright Notice
Portions of the software contained in this product are:
Copyright © 1998, 1999, 2000 Thai Open Source Software Center Ltd. and Clark Cooper
Copyright © 1998 by the Massachusetts Institute of Technology
Copyright © 1998-2003 The OpenSSL Project
Copyright © 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved
Copyright © 1995-2002 Jean-Loup Gailly and Mark Adler
Copyright © 1996-2004, Daniel Stenberg, <daniel@haxx.se>
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated
documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to
whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the
Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.
ii
About This Guide
• Quick User Guides, which describe the most basic features available on
the phones
• User Guides, which describe the basic and advanced features available on
the phones
• Release Notes, which describe the new and changed features and fixed
problems in the latest version of the software
For support or service, please contact your Polycom® reseller or go to Polycom
Technical Support at http://www.polycom.com/voicedocumentation/.
Polycom recommends that you record the phone model numbers, software
(both the BootROM and SIP), and partner platform for future reference.
SoundPoint IP/SoundStation IP/VVX models: __________________________
BootROM version: ________________________________________________
SIP Software version: ______________________________________________
Partner Platform: _________________________________________________
iii
Administrator’s Guide for the SoundPoint IP/SoundStation IP/VVX Family
iv
Contents
2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1
Where SoundPoint IP / SoundStation IP / VVX Phones Fit . . . . . . . . . . 2–2
Session Initiation Protocol Application Architecture . . . . . . . . . . . . . . . . . 2–3
BootROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3
SIP Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5
Resource Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
Available Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
New Features in SIP 3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14
v
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
vi
Contents
vii
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
viii
Contents
ix
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
x
Contents
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Index–1
xi
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
xii
1
Introducing the SoundPoint IP /
SoundStation IP / VVX Family
1-1
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Note Documentation for the SoundPoint IP 300, 301, 500, 501, 600, and 601 desktop
phones and the SoundStation IP 4000 conference phone is available at
http://www.polycom.com/voicedocumentation/ .
• SoundPoint IP 320/321/330/331/335
• SoundPoint IP 430
1-2
Introducing the SoundPoint IP / SoundStation IP / VVX Family
• SoundPoint IP 450
• SoundPoint IP 550/560
1-3
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
• SoundPoint IP 650
• SoundPoint IP 670
1-4
Introducing the SoundPoint IP / SoundStation IP / VVX Family
• SoundStation IP 6000
• SoundStation IP 7000
1-5
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
• Easy-to-use
— An easy transition from traditional PBX systems into the world of IP
— Up to 18 dedicated hard keys for access to commonly used features
— Up to four context-sensitive soft keys for further menu-driven
activities
1-6
Introducing the SoundPoint IP / SoundStation IP / VVX Family
• Platform independent
— Supports multiple protocols and platforms enabling standardization
on one phone for multiple locations, systems and vendors
— Polycom’s support of the leading protocols and industry partners
makes it a future-proof choice
• Field upgradeable
— Upgrade SoundPoint IP / SoundStation IP / VVX as standards
develop and protocols evolve
— Extends the life of the phone to protect your investment
— Application flexibility for call management and new telephony
applications
• Large LCD
— Easy-to-use, easily readable and intuitive interface
— Support of rich application content, including multiple call
appearances, presence and instant messaging, and XML services
— 102 x 23 pixel graphical LCD for the SoundPoint IP
320/321/330/331/335
— 256 x 116 pixel graphical grayscale LCD for the SoundPoint IP 450
— 320 x 160 pixel graphical grayscale LCD for the SoundPoint IP
550/560/650 (supports Asian characters)
— 320 x 160 pixel graphical color LCD for the SoundPoint IP 670
(supports Asian characters)
— 248 x 68 pixel graphical LCD for the SoundStation IP 6000
— 256 x 128 pixel graphical grayscale LCD for the SoundStation IP 7000
— 800 x 480 pixel graphical color LCD for the Polycom VVX 1500 (touch
screen)
1-7
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
— Unused pairs on Ethernet port are used to deliver power to the phone
via a wall adapter allowing fewer wires to desktop (for the
SoundStation IP 6000 and 7000 conference phones)
• Microbrowser
— Supports a subset of XHTML constructs; otherwise runs like any other
Web browser.
1-8
2
Overview
• A call server is active and configured to receive and send SIP messages.
For more information on IP PBX and softswitch vendors, go to
http://www.polycom.com/techpartners1/ .
This chapter contains information on:
• Available Features
2-1
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Remote
Boot Server
Internet
PSTN
Remote
Application
Server
Router/
Firewall
PSTN Gateway
10/100 Ethernet
Ethernet Switches
Switch
Voice Bridge
PC PC
Local Application
Server
Or
Local
10/100 Boot Server
Ethernet
Hub
PC
2-2
Overview
BootROM
The BootROM is a small application that resides in the flash memory on the
phone. All phones come from the factory with a BootROM pre-loaded.
The BootROM performs the following tasks in order:
1. Performs a power on self test (POST).
2. (Optional) Allows you to enter the setup menu where various network
and provisioning options can be set.
The BootROM software controls the user interface when the setup menu
is accessed.
3. Requests IP settings and accesses the provisioning server (or boot server)
to look for any updates to the BootROM application.
If updates are found, they are downloaded and saved to flash memory,
eventually overwriting itself after verifying the integrity of the download.
4. If a new BootROM is downloaded, formats the file system clearing out
any application software and configuration files that may have been
present.
2-3
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
SIP Application
The SIP application manages the VoIP stack, the digital signal processor (DSP),
the user interface, and the network interaction. The SIP application manages
everything to do with the phone’s operation.
The application is a single file binary image and contains a digital signature to
prevent tampering or loading rogue software images.
There is a new image file in each release of software.
The application performs the following tasks in order:
1. Downloads system, per-phone configuration, and resource files.
These files are called sip.cfg and phone1.cfg by default. You can
customize the filenames.
2. Controls all aspects of the phone.
3. Uploads log files.
2-4
Overview
Configuration
The SoundPoint IP / SoundStation IP / VVX phones can be configured
automatically through files stored on a central provisioning server, manually
through the phone’s local UI or web interface, or by using a combination of the
automatic and manual methods.
The recommended method for configuring phones is automatically through a
central provisioning server, but if one is not available, the manual method will
allow changes to most of the key settings.
Note You can make changes to the configuration files through the web interface to the
phone. Using your chosen browser, enter the phone’s IP address as the browser
address. For more information, refer to Modifying Phone’s Configuration Using the
Web Interface on page C-27.
Changes made through the web interface are written to the override file (highest
priority). These changes remain active and will take precedence over the
configuration files stored on the provisioning server until Reset Local Config is
performed.
• Override Files
This section also contains information on:
• Central Provisioning
• Manual Configuration
2-5
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Override Files
This file contains all changes that are made by a user through the their phone
(for example, time/date formats, ring types, and backlight intensity). The file
allows the phone to keep user preferences through reboots and upgrades.
There is an option to clear the override file available to the system
administrator—press the Menu key, and then select Settings > Advanced >
Admin Settings > Reset to Default > Reset Local Config. You will be
prompted to enter the administrative password.
Central Provisioning
The phones can be centrally provisioned from a provisioning server through a
system of global and per-phone configuration files. The provisioning server
also facilitates automated application upgrades, logging, and a measure of
fault tolerance. Multiple redundant provisioning servers can be configured to
improve reliability.
In the central provisioning method, there are two major classifications of
configuration files:
2-6
Overview
Parameters can be stored in the files in any order and can be placed in any
number of files. The default is to have 2 files, one for per-phone setting and one
for system settings. The per-phone file is typically loaded first, and could
contain system level parameters, letting you override that parameter for a
given user. For example, it might be desirable to set the default CODEC for a
remote user differently than for all the users who reside in the head office. By
adding the CODEC settings to a particular user’s per-phone file, the values in
the system file are ignored.
Note Verify the order of the configuration files. Parameters in the configuration file loaded
first will overwrite those in later configuration files.
The following figure shows one possible layout of the central provisioning
method.
Boot Server
SoundPoint IP SIP
Local User Interface Local
MAC 00:04:f2:00:29:99 Web Server
Manual Configuration
When the manual configuration method is employed, any changes made are
stored in a configuration override file. This file is stored on the phone, but a
copy will also be uploaded to the central provisioning server if one is being
used. When the phone boots, this file is loaded by the application after any
centrally provisioned files have been read, and its settings will override those
in the centrally provisioned files.
2-7
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
This can create a lot of confusion about where parameters are being set, and so
it is best to avoid using the manual method unless you have good reason to do
so.
Resource Files
In addition to the application and the configuration files, the phones may
require resource files that are used by some of the advanced features. These
files are optional, but if the particular feature is being employed, these files are
required.
Some examples of resource files include:
• Language dictionaries
• Custom fonts
• Ring tones
• Synthesized tones
• Contact directories
Note If you need to remove the resource files from a phone at some later date—for
example, you are giving the phone to a new user—instructions on how to put the
phone into the factory default state can be found in “Quick Tip 18298: Resetting and
Rebooting SoundPoint IP, SoundStation IP, and Polycom VVX 1500 Phones“ at
http://www.polycom.com/support/voice/soundpoint_ip/VoIP_Technical_Bulletins_pu
b.html .
Available Features
This section provides information about the features available on the
SoundPoint IP / SoundStation IP / VVX phones:
2-8
Overview
2-9
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
— Last Call Return—The phone allows call server-based last call return.
— Local / Centralized Conferencing—The phone can conference
together the local user with the remote parties of two independent
calls and can support centralized conferences for which external
resources are used such as a conference bridge. The advanced aspects
of conferencing are part of the Productivity Suite.
— Local Contact Directory—The phone maintains a local contact
directory that can be downloaded from the provisioning server and
edited locally. Any edits to the Contact Directory made on the phone
are saved to the provisioning server as a backup.
— Local Digit Map—The phone has a local digit map to automate the
setup phase of number-only calls.
— Message Waiting Indication—The phone will flash a message-waiting
indicator (MWI) LED when instant messages and voice messages are
waiting.
— Microphone Mute—When the microphone mute feature is activated,
visual feedback is provided.
— Missed Call Notification—The phone can display the number of calls
missed since the user last looked at the Missed Calls list.
— Soft Key Activated User Interface—The user interface makes
extensive use of intuitive, context-sensitive soft key menus.
— Speed Dial—The speed dial system allows calls to be placed quickly
from dedicated keys as well as from a speed dial menu.
— Time and Date Display—Time and date can be displayed in certain
operating modes such as when the phone is idle and during a call.
• Advanced Features
— Access URL in SIP Message—Ability for the SoundPoint IP phones to
be able to receive a URL inside a SIP message (for example, as a SIP
header extension in a SIP INVITE) and subsequently access that given
URL in the Microbrowser.
— SIP-B Automatic Call Distribution—Supports ACD agent available
and unavailable and allows ACD login and logout. Requires call
server support.
— Bridged Line Appearance—Calls and lines on multiple phones can be
logically related to each other. Requires call server support.
— Busy Lamp Field—Allows monitoring the hook status and remote
party information of users through the busy lamp field (BLF) LEDs
and displays on an attendant console phone. This feature may require
call server support.
— Configurable Feature Keys—Certain key functions can be changed
from the factory defaults.
2 - 10
Overview
2 - 11
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
• Audio Features
— Acoustic Echo Cancellation—Employs advanced acoustic echo
cancellation for hands-free operation.
— Audio Codecs—Supports a wide range of industry standard audio
codecs.
— Automatic Gain Control—Designed for hands-free operation, boosts
the transmit gain of the local user in certain circumstances.
— Background Noise Suppression—Designed primarily for hands-free
operation, reduces background noise to enhance communication in
noisy environments.
— Comfort Noise Fill—Designed to help provide a consistent noise level
to the remote user of a hands-free call.
— DTMF Event RTP Payload—Conforms to RFC 2833, which describes
a standard RTP-compatible technique for conveying DTMF dialing
and other telephony events over an RTP media stream.
2 - 12
Overview
• Security Features
— Local User and Administrator Privilege Levels—Several local settings
menus are protected with two privilege levels, user and
administrator, each with its own password.
— Configuration File Encryption—Confidential information stored in
configuration files must be protected (encrypted). The phone can
recognize encrypted files, which it downloads from the provisioning
server and it can encrypt files before uploading them to the
provisioning server.
— Custom Certificates—When trying to establish a connection to a
provisioning server for application provisioning, the phone trusts
certificates issued by widely recognized certificate authorities (CAs).
— Incoming Signaling Validation—Levels of security are provided for
validating incoming network signaling.
— Secure Real-Time Transport Protocol—Encrypting audio streams to
avoid interception and eavesdropping.
2 - 13
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
2 - 14
Overview
• Busy Lamp Field— The BLF feature has been enhanced as follows:
— To provide individual subscription-based BLF monitoring (without
requiring a centralized resource list to be maintained by the call
server.
— To allow the single button ‘remote pick-up’ feature to be implemented
using Directed Call Pick-Up using SIP signaling as well as the star
code method supported in SIP 3.1 .
• H.323 Protocol—Support for the H.323 protocol for the Polycom VVX 1500
phone.
Note When SoundPoint IP 32x/33x is used in this guide, it includes the SoundPoint IP
320, 321, 330, 331, and 335 phones.
2 - 15
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
2 - 16
3
Setting up Your System
3-1
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
The following table shows the manually entered networking parameters that
may be overridden by parameters obtained from a DHCP server, an alternate
DHCP server, or configuration file:
1 2 3 4
IP address 1 • - - •
subnet mask 1 • - - •
IP gateway 3 • - - •
3-2
Setting up Your System
Refer to DHCP • • - •
boot server Menu on page
address 3-8
151 • - - •
Note: This value
SIP server address is configurable.
DNS server IP 6 • - - •
address
alternate DNS 6 • - - •
server IP address
DNS domain 15 • - - •
Refer to DHCP Warning: Link Layer Discovery Protocol (LLDP) overrides Cisco
Menu on page Discovery Protocol (CDP). CDP overrides Local FLASH which
VLAN ID 3-8 overrides DHCP VLAN Discovery.
Note The configuration file value for SNTP server address and SNTP GMT offset can
be configured to override the DHCP value. Refer to
tcpIpApp.sntp.address.overrideDHCP in Time Synchronization <sntp/> on page
A-75.
The CDP Compatibility value can be obtained from a connected Ethernet switch if
the switch supports CDP.
In the case where you do not have control of your DHCP server or do not have
the ability to set the DHCP options, an alternate method of automatically
discovering the provisioning server address is required. Connecting to a
secondary DHCP server that responds to DHCP INFORM queries with a
requested provisioning server value is one possibility. For more information,
refer to http://www.ietf.org/rfc/rfc3361.txt?number=3361 and
http://www.ietf.org/rfc/rfc3925.txt?number=3925.
3-3
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Note A URL should contain forward slashes instead of back slashes and should not
contain spaces. Escape characters are not supported. If a user name and password
are not specified, the Server User and Server Password will be used (refer to
Server Menu on page 3-10).
Note There are two types of FTP methods—active and passive. The SIP application is
not compatible with active FTP. Secure provisioning was implemented in a previous
release.
3-4
Setting up Your System
Note Setting Option 66 to tftp://192.168.9.10 has the effect of forcing a TFTP download.
Using a TFTP URL (for example, tftp://provserver.polycom.com) has the same
effect.
Note Both digest and basic authentication are supported when using HTTP/S for the SIP
application. Only digest authentication is supported when using HTTP by the
BootROM. If the Server Type is configured as HTTPS, the BootROM will contact
the same address and apply the same username and password to authentication
challenges only the protocol used will be HTTP. No SSL negotiation will take place,
so servers that do not allow unsecured HTTP connections will not be able to
provision files.
For downloading the BootROM and application images to the phone, the
secure HTTPS protocol is not available. To guarantee software integrity, the
BootROM will only download cryptographically signed BootROM or
application images. For HTTPS, widely recognized certificate authorities are
trusted by the phone (refer to Trusted Certificate Authority List on page C-1)
and custom certificates can be added to the phone (refer to “Technical Bulletin
17877: Using Custom Certificates With SoundPoint IP, SoundStation IP, and É
Phones“ at
http://www.polycom.com/usa/en/support/voice/soundpoint_ip/VoIP_T
echnical_Bulletins_pub.html .
As of SIP 3.2, Mutual Transport Layer Security (TLS) authentication is
available. For more information, refer to Mutual TLS Authentication on page
4-97.
Note If you want to use digest authentication against the Microsoft Internet Information
Services server:
• Use Microsoft Internet Information Server 6.0 or later.
• Digest authentication needs the user name and password to be saved in
reversible encryption.
• The user account on the server must have administrative privileges.
• The wildcard must be set as MIME type; otherwise the phone will not download
*.cfg, *.ld and other required files. This is due to the fact that the Microsoft
Internet Information Server cannot recognize these extensions and will return a
“File not found” error. To configure wildcard for MIME type, refer to
http://support.microsoft.com/kb/326965 .
For more information, refer to
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/809
552a3-3473-48a7-9683-c6df0cdfda21.mspx?mfr=true .
3-5
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
• Main Menu
• DHCP Menu
• Server Menu
• Ethernet Menu
• Syslog Menu
Use the soft keys, the arrow keys, the Select and Delete keys to make changes.
Certain parameters are read-only due to the value of other parameters. For
example, if the DHCP Client parameter is enabled, the Phone IP Addr and
Subnet Mask parameters are dimmed or not visible since these are guaranteed
to be supplied by the DHCP server (mandatory DHCP parameters) and the
statically assigned IP address and subnet mask will never be used in this
configuration.
3-6
Setting up Your System
Main Menu
The following configuration parameters can be modified on the main setup
menu:
DHCP Client Enabled, Disabled If enabled, DHCP will be used to obtain the parameters
discussed in DHCP or Manual TCP/IP Setup on page
3-2.
SNTP Address dotted-decimal IP address Simple Network Time Protocol (SNTP) server from
OR which the phone will obtain the current time.
domain name string
GMT Offset -13 through +12 Offset of the local time zone from Greenwich Mean
Time (GMT) in half hour increments.
DNS Server dotted-decimal IP address Primary server to which the phone directs Domain
Name System (DNS) queries.
DNS Alternate Server dotted-decimal IP address Secondary server to which the phone directs Domain
Name System queries.
EM Power Enabled, Disabled This parameter is relevant if the phone gets Power over
Ethernet (PoE). If enabled, the phone will set power
requirements in CDP to 12W so that up to three
Expansion Modules (EM) can be powered. If disabled,
the phone will set power requirements in CDP to 5W
which means no Expansion Modules can be powered (it
will not work).
3-7
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Note A parameter value of “???” indicates that the parameter has not yet been set and
saved in the phone’s configuration. Any such parameter should have its value set
before continuing.
The EM Power parameter is only available on SoundPoint IP 650 and 670 phones.
Note To switch the text entry mode on the SoundPoint IP 32x/33x, press the #. You may
want to use URL or IP address modes when entering server addresses.
DHCP Menu
The DHCP menu is accessible only when the DHCP client is enabled. The
following DHCP configuration parameters can be modified on the DHCP
menu:
Possible
Name Values Description
Boot Server 0=Option 66 The phone will look for option number 66 (string type) in the
response received from the DHCP server. The DHCP server
should send address information in option 66 that matches one
of the formats described for Server Address in the next
section, Server Menu.
If the DHCP server sends nothing, the following scenarios are
possible:
• If a boot server value is stored in flash memory and the
value is not “0.0.0.0”, then the value stored in flash is used.
• Otherwise the phone sends out a DHCP INFORM query.
3-8
Setting up Your System
Possible
Name Values Description
Boot Server (continued) 1=Custom The phone will look for the option number specified by the Boot
Server Option parameter (below), and the type specified by
the Boot Server Option Type parameter (below) in the
response received from the DHCP server.
If the DHCP server sends nothing, the following scenarios are
possible:
• If a boot server value is stored in flash memory and the
value is not “0.0.0.0”, then the value stored in flash is used.
• Otherwise the phone sends out a DHCP INFORM query.
2=Static The phone will use the boot server configured through the
Server Menu. For more information, refer to the next section,
Server Menu.
3=Custom+Option The phone will first use the custom option if present or use
66 Option 66 if the custom option is not present.
If the DHCP server sends nothing, the following scenarios are
possible:
• If a boot server value is stored in flash memory and the
value is not “0.0.0.0”, then the value stored in flash is used.
• Otherwise the phone sends out a DHCP INFORM query.
Boot Server Option 128 through 254 When the boot server parameter is set to Custom, this
(Cannot be the parameter specifies the DHCP option number in which the
same as VLAN ID phone will look for its boot server.
Option)
Boot Server Option Type 0=IP Address, When the Boot Server parameter is set to Custom, this
1=String parameter specifies the type of the DHCP option in which the
phone will look for its boot server. The IP Address must specify
the boot server. The String must match one of the formats
described for Server Address in the next section, Server
Menu.
3-9
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Possible
Name Values Description
2=Custom Use the number specified in the VLAN ID Option field as the
DHCP private option value.
VLAN ID Option 128 through 254 The DHCP private option value (when VLAN Discovery is set
(Cannot be the to Custom).
same as Boot For more information, refer to Assigning a VLAN ID Using
Server Option) DHCP on page C-23.
(default is 129)
Server Menu
The following server configuration parameters can be modified on the Server
menu:
Server Type 0=FTP, 1=TFTP, 2=HTTP, The protocol that the phone will use to obtain
3=HTTPS, 4=FTPS, 5=Invalid configuration and phone application files from the
provisioning server. Refer to Supported Provisioning
Protocols on page 3-4.
Note: Active FTP is not supported for BootROM version
3.0 or later. Passive FTP is still supported.
Note: Only implicit FTPS is supported.
3 - 10
Setting up Your System
Server Address dotted-decimal IP address The provisioning server to use if the DHCP client is
OR disabled, the DHCP server does not send a boot server
domain name string option, or the Boot Server parameter is set to Static. The
OR phone can contact multiple IP addresses per DNS name.
URL These redundant provisioning servers must all use the
All addresses can be followed same protocol. If a URL is used it can include a user
by an optional directory and name and password. Refer to Supported Provisioning
optional file name. Protocols on page 3-4. A directory and the master
configuration file can be specified.
Note: ":", "@", or "/" can be used in the user name or
password these characters if they are correctly escaped
using the method specified in RFC 1738.
Server User any string The user name used when the phone logs into the server
(if required) for the selected Server Type.
Note: If the Server Address is a URL with a user name,
this will be ignored.
Server Password any string The password used when the phone logs in to the server
if required for the selected Server Type.
Note: If the Server Address is a URL with user name and
password, this will be ignored.
File Transmit Tries 1 to 10 The number of attempts to transfer a file. (An attempt is
Default 3 defined as trying to download the file from all IP
addresses that map to a particular domain name.)
Retry Wait 0 to 300 The minimum amount of time that must elapse before
Default 1 retrying a file transfer, in seconds. The time is measured
from the start of a transfer attempt which is defined as the
set of upload/download transactions made with the IP
addresses that map to a given provisioning server's DNS
host name. If the set of transactions in an attempt is equal
to or greater than the Retry Wait value, then there will be
no further delay before the next attempt is started.
For more information, refer to Deploying Phones From the
Provisioning Server on page 3-17.
Tag SN to UA Disabled, Enabled If enabled, the phone’s serial number (MAC address) is
included in the User-Agent header of the Microbrowser.
The default value is Disabled.
Note The Server User and Server Password parameters should be changed from the
default values. Note that for insecure protocols the user chosen should have very
few privileges on the server.
3 - 11
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Ethernet Menu
The following Ethernet configuration parameters can be modified on the
Ethernet menu:
LLDP Enabled, Disabled If enabled, the phone will use the LLDP protocol to
communicate with the network switch for certain network
parameters. Most often this will be used to set the VLAN
that the phone should use for voice traffic. It also reports
power management to the switch. The default value is
Enabled.
If the switch does not support it, VLAN Discovery is used.
Refer to DHCP Menu on page 3-8.
There are four ways to get VLAN on the phone and they
can all be turned on, but the VLAN used is chosen by
priority of each method. The priority is: 1. LLDP; 2. CDP;
3. DVD (VLAN Via DHCP); 4. Static (VLAN ID entered in
config menu).
For more information, refer to LLDP and Supported TLVs
on page C-30.
CDP Compatibility Enabled, Disabled If enabled, the phone will use CDP compatible signaling to
communicate with the network switch for certain network
parameters. Most often this will be used to set the VLAN
that the phone should use for Voice Traffic, and for the
phone to communicate its PoE power requirements to the
switch. The default value is Enabled.
VLAN ID Null, 0 through 4094 Phone’s 802.1Q VLAN identifier. The default value is Null.
Note: Null = no VLAN tagging
VLAN Filtering Enabled, Disabled Filter received Ethernet packets so that the TCP/IP stack
does not process bad data or too much data.
Enable/disable the VLAN filtering state.
The default value is Disabled.
3 - 12
Setting up Your System
Storm Filtering Enabled, Disabled Filter received Ethernet packets so that the TCP/IP stack
does not process bad data or too much data.
Enable/disable the DoS storm prevention state.
The default value is Enabled.
LAN Port Mode 0 = Auto The network speed over the Ethernet.
1 = 10HD The default value is Auto.
2 = 10FD
HD means half duplex and FD means full duplex.
3 = 100HD
4 = 100FD Note: Polycom recommends that you do not change this
5 = 1000FD setting.
Note The LAN Port Mode applies to all phones supported by SIP 3.0 . The PC Port Mode
parameters are only available on phones with a second Ethernet port.
Only the SoundPoint IP 560 and 670 and Polycom VVX 1500 phones supports the
LAN Port Mode and PC Port Mode setting of 1000FD.The 1000BT LAN Clock and
1000BT PC Clock parameters are only available on SoundPoint IP 560 and 670
phones
Syslog Menu
Syslog is a standard for forwarding log messages in an IP network. The term
“syslog” is often used for both the actual syslog protocol, as well as the
application or library sending syslog messages.
The syslog protocol is a very simplistic protocol: the syslog sender sends a
small textual message (less than 1024 bytes) to the syslog receiver. The receiver
is commonly called “syslogd”, “syslog daemon” or “syslog server”. Syslog
messages can be sent through UDP, TCP, or TLS. The data is sent in cleartext.
Syslog is supported by a wide variety of devices and receivers. Because of this,
syslog can be used to integrate log data from many different types of systems
into a central repository.
The syslog protocol is defined in RFC 3164. For more information on syslog,
go to http://www.ietf.org/rfc/rfc3164.txt?number=3164 .
3 - 13
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Server Address dotted-decimal IP address The syslog server IP address or host name.
OR The default value is NULL.
domain name string
Server Type None=0, The protocol that the phone will use to write to the syslog
UDP=1, server.
TCP=2, If set to “None”, transmission is turned off, but the server
TLS=3 address is preserved.
Render Level 0 to 6 Specifies the lowest class of event that will be rendered to
syslog. It is based on log.render.level and can be a
lower value.
Refer to Basic Logging <level/><change/> and <render/>
on page A-106.
Note: Use left and right arrow keys to change values.
Prepend MAC Enabled, Disabled If enabled, the phone’s MAC address is prepended to the
Address log message sent to the syslog server.
3 - 14
Setting up Your System
Note Be aware of how logs, overrides and directories are uploaded to servers that map
to multiple IP addresses. The server that these files are uploaded to may change
over time.
If you want to use redundancy for uploads, synchronize the files between servers in
the background.
However, you may want to disable the redundancy for uploads by specifying
specific IP addresses instead of URLs for logs, overrides, and directory in the
<MAC-address>.cfg .
Note Use this procedure as a recommendation if this is your first provisioning server
setup.
Note If the provisioning protocol requires an account name and password, the server
account name and password must match those configured in the phones. Defaults
are: provisioning protocol: FTP, name: PlcmSpIp, password: PlcmSpIp.
Note Typically all phones are configured with the same server account, but the server
account provides a means of conveniently partitioning the configuration. Give each
account an unique home directory on the server and change the configuration on
an account-by-account basis.
3 - 15
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
3. Copy all files from the distribution zip file to the phone home directory.
Maintain the same folder hierarchy.
There are two distribution zip files. The combined image file contains:
— sip.ld
— sip.cfg
— phone1.cfg
— 000000000000.cfg
— 000000000000-directory~.xml
— SoundPointIP-dictionary.xml (one of each supported language)
— SoundPointIPWelcome.wav
The split image file contains individual sip.ld files for each model as well
as the configuration files and dictionary files.
Refer to the latest Release Notes for a detailed description of each file in the
distribution and further information on determining which distribution to
use.
Polycom recommends allowing file uploads to the provisioning server where the
security environment permits. This allows event log files to be uploaded and
changes made by the phone user to the configuration (through the web server and
local user interface) and changes made to the directory to be backed up. This
greatly eases our ability to provide customer support in diagnosing issues that may
occur with the phone operation.
3 - 16
Setting up Your System
Provisioning Phones
The default configuration files will work without any changes; however, if you
change any configuration file, then the others will have to adjusted
accordingly.
For more information on why to create another configuration file, refer to the
“Configuration File Management on SoundPoint IP, SoundStation IP, and
Polycom VVX 1500 Phones” white paper at
http://www.polycom.com/global/documents/support/technical/products
/voice/white_paper_configuration_file_management_on_soundpoint_ip_ph
ones.pdf .
For more information on phone configuration and provisioning, refer to the
appropriate Technical Bulletins and Quick Tips at
http://www.polycom.com/support/voice/soundpoint_ip/VoIP_Technical
_Bulletins_pub.html .
For more information on encrypting configuration files, refer to Encrypting
Configuration Files on page C-4.
Note Throughout this guide, the terms Ethernet address and MAC address are used
interchangeable.
Do not use [MACaddress]-phone.cfg as the per-phone filename. This filename is
used by the phone itself to store user preferences (overrides).
3 - 17
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
3 - 18
Setting up Your System
Note At this point, the phone sends a DHCP Discover packet to the DHCP server. This is
found in the Bootstrap Protocol/option "Vendor Class Identifier" section of the
packet and includes the phone’s part number and the BootROM version.
For example, a SoundPoint IP 650 might send the following information:
5EL@
DC?5cSc52*46*(9N7*<u6=pPolycomSoundPointIP-SPIP_6502345-12600-001,1B
R/4.0.0.0155/23-May-07 13:35BR/4.0.0.0155/23-May-07 13:35
For more information, refer to Parsing Vendor ID Information on page C-24.
3 - 19
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Power Adapter
Multi-Interface
Module
5
12-foot
Ethernet Cable
Interconnect Cable
25-foot
Network Cable 4
3 - 20
Setting up Your System
• If the secondary is not configured for DHCP, use the secondary’s static
provisioning server if it exists.
• If the secondary’s static provisioning server does not exists, use the
primary’s provisioning server (ignoring the source).
For more information on daisy-chaining and setting up the SoundStation IP
7000 conference phone, refer to the Setup Guide for the Polycom SoundStation IP
7000 Phone, which is available at
http://www.polycom.com/voicedocumentation/.
3 - 21
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Warning The SoundPoint IP 300 and 500 phones will be supported on the latest
maintenance patch release of the SIP 2.1 software stream—currently SIP 2.1.4.
Any critical issues that affect SoundPoint IP 300 and 500 phones will be addressed
by a maintenance patch on this stream until the End of Life date for these products.
Phones should be upgraded to BootROM 4.0.0 for these changes to be effective.
The SoundPoint IP 301, 501, 600, and 601 and the SoundStation IP 4000 phones
will be supported on the latest maintenance patch release of the SIP 3.1 software
stream—currently SIP 3.1.3 . Any critical issues that affect SoundPoint IP 300 and
500 phones will be addressed by a maintenance patch on this stream until the End
of Life date for these products. Phones should be upgraded to BootROM 4.0.0 or
later for these changes to be effective.
Warning If you need to upgrade any Polycom VVX 1500 phones running SIP 3.1.3 or earlier
to SIP 3.2.2, you must perform additional steps before rebooting the phone to
download the new SIP software. Refer to “Technical Bulletin 53522: Upgrading the
Polycom VVX 1500 Phone to SIP 3.2.2” at
http://www.polycom.com/usa/en/support/voice/soundpoint_ip/VoIP_Technical_Bulle
tins_pub.html .
To automatically update:
1. Back up old application and configuration files.
The old configuration can be easily restored by reverting to the backup
files.
2. Customize new configuration files or apply new or changed parameters
to the old configuration files.
Differences between old and new versions of configuration files are
explained in the Release Notes that accompany the software. Both
mandatory and optional changes may present. Changes to site-wide
configuration files such as sip.cfg can be done manually, but a scripting
tool is useful to change per-phone configuration files.
Warning The configuration files listed in CONFIG_FILES attribute of the master configuration
file must be updated when the software is updated. Any new configuration files
must be added to the CONFIG_FILES attribute in the appropriate order.
Mandatory changes must be made or the software may not behave as expected.
For more information, refer to the “Configuration File Management on SoundPoint
IP, SoundStation IP, and Polycom VVX 1500 Phones” white paper at
http://www.polycom.com/global/documents/support/technical/products/voice/white_
paper_configuration_file_management_on_soundpoint_ip_phones.pdf .
3. Save the new configuration files and images (such as sip.ld) on the
provisioning server.
3 - 22
Setting up Your System
Supporting SoundPoint IP 300, 301, 500, 501, 600 and 601 and
SoundStation IP 4000 Phones
With enhancements available since BootROM 4.0.0 and SIP 2.1.2, you can
modify the 000000000000.cfg or <MACaddress>.cfg configuration file to
direct phones to load the software image and configuration files based on the
phone model number. Refer to Master Configuration Files on page A-2.
The SIP 3.2.0 or later software distributions contain only the new distribution
files for the new release. You must rename the sip.ld, sip.cfg, and phone1.cfg
from a previous 2.1.x distribution that is compatible with SoundPoint IP 300
and 500 phones or a previous 3.1.y distribution that is compatible with
SoundPoint IP 301, 501, 600, and 601 SoundStation IP 4000 phones.
The following procedure must be used for upgrading to SIP 3.2.0 or later for
installations that have SoundPoint IP 300, 301, 500, 501, 600, 601 and
SoundStation IP 4000 phones deployed. It is also recommended that this same
approach be followed even if these phones are not part of the deployment as
it will simplify management of phone systems with future software releases.
3 - 23
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
2. Copy sip.ld, sip.cfg and phone1.cfg from the SIP 3.2.0 or later release
distribution onto the provisioning server.
These are the relevant files for all phones except the SoundPoint IP 300,
301, 500, 501, 600, 601 and SoundStation IP 4000 phones.
3. Rename sip.ld, sip.cfg, and phone1.cfg from the previous distribution to
sip_21x.ld, sip_21x.cfg, and phone1_21x.cfg respectively on the
provisioning server.
These are the relevant files for supporting the SoundPoint IP 300 and 500
phones.
4. Rename sip.ld, sip.cfg, and phone1.cfg from the previous distribution to
sip_31y.ld, sip_31y.cfg, and phone1_31y.cfg respectively on the
provisioning server.
These are the relevant files for supporting the SoundPoint IP 301, 501, 600,
601 and SoundStation IP 4000 phones.
5. Modify the 000000000000.cfg file, if required, to match your configuration
file structure.
For example:
<APPLICATION
APP_FILE_PATH="sip.ld"
APP_FILE_PATH_SPIP500="sip_214.ld"
APP_FILE_PATH_SPIP300="sip_214.ld"
APP_FILE_PATH_SPIP601="sip_313.ld"
APP_FILE_PATH_SPIP600="sip_313.ld"
APP_FILE_PATH_SPIP501="sip_313.ld"
APP_FILE_PATH_SPIP301="sip_313.ld"
APP_FILE_PATH_SSIP4000="sip_313.ld"
CONFIG_FILES="[PHONE_MAC_ADDRESS]-user.cfg, phone1.cfg, sip.cfg"
CONFIG_FILES_SPIP500="[PHONE_MAC_ADDRESS]-user.cfg,
phone1_214.cfg, sip_214.cfg"
CONFIG_FILES_SPIP300="[PHONE_MAC_ADDRESS]-user.cfg,
phone1_214.cfg, sip_214.cfg"
CONFIG_FILES_SPIP601="[PHONE_MAC_ADDRESS]-user.cfg,
phone1_313.cfg, sip_313.cfg"
CONFIG_FILES_SPIP600="[PHONE_MAC_ADDRESS]-user.cfg,
phone1_313.cfg, sip_313.cfg"
CONFIG_FILES_SPIP501="[PHONE_MAC_ADDRESS]-user.cfg,
phone1_313.cfg, sip_313.cfg"
CONFIG_FILES_SPIP301="[PHONE_MAC_ADDRESS]-user.cfg,
phone1_313.cfg, sip_313.cfg"
CONFIG_FILES_SSIP4000="[PHONE_MAC_ADDRESS]-user.cfg,
phone1_313.cfg, sip_313.cfg"
MISC_FILES=""
LOG_FILE_DIRECTORY=""
OVERRIDES_DIRECTORY=""
CONTACTS_DIRECTORY=""
/>
3 - 24
Setting up Your System
6. Remove any <MACaddress>.cfg files that may have been used with
earlier releases from the provisioning server.
3 - 25
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
3 - 26
4
Configuring Your System
• Call Log
• Call Timer
• Call Waiting
4-1
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
• Distinctive Ringing
• Do Not Disturb
• Microphone Mute
• Speed Dial
• Ethernet Switch
• Call Hold
• Call Transfer
• Call Forward
• Call Park/Retrieve
4-2
Configuring Your System
Call Log
The phone maintains a call log. The log contains call information such as
remote party identification, time and date, and call duration. It can be used to
redial previous outgoing calls, return incoming calls, and save contact
information from call log entries to the contact directory.
The call log is stored in volatile memory and is maintained automatically by
the phone in three separate lists: Missed Calls, Received Calls and Placed
Calls. The call lists can be cleared manually by the user and will be erased
when the phone is restarted.
Note On some SoundPoint IP platforms, missed calls and received calls appear in one
Central Configuration File: Enable or disable all call lists or individual call lists.
(provisioning sip.cfg • For more information, refer to Feature <feature/> on page A-116.
server)
Call Timer
A call timer is provided on the display. A separate call timer is maintained for
each distinct call in progress. The call duration appears in hours, minutes, and
seconds.
There are no related configuration changes.
Call Waiting
When an incoming call arrives while the user is active on another call, the
incoming call is presented to the user visually on the LCD display. A
configurable sound effect such as the familiar call-waiting beep will be mixed
with the active call audio as well.
Configuration changes can performed centrally at the provisioning server:
Central Configuration File: Specify the ring tone heard on an incoming call when another call is
(provisioning phone1.cfg active.
server) • For more information, refer to Call Waiting <callWaiting/> on page
A-142.
Disable call waiting.
• For more information, refer to Registration <reg/> on page A-134.
4-3
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Note The phone does not match the number of the placed call to any entries in the Local
Contact Directory or Corporate Directory.
Note The phone does not match the received number to any entries in the Corporate
Directory.
Central Configuration File: Specify whether or not to use directory name substitution.
(provisioning sip.cfg • For more information, refer to User Preferences <up/> on page
server) A-31.
Local Web Server Specify whether or not to use directory name substitution.
(if enabled) Navigate to: http://<phoneIPAddress>/coreConf.htm#us
Changes are saved to local flash and backed up to <Ethernet
address>-phone.cfg on the provisioning server. Changes will
permanently override global settings unless deleted through the
Reset Local Config menu selection.
4-4
Configuring Your System
Note On some SoundPoint IP platforms, missed calls and received calls appear in one
list.
4-5
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Note L16/32000 and L16/48000 are only supported on SoundPoint IP 7000 phones.
Note The alternate sampled audio sound effect files must be present on the provisioning
server or the Internet for downloading at boot time.
Central Configuration File: Specify patterns used for sound effects and the individual tones or
(provisioning sip.cfg sampled audio files used within them.
server) • For more information, refer to Sampled Audio for Sound Effects
<saf/> on page A-37 or Sound Effects <se/> on page A-38.
Local Web Server Specify sampled audio wave files to replace the built-in defaults.
(if enabled) Navigate to http://<phoneIPAddress>/coreConf.htm#sa
Changes are saved to local flash and backed up to <Ethernet
address>-phone.cfg on the provisioning server. Changes will
permanently override global settings unless deleted through the
Reset Local Config menu selection.
4-6
Configuring Your System
Central Configuration file: Specify per-registration whether the MWI LED is enabled or disabled.
(provisioning phone1.cfg • For more information, refer to Message Waiting Indicator <mwi/>
server) on page A-149.
Specify whether MWI notification is displayed for registration x
(pre-SIP 2.1 behavior is enabled).
• For more information, refer to User Preferences <up/> on page
A-31.
Distinctive Ringing
There are three options for distinctive ringing:
1. The user can select the ring type for each line by pressing the Menu key,
and then selecting Settings > Basic > Ring Type. This option has the
third (lowest) priority.
2. The ring type for specific callers can be assigned in the contact directory.
For more information, refer to Distinctive Incoming Call Treatment, the
previous section. This option is second in priority.
3. The voIpProt.SIP.alertInfo.x.value and
voIpProt.SIP.alertInfo.x.class fields can be used to map calls to
specific ring types. This option requires server support and is first
(highest) in priority.
4-7
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Central Configuration file: Specify the mapping of Alert-Info strings to ring types.
(provisioning sip.cfg • For more information, refer to Alert Information <alertInfo/> on
server) page A-19.
Configuration file: Specify the ring type to be used for each line.
phone1.cfg • For more information, refer to Registration <reg/> on page A-134.
XML File: <Ethernet This file can be created manually using an XML editor.
address>-directory. • For more information, refer to Local Contact Directory on page
xml 4-10.
Local Local Phone User The user can edit the ring types selected for each line under the
Interface Settings menu. The user can also edit the directory contents.
Changes are saved to local flash and backed up to <Ethernet
address>-phone.cfg on the provisioning server. Changes will
permanently override global settings unless deleted through the
Reset Local Config menu selection and the <Ethernet
address>-phone.cfg is removed from the provisioning server.
Central Configuration file: Specify the mapping of Alert-Info strings to call waiting types.
(provisioning sip.cfg • For more information, refer to Alert Information <alertInfo/> on
server) page A-19.
Do Not Disturb
A Do Not Disturb (DND) feature is available to temporarily stop all incoming
call alerting. Calls can optionally be treated as though the phone is busy while
DND is enabled. DND can be configured as a per-registration feature.
Incoming calls received while DND is enabled are logged as missed. For more
information on forwarding calls while DND is enabled, refer to Call Forward
on page 4-22.
Server-based DND is active if the feature is enabled on both the phone and the
server and the phone is registered. The server-based DND feature is applicable
for all registrations on the phone (no per-registration mode) and it disables
local Call Forward and DND features unless configured otherwise.
4-8
Configuring Your System
Server-based DND will behave the same as per-SIP 2.1 per-registration feature
with the following exceptions:
• If server-based DND is enabled, but inactive, and the user presses the
DND key or selects the DND option on the Feature menu, the “Do Not
Disturb” message does not appear on the user’s phone (incoming call
alerting will continue).
Configuration changes can be performed centrally at the provisioning server
or locally:
Local Local Phone User Enable or disable DND using the Do Not Disturb key on the
Interface SoundPoint IP 550, 560, 650, and 670 and the Polycom VVX 1500 or
the “Do Not Disturb” option on the Features menu on the SoundPoint
IP 32x/33x, 430, and 450 and SoundStation IP 5000, 6000 and 7000.
Note: The LED on the Do Not Disturb key on the Polycom VVX
1500 is red when pressed or when server-based DND is enabled.
4-9
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Configuration file: Specify whether or not the electronic hookswitch is enabled and what
phone1.cfg type of headset is attached.
• For more information, refer to User Preferences <up/>on page
A-134.
Local Phone User Enable or disable persistent headset mode through the Settings
Interface menu (Settings > Basic > Preferences > Headset > Headset
Memory Mode).
Enable or disable hands-free speakerphone mode through the
Settings menu (Settings > Advanced > Admin Settings > Phone
Settings).
Changes are saved to local flash and backed up to <Ethernet
address>-phone.cfg on the provisioning server. Changes will
permanently override global settings unless deleted through the
Reset Local Config menu selection.
Note If a user makes a change to the local contact directory, there is a five second
timeout before it is uploaded to the provisioning server as
<mac-address>-directory.cfg.
If so configured, the first and last name fields of the local contact directory entries
which match incoming calls will be used for caller identification display and in the
call lists (instead of the name provided through network signaling).
4 - 10
Configuring Your System
Central Configuration file: Set whether the directory uses volatile storage on the phone.
(provisioning sip.cfg • For more information, refer to Local Directory <local/> on page
server) A-86.
Specify whether or not the local contact directory is read only.
• For more information, refer to Local Directory <local/> on page
A-86.
XML file: <Ethernet This file can be created manually using an XML editor.
address>-directory. For information on file format, refer to the next section, Local Contact
xml Directory File Format.
Local Local Phone User The user can edit the directory contents if configured in that way.
Interface Changes will be stored in the phone’s flash file system and backed up
to the provisioning server copy of <Ethernet
address>-directory.xml if this is configured. When the phone boots,
the provisioning server copy of the directory, if present, will overwrite
the local copy.
4 - 11
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
<dc/>
<ad>0</ad>
<ar>0</ar>
<bw>0</bw>
<bb>0</bb>
</item>
...
<item>
<ln>Smith</ln>
<fn>Bill</fn>
<ct>1003</ct>
<sd>3</sd>
<lb>Dr</lb>
<pt>SIP</pt>
<rt>3</rt>
<dc/>
<ad>0</ad>
<ar>0</ar>
<bw>0</bw>
<bb>0</bb>
</item>
</item_list>
</directory>
4 - 12
Configuring Your System
ar 0,1 auto-reject
If set to 1, automatically rejects callers that match the directory entry.
Note: If auto-divert is also enabled, it has precedence over
auto-reject.
4 - 13
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
the introduction of “R” to the digit map). It is also possible to direct the
protocol used to place a call (with the introduction of “S” and “H” to the digit
map).
For more information digit maps, refer to “Technical Bulletin 11572: Changes
to Local Digit Maps on SoundPoint IP / SoundStation IP / VVX Phones“ at
http://www.polycom.com/support/voice/soundpoint_ip/VoIP_Technical
_Bulletins_pub.html .
Note Digit maps do not apply to on-hook dialing. The parameter settings described in
Dial Plan <dialplan/> on page A-23 are ignored during on-hook dialing.
Central Configuration file: Specify impossible match behavior, trailing # behavior, digit map
(provisioning sip.cfg matching strings, and time out value.
server) • For more information, refer to Dial Plan <dialplan/> on page A-23.
Local Web Server Specify impossible match behavior, trailing # behavior, digit map
(if enabled) matching strings, and time out value.
Navigate to: http://<phoneIPAddress>/appConf.htm#ls
Changes are saved to local flash and backed up to <Ethernet
address>-phone.cfg on the provisioning server. Changes will
permanently override global settings unless deleted through the
Reset Local Config menu selection and the <Ethernet
address>-phone.cfg is removed from the provisioning server.
Microphone Mute
A microphone mute feature is provided. When activated, visual feedback is
provided. This is a local function and cannot be overridden by the network.
There are no related configuration changes.
4 - 14
Configuring Your System
Speed Dial
Entries in the local directory can be linked to the speed dial system. The speed
dial system allows calls to be placed quickly from dedicated keys as well as
from a speed dial menu.
For SoundPoint IP 32x/33x desktop phones and SoundStation IP 6000 and
7000 conference phones, the speed dial index range is 1 to 99. For all other
SoundPoint IP and Polycom VVX phones, the range is 1 to 9999.
If Presence watching is enabled for speed dial entries, their status will be
shown on the idle display (if the SIP server supports this feature). For more
information, refer to Presence on page 4-64.
Configuration changes can performed centrally at the provisioning server or
locally:
Local Local Phone User The next available Speed Dial Index is assigned to new directory
Interface entries. Key pad short cuts are available to facilitate assigning and
modifying the Speed Dial Index value for entries in the directory. The
Speed Dial Index field is used to link directory entries to speed dial
operations.
Changes will be stored in the phone’s flash file system and backed up
to the provisioning server copy of <Ethernet
address>-directory.xml if this is configured. When the phone boots,
the provisioning server copy of the directory, if present, will overwrite
the local copy.
4 - 15
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
of several different formats and can be turned off. The SoundPoint IP 32x/33x
and IP 4xx phones have a limited selection of date formats due to a smaller
display size.
Configuration changes can be performed centrally at the provisioning server
or locally:
Local Web Server Set the basic SNTP and daylight savings settings.
(if enabled) Navigate to: http://<phoneIPAddress>/coreConf.htm#ti
Changes are saved to local flash and backed up to <Ethernet
address>-phone.cfg on the provisioning server. Changes will
permanently override global settings unless deleted through the
Reset Local Config menu selection and the <Ethernet
address>-phone.cfg is removed from the provisioning server.
Local Phone User The basic SNTP settings can be made in the Network Configuration
Interface menu.
For more information, refer to DHCP or Manual TCP/IP Setup on
page 3-2.
The user can edit the time and date format and enable or disable the
time and date display under the Settings menu.
Changes are saved to local flash and backed up to <Ethernet
address>-phone.cfg on the provisioning server. They will permanently
override global settings unless deleted through the Reset Local
Config menu selection.
Note Currently customized animations are not supported on the Polycom VVX 1500.
4 - 16
Configuring Your System
Ethernet Switch
The SoundPoint IP phones (except the SoundPoint IP 32x) and the Polycom
VVX 1500 contain two Ethernet ports, labeled LAN and PC, and an embedded
Ethernet switch that runs at full line-rate. The SoundStation IP phones contain
only one Ethernet port, labeled LAN. The Ethernet switch allows a personal
computer and other Ethernet devices to connect to the office LAN by daisy
chaining through the phone, eliminating the need for a stand-alone hub. The
SoundPoint IP switch gives higher transmit priority to packets originating in
the phone. The phone can be powered through a local AC power adapter or
can be line-powered (power supplied through the signaling or idle pairs of the
LAN Ethernet cable). Line powering typically requires that the phone plugs
directly into a dedicated LAN jack. Devices that do not require LAN power
can then plug into the SoundPoint IP PC Ethernet port. To disable the PC
Ethernet port, refer to Disabling PC Ethernet Port on page C-27.
4 - 17
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Note When installing a background of your choice, care needs to be taken to ensure that
the background does not adversely affect the visibility of the text on the phone
display. As a general rule, backgrounds should be light in shading for better
usability.
• There are a number of default backgrounds, both solid color and pictures.
Both BMP and JPEG files are supported. You can also select the label color
for soft key and line key labels. Users can select which background and
label color appears on their phone.
You can modify the supported solid color and pictures backgrounds. For
example, you can add a gray solid color background or modify a picture
to one of your choice.
For Polycom VVX 1500 phones:
• You can select the pictures or designs displayed on the background. The
supported formats include JPEG, BMP, and PNG and the maximum size
is 800x480. A default picture is displayed when the phone starts up the
first time.
Users can select which background appears on their individual phones.
Users can also select a background from an image displayed by the digital
picture frame feature (refer to Digital Picture Frame on page 4-37).
Note Support for resolutions greater than 800x480 is inconsistent. Content may be
truncated or nor displayed. Progressive/multiscan JPEG images are not supported
at this time.
Local Local Phone User On the Polycom VVX 1500, the user can save one of the images as
Interface the background by selecting Save as Background on the touch
screen.
4 - 18
Configuring Your System
c For the solid backgrounds, set the name and RGB values. For example:
bg.hiRes.gray.pat.solid.3.name=”Gray”
bg.hiRes.gray.pat.solid.3.red=”128”
bg.hiRes.gray.pat.solid.3.green=”128”
bg.hiRes.gray.pat.solid.3.blue=”128”
The default size for images on a phone is 320 x 160. The default size for
images on an Expansion Module is 160 x 320. Use a photo editor on a
computer to adjust the image you want to display. (Edit the image so
the main subject is centered in the upper right corner of the display.)
Download the file to the provisioning server.
e Save the modified sip.cfg configuration file.
Central Configuration file: Specify which registrations have the feature and what contact to call
(provisioning phone1.cfg when going off hook.
server) • For more information, refer to Automatic Off-Hook Call Placement
<autoOffHook/> on page A-140.
Call Hold
The purpose of hold is to pause activity on one call so that the user may use
the phone for another task, such as to make or receive another call. Network
signaling is employed to request that the remote party stop sending media and
to inform them that they are being held. A configurable local hold reminder
feature can be used to remind the user that they have placed calls on hold. The
call hold reminder is always played through the speakerphone.
As of SIP 3.1, you can supply a Music on Hold URI if supported by the call
server. For more information, refer to draft RFC draft-worley-service-example.
4 - 19
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Central Configuration file: Specify whether RFC 2543 (c=0.0.0.0) or RFC 3264 (a=sendonly or
(provisioning sip.cfg a=inactive) outgoing hold signaling is used.
server) • For more information, refer to SIP <SIP/> on page A-11.
Specify local hold reminder options.
• For more information, refer to Hold, Local Reminder
<hold/><localReminder/> on page A-85.
Specify the Music on Hold URI.
• For more information, refer to Music on Hold <musicOnHold/> on
page A-21.
Local Web Server Specify whether or not to use RFC 2543 (c=0.0.0.0) outgoing hold
(if enabled) signaling. The alternative is RFC 3264 (a=sendonly or a=inactive).
Navigate to: http://<phoneIPAddress>/appConf.htm#ls
Changes are saved to local flash and backed up to <Ethernet
address>-phone.cfg on the provisioning server. Changes will
permanently override global settings unless deleted through the
Reset Local Config menu selection and the <Ethernet
address>-phone.cfg is removed from the provisioning server.
Local Phone User Use the Call Server Configuration menu to specify whether or not to
Interface use RFC 2543 (c=0.0.0.0) outgoing hold signaling. The alternative is
RFC 3264 (a=sendonly or a=inactive).
Call Transfer
Call transfer enables the user (party A) to move an existing call (party B) into
a new call between party B and another user (party C) selected by party A. The
phone offers three types of transfers:
4 - 20
Configuring Your System
Central Configuration file: Specify whether to allow a transfer during the proceeding state of a
(provisioning sip.cfg consultation call.
server) • For more information, refer to SIP <SIP/> on page A-11.
Specify whether a transfer is blind or not.
• For more information, refer to Call Handling Configuration <call/>
on page A-80.
Note Four-party conferencing requires a license key for activation. For more information,
refer to Manage Conferences on page 4-22.
If the initiator of a three-party local conference ends the call, the other members of
the call may still communicate. If the initiator of a four-party local conference ends
the call, the conference ends.
The phone also supports centralized conferences for which external resources
are used such as a conference bridge. This relies on network signaling.
Configuration changes can be performed centrally at the provisioning server:
Central Configuration file: Specify the conference hold behavior (all parties on hold or only host
(provisioning sip.cfg is on hold).
server) • For more information, refer to Call Handling Configuration <call/>
on page A-80.
Specify whether or not all parties hear sound effects while setting up a
conference.
• For more information, refer to Call Handling Configuration <call/>
on page A-80.
Specify which type of conference to establish and the address of the
centralized conference resource.
• For more information, refer to Conference Setup <conference/>
on page A-20.
4 - 21
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Manage Conferences
Note This feature is supported on the SoundPoint IP 450, 550, 560, 650, and 670
desktop phones, the SoundStation IP 7000 conference phone, and the Polycom
VVX business media phone.
This feature requires a license key for activation on all phones except the
SoundStation IP 7000 and the Polycom VVX 1500. Using this feature may require
purchase of a license key or activation by Polycom channels. For more information,
contact your Certified Polycom Reseller.
The individual parties within a conference can be managed. New parties can
be added and information about the conference participants can be viewed
(for example, names, phone numbers, send/receive status or media flow,
receive and transmit codecs, and hold status).
Configuration changes can be performed centrally at the provisioning server:
Call Forward
The phone provides a flexible call forwarding feature to forward calls to
another destination. Call forwarding can be applied in the following cases:
4 - 22
Configuring Your System
Note Server-based and local call forwarding are disabled if Shared Call Appearance or
Bridged Line Appearance is enabled.
The Diversion field with a SIP header is often used by the call server to inform
the phone of a call’s history. For example, when a phone has been set to enable
call forwarding, the Diversion header allows the receiving phone to indicate
who the call was from, and from which phone number it was forwarded. (For
more information, refer to Header Support on page B-4.) .
Configuration changes can be performed centrally at the provisioning server
or locally:
Local Phone User The user can set the call-forward-all setting from the idle display
Interface (enable/disable and specify the forward-to contact) as well as divert
callers while the call is alerting.
Changes are saved to local flash and backed up to <Ethernet
address>-phone.cfg on the provisioning server. Changes will
permanently override global settings unless deleted through the
Reset Local Config menu selection and the <Ethernet
address>-phone.cfg is removed from the provisioning server.
4 - 23
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Call Park/Retrieve
An active call can be parked, and the parked call can be retrieved by another
phone. This feature depends on support from a SIP server. With many SIP
servers, this feature is implemented using a particular star code sequence.
With some SIP servers, specific network signaling is used to implement this
feature.
Configuration changes can be performed centrally at the provisioning server:
4 - 24
Configuring Your System
• Instant Messaging
• Downloadable Fonts
• Corporate Directory
4 - 25
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
This section also provides information for making configuration changes for
the following advanced call server features:
• Multiple Registrations
• Server Redundancy
• Presence
Note Since there is no Redial key on the SoundPoint IP 32x/33x phone, the redial
function cannot be remapped.
• The phone keys that have removable key caps can be mapped to the
following:
— Any function that is implemented as a removable key cap on any of
the phones (Directories, Applications, Conference, Transfer, Redial,
Menu, Messages, Do Not Disturb, Call Lists)
— A speed-dial
— An enhanced feature key operation
— Null
4 - 26
Configuring Your System
• The phone keys without removable key caps cannot be remapped. These
include:
— Any keys on the dial pad
— Volume control
— Handsfree, Mute, Headset
— Hold
— Navigation Cluster
Configuration changes can be performed centrally at the provisioning server:
Central Configuration File: Set the key scrolling timeout, key functions, and sub-pointers for each
(provisioning sip.cfg key (usually not necessary).
server) • For more information, refer to Keys <key/> on page A-94.
For more information on the default feature key layouts, refer to Default
Feature Key Layouts on page C-13.
Central Configuration file: Specify the number of line keys to assign per registration.
(provisioning phone1.cfg • For more information, refer to Registration <reg/> on page A-134.
server)
Local Web Server Specify the number of line keys to assign per registration.
(if enabled) Navigate to http://<phoneIPAddress>/reg.htm
Changes are saved to local flash and backed up to <Ethernet
address>-phone.cfg on the provisioning server. Changes will
permanently override global settings unless deleted through the
Reset Local Config menu selection and the <Ethernet
address>-phone.cfg is removed from the provisioning server.
Local Phone User Specify the number of line keys to assign per registration using the
Interface Line Configuration menu. Either the Web Server or the provisioning
server configuration files or the local phone user interface should be
used to configure registrations, not a mixture of these options. When
the Line Configuration menu is used, it is assumed that all
registrations use the same server.
4 - 27
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Central Configuration file: Specify the default number of calls that can be active or on hold per
(provisioning sip.cfg line key.
server) • For more information, refer to Call Handling Configuration <call/>
on page A-80.
Configuration file: Specify per-registration the number of calls that can be active or on
phone1.cfg hold per line key assigned to that registration. This will override the
default value specified in sip.cfg.
• For more information, refer to Registration <reg/> on page A-134.
Local Web Server Specify the default number of calls that can be active or on hold per
(if enabled) line key and the number of calls per registration that can be active or
on hold per line key assigned to that registration.
Navigate to http://<phoneIPAddress>/appConf.htm#ls and
http://<phoneIPAddress>/reg.htm
Changes are saved to local flash and backed up to <Ethernet
address>-phone.cfg on the provisioning server. Changes will
permanently override global settings unless deleted through the
Reset Local Config menu selection and the <Ethernet
address>-phone.cfg is removed from the provisioning server.
Local Phone User Specify per-registration the number of calls that can be active or on
Interface hold per line key assigned to that registration using the Line
Configuration menu. Either the Web Server or the provisioning
server configuration files or the local phone user interface should be
used to configure registrations, not a mixture of these options. When
the Line Configuration menu is used, it is assumed that all
registrations use the same server.
Note Customizable fonts and indicators are not supported on the Polycom VVX 1500.
4 - 28
Configuring Your System
Central Configuration File: Specify fonts to overwrite existing ones or specify new fonts.
(provisioning sip.cfg • For more information, refer to Fonts <font/> on page A-91.
server)
Specify which bitmaps to use.
• For more information, refer to Bitmaps <bitmap/>on page A-100.
Specify how to create animations and LED indicator patterns.
• For more information, refer to Indicators <ind/> on page A-100.
Instant Messaging
The phone supports sending and receiving instant text messages. The user is
alerted to incoming messages visually and audibly. The user can view the
messages immediately or when it is convenient. For sending messages, the
user can either select a message from a preset list of short messages or an
alphanumeric text entry mode allows the typing of custom messages using the
dial pad. Message sending can be initiated by replying to an incoming
message or by initiating a new dialog. The destination for new dialog
messages can be entered manually or selected from the contact directory, the
preferred method.
Configuration changes can be performed centrally at the provisioning server:
4 - 29
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Note The multilingual feature relies on dictionary files resident on the provisioning server.
The dictionary files are downloaded from the provisioning server whenever the
language is changed or at boot time when a language other than the internal US
English language has been configured. If the dictionary files are inaccessible, the
language will revert to the internal language.
Note Currently, the multilingual feature is only available in the SIP application. The
BootROM application is available in English only.
Central Configuration file: Specify the boot-up language and the selection of language choices
(provisioning sip.cfg to be made available to the user.
server) • For more information, refer to Multilingual <ml/> on page A-28.
For instructions on adding new languages, refer to To add new
languages to those included with the distribution: on page A-29.
Local Local Phone User The user can select the preferred language under the Settings menu.
Interface The languages appears in the list in the language itself. For example,
German appears in the list as “Deutsch” and Swedish appears as
“Svenska”. For administrator convenience, the ISO representation of
each language is also included in the language selection menu.
Changes are saved to local flash and backed up to <Ethernet
address>-phone.cfg on the provisioning server. Changes will
permanently override global settings unless deleted through the
Reset Local Config menu selection and the <Ethernet
address>-phone.cfg is removed from the provisioning server.
Downloadable Fonts
New fonts can be loaded onto the phone. For guidelines on downloading
fonts, refer to Fonts <font/> on page A-91.
Note Downloadable fonts are not supported on the SoundStation IP 6000 and 7000 and
the Polycom VVX 1500.
4 - 30
Configuring Your System
Central Configuration file: Specify the basic tone frequencies, levels, and basic repetitive
(provisioning sip.cfg cadences.
server) • For more information, refer to Chord-Sets <chord/> on page A-36.
Specify downloaded sampled audio files for advanced call progress
tones.
• For more information, refer to Sampled Audio for Sound Effects
<saf/> on page A-37.
Specify patterns.
• For more information, refer to Patterns <pat/> on page A-39 and
Call Progress Patterns on page A-40.
The Polycom VVX 1500 phones running SIP 3.2.2 or later support a full
browser. This can be launched by pressing the App key or it can accessed
through the Menu key by selecting Applications.
Note If Browser uses over 30MB of memory and either the amount of free memory on the
phone is below 6MB or the real time is between 1am to 5am, then the browser will
restart. Once the browser has restarted, the last displayed web page is restored.
• An instance that does not support user input, but appears in a window on
the idle display
For more information, refer to the Web Application Developer’s Guide, which can
be found at http://www.polycom.com/voicedocumentation/.
4 - 31
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Central Configuration file: Specify the Application browser home page, a proxy to use, and size
(provisioning sip.cfg limits.
server) • For more information, refer to Microbrowser <mb/> on page
A-119.
Specify the telephone notification and state polling events to be
recorded and location of the push server.
• For more information, refer to Applications <apps/> on page
A-122.
Local Web Server Specify the Applications browser home page and proxy to use.
(if enabled) Navigate to http://<phoneIPAddress>/coreConf.htm#mb
Changes are saved to local flash and backed up to <Ethernet
address>-phone.cfg on the provisioning server. Changes will
permanently override global settings unless deleted through the
Reset Local Config menu selection and the <Ethernet
address>-phone.cfg is removed from the provisioning server.
4 - 32
Configuring Your System
Central Configuration file: Specify whether to filter incoming RTP packets by IP address,
(provisioning sip.cfg whether to require symmetric port usage or whether to jam the
server) destination port and specify the local RTP port range start.
• For more information, refer to RTP <rtp/> on page A-73.
Local Web Server Specify whether to filter incoming RTP packets by IP address,
(if enabled) whether to require symmetric port usage, whether to jam the
destination port and specify the local RTP port range start.
Navigate to: http://<phoneIPAddress>/netConf.htm#rt
Changes are saved to local flash and backed up to <Ethernet
address>-phone.cfg on the provisioning server. Changes will
permanently override global settings unless deleted through the
Reset Local Config menu selection.
Central Configuration file: Specify the external NAT IP address and the ports to be used for
(provisioning sip.cfg signaling and RTP traffic.
server) • For more information, refer to Network Address Translation
<nat/> on page A-150.
Local Web Server Specify the external NAT IP address and the ports to be used for
(if enabled) signaling and the RTP traffic.
Navigate to: http://<phoneIPAddress>/netConf.htm#na
Changes are saved to local flash and backed up to <Ethernet
address>-phone.cfg on the provisioning server. Changes will
permanently override global settings unless deleted through the
Reset Local Config menu selection and the <Ethernet
address>-phone.cfg is removed from the provisioning server.
4 - 33
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Corporate Directory
Note This feature requires a license key for activation except on the SoundStation IP
7000 and Polycom VVX 1500. Using this feature may require purchase of a license
key or activation by Polycom channels. For more information, contact your Certified
Polycom Reseller.
The SoundPoint IP, SoundStation IP, and Polycom VVX phones can be
configured to interface with a corporate directory server that supports the
Lightweight Directory Access Protocol (LDAP) version 3. Currently the
following LDAP servers are supported:
The corporate directory can be browsed or searched. Entries retrieved from the
LDAP server can be saved to the local contact directory on the phone. Phone
calls can be placed based on the phone number contained in the LDAP entry.
The corporate directory interface is read only, so that editing or deleting
existing directory entries as well as adding new directory entries from the
phone is not be possible. (There is no matching of first and last names in the
corporate directory to incoming calls, caller identification display, and in the
call lists.)
All attributes are considered to be Unicode text. Validity checking will be
performed when a call is placed or the entry is saved to the local contact
directory.
The corporate directory LDAP server status can be reviewed through the
Status menu (Status > CD Server Status).
For detailed examples for all currently supported LDAP directories, refer to
“Technical Bulletin 41137: Best Practices When Using Corporate Directory on
SoundPoint IP / SoundStation IP / VVX Phones“ at
http://www.polycom.com/support/voice/soundpoint_ip/VoIP_Technical
_Bulletins_pub.html .
4 - 34
Configuring Your System
Central Configuration file: Specify the location of the corporate directory’s LDAP server, the
(provisioning sip.cfg LDAP attributes, how often to refresh the local cache from the LDAP
server) server, and other miscellaneous parameters.
• For more information, refer to Corporate Directory <corp/> on
page A-87.
Local Local Phone User Enable or disable persistent viewing through the Settings menu
Interface (Settings > Basic > Preferences > Corporate Directory > View
Persistency).
Changes are saved to local flash and backed up to <Ethernet
address>-phone.cfg on the provisioning server. Changes will
permanently override global settings unless deleted through the
Reset Local Config menu selection.
The configuration order dictates how the attributes are displayed and sorted.
The first attribute is the primary sort index and the second attribute is the
secondary sort index. The other attributes are not used in sorting.
To limit the amount of data displayed in the corporate directory, filtering of
the entries can be configured for all attribute types. Filtering can be configured
to be retained if the phone reboots.
For more information on LDAP attributes, refer to RFC 4510 - Lightweight
Directory Access Protocol (LDAP): Technical Specification Road Map.
4 - 35
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Note This feature requires a license key for activation except for the Polycom VVX 1500.
Using this feature may require purchase of a license key or activation by Polycom
channels. For more information, contact your Certified Polycom Reseller.
The SoundPoint IP 650 and 670 and the Polycom VVX 1500 phones can be
configured to allow recording of audio calls on a supported USB device.
The filenames of the recorded .wav files will include a date/time stamp (for
example, 20Apr2007_190012.wav was created on April 20, 2007 at 19:00:12).
An indication of the recording time remaining—the space available of the
attached USB storage media—appears on the graphic display. The user can
browse through all recorded files through the menu shown on the graphic
display.
Note Notify your users that they may be required by federal, state, and/or local laws to
notify some or all called parties when they are recording.
Playback of recorded files can occur on the phone as well as on other devices,
such as a Windows® or Apple® based computer using an application like
Windows Media Player® or iTunes®.
The user controls which calls are recorded and played back.
For a list of supported USB devices, refer to “Technical Bulletin 38084:
Supported USB Devices for SoundPoint IP 650 and 670 and Polycom VVX 1500
Phones“ at
http://www.polycom.com/support/voice/soundpoint_ip/VoIP_Technical
_Bulletins_pub.html .
4 - 36
Configuring Your System
A slide show of multiple personal images stored on a USB flash drive can be
displayed on the Polycom VVX 1500 phone during the idle mode. The
supported formats include JPEG, BMP, and PNG. The maximum image size is
9999x9999. A maximum of 1000 images can be displayed and these must be
stored in a directory of the USB flash drive that you create.
Central Configuration file: Turn this feature on or off and configure how it appears.
(provisioning sip.cfg • For more information, refer to Feature <feature/> on page A-116
server) • For more information, refer to User Preferences <up/> on page
A-155.
Note The digital picture frame can be accessed through the PicFrame:// URL.
4 - 37
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Note The Enhanced Feature Key feature from SIP 3.0 is compatible with Enhanced
Feature Key feature from SIP 3.0 . However, improvements have been made, and
Polycom recommends that existing configuration files be reviewed and updated.
Customers replacing legacy telephony PBX or key system would like to get
equivalent functionality from their new VoIP telephony system. The enhanced
feature key capability is designed to allow system administrators to program
the speed-dials and soft keys on their phones to interact with the phone user
to implement commonly used functions such as “Call Park” in an intuitive
fashion.
This capability applies to the SoundPoint IP 32x/33x, 430, 450, 550, 560, 650,
and 670 desktop phones and Polycom VVX 1500 business media phones. The
enhanced feature key functionality is implemented using Star Code sequences
and SIP messaging.
The enhanced feature key macro language was designed to follow current
configuration file standards and to be extensible. It is described in more detail
in Enhanced Feature Key Definition Language.
The particular Star Code sequence and the associated prompts displayed on
the SoundPoint IP phone for the enhanced feature are defined by macros.
These macros are case sensitive.
The enhanced feature key capability can be used to provide a customized,
interactive user interface by mapping functions from speed-dial keys, soft
keys and re-mapped hard function keys.
This section provides detailed information on:
• Macro Definition
• Useful Tips
• Examples
For more examples including sample configuration files, refer to “Technical
Bulletin 42250: Using Enhanced Feature Keys and Configurable Soft Keys on
SoundPoint IP, SoundStation IP, and Polycom VVX 1500 Phones” at
http://www.polycom.com/usa/en/support/voice/soundpoint_ip/VoIP_T
echnical_Bulletins_pub.html .
4 - 38
Configuring Your System
• <efk/>
• <efklist/>
• <efkprompt/>
• <version/>
• Special Characters
<efk/>
This element indicates the start of enhanced feature key definition section. The
efk element has the following format:
<efklist/>
This element describes behavior of enhanced feature key.
The different blocks of the enhanced feature key definitions are uniquely
identified by number following efk.efklist prefix (for example,
efk.efklist.1.<suffix>).
Note In SIP 3.0, a maximum of 50 element groups is supported, however, the exact
number is dependent on available RAM and processing speed. The disabled
elements are included in the total count.
Name Interpretation
4 - 39
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Name Interpretation
label This field defines the text string that will be used as a
label on any user text entry screens during enhanced
feature key operation. The value can be any string
including the null string (in this case, no label appears).
If this parameter is omitted, the Null string is used.
Note: If you exceed the phone physical layout text
limits, the text will be shortened and "..." will be
appended.
<efkprompt/>
This element describes the behavior of the user prompts.
The different blocks are uniquely identified by number following
efk.efkprompt prefix (for example, efk.efkprompt.1.<suffix>).
Note In SIP 3.0, a maximum of four user prompts were supported. In SIP 3.0, a
maximum of ten user prompts are supported.
Name Interpretation
4 - 40
Configuring Your System
Name Interpretation
<version/>
This element contains the version of the enhanced feature key elements. The
version element has the following format:
<version efk.version=”2”/>
Note In SIP 3.0, “1” is the only supported version. In SIP 3.1 or later, “2” is the only
supported version.
4 - 41
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Special Characters
The following special characters are used to implement the enhanced feature
key functionality:
• ' or ASCII (0x27) — This character delimits the commands within the
macro.
• $ — This character delimits the parts of the macro string. This character
must exist in pairs, where the delimits the characters to be expanded.
Macro Definition
The action.string in the efklist element can be defined by either:
• Macro Action
• Expanded Macros
Macro Action
The action string is executed in the order it appears. User input is collected
before any action is taken.
The action string contains the following fields:
Name Interpretation
$L<label>$ This is the label for the entire operation. The value can
be any string including the null string (in this case, no
label appears). This label will be used if no other
operation label collection method worked (up to the
point where this field is introduced). Make this the first
entry in action string to be sure this label is used;
otherwise another label may be used and this one
ignored.
4 - 42
Configuring Your System
Name Interpretation
$S<speed dial index>$ The speed dial index. Only digits are valid.
The action is found in the contact field of the local
directory entry pointed to by the index.
• Nn is the number of digits or letters that the user can enter. The maximum
number is 32. The user needs to press the Enter soft key to complete data
entry.
4 - 43
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Note If the maximum number of characters is greater than 32 or less than one, macro
execution fails.
The macros provide a generic and easy to manage way to define the prompt to
be displayed to the user, the maximum number of characters that the user can
input, and action that the phone performs once all user input has been
collected. The macros are case sensitive.
If a macro attempts to use a prompt that is disabled, the macro execution fails.
A prompt is not required for every macro.
Expanded Macros
Expanded macros are prefixed with the “^” character and are inserted directly
into the local directory contact field. For more information, refer to Local
Contact Directory File Format on page 4-11.
Note The configuration file changes and the enhanced feature key definitions can be
included together in one configuration file.
A sample configuration for this feature—including the enhanced feature keys
definitions shown in the following section, Examples— may be included with the
SIP 3.1 release.
Create a new configuration file in the style of sip.cfg in order to make configuration
changes. For more information on why to create another configuration file,refer to
the “Configuration File Management on SoundPoint IP, SoundStation IP, and
Polycom VVX 1500 Phones” white paper at
http://www.polycom.com/global/documents/support/technical/products/voice/white_
paper_configuration_file_management_on_soundpoint_ip_phones.pdf .
XML file: <Ethernet This file holds the macro names which correspond to the mname fields
address>-directory. in the configuration file where the enhanced feature keys are defined.
xml Macro names must be embedded into the contact (cn) fields with the
“!” prefix. You can also add labels in the first name (fn) fields.
For information on file format, refer to Local Contact Directory File
Format on page 4-11.
4 - 44
Configuring Your System
Useful Tips
The following information should be noted:
• Activation of the enhanced feature key will fail if configured values are
invalid except where noted in previous sections.
• If two macros have the same name, the first one will be used and the
subsequent ones will be ignored.
• “'!” and “^” macro prefixes cannot be mixed in the same macro line.
• The sequence of characters accessed from speed dial keys must be prefixed
by either “!” or “^” so it will be processed as an enhanced feature key. All
macro references and action strings added to the local directory contact
field must be prefixed by either “!” or “^”.
• Macro names that appear in the local contact directory must follow the
format “!<macro name>” , where <macro name> must match an
<elklist> mname entry. The maximum macro length is 100 characters.
• Action strings that appear in the local contact directory must follow the
format “^<action string>”. Action strings can reference other macros or
speed dial indexes. Protection against recursive macro calls exists (the
enhanced feature keys fails once 50 macro substitutions is reached).
4 - 45
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Examples
Configuration File Changes
You must make the the following changes to the <feature/> parameter that
is defined in the sip.cfg configuration file:
<feature feature.18.name="enhanced-feature-keys"
feature.18.enabled="1"/>
...
<efklist
...
efk.efklist.2.mname="callpark"
efk.efklist.2.status="1"
efk.efklist.2.label="Call Park"
efk.efklist.2.use.idle="1"
efk.efklist.2.use.active="1"
efk.efklist.2.use.alerting="1"
efk.efklist.2.use.dialtone="1"
efk.efklist.2.use.proceeding="1"
efk.efklist.2.use.setup="1"
efk.efklist.2.type="invite"
efk.efklist.2.action.string="*68*$P1N10$"
...
/>
<efkprompt
efk.efkprompt.1.status="1"
4 - 46
Configuring Your System
<directory>
<item_list>
<item>
<fn>Call Park</fn>
<ct>!callpark</ct>
<sd>2</sd>
<rt>4</rt>
<ad>0</ad>
<ar>0</ar>
<bw>0</bw>
<bb>0</bb>
</item>
</item_list>
</directory>
Note To avoid users accidently deleting the definitions in the contact directory, make the
contact directory read only. For more information, refer to Local Directory <local/>
on page A-86.
4 - 47
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
b Enter the number where you want to park the active call, then select
the Enter soft key.
The Call Park * code (*68) is prepended to the number you entered and
the call is parked at that location by the call server. The active call is
put on hold during this operation.
4 - 48
Configuring Your System
• New Call
• End Call
• Split
• Join
• Forward
Note The Hold, Transfer, and Conference are grouped together to avoid usability
issues.
• Active—This state starts when a call is connected. It stops when the call
stops or changes to another state (like hold or dial tone).
• Setup—This state starts when the user starts keying in a phone number.
This state ends when the Proceeding state starts.
4 - 49
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Custom soft keys can be configured to precede the standard soft keys that are
still displayed. The order of the custom soft keys follows the configuration
order. The standard soft keys are shifted to the right and any empty spaces are
removed.
If the custom soft keys are configured to not precede the standard soft keys,
then the standard soft keys do not move. The order of the custom soft keys—
starting from the leftmost empty space—follows the empty spaces. Any extra
custom soft keys that are left after all empty spaces are used are appended at
the end.
Up to 10 soft keys can be configured. Any additional soft keys are ignored. If
more soft keys are defined than fit on the graphic display at one time, a More
soft key is displayed followed by the remainder of the soft keys that you have
defined.
This capability applies to the SoundPoint IP 32x, 33x, 430, 450, 550, 560, 650,
and 670, and Polycom VVX 1500 phones. This capability is linked to the
Enhanced Feature Key feature (refer to Enhanced Feature Keys on page 4-38.)
Configuration changes can be performed centrally at the boot server:
softkey.feature.newcall = 0
4 - 50
Configuring Your System
softkey.1.label = ChainAct
softkey.1.action = $S1$$Tinvite$
softkey.1.use.idle = 1
To map the Do Not Disturb Enhanced Feature Key sequence to a soft key:
1. Update sip.cfg as follows:
softkey.1.label = DND
softkey.1.action = $FDoNotDisturb$
softkey.1.use.idle = 1
To map a Send to Voice Mail Enhanced Feature Key sequence to a soft key:
Note The exact star code to transfer the active call to Voice Mail depends on your call
server.
softkey.2.label = ToVMail
softkey.2.action = ^*55$P1N10$$Tinvite$
softkey.2.use.alerting = 1
4 - 51
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
This feature applies during configured non-working hours and when the
phone is idle. Working hours are defined in the configuration files and users
can change the default values through the phone’s menu to accommodate
their individual schedules. The Polycom VVX 1500 phone enters
power-saving mode after it has been idle for a certain period of time and its
camera doesn’t detect motion. The phone’s ability to detect the users’ presence
is biased for easy detection during office hours and for difficult detection
during off hours.
Configuration changes can be performed centrally at the provisioning server:
Central Configuration file: Turn this feature on or off and configure how it works.
(provisioning sip.cfg • For more information, refer to LCD Power Saving
server) <powerSaving/> on page A-132.
Note Shared call appearances and bridged line appearances are two different signaling
methods of implementing a feature whereby more than one phone can share the
same line or registration. These implementations are dependent on the SIP server.
The methods are mutually exclusive and you should confirm with the call server
vendor which (if any) method is supported.
4 - 52
Configuring Your System
Central Configuration file: Specify whether diversion should be disabled on shared lines.
(provisioning sip.cfg • For more information, refer to Shared Calls <shared/> on page
server) A-84.
Specify line-seize subscription period.
• For more information, refer to Server <server/> on page A-8.
Specify standard or non-standard behavior for processing line-seize
subscription for mutual exclusion feature.
• For more information, refer to Special Events <specialEvent/> on
page A-20.
Local Phone User Specify per-registration line type (private or shared) using the Line
Interface Configuration menu. Either the Web Server or the provisioning
server configuration files or the local phone user interface should be
used to configure registrations, not a mixture of these options. When
the Line Configuration menu is used, it is assumed that all
registrations use the same server.
4 - 53
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Note Bridged line appearances and shared call appearances are two different signaling
methods of implementing a feature whereby more than one phone can share the
same line or registration. These implementations are dependent on the SIP server.
The methods are mutually exclusive and you should confirm with the call server
vendor which (if any) method is supported.
In the configuration files, bridged lines are configured by “shared line” parameters.
Central Configuration file: Specify whether diversion should be disabled on shared lines.
(provisioning sip.cfg • For more information, refer to Call Handling Configuration <call/>
server) on page A-80.
Configuration file: Specify per-registration line type (private or shared) and the shared
phone1.cfg line third party name. A shared line will subscribe to a server
providing call state information.
• For more information, refer to Registration <reg/> on page A-134.
Specify per-registration whether diversion should be disabled on
shared lines.
• For more information, refer to Diversion <divert/> on page A-142.
Local Web Server Specify per-registration line type (private or shared) and third party
(if enabled) name, and whether diversion should be disabled on shared lines.
Navigate to http://<phoneIPAddress>/reg.htm
Changes are saved to local flash and backed up to <Ethernet
address>-phone.cfg on the provisioning server. Changes will
permanently override global settings unless deleted through the
Reset Local Config menu selection and the <Ethernet
address>-phone.cfg is removed from the provisioning server.
Local Phone User Specify per-registration line type (private or shared) and the shared
Interface line third party name using the Line Configuration menu. Either the
Web Server or the provisioning server configuration files or the local
phone user interface should be used to configure registrations, not a
mixture of these options. When the Line Configuration menu is used,
it is assumed that all registrations use the same server.
4 - 54
Configuring Your System
Note This feature is available only on SoundPoint IP 430, 450, 550, 560, 600, 601, 650,
and 670 phones. Other SoundPoint IP phone models may be monitored, but cannot
be configured to monitor other phones.
Some aspects of this feature are dependent on the SIP server signaling. You
should consult your SIP server partner or Polycom Channel partner for information
as needed.
The Busy Lamp Field (BLF) feature enhances support for a phone-based
attendant console. It allows monitoring the hook status and remote party
information of users through the busy lamp fields and displays on an
attendant console phone.
In the SIP 3.1 release, the BLF feature was updated for the following:
Note The SIP 3.2 update to the BLF feature is not supported on the SoundPoint IP 430.
Polycom recommends that the BLF not be used in conjunction with the Microsoft
Live Communications Server 2005 feature. For more information, refer to Microsoft
Live Communications Server 2005 Integration on page 4-64.
Note Use this feature with TCPpreferred transport (refer to Server <server/> on page
A-8). You can also use UDP transport on SoundPoint IP 650 and 670 phones.
4 - 55
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Central Configuration file: Specify the list SIP URI and index of the registration which will be
(provisioning phone1.cfg used to send a SUBSCRIBE to the list SIP URI specified in
server) attendant.uri.
• For more information, refer to Attendant <attendant/> on page
A-151.
Specify the list of monitored resources.
• For more information, refer to Resource List <resourceList/> on
page A-152 and Behaviors <behaviors/> on page A-153.
Central Configuration file: For one-touch voice mail access, enable the “one-touch voice mail”
(provisioning sip.cfg user preference.
server) • For more information, refer to User Preferences <up/> on page
A-31.
Configuration file: For one-touch voice mail access, bypass instant messages to remove
phone1.cfg the step of selecting between instant messages and voice mail after
pressing the Messages key on the SoundPoint IP 430, 450, 550,
560, 650, and 670 and the MSG key on the Polycom VVX 1500
(Instant messages are still accessible from the Main Menu).
On a per-registration basis, specify a subscribe contact for solicited
NOTIFY applications, a callback mode (self call-back or another
contact), and the contact to call when the user accesses voice mail.
• For more information, refer to Messaging <msg/> on page A-149.
4 - 56
Configuring Your System
Local Web Server For one-touch voice mail access, enable the “one-touch voice mail”
(if enabled) user preference and bypass instant messages to remove the step of
selecting between instant messages and voice mail after pressing the
Messages key on the SoundPoint IP 430, 450, 550, 560, 650, and
670 and the MSG key on the Polycom VVX 1500 (Instant messages
are still accessible from the Main Menu).
Navigate to http://<phoneIPAddress>/coreConf.htm#us
On a per-registration basis, specify a subscribe contact for solicited
NOTIFY applications, a callback mode (self call-back or another
contact) to call when the user accesses voice mail.
Navigate to http://<phoneIPAddress>/reg.htm
Changes are saved to local flash and backed up to <Ethernet
address>-phone.cfg on the provisioning server. Changes will
permanently override global settings unless deleted through the
Reset Local Config menu selection.
Multiple Registrations
The SoundPoint IP 32x/33x and 430 support a maximum of two registrations,
the SoundPoint IP 450 supports three registrations, the SoundPoint IP 550 and
560 support four, and the SoundPoint IP 650 and 670 and the Polycom VVX
1500 support 6. Up to three SoundPoint IP Expansion Modules can be added
to a single host SoundPoint IP 650 and 670 phone increasing the total number
of registrations to 34. The SoundStation IP 6000 and 7000 supports a single
registration.
Each registration can be mapped to one or more line keys (a line key can be
used for only one registration). The user can select which registration to use for
outgoing calls or which to use when initiating new instant message dialogs.
Configuration changes can be performed centrally at the provisioning server
or locally:
Central Configuration file: Specify the local SIP signaling port and an array of SIP servers to
(provisioning sip.cfg register to. For each server specify the registration period and the
server) signaling failure behavior.
• For more information, refer to Server <server/> on page A-8 and
Server <server/> on page A-8.
4 - 57
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Local Web Server Specify the local SIP signaling port and an array of SIP servers to
(if enabled) register to.
Navigate to http://<phoneIPAddress>/appConf.htm#se
For up to six registrations (depending on the phone model, in this
case the maximum is six even for the IP 650 and 670), specify a
display name, a SIP address, an optional display label, an
authentication user ID and password, the number of line keys to use,
and an optional array of registration servers. The authentication user
ID and password are optional and for security reasons can be omitted
from the configuration files. The local flash parameters will be used
instead. The optional array of servers will override the servers
specified in sip.cfg in non-Null. This will also override the servers on
the appConf.htm web page.
Navigate to http://<phoneIPAddress>/reg.htm
Changes are saved to local flash and backed up to <Ethernet
address>-phone.cfg on the provisioning server. Changes will
permanently override global settings unless deleted through the
Reset Local Config menu selection.
Local Local Phone User Use the Call Server Configuration and Line Configuration menu to
(continued) Interface specify the local SIP signaling port, a default SIP server to register to
and registration information for up to twelve registrations (depending
on the phone model). These configuration menus contains a sub-set
of all the parameters available in the configuration files.
Either the Web Server or the provisioning server configuration files or
the local phone user interface should be used to configure
registrations, not a mixture of these options. When the Line
Configuration menu is used, it is assumed that all registrations use
the same server.
Changes are saved to local flash and backed up to <Ethernet
address>-phone.cfg on the provisioning server. Changes will
permanently override global settings unless deleted through the
Reset Local Config menu selection.
For more information, refer to Server <server/> on page A-8, Server
<server/> on page A-8, and Registration <reg/> on page A-134.
Note For more information on SIP-B and supported features on SoundPoint IP,
SoundStation IP, and Polycom VVX phones, contact Polycom Product
Management.
The phone allows Automatic Call Distribution (ACD) login and logout. This
feature depends on support from a SIP server.
4 - 58
Configuring Your System
The phone also supports ACD agent availability. This feature depends on
support from a SIP server.
Configuration changes can be performed centrally at the provisioning server:
Note The Feature Synchronized ACD feature is distinct from the existing SIP-B
Automatic Call Distribution functionality, which was added in SIP 1.6 .
For details on how to configure SoundPoint IP, SoundStation IP, and VVX
phones for Feature Synchronized ACD, refer to “Technical Bulletin 34787:
Using Feature Synchronized Automatic Call Distribution with SoundPoint IP
and Polycom VVX 1500 Phones” at
http://www.polycom.com/support/voice/soundpoint_ip/VoIP_Technical
_Bulletins_pub.html .
4 - 59
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Configuration file: Set the registration to be used for Feature Synchronized ACD and the
phone1.cfg users sign-in state.
• For more information, refer to Automatic Call Distribution
<acd/>on page A-156.
Server Redundancy
Server redundancy is often required in VoIP deployments to ensure continuity
of phone service for events where the call server needs to be taken offline for
maintenance, the server fails, or the connection between the phone and the
server fails.
Two types of redundancy are possible:
Note Your SIP server provider should be consulted for recommended methods of
configuring phones and servers for fail-over configuration.
Warning Prior to SIP 2.1, the reg.x.server.y parameters (refer to Registration <reg/> on
page A-134) could be used for fail-over configuration. The older behavior is no
longer supported. Customers that are using the reg.x.server.y. configuration
parameters where y>=2 should take care to ensure that their current deployments
are not adversely affected. For example the phone will only support advanced SIP
features such as shared lines, missed calls, presence with the primary server (y=1).
4 - 60
Configuring Your System
For more information, refer to “Technical Bulletin 5844: SIP Server Fallback
Enhancements on SoundPoint IP Phones” at
http://www.polycom.com/support/voice/soundpoint_ip/VoIP_Technical
_Bulletins_pub.html .
Configuration changes can be performed centrally at the provisioning server:
Central Configuration file: Specify global primary and fallback server configuration parameters.
(provisioning sip.cfg • For more information, refer to Protocol <voIpProt/> on page A-7.
server)
Configuration file: Specify per registration primary and fallback server configuration
phone1.cfg parameters values that override those in sip.cfg.
• For more information, refer to Registration <reg/> on page A-134.
Note Failure to resolve a DNS name is treated as signaling failure that will cause a
failover.
4 - 61
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
• If TCP is used, then the signaling fails if the connection fails or the Send
fails.
• If UDP is used, then the signaling fails if ICMP is detected or if the signal
times out. If the signaling has been attempted through all servers in the list
and this is the last server, then the signaling fails after the complete UDP
timeout defined in RFC 3261. If it is not the last server in the list, the
maximum number of retries using the configurable retry timeout is used.
For more information, refer to Server <server/> on page A-8 and
Registration <reg/> on page A-134.
Warning If DNS is used to resolve the address for Servers, the DNS server is unavailable,
and the TTL for the DNS records has expired, the phone will attempt to contact the
DNS server to resolve the address of all servers in its list before initiating a call.
These attempts will timeout, but the timeout mechanism can cause long delays (for
example, two minutes) before the phone call proceeds “using the working server”.
To mitigate this issue, long TTLs should be used. It is strongly recommended that
an on-site DNS server is deployed as part of the redundancy solution.
Call Server 1B
Call Server 1A
Internet
DNS Server
`
PSTN
PSTN Gateway
`
Phone Configuration
The phones at the customer site are configured as follows:
• Server 1 (the primary server) will be configured with the address of the
service provider call server. The IP address of the server(s) to be used will
be provided by the DNS server. For example:
reg.1.server.1.address="voipserver.serviceprovider.com"
4 - 62
Configuring Your System
Note It is possible to configure the phone for more than two servers per registration, but
you need to exercise caution when doing this to ensure that the phone and network
load generated by registration refresh of multiple registrations do not become
excessive. This would be of particularly concern if a phone had multiple
registrations with multiple servers per registration and it is expected that some of
these servers will be unavailable.
Note If reg.x.server.y.register is set to 0, then phone will not register to that server.
However, the INVITE will fail over to that server if all higher priority servers are
down.
4 - 63
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Presence
The Presence feature allows the phone to monitor the status of other
users/devices and allows other users to monitor it. The status of monitored
users is displayed visually and is updated in real time in the Buddies display
screen or, for speed dial entries, on the phone’s idle display. Users can block
others from monitoring their phones and are notified when a change in
monitored status occurs. Phone status changes are broadcast automatically to
monitoring phones when the user engages in calls or invokes do-not-disturb.
The user can also manually specify a state to convey, overriding, and perhaps
masking, the automatic behavior.
Central XML file: <Ethernet The <bw>0</bw> (buddy watching) and <bb>0</bb> (buddy
(provisioning address>-directory. blocking) elements in the <Ethernet address>-directory.xml file
server) xml dictate the Presence aspects of directory entries.
• For more information, refer to Local Contact Directory on page
4-10.
Local Local Phone User The user can edit the directory contents. The Watch Buddy and
Interface Block Buddy fields control the buddy behavior of contacts.
Changes will be stored in the phone’s flash file system and backed up
to the provisioning server copy of <Ethernet
address>-directory.xml if this is configured. When the phone boots,
the provisioning server copy of the directory, if present, will overwrite
the local copy.
Note Any contacts added through the SoundPoint IP, SoundStation IP, and VVX phone’s
buddy list will appear as a contact in Microsoft Office Communicator and Windows
Messenger.
4 - 64
Configuring Your System
Polycom recommends that the BLF not be used in conjunction with the Microsoft
Live Communications Server 2005 feature. For more information, refer to Busy
Lamp Field on page 4-55.
Central Configuration file: Specify that support for Microsoft Live Communications Server 2005
(provisioning sip.cfg is enabled.
server) • For more information, refer to SIP <SIP/> on page A-11.
Specify the line/registration number used to send SUBSCRIBE for
presence.
• For more information, refer to Presence <pres/> on page A-91.
Turn the presence and messaging features on or off.
• For more information, refer to Feature <feature/> on page A-116.
Configuration file: Specify the number of line keys to assign per registration.
phone1.cfg • For more information, refer to Registration <reg/> on page A-134.
Specify the line/registration number which has roaming buddies
support enabled.
• For more information, refer to Roaming Buddies
<roaming_buddies/> on page A-154.
Specify the line/registration number which has roaming privacy
support enabled.
• For more information, refer to Roaming Privacy
<roaming_privacy/> on page A-154.
4 - 65
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Note The TLS protocol is not supported on SoundPoint IP 300 and 500 phones.
4 - 66
Configuring Your System
4 - 67
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
• User Interface
• Signaling Changes
4 - 68
Configuring Your System
User Interface
There are three user interface aspects to this feature:
4 - 69
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
• Passive Mode. Web content can also be retrieved when the user chooses
to do so. The fact that web content is available for viewing is shown
through the call appearance-based web content icon described in Web
Content Status Indication on page 4-69. The Select key can be used to fetch
the associated web content for the call that is in focus. If the web content
has expired, the icon will be removed and the Select key will perform no
function.
Passive mode is recommended for applications where the Microbrowser
is used for other applications. In the SIP 2.2 feature, interactive
microbrowser sessions will be interrupted by the arrival of active-mode
web content URLs, which may cause annoyance, although the Back
navigation function will work in this context.
Settings Menu
If enabled, a new SIP web content entry is added to the Setting > Basic >
Preferences menu to allow the user to change the current content retrieval
mode. Two options are provided: passive mode and active mode.
Signaling Changes
A new SIP header must be used to report web content associated with SIP
phone calls (the SSAWC header follow the BNF for the standard SIP header
Alert-Info):
4 - 70
Configuring Your System
The web content must be located with an absolute URI, which begins with the
scheme identifier. Currently only the HTTP scheme is supported.
So an example header might look like:
Access-URL: <http://server.polycom.com/content23456.xhtml>
Access-URL:
<http://server.polycom.com/content23456.xhtml>;expires=60
If the server wishes to invalidate a previous URL, it can send a new header
(through UPDATE) with expires=0. The expires parameter is ignored when
determining whether to spontaneously retrieve the web content unless
expires=0.
Access-URL:
<http://server.polycom.com/content23456.xhtml>;expires=60;mode
=passive
In this case, the phone will indicate in the call appearance user interface
that web content is available for a period of 60 seconds and will retrieve
the web content at the request of the user for a period of up to 60 seconds
but the phone will not spontaneously switch to the microbrowser
application and download the content.
4 - 71
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
• If the initial DNS query returns no results for the hostname or cannot be
contacted, then the values in the static cache are used for their configured
time interval.
• After the configured time interval has elapsed, a resolution attempt of the
hostname will again result in a query to the DNS.
• If a DNS query for a hostname that is in the static cache returns a result,
the values from the DNS are used and the statically cached values are
ignored.
When a phone is not configured with a DNS server, it will behave as follows
• An attempt to resolve a hostname that is within the static DNS cache will
always return the results from the static cache.
Support for negative DNS caching as described in RFC 2308 is also provided
to allow faster failover when prior DNS queries have returned no results from
the DNS server. For more information, go to
http://tools.ietf.org/html/rfc2308 .
Configuration changes can be performed centrally at the boot server:
Central Configuration file: Specify DNS NAPTR, SRV, and A records for use when the phone is
(boot server) sip.cfg not configured to use a DNS server.
• For more information, refer to DNS Cache <dns/> on page A-126.
Polycom recommends that you create another file with your organization’s
modifications. If you must change any Polycom templates, back them up first.
For more information, refer to the “Configuration File Management on SoundPoint
IP, SoundStation IP, and Polycom VVX 1500 Phones” white paper at
http://www.polycom.com/global/documents/support/technical/products/voice/white_
paper_configuration_file_management_on_soundpoint_ip_phones.pdf .
4 - 72
Configuring Your System
Example 1
This example shows how to configure static DNS cache using A records IP
addresses in SIP server address fields.
When the static DNS cache is not used, the sip.cfg configuration would look
as follows:
reg.1.address="1001"
reg.1.server.1.address="172.23.0.140"
reg.1.server.1.port="5075"
reg.1.server.1.transport="UDPOnly"
reg.1.server.2.address="172.23.0.150"
reg.1.server.2.port="5075"
reg.1.server.2.transport="UDPOnly"
When the static DNS cache is used, the sip.cfg configuration would look as
follows:
reg.1.address="1001"
reg.1.server.1.address="sipserver.example.com"
reg.1.server.1.port="5075"
reg.1.server.1.transport="UDPOnly"
reg.1.server.2.address=""
reg.1.server.2.port=""
reg.1.server.2.transport=""
dns.cache.A.1.name="sipserver.example.com"
dns.cache.A.1.ttl="3600"
dns.cache.A.1.address="172.23.0.140"
dns.cache.A.2.name="sipserver.example.com"
dns.cache.A.2.ttl="3600"
dns.cache.A.2.address="172.23.0.150"
Note Above addresses are presented to SIP application in order, for example,
dns.cache.A.1, dns.cache.A.2, and so on.
Example 2
This example shows how to configure static DNS cache where your DNS
provides A records for server.X.address but not SRV. In this case, the static
DNS cache on the phone provides SRV records. For more information, go to
http://tools.ietf.org/html/rfc3263 .
When the static DNS cache is not used, the sip.cfg configuration would look
as follows:
reg.1.address="1002@sipserver.example.com"
reg.1.server.1.address="primary.sipserver.example.com"
reg.1.server.1.port="5075"
reg.1.server.1.transport="UDPOnly"
reg.1.server.2.address="secondary.sipserver.example.com"
4 - 73
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
reg.1.server.2.port="5075"
reg.1.server.2.transport="UDPOnly"
When the static DNS cache is used, the sip.cfg configuration would look as
follows:
reg.1.address="1002"
reg.1.server.1.address="sipserver.example.com"
reg.1.server.1.port=""
reg.1.server.1.transport="UDPOnly"
reg.1.server.2.address=""
reg.1.server.2.port=""
reg.1.server.2.transport=""
dns.cache.SRV.1.name="_sip._udp.sipserver.example.com "
dns.cache.SRV.1.ttl= "3600"
dns.cache.SRV.1.priority="1"
dns.cache.SRV.1.weight="1"
dns.cache.SRV.1.port="5075"
dns.cache.SRV.1.target="primary.sipserver.example.com"
dns.cache.SRV.2.name="_sip._udp.sipserver.example.com "
dns.cache.SRV.2.ttl= "3600"
dns.cache.SRV.2.priority="2"
dns.cache.SRV.2.weight="1"
dns.cache.SRV.2.port="5075"
dns.cache.SRV.2.target="secondary.sipserver.example.com
Example 3
This example shows how to configure static DNS cache where your DNS
provides NAPTR and SRV records for server.X.address .
When the static DNS cache is not used, the sip.cfg configuration would look
as follows:
reg.1.address="1002@sipserver.example.com
reg.1.server.1.address="172.23.0.140"
reg.1.server.1.port="5075"
reg.1.server.1.transport="UDPOnly"
reg.1.server.2.address="172.23.0.150"
reg.1.server.2.port="5075"
reg.1.server.2.transport="UDPOnly"
When the static DNS cache is used, the sip.cfg configuration would look as
follows:
reg.1.address="1002"
4 - 74
Configuring Your System
reg.1.server.1.address="sipserver.example.com"
reg.1.server.1.port=""
reg.1.server.1.transport=""
reg.1.server.2.address=""
reg.1.server.2.port=""
reg.1.server.2.transport=""
dns.cache.NAPTR.1.name="sipserver.example.com"
dns.cache.NAPTR.1.ttl= "3600"
dns.cache.NAPTR.1.order="1"
dns.cache.NAPTR.1.preference="1"
dns.cache.NAPTR.1.flag="s"
dns.cache.NAPTR.1.service=" SIP+D2U"
dns.cache.NAPTR.1.regexp=""
dns.cache.NAPTR.1.replacement="_sip._udp.sipserver.example.com"
dns.cache.SRV.1.name="_sip._udp.sipserver.example.com "
dns.cache.SRV.1.ttl= "3600"
dns.cache.SRV.1.priority="1"
dns.cache.SRV.1.weight="1"
dns.cache.SRV.1.port="5075"
dns.cache.SRV.1.target="primary.sipserver.example.com"
dns.cache.SRV.2.name="_sip._udp.sipserver.example.com "
dns.cache.SRV.2.ttl= "3600"
dns.cache.SRV.2.priority="2"
dns.cache.SRV.2.weight="1"
dns.cache.SRV.2.port="5075"
dns.cache.SRV.2.target="secondary.sipserver.example.com
dns.cache.A.1.name="primary.sipserver.example.com"
dns.cache.A.1.ttl="3600"
dns.cache.A.1.address="172.23.0.140"
dns.cache.A.2.name="secondary.sipserver.example.com"
dns.cache.A.2.ttl="3600"
dns.cache.A.2.address="172.23.0.150"
4 - 75
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
These messages are displayed in any language supported by the phone for
three seconds unless overridden by another message or action.
For example, if a user parks a call, the following message appears on their
phone:
Central Configuration file: Turn this feature on or off and specify which warnings are
(boot server) sip.cfg displayable.
• For more information, refer to SIP <SIP/> on page A-11.
4 - 76
Configuring Your System
• Audio Codecs
• IP Type-of-Service
• IEEE 802.1p/Q
• Treble/Bass Controls
4 - 77
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Central Configuration file: Set the jitter buffer tuning parameters including minimum and
(provisioning sip.cfg maximum size and shrink aggression.
server) • For more information, refer to Codec Profiles <audioProfile/> on
page A-49.
Local Web Server Set the jitter buffer tuning parameters including minimum and
(if enabled) maximum size and shrink aggression.
Navigate to http://<phoneIPAddress>/coreConf.htm#au
Changes are saved to local flash and backed up to <Ethernet
address>-phone.cfg on the provisioning server. Changes will
permanently override global settings unless deleted through the
Reset Local Config menu selection.
Central Configuration file: Enable or disable VAD and set the detection threshold.
(provisioning sip.cfg • For more information, refer to Voice Activity Detection <vad/> on
server) page A-60.
4 - 78
Configuring Your System
Central Configuration file: Set the DTMF tone levels, autodialing on and off times, and other
(provisioning sip.cfg parameters.
server) • For more information, refer to Dual Tone Multi-Frequency
<DTMF/> on page A-35.
Central Configuration file: Enable or disable RFC 2833 support in SDP offers and specify the
(provisioning sip.cfg payload value to use in SDP offers.
server) • For more information, refer to Dual Tone Multi-Frequency
<DTMF/> on page A-35.
voice.aec.hs.enable = 1
voice.aes.hs.enable = 1
voice.ns.hs.enable = 1
voice.ns.hs.signalAttn = -6
voice.ns.hs.silenceAttn = -9
4 - 79
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Audio Codecs
The following table shows which audio codecs are support by each of the
SoundPoint IP, SoundStation IP, and Polycom VVX phones:
SoundPoint IP 335, 450, 550, 560, 650, and 670 G.711μ-law, G.711a-law, G.722, G.729AB, iLBC
Effective
Sample audio
Algorithm MIME Type Ref. Bit Rate Rate Frame Size bandwidth
4 - 80
Configuring Your System
Effective
Sample audio
Algorithm MIME Type Ref. Bit Rate Rate Frame Size bandwidth
Lin16 L16/8000 RFC 1890 128 Kbps 8 Ksps 10ms 3.5 KHz
L16/16000 256 Kbps 16 Ksps 7 KHz
L16/32000 512 Kbps 32 Ksps 14 KHz
L16/44100 705.6 Kbps 44.1 Ksps 20 KHz
L16/48000 768 Kbps 48 Ksps 22 KHz
Note The network bandwidth necessary to send the encoded voice is typically 5-10%
higher than the encoded bit rate due to packetization overhead. For example, a
G.722.1C call at 48kbps consumes about 100kbps of network bandwidth (two-way
audio).
Central Configuration file: Specify codec priority, preferred payload sizes, and jitter buffer tuning
(provisioning sip.cfg parameters.
server) • For more information, refer to Codec Preferences <codecPref/>
on page A-45 and Codec Profiles <audioProfile/> on page A-49.
Local Web Server Specify codec priority, preferred payload sizes, and jitter buffer tuning
(if enabled) parameters.
Navigate to http://<phoneIPAddress>/coreConf.htm#au
Changes are saved to local flash and backed up to <Ethernet
address>-phone.cfg on the provisioning server. Changes will
permanently override global settings unless deleted through the
Reset Local Config menu selection.
4 - 81
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
IP Type-of-Service
The “type of service” field in an IP packet header consists of four
type-of-service (TOS) bits and a 3-bit precedence field. Each TOS bit can be set
to either 0 or 1. The precedence field can be set to a value from 0 through 7. The
type of service can be configured specifically for RTP packets and call control
packets, such as SIP signaling packets.
Configuration changes can be performed centrally at the provisioning server
or locally:
IEEE 802.1p/Q
The phone will tag all Ethernet packets it transmits with an 802.1Q VLAN
header for one of the following reasons:
4 - 82
Configuring Your System
Local Phone User Specify whether CDP is to be used or manually set the VLAN ID or
Interface configure DHCP VLAN Discovery.
Phase 1: BootRom - Navigate to: SETUP menu during auto-boot
countdown.
Phase 2: SIP Application - Navigate to:
Menu>Settings>Advanced>Admin Settings>Network
Configuration
• For more information, refer to Setting Up the Network on page
3-2.
Note This feature requires a license key for activation except for the Polycom VVX 1500.
Using this feature may require purchase of a license key or activation by Polycom
channels. For more information, contact your Certified Polycom Reseller.
Note Voice Quality Monitoring is not supported on the SoundStation IP 6000 and 7000
conference phones at this time. Only Voice Quality Monitoring of the audio portion
is supported on the Polycom VVX 1500 at this time.
4 - 83
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
The RTCP XR packets are compliant with RFC 3611 - RTP Control Extended
Reports (RTCP XR). The packets are sent to a report collector as specified in
draft RFC draft-ietf_sipping_rtcp-summary-02.
Three types of quality reports can be enabled:
Central Configuration file: Specify the location of the central report collector, how often the
(provisioning sip.cfg reports are generated, and the warning and critical threshold values
server) that will cause generation of alert reports.
• For more information, refer to Quality Monitoring <quality
monitoring/> on page A-61.
Treble/Bass Controls
The treble and bass controls equalize the tone of the high and low frequency
sound from the speakers.
The SoundStation IP 7000 phone’s treble and bass controls can be modified by
the user (through Menu > Settings > Basic > Audio > Treble EQ or Bass EQ).
Configuration changes can be performed centrally at the provisioning server:
Central Configuration file: Specify the user’s preferences for treble and bass.
(provisioning sip.cfg • For more information, refer to User Preferences <up/> on page
server) A-31.
4 - 84
Configuring Your System
• Video Transmission
• Video Codecs
• H.323 Protocol
Video Transmission
By default, at the start of a video call, the Polycom VVX 1500 phone transmits
an RTP encapsulated video stream with images captured from the local
camera. Users can stop and start video transmission by pressing the Video
key, and then selecting the appropriate soft key.
You can control of the following features of the Polycom VVX 1500 phone’s
camera:
• Flicker avoidance
• Frame rate
• Brightness level
• Saturation level
• Contrast level
• Sharpness level
4 - 85
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Central Configuration file: Turn video transmission off at the near end when calls start and
(provisioning sip.cfg transmit still image if video not available.
server) • For more information, refer to Video Settings <video/> on page
A-64.
Local Local Phone User The user can set the individual video settings from the menu through
Interface Settings > Basic > Video > Video Call Settings, Video Screen
Mode, and Local Camera View.
The user can set the individual camera settings from the menu
through Settings > Basic > Video > Camera Settings.
Video Codecs
The following table summarizes the Polycom VVX 1500 phone’s video codec
support:
Effective
Frame video
Algorithm MIME Type Bit Rate Rate Frame Size bandwidth
Central Configuration file: Specify codec priority, payload type and jitter buffer tuning
(provisioning sip.cfg parameters.
server) • For more information, refer to Codec Preferences <codecPref/>
on page A-66 and Codec Profiles <profile/> on page A-66.
4 - 86
Configuring Your System
H.323 Protocol
Note This feature requires a license key for activation on the Polycom VVX 1500. Using
this feature may require purchase of a license key or activation by Polycom
channels. For more information, contact your Certified Polycom Reseller.
As of SIP 3.2.2, telephony signaling support via the H.323 family of protocols
enabling direct communication with H.323 endpoints, gatekeepers, call and
media servers, and signaling gateways is supported on the Polycom VVX 1500
phone.
SIP and H.323 signaling can be supported at the same time, including bridging
both types of calls during multi-party conference calls. Automatic detection of
the correct or optimal signaling protocol is available when dialing from the
contact or corporate directories. While SIP supports server redundancy and
several transport options, only a single configured H.323 gatekeeper address
per phone is supported. H.323 gatekeepers are optional, but if available, they
must be used. If a gatekeeper is not configured or unavailable, calls can still be
made if so configured.
If the H.323 protocol is disabled, there will be no visible evidence in the user
interface of the Polycom VVX 1500 phone.
Support of the SIP protocol for telephony signaling can be disabled on the
Polycom VVX 1500 such that all calls would be routed via the H.323 protocol.
This section provides detailed information on:
• Supported Standards
• Useful Tips
• Examples
Supported Standards
The following standards are supported by the implementation of this feature:
Standard Description
4 - 87
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Standard Description
Note Refer to the Release Notes for the latest list of supported Polycom
endpoints/bridges/call servers (or gatekeepers)/media servers and any supported
third party products. Any issues (and possible workarounds) with any of the
above-mentioned products are also documented in the Release Notes.
4 - 88
Configuring Your System
Central Configuration file: Specify H.323 protocol, server, gatekeeper, and DTMF signaling
(provisioning sip.cfg parameters.
server) • For more information, refer to Protocol <voIpProt/> on page A-7.
Specify call routing parameters.
• For more information, refer to User Preferences <up/> on page
A-31 and Call Handling Configuration <call/> on page A-80.
Specify the video call rate.
• For more information, refer to Video Settings <video/> on page
A-64.
Specify auto-answer parameters.
• For more information, refer to Call Handling Configuration <call/>
on page A-80.
Specify H.323 media encryption parameters.
• For more information, refer to H.235 <H235/> on page A-112.
Useful Tips
The following information should be noted:
• If the phone has only the H.323 protocol enabled, it cannot be used to
answer SIP calls.
• If the phone has only the SIP protocol enabled, it cannot be used to answer
H.323 calls.
• If both SIP and H.323 protocols are disabled by mistake, the phone will
continue to work as a SIP-only phone; however, the phone is not
registered (you are able to send and receive SIP URL calls).
• The protocol that is used to place a call is stored in the placed call list of the
user’s phone.
• The protocol to be used when placing a call from the user’s local contact
directory is unspecified by default. The user can select SIP or H.323.
• The protocol that is used when placing a call from the user’s corporate
directory depends on the order of the attributes in the corporate directory.
If only SIP_address is defined, then the SIP protocol is used. If only
H323_address is defined, then the H.323 protocol is used. If both are
defined, then the one that is defined first is used. For example, if
dir.corp.attribute.4.type is SIP_address and
4 - 89
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
• By default, the user is presented with protocol routing choices when a call
could be placed with more than one protocol from its current context. The
user must choose between SIP and H.323 to place a call by pressing the
appropriate soft key.
Examples
The following example sip.cfg configuration file shows the relevant
parameters:
• To set up a SIP and H.323 dial plan—Numbers with the format “0xxx” are
placed on a SIP line and numbers with the format “33xx” are placed on an
H.323 line
• To set up manual protocol routing using soft keys—If the protocol to use
to place a call cannot be determined, the Use SIP and Use H.323 soft keys
appear, and the user must select one for the call to be placed.
4 - 90
Configuring Your System
• To set to configure one SIP line, one H.323 line, and a dual protocol
line—both SIP and H.323 can be used.
• To set the preferred protocol for off-hook calls on the third (dual protocol)
line to SIP
4 - 91
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
• Custom Certificates
• Digital Certificates
Central Configuration file: Specify the minimum lengths for the user and administrator
(provisioning sip.cfg passwords.
server) • For more information, refer to Password Lengths
<pwd/><length/> on page A-109.
Local Phone User The user and administrator passwords can be changed under the
Interface Settings menu or through configuration parameters (refer to Flash
Parameter Configuration on page A-157). Passwords can consist of
ASCII characters 32-127 (0x20-0x7F) only.
Changes are saved to local flash but are not backed up to <Ethernet
address>-phone.cfg on the provisioning server for security reasons.
4 - 92
Configuring Your System
Custom Certificates
The phone trusts certificates issued by widely recognized certificate
authorities when trying to establish a connection to a provisioning server for
application provisioning. Refer to Trusted Certificate Authority List on page
C-1.
In addition, custom certificates can be added to the phone. This is done by
using the SSL Security menu on the phone to provide the URL of the custom
certificate then select an option to use this custom certificate.
Note For more information on using custom certificates, refer to “Technical Bulletin
17877: Using Custom Certificates With SoundPoint IP Phones” at
http://www.polycom.com/support/voice/soundpoint_ip/VoIP_Technical_Bulletins_pu
b.html .
Local Local Phone User The custom certificate can be specified and the type of certificate to
Interface trust can be set under the Settings menu.
• Digest authentication
4 - 93
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Note When using SRTP with Polycom VVX 1500 phone, limit the video bandwidth on the
Polycom VVX 1500 to 384kbps; otherwise you will experience performance issues.
If the call is completely secure (RTP authentication and encryption and RTCP
authentication and RTCP encryption are enabled), then the user sees a padlock
symbol appearing in the last frame of the connected context animation
(two arrow moving towards each other).
In SIP 2.2, the SRTP feature has been implemented in a very configurable
manner. The reason for this is to allow deployment in a mixed environment
where some elements of the solution are SRTP capable and some are not.
In SIP 3.2, sec.srtp.requireMatchingTag was added to sip.cfg as a flag to
force a check of the tag value in the crypto attribute in an SDP answer.
For detailed configuration instructions, refer to “Technical Bulletin 25751:
Secure Real-Time Transport Protocol on SoundPoint IP Phones” at
http://www.polycom.com/support/voice/soundpoint_ip/VoIP_Technical
_Bulletins_pub.html .
Configuration changes can be performed centrally at the boot server:
Central Configuration File: Specify the parameters to enable and disable SRTP.
(boot server) sip.cfg • For more information, refer to SRTP <srtp/>on page A-110.
4 - 94
Configuring Your System
Note Encrypted configuration files can be decrypted on the SoundPoint IP 32x, 33x, 430,
450, 550, 560, 650, and 670, the SoundStation IP 6000, and 7000, and the
Polycom VVX 1500 phones.
The master configuration file cannot be encrypted on the provisioning server. This
file is downloaded by the BootROM that does not recognize encrypted files. For
more information, refer to Master Configuration Files on page A-2.
Central Configuration File: Specify the phone-specific contact directory and the
(provisioning sip.cfg phone-specific configuration override file.
server) • For more information, refer to Encryption <encryption/>
on page A-109.
Digital Certificates
Starting in May 2009, Polycom is installing a digital certificate on certain
SoundPoint IP phone models at the manufacturing facility. Over time, other
SoundPoint IP phone models as well as all SoundStation IP and Polycom VVX
phone models will have a digital certificate. Refer to “Technical Bulletin 37148:
Device Certificates on SoundPoint IP, SoundStation IP, and Polycom VVX
1500 Phones“at
http://www.polycom.com/support/voice/soundpoint_ip/VoIP_Technical
_Bulletins_pub.html .
This X.509 digital certificate is ‘signed’ by the Polycom Root CA and may be
used for a server to authenticate the phone when initiating Transport Layer
Security (TLS) based communications such as those used for HTTPS
provisioning and TLS SIP signaling encryption. The Polycom Root CA can be
downloaded from http://pki.polycom.com/pki . The X.509 digital certificates
are set to expire on March 9, 2044.
4 - 95
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
• Version. This identifies which version of the X.509 standard applies to this
certificate, which affects what information can be specified in it.
• Serial Number. The entity that created the certificate is responsible for
assigning it a serial number to distinguish it from other certificates it
issues.
• Issuer Name. The X.500 name of the entity that signed the certificate. This
is normally a CA. Using this certificate implies trusting the entity that
signed this certificate.
• Validity Period. Each certificate is valid only for a limited amount of time.
This period is described by a start date and time and an end date and time,
and can be as short as a few seconds or almost as long as a century.
• Subject Name. The name of the entity whose public key the certificate
identifies. This name uses the X.500 standard, so it is intended to be unique
across the Internet.
• Subject Public Key Information. This is the public key of the entity being
named, together with an algorithm identifier which specifies which public
key cryptographic system this key belongs to and any associated key
parameters.
The following is an example of a Polycom device certificate (if opened with the
Microsoft Internet Explorer 7 or Firefox 3.5 browser on a computer running
Microsoft XP Service Pack 3):
The device certificate and associated private key are stored on the phone in its
non-volatile memory as part of the manufacturing process.
4 - 96
Configuring Your System
4 - 97
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
• SIP signaling—when the selected transport protocol is TLS and the server
is configured for Mutual Authentication
Note At this time, the user will not be able to modify or update the digital certificate or the
associated private key stored on the phone during manufacturing.
4 - 98
Configuring Your System
Local Settings Some items in the Settings menu are locked to prevent accidental changes.
Menu Access To unlock these menus, enter the user or administrator passwords.
The administrator password can be used anywhere that the user password is
used. (Polycom recommends that you change the administrative password
from the default value.)
Factory default passwords are:
User password: 123
Administrator password: 456
Passwords:
Changes made through the web server or local user interface are stored
internally as overrides. These overrides take precedence over settings
contained in the configuration obtained from the provisioning server.
If the provisioning server permits uploads, these override setting will be saved
in a file called <Ethernet address>-phone.cfg on the provisioning server as
well as in flash memory.
4 - 99
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
4 - 100
5
Troubleshooting Your SoundPoint IP /
SoundStation IP / VVX Phones
This chapter provides you with some tools and techniques for troubleshooting
SoundPoint IP / SoundStation IP / VVX phones and installations. The phone
can provide feedback in the form of on-screen error messages, status
indicators, and log files for troubleshooting issues.
This chapter includes information on:
• Status Menu
• Log Files
• Controls
• Calling
• Displays
• Audio
• Licensable Features
• Upgrading
Review the latest Release Notes for the SIP application for known problems and
possible workarounds. For the latest Release Notes and the latest version of this
Administrator’s Guide, go to Polycom Technical Support at
http://www.polycom.com/support/voice/.
5-1
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
If a problem is not listed in this chapter nor described in the latest Release Notes,
contact your Certified Polycom Reseller for support.
Error Messages
There are several different error messages that can be displayed on the phone
when it is booting. Some of these errors are fatal, meaning that the phone will
not able to boot until this issue has been resolved, and some are recoverable,
meaning the phone will continue booting after the error, but the configuration
of the phone may not be what you were expecting.
5-2
Troubleshooting Your SoundPoint IP / SoundStation IP / VVX Phones
Note This error does not occur with BootROM 3.2.2 B or later.
Note This error does not occur with BootROM 3.2.2 B or later.
5-3
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
the phone is not in the menu system and will remain on screen until the link
problem is resolved. Call related functions (for example, soft keys and feature
keys) disabled when the network is down; however the menu works.
Status
When the phone is unable to register with the call control server, the icon
Flashing Time
If the phone has not been able to contact the SNTP server or if one has not been
configured, the date/time display will flash until this is fixed. If an SNTP is not
available, the data/time display can be turned off so that the flashing display
is not a distraction.
Status Menu
Debugging of single phone may be possible through an examination of the
phone’s status menu. Press Menu, select Status, and then press the Select soft
key.
Under the Platform selection, you can get details on the phone’s serial number
or MAC address, the current IP address, the BootROM version, the application
version, the name of the configuration files in use, and the address of the
provisioning server.
In the Network menu, the phone will provide information about TCP/IP
setting, Ethernet port speed, connectivity status of the PC port, and statistics
on packets sent and received since last boot. This would also be a good place
to look and see how long it has been since the phone rebooted. The Call
Statistics screen shows packets sent and received on the last call.
The Lines menu will give you details about the status of each line that has been
configured on the phone.
Finally, the Diagnostics menu offers a series of hardware tests to verify correct
operation of the microphone, speaker, handset, and third party headset, if
present. It will also let you test that each of the keys on the phone is working,
and it will display the function that has been assigned to each of the keys in the
configuration. This is also where you can test the LCD for faulty pixels.
5-4
Troubleshooting Your SoundPoint IP / SoundStation IP / VVX Phones
Log Files
SoundPoint IP and SoundStation IP phones will log various events to files
stored in the flash file system and will periodically upload these log files to the
provisioning server. The files are stored in the phone’s home directory or a
user-configurable directory. You can also configure a phone to send log
messages to a syslog server.
There is one log file for the BootROM and one for the application. When a
phone uploads its log files, they are saved on the provisioning server with the
MAC address of the phone prepended to the file name. For example,
0004f200360b-boot.log and 0004f200360b-app.log are the files associated with
MAC address 00f4f200360b. The BootROM log file is uploaded to the
provisioning server after every reboot. The application log file is uploaded
periodically or when the local copy reaches a predetermined size. Refer to
Basic Logging <level/><change/> and <render/> on page A-106.
Both log files can be uploaded on demand using a multiple key combination
described in Multiple Key Combinations on page C-11. The phone uploads
four files, namely, mac-boot.log, app-boot.log, mac-now-boot.log, and
mac-now-app.log. The “now_” logs are uploaded manually unless they are
empty.
The amount of logging that the phone performs can be tuned for the
application to provide more or less detail on specific components of the
phone’s software. For example, if you are troubleshooting a SIP signaling
issue, you are not likely interested in DSP events. Logging levels are adjusted
in the configuration files or via the web interface. You should not modify the
default logging levels unless directed to by Polycom Technical Support.
Inappropriate logging levels can cause performance issues on the phone.
In addition to logging events, the phone can be configured to automatically
execute command-line instructions at specified intervals that output run-time
information such as memory utilization, task status, or network buffer
contents to the log file. These techniques should only be used in consultation
with Polycom Technical Support.
5-5
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
The parameters for log level settings are found in the sip.cfg configuration file.
They are log.level.change.module_name. Log levels range from 1 to 6 (1 for
the most detailed logging, 6 for critical errors only). There are currently 27
different log types that can be adjusted to assist with the investigation of
different problems.
When testing is complete, remember to return all logging levels to the default
value of 4.
There are other logging parameters that you may wish to modify. Changing
these parameters does not have the same impact as changing the logging
levels, but you should still understand how your changes will affect the phone
and the network.
Scheduled Logging
Scheduled logging is a powerful tool for anyone who is trying to troubleshoot
an issue with the phone that only occurs after some time in operation.
The output of these instructions is written to the application log, and can be
examined later (for trend data).
The parameters for scheduled logging are found in the sip.cfg configuration
file. They are log.sched.module_name.
5-6
Troubleshooting Your SoundPoint IP / SoundStation IP / VVX Phones
5-7
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
5-8
Troubleshooting Your SoundPoint IP / SoundStation IP / VVX Phones
5-9
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Reading a Syslog
The following shows a portion of a syslog log file—the messages look identical
to the normal log with the addition of a timestamp and IP address:
5 - 10
Troubleshooting Your SoundPoint IP / SoundStation IP / VVX Phones
5 - 11
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Controls
Symptom Problem Corrective Action
The dial pad does not work. The dial pad on the SoundPoint Do one of the following:
IP / SoundStation IP / VVX family • Check for a response from other
SIP phone does not respond. feature keys or from the dial pad.
• Place a call to the phone from a known
working telephone. Check for display
updates.
• Press the Menu key followed by
System Status and Server Status to
check if the telephone is correctly
registered to the server.
• Press the Menu key followed by
System Status and Network
Statistics. Scroll down to see if LAN
port shows active or Inactive.
• Check the termination at the switch or
hub end of the network LAN cable.
Ensure that the switch/hub port
connected to the telephone is
operational (if not accessible, contact
your system administrator).
• Before restarting your phone, contact
your system administrator, since this
may allow more detailed
troubleshooting to occur before losing
any current status information.
5 - 12
Troubleshooting Your SoundPoint IP / SoundStation IP / VVX Phones
The display shows “Network Link The LAN cable is not properly Do one of the following:
is Down”. connected. • Check termination at the switch or hub
(furthest end of the cable from the
phone).
• Check that the switch or hub is
operational (flashing link/status lights)
or contact your system administrator.
• Press Menu followed by Status >
Network. Scroll down to verify that the
LAN is active.
• Ping phone from another machine.
• Reboot the phone to attempt
re-registration to the call server (refer
to Rebooting the Phone on page
C-11).
5 - 13
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Calling
Symptom Problem Corrective Action
There is no dial tone. Power is not correctly applied to Do one of the following:
the SoundPoint IP family SIP • Check that the display is illuminated.
phone.
• Make sure the LAN cable is inserted
properly at the rear of the phone (try
unplugging and re-inserting the
cable).
• If using in-line powering, have your
system administrator check that the
switch is supplying power to the
phone.
The phone does not ring. Ring setting or volume is low. Do one of the following:
• Adjust the ringing level from the front
panel using the volume up/down keys.
• Check same status of handset,
headset (if connected) and through
the Hands-Free Speakerphone.
The line icon shows an The phone line is unregistered. Contact your system administrator.
unregistered line icon.
5 - 14
Troubleshooting Your SoundPoint IP / SoundStation IP / VVX Phones
Displays
Symptom Problem Corrective Action
The display is flickering. Certain type of older fluorescent Do one of the following:
lighting causes the display to • Move the SoundPoint IP /
appear to flicker. SoundStation IP / VVX SIP phone
away from the lights.
• Replace the lights.
• Use the screen capture feature. Refer
to Capturing Phone’s Current Screen
on page C-30.
5 - 15
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Audio
Symptom Problem Corrective Action
There is no audio on the The connections are not correct. Do one of the following:
headset. • Ensure the headset is plugged into the
jack marked Headset at the rear of the
phone.
• Ensure the headset amplifier (if
present) is turned on and/or the
volume is correctly adjusted).
There are audio and echo issues Possible issues include: Refer to “Technical Bulletin 16249:
on the headset. • Echo on external calls Troubleshooting Audio and Echo Issues
through a gateway. on SoundPoint® IP Phones” at
http://www.polycom.com/usa/en/support/v
• Internal calls (no gateway),
oice/soundpoint_ip/VoIP_Technical_Bullet
handsfree echo.
ins_pub.html .
• Internal calls (no gateway),
handset to handset echo.
Licensable Features
Symptom Problem Corrective Action
A user is trying to access one of The license is not installed on the Do the following:
the following features, but it is not phone or it has expired. • Press the Menu key, then select
available on their phone: Status > Licenses.
• Corporate Directory • Using the arrow keys, verify that the
• Recording and Playback of feature in question has a valid license.
Audio Calls If no licenses are installed, the “No
• Managing Conferences license installed.” message appears.
• Voice Quality Monitoring
• H.323
5 - 16
Troubleshooting Your SoundPoint IP / SoundStation IP / VVX Phones
Upgrading
Symptom Problem Corrective Action
SoundPoint IP 300, 301, 500, New features are not supported The attempt to load the new application
501, 600, and/or 601 and/or on the SoundPoint IP 300, 301, will fail since there is no
SoundStation IP 4000 behave 500, 501, 600, and 601 and 300/301/500/501/600/601/4000 image
incorrectly or do not display new SoundStation IP 4000 and the contained within the sip.ld file, so the
features. configuration files have not been phone will continue on and run the current
correctly modified. These phones version of application that it has in
will not ‘understand’ the new memory. It will however use the new
configuration parameters, and configuration files. Refer to Supporting
will attempt to load the new SoundPoint IP 300, 301, 500, 501, 600
application. and 601 and SoundStation IP 4000
Phones on page 3-23.
5 - 17
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
5 - 18
A
Configuration Files
Note In the tables in the subsequent sections, “Null” should be interpreted as the empty
string, that is, attributeName=“” when the file is viewed in an XML editor.
To enter special characters in a configuration file, enter the appropriate sequence
using an XML editor:
• & as &
• ” as "
• ’ as '
• < as <
• > as >
A-1
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Note You can make changes to the configuration files through the web interface to the
phone. Using your chosen browser, enter the phone’s IP address as the browser
address. For more information, refer to Modifying Phone’s Configuration Using the
Web Interface on page C-27.
Changes made through the web interface are written to the override file (highest
priority). These changes remain active until Reset Local Config is performed.
A-2
Configuration Files
<!--
http://www.polycom.com/common/documents/whitepapers/configuration_file
_management_on_soundpoint_ip_phones.pdf -->
<!-- $RCSfile: 000000000000.cfg,v $ $Revision: 1.21 $ -->
<APPLICATION APP_FILE_PATH="sip.ld" CONFIG_FILES="phone1.cfg,
sip.cfg" MISC_FILES="" LOG_FILE_DIRECTORY="" OVERRIDES_DIRECTORY=""
CONTACTS_DIRECTORY="" LICENSE_DIRECTORY="">
<APPLICATION_SPIP300 APP_FILE_PATH_SPIP300="sip_212.ld"
CONFIG_FILES_SPIP300="phone1_212.cfg, sip_212.cfg"/>
<APPLICATION_SPIP500 APP_FILE_PATH_SPIP500="sip_212.ld"
CONFIG_FILES_SPIP500="phone1_212.cfg, sip_212.cfg"/>
<APPLICATION_SPIP301 APP_FILE_PATH_SPIP301="sip_313.ld"
CONFIG_FILES_SPIP301="phone1_313.cfg, sip_313.cfg"/>
<APPLICATION_SPIP501 APP_FILE_PATH_SPIP501="sip_313.ld"
CONFIG_FILES_SPIP501="phone1_313.cfg, sip_313.cfg"/>
<APPLICATION_SPIP600 APP_FILE_PATH_SPIP600="sip_313.ld"
CONFIG_FILES_SPIP600="phone1_313.cfg, sip_313.cfg"/>
<APPLICATION_SPIP601 APP_FILE_PATH_SPIP601="sip_313.ld"
CONFIG_FILES_SPIP601="phone1_313.cfg, sip_313.cfg"/>
<APPLICATION_SSIP4000 APP_FILE_PATH_SSIP4000="sip_313.ld"
CONFIG_FILES_SSIP4000="phone1_313.cfg, sip_313.cfg"/>
</APPLICATION>
A-3
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
A-4
Configuration Files
Application Configuration
The configuration file sip.cfg contains SIP protocol and core configuration
settings that would typically apply to an entire installation and must be set
before the phones will be operational, unless changed through the local web
server interface or local menu settings on the phone. These settings include the
local port used for SIP signaling, the address and ports of a cluster of SIP
application servers, voice codecs, gains, and tones, and other parameters.
A-5
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Polycom recommends that you create another file with your organization’s
modifications. If you must change any Polycom templates, back them up first.
For more information, refer to the“Configuration File Management on SoundPoint
IP, SoundStation IP, and Polycom VVX 1500 Phones” white paper at
http://www.polycom.com/global/documents/support/technical/products/voice/white_
paper_configuration_file_management_on_soundpoint_ip_phones.pdf .
• Protocol <voIpProt/>
• Localization <lcl/>
• Tones <tones/>
• Directory <dir/>
• Presence <pres/>
• Fonts <font/>
• Keys <key/>
• Backgrounds <bg/>
• Bitmaps <bitmap/>
• Indicators <ind/>
• Security <sec/>
• License <license/>
• Provisioning <prov/>
A-6
Configuration Files
• Request <request/>
• Feature <feature/>
• Resource <res/>
• Microbrowser <mb/>
• Applications <apps/>
Protocol <voIpProt/>
This attribute includes:
• Server <server/>
• SIP <SIP/>
• H.323 <H323/>
A-7
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Server <server/>
This configuration attribute is defined as follows:
Permitted
Attribute Values Default Interpretation
voIpProt.server.dhcp.option 128 to 255 Null Option to request from the DHCP server if
voIpProt.server.dhcp.available = 1.
There is no default value for this parameter, it
must be filled in with a valid value.
Note: If the reg.x.server.y.address parameter
in Registration <reg/> on page A-134 is
non-Null, it takes precedence even if the
DHCP server is available.
A-8
Configuration Files
Permitted
Attribute Values Default Interpretation
A-9
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
A - 10
Configuration Files
Permitted
Attribute Values Default Interpretation
SIP <SIP/>
This configuration attribute is defined as follows:
Permitted
Attribute Values Default Interpretation
A - 11
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
A - 12
Configuration Files
Permitted
Attribute Values Default Interpretation
A - 13
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
A - 14
Configuration Files
Permitted
Attribute Values Default Interpretation
A - 15
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
• SDP <SDP/>
• Dialog <dialog/>
• Connection Reuse<dialog/>
• Compliance <compliance/>
A - 16
Configuration Files
SDP <SDP/>
This configuration attribute is defined as follows:
Permitted
Attribute Values Default Interpretation
A - 17
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
A - 18
Configuration Files
Permitted
Attribute Values Default Interpretation
Permitted
Attribute Values Default Interpretation
voIpProt.SIP.requestValidation.x. One of: Null Sets the name of the method for which
request “INVITE”, “ACK” validation will be applied.
, “BYE” WARNING: Intensive request validation
“REGISTER”, may have a negative performance impact
“CANCEL”, due to the additional signaling required in
“OPTIONS”, some cases, therefore, use it wisely.
“INFO”,
“MESSAGE”,
“SUBSCRIBE”
“NOTIFY”,
“REFER”,
“PRACK”, or
“UPDATE”
A - 19
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
voIpProt.SIP.requestValidation.x. A valid string Null Determines which events specified with the
request.y.event Event header should be validated; only
applicable when
voIpProt.SIP.requestValidation.x.re
quest is set to “SUBSCRIBE” or “NOTIFY”.
If set to Null, all events will be validated.
Permitted
Attribute Values Default Interpretation
Permitted
Attribute Values Default Interpretation
voIpProt.SIP.conference.address ASCII string Null If Null, conferences are set up on the phone
up to 128 locally.
characters If set to some value, conferences are set up
long by the server using the conferencing agent
specified by this address. The acceptable
values depend on the conferencing server
implementation policy.
A - 20
Configuration Files
Dialog <dialog/>
This configuration attribute is defined as follows:
Permitted
Attribute Values Default Interpretation
Connection Reuse<dialog/>
This configuration attribute is defined as follows:
Permitted
Attribute Values Default Interpretation
Permitted
Attribute Values Default Interpretation
voIpProt.SIP.musicOnHold.uri string Null A URI that provides the media stream to play
for the remote party on hold.
If reg.x.musicOnHold is set to Null, this
attribute is checked.
Note: The SIP URI parameter transport is
supported when configured with the values of
UDP, TCP, or TLS.
A - 21
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Compliance <compliance/>
This configuration attribute is defined as follows:
Permitted
Attribute Values Default Interpretation
H.323 <H323/>
Note At this time, this attribute is used with the Polycom VVX 1500 phone only.
Permitted
Attribute Values Default Interpretation
A - 22
Configuration Files
Permitted
Attribute Values Default Interpretation
Note The dial plan is not applied against Placed Call List, VoiceMail, last call return,
remote control dialed numbers, and on-hook dialing.
Permitted
Attribute Values Default Interpretation
A - 23
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
• Routing <routing/>
A - 24
Configuration Files
Digit map extension letter “R” indicates that certain matched strings are
replaced. Digit map timer letter “T” indicates a timer expiry. Digit map
protocol letters “S” and “H” indicate the protocol to use when placing a call.
The following examples shows the semantics of the syntax:
Note Only Polycom VVX 1500 phones will match the “H”. It is ignored by all other phones
and the user will need to press the Send soft key to complete dialing. For example,
if the digit map is “33xxH”, the result is as follows:
• If a Polycom VVX 1500 user dials “3302” on an H.323 or dual protocol line, the
call will be placed after the user dials the last digit.
• If a SoundPoint IP 650 user dials “3307”, the user must press the Send soft key
to complete dialing.
A - 25
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
• If a digit map does not comply, it is not included in the digit plan as a valid
one. That is, no matching is done against it.
• Using T in the left part of RRR syntax is not recommended. For example,
R0TR322R should be avoided.
This configuration attribute is defined as follows:
Routing <routing/>
This attribute allows the user to create a specific routing path for outgoing SIP
calls independent of other “default” configurations.
This attribute also includes:
• Server <server/>
A - 26
Configuration Files
• Emergency <emergency/>
Server <server/>
This configuration attribute is defined as follows:
Emergency <emergency/>
In the following attributes, x is the index of the emergency entry description
and y is the index of the server associated with emergency entry x. For each
emergency entry (index x), one or more server entries (indexes (x,y)) can be
configured. x and y must both use sequential numbering starting at 1.
dialplan.routing.emergency.x. Single entry representing for x =1, This determines the URLs
value a SIP URL value = “911”, Null that should be watched for.
for all others When one of these defined
URLs is detected as having
been dialed by the user, the
call will automatically be
directed to the defined
emergency server.
dialplan.routing.emergency.x. positive integer for x=1, y =1, Null Index representing the
server.y for all others server defined in Server
<server/> on page A-27 that
will be used for emergency
routing.
Localization <lcl/>
The phone has a multilingual user interface. It supports both North American
and international time and date formats. The call progress tones can also be
customized. For more information, refer to Chord-Sets <chord/> on page
A-36, and Call Progress Patterns on page A-40.
This attribute includes:
• Multilingual <ml/>
A - 27
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Multilingual <ml/>
The multilingual feature is based on string dictionary files downloaded from
the provisioning server. These files are encoded in standalone XML format.
Several eastern European and Asian languages are included with the
distribution.
A - 28
Configuration Files
A - 29
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Name Range
Extended character support available on SoundPoint IP 600 and SoundStation IP 4000 and 7000 platforms
includes the following Unicode character ranges
Name Range
Note Within a Unicode range, some characters may not be supported due to their
infrequent usage
A - 30
Configuration Files
Permitted
Attribute Values Interpretation
lcl.datetime.date.longFormat 0,1 If set to 1, display the day and month in long format
(Friday/November), otherwise, use abbreviations
(Fri/Nov).
Permitted
Attribute Values Default Interpretation
A - 31
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
up.idleTimeout positive Null Timeout for the idle display or default call
integer, handling display.
seconds If set to 0, there is no timeout.
If set to Null, the default timeout of 40 seconds
is used.
If set to value greater than 0, the timeout is for
that number of seconds (maximum 65535).
A - 32
Configuration Files
Permitted
Attribute Values Default Interpretation
A - 33
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
Tones <tones/>
This attribute describes configuration items for the tone resources available in
the phone.
This attribute includes:
• Chord-Sets <chord/>
A - 34
Configuration Files
Permitted
Attribute Values Default Interpretation
A - 35
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
Chord-Sets <chord/>
Chord-sets are the building blocks of sound effects that use synthesized rather
than sampled audio (most call progress and ringer sound effects). A chord-set
is a multi-frequency note with an optional on/off cadence. A chord-set can
contain up to four frequency components generated simultaneously, each
with its own level.
There are three blocks of chord sets:
• ringer
• misc (miscellaneous)
All three blocks use the same chord set specification format.
A - 36
Configuration Files
In the following table, x is the chord-set number and cat is one of callProg,
ringer, or misc.
Permitted
Attribute Values Interpretation
• G.711 A-Law
Note L16/32000 and L16/48000 are supported on SoundStation IP 6000 and 7000
phones.
The phone uses built-in wave files for some sound effects. The built-in wave
files can be replaced with files downloaded from the provisioning server or
from the Internet, however, these are stored in volatile memory so the files will
need to remain accessible should the phone need to be rebooted. Files will be
truncated to a maximum size of 300 kilobytes.
A - 37
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
saf.x Null OR valid path name If Null, the phone will use a built-in file.
OR an RFC If set to a path name, the phone will attempt to download this file
1738-compliant URL to a at boot time from the provisioning server.
HTTP, FTP, or TFTP wave
If set to a URL, the phone will attempt to download this file at boot
file resource.
time from the Internet.
Note: Refer to the above
Note: A TFTP URL is expected to be in the format:
wave file format
tftp://<host>/[pathname]<filename>, for example:
restrictions.
tftp://somehost.example.com/sounds/example.wav .
The following table defines the default usage of the sampled audio files with
the phone:
Note In SIP 3.1, the SoundPoint IP welcome sound was removed from saf.1 . If you
want the welcome sound to be played when a phone reboots or restarts, set saf.1
to SoundPointIPWelcome.wav .
A - 38
Configuration Files
Permitted
Attribute Values Default Interpretation
• Patterns <pat/>
Patterns <pat/>
Patterns use a simple script language that allows different chord sets or wave
files to be strung together with periods of silence. The script language uses the
following instructions:
sampled (n) Play sampled audio file se.pat.callProg.x.inst.y.type =”sampled” (sampled audio
n file instruction type)
se.pat.callProg.x.inst.y.value =”3” (specifies sampled
audio file 3)
A - 39
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Note Currently, patterns that use the sampled instruction are limited to the following
format: sampled followed by optional silence and optional branch back to the
beginning.
Permitted
Attribute Values Interpretation
se.pat.callProg.x.name UTF-8 Used for identification purposes in the user interface (currently
encoded used for ringer patterns only); for patterns that use a sampled
string audio file which has been overridden by a downloaded
replacement, the se.pat.ringer.x.name parameter will be
overridden in the user interface by the file names of the wave file.
se.pat.callProg.x.inst.y. positive If instruction type is chord, this optional parameter specifies the on
param integer duration to be used, overriding the on duration specified in the
chord-set definition.
Call progress
pattern number Use within phone
1 dial tone
2 busy tone
4 reorder tone
A - 40
Configuration Files
Call progress
pattern number Use within phone
8 confirmation tone
10 record warning
12 alerting
14 barge-in tone
Ringer Patterns
The following table maps ringer pattern numbers to their default descriptions.
1 Silent Ring
2 Low Trill
4 Medium Trill
6 High Trill
8 Highest Trill
10 Beeble
11 Triplet
12 Ringback-style
A - 41
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Note Silent Ring will only provide a visual indication of an incoming call, but no audio
indication.
Sampled audio files 1-21 all use the same built-in file unless that file has been
replaced with a downloaded file. For more information, refer to Sampled Audio for
Sound Effects <saf/> on page A-37.
Miscellaneous Patterns
The following table maps miscellaneous patterns to their usage within the
phone.
Miscellaneous
pattern number Use within phone
3 Not used
5 positive confirmation
6 negative confirmation
A - 42
Configuration Files
Note The auto-answer on incoming call is currently only applied if there is no other call in
progress on the phone at the time.
In the following table, x is the ring class number. The x index needs to be
sequential.
se.rt.enabled 0,1 Set to 1 to enable the ring type feature within the
phone, 0 otherwise.
se.rt.x.name UTF-8 encoded string Used for identification purposes in the user
interface.
se.rt.x.ringer integer - only relevant if the The ringer index to be used for this class of ring.
type is set to ‘ring’ or The ringer index should match one of Ringer
‘ring-answer’ Patterns on page A-41.
se.rt.x.callWait integer - only relevant if the The call waiting index to be used for this class of
type is set to ‘ring’ or ring. The call waiting index should match one
‘ring-answer’ defined in Call Progress Patterns on page A-40.
se.rt.x.timeout positive integer - only The duration of the ring in milliseconds before the
relevant if the type is set to call is auto answered. If this field is omitted or is left
‘ring-answer’. Default blank, a value of 2000 is used.
value is 2000.
A - 43
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
• Gains <gain/>
A - 44
Configuration Files
Permitted
Attribute Values Default Interpretation
voice.codecPref.IP_650.G722 1
voice.codecPref.iLBC.IP_650. Null
13_33kbps
voice.codecPref.iLBC.IP_650.15_2kbps Null
A - 45
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
voice.codecPref.IP_6000.G7221.16kbps Null
voice.codecPref.IP_6000.G7221.24kbps Null
voice.codecPref.IP_6000.G7221.32kbps 4
voice.codecPref.IP_6000.G729AB 7
voice.codecPref.IP_6000.G7221C. Null
24kbps
voice.codecPref.IP_6000.G7221C. Null
32kbps
voice.codecPref.IP_6000.G7221C. 1
48kbps
voice.codecPref.IP_6000.Siren14. Null
24kbps
voice.codecPref.IP_6000.Siren14. Null
32kbps
voice.codecPref.IP_6000.Siren14. 2
48kbps
voice.codecPref.iLBC.IP_6000. Null
13_33kbps
voice.codecPref.iLBC.IP_6000. Null
15_2kbps
A - 46
Configuration Files
Permitted
Attribute Values Default Interpretation
voice.codecPref.IP_7000.G7221.16kbps Null
voice.codecPref.IP_7000.G7221.24kbps Null
voice.codecPref.IP_7000.G7221.32kbps 5
voice.codecPref.IP_7000.G7221C. Null
24kbps
voice.codecPref.IP_7000.G7221C. Null
32kbps
voice.codecPref.IP_7000.G7221C. 2
48kbps
voice.codecPref.IP_7000.G729AB 8
voice.codecPref.IP_7000.Lin16.16ksps Null
voice.codecPref.IP_7000.Lin16.32ksps Null
voice.codecPref.IP_7000.Lin16.48ksps Null
voice.codecPref.IP_7000.Siren22. Null
32kbps
voice.codecPref.IP_7000.Siren22. Null
48kbps
voice.codecPref.IP_7000.Siren22. 1
64kbps
voice.codecPref.IP_7000.Siren14. Null
24kbps
voice.codecPref.IP_7000.Siren14. Null
32kbps
voice.codecPref.IP_7000.Siren14. 3
48kbps
voice.codecPref.iLBC.IP_7000. Null
13_33kbps
voice.codecPref.iLBC.IP_7000. Null
15_2kbps
A - 47
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
voice.codecPref.VVX_1500. Null
G719.48kbps
voice.codecPref.VVX_1500. Null
G719.64kbps
voice.codecPref.VVX_1500.G722 3
voice.codecPref.VVX_1500. Null
G7221.16kbps
voice.codecPref.VVX_1500. Null
G7221.24kbps
voice.codecPref.VVX_1500. 2
G7221.32kbps
voice.codecPref.VVX_1500. Null
G7221C.24kbps
voice.codecPref.VVX_1500. Null
G7221C.32kbps
voice.codecPref.VVX_1500. 1
G7221C.48kbps
voice.codecPref.VVX_1500.G729AB 6
voice.codecPref.VVX_1500. Null
Lin16.16ksps
voice.codecPref.VVX_1500. Null
Lin16.32ksps
voice.codecPref.VVX_1500. Null
Lin16.44_1ksps
voice.codecPref.VVX_1500. Null
Lin16.48ksps
voice.codecPref.VVX_1500.Lin16.8ksps Null
voice.codecPref.VVX_1500. Null
Siren14.24kbps
voice.codecPref.VVX_1500. Null
Siren14.32kbps
A - 48
Configuration Files
Permitted
Attribute Values Default Interpretation
voice.codecPref.VVX_1500. Null
Siren14.48kbps
voice.codecPref.iLBC.VVX_1500. Null
13_33kbps
voice.codecPref.iLBC.VVX_1500. Null
15_2kbps
Note Codecs with a default of Null are available for test purposes only and are not
expected to be used in your deployment.
Permitted
Attribute Values Interpretation
voice.audioProfile.x.jitterBufferMin 20, 40, 50, 60, The smallest jitter buffer depth (in milliseconds)
... (multiple of that must be achieved before play out begins
10) for the first time. Once this depth has been
achieved initially, the depth may fall below this
point and play out will still continue. This
parameter should be set to the smallest
possible value which is at least two packet
payloads, and larger than the expected short
term average jitter. The IP4000 values are the
same as the IP30x values.
voice.audioProfile.x.jitterBufferShrink 10, 20, 30, ... The absolute minimum duration time (in
(multiple of 10) milliseconds) of RTP packet Rx with no packet
loss between jitter buffer size shrinks. Use
smaller values (1000 ms) to minimize the delay
on known good networks. Use larger values to
minimize packet loss on networks with large
jitter (3000 ms).
A - 49
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Interpretation
Permitted
Attribute Values Default Interpretation
Gains <gain/>
The default gain settings have been carefully adjusted to comply with the
TIA-810-A digital telephony standard.
Attribute Default
voice.gain.rx.analog.handset 0
voice.gain.rx.analog.handset.VVX_1500 -2
voice.gain.rx.analog.headset 0
voice.gain.rx.analog.headset.VVX_1500 -2
voice.gain.rx.analog.chassis 0
A - 50
Configuration Files
Attribute Default
voice.gain.rx.analog.chassis.IP_330 0
voice.gain.rx.analog.chassis.IP_430 0
voice.gain.rx.analog.chassis.IP_450 0
voice.gain.rx.analog.chassis.IP_650 0
voice.gain.rx.analog.chassis.IP_6000 0
voice.gain.rx.analog.chassis.IP_7000 0
voice.gain.rx.analog.chassis.VVX_1500 -3
voice.gain.rx.analog.ringer 0
voice.gain.rx.analog.ringer.IP_330 0
voice.gain.rx.analog.ringer.IP_430 0
voice.gain.rx.analog.ringer.IP_450 0
voice.gain.rx.analog.ringer.IP_650 0
voice.gain.rx.analog.ringer.IP_6000 0
voice.gain.rx.analog.ringer.IP_7000 0
voice.gain.rx.analog.ringer.VVX_1500 0
voice.gain.rx.digital.handset -15
voice.gain.rx.digital.headset -21
voice.gain.rx.digital.chassis 0
voice.gain.rx.digital.chassis.IP_450 5
voice.gain.rx.digital.chassis.IP_6000 5
voice.gain.rx.digital.chassis.IP_7000 5
voice.gain.rx.digital.chassis.VVX_1500 0
voice.gain.rx.digital.ringer -21
voice.gain.rx.digital.ringer.IP_330 -12
voice.gain.rx.digital.ringer.IP_430 -12
voice.gain.rx.digital.ringer.IP_450 -12
voice.gain.rx.digital.ringer.IP_650 -12
voice.gain.rx.digital.ringer.IP_6000 -21
voice.gain.rx.digital.ringer.IP_7000 -21
voice.gain.rx.digital.ringer.VVX_1500 -21
A - 51
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Attribute Default
voice.gain.rx.analog.handset.sidetone -20
voice.gain.rx.analog.handset.sidetone.VVX_1500 -15
voice.gain.rx.analog.headset.sidetone -24
voice.gain.rx.analog.headset.sidetone.VVX_1500 -31
voice.gain.tx.analog.handset 6
voice.gain.tx.analog.handset.VVX_1500 -48
voice.gain.tx.analog.headset 3
voice.gain.tx.analog.headset.VVX_1500 -47
voice.gain.tx.analog.chassis 3
voice.gain.tx.analog.chassis.IP_330 36
voice.gain.tx.analog.chassis.IP_430 36
voice.gain.tx.analog.chassis.IP_450 36
voice.gain.tx.analog.chassis.IP_650 36
voice.gain.tx.analog.chassis.IP_6000 0
voice.gain.tx.analog.chassis.IP_7000 0
voice.gain.tx.analog.chassis.VVX_1500 -25
voice.gain.tx.digital.handset 0
voice.gain.tx.digital.handset.IP_330 10
voice.gain.tx.digital.handset.IP_430 6
voice.gain.tx.digital.handset.IP_450 6
voice.gain.tx.digital.handset.IP_650 6
voice.gain.tx.digital.handset.VVX_1500 12
voice.gain.tx.digital.headset 0
voice.gain.tx.digital.headset.IP_330 10
voice.gain.tx.digital.headset.IP_430 10
voice.gain.tx.digital.headset.IP_450 6
voice.gain.tx.digital.headset.IP_650 6
voice.gain.tx.digital.headset.VVX_1500 12
voice.gain.tx.digital.chassis 3
voice.gain.tx.digital.chassis.IP_330 12
A - 52
Configuration Files
Attribute Default
voice.gain.tx.digital.chassis.IP_430 12
voice.gain.tx.digital.chassis.IP_450 12
voice.gain.tx.digital.chassis.IP_650 12
voice.gain.tx.digital.chassis.IP_6000 6
voice.gain.tx.digital.chassis.IP_7000 6
voice.gain.tx.digital.chassis.VVX_1500 3
voice.gain.tx.analog.preamp.handset 23
voice.gain.tx.analog.preamp.headset 23
voice.gain.tx.analog.preamp.chassis 32
voice.gain.tx.analog.preamp.chassis.IP_601 32
voice.handset.rxag.adjust.IP_330 1
voice.handset.rxag.adjust.IP_430 1
voice.handset.rxag.adjust.IP_450 1
voice.handset.rxag.adjust.IP_650 1
voice.handset.txag.adjust.IP_330 18
voice.handset.txag.adjust.IP_430 18
voice.handset.txag.adjust.IP_450 18
voice.handset.txag.adjust.IP_650 18
voice.handset.sidetone.adjust.IP_330 3
voice.handset.sidetone.adjust.IP_430 3
voice.handset.sidetone.adjust.IP_450 0
voice.handset.sidetone.adjust.IP_650 0
voice.headset.rxag.adjust.IP_330 4
voice.headset.rxag.adjust.IP_430 1
voice.headset.rxag.adjust.IP_450 1
voice.headset.rxag.adjust.IP_650 1
voice.headset.txag.adjust.IP_330 21
voice.headset.txag.adjust.IP_430 21
voice.headset.txag.adjust.IP_450 21
voice.headset.txag.adjust.IP_650 21
A - 53
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Attribute Default
voice.headset.sidetone.adjust.IP_330 -3
voice.headset.sidetone.adjust.IP_430 -3
voice.headset.sidetone.adjust.IP_450 -3
voice.headset.sidetone.adjust.IP_650 -3
Attribute Default
voice.aec.hs.enable 1
voice.aec.hs.lowFreqCutOff 100
voice.aec.hs.highFreqCutOff 7000
voice.aec.hs.erlTab_0_300 -24
voice.aec.hs.erlTab_300_600 -24
voice.aec.hs.erlTab_600_1500 -24
voice.aec.hs.erlTab_1500_3500 -24
voice.aec.hs.erlTab_3500_7000 -24
voice.aec.hd.enable 0
voice.aec.hd.lowFreqCutOff 100
voice.aec.hd.highFreqCutOff 7000
voice.aec.hd.erlTab_0_300 -24
voice.aec.hd.erlTab_300_600 -24
voice.aec.hd.erlTab_600_1500 -24
voice.aec.hd.erlTab_1500_3500 -24
voice.aec.hd.erlTab_3500_7000 -24
voice.aec.hf.enable 1
voice.aec.hf.lowFreqCutOff 100
A - 54
Configuration Files
Attribute Default
voice.aec.hf.highFreqCutOff 7000
voice.aec.hf.erlTab_0_300 -6
voice.aec.hf.erlTab_300_600 -6
voice.aec.hf.erlTab_600_1500 -6
voice.aec.hf.erlTab_1500_3500 -6
voice.aec.hf.erlTab_3500_7000 -6
Attribute Default
voice.aes.hs.enable 1
voice.aes.hs.duplexBalance 7
voice.aes.hd.enable 0
voice.aes.hd.duplexBalance 0
voice.aes.hf.enable 1
voice.aes.hf.duplexBalance.0 7
voice.aes.hf.duplexBalance.1 7
voice.aes.hf.duplexBalance.2 6
voice.aes.hf.duplexBalance.3 6
voice.aes.hf.duplexBalance.4 5
voice.aes.hf.duplexBalance.5 4
voice.aes.hf.duplexBalance.6 4
A - 55
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Attribute Default
voice.aes.hf.duplexBalance.7 3
voice.aes.hf.duplexBalance.8 2
voice.aes.hf.duplexBalance.IP_4000.0 10
voice.aes.hf.duplexBalance.IP_4000.1 9
voice.aes.hf.duplexBalance.IP_4000.2 8
voice.aes.hf.duplexBalance.IP_4000.3 7
voice.aes.hf.duplexBalance.IP_4000.4 6
voice.aes.hf.duplexBalance.IP_4000.5 5
voice.aes.hf.duplexBalance.IP_4000.6 4
voice.aes.hf.duplexBalance.IP_4000.7 3
voice.aes.hf.duplexBalance.IP_4000.8 2
Attribute Default
voice.ns.hs.enable 1
voice.ns.hs.signalAttn -6
voice.ns.hs.silenceAttn -9
voice.ns.hd.enable 0
voice.ns.hd.signalAttn 0
voice.ns.hd.silenceAttn 0
voice.ns.hf.enable 1
voice.ns.hf.signalAttn -6
voice.ns.hf.silenceAttn -9
A - 56
Configuration Files
Attribute Default
voice.ns.hf.IP_4000.enable 1
voice.ns.hf.IP_4000.signalAttn -6
voice.ns.hf.IP_4000.silenceAttn -9
Attribute Default
voice.agc.hs.enable 0
voice.agc.hd.enable 0
voice.agc.hf.enable 0
Attribute Default
voice.rxEq.hs.IP_330.preFilter.enable 1
voice.rxEq.hs.IP_430.preFilter.enable 1
voice.rxEq.hs.IP_450.preFilter.enable 1
voice.rxEq.hs.IP_650.preFilter.enable 1
voice.rxEq.hs.VVX_1500.preFilter.enable 1
A - 57
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Attribute Default
voice.rxEq.hs.IP_330.postFilter.enable 0
voice.rxEq.hs.IP_430.postFilter.enable 0
voice.rxEq.hs.IP_450.postFilter.enable 0
voice.rxEq.hs.IP_650.postFilter.enable 0
voice.rxEq.hs.VVX_1500.postFilter.enable 0
voice.rxEq.hd.IP_330.preFilter.enable 0
voice.rxEq.hd.IP_430.preFilter.enable 0
voice.rxEq.hd.IP_450.preFilter.enable 0
voice.rxEq.hd.IP_650.preFilter.enable 1
voice.rxEq.hd.VVX_1500.preFilter.enable 0
voice.rxEq.hd.IP_330.postFilter.enable 0
voice.rxEq.hd.IP_430.postFilter.enable 0
voice.rxEq.hd.IP_450.postFilter.enable 0
voice.rxEq.hd.IP_650.postFilter.enable 0
voice.rxEq.hd.VVX_1500.postFilter.enable 0
voice.rxEq.hf.IP_330.preFilter.enable 1
voice.rxEq.hf.IP_430.preFilter.enable 1
voice.rxEq.hf.IP_450.preFilter.enable 1
voice.rxEq.hf.IP_650.preFilter.enable 1
voice.rxEq.hf.IP_6000.preFilter.enable 0
voice.rxEq.hf.IP_7000.preFilter.enable 0
voice.rxEq.hf.VVX_1500.preFilter.enable 1
voice.rxEq.hf.IP_330.postFilter.enable 0
voice.rxEq.hf.IP_430.postFilter.enable 0
voice.rxEq.hf.IP_450.postFilter.enable 0
voice.rxEq.hf.IP_650.postFilter.enable 0
voice.rxEq.hf.IP_6000.postFilter.enable 0
voice.rxEq.hf.IP_7000.postFilter.enable 0
voice.rxEq.hf.VVX_1500.postFilter.enable 0
A - 58
Configuration Files
Attribute Default
voice.txEq.hs.IP_330.preFilter.enable 0
voice.txEq.hs.IP_430.preFilter.enable 0
voice.txEq.hs.IP_450.preFilter.enable 0
voice.txEq.hs.IP_650.preFilter.enable 1
voice.txEq.hs.VVX_1500.preFilter.enable 0
voice.txEq.hs.IP_330.postFilter.enable 1
voice.txEq.hs.IP_430.postFilter.enable 1
voice.txEq.hs.IP_450.postFilter.enable 1
voice.txEq.hs.IP_650.postFilter.enable 1
voice.txEq.hs.VVX_1500.postFilter.enable 1
voice.txEq.hd.IP_330.preFilter.enable 0
voice.txEq.hd.IP_430.preFilter.enable 0
voice.txEq.hd.IP_450.preFilter.enable 0
voice.txEq.hd.IP_650.preFilter.enable 1
voice.txEq.hd.VVX_1500.preFilter.enable 0
voice.txEq.hd.IP_330.postFilter.enable 0
voice.txEq.hd.IP_430.postFilter.enable 0
voice.txEq.hd.IP_450.postFilter.enable 0
voice.txEq.hd.IP_650.postFilter.enable 0
voice.txEq.hd.VVX_1500.postFilter.enable 0
voice.txEq.hf.IP_330.preFilter.enable 0
voice.txEq.hf.IP_430.preFilter.enable 0
voice.txEq.hf.IP_450.preFilter.enable 0
voice.txEq.hf.IP_650.preFilter.enable 1
A - 59
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Attribute Default
voice.txEq.hf.IP_6000.preFilter.enable 0
voice.txEq.hf.IP_7000.preFilter.enable 0
voice.txEq.hf.VVX_1500.preFilter.enable 0
voice.txEq.hf.IP_330.postFilter.enable 1
voice.txEq.hf.IP_430.postFilter.enable 1
voice.txEq.hf.IP_450.postFilter.enable 1
voice.txEq.hf.IP_650.postFilter.enable 1
voice.txEq.hf.IP_6000.postFilter.enable 0
voice.txEq.hf.IP_7000.postFilter.enable 0
voice.txEq.hf.VVX_1500.postFilter.enable 1
Permitted
Attribute Values Default Interpretation
voice.vadThresh integer from 0 15 The threshold for determining what is active voice and
to 30 what is background noise in dB. This does not apply to
G.729AB codec operation which has its own built-in VAD
function.
A - 60
Configuration Files
• Server <server/>
• RTCP-XR <rtcpxr/>
Central Report Collector <collector/>
This configuration attribute is defined as follows:
Permitted
Attribute Values Default Interpretation
A - 61
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
A - 62
Configuration Files
Server <server/>
This configuration attribute is defined as follows:
Permitted
Attribute Values Default Interpretation
RTCP-XR <rtcpxr/>
This configuration attribute is defined as follows:
Permitted
Attribute Values Default Interpretation
A - 63
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Note This attribute is only supported for use on the Polycom VVX 1500.
Permitted
Attribute Values Default Interpretation
video.screenMode “normal”, “full”, normal Applies to the video window shown in the normal
“crop” mode.
If set to “normal” or Null, all pixels are displayed,
black bars appear on the top, bottom, or sides of
the window, if necessary, to maintain the correct
aspect ratio.
If set to “full”, all pixels are displayed and the
image is stretched linearly and independently to fill
the video frame.
If set to “crop”, the black bars do not appear, the
image size is re-sized to maintain the correct
aspect ratio, and any parts of the image that do not
fit in the display are cropped.
video.screenModeFS “normal”, “full”, normal Applies to the video window in Full Screen mode.
“crop” The image is re-sized to maintain the correct
aspect ratio and any parts of the image that do not
fit in the display are cropped.
A - 64
Configuration Files
Permitted
Attribute Values Default Interpretation
video.callRate 128 - 1024 448 The maximum call rate in kbps to use when initially
kbps negotiating the bandwidth for a video call.
This value cannot exceed video.maxCallRate.
video.maxCallRate 128 - 1024 512 Limits the maximum network bandwidth used in a
kbps call. It is used in the SDP bandwidth signaling.
If honored by the far end, both Rx and Tx network
bandwidth used in a call will not exceed this value
(in kbps).
If set to Null, the value 1024 is used.
A - 65
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
video.codecPref.H2631998 1 to 4 2
video.codecPref.H263 1 to 4 3
Note Codecs with a default of Null are available for test purposes only and are not
expected to be used in your deployment.
Permitted
Attribute Values Interpretation
A - 66
Configuration Files
Permitted
Attribute Values Interpretation
video.profile.H264.profileLevel 1, 1b, 1.1, 1.2, This value is H.264's level used in the phone.
1.3 (default) The Level is a constraint set to selected key
algorithm parameters, codec in different level
has different ability, at this time Polycom VVX
1500 support these level (1,1b,1.1,1.2,1.3), as
to detailed level definition. For more
information, refer to ITU-T H.264.
A - 67
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Interpretation
A - 68
Configuration Files
Permitted
Attribute Values Interpretation
A - 69
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Interpretation
Permitted
Attribute Values Default Interpretation
A - 70
Configuration Files
Permitted
Attribute Values Default Interpretation
Permitted
Attribute Values Default Interpretation
• IP TOS <IP/>
• RTP <RTP/>
A - 71
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
• Other <other/>
RTP <RTP/>
These parameters apply to RTP packets.
Permitted
Attribute Values Default Interpretation
Permitted
Attribute Values Default Interpretation
Other <other/>
These default parameter values are used for all packets which are not set
explicitly.
Permitted
Attribute Values Default Interpretation
IP TOS <IP/>
The following settings control the “type of service” field in outgoing packets:
• RTP <rtp/>
A - 72
Configuration Files
RTP <rtp/>
These parameters apply to RTP packets.
Permitted
Attribute Values Default Interpretation
A - 73
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
Permitted
Attribute Values Default Interpretation
A - 74
Configuration Files
• Port <port/>
• Keep-Alive <keepalive/>
Permitted
Attribute Values Default
tcpIpApp.netMon.enabled 0 or 1 1
tcpIpApp.netMon.period 1 to 86400 30
• Do not use fixed day, use first or last day of week in the month.
Permitted
Attribute Values Default Interpretation
A - 75
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
A - 76
Configuration Files
Permitted
Attribute Values Default Interpretation
A - 77
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Port <port/>
This attribute includes:
• RTP <rtp/>
RTP <rtp/>
This configuration attribute is defined as follows:
Permitted
Attribute Values Default Interpretation
tcpIpApp.port.rtp.mediaPortRangeStart Null, even Null If set to Null, the value 2222 will
integer from be used for the first allocated
1024-65534 RTP port, otherwise, the
specified port will be used. Ports
will be allocated from a pool
starting with the specified port up
to a value of (start-port + 47) for
a voice-only phone or (start-port
+ 95) for a video phone.
A - 78
Configuration Files
Keep-Alive <keepalive/>
Allowing for the configuration of TCP keep-alive on SIP TLS connections, the
phone can detect a failures quickly (in minutes) and attempt to re-register with
the SIP call server (or its redundant pair).
This configuration attribute is defined as follows:
Permitted
Attribute Values Default Interpretation
A - 79
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
httpd.cfg.port 1-65535 80 Port is 80 for HTTP servers. Care should be taken when
choosing an alternate port.
Permitted
Attribute Values Default Interpretation
A - 80
Configuration Files
Permitted
Attribute Values Default Interpretation
call.lastCallReturnString string of *69 The string sent to the server when the user
maximum selects the “last call return” action.
length 32
call.callsPerLineKey 1 to 24 OR 34, 24, 8 For the SoundPoint IP 650 and 670, the
1 to 8 OR 4 permitted range is 1 to 34 and the default is 34.
For the SoundPoint IP 550 and 560, the
permitted range is 1 to 24 and the default is 24.
For the SoundPoint IP 32x/33x and 430, the
permitted range is 1 to 8 and the default is 4.
For all other phones, the permitted range is 1 to
8 and the default is 8.
This is the number of calls that may be active or
on hold per line key on the phone.
Note that this may be overridden by the
per-registration attribute of
reg.x.callsPerLineKey. Refer to Registration
<reg/> on page A-134.
A - 81
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
call.transfer.blindPreferred 0,1 Null If set to 1, the blind transfer is the default mode.
The Normal soft key is available to switch to a
consultative transfer.
If set to 0 or Null, the consultative transfer is the
default mode. The Blind soft key is available to
switch to a blind transfer.
Note: This parameter is supported on the
SoundPoint IP 32x/33x only.
A - 82
Configuration Files
Permitted
Attribute Values Default Interpretation
call.directedCallPickupString star code *97 The star code to initiate a directed call pickup.
Note: The default value supports the
BroadWorks calls server only. You must change
the value if your organization uses a different call
server.
call.directedCallPickupMethod “native” or Null The method the phone will use to perform a
“legacy” directed call pick-up of a BLF resource's inbound
ringing call. “native” indicates the phone will use
a native protocol method (in this case SIP
INVITE with the Replaces header [4]). “legacy”
indicates the phone will use the method specified
in call.directedCallPickupString.
call.parkedCallRetrieveMethod “native” or Null The method the phone will use to retrieve a BLF
“legacy” resource's call which has dialog state confirmed.
“native” indicates the phone will use a native
protocol method (in this case SIP INVITE with
the Replaces header [4]). “legacy” indicates the
phone will use the method specified in
call.parkedCallRetrieveString .
call.parkedCallRetrieveString star code Null The star code used to initiate retrieve of a parked
call.
A - 83
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
call.autoRouting.preference “line” or “line If set to line, calls are placed via the first
“protocol” available line, regardless of its protocol
capabilities. If the first available line has both SIP
and H.323 capabilities, the preferred protocol will
be used preferentially
(call.autoRouting.preferredProtocol).
If set to protocol, the first available line with the
preferred protocol activated is used, if available,
and if not available, the first available line will be
used.
Note: Auto-routing is used when manual routing
selection features are disabled. Refer to User
Preferences <up/> on page A-31.
Note: This parameter is supported on the
Polycom VVX 1500 only.
call.autoRouting. “SIP or SIP If set to SIP, calls are placed via SIP if available,
preferredProtocol “H323” or via H.323 if SIP is not available.
If set to H323, calls are placed via H.323 if
available, or via SIP if H.323 is not available.
Note: This parameter is supported on the
Polycom VVX 1500 only.
Permitted
Attribute Values Default Interpretation
A - 84
Configuration Files
Permitted
Attribute Values Default Interpretation
Permitted
Attribute Values Default Interpretation
Directory <dir/>
This attribute includes:
A - 85
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
A - 86
Configuration Files
Permitted
Attribute Values Default Interpretation
A - 87
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
A - 88
Configuration Files
Permitted
Attribute Values Default Interpretation
dir.corp.attribute.x.filter UTF-8 encoded Null The filter string for this attribute,
string which is edited when searching.
A - 89
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
dir.corp.vlv.sortOrder list of attributes Null The list of attributes (in the exact
order) to be used by the LDAP
server when indexing. For example,
sn, givenName, telephoneNumber.
A - 90
Configuration Files
Permitted
Attribute Values Default Interpretation
Presence <pres/>
The parameter pres.reg is the line number used to send SUBSCRIBE. If this
parameter is missing, the phone will use the primary line to send SUBSCRIBE.
Permitted
Attribute Values Default Interpretation
Fonts <font/>
These settings control the phone’s ability to dynamically load an external font
file during boot up. Loaded fonts can either overwrite pre-existing fonts
embedded within the software (not recommended) or can extend the phone’s
A - 91
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
font support for Unicode ranges not already embedded. The font file must be
a Microsoft .fnt file format. The font file name must follow a specific pattern as
described:
• Font filename:
<fontName>_<fontHeightInPixels>_<fontRange>.<fontExtension>
• <fontRange> describes the Unicode range covered by this font. Since .fnt
are 256 characters based blocks, the <fontRange> is Uxx00_UxxFF (.fnt
file). For more information, refer to Multilingual User Interface on page
4-29.
• <fontExtension> describes the file type. Either .fnt for single 256
characters font .
If it is necessary to overwrite an existing font, use these
<fontName>_<fontHeightInPixels>:
• to overwrite the font used for SoundPoint IP 500 soft keys for ASCII, the
name should be fontPropSoftkey_10_U0000_U00FF.fnt .
• to add support for a new font that will be used everywhere and that is not
currently supported. For example, for the Eastern/Central European
Czech language, this is Unicode range 100-17F, the name could be
fontCzechIP500_10_U0100_U01FF.fnt and
fontCzechIP600_19_U0100_U01FF.fnt .
A - 92
Configuration Files
The font delimiter is important to retrieve the different scrambled .fnt blocks.
This font delimiter must be placed in the “copyright” attribute of the .fnt
header. If you are simply adding or changing a few fonts currently in use,
multiple .fnt files are recommended since they are easier to work with
individually.
This configuration attribute is defined as follows:
font.IP_330.x.name fontName_height_Uxx00_U Null Defines the font file that will be loaded from
xxFF.fnt provisioning server during boot up.
Note: When several font.IP_330.x.name
are defined, the index x must follow
consecutive increasing order.
font.IP_400.x.name fontName_height_Uxx00_U Null Defines the font file that will be loaded from
xxFF.fnt provisioning server during boot up.
Note: When several font.IP_400.x.name
are defined, the index x must follow
consecutive increasing order.
A - 93
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
font.IP_500.x.name fontName_height_Uxx00_U Null Defines the font file that will be loaded from
xxFF.fnt provisioning server during boot up.
Note: When several font.IP_500.x.name
are defined, the index x must follow
consecutive increasing order.
font.IP_600.x.name fontName_height_Uxx00 Null Defines the font file that will be loaded from
_UxxFF.fnt provisioning server during boot up.
Note: When several font.IP_600.x.name
are defined, the index x must follow
consecutive increasing order.
Keys <key/>
These settings control the scrolling behavior of keys and can be used to change
key functions.
Permitted
Attribute Values Default Interpretation
key.scrolling.timeout positive 1 The time-out after which a key that is enabled for
integer scrolling will go into scrolling mode until the key is
released. Keys enabled for scrolling are menu
navigation keys (left, right, up, down arrows), volume
keys, and some context-specific soft keys. The value is
an integer multiple of 500 milliseconds (1=500ms).
SoundPoint IP 32x/33x, 430, 450, 550, 560, 650, and 670, SoundStation IP 6000
and 7000, and Polycom VVX 1500 key functions can be changed from the
factory defaults, although this is typically not necessary. For each key whose
function you wish to change, add an XML attribute in the format described in
the following table to the <keys .../> element of the configuration file. These
will override the built-in assignments.
A - 94
Configuration Files
In the following table, x=IP_ IP_330, IP 430, IP_450, IP_550, IP_650, and
IP_6000, and IP_7000 and y is the key number. Note that IP_330 parameters
affect SoundPoint IP 32x/33x phones, IP_430 parameters affect SoundPoint IP
430 phones, IP_550 parameters affect SoundPoint IP 550 and 560 phones,
IP_650 parameters affect SoundPoint IP 650 and 670 phones, IP_6000
parameters affect the SoundStation IP 6000 phones, IP_7000 parameters affect
the SoundStation IP 7000 phones, and the VVX_1500 parameters affect the
Polycom VVX 1500 phones. IP 330: y=1-34; IP 430: y=1-35; IP_450: y=1-35;
IP_550: y=1-40; IP_650:y=1-42; IP_6000:y=1-29; IP_7000:y=1-30;
VVX_1500:y=1-42.
key.x.y.function.prim Functions listed below. Sets the function for key y on platform x.
key.x.y.subPoint.prim positive integer Sets the sub-identifier for key functions with
a secondary array identifier such as
SpeedDial.
Functions
ArrowDown Dialpad5 Line2 Select
ArrowLeft Dialpad6 Line3 Setup
ArrowRight Dialpad7 Line4 SoftKey1
ArrowUp Dialpad8 Line5 SoftKey2
BuddyStatus Dialpad9 Line6 SoftKey3
CallList DialpadStar Messages SoftKey4
Conference DialpadPound Menu SpeedDial
Delete Directories MicMute SpeedDialMenu
Dialpad0 DoNotDisturb MyStatus Transfer
Dialpad1 Handsfree Null Video
Dialpad2 Headset Offline VolDown
Dialpad3 Hold Redial VolUp
Dialpad4 Line1 Release
Backgrounds <bg/>
The backgrounds used by the SoundPoint IP 450, 550, 560, 650, and 670 and the
Polycom VVX 1500 phones are defined in this section. In the following table,
w=1 to 3, x=1 to 6. hiRes parameters are used by SoundPoint IP 550, 560, 650,
and 670 phones, medRes parameters are used by SoundPoint IP 450 phones,
and VVX_1500 parameters are used by Polycom VVX 1500 phones.
A - 95
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
bg.VVX_1500.color.selection w,x 1,1 Specify which type of background (w) and index
for that type (x) is selected on reboot where w=1
to 3, x=1 to 6.
The type of backgrounds are built-in (w=1), solids
(w=2), and bitmaps (w=3).
w=2 is used when selecting any image as a
background.
w=3 is used when selecting any image from the
Digital Picture Frame as a background. This
image is stored under “Local File”. Only one local
file at a time is supported.
bg.VVX_1500.color.bm.x.name any string Null Graphic files for display on the phone.
For example, if you set
bg.VVX_1500.color.bm.1.name to
Polycom.bmp, the user will be able to select
“Polycom.bmp” as a background on the phone.
bg.hiRes.color.selection w,x 1,1 Specify which type of background (w) and index
for that type (x) is selected on reboot where w=1
to 3, x=1 to 6.
A - 96
Configuration Files
Permitted
Attribute Values Default Interpretation
bg.hiRes.color.bm.x.name any string built-in Graphic files for display on the phone and
value of Expansion Module.
bg.hiRes.color.bm.x.em.name any string “Thistle” For x=1:
• name is “Leaf.jpg”
name is “LeafEM.jpg”
For x=2:
• name is “Sailboat.jpg”
name is “SailboatEM.jpg”
For x=3:
• name is “Beach.jpg”
name is “BeachEM.jpg”
For x=4:
• name is “Palm.jpg”
name is “PalmEM.jpg”
For x=5:
• name is “Jellyfish.jpg”
name is “JellyfishEM.jpg”
For x=6:
• name is “Mountain.jpg”
name is “MountainEM.jpg”
Note: If the file is missing or unavailable, the
built-in default solid pattern is displayed.
bg.hiRes.gray.selection w,x 2,1 Specify which type of background (w) and index
(x) for that type is selected on reboot.
A - 97
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
bg.hiRes.gray.bm.x.name any string Graphic files for display on the phone and
Expansion Module and also the brightness
bg.hiRes.gray.bm.x.em.name any string adjustment to the graphic.
bg.hiRes.gray.bm.x.adj integer For x=1:
• name is “Leaf.jpg”
name is “LeafEM.jpg”
adjustment is “0”
For x=2:
• name is “Sailboat.jpg”
name is “SailboatEM.jpg”
adjustment is “-3”
For x=3:
• name is “Beach.jpg”
name is “BeachEM.jpg”
adjustment is “0”
For x=4:
• name is “Palm.jpg”
name is “PalmEM.jpg”
adjustment is “-3”
For x=5:
• name is “Jellyfish.jpg”
name is “JellyfishEM.jpg”
adjustment is “-2”
For x=6:
• name is “Mountain.jpg”
name is “MountainEM.jpg”
adjustment is “0”
Note: If the file is missing or unavailable, the
built-in default solid pattern is displayed.
Note: The adjustment value is changed on each
individual phone when the user lightens or
darkens the graphic during preview.
bg.medRes.gray.selection w,x 2,1 Specify which type of background (w) and index
(x) for that type is selected on reboot.
A - 98
Configuration Files
Permitted
Attribute Values Default Interpretation
bg.medRes.gray.bm.x.name any string Graphic files for display on the phone and
Expansion Module and also the brightness
bg.medRes.gray.bm.x.em. any string adjustment to the graphic.
name
For x=1:
bg.medRes.gray.bm.x.adj integer • name is “Leaf256x116.jpg”
adjustment is “0”
For x=2:
• name is “Sailboat256x116.jpg”
adjustment is “-3”
For x=3:
• name is “Beach256x116.jpg”
adjustment is “0”
For x=4:
• name is “Palm256x116.jpg”
adjustment is “-3”
For x=5:
• name is “Jellyfish256x116.jpg”
adjustment is “-2”
For x=6:
• name is “Mountain256x116.jpg”
adjustment is “0”
Note: If the file is missing or unavailable, the
built-in default solid pattern is displayed.
Note: The adjustment value is changed on each
individual phone when the user lightens or
darkens the graphic during preview.
button.color.selection.x.y. any string The label color for soft keys and line key labels
modify associated with the defined colored backgrounds.
These values can be modified locally by the user.
The format is:
“rgbHILo, <parameter list>”.
For example:
“rbgHiLo, 51, 255, 68, 255, 0, 119” is the default
button color associated with the built-in
background.
button.gray.selection.x.y. any string The label color for soft keys and line key labels
modify associated with the defined gray backgrounds.
These values can be modified locally by the user.
The format is:
“rgbHILo, <parameter list>”.
By default, all defaults are set to “none”.
A - 99
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Bitmaps <bitmap/>
The bitmaps used by each phone model are defined in this section.
bitmap.x.y.name The name of a bitmap This is the name of a bitmap to be used for creating an
to be used. animation. If the bitmap is to be downloaded from the
provisioning server, its name must:
• Be different from any name already in use in sip.cfg.
• Match the name of the corresponding <fileName>.bmp to
be retrieved from the provisioning server.
Indicators <ind/>
The following indicators are used by the phone:
• Patterns <pattern/>
• Classes <class/>
• Assignments
A - 100
Configuration Files
Permitted
Attribute Values Default Interpretation
A - 101
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Patterns <pattern/>
This section defines patterns for the LED indicators. In the following table, x is
the pattern number, y is the step in the pattern.
Permitted
Attribute Values Interpretation
Classes <class/>
This section defines the available classes for the LED and graphical icon
indicator types. In the following table, x is the class number, y is the identifier
of the state number for that class.
Permitted
Attribute Values Interpretation
ind.class.x.state.y.index positive integer For LED type indicators, index refers to the pattern index,
such as index x in the Patterns <pattern/> tag above.
For Graphic Icon type indicators, index refers to the
animation index, such as index y in the Animations <anim/>
<IP_330/>, <IP_335/>, <IP_400/>, <IP_450/>, <IP_600/>,
<IP_4000/>, and <IP_7000/> tag above.
Assignments
This attribute assigns a type and a class to an indicator. In the case of the
Graphic Icon type, it also assigns a physical location and size in pixels on the
LCD display (refer to the next section). In the case of the LED type, it assigns a
physical LED number (refer to Graphic Icons <gi/> <IP_330>, <IP_400/>,
<IP_450/>, <IP_600/>, <IP_4000/>, and <IP_7000/> on page A-103).
A - 102
Configuration Files
LEDs <led/>
In the following table, x is the LED number.
Permitted
Attribute Values Interpretation
ind.led.x.index This is for internal usage only and should not be changed (this is
the logical index).
ind.led.x.class positive integer Assigns the class (defined in Classes <class/> on page A-102) for
this indicator.
Permitted
Attribute Values Interpretation
ind.gi.x.y.index This is for internal usage only and should not be changed (this is
the logical index).
ind.gi.x.y.class positive integer Assigns the class (defined in Classes <class/> on page A-102) for
this indicator.
ind.gi.x.y.physX IP 330: 0-101 For Graphic Icon type indicators, this is the x-axis location of the
IP 400: 0-122 upper left corner of the indictor measured in pixels from left to
right.
IP 450: 0-238
IP 600: 0-319
IP 4000: 0-247
IP 7000: 0-255
A - 103
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Interpretation
ind.gi.x.y.physY IP 330: 0-19 For Graphic Icon type indicators, this is the y-axis location of the
IP 400: 0-45 upper left corner of the indicator measured in pixels from top to
bottom.
IP 450: 0-89
IP 600: 0-159
IP 4000: 0-67
IP 7000: 0-127
ind.gi.x.y.physW IP 330: 1-87 For Graphic Icon type indicators, this is the width of the indicator
IP 400: 1-102 measured in pixels.
IP 450: 1-170
IP 600: 1-320
IP 4000: 1-248
IP 7000: 1-256
ind.gi.x.y.physH IP 330: 1-20 For Graphic Icon type indicators, this is the height of the indicator
IP 400: 1-23 measured in pixels.
IP 450: 1-73
IP 600: 1-160
IP 4000: 1-68
IP 7000: 1-128
Warning Logging parameter changes can impair system operation. Do not change any
logging parameters without prior consultation with Polycom Technical Support.
Level Interpretation
0 Debug only
1 High detail event class
2 Moderate detail event class
3 Low detail event class
4 Minor error - graceful recovery
5 Major error - will eventually incapacitate the system
6 Fatal error
A - 104
Configuration Files
Each event in the log contains the following fields separated by the | character:
• event class
Example:
011511.006|so |2|00|soCoreAudioTermChg: chassis -> idle
time stamp
ID
event class
missed events
text
Three formats are available for the event timestamp:
Type Example
1 - absolute time with minute resolution 0210281716 -- 2002 October 28, 17:16
A - 105
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
log.render.realtime 0 or 1 1 Set to 1.
Note: Polycom recommends that
you do not change this value.
log.render.stdout 0 or 1 1 Set to 1.
Note: Polycom recommends that
you do not change this value.
log.render.file 0 or 1 1 Set to 1.
Note: Polycom recommends that
you do not change this value.
A - 106
Configuration Files
Permitted
Attribute Values Default Interpretation
log.render.file.upload.append.limitMode delete, stop delete Behavior when server log file has
reached its limit.
delete=delete file and start over
stop=stop appending to file
Permitted
Attribute Values Interpretation
log.sched.x.level 0-5 Event class to assign to the log events generated by this command.
This needs to be the same or higher than log.level.change.slog for
these events to appear in the log.
A - 107
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Interpretation
log.sched.x.startTime positive Seconds since boot when startMode is rel or the start time in 24-hour
integer OR clock format when startMode is abs.
hh:mm
log.sched.x.startDay 1-7 When startMode is abs, specifies the day of the week to start
command execution. 1=Sun, 2=Mon, ..., 7=Sat
Security <sec/>
This attribute’s settings affect security aspects of the phone.
This configuration attribute is defined as follows:
.
Permitted
Attribute Values Default Interpretation
sec.tagSerialNo 0 or 1 Null If set to 1, the phone may advertise its serial number
(Ethernet address) through protocol signaling.
If set to 0 or Null, the phone does advertise its serial
number.
• Encryption <encryption/>
• SRTP <srtp/>
• H.235 <H235/>
A - 108
Configuration Files
Encryption <encryption/>
This configuration attribute is defined as follows:
Permitted
Attribute Values Default Interpretation
Permitted
Attribute Values Default Interpretation
A - 109
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
SRTP <srtp/>
Note As per RFC 3711, you cannot turn off authentication of RTCP.
Permitted
Attribute Values Default Interpretation
A - 110
Configuration Files
Permitted
Attribute Values Default Interpretation
sec.srtp.key.lifetime 0, positive Null The master key lifetime used for the cryptographic
integer attribute in the SDP. The value specified is the
minimum 1024 number of SRTP packets.
If set to 0 or Null, the master key lifetime is not set.
If set to 1 or greater, master key lifetime is set.
The default setting should be suitable for most
installations. When the lifetime is set greater than 0,
a re-invite with a new key will be sent when the
number of SRTP packets sent for an outgoing call
exceeds half the value of the master key lifetime.
Note: Setting this parameter to a non-zero value
may affect performance of the phone.
A - 111
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
H.235 <H235/>
Note At this time, this attribute is used with the Polycom VVX 1500 phone only.
The H.235 Voice Profile implementation is Polycom HDX-compatible.
OpenSSL-based Diffie-Hellman key exchange and AES-128 CBC encryption
algorithms is used to encrypt the RTP media
A - 112
Configuration Files
Permitted
Attribute Values Default Interpretation
License <license/>
This attribute’s settings control aspects of the feature licensing system.
This configuration attribute is defined as follows:
Permitted
Attribute Values Default Interpretation
license.polling.time 00:00 – 23:59 2:00am The time to check whether or not the license has
expired.
A - 113
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Provisioning <prov/>
This attribute’s settings control aspects of the phone’s provisioning server
provisioning system.
Permitted
Attribute Values Default Interpretation
A - 114
Configuration Files
Permitted
Attribute Values Default Interpretation
ramdisk.bytesPerBlock 0, 32, 33, ..., 0 These four parameters use internal defaults when
1024 value is set to 0.
Note: For the SoundPoint IP 650 phone,
ramdisk.blocksPerTrack 0, 1, 2, ..., 0
ramdisk.bytesPerBlock is internally replaced by 2X
65536
the value.
ramdisk.nBlocks 0, 1, 2, ..., 4096 Note: For the SoundPoint IP 7000 phone,
65536 ramdisk.bytesPerBlock is internally replaced by 4X
the value.
ramdisk.nBlocks.IP_650 0, 1, 2, ..., 2048
65536
ramdisk.minfree 512 to 16384 3150 Minimum amount of free space that must be left
after the RAM disk has been created. The RAM
disk’s size will be reduced as necessary in order to
leave this amount of free RAM.
Request <request/>
This attribute includes:
• Delay <delay/>
A - 115
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Delay <delay/>
These settings control the phone’s behavior when a request for restart or
reconfiguration is received.
Permitted
Attribute Values Default Interpretation
request.delay.type Null, “audio”, or call Defines the strategy to adopt before a request gets
“call” executed. If set to “audio”, a request can be executed as
soon as there is no active audio on the phone,
independently of any call state. If set to “call”, a request
can be executed as soon as there are no calls in any
state on the phone.
Feature <feature/>
These settings control the activation or deactivation of a feature at run time. In
the table below, x is the feature number.
A - 116
Configuration Files
A - 117
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Resource <res/>
This attribute’s settings control the maximum size or an external resource
retrieved at run time.
For more information, refer to “Technical Bulletin 35704: Allocating Adequate
Memory for resources on SoundPoint IP and SoundStation IP Phones“ at
http://www.polycom.com/usa/en/support/voice/soundpoint_ip/VoIP_T
echnical_Bulletins_pub.html .
This attribute also includes:
• Finder <finder/>
• Quotas <quotas/>
Finder <finder/>
This configuration attribute is defined as follows:
Permitted
Attribute Values Default Interpretation
res.finder.minfree 1 to 2048 600 A resource will not be downloaded to the phone if the
amount of free memory is less than this value * 1024
bytes (= the minimum size). This parameter is used
for 16MB SDRAM platforms and scaled up for
platforms with more SDRAM.
If set to 0 or Null, the default value of 600 is used.
Note: For the SoundPoint IP 550, 560, 650, and 670
phones, this value is internally replaced by 2X the
value. For the SoundStation IP 6000 and 7000
phones, this value is internally replaced by 4X the
value.
A - 118
Configuration Files
Quotas <quotas/>
This configuration attribute is defined as follows:
Permitted
Attribute Values Interpretation
res.quotas.x.name 1=“tone”, The name of the sub-application for which the particular quota
2= “bitmap”, will apply:
3=“font”, “tone” relates to all downloaded tones and sound effects
5=”background”
“bitmap” relates to all downloaded bitmaps
“font” relates to all downloaded fonts
“background” relates to all downloaded backgrounds
res.quotas.x.value positive integer When a particular resource (one of category “font”, “bitmap”, or
“font”) is downloaded to the phone, a quota equal to this value
* 1024 bytes of compound data size is applied for that
category. If downloading a resource would exceed the quota
for that category, the resource will not be downloaded and a
predefined default will be used instead.
For res.quotas.x.value, the default is 300 KB for tones,
10 KB for bitmaps and fonts, and 600KB for backgrounds.
Note: For the SoundPoint IP 550, 560, 650, and 670 phones,
this value is internally replaced by 2X the value. For the
SoundStation IP 6000 and 7000 phones, this value is internally
replaced by 4X the value.
Microbrowser <mb/>
This attribute’s settings control the home page, proxy and size limits to be used
by the Microbrowser and Browser when it is selected to provide services. The
Microbrowser is supported on the SoundPoint IP 430, 450, 550, 560, 601, 650,
and 670, and the SoundStation IP 6000 and 7000 phones, and the Browser is
supported on the Polycom VVX 1500 phones.
This configuration attribute is defined as follows:
A - 119
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
mb.ssawc.call.mode Active, Passive Null Control the spontaneous display of web content.
If set to passive or Null, the web content is
displayed only when requested by the user.
If set to active, the web content is displayed
immediately.
mb.idleDisplay.home Null or any fully Null URL used for Microbrowser idle display home
formed valid HTTP page. For example:
URL. Length up to http://www.example.com/xhtml/frontpage.cgi?pa
255 characters. ge=home. If empty, there will be no
Microbrowser idle display feature. Note that the
Microbrowser idle display will displace the idle
display indicator (refer to
ind.idleDisplay.enabled in Indicators <ind/>
on page A-100).
Note: If ind.idleDisplay.enabled is enabled,
miscellaneous XML errors can occur on
SoundPoint IP 430, 550, 560, 650, and 670 and
SoundStation IP 6000 and 7000 phones.
A - 120
Configuration Files
mb.main.home Any fully formed valid Null URL used for Microbrowser home page. If blank,
HTTP URL. Length the browser will notify the user that a blank
up to 255 characters. home-page was used.
For example:
http://www.example.com/xhtml/frontpage.cgi?pa
ge=home.
mb.main.idleTimeout 0 - 600, seconds Null Timeout for the interactive browser. If the
interactive browser remains idle for a defined
period of time, the phone should return to the
idle browser.
If set to 0, there is no timeout.
If set to Null, the value from up.idleTimeout is
used. Refer to User Preferences <up/> on page
A-31. If mb.main.idleTimeout and
up.idleTimeout are Null, the timeout is 40
seconds.
If set to value greater than 0 and less than 600,
the timeout is for that number of seconds.
A - 121
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
mb.limits.nodes positive integer 256 Limits the number of tags that the XML parser
will handle. This limits the amount of memory
used by complicated pages. A maximum total of
500 (256 each) is recommended. This value is
used as referent values for 16MB of SDRAM.
Note: Increasing this value may have a
detrimental effect on performance of the phone.
mb.limits.cache positive integer 200 Limits the total size of objects downloaded for
each page (both XHTML and images). Once this
limit is reached, no more images are
downloaded until the next page is requested.
Units = kBytes. This value is used as referent
values for 16MB of SDRAM.
Note: Increasing this value may have a
detrimental effect on performance of the phone.
Applications <apps/>
This attribute’s settings control the telephone notification events, state polling
events, and the push server controls. For more information, refer to the Web
Application Developer’s Guide, which can be found at
http://www.polycom.com/voicedocumentation/.
This attribute also includes:
• Push <push/>
A - 122
Configuration Files
apps.telNotification.URL URL Null The URL to which the phone sends notifications
of specified events. The protocol used can be
either HTTP or HTTPS.
apps.statePolling.URL URL Null The URL to which the phone sends call
processing state/device/network information.
The protocol used can be either HTTP or
HTTPS.
Note: To enable state polling, the attributes
apps.statePolling.URL,
apps.statePolling.username, and
apps.statePolling.password must be set to
non-Null values.
apps.statePolling. string Null The user name to access the state polling URL..
username
apps.statePolling. string Null The password to access the state polling URL.
password
A - 123
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Push <push/>
This configuration attribute is defined as follows:
apps.push. URL Null The relative URL (received from HTTP URL
serverRootURL Push message) is appended to the application
server root URL and the resultant URL is sent to
the Microbrowser.
For example, if the application server root URL
is http://172.24.128.85:8080/sampleapps and
the relative URL is /examples/sample.html, the
URL that is sent to the Microbrowser is
http://172.24.128.85:8080/sampleapps/example
s/sample.html.
The protocol used can be either HTTP or
HTTPS.
apps.push.username string Null The user name to access the push server URL.
Note: To enable the push functionality, the
attributes apps.push.username and
apps.push.password must be set to non-Null
values.
apps.push.password string Null The password to access the push server URL.
A - 124
Configuration Files
A - 125
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
• SRV <SRV/>
• A <A/>
NAPTR <NAPTR/>
This configuration attribute is defined as follows:
dns.cache.NAPTR.x. domain name string Null The domain name to which this resource record
name refers.
dns.cache.NAPTR.x.ttl 300 to 65535 300 Specifies the time interval (in seconds) that the
resource record may be cached before the
source of the information should again be
consulted.
A - 126
Configuration Files
dns.cache.NAPTR.x. domain name string Null The next name to query for NAPTR, SRV, or
replacement with SRV prefix address records depending on the value of the
flags field. It must be a fully qualified
domain-name.
SRV <SRV/>
This configuration attribute is defined as follows:
dns.cache.SRV.x.name domain name string Null The domain name string with SRV prefix.
dns.cache.SRV.x.ttl 0 to 65535, seconds 300 Specifies the time interval that the resource
record may be cached before the source of the
information should again be consulted.
dns.cache.SRV.x.port 0 to 65535 0 The port on this target host of this service. For
more information, go to
http://tools.ietf.org/html/rfc2782 .
dns.cache.SRV.x.target domain name string Null The domain name of the target host. For more
information, go to
http://tools.ietf.org/html/rfc2782 .
A - 127
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
A <A/>
This configuration attribute is defined as follows:
dns.cache.A.x.ttl 0 to 65535 300 Specifies the time interval that the resource
record may be cached before the source of the
information should again be consulted.
Permitted
Attribute Values Default Interpretation
softkey.x.label string Null This is the text displayed with the soft key.
If set to Null, the label to display is
determined as follows:
• If the soft key is mapped to a enhanced
feature key macro, the label of the
enhanced feature key macro will be
used.
• If the soft key is mapped to a speed
dial, the label of the corresponding
directory entry will be used. If this label
does not exist as well and the directory
entry is a enhanced feature key macro,
then the label of the enhanced feature
key macro will be used.
• If the soft key is mapped to chained
actions, only the first one is considered
for label, using the rules above.
• If no labels are found after the above
steps, the soft key label will be blank.
A - 128
Configuration Files
Permitted
Attribute Values Default Interpretation
softkey.x.precede 0 (default) Null If set to 0 or Null, the soft key replaces any
1 empty space from the leftmost position.
If set to 1, the soft key is displayed before
the first standard soft key.
A - 129
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
A - 130
Configuration Files
Permitted
Attribute Values Default Interpretation
A - 131
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
A - 132
Configuration Files
Permitted
Attribute Values Default Interpretation
Per-Phone Configuration
This section covers the parameters in the per-phone example configuration file
phone1.cfg. This file would normally be used as a template for the per-phone
configuration files. For more information, refer to Deploying Phones From the
Provisioning Server on page 3-17.
Polycom recommends that you create another file with your organization’s
modifications. If you must change any Polycom templates, back them up first.
For more information, refer to the “Configuration File Management on SoundPoint
IP, SoundStation IP, and Polycom VVX 1500 Phones” white paper at
http://www.polycom.com/global/documents/support/technical/products/voice/white_
paper_configuration_file_management_on_soundpoint_ip_phones.pdf .
• Registration <reg/>
• Calls <call/>
• Diversion <divert/>
• Messaging <msg/>
• Attendant <attendant/>
A - 133
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Registration <reg/>
SoundPoint IP 32x/33x and 430 support a maximum of two unique
registrations, SoundPoint IP 450 supports three, the SoundPoint IP 550 and 560
supports four, and SoundPoint IP 650 and 670 and the Polycom VVX 1500
support six. Up to three SoundPoint IP Expansion Modules can be added to a
single host SoundPoint IP 650 and 670 phone increasing the total number of
buttons to 34 registrations on the IP 650 and 670. Each registration can
optionally be associated with a private array of servers for completely
segregated signaling. The SoundStation IP 6000, and 7000 supports a single
registration.
In the following table, x is the registration number. IP 32x/33x, 430: x=1-2; IP
450: x=1-3; IP 550, 560: x=1-4; VVX 1500: x=1-6; IP 650, 670: x=1-34; IP 6000: x=1;
IP 7000: x=1.
Permitted
Attribute Values Default Interpretation
reg.x.displayName UTF-8 encoded Null Display name used in SIP signaling as the
string default caller ID.
Display name used in SIP signaling and/or
H.323 alias as the default caller ID.
reg.x.address string in the format Null The user part or the user and the host part of
userPart from the phone’s SIP URI or the H.323
userPart@domain ID/extension.
For example (SIP): reg.x.address=”1002”
from 1002@polycom.com or
reg.x.address=”1002@polycom.com”.
For example (H.323): reg.x.address=”23456”
reg.x.label UTF-8 encoded Null Text label to appear on the display adjacent
string to the associated line key. If omitted, the label
will be derived from the user part of
reg.x.address.
A - 134
Configuration Files
Permitted
Attribute Values Default Interpretation
reg.x.type private OR shared private If set to private, use standard call signaling.
If set to shared, augment call signaling with
call state subscriptions and notifications and
use access control for outgoing calls.
reg.x.thirdPartyName string in the same Null This field must match the reg.x.address
format as value of the other registration which makes
reg.x.address up the bridged line appearance (BLA). It must
be Null in all other cases.
A - 135
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
A - 136
Configuration Files
Permitted
Attribute Values Default Interpretation
A - 137
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
reg.x.musicOnHold.uri string Null A URI that provides the media stream to play
for the remote party on hold.
When present, and if reg.x.musicOnHold is
not Null, this attribute overrides the global
Music on Hold defined in the sip.cfg
configuration file.
A - 138
Configuration Files
Permitted
Attribute Values Default Interpretation
Calls <call/>
This attribute affects the call-oriented per-phone configuration.
This attribute includes:
A - 139
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
A - 140
Configuration Files
Permitted
Attribute Values Default Interpretation
Permitted
Attribute Values Default Interpretation
A - 141
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
call.callWaiting.ring beep, ring, beep Specifies the ring tone heard on an incoming
silent call when another call is active.
If set to Null, the default value is beep.
Diversion <divert/>
The phone has a flexible call forward/diversion feature for each registration.
In all cases, a call will only be diverted if a non-Null contact has been
configured.
In the following table, x is the registration number. IP 32x/33x, 430: x=1-2; IP
450: x=1-3; IP 550, 560: x=1-4; VVX 1500: x=1-6; IP 650, 670: x=1-34; IP 6000: x=1;
IP 7000: x=1.
divert.x.contact ASCII encoded string Null The forward-to contact used for
containing digits (the user all automatic call diversion
part of a SIP URL) or a string features unless overridden by a
that constitutes a valid SIP specific contact of a per-call
URL (6416 or diversion feature (refer to
6416@polycom.com below).
• Busy <busy/>
• No Answer <noanswer/>
A - 142
Configuration Files
Permitted
Attribute Values Default Interpretation
Busy <busy/>
Calls can be automatically diverted when the phone is busy.
A - 143
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
No Answer <noanswer/>
The phone can automatically divert calls after a period of ringing.
divert.dnd.x.contact ASCII encoded string containing digits Null Forward-to contact used for
(the user part of a SIP URL) or a string calls forwarded due to DND
that constitutes a valid SIP URL (6416 or status, if Null
6416@polycom.com) divert.x.contact will be
used.
A - 144
Configuration Files
Permitted
Attribute Values Default Interpretation
A - 145
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
• Routing <routing/>
A - 146
Configuration Files
Permitted
Attribute Values Default Interpretation
dialplan.x.digitmap A string compatible with the Null When present, this attribute
digit map feature of MGCP overrides the global dial plan
described in 2.1.5 of RFC defined in the sip.cfg
3435; string is limited to 768 configuration file.
bytes and 30 segments; a For more information, refer to
comma is also allowed; a Digit Map <digitmap/> on page
comma is also allowed; A-24.
when reached in the digit
map, a comma will turn dial
tone back on;’+’ is allowed
as a valid digit; extension
letter ‘R’ is used as defined
above.
Routing <routing/>
This attribute allows specific routing paths for outgoing SIP calls to be
configured independent of other ‘default’ configuration.
This attribute includes:
• Server <server/>
• Emergency <emergency/>
A - 147
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Server <server/>
This configuration attribute is defined as follows:
Emergency <emergency/>
In the following attributes, y is the index of the emergency entry description
and z is the index of the server associated with the emergency entry y. For each
emergency entry (index y), one or more server entry (indexes (y,z)) can be
configured. y and z must both follow single step increasing numbering starting
at 1.
This configuration attribute is defined as follows:
A - 148
Configuration Files
Messaging <msg/>
Message-waiting indication is supported on a per-registration basis.
This configuration attribute is defined as follows:
Permitted
Attribute Values Default Interpretation
A - 149
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
msg.mwi.x.subscribe ASCII encoded string containing Null If non-Null, the phone will send
digits (the user part of a SIP a SUBSCRIBE request to this
URL) or a string that constitutes contact after boot-up.
a valid SIP URL (6416 or
6416@polycom.com)
msg.mwi.x.callBack ASCII encoded string containing Null Contact to call when retrieving
digits (the user part of a SIP messages for this registration.
URL) or a string that constitutes
a valid SIP URL (6416 or
6416@polycom.com)
A - 150
Configuration Files
Permitted
Attribute Values Default Interpretation
nat.signalPort 1024 to 65535 Null If non-Null, this port will be used by the phone for SIP
signaling, overriding the value set for
voIpProt.local.Port in sip.cfg.
nat.mediaPortStart 1024 to 65535 Null If non-Null, this attribute will be used to set the initially
allocated RTP port, overriding the value set for
tcpIpApp.port.rtp.mediaPortRangeStart in sip.cfg.
Refer to RTP <rtp/> on page A-78.
nat.keepalive.interval 0 to 3600 Null If non-Null (or 0), the keepalive interval in seconds. This
parameter is used to set the interval at which phones will
send a keep-alive packet to the gateway/NAT device to
keep the communication port open so that NAT can
continue to function as setup initially.
The Microsoft Live Communications Server 2005
keepalive feature will override this interval. If you want to
deploy phones behind a NAT and connect them to Live
Communications Server, the keepalive interval received
from the Live Communications Server must be short
enough to keep the NAT port open. Once the TCP
connection is closed, the phones stop sending keep-alive
packets.
Attendant <attendant/>
Note These attributes are available on SoundPoint IP 32x/33x, 430, 450, 550, 560, 650,
and 670 phones only.
The Busy Lamp Field (BLF) / attendant console feature enhances support for
a phone-based attendant console.
A - 151
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
attendant.uri string Null For attendant console / busy lamp field (BLF) feature.
This specifies the list SIP URI on the server. If this is just
a user part, the URI is constructed with the server host
name/IP.
Note: If attendant.uri is set, then the individually
addressed users configured by
attendant.resourceList and attendant.behaviors
attributes are ignored.
attendant.reg positive 1 For attendant console / BLF feature. This is the index of
integer the registration which will be used to send a SUBSCRIBE
to the list SIP URI specified in attendant.uri. For example,
attendant.reg = 2 means the second registration will
be used.
attendant.ringType 1 to 22 1 The ring tone to play when a BLF dialog is in the offering
state.
• Behaviors <behaviors/>
A - 152
Configuration Files
Behaviors <behaviors/>
This configuration attribute is defined as follows:
A - 153
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
roaming_buddies.reg positive Null Specifies the line/registration number which has roaming
integer buddies support enabled. If Null, roaming buddies is
disabled. If value < 1, then value is replaced with 1.
Warning: This parameter must be enabled
(value > 0) if the call server is Microsoft Live
Communications Server 2005.
Permitted
Attribute Values Default Interpretation
roaming_privacy.reg positive Null Specifies the line/registration number which has roaming
integer privacy support enabled. If Null, roaming privacy is
disabled. If value < 1, then value is replaced with 1.
A - 154
Configuration Files
Permitted
Attribute Values Default Interpretation
up.pictureFrame.folder string Null The path name for images. The maximum length is 40
characters.
If set to Null, images stored in the root folder on the
USB flash drive are displayed.
For example, if the images are stored in the
“/images/phone” folder on the USB flash drive, set
up.pictureFrame.folder to images/phone .
Note: This parameter is supported on the
Polycom VVX 1500 only.
A - 155
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Permitted
Attribute Values Default Interpretation
up.screenSaver.waitTime 1 to 9999 Null The time to wait (In minutes) in the idle state (until the
screen saver starts).
If set to Null, the default time is 15 minutes.
Note: This parameter is supported on the
Polycom VVX 1500 only.
Permitted
Attribute Values Default Interpretation
A - 156
Configuration Files
Warning The parameters for this feature should be put in separate configuration files to
simplify maintenance. Do not add them to existing configuration files (such as
sip.cfg). One new configuration file will be required for parameters that should
apply to all phones, and individual configuration files will be required for
phone-specific parameters such as SIP registration information.
Warning This feature is very powerful and should be used with caution. For example, an
incorrect setting could set the IP Address of multiple phones to the same value.
Note that some parameters may be ignored, for example if DHCP is enabled it will
still override the value set with device.net.ipAddress.
Individual parameters are checked to see whether they are in range, however, the
interaction between parameters is not checked. If a parameter is out of range, an
error message will appear in the log file and parameter will not be used.
Incorrect configuration could cause phones to get into a reboot loop. For example,
server A has a configuration file that specifies that server B should be used, which
has a configuration file that specifies that server A should be used.
Polycom recommends that you test the new configuration files on two phones
before initializing all phones. This should detect any errors including IP address
conflicts.
A - 157
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
device.dhcp. 0 or 1
bootSrvOptType
device.dhcp. 0 to 2
dhcpVlanDiscUseOpt
A - 158
Configuration Files
device.prov.serverName any string For descriptions, refer to Server Menu on page 3-10.
device.prov.serverType 0 to 4
device.prov.appProvType 0 or 1
device.prov. 1 to 8
maxRedunServers
device.dns.serverAddress dotted-decimal IP address Primary server to which the phone directs Domain
Name System queries.
device.dns.altSrvAddress dotted-decimal IP address Secondary server to which the phone directs Domain
Name System queries.
device.auth.regUserx any string The SIP registration user name for registration x
where x = 1 to 48.
A - 159
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
device.syslog.transport None=0, The protocol that the phone will use to write to the
UDP=1, syslog server.
TCP=2, If set to “None”, transmission is turned off, but the
TLS=3 server address is preserved.
device.em.power Enabled, Disabled, Null Refer to the EM Power parameter in Main Menu on
page 3-7.
A - 160
B
Session Initiation Protocol (SIP)
• Request Support
• Header Support
• Response Support
• Hold Implementation
• Transfer
B-1
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
• RFC 3725—Best Current Practices for Third Party Call Control (3pcc) in
the Session Initiation Protocol (SIP)
• RFC 3856—A Presence Event Package for Session Initiation Protocol (SIP)
• RFC 3959—The Early Session Disposition Type for the Session Initiation
Protocol (SIP)
B-2
Session Initiation Protocol (SIP)
Request Support
The following SIP request messages are supported:
REGISTER Yes
INVITE Yes
ACK Yes
CANCEL Yes
BYE Yes
OPTIONS Yes
SUBSCRIBE Yes
NOTIFY Yes
REFER Yes
PRACK Yes
B-3
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
INFO Yes RFC 2976, the phone does not generate INFO
requests, but will issue a final response upon
receipt. No INFO message bodies are parsed.
UPDATE Yes
Header Support
The following SIP request headers are supported:
Note In the following table, a “Yes” in the Supported column means the header is sent
and properly parsed.
Accept Yes
Accept-Encoding No
Accept-Language Yes
Access-Network-Info No
Alert-Info Yes
Allow Yes
Allow-Events Yes
Authentication-Info No
Authorization Yes
Call-ID Yes
Call-Info Yes
Contact Yes
Content-Disposition No
Content-Encoding No
Content-Language No
Content-Length Yes
Content-Type Yes
CSeq Yes
B-4
Session Initiation Protocol (SIP)
Date No
Diversion Yes
Error-Info No
Event Yes
Expires Yes
From Yes
In-Reply-To No
Max-Forwards Yes
Min-Expires No
Min-SE Yes
MIME-Version No
Organization No
P-Asserted-Identity Yes
P-Preferred-Identity Yes
Priority No
Privacy No
Proxy-Authenticate Yes
Proxy-Authorization Yes
Proxy-Require Yes
RAck Yes
Record-Route Yes
Refer-To Yes
Referred-By Yes
Referred-To Yes
Remote-Party-ID Yes
Replaces Yes
Reply-To No
Requested-By No
Require Yes
Response-Key No
B-5
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Retry-After Yes
Route Yes
RSeq Yes
Server Yes
Session-Expires Yes
Subject Yes
Subscription-State Yes
Supported Yes
Timestamp Yes
To Yes
Unsupported Yes
User-Agent Yes
Via Yes
WWW-Authenticate Yes
Response Support
The following SIP responses are supported:
Note In the following table, a “Yes” in the Supported column means the header is sent
and properly parsed. The phone may not actually generate the response.
182 Queued No
B-6
Session Initiation Protocol (SIP)
200 OK Yes
Note All 4xx responses for which the phone does not provide specific support will be
treated the same as 400 Bad Request.
403 Forbidden No
410 Gone No
B-7
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
485 Ambiguous No
493 Undecipherable No
B-8
Session Initiation Protocol (SIP)
Hold Implementation
The phone supports both currently accepted means of signaling hold.
The first method, no longer recommended due in part to the RTCP problems
associated with it, is to set the “c” destination addresses for the media streams
in the SDP to zero, for example, c=0.0.0.0.
The second, and preferred, method is to signal the media directions with the
“a” SDP media attributes sendonly, recvonly, inactive, or sendrecv. The hold
signaling method used by the phone is configurable (refer to SIP <SIP/>on
page A-11), but both methods are supported when signaled by the remote end
point.
Note Even if the phone is set to use c=0.0.0.0, it will not do so if it gets any sendrecv,
sendonly, or inactive from the server. These flags will cause it to revert to the other
hold method.
Transfer
The phone supports transfer using the REFER method specified in
draft-ietf-sip-cc-transfer-05 and RFC 3515.
B-9
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
The phone is compliant with “Using CSTA for SIP Phone User Agents
(uaCSTA), ECMA TR/087” for the Answer Call, Hold Call, and Retrieve Call
functions and “Services for Computer Supported Telecommunications
Applications Phase III”, ECMA – 269 for the Conference Call function.
This feature is enabled by configuration parameters described in SIP <SIP/>
on page A-11 and Registration <reg/> on page A-134 and needs to be
activated by a feature application key.
• draft-ietf-simple-cpim-mapping-01
• draft-ietf-simple-presence-07
• draft-ietf-simple-presencelist-package-00
• draft-ietf-simple-winfo-format-02
• draft-ietf-simple-winfo-package-02
B - 10
C
Miscellaneous Administrative Tasks
C-1
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
• American Express CA
• Equifax Premium CA
• Equifax Secure CA
• GeoTrust Global CA
• GeoTrust Global CA 2
• GeoTrust Universal CA
• GeoTrust Universal CA 2
C-2
Miscellaneous Administrative Tasks
• GlobalSign Partners CA
• GlobalSign Root CA
• Thawte Server CA
• ValiCert Class 1 VA
• ValiCert Class 2 VA
• ValiCert Class 3 VA
C-3
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
• Verisign/RSA Commercial CA
Crypt=1;KeyDesc=companyNameKey1;Key=06a9214036b8a15b512e03d534120006;
If the phone doesn't have a key, it must be downloaded to the phone in plain
text (a potential security hole if not using HTTPS). If the phone already has a
key, a new key can be downloaded to the phone encrypted using the old key
(refer to Changing the Key on the Phone on page C-6). At a later date, new
phones from the factory will have a key pre-loaded in them. This key will be
changed at regular intervals to enhance security
C-4
Miscellaneous Administrative Tasks
Note If a phone downloads an encrypted file that it cannot decrypt, the action is logged,
an error message displays, and the phone reboots. The phone will continue to do
this until the provisioning server provides an encrypted file that can be read, an
unencrypted file, or the file is removed from the master configuration file list.
Note Encrypted configuration files can only be decrypted on the SoundPoint IP 32x/33x,
430, 450, 550, 560, 650, and 670, the SoundStation IP 6000 and 7000 phones, and
the Polycom VVX 1500 phones.
The master configuration file cannot be encrypted on the provisioning server. This
file is downloaded by the BootROM that does not recognize encrypted files. For
more information, refer to Master Configuration Files on page 2-5.
The following configuration file changes are required to modify this feature:
Central Configuration File: sip.cfg Specify the phone-specific contact directory and the
(provisioning server) phone-specific configuration override file.
For more information, refer to Encryption
<encryption/> on page A-109.
C-5
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
To change a key:
1. Put the new key into a configuration file that is in the list of files
downloaded by the phone (specified in 000000000000.cfg or <Ethernet
address>.cfg).
Use the device.sec.configEncryption.key parameter to specify the
new key.
2. Manually reboot the phone so that it will download the new key. The
phone will automatically reboot a second time to use the new key.
At this point, the phone expects all encrypted configuration files on the
provisioning server to use the new key and it will continue to reboot until
this is the case. The files on the server must be updated to the new key or
they must be made available in unencrypted format. Updating to the new
key requires decrypting the file with the old key, then encrypting it with
the new key.
Note that configuration files, contact directory files and configuration
override files may all need to be updated if they were already encrypted.
In the case of configuration override files, they can be deleted from the
provisioning server so that the phone will replace them when it
successfully boots.
IP 430 94 23 monochrome
C-6
Miscellaneous Administrative Tasks
Logos smaller than described in the table above are acceptable, but larger
logos may be truncated or interfere with other areas of the user interface.
RGB Values
Color RGB Values (Decimal) (Hexadecimal)
IP 32x/33x bitmap.IP_330.68.name
IP 430 bitmap.IP_400.61.name
IP 450 bitmap.IP_450.82.name
IP 6000 bitmap.IP_4000.83.name
IP 7000 bitmap.IP_7000.84.name
C-7
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
For example:
<bitmaps>
<IP_330 … bitmap.IP_330.68.name="logo-330" />
<IP_400 … bitmap.IP_400.61.name="logo-430" />
<IP_450 … bitmap.IP_450.82.name="logo-450" />
<IP_600 … bitmap.IP_600.83.name="logo-650" />
<IP_4000 … bitmap.IP_4000.83.name="logo-6000" />
<IP_7000 … bitmap.IP_7000.84.name="logo-7000" />
</bitmaps>
Next, enable the idle display feature and modify the idle display “animation”
for each model to point to your bitmap (again without the .bmp extension):
<indicators ind.idleDisplay.enabled="1">
<Animations>
<IP_330>
…
<IDLE_DISPLAY ind.anim.IP_330.30.frame.1.bitmap="logo-330"
ind.anim.IP_330.30.frame.1.duration="0"/>
…
</IP_330>
<IP_400>
…
<IDLE_DISPLAY ind.anim.IP_400.30.frame.1.bitmap="logo-400"
ind.anim.IP_400.30.frame.1.duration="0"/>
…
</IP_400>
<IP_450>
…
<IDLE_DISPLAY ind.anim.IP_450.45.frame.1.bitmap="logo-450"
ind.anim.IP_450.45.frame.1.duration="0"/>
…
</IP_450>
<IP_600>
…
<IDLE_DISPLAY ind.anim.IP_600.46.frame.1.bitmap="logo-650"
ind.anim.IP_600.46.frame.1.duration="0"/>
…
</IP_600>
<IP_4000>
…
<IDLE_DISPLAY ind.anim.IP_4000.45.frame.1.bitmap="logo-6000"
ind.anim.IP_4000.45.frame.1.duration="0"/>
…
</IP_4000>
<IP_7000>
…
<IDLE_DISPLAY ind.anim.IP_7000.46.frame.1.bitmap="logo-7000"
ind.anim.IP_7000.46.frame.1.duration="0"/>
…
C-8
Miscellaneous Administrative Tasks
</IP_7000>
</Animations>
…
</indicators>
Note 1. SoundPoint IP 550, 560 and 650 phones manufactured as of February 2009
have additional BootROM/SIP application dependencies. For more
information, refer to “Technical Bulletin TB 46440: Notice of Product Shipping
Configuration Change” at
http://www.polycom.com/support/voice/soundpoint_ip/VoIP_Technical_Bulletin
s_pub.html .
2. If the SoundStation IP 7000 is connected to a Polycom HDX system, the
BootROM must be 4.1.2 or later.
C-9
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Migration Dependencies
In addition to the BootROM and application dependencies, there are certain
restrictions with regard to upgrading or downgrading from one BootROM
release to another BootROM release. These restrictions are typically caused by
the addition of features that change the way BootROM provisioning is done,
so the older version become incompatible.
There is always a way to move forward with BootROM releases, although it
may be a two or three step procedure sometimes, but there are cases where it
is impossible to move backward. Make special note of these cases before
upgrading.
For the latest information, refer to the latest Release Notes.
• Polycom HDX systems running HDX Version 2.5.0.2_29-3382 (hot fix 29)
The following table shows all supported software for the SoundStation IP 7000
and Polycom HDX systems.
C - 10
Miscellaneous Administrative Tasks
• IP 450, 550, 560, 600, 601, and 650, and 670: Volume-, Volume+, Mute, and
Messages
Note As of SIP 3.2.0, users can restart their phones by pressing the Menu key, and then
selecting Settings > Basic > Restart Phone. Any new BootROM and SIP
applications will be downloaded to the phone as a result of this restart.
• IP 450, 550, 600, 601, and 650, and 670 and VVX 1500: 4, 6, 8 and * dial pad
keys
C - 11
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
• IP 430, 450, 550, 560, 600, 601, 650, 670, and 7000 and VVX 1500: Up, Down,
Left, and Right arrow keys
C - 12
Miscellaneous Administrative Tasks
31 13 7
14
Menu Line 1
32 15 8
33 9
Dial Line 2
34 10
16
ABC DEF
1 6 2 1 325
Hold
GHI JKL MNO 19
4 5
5 2 6 26
PQRS TUV WXYZ 20
7 4 8 3 9 27
30 OPER 21
29
0 28 22
24 23
Key ID
C - 13
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
SoundPoint IP 430
C - 14
Miscellaneous Administrative Tasks
SoundPoint IP 450
1
2
3
4
30
28 27 34 25 31 22
29
5 35
26
32
21 20 19
23
16 17 18
7
15 14 13
33
10 11 12
9 8
Key ID
C - 15
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
SoundPoint IP 550/560/650/670
34 1
33
Sel
35 2 5 4
41
42 3
31
Del
6
Directories Menu
30 28 27 26 25 7
Services Messages
29
1 24 2 23 3
ABC DEF
8
Conference 22 Do Not Disturb
ABC DEF
32 9
4 19 5 20 6
GHI JKL MNO
Transfer
37 GHI JKL MNO 21 10
77 88 99 16
PQRS TUV WXYZ
Redial
Hold
36 18 TUV 17 39 38
PQRS WXYZ
Hold
0
OPER
40 * 15 OPER
14
#
13
12 11
Key ID
Note The SoundPoint IP 550 and 560 has have only the top four lines keys. Key IDs 31
and 42 are not used on SoundPoint IP 550 and 560 phones.
C - 16
Miscellaneous Administrative Tasks
SoundStation IP 6000
27 17
23
26 11
28 29 25
1 2 3 4
5
7 8 9 10
22 13 14 15 16
19 20 21
Key ID
C - 17
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
SoundStation IP 7000
1 7 13 19
26
6 14 20 30
8
9 15 21
3 27
10 16 22
4 28
11 17 23
5 29
12 18 24
Key ID
C - 18
Miscellaneous Administrative Tasks
37 25 13 1
8
2 4
39 33 27 3
20 14
40 34 28 21 15
5
41 35 29 22 16
24 18
42 36 30 23 17 12
Key ID
• Some functions are dependent on call state. Generally, if the soft key
appears on a call screen, the soft key function is executable. There are some
exceptions on the SoundPoint IP 32x/33x phone (because it does not
display as many soft keys).
C - 19
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
• Hard key remappings do not require the Enhanced Feature key feature to
be enabled. This include the SpeedDial function on older platforms. On
newer platforms, use line key functions.
• The table below shows only Line1 to Line6 functions. For the SoundPoint
IP 650 and 670 phones with attached Expansion Modules, Line7 to Line48
functions are also supported.
ACDAvailable ACDAvailableFromIdle
ACDLogin ACDLoginLogout
ACDLogout ACDLoginLogout
ACDUnavailable ACDAvailableFromIdle
ArrowDown ArrowDown
ArrowLeft ArrowLeft
ArrowRight ArrowRight
ArrowUp ArrowUp
Callers Callers
Delete Delete
Dialpad0 Dialpad0
Dialpad1 Dialpad1
Dialpad2 Dialpad2
C - 20
Miscellaneous Administrative Tasks
Dialpad3 Dialpad3
Dialpad4 Dialpad4
Dialpad5 Dialpad5
Dialpad6 Dialpad6
Dialpad7 Dialpad7
Dialpad8 Dialpad8
Dialpad9 Dialpad9
DialpadPound DialpadPound
DialpadStar DialpadStar
Directories Directories
Divert Forward
GroupPickup GroupPickup
Handsfree Handsfree
LCR LastCallReturn
Menu Menu
C - 21
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
MicMute MicMute
MyStatus MyStatus
Null Do nothing
Select Select
ServerACDAgentAvailable serverACDAgentAvailable
ServerACDAgentUnavailable serverACDAgentUnavailable
ServerACDSignIn serverACDSignIn
ServerACDSignOut serverACDSignOut
SoftKey1 SoftKey1
SoftKey2 SoftKey2
SoftKey3 SoftKey3
SoftKey4 SoftKey4
SpeedDial SpeedDial
VolDown VolDown
VolUp VolUp
C - 22
Miscellaneous Administrative Tasks
Note If a VLAN tag is assigned by CDP, DHCP VLAN tags will be ignored.
C - 23
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
The following figure shows the phone’s processing to determine if the VLAN
ID is valid:
C - 24
Miscellaneous Administrative Tasks
3c 74
- Option 60, length of Option data (part of the DHCP spec.)
00 00 36 3d
- Polycom signature (always 4 octects)
6f
- Length of Polycom data
01 07 50 6f 6c 79 63 6f 6d
- sub-option 1 (company), length, "Polycom"
02 15 53 6f 75 6e 64 50 6f 69 6e 74 49 50 2d 53 50 49 50 5f 36 30 31
- sub-option 2 (part), length, "SoundPointIP-SPIP_601"
03 10 32 33 34 35 2d 31 31 36 30 35 2d 30 30 31 2c 32
- sub-option 3 (part number), length, "2345-11605-001,2"
04 1c 53 49 50 2f 54 69 70 2e 58 58 58 58 2f 30 38 2d 4a 75 6e 2d 30 37
20 31 30 3a 34 34
- sub-option 4 (Application version), length, "SIP/Tip.XXXX/08-Jun-07
10:44"
05 1d 42 52 2f 33 2e 31 2e 30 2e 58 58 58 58 2f 32 38 2d 41 70 72 2d 30
35 20 31 33 3a 33 30
- sub-option 5 (BootROM version), length, "BR/3.1.0.XXXX/28-Apr-05
13:30"
ff
- end of sub-options
For the BootROM, sub-option 4 and sub-option 5 will contain the same string.
The string is formatted as follows:
<apptype>/<buildid>/<date+time>
where:
<apptype> can be 'BR' (BootROM) or 'SIP' (SIP Application)
C - 25
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
C - 26
Miscellaneous Administrative Tasks
1. Press .
2. Select Settings > Advanced > Network Configuration > Ethernet Menu.
You must enter the administrator password to access the network
configuration. The factory default password is 456.
3. Scroll down to PC Port Mode and select Edit.
4. Select Disabled, and then press the OK soft key.
5. Press the Exit soft key.
6. Select Save Config.
The SoundPoint IP phone reboots. When the reboot is complete, the PC
Ethernet port is disabled.
C - 27
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
C - 28
Miscellaneous Administrative Tasks
h If you make any changes, scroll down to the bottom of the section.
i Select the Submit button.
Your phone will reboot.
C - 29
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Note You need to re-enable the Screen Capture feature after every phone restart or
reboot (repeat step 2).
C - 30
Miscellaneous Administrative Tasks
The LLDP feature (added in SIP 3.2.0) supports VLAN discovery and LLDP
power management, but not power negotiation. LLDP has a higher priority
than CDP and DHCP VLAN discovery.
The following Type Length Values (TLVs) are supported:
• Mandatory
— Chassis ID—Must be first TLV
— Port ID—Must be second TLV
— Time-to-live—Must be third TLV, set to 120 seconds
— End-of-LLDPDU—Must be last TLV
— LLDP-MED Capabilities
— LLDP-MED Network Policy—VLAN, L2 QoS, L3 QoS
— LLDP-MED Extended Power-Via-MDI TLV—Power Type, Power
Source, Power Priority, Power Value
• Optional
— Port Description
— System Name—Administrator assigned name
— System Description—Includes device type, phone number, hardware
version, and software version
— System Capabilities—Set as "Telephone" capability
— MAC / PHY config status—Detects duplex mismatch
— Management Address—Used for network discovery
— LLDP-MED Location Identification—Location data formats:
Co-ordinate, Civic Address, ECS ELIN
— LLDP-MED Inventory Management —Hardware Revision, Firmware
Revision, Software Revision, Serial Number, Manufacturer’s Name,
Model Name, Asset ID
An LLDP frame shall contain all mandatory TLVs. The frame will be
recognized as LLDP only if it contains mandatory TLVs. SoundPoint IP /
SoundStation IP / VVX phones will support LLDP frames with both
mandatory and optional TLVs. The basic structure of an LLDP frame and a
table containing all TLVs along with each field is explained in Supported TLVs
on page C-32.
C - 31
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Note As per section 10.2.4.4 of the LLDP-MED standard, LLDP-MED endpoint devices
need to transmit Location Identification TLVs if they are capable of either
automatically determining their physical location by use of GPS or radio beacon or
capable of being statically configured with this information.
At present, the SoundPoint IP / SoundStation IP / VVX phones do not have the
capability to determine their physical location automatically or provision to a
statically configured location. Because of these limitations, the SoundPoint IP /
SoundStation IP / VVX phones will not transmit Location Identification TLV in the
LLDP frame. However, the location information from the switch is decoded and
displayed on the phone’s menu.
Supported TLVs
This is the basic TLV format:
TLV Type (7 bits) [0-6] TLV Length (9 bits) TLV Information (0-511
[7-15] bytes)
Org. Version
Type Length Unique
(7 bits) (9 bits) Type Code Sub-
No Name [0-6] [7-15] Length (3 bytes) Type Information
C - 32
Miscellaneous Administrative Tasks
Org. Version
Type Length Unique
(7 bits) (9 bits) Type Code Sub-
No Name [0-6] [7-15] Length (3 bytes) Type Information
C - 33
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Org. Version
Type Length Unique
(7 bits) (9 bits) Type Code Sub-
No Name [0-6] [7-15] Length (3 bytes) Type Information
C - 34
Miscellaneous Administrative Tasks
Org. Version
Type Length Unique
(7 bits) (9 bits) Type Code Sub-
No Name [0-6] [7-15] Length (3 bytes) Type Information
14 LLDP-MED 127 min len > - 0x0012bb 3 ELIN data format: 10 digit
location 0, max len emergency number
identificatio <= 511 configured on the switch.
n3 Civic Address: physical
address data such as city,
street number, and building
information.
C - 35
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Org. Version
Type Length Unique
(7 bits) (9 bits) Type Code Sub-
No Name [0-6] [7-15] Length (3 bytes) Type Information
16 LLDP-MED 127 min len > - 0x0012bb 5 Hardware part number and
inventory 0, max len revision
hardware <= 32
revision
23 End of 0 0 0x0000 - - -
LLDP DU
C - 36
Miscellaneous Administrative Tasks
System Names
Model Names
IP 320 SoundPointIP-SPIP_320
IP 321 SoundPointIP-SPIP_321
IP 330 SoundPointIP-SPIP_330
IP 331 SoundPointIP-SPIP_331
IP 335 SoundPointIP-SPIP_335
IP 430 SoundPointIP-SPIP_430
C - 37
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
IP 450 SoundPointIP-SPIP_450
IP 550 SoundPointIP-SPIP_550
IP 560 SoundPointIP-SPIP_560
IP 650 SoundPointIP-SPIP_650
IP 670 SoundPointIP-SPIP_670
IP 6000 SoundStationIP-SSIP_6000
IP 7000 SoundStationIP-SSIP_7000
PMD Advertise
Mode/Speed Capability Bit Operational MAU Type
Unknown 0 0
Note By default, all phones have the PMD Advertise Capability set for 10HD, 10FD,
100HD and 100FD bits. For SoundPoint IP 560 and IP 670, and Polycom VVX 1500
phones that have Gigabit Ethernet support PMD Advertise Capability also contains
set 1000FD bit.
C - 38
Miscellaneous Administrative Tasks
Power Values
IP 320/330 4.5 45
IP 321/331 4.5 45
IP 335 5.5 55
IP 430 4.5 45
IP 450 4.5 45
IP 550 6 60
IP 560 8 80
Note By default, the power values for the SoundPoint IP 650 and 670 are sent for the
phone and the Expansion Module(s). The values are not adjusted when the
Expansion Module(s) are detached from the phone.
C - 39
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
C - 40
D
Third Party Software
This appendix provides the copyright statements for third party software
products that are part of the application programs that run on Polycom
SoundPoint IP, SoundStation IP, and VVX 1500 phones.
This appendix provides the copyright statements for third party software
products that are part of the application programs that run on Polycom VVX
1500 phones only.
D-1
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Linux kernel Refer to the “Polycom Voice OFFER of Source for GPL
and LGPL Software”
The “Polycom Voice OFFER of Source for GPL and LGPL Software” is
available at
http://downloads.polycom.com/voice/voip/offerForSourceVoiceProducts.
html .
c-ares
Copyright 1998 by the Massachusetts Institute of Technology.
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose and without fee is hereby granted, provided
that the above copyright notice appear in all copies and that both that
copyright notice and this permission notice appear in supporting
documentation, and that the name of M.I.T. not be used in advertising or
publicity pertaining to distribution of the software without specific, written
prior permission.
D-2
Third Party Software
M.I.T. makes no representations about the suitability of this software for any
purpose. It is provided "as is" without express or implied warranty.
curl
COPYRIGHT AND PERMISSION NOTICE
Copyright (c) 1996 - 2008, Daniel Stenberg, <daniel@haxx.se>.
All rights reserved.
Permission to use, copy, modify, and distribute this software for any purpose
with or without fee is hereby granted, provided that the above copyright
notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY
KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO
EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE
FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT
OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.
Except as contained in this notice, the name of a copyright holder shall not be
used in advertising or otherwise to promote the sale, use or other dealings in
this Software without prior written authorization of the copyright holder.
dhcp 4.0.0-14
Copyright (c) 2004-2009 by Internet Systems Consortium, Inc. ("ISC")
Copyright (c) 1995-2003 by Internet Software Consortium
Permission to use, copy, modify, and distribute this software for any purpose
with or without fee is hereby granted, provided that the above copyright
notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL
WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO
EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT,
OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER
RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION,
ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THIS SOFTWARE.
Internet Systems Consortium, Inc.
950 Charter Street
Redwood City, CA 94063
<info@isc.org>
D-3
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
http://www.isc.org/
Dropbear
The majority of code is written by Matt Johnston, under the license below.
Portions of the client-mode work are (c) 2004 Mihnea Stoenescu, under the
same license:
Copyright (c) 2002-2006 Matt Johnston
Portions copyright (c) 2004 Mihnea Stoenescu
All rights reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the rights to use,
copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the
Software, and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY
KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF
CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.
=====
LibTomCrypt and LibTomMath are written by Tom St Denis, and are Public
Domain.
=====
sshpty.c is taken from OpenSSH 3.5p1,
Copyright (c) 1995 Tatu Ylonen <ylo@cs.hut.fi>, Espoo, Finland
All rights reserved
"As far as I am concerned, the code I have written for this software can be used
freely for any purpose. Any derived versions of this software must be clearly
marked as such, and if the derived work is incompatible with the protocol
description in the RFC file, it must be called by a name other than "ssh" or
"Secure Shell". "
=====
loginrec.c
loginrec.h
D-4
Third Party Software
atomicio.h
atomicio.c
and strlcat() (included in util.c) are from OpenSSH 3.6.1p2, and are licensed
under the 2 point BSD license.
loginrec is written primarily by Andre Lucas, atomicio.c by Theo de Raadt.
strlcat() is (c) Todd C. Miller
=====
Import code in keyimport.c is modified from PuTTY's import.c, licensed as
follows:
PuTTY is copyright 1997-2003 Simon Tatham.
Portions copyright Robert de Bath, Joris van Rantwijk, Delian Delchev,
Andreas Schultz, Jeroen Massar, Wez Furlong, Nicolas Barry, Justin Bradford,
and CORE SDI S.A.
Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the rights to use,
copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the
Software, and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY
KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
droidfonts
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND
DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction, and
distribution as defined by Sections 1 through 9 of this document.
D-5
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
D-6
Third Party Software
D-7
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
D-8
Third Party Software
eXpat
Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd and
Clark Cooper
Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the rights to use,
copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the
Software, and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY
KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF
CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.
IJG JPEG
Independent JPEG Group's free JPEG software
This package contains C software to implement JPEG image encoding,
decoding, and transcoding. JPEG is a standardized compression method for
full-color and gray-scale images.
The distributed programs provide conversion between JPEG "JFIF" format and
image files in PBMPLUS PPM/PGM, GIF, BMP, and Targa file formats. The
core compression and decompression library can easily be reused in other
programs, such as image viewers. The package is highly portable C code; we
have tested it on many machines ranging from PCs to Crays.
We are releasing this software for both noncommercial and commercial use.
Companies are welcome to use it as the basis for JPEG-related products. We
do not ask a royalty, although we do ask for an acknowledgement in product
literature (see the README file in the distribution for details). We hope to
make this software industrial-quality --- although, as with anything that's free,
we offer no warranty and accept no liability.
For more information, contact jpeg-info@jpegclub.org.
Contents of this directory
jpegsrc.vN.tar.gz contains source code, documentation, and test files for
release N in Unix format.
jpegsrN.zip contains source code, documentation, and test files for release N
in Windows format.
D-9
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
libMng
COPYRIGHT NOTICE:
Copyright © 2000-2008 Gerard Juyn (gerard@libmng.com)
For the purposes of this copyright and license, "Contributing Authors" is
defined as the following set of individuals:
Gerard Juyn
(hopefully some more to come...)
The MNG Library is supplied "AS IS". The Contributing Authors disclaim all
warranties, expressed or implied, including, without limitation, the
warranties of merchantability and of fitness for any purpose. The
Contributing Authors assume no liability for direct, indirect, incidental,
special, exemplary, or consequential damages, which may result from the use
of the MNG Library, even if advised of the possibility of such damage.
Permission is hereby granted to use, copy, modify, and distribute this source
code, or portions hereof, for any purpose, without fee, subject to the following
restrictions:
1. The origin of this source code must not be misrepresented.
2. Altered versions must be plainly marked as such and must not be
misrepresented as being the original source.
D - 10
Third Party Software
3. This Copyright notice may not be removed or altered from any source or
altered source distribution.
The Contributing Authors specifically permit, without fee, and encourage the
use of this source code as a component to supporting the MNG and JNG file
format in commercial products. If you use this source code in a product,
acknowledgment would be highly appreciated.
libPng
COPYRIGHT NOTICE, DISCLAIMER, and LICENSE:
If you modify libpng you may insert additional notices immediately following
this sentence.
This code is released under the libpng license.
libpng versions 1.2.6, August 15, 2004, through 1.2.40, September 10, 2009, are
Copyright (c) 2004, 2006-2009 Glenn Randers-Pehrson, and are distributed
according to the same disclaimer and license as libpng-1.2.5 with the following
individual added to the list of Contributing Authors
Cosmin Truta
libpng versions 1.0.7, July 1, 2000, through 1.2.5 - October 3, 2002, are
Copyright (c) 2000-2002 Glenn Randers-Pehrson, and are distributed
according to the same disclaimer and license as libpng-1.0.6 with the following
individuals added to the list of Contributing Authors
Simon-Pierre Cadieux
Eric S. Raymond
Gilles Vollant
and with the following additions to the disclaimer:
There is no warranty against interference with your enjoyment of the library
or against infringement. There is no warranty that our efforts or the library
will fulfill any of your particular purposes or needs. This library is provided
with all faults, and the entire risk of satisfactory quality, performance,
accuracy, and effort is with the user.
libpng versions 0.97, January 1998, through 1.0.6, March 20, 2000, are
Copyright (c) 1998, 1999 Glenn Randers-Pehrson, and are distributed
according to the same disclaimer and license as libpng-0.96, with the following
individuals added to the list of Contributing Authors:
Tom Lane
Glenn Randers-Pehrson
Willem van Schaik
libpng versions 0.89, June 1996, through 0.96, May 1997, are Copyright (c) 1996,
1997 Andreas Dilger Distributed according to the same disclaimer and license
as libpng-0.88, with the following individuals added to the list of Contributing
Authors:
D - 11
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
John Bowler
Kevin Bracey
Sam Bushell
Magnus Holmgren
Greg Roelofs
Tom Tanner
libpng versions 0.5, May 1995, through 0.88, January 1996, are Copyright (c)
1995, 1996 Guy Eric Schalnat, Group 42, Inc.
For the purposes of this copyright and license, "Contributing Authors" is
defined as the following set of individuals:
Andreas Dilger
Dave Martindale
Guy Eric Schalnat
Paul Schmidt
Tim Wegner
The PNG Reference Library is supplied "AS IS". The Contributing Authors
and Group 42, Inc. disclaim all warranties, expressed or implied, including,
without limitation, the warranties of merchantability and of fitness for any
purpose. The Contributing Authors and Group 42, Inc. assume no liability for
direct, indirect, incidental, special, exemplary, or consequential damages,
which may result from the use of the PNG Reference Library, even if advised
of the possibility of such damage.
Permission is hereby granted to use, copy, modify, and distribute this source
code, or portions hereof, for any purpose, without fee, subject to the following
restrictions:
1. The origin of this source code must not be misrepresented.
2. Altered versions must be plainly marked as such and must not be
misrepresented as being the original source.
3. This Copyright notice may not be removed or altered from any source or
altered source distribution.
The Contributing Authors and Group 42, Inc. specifically permit, without fee,
and encourage the use of this source code as a component to supporting the
PNG file format in commercial products. If you use this source code in a
product, acknowledgment is not required but would be appreciated.
Libpng is OSI Certified Open Source Software. OSI Certified Open Source is a
certification mark of the Open Source Initiative.
Glenn Randers-Pehrson
glennrp at users.sourceforge.net
September 10, 2009
D - 12
Third Party Software
libSRTP
Copyright (c) 2001-2005 Cisco Systems, Inc.
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
* Neither the name of the Cisco Systems, Inc. nor the names of its
contributors may be used to endorse or promote products derived from this
software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
libssh2
Copyright (c) 2004-2007 Sara Golemon <sarag@libssh2.org>
Copyright (C) 2006-2007 The Written Word, Inc.
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
Neither the name of the copyright holder nor the names of any other
contributors may be used to endorse or promote products derived from this
software without specific prior written permission.
D - 13
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
ncurses
Copyright (c) 1998-2004, 2006 Free Software Foundation, Inc.
Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the rights to use,
copy, modify, merge, publish, distribute, distribute with modifications,
sublicense, and/or sell copies of the Software, and to permit persons to whom
the Software is furnished - to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY
KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE ABOVE
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Except as contained in this notice, the name(s) of the above copyright holders
shall not be used in advertising or otherwise to promote the sale, use or other
dealings in this Software without prior written authorization.
OpenLDAP
The OpenLDAP Public License
Version 2.8, 17 August 2003
Redistribution and use of this software and associated documentation
("Software"), with or without modification, are permitted provided that the
following conditions are met:
D - 14
Third Party Software
OpenSSL
The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the
OpenSSL License and the original SSLeay license apply to the toolkit. See
below for the actual license texts. Actually both licenses are BSD-style Open
Source licenses. In case of any license issues related to OpenSSL please contact
openssl-core@openssl.org.
OpenSSL License
Copyright (c) 1998-2008 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
D - 15
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
1. Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must
display the following acknowledgment:
"This product includes software developed by the OpenSSL Project for use in
the OpenSSL Toolkit. (http://www.openssl.org/)"
4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
endorse or promote products derived from this software without prior written
permission. For written permission, please contact openssl-core@openssl.org.
5. Products derived from this software may not be called "OpenSSL" nor may
"OpenSSL" appear in their names without prior written permission of the
OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following
acknowledgment:
"This product includes software developed by the OpenSSL Project for use in
the OpenSSL Toolkit (http://www.openssl.org/)"
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND
ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes cryptographic software written by Eric Young
(eay@cryptsoft.com). This product includes software written by Tim Hudson
(tjh@cryptsoft.com).
Original SSLeay License:
Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
All rights reserved.
This package is an SSL implementation written by Eric Young
(eay@cryptsoft.com).
The implementation was written so as to conform with Netscape’s SSL.
This library is free for commercial and non-commercial use as long as the
following conditions are adhered to. The following conditions apply to all
code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not
just the SSL code. The SSL documentation included with this distribution is
covered by the same copyright terms except that the holder is Tim Hudson
(tjh@cryptsoft.com).
Copyright remains Eric Young's, and as such any Copyright notices in the
code are not to be removed. If this package is used in a product, Eric Young
D - 16
Third Party Software
should be given attribution as the author of the parts of the library used. This
can be in the form of a textual message at program startup or in documentation
(online or textual) provided with the package. Redistribution and use in
source and binary forms, with or without modification, are permitted
provided that the following conditions are met:
1. Redistributions of source code must retain the copyright notice, this list of
conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must
display the following acknowledgement: "This product includes
cryptographic software written by Eric Young (eay@cryptsoft.com)"
The word 'cryptographic' can be left out if the routines from the library being
used are not cryptographic related.
4. If you include any Windows specific code (or a derivative thereof) from the
apps directory (application code) you must include an acknowledgement:
"This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
The licence and distribution terms for any publicly available version or
derivative of this code cannot be changed. i.e. this code cannot simply be
copied and put under another distribution licence [including the GNU Public
Licence.]
pmap-29092002
Copyright (c) 2002 Andrew Isaacson <adi@hexapodia.org>
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
D - 17
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
3. The name of the author may not be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
zlib
version 1.2.3, July 18th, 2005
Copyright (C) 1995-2005 Jean-loup Gailly and Mark Adler
This software is provided 'as-is', without any express or implied warranty. In
no event will the authors be held liable for any damages arising from the use
of this software.
Permission is granted to anyone to use this software for any purpose,
including commercial applications, and to alter it and redistribute it freely,
subject to the following restrictions:
1. The origin of this software must not be misrepresented; you must not claim
that you wrote the original software. If you use this software in a product, an
acknowledgment in the product documentation would be appreciated but is
not required.
2. Altered source versions must be plainly marked as such, and must not be
misrepresented as being the original software.
3. This notice may not be removed or altered from any source distribution.
Jean-loup Gailly Mark Adler
jloup@gzip.org madler@alumni.caltech.edu
D - 18
Index
Numerics Ethernet call control A–72
802.1Q VLAN header 4–82 event logging A–104
feature A–116
A finder A–118
fonts A–92
access URL 4–68 gains A–50
ACD. See also automatic call distribution graphic icons A–103
acoustic echo cancellation 4–79 H.235 A–112
acoustic echo cancellation <aec> A–54 H.323 A–22
acoustic echo suppression <aes> A–55 hold, local reminder A–85
idle display A–120
AEC. See also acoustic echo cancellation
indicator classes A–102
AGC. See also automatic gain control indicator patterns A–102
alert information A–19 indicators, assignments A–102
animations <anim> A–101 IP TOS call control A–74
application configuration keep-alive A–79
acoustic echo cancellation A–54 keys A–94
acoustic echo suppression A–55 local camera view A–71
animations A–101 local protocol A–8
audio codec preferences A–45 localization A–27
audio codec profiles A–49 main browser A–121
automatic gain control A–57 multilingual A–28
background noise suppression A–56 music on hold A–21
backgrounds A–96 network monitoring A–75
bitmaps A–100 outbound proxy A–18
call handling configuration A–80 password lengths A–109
call progress patterns A–40 platform A–100
camera controls A–70 port A–78
chord-sets A–36 power saving A–132
compliance A–22 presence A–91
conference setup A–20 protocol A–7
connection reuse A–21 protocol server A–8
date and time A–31 protocol special events A–20
dial plan A–23 provisioning A–114
dial plan, emergency A–27 Quality of Service A–71
dialog A–21 RAM disk A–115
directory A–85 receive equalization A–57
DNS cache A–126 request A–115
dual tone multi-frequency A–35 request delay A–116
encryption A–109 request validation A–19
resource A–118
ring type A–43
routing server A–27
Index – 1
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Index – 2
Index
Index – 3
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Index – 4
Index
N Polycom HDX
Network Address Translation <nat> A–150 supported software C–10
network configuration, modifying 3–6 Polycom VVX 1500
power saving feature 4–52
network monitoring <netMon> A–75
Polycom VVX 1500 D
new features
H.323 protocol 2–15, 4–87
SIP 3.1.2 2–14
SIP 3.1.3 2–14 port <port> A–78
SIP 3.2 2–14 power saving <powerSaving> A–132
SIP 3.2.2 2–15 presence 4–64
no answer <noanswer> A–144 presence <pres> A–91
product-model-part number mapping C–26
O protocol <voIpProt> A–7
Option 66 3–8 protocol server <server> A–8
outbound proxy <outboundProxy> A–18 protocol special events <specialEvent> A–20
provisioning <prov> A–114
P
provisioning protocols 3–4
packet error concealment 4–78
provisioning protocols, supported 3–4
password <pwd> A–109
patterns <pat> A–39 Q
patterns <pattern> A–102 QOS. See also Quality of Service
peer networking <pnet>application Quality of Service <QOS> A–71
configuration
quick setup feature 4–76
peer networking A–125
quotas <quotas> A–119
per-phone configuration
attendant A–151
R
automatic call distribution A–156
automatic off-hook call placement A–140 RAM disk <ramdisk> A–115
behaviors A–153 rebooting phones 3–19, 3–23
busy A–143 receive equalization <rxEq> A–57
calls A–139 registration <reg> A–134
dial plan, emergency A–148
digit map A–147 reliability of provisional responses B–9
do not disturb A–140, A–144 request <request> A–115
forward all A–143 request delay <delay> A–116
message waiting indicator A–149 request validation <requestValidation> A–19
messaging A–149 resetting to factory defaults 3–6
missed call configuration A–141
resource <res> A–118
Network Address Translation A–150
no answer A–144 resource files, overview 2–8
quotas A–119 resource list <resourceList> A–152
registration A–134 RFC support B–2
resource list A–152 ring type <rt> A–43
roaming buddies A–154 ringer patterns A–41
roaming privacy A–154
roaming buddies <roaming_buddies> A–154
routing A–147
routing server A–148 roaming privacy <roaming_provacy> A–154
per-phone configuration file A–133 routing <routing> A–147
phone diagnostics 5–10 routing server <server> A–27, A–148
phone quick setup 4–76 RTP <RTP> A–72, A–73, A–78
phone1.cfg A–133
Index – 5
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
S SIP header
sampled audio files A–38 diversion A–14
warning A–15
sampled audio for sound effects <saf> A–37
SIP headers, warnings 4–75
SCA. See also shared call appearances
SIP. See also Session Initiation Protocol
scheduled logging parameters A–107
sip.cfg A–5
screen capture, phone A–33
SIP<SIP> A–11
SDP <SDP> A–17
SIP-B automatic call distribution 4–58
secure real-time transport protocol 4–93
soft keys <softkey> A–128
security <sec> A–108
sound effects <se> A–38
server menu 3–10
SoundPoint IP
server redundancy 4–60
applications 4–32
server-based call forwarding See also call configuring phones locally 4–98
forwarding device certificates 4–95
server-based DND See also do not disturb features, list of 1–6
Services key. See also Applications key supported languages 4–29
Session Initiation Protocol SoundPoint IP / SoundStation IP / VVX phones
setting up changed features, overview 2–15
advanced features 4–25 features, overview 2–8
audio features 4–77 introduction 1–1
basic features 4–1 network 2–2
boot server 3–14 new features, overview 2–14, 2–15
network 3–2 SoundPoint IP 32x/33x
security features 4–92 switching text entry mode 3–8
shared call appearance signaling B–10 SoundPoint IP 650
shared call appearances playback 4–36, A–117
shared calls <shared> A–84 recording 4–36, A–117
shared lines SoundPoint IP 670
barge-in 4–53, A–136 playback 4–36, A–117
recording 4–36, A–117
SIP
1xx Responses - Provisional B–6 SoundStation IP
2xx Responses - Success B–7 applications 4–32
3xx Responses - Redirection B–7 configuring phones locally 4–98
4xx Responses - Request Failure B–7 device certificates 4–95
5xx Responses - Server Failure B–8 features, list of 1–6
6xx Responses - Global Failure B–9 supported languages 4–29
application architecture 2–3 SoundStation IP 7000
basic protocols, hold implementation B–9 supported software C–10
basic protocols, request support B–3 treble/bass controls 4–84
basic protocols, response support B–6 speed dial 4–15
basic protocols, RFC and Internet draft SRTP. See also secure real-time transport
support B–2 protocol
basic protocols, transfer B–9 static DNS cache 4–72
instant messaging and presence leveraging
status menu 5–4
extensions B–10
RFC 2–1 supported LDAP directories 4–34
SIP application
description 2–4 T
installing 3–17 text entry mode, switching 3–8
upgrading 3–21 time and date display 4–15
SIP basic protocols, header support B–4 time synchronization A–75
Index – 6
Index
TLS. See also transport layer security voice activity detection <vad> A–60
TLVs. See also type length values voice mail integration 4–56
transmit equalization <txEq> A–59 voice quality monitoring 4–83, A–61
transport layer security voice setting <voice> A–44
troubleshooting volume persistence <volume> A–50
Application is not compatible 5–2
application error messages 5–3 W
application logging options 5–5 web server <httpd> A–79
audio issues 5–16
blinking time 5–4 welcome sound, reboot A–38
boot failure messages 5–8
bootROM error messages 5–2
calling issues 5–14
Config file error. Error is 5–3
controls issues 5–12
Could not contact boot server 5–2
displays issues 5–15
Error loading 5–3
Error, application is not present! 5–3
Failed to get boot parameters via DHCP 5–2
log files 5–5
manual log upload 5–7
Network link is down 5–3
Not all configuration files were present 5–3
power and startup issues 5–11
productivity suite 5–16
reading a boot log 5–8
reading an application log 5–9
registration status 5–4
scheduled logging 5–6
screens and systems access issues 5–13
trusted certificate authority list C–1
type length values
type-of-service bits 4–82
U
uaCSTA A–14, A–134, B–9
upgrading SIP application 3–21
USB device 4–36
USB devices, supported 4–36
user interface, soft key activated 4–14
user preferences <up> A–31
V
VAD. See also voice activity detection
video <video> A–64
video codec preferences <codecPref> A–66
video codec profiles <profile> A–66
VLAN ID using DHCP C–23
voice activity detection 4–78
Index – 7
Administrator’s Guide for the SoundPoint IP / SoundStation IP / VVX Family
Index – 8
POLYCOM, INC.
APPLICATION PROGRAMMING INTERFACE LICENSE (“API”)
FOR SOUNDPOINT IP AND SOUNDSTATION IP PRODUCTS (“Product” or “Products”).
1. Agreement. You understand and agree that by using the API you will be bound by the terms of the End User License and Warranty
Terms included with the Product(s) and this document (together, the “Agreement”). In the event of any conflicts between the End User
License and Warranty Terms and this document, this document shall govern with respect to the API.
2. Parties. For purposes of this Agreement “you” or “your” shall mean the individual or entity accepting this Agreement or using the
API. The relationship between you and Polycom is that of licensee/licensor. No legal partnership or agency relationship is created
between you and Polycom. Neither you nor Polycom is a partner, an agent or has any authority to bind the other. You agree not to
represent otherwise.
3. License/Ownership. Subject to your compliance with this Agreement, Polycom hereby grants you a limited license to use the API
solely for the purposes of developing and testing your own proprietary software to be used in conjunction with the Product(s). The
foregoing license does not grant you any distribution rights or other rights to use the API for any other purpose and you agree that you
shall not rent, lease, loan, sell, sublicense, assign or otherwise transfer any rights in the API. Polycom retains ownership of the API, and
except as expressly set forth herein, no other rights or licenses are granted. Polycom may change, suspend or discontinue providing the
API at any time.
4. Term/Survival. Without prejudice to any other rights, Polycom may terminate this Agreement if you fail to comply with any of the
terms and conditions of this Agreement. In such an event, you must destroy all copies of the API. You may terminate this Agreement at
any time by destroying the API. In the event of any termination of this Agreement, Sections 1, 2, 5, and 7-11 shall survive termination.
5. Development. Nothing in this Agreement shall impair Polycom’s right to develop, acquire, license, market, promote or distribute
products, software or technologies that perform the same or similar functions as, or otherwise compete with any other products, software
or technologies that you may develop, produce, market, or distribute. In the absence of a separate written agreement to the contrary,
Polycom shall be free to use any information, suggestions or recommendations you provide to Polycom for any purpose, subject to any
applicable patents or copyrights.
6. Harmful Code. You agree not to include any “Harmful Code” in any products you develop by use of the API, including but not limited
to any code that: (i) contains hidden files, “time bombs” or viruses; or (ii) can alter, damage, disclose or erase any data or other computer
programs without control of a person operating the computing equipment on which it resides, or (iii) retrieves or collects information
without the consent of the user or for any illegal or unauthorized purpose; or (iv) contains a key, node lock, time-out or other function
whether implemented by electronic, mechanical or other means which restricts or may restrict use or access to programs or data on the
Products, frequency or duration of use, or other limiting criteria; or (v) any code which may restrict, inhibit, disrupt or interfere with the
functionality of the Products as provided by Polycom. You agree not to use the API for any illegal or unauthorized purpose.
7. Marketing/Trademarks. You are free to market any products you develop using the API, provided you agree not use the Polycom
logo, the marks "Polycom," "SoundPoint," "SoundStation," any other marks belonging or licensed to Polycom, or any marks that are
confusingly similar to marks belonging or licensed to Polycom in any way except as otherwise expressly authorized by Polycom in each
instance. In no event shall you (i) expressly state or imply that any products developed by you were created by or on behalf of Polycom
or are being marketed by or on behalf of Polycom; or (ii) expressly state or imply that Polycom has reviewed, sanctioned, or endorsed
your product in any way.
8. No Warranty. You understand the API provided to you is supplied "AS IS" AND “WITH ALL FAULTS” WITHOUT ANY
WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES
OF MERCHANTIBILITY, NON-INFRINGEMENT, ACCURACY, COMPLETENESS, PERFORMANCE, AND FITNESS FOR A
PARTICULAR PURPOSE, AND POLYCOM PROVIDES NO SUPPORT FOR THIS API. You understand that Polycom is under no
obligation to provide updates, enhancements, or corrections, or to notify you of any API changes that Polycom may make. In the event
you market a product you develop using the API, any obligations, representations or warranties provided by you to an end user shall be
solely your obligations, and in no event shall Polycom be responsible to fulfill any such obligations.
9. Indemnity. You shall indemnify and hold Polycom harmless from and against any and all costs, damages, losses, liability or
expenses (including reasonable attorneys’ fees) arising from your use of the API (including without limitation any actions arising from acts
or omissions of your employees or agents) or any failure by you to comply with the terms of this Agreement.
10. Disclaimer of Liability. UNDER NO CIRCUMSTANCES SHALL POLYCOM BE LIABLE FOR SPECIAL, INDIRECT, INCIDENTAL,
OR CONSEQUENTIAL DAMAGES, INCLUDING WITHOUT LIMITATION, DAMAGES RESULTING FROM DELAY OF DELIVERY OR
FROM LOSS OF PROFITS, DATA, BUSINESS OR GOODWILL, ON ANY THEORY OF LIABILITY, WHETHER ARISING UNDER
TORT (INCLUDING NEGLIGENCE), CONTRACT OR OTHERWISE, WHETHER OR NOT POLYCOM HAS BEEN ADVISED OR IS
AWARE OF THE POSSIBILITY OF SUCH DAMAGES. POLYCOM’S ENTIRE LIABILITY FOR DIRECT DAMAGES UNDER THIS
AGREEMENT IS LIMITED TO FIVE DOLLARS ($5.00).
11. Miscellaneous. If any provision is found to be unenforceable or invalid, that provision shall be limited or eliminated to the minimum
extent necessary so that this Agreement shall otherwise remain in full force and effect and enforceable. This Agreement constitutes the
entire agreement between the parties with respect to its subject matter and supersedes all prior or contemporaneous understandings
regarding such subject matter. No addition to or removal or modification of any of the provisions of this Agreement will be binding upon
Polycom unless made in writing and signed by an authorized representative of Polycom.
YOUR USE OF THIS API ACKNOWLEDGES THAT YOU HAVE READ, UNDERSTAND AND AGREE TO BE BOUND BY THE
TERMS AND CONDITIONS INDICATED ABOVE.
The software you are about to download (the "Software") comprises sample code that
may be useful in the development of applications designed to operate on or in
conjunction with Polycom Products.
Polycom is willing to license the Software to you only upon the condition that you accept
all of the terms contained in this agreement. Select the "Accept" button at the bottom of
the page to confirm your acceptance. If you are not willing to be bound by these terms,
select the "Do Not Accept" button and the downloading process will not continue.
PLEASE NOTE:
* THE SOFTWARE HAS NOT BEEN TESTED BY POLYCOM AND SHOULD NOT
BE LOADED ON PRODUCTION SYSTEMS.
1. GRANT OF LICENSE.
1.1. License. Subject to the terms of this Agreement, Polycom grants to you a
nonexclusive, nontransferable license to copy, install, use, and modify the Software,
including the Software in source code format, and to produce your own commercial or
other purposes derivative works thereof. Except as provided below, this License
Agreement does not grant you any rights to patents, copyrights, trade secrets, trademarks,
or any other rights related to the Software.
2.1. Copyright. All title and copyrights in and to the Software and any copies of the
Software are owned by Polycom or its suppliers. The Software is protected by copyright
laws and international treaty provisions. Title, ownership rights, and intellectual property
rights in the Software shall remain in Polycom or its suppliers.
2.2. Ownership of Derivative Works. As between you and Polycom, you will own
copyright and other intellectual property rights in derivative works of the Software that
you develop.
2.3. Reservation. Polycom reserves all rights in the Software not expressly granted to you
in this Agreement.
3. SUPPORT SERVICES.
3.1. No Support Services. Polycom provides no support services for the Software.
4. TERMINATION.
4.1. Termination. Without prejudice to any other rights, Polycom may terminate this
Agreement if you fail to comply with any of the terms and conditions of this Agreement.
In such event, you must destroy all copies of the Software and all of its component parts.
You may terminate this Agreement at any time by destroying the Software and all of its
component parts.
5. NO WARRANTY.
6. LIMITATION OF LIABILITY.
7. DISCLAIMER.
7.1. Disclaimer. Some countries, states, or provinces do not allow the exclusion or
limitation of implied warranties or the limitation of incidental or consequential damages
for certain products supplied to consumers or the limitation of liability for personal
injury, so the above limitations and exclusions may be limited in their application to you.
8. EXPORT CONTROLS.
8.1. Export Controls. The Software may not be downloaded or otherwise exported or re-
exported (i) into (or to a national or resident of) Cuba, Iraq, Libya, North Korea,
Yugoslavia, Iran, Syria, Republic of Serbia, or any other country to which the U.S. has
embargoed goods; or (ii) to anyone on the U.S Treasury Department's List of Specially
Designated Nationals or the U.S. Commerce Department's Table of Denial Orders. By
downloading or using this Software, you are agreeing to the foregoing and you are
representing and warranting that you are not located in, under the control of, or a national
or resident of any such country or on any such list. If you obtained this Software outside
of the United States, you are also agreeing that you will not export or re-export it in
violation of the laws of the country in which it was obtained.
9. MISCELLANEOUS.
9.1. Governing Law. This Agreement shall be governed by the laws of the State of
California as such laws are applied to agreements entered into and to be performed
entirely within California between California residents, and by the laws of the United
States. The United Nations Convention on Contracts for the International Sale of Goods
(1980) is hereby excluded in its entirety from application to this Agreement.
9.2. Venue for Resolving Disputes. Any disputes relating to this Agreement will be
resolved only in the state or federal courts located in Santa Clara County, California.
Each of the parties agrees to the exercise over them of the personal jurisdiction of such
courts for such purpose.
9.3. U.S. Government Restricted Rights. The Software and documentation are provided
with Restricted Rights. The Software programs and documentation are deemed to be
"commercial computer software" and "commercial computer software documentation,"
respectively, pursuant to DFAR Section 227.7202 and FAR 12.212(b), as applicable. Any
use, modification, reproduction, release, performance, display, or disclosure of the
Software programs and/or documentation by the U S. Government or any of its agencies
shall be governed solely by the terms of this Agreement and shall be prohibited except to
the extent expressly permitted by the terms of this Agreement. Any technical data
provided that is not covered by the above provisions is deemed to be "technical data
commercial items" pursuant to DFAR Section 227.7015(a). Any use, modification,
reproduction, release, performance, display, or disclosure of such technical data shall be
governed by the terms of DFAR Section 227.7015(b).
9.4. Relationship Between the Parties. The relationship between you and Polycom is that
of licensee/licensor. Neither party will represent that it has any authority to assume or
create any obligation, express or implied, on behalf of the other party, nor to represent the
other party as agent, employee, franchisee, or in any other capacity. Nothing in this
agreement shall be construed to limit either party's right to independently develop or
distribute software that is functionally similar to the other party's products, so long as
proprietary information of the other party is not included in such software.
9.5. Entire Agreement. This Agreement represents the complete agreement concerning
this license and may be amended only by a writing executed by both parties. If any
provision of this Agreement is held to be unenforceable, such provision shall be reformed
only to the extent necessary to make it enforceable.
www.polycom.com
Corporate Headquarters: 4750 Willow Road, Pleasanton, CA 94588, USA Phone 408-
526.9000 Fax: 408-526-9100