Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
external Live Meeting failes RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi!

    We have deployed OCS 2007 R2. The Edge Server has 4 NICs - 3 outside (NAT) an 1 inside. NAT option is enabled on the A/V interface.


    I can Login with my MOC from the Internet, but my Live Meeting can not join any session or create one.

    Tested:
    The Connection test of the LiveMeeting Client runs successful.
    Telnet on 443 sip.domain.com works
    Validation of the Edge Server is Successful (2Party test not set)
    Web Conferencing Validation on the FE is Successful


    Has anyone an idea why i can not join meetings ?

    thanks
    Markus
    Monday, May 18, 2009 12:02 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Have you published an external DNS record for the Web Conferenceing Edge external IP address (e.g. webconf.domain.com)?  This DNS record is passed in-band to the external clients, but they still need to be able to resolve that name to the IP address in order to connect to Live Meeting sessions.

    Also, check the Application event log on the external client as there should be a warning or error from Live Meeting explaining the specific connection issue.

    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Monday, May 18, 2009 12:07 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Jeff,


    the external DNS is pulished

    The application event log tells nothing:

    Only entry

    "LiveMeeting has enabled event logging.

    Information about failed calls will be sent to the Windows event log."

    Monday, May 18, 2009 12:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Do you have a certificate assigned to the Web Conferencing Edge service that matches the external FQDN and the client trusts?

    Might also check your link between the FE and your Edge's private NIC to verify port 8057 is open between those two servers.
    Wednesday, May 20, 2009 8:53 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Tom,

    the certificate is assigned, valid and trusted by the Client.
    I have also created a new one and assigned it manually to be sure

    telnet between FE and Edge on port 8057 works

    Friday, May 22, 2009 8:29 AM