Subject: [asterisk-dev] The Trouble with CDR's...!
Jonathan k. Creasy
jonathan at bluegrass.net
Tue Dec 19 07:35:29 MST 2006
> -----Original Message-----
> From: asterisk-dev-bounces at lists.digium.com [mailto:asterisk-dev-
> bounces at lists.digium.com] On Behalf Of Paul Hewlett
> Sent: Tuesday, December 19, 2006 9:13 AM
> To: asterisk-dev at lists.digium.com
> Subject: Re: Subject: [asterisk-dev] The Trouble with CDR's...!
>
> On Tuesday 19 December 2006 15:42, Jonathan k. Creasy wrote:
>
> >
> > I would like to see the ability to have more user fields.
Userfield1,
> > Userfield2, Userfieldn, etc.
> >
> > Possibly be able to define a field in the table and use it in the
> > dialplan like the user field. In the example above he would create a
> > field called "ServerID" and then in the dialplan he could reference
> > CDR(ServerID) and it would know since that was not a defined CDR
field
> > it must go with the field that has that name in the table, if no
such
> > field exists then just ignore it.
> >
>
> This is already available in 1.2
>
> exten => s,n,Set(CDR(myfield)=myvalue)
> exten => s,n,Noop(Myfield=${CDR(myfield)})
>
> You can then make your own CDR records by editing cdr-custom.conf
>
>
> Paul
> --
> Paul Hewlett Technical Director
> Global Call Center Solutions Ltd, 2nd Floor, Milnerton Mall
> Cnr Loxton & Koeberg Roads, 7435 Milnerton
> paul at gccs.co.za www.gccs.co.za
> Tel: +27 86 111 3433 Fax: +27 86 111 3520 Cel: +27 84 420 9282
> Gizmo: 1 747 659 6171
>
All I have to say is wow...I completely missed that. I have several
fields in the database and a creative way of getting data into them...oh
well..i'm off to set that straight. :)
More information about the asterisk-dev
mailing list