User`s guide

Polycom VVX Expansion Module Administrator’s Guide Addendum UC Software 4.1.6
Polycom, Inc. 46
Parameter
Permitted Values
Default
reg.x.thirdPartyName
string address
Null
This field must match the reg.x.address value of the registration that makes up the part of a bridged line
appearance (BLA). It must be Null in all other cases.
reg.x.type
private or shared
private
If set to private, use standard call signaling. If set to shared, augment call signaling with call state subscriptions and
notifications and use access control for outgoing calls.
reg.x.useCompleteUriForRetrieve
0 or 1
1
This parameters overrides voipPort.SIP.useCompleteUriForRetrieve. If set to 1, the target URI in BLF
signaling will use the complete address as provided in the xml dialog document. If set to 0, only the user portion of
the XML dialog document is used and the current registrar's domain is appended to create the full target URI.
1
Change causes phone to restart or reboot.
You can list multiple registration servers for fault tolerance. The server registration parameters are listed
in the following table. You can list four servers by using y=1 to 4. If the reg.x.server.y.address is
not Null, all of the parameters in the following table override the parameters specified in
voIpProt.server.*.
Registration Server Parameters
Parameter
Permitted Values
Default
reg.x.server.H323.y.address
dotted-decimal
IP address or
hostname
Null
Address of the H.323 gatekeeper.
reg.x.server.H323.y.port
0 to 65535
0
Port to be used for H.323 signaling. If set to Null, 1719 (H.323 RAS signaling) is used.
reg.x.server.H323.y.expires
positive integer
3600
Desired registration period.
reg.x.server.y.address
dotted-decimal
IP address or
hostname
Null
The IP address or hostname of a SIP server that accepts registrations. If not Null, all of the parameters in this
table will override the parameters specified in voIpProt.server.*.
reg.x.server.y.expires
positive integer,
minimum 10
3600
The phone’s requested registration period in seconds. Note: The period negotiated with the server may be
different. The phone will attempt to re-register at the beginning of the overlap period. For example, if
expires=300 and overlap=5, the phone will re-register after 295 seconds (300–5).