locked
External A/V Connections cannot be established. RRS feed

  • Question

  • Hi,

    I read about this issue several times here in this forum.
    But I still couldn't fix my problem.

    Here is what I have:

    1 internal OCS Enterprise Edition Server
    1 Edge Server (consolidated)
    Publically Routable IP Adresses for all 3 roles (NO NAT on external Firewall)

    IM and external Connections work like a charm.

    When I make a Communicator Call from User A (inside) to User B (outside) the call gets dropped.
    Because the Session wants to connect to the private (NATed) IP of User B.

    How can I fix this?
    Why does OCS not address the public IP of USER B?

    I think the Edge Server does not recognize that USER B is in another net and does not establish the connection through the A/V Edge Server....


    Thanks

    Monday, September 21, 2009 10:22 AM

Answers

  • Configuration was OK.
    Today I found the "Limited External Calling" sign in Communicator and after some google research i found my error.
    RTCproxyService's localization was set to GERMANY after applying EN-EN connection to A/V Edge succeeded.

    I should have installed the Updates before configuring.

    Thanks anyway.

    • Marked as answer by g3ocs Tuesday, September 22, 2009 8:21 AM
    Tuesday, September 22, 2009 8:21 AM

All replies

  • Do your internal workstations have the ability to resolve via DNS the Edge Interface Interface FQDN and can they connect to it over both 443 and 3478?  Media sessions between clients will first attempt a peer-to-peer connection (which would fail) and then should fall-back to trying via Edge.  If the internal client does not even make an attempt to contact the Internal Edge interface (you can validate this by capturing traffic on internal client) then you may not have the Edge server completely configured in the Global and Pool properties in OCS.
    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Monday, September 21, 2009 12:35 PM
    Moderator
  • hi jeff,

    the internal interface FQDN is resolvable by the internal workstations.
    ports 443 and 3478 are open, though there haven't been any traffic on port 3478, i checked that with the firewall administrator.

    it seems that there is no fall back happening, since the clients still try p2p connections.

    i configured the following:
    Global Properties:
    Edge Servers Tab:
    Access Edge
    internal FQDN

    A/V Edge:
    internal FQDN 5062

    pool properties:
    media
    A/V Authentication Service:
    internal FQDN:5062
    support encryption

    web conferencing properties:
    internal: Edge internal FQDN
    external: Edge Webconf external FQDN
    external port 443
    internal port 8057

    I don't think i missed someting here, did I ?

    This is driving me crazy ....


    Monday, September 21, 2009 12:54 PM
  • Configuration was OK.
    Today I found the "Limited External Calling" sign in Communicator and after some google research i found my error.
    RTCproxyService's localization was set to GERMANY after applying EN-EN connection to A/V Edge succeeded.

    I should have installed the Updates before configuring.

    Thanks anyway.

    • Marked as answer by g3ocs Tuesday, September 22, 2009 8:21 AM
    Tuesday, September 22, 2009 8:21 AM