none
OCS 2007 R2 with Exchange 2010 UM Voicemail

    Question

  • Hello Everyone,
     Been having a fun time migrating to Exchange 2010 UM from 2007 UM. I have the new SIP Dial plan setup for Exchange 2010 with one user added. The new dial plan has been setup in Active Directory for a Subscriber Access number. When i click Call Voicemail from within communicator i get "Voicemail is unreachable". The error in event viewer is below, anyone have an idea of where  i have the problem?

    Response Data:

    183 Session Progress

     

    101 Progress Report

    ms-diagnostics: 13007;reason="Request was proxied to an application.";source="OCS1.Domain.local";targetApp="voicemail";appName="InboundRouting"

     

    101 Diagnostics

    ms-diagnostics: 15008;reason="Routing to UM for Subscriber Access";source="OCS1.Domain.local";dialplan="IBT_Exchange2010.Domain.local";umserver="EXCHANGE10-UM.Domain.local";appName="ExumRouting"

     

    101 Diagnostics

    ms-diagnostics: 15008;reason="Routing to UM for Subscriber Access";source="OCS1.Domain.local";dialplan="IBT_Exchange2010.Domain.local";umserver="EXCHANGE10-UM.Domain.local";appName="ExumRouting"

     

    480 Temporarily Unavailable

    ms-diagnostics: 13001;reason="The routing rules did not result in a suitable final response";source="OCS1.Domain.local";received="403";appName="InboundRouting"

    Tuesday, February 02, 2010 9:24 PM

Answers

  • Gavin,
      Sorry for the late reply, i didnt get a notification about an update.

    With some direction from Drago i will able to work my way into the cause of the issues. The system mailbox and search mailbox was not working properly, so recreating them and re running setup /preparead fixed the issues.

    -Jason
    Thursday, February 18, 2010 10:58 PM

All replies

  • Might not be related, but... I pulled my hair (or what left of it) one whole day only to find that with Exchange 2010, TLS support is not enabled by default - you must do it, or Voicemail with OCS integration will not work.

    You wil find it under Server Configuration -> Unified Messaging -> Properties -> UM Settings. Set it to "Dual" if you will use both OCS and another gateways...

    Drago
    http://ocsdude.blogspot.com | MVP Snom OCS Edition
    Tuesday, February 02, 2010 9:33 PM
  • Thanks for the suggestion, but it didnt fix my problem. I have done everything i can see possible, but there is something still missing. I can dial the UM access for Exchange 2007, but 2010 says Voicemail Unavailable.
    Thursday, February 04, 2010 3:47 AM
  • Assuming you installed a valid certificate on UM role server…

    The next step is: use the Front End Server's Logging Tool and capture SIP Stack trace while attempting to reach the voicemail. To view the log, you need to have OCS 2007 R2 Resource Kit installed on your FE server. 99% of the time the reason as of why something is not working is pretty obvious.

    Drago


    http://ocsdude.blogspot.com | MVP Snom OCS Edition
    Thursday, February 04, 2010 7:13 PM
  • OK just to verify you have done the following:

    1. Exchange 2010 UM server is installed and has a cert (other than the default self signed cert) on the UM role.  (If you could a get-exchangecertificate would help)
    2. You have restarted the Exchange Unified Messaging Service after Installing the Cert and changing the UM Startup to Both or TLS
    3. The New Exchange 2010 server shows up under Associated UM Servers on the EMC Org Config - UM - UM Dial Plans Tab
    4. You have run OCSUMUTIL.exe to associate the subscriber access number with the dial plan

    What happens if you dial the VM Pilot number from OCS without clicking call voicemail?
    Mark King | C/D/H | MCTS:OCS | MCSE: Messaging | MCITP:Enterprise Administrator | CCNA
    Thursday, February 04, 2010 7:33 PM
  • 1. [PS] C:\Windows\system32>Get-ExchangeCertificate

    Thumbprint                                Services   Subject
    ----------                                --------   -------
    53F9B2893B7E18FC7F6D480C45A9C17523151856  ......     CN=WMSvc-EXCHANGE10-UM
    10C590EC0A6EA890B5DF2CCDF4A4B2E972A1404A  ..U...     CN=EXCHANGE10-UM.Domain.local

    2. i restarted the entire server after the certificate installation, startup of mode is Dual
    3. the new dial plan i created for exchange 2010 has EXCHANGE10-UM as an Associated UM Server
    4. i ran the OCSUMUTIL program and created a new subscriber access for Exchange 2010 dial plan, extension 194

    this server is only running the EXCH 2010 UM role no other exchange services

    If i dial the pilot, 194, i get an error with reference to this link: http://office.microsoft.com/client/helppreview.aspx?AssetID=HA103556481033&ns=COMM2007R2&lcid=1033

    Friday, February 05, 2010 9:53 PM
  • Does your Front End server appears in "UM IP Gateways" tab?

    If not, you must run ExchUCUtil.ps1 script form EMS to associate the OCS server with this UM server (http://technet.microsoft.com/en-us/library/bb676409.aspx)


    Also, I think pilot numbers for SA and AA must be in E.164 format (or at least have "+" on front)

    Drago


    http://ocsdude.blogspot.com | MVP Snom OCS Edition
    Friday, February 05, 2010 11:36 PM
  • From our previous Exchange 2007 UM install, the Front End server shows up under IP Gateways tab.

    our last pilot number for exchange 2007 just has the 3 digit number


    i ran the trace and got 3 red lines... see below in the order they happen:

    i can send the etl file it created if it would help seeing the entire trace....


    27 ! 23:30:25.677.00007a88 In 33dcaf73efa34578ba316473493b4aec TL_INFO(TF_PROTOCOL) [1]0C44.0E70::02/05/2010-23:30:25.677.00007a88 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(122))$$begin_record
    Instance-Id: 00010105
    Direction: incoming
    Peer: EXCHANGE10-UM.Domain.local:5066
    Message-Type: response
    Start-Line: SIP/2.0 415 Unsupported Media Type
    From: "Jason Aday"<sip:jaday@integratedbt.com>;tag=09968a0b92;epid=d9f98e6e41
    To: <sip:jaday@integratedbt.com;opaque=app:voicemail>;tag=fe65be8875
    CSeq: 1 INVITE
    Call-ID: 33dcaf73efa34578ba316473493b4aec
    VIA: SIP/2.0/TLS 192.168.1.18:49285;branch=z9hG4bK2A51BFCB.E9E929629B17A721;branched=TRUE,SIP/2.0/TLS 192.168.1.106:50474;ms-received-port=50474;ms-received-cid=DE800
    CONTENT-LENGTH: 0
    SERVER: RTCC/3.1.0.0
    Message-Body: –
    $$end_record SIP/2.0 415 Unsupported Media Type jaday@integratedbt.com jaday@integratedbt.com;opaque=app:voicemail False True 262171 Microsoft.Rtc.Sip.Snooper.Message 0


    ---------------------------------

    43 ! 23:30:26.097.0000b91d In 33dcaf73efa34578ba316473493b4aec TL_INFO(TF_PROTOCOL) [1]0C44.201C::02/05/2010-23:30:26.097.0000b91d (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(122))$$begin_record
    Instance-Id: 00010114
    Direction: incoming
    Peer: EXCHANGE10-UM.Domain.local:5066
    Message-Type: response
    Start-Line: SIP/2.0 403 Forbidden
    From: "Jason Aday"<sip:jaday@integratedbt.com>;tag=09968a0b92;epid=d9f98e6e41
    To: <sip:jaday@integratedbt.com;opaque=app:voicemail>;tag=f93d7c1aa9
    CSeq: 1 INVITE
    Call-ID: 33dcaf73efa34578ba316473493b4aec
    VIA: SIP/2.0/TLS 192.168.1.18:49285;branch=z9hG4bK2A51BFCB.2427E1489B32F721;branched=TRUE,SIP/2.0/TLS 192.168.1.106:50474;ms-received-port=50474;ms-received-cid=DE800
    CONTENT-LENGTH: 0
    SERVER: RTCC/3.1.0.0
    Message-Body: –
    $$end_record SIP/2.0 403 Forbidden jaday@integratedbt.com jaday@integratedbt.com;opaque=app:voicemail False True 262187 Microsoft.Rtc.Sip.Snooper.Message 0

    ------------------------------
    47 ! 23:30:26.104.0000d15c Out 33dcaf73efa34578ba316473493b4aec TL_INFO(TF_PROTOCOL) [2]0C44.0A6C::02/05/2010-23:30:26.104.0000d15c (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(122))$$begin_record
    Instance-Id: 00010117
    Direction: outgoing;source="local"
    Peer: 192.168.1.106:50474
    Message-Type: response
    Start-Line: SIP/2.0 480 Temporarily Unavailable
    From: "Jason Aday"<sip:jaday@integratedbt.com>;tag=09968a0b92;epid=d9f98e6e41
    To: <sip:jaday@integratedbt.com;opaque=app:voicemail>;tag=B38F541481450C5E7C3F6CF5A720EE94
    CSeq: 1 INVITE
    Call-ID: 33dcaf73efa34578ba316473493b4aec
    Proxy-Authentication-Info: Kerberos rspauth="602306092A864886F71201020201011100FFFFFFFF997050671C44F790310CF19171C2D643", srand="B2C8D982", snum="154", opaque="E400F224", qop="auth", targetname="sip/OCS1.Domain.local", realm="SIP Communications Service"
    Content-Length: 0
    Via: SIP/2.0/TLS 192.168.1.106:50474;ms-received-port=50474;ms-received-cid=DE800
    ms-diagnostics: 13001;reason="The routing rules did not result in a suitable final response";source="OCS1.Domain.local";received="403";appName="InboundRouting"
    Server: InboundRouting/3.5.0.0
    Message-Body: –
    $$end_record SIP/2.0 480 Temporarily Unavailable jaday@integratedbt.com jaday@integratedbt.com;opaque=app:voicemail False True 262191 Microsoft.Rtc.Sip.Snooper.Message 0

    Friday, February 05, 2010 11:54 PM
  • you receive 403 Forbidden because: "SIP/2.0 415 Unsupported Media Type"

    Is your dial plan's VoIP Security parameter set to "Secured" (I assume it is, just to confirm...)

    Drago

    P.S. IM me if you want - dragomir at gmc.cc.ga.us

    http://ocsdude.blogspot.com | MVP Snom OCS Edition
    Saturday, February 06, 2010 12:34 AM
  • sent you an email
    Saturday, February 06, 2010 3:27 AM
  • Hi
    Any update for your issue?

    Regards!
    gavin
    Monday, February 08, 2010 3:36 AM
    Moderator
  • Gavin,
      Sorry for the late reply, i didnt get a notification about an update.

    With some direction from Drago i will able to work my way into the cause of the issues. The system mailbox and search mailbox was not working properly, so recreating them and re running setup /preparead fixed the issues.

    -Jason
    Thursday, February 18, 2010 10:58 PM
  • HI Jason,

    I am running into the exactly same issue when i tried OCS 2007 and Exchange 2010. My symptoms are exactly same as you have mentioned at the first place.

    However, i didn't doesn't understand completely how you fixed the issue. Could you please reply in detail.

    Thanks,
    Vijay

    Tuesday, March 29, 2011 10:52 PM