Hello
Why not use the CDR(userfield) field instead. You can set that to any integer of your liking, and use that to identify the type of call. Jon From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Keagy Sent: 8. januar 2007 06:06 To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: [asterisk-users] AMAFlags always"Documentation" (or 3 in astcdrmysql) even after Set(CDR(amaflags)=bill) or SetAMAFlags(bill) Is anyone out there using AMAFlags? I'd like to set this field as a marker to distinguish different types of calls in CDRs, but can't seem to make it respond to the documented commands Set(CDR(amaflags)=bill) or SetAMAFlags(bill). I've googled this issue, seen others have had this problem with IAX, with different DB drivers for CDR records, etc. I'm using SIP and LOCAL channels, asterisk-1.4beta2 release (I don't think upgrading to current release will fix this problem, it's been around for years based on trouble reports), both text .csv and mysql astcdr.cdr types. Seems like a problem with basic AMAflags support in CDR. They always show up as DOCUMENTATION in the .csv text file, and they always show up as '3' in mysql. I hurt my brain trying to follow the layers of indirection in the source code for where this is actually set. With verbosity turned on in asterisk console I can see the SetAMAFlags function being run. Any tips, tricks, or pointers in the right direction? Thanks, Scott
_______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
