locked
OCS2007R1 Unable to Multiparty IM RRS feed

  • Question

  • Environment:
    Front-End and Mediation servers are Windows Server 2003 R2 x64
    SQL 2005 SP2
    Cisco Call Manager 7.x
    Cisco Unified Presence Server  (Provides integration between OCS and Call Manager)
    Currently external conferencing is not enabled, nor public IM, or PSTN calling
    Communicator 2007 build: 2.0.6362.129
    OCS 2007 Server build: 3.0.6362.0

    When users attempt to invite a 3rd participant to an IM chat, they receive a ID 408 error.  The event logs on the client show this:

    Event Type: Warning
    Event Source: Communicator
    Event Category: None
    Event ID: 11
    Date:  6/5/2009
    Time:  2:30:22 PM
    User:  N/A
    Computer: OCS 2007 R1 server
    Description:
    A SIP request made by Communicator failed in an unexpected manner (status code 80ef0198). More information is contained in the following technical data:
     
     RequestUri:   sip:user1@sip.domain;gruu;opaque=app:conf:chat:id:2E725E75684637439DD51629BDACECB8
    From:         sip:user1@sip.domain;tag=4d60a05e21
    To:           sip:user1@sip.domain;gruu;opaque=app:conf:chat:id:2E725E75684637439DD51629BDACECB8;tag=1d5d41f1-19c44ffe
    Call-ID:      f4a98bac8e33441089032b73f5ffe939
    Content-type: application/sdp;call-type=im

    v=0
    o=- 0 0 IN IP4 172.20.5.32
    s=session
    c=IN IP4 172.20.5.32
    t=0 0
    m=message 5060 sip null
    a=accept-types:text/rtf application/x-ms-ink image/gif multipart/alternative application/ms-imdn+xml


    Response Data:

    408  Request Timeout
    ms-diagnostics:  1011;reason="Ms-Diagnostics header not provided by previous hop";source="OCS Server.FQDN";Domain="domain.local";PeerServer="10.20.1.4"

     
     Resolution:
     If this error continues to occur, please contact your network administrator. The network administrator can use a tool like winerror.exe from the Windows Resource Kit or lcserror.exe from the Office Communications Server Resource Kit in order to interpret any error codes listed above.

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

    On the front end server, the IM Conferencing IP Address is set to: All, port 5062.

    The certificate is set to "Enable all purposes for this certificate."  (Only one is in use, issued by an internal CA).

    Trace logging shows the following errors from the server:

    TL_WARN(TF_COMPONENT) [1]0AC0.063C::06/04/2009-16:39:16.866.000000ba (ImMcu,ConferenceManager.AddToConferenceTable:119.idx(530))( 02EC2D49 )confUri sip:user1@sip.domain;gruu;opaque=app:conf:focus:id:20AF4C5444689A4393D192213FF7BD8E already present in hash table
    TL_WARN(TF_COMPONENT) [1]0E2C.0E44::06/05/2009-15:35:50.596.0000059c (SIPStack,ListenPortConfig::GetListeningPort:1085.idx(1841))( 001A0740 ) No socket configured to listen for SIP_TRANSPORT_TCP at [172.020.005.032:3994]
    TL_WARN(TF_COMPONENT) [1]0E2C.0E44::06/05/2009-12:03:17.758.00000439 (SIPStack,ListenPortConfig::GetListeningPort:1085.idx(1841))( 001A0740 ) No socket configured to listen for SIP_TRANSPORT_TCP at [172.020.005.032:3994]
    TL_ERROR(TF_COMPONENT) [1]0E2C.0C2C::06/05/2009-12:03:52.510.0000043a (SIPStack,CRecvContext::ProcessCompletion:974.idx(147))( 03E67C98 ) Receive failed
    TL_ERROR(TF_CONNECTION) [1]0E2C.0C2C::06/05/2009-12:03:52.510.0000043b (SIPStack,SIPAdminLog::TraceConnectionRecord:1224.idx(157))$$begin_record
    LogType: connection
    Severity: error
    Text: Receive operation on the connection failed
    Local-IP: 172.20.5.32:5061
    Peer-IP: 172.20.4.129:1228
    Connection-ID: 0x1800
    Transport: TLS
    Result-Code: 0x80072746 WSAECONNRESET
    User-Uri:
    user2@sip.domain
    $$end_record

    It seems to boil down to one of the following, there is a missing DNS SRV record for the IM Conferencing service, but I do not see any reference in the documentation.

    The server is unable to create a socket for the IM Conference.

    Or there is a component to the IM Conferencing service that is not listening on TCP/5062 that should be, but I can not find any errors, or failed services.

    I have tried telneting to the server on the 5062 port, and there is no response.

    Validation and Best Practice scans do not reveal anything that is not configured, i.e., we are not using external conferencing, and the routing plans/normalization patterns must match Cisco Call manager.

    Thanks in advance for any help!


    Thanks! -Josh
    Friday, June 5, 2009 7:01 PM

All replies

  • Can anyone provide detailed steps in how the multiparty conferencing works?  I know that when more than two participants are involved, it is no longer an ad hoc conference, and the server takes over, but what services, functions are required?

    I'm just looking for a different means of troubleshooting as the standard set si not working?
    Thanks! -Josh
    Monday, June 8, 2009 12:39 PM
  • Hello? Anyone? Bueller?


    Thanks! -Josh
    Tuesday, June 9, 2009 1:44 PM