We have attempted our first Cisco CallManager Express (CME) to Exchange 2013 UM integration (we have a lot of successful experience with Exchange 2007 and 2010). In our initial tests, all calls into Exchange are giving us busy signals. So we compared the dialplan with a 2010 dialplan (Get-UMDialPlan | fl) and found one key difference. The UMservers field is blank in our 2013 dialplan. So we attempt to associate the dialplan with the server and we're running into errors:
- [PS] C:\Windows\system32>Set-UMCallRouterSettings -Server Exchange -DialPlans CME
Creating a new session for implicit remoting of "Set-UMCallRouterSettings" command...
The dial plan 'CME' can't be associated with the Client Access server. Only SIP URI dial plans can be associated with Exchange 2013 Client Access servers.
+ CategoryInfo : InvalidData: (CME:UMDialPlan) [Set-UMCallRouterSettings], CannotAddNonSip...RouterException
+ FullyQualifiedErrorId : 2E9F8B3,Microsoft.Exchange.Management.Tasks.UM.SetUMCallRouterSettings
+ PSComputerName : Exchange.domain.local
- [PS] C:\Windows\system32>Set-UMService -Identity Exchange -Dialplans CME
The dial plan 'CME' can't be associated with the Client Access or Mailbox server. Only SIP URI dial plans can be associated with a Client Access or Mailbox server.
+ CategoryInfo : InvalidData: (CME:UMDialPlan) [Set-UMService], CannotAddNonSipNameDialplanException
+ FullyQualifiedErrorId : F179D874,Microsoft.Exchange.Management.Tasks.UM.SetUMServer
+ PSComputerName : Exchange.domain.local
So according to the errors, only SIP URI dial plans can be associated with 2013 UM servers. The trouble is we're using TelExtn dial plan. Something has changed that's not permitting this in 2013, so any pointers would be welcome.
Thank you!