[asterisk-bugs] [Asterisk 0011644]: 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:                     assigned
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:              12-28-2007 10:34 CST
====================================================================== 
Summary:                    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.
====================================================================== 

---------------------------------------------------------------------- 
 phsultan - 12-28-07 10:34  
---------------------------------------------------------------------- 
elguero: you mean SASL DIGEST-MD5 rather than SSL in your note, right?

SSL/TLS is used to protect the network connection, SASL (PLAIN,
DIGEST-MD5, ..) refers to the authentication mechanism.

If we use SASL PLAIN as the authentication mechanism, we *must* protect
the network connection with SSL/TLS, in order to safely authenticate to the
XMPP server. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-28-07 10:34  phsultan       Note Added: 0076106                          
======================================================================