3 per-phone configuration - phone1.cfg, 1 registration Page 129
Page 129
Administrator Guide - SoundPoint
®
IP / SoundStation
®
IP
Optimization
Copyright © 2004 Polycom, Inc.
121
4.6.3 Per-phone Configuration - phone1.cfg
This section covers the parameters in the per-phone example configuration file
phone1.cfg. This file would normally be used as a template for the per-phone config-
uration files. For more information, see 2.2.2.1.3 Deploying a Boot Server for the
Phones on page 13.
4.6.3.1 Registration
SoundPoint
®
IP 300 supports two unique registrations, IP 500 supports three and IP
600 supports six. Each registration can optionally be associated with a private array of
servers for completely segregated signaling. SoundStation
®
IP 4000 supports a single
registration.
In the following table, x is the registration number. IP 300: x=1-2; IP 500: x=1-3; IP
600: x=1-6; IP 4000: x=1
Attribute
Permitted
Values
Default
Interpretation
reg.x.displayName
UTF-8 encoded
string
Null
Display name used for local user
interface as well as SIP signaling.
reg.x.address
string in the for-
mat userPart or
user-
Part@domain
Null
The actual address corresponding
to this registration (userPart or
[email protected]). For user
part only registration
(reg.x.address=”1002”), the regis-
tration will be userPart@proxy-
HostNameOrIPAddress where
userPart is reg.x.address and proxy-
HostNameOrIPAddress is either
reg.x.server.1.address if non-Null
or voIpProt.server.1.address speci-
fied in sip.cfg.
reg.x.label
UTF-8 encoded
string
Null
Text label to appear on the display
adjacent to the associated line key.
If omitted, the label will be derived
from the user part of reg.x.address.
reg.x.type
private OR
shared
private
If set to private, use standard call
signaling.
If set to shared, augment call sig-
naling with call state subscriptions
and notifications and use access
control for outgoing calls.