ejabberd - Comments for "gtalk federation"

still the same problem with ejabberd 1.1.4

Anonymous — Thu, 04 Oct 2007 19:01:36 +0000

log:

I(<0.375.0>:ejabberd_s2s_out:106): started: {"192.168.5.183",
"gmail.com",
{new,"701378265"}}

=INFO REPORT==== 2007-10-04 22:10:20 ===
I(<0.375.0>:ejabberd_s2s_out:249): recv result: {"gmail.com",
"192.168.5.183",
[],
"invalid"}
please let me know if any success on this.. i have tried the option to edit /etc/hosts file but no luck..

worked for me too

KaT — Sat, 21 Jan 2006 21:10:22 +0000

I added:

216.239.37.125 gmail.com

to my c:\winnt\system32\drivers\etc\hosts

and voila!

Solution available

mfoss — Sat, 21 Jan 2006 15:41:46 +0000

You are probably experiencing a known problem. There's a solution that have provided 100% success until now. Try it and tell us if it works or not: ejabberd can't connect to some servers: Fix DNS SRV.

Thanks, it worked for me, i

LonelyOne — Sat, 21 Jan 2006 09:49:10 +0000

Thanks, it worked for me, i can now get authorizations requests both ways, and then successfully get presence for contacts.
:)

Solution

yeyo — Sat, 21 Jan 2006 08:16:27 +0000

I think problem is that jid is like xxx@gmail.com but server is talk.google.com.
Solution 1 -> add to /etc/hosts section like this:
gmail.com 216.239.37.125
Solution 2 -> i have no idea :)

216.239.37.125 is talk.google.com ip..

Andrzej

more info

KaT — Fri, 20 Jan 2006 18:35:23 +0000

I am using erlang 5.4.12 r10b on W2K and ejabberd 1.0.0

When i try to write from an account at fiade.com to one on gtalk the logs are:

=INFO REPORT==== 2006-01-20 19:19:04 ===
I(<0.360.0>:ejabberd_s2s_out:104): started: {"fiade.com",
"gmail.com",
{new,"1301749924"}}

=INFO REPORT==== 2006-01-20 19:20:07 ===
I(<0.360.0>:ejabberd_s2s_out:632): terminated: normal

If I try from gmail to fiade.com, i see:

=INFO REPORT==== 2006-01-20 17:41:55 ===
I(<0.230.0>:ejabberd_listener:90): (#Port<0.301>) Accepted connection {{64,233,166,129},42788} -> {{192,168,2,100},5269}

=INFO REPORT==== 2006-01-20 17:41:55 ===
I(<0.292.0>:ejabberd_s2s_in:102): started: {gen_tcp,#Port<0.301>}

=INFO REPORT==== 2006-01-20 17:41:55 ===
I(<0.292.0>:ejabberd_s2s_in:501): terminated: normal

=INFO REPORT==== 2006-01-20 17:41:55 ===
I(<0.230.0>:ejabberd_listener:90): (#Port<0.333>) Accepted connection {{64,233,166,129},42793} -> {{192,168,2,100},5269}

=INFO REPORT==== 2006-01-20 17:41:55 ===
I(<0.294.0>:ejabberd_s2s_in:102): started: {gen_tcp,#Port<0.333>}

=INFO REPORT==== 2006-01-20 17:41:55 ===
I(<0.294.0>:ejabberd_s2s_in:308): GET KEY: {"fiade.com",
"gmail.com",
[],
"CAESBxCXvc/FjiEaELnG/k4elEH7PU6FqdXocKQ="}

=INFO REPORT==== 2006-01-20 17:41:55 ===
I(<0.296.0>:ejabberd_s2s_out:104): started: {"fiade.com",
"gmail.com",
{verify,
<0.294.0>,
"CAESBxCXvc/FjiEaELnG/k4elEH7PU6FqdXocKQ=",
"725950031"}}

=INFO REPORT==== 2006-01-20 17:42:14 ===
I(<0.294.0>:ejabberd_s2s_in:501): terminated: normal

any idea?

Me too

MaximeAD — Wed, 18 Jan 2006 15:01:00 +0000

Me too I've got problems about that... I'll wait and pray for a solution.

Maxime Amyot-Desmarais
http://maximead.is-a-geek.com:8080/maximead

:(

KaT — Wed, 18 Jan 2006 14:37:32 +0000

I have tested:

-using a self-signed cert
-s2s encryption disabled
-I added my ejabberd account as a contact for my gtalk account

everything failed

ejabberd logs show that gtalk server connects to my ejabberd server, and that my server is able to connect to gtalk server too, so it does not seem to be a "firewall-like" problem...

any idea?

I also did not yet succeeded

sander — Wed, 18 Jan 2006 13:25:31 +0000

I also did not yet succeeded in it, but I heard you need to get a subscription from a Google Talke user first. So, Google Talk might use the users' rosters as a whitelist.

--
sander

It's known to work

mfoss — Wed, 18 Jan 2006 12:46:43 +0000

ejabberd and gtalk are known to work:

1.0.0 with TLS and SASL on S2S (self signed certificate): jabber.ru
0.9.8 without TLS or SASL on S2S: jabberes.org

And there are examples of it not working, too, but I didn't ask what was their setup.

What happens if you use a self-signed cert? And if you disable S2S encryption at all?