Link to home
Start Free TrialLog in
Avatar of usslindstrom
usslindstromFlag for Japan

asked on

Exchange 2013 Unified Messaging / Server not answering calls


I've been attempting to get Exchange 2013 Unified Messaging working in my lab enviornment.  In every instance I've installed Exchange (new forest/domain, new servers with unique SIDS, etc.), UM on the Exchange server has never answered any phone calls.

In this environment, all of the IP phones are reporting into CME 7, and the voicemail/sip service of that device points directly to the Exchange box.  When voicemail or any configured auto attendant is attempted to be called, the cisco phones just "ring out" (they're trying to call), but they eventually just time out trying to connect.

This is only for Exchange 2013, that it doesn't work - to make sure I wasn't crazy in one of my tests I threw on an Exchange 2010 instance, and everything works absolutely perfectly.  Exchange 2010 UM picks up the phone calls for all of the configured attendants, and the mailbox service.  Removing that domain and returning to test to Exchange 2013, I'm back to where the server doesn't answer again.

I've made sure the configurations between Exchange 2010 and 2013 are 100% identical.  The one caveat is that 2013 no longer forces you to bind a server to a dial-plan like 2010 did.  (This may be the issue).

In any case, would anybody happen to have any ideas where I can go to find a path to resolution?  - And as always, thanks for always assisting me.
Avatar of usslindstrom
Flag of Japan image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of usslindstrom


I am awesome!