EnableCallPickup
|
true
false
|
Specifies if a user can pickup a call in their call pickup
group.
Example: <EnableCallPickup>true </EnableCallPickup>
|
EnableGroupCallPickup
|
true
false
|
Specifies if a user can pickup incoming calls in another
call pickup group, by entering the call pickup group number.
Example: <EnableGroupCallPickup>true </EnableGroupCallPickup>
|
EnableOtherGroupPickup
|
true
false
|
Specifies if a user can pickup an incoming call in a group
that is associated with their own call pickup group.
Example: <EnableOtherGroupPickup>true </EnableOtherGroupPickup>
|
EnableHuntGroup
|
true
false
|
Specifies if a user can log into a hunt group.
Example: <EnableHuntGroup>true</EnableHuntGroup>
|
PreventDeclineOnHuntCall
|
true
false
|
Specifies if the Decline button is displayed for an incoming
call in a hunt group.
Example: <PreventDeclineOnHuntCall>true</PreventDeclineOnHuntCall>
|
TelemetryCustomerID
|
String
|
Specifies the source of analytic information. This can be a
string that explicitly identifies an individual customer or a string that
identifies a common source without identifying the customer. Cisco recommends
using a Global Unique Identifier (GUID) generating utility to generate a 36
character unique identifier or to use a reverse domain name. The following
utilities are available for generating a GUID:
This identifier should be globally unique regardless of the
method used to create the GUID.
Example: <TelemetryCustomerID>customerIdentifier</TelemetryCustomerID>
|
SSO_Enabled
|
TRUE
FALSE
|
Specifies whether users sign in by using single sign-on
(SSO).
Example: <SSO_Enabled>FALSE</SSO_Enabled>
|
EnableSIPURIDialling
|
true
false
|
Enables URI dialing with Cisco UC Integration for Microsoft Lync and allows users to make calls with URIs.
Example: <EnableSIPURIDialling>true </EnableSIPURIDialling>
|
ServicesDomainSsoEmailPrompt
|
ON
OFF
|
Specifies whether the user is shown the email prompt for the
purposes of determining their home cluster.
Example: <ServicesDomainSsoEmailPrompt>ON</ServicesDomainSsoEmailPrompt>
|
EnableTelProtocol
|
true
false
|
Specifies if the client registers as the protocol handler for the tel: URI.
Example: <EnableTelProtocol>false</EnableTelProtocol>
|
EnableImProtocol
|
true
false
|
Specifies if the client registers as the protocol handler for the IM: URI.
Example: <EnableIMProtocol>false</EnableIMProtocol>
|
EnableProvisionProtocol
|
true
false
|
Specifies if the client registers as the protocol handler for the provision URI.
Example: <EnableProvisionProtocol>false</EnableProvisionProtocol>
|
EnableSIPProtocol
|
true
false
|
Specifies if the client registers as the protocol handler for the SIP: URI.
Example: <EnableSIPProtocol>false</EnableSIPProtocol>
|
EnableTelephonyProtocolRateLimit
|
true
false
|
Specifies if rate limiting is enabled for executing the telephony protocol handlers
Example: <EnableTelephonyProtocolRateLimit>false</EnableTelephonyProtocolRateLimit>
|
TelephonyProtocolRateLimit
|
number
|
Specifies the number of times a call can be initiated from one of the telephony protocol handlers (tel: ciscotel,
sip). For example, if the TelephonyProtocolRateLimit is 2 and the TelephonyProtocolTimeLimit is 10 seconds,
then a user can initiate a call from one of the telephony protocol handlers 2 times every 10 seconds.
You can set the value between 1-100. The default value is 2.
Note
|
Only one protocol handler can be processed at one time. Any other protocol handler arriving when the
user already has a call alert are either discarded or queued up.
|
Example: <TelephonyProtocolRateLimit>10</TelephonyProtocolRateLimit>
|
TelephonyProtocolTimeLimit
|
number
|
Specifies the time within which a user can initiate a call from one of the telephony protocol handlers (sip, tel, ciscotel)
before the TelephonyProtocolRateLimit is hit or reset. The default value for initiating a call from one of the telephony protocol
handlers is 10 seconds for every 2 attempts. You can set the value between 1-300 seconds.
Example: <TelephonyProtocolTimeLimit>10</TelephonyProtocolTimeLimit>
|
LogWritingDesktop
|
|
Defines the level of security for PRT logging by specifying whether logs are written to disc for desktop clients.
-
Always (default)—Logs are always written to disc. No option appears in the client Help menu.
-
UserCanEnable—Allows users to decide whether logs are written to disc or not. Setting this value creates
an Enable Detailed Logging option in the Help menu of the client that the user can enable or disable.
-
Never—Logs are never written to disc. When a PRT is manually generated, in-memory logs are flushed
to a temporary file that is deleted as soon as the PRT is generated.
Example: <LogWritingDesktop>UserCanEnable</LogWritingDesktop>
|
DetailedLogDurationDesktop
|
|
If you configure the LogWritingDesktop parameter with the value UserCanEnable, then this parameter defines
the number of hours that the desktop client writes logs to the disc. After the defined period expires, all logs
are cleared from the disc.
If you do not specify a value for this parameter (default), then the client writes logs to the disc indefinitely,
or until the user disables detailed logging.
Example: <DetailedLogDurationDesktop>10</DetailedLogDurationDesktop>
|