locked
Stopped Receiving Audio Error - intermittent issues RRS feed

  • Question

  • We have external connectivity working with our OCS 2007 infrastructure.  A few remote users have requested an OCS phone so they can try out things.  Some have had success, but others are saying when they call they get the error that Communicator stopped receiving audio from the remote end.  I've tested this out on my end with a laptop connected to a broadband card while at work and I cannot duplicate it.  I suspect that the only difference would be that when I connect to the internet with my broadband card I am getting a public routable IP address.  When remote users are connecting, they are most likely going to be behind their router and NAT'd to a public IP. 

    I'm going to take my laptop home with me this weekend and try it out.  I suspect I should have the same problem as them since I have a private network at home. 

    Has anyone come across this before and know of any resolutions to this issue that we can tell our employees to try (short of bypass their router and connect directly to the internet)?  I'm thinking it has to be on their end as I can successfully call, transfer, and forward calls when I have my test laptop set up with external access.

    Thanks..... 
    Friday, February 13, 2009 10:31 PM

All replies

  • Did you also configure your A/V EDGE Server? (required if you want to do Audio from the internet)
    Can be collocated on the Access & Web Conferencing EDGE!
    - Belgian Exchange Community : http://www.pro-exchange.be -
    Monday, February 16, 2009 11:37 PM
  • Hi,
    Make sure you have AV Edge server and Public Ip for AV edge interface if you have OCS 2007. In OCS 2007 R2 you dont need public IP but it should be cnsolidated Edge. After having the Public Ip for AV edge if you still receive error then take a look at your remote client UCCP log by snooper tool and filter it by a=candidates and see what Ip address you are receiving form the internal client. You should have Internal Client's Mechine Ip and Public Ip of Edge server. If you are not seeing Public Ip of the edge then this will be most likey routing issue.

    Hope this helps.
    Jithendranath Reddy
    Monday, February 16, 2009 11:51 PM
  • I think I might have fixed it.  A few people are testing now (but I confirmed that I was having the problem at home and now I'm not).  I added a static route from our mediation server to our A/V Edge server and that seemed to resolve it.

    We're hoping to move to OCS R2 soon as the public IP for the A/V Edge was a pain to have to deal with in our situation.

    Thanks!
    Wednesday, February 18, 2009 4:13 PM
  • A Static route may work but that is certainly not the intended configuration
    You should read the EDGE deployment guide: At the end you will find a section on how to connect your EDGE server with the OCS Pool
    You must rerun the configure pool wizard and configure the EDGE Server connections
    - Belgian Exchange Community : http://www.pro-exchange.be -
    Wednesday, February 18, 2009 5:23 PM
  • Deli Pro-Exchange said:

    A Static route may work but that is certainly not the intended configuration
    You should read the EDGE deployment guide: At the end you will find a section on how to connect your EDGE server with the OCS Pool
    You must rerun the configure pool wizard and configure the EDGE Server connections


    - Belgian Exchange Community : http://www.pro-exchange.be -



    Thanks - I'll take a look at that.  When I set this up it was right after OCS was released and I had a hard time finding decent documentation so I might not have set things up correctly (thankfully, most everything is working though).
    Wednesday, February 18, 2009 6:44 PM
  • Here you can find the EDGE server deployment guide
    http://www.microsoft.com/downloadS/details.aspx?familyid=ED45B74E-00C4-40D2-ABEE-216CE50F5AD2&displaylang=en

    Go to step 4.4 for details
    Step 4.4. Connect Your Internal Servers with Your Edge Servers

    - Belgian Exchange Community : http://www.pro-exchange.be -
    Wednesday, February 18, 2009 8:01 PM