[asterisk-bugs] [Asterisk 0011644]: [patch] res_jabber appears to not be working correctly in /trunk

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11644 
====================================================================== 
Reported By:                davevg
Assigned To:                phsultan
====================================================================== 
Project:                    Asterisk
Issue ID:                   11644
Category:                   Resources/res_jabber
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 94978 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             12-27-2007 15:43 CST
Last Modified:              01-01-2008 23:08 CST
====================================================================== 
Summary:                    [patch] res_jabber appears to not be working
correctly in /trunk
Description: 
I did an in-place upgrade from a recent asterisk/branch/1.4 to
asterisk/trunk.  res_jabber did work correctly with 1.4 svn.  With the
trunk version every 4 seconds I receive this error:
[Dec 27 16:25:02] WARNING[16509]: res_jabber.c:1943 aji_recv_loop: JABBER:
socket read error
Both asterisk and jabber are located on the same server (CentOS 5) in this
instance.  See Additional info for details.
====================================================================== 

---------------------------------------------------------------------- 
 elguero - 01-01-08 23:08  
---------------------------------------------------------------------- 
Yep.  You were right.  Here is my feedback.

Upon applying the patch, this is what I am getting on the console:

JABBER: asterisk INCOMING: <?xml version='1.0'?><stream:stream
xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'
id='2327307689' from='xxxxxx.xxxxxx.com' version='1.0'
xml:lang='en'><stream:features><starttls
xmlns='urn:ietf:params:xml:ns:xmpp-tls'><required/></starttls><mechanisms
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>DIGEST-MD5</mechanism><mechanism>PLAIN</mechanism></mechanisms><register
xmlns='http://jabber.org/features/iq-register'/></stream:features>

JABBER: asterisk OUTGOING: <starttls
xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>

JABBER: asterisk INCOMING: <proceed
xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>

JABBER: asterisk OUTGOING: <?xml version='1.0'?><stream:stream
xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client'
to='xxxxxx.xxxxxx.com' version='1.0'>

JABBER: asterisk INCOMING: <?xml version='1.0'?><stream:stream
xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'
id='2944940555' from='xxxxxx.xxxxxx.com' version='1.0' xml:lang='en'>

JABBER: asterisk INCOMING: <stream:features><mechanisms
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>DIGEST-MD5</mechanism><mechanism>PLAIN</mechanism></mechanisms><register
xmlns='http://jabber.org/features/iq-register'/></stream:features>

JABBER: asterisk OUTGOING: <auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl'
mechanism='PLAIN'>encodedpassword</auth>

JABBER: asterisk INCOMING: <failure
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><bad-protocol/></failure>
[Jan  1 23:55:25] ERROR[16134]: res_jabber.c:912 aji_act_hook: JABBER:
encryption failure. possible bad password.
       > JABBER: reconnecting.

JABBER: asterisk OUTGOING: <?xml version='1.0'?><stream:stream
xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client'
to='xxxxxx.xxxxxx.com' version='1.0'>
[Jan  1 23:56:19] WARNING[16134]: res_jabber.c:1926 aji_recv_loop: JABBER:
socket read error
       > JABBER: reconnecting.

I confirmed that I am using the right password by using another client to
connect to the server. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-01-08 23:08  elguero        Note Added: 0076195                          
======================================================================