[asterisk-bugs] [Asterisk 0014069]: too small reponse for dbget through agi

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=14069 
====================================================================== 
Reported By:                evandro
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   14069
Category:                   Resources/res_agi
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.4.21.2 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2008-12-12 11:22 CST
Last Modified:              2009-01-08 16:08 CST
====================================================================== 
Summary:                    too small reponse for dbget through agi
Description: 
I'm using agi to get persistent members in queues, but the response in some
cases come incomplete, when have too many members in queue. I changed the
size of char tmp variable from 256 to 1024 on res/res_agi.c file, and fixed
this issue in a sample test. But I want to know, this change can cause
problems?? 
I also would suggest that this changed to be applied in asterisk and
asterisk CLI. 
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-08 16:08 svnbot         Status                   acknowledged =>
resolved
2009-01-08 16:08 svnbot         Resolution               open => fixed       
======================================================================