80 Commits

Author	SHA1	Message	Date
Nate	a333fc6ea6	CDR: List view updates.	2019-10-22 01:43:55 -06:00
FusionPBX	c03d268aa3	Update xml_cdr.php	2019-10-07 23:49:24 -06:00
FusionPBX	12b9788a6e	Update xml_cdr.php	2019-10-07 15:44:05 -06:00
FusionPBX	738d753042	Update xml_cdr.php	2019-10-07 15:32:23 -06:00
FusionPBX	7ebfb8f0d7	Update xml_cdr.php	2019-10-07 15:28:05 -06:00
FusionPBX	8e070102e1	Update xml_cdr.php	2019-09-16 08:00:30 -06:00
Nate	231ac12381	Update xml_cdr.php	2019-09-16 04:13:03 -06:00
FusionPBX	cf146cee48	Update xml_cdr.php	2019-09-13 00:36:24 -06:00
FusionPBX	3f2615431c	Update xml_cdr.php	2019-09-13 00:11:37 -06:00
FusionPBX	3ef183169d	Update xml_cdr.php	2019-09-12 18:28:34 -06:00
Nate	ef9a443e98	Extension Summary: Fix Start & End Date/Time search.	2019-09-11 17:12:01 -06:00
FusionPBX	c85fa16f80	Update xml_cdr.php	2019-09-06 11:04:17 -06:00
FusionPBX	4716e9c615	Update xml_cdr.php	2019-09-03 23:41:04 -06:00
FusionPBX	3a65adae51	Update xml_cdr.php	2019-09-03 23:25:58 -06:00
FusionPBX	423f893c0d	Update xml_cdr.php	2019-09-03 23:01:19 -06:00
FusionPBX	6e9542d4ff	Update xml_cdr.php	2019-09-03 14:32:33 -06:00
konradSC	2a2c405528	Check for null uuid's (#4402) ... Null UUID's are not very kind. They will sneak into your CDR's when you aren't looking and break an otherwise very nice database INSERT statement. We cannot tolerate that sort of behavior.	2019-07-31 16:00:20 -06:00
Luis Daniel Lucio Quiroz	67043c6ad8	[4.5] fixes null record_name and record_path fields in v_xml_cdr (#4053) ... * record_name verification * record_name better verification when you carry on some updates from 4.0 to 4.2 and then 4.4, old dialplans do not create all the variables, record_session is created, but record_name (and record_path) are not null, set and lenght zero, "" in otherwords. Then, in the db record, record_name and record_path are empty, regardless if the recording file exists. Therefore, they are not shown in the CDR app. This fixes this issue.	2019-04-20 17:05:40 -06:00
konradSC	7fe9794191	Bug fix: No answer_stamp in CDR (#4049) ... * Bug fix: No answer_stamp in CDR Here's a fun little bug that took me a longer than it should have to figure out. When a person make a call and then cancels the request there is no "answer_stamp" written to the CDR. Because of this, v_call_recordings.call_recording_name gets imported as NULL. This causes all the canceled calls to show up in the Call Recordings app first in the list and with no date set. * Update xml_cdr.php * Update v_xml_cdr_import.php	2019-04-11 18:00:11 -06:00
FusionPBX	75182f2ee1	Update xml_cdr.php	2019-03-17 00:55:09 -06:00
FusionPBX	4972776d73	Update xml_cdr.php	2019-02-18 13:30:17 -07:00
FusionPBX	e29dcbeb37	Update xml_cdr.php	2018-11-23 08:03:36 -07:00
FusionPBX	7eab2ffb06	Update xml_cdr.php	2018-11-21 16:07:02 -07:00
FusionPBX	d58d9914cc	Update xml_cdr.php	2018-10-17 22:08:20 -06:00
FusionPBX	3a7fee84c8	Update xml_cdr.php	2018-10-17 15:52:15 -06:00
Luis Daniel Lucio Quiroz	483cf5542d	Same logic as v_xml_cdr_import.php (#3048)	2018-06-09 09:30:02 -06:00
FusionPBX	c2f8733728	Update xml_cdr.php	2018-02-05 13:32:40 -07:00
FusionPBX	3cbc25d669	Update xml_cdr.php	2018-01-29 17:25:40 -07:00
FusionPBX	4046a8ab34	Update xml_cdr.php	2018-01-09 11:11:03 -07:00
konradSC	fa58a7ed33	Update xml_cdr.php (#2942) ... Add check for duplicate call records. Duplicate records will cause the entire db insert to fail. I have tested this with the /app/xml_cdr/xml_cdr_import.php method for cdr insertion.	2018-01-09 11:01:10 -07:00
Alexey Melnichuk	cc22f35e74	Fix. Extension summary for local calls (#2918)	2017-11-21 09:13:58 -07:00
konradSC	49417a105a	Bug Fix - Match correct database column names (#2908) ... call_recording_name & call_recording_path are the correct values.	2017-11-14 22:02:08 -07:00
konradSC	9fb207c16b	More ways of adding recordings to CDR's (#2904) ... This grabs a recording if started by bind_digit_action "*2" or by "nolocal:api_on_answer=uuid_record ${uuid} start ${recordings_dir}/${domain_name}/archive/${strftime(%Y)}/${strftime(%b)}/${strftime(%d)}/${uuid}.${record_ext}".	2017-11-08 09:51:53 -07:00
FusionPBX	20b5f61ae7	Update xml_cdr.php	2017-11-05 11:32:05 -07:00
konradSC	9d1f16fe64	Bug fix for caller_destination populating CDR's (#2902)	2017-11-02 21:57:36 -06:00
FusionPBX	9b9c3950c0	Update xml_cdr.php	2017-10-20 18:04:07 -06:00
FusionPBX	65dd10e433	Update xml_cdr.php	2017-10-20 17:54:49 -06:00
FusionPBX	e7038b0ed4	Update xml_cdr.php	2017-10-20 16:55:19 -06:00
FusionPBX	7a967d8d3f	Update xml_cdr.php	2017-10-15 14:26:06 -06:00
FusionPBX	66c90568a0	Update xml_cdr.php	2017-10-15 11:53:10 -06:00
FusionPBX	760eea11af	Update xml_cdr.php	2017-10-15 11:35:55 -06:00
FusionPBX	a45b9ffa78	Update xml_cdr.php	2017-10-05 12:52:08 -06:00
FusionPBX	1e4aeace11	Update xml_cdr.php	2017-09-22 19:24:40 -06:00
FusionPBX	4b7c529336	Update xml_cdr.php	2017-09-22 19:04:18 -06:00
FusionPBX	5d07761381	Update xml_cdr.php	2017-09-14 17:27:38 -05:00
FusionPBX	dcdaec1850	Update xml_cdr.php	2017-09-11 01:27:37 -05:00
FusionPBX	1aa94e1e2c	Update xml_cdr.php	2017-09-11 01:23:41 -05:00
FusionPBX	179df1c064	Update xml_cdr.php	2017-09-10 13:14:42 -06:00
FusionPBX	a9fbc3e9c7	Update xml_cdr.php	2017-09-10 11:53:40 -06:00
FusionPBX	116ba64fcb	Update xml_cdr.php	2017-06-21 23:46:17 -06:00