On Tue, Jul 14, 2009 at 3:13 PM, Scott Lawrence<[email protected]> wrote: > On Tue, 2009-07-14 at 14:52 -0400, M. Ranganathan wrote: >> 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. > > Aside from the difficulties in configuring it, is there something wrong > with that?
None . It would be tricky to configure, however. > >> 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. > > I don't quite understand what the problem is... how does the name relate > to federation and IP addresses? The xmpp domain is the host name. > > > -- 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/
