You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/Export-UMCallDataRecord.md
+3-83Lines changed: 3 additions & 83 deletions
Original file line number
Diff line number
Diff line change
@@ -6,12 +6,6 @@ schema: 2.0.0
6
6
# Export-UMCallDataRecord
7
7
8
8
## SYNOPSIS
9
-
!!! Exchange Server 2010
10
-
11
-
Use the Export-UMCallDataRecord cmdlet to export Unified Messaging (UM) call data records for UM dial plans and UM IP gateways for a date that you've specified.
12
-
13
-
!!! Exchange Server 2013
14
-
15
9
This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
16
10
17
11
Use the Export-UMCallDataRecord cmdlet to export Unified Messaging (UM) call data records for UM dial plans and UM IP gateways for a date that you've specified.
@@ -22,23 +16,10 @@ For information about the parameter sets in the Syntax section below, see Exchan
The Export-UMCallDataRecord cmdlet exports Unified Messaging call data records for a specified date to a comma separated value (.csv) file. You can filter call data records for specific UM dial plans and/or UM IP gateways; however, if you don't specify a UM IP gateway, all call data records will be returned.
33
-
34
-
The Export-UMCallDataRecord cmdlet is available when you're using the Exchange Control Panel. You can't use the cmdlet from the Exchange Management Shell.
35
-
36
-
After this task is completed, a report is generated that contains Unified Messaging call data records.
37
-
38
-
You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "UM call data and summary reports" entry in the Unified Messaging Permissions topic.
39
-
40
-
!!! Exchange Server 2013
41
-
42
23
The Export-UMCallDataRecord cmdlet exports Unified Messaging call data records for a specified date to a comma-separated value (CSV) file. You can filter call data records for specific UM dial plans or UM IP gateways. However, if you don't specify a UM IP gateway, all call data records are returned.
43
24
44
25
The Export-UMCallDataRecord cmdlet is available when you're using the Exchange Administration Center. You can't use the cmdlet from the Exchange Management Shell.
@@ -49,28 +30,14 @@ You need to be assigned permissions before you can run this cmdlet. Although all
49
30
50
31
## EXAMPLES
51
32
52
-
### Example 1 -------------------------- (Exchange Server 2010)
53
-
```
54
-
Export-UMCallDataRecord -Date 02/01/10
55
-
```
56
-
57
-
This example returns all Unified Messaging call data records and exports them to a CSV file.
58
-
59
-
### Example 1 -------------------------- (Exchange Server 2013)
33
+
### Example 1
60
34
```
61
35
Export-UMCallDataRecord -Date 02/01/12
62
36
```
63
37
64
38
This example returns all Unified Messaging call data records on February 1, 2012, and exports them to a CSV file.
65
39
66
-
### Example 2 -------------------------- (Exchange Server 2010)
The Date parameter specifies the date of Unified Messaging call data records to retrieve, in the last 90 days. If there are no call records for the date specified, the report will be empty.
102
-
103
-
104
-
105
-
!!! Exchange Server 2013
106
-
107
66
The Date parameter specifies the date of Unified Messaging call data records to retrieve. If there are no call records for the date specified, the report will be empty.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
148
-
149
-
150
-
151
-
!!! Exchange Server 2013
152
-
153
102
This parameter is available only in on-premises Exchange.
154
103
155
104
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
156
105
157
-
158
-
159
106
```yaml
160
107
Type: Fqdn
161
108
Parameter Sets: (All)
@@ -169,35 +116,9 @@ Accept pipeline input: False
169
116
Accept wildcard characters: False
170
117
```
171
118
172
-
### -Organization
173
-
The Organization parameter is reserved for internal Microsoft use.
174
-
175
-
```yaml
176
-
Type: OrganizationIdParameter
177
-
Parameter Sets: (All)
178
-
Aliases:
179
-
Applicable: Exchange Server 2010
180
-
181
-
Required: False
182
-
Position: Named
183
-
Default value: None
184
-
Accept pipeline input: False
185
-
Accept wildcard characters: False
186
-
```
187
-
188
119
### -UMDialPlan
189
-
!!! Exchange Server 2010
190
-
191
-
The UMDialPlan parameter specifies the UM dial plan to export statistics for. If you don't specify a UM dial plan, statistics include all UM dial plans in the organization
192
-
193
-
194
-
195
-
!!! Exchange Server 2013
196
-
197
120
The UMDialPlan parameter specifies the UM dial plan to export statistics for. If you don't specify a UM dial plan, statistics include all UM dial plans in the organization.
198
121
199
-
200
-
201
122
```yaml
202
123
Type: UMDialPlanIdParameter
203
124
Parameter Sets: (All)
@@ -261,4 +182,3 @@ To see the return types, which are also known as output types, that this cmdlet
0 commit comments