Parameter Permitted Values Default
voIpProt.server.dhcp.available1 0 or 1 0
If 0, do not check with the DHCP server for the SIP server IP address. If 1, check with the server for the IP address.
voIpProt.server.dhcp.option1 128 to 254 128
The option to request from the DHCP server if voIpProt.server.dhcp.available= 1. Note: If reg.x.server.y.address
is
non-Null, it takes precedence even if the DHCP server is available.voIpProt.server.dhcp.type1 0 or 1 0
Type to request from the DHCP server if voIpProt.server.dhcp.available is set to 1. If this parameter is set to 0, IP request address. If set to 1, request string
voIpProt.server.x.address dotted- decimal IP
address or hostname
Null
The IP address or hostname and port of a SIP server that accepts registrations. Multiple servers can be listed starting with x=1 to 4 for fault tolerance.
voIpProt.server.x.port 0, 1 to 65535 0
The port of the server that specifies registrations. If 0, the port used depends on voIpProt.server.x.transport.
voIpProt.server.x.registerRetry.baseTimeOut 10 to 120 60
The base time period to wait before a registration retry. Used in conjunction with
voIpProt.server.x.registerRetry.maxTimeOut to determine how long to wait. The algorithm is defined in RFC 5626.
If both parameters voIpProt.server.x.registerRetry.baseTimeOut and reg.x.server.y.registerRetry.baseTimeOut are set, the value of reg.x.server.y.registerRetry.baseTimeOut takes precedence.
voIpProt.server.x.registerRetry.maxTimeOut 60 to 1800 60
The maximum time period to wait before a registration retry. Used in conjunction with
voIpProt.server.x.registerRetry.maxTimeOut to determine how long to wait. The algorithm is defined in RFC 5626.
If both parameters voIpProt.server.x.registerRetry.maxTimeOut and reg.x.server.y.registerRetry.maxTimeOut are set, the value of reg.x.server.y.registerRetry.maxTimeOut takes precedence.
Parameter Permitted Values Default voIpProt.server.x.transport DNSnaptr, TCPpreferred, UDPOnly, TLS, TCPOnly DNSnaptr
The transport method the phone uses to communicate with the SIP server.
- Null or DNSnaptr If voIpProt.server.x.address is a hostname and voIpProt.server.x.port is 0 or Null, do NAPTR then SRV lookups to try to discover the transport, ports, and servers, as per RFC 3263. If voIpProt.server.x.address is an IP address, or a port is given, then UDP is used.
- TCPpreferred TCP is the preferred transport; UDP is used if TCP fails. - UDPOnly Only UDP will be used.
- TLS If TLS fails, transport fails. Leave port field empty (will default to 5061) or set to 5061. - TCPOnly Only TCP will be used.
voIpProt.server.x.protocol.SIP 0 or 1 1
If 1, server is a SIP proxy/registrar. Note: if set to 0, and the server is confirmed to be a SIP server, then the value is assumed to be 1.
voIpProt.server.x.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).
voIpProt.server.x.expires.overlap 5 to 65535 60
The number of seconds before the expiration time returned by server x at which the phone should try to re- register. The phone will try to re-register at half the expiration time returned by the server if the server value is less than the configured overlap value.
voIpProt.server.x.expires.lineSeize positive integer, minimum 0 was 10
30
Requested line-seize subscription period.
voIpProt.server.x.failOver.failBack.mode newRequests, DNSTTL, registration, duration
newRequest s
The mode for failover failback:
- newRequests All new requests are forwarded first to the primary server regardless of the last used server. - DNSTTL The phone tries the primary server again after a timeout equal to the DNS TTL configured for the server that the phone is registered to.
- registration The phone tries the primary server again when the registration renewal signaling begins. - duration The phone tries the primary server again after the time specified by
voIpProt.server.x.failOver.failBack.timeout.
voIpProt.server.x.failOver.failBack.timeout 0, 60 to 65535 3600
If voIpProt.server.x.failOver.failBack.mode is set to duration, this is the time in seconds after failing over to the current working server before the primary server is again selected as the first server to forward new requests to. Values between 1 and 59 will result in a timeout of 60, and 0 means do not fail back until a failover event occurs with the current server.
Parameter Permitted Values Default
voIpProt.server.x.failOver.failRegistrationOn 0 or 1 0
When set to 1, and the reRegisterOn parameter is enabled, the phone will silently invalidate an existing registration (if it exists), at the point of failing over. When set to 0, and the reRegisterOn parameter is enabled, existing registrations will remain active. This means that the phone will attempt failback without first attempting to register with the primary server to determine if it has recovered.
voIpProt.server.x.failOver.onlySignalWithRegistered 0 or 1 1
When set to 1, and the reRegisterOn and failRegistrationOn parameters are enabled, no signaling is accepted from or sent to a server that has failed until failback is attempted or failover occurs. If the phone attempts to send signaling associated with an existing call via an unregistered server (for example, to resume or hold a call), the call will end. No SIP messages will be sent to the unregistered server. When set to 0, and the reRegisterOn and failRegistrationOn parameters are enabled, signaling will be accepted from and sent to a server that has failed (even though failback hasn’t been attempted or failover hasn’t occurred).
voIpProt.server.x.failOver.reRegisterOn 0 or 1 0
When set to 1, the phone will attempt to register with (or via, for the outbound proxy scenario) the secondary server. If the registration succeeds (a 200 OK response with valid expires), signaling will proceed with the secondary server. When set to 0, the phone won’t attempt to register with the second.
voIpProt.server.x.lcs 0 or 1 0
If 0, the Microsoft Live Communications Server (LSC) is not supported. If 1, LCS is supported for registration x. This parameter overrides voIpProt.SIP.lcs.
voIpProt.server.x.register 0 or 1 1
If 0, calls can be routed to an outbound proxy without registration. See reg.x.server.y.register. For more information, see Technical Bulletin 5844: SIP Server Fallback Enhancements on Polycom Phones.
voIpProt.server.x.retryTimeOut 0 to 65535 0
The amount of time (in milliseconds) to wait between retries. If 0, use standard RFC 3261 signaling retry behavior.
voIpProt.server.x.retryMaxCount 0 to 20 3
If set to 0, 3 is used. The number of retries that will be attempted before moving to the next available server.
voIpProt.server.x.specialInterop standard,
ocs2007r2, lcs2005, lync2010
standard
Specify whether this registration should support Microsoft Office Communications Server 2007 R2 (ocs2007r2), Microsoft Live Communications Server 2005 (lcs2005), or Microsoft Lync 2010 (lync2010).
voIpProt.server.x.useOutboundProxy 0 or 1 1
Specify whether or not to use the outbound proxy specified in voIpProt.SIP.outboundProxy.address for server x.
voIpProt.server.H323.x.address dotted-decimal IP
address or hostname
Null
Address of the H.323 gatekeeper. Note: Only one H.323 gatekeeper per phone is supported; if more than one is configured, only the first is used.
Parameter Permitted Values Default
voIpProt.server.H323.x.port 0 to 65535 1719
Port to be used for H.323 signaling. Note: The H.323 gatekeeper RAS signaling uses UDP, while the H.225/245 signaling uses TCP.
voIpProt.server.H323.x.expires positive integer 3600
Desired registration period.
1 Change causes phone to restart or reboot.