Cannot complete Video Conference RRS feed

  • Question

  • Having trouble completing a conference.


    Get the following error when inviting 3<sup>rd</sup> party.


    Cannot perform the selected action. This action may not be permitted by the conferencing service. Please try again. If the problem persists, please contact your system administrator.


    Event Viewer has the following message.


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


     RequestUri:   sip:tim.gaither@astoundtech.demo2;gruu;opaque=app:conf:audio-video:id:FC6A2AA2812A054F8184C4676B13CE3C

    From:         sip:tim.gaither@astoundtech.demo2;tag=57a07e7b7f

    To:           sip:tim.gaither@astoundtech.demo2;gruu;opaque=app:conf:audio-video:id:FC6A2AA2812A054F8184C4676B13CE3C;tag=810022A52E177F8D3BB5FADE9A8C62D7

    Call-ID:      6162eeeb2105468a8200bdd68ebc0dc8

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




    Response Data:


    504  Server time-out

    ms-diagnostics:  1007;reason="Temporarily cannot route";source="OCSDemo2.AstoundTech.Demo2";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="ocsdemo2.astoundtech.demo2"




     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.


    The message appears as if I am inviting myself to a conference even though I selected a contact from the list. There is no mention of the invited person’s name in the communicator log.

    Any thoughts as to what’s causing the problem.

    Wednesday, March 17, 2010 10:20 PM

All replies

  • The first thing to check is that your conferencing services are running and that you can successfully restart them.  Also make sure there are no firewall and/or port filtering applications running on the system.
    Mike Stacy |
    Wednesday, March 17, 2010 11:10 PM