locked
Communicator Voice Behing NAT? RRS feed

  • Question

  • I am not able to establish voice calls with Communicator when behind a NAT router.  For example, when I am at home behind a typical home NAT router, I can IM with people in our office but am not able to establish voice conversations with them.  I can, however, establish a voice conversation with another machine in my home.

     

    For voice conversations, does Communicator need to be able to establish TCP/TLS connections director to the other party's Communicator instance?  In other words, is Communicator listening for connection requests when a voice call is started?  I can see where that would not work if you are behind a NAT router...but that seems like a big limitation if it's the case...

     

    jon

    Friday, February 8, 2008 4:02 AM

All replies

  •  

    I dont know about your Voice setup.. but OCS Audio/Video edge service doesn't work when it is confiured with the NATED IP Address. There should not be NATING between the client and the Voice server.

     

     

     

     

    Ram K Ojha
    MCSE 2003 - Messaging, MCTS- (LCS 2005 & OCS 2007)
    http://www.OCSPedia.com
    http://www.ITCentrics.com
    Friday, February 8, 2008 8:12 PM
  • Hi Ram,

    You definitely can't use a NAT'd IP address for the A/V server. I tried many different ways & could never get it all working exactly right:

    https://blogs.pointbridge.com/Blogs/mcgillen_matt/Pages/Post.aspx?_ID=10

     

    OCS uses STUN for voice calls made by communicator clients outside your firewall. the STUN RFC calls out that either the client or the server must have a publicly routeable IP address, but if both are NAT'd you'll get wacky results.

     

    Regards,

    Matt

     

    Wednesday, February 13, 2008 4:49 AM