locked
Exchange 2010 to 2013 Unified Messaging migration - issues RRS feed

  • Question

  • Hi,

    I am trying to work through the process of migrating Exchange 2010 UM to Exchange 2013 using Cisco Call Manager. I have voicemail working on my Exchange 2010 servers using port 5060 - VOIP security set to unsecure

    I have reviewed article at https://technet.microsoft.com/en-us/library/dn169226%28v=exchg.150%29.aspx and various other articles.

    The route I have taken is as follows:

    - My pilot number, default dial plan, IP gateways and hungroup are configured on the Exchange 2010 servers

    - I updated the SIP trunk on Call Manger to point to my Exchange 2013 servers.  After a short delay, I was able to dial the pilot number and leave a voicemail message on a new Exchange 2013 voice mail enabled mail box.  However,.... when I try to leave a voicemail on an Exchange 2010 mailbox, the call is dropped. 

    My Observations:

    - powershell commands test-serverhealth and Test-UMserver shows no errors

    - when I view the um mailbox settings of Exchange 2010 user in 2013 the following error is displayed "The user 'D.Brown@.test.com' isn't UM-enabled, or is UM-enabled and has a mailbox whose version isn't supported by this Mailbox server.

    - I've reviewed event logs and see no errors.

    It looks to me that Exchange 2013 is not recognising that the Exchange 2010 voicemail enabled accounts exists. Does anyone have any suggestions on how to move forward with this issue?

    Thanks in advance , Joe


    Tuesday, September 20, 2016 6:07 PM

Answers

  • An update:

    We have now migrated our Exchange Unified Messaging services over to our new Exchange 2013 servers.

    In our environment we had dedicated Exchange 2010 unified messaging servers.  The below articles are a must read for anyone migrating from Exchange 2010 to Exchange 2013 where Cisco Call Manger 10.6 is implemented.

    https://supportforums.cisco.com/discussion/11914031/exchange-2013-um-and-cucm-86

    http://social.technet.microsoft.com/wiki/contents/articles/23416.exchange-2013-unified-messaging-with-cisco-unified-communication-manager.aspx

    • Marked as answer by Rob Garbutt Friday, November 25, 2016 3:50 PM
    Friday, November 25, 2016 3:50 PM

All replies

  • Hi.

    Are you run Exchucutl.ps1 on every Exchange 2013 cas servers and on every Exchange 2013 mailbox servers?

    Use Unified Messaging Troubleshooting Tool for troubleshooting.


    MCITP, MCSE. Regards, Oleg

    Tuesday, September 20, 2016 6:32 PM
  • Hi.

    Are you run Exchucutl.ps1 on every Exchange 2013 cas servers and on every Exchange 2013 mailbox servers?


    MCITP, MCSE. Regards, Oleg

    You only need to run that command once.


    Blog:    Twitter:   

    Tuesday, September 20, 2016 6:40 PM
  • Hi,

    I am trying to work through the process of migrating Exchange 2010 UM to Exchange 2013 using Cisco Call Manager. I have voicemail working on my Exchange 2010 servers using port 5060 - VOIP security set to unsecure

    I have reviewed article at https://technet.microsoft.com/en-us/library/dn169226%28v=exchg.150%29.aspx and various other articles.

    The route I have taken is as follows:

    - My pilot number, default dial plan, IP gateways and hungroup are configured on the Exchange 2010 servers

    - I updated the SIP trunk on Call Manger to point to my Exchange 2013 servers.  After a short delay, I was able to dial the pilot number and leave a voicemail message on a new Exchange 2013 voice mail enabled mail box.  However,.... when I try to leave a voicemail on an Exchange 2010 mailbox, the call is dropped. 

    My Observations:

    - powershell commands test-serverhealth and Test-UMserver shows no errors

    - when I view the um mailbox settings of Exchange 2010 user in 2013 the following error is displayed "The user 'D.Brown@.test.com' isn't UM-enabled, or is UM-enabled and has a mailbox whose version isn't supported by this Mailbox server.

    - I've reviewed event logs and see no errors.

    It looks to me that Exchange 2013 is not recognising that the Exchange 2010 voicemail enabled accounts exists. Does anyone have any suggestions on how to move forward with this issue?

    Thanks in advance , Joe


    Enabled SIP logging on the Cisco side and make sure it can handle the redirect SIP commands when the mailbox is on 2010. It should be redirecting (302) to the 2010 UM server. 

    You can also enable UM Logging on the Exch servers.


    Blog:    Twitter:   

    Tuesday, September 20, 2016 6:42 PM
  • Thanks for your responses guys.

    Making good progress with the help of the below articles. All seems to be working now expected for the "play  voice mail on phone.." link which is embedded in the voice mail message. Will provide a further update when this issue is resolved

     https://supportforums.cisco.com/discussion/11914031/exchange-2013-um-and-cucm-86

    http://social.technet.microsoft.com/wiki/contents/articles/23416.exchange-2013-unified-messaging-with-cisco-unified-communication-manager.aspx

    • Proposed as answer by Oleg.Kovalenko Wednesday, September 21, 2016 6:47 PM
    Wednesday, September 21, 2016 5:27 PM
  • An update:

    We have now migrated our Exchange Unified Messaging services over to our new Exchange 2013 servers.

    In our environment we had dedicated Exchange 2010 unified messaging servers.  The below articles are a must read for anyone migrating from Exchange 2010 to Exchange 2013 where Cisco Call Manger 10.6 is implemented.

    https://supportforums.cisco.com/discussion/11914031/exchange-2013-um-and-cucm-86

    http://social.technet.microsoft.com/wiki/contents/articles/23416.exchange-2013-unified-messaging-with-cisco-unified-communication-manager.aspx

    • Marked as answer by Rob Garbutt Friday, November 25, 2016 3:50 PM
    Friday, November 25, 2016 3:50 PM