Polycom SIP 2.2.2 User Manual

Administrator’s Guide for the

SoundPoint

IP/SoundStation

Family

SIP 2.2.2

November, 2007 Edition

1725-11530-220 Rev. A1

SIP 2.2.2

Trademark Information

Polycom®, the Polycom logo design, SoundPoint® IP, SoundStation®, SoundStation VTX 1000®, ViaVideo®, ViewStation®, and Vortex® are registered trademarks of Polycom, Inc. Conference Composer™, Global Management System™, ImageShare™, Instructor RP™, iPower™, MGC™, PathNavigator™, People+Content™, PowerCam™,

Pro-Motion™, QSX™, ReadiManager™, Siren™, StereoSurround™, V

IU™, Visual Concert™, VS4000™, VSX™, and the industrial design of SoundStation are trademarks of Polycom, Inc. in the United States and various other countries. All other trademarks are the property of their respective owners.

Patent Information

The accompanying product is protected by one or more U.S. and foreign patents and/or pending patent applications held by Polycom, Inc.

Disclaimer

Some countries, states, or provinces do not allow the exclusion or limitation of implied warranties or the limitation of incidental or consequential damages for certain products supplied to consumers, or the limitation of liability for personal injury, so the above limitations and exclusions may be limited in their application to you. When the implied warranties are not allowed to be excluded in their entirety, they will be limited to the duration of the applicable written warranty. This warranty gives you specific legal rights which may vary depending on local law.

Portions of the software contained in this product are: Copyright © 1998, 1999, 2000 Thai Open Source Software Center Ltd. and Clark Cooper Copyright © 1998 by the Massachusetts Institute of Technology Copyright © 1998-2003 The OpenSSL Project Copyright © 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved Copyright © 1995-2002 Jean-Loup Gailly and Mark Adler Copyright © 1996 - 2004, Daniel Stenberg, <daniel@haxx.se>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be include d in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

4750 Willow Road Pleasanton, CA 94588-2708 USA

No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc. Under the law, reproducing includes translating into another language or format.

As between the parties, Polycom, Inc. retains title to, and ownership of, all proprietary rights with respect to the software contained within its products. The software is protected by United States copyright laws and international treaty provision. Therefore, you must treat the software like any other copyrighted material (e.g. a book or sound recording).

Every effort has been made to ensure that the information in this manual is accurate. Polycom, Inc. is not responsible for printing or clerical errors. Information in this document is subject to change without notice.

About This Guide

The Administrator’s Guide for the SoundPoint IP / SoundStation IP family is for administrators who need to configure, customize, manage, and troubleshoot SoundPoint IP / SoundStation IP phone systems. This guide covers the SoundPoint IP 301, 320, 330, 430, 501, 550, 600, 601, and 650 desktop phones, and the SoundStation IP 4000 conference phone.

The following related documents for SoundPoint IP / SoundStation IP family are available:

• Quick Start Guides, which describe how to assemble the phones

• Quick User Guides, which describe the most basic features available on

the phones

• User Guides, which describe the basic and advanced features available on

the phones

• Developer’s Guide, which assists in the development of applications that

run on the SoundPoint IP / SoundStation IP phone’s Microbrowser

• Technical Bulletins, which describe workarounds to existing issues

• Release Notes, which describe the new and changed features and fixed

problems in the latest version of the software

For support or service, please contact your Polycom Technical Support at http://www.polycom.com/support/voice/.

Polycom recommends that you record the phone model numbers, software (both the bootROM and SIP), and partner platform for future reference.

SoundPoint IP / SoundStation IP models: ___________________________

BootROM version: ________________________________________________

SIP Application version: ___________________________________________

Partner Platform: _________________________________________________

reselle r or go to Polycom

iii

Administrator’s Guide SoundPoint IP / SoundStation IP

Contents

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

1 Introducing the SoundPoint IP / SoundStation IP Family . . . 1–1

2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1

SoundPoint IP Desktop Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2

SoundStation IP Conference Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4

Key Features of Your SoundPoint IP / SoundStation IP Phones . . . . . . . 1–5

Where SoundPoint IP / SoundStation IP Phones Fit . . . . . . . . . . . . . . . . . 2–2

Session Initiation Protocol Application Architecture . . . . . . . . . . . . . . . . . 2–3

BootROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3

Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5

Resource Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7

Available Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8

3 Setting up Your System . . . . . . . . . . . . . . . . . . . . . . . . . . .3–1

Setting Up the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2

DHCP or Manual TCP/IP Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2

Supported Provisioning Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4

Modifying the Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 3–5

Setting Up the Boot Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12

Deploying Phones From the Boot Server . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14

Upgrading SIP Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–17

Supporting SoundPoint IP and SoundStation IP Phones . . . . . . . . . 3–17

Supporting SoundPoint IP 300 and 500 Phones . . . . . . . . . . . . . . . . . 3–18

4 Configuring Your System . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1

Setting Up Basic Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1

Call Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3

Call Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3

Administrator’s Guide SoundPoint IP / SoundStation IP

Call Waiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3

Called Party Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4

Calling Party Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4

Missed Call Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4

Connected Party Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5

Context Sensitive Volume Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5

Customizable Audio Sound Effects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5

Message Waiting Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6

Distinctive Incoming Call Treatment . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6

Distinctive Ringing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7

Distinctive Call Waiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7

Do Not Disturb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8

Handset, Headset, and Speakerphone . . . . . . . . . . . . . . . . . . . . . . . . . 4–9

Local Contact Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–9

Local Digit Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–12

Microphone Mute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–13

Soft Key Activated User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–13

Speed Dial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–13

Time and Date Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–13

Idle Display Animation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–14

Ethernet Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–15

Automatic Off-Hook Call Placement . . . . . . . . . . . . . . . . . . . . . . . . . . 4–16

Call Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–16

Call Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–17

Local / Centralized Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–17

Call Forward . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–18

Directed Call Pick-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–19

Group Call Pick-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–20

Call Park/Retrieve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–20

Last Call Return . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–20

Setting Up Advanced Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–20

Configurable Feature Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–21

Multiple Line Keys per Registration . . . . . . . . . . . . . . . . . . . . . . . . . . 4–22

Multiple Call Appearances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–23

Shared Call Appearances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–23

Bridged Line Appearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–24

Busy Lamp Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–25

Customizable Fonts and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–26

Instant Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–26

Multilingual User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–27

Contents

Downloadable Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–28

Synthesized Call Progress Tones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–28

Microbrowser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–28

Real-Time Transport Protocol Ports . . . . . . . . . . . . . . . . . . . . . . . . . . 4–29

Network Address Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–30

Voice Mail Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–30

Multiple Registrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–31

Automatic Call Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–33

Server Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–34

Presence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–37

Microsoft Live Communications Server 2005 Integration . . . . . . . . 4–38

Setting Up Audio Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–42

Low-Delay Audio Packet Transmission . . . . . . . . . . . . . . . . . . . . . . . 4–42

Jitter Buffer and Packet Error Concealment . . . . . . . . . . . . . . . . . . . . 4–42

Voice Activity Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–43

DTMF Tone Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–43

DTMF Event RTP Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–44

Acoustic Echo Cancellation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–44

Audio Codecs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–45

Background Noise Suppression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–46

Comfort Noise Fill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–46

Automatic Gain Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–46

IP Type-of-Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–46

IEEE 802.1p/Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–47

Setting Up Security Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–47

Local User and Administrator Privilege Levels . . . . . . . . . . . . . . . . . 4–48

Custom Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–48

Incoming Signaling Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–49

Configuration File Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–49

Configuring SoundPoint IP / SoundStation IP Phones Locally . . . . . . . 4–50

5 Troubleshooting Your SoundPoint IP / SoundStation IP

Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1

Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2

BootROM Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2

Application Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3

Status Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4

Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4

Reading a Boot Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–7

Reading an Application Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–8

vii

Administrator’s Guide SoundPoint IP / SoundStation IP

Power and Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–9

Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–10

Access to Screens and Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–11

Calling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–12

Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–13

Audio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14

Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14

A Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–1

Master Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–2

Application Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–4

Protocol <volpProt/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–6

Dial Plan <dialplan/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–16

Localization <lcl/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–19

User Preferences <up/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–23

Tones <tones/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–24

Sampled Audio for Sound Effects <saf/> . . . . . . . . . . . . . . . . . . . . . A–27

Sound Effects <se/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–28

Voice Settings <voice/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–34

Quality of Service <QOS/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–47

Basic TCP/IP <TCP_IP/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–50

Web Server <httpd/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–54

Call Handling Configuration <call/> . . . . . . . . . . . . . . . . . . . . . . . . A–55

Directory <dir/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–58

Presence <pres/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–60

Fonts <font/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–60

Keys <key/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–63

Bitmaps <bitmap/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–65

Indicators <ind/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–65

Event Logging <log/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–69

Security <sec/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–73

License <license/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–74

Provisioning <prov/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–75

RAM Disk <ramdisk/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–76

Request <request/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–76

Feature <feature/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–77

Resource <res/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–78

Microbrowser <mb/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–79

USB Port <usb/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–83

viii

Contents

Per-Phone Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–82

Registration <reg/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–83

Calls <call/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–87

Diversion <divert/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–90

Dial Plan <dialplan/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–92

Messaging <msg/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–95

Network Address Translation <nat/> . . . . . . . . . . . . . . . . . . . . . . . A–96

Attendant <attendant/> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–97

Roaming Buddies <roaming_buddies/> . . . . . . . . . . . . . . . . . . . . . A–98

Roaming Privacy <roaming_privacy/> . . . . . . . . . . . . . . . . . . . . . . A–98

Flash Parameter Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–99

B Session Initiation Protocol (SIP) . . . . . . . . . . . . . . . . . . . . . B–1

RFC and Internet Draft Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–2

Request Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–3

Header Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–4

Response Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–6

Hold Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–9

Reliability of Provisional Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . B–9

Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–9

Third Party Call Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–9

SIP for Instant Messaging and Presence Leveraging Extensions . . . B–9

Shared Call Appearance Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . B–10

Bridged Line Appearance Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . B–10

C Miscellaneous Administrative Tasks . . . . . . . . . . . . . . . . . .C–1

Trusted Certificate Authority List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–1

Encrypting Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–3

Changing the Key on the Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–5

Adding a Background Logo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–5

BootROM/SIP Application Dependencies . . . . . . . . . . . . . . . . . . . . . . . . C–7

Migration Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–8

Multiple Key Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–9

Default Feature Key Layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–10

Assigning a VLAN ID Using DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–14

Parsing Vendor ID Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–16

Administrator’s Guide SoundPoint IP / SoundStation IP

D Third Party Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D–1

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Index–1

Introducing the SoundPoint IP / SoundStation IP Family

This chapter introduces the SoundPoint IP / SoundStation IP family, which is supported by the software described in this guide.

The SoundPoint IP / SoundStation IP family provides a powerful, yet flexible IP communications solution for Ethernet TCP/IP networks, delivering excellent voice quality. The high-resolution graphic display supplies content for call information, multiple languages, directory access, and system status. The SoundPoint IP / SoundStation IP family supports advanced functionality, including multiple call and flexible line appearances, HTTPS secure provisioning, presence, custom ring tones, and local conferencing.

The SoundPoint IP / SoundStation IP phones are end points in the overall network topology designed to interoperate with other compatible equipment including application servers, media servers, internet-working gateways, voice bridges, and other end points

The following models are described:

• SoundPoint IP Desktop Phones

— IP 301

— IP 320/330

— IP 430

— IP 501

— IP 550

— IP 600/601

— IP 650

• SoundStation IP Conference Phone

— IP 4000

This chapter also lists the key features available on the SoundPoint IP / SoundStation IP phones running the latest software.

1 - 1

Administrator’s Guide SoundPoint IP / SoundStation IP

SoundPoint IP Desktop Phones

This section describes the current SoundPoint IP desktop phones. For individual guides, refer to the product literature available at

http://www.polycom.com/support/voice/. Additional options are also

available. For more information, contact your Polycom distributor.

The currently supported desktop phones are:

• SoundPoint IP 301

• SoundPoint IP 320/330

1 - 2

• SoundPoint IP 430

• SoundPoint IP 501

Introducing the SoundPoint IP / SoundStation IP Family

• SoundPoint IP 550

1 - 3

Administrator’s Guide SoundPoint IP / SoundStation IP

• SoundPoint IP 600/601

• SoundPoint IP 650

SoundStation IP Conference Phone

This section describes the current SoundPoint IP conference phone. For individual guides, refer to the product literature available at

http://www.polycom.com/support/voice/. Additional options are also

available. For more information, contact your Polycom distributor.

1 - 4

Introducing the SoundPoint IP / SoundStation IP Family

The currently supported conference phone is:

• SoundStation IP 4000

Key Features of Your SoundPoint IP / SoundStation IP Phones

The key features of the SoundPoint IP / SoundStation IP phones are:

• Award winning sound quality and full-duplex speakerphone or

conference phone

— Permits natural, high-quality, two-way conversations (one-way,

monitor speaker in the SoundPoint IP 301)

— Uses Polycom’s industry leading Acoustic Clarity Technology

• Easy-to-use

— An easy transition from traditional PBX systems into the world of IP

— Up to 18 dedicated hard keys for access to commonly used features

— Up to four context-sensitive soft keys for further menu-driven

activities

• Platform independent

— Supports multiple protocols and platforms enabling standardization

on one phone for multiple locations, systems and vendors

— Polycom’s support of the leading protocols and industry partners

makes it a future-proof choice

• Field upgradeable

— Upgrade SoundPoint IP / SoundStation IP as standards develop and

protocols evolve

— Extends the life of the phone to protect your investment

1 - 5

Administrator’s Guide SoundPoint IP / SoundStation IP

— Application flexibility for call management and new telephony

applications

• Large LCD

— Easy-to-use, easily readable and intuitive interface

— Support of rich application content, including multiple call

appearances, presence and instant messaging, and XML services

— 4 line x 20 character monochrome LCD for the SoundPoint IP 301

— 102 x 23 pixel graphical LCD for the SoundPoint IP 320/330

— 160 x 80 pixel graphical grayscale LCD for the SoundPoint IP 501

— 320 x 160 pixel graphical grayscale LCD for the SoundPoint IP

550/600/601/650 (supports Asian characters)

— 248 x 68 pixel graphical LCD for the SoundStation IP 4000

• Dual auto-sensing 10/100baseT Ethernet ports

— Leverages existing infrastructure investment

— No re-wiring with existing CAT 5 cabling

— Simplifies installation

• Power over Ethernet (PoE) port

— Unused pairs on Ethernet port pairs are used to deliver power to the

phone via a wall adapter allowing fewer wires to desktop

— Optional accessory cable for CiscoR Inline Powering and IEEE 802.3af

on the SoundPoint IP 301 and SoundPoint IP 501

— Built-in PoE on the SoundPoint IP 550, 600, 601, and 650 (auto-sensing)

• Multiple language support

— Set on-screen language to your preference. Select from Chinese,

Danish, Dutch, English, French, German, Italian, Japanese, Korean, Norwegian, Portuguese, Russian, Spanish, and Swedish

1 - 6

Overview

This chapter provides an overview of the Session Initiation Protocol (SIP) application and how the phones fit into the network configuration.

SIP is the Internet Engineering Task Force (IETF) standard for multimedia conferencing over IP. It is an ASCII-based, application-layer control protocol (defined in RFC 3261) that can be used to establish, maintain, and terminate calls between two or more endpoints. Like other voice over IP (VoIP) protocols, SIP is designed to address the functions of signaling and session management within a packet telephony network. Signaling allows call information to be carried across network boundaries. Session management provides the ability to control the attributes of an end-to-end call.

For the SoundPoint IP / SoundStation IP phones to successfully operate as a SIP endpoint in your network, it must meet the following requirements:

• A working IP network is established.

• Routers are configured for VoIP.

• VoIP gateways are configured for SIP.

• The latest (or compatible) SoundPoint IP / SoundStation IP phone SIP

application image is available.

• A call server is active and configured to receive and send SIP messages.

For more information on IP PBX and softswitch vendors, go to

http://www.polycom.com/techpartners1/ .

This chapter contains information on:

• Where SoundPoint IP / SoundStation IP Phones Fit

• Session Initiation Protocol Application Architecture

• Available Features

To install your SoundPoint IP / SoundStation IP phones on the network, refer to Setting up Your System on page 3-1. To configure your SoundPoint IP / SoundStation IP phones with the desired features, refer to Configuring Your

2 - 1

Administrator’s Guide SoundPoint IP / SoundStation IP

System on page 4-1. To troubleshoot any problems with your SoundPoint IP /

SoundStation IP phones on the network, refer to Troubleshooting Your

SoundPoint IP / SoundStation IP Phones on page 5-1.

Where SoundPoint IP / SoundStation IP Phones Fit

The phones connect physically to a standard office twisted-pair (IEEE 802.3) 10/100 megabytes per second Ethernet LAN and send and receive all data using the same packet-based technology. Since the phone is a data terminal, digitized audio being just another type of data from its perspective, the phone is capable of vastly more than traditional business phones. AsSoundPoint IP / SoundStation IP phones run the same protocols as your office personal computer, many innovative applications can be developed without resorting to specialized technology.

2 - 2

Session Initiation Protocol Application Architecture

Configuration

Resource

Files

bootROM

Application

The software architecture of SIP application is made of 4 basic components:

• BootROM—loads first when the phone is powered on

• Application—software that makes the device a phone

• Configuration—configuration parameters stored in separate files

• Resource Files—optional, needed by some of the advanced features

Overview

BootROM

The bootROM is a small application that resides in the flash memory on the phone. All phones come from the factory with a bootROM pre-loaded.

The bootROM performs the following tasks in order:

1. Performs a power on self test (POST).

2. (Optional) Allows you to enter the setup menu where various network on

provisioning options can be set.

The bootROM software controls the user interface when the setup menu is accessed.

3. Requests IP settings and accesses the boot server to look for any updates

to the bootROM application.

If updates are found, they are downloaded and saves to flash memory, eventually overwriting itself after verifying the integrity of the download.

4. If a new bootROM is downloaded, format the file system clearing out any

application software or configuration files that may have been present.

2 - 3

Administrator’s Guide SoundPoint IP / SoundStation IP

5. Download the master configuration file.

This file is either called <mac-address>.cfg or 000000000000.cfg . This file is used by the both the bootROM and the application for a list of other files that are needed for the operation of the phone.

6. Examine the master configuration file for the name of the application file,

and then look for this file on the boot server.

If the copy on the boot server is different than the one stored in flash memory or, if there is no file stored in flash memory, the application file is downloaded.

Application

Note

Warning

If the Application is any SIP version prior to 1.5, the bootROM will also download all the configuration files that are listed in the master configuration file.

7. Extract the application from flash memory.

8. Install the application into RAM, then upload a log file with events from

the boot cycle.

The bootROM will then terminate, and the application takes over.

The application manages the VoIP stack, the digital signal processor (DSP), the user interface, and the network interaction. The application managed everything to do with the phone’s operation.

The application is a single file binary image and, as of SIP 1.5, contains a digital signature to prevent tampering or loading or rogue software images.

If your phones are using bootROM 3.0 or later, the application must be signed. All SIP 1.5 applications and later are signed, but later patched versions of 1.3 and

1.4 support this feature. Refer to the latest Release Notes to verify if the image is signed.

2 - 4

Note

There is a new image file in each release of software.

The application performs the following tasks in order:

1. Downloads system and per-phone configuration files and resource files.

These files are called sip.cfg and phone1.cfg by default. You can customized the filenames.

If the Application is any SIP version prior to 1.5, the bootROM would have downloaded all the configuration files that are listed in the master configuration file.

Configuration

Overview

2. Controls all aspects of the phone after it has restarted.

3. Uploads log files.

BootROM and Application Wrapper

Both the bootROM and the application run on multiple platforms (meaning all previously released versions of hardware that are still supported).

The file stored on the boot server is a wrapper, with multiple hardware specific images contained within. When a new bootROM or application is being saved, the file is read until a header matching the hardware model and revision are found, and then only this image is saved to flash memory.

The SoundPoint IP / SoundStation IP phones can be configured automatically through files stored on a central boot server, manually through the phone’s local UI or web interface, or a combination of the automatic and manual methods.

The recommended method for configuring phones is automatically through a central boot server, but if one is not available, the manual method will allow changes to most of the key settings.

Warning

The phone configuration files consist of:

• Master Configuration Files

• Application Configuration Files

Configuration files should only be modified by a knowledgeable system administrator. Applying incorrect parameters may render the phone unusable. The configuration files which accompany a specific release of the SIP software must be used together with that software. Failure to do this may render the phone unusable.

Master Configuration Files

The master configuration files can be one of:

• Specified master configuration file

• Per-phone master configuration file

• Default master configuration file

For more information, refer to Master Configuration Files on page A-2.

2 - 5

Administrator’s Guide SoundPoint IP / SoundStation IP

Application Configuration Files

Typically, the files are arranged in the following manner although parameters may be moved around within the files and the filenames themselves can be changed as needed. These files dictate the behavior of the phone once it is running the executable specified in the master configuration file.

The application files are:

• Application—It contains parameters that affect the basic operation of the

phone such as voice codecs, gains, and tones and the 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. By default, sip.cfg is included.

• Per-phone—It contains parameters unique to a particular phone user.

Typical parameters include:

— display name

— unique addresses

Each phone in an installation usually has its own customized version of user files derived from Polycom templates. By default, phone1.cfg is included.

Note

Central Provisioning

The phones can be centrally provisioned from a boot server through a system of global and per-phone configuration files. The boot server also facilitates automated application upgrades, logging, and a measure of fault tolerance. Multiple redundant boot servers can be configured to improve reliability.

In the central provisioning method, there are two major classifications of configuration files:

• System configuration files

• Per-phone configuration files

Parameters can be stored in the files in any order and can be placed in any number of files. The default is to have 2 files, one for per-phone setting and one for system settings. The per-phone file is typically loaded first, and could contain system level parameters, letting you override that parameter for a given user. For example, it might be desirable to set the default CODEC for a remote user differently than for all the users who reside in the head office. By adding the CODEC settings to a particular user’s per-phone file, the values in the system file are ignored.

Verify the order of the configuration files. Parameters in the configuration file loaded first will overwrite those in later configuration files.

2 - 6

Overview

The following figure shows one possible layout of the central provisioning method.

Resource Files

Manual Configuration

When the manual configuration method is employed, any changes made are stored in a configuration override file. This file is stored on the phone, but a copy will also be uploaded to the central boot server if one is being used. When the phone boots, this file is loaded by the application after any centrally provisioned files have been read, and its settings will override those in the centrally provisioned files.

This can create a lot of confusion about where parameters are being set, and so it is best to avoid using the manual method unless you have good reason to do so.

In addition to the application and the configuration files, the phones may require resource files that are used by some of the advanced features. These files are optional, but if the particular feature is being employed, these files are required.

Some examples of resource files include:

• Language dictionaries

• Custom fonts

2 - 7

Administrator’s Guide SoundPoint IP / SoundStation IP

• Ring tones

• Synthesized tones

• Contact directories

Available Features

Note

Any new features introduced after SIP 2.1.2 are not supported on the SoundPoint IP 300 and 500.

This section provides information the features available on the SoundPoint IP / SoundStation IP phones:

• Basic Features

— Automatic Off-Hook Call Placement—Supports an optional

automatic off-hook call placement feature for each .

— Call Forward—Provides a flexible call forwarding feature to forward

calls to another destination.

— Call Hold—Pauses activity on one call so that the user may use the

phone for another task, such as making or receiving another call.

— Call Log—Contains call information such as remote party

identification, time and date, and call duration in three separate lists, missed calls, received calls, and placed calls on most platforms.

— Call Park/Retrieve—An active call can be parked. A parked call can

be retrieved by any phone.

— Call Timer—A separate call timer, in hours, minutes, and seconds, is

maintained for each distinct call in progress.

— Call Transfer—Call transfer allows the user to transfer a call in

progress to some other destination.

2 - 8

— Call Waiting—When an incoming call arrives while the user is active

on another call, the incoming call is presented to the user visually on the display and a configurable sound effect will be mixed with the active call audio.

— Called Party Identification—The phone displays and logs the identity

of the party specified for outgoing calls.

— Calling Party Identification—The phone displays the caller identity,

derived from the network signalling, when an incoming call is presented, if information is provided by the call server.

— Connected Party Identification—The identity of the party to which the

user has connected is displayed and logged, if the name is provided by the call server.

Overview

— Context Sensitive Volume Control—The volume of user interface

sound effects, such as the ringer, and the receive volume of call audio is adjustable.

— Customizable Audio Sound Effects—Audio sound effects used for

incoming call alerting and other indications are customizable.

— Directed Call Pick-Up and Group Call Pick-Up—Calls to another

phone can be picked up by dialing the extension of the other phone. Calls to another phone within a pre-defined group can be picked up without dialing the extension of the other phone.

— Distinctive Call Waiting—Calls can be mapped to distinct call waiting

types.

— Distinctive Incoming Call Treatment—The phone can automatically

apply distinctive treatment to calls containing specific attributes.

— Distinctive Ringing—The user can select the ring type for each line

and the ring type for specific callers can be assigned in the contact directory.

— Do Not Disturb—A do-not-disturb feature is available to temporarily

stop all incoming call alerting.

— Handset, Headset, and Speakerphone—SoundPoint IP phones come

standard with a handset and a dedicated headset connection (not supplied). The SoundPoint IP 320, 330, 430, 500, 501, 550, 600, 601, and 650 and SoundStation IP 4000 phone are full-duplex speakerphones. The SoundPoint IP 301 phone is a listen-only speakerphone.

— Idle Display Animation—All phones except the SoundPoint IP 301 can

display a customized animation on the idle display in addition to the time and date.

— Last Call Return—The phone allows call server-based last call return.

— Local / Centralized Conferencing—The phone can conference

together the local user with the remote parties of two independent calls and can support centralized conferences for which external resources are used such as a conference bridge.

— Local Contact Directory—The phone maintains a local contact

directory that can be downloaded from the boot server and edited locally.

— Local Digit Map—The phone has a local digit map to automate the

setup phase of number-only calls.

— Message Waiting Indication—The phone will flash a message-waiting

indicator (MWI) LED when instant messages and voice messages are waiting.

— Microphone Mute—When the microphone mute feature is activated,

visual feedback is provided.

2 - 9

Administrator’s Guide SoundPoint IP / SoundStation IP

— Missed Call Notification—The phone can display the number of calls

missed since the user last looked at the Missed Calls list.

— Soft Key Activated User Interface—The user interface makes

extensive use of intuitive, context-sensitive soft key menus.

— Speed Dial—The speed dial system allows calls to be placed quickly

from dedicated keys as well as from a speed dial menu.

— Time and Date Display—Time and date can be displayed in certain

operating modes such as when the phone is idle and during a call.

• Advanced Features

— Automatic Call Distribution—Supports ACD agent available and

unavailable and allows ACD login and logout. Requires call server support.

— Bridged Line Appearance—Calls and lines on multiple phones can be

logically related to each other. Requires call server support.

— Busy Lamp Field—Allows monitoring the hook status and remote

party information of users through the busy lamp field (BLF) LEDs and displays on an attendant console phone. Requires call server support.

— Configurable Feature Keys—Certain key functions can be changed

from the factory defaults.

— Customizable Fonts and Indicators—The phone’s user interface can

be customized by changing the fonts and graphic icons used on the display and the LED indicator patterns.

— Downloadable Fonts—New fonts can be loaded onto the phone.

— Instant Messaging—Supports sending and receiving instant text

messages.

— Microbrowser—The SoundPoint IP 430, 501, 550, 600, 601, and 650

phones and the SoundStation IP 4000 phone support an XHTML microbrowser.

— Microsoft Live Communications Server 2005

Integration—SoundPoint IP and SoundStation IP phones can used

with Microsoft Live Communications Server 2005 and Microsoft Office Communicator to help improve business efficiency and increase productivity and to share ideas and information immediately with business contacts. Requires call server support.

— Multilingual User Interface—All phones except SoundPoint IP 301

have multilingual user interfaces.

— Multiple Call Appearances—The phone supports multiple concurrent

calls. The hold feature can be used to pause activity on one call and switch to another call.

2 - 10

— Multiple Line Keys per Registration—More than one line key can be

allocated to a single .

Overview

— Multiple Registrations—SoundPoint IP phones support multiple s per

phone. (SoundStation IP 4000 supports a single .)

— Network Address Translation—The phones can work with certain

types of network address translation (NAT).

— Presence—Allows the phone to monitor the status of other

users/devices and allows other users to monitor it. Requires call server support.

— Real-Time Transport Protocol Ports—The phone treats all real- time

transport protocol (RTP) streams as bi-directional from a control perspective and expects that both RTP end points will negotiate the respective destination IP addresses and ports.

— Server Redundancy—Server redundancy is often required in VoIP

deployments to ensure continuity of phone service for events where the call server needs to be taken offline for maintenance, the server fails, or the connection from the phone to the server fails.

— Shared Call Appearances—Calls and lines on multiple phones can be

logically related to each other. Requires call server support.

— 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 during the life cycle of a call. Customizable for certain regions, for example, Europe has different tones from North America.

— Voice Mail Integration—Compatible with voice mail servers.

• Audio Features

— Acoustic Echo Cancellation—Employs advanced acoustic echo

cancellation for hands-free operation.

— Audio Codecs—Supports the standard audio codecs.

— Automatic Gain Control—Designed for hands-free operation, boosts

the transmit gain of the local user in certain circumstances.

— Background Noise Suppression—Designed primarily for hands-free

operation, reduces background noise to enhance communication in noisy environments.

— Comfort Noise Fill—Designed to help provide a consistent noise level

to the remote user of a hands-free call.

— DTMF Event RTP Payload—Conforms to RFC 2833, which describes

a standard RTP-compatible technique for conveying DTMF dialing and other telephony events over an RTP media stream.

— DTMF Tone Generation—Generates dual tone multi-frequency

(DTMF) tones in response to user dialing on the dial pad.

— IEEE 802.1p/Q—The phone will tag all Ethernet packets it transmits

with an 802.1Q VLAN header.

2 - 11

Administrator’s Guide SoundPoint IP / SoundStation IP

— IP Type-of-Service—Allows for the setting of TOS settings.

— Jitter Buffer and Packet Error Concealment—Employs a

high-performance jitter buffer and packet error concealment system designed to mitigate packet inter-arrival jitter and out-of-order or lost (lost or excessively delayed by the network) packets.

— Low-Delay Audio Packet Transmission—Designed to minimize

latency for audio packet transmission.

— Voice Activity Detection—Conserves network bandwidth by

detecting periods of relative “silence” in the transmit data path and replacing that silence efficiently with special packets that indicate silence is occurring.

• Security Features

— Local User and Administrator Privilege Levels—Several local settings

menus are protected with two privilege levels, user and administrator, each with its own password.

— Configuration File Encryption—Confidential information stored in

configuration files must be protected (encrypted). The phone can recognize encrypted files, which it downloads from the boot server and it can encrypt files before uploading them to the boot server.

— Custom Certificates—When trying to establish a connection to a boot

server for application provisioning, the phone trusts certificates issued by widely recognized certificate authorities (CAs).

— Incoming Signaling Validation—Levels of security are provided for

validating incoming network signaling.

For more information on each feature and its associated configuration parameters, see the appropriate section in Configuring Your System on page

4-1.

2 - 12

Setting up Your System

Your SoundPoint IP / SoundStation IP SIP phone is designed to be used like a regular phone on a public switched telephone network (PSTN).

This chapter provides basic instructions for setting up your SoundPoint IP / SoundStation IP phones. This chapter contains information on:

• Setting Up the Network

• Setting Up the Boot Server

• Deploying Phones From the Boot Server

• Upgrading SIP Application

Note

Because of the large number of optional installations and configurations that are available, this chapter focuses on one particular way that the SIP application and the required external systems might initially be installed and configured in your network.

For more information on configuring your system, refer to Configuring Your

System on page 4-1. For more information on the configuration files required

for setting up your system, refer to Configuration Files on page A-1.

For installation and maintenance of Polycom SoundPoint IP phones, the use of a boot server is strongly recommended. This allows for flexibility in installing, upgrading, maintaining, and configuring the phone. Configuration, log, and directory files are normally located on this server. Allowing the phone write access to the server is encouraged.

The phone is designed such that, if it cannot locate a boot server when it boots up, it will operate with internally saved parameters. This is useful for occasions when the boot server is not available, but is not intended to be used for long-term operation of the phones.

3 - 1

Administrator’s Guide SoundPoint IP / SoundStation IP

Setting Up the Network

Regardless of whether or not you will be installing a centrally provisioned system, you must perform basic TCP/IP network setup, such as IP address and subnet mask configuration, to get your organization’s phones up and running.

The bootROM application uses the network to query the boot server for upgrades, which is an optional process that will happen automatically when properly deployed. For more information on the basic network settings, refer to DHCP or Manual TCP/IP Setup on page 3-2.

The bootROM on the phone performs the provisioning functions of downloading the bootROM, the <Ethernet address>.cfg file, and the SIP application, and uploading log files. For more information, refer to Supported

Provisioning Protocols on page 3-4.

Basic network settings can be changed during bootROM download using the bootROM’s setup menu. A similar menu system is present in the application for changing the same network parameters. For more information, refer to

Modifying the Network Configuration on page 3-5.

DHCP or Manual TCP/IP 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.

Polycom recommends using DHCP where possible to eliminate repetitive manual data entry.

The following table shows the manually entered networking parameters that may be overridden by parameters obtained from a DHCP server, an alternate DHCP server, or configuration file:

Alternate

Parameter

IP address 1•-- • subnet mask 1•-- •

DHCP Option

DHCP

D priority when more than one source exists D 12 3 4

DHCP

Configuration File (application only)

Local FLASH

IP gateway 3•-- •

3 - 2

+ 226 hidden pages