[asterisk-users] AMAFlags always"Documentation" (or 3 inastcdrmysql) even after Set(CDR(amaflags)=bill) or SetAMAFlags(bill)

[Scott Keagy]

Hi Folks,

 

I figured out how to get the AMAFlags set correctly! It was not documented anywhere I could find, and I grepped through the source code trying to track through the different function calls etc. all to no avail.

 

But... if you note in the sample.call file, they show how to do Set(CDR(userfield|r)=whatever. I tried adding this "|r" piece into amaflags, like so:

 

            Set(CDR(amaflags|r)=billing

            Set(CDR(amaflags|r)=omit

            Set(CDR(amaflags|r)=documentation

 

And it actually works! At least for 1.4beta3 which happens to be running on this box.

 

Regards,

Scott

________________________________

From: Scott Keagy 
Sent: Monday, January 08, 2007 1:28 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: RE: [asterisk-users] AMAFlags always"Documentation" (or 3 inastcdrmysql) even after Set(CDR(amaflags)=bill) or SetAMAFlags(bill)

 

Already using the CDR(userfield), and overloading it with multiple variables will make some DB operations nastier to work with (I'm a little fuzzy and vague on exactly what... something to do with sql joins?). I'm digging deeper into how much pain it really causes us on the DB/App side to see if our work-arounds there are less painful than trying to get AMAFlags to work.

 

It seems that AMAFlags are a really seldom used feature, considering that I'm asking same question that went unanswered several years ago.

 

Thanks all,

Scott

 

________________________________

From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Jon Schøpzinsky
Sent: Sunday, January 07, 2007 9:46 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: RE: [asterisk-users] AMAFlags always"Documentation" (or 3 inastcdrmysql) even after Set(CDR(amaflags)=bill) or SetAMAFlags(bill)

 

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: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] 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

 

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070113/b897704e/attachment.htm