Attempts to route to servers in an Exchange UM Dialplan failed – Lync 2010-2013

For whatever reason I get this error message every 10 days the outcome of which no user is able to access Voicemail internally or externally.

Call logs for the past 30 days show that this happens every 10 business days and the solution has always been to restart the exchange UM service on the Windows SBS . However yesterday, that solution did not work and I had to spend an hour going over the Lync + Exchange Um steps to see what was wrong.

What seemed to resolve this for now was simply re-running the exchutil.ps1 from the exchange server.

Logs from the Lync server read as such :

Attempts to route to servers in an Exchange UM Dialplan failed

No server in the dialplan [CIN_SA.cin.local] accepted the call with id [67ab49c9-111b-4700-b33b-a416d6cd6879].

Cause: Dialplan is not configured properly.

Resolution:

Check the configuration of the dialplan on Exchange UM Servers.

Any idea why the weekly failure ?

March 6th, 2015 12:46pm

I haven't seen anything quite like that, do you see any events in the event log on the Exchange server?  Are both Exchange and Lync fully up to date from a service pack and CU standpoint?

Free Windows Admin Tool Kit Click here and download it now
March 6th, 2015 2:28pm

lol - Welcome to my world and Lync ! It hasn't been that friendly to me :(

I cant speak for the Exchange but Lync is up to date. Does it help that the Exchange Server is on a Windows SBServer ? In any case It has not been the Issue but for the last 30days.

March 6th, 2015 3:20pm

SBS might be an issue, if there are performance issues.  Is the server running at a pretty taxed level RAM-wise?
Free Windows Admin Tool Kit Click here and download it now
March 6th, 2015 3:40pm

We've pretty okay on that level I found this article

http://empiricalmusing.com/Lists/Posts/Post.aspx?ID=48

but could not run the cmdlet on the xchange server 2010 do you have an idea what the command Is on exchange 2010 ?

March 6th, 2015 5:00pm

There's not an equivalent for 2010, but that's likely not your issue either.  They're saying the 2013 call router was deactivated.  Do you see anything in your event logs?
Free Windows Admin Tool Kit Click here and download it now
March 6th, 2015 5:42pm

Nope - I guess I was just grasping and trying to find what the Issue is.
March 6th, 2015 6:10pm

Hi,

Base on your description above, it can be the issue of the SBS Performance.

Also, please try to delete and re-create the dialplan to check if it could solve the problem.

Best Regards,
Eason Huang

Free Windows Admin Tool Kit Click here and download it now
March 9th, 2015 6:24am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics