[jadmin] Msn-t transport with Jabber2 server ?

[nux]

On Sunday 28 March 2004 10.49, xavier xavier wrote:
> Hi,
>
> I'm using a Jabber 1.4 server for a while and i decide
> to install jabber2 on an another server. All work fine
> with Jabber protocol. But i don't understant how i can
> use the msn-t gateway with Jabber2. I can see in this
> newsgroup that i've to use msn-t on Jabber 1.4 on the
> same server than Jabber 2... How can i do this ??? I
> think that it will don't work if i install an older
> version of Jabber on the same server than Jabber2 (TCP
> ports conflict and so on...). Say me if i'm wrong ...
>
> All configuration example (Jabber 1.4 and 2) are
> welcome !
>
> Thanks in advance for your answer and excuse me for my
> bad english...
>
> Xavier
> xavier_post at yahoo.fr
>
hello xavier -- .actually, it seems the only component available to run with 
jabber2 is mu-conference via jabber component runtime.(the next release of 
jcr will be able to compile the other transports ) , the others must be 
running with jabber vers 1.

like that per ex.  ./jabberd/jabberd -c msnt.xml
do 
here an example config in 3 parts.
1rst ---
config file jabber-1 to run msn-transport component to connect to jabber2 the 
main server ( the 1rst jabber-1 not needs to listen , u will not have any 
port conflict ! )
2 .--- 
sm.xml conf file of the main jabber2 -- just the discovery section. 
3..---
router.xml conf file of the main jabber2 --- just the alias section--  

i hope it help u. .. .. i'm new user to jabber .  ;O) , maybe anyone will have 
more info.
courrage !

laurent.

///  ---#############--- part delimiter ---#############--- ///
msnt.xml
<jabber>

  <!-- you can add elogger and rlogger entries here if
       you don't want the main Jabber server do the
       logging -->
  <log id='elogger'>
    <host/>
    <logtype/>
    <format>%d: [%t] (%h): %s</format>
    <file>./msnerror</file>
  </log>

  <log id='rlogger'>
    <host/>
    <logtype>record</logtype>
    <format>%d %h %s</format>
    <file>./msnrecord</file>
  </log>

  <!-- Some Jabber server implementations do not
     provide XDB services (for example jabberd 2.0).    < 
----------------------- IMPORTANT --------------------------
     Configure XDB here to have the transport's
     jabberd 1.4.x handle all XDB requests. This
     is strongly recommended if you use xdb_ldap,
     xdb_sql or other non-file XDB implementations,
     too.  -->
  <xdb id="xdb">
    <host/>
    <load>
      <xdb_file>xdb_file/xdb_file.so</xdb_file>
    </load>
    <xdb_file xmlns="jabber:config:xdb_file">
      <spool><jabberd:cmdline flag='s'>./spool</jabberd:cmdline></spool>
    </xdb_file>
  </xdb>

  <!--
     Replace "localhost" by the full host name of your server
     and have all host names here resolveable via DNS if you
     want the transport to be available to the public.
  -->
  <service id="msn.localhost">
   <host>confe.msn.localhost</host>
    <msntrans xmlns="jabber:config:msntrans">
     <instructions>Enter your MSN Messenger account and password. Example: 
user1 at hotmail.com.  Nickname is optional.</instructions>

      <!-- the transport vCard -->
      <vCard>
        <FN>MSN Transport</FN>
        <DESC>This is MSN Transport</DESC>
        <URL>http://msn-transport.jabberstudio.org/</URL>
      </vCard>

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

      <conference id="conference.msn.localhost">

        <!-- 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>

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

      <!-- Set options for CURL library -->
      <curl>
        <!-- Use insecure mode for SSL transactions (see man curl for -k 
option)
             Note, this is BAD. Fix your curl certificates, unless you
             really don't care about the passport accounts that will be used
             by this server -->

<!--    <insecureSSL/> -->


        <!-- Proxy settings for Curl, use this if you need a proxy for outside
             HTTPS connections, note that this does *not* affect the rest of
             MSN-t, meaning you still must be able to connect to
             messenger.hotmail.com on port 1863 directly for this to work
        -->
        <!--
        <proxyhost>proxy-host.com:8080</proxyhost>
        <proxypass>user:password</proxypass>
        -->

        <!-- To set the curl library to use a SOCKS5 proxy instead of an HTTP
             proxy, uncomment the line below  -->

        <!-- <socksproxy/> -->
      </curl>
    </msntrans>
    <load>
      <msntrans>./msn-transport/src/msntrans.so</msntrans>
    </load>
  </service>

  <!--
     Here the jabberd 1.4.x that runs the MSN Transport
     module is instructed to uplink to the main Jabber
     server.
     The settings here have to match the setting you made
     in your main Jabber server's configuration.
  -->
  <service id="msnlink">  <!-- that is for the component link with jabber2 -->
    <uplink/>
    <connect>
      <ip>127.0.0.1</ip>
      <port>5347</port>
      <secret>component-secret-pass</secret> 

 <!-- Shared secret used to identify legacy components (that is,
         "jabber:component:accept" components that authenticate using
         the "handshake" method). -->
 
    </connect>
  </service>

</jabber>
///  ---#############--- part delimiter ---#############--- ///
sm.xml)
  <discovery>
   <items>

      <!-- example entry for a groupchat (conference) service -->

      <item category='conference' type='public' jid='conf.localhost' 
name='salles de discussion'/>

      <item category='service' type='msn' jid='msn.localhost' name='passerelle 
vers msn hotmail'/>

    </items>

  </discovery>

///  ---#############--- part delimiter ---#############--- ///
router.xml
 <aliases>

    <alias name='msn.localhost' target='msnlink'/>    <!-- target => name of 
service id  --> 

    <alias name='conference.localhost' target='msnlink'/>

  </aliases>

///  ---#############--- part delimiter ---#############--- ///