locked
OCS 2007 R2 Not showing video with Live Meeting Client RRS feed

  • Question

  • Hello

    I am hoping that someone can help me.
    I have OCS 2007 R2 installed on Win Serv 2008 R2 X64 with SQL Server 2008.

    I am unable to get the MS Live Meeting Client to show any video, but the communicator client can. I am only using the services inside my network.
    The server was working as it should until yesterday and I cannot figure out what has changed. I do not get any event logs on the server but here is the log from a workstation trying to use video.

     A SIP request made by LiveMeeting failed in an unexpected manner (status code 80ef01f8). More information is contained in the following technical data:

     

     RequestUri:   sip:myuser@fqdn;gruu;opaque=app:conf:audio-video:id:04ca9f15e21745e681220fa71428e807

    From:         sip:myuser@fqdn;tag=55f222c772

    To:           sip:myuser@fqdn;gruu;opaque=app:conf:audio-video:id:04ca9f15e21745e681220fa71428e807;tag=7092A1BC9FA81A423AD637AB3A57D5F8

    Call-ID:      8461f495927640cdb1bd1667b61e0f7b

    Content-type: application/sdp;call-type=audiovideo

     

    v=0

    o=- 0 0 IN IP4 10.64.32.12

    s=session

    c=IN IP4 10.64.32.12

    b=CT:99980

    t=0 0

    m=video 13042 RTP/AVP 121 34

    k=base64:Qq8mo4X9NaDdH+IZ69cjyY979DEyEMs4SSN2ubOKdn2K+LxxHU141ehwlWqY

    a=candidate:RsvQsoga86ILskBWz8d5QBO/cJRyRpD04/6a92pTnR8 1 ZPlnHe+OIgYxHs11P/AX4A UDP 0.830 10.64.32.12 13042

    a=candidate:RsvQsoga86ILskBWz8d5QBO/cJRyRpD04/6a92pTnR8 2 ZPlnHe+OIgYxHs11P/AX4A UDP 0.830 10.64.32.12 2582

    a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80 inline:+wSVmF/z5H18b+jWmDLxKgY2N9rAy4vj89RGkTt8|2^31|1:1

    a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:aFWR4qs6E6udySgsyqHeteRRxhrWvXNWjWC8j/IV|2^31|1:1

    a=maxptime:200

    a=rtcp:2582

    a=recvonly

    a=rtpmap:121 x-rtvc1/90000

    a=rtpmap:34 H263/90000

    a=encryption:optional

     

     

    Response Data:

     

    504  Server time-out

    ms-diagnostics:  1007;reason="Temporarily cannot route";source="servername.fqdn";ErrorType="Failure reading or writing data on connection";WinsockFailureDescription="This machine closed the connection due to transmission timeout or other protocol error";WinsockFailureCode="10053(WSAECONNABORTED)";Peer=" servername.fqdn"

     

     

     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.

     

     

    Wednesday, September 23, 2009 6:01 PM

Answers

  • I don't know if this is the problem but OCS don't support Window 2008 R2. I saw the most different issues caused by Windows 2008 R2.
    Bruno Estrozi - MCSE +S +M/MCTS/MCITP - Unified Communications Specialist | http://brunoestrozi.com.br
    Wednesday, September 23, 2009 10:20 PM