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

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

  <service id="msn.mydomain">

    <!-- required for conference support
    <host>conference.msn.mydomain</host> -->

    <msntrans xmlns="jabber:config:msntrans">

      <instructions>Enter your MSN Messenger account and password. Example: user1@hotmail.com.  Nickname is optional.</instructions>

      <!-- the transport vCard -->
      <vCard>
        <FN>MSN Transport</FN>
        <DESC>This is MSN Transport</DESC>
        <URL>http://foo.bar/</URL>
      </vCard>

      <!-- Conference support allows you to create groupchat rooms on MSN
           transport and invite MSN users to join. -->

      <!--
      <conference id="conference.msn.mydomain">

        <!-- This will make MSN transport invite you to a special groupchat
             room when more then one user joins a normal one-on-one session.
             Joining this room will make MSN transport "switch" the session
             into groupchat mode.  If you ignore it, MSN transport will
             continue to send the messages as one-on-one chats. -->

        <!-- <invite>More then one user has joined this chat session.  Join this room to switch into groupchat mode.</invite> -->

        <notice>
          <join> has become available</join>
          <leave> has left</leave>
        </notice>

      </conference> -->

      <!-- The default server(s) is usually ok
      <servers>
         <ip>64.4.13.56</ip>
         <ip>64.4.13.57</ip>
      </servers> -->

      <headlines/>  <!-- Enable Hotmail inbox notification -->

    </msntrans>

    <load>
      <msntrans>./msn-transport/src/msntrans.so</msntrans>
    </load>

  </service>

Add this to your JSM browse configuration:

  <browse>

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

<!-- For clients that don't support browsing, this is needed for MSN Conferencing to appear in the agent list.
    <conference type="private" jid="conference.msn.mydomain" name="MSN Transport Conference"/>
-->

    ...

  </browse>


Separate process
----------------

To increase stability, it is best to run MSN transport in its own process.
MSN-t will communicate with the "master" process (frequently the JSM process)
via base_accept and base_connect.  In the below example, the master process will
listen on port "1234" for MSN Transport to connect.

Create a file called msntrans.xml which contains the following XML.

<jabber>

  <!-- msnlinker is the "uplink" to the other process -->
  <service id="msnlinker">
    <uplink/>
    <connect>
      <ip>127.0.0.1</ip>
      <port>1234</port>
      <secret>test</secret>
    </connect>
  </service>

  <service id="msn.mydomain">

    <msntrans xmlns="jabber:config:msntrans">
      <!-- Put your MSN config here -->
    </msntrans>

    <load>
      <msntrans>./msn-transport/src/msntrans.so</msntrans>
    </load>

  </service>

  <!-- By uncommenting the these two sections, xdb and log packets will be handled here and not
       delivered to the master process

  <log id="msnlog">
    <file>./msnlog</file>
  </log>

  <xdb id="xdb">
    <host>msn.mydomain</host>
    <load><xdb_file>./xdb_file/xdb_file.so</xdb_file></load>
    <xdb_file xmlns="jabber:config:xdb_file"><spool>/home/sheath/jabber/jabber2/spool</spool></xdb_file>
  </xdb>

  -->

</jabber>

In the master configuration file, add the following section:

  <service id="msnlinker">
    <uplink/>
    <accept>
      <ip>127.0.0.1</ip>
      <port>1234</port>
      <secret>test</secret>
    </accept>
  </service>


Notes
-----

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