| Summary: | ASTERISK-06987: enumlookup function bug | ||
| Reporter: | evilbunny (evilbunny) | Labels: | |
| Date Opened: | 2006-05-17 02:26:32 | Date Closed: | 2006-05-18 14:39:51 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Related to previous bug with fixed length strings in asterisk and enumlookups. May 17 17:56:38 WARNING[10859]: enum.c:91 parse_ie: ENUM parsing failed: Wanted -118 characters, got 139 May 17 17:56:38 WARNING[10859]: enum.c:146 parse_naptr: Failed to get regexp ('') from NAPTR record - Answer ('�!^.*$!ADDRESS:CN=Fred Smith;O=XYZ Blah blah blah;OU=Special projects;STREET=12345 My Street ASTERISK-994;L=Dullsville;ST=New South Wales;C=Australia;PC=2000!') ****** ADDITIONAL INFORMATION ****** I've been unable to find the problem in the code where the string length is being set to ~118 bytes, rather then 256... Previous bug was storing 80 bytes maximum and obviously this wouldn't have been tripped as a result, but since increasing it to 256 bytes this has become an issue... | ||
| Comments: | By: evilbunny (evilbunny) 2006-05-17 02:28:06 Related to bug ASTERISK-6301 http://bugs.digium.com/view.php?id=6476 By: Kevin P. Fleming (kpfleming) 2006-05-18 14:39:51 This was caused by the use of signed length counters when unsigned should have been used. Fixed in branch 1.2 in revision 28337 and trunk in revision 28338. Thanks for the detailed report! | ||