dbxe
/
fusionpbx
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
14,410 Commits 3 Branches 10 Tags 224 MiB
Commit Graph

112 Commits

Author SHA1 Message Date
FusionPBX 8ca4d87bb9
Update v_xml_cdr_import.php 2019-09-03 13:21:06 -06:00
FusionPBX c4548c0c06
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
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 cd6e5fe791
Update v_xml_cdr_import.php 2019-03-17 00:51:06 -06:00
FusionPBX 4461a5ce6f
Update v_xml_cdr_import.php 2019-03-17 00:49:43 -06:00
FusionPBX bb5e79572e
Update v_xml_cdr_import.php 2019-03-16 04:17:01 -06:00
FusionPBX e8cd217b58
Update v_xml_cdr_import.php 2019-03-14 14:57:46 -06:00
FusionPBX ca4ee3a6c3
Update v_xml_cdr_import.php 2018-10-24 10:51:56 -06:00
FusionPBX 677978afa1
Update v_xml_cdr_import.php 2018-10-17 22:03:31 -06:00
FusionPBX cbd2625bc0
Update v_xml_cdr_import.php 2018-10-17 15:45:23 -06:00
FusionPBX 92e9c7e5eb
Update v_xml_cdr_import.php 2018-10-17 15:41:14 -06:00
FusionPBX f6b3a6f035
Update v_xml_cdr_import.php 2018-07-02 21:01:37 -06:00
FusionPBX 8aca3d5728
Update v_xml_cdr_import.php 2018-05-19 16:59:24 -06:00
FusionPBX 6e776a16b0
Update v_xml_cdr_import.php 2018-05-09 16:48:20 -06:00
FusionPBX 55cdc99eb3
Update v_xml_cdr_import.php 2018-04-22 11:51:36 -06:00
FusionPBX d7032b6c7f
Update v_xml_cdr_import.php 2018-04-18 16:29:57 -06:00
FusionPBX 5e3ce95ca8
Update v_xml_cdr_import.php 2018-04-18 11:52:45 -06:00
FusionPBX 6fedb08d8c
Update v_xml_cdr_import.php 2018-03-15 23:21:56 -06:00
FusionPBX 9ba1fcb084
Update v_xml_cdr_import.php 2018-02-23 08:40:25 -07:00
FusionPBX 7e2d5a3b6d
Update v_xml_cdr_import.php 2018-02-13 10:17:14 -07:00
FusionPBX ef0099c6bb
Update v_xml_cdr_import.php 2018-02-05 13:26:30 -07:00
FusionPBX c792a30ec4
Update v_xml_cdr_import.php 2018-01-29 17:30:12 -07:00
FusionPBX 67a0f9eb07 Update v_xml_cdr_import.php 2017-10-20 18:02:58 -06:00
FusionPBX 770f412618 Update v_xml_cdr_import.php 2017-10-20 17:57:57 -06:00
FusionPBX 16972b0dbf Update v_xml_cdr_import.php 2017-10-20 16:46:29 -06:00
FusionPBX d623eae97c Update v_xml_cdr_import.php 2017-10-15 11:50:09 -06:00
FusionPBX a7cde16bd0 Update v_xml_cdr_import.php 2017-10-15 11:38:49 -06:00
FusionPBX d25c639d8f Update v_xml_cdr_import.php 2017-10-05 12:51:13 -06:00
FusionPBX 90ae681fb7 Update v_xml_cdr_import.php 2017-09-22 19:23:39 -06:00
FusionPBX 67f78dcb1a Update v_xml_cdr_import.php 2017-09-22 19:05:24 -06:00
FusionPBX e2631f20a5 Update v_xml_cdr_import.php 2017-09-14 17:25:51 -05:00
FusionPBX 3b38213791 Update v_xml_cdr_import.php 2017-09-11 02:46:50 -05:00
FusionPBX fea6521e01 Update v_xml_cdr_import.php 2017-09-11 01:34:31 -05:00
FusionPBX 962d624459 Update v_xml_cdr_import.php 2017-09-11 01:26:58 -05:00
FusionPBX 54aa50c193 Update v_xml_cdr_import.php 2017-09-10 13:13:18 -06:00
FusionPBX 2e2f8e43fe Update v_xml_cdr_import.php 2017-09-10 11:54:24 -06:00
FusionPBX 463a971275 Update v_xml_cdr_import.php 2017-06-21 19:34:06 -06:00
Alexey Melnichuk 5d43f73134 Add. Handle `b` legs in CDR. (#2626) 
* Add. Handle `b` legs in CDR.

CDR list/statistic by default handle only `a` legs.
So it prevent display wrong result when b-leg turn on.
Add ability to write to db `b` legs only for specific call directions.

To be able see b-legs in CDR need set xml_cdr_b_leg permission.
To add specific call direction to filter need add element to `cdr/b_leg/array` in default/domain settings.

* Add. `b_leg` to defalut settings.
 2017-06-02 22:31:20 -06:00
FusionPBX d1754cc3d2 Update v_xml_cdr_import.php 2017-05-29 15:14:38 -06:00
FusionPBX 2d1f89fbba Update v_xml_cdr_import.php 2017-05-29 10:48:30 -06:00
FusionPBX 335084e9d8 Update v_xml_cdr_import.php 2016-12-22 21:10:22 -07:00
FusionPBX d57c9dcafd Update v_xml_cdr_import.php 2016-12-22 20:50:09 -07:00
FusionPBX b667a78d4a Update v_xml_cdr_import.php 2016-12-21 14:14:45 -07:00
FusionPBX 6d722bd34f Update v_xml_cdr_import.php 2016-09-03 20:48:27 -06:00
markjcrane 6f2601e32a Use FreeSWITCH to run mkdir so it inherits its own user and group permissions. 2016-06-28 15:18:40 -06:00
markjcrane d56b8ab6a1 If last_sent_callee_id_number is set use it as the destination_number. 2016-06-01 16:45:50 -06:00
Mafoo 59ddf92f1b I got the permissions wrong (#1616) 
it should have been in octal mod (leading 0)
also updated the fax application as it needs the stickygid too
 2016-05-26 05:55:46 -06:00
Mafoo a8b667cd0b Added sticky GID permissions (#1615) 2016-05-25 21:51:41 -06:00
mafoo ce8137b407 WhitespaceClean-app/xml_cdr 
whitespace pass over files
for reference regex that was used s/[ \t]+(\r?\n)/\1/
 2016-03-11 11:54:18 +00:00