Shared Call Appearances Parameters

This feature is dependent on support from a SIP call server.

To enable shared call appearances on your phone, you must obtain a shared line address from your SIP service provider.

Use the parameters in the following table to configure options for this feature.

.
Table 1. Shared Call Appearances Parameters

Template

Parameter

Permitted Values

Change Causes Restart or Reboot

reg-basic.cfg

reg.x.address

The user part (for example, 1002) or the user and the host part (for example, 1002@polycom.com ) of the registration SIP URI or the H.323 ID/extension.

Null (default)

string address

No

reg-advanced.cfg

reg.x.type

private (default) - Use standard call signaling.

shared - Use augment call signaling with call state subscriptions and notifications and use access control for outgoing calls.

No

sip-interop.cfg

call.shared.reject

For shared line calls on the BroadWorks server.

0 - The phone displays a Reject soft key to reject an incoming call to a shared line.

1 - The Reject soft key does not display.

No

sip-interop.cfg

call.shared.exposeAutoHolds

0 (default) - No re-INVITE is sent to the server when setting up a conference on a shared line.

1 - A re-INVITE is sent to the server when setting up a conference on a shared line.

Yes

sip-interop.cfg

call.shared.oneTouchResume

0 (default) - Selecting the shared line opens all current calls that the user can choose from.

1 - All users on a shared line can resume held calls by pressing the shared line key. If more than one call is on hold, the first held call is selected and resumed.

A quick press and release of the line key resumes a call whereas pressing and holding down the line key shows a list of calls on that line.

Yes

sip-interop.cfg

call.shared.preferCallInfoCID

0 (default) - The Caller-ID information received in the 200 OK status code is not ignored if the NOTIFY message received with caller information includes display information.

1 - The Caller-ID information received in the 200 OK status code is ignored if the NOTIFY message received with caller information includes display information.

No

sip-interop.cfg, site.cfg

call.shared.remoteActiveHoldAsActive

1 (default) - Shared remote active/hold calls are treated as a active call on the phone.

0 - Shared remote active/hold calls are not treated as a active call on the phone.

No

sip-interop.cfg

call.shared.seizeFailReorder

1 (default) - Play a re-order tone locally on shared line seize failure.

0 - Do not play a re-order tone locally on shared line seize failure.

Yes

sip-interop.cfg

voIpProt.SIP.specialEvent.lineSeize.nonStandard

Controls the response for a line-seize event SUBSCRIBE.

1 (default) - This speeds up the processing of the response for line-seize event.

0 - This will process the response for the line seize event normally

Yes

reg-advanced.cfg

reg.x.ringType

The ringer to be used for calls received by this registration. The default is the first non-silent ringer.

If you use the configuration parameters ringer13 and ringer14 on a single registered line, the phone plays SystemRing.wav.

default (default)

ringer1 to ringer24

No

sip-interop.cfg

reg.x.protocol.H323

You can use this parameter for the VVX 500/501, 600/601, and 1500.

0 (default) - H.323 signaling is not enabled for registration x.

1 - H.323 signaling is enabled for registration x.

No

site.cfg

reg.x.server.H323.y.address

Address of the H.323 gatekeeper.

Null (default)

IP address or hostname

No

site.cfg

reg.x.server.H323.y.port

Port to be used for H.323 signaling. If set to Null, 1719 (H.323 RAS signaling) is used.

0 (default)

0 to 65535

No

site.cfg

reg.x.server.H323.y.expires

Desired registration period.

3600

positive integer

No

site.cfg

reg.x.line.y.label

Configure a unique line label for a shared line that has multiple line key appearances. This parameter takes effect when u p.cfgUniqueLineLabel=1 . If reg.x.linekeys=1 , this parameter does not have any effect.

x = the registration index number starting from 1.

y = the line index from 1 to the value set by reg.x.linekeys . Specifying a string sets the label used for the line key registration on phones with multiple line keys.

If no parameter value is set for reg.x.line.y.label , the phone automatically numbers multiple lines by prepending “<y>_” where <y> is the line index from 1 to the value set by reg.x.linekeys .

  • The following examples show labels for line 1 on a phone with user registration 1234, where reg.x.linekeys=2 :
    • If no label is configured for registration, the labels are “1_1234” and “2_1234”.
    • If reg.1.line.1.label=Polycom and reg.1.line.2.label=VVX , the labels display as ‘Polycom' and ‘VVX'.

No

reg-advanced.cfg

reg.x.callsPerLineKey

Set the maximum number of concurrent calls for a single registration x. This parameter applies to all line keys using registration x. If registration x is a shared line, an active call counts as a call appearance on all phones sharing that registration.

This per-registration parameter overrides call.callsPerLineKey .

24 (default)

1-24

VVX 101, 201

8 (default)

1 - 8

No

reg-advanced.cfg

reg.x.header.pearlymedia.support

0 (Default) - The p-early-media header is not supported on the specified line registration.

1 - The p-early-media header is supported by the specified line registration.

No

reg-basic.cfg

reg.X.insertOBPAddressInRoute

1 (Default) - The outbound proxy address is added as the topmost route header.

0 - The outbound proxy address is not added to the route header.

No

features.cfg

reg.x.path

0 (Default) - The path extension header field in the Register request message is not supported for the specific line registration.

1 - The phone supports and provides the path extension header field in the Register request message for the specific line registration.

No

features.cfg

reg.x.regevent

0 (default) - The phone is not subscribed to registration state change notifications for the specific phone line.

1 - The phone is subscribed to registration state change notifications for the specific phone line.

This parameter overrides the global parameter voIpProt.SIP.regevent.

No

reg-advanced.cfg

reg.x.rejectNDUBInvite

Specify whether or not the phone accepts a call for a particular registration in case of a Network Determined User Busy (NDUB) event advertised by the SIP server.

0 (Default) - If an NDUB event occurs, the phone does not reject the call.

1 - If an NDUB event occurs, the phone rejects the call with a 603 Decline response code.

No

reg-advanced.cfg

reg.x.server.y.specialInterop

Specify the server-specific feature set for the line registration.

Standard (Default)

VVX 101:

Standard

GENBAND

ALU-CTS

DT

VVX 201:

Standard,

GENBAND

ALU-CTS

ocs2007r2

lync2010

All other phones:

Standard

GENBAND

ALU-CTS

ocs2007r2

lync2010

lcs2005

sip-interop.cfg

reg.x.gruu

1 - The phone sends sip.instance in the REGISTER request.

0 (default) - The phone does not send sip.instance in the REGISTER request.

No

reg-advanced.cfg

reg.x.serverFeatureControl.securityClassification

0 (default) - The visual security classification feature for a specific phone line is disabled.

1 - The visual security classification feature for a specific phone line is enabled.

No

reg-advanced.cfg

reg.x.terminationType

Determines the type of termination that is used for the line where the line can be managed automatically on the VVX, the wireless handset, or on both. X = each registration index.

NULL (default)

VVX, DECT, or VVX-DECT

No

reg-advanced.cfg reg-advanced.cfg

reg.x.acd-login-logout reg.x.acd-agent-available

0 (default) - The ACD feature is disabled for registration.

1 - If both ACD login/logout and agent available are set to 1 for registration x, the ACD feature is enabled for that registration.

No

reg-advanced.cfg

reg.x.advancedConference.maxParticipants

Sets the maximum number of participants allowed in a push to conference for advanced conference calls. The number of participants configured must match the number of participants allowed on the ALU CTS.

3 (default)

0 - 25

No

reg-advanced.cfg

reg.x.advancedConference.pushToConference

0 (default) - Disable push-to-conference functionality.

1 - Enable push-to-conference functionality.

No

reg-advanced.cfg

reg.x.advancedConference.subscribeForConfEvents

1 (default) - Conference participants to receive notifications for conference events is enabled.

0 - Conference participants to receive notifications for conference events is disabled.

No

reg-advanced.cfg

reg.x.advancedConference.subscribeForConfEventsOnCCPE

1 (default) - Enable the conference host to receive notifications for conference events.

0 - Disable the conference host to receive notifications for conference events.

No

reg-advanced.cfg

reg.x.auth.domain

The domain of the authorization server that is used to check the user names and passwords.

Null (default)string

No

reg-advanced.cfg

reg.x.auth.optimizedInFailover

The destination of the first new SIP request when failover occurs.

0 (default) - The SIP request is sent to the server with the highest priority in the server list.

1 - The SIP request is sent to the server which sent the proxy authentication request.

No

reg-basic.cfg

reg.x.auth.password

The password to be used for authentication challenges for this registration.

Null (default)

string - It overrides the password entered into the Authentication submenu on the Settings menu of the phone.

No

reg-basic.cfg

reg.x.auth.userId

User ID to be used for authentication challenges for this registration.

Null (default)

string - If the User ID is non-Null, it overrides the user parameter entered into the Authentication submenu on the Settings menu of the phone.

No

reg-advanced.cfg

reg.x.auth.useLoginCredentials

0 - (default) The Login credentials are not used for authentication to the server on registration x.

1 - The login credentials are used for authentication to the server.

No

reg-advanced.cfg

reg.x.bargeInEnabled

0 (default) - barge-in is disabled for line x.

1 - barge-in is enabled (remote users of shared call appearances can interrupt or barge in to active calls).

No

reg.x.bridgeInEnabled

0 (default) - Bridge In feature is disabled.

1 - Bridge In feature is enabled.

No

features.cfg

reg.x.broadsoft.userId

Enter the BroadSoft user ID to authenticate with the BroadSoft XSP service interface.

Null (default)

string

No

features.cfg

reg.x.broadsoft.useXspCredentials

If this parameter is disabled, the phones use standard SIP credentials to authenticate.

1 (default) - Use this value, if phone lines are registered with a server running BroadWorks R19 or earlier.

0 - Set to 0, if phone lines are registered with a server running BroadWorks R19 SP1 or later.

No

features.cfg

reg.x.broadsoft.xsp.password

Enter the password associated with the BroadSoft user account for the line. Required only when reg.x.broadsoft.useXspCredentials=1 .

Null (default)

string

No

reg-advanced.cfg

reg.x.displayName

The display name used in SIP signaling and/or the H.323 alias used as the default caller ID.

Null (default)

UTF-8 encoded string

No

features.cfg

reg.x.enablePvtHoldSoftKey

This parameter applies only to shared lines.

0 (default) - To disable user on a shared line to hold calls privately.

1 - To enable users on a shared line to hold calls privately.

No

reg-advanced.cfg

reg.x.enhancedCallPark.enabled

0 (default) - To disable the BroadWorks Enhanced Call Park feature.

1 - To enable the BroadWorks Enhanced Call Park feature.

No

reg.x.filterReflectedBlaDialogs

1 (default) - bridged line appearance NOTIFY messages are ignored.

0 - bridged line appearance NOTIFY messages is not ignored

No

reg-advanced.cfg

reg.x.fwd.busy.contact

The forward-to contact for calls forwarded due to busy status.

Null (default) - The contact specified by divert.x.contact is used.

string - The contact specified by divert.x.contact is not used

No

reg-advanced.cfg

reg.x.fwd.busy.status

0 (default) - Incoming calls that receive a busy signal is not forwarded

1 - Busy calls are forwarded to the contact specified by reg.x.fwd.busy.contact .

No

reg-advanced.cfg

reg.x.fwd.noanswer.contact

Null (default) - The forward-to contact specified by divert.x.contact is used.

string - The forward to contact used for calls forwarded due to no answer.

No

reg-advanced.cfg

reg.x.fwd.noanswer.ringCount

The number of seconds the phone should ring for before the call is forwarded because of no answer. The maximum value accepted by some call servers is 20.

0 - (default)

1 to 65535

No

reg-advanced.cfg

reg.x.fwd.noanswer.status

0 (default) - The calls are not forwarded if there is no answer.

1 - The calls are forwarded to the contact specified by reg.x.noanswer.contact after ringing for the length of time specified by reg.x.fwd.noanswer.ringCount .

No

debug.cfg

reg.x.gruu

Specify if the phone sends sip.instance in the REGISTER request.

0 (default)

1

No

reg-basic.cfg

reg.x.label

The text label that displays next to the line key for registration x.

The maximum number of characters for this parameter value is 256; however, the maximum number of characters that a phone can display on its user interface varies by phone model and by the width of the characters you use. Parameter values that exceed the phone's maximum display length are truncated by ellipses (…). The rules for parameter up.cfgLabelElide determine how the label is truncated.

Null (default) - the label is determined as follows:
  • If reg.1.useteluriAsLineLabel=1 , then the tel URI/phone number/address displays as the label.
  • If reg.1.useteluriAsLineLabel=0 , then the value for reg.x.displayName , if available, displays as the label. If reg.x.displayName is unavailable, the user part of reg.x.address is used.

UTF-8 encoded string

No

reg-basic.cfg

reg.x.lineAddress

The line extension for a shared line. This parameter applies to private lines and BroadSoft call park and retrieve. If there is no extension provided for this parameter, the call park notification is ignored for the shared line.

Null (default)

String

No

reg-advanced.cfg

reg.x.lineKeys

Specify the number of line keys to use for a single registration. The maximum number of line keys you can use per registration depends on your phone model.

1 (default)

1 to max

No

lync.cfg

reg.x.lisdisclaimer

This parameter sets the value of the location policy disclaimer. For example, the disclaimer may be “Warning: If you do not provide a location, emergency services may be delayed in reaching your location should you need to call for help.”

Null (default)

string, 0 to 256 characters

No

reg-advanced.cfg

reg.x.musicOnHold.uri

A URI that provides the media stream to play for the remote party on hold.

Null (default) - This parameter does not overrides voIpProt.SIP.musicOnHold.uri .

a SIP URI - This parameter overrides voIpProt.SIP.musicOnHold.uri .

No

reg-advanced.cfg

reg.x.offerFullCodecListUponResume

1 (default) - The phone sends full audio and video capabilities after resuming a held call irrespective of the audio and video capabilities negotiated at the initial call answer.

0 - The phone does not send full audio and video capabilities after resuming a held call.

No

reg-basic.cfg

reg.x.outboundProxy.address

The IP address or hostname of the SIP server to which the phone sends all requests.

Null (default)

IP address or hostname

No

sip-interop.cfg

reg.x.outboundProxy.failOver.failBack.mode

The mode for failover failback (overrides reg.x.server.y.failOver.failBack.mode ).

duration - (default) The phone tries the primary server again after the time specified by reg.x.outboundProxy.failOver.failBack.timeout expires.

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.

No

reg-advanced.cfg

reg.x.outboundProxy.failOver.failBack.timeout

3600 (default) -The time to wait (in seconds) before failback occurs (overrides reg.x.server.y.failOver.failBack.timeout ).

0, 60 to 65535 - The phone does not fail back until a failover event occurs with the current server.

No

reg-advanced.cfg

reg.x.outboundProxy.failOver.failRegistrationOn

1 (default) - The reRegisterOn parameter is enabled, the phone silently invalidates an existing registration.

0 - The reRegisterOn parameter is enabled, existing registrations remain active.

No

reg-advanced.cfg

reg.x.outboundProxy.failOver.onlySignalWithRegistered

1 (default) - 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.

0 - The reRegisterOn and failRegistrationOn parameters are enabled, signaling is accepted from and sent to a server that has failed.

No

reg-advanced.cfg

reg.x.outboundProxy.failOver.reRegisterOn

This parameters overrides reg.x.server.y.failOver.reRegisterOn .

0 (default) - The phone won't attempt to register with the secondary server.

1 - The phone attempts to register with (or via, for the outbound proxy scenario), the secondary server.

No

reg-advanced.cfg

reg.x.outboundProxy.port

The port of the SIP server to which the phone sends all requests.

0 - (default)

1 to 65535

No

reg-advanced.cfg

reg.x.outboundProxy.transport

The transport method the phone uses to communicate with the SIP server.

DNSnaptr (default)

DNSnaptr, TCPpreferred, UDPOnly, TLS, TCPOnly

No

sip-interop.cfg

reg.x.protocol.SIP

You can use this parameter for the VVX 500/501, 600/601, and 1500.

1 (default) - SIP signaling is enabled for this registration.

0 - SIP signaling is not enabled for this registration.

No

sip-interop.cfg

reg.x.proxyRequire

Null (default) - No Proxy-Require is sent.

string - Needs to be entered in the Proxy-Require header.

No

reg-advanced.cfg

reg.x.ringType

The ringer to be used for calls received by this registration.

ringer2 (default) - Is the first non-silent ringer.

ringer1 to ringer24 - To play ringer on a single registered line.

No

reg-advanced.cfg

reg.x.serverFeatureControl.callRecording

1 (default) - BroadSoft BroadWorks v20 call recording feature for individual phone lines is enabled.

0 - BroadSoft BroadWorks v20 call recording feature for individual phone lines is disabled.

No

reg-advanced.cfg

reg.x.serverFeatureControl.cf

This parameter overrides voIpProt.SIP.serverFeatureControl.cf .

0 (default) - The server-based call forwarding is disabled.

1 - server based call forwarding is enabled.

Yes

reg-advanced.cfg

reg.x.serverFeatureControl.dnd

This parameter overrides voIpProt.SIP.serverFeatureControl.dnd.

0 (default) - server-based do-not-disturb (DND) is disabled.

1 - server-based DND is enabled and the call server has control of DND.

Yes

sip-interop.cfg

reg.x.serverFeatureControl.localProcessing.cf

This parameter overrides voIpProt.SIP.serverFeatureControl.localProcessing.cf .

0 (default) - If reg.x.serverFeatureControl.cf is set to 1 the phone does not perform local Call Forward behavior.

1 - The phone performs local Call Forward behavior on all calls received.

No

sip-interop.cfg

reg.x.serverFeatureControl.localProcessing.dnd

This parameter overrides voIpProt.SIP.serverFeatureControl.localProcessing.dnd .

0 (default) - If reg.x.serverFeatureControl.dnd is set to 1, the phone does not perform local DND call behavior.

1 - The phone performs local DND call behavior on all calls received.

No

reg-advanced.cfg

reg.x.serverFeatureControl.securityClassification

0 (default) - The visual security classification feature for a specific phone line is disabled.

1 - The visual security classification feature for a specific phone line is enabled.

No

reg-advanced.cfg

reg.x.serverFeatureControl.signalingMethod

Controls the method used to perform call forwarding requests to the server.

serviceMsForwardContact (default)

string

No

sip-interop.cfg

reg.x.srtp.enable

1 (default) - The registration accepts SRTP offers.

0 - The registration always declines SRTP offers.

Yes

sip-interop.cfg

reg.x.srtp.offer

This parameter applies to the registration initiating (offering) a phone call.

0 (default) - No secure media stream is included in SDP of a SIP INVITE.

1 - The registration includes a secure media stream description along with the usual non-secure media description in the SDP of a SIP INVITE.

Yes

sip-interop.cfg

reg.x.srtp.require

0 (default) - Secure media streams are not required.

1 - The registration is only allowed to use secure media streams.

Yes

sip-interop.cfg

reg.x.srtp.simplifiedBestEffort

This parameter overrides sec.srtp.simplifiedBestEffort .

1 (default) - Negotiation of SRTP compliant with Microsoft Session Description Protocol Version 2.0 Extensions is supported.

0 - No SRTP is supported.

No

sip-interop.cfg

reg.x.strictLineSeize

0 (default) - Dial prompt is provided immediately without waiting for a successful OK from the call server.

1 - The phone is forced to wait for 200 OK on registration x when receiving a TRYING notify.

This parameter overrides voIpProt.SIP.strictLineSeize for registration x.

No

sip-interop.cfg

reg.x.tcpFastFailover

0 (default) - A full 32 second RFC compliant timeout is used.

1 - failover occurs based on the values of reg.x.server.y.retryMaxCount and voIpProt.server.x.retryTimeOut .

No

reg-advanced.cfg

reg.x.thirdPartyName

Null (default) - In all other cases.

string address -This field must match the reg.x.address value of the registration which makes up the part of a bridged line appearance (BLA).

No

reg-advanced.cfg

reg.x.useCompleteUriForRetrieve

This parameters overrides voipPort.SIP.useCompleteUriForRetrieve .

1 (default) - The target URI in BLF signaling uses the complete address as provided in the XML dialog document.

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.

No

site.cfg

reg.x.server.H323.y.address

Address of the H.323 gatekeeper.

Null (default)

IP address or hostname

No

site.cfg

reg.x.server.H323.y.port

Port to be used for H.323 signaling. If set to Null, 1719 (H.323 RAS signaling) is used.

0 (default)

0 to 65535

No

site.cfg

reg.x.server.H323.y.expires

Desired registration period.

3600

positive integer

No

site.cfg

reg.x.server.y.address

If this parameter is set, it takes precedence even if the DHCP server is available.

Null (default) - SIP server does not accepts registrations.

IP address or hostname - SIP server that accepts registrations. If not Null, all of the parameters in this table override the parameters specified in voIpProt.server.*

No

reg-advanced

reg.x.server.y.expires

The phone's requested registration period in seconds.

The period negotiated with the server may be different. The phone attempts to re-register at the beginning of the overlap period.

3600 - (default)

positive integer, minimum 10

No

reg-advanced

reg.x.server.y.expires.lineSeize

Requested line-seize subscription period.

30 - (default)

0 to 65535

No

reg-advanced

reg.x.server.y.expires.overlap

The number of seconds before the expiration time returned by server x at which the phone should try to re-register.

The phone tries to re-register at half the expiration time returned by the server if the server value is less than the configured overlap value.

60 (default)

5 to 65535

No

site.cfg

reg.x.server.y.failOver.failBack.mode

duration (default) - The phone tries the primary server again after the time specified by reg.x.server.y.failOver.failBack.timeout .

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.

This parameter overrides voIpProt.server.x.failOver.failBack.mode)

No

site.cfg

reg.x.server.y.failOver.failBack.timeout

3600 (default) - The time to wait (in seconds) before failback occurs.

0 - The phone does not fail back until a failover event occurs with the current server.

60 to 65535 - If set to Duration, the phone waits this long after connecting to the current working server before selecting the primary server again.

No

site.cfg

reg.x.server.y.failOver.failRegistrationOn

1 (default) - The reRegisterOn parameter is enabled, the phone silently invalidates an existing registration (if it exists), at the point of failing over.

0 - The reRegisterOn parameter is disabled, existing registrations remain active.

No

site.cfg

reg.x.server.y.failOver.onlySignalWithRegistered

1 (default) - Set to this value and 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 ends. No SIP messages are sent to the unregistered server.

0 - Set to this value and reRegisterOn and failRegistrationOn parameters are enabled, signaling is accepted from and sent to a server that has failed (even though failback hasn't been attempted or failover hasn't occurred).

No

site.cfg

reg.x.server.y.failOver.reRegisterOn

0 (default) - The phone does not attempt to register with the secondary server, since the phone assumes that the primary and secondary servers share registration information.

1 - The phone attempts 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 proceeds with the secondary server.

This parameter overrides voIpProt.server.x.failOver.reRegisterOn .

No

site.cfg

reg.x.server.y.port

Null (default) - The port of the SIP server does not specifies registrations.

0 - The port used depends on reg.x.server.y.transport .

1 to 65535 - The port of the SIP server that specifies registrations.

No

site.cfg

reg.x.server.y.register

1 (default) - Calls can not be routed to an outbound proxy without registration.

0 - Calls can be routed to an outbound proxy without registration.

See voIpProt.server.x.register for more information, see SIP Server Fallback Enhancements on Polycom Phones - Technical Bulletin 5844 on Polycom Engineering Advisories and Technical Notifications.

No

sip-interop.cfg

reg.x.server.y.registerRetry.baseTimeOut

For registered line x, set y to the maximum time period the phone waits before trying to re-register with the server.Used in conjunction with reg.x.server.y.registerRetry.maxTimeOut to determine how long to wait.

60 (default)

10 - 120 seconds

No

sip-interop.cfg

reg.x.server.y.registerRetry.maxTimeout

For registered line x, set y to the maximum time period the phone waits before trying to re-register with the server. Use in conjunction with r eg.x.server.y.registerRetry.baseTimeOut to determine how long to wait. The algorithm is defined in RFC 5626.

180 - (default)

60 - 1800 seconds

No

reg-advanced.cfg

reg.x.server.y.retryMaxCount

The number of retries attempted before moving to the next available server.

3 - (default)

0 to 20 - 3 is used when the value is set to 0.

No

reg-advanced.cfg

reg.x.server.y.retryTimeOut

0 (default) - Use standard RFC 3261 signaling retry behavior.

0 to 65535 - The amount of time (in milliseconds) to wait between retries.

No

reg-advanced.cfg

reg.x.server.y.subscribe.expires

The phone's requested subscription period in seconds after which the phone attempts to resubscribe at the beginning of the overlap period.

3600 seconds - (default)

10 - 2147483647 (seconds)

You can use this parameter in conjunction with reg.x.server.y.subscribe.expires.overlap .

No

reg-advanced.cfg

reg.x.server.y.subscribe.expires.overlap

The number of seconds before the expiration time returned by server x after which the phone attempts to resubscribe. If the server value is less than the configured overlap value, the phone tries to resubscribe at half the expiration time returned by the server.

60 seconds (default)

5 - 65535 seconds

No

site.cfg

reg.x.server.y.transport

The transport method the phone uses to communicate with the SIP server.

DNSnaptr (default) - If reg.x.server.y.address is a hostname and reg.x.server.y.port is 0 or Null, do NAPTR then SRV look-ups to try to discover the transport, ports and servers, as per RFC 3263. If reg.x.server.y.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 is used.

TLS - If TLS fails, transport fails. Leave port field empty (defaults to 5061 ) or set to 5061 .

TCPOnly - Only TCP is used.

No

site.cfg

reg.x.server.y.useOutboundProxy

1 (default) - Enables to use the outbound proxy specified in reg.x.outboundProxy.address for server x.

0 - Disable to use the outbound proxy specified in reg.x.outboundProxy.address for server x.

No

site.cfg

divert.x.sharedDisabled

1 (default) - Disables call diversion features on shared lines.

0 - Enables call diversion features on shared lines.

Yes

A shared line is an address of record managed by a call server. The server allows multiple endpoints to register locations against the address of record.

Polycom devices support Shared Call Appearance (SCA) using the SUBSCRIBE-NOTIFY method specified in RFC 6665. The events used are:
  • call-info for call appearance state notification
  • line-seize for the phone to ask to seize the line