Sign in
Microsoft.com
 
Microsoft
 
 
 
Microsoft >
> 
> 
What is the *actual* network flow for federation with Live Meeting

Locked What is the *actual* network flow for federation with Live Meeting

  • Thursday, June 05, 2008 8:31 PM
     
     
    Sign In to Vote
    0

     

    Hello,

     

    We try to establish a federation between our company and a partner company

    Communicator federation works as expected for IM, presence and A/V calls. The network flow path for a p2p call is

    client A => edge A => edge B => client B

     

    But for Live Meeting it's another story. This network path doesn't work at all and the only workgin path is the same as anonymous LM path : direct connection between the remote federated client and our edge, (so short-circuiting federated edge), like that :

    client A ====> edge B => client B

    or

    client B ====> edge A => client A

     

    Isn't it a strange behavior ? is there a way to force LM traffic through both edge servers like for Communicator ?

     

    Any help would be greatly appreciated

     

    Thanks

     

    Matthieu

       

    All Replies

    • Thursday, June 05, 2008 10:10 PM
      Moderator
       
       
      Sign In to Vote
      0
      Do you have all the components of the Edge Server installed (Access Edge, Webconf, and A/V Auth?)

       

         
      • Friday, June 06, 2008 6:06 AM
         
         
        Sign In to Vote
        0

        Yes they are all installed and up and running. If not,  communicator federation with A/V wouldn't work. Remote access both sides works fine too for both LM and OC.

           
        • Thursday, December 17, 2009 2:18 PM
           
           
          Sign In to Vote
          0
          Did you ever find an answer or solution to this. As the company I'm currently working for is experiencing the same issue on OCS 2007 R2.