19.08.2013 Views

Polycom UC Software Administrators' Guide - 4.1.0

Polycom UC Software Administrators' Guide - 4.1.0

Polycom UC Software Administrators' Guide - 4.1.0

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Polycom</strong> ® <strong>UC</strong> <strong>Software</strong> Administrators’ <strong>Guide</strong><br />

Parameter Permitted Values Default<br />

voIpProt.server.dhcp.option 1 128 to 254 128<br />

The option to request from the DHCP server if voIpProt.server.dhcp.available= 1.<br />

Note: If reg.x.server.y.address is non-Null, it takes precedence even if the DHCP server is<br />

available.<br />

voIpProt.server.dhcp.type 1 0 or 1 0<br />

Type to request from the DHCP server if voIpProt.server.dhcp.available is set to 1.If this<br />

parameter is set to 0, IP request address. If set to 1, request string<br />

voIpProt.server.x.address dotted- decimal IP<br />

address or<br />

hostname<br />

The IP address or hostname and port of a SIP server that accepts registrations. Multiple servers can be<br />

listed starting with x=1 to 4 for fault tolerance.<br />

voIpProt.server.x.port 0, 1 to 65535 0<br />

The port of the server that specifies registrations. If 0, the port used depends on<br />

voIpProt.server.x.transport.<br />

voIpProt.server.x.registerRetry.baseTimeOut 10 - 120 60<br />

The base time period to wait before a registration retry. Used in conjunction with<br />

voIpProt.server.x.registerRetry.maxTimeOut to determine how long to wait. The algorithm is<br />

defined in RFC 5626.<br />

If both parameters voIpProt.server.x.registerRetry.baseTimeOut and<br />

reg.x.server.y.registerRetry.baseTimeOut are set, the value of<br />

reg.x.server.y.registerRetry.baseTimeOut takes precedence.<br />

voIpProt.server.x.registerRetry.maxTimeOut 60 - 1800 60<br />

The maximum time period to wait before a registration retry. Used in conjunction with<br />

voIpProt.server.x.registerRetry.maxTimeOut to determine how long to wait. The algorithm is<br />

defined in RFC 5626.<br />

If both parameters voIpProt.server.x.registerRetry.maxTimeOut and<br />

reg.x.server.y.registerRetry.maxTimeOut are set, the value of<br />

reg.x.server.y.registerRetry.maxTimeOut takes precedence.<br />

556<br />

Null

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!