[asterisk-bugs] [Asterisk 0018177]: Certain Unicode causes res_jabber to report "Parsing failure: Invalid XML"

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Oct 20 16:52:49 CDT 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18177 
====================================================================== 
Reported By:                bigfan2010
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18177
Category:                   Resources/res_jabber
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.1 - SECURITY ONLY! Test 1.6.2 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-10-20 14:29 CDT
Last Modified:              2010-10-20 16:52 CDT
====================================================================== 
Summary:                    Certain Unicode causes res_jabber to report "Parsing
failure: Invalid XML"
Description: 
If a buddy send Hindi Unicode text like ????? ??, asterisk reports:

res_jabber.c:692 aji_recv: Parsing failure: Invalid XML

res_jabber is unable to recover from this error. All future jabber
messages received (even though they are in English) keeps failing with same
error:

res_jabber.c:692 aji_recv: Parsing failure: Invalid XML

'jabber reload' doesn't remedy the situation. 

Unicode text in Chinese like ??? gets properly parsed.

====================================================================== 

---------------------------------------------------------------------- 
 (0128249) bigfan2010 (reporter) - 2010-10-20 16:52
 https://issues.asterisk.org/view.php?id=18177#c128249 
---------------------------------------------------------------------- 
Upgrading libiksemel from version 1.3 to latest SVN trunk
(http://iksemel.googlecode.com/svn/trunk/) seems to fix the problem. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-10-20 16:52 bigfan2010     Note Added: 0128249                          
======================================================================




More information about the asterisk-bugs mailing list