|
| Author |
Message |
dubbeld00
Newbie
Joined: 24 Aug 2005
Posts: 5
  
|
 Posted: Wed Aug 24, 2005 2:38 pm Post subject: Try to connect to google's TALK |
 |
|
I'm trying to connect with the google talk server with net::jabber. (v 2.0)
But i only get:
ERROR: Authorization failed: -
I'll try to connect with:
my $server = "talk.google.com";
my $port = "5222";
my $username = "######\@gmail.com";
my $password = "---------";
my $resource = "Trillian";
is there someone who can connect to talk.google.com? and how?
this is what i'm trying to do:
| Code: | my $Connection = new Net::Jabber::Client();
$Connection->SetCallBacks(message=>\&InMessage,
presence=>\&InPresence,
iq=>\&InIQ);
my $status = $Connection->Connect(hostname=>$server,
port=>$port,
);
if (!(defined($status)))
{
print "ERROR: Jabber server is down or connection was not allowed.\n";
print " ($!)\n";
exit(0);
}
my @result = $Connection->AuthSend("username" => $username,
"password" => $password,
"resource" => $resource);
if ($result[0] ne "ok")
{
print "ERROR: Authorization failed: $result[0] - $result[1]\n";
exit(0);
} |
|
|
| Back to top |
|
 |
alienz
Almost An Agent
Joined: 22 Mar 2004
Posts: 1436
Location: Mars
|
|
| Back to top |
|
|
darkmonkey
The Merovingian
Joined: 18 Apr 2004
Posts: 2557
Location: London, England
votes: 7
|
| Posted: Sat Aug 27, 2005 10:28 am Post subject: |
|
|
The Jabbber module won't connect to Google Talk as it doesn't have any SSL support. I [yesterday] started sniffing the protocol [with matt's guidance] and may make a working Google Talk module some time.
_________________
~ Josh
[ Need bot hosting on a dedicated server? PM me. ] |
|
| Back to top |
|
|
dubbeld00
Newbie
Joined: 24 Aug 2005
Posts: 5
|
| Posted: Sat Aug 27, 2005 1:12 pm Post subject: |
|
|
| Quote: | | and may make a working Google Talk module some time. |
That's great news 
I don't know if you've seen it, but you can also logon on port 5223. This is used by connections with miranda and Psy... Port 5223 is using SSL protection and Port 5222 is using TLS protection (that is based on SSL 3.0 protection but not the same, i thought  ). |
|
| Back to top |
|
|
Thus0
Newbie
Joined: 06 Dec 2005
Posts: 1
|
| Posted: Tue Dec 06, 2005 8:37 am Post subject: |
|
|
| dubbeld00 wrote: | | Quote: | | and may make a working Google Talk module some time. |
That's great news
I don't know if you've seen it, but you can also logon on port 5223. This is used by connections with miranda and Psy... Port 5223 is using SSL protection and Port 5222 is using TLS protection (that is based on SSL 3.0 protection but not the same, i thought ). |
It does work with Net::XMPP (you just need to modify a line in the source code). For now, as I'm doing some tests, I've written a small library gtalk.pm and I can send some google talk messages with perl
See my tutorial :
http://www.pervasive-network.org/SPIP/GoogleTalk-with-perl
I'm trying to see how google talk can bypass a proxy so I can send some messages when I'm at work but for now, it doesn't seem to work.
Rq : you can send jabber on talk.google.com:80
--
Thus0 |
|
| Back to top |
|
|
Cer
Upgraded Agent
Joined: 03 Feb 2004
Posts: 3776
Location: Michigan
votes: 4
|
| Posted: Tue Dec 06, 2005 12:09 pm Post subject: |
|
|
I think the naming of MSN.pm was a bad idea, it's apparently giving people a bad impression of how to name modules.
You shouldn't use toplevel namespace unless you have to. Net::GTalk would work just as well and plus you can share your work with CPAN when it's done without writing a lengthy 5 paragraph essay explaining why gtalk has to be a toplevel namespace.
_________________
Current Site (2008) http://www.cuvou.com/ |
|
| Back to top |
|
|
Mojave
Almost An Agent
Joined: 01 Nov 2003
Posts: 1434
|
| Posted: Tue Dec 06, 2005 5:58 pm Post subject: |
|
|
| Cer wrote: | | I think the naming of MSN.pm was a bad idea, it's apparently giving people a bad impression of how to name modules. |
For the record, MSN.pm was named like that when I first started working on it and I thought it might cause more confusion for people if I changed it. In addition, the proper place for it, Net::MSN, was already taken. In any case, I agree that it should be renamed at some point, the question is to what. I remember actually emailing the Net::MSN owner about taking over his module name but never got a reply. That is the logical place for it. |
|
| Back to top |
|
|
|
User Control Panel
