[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:07 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.
====================================================================== 

---------------------------------------------------------------------- 
 elguero - 12-28-07 10:07  
---------------------------------------------------------------------- 
I too will try the patch later and report back.

The XMPP server I am using is ejabberd.  Currently, I have it set to only
accept SSL but that can be changed (since our server is internal anyways)
as you have pointed out some very good reasons for not supporting it for
the time being. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-28-07 10:07  elguero        Note Added: 0076104                          
======================================================================