Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Strange Audio/Video routing behaviour - Is static routing a solution? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Connecting via our internal and external OCS pool we are able to log on using communicator and make voip/video calls with other users. Live Meeting also works fine when it comes to signing on and sharing content.

     

    But there are two things that doesn't work connecting via the external pool (Edge server)..

    • We have problems to receive voicemail audio using communicator
    • In Live Meeting we can not get video/audio

    Communicator can call the voicemail system but then there is no audio coming back through the line. The same for Live Meeting: via Edge (external pool) we are able to log on but are not receiving any Audio/ Video.

     

    The message we get in Live Meeting is:

     

    ""Your request to add/remove a media failed.

     

    Action required: Please try your action again. If that doesn't work, set up audio and video from the Options menu.

     

    ---------------------------------------------------------------------------

    More details for technical support:

    ---------------------------------------------------------------------------

    Message Category: 5 (kOperationFailure)

    Message Code: 2 (kReinviteFailed)

    Root Cause Error: 0x80EF01F4

    Root Cause Component: kAVMCU

    Audio Input Device: Microphone (2- Microsoft® LifeCam NX-6000)

    Audio Output Device: Speakers (SoundMAX Integrated Digital HD Audio)

    Video Input Device: Microsoft® LifeCam NX-6000

    Audio Muted: Yes

    Media State: (47,10,10,10,12,0,Reinviting)

    AvMcu Uri: sip<INTERNAL OCS POOL>:5063;transport=tls

    Avmcu Reachable: Yes

    Acp Reachable: No

    Diagnostics Information:

    ---------------------------------------------------------------------------

    To copy this message, press CTRL+C or press ALT+PRINT SCREEN.
    ---------------------------
    OK  
    --------------------------- ""


    Doing some tracing on our ISA firewall I found out that Voice Mail Audio is routed directly to the external client from the Exchange UM Server and the internal OCS pool. Not via the external pool (Edge server)!

     

    Exchange is routing audio traffic via our IP gateway back to the client. It is trying to reach the client based on the local IP adres which is not accessible when it is behind a router.

     

    When I was connecting my laptop directly to my cable modem (and getting a public IP adres) voicemail works. I also get audio/video in Live Meeting.

     

    Has anyone else experienced this? Adding the EDGE IP in the static routing settings (of the frontend properties) causes the OCS frontend not to start.

     

    How to solve this AV routing issue?


    Thomas

    Thursday, October 25, 2007 7:08 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Thomas,

    Until I added the publicly routeable IP address on the A/V Edge service, I had these exact same problems. If you have the A/V edge server with the correct public IP, then all the traffic will try to route peer-to-peer.

     

    I had absolutely everything working except for livemeeting audio etc. I think it has to do with STUN (simple traversal of UDP through NAT). Having the edge and your client both being NAT'ed is likely the source of the issue.

     

    I couldn't believe that changing to the public IP for A/V edge fixed it all. I still am not totally sold on why it has to operate like that, but it definitely works.

     

    Matt

     

    Thursday, October 25, 2007 7:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    My question is, why has microsoft not implemented the same traversing mechanisms in Ex UM, like in the Mediation Server? Outbound calling via Edge and Mediation works perfectly !!
    Thursday, November 1, 2007 5:32 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    ...and in what scenario would we use static routing in OCS?

     

    Saturday, November 3, 2007 8:33 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    hello...
    I've got same error, but my situation is different from your.

    I have only one standard OCS in basic intrasite role for IM and audio/video conferencing. no edge role, no external access.

    my deploy seems very simple config without edge servers but  error is same like your.  

    Do you have any advice for my please ?

    I'm only beginer in ocs so now I have headache.

    Thank for any advice.

    my error :


    ---------------------------
    Voice and Video Error Information
    ---------------------------
    Your request to add/remove a media failed.

     

    Action required: Please try your action again. If that doesn't work, set up audio and video from the Options menu.

     

    ---------------------------------------------------------------------------

    More details for technical support:

    ---------------------------------------------------------------------------

    Message Category: 5 (kOperationFailure)

    Message Code: 2 (kReinviteFailed)

    Root Cause Error: 0x80EF0194

    Root Cause Component: kAVMCU

    Audio Input Device: Logitech Mic (Orbit/Sphere MP)

    Audio Output Device: SoundMAX Digital Audio

    Video Input Device: QuickCam Orbit/Sphere MP

    Audio Muted: Yes

    Media State: (47,2,2,2,0,0,Reinviting)

    AvMcu Uri: sip:vmocs2007.softec.sk:5063;transport=tls

    Avmcu Reachable: Yes

    Acp Reachable: No

    Diagnostics Information:

    ---------------------------------------------------------------------------

    To copy this message, press CTRL+C or press ALT+PRINT SCREEN.
    <!--[if !supportLineBreakNewLine]-->
    <!--[endif]-->
    Thursday, January 10, 2008 4:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    My live meeting video sessions are also trying to connect to the internal fqdn of the OCS server. Where on the ocs or edge servers should I change it to point to the external fqdn/ip of the edge?

    Friday, February 29, 2008 3:58 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello 

      Keep in mind this. Some firewalls doesn´t support STUN protocol, which is used with OCS. For example, Checkpoint FW-1 doesnt´t support it. We have it implemented with cisco pix and it works.

     

    Solution ID: sk34538  
       
    Supporting STUN server
     
    Product: VPN-1 Power/UTM
    Version: NG AI R55, NGX R60, NGX R62, NGX R65
    Last Modified: 03-feb-2009
    Print this Solution
    Email this Solution
    Back to Results List
              Solution         The STUN (Simple Traversal of User Datagram Protocol [UDP] Through Network Address Translators [NATs]) server allows NAT clients to setup phone calls to a VoIP provider hosted outside of the local network. The STUN server allows clients to find out their public address, the type of NAT they are behind and the internet side port associated by the NAT with a particular local port. This information is used to set up UDP communication between the client and the VoIP provider and so establish a call. The STUN protocol is defined in RFC 3489.

    Check Point does not support STUN server.

    Wednesday, May 13, 2009 8:12 AM