I've successfully installed ejabberd and added various virtual domains. So my next step was to start introducing transports, as my users generally use MSN I thought I'd start with that. I have managed to get this working on one domain, however users on the other domains cannot see the MSN transport.
Has anyone configured pymsnt for more than one domain? It may be as simple as adding the domains into config.xml but I can't find the documentation.
I've also tried configuring an instance for each vhost but I can only get one instance started at a time even though they have separate pid files.
Please let me know if I should be posting this somewhere else.
PS I'm still trying to understand why the transports aren't built into ejabberd, why do we need to install "modules" for each transport?
try extra_domains
I have managed to get this working on one domain, however users on the other domains cannot see the MSN transport.
The users in the other vhosts do not see the MSN transport when they open the Service Discovery of their vhosts. But if they enter the JID of the transport in the address bar (try with Psi or Gajim), they will see it, can register and use it.
With that you only need 1 PyMSNt running.
You have example.com and example.org. You installed PyMSNt and it serves the JID msnt.example.com. As you noticed, a user in example.org will not see the transport. But he can put this in the Service Discovery: msnt.example.com and he can register, etc.
Even better: check the option 'extra_domains' of mod_disco: it will allow you to show msnt.example.com as a service for example.org users.
Has anyone configured pymsnt for more than one domain? It may be as simple as adding the domains into config.xml but I can't find the documentation.
Maybe PyMSNt doesn't support 'virtual hosts'.
I've also tried configuring an instance for each vhost but I can only get one instance started at a time even though they have separate pid files.
I imagine each pymsnt instance needs to run in a different port. And you need to configure a different port in ejabberd.cfg too, for each pymsnt.
Please let me know if I should be posting this somewhere else.
You can try in the py-transports mailing list, or in the JADMIN mailing list.
why the transports aren't built into ejabberd
Because you didn't implement them! :D
Firstly thanks for the reply
Firstly thanks for the reply I'll give your suggestions a go this evening.
I imagine each pymsnt instance needs to run in a different port. And you need to configure a different port in ejabberd.cfg too, for each pymsnt.
I tried that and it still wouldn't start the second instance. I believe there may be a few ports that are "MSN specific" that can't be changed. Some form of error reporting would be nice but I'll take that up with the py-transport people ( there may be some that I haven't enabled yet ).
Maybe PyMSNt doesn't support 'virtual hosts'.
I have to say that is a little disappointing as I chose ejabberd for its vhost and clustering abilities. I can't really say that can I ... if I really wanted it I should write it myself. Just thought it was something that would already have been thought of.
Because you didn't implement them! :D
I think what I meant was is there a reason no one has yet?
Again thanks for the answers, it appears I have few more things to try before rewriting the transports :P
Regards,
Kurt
MSN Transport
I've just tried browsing for example.org services (where PyMSNt is resident) and I've found it and connected to it from my example.com account. I guess I was over complicating things a little although it would be nice to have the services listed for each vhost. Just means a few more instructions on the how to page :P
Thanks again for you help.
mod_disco
mod_disco rocks, even though it'll always display even if the service is unavailable. Thanks again.