On 10/11/05, Daniel Henninger <[EMAIL PROTECTED]> wrote:
> I don't particular understand ejabberd's logs, but have you verified
> that icq.jabber.galle.com.br is set up in your ejabberd config on
> port 5348? (I'm sure you have as 5348 is not the 'standard' port to
> begin with ;D ) Just eliminating possibilities. I think Sander is
> on this list, perhaps he can speak more on it... you may be required
> to have that address resolve in DNS. Not sure. =(
Host is resolving fine:
[EMAIL PROTECTED]:/usr/local/etc/ejabberd# host icq.jabber.galle.com.br
icq.jabber.galle.com.br is an alias for jabber.galle.com.br.
jabber.galle.com.br is an alias for srv1.news.galle.com.br.
srv1.news.galle.com.br has address 200.246.25.4
It's listening:
[EMAIL PROTECTED]:/usr/local/etc/ejabberd# sockstat -4 | grep 5348
ejabberd beam 8999 17 tcp4 *:5348 *:*
and I have correct line there
{5348, ejabberd_service, [{access, all},
{host, "icq.jabber.galle.com.br",
[{password, "secret"}]}]}
It's very strange
--
Renato Botelho
ICQ: 54596223
AIM: RBGargaBR
From [EMAIL PROTECTED] Tue Oct 11 13:51:08 2005
From: [EMAIL PROTECTED] (Stian B. Barmen)
Date: Tue Oct 11 13:51:58 2005
Subject: [py-transports] ejabberd + pyICQt problems
In-Reply-To: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
>Host is resolving fine:
>
>[EMAIL PROTECTED]:/usr/local/etc/ejabberd# host icq.jabber.galle.com.br
>icq.jabber.galle.com.br is an alias for jabber.galle.com.br.
>jabber.galle.com.br is an alias for srv1.news.galle.com.br.
>srv1.news.galle.com.br has address 200.246.25.4
>
>It's listening:
>
>[EMAIL PROTECTED]:/usr/local/etc/ejabberd# sockstat -4 | grep 5348
>ejabberd beam 8999 17 tcp4 *:5348 *:*
>
>and I have correct line there
>
> {5348, ejabberd_service, [{access, all},
> {host, "icq.jabber.galle.com.br",
>[{password, "secret"}]}]}
>
>It's very strange
Do you use "secret" as the shared secret?? Would not recommend this
particularly, but, in the pyicq-t.xml file there should be something like:
<!-- The authentication token to use when connecting to the Jabber server ->
<secret>secret</secret>
Change "secret" to the same thing as in ejabberd.
Also, did you check the ejabberd config trough the web admin, or is this
from the ejabberd config file?
That's my five cents worth....
-stian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3095 bytes
Desc: not available
Url :
http://modevia.com/pipermail/py-transports/attachments/20051011/53591a5f/smime-0001.bin
From [EMAIL PROTECTED] Tue Oct 11 14:02:38 2005
From: [EMAIL PROTECTED] (Renato Botelho)
Date: Tue Oct 11 14:02:41 2005
Subject: [py-transports] ejabberd + pyICQt problems
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
On 10/11/05, Stian B. Barmen <[EMAIL PROTECTED]> wrote:
> >Host is resolving fine:
> >
> >[EMAIL PROTECTED]:/usr/local/etc/ejabberd# host icq.jabber.galle.com.br
> >icq.jabber.galle.com.br is an alias for jabber.galle.com.br.
> >jabber.galle.com.br is an alias for srv1.news.galle.com.br.
> >srv1.news.galle.com.br has address 200.246.25.4
> >
> >It's listening:
> >
> >[EMAIL PROTECTED]:/usr/local/etc/ejabberd# sockstat -4 | grep 5348
> >ejabberd beam 8999 17 tcp4 *:5348 *:*
> >
> >and I have correct line there
> >
> > {5348, ejabberd_service, [{access, all},
> > {host, "icq.jabber.galle.com.br",
> >[{password, "secret"}]}]}
> >
> >It's very strange
>
> Do you use "secret" as the shared secret?? Would not recommend this
> particularly, but, in the pyicq-t.xml file there should be something like:
>
> <!-- The authentication token to use when connecting to the Jabber server ->
> <secret>secret</secret>
>
> Change "secret" to the same thing as in ejabberd.
>
> Also, did you check the ejabberd config trough the web admin, or is this
> from the ejabberd config file?
>
> That's my five cents worth....
I'm using secret just to test, now I change it like you can se here:
[EMAIL PROTECTED]:/usr/local/etc/ejabberd# grep secret ../jabber-pyicq2.xml
<secret>xpto</secret>
and change o ejabberd.cfg too:
{5348, ejabberd_service, [{access, all},
{host, "icq.jabber.galle.com.br",
[{password, "xpto"}]}]}
But still have same problems.
--
Renato Botelho
ICQ: 54596223
AIM: RBGargaBR
From [EMAIL PROTECTED] Tue Oct 11 14:02:40 2005
From: [EMAIL PROTECTED] (Norman Rasmussen)
Date: Tue Oct 11 14:02:43 2005
Subject: [py-transports] ejabberd + pyICQt problems
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
It's tcpdump'ing time!
On 11/10/05, Stian B. Barmen <[EMAIL PROTECTED]> wrote:
> >Host is resolving fine:
> >
> >[EMAIL PROTECTED]:/usr/local/etc/ejabberd# host icq.jabber.galle.com.br
> >icq.jabber.galle.com.br is an alias for jabber.galle.com.br.
> >jabber.galle.com.br is an alias for srv1.news.galle.com.br.
> >srv1.news.galle.com.br has address 200.246.25.4
> >
> >It's listening:
> >
> >[EMAIL PROTECTED]:/usr/local/etc/ejabberd# sockstat -4 | grep 5348
> >ejabberd beam 8999 17 tcp4 *:5348 *:*
> >
> >and I have correct line there
> >
> > {5348, ejabberd_service, [{access, all},
> > {host, "icq.jabber.galle.com.br",
> >[{password, "secret"}]}]}
> >
> >It's very strange
>
> Do you use "secret" as the shared secret?? Would not recommend this
> particularly, but, in the pyicq-t.xml file there should be something like:
>
> <!-- The authentication token to use when connecting to the Jabber server ->
> <secret>secret</secret>
>
> Change "secret" to the same thing as in ejabberd.
>
> Also, did you check the ejabberd config trough the web admin, or is this
> from the ejabberd config file?
>
> That's my five cents worth....
>
> -stian
>
>
> _______________________________________________
> py-transports mailing list
> py-transports@blathersource.org
> 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] Tue Oct 11 14:05:40 2005
From: [EMAIL PROTECTED] (Stian B. Barmen)
Date: Tue Oct 11 14:06:23 2005
Subject: [py-transports] ejabberd + pyICQt problems
In-Reply-To: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Did you check ejabberds web interface config? Just to make sure it is the
same there?
If you haven't done so yet try to add
override_local.
override_global.
To the top of ejabberd.cfg before you restart ejabberd with the new
settings. This tells ejabberd to load the settings from the conf file and
override settings in the database.
-stian
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Renato Botelho
Sent: 11. oktober 2005 16:03
To: PyAIM-t/PyICQ-t/PyMSN-t Discussion
Subject: Re: [py-transports] ejabberd + pyICQt problems
On 10/11/05, Stian B. Barmen <[EMAIL PROTECTED]> wrote:
> >Host is resolving fine:
> >
> >[EMAIL PROTECTED]:/usr/local/etc/ejabberd# host icq.jabber.galle.com.br
> >icq.jabber.galle.com.br is an alias for jabber.galle.com.br.
> >jabber.galle.com.br is an alias for srv1.news.galle.com.br.
> >srv1.news.galle.com.br has address 200.246.25.4
> >
> >It's listening:
> >
> >[EMAIL PROTECTED]:/usr/local/etc/ejabberd# sockstat -4 | grep 5348
> >ejabberd beam 8999 17 tcp4 *:5348 *:*
> >
> >and I have correct line there
> >
> > {5348, ejabberd_service, [{access, all},
> > {host, "icq.jabber.galle.com.br",
> >[{password, "secret"}]}]}
> >
> >It's very strange
>
> Do you use "secret" as the shared secret?? Would not recommend this
> particularly, but, in the pyicq-t.xml file there should be something like:
>
> <!-- The authentication token to use when connecting to the Jabber server
->
> <secret>secret</secret>
>
> Change "secret" to the same thing as in ejabberd.
>
> Also, did you check the ejabberd config trough the web admin, or is this
> from the ejabberd config file?
>
> That's my five cents worth....
I'm using secret just to test, now I change it like you can se here:
[EMAIL PROTECTED]:/usr/local/etc/ejabberd# grep secret ../jabber-pyicq2.xml
<secret>xpto</secret>
and change o ejabberd.cfg too:
{5348, ejabberd_service, [{access, all},
{host, "icq.jabber.galle.com.br",
[{password, "xpto"}]}]}
But still have same problems.
--
Renato Botelho
ICQ: 54596223
AIM: RBGargaBR
_______________________________________________
py-transports mailing list
py-transports@blathersource.org
http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3095 bytes
Desc: not available
Url :
http://modevia.com/pipermail/py-transports/attachments/20051011/c285b35f/smime.bin
From [EMAIL PROTECTED] Tue Oct 11 14:08:13 2005
From: [EMAIL PROTECTED] (Daniel Henninger)
Date: Tue Oct 11 14:08:17 2005
Subject: [py-transports] ejabberd + pyICQt problems
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Definitely check in the web interface to make sure it's set right
there. If I recall correctly, ejabberd.cfg isn't really read after
the first time unless you uncomment some lines near the top to say
"override with these values". (otherwise, it's all stored in the
database and kept there)
Daniel
On Oct 11, 2005, at 10:02 AM, Renato Botelho wrote:
> On 10/11/05, Stian B. Barmen <[EMAIL PROTECTED]> wrote:
>
>>> Host is resolving fine:
>>>
>>> [EMAIL PROTECTED]:/usr/local/etc/ejabberd# host icq.jabber.galle.com.br
>>> icq.jabber.galle.com.br is an alias for jabber.galle.com.br.
>>> jabber.galle.com.br is an alias for srv1.news.galle.com.br.
>>> srv1.news.galle.com.br has address 200.246.25.4
>>>
>>> It's listening:
>>>
>>> [EMAIL PROTECTED]:/usr/local/etc/ejabberd# sockstat -4 | grep 5348
>>> ejabberd beam 8999 17 tcp4 *:5348 *:*
>>>
>>> and I have correct line there
>>>
>>> {5348, ejabberd_service, [{access, all},
>>> {host, "icq.jabber.galle.com.br",
>>> [{password, "secret"}]}]}
>>>
>>> It's very strange
>>>
>>
>> Do you use "secret" as the shared secret?? Would not recommend this
>> particularly, but, in the pyicq-t.xml file there should be
>> something like:
>>
>> <!-- The authentication token to use when connecting to the Jabber
>> server ->
>> <secret>secret</secret>
>>
>> Change "secret" to the same thing as in ejabberd.
>>
>> Also, did you check the ejabberd config trough the web admin, or
>> is this
>> from the ejabberd config file?
>>
>> That's my five cents worth....
>>
>
> I'm using secret just to test, now I change it like you can se here:
>
> [EMAIL PROTECTED]:/usr/local/etc/ejabberd# grep secret ../jabber-pyicq2.xml
> <secret>xpto</secret>
>
> and change o ejabberd.cfg too:
>
> {5348, ejabberd_service, [{access, all},
> {host, "icq.jabber.galle.com.br",
> [{password, "xpto"}]}]}
>
> But still have same problems.
> --
> Renato Botelho
> ICQ: 54596223
> AIM: RBGargaBR
> _______________________________________________
> py-transports mailing list
> py-transports@blathersource.org
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
>
>
>
