gtalk transport for ejabberd server

[ravindra]

Hi,
Is there any transport for ejabberd to enable gtalk chat? I am running
ejabberd 2.0.0 on my server.

[Wouter Horré]

You don't need any transport to talk to gtalk contacts. Just add you
contact with it's gmail address as a contact.

regards
Wouter

--
http://wouter.horre.be/

[Arup Malakar]

I think what ravindra is looking for is having a gtalk transport similar to yahoo or msn etc. To be able to see all the contacts that he has already in gtalk via the ejabber server. To be able to login using his existing gtalk username and password to his ejabberd. Openfire seems to have gtalk transport support. I am also looking for gtalk transport for ejabberd, but haven't come across any documentation.

Regards,
Arup

--
Arup Malakar
Ph: +91 98804 55200
Email: amal...@gmail.com

[Vadim Efimov]

very strange feature - gtalk = jabber server...

[karma]

I too have been curious in finding something similar to this, though I think there may be some confusion going around about how this may work.  Essentially, gmail is implemented utilizing jabber/xmpp.  Google now allows for s2s (server-to-server) connections enabling you to add a gmail contact.  So, I could tell all of my friends that have gmail, they can use my jabber ID to chat with me through gmail; likewise I can use my jabber ID to 'contact' my gmail friends.  This should all happen transparently (provided everything is setup correctly) utilizing s2s communications.

What this does not provide is the ability to access multiple accounts synchronously (and seamlessly on the contacts' end) without the chat client supporting multiple logins.  The reason that I would like to have this functionality is that I have multiple accounts from multiple networks and there is no way that I can be logged on to all of them at the same time without either providing an xmpp transport or giving in and setting up a client that supports multiple accounts simultaneously.

As of now, I have only found one xmpp transport and I have not yet been able to get it to work with gmail.  The project is called xmppgateway, and it can be found here:

http://zerlargal.org/c/xmppgateway/

Please note the issues lower on the page as well, they sound a bit like production show stoppers, IMO. 


If anyone has any further information on the topic, I would love to hear it!

Thanks.

[Jamin W. Collins]

karma wrote:
>
> What this does not provide is the ability to access multiple accounts
> synchronously (and seamlessly on the contacts' end) without the chat
> client supporting multiple logins. The reason that I would like to have
> this functionality is that I have multiple accounts from multiple
> networks and there is no way that I can be logged on to all of them at
> the same time without either providing an xmpp transport or giving in
> and setting up a client that supports multiple accounts simultaneously.

Rather than creating an essentially redundant transport, why not request
client developers support multiple logins? I've been using Psi as my
Jabber client for some time now and its had multiple login support for
quite some time (since I started using it years ago). I haven't
specifically checked for other clients that support this, but I wouldn't
think that Psi is the only one.

--
Jamin W. Collins

[Norman Rasmussen]

On Wed, Apr 2, 2008 at 1:59 PM, Jamin W. Collins
<jcol...@asgardsrealm.net> wrote:
> Rather than creating an essentially redundant transport, why not request
> client developers support multiple logins? I've been using Psi as my
> Jabber client for some time now and its had multiple login support for
> quite some time (since I started using it years ago). I haven't
> specifically checked for other clients that support this, but I wouldn't
> think that Psi is the only one.

I use primarily use Psi so I mainly agree, things to note though:

1) logging in from a remote/new/web location means you have to
manually connect to each and every account, which is an utter pain.
It's actually easier to use legacy networks because of this central
login that XMPP provides.
2) indeed --> pidgin and gajim both supports multiple accounts - in
fact they do better than Psi because they allow a combined roster in
which all account contacts appear together and you can even
meta-contact them. I'm assuming Psi's meta-contact support will be
released just before the next Duke Nukem.

--
- Norman Rasmussen
- Email: nor...@rasmussen.co.za
- Home page: http://norman.rasmussen.co.za/

[Phil Reynolds]

On Wed, Apr 02, 2008 at 02:26:20PM +0200, Norman Rasmussen wrote:
>
> On Wed, Apr 2, 2008 at 1:59 PM, Jamin W. Collins
> <jcol...@asgardsrealm.net> wrote:
> > Rather than creating an essentially redundant transport, why not request
> > client developers support multiple logins? I've been using Psi as my
> > Jabber client for some time now and its had multiple login support for
> > quite some time (since I started using it years ago). I haven't
> > specifically checked for other clients that support this, but I wouldn't
> > think that Psi is the only one.
>
> I use primarily use Psi so I mainly agree, things to note though:
>
> 1) logging in from a remote/new/web location means you have to
> manually connect to each and every account, which is an utter pain.
> It's actually easier to use legacy networks because of this central
> login that XMPP provides.

I agree completely. I use Psi and also IM+, and have found I can be on
the various messengers continuously if I wish. In fact, I very rarely
log out of any of them, provided the transports are working, unless I am
on underground trains or driving (when running IM+ would be somewhat
pointless and probably stop Wayfinder working well too!).

> 2) indeed --> pidgin and gajim both supports multiple accounts - in
> fact they do better than Psi because they allow a combined roster in
> which all account contacts appear together and you can even
> meta-contact them. I'm assuming Psi's meta-contact support will be
> released just before the next Duke Nukem.

IM+ doesn't have meta-contact support either. In fact, being a
multi-protocol program, it probably doesn't actually expect users to use
everything through Jabber, though, provided the transports stay
connected, it works just fine.

I had only a very limited number of Gtalk contacts before they supported
s2s and was able to migrate them over to using my main Jabber account
very soon thereafter. I have not logged into Gtalk since, but Psi
supports multiple logins, and IM+ has Gtalk support, should I ever need
to.

I long for the day when I can get rid of another IM network from my
regular use - though it's anybody's guess which will be next to go.

--
Phil Reynolds
o ____ mail: ph...@tinsleyviaduct.com and emle...@gmail.com
|L_ \ / Web: http://www.tinsleyviaduct.com/phil/
(_)- \/ Waltham 66, Emley Moor 69, Droitwich 79, Windows 95

[karma]

There probably is a plethora of clients that support multiple
accounts. The developer of the Coccinella client provides some very
good points about transports on this page (several of which apply to
xmpp-to-xmpp gateways):

http://thecoccinella.org/whytransportsmatter

The perl 'xmppgateway' provides these reasons for it's inception:

- Gaining access to a system which your client cannot access on its
own (eg, SSL or TLS differences, or one connection-at-a-time
limitations in the client).
- A limited way of providing external Jabber connectivity to corporate clients.
- An anonymous Jabber relay.

My reason for wanting to implement an xmpp transport is to have a
single sign-on capability for multiple networks. This way if I decide
to use a command line client, Coccinella, or gtalk, depending on my
location, context (as domain), network environment, and platform
environment, I can implement them all without exclusion of my work
chat server, public networks, or any of my private chat servers.

Additionally this works if I am in an untrusted environment and I want
to implement communications securely from within the environment.
(Sorry, not going to provide details on this one. ;-) Just off the
top of my head though, I can also think of a few uses for this
functionality when it comes to using XMPP as a carrier for other
protocols such as SOAP, RSS, or SMTP.

My point here is simply that there is most definitely a need for both
s2s and xmpp gateways, yet at the moment the breadth of functional and
flexible xmpp gateways seems to be non-existent. On the other hand,
perhaps this goes beyond the functionality of a transport and would
need to be an extension.

[Arup Malakar]

Mailing jad...@jabber.org I came to know about the following xmpp-xmpp transport.

http://wiki.jrudevels.org/index.php/Eng:J2J

Has anyone used the above mentioned transport. I am having some difficulty installing it though. The python script is throwing an exception which I don't have much clue:

Exception exceptions.AttributeError: "database instance has no attribute 'dbCursor'" in <bound method database.__del__ of <database.database instance at 0x859306c>> ignored

Is anybody successfully running j2j transport?

One more thought J2J documentation says it doesn't support SSL, but it does support GTalk. I thought gtalk
supports only SSL enabled clients then how come j2j support gtalk? [ Does StartTLS play any role here as J2J supports
StartTLS ]

Arup

[nubg...@gmail.com]

I realize this might be too late to be of use to you, but maybe this
will help the next person who comes along and tries to tackle j2j.

On Apr 10, 10:06 am, "Arup Malakar" <amala...@gmail.com> wrote:
> Mailing jad...@jabber.org I came to know about the following xmpp-xmpp
> transport.
>
> http://wiki.jrudevels.org/index.php/Eng:J2J
>
> Has anyone used the above mentioned transport. I am having some difficulty
> installing it though. The python script is throwing an exception which I
> don't have much clue:

It's not the easiest thing to setup, but it does work quite robustly.

> Exception exceptions.AttributeError: "database instance has no attribute
> 'dbCursor'" in <bound method database.__del__ of <database.database instance
> at 0x859306c>> ignored

This error indicates that you do not have the right database driver
installed. j2j supports both mysql and postgresql, but needs the
appropriate python libraries to access the database. Not the most
friendly error message, I know.

> One more thought J2J documentation says it doesn't support SSL, but it does
> support GTalk. I thought gtalk
> supports only SSL enabled clients then how come j2j support gtalk? [ Does
> StartTLS play any role here as J2J supports
> StartTLS ]

j2j does not support *legacy* SSL connections (port 5223, I think it
was), but it does communicate securely with all modern Jabber servers,
including Google's.

[Vishal]

Hello

Am facing the same problem. Got the following installed

Python
PostgreSQL
PyGreSQL
Twisted

Following Drivers also installed

JDBC - JDBC Driver
PgOleDb - OLE-DB Driver
psqlODBC - ODBC Driver

Are there any more drivers to be installed?

Kinldy let me know

Thanks
Vishal