Page 2 Notices 1. Specifications subject to change without notice. Polycom, Inc. 1565 Barber Lane, Milpitas CA 95035, USA www.polycom.com Part Number: 1725-11530-200 Rev A1 Copyright © 2006 Polycom, Inc. All rights reserved.
Page 3: Table Of Contents
3.1.10 Customizable Audio Sound Effects ....................34 3.1.11 Message Waiting Indication ......................35 3.1.12 Distinctive Incoming Call Treatment....................35 3.1.13 Distinctive Ringing........................35 3.1.14 Distinctive Call Waiting ......................... 36 3.1.15 Do-Not-Disturb..........................36 3.1.16 Handset, Headset, and Speakerphone ................... 37 Copyright © 2006 Polycom, Inc.
Page 4 3.3.5 DTMF Event RTP Payload ........................ 58 3.3.6 Acoustic Echo Cancellation (AEC) ..................... 58 3.3.7 Audio Codecs..........................59 3.3.8 Background Noise Suppression (BNS)....................60 3.3.9 Comfort Noise Fill........................... 60 3.3.10 Automatic Gain Control (AGC)....................... 60 Copyright © 2006 Polycom, Inc.
Page 5 4.2 Application Network Setup ........77 4.2.1 Real-Time Transport Protocol Ports....................77 4.2.2 Working with Network Address Translation..................78 4.3 Updating and Rebooting...........79 4.4 Event Logging ............80 4.5 Audio Quality Issues and VLANs ........81 4.5.1 IP TOS ............................81 Copyright © 2006 Polycom, Inc.
Page 6 4.6.2.1 Registration <reg/> ......................149 4.6.2.2 Calls <call/>........................153 4.6.2.3 Diversion <divert/>......................154 4.6.2.4 Dial Plan <dialplan/>......................156 4.6.2.5 Messaging <msg/> ......................159 4.6.2.6 Network Address Translation <nat/> ..................160 4.6.2.7 Attendant <attendant/> ......................161 4.6.2.8 Roaming Buddies <roaming_buddies/>.................161 4.6.2.9 Roaming Privacy <roaming_privacy/>...................162 Copyright © 2006 Polycom, Inc.
Page 7 5.2.5 Bridged Line Appearance Signaling ....................172 6 Appendix 1 ............173 6.1 Trusted Certificate Authority List ........173 6.2 Miscellaneous Administrative Tasks ......175 6.2.1 Adding a Background Logo......................175 7 Appendix 2 ............177 7.1 Third Party Software Attribution ........177 Copyright © 2006 Polycom, Inc.
Page 9: Overview
Ethernet TCP/IP networks. They are designed to facilitate high- quality audio communications. These phones are end points in the overall network topology designed to interoperate with other compatible equipment including applica- tion servers, media servers, internetworking gateways, voice bridges, and other end points. Copyright © 2006 Polycom, Inc.
Page 10 Regardless of the diverse application potential, it provides the productivity enhancing features needed today such as multiple call appearances, full-duplex speakerphone, hold, transfer, confer- ence, forward, voice mail compatibility, and contact directory. Copyright © 2006 Polycom, Inc.
Page 11: Installation And Operation
To augment the central provisioning model or as the sole method in smaller systems, configuration can be done using user interfaces driven from the phones themselves: both a local setup user interface and a web server-based user interface are available to make configuration changes. Copyright © 2006 Polycom, Inc.
Page 12: Installation Process
Polycom recommends the boot server central provisioning model for installations involving more than a few phones. The investment required is minimal in terms of time and equipment, and the benefits are significant.
Page 13: Basic Network Setup
Basic network settings can be derived from DHCP, or entered manually using the phone’s LCD-based user interface, or downloaded from configuration files. Contact Polycom Customer Support for more information on this use of configuration files. Polycom recommends using DHCP where possible to eliminate repetitive manual data entry.
Page 14: Provisioning File Transfer
TFTP and FTP are supported by all SoundPoint ® ® SoundStation phones. The SoundPoint IP 301, 430, 501, 600 and 601 and ® SoundStation IP 4000 bootROM also supports HTTP, while the SIP application sup- Copyright © 2006 Polycom, Inc.
Page 15 For HTTPS, widely recognized certificate authorities are trusted by the phone and custom certificates can be added (refer to 6.1 Trusted Certificate Authority List on page 173). Copyright © 2006 Polycom, Inc.
Page 16: Local User Interface Setup Menus
Note: Disabled when DHCP client is disabled. Phone IP Address dotted-decimal IP Phone’s IP address. address Note: Disabled when DHCP client is enabled. Subnet Mask dotted-decimal subnet Phone’s subnet mask. mask Note: Disabled when DHCP client is enabled. Copyright © 2006 Polycom, Inc.
Page 17 The DHCP menu is accessible only when the DHCP client is enabled. DHCP configu- ration parameters are described in the following table: Possible Name Values Description Timeout 1 through 600 Number of seconds the phone waits for secondary DHCP Offer messages before selecting an offer. Copyright © 2006 Polycom, Inc.
Page 18 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 Discov- (Cannot be the ery is set to Custom). same as Boot Server Option) Copyright © 2006 Polycom, Inc.
Page 19 For more information, refer to 2.2.2.1.2 Boot Server Deployment for the Phones on page 19. Provisioning Default or SAS-VP If SAS-VP is selected, provisioning is done (in addition to the normal process). Method Copyright © 2006 Polycom, Inc.
Page 20: Reset To Factory Defaults
• On the IP 4000, simultaneously press and hold the 6, 8 and * dial pad keys until the password prompt appears. Enter the administrator password to initiate the reset. Resetting to factory defaults will also reset the administrator password (factory default password is 456). Copyright © 2006 Polycom, Inc.
Page 21: Application Configuration
0004f200106c.cfg. The Ethernet address can be ABOUT viewed using the soft key during the auto-boot countdown of the bootROM or through the Menu>Status>Platform>Phone menu in the application. It is also printed Copyright © 2006 Polycom, Inc.
Page 22 If a phone does not find its own <Ethernet address>.cfg file, it will use this one, and establish a baseline configuration. This file is part of the standard Polycom distribution of configuration files. It should be used as the template for the <Ethernet address>.cfg files.
Page 23 IP address of an application server. All phones in an installation usually share this category of files. Polycom recommends that you create another file with your organization’s modifications. If you must change any Polycom templates, back them up first.
Page 24 Each phone in an installation usually has its own customized ver- sion of user files derived from Polycom templates. These application configuration files dictate the behavior of the phone once it is run- ning the executable specified in the master configuration file.
Page 25 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.
Page 26 Secondary server to which the phone directs Domain Name System queries. device.dns.domain any string The phone’s DNS domain. device.auth.localAdmin- any string The phone’s local administrator password. Password device.auth.localUser- any string The phone user’s local password. Password Copyright © 2006 Polycom, Inc.
Page 27 Menu on page 11 can be used to configure the number of times each server will be tried for a file transfer and also how long to wait between each attempt. The maximum number of servers to be tried is configurable. Contact Polycom Customer Support for more information.
Page 28 Edit contents of phoneXXXX.cfg as appropriate. For example, edit the registration parameters. Edit the CONFIG_FILES attribute of the <Ethernet address>.cfg files so that it references the appropriate phoneXXXX.cfg file. (Replace the reference to phone1.cfg with phoneXXXX.cfg.) Copyright © 2006 Polycom, Inc.
Page 29 • time and date format 5. Decide on boot server security policy. Polycom recommends allowing file uploads to the boot 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.
Page 30: Local Phone Configuration
Configuration pages are accessible from the menu along the top ban- ner. The web server will issue an authentication challenge to all pages except for the home page. Credentials are (case sensitive): • User Name: Polycom • Password: The administrator password is used for this. Copyright © 2006 Polycom, Inc.
Page 31: Management Of File Encryption And Decryption
The device.sec.configEncryption.key configuration file parameter is used to set the key on the phone. The utility generates a random key and Copyright © 2006 Polycom, Inc.
Page 32: Changing The Key On 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. Copyright © 2006 Polycom, Inc.
Page 35: Features
None. User Interface 3.1.2 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. Copyright © 2006 Polycom, Inc.
Page 36: Call Waiting
Missed Calls list. The types of calls that are counted as “missed” can be configured per registration. Remote missed-call notification can be used to notify the phone when a call originally destined for it is diverted by another entity such as a Session Initiation protocol (SIP) server. Copyright © 2006 Polycom, Inc.
Page 37: Configurable Feature Keys
User Interface The following diagrams and table show the default SIP key layouts for ® ® SoundPoint IP 300, IP 301, IP 430, IP 500, IP 501, IP 600, IP 601 and SoundStation IP 4000 models. Copyright © 2006 Polycom, Inc.
Page 38 IP / SoundStation Features ® SoundPoint IP 300 and 301 Key Layout Menu Do Not Disturb Redial PQRS WXYZ Hold Hold PQRS WXYZ OPER OPER Key ID ® SoundPoint IP 430 Key Layout Key ID Copyright © 2006 Polycom, Inc.
Page 39 Hold PQRS WXYZ OPER OPER Key ID ® SoundPoint IP 600 and 601 Key Layout Menu Directories Services Messages Do Not Disturb Conference Transfer PQRS WXYZ Redial Hold PQRS WXYZ Hold OPER OPER Key ID Copyright © 2006 Polycom, Inc.
Page 40 Dialpad7 Dialpad8 Dialpad8 Dialpad0 Dialpad0 Dialpad8 Dialpad7 Dialpad7 DialpadStar DialpadStar Dialpad9 Dialpad4 Dialpad4 Dialpad9 Dialpad9 MicMute Dialpad5 Dialpad5 Dialpad8 Dialpad8 Dialpad6 Dialpad6 Dialpad7 Dialpad7 ArrowDown Dialpad3 Dialpad3 Dialpad4 Dialpad4 DialpadStar Dialpad2 Dialpad2 Dialpad5 Dialpad5 Dialpad0 Copyright © 2006 Polycom, Inc.
Page 41: Connected Party Identification
ID is provided by the call server. The connected party identity is derived from the network signaling. In some cases the remote party will be different from the called party identity due to network call diversion. Copyright © 2006 Polycom, Inc.
Page 42: Context Sensitive Volume Control
Reset Local Config menu selection. Local Phone User None. Interface ® ® 1. L16/16000 is not supported on SoundPoint IP 300, 301 and SoundStation IP 4000 phones. Copyright © 2006 Polycom, Inc.
Page 43: Message Waiting Indication
<reg/> on page 149. XML File: <Ethernet This file can be created manually using an XML editor. address>-direc- • For more information, refer to 3.1.17.1 Local Con- tory.xml tact Directory File Format on page 39. Copyright © 2006 Polycom, Inc.
Page 44: Distinctive Call Waiting
Configuration file: Specify whether DND is treated as a per-registration fea- server) phone1.cfg ture or a global feature on the phone. • For more information, refer to 4.6.2.2.1 Do Not Dis- turb <donotdisturb/> on page 153. Copyright © 2006 Polycom, Inc.
Page 45: Handset, Headset, And Speakerphone
Enable or disable persistent headset mode through the Local Interface Settings menu. Changes are saved to local flash and backed up to <Ethernet address>-phone.cfg on the boot server. Changes will permanently override global settings unless deleted through the Reset Local Config menu. Copyright © 2006 Polycom, Inc.
Page 46: Local Contact Directory
Local backed up to the boot server copy of <Ethernet address>-directory.xml if this is configured. When the phone boots, the boot server copy of the directory, if present, will overwrite the local copy. Copyright © 2006 Polycom, Inc.
Page 47: Local Contact Directory File Format
<sd>3</sd> <rt>3</rt> <dc /> <ad>0</ad> <ar>0</ar> <bw>0</bw> <bb>0</bb> </item> </item_list> </directory> Element Permitted Values Interpretation UTF-8 encoded string of up to first name 40 bytes UTF-8 encoded string of up to last name 40 bytes Copyright © 2006 Polycom, Inc.
Page 48: Local Digit Map
Instead, as soon as a digit pattern matching the digit map is found, the call setup process will complete automatically. This feature is simi- lar to the digit map feature of the Media Gateway Control Protocol (MGCP) and the Copyright © 2006 Polycom, Inc.
Page 49: Microphone Mute
The number of line keys allocated per registration is configurable. Configuration file: Specify the number of line keys to assign per registration. Central phone1.cfg (boot • For more information, refer to 4.6.2.1 Registration server) <reg/> on page 149. Copyright © 2006 Polycom, Inc.
Page 50: Multiple Call Appearances
Specify per-registration the number of calls that can be server) phone1.cfg active or on hold per line key assigned to that registration. This will override the default value specified in sip.cfg. • For more information, refer to 4.6.2.1 Registration <reg/> on page 149. Copyright © 2006 Polycom, Inc.
Page 51: Shared Call Appearances
For more information, refer to 5.2.4 Shared Call Appearance Signaling on page 171. Important Emergency routing is not supported on shared lines (refer to 4.6.1.2.2.2 Emergency <emergency/> on page 95). Copyright © 2006 Polycom, Inc.
Page 52 • For more information, refer to 4.6.2.1 Registration <reg/> on page 149. Specify per-registration whether diversion should be dis- abled on shared lines. • For more information, refer to 4.6.2.3 Diversion <divert/> on page 154. Copyright © 2006 Polycom, Inc.
Page 53: Bridged Line Appearances
Incoming calls can be presented to multiple phones simultaneously. This feature is dependent on support from a SIP server that binds the appearances together logically and looks after the necessary state notifications and performs an access control func- Copyright © 2006 Polycom, Inc.
Page 55: Busy Lamp Field
The phone’s user interface can be customized by changing the fonts and graphic icons used on the display and the LED indicator patterns. Pre-existing fonts embedded in the software can be overwritten or new fonts can be downloaded. The bitmaps and bitmap Copyright © 2006 Polycom, Inc.
Page 56: Soft Key-Driven User Interface
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. If Presence watching is enabled for speed dial entries, their status will be Copyright © 2006 Polycom, Inc.
Page 57: Time And Date Display
The clock and calendar must be synchronized to a remote Simple Network Time Protocol (SNTP) timeserver. The time and date displayed on the phone will flash continuously Copyright © 2006 Polycom, Inc.
Page 58 Settings menu. Changes are saved to local flash and backed up to <Ethernet address>-phone.cfg on the boot server. They will permanently override global settings unless deleted through the Reset Local Config menu selection. Copyright © 2006 Polycom, Inc.
Page 59: Idle Display Animation
Configuration file: Specify which registrations have the feature and what phone1.cfg contact to call when going off hook. Central (boot • For more information, refer to 4.6.2.2.2 Automatic server) Off-hook Call Placement <autoOffHook/> on page 153. Copyright © 2006 Polycom, Inc.
Page 60: Call Hold
User A. The phone offers three types of transfers; • Blind transfers: The call is transferred immediately to C after A has finished dialing C’s number. User A does not hear ring-back. Copyright © 2006 Polycom, Inc.
Page 61: Three-Way Conference, Local Or Centralized
(if enabled) Local Local Phone User None. Interface ® 2. On SoundStation IP 4000, conferences are not available if the G.729 codec is enabled on the phone. This restriction will be removed in future releases. Copyright © 2006 Polycom, Inc.
Page 62: Call Diversion (Call Forward)
Calls to another phone can be picked up by dialing the extension of the other phone. This feature depends on support from a SIP server. Configuration file: Turn this feature on or off. Central sip.cfg (boot • For more information, refer to 4.6.1.24 Feature <fea- server) ture/> on page 144. Copyright © 2006 Polycom, Inc.
Page 63: Group Call Pick-Up
Configuration file: Turn this feature on or off. Central sip.cfg (boot • For more information, refer to 4.6.1.24 Feature <fea- server) ture/> on page 144. Web Server None. (if enabled) Local Local Phone User None. Interface Copyright © 2006 Polycom, Inc.
Page 64: Last Call Return
The phone employs a high-performance jitter buffer and packet error concealment sys- tem designed to mitigate packet inter-arrival jitter and out-of-order or lost (lost or excessively delayed by the network) packets. The jitter buffer is adaptive and config- Copyright © 2006 Polycom, Inc.
Page 65: Voice Activity Detection
Enable or disable VAD and set the detection threshold. Central sip.cfg (boot • For more information, refer to 4.6.1.8.10 Voice Activity server) Detection <VAD/> on page 118. Web Server None. (if enabled) Local Local Phone User None. Interface Copyright © 2006 Polycom, Inc.
Page 66: Dtmf Tone Generation
None. Interface 3.3.6 Acoustic Echo Cancellation (AEC) The phone employs advanced acoustic echo cancellation for hands-free operation. Both linear and non-linear techniques are employed to aggressively reduce echo yet provide for natural full-duplex communication patterns. Copyright © 2006 Polycom, Inc.
Page 67: Audio Codecs
Changes are saved to local flash and backed up to <Ethernet Local address>-phone.cfg on the boot server. Changes will per- manently override global settings unless deleted through the Reset Local Config menu selection. Local Phone User None. Interface Copyright © 2006 Polycom, Inc.
Page 68: Background Noise Suppression (Bns)
3. AGC support will be available in a subsequent release. 4. Notification when a change in monitored status occurs will be available in a subsequent release. Copyright © 2006 Polycom, Inc.
Page 69: Instant Messaging
Support for major western European languages is included and additional languages can be easily added. Support for Asian languages (Chinese, Japanese, and Korean) is also included but will render Copyright © 2006 Polycom, Inc.
Page 71: Downloadable Fonts
<font/> on page 129. 3.5.3 Synthesized Call Progress Tones In order to emulate the familiar and efficient audible call progress feedback generated by the PSTN and traditional PBX equipment, call progress tones are synthesized dur- Copyright © 2006 Polycom, Inc.
Page 72: Advanced Server Features
SIP URL to be called automatically by the phone when the user elects to retrieve messages. Voice mail access can be configured to be through a single key ® press (for example, the Messages key on the SoundPoint IP 300, 301, 430, 500, 501, Copyright © 2006 Polycom, Inc.
Page 73 Changes are saved to local flash and backed up to <Ethernet address>-phone.cfg on the boot server. These changes will permanently override global settings unless deleted through the Reset Local Config menu selection. Local Phone User None. Interface Copyright © 2006 Polycom, Inc.
Page 74: Multiple Registrations
The optional array of serv- ers and their associated parameters will override the servers specified in sip.cfg if non-Null. • For more information, refer to 4.6.2.1 Registration <reg/ > on page 149. Copyright © 2006 Polycom, Inc.
Page 75 Reset Local Config menu selection. • For more information on the fields in this menu, refer to 4.6.1.1.1 Local <local/> on page 85, 4.6.1.1.2 Server <server/> on page 85 and 4.6.2.1 Registration <reg/> on page 149. Copyright © 2006 Polycom, Inc.
Page 76: Acd Login / Logout
The phone can be configured with multiple SIP servers, one primary and one or more backup. The phone will switch to a backup server when the current primary server fails. Backup server configuration can be static or can use advanced DNS methods. In Copyright © 2006 Polycom, Inc.
Page 77: Dns Sip Server Name Resolution
IP phones can used with Microsoft Office Live Communications ® Server 2005 and Microsoft Office Communicator to help improve business efficien- cies and increase productivity and to share ideas and information immediately with business contacts. Copyright © 2006 Polycom, Inc.
Page 78 Specify the line/registration number which has roaming pri- vacy support enabled. • For more information, refer to 4.6.2.9 Roaming Privacy <roaming_privacy/> on page 162. Web Server None. (if enabled) Local Local Phone User None. Interface Copyright © 2006 Polycom, Inc.
Page 79: Configuration File Changes
7. Set reg.1.auth.password to the LCS password. For example, reg.1.auth.password = "Password2" 8. Locate the roaming_buddies attribute. 9. Set the roaming_buddies.reg element to 1. Refer to 4.6.2.8 Roaming Buddies <roaming_buddies/> on page 161. 10. Locate the roaming_privacy attribute. Copyright © 2006 Polycom, Inc.
Page 80 11. Locate the roaming_privacy attribute. 12. Set the roaming_privacy.reg element to the number coresponding to the LCS registration. For example, roaming_privacy.reg = 2. Refer to 4.6.2.9 Roaming Privacy <roaming_privacy/> on page 162. 13. Save the modified Per-Phone Configuration file. Copyright © 2006 Polycom, Inc.
Page 81: Accessory Internet Features
Configuration file: Specify the minimum lengths for the user and administrator Central sip.cfg passwords. (boot • For more information, refer to 4.6.1.20.2 Password server) Lengths <pwd/><length/> on page 141. Copyright © 2006 Polycom, Inc.
Page 82: Custom Certificates
Specify the type of validation to perform on a request-by- sip.cfg request basis, appropriate to specific event types in some Central cases. (boot server) • For more information, refer to 4.6.1.1.4.3 Request Vali- dation <requestValidation/> on page 92. Copyright © 2006 Polycom, Inc.
Page 83: Configuration File Encryption
Change the encryption key. server) <device>.cfg • For more information, refer to section 2.2.2.1.1.3 Set- ting Flash Parameters from Configuration Files on page 16. Web Server (if None. enabled) Local Local Phone User None. Interface Copyright © 2006 Polycom, Inc.
Page 84 The master configuration file cannot be encrypted on the boot server. This file is downloaded by the bootROM that does not recognize encrypted files. For more information, refer to 2.2.2.1.1.1 Master Configuration Files on page 13. Copyright © 2006 Polycom, Inc.
Page 85: Optimization
This allows real-time transport control protocol (RTCP) to operate correctly even with RTP media flowing in only a single direction, or not at all. It also allows greater security: packets from unauthorized sources can be rejected. Copyright © 2006 Polycom, Inc.
Page 87: Updating And Rebooting
. 3. Save the new configuration files and images (such as sip.ld) on the boot server. 4. Reboot the phones. Refer to Manual Reboot: Menu Option or Key Presses on page 80. Copyright © 2006 Polycom, Inc.
Page 88: Event Logging
The event log files are: • <Ethernet address>-boot.log • <Ethernet address>-app.log The boot log file is uploaded to the boot server after every reboot. 5. HTTP and TFTP don’t support append mode unless server settings are changed for this. Copyright © 2006 Polycom, Inc.
Page 89: Audio Quality Issues And Vlans
The “type of service” field in an IP packet header consists of four TOS bits and a 3-bit precedence field. Each TOS bit can be set to either 0 or 1. The precedence field can be Copyright © 2006 Polycom, Inc.
Page 90: Ieee 802.1P/Q
Phase 1: bootRom - Navigate to: SETUP menu during auto- Local boot countdown. Phase 2: Application - Navigate to: Menu>Set- tings>Advanced>Admin Settings>Network Configuration • For more information, refer to 2.2.1 Basic Network Setup on page 5. Copyright © 2006 Polycom, Inc.
Page 91: Rtcp Support
4.5.3 RTCP Support The phone supports RTCP per RFC 1889. For each RTP stream, which, by conven- tion, uses even ports only, the next higher odd port is used to send and receive RTCP reports. Copyright © 2006 Polycom, Inc.
Page 92: Configuration Files
The files are processed in the order listed (left to right). • The same parameters may be included in more than one file. The parameter found first in the list of files will be the one that is effective. Copyright © 2006 Polycom, Inc.
Page 93: Protocol
If set to 1, request string. Type to request from the DHCP server if voIp- Prot.server.dhcp.available = 1. There is no default value for this parameter, it must be filled in with a valid value. Copyright © 2006 Polycom, Inc.

Page 94 IP address, there is no DNS lookup and 5060 is used for the port but it is not advertised in signaling. If port is 1 to 65535: This value is used and it is advertised in signaling. Copyright © 2006 Polycom, Inc.
Page 95 Null or If set to 0 or Null, use standard non-negative RFC 3261 signaling retry integer behavior. Otherwise retryTim- eOut determines how often retries will be sent. Units = milliSeconds. (Finest resolution = 100ms). Copyright © 2006 Polycom, Inc.
Page 97 UPDATE even if remote end point asks for it. voIpProt.SIP.request- 0, 1 If set to 1, ‘+’ global prefix is added to URI.E164.addGlobalPrefix E.164 user parts in sip: URIs:. Copyright © 2006 Polycom, Inc.
Page 98 Default Interpretation voIpProt.SIP.outboundProxy.address dotted-deci- Null IP address or host name and mal IP address port of a SIP server to which or host name the phone shall send all requests. voIpProt.SIP.outboundProxy.port 1 to 65535 5060 Copyright © 2006 Polycom, Inc.
Page 99 (x=1, 2, ..., N) and if a INVITE match is found, the behavior requests described in the correspond- ing ring class (refer to voIpProt.SIP.alertInfo.x.class positive Null 4.6.1.7.2 Ring type <ring- integer Type/> on page 107) will be applied. Copyright © 2006 Polycom, Inc.
Page 100 Prot.SIP.requestValida- tion.x.request is set to “SUBSCRIBE” or “NOTIFY”. If set to Null, all events will be validated. voIpProt.SIP.requestValida- A valid string PolycomSPIP Determines string used for tion.digest.realm Realm. Copyright © 2006 Polycom, Inc.
Page 101 If set to some value, conferences are set up by the server using the conferencing agent specified by this address. The acceptable values depend on the confer- encing server implementation policy. Copyright © 2006 Polycom, Inc.
Page 102: Dial Plan
Timeout in seconds for ‘T’ feature of digitmap. 4.6.1.2.2 Routing <routing/> This configuration section allows the user to create a specific routing path for outgoing SIP calls independent of other ‘default’ configuration. Copyright © 2006 Polycom, Inc.

Page 103: Localization
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 4.6.1.5.2 Chord Sets <chord_sets/> on page 100, and 4.6.1.7.1.1 Call Progress Patterns on page 105. Copyright © 2006 Polycom, Inc.

Page 104 For example: D,dM = Thursday, 3 July or Md,D = July 3, Thursday The field may contain 0, 1 or 2 com- mas which can occur only between characters and only one at a time. For example: “D,,dM” is illegal. Copyright © 2006 Polycom, Inc.
Page 105 6. (Optional) Set lcl.ml.lang to be the new language_region string. 4.6.1.3.2 Date and Time <datetime/> Permitted Attribute Values Interpretation lcl.datetime.time.24HourClock If 1, display time in 24-hour clock mode rather than a.m./p.m. Copyright © 2006 Polycom, Inc.
Page 106: User Preferences
If set to 1, play welcome sound effect after a reboot. up.welcomeSoundOnWarm- 0, 1 If set to 1, play welcome sound effect on BootEnabled warm as well as cold boots, otherwise only a cold boot will trigger the wel- come sound effect. Copyright © 2006 Polycom, Inc.

Page 107: Tones
This prevents DTMF digits being broadcast to other surrounding telephony devices or being inadvert- ently transmitted in-band due to local acoustic echo. Note: tone.dtmf.chassis.masking should only be enabled when tone.dtmf.viaRtp is disabled. Copyright © 2006 Polycom, Inc.

Page 108 There are three blocks of chord sets: • callProg (used for call progress sound effect patterns) • ringer • misc (miscellaneous) All three blocks use the same chord set specification format. Copyright © 2006 Polycom, Inc.
Page 109: Sampled Audio For Sound Effects
Files will be truncated to a maximum size of 300 kilo- bytes. ® ® 6. L16/16000 is not supported on SoundPoint IP 300, 301 and SoundStation IP 4000 phones. Copyright © 2006 Polycom, Inc.

Page 110 Welcome Sound Effect (se.pat.misc.7) Ringer 13 (se.pat.ringer.13) Ringer 14 (se.pat.ringer.14) Ringer 15 (se.pat.ringer.15) Ringer 16 (se.pat.ringer.16) Ringer 17 (se.pat.ringer.17) Ringer 18 (se.pat.ringer.18) Ringer 19 (se.pat.ringer.19) Ringer 20 (se.pat.ringer.20) Ringer 21 (se.pat.ringer.21) Ringer 22 (se.pat.ringer.22) 12-24 Not used. Copyright © 2006 Polycom, Inc.
Page 111: Sound Effects
2000 milliseconds) silence (d) Play silence for d se.pat.callProg.x.inst.y.type = “silence” (silence instruc- milliseconds (Rx tion type) audio is not muted) se.pat.callProg.x.inst.y.value = “300” (specifies silence is to last 300 milliseconds) Copyright © 2006 Polycom, Inc.

Page 112 If instruction type is chord, this optional parameter speci- Prog.x.inst.y.param integer fies the on duration to be used, overriding the on duration specified in the chord-set definition. Copyright © 2006 Polycom, Inc.
Page 113 4.6.1.7.1.2 Ringer Patterns The following table maps ringer pattern numbers to their default descriptions. Ringer pattern number Default description Silent Ring Low Trill Low Double Trill Medium Trill Medium Double Trill High Trill High Double Trill Copyright © 2006 Polycom, Inc.
Page 114 4.6.1.7.1.3 Miscellaneous Patterns The following table maps miscellaneous patterns to their usage within the phone. Miscellaneous pattern number Use within phone new message waiting indication new instant message Not used. local hold notification positive confirmation negative confirmation Copyright © 2006 Polycom, Inc.
Page 115 The call waiting index to be used for this if the type is set to class of ring. The call waiting index should ‘ring’ or ‘ring-answer’ match one defined in 4.6.1.7.1.1 Call Progress Patterns on page 105. Copyright © 2006 Polycom, Inc.
Page 116: Voice Settings
IP 430, 500, 501, 600 voice.codecPref.G711A and 601 platforms. voice.codecPref.G729AB 1 = highest 3 = lowest Null = do not use Give each codec a unique priority, this will dictate the order used in SDP negotiations. Copyright © 2006 Polycom, Inc.

Page 118 If set to 1, the receive volume will be remembered between calls. voice.volume.persist.headset 0, 1 If set to 0, the receive volume will be voice.volume.persist.handsfree 0, 1 reset to nominal at the start of each call. Copyright © 2006 Polycom, Inc.
Page 119 Administrator’s Guide - SoundPoint IP / SoundStation Optimization 4.6.1.8.3 Gains <gains/> The default gain settings have been carefully adjusted to comply with the TIA-810-A digital telephony standard. Note Polycom recommends that you do not change these values. Attribute Default voice.gain.rx.analog.handset voice.gain.rx.analog.headset voice.gain.rx.analog.chassis voice.gain.rx.analog.chassis.IP_300 voice.gain.rx.analog.chassis.IP_430...
Page 120 ® Administrator’s Guide - SoundPoint IP / SoundStation Optimization Attribute Default voice.gain.tx.analog.handset voice.gain.tx.analog.headset voice.gain.tx.analog.chassis voice.gain.tx.analog.chassis.IP_300 voice.gain.tx.analog.chassis.IP_430 voice.gain.tx.analog.chassis.IP_4000 voice.gain.tx.analog.chassis.IP_601 voice.gain.tx.digital.handset voice.gain.tx.digital.headset voice.gain.tx.digital.chassis voice.gain.tx.digital.chassis.IP_4000 voice.gain.tx.digital.chassis.IP_601 voice.gain.tx.digital.chassis.IP_430 voice.gain.tx.analog.preamp.handset voice.gain.tx.analog.preamp.headset voice.gain.tx.analog.preamp.chassis voice.gain.tx.analog.preamp.chassis.IP_430 voice.gain.tx.analog.preamp.chassis.IP_601 voice.handset.rxag.adjust.IP_430 voice.handset.txag.adjust.IP_430 voice.handset.sidetone.adjust.IP_430 voice.headset.rxag.adjust.IP_430 voice.headset.txag.adjust.IP_430 voice.headset.sidetone.adjust.IP_430 Copyright © 2006 Polycom, Inc.
Page 121 Administrator’s Guide - SoundPoint IP / SoundStation Optimization 4.6.1.8.4 Acoustic Echo Cancellation <AEC/> These settings control the performance of the speakerphone acoustic echo canceller. Note Polycom recommends that you do not change these values. Attribute Default voice.aec.hs.enable voice.aec.hs.lowFreqCutOff voice.aec.hs.highFreqCutOff 7000 voice.aec.hs.erlTab_0_300...
Page 122 ® Administrator’s Guide - SoundPoint IP / SoundStation Optimization 4.6.1.8.5 Acoustic Echo Suppression <AES/> These settings control the performance of the speakerphone acoustic echo suppressor. Note Polycom recommends that you do not change these values. Attribute Default voice.aes.hs.enable voice.aes.hs.duplexBalance voice.aes.hd.enable voice.aes.hd.duplexBalance...
Page 123 Administrator’s Guide - SoundPoint IP / SoundStation Optimization 4.6.1.8.6 Background Noise Suppression <NS/> These settings control the performance of the transmit background noise suppression feature. Note Polycom recommends that you do not change these values. Attribute Default voice.ns.hs.enable voice.ns.hs.signalAttn voice.ns.hs.silenceAttn voice.ns.hd.enable voice.ns.hd.signalAttn...
Page 124 ® Administrator’s Guide - SoundPoint IP / SoundStation Optimization 4.6.1.8.8 Receive Equalization <RXEQ/> These settings control the performance of the receive equalizaton feature. Note Polycom recommends that you do not change these values. Attribute Default voice.rxEq.hs.IP_430.preFilter.enable voice.rxEq.hs.IP_500.preFilter.enable voice.rxEq.hs.IP_600.preFilter.enable voice.rxEq.hs.IP_601.preFilter.enable voice.rxEq.hs.IP_430.postFilter.enable voice.rxEq.hs.IP_500.postFilter.enable...
Page 125 IP / SoundStation Optimization Attribute Default voice.rxEq.hf.IP_4000.postFilter.enable 4.6.1.8.9 Transmit Equalization <TXEQ/> These settings control the performance of the hands-free transmit equalization feature. Note Polycom recommends that you do not change these values. Attribute Default voice.txEq.hs.IP_430.preFilter.enable voice.txEq.hs.IP_500.preFilter.enable voice.txEq.hs.IP_600.preFilter.enable voice.txEq.hs.IP_601.preFilter.enable voice.txEq.hs.IP_430.postFilter.enable voice.txEq.hs.IP_500.postFilter.enable voice.txEq.hs.IP_600.postFilter.enable...
Page 126: Quality Of Service
These settings control the Quality of Service (QOS) options. 4.6.1.9.1 Ethernet IEEE 802.1p/Q <Ethernet/> These settings control the 802.1p/Q user_priority field. 4.6.1.9.1.1 RTP <RTP/> These parameters apply to RTP packets. Permitted Attribute Values Default Interpretation qos.ethernet.rtp.user_priority User-priority used for RTP packets. Copyright © 2006 Polycom, Inc.

Page 127 Other- AF33,AF41, wise, these values are overrid- AF42,AF43 den. qos.ip.rtp.min_delay 0, 1 If set to 1, set min-delay bit in the IP TOS field of the IP header, or else don’t set it. Copyright © 2006 Polycom, Inc.
Page 128 IP TOS field of the IP header, or else don’t set it. qos.ip.callControl.min_cost 0, 1 If set to 1, set min-cost bit in the IP TOS field of the IP header, or else don’t set it. Copyright © 2006 Polycom, Inc.
Page 129: Basic Tcp/Ip
If set to 1, set precedence bits in the IP TOS field of the IP header, or else don’t set them. 4.6.1.10 Basic TCP/IP <TCP_IP/> 4.6.1.10.1 Network Monitoring <netMon/> Note Polycom recommends that you do not change these values. Attribute Permitted Values Default tcpIpApp.netMon.enabled 0, 1 tcpIpApp.netMon.period...

Page 130 0, 1 If set to 1, then month Enable and date are used (for example, April 1st); otherwise month, date, and dayOfWeek are used. tcpIpApp.sntp.daylightSavings.start.month 1-12 4 (April) Month to start DST. 1=Jan, 2=Feb, ..., 12=Dec Copyright © 2006 Polycom, Inc.
Page 131 ..., 7=Sat tcpIpApp.sntp.daylightSavings.stop.dayOf- 0, 1 If set to 1 and fixedDay- Week.lastInMonth Enable=0, stop DST on the last day of the week (specified by dayOf- Week) in the month, rather than the first in the month. Copyright © 2006 Polycom, Inc.
Page 132 Subsequent ports will be allocated from a pool starting with the specified port plus two up to a value of (start-port + 46), after which the port number will wrap back to the starting value. Copyright © 2006 Polycom, Inc.
Page 133: Web Server
Time in seconds to allow an incoming call integer to ring before dropping the call, 0=infi- nite call.ringBackTimeOut positive Time in seconds to allow an outgoing call integer to remain in the ringback state before dropping the call, 0=infinite. Copyright © 2006 Polycom, Inc.

Page 134 4.6.1.12.1 Shared Calls <shared/> Permitted Attribute Values Default Interpretation 0, 1 If set to 1, disable diversion feature for call.shared.disableDivert shared lines. call.shared.seizeFailReorder 0, 1 If set to 1, play re-order tone locally on shared line seize failure. Copyright © 2006 Polycom, Inc.
Page 135 Time in seconds between subse- integer quent reminders. call.hold.localReminder.startDelay non-negative Time in seconds to wait before integer the initial reminder. Copyright © 2006 Polycom, Inc.
Page 136: Directory
1 to 100 Maximum size in Kbytes of volatile storage that the direc- tory will be permitted to con- sume. 8. Different phone models have variable flash memory. Copyright © 2006 Polycom, Inc.

Page 137: Presence
• <fontExtension> describes the file type. Either .fnt for single 256 characters font or .fon for multiple .fnt files. 9. .fon file format is a collection of .fnt fonts grouped together within a single file. Copyright © 2006 Polycom, Inc.

Page 138 When defining a single .fon file, there is a need for a “font delimiter”, currently “Copyright Polycom Canada Ltd” is used as an embedded delimiter, but this can be configured using “font.delimiter”. The font delimiter is important to retrieve the dif- ferent mangled .fnt blocks.
Page 139 Interpretation font.IP_600.x.name fontName_height_Uxx Null Defines the font file that will be 00_UyyFF.fon OR loaded from boot server during boot fontName_height_Uxx 00_UxxFF.fnt Note: When several font.IP_600.x.name are defined, the index x must follow consecutive increasing order. Copyright © 2006 Polycom, Inc.
Page 140: Keys
Sets the sub-identifier for key functions with a secondary array identifier such as SpeedDial. The following table lists the functions that are available: Function Function ArrowDown Line1 ArrowLeft Line2 ArrowRight Line3 ArrowUp Line4 Copyright © 2006 Polycom, Inc.

Page 141: Bitmaps
In the following table, x=IP_300, IP_400, IP_500, IP_600, or IP_4000 and y is the bit- map number. Note that IP_300 parameters affect SoundPoint ® IP 300 and 301 phones, ® IP_400 parameters affects SoundPoint IP 430 phones, IP_500 parameters affect Copyright © 2006 Polycom, Inc.

Page 142: Indicators
IP 600 and 601 phones. Attribute Permitted Values Interpretation ind.anim.x.y.frame.z.bitmap A bitmap name Bitmap to use. defined previously. Note that it must be defined already, refer to 4.6.1.17.1 Platform <IP_300/>, <IP_400/>, <IP_500/>, <IP_600/> and <IP_4000/> on page 133. Copyright © 2006 Polycom, Inc.

Page 143 This section assigns a type, a class, and, in the case of the GraphicIcon type, a physical location and size in pixels on the LCD display or in the case of the LED type, a physi- cal LED number. Copyright © 2006 Polycom, Inc.
Page 144 For GraphicIcon type indicators, this is the y-axis loca- tion of the upper left corner of the indicator measured in IP 400: 0-45 pixels from top to bottom. IP 500: 0-79 IP 600: 0-159 IP 4000: 0-67 Copyright © 2006 Polycom, Inc.
Page 145: Event Logging
IP 4000: 1-68 4.6.1.19 Event Logging <logging/> Important Logging parameter changes can impair system operation. Do not change any logging parameters with- out prior consultation with Polycom Customer Support. The event logging system supports the following classes of events: Level Interpretation...

Page 146 This is the output filter from the internal mem- ory-based log system. log.render.type Refer to above table for times- tamp type. log.render.realtime 0, 1 Set to 1. Note: Polycom recommends that you do not change this value. Copyright © 2006 Polycom, Inc.
Page 147 Maximum log file size on boot integer server in Kbytes. log.render.file.upload.append.limit- delete, stop delete Behavior when server log file Mode has reached its limit. delete=delete file and start over stop=stop appending to file Copyright © 2006 Polycom, Inc.
Page 148: Security
The phone can be configured to schedule certain advanced logging tasks on a periodic basis. These attributes should be set in consultation with Polycom. Each scheduled log task is controlled by a unique attribute set starting with log.sched.x where x identifies the task.

Page 149 4.6.1.20.2 Password Lengths <pwd/><length/> Permitted Attribute Values Default Interpretation sec.pwd.length.admin 0-32 Password changes will need to be at least this long. Use 0 to allow null passwords. sec.pwd.length.user 0-32 Copyright © 2006 Polycom, Inc.
Page 150: Provisioning
Permitted Attribute Values Default Interpretation ramdisk.enable 0, 1 If set to 1, RAM disk will be available. The RAM disk is used to cache downloaded wave files, and other resources for the user interface. Copyright © 2006 Polycom, Inc.

Page 152: Feature
If set to 1, the feature will be enabled and usable by the local user. Note: The "url-dialing" feature must be disabled by setting feature.9.enabled to 0 in order to prevent unknown callers from being identified on the display by an IP address. Copyright © 2006 Polycom, Inc.

Page 153: Resource
The name of the sub-application for which the particu- map”, or “font” lar quota will apply: • “tone” relates to all downloaded tones and sound effects • “bitmap” relates to all downloaded bitmaps • “font” relates to all downloaded fonts Copyright © 2006 Polycom, Inc.

Page 154: Microbrowser
If empty, characters. there will be no MicroBrowser idle dis- play feature. Note that the MicroBrowser idle display will displace the idle display indicator (refer to ind.idleDisplay.enabled in 4.6.1.18 Indicators <indicators/> on page 134). Copyright © 2006 Polycom, Inc.

Page 155 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. Copyright © 2006 Polycom, Inc.
Page 157: Per-Phone Configuration - Phone1.Cfg
1002@polycom.com or reg.x.address=”1002@polycom.com”. reg.x.label UTF-8 encoded Null Text label to appear on the display string adjacent to the associated line key. If omitted, the label will be derived from the user part of reg.x.address. Copyright © 2006 Polycom, Inc.
Page 158 Null Password to be used for authentication challenges for this registration. If non- Null, will override the “Reg Password x” parameter entered into the Authenti- cation submenu off of the Settings menu on the phone. Copyright © 2006 Polycom, Inc.
Page 159 = 6 on IP 600, max = 24 on IP 601 (without any Expansion Modules attached, only 6 line keys are available) The number of line keys on the phone to be associated with registration ‘x’. Copyright © 2006 Polycom, Inc.
Page 160 5061. Note: TLS is not supported on Sound- ® Point IP 300 and 500 phones. reg.x.proxyRequire string Null The string that needs to appear in the “Proxy-Require” header. If Null, no "Proxy-Require" will be sent. Copyright © 2006 Polycom, Inc.
Page 161: Calls
Null cally placed to the digits (the user part of a SIP contact specified URL) or a string that constitutes upon going off a valid SIP URL (6416 or hook on this regis- 6416@polycom.com) tration. Copyright © 2006 Polycom, Inc.

Page 162: Diversion
Divert feature of the direc- tory. This is a global flag. divert.x.sharedDisabled 0, 1 If set to 1, all diversion fea- tures on that line will be disabled if the line is con- figured as shared. Copyright © 2006 Polycom, Inc.
Page 163 Permitted Values Default Interpretation divert.noanswer.x.enabled 0, 1 If set to 1, calls will be for- warded on no answer to the contact specified. divert.noanswer.x.timeout positive integer Time in seconds to allow altering before initiating the diversion. Copyright © 2006 Polycom, Inc.
Page 164: Dial Plan
0, 1 or 2 When present, and if dial- plan.x.digitmap is not Null, this attribute overrides the global dial plan defined in the sip.cfg configuration file. For interpretation, refer to 4.6.1.2 Dial Plan <dialplan/> on page 94. Copyright © 2006 Polycom, Inc.

Page 165 Null When present, and if dial- plan.x.digitmap is not Null, this attribute overrides the global dial plan defined in the sip.cfg configuration file. For more information, refer to 4.6.1.2.1 Digit Map <digitmap/> on page 94. Copyright © 2006 Polycom, Inc.
Page 167: Messaging
ASCII encoded string con- Null Contact to call when taining digits (the user part retrieving messages for this of a SIP URL) or a string registration. that constitutes a valid SIP URL (6416 or 6416@poly- com.com) Copyright © 2006 Polycom, Inc.

Page 168: Network Address Translation
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. Copyright © 2006 Polycom, Inc.

Page 169: Attendant
If value < 1, then value is replaced with 1. Warning: This parameter must be enabled (value ® < 0) if the call server is Microsoft Office Live Communications Server 2005. Copyright © 2006 Polycom, Inc.

Page 170: Roaming Privacy
Attribute Values Default Interpretation roaming_privacy.re positive Null Specifies the line/registration number which has integer roaming privacy support enabled. If Null, roam- ing privacy is disabled. If value < 1, then value is replaced with 1. Copyright © 2006 Polycom, Inc.

Page 171: Administrator's Guide - Soundpoint
Session Initiation Protocol (SIP) - Specific Event Notification RFC 3515 The Session Initiation Protocol (SIP) Refer Method draft-ietf-sip-cc-transfer-05.txt SIP Call Control - Transfer RFC 3891 The Session Initiation Protocol (SIP) “Replaces” Header 5.1.2 Request Support Method Supported Notes REGISTER INVITE CANCEL Copyright © 2006 Polycom, Inc.
Page 172: Header Support
In the following table, a “Yes” in the Supported column means the header is sent and properly parsed. Header Supported Notes Accept Accept-Encoding Accept-Language Alert-Info Allow Allow-Events Authentication-Info Authorization Call-ID Call-Info Contact Content-Disposition Content-Encoding Content-Language Content-Length Content-Type CSeq Date Diversion Copyright © 2006 Polycom, Inc.
Page 173 Session Initiation Protocol (SIP) Header Supported Notes Error-Info Event Expires From In-Reply-To Max-Forwards Min-Expires Min-SE MIME-Version Organization P-Asserted-Identity P-Preferred-Identity Priority Proxy-Authenticate Proxy-Authorization Proxy-Require RAck Record-Route Refer-To Referred-By Remote-Party-ID Replaces Reply-To Require Retry-After Route RSeq Server Session-Expires Subject Subscription-State Copyright © 2006 Polycom, Inc.
Page 174: Response Support
5.1.4.1 1xx Responses - Provisional Response Supported Notes 100 Trying 180 Ringing 181 Call Is Being Forwarded 182 Queued 183 Session Progress 5.1.4.2 2xx Responses - Success Response Supported Notes 200 OK 202 Accepted In REFER transfer. Copyright © 2006 Polycom, Inc.
Page 175: 3Xx Responses - Redirection
404 Not Found 405 Method Not Allowed 406 Not Acceptable 407 Proxy Authentication Required 408 Request Timeout 410 Gone 413 Request Entity Too Large 414 Request-URI Too Long 415 Unsupported Media Type 416 Unsupported URI Scheme Copyright © 2006 Polycom, Inc.
Page 176: 5Xx Responses - Server Failure
493 Undecipherable 5.1.4.5 5xx Responses - Server Failure Response Supported Notes 500 Server Internal Error 501 Not Implemented 502 Bad Gateway 503 Service Unavailable 504 Server Time-out 505 Version Not Supported 513 Message Too Large Copyright © 2006 Polycom, Inc.
Page 177: 6Xx Responses - Global Failure
The phone supports transfer using the REFER method specified in draft-ietf-sip-cc- transfer-05 and RFC 3515. 5.1.8 Third Party Call Control The phone supports the delayed media negotiations (INVITE without SDP) associated with third party call control applications. Copyright © 2006 Polycom, Inc.
Page 178: Protocol Extensions
SIP Extensions for Network-Asserted Caller Identity and Privacy within Trusted Networks draft-ietf-sip-referredby-05.txt SIP Referred by Mechanism draft-levy-sip-diversion-06.txt Diversion Indication in SIP draft-ietf-sipping-cc-conferencing- SIP Call Control - Conferencing for User Agents 03.txt draft-ietf-sip-connect-reuse-04 Connection Reuse in the Session Initiation Protocol (SIP) Copyright © 2006 Polycom, Inc.
Page 179: Request Support
The phone supports shared call appearances (SCA) using the SUBSCRIBE-NOTIFY method in the “SIP Specific Event Notification” framework (RFC 3265). The events used are: • “call-info” for call appearance state notification • “line-seize for the phone to ask to seize the line Copyright © 2006 Polycom, Inc.
Page 180: Bridged Line Appearance Signaling
The phone supports bridged line appearances (BLA) using the SUBSCRIBE-NOTIFY method in the “SIP Specific Event Notification” framework (RFC 3265). The events used are: • “dialog” for bridged line appearance subscribe and notify Copyright © 2006 Polycom, Inc.
Page 181: Trusted Certificate Authority List
Equifax Premium CA Equifax Secure CA GTE CyberTrust Global Root GTE CyberTrust Japan Root CA GTE CyberTrust Japan Secure Server CA GTE CyberTrust Root 2 GTE CyberTrust Root 3 GTE CyberTrust Root 4 GTE CyberTrust Root 5 Copyright © 2006 Polycom, Inc.
Page 182 Verisign Class 2 Public Primary Certification Authority - G2 Verisign Class 2 Public Primary Certification Authority - G3 Verisign Class 3 Public Primary Certification Authority Verisign Class 3 Public Primary Certification Authority - G2 Verisign Class 3 Public Primary Certification Authority - G3 Copyright © 2006 Polycom, Inc.
Page 183: Miscellaneous Administrative Tasks
IP 4000 phone only supports black and white. Any other colors will be rendered as either black or white. RGB Values RGB Values Color (Decimal) (Hexadecimal) Black 0,0,0 00,00,00 Dark Gray 96,96,96 60,60,60 Light Gray 160,160,160 A0,A0,A0 White 255,255,255 FF,FF,FF Copyright © 2006 Polycom, Inc.
Page 184 Many configuration-generation systems do not make it easy to customize the contents of this file based on the model; if you are using one of these systems, you can have all phones download all the bitmaps: MISC_FILES="logo-500.bmp, logo-600.bmp, logo-4000.bmp" [for all phones] Copyright © 2006 Polycom, Inc.
Page 185: Third Party Software Attribution
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/)" Copyright © 2006 Polycom, Inc.
Page 186 1. Redistributions of source code must retain the copyright notice, this list of condi- tions 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. Copyright © 2006 Polycom, Inc.
Page 187 2. Altered source versions must be plainly marked as such, and must not be misrepre- sented 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 Copyright © 2006 Polycom, Inc.
Page 188 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. Copyright © 2006 Polycom, Inc.

This manual is also suitable for:

Soundpoint ip 430 Soundpoint ip 500 Soundpoint ip 601 Soundpoint ip 600 Soundpoint ip 301 Soundpoint ip 501

Polycom SoundPoint IP 300 Administrator's Manual

1 Overview

2 Installation and Operation

3 Features

4 Optimization

5 Session Initiation Protocol (SIP)

6 Appendix 1

7 Appendix 2

Quick Links

Need help?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Polycom SoundPoint IP 300

Summary of Contents for Polycom SoundPoint IP 300

This manual is also suitable for:

Table of Contents