If you do not know how Exchange will communicate with the PBX, it would be wise to ask your
PBX admin to find out what options your PBX has for interfacing with the UM server. For a list of
supported connections, see microsoft.com/technet/prodtechnol/exchange/telephonyadvisor.
mspx . The last required option is to generate the UM mailbox policy. If you were to use the
wizard in the EMC it would automatically create one. The syntax for the New - UMDialPlan is as follows:
New-UMDialPlan -Name < String > -NumberOfDigitsInExtension < Int32 > [-
AccessTelephoneNumbers < MultiValuedProperty > ] [-Confirm [ < SwitchParameter > ]] [-
DomainController < Fqdn > ] [-FaxEnabled < $true | $false > ] [-GenerateUMMailboxPolicy
< $true | $false > ] [-NDREnabled < $true | $false > ] [-TemplateInstance < PSObject > ] [-
URIType < TelExtn | E164 | SipName > ] [-VoIPSecurity < SIPSecured |Unsecured |
Secured > ] [-WhatIf [ < SwitchParameter > ]] [ < CommonParameters > ]
In the following example, the UM mailbox policy is blank so you can learn what goes into a UM
mailbox policy:
New-UMDialPlan -name test -NumberOfDigitsInExtension 4 -URIType TelExtn -
GenerateUMMailboxPolicy $false
The second component required in a working UM configuration is to configure the UM IP gateway. For
the New-UMIPGateway cmdlet there are also three required parameters: name, IP address, and UM dial
plan.
Pages:
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389