MSN Transport (CVS)
===================
http://msn-transport.jabberstudio.org/

Features
--------

- MSN protocol 8

Requirements
------------

- jabberd 1.4.x source and header files (-dev)
- libcurl2-ssl with headers (-dev)

Building from tarball
---------------------

  Run "./configure --with-jabberd=/path/to/jabberd" to regenerate the Makefile
  Run "make" to build the transport

  Other configure options are --with-curl-includes, --with-curl-libs and
  --with-pth to specify the path to curl/curl.h, libcurl.a and pth.h

Building from CVS
-----------------

  Make sure you have the auto tools installed (autoconf 2.50+ and automake 1.4+)
  Run "./bootstrap" to generate the configure file
  Then, to just build the transport:
   Run "./configure --with-jabberd=/path/to/jabberd" to regenerate the Makefile
   Run "make" to build the transport
  To create a tarball for distribution:
   Run "./configure --with-jabberd=../jabberd"
   Run "make dist"


Building the transport module
-----------------------------

Go to the transport's main directory and
 ./configure
 make

You should get a
 src/msntrans.so
then (MSN-t module for jabberd 1.4.x).


Overview
--------

MSN-t is a module for jabberd 1.4.2.

MSN-t (or precisely spoken, jabberd 1.4.x running the MSN-t
module) links to the main Jabber server via the connect/accept
mechanism. This means you can use the transport with every 
Jabber server implementation (be it jabberd 1.4.x, jabberd 2,
WPJabber or a commercial server) that can accept TCP
connections from external components.


Configuration
-------------

1. Main Jabber server configuration files

In order to have your main Jabber server accept connections from the
transport's jabberd, you have to configure it accordingly.

If you run jabberd 1.4.x as your main server , add the following to
the <service> section of its configuration file.

 <service id="msnlinker">
   <host>msn.localhost</host>
   <host>conference.msn.localhost</host>
   <accept>
     <ip>127.0.0.1</ip>
     <port>1234</port>
     <secret>test</secret>
   </accept>
 </service>

Be sure to replace "localhost" with the full host name of your server
if you want users of other Jabber servers to be able to use this
transport. Also, the host name of the transport has to be resolveable
via DNS then.
If you do not want users of other Jabber server to be able to use
your server's transport, just add the hostnames of the transport to
/etc/hosts.
In every case all hostnames must resolve on the main Jabber server's
machine, e.g. "ping msn.localhost" must run fine.

In order to advertise the transport's services to the Jabber clients,
add the following to the <browse> section of the main jabberd 1.4.x
configuration file.

 <service type="msn" jid="msn.localhost" name="MSN Transport">
   <ns>jabber:iq:gateway</ns>
   <ns>jabber:iq:register</ns>
 </service>


2. MSN module configuration files

An example configuration file is included (msnt.xml), modify it as
needed.


Running
-------

- make sure the main Jabber server is running
- chdir to the main directory of the tarball
- run "jabberd -c msnt.xml"

If you run into trouble, add "-D" for debug output.

If the transport fails to connect to the main Jabber server,
make sure "telnet 127.0.0.1 1234" (or whatever values you used
in the configuration files) is working on the machine you try
to start the transport on.


Notes
-----

MSN-t uses TCP port 1863 for outgoing connections so you have to open
this port if you use a firewall. No incoming connections are used.
