Advertisement
Quick Links
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,
Advertisement
Related Manuals for Polycom SoundPoint IP30 Series
Summary of Contents for Polycom SoundPoint IP30 Series
- Page 1 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.
- Page 2 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 •...
- Page 3 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...
- Page 4 1.1.5.1 Configuration files The Polycom SoundPoint SIP software package consists of a binary image file (sip.ld), a binary BootROM file (bootrom.ld), and three XML based config files (macaddress.cfg, phonex.cfg and sip.cfg). The XML-formatted configuration files consist of master configuration (macaddress.cfg) files and phone specific (phonex.cfg) files.
- Page 5 Configuration steps for use with Interaction Center (un-Managed 3.0 stations or pre-3.0 integrations) The following steps lay out the minimum steps required to use the Polycom phones as managed SIP stations with the Interaction Center. 1. Set up the FTP server and copy all the template XML files and application files that came with the Polycom phone into the root directory of the FTP server.
- Page 6 FTP server. 1.1.5.3 Voicemail Retrieval There are two ways to configure a Polycom IP phone for voicemail retrieval: 1. Program the Message Center (Messages button) Programming the Message Center Connect option is a 3 step process for retrieving voicemails but it’s initiated by pressing the Messages button on the phone.
- Page 7 Interaction Administrator. From any phone on the system dial “*901” and press a line key. Note that you cannot press a line key then dial the “*901” as the Polycom dial plan will interfere with the dial string.
- Page 8 When the call is places all phones will be paged and placed off-hook to all the caller to announce the “page.” 1.1.5.6 Shared Line Appearances (xIC 2.4 and 3.0 un-managed Phones) This functionality will allow two physical phones to share the same line appearance (station in IA).
- Page 9 1.1.5.7 Line Roll-Down (Polycom firmware 1.5.x and beyond) Post 1.5.x firmware, the Polycom phones have the ability for inbound calls to “ring down,” the line keys. This behavior is very similar to legacy PBX operations where each user had a roll-over line. If the primary line is busy, a second incoming call would “roll-down,”...
- Page 10 Due to resource limitations on the older phones, conferencing will not work under 501 or 601 models using TLS. Another issue that can surface is that some of the phone models will not continue a conference if the conference is initiated from the phone, and the originator disconnects.