FusionPBX
3ef8a0ae12
Update v_xml_cdr_import.php
2019-12-23 11:23:53 -07:00
FusionPBX
71479d69fc
Update v_xml_cdr_import.php
2019-12-23 11:17:34 -07:00
FusionPBX
11f80ba1bf
Update v_xml_cdr_import.php
2019-10-07 23:43:02 -06:00
FusionPBX
1c0368cb5f
Update v_xml_cdr_import.php
2019-10-07 23:37:53 -06:00
FusionPBX
cc6a5758fb
Update v_xml_cdr_import.php
2019-10-07 14:55:20 -06:00
FusionPBX
a1164b4999
Update v_xml_cdr_import.php
2019-10-07 13:17:21 -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
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
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
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
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
1a40dfe9ee
Update v_xml_cdr_import.php
2018-10-24 10:51:56 -06:00
FusionPBX
32f794fb3f
Update v_xml_cdr_import.php
2018-10-17 22:03:31 -06:00
FusionPBX
711e008b3a
Update v_xml_cdr_import.php
2018-10-17 15:45:23 -06:00
FusionPBX
dc2925e922
Update v_xml_cdr_import.php
2018-10-17 15:41:14 -06:00
FusionPBX
9eb861e971
Update v_xml_cdr_import.php
2018-07-02 21:01:37 -06:00
FusionPBX
6a46b541dc
Update v_xml_cdr_import.php
2018-05-19 16:59:24 -06:00
FusionPBX
eaea0d53c5
Update v_xml_cdr_import.php
2018-05-09 16:48:20 -06:00
FusionPBX
910ba8fd08
Update v_xml_cdr_import.php
2018-04-22 11:51:36 -06:00
FusionPBX
093f9d3f0a
Update v_xml_cdr_import.php
2018-04-18 16:29:57 -06:00
FusionPBX
37a83627ce
Update v_xml_cdr_import.php
2018-04-18 11:52:45 -06:00
FusionPBX
fcda5def50
Update v_xml_cdr_import.php
2018-03-15 23:21:56 -06:00
FusionPBX
14155c1ded
Update v_xml_cdr_import.php
2018-02-23 08:40:25 -07:00
FusionPBX
11bfa81edd
Update v_xml_cdr_import.php
2018-02-13 10:17:14 -07:00
FusionPBX
e6a5299593
Update v_xml_cdr_import.php
2018-02-05 13:26:30 -07:00
FusionPBX
0703fce4d2
Update v_xml_cdr_import.php
2018-01-29 17:30:12 -07:00
FusionPBX
8e4fb530fa
Update v_xml_cdr_import.php
2017-10-20 18:02:58 -06:00
FusionPBX
23428c82ee
Update v_xml_cdr_import.php
2017-10-20 17:57:57 -06:00
FusionPBX
5497ac121e
Update v_xml_cdr_import.php
2017-10-20 16:46:29 -06:00
FusionPBX
27dd6fec90
Update v_xml_cdr_import.php
2017-10-15 11:50:09 -06:00
FusionPBX
ed9719d821
Update v_xml_cdr_import.php
2017-10-15 11:38:49 -06:00
FusionPBX
70c645810a
Update v_xml_cdr_import.php
2017-10-05 12:51:13 -06:00
FusionPBX
62eb855819
Update v_xml_cdr_import.php
2017-09-22 19:23:39 -06:00
FusionPBX
0c8f962488
Update v_xml_cdr_import.php
2017-09-22 19:05:24 -06:00
FusionPBX
d6e382d5c4
Update v_xml_cdr_import.php
2017-09-14 17:25:51 -05:00
FusionPBX
539944a527
Update v_xml_cdr_import.php
2017-09-11 02:46:50 -05:00
FusionPBX
8cfef14a4b
Update v_xml_cdr_import.php
2017-09-11 01:34:31 -05:00
FusionPBX
bf1d52d4e8
Update v_xml_cdr_import.php
2017-09-11 01:26:58 -05:00
FusionPBX
449bad348e
Update v_xml_cdr_import.php
2017-09-10 13:13:18 -06:00
FusionPBX
a922a3532a
Update v_xml_cdr_import.php
2017-09-10 11:54:24 -06:00
FusionPBX
b0bef2fc80
Update v_xml_cdr_import.php
2017-06-21 19:34:06 -06:00
Alexey Melnichuk
9050da03cc
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
52bb56fdf2
Update v_xml_cdr_import.php
2017-05-29 15:14:38 -06:00
FusionPBX
a787715900
Update v_xml_cdr_import.php
2017-05-29 10:48:30 -06:00
FusionPBX
06f8010854
Update v_xml_cdr_import.php
2016-12-22 21:10:22 -07:00
FusionPBX
0c600c9df8
Update v_xml_cdr_import.php
2016-12-22 20:50:09 -07:00
FusionPBX
ea4ef9b9c4
Update v_xml_cdr_import.php
2016-12-21 14:14:45 -07:00