[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 05:45 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 05:45  
---------------------------------------------------------------------- 
The XMPP server announces both DIGEST-MD5 and PLAIN as SASL authentication
mechanisms, and we choose DIGEST-MD5, which eventually leads to call
'iks_send' somewhere, which is bad, as elguero reported it.

Can you try the attached patch, and report back please?

Basically, we probably don't want to authenticate with SASL DIGEST-MD5
anymore. Reasons for that are that the very mechanism itself is subject to
discussion at the IETF, and that other XMPP open-source projects reported
problems when trying to implement it.

See :
http://www.ietf.org/internet-drafts/draft-melnikov-digest-to-historic-00.txt
http://ietfreport.isoc.org/ids-wg-sasl.html (latest publications of the
SASL WG mention deprecating SASL DIGEST-MD5)
http://trac.adiumx.com/ticket/8135 (Bug report for the Adium XMPP client
related to SASL DIGEST-MD5)

Michiel, I suspect Asterisk fails to reconnect when detecting a dead link,
but that's another bug that's worth opening another report. Please provide
us with as much information as you can, it looks hard to reproduce. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-28-07 05:45  phsultan       Note Added: 0076088                          
======================================================================