|Summary:||ASTERISK-00189: [patch] module for posting cdr through manager interface|
|Date Opened:||2003-08-28 05:38:49||Date Closed:||2011-06-07 14:04:43|
|Environment:||Attachments:||( 0) cdr_manevent.c|
|Description:||This is a module for posting CDR's through the manager interface. I made an own module so that it is possible to turn off the cdr posting. Otherwise it can be a patch in the cdr_csv.c. But then it is not possible to turn it off...|
|Comments:||By: John Todd (jtodd) 2003-09-08 18:25:19|
Is there any documentation on this?
By: thaeger (thaeger) 2003-09-09 05:54:41
this module only send a cdr through the manager interface as event like:
TStart: 2003-09-09 20:33:09
TAnsw: 2003-09-09 20:33:23
TEnd: 2003-09-09 20:33:27
Is this documentation enough ?
The only thing is, that the uid is missing, i think. I have implemented this before the unique id was implemented :-)
By: John Todd (jtodd) 2003-10-16 04:36:47
1) In what instances would you need to submit a CDR through the manager interface? I'm just curious.
2) Do you need to re-create your patch with unique ID? How do you get unique-ID, anyway, if this is submitted by an external module? Just leave it blank?
By: jrollyson (jrollyson) 2004-01-11 01:07:10.000-0600
Why do we need this? You could easily read this data via cdr_odbc or cdr_mysql, using the event reporting in the Manager API to know when a new record should be ready.
edited on: 01-11-04 00:54
By: Olle Johansson (oej) 2004-03-21 11:03:09.000-0600
This one needs to be checked against recent additions to CDR records (userfield). Also, there are unanswered questions. Patches need sponsors that promote it, so it's important to answer people who are curious. They might be convinced by your arguments!
Jrollyson: It seems to me that this is about creating additional CDR's, not reading.