Polycom SoundPoint IP 600 SIP Administrator's Manual

Hide thumbs Also See for SoundPoint IP 600 SIP:

User manual (37 pages)

Quick reference manual (11 pages)

User manual (39 pages)

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

Table Of Contents

134

page of 134

/ 134
Contents
Table of Contents
Bookmarks

Table of Contents

Quick Links

Download this manual See also: User Manual, Quick Reference Manual

Administrator Guide

SoundPoint

IP SIP

Version 1.2.0

4 March 2004

Table of Contents

Summary of Contents for Polycom SoundPoint IP 600 SIP

Page 1: Administrator Guide
Administrator Guide SoundPoint IP SIP ® Version 1.2.0 4 March 2004 Copyright © 2004 Polycom, Inc. All rights reserved.
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-11518-120 Rev A Copyright © 2004 Polycom, Inc. All rights reserved.
Page 3 3.1.13 Distinctive Call Waiting ......................... 23 3.1.14 Do-Not-Disturb..........................24 3.1.15 Handset, Headset, and Speakerphone ................... 24 3.1.16 Local Contact Directory ......................... 25 3.1.16.1 Local Contact Directory File Format..................26 3.1.17 Local Digit Map ..........................27 3.1.18 Microphone Mute ......................... 28 Copyright © 2004 Polycom, Inc.
Page 4 3.5.1 Multilingual User Interface ......................41 3.5.2 Downloadable Fonts ........................43 3.5.3 Synthesized Call Progress Tones...................... 43 3.6 Advanced Server Features ........43 3.6.1 Voicemail Integration ........................43 3.6.2 Multiple Registrations........................44 3.6.3 Server Redundancy ........................45 Copyright © 2004 Polycom, Inc.
Page 5 4.6.1.9 Web Server <HTTPD/>......................82 4.6.1.10 Call Handling Configuration <call/> ..................83 4.6.1.11 Directory <directory/>.......................84 4.6.1.12 Fonts <font/>........................85 4.6.1.13 Keys <keys/> ........................88 4.6.1.14 Bitmaps <bitmaps/>......................91 4.6.1.15 Indicators <indicators/>.....................92 4.6.1.16 Event Logging <logging/> ....................94 4.6.1.17 Security <security/> ......................97 Copyright © 2004 Polycom, Inc.
Page 6 5.2 Protocol Extensions..........125 5.2.1 RFC and Internet Draft Support....................... 126 5.2.2 Request Support..........................126 5.2.3 Header Support..........................126 5.2.4 SIP for Instant Messaging and Presence Leveraging Extensions (SIMPLE).......... 126 5.2.5 Shared Call Appearance Signaling ....................127 Copyright © 2004 Polycom, Inc.
Page 7: Overview
SoundPoint ® is capable of vastly more than traditional business telephones. As SoundPoint runs the same protocols as your office personal computer, many innovative applica- Copyright © 2004 Polycom, Inc.
Page 8 IP’s diverse application potential, it is fundamentally a good office tele- phone, providing the productivity enhancing features needed today such as multiple call appearances, full-duplex speakerphone, hold, transfer, conference, forward, voice mail compatibility, and contact directory. Copyright © 2004 Polycom, Inc.
Page 9: Installation And Operation
SoundPoint IP Local User Interface MAC 00:04:f2:00:29:99 Local Web Server A boot server allows global and per-phone configuration to be managed centrally via text XML-format configuration files that are downloaded by the telephones at boot Copyright © 2004 Polycom, Inc.
Page 10: Installation Process
Polycom recommends the boot server central provisioning model for installations involving more than a few telephones. The investment required is minimal in terms of time and equipment, and the benefits are significant.
Page 11: Dhcp Or Manual Tcp/Ip Setup
2.2.1.1 DHCP or Manual TCP/IP Setup Basic network settings can be derived from DHCP or entered manually using the tele- phone’s LCD-based user interface. Polycom recommends using DHCP where possi- ble to eliminate repetitive manual data entry. The following table shows the manually entered networking parameters that may be...
Page 12: Local User Interface Setup Menus
IP Telephone’s IP address. address Note: Disabled when DHCP client is enabled. Subnet Mask dotted-decimal subnet Telephone’s subnet mask. mask Note: Disabled when DHCP client is enabled. IP Gateway dotted-decimal IP Telephone’s default router. address Copyright © 2004 Polycom, Inc.
Page 13 The DHCP menu is accessible only when the DHCP client is enabled. DHCP config- uration parameters are described in the following table: Possible Name Values Description Timeout 1 through 600 Number of seconds the telephone waits for secondary DHCP Offer messages before selecting an offer. Copyright © 2004 Polycom, Inc.
Page 14: Server Menu
Boot Server parameter is set domain name string to Static. any string When the Server Type parameter is set to FTP, FTP User this is the user name used when the telephone logs into the FTP server. Copyright © 2004 Polycom, Inc.
Page 15: Reset To Factory Defaults
6. The boot server copy of the application images and configuration files can be used to “repair” a damaged telephone configuration in the same way that system repair disks work for PCs. The following sections discuss the available configuration options. Copyright © 2004 Polycom, Inc.
Page 16: Centralized Configuration
The master configuration file, which references the other files and is always down- loaded and parsed by the telephone, will need to change to reflect these name changes. Polycom does not recommend TFTP boot servers for actively managed systems. File name management is the responsibility of the System Administrator.
Page 17 If a telephone 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 18 Typical parameters include the IP address of an application server. All telephones in an installation usually share application-specific files. This file would normally be modified from Polycom tem- plates. User Contain parameters unique to a particular telephone user. Typical phone1.cfg...
Page 19 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.) Edit <application>.cfg: See 4.6.2 SIP Configuration - sip.cfg on page 101, particularly for SIP server address. Copyright © 2004 Polycom, Inc.
Page 20 • time and date format Decide on FTP server security pol- Polycom recommends allowing file uploads to the icy: FTP server where the security environment permits. This allows event log files to be uploaded and changes made by the telephone user to the configuration (via the web server and local user interface) and changes made to the directory to be backed up.
Page 21: Local Telephone Configuration
Changes made via the web server or local user interface are stored internally as over- rides. These overrides take precedence over settings contained in the configuration obtained from the boot server that existed previously within the telephone. Copyright © 2004 Polycom, Inc.
Page 22: Sip Authentication Parameters
For more information, see 4.6.3.1 Registration <reg/> on page 108. Reg User x should contain the authentication username for the first registration (corresponds to reg.x.auth.userId) and Reg Password x should contain the corresponding password (corresponds to reg.x.auth.password). Copyright © 2004 Polycom, Inc.
Page 23: Features
3.1.4 Called Party Identification ® SoundPoint IP displays and logs the identity of the remote party specified for outgo- ing calls. This is the party that the user intends to connect with. Copyright © 2004 Polycom, Inc.
Page 24: Calling Party Identification
For more information, see 4.6.1.13 Keys <keys/> on server) page 88. Web Server None. (if enabled) Local Local Telephone None. User Interface The following diagrams and table show the default SIP key layouts for SoundPoint ® IP 500 and IP 600 models. Copyright © 2004 Polycom, Inc.
Page 25 Call Lists Messages Conference Do Not Disturb Transfer PQRS WXYZ Redial Hold Hold PQRS WXYZ OPER OPER Key ID SoundPoint IP 600 SIP Key Layout Directories Menu Services Messages Conference Do Not Disturb Transfer Redial PQRS WXYZ Hold PQRS WXYZ Hold...
Page 26 Dialpad0 DialpadStar DialpadStar Dialpad9 Dialpad9 Dialpad8 Dialpad8 Dialpad7 Dialpad7 Dialpad4 Dialpad4 Dialpad5 Dialpad5 Dialpad6 Dialpad6 Dialpad3 Dialpad3 Dialpad2 Dialpad2 Dialpad1 Dialpad1 SoftKey4 SoftKey4 SoftKey3 SoftKey3 SoftKey2 SoftKey2 SoftKey1 SoftKey1 Conference Services CallHistory Directories Services Line6 Copyright © 2004 Polycom, Inc.
Page 27: Connected Party Identification
Sound effects can be composed of patterns of synthesized tones or sample audio files. The default sample audio files may be replaced with alter- nates in .wav file format. Supported .wav formats include: • mono G.711 (13-bit dynamic range, 8-khz sample rate), Copyright © 2004 Polycom, Inc.
Page 28: Message Waiting Indication
Call attributes that can trigger distinctive treatment include the calling party name or SIP contact (number or URL format). Administration: Distinctive Incoming Call Treatment For more information, see 3.1.16 Local Contact Directory on page 25. Copyright © 2004 Polycom, Inc.
Page 29: Distinctive Ringing
Specify the mapping of Alert-Info strings to call waiting Central sip.cfg types. (boot • For more information, see 4.6.2.1.3.2 Alert Informa- server) tion <alertInfo/> on page 104. Web Server None. (if enabled) Local Local Phone User None. Interface Copyright © 2004 Polycom, Inc.
Page 30: Do-Not-Disturb
Enable or disable persistent headset mode via the Settings Local Interface 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 via the Reset User Settings menu. Copyright © 2004 Polycom, Inc.
Page 31: Local Contact Directory
Local backed up to the boot server copy of <Ethernet address>-directory.xml if this is configured. When the telephone boots, the boot server copy of the directory, if present, will overwrite the local copy. Copyright © 2004 Polycom, Inc.
Page 32: 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 © 2004 Polycom, Inc.
Page 33: Local Digit Map
If auto-divert is also enabled, it has precedence over auto-reject. 3.1.17 Local Digit Map SoundPoint ® IP has a local digit map feature to automate the setup phase of number- only calls. When properly configured, this feature eliminates the need for using the Copyright © 2004 Polycom, Inc.
Page 34: Microphone Mute
“call waiting” style. Soft keys with call disposition options are presented to the user. The current user interface is limited to two concurrent calls per registration (line). This is an artificial limit and will be expanded in the future. Copyright © 2004 Polycom, Inc.
Page 35: Shared Call Appearances
• For more information, see 4.6.3.1 Registration <reg/> on page 108. Specify per-registration whether diversion should be dis- abled on shared lines. • For more information, see 4.6.3.3 Diversion <divert/> on page 111. Copyright © 2004 Polycom, Inc.
Page 36: Customizable Fonts And Indicators
Central (boot • For more information, see 4.6.1.14 Bitmaps <bitmaps/> server) on page 91. Specify how to create animations and LED indicator patterns. • For more information, see 4.6.1.15 Indicators <indicators/ > on page 92. Copyright © 2004 Polycom, Inc.
Page 37: Soft Key-Driven User Interface
<Ethernet address>-direc- tory.xml if this is configured. When the tele- phone boots, the boot server copy of the directory, if present, will overwrite the local copy. Copyright © 2004 Polycom, Inc.
Page 38: Time And Date Display
The user can edit the time and date format under the Set- tings 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 via the Reset User Settings menu selection. Copyright © 2004 Polycom, Inc.
Page 39: Call Management Features
103. (boot server) Configuration file: Specify local hold reminder options. ipmid.cfg • For more information, see 4.6.1.10.1 Hold, Local Reminder <localReminder/> on page 84. Web Server None. (if enabled) Local Local Phone User None. Interface Copyright © 2004 Polycom, Inc.
Page 40: Call Transfer
Central ward busy, call forward no-answer, and call forward do-not- (boot disturb. server) • For more information, see 4.6.3.3 Diversion <divert/> on page 111. Copyright © 2004 Polycom, Inc.
Page 41: Audio Processing Features
Configuration file: Set the jitter buffer tuning parameters including minimum Central ipmid.cfg and maximum size and shrink aggression. (boot • For more information, see 4.6.1.6.1.2 Codec Profiles server) <profiles/> on page 69. Copyright © 2004 Polycom, Inc.
Page 42: Local Conference Mixing
Enable or disable VAD and set the detection threshold. Central ipmid.cfg (boot • For more information, see 4.6.1.6.10 Voice Activity server) Detection <VAD/> on page 77. Web Server None. (if enabled) Local Local Phone User None. Interface Copyright © 2004 Polycom, Inc.
Page 43: Dtmf Tone Generation
3.3.7 Acoustic Echo Cancellation (AEC) ® SoundPoint IP employs advanced acoustic echo cancellation for hands-free opera- tion. Both linear and non-linear techniques are employed to aggressively reduce echo yet provide for natural full-duplex communication patterns. Copyright © 2004 Polycom, Inc.
Page 44: 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 via the Reset User Settings menu selection. Local Phone User None. Interface Copyright © 2004 Polycom, Inc.
Page 45: Background Noise Suppression (Bns)
• For more information, see 4.6.1.6.7 Automatic Gain Control <AGC/> on page 76. Web Server None. (if enabled) Local Local Phone User None. Interface 2. AGC support will be available in a subsequent release. Copyright © 2004 Polycom, Inc.
Page 46: Presence And Instant Messaging Features
IP supports sending and receiving instant text messages. The user is alerted to incoming messages visually and audibly. The user can choose to view the 3. Notification when a change in monitored status occurs will be available in a subsequent release. Copyright © 2004 Polycom, Inc.
Page 47: Localization Features
CJK Symbols and Punctuation U+3000 - U+303F Hiragana U+3040 - U+309F Katakana U+30A0 - U+30FF Bopomofo U+3100 - U+312F 4. Within a Unicode range, some characters may not be supported due to their infrequent usage. Copyright © 2004 Polycom, Inc.
Page 48 Local Interface tings 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 via the Reset User Settings menu selection. Copyright © 2004 Polycom, Inc.
Page 49: Downloadable Fonts
The telephone can be configured with a SIP URL to be called automatically by the telephone when the user elects to retrieve messages. Voicemail access can be configured to be via a Copyright © 2004 Polycom, Inc.
Page 50: Multiple Registrations
Local Phone User None. Interface 3.6.2 Multiple Registrations SoundPoint ® IP supports multiple registrations per telephone. Each registration is mapped to the familiar concept of a telephone line. The user can select which line to Copyright © 2004 Polycom, Inc.
Page 51: Server Redundancy
IP can be configured with multiple SIP servers, one primary and one or ® more backup. SoundPoint IP will switch to a backup server when the current primary server fails. Backup server configuration can be static or use advanced DNS methods. Copyright © 2004 Polycom, Inc.
Page 52: Dns Sip Server Name Resolution
Configuration file: Specify the minimum lengths for the user and administrator Central ipmid.cfg passwords. (boot • For more information, see 4.6.1.17.1 Password Lengths server) <pwd/><length> on page 97. Copyright © 2004 Polycom, Inc.
Page 53: Incoming Signaling Validation
Central cases. (boot server) • For more information, see 4.6.2.1.3.3 Request Valida- tion <requestValidation/> on page 104. Web Server (if None. enabled) Local Local Phone User None. Interface Copyright © 2004 Polycom, Inc.
Page 54 ® Administrator Guide - SoundPoint Features Copyright © 2004 Polycom, Inc.
Page 55: Optimizing Soundpoint
® SoundPoint IP can filter incoming RTP packets arriving on a particular port by IP address. Packets arriving from a non-negotiated IP address can be discarded. Copyright © 2004 Polycom, Inc.
Page 56: Working With Network Address Translation (Nat)
IP address and ports used by the NAT on the telephone’s behalf can be configured on a per-telephone basis. Copyright © 2004 Polycom, Inc.
Page 57: Updating And Rebooting
3. Save the new configuration files and images (such as sip.ld) on the boot server. 4. Reboot the telephones (see below). For more information, see 2.2.2 Application Configuration on page 9. 5. For TFTP, refer to 2.2.2.1.1 FTP vs. TFTP on page 10 Copyright © 2004 Polycom, Inc.
Page 58: Event Logging
As an additional diagnostic tool, both log files can be uploaded on demand to the boot server by pressing and holding the four arrow keys until a confirmation tone is heard or for about three seconds. Log files uploaded in this manner are named: • <Ethernet address>-now-boot.log • <Ethernet address>-now-app.log Copyright © 2004 Polycom, Inc.
Page 59: Audio Quality Issues And Vlans
RTP packets and call control packets, such as SIP signaling packets. Configuration file: Specify protocol-specific IP TOS settings. Central ipmid.cfg (boot • For more information, see 4.6.1.7.2 IP TOS <IP/> on server) page 78. Copyright © 2004 Polycom, Inc.
Page 60: Ieee 802.1P/Q
® SoundPoint IP supports RTCP per RFC 1889. For each RTP stream, which, by con- ® vention, uses even ports only, SoundPoint IP uses the next higher odd port to send and receive RTCP reports. Copyright © 2004 Polycom, Inc.
Page 61: Configuration Files
The call progress tones can also be custom- ized. For more information, see 4.6.1.1.3 Call Progress Tones <callProgTones> on page 58, 4.6.1.3.2 Chord Sets <chord_sets/> on page 61, and 4.6.1.5.1.1 Call Progress Patterns on page 65. Copyright © 2004 Polycom, Inc...
Page 62 The call progress tone index to be associated to this language. See 4.6.1.1.3 Call Progress Tones <call- ProgTones> on page 58. lcl.ml.lang.clock.x.24HourClock If attribute present, overrides lcl.datetime.time.24HourClock; If 1, display time in 24-hour clock mode rather than a.m./p.m. Copyright © 2004 Polycom, Inc.
Page 63 4. Add a lcl.ml.lang.clock.menu.x attribute to the configuration file. 5. Add lcl.ml.lang.clock.x.24HourClock, lcl.ml.lang.clock.x.format, lcl.ml.lang.clock.x.longFormat and lcl.ml.lang.clock.x.dateTop attributes and set them according to the regional preferences. 6. (Optional) Set lcl.ml.lang to be the new language_region string. Copyright © 2004 Polycom, Inc...
Page 64 String to specify the country or region e.g. Italy. Multiple lcl.cpt.menu.x strings are supported, the strings are displayed in the Call Progress Tones menu. The lcl.cpt.menu.x attributes must be sequential (lcl.cpt.menu.1, lcl.cpt.menu.2, lcl.cpt.menu.3, ..., lcl.cpt.menu.N) with no gaps. Copyright © 2004 Polycom, Inc.
Page 65: User Preferences
0, 1 If set to 1, the voicemail summary dis- play is bypassed and voicemail is dialed directly (if configured). Copyright © 2004 Polycom, Inc...

Page 66: 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. tone.dtmf.stim.pac.offHookOnly 0, 1 Not currently used. Copyright © 2004 Polycom, Inc.

Page 67 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 © 2004 Polycom, Inc...
Page 68: Sampled Audio For Sound Effects
Internet. Note: Refer to the Note: A TFTP URL is expected to be in the format: above wave file for- tftp://<host>/[pathname]<filename>, for example: tftp:// mat restrictions. somehost.example.com/sounds/example.wav Copyright © 2004 Polycom, Inc.

Page 69: Sound Effects
(voice-mail) are waiting at the message center. se.appLocalEnabled 0, 1 If set to 1, local user interface sound effects such as confirmation/error tones, will be enabled. Copyright © 2004 Polycom, Inc...

Page 70 (currently used for ringer patterns only); for patterns that use a sampled 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. Copyright © 2004 Polycom, Inc.
Page 72 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, see 4.6.1.4 Sampled Audio for Sound Effects <sampled_audio/> on page 62. Copyright © 2004 Polycom, Inc.
Page 73 In the following table, x is the ring class number. The x index needs to be sequential. Attribute Permitted Values Interpretation se.rt.enabled Set to 1 to enable the ring type feature within the telephone, 0 otherwise. Copyright © 2004 Polycom, Inc...
Page 74: Voice Settings
Frame Size Bandwidth G.711µ-law PMCU G711mu 64 Kbps 8 Ksps 10ms - 80ms 3.5KHz G.711a-law PCMA G711A 64 Kbps 8 Ksps 10ms - 80ms 3.5KHz G.729AB G729 G729AB 8 Kbps 8 Ksps 10ms - 80ms 3.5KHz Copyright © 2004 Polycom, Inc.

Page 76 The default gain settings have been carefully adjusted to comply with the TIA-810-A digital telephony standard. Changing these is not advised. Permitted TIA-810-A Attribute Values Default Interpretation voice.gain.rx.analog.handset -30, -27, -24, Rx analog gain in dB when ..., 0 using handset. Copyright © 2004 Polycom, Inc.
Page 77 Tx analog gain in dB when using speakerphone. voice.gain.tx.digital.handset 60, -57, -54, Tx digital gain in dB when ..., 30 using handset. voice.gain.tx.digital.headset Tx digital gain in dB when using headset. voice.gain.tx.digital.chassis Tx digital gain in dB when using speakerphone. Copyright © 2004 Polycom, Inc...
Page 78 DSP is going to be per- formed. All Tx outside this fre- quency range will Tx to zero. These limits have no effect when there is no DSP being performed (such as in the low delay handset mode). Copyright © 2004 Polycom, Inc.
Page 79 -30, -29, ..., 0 See voice.aec.hs.erlTab_300_600 voice.aec.hd.erlTab_600_1500 -30, -29, ..., 0 voice.aec.hs.erlTab_600_1500 voice.aec.hd.erlTab_1500_3500 -30, -29, ..., 0 voice.aec.hs.erlTab_1500_3500 voice.aec.hd.erlTab_3500_7000 -30, -29, ..., 0 voice.aec.hs.erlTab_3500_7000 voice.aec.hf.enable 0, 1 If set to 1, enable AEC for hands- free. Copyright © 2004 Polycom, Inc...
Page 80 If set to 1, enable AES for handsfree. voice.aes.hf.duplexBalance.0 0, 1, 2, ..., 15 Index into table of pre-defined full/ half-duplex tuning parameters for duplex balance at hands-free Rx digi- tal gain values of -9 dB and lower. Copyright © 2004 Polycom, Inc.
Page 81 15 dB 4.6.1.6.6 Background Noise Suppression <NS/> These settings control the performance of the transmit background noise suppression feature. Permitted Attribute Values Default Interpretation voice.ns.hs.enable 0, 1 If set to 1, enable NS for handset. Copyright © 2004 Polycom, Inc...
Page 82 These settings control the performance of the handsfree receive equalizaton feature. Permitted Attribute Values Default Interpretation voice.rxEq.hf.IP_500.enable 0, 1 If set to 1, enable Rx equalization for handsfree (IP 500). voice.rxEq.hf.IP_600.enable 0, 1 If set to 1, enable Rx equalizaton for handsfree (IP 600). Copyright © 2004 Polycom, Inc.
Page 83 The threshold for determining what is active 0 to 30 voice and what is background noise in dB. This does not apply to G.729AB codec operation which has its own built-in VAD function. Copyright © 2004 Polycom, Inc...
Page 84: Quality Of Service
These default parameter values are used for all packets which are not set explicitly. Permitted Attribute Values Default Interpretation qos.ethernet.other.user_priority User-priority used for packets that do not have a per-protocol setting. 4.6.1.7.2 IP TOS <IP/> These settings control the “type of service” field in outgoing packets. Copyright © 2004 Polycom, Inc.

Page 85 If set to 1, set min-cost bit in the IP TOS field of the IP header, or else don’t set it. qos.ip.callControl.precedence If set to 1, set precedence bits in the IP TOS field of the IP header, or else don’t set them. Copyright © 2004 Polycom, Inc...
Page 86: Basic Tcp/Ip
0, 1 If set to 1, apply day- light savings rules to displayed time. tcpIpApp.sntp.daylightSavings.fixedDay- 0, 1 If set to 1, “April 1st” is Enable used, otherwise “the first Sunday in April” is used. Copyright © 2004 Polycom, Inc.

Page 87 (specified by dayOf- Week) in the month, rather than the first in the month. a. Both tcpIpApp.sntp.address and tcpIpApp.sntp.gmtOffset can be provided via DHCP. If so, the DHCP parameters will override the parameters in ipmid.cfg. Copyright © 2004 Polycom, Inc...
Page 88: Web Server
4.6.1.9 Web Server <HTTPD/> ® SoundPoint IP contains a local web server for user and administrator features. This can be disabled for applications where it is not needed or where it poses a security Copyright © 2004 Polycom, Inc.

Page 89: Call Handling Configuration
0=infinite. call.shared.disableDivert 0, 1 If set to 1, disable diversion feature for shared lines. call.shared.seizeFailReorder 0, 1 If set to 1, play re-order tone locally on shared line seize failure. Copyright © 2004 Polycom, Inc...

Page 90: Directory
The directory is stored in either flash memory or RAM on SoundPoint IP. The direc- tory size is limited based on the amount of flash memory in the telephone 6. IP 500 has 2 megabytes of flash memory, IP 600 has 4 megabytes of flash memory. Copyright © 2004 Polycom, Inc.

Page 91: Fonts
Loaded fonts can either overwrite pre-existing fonts embed- ded within the software (not recommended) or can extend the SoundPoint ® IP’s font support for Unicode ranges not already embedded. The font file must be a Microsoft Copyright © 2004 Polycom, Inc...

Page 92 • to overwrite the font used for SoundPoint IP 500 soft keys for ASCII, the name should be “fontPropSoftkey_10_U0000_U00FF.fnt” 7. .fon file format is a collection of .fnt fonts mangled together within a single file. Copyright © 2004 Polycom, Inc.
Page 93 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 94: Keys
SpeedDial. The following table lists the functions that are available based on the application: Function Usable in SIP application Usable in MGCP application ArrowDown ArrowLeft ArrowRight Copyright © 2004 Polycom, Inc.

Page 95 Usable in MGCP application ArrowUp Browse BuddyStatus CallAppearance1 CallAppearance2 CallAppearance3 CallAppearance4 CallAppearance5 CallAppearance6 CallHistory CallPark CallPickup CallWaiting Callers Cancel ColdBoot Conference Delete Dial Dialpad0 Dialpad1 Dialpad2 Dialpad3 Dialpad4 Dialpad5 Dialpad6 Dialpad7 Dialpad8 Dialpad9 DialpadStar DialpadPound Copyright © 2004 Polycom, Inc...
Page 96 Usable in MGCP application Directories Divert DoNotDisturb Email Favorites Flash Handsfree Headset Feature Help Hold Line1 Line2 Line3 Line4 Line5 Line6 LocalDirectory Macro Messages Menu MicMute MyStatus Null Offline Redial Release RemoteDirectory Select SelfTest Services Copyright © 2004 Polycom, Inc.
Page 97: Bitmaps
Different from any name already in usage in ipmid.cfg. Must match the name of the corresponding <file- Name>.bmp expected to be retrieved from the boot server. Copyright © 2004 Polycom, Inc...

Page 98: Indicators
On or Off Turn LED on or off for this step. ind.pattern.x.step.y.duration positive integer Duration in milliseconds for this step. 0=infinite ind.pattern.x.step.y.colour Red or Green For bi-color LEDs, specify color. (default is Red if not specified) Copyright © 2004 Polycom, Inc.

Page 99 In the following table, x=IP_500 or IP_600, y is the graphic icon number. 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 above) for this indicator. Copyright © 2004 Polycom, Inc...
Page 100: Event Logging
IP 600: 1-160 4.6.1.16 Event Logging <logging/> Logging parameter changes can impair system operation. Do not change any logging parameters Warning! without prior consultation with Polycom. The event logging system supports the following classes of events: Level Interpretation Debug only...

Page 101 See above table for timestamp type. log.render.realtime 0, 1 Set to 1. Do not change. log.render.stdout 0, 1 Set to 1. Do not change. log.render.file 0, 1 Set to 1. Do not change. Copyright © 2004 Polycom, Inc...
Page 102 SoundPoint IP 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 103: Security
These settings control aspects of the telephone’s boot server provisioning system. Changing these parameters is not advised. Permitted Attribute Values Default Interpretation prov.fileSystem.rfs0.minFreeSpace 5-512 Minimum free space in Kbytes to reserve in the file prov.fileSystem.ffs0.4meg.minFreeSpace system when downloading files from the boot server. prov.fileSystem.ffs0.2meg.minFreeSpace Copyright © 2004 Polycom, Inc...

Page 104: Ram Disk
Minimum amount of free space that must be 16384 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. Copyright © 2004 Polycom, Inc.

Page 105: Request
(it is never available from a shared line) feature.x.enabled 0 or 1 (default) If 0, the feature will be disabled. If 1, the feature will be enabled and usable by the local user. Copyright © 2004 Polycom, Inc...

Page 106: Resource
If downloading a resource would make the quota exceeded for that category, the resource will not be downloaded and a predefined default will be used instead. a. This is available on MGCP application, but not on SIP application. Copyright © 2004 Polycom, Inc.

Page 107: Sip Configuration - Sip.cfg
If set to 0 or Null, 5060 is used for the local port but it is not advertised in the SIP signaling. If set to some other value, that value is used for the local port and it is advertised in the SIP signaling. Copyright © 2004 Polycom, Inc.
Page 108 If set to TCPpreferred: TCP is the preferred transport, UDP is used if TCP fails. If set to UDPonly: Only UDP will be used. voIpProt.server.x.expires positive integer, 3600 Requested registration period minimum 300 in seconds Copyright © 2004 Polycom, Inc.
Page 109 In either case, the telephone processes incoming hold signaling in either format. voIpProt.SIP.lcs 0, 1 If set to 1, the proprietary “epid” parameter is added to the From field of all requests to support Windows Live Communications Server. Copyright © 2004 Polycom, Inc.
Page 110 Permitted Values Default Interpretation voIpProt.SIP.requestValida- One of: Null Sets the name of the method tion.x.request “INVITE”, for which validation will be “ACK”, “BYE”, applied “REGISTER”, “CANCEL”, “OPTIONS”, “INFO”, “MESSAGE”, “SUB- SCRIBE”, “NOTIFY”, “REFER”, “PRACK”, or “UPDATE” Copyright © 2004 Polycom, Inc.
Page 111 0, 1 If set to 1, process a 200 OK ent.lineSeize.nonStandard response for a line-seize event SUBSCRIBE as though a line- seize NOTIFY with Subscription State: active header had been received, this speeds up process- ing. Copyright © 2004 Polycom, Inc.
Page 114: Per-Phone Configuration - Phone1.Cfg
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 © 2004 Polycom, Inc.
Page 116: Calls
ASCII encoded string containing Null placed to the contact digits (the user part of a SIP specified upon going URL) or a string that constitutes off hook on this reg- a valid SIP URL (6416 or istration. 6416@polycom.com) Copyright © 2004 Polycom, Inc.

Page 117: Diversion
SoundPoint ® IP can automatically divert calls when the telephone is busy. Attribute Permitted Values Default Interpretation divert.busy.x.enabled 0, 1 If set to 1, calls will be forwarded on busy to the contact specified below. Copyright © 2004 Polycom, Inc.

Page 118 Forward-to contact used digits (the user part of a SIP URL) for calls forwarded due to or a string that constitutes a valid DND status, if Null SIP URL (6416 or 6416@poly- divert.x.contact will be com.com) used. Copyright © 2004 Polycom, Inc.
Page 119: Dial Plan
4.6.2.1.4 Dial Plan <dial- 512 bytes and 20 plan/> on page 106. segments; a comma is also allowed; when reached in the digit map, a comma will turn dial tone back on. Copyright © 2004 Polycom, Inc.

Page 120 4.6.3.4.2.2 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 Copyright © 2004 Polycom, Inc.
Page 121: Messaging
Messages key, the telephone will act as if “Message Center” was chosen. See 3.6.1 Voicemail Integration on page 43. Instant Messages will still be accessible from the Main Menu. Copyright © 2004 Polycom, Inc.

Page 122: Network Address Translation
NAT device can be sent to port 5432 on an internal device, but not port 1234. Permitted Attribute Values Default Interpretation nat.ip dotted- Null IP address to advertise within SIP signaling - decimal IP should match the external IP address used by address the NAT device. Copyright © 2004 Polycom, Inc.

Page 123: User Preferences
0, 1 If set to 1, the voicemail summary display is bypassed and voicemail is dialed directly (if configured). See 3.6.1 Voicemail Integration on page 43. Copyright © 2004 Polycom, Inc.

Page 125: Session Initiation Protocol (Sip)
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 draft-ietf-sip-replaces-03.txt The Session Initiation Protocol (SIP) “Replaces” Header 5.1.2 Request Support Method Supported Notes REGISTER INVITE CANCEL Copyright © 2004 Polycom, Inc.
Page 126: 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 © 2004 Polycom, Inc.
Page 127 Session Initiation Protocol (SIP) Header Supported Notes Error-Info Event Expires From In-Reply-To Max-Forwards Messages-Waiting Min-Expires Min-SE MIME-Version Organization P-Asserted-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 © 2004 Polycom, Inc.
Page 128: 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 © 2004 Polycom, Inc.
Page 129: Xx Responses - Redirection
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 420 Bad Extension 421 Extension Required 423 Interval Too Brief Copyright © 2004 Polycom, Inc.
Page 130: Xx Responses - Server Failure
502 Bad Gateway 503 Service Unavailable 504 Server Time-out 505 Version Not Supported 513 Message Too Large 5.1.4.6 6xx Responses - Global Failure Response Supported Notes 600 Busy Everywhere 603 Decline 604 Does Not Exist Anywhere Copyright © 2004 Polycom, Inc.
Page 131: Hold Implementation
5.1.8 Third Party Call Control SoundPoint ® IP supports the delayed media negotiations (INVITE without SDP) asso- ciated with third party call control applications. 5.2 Protocol Extensions ® SoundPoint IP supports the following SIP protocol extensions. Copyright © 2004 Polycom, Inc.
Page 132: Rfc And Internet Draft Support
5.2.4 SIP for Instant Messaging and Presence Leverag- ing Extensions (SIMPLE) ® SoundPoint IP is compatible with the presence and instant messaging features of Windows ® Messenger ® and MSN ® Messenger 4.6. In a future release, Copyright © 2004 Polycom, Inc.
Page 133: Shared Call Appearance Signaling
IP 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 telephone to ask to seize the line Copyright © 2004 Polycom, Inc.

This manual is also suitable for:

Soundpoint ip 500 sip

Polycom SoundPoint IP 600 SIP Administrator's Manual

Quick Links

Administrator Guide

Related Manuals for Polycom SoundPoint IP 600 SIP

Summary of Contents for Polycom SoundPoint IP 600 SIP

This manual is also suitable for:

Table of Contents