Polycom SoundPoint IP320, SoundPoint IP330, SoundPoint IP430, SoundPoint IP550, SoundPoint IP560 User Manual

1.1 Polycom SoundPoint IP30x, IP320/330, IP430, IP50x, IP550/560,
IP60x, IP650, IP670, IP4000, IP6000, IP7000

1.1.1 Important Notes

• The IP 560 supports Gigabit Ethernet for both the phone uplink as well as
the PC port. This includes in-line power for the phone.

• WARNING: The IP-601, IP-650, IP-670, IP-550/560, and IP430 power
supplies are NOT compatible with any of the previous models. Prior to
the these models, power supplies could be interchanged between units. If
a power supply from any other unit is used on the models listed above, it
will reboot un-predictably. However, if a power supply from the 601, 550,

430, or 650 is used on any other model, permanent damage could result
to the unit.

• Check the SIP 3rd Party Validation Website for current validation status.
The SIP 3rd Party Component Validation Website can be viewed at:

http://testlab.inin.com

• BootROMs 3.x and newer are signed. Once the 3.x BootROM is installed,
the phone cannot be downgraded to the 2.x series BootROM.

• As of firmware v1.5.x, there is no longer an ‘ipmid.cfg’ this has been
merged with the ‘sip.cfg’

• As with any Polycom firmware upgrade, it is not recommended to use
pre-existing configuration files. From version to version the XML tags in
the config files change. If older config files are used with newer firmware
versions the results will be unpredictable. I3 Support will insist that
appropriate config files be used with any given version of Polycom
firmware.

• Managed Phone Provisioning is the recommended/tested configuration
option for IC 3.0 or above. FTP is recommended for other IC versions.

• Due to the limited configuration options, configuration via the web
interface is not recommended or supported.

• SFTP is not supported by Polycom as of the current firmware release, even
though it is a selectable menu item.

• Do not mix configuration options (FTP, web interface, or the phone
menus). It is very easy for one interface to over ride another and limit
the ability to fully configure the phone until a complete reset of the phone
and configuration files is performed.

1.1.2 Vendor Documentation

Updated documentation can be found on Polycom’s website:

http://www.polycom.com/

1.1.3 Validated Firmware Versions

Unless otherwise noted all phones were validated on the following Firmware
and BootROMs.

Firmware: 3.0.3.0401
BootROM: 4.1.1.0232

IP 4000 Firmware: 3.0.0.0258 - BootROM version: 4.0.0.0423
IP 7000 Firmware: 3.0.1.0613 - BootROM version: 4.1.1.0232
IP 301 Firmware: 2.1.0.2695 - BootROM version: 3.2.3.0002
IP 300 Firmware: 1.6.7.0098 - BootROM version: 3.2.1
IP 500 Firmware: 1.6.7.0098 - BootROM version: 3.2.1
IP 600 Firmware: 1.6.7.0098 - BootROM version: 3.2.1

Not all combinations of BootROM and firmware versions are validated. The
current testing period was performed with the 4.0.0.0423 BootROM. It is
recommended to use firmware and Bootrom combinations listed above.

1.1.4 Install

A functional file distribution mechanism will be needed to distribute
firmware and configuration files to your phones. You can choose from
options like FTP, TFTP, and HTTP/HTTPS. Once a functional FTP server has
been setup, credentials to log into the FTP server will be required. The
phone will use this account to connect to the FTP server and download
BootROM, Firmware, and configuration files.

TFTP is the recommended server for small to midsize implementations. In
order for the Polycom phones to function as designed, the ability to write
configuration and log files back to the boot server is required. Since TFTP
provides no facility for authentication, this opens up the possibility that a
malicious user could manipulate configuration files on a standard TFTP
server running in a read/write mode. For this reason, version 2.4 of the
CIC and EIC products include a custom TFTP service on the server that has
more advanced options to enhance the security of TFTP. The ININ/Vonexus
TFTP server adds facilities like file extension filters and IP filters to create a
secure, yet simple way to support your IP phone base.

A newly supported option available with firmware 2.2.1 is the ability to
provision the phones via HTTP and or HTTPS. Interaction Center 3.0
introduces the Managed Phone concept, allowing auto provisioning of the
phone from Interaction Administrator. This is not part of any release prior
to 3.0. The preferred provisioning method continues to be FTP for releases
prior to 3.0.

Note: When provisioning managed phones that are not yet in the list,
please use the following profiles. All the phones should be in the list with
SU3.

• IP6000 and IP7000 should use the IP4000 managed phone
template.

• IP670 should use the IP650 managed phone template.

1.1.5 Configuration

Line Appearances: The line appearance is equivalent to a station in the
Interaction Administrator.

SoundPoint IP4000 – 1 line appearance
SoundPoint IP6000 – 1 line appearance