Exchange 2013 SP1 and CUCM 9.1.2 - Exch not recognizing called extension RRS feed

  • Question

  • I think I'm almost there in getting Exchange 2013 SP1 UM working with CUCM 9.1.2...I've got two issues at the moment that I need a little help with.

    1) When I dial my VM pilot (6040) from a UM enabled extension it prompts to enter an extension. When I dial the same extension and let it ring to VM, Exchange picks up and says "the person you are trying to reach does not have a valid voice mail box on our system".

    2) This just started happening this afternoon, when I dial my VM pilot (6040) exch3 picks up as thats what I have my route pattern pointing to. If I enter the extension of a mailbox on exch2, I get stuck in a endless loop.

    I've followed this post as a guide but it hasn't resolved my issue.


    My Exchange environment looks like this:

    Site 1:

    exch1 - CAS/Mailbox, used for mainly utility type work, journal, dedicated SMTP flows etc
    exch2 - CAS/Mailbox, part DAG13
    exch3 - CAS/Mailbox, part of DAG13

    Site 2:

    exch2dr - CAS/Mailbox, part of DAG13
    exch3dr - CAS/Mailbox, part of DAG13

    DAG13 is stretched between two sites, there are no users at our DR site so CUCM is pointing to Site 1 for UM. Each site has an internet facing CAS-only server for OWA/EAS etc.

    Any help is greatly appreciated. I'd love to get rid of Unity. 


    I just found this event in the event logs:

    The Microsoft Exchange Unified Messaging service on the Mailbox server received a diverted call with ID "d51600-3a3140c5-9b8-c1414ac@EXCH3-IPADDR" for extension "4099" on UM dial plan "CUCM" from UM IP gateway "CUCM IP", but no UM-enabled mailbox for the corresponding extension could be found. Please check the extension and make sure that the corresponding mailbox is enabled for UM and associated with the correct UM dial plan.

    • Edited by ScottHeath7288 Thursday, June 19, 2014 9:45 PM new information
    Thursday, June 19, 2014 9:41 PM

All replies

  • Exchange 2013 will send redirects with the FQDN of the mailbox servers, can you confirm that your CUCM can resolve against AD DNS? Something is strange with your diversion headers.

    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer". SWC Unified Communications

    Friday, June 20, 2014 2:06 AM
  • yeah I went through that already. If it can't resolve DNS then in a packet capture you don't see anything after the initial 302 status. The guy that implemented our CUCM didn't have DNS servers configured in CM. We resolved that a few nights ago. Exchange at least answers the call now, just not properly.
    Friday, June 20, 2014 11:44 AM
  • Hello Mate

    Have you been able to make any progress with this by any chance? We have the same issues and are dead in the water


    Monday, September 29, 2014 2:14 AM
  • Nope. We are in the process of reconfiguring our exchange environment to separate rolls out. If I have time in the next few months I'll do some more testing.
    Monday, September 29, 2014 6:35 PM
  • Hit me up on a private message if you are still interested in this one - we just got it working - be good to see if it works for someone else before making it public

    Thursday, October 2, 2014 10:26 PM
  • Angus, what version of CUCM are you running? I can't find the PM option to PM you. We are running 10.5 now and Exchange 2013 SP1
    Friday, October 3, 2014 4:27 PM
  • 9.1.2 I think it is, we upgraded to avoid the known DNS bug

    I cant see how to PM you either

    The crux of it was outlined below with some tweaks


    As we have multiple combined role servers, our trunks are set up as follows:
    1. 1 x CAS Trunk - contains all CAS Servers on port 5060
    2. 4 x MBX Trunks - contains Maibox Server with ports 5062-5068

    On top of that, we had to Allow "Redirecting Diversion Header Delivery - Inbound (and Outbound)" on the CAS Trunk but DISABLE it on the Mailbox Trunks

    Also, make sure that you are using Telephone Extension Dial plans in Exchange 2013 (Despite them being unable to be associated with a 13 Server - EX13 answers for all calls anyway)

    Lastly, the MS documentation is a little strange - it says that as your last step of UM migration, you should point your Call Manager to 2013 - I don't agree with that statement, EX13 routes calls back to 2010 UM Servers perfectly fine, so treat it the same as any other CAS based service - point to 2013, and it will handle the rest

    Tuesday, October 7, 2014 12:20 AM
  • Thanks Angus! Once I get some time I'll look into this again with those tweaks in mind. I guess since MS left out the PM feature, you can reach me by e-mail at sheath7288 at gmail if you'd like.
    Thursday, October 9, 2014 6:24 PM