ejabberd - Comments for "MSN Transport"

Found the issue

tiaan — Fri, 14 Oct 2005 08:28:08 +0000

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

sander — Thu, 13 Oct 2005 21:13:11 +0000

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 mailing list of Py-transports.

--
sander

PyTransport Log

tiaan — Thu, 13 Oct 2005 15:17:39 +0000

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