Daniel D?az wrote:
...
>
> That's for the end user, but the same applies to whatever bot you have
> (given the bot "follows" the same procedure to register itself with
> the gateways/transports (hint: you'll end up doing it in its behalf)).
>
> Let us know how it goes.
>
> Greetings!
>
> Daniel D?az
> [EMAIL PROTECTED]
Hi Daniel,
I'm still working on this. I sniffed the protocol between a psi client
and the server when the client registers to the msn transport and I'm
trying to replicate this in my component.
What I have so far is this:
send:
<iq type="set" id="790-30" to="msn.devel.pbxip.net"
from="[EMAIL PROTECTED]"><query
xmlns="jabber:iq:register"><username>[EMAIL
PROTECTED]</username><password>xxxxxx</password><nick>SIGKILL</nick></query></iq>
receive:
<iq from="msn.devel.pbxip.net" type="result" id="790-30"
to="[EMAIL PROTECTED]"/>
receive:
<presence to="[EMAIL PROTECTED]" from="msn.devel.pbxip.net"
type="subscribe"/>
send:
<presence from="[EMAIL PROTECTED]" to="msn.devel.pbxip.net"
type="subscribe"/>
send:
<presence from="[EMAIL PROTECTED]" to="msn.devel.pbxip.net"
type="subscribed"/>
receive:
<presence type="probe" from="msn.devel.pbxip.net"
to="[EMAIL PROTECTED]"/>
send:
<presence from="[EMAIL PROTECTED]" to="msn.devel.pbxip.net"/>
receive:
<presence to="[EMAIL PROTECTED]" from="msn.devel.pbxip.net"
type="unavailable"/>
receive:
<presence to="[EMAIL PROTECTED]" from="msn.devel.pbxip.net"
type="unavailable"/>
And that's all I get. In the conversation between psi and the server I
see more iq packets like this:
<iq type="set" id="395-16" to="[EMAIL PROTECTED]/Psi"><query
xmlns="jabber:iq:roster"><item jid="msn.devel
.pbxip.net" subscription="none"/></query></iq>
but I don't receive those in my component.
What am I missing?
Thank you for your time
Regards,
Jorge
From [EMAIL PROTECTED] Thu Aug 11 22:30:43 2005
From: [EMAIL PROTECTED] (Norman Rasmussen)
Date: Thu Aug 11 22:30:46 2005
Subject: [py-transports] Register another component to msn
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
The most import parts are you need to send:
<iq type="set" id="790-30" to="msn.devel.pbxip.net"
from="[EMAIL PROTECTED]"><query
xmlns="jabber:iq:register"><username>[EMAIL
PROTECTED]</username><password>xxxxxx</password><nick>SIGKILL</nick></query></iq>
and respond to the presence request with:
<presence from="[EMAIL PROTECTED]" to="msn.devel.pbxip.net"/>
the probe is just a are-you-there query, which you should respond to.
If in doubt read RFC's:
RFC 3920 - XMPP Core - http://www.ietf.org/rfc/rfc3920.txt
RFC 3921 - XMPP IM - http://www.ietf.org/rfc/rfc3921.txt
IIRC - 3921 has presence info in section 2.2.1
On 11/08/05, Jorge Merlino <[EMAIL PROTECTED]> wrote:
> Daniel D?az wrote:
> ...
> >
> > That's for the end user, but the same applies to whatever bot you have
> > (given the bot "follows" the same procedure to register itself with
> > the gateways/transports (hint: you'll end up doing it in its behalf)).
> >
> > Let us know how it goes.
> >
> > Greetings!
> >
> > Daniel D?az
> > [EMAIL PROTECTED]
>
> Hi Daniel,
>
> I'm still working on this. I sniffed the protocol between a psi client
> and the server when the client registers to the msn transport and I'm
> trying to replicate this in my component.
> What I have so far is this:
>
> send:
> <iq type="set" id="790-30" to="msn.devel.pbxip.net"
> from="[EMAIL PROTECTED]"><query
> xmlns="jabber:iq:register"><username>[EMAIL
> PROTECTED]</username><password>xxxxxx</password><nick>SIGKILL</nick></query></iq>
>
> receive:
> <iq from="msn.devel.pbxip.net" type="result" id="790-30"
> to="[EMAIL PROTECTED]"/>
>
> receive:
> <presence to="[EMAIL PROTECTED]" from="msn.devel.pbxip.net"
> type="subscribe"/>
>
> send:
> <presence from="[EMAIL PROTECTED]" to="msn.devel.pbxip.net"
> type="subscribe"/>
>
> send:
> <presence from="[EMAIL PROTECTED]" to="msn.devel.pbxip.net"
> type="subscribed"/>
>
> receive:
> <presence type="probe" from="msn.devel.pbxip.net"
> to="[EMAIL PROTECTED]"/>
>
> send:
> <presence from="[EMAIL PROTECTED]" to="msn.devel.pbxip.net"/>
>
> receive:
> <presence to="[EMAIL PROTECTED]" from="msn.devel.pbxip.net"
> type="unavailable"/>
>
> receive:
> <presence to="[EMAIL PROTECTED]" from="msn.devel.pbxip.net"
> type="unavailable"/>
>
> And that's all I get. In the conversation between psi and the server I
> see more iq packets like this:
>
> <iq type="set" id="395-16" to="[EMAIL PROTECTED]/Psi"><query
> xmlns="jabber:iq:roster"><item jid="msn.devel
> .pbxip.net" subscription="none"/></query></iq>
>
> but I don't receive those in my component.
>
> What am I missing?
>
>
> Thank you for your time
> Regards,
> Jorge
> _______________________________________________
> py-transports mailing list
> [email protected]
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
>
--
- Norman Rasmussen
- Email: [EMAIL PROTECTED]
- Home page: http://norman.rasmussen.co.za/
From [EMAIL PROTECTED] Thu Aug 11 22:32:39 2005
From: [EMAIL PROTECTED] (Norman Rasmussen)
Date: Thu Aug 11 22:32:41 2005
Subject: [py-transports] Register another component to msn
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
oh, and also:
JEP-0100: Gateway Interaction - http://www.jabber.org/jeps/jep-0100.html
in section 4.1.1.5. (example 7) it gives an example of registering
with a gateway
--
- Norman Rasmussen
- Email: [EMAIL PROTECTED]
- Home page: http://norman.rasmussen.co.za/
From [EMAIL PROTECTED] Fri Aug 12 07:45:39 2005
From: [EMAIL PROTECTED] (Magnus Henoch)
Date: Fri Aug 12 07:44:05 2005
Subject: [py-transports] Register another component to msn
In-Reply-To: <[EMAIL PROTECTED]> (Jorge Merlino's message of
"Thu, 11 Aug 2005 18:34:33 -0300")
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Jorge Merlino <[EMAIL PROTECTED]> writes:
[...]
> And that's all I get. In the conversation between psi and the server I
> see more iq packets like this:
>
> <iq type="set" id="395-16" to="[EMAIL PROTECTED]/Psi"><query
> xmlns="jabber:iq:roster"><item jid="msn.devel
> .pbxip.net" subscription="none"/></query></iq>
>
> but I don't receive those in my component.
>
> What am I missing?
That's a packet from the server, notifying the client of the current
state of its roster. As opposed to a client, a component needs to
track the state of its roster for itself. Basically, remember
everything that sends presence of type "subscribe", and remember
whether you answered with "subscribed" or "unsubscribed".
Magnus
From [EMAIL PROTECTED] Fri Aug 12 12:31:20 2005
From: [EMAIL PROTECTED] (Kawthar Telli)
Date: Fri Aug 12 12:31:23 2005
Subject: [py-transports] Re: jabber Gateway to msn
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Yes it does..I think...actually in a configuration file of the server
there is a command:
JABBER_SPOOL=/var/lib/jabber
but what I don't understand it is even the server does't start again if I
add the configuration of the gateway.
Kawthar
> Does the user the transport is running under have permission to write
> to the spool directory?
>
> Also, could you please ask this again on the py-transports list, that
> way when we figure out what went wrong, others can search it later.
>
> ---
>
> James
>
>
>
> On 12/08/2005, at 7:57 PM, Kawthar Telli wrote:
>
>> Hello ,
>>
>> I am truying to install a jabber gateway to msn trough PyMSNT. I
>> followed
>> the instructions given in the following website:
>> http://msn-transport.jabberstudio.org/docs/server.html
>> Unfortunately it doesn't work, and I get the following error "xdb_file
>> failed to open file amoula.xml" where "amoula" is an account of a
>> jabber
>> client, and the same error message for the other accounts.
>> I don't have any idea about how to fix the problem, if you have an idea
>> I'll be gald to know it.
>>
>> Thank you in advance
>>
>>
>> Yours,
>> Kawthar Telli
>>
>
>
