> -----Original Message----- > From: [email protected] [mailto:sipx-dev- > [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? >
Since openfire can run on its own "server" the public address piece wouldn't be too ominous. That said I am not sure without IP tables and SELinux we would want to expose a sipXecs box.. would we? > Thanks > > -- > 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/ _______________________________________________ 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/
