Vikas
2009-Apr-22 08:12 UTC
[asterisk-users] CDR feature not working properly for "failed call attempt"
Hi Asterisk Developers/users, I am facing a problem while using the cdr feature of asterisk(version asterisk1.4.24.1). Whenever I make a call using a ?*.call? file and it gets failed , it don't produce the CDR for that channel as it falls into ?OutgoingSpoolFailed? channel As there is no such channel defined for ?OutgoingSpoolfailed?.. I am using this line in extension.conf for capturing the failed atempt: exten => failed,1,Set(CDR(userfield)=${HANGUPCAUSE}) I did a bit of googling and found that this problem is coming out with Asterisk1.14.24 and it was quite OK in 1.4.17. http://forums.digium.com/viewtopic.php?t=64832&highlight=outgoingspoolfailed It seems to be bug with this new release , can any developer look into this or give any workaround so for this feature to work in failed cases also. Best Regards, Parveen Jain -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090422/3d289485/attachment-0001.htm
C. Savinovich
2009-Apr-22 12:24 UTC
[asterisk-users] CDR feature not working properly for "failed call attempt"
As far as I know, just reinstall 1.4.20, and your problem goes away. CS From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Vikas Sent: Wednesday, April 22, 2009 4:12 AM To: asterisk-users at lists.digium.com; asterisk-dev at lists.digium.com Subject: [asterisk-users] CDR feature not working properly for "failed call attempt" Hi Asterisk Developers/users, I am facing a problem while using the cdr feature of asterisk(version asterisk1.4.24.1). Whenever I make a call using a "*.call" file and it gets failed , it don't produce the CDR for that channel as it falls into "OutgoingSpoolFailed" channel As there is no such channel defined for "OutgoingSpoolfailed".. I am using this line in extension.conf for capturing the failed atempt: exten => failed,1,Set(CDR(userfield)=${HANGUPCAUSE}) I did a bit of googling and found that this problem is coming out with Asterisk1.14.24 and it was quite OK in 1.4.17. http://forums.digium.com/viewtopic.php?t=64832 <http://forums.digium.com/viewtopic.php?t=64832&highlight=outgoingspoolfaile d> &highlight=outgoingspoolfailed It seems to be bug with this new release , can any developer look into this or give any workaround so for this feature to work in failed cases also. Best Regards, Parveen Jain -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090422/97c31874/attachment.htm