locked
MOC and UM RRS feed

  • Question

  • I'm able to leave voice messages on a MOC-to-MOC call, and retrieve them in Outlook.  However, when I call the subscriber access number from the MOC, the call fails.  Are there any logs on OCS and Exchange that might help troubleshoot?

     

    Below is an excerpt from the OCS log:

     

    TL_INFO(TF_PROTOCOL) [0]09EC.1134::07/18/2007-14:06:39.676.00001167 (SIPStack,SIPAdminLog::WriteProtocolMessage:1228.idx(234))$$begin_record Instance-Id: 000006A2 Direction: outgoing;source="local" Peer: 135.8.19.107:3514 Message-Type: response Start-Line: SIP/2.0 403 Forbidden From: "Dilbert Engineer"<sipBig Smileilbert@sitlms.net>;tag=a8a07f96f7;epid=33c91bd32f To: <sip:+17328530000@sitlms.net;user=phone>;tag=968EE2EBF902B0A1B2B52374A1BFF226 CSeq: 1 INVITE Call-ID: 9c54df332de849638099693afc204c97 Authentication-Info: Kerberos rspauth="602306092A864886F71201020201011100FFFFFFFF13722D71A388D4090A1664660F3F82D3", srand="161C10B3", snum="18", opaque="3E8F46C5", qop="auth", targetname="sip/msocsee1.sitlms.net", realm="SIP Communications Service" Content-Length: 0 Via: SIP/2.0/TLS 135.8.19.107:3514;ms-received-port=3514;ms-received-cid=2B800 ms-diagnostics: 12004;reason="No route found";source="msocsee1.sitlms.net" Server: APP/OutboundRouting3.0.0.0 Message-Body: – $$end_record

     

    From the MOC, I'm trying to call the Exchange Server 2007 UM subscriber access number.  However, it looks like OCS is denying it with 403 Forbidden and there's also a "No route found" reason given.  On the other hand, I am able to divert to voicemail, i.e., an unanswered call from a MOC to another MOC is able to divert to UM and leave a message.

     

    What configuration in OCS and/or UM is needed to be able to route to the UM subscriber access number(s)?  How is that routing to the UM server works when diverting to voicemail, but not direct calling in?

     

    I also get the following in the Exchange server Event Viewer, but not sure it's related:

    Event Type: Warning
    Event Source: MSExchange Unified Messaging
    Event Category: UMService
    Event ID: 1088
    Date:  7/18/2007
    Time:  11:41:18 AM
    User:  N/A
    Computer: MSEXCHG1
    Description:
    The IP gateway or IP-PBX EEpool.sitlms.net did not respond to a SIP OPTIONS request from the Unified Messaging server. The error code that was returned is "0" and the error text is ":This operation has timed out.".

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     

    Tuesday, July 17, 2007 10:11 PM

Answers

  • I got it to work, and I think by normalizing the number in OCS and entering the E.164 in the Line URI of the User object corresponding to the UM dial plan.  What's confusing to me is that the UM instructions tell you to assign one or more extensions for dial in (for example, there is a UM global setting for extension length), but I still had to normalize to E.164 in OCS.

    Wednesday, August 15, 2007 1:22 PM

All replies

  • Can you use the route helper tool to verify your phone number normalization rules and the rest of your voice settings?

    Friday, July 27, 2007 6:42 PM
  • Can you let us know your status?

    Monday, August 13, 2007 6:24 PM
  • I got it to work, and I think by normalizing the number in OCS and entering the E.164 in the Line URI of the User object corresponding to the UM dial plan.  What's confusing to me is that the UM instructions tell you to assign one or more extensions for dial in (for example, there is a UM global setting for extension length), but I still had to normalize to E.164 in OCS.

    Wednesday, August 15, 2007 1:22 PM