Video call gets disconnected using communicator over the Internet RRS feed

  • Question


    Hi All.

    I am using OCS 2007 Server in my facility. I  am facing issues while initiating a  video call to any user in my organization  over the Internet. I can initiate a video call  but as soon as the connection is made, it disconnects. The IM Works fine. I can initiate the video between the users within the LAN it works perfect, However on initiating it from outside my organization using Office 2007 communicator the Video call gets disconnected.

    Below is the brief of my OCS Setup.

    ·         One OCS 2007 Standard edition IM Server.

    ·         One OCS 2007 Edge Server. The edge server has three NIC,S.One for the internal interface. One NIC directly routed to the router with External Static public IP Address bypassing the Hardware firewall. One NIC for Web conferencing and remote access. All the three NIC,S have certificates imported from the Windows enterprise CA with the respective edge server roles.

    ·         Windows 2003 enterprise CA for certificate services.

    ·         ISA 2006 as reverse proxy.


    Has anyone faced this kind of issues. I have enabled the communicator logging which gives the following Warning in the application log:


    Event Type:        Warning

    Event Source:    Communicator

    Event Category:                None

    Event ID:              11

    Date:                     10/21/2008

    Time:                     10:33:13 AM

    User:                     N/A

    Computer:          Test


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


     RequestUri:   sip:access.test.com:5061;transport=tls;lr;ms-route-sig=bbGKMCt1ffCwQgBOWPn4E_IesAB4yCY5FgqawD3QAA

    From:         sip:user1@test.com;tag=4f840b3c95

    To:           sip:uesr2@test.com;tag=eaaf5c2b54

    Call-ID:      522839882df44fceaae2e05e48d6cebe

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



    o=- 0 0 IN IP4


    c=IN IP4


    t=0 0

    m=audio 16640 RTP/AVP 114 111 112 115 116 4 8 0 97 101


    a=candidate:F9GQaaXZcUdfTso5+f0GVs9cWvNpLGKPbuPhVrY1BPg 1 x10lMWO1J0ra07kZcvnYtw UDP 0.900 16640

    a=candidate:F9GQaaXZcUdfTso5+f0GVs9cWvNpLGKPbuPhVrY1BPg 2 x10lMWO1J0ra07kZcvnYtw UDP 0.900 59904

    a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80 inlineBig SmileihZFuvjZmP0Y9aMxn3C3w8YAKwG+DISmfMAKKKm|2^31|1:1

    a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:KiYizsqZRQobED7Gy31eXZ8fhfxnzJDGCSwWX4Vl|2^31|1:1



    a=rtpmap:114 x-msrta/16000

    a=fmtp:114 bitrate=29000

    a=rtpmap:111 SIREN/16000

    a=fmtp:111 bitrate=16000

    a=rtpmap:112 G7221/16000

    a=fmtp:112 bitrate=24000

    a=rtpmap:115 x-msrta/8000

    a=fmtp:115 bitrate=11800

    a=rtpmap:116 AAL2-G726-32/8000

    a=rtpmap:4 G723/8000

    a=rtpmap:8 PCMA/8000

    a=rtpmap:0 PCMU/8000

    a=rtpmap:97 RED/8000

    a=rtpmap:101 telephone-event/8000

    a=fmtp:101 0-16




    Response Data:


    183  Session Progress

    101  Progress Report

    ms-diagnostics:  13004;reason="Request was proxied to one or more registered endpoints";source="server15.abraaj.com";appName="InboundRouting"

    180  Ringing

    0  (null)

    Ms-client-diagnostics:  52031; reason="Call terminated on media connectivity failure"


     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.


    Would appreciate your feedback.

    Tuesday, October 21, 2008 7:47 AM

All replies

  • It looks like a routing issue of your audio/video streams towards external users. How have you configured your gateway settings on the internal and external interfaces of your Edge servers?


    Have you configured your audio/video Edge server on the OCS frontend (mmc console)?


    * On forest level: Select global properties and the tab named Edge servers: check if you have filled up the FQDN of the A/v Edge server and the correct port

    * Check if you can connect to your a/v edge server by pinging it from your OCS frontend server.

    * On pool level: Check your A/V conferencing settings by opening the properties of your A/V conferencing server 




    Tuesday, October 21, 2008 8:21 AM
  • Use the EDGE Planning tool to check settings like DNS, Certificates, Firewall rules...




    Wednesday, October 22, 2008 11:42 AM