On Tue, Jul 14, 2009 at 5:07 PM, Tony Graziano<[email protected]> wrote: >>>> "Peter Fowler" <[email protected]> 07/14/09 4:38 PM >>> > Since Enterprise IM (EIM) is a growing segment, how do others solve this > problem? > > Do the OpenFire folks have a recommendation? > > Peter
> > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of M. > Ranganathan > Sent: Tuesday, July 14, 2009 2:53 PM > To: sipX developers > Subject: [sipX-dev] Openfire S2S federation : Deployment scenarios > > To support S2S federation we need to support the ability for other > servers to connect to our openfire server. > > Unlike sipx, openfire is not able to have domain aliases, thus making it > difficult to deploy behind a NAT + firewall. Bob Joly and I discussed > two possible solutions: > > In the case where openfire is deployed on a NATTed address, we would > need to utilize split-dns so that xmpp requests received by openfire can > be recognized as belonging to the openfire domain. > > The alternative would be to place openfire on a public address ( without > NAT/Firewall ). > > I will investigate if it is possible to add a plugin to support a > "domain alias" for openfire. > > Any comments? Any others approaches? > > Thanks > > **</[email protected]> > What if your IM is already built and hosted elsewhere? > Thats the point behind federation. You should be able to federate with that account. Federation works if you run openfire on a public IP address. The trick is to come up with a good solution for the case where openfire runs on a private address beihind a NAT + firewall. Some experimentation is needed. Ranga -- M. Ranganathan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
