Hi,
I'm trying to setup PyMSN. When PyMSN is started the message below is logged, and nothing else. But there is no "Service" listed in my jabber client, I tried both jajc and tkabber. PyMSN is not running on the same server as ejabber.
=INFO REPORT==== 13-Oct-2005::16:12:26 ===
I(<0.225.0>:ejabberd_listener:90): (#Port<0.338>) Accepted connection {{192,168,30,101},62149} -> {{192,168,30,105},5555}
The following entry is in the ejabber.cfg file :
{5555, ejabberd_service, [{host, "msn.host.com",
[{password, "secret"}]}]},
Am I correct in saying that "msn.host.com" must be the fqdn of the PyMSN server? Can I switch on debug logging? What else could be wrong?
Thanks
Tiaan
PyTransport Log
I don't see any errors in the PyTransport log.
- 17:14:24 - Debug logging enabled.
- 17:14:24 - PyTransport: Service starting up
- 17:14:24 - Discovery: Created server discovery manager
- 17:14:24 - Discovery: Adding feature support "http://jabber.org/protocol/disco" "None"
- 17:14:24 - Discovery: Adding identitity "gateway" "msn" "MSN Transport"
- 17:14:24 - Discovery: Adding identitity "conference" "text" "MSN Transport Chatrooms"
- 17:14:24 - Discovery: Adding feature support "http://jabber.org/protocol/muc" "None"
- 17:14:24 - Discovery: Adding feature support "jabber:iq:register" ">"
- 17:14:24 - RegisterManager: Created
- 17:14:24 - Discovery: Adding feature support "jabber:iq:gateway" ">"
- 17:14:24 - Discovery: Adding feature support "jabber:iq:version" ">"
- 17:14:25 - PyTransport: Connected to main Jabberd server
Found the issue
It started working after making the fqdn of the jid, mainServer, mainServerJID and ejabberd_service the same. Added entry in the hosts file for the name.
{!-- The JabberID of the transport -->
{jid>msn.domain.com
{!-- The IP address of the main Jabber server to connect to -->
{mainServer>msn.domain.com
{mainServerJID>domain.com
{5347, ejabberd_service, [{host, "msn.domain.com",
[{password, "testing"}]}]},
Tiaan
Are you running the
Are you running the transport on Windows? If so, I thought there is a known bug in PyMSNt...maybe you better ask then on the of Py-transports.
--
sander