FusionPBX
08de8d1f81
Remove code that caused an error.
2020-10-07 13:48:17 -06:00
FusionPBX
1abd1f1670
Change prefix from tmp_ to start_ as the variable is based on the start date.
2020-08-11 10:39:27 -06:00
agree
e2498a81de
fix extension summary date selection ( #5358 )
2020-07-16 09:54:10 -06:00
FusionPBX
fa7bb2a781
Add direction inbound for call center calls and update missed_calls.
2020-07-02 18:02:19 -06:00
FusionPBX
2d5745c283
Adjust the key string to match the value.
2020-07-02 16:48:07 -06:00
FusionPBX
0a3d809556
Add cc values to the altnernate import.
2020-07-02 16:27:54 -06:00
FusionPBX
87a7073889
If you don't have xml_cdr_lose_race permission then hide the call.
2020-06-01 16:13:40 -06:00
FusionPBX
314a217d56
Update xml_cdr.php
2020-05-05 21:32:33 -06:00
FusionPBX
b261c7e6d5
Update xml_cdr.php
2020-04-28 16:11:06 -06:00
FusionPBX
4c34f3d4be
Update xml_cdr.php
2020-04-17 12:53:50 -06:00
FusionPBX
311e647783
Update xml_cdr.php
2020-04-06 16:11:31 -06:00
Nate
365e20926f
Safari Audio Support: Call Recordings, MOH, VM Greetings & Messages and CDR audio files.
2020-03-30 20:08:45 -06:00
FusionPBX
c1b80ade27
Update xml_cdr.php
2020-03-10 10:43:58 -06:00
FusionPBX
4bc1512fec
Update xml_cdr.php
2020-02-19 12:56:16 -07:00
Nate
82367a5137
CDR: Remove domain_uuid from delete() method.
2020-02-12 14:14:16 -07:00
FusionPBX
a2b135809f
Update xml_cdr.php
2020-02-02 12:50:34 -07:00
FusionPBX
c00563efd8
Update xml_cdr.php
2020-01-31 21:28:29 -07:00
FusionPBX
729c06cb25
Update xml_cdr.php
2020-01-31 17:17:55 -07:00
FusionPBX
2185780bef
Update xml_cdr.php
2019-12-23 11:20:43 -07:00
Nate
0ebddaf2fa
CDR: List view updates.
2019-10-22 01:43:55 -06:00
FusionPBX
dd7279b6e4
Update xml_cdr.php
2019-10-07 23:49:24 -06:00
FusionPBX
a9e60d0fb8
Update xml_cdr.php
2019-10-07 15:44:05 -06:00
FusionPBX
64158012a2
Update xml_cdr.php
2019-10-07 15:32:23 -06:00
FusionPBX
05dc333ef6
Update xml_cdr.php
2019-10-07 15:28:05 -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
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
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
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
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
ea63afcc02
Update xml_cdr.php
2019-03-17 00:55:09 -06:00
FusionPBX
0d98092c9c
Update xml_cdr.php
2019-02-18 13:30:17 -07:00
FusionPBX
7b8eda9e49
Update xml_cdr.php
2018-11-23 08:03:36 -07:00
FusionPBX
6ca703693a
Update xml_cdr.php
2018-11-21 16:07:02 -07:00
FusionPBX
fabc145bd7
Update xml_cdr.php
2018-10-17 22:08:20 -06:00
FusionPBX
3bcd6b1f4f
Update xml_cdr.php
2018-10-17 15:52:15 -06:00
Luis Daniel Lucio Quiroz
07a292b552
Same logic as v_xml_cdr_import.php ( #3048 )
2018-06-09 09:30:02 -06:00
FusionPBX
ff363d921f
Update xml_cdr.php
2018-02-05 13:32:40 -07:00
FusionPBX
20219c1735
Update xml_cdr.php
2018-01-29 17:25:40 -07:00
FusionPBX
73cd5b3443
Update xml_cdr.php
2018-01-09 11:11:03 -07:00
konradSC
0170979401
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
9ee2b71ce2
Fix. Extension summary for local calls ( #2918 )
2017-11-21 09:13:58 -07:00