[asterisk-bugs] [Asterisk 0011644]: [patch] res_jabber appears to not be working correctly in /trunk
noreply at bugs.digium.com
noreply at bugs.digium.com
Fri Jan 4 11:17:37 CST 2008
The following issue has been CLOSED
======================================================================
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: closed
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:
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 12-27-2007 15:43 CST
Last Modified: 01-04-2008 11:17 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.
======================================================================
----------------------------------------------------------------------
phsultan - 01-04-08 11:17
----------------------------------------------------------------------
Fixed in trunk, revision 96499.
Thanks!
Issue History
Date Modified Username Field Change
======================================================================
01-04-08 11:17 phsultan Note Added: 0076292
======================================================================
More information about the asterisk-bugs
mailing list