[asterisk-bugs] [Asterisk 0010913]: Jabber gtalk not connecting anymore

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10913 
====================================================================== 
Reported By:                tootai
Assigned To:                phsultan
====================================================================== 
Project:                    Asterisk
Issue ID:                   10913
Category:                   Resources/res_jabber
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 84939 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             10-08-2007 07:34 CDT
Last Modified:              10-09-2007 08:48 CDT
====================================================================== 
Summary:                    Jabber gtalk not connecting anymore
Description: 
Good day,

as from version trunk from yesterday we have following logs and no
conenction to gtalk. Hadn't had this issue till now (last update: trunk
from around one month):

[Oct  8 14:40:57] VERBOSE[3995] logger.c:
JABBER: googletalk INCOMING: <stream:features><starttls
xmlns="urn:ietf:params:xml:ns:xmpp-tls"><required/></starttls><mechanisms
xmlns="urn:ietf:params:xml:
ns:xmpp-sasl"><mechanism>X-GOOGLE-TOKEN</mechanism></mechanisms></stream:features><proceed
xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>
[Oct  8 14:40:57] VERBOSE[3995] logger.c:
JABBER: googletalk OUTGOING: <?xml version='1.0'?><stream:stream
xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client'
to='gmail.com' version
='1.0'>
[Oct  8 14:40:57] VERBOSE[3995] logger.c:
JABBER: googletalk INCOMING: <?xml version="1.0"
encoding="UTF-8"?><stream:stream from="gmail.com" id="37EFFCC36FEC8C8F"
version="1.0" xmlns:stream="http://e
therx.jabber.org/streams" xmlns="jabber:client">
[Oct  8 14:40:57] VERBOSE[3995] logger.c:
JABBER: googletalk INCOMING: <stream:features><mechanisms
xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>PLAIN</mechanism><mechanism>X-GOOGLE-TOKEN</mec
hanism></mechanisms></stream:features>
[Oct  8 14:40:57] VERBOSE[3995] logger.c:
JABBER: googletalk OUTGOING: <auth
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'
mechanism='PLAIN'>AHRvb3RhaW5ldAAubmV0bWRw</auth>
[Oct  8 14:40:57] VERBOSE[3995] logger.c:
JABBER: googletalk INCOMING: <failure
xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><not-authorized/></failure>
[Oct  8 14:40:57] ERROR[3995] res_jabber.c: JABBER: encryption failure.
possible bad password.
[Oct  8 14:40:57] VERBOSE[3995] logger.c:
JABBER: googletalk INCOMING: </stream:stream>
[Oct  8 14:40:57] ERROR[3995] res_jabber.c: aji_act_hook was called with
out a packet
[Oct  8 14:40:58] VERBOSE[3995] logger.c:
JABBER: googletalk OUTGOING: <?xml version='1.0'?><stream:stream
xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client'
to='gmail.com' version='1.0'>
[Oct  8 14:40:58] VERBOSE[3995] logger.c:
JABBER: googletalk INCOMING: <?xml version="1.0"
encoding="UTF-8"?><stream:stream from="gmail.com" id="6DCA9605189AA9E9"
version="1.0" xmlns:stream="http://etherx.jabber.org/streams"
xmlns="jabber:client">
[Oct  8 14:40:58] VERBOSE[3995] logger.c:
JABBER: googletalk OUTGOING: <starttls
xmlns='urn:ietf:params:xml:ns:xmpp-tls'/> 

-- 
Daniel
====================================================================== 

---------------------------------------------------------------------- 
 phsultan - 10-09-07 08:48  
---------------------------------------------------------------------- 
Daniel, the credentials are not encrypted in your console debug output,
they're simply encoded (base64 form). I'll masquerade them in your initial
post, but I would advice you change them, now they've been publicly
posted.

The <unauthorized/> tag usually means that a wrong username or password
has been entered. Can you confirm you can connect with another Jabber
client (GoogleTalk, PSI, Jabbin, ...) with the credentials taken from your
jabber.conf file?

Thanks! 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-09-07 08:48  phsultan       Note Added: 0071689                          
======================================================================