I'd like my ejabberd servers to point at another system that is running the transports. I've seen the tutorials that describe setting up the transports on the same system running ejabberd. Is there an easy way to point ejabberd at another system for transport use?
Try extra_domains option for
Try 'extra_domains' option formod_disco .
I modified the mod_disco line
I modified the mod_disco line like this:
{mod_disco, [{extra_domains, ["jabber.server.com"]}]},
but the transports don't show up automatically. I still have to tell the client where to look for them. Not a real big deal, but it would be nice to have this functionality.
I cannot reproduce this
I cannot reproduce this behavior with versions 0.7.5--0.9.1-alpha, there is always a correct <item jid='jabber.server.com'/> line in the discovery response.
What is the version of ejabberd you are running?