Commit Graph

575 Commits

Author SHA1 Message Date
emaktech
7b856d49cc Modified fr-ca / fr-fr translation. (#4628) 2019-09-17 16:54:06 -06:00
FusionPBX
25f3ff2051 Update xml_cdr.php 2019-09-16 08:00:30 -06:00
Nate
fe1493fcb5 Update xml_cdr.php 2019-09-16 04:13:03 -06:00
agree
4e69f79311 default setting to remove prefix on cdr page (#4588)
* Update app_config.php

* Update app_config.php

* Update app_config.php
2019-09-14 09:52:34 -06:00
FusionPBX
fca9b7d848 Update xml_cdr.php 2019-09-13 00:36:24 -06:00
FusionPBX
76e1f2fa06 Update xml_cdr.php 2019-09-13 00:11:37 -06:00
FusionPBX
304eba3601 Update xml_cdr.php 2019-09-12 18:28:34 -06:00
Nate
0618d4eada Extension Summary: Fix Start & End Date/Time search. 2019-09-11 17:12:01 -06:00
FusionPBX
a4e8490d41 Update xml_cdr_details.php 2019-09-07 00:16:05 -06:00
FusionPBX
c7fe77b328 Update xml_cdr_inc.php 2019-09-06 18:46:50 -06:00
FusionPBX
e389a0849e Update download.php 2019-09-06 11:05:01 -06:00
FusionPBX
c2027ab6bb Update xml_cdr.php 2019-09-06 11:04:17 -06:00
FusionPBX
50d7e33fbd Update xml_cdr.php 2019-09-03 23:41:04 -06:00
FusionPBX
bfc548b5ce Update xml_cdr.php 2019-09-03 23:25:58 -06:00
FusionPBX
811b53fd47 Update xml_cdr.php 2019-09-03 23:01:19 -06:00
FusionPBX
39cf5583bb Update xml_cdr.php 2019-09-03 14:32:33 -06:00
FusionPBX
24a3028092 Update v_xml_cdr_import.php 2019-09-03 13:21:06 -06:00
FusionPBX
0597179a1c Remove the 3rd party billing system
A better way to integrate 3rd party billing is is to create own CDR import code to fit their needs.
2019-09-03 08:53:11 -06:00
FusionPBX
2cc6ae0b4a Update xml_cdr_details.php 2019-09-03 08:44:56 -06:00
Nate
cc33248ac7 CDR: Database class integration. 2019-09-03 08:29:44 -06:00
Nate
6e813908fc Update date/time picker to latest version, restoring functionality. 2019-08-22 11:04:03 -06:00
Nate
733ba98dc6 Update to Bootstrap v4.3.1, jQuery 3.4.1. Adjustments to support updates. 2019-08-20 18:15:50 -06:00
Nate
c7baaab4a9 Update to latest jQuery 1.x, in preparation to update to latest (3.x). Update jQuery UI, QR Code. Misc adjustments for compatibility. 2019-08-19 10:51:21 -06:00
FusionPBX
7973b760b6 Update xml_cdr_delete.php 2019-08-13 00:55:13 -06:00
konradSC
d0bc9034a1 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
FusionPBX
eb0d39f1f9 Update xml_cdr_inc.php 2019-06-27 09:05:06 -06:00
FusionPBX
788614f74e Update xml_cdr_inc.php 2019-06-17 23:35:48 -06:00
FusionPBX
1fcd780aa0 Update xml_cdr_inc.php 2019-06-06 21:10:20 -06:00
agree
1c935a44e5 Update xml_cdr.php (#4256) 2019-06-05 12:18:56 -06:00
agree
62ae643399 Update xml_cdr.php 2019-05-30 15:02:32 -04:00
FusionPBX
fa3d83d0a1 Update xml_cdr.php 2019-05-24 19:54:27 -06:00
FusionPBX
c2f77eb539 Update xml_cdr.php 2019-05-24 13:51:43 -06:00
FusionPBX
c23d39bbd9 Update xml_cdr.php 2019-05-24 13:45:29 -06:00
agree
a07a846d58 Update xml_cdr.php 2019-05-24 13:58:31 -04:00
agree
a2d67d8e7a Update xml_cdr_inc.php 2019-05-24 13:55:59 -04:00
FusionPBX
97587e58a2 Update xml_cdr_inc.php 2019-04-24 14:37:26 -06:00
Luis Daniel Lucio Quiroz
186d7981a2 [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
FusionPBX
7bea8d07be Update xml_cdr_statistics_inc.php 2019-04-19 11:02:58 -06:00
Luis Daniel Lucio Quiroz
10790178d1 [4.5] Fix CDR Details (#4052)
Same as 4.4
2019-04-18 11:58:34 -06:00
konradSC
7eafc693c4 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
8eda84cf55 Update xml_cdr_inc.php 2019-04-11 17:53:10 -06:00
FusionPBX
ea63afcc02 Update xml_cdr.php 2019-03-17 00:55:09 -06:00
FusionPBX
185b28cacc Update v_xml_cdr_import.php 2019-03-17 00:51:06 -06:00
FusionPBX
05d2d4ca98 Update v_xml_cdr_import.php 2019-03-17 00:49:43 -06:00
FusionPBX
3102bc9096 Update app_config.php 2019-03-16 04:18:21 -06:00
FusionPBX
e48256aee5 Update v_xml_cdr_import.php 2019-03-16 04:17:01 -06:00
FusionPBX
e6ad6ef488 Update v_xml_cdr_import.php 2019-03-14 14:57:46 -06:00
FusionPBX
978dd8342e Update xml_cdr.php 2019-03-13 20:15:19 -06:00
FusionPBX
57b742cf6f Update app_config.php 2019-03-13 20:14:32 -06:00
FusionPBX
acac0f284d Update xml_cdr_inc.php 2019-03-03 12:03:13 -07:00