EXAMPLE 1

This example uses the Get-CsCdrConfiguration cmdlet to return a collection of all the CDR settings configured for use in your organization.

	Copy Code
Get-CsCdrConfiguration

EXAMPLE 2

Example 2 uses the Identity parameter to return a single collection of CDR settings: the settings with the Identity site:Redmond.

	Copy Code
Get-CsCdrConfiguration -Identity site:Redmond

EXAMPLE 3

In Example 3, the Filter parameter is employed to return all the CDR settings that have been configured at the site scope. The filter value "site:*" returns all the CDR settings that have an Identity that begins with the string value "site:". By definition, those are settings that have been configured at the site scope.

	Copy Code
Get-CsCdrConfiguration -Filter site:*

EXAMPLE 4

Example 4 returns a collection of all the CDR settings where the KeepCallDetailForDays property is fewer than 30 days. To do this, the command first uses the Get-CsCdrConfiguration cmdlet to return a collection of all the CDR settings configured in the organization. That collection is then piped to the Where-Object cmdlet, which picks out only those settings where the KeepCallDetailForDays value is less than 30 days.

	Copy Code
Get-CsCdrConfiguration | Where-Object {$_.KeepCallDetailForDays -lt 30}

Call detail recording (CDR) provides a way for you to track usage of Lync Server capabilities such as Voice over IP (VoIP) phone calls; instant messaging (IM); file transfers; audio/video (A/V) conferencing; and application sharing sessions. CDR (which is available only if you have deployed the Monitoring service) keeps usage information: it logs information such as the parties involved in the call; the length of the call; and whether or not any files were transferred. (However, CDR does not make a recording of the call itself.)

CDR also keeps track of call error information: detailed diagnostic data for both peer-to-peer sessions and for conferencing calls.

As an administrator, you can determine whether or not CDR is used in your organization. If the Monitoring service has been deployed, you can enable or disable CDR. In addition, you can make this decision globally (in which case CDR will either be enabled or disabled throughout the organization) or on a site-by-site basis; for example, you could use CDR in the Redmond site but not use CDR in the Paris site.

The Get-CsCdrConfiguration cmdlet provides a way for you return detailed information about how CDR is used in your organization.

Who can run this cmdlet: By default, members of the following groups are authorized to run the Get-CsCdrConfiguration cmdlet locally: RTCUniversalUserAdmins, RTCUniversalServerAdmins. To return a list of all the role-based access control (RBAC) roles this cmdlet has been assigned to (including any custom RBAC roles you have created yourself), run the following command from the Windows PowerShell prompt:

Get-CsAdminRole | Where-Object {$_.Cmdlets –match "Get-CsCdrConfiguration"}

None. The Get-CsCdrConfiguration cmdlet does not accept pipelined input.

The Get-CsCdrConfiguration cmdlet returns instances of the Microsoft.Rtc.Management.WritableConfig.Settings.CallDetailRecording.CdrSettings object.