In order to do this, Exchange Server 2007 has shipped with a
series of Get-UM* cmdlets. These wonderful cmdlets allow for the retrieval of data as well as using the
data as pipelined input into other cmdlets. This section deals with the following cmdlets:
??‘ Get-UMAutoAttendant
??‘ Get-UMDialPlan
Chapter 10: Unifi ed Messaging
285
??‘ Get-UMHuntGroup
??‘ Get-UMIPGateway
??‘ Get-UMServer
??‘ Get-UMVirtualDirectory
??‘ Get-UMMailbox
??‘ Get-UMMailboxPIN
??‘ Get-UMMailboxPolicy
When looking at the Get-UM cmdlets, they can be broken down into two categories, SIP/Server facing
and user facing. The Sip/Server - facing cmdlets allow for the retrieval of the UMIPGateway, or a
UMDialPlan name. The user - facing cmdlets deal with UMMailboxPolicies or a UMMailboxPIN
number. First we discuss the SIP - facing Get-UM cmdlets.
During day - to - day operations, the UM administrator may want to see what the current call volume
looks like on a particular server, dial plan, or gateway. Get-UMActiveCalls allows that. The syntax for
Get-UMActive calls is as follows:
Get-UMActiveCalls [-DomainController < Fqdn > ] [-Server < ServerIdParameter > ]
[ < CommonParameters > ]
Get-UMActiveCalls -InstanceServer < UMServer > [-DomainController < Fqdn > ]
[ < CommonParameters > ]
Get-UMActiveCalls -DialPlan < UMDialPlanIdParameter > [-DomainController < Fqdn > ]
[ < CommonParameters > ]
Get-UMActiveCalls -IPGateway < UMIPGatewayIdParameter > [-DomainController < Fqdn > ]
[ < CommonParameters > ]
If the cmdlet is run without any parameters, it will return statistics for the local server.
Pages:
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411