none
OCS 2007 R2 audio and video conference timeout

    Question

  • Hi everybody

    I'm running OCS 2007 R2 on a Windows 2008 SP1 server in a Windows 2008 R2 domain. Everything works ok except when I try to make a three-party audio-video conference - the conference just times out.

    Scenario 1:
    We have a three person IM session going. I decide to add voice and video and get the "Connection to server..." status. After a while I get connection terminated.

    From the logs (DBanalyze etc), I can see that the conference is being created, but after I send the INVITE for the conf:audio-video session, nothing happens for about a minute or so - and then the conference times out.

    I get event id 11 on my PC, with this text:
    A SIP request made by Communicator failed in an unexpected manner (status code 80ee000c). More information is contained in the following technical data:
    RequestUri: sip:agl@mydomain.com;gruu;opaque=app:conf:audio-video:id:B2D99B42C7AA4949A04FD1C38B20E0B6 From: sip:agl@mydomain.com;tag=eff9b80201
    To: sip:agl@mydomain.com;gruu;opaque=app:conf:audio-video:id:B2D99B42C7AA4949A04FD1C38B20E0B6;tag=(null)
    Call-ID: c5e04147f3d84e4e8c454f3113b0d949
    Content-type: application/sdp;call-type=audiovideo
    (null)
    Response Data:
    2163081228 (null)

    I have no idea what that means.

    Our certificate is fine, at least it seems so. All validation wizards pass without problems.

    Scenario two:
    I click the Meet Now butten in Outlook, to create a Live Meeting. When I then click tha Audio and Video menu to get my gear connected to the conference, same thing happens - timeout. This time there's no event created.

    I can't find anything in the A/V MCU log, did a wireshark trace on my own PC - similar result as above, no responce after the INVITE to conf:audio-video.

    I have a anonymized screenshot I could share...

    Any suggestions would be welcome. Meanwhile, I'll make some more attempts to get something going in the A/V MCU log...

    Best regards
    Allan

    • Edited by Allan Glargaard Friday, May 07, 2010 9:17 PM Reformatted for readability
    • Moved by Ben-Shun Zhu Tuesday, May 11, 2010 8:36 AM cross posting (From:Planning and Deployment)
    Friday, May 07, 2010 10:40 AM

Answers

  • Although we already installed several of the individual hotfixes from the april cumulative update KB968802, installing the remaining package seems to have fixed the problem.

    Which of the missing 4 to 5 fixes really solved it, we will never know.

    Meet now audio-video conference is working as well as a three-person IM chat raised to a fullblown audio-video conference, hooorrrraaaayyyy !!!

    Best regards
    Allan

    Tuesday, May 11, 2010 5:19 PM

All replies

  • I forgot to mention that this is an internal deployment only, ie. no edge server involved. Just a Front End server and a Archiving/Monitor server - and of course an SQL server for the databases.

    Could someone post a log from a successfull raise of a three-person internal IM chat to a audio/video conference? I might be able to spot what I'm missing then.

    My wireshark log is like this (I cut the most of the chat conference part, as that is working:
    145.139407  SIP/XML  Request: INFO sip:x@somedomain.com;gruu;opaque=app:conf:chat:id:60EF1685....
    145.156404  SIP         Status: 202 Accepted
    149.520664  SIP/SDP  Request: INVITE sip:x@somedomain.com;gruu;opaque=app:conf:audio-video:id:60EF1685....
    149.542852  SIP        Status: 100 Trying
    149.564835  SIP/XML  Request: INFO sip:x@somedomain.com;gruu;opaque=app:conf:chat:id:60EF1685....
    149.582077  SIP        Status: 202 Accepted
    269.550277  SIP        Continuation
    314.537932  SIP        Request: CANCEL sip:x@somedomain.com;gruu;opaque=app:conf:audio-video:id:60EF1685....
    314.551612  SIP        Status: 200 OK
    314.563842  SIP        Status: 487 Request terminated

    Notice the time delay on the SIP Continuation record and again before the SIP Cancel is sent.

    I don't think I ever get a responce on the SIP/SDP Invite?

    In OCSlogger, I've turned on trace on all MCU related stuff, but when I analyse the log, there is nothing from the A/V MCU - as far as I can tell.

    What happens to my INVITE for the audio-video conference - any ideas?

    Best regards,
    Allan

    Saturday, May 08, 2010 7:59 AM
  • You say you are running in a Win2008R2 domain there are 3 party conferencing issues with R2 unless you went through the following processes:

    http://support.microsoft.com/kb/982020/

    http://support.microsoft.com/kb/982021/


    Chris Clark - | MCTS:OCS & UC Voice Specialization | MCSE | MCSA | CCNA
    Sunday, May 09, 2010 7:58 PM
  • Hi Chris

    The forest/domain was already upgraded to Windows 2008 R2 before we did the forest and domain prep, so KB982020 does not apply. But I will double check the forest prep tomorrow of course.

    As for the member server, it is running Windows 2008 SP1 - so the KB982021 does not apply to our scenario, I think.

    This is really puzzling - or possibly quite simple when I find out what is causing it.

    Will also double check the certificate tomorrow - see if it is RSA128-something and enabled for all purposes. Checked it once, but twice is always better...

    Keep the good ideas rolling, please...

    Best regards
    Allan

    Sunday, May 09, 2010 8:25 PM
  • I finally managed to get something useful out of OCSlogger by moving the logfile to my client PC and opening it with Snooper.

    It turns out there is a diagnostic message right after the conference is terminated. This is the scenario where a three person IM chat is raised to a audio-video conference, the diagnostics read:

    TL_WARN(TF_DIAG) [3]0B38.1C14::05/10/2010-10:13:55.239.001267b0 (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(142))$$begin_record
    LogType: diagnostic
    Severity: warning
    Text: Message or one of its headers caused SIP transaction processing error
    Result-Code: 0xc3e93c5c SIPPROXY_E_INVALID_TRANSACTION_STATE
    SIP-Start-Line: SIP/2.0 200 OK
    SIP-Call-ID: cbfbaa0b2caf4c0098ec57e453b97496
    SIP-CSeq: 1 CANCEL
    $$end_record

    You can see a snapshot of the snooper trace here:

    http://i41.tinypic.com/9u6o3t.jpg

    The complete log file is 62MB so probably too big to share :-)

    Although I now verified that a AVMCU session is actually created, I'm still totally puzzled as to why the session terminates before tha audio-video conference starts.

    Any ideas are most welcome.

    Best regards,
    Allan

    Monday, May 10, 2010 12:28 PM
  • Although we already installed several of the individual hotfixes from the april cumulative update KB968802, installing the remaining package seems to have fixed the problem.

    Which of the missing 4 to 5 fixes really solved it, we will never know.

    Meet now audio-video conference is working as well as a three-person IM chat raised to a fullblown audio-video conference, hooorrrraaaayyyy !!!

    Best regards
    Allan

    Tuesday, May 11, 2010 5:19 PM