[asterisk-dev] Channel Event Logging and newcdr svn branch

[Russell Bryant]

On Jun 5, 2009, at 1:40 AM, Alexander Krylowsky wrote:

> On Thu, 2009-06-04 17:51:28 -0500, Matthew Nicholson wrote:
>> On Thu, 2009-06-04 at 18:30 +0400, Alexander Krylowsky wrote:
>>
>>> 1. with CEL logging enabled ("enable=yes" in cel.conf general  
>>> section)
>>> a lot of astobj2.c warnings on every cel event appears on console:
>>>
>>> ERROR[9355]: astobj2.c:116 INTERNAL_OBJ: bad magic number 0x3b5  
>>> for 0xb78f3a70
>>> ERROR[9355]: astobj2.c:116 INTERNAL_OBJ: bad magic number 0x3b5  
>>> for 0xb78f3a70
>>> ERROR[9355]: astobj2.c:116 INTERNAL_OBJ: bad magic number 0x3b5  
>>> for 0xb78f3a70
>>> ERROR[9355]: astobj2.c:116 INTERNAL_OBJ: bad magic number 0x3b5  
>>> for 0xb78f3a70
>>> .........
>>>
>>> Looks like it doesn't affect normal asterisk operation. This bug  
>>> is similar to #14974.
>>
>> I was not able to reproduce this.  Please give me some more  
>> information
>> about your setup.
>
> It is cel_custom issue.
> Make sure you have ("enable=yes" in cel.conf general section) and
> cel_custom.conf with uncommented mappings section and Master.csv  
> entry.
> Everything works fine without cel_custom.conf.


Thanks for the info.  I don't have time to fix it at the moment, but  
for the record, the problem is the implementation of  
ast_dummy_channel_alloc().  It does not reflect the changes made to  
make ast_channel an astobj2 object.

Really, it would be nice to just get rid of requiring a channel for  
doing substitution.  Having to allocate these temporary channels all  
over the place for doing this is just silly ...

--
Russell Bryant
Digium, Inc. | Senior Software Engineer, Open Source Team Lead
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: www.digium.com & www.asterisk.org