Commit Graph

6108 Commits

Author SHA1 Message Date
FusionPBX
dec6b950f9 Update app_config.php 2019-03-24 08:57:10 -06:00
FusionPBX
dc8a336103 Update app_config.php 2019-03-24 08:30:34 -06:00
FusionPBX
0ff1e70aaa Update app_config.php 2019-03-24 08:28:16 -06:00
FusionPBX
15613046a5 Update app_config.php 2019-03-24 08:26:29 -06:00
FusionPBX
862528db2b Update app_config.php 2019-03-24 08:21:26 -06:00
FusionPBX
1db892de32 Update app_config.php 2019-03-24 08:07:38 -06:00
FusionPBX
312ce83fd5 Update app_config.php 2019-03-24 08:06:01 -06:00
FusionPBX
0f8b1a9ed2 Update app_config.php 2019-03-24 08:04:45 -06:00
FusionPBX
1a1cbd2dfb Update app_config.php 2019-03-24 08:02:01 -06:00
FusionPBX
cc2f995331 Update app_config.php 2019-03-24 07:56:12 -06:00
FusionPBX
0e192bd2fe Update app_config.php 2019-03-24 07:54:22 -06:00
FusionPBX
8fa8729bbb Update app_config.php 2019-03-23 22:37:49 -06:00
FusionPBX
d527e45959 Update follow_me.php 2019-03-21 21:06:07 -06:00
FusionPBX
49797b36d8 Update follow_me.php 2019-03-21 20:05:48 -06:00
FusionPBX
4472f99bab Update follow_me.php 2019-03-21 16:56:00 -06:00
FusionPBX
4cef72bf89 Update call_block_edit.php 2019-03-21 14:06:42 -06:00
FusionPBX
3f6a57c783 Update app_config.php 2019-03-21 14:04:16 -06:00
Len
33a7164f68 Update app_config.php (#4039) 2019-03-20 08:23:58 -06:00
FusionPBX
f6188357b1 Update 400_recordings.xml 2019-03-19 17:29:57 -06:00
FusionPBX
616ad4ab8d Update app_config.php 2019-03-18 09:37:30 -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
09eece9555 Update call_center_agent_edit.php 2019-03-15 00:02:20 -06:00
FusionPBX
a0a498fc01 Update fax_edit.php 2019-03-15 00:01:21 -06:00
FusionPBX
097294c0d1 Update app_config.php 2019-03-14 23:54:59 -06:00
FusionPBX
06b040c42f Update app_defaults.php 2019-03-14 23:53:15 -06:00
FusionPBX
9076f44d3a Update 400_recordings.xml 2019-03-14 23:42:09 -06:00
FusionPBX
e6ad6ef488 Update v_xml_cdr_import.php 2019-03-14 14:57:46 -06:00
Nate
a35f618ec2 Password Reset: Add email message to Email Templates. 2019-03-13 23:30:39 -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
b470ec914e Update app_config.php 2019-03-12 08:23:11 -06:00
FusionPBX
0bc846df56 Update gateway_delete.php 2019-03-08 14:13:16 -07:00
FusionPBX
cf41c6a093 Update destination_edit.php 2019-03-08 08:48:38 -07:00
FusionPBX
3841c6f51c Update gateway_delete.php 2019-03-07 16:44:09 -07:00
FusionPBX
7ba3fd49c5 Update app_defaults.php 2019-03-07 16:37:47 -07:00
Nate
06a0fa7235 User Edit: Only list Contacts not already assigned to a User. Contact Edit: Display button to User the Contact is assigned to (if any). 2019-03-06 19:54:12 -07:00
Len
ed9d23658e Update app_config.php (#4009)
fix duplicate uuid
2019-03-05 20:00:00 -07:00
FusionPBX
2395ec6f1f Update app_config.php 2019-03-05 18:34:52 -07:00
FusionPBX
6dde7f362f Update app_config.php 2019-03-05 18:17:42 -07:00
ednt
b1faf1cf83 Bug option list and with multiple registartions. (#4012)
de-ring was not in the option list.

If multiple devices are registered with the same extension, only on device was ringing. (And this was not the device in front of you :) )
The Call UUID was 'duplicated'
The fix is to remove the origination_uuid. Then all devices rings simultaniously.
2019-03-05 12:19:10 -07:00
FusionPBX
28c8c69843 Update follow_me.php 2019-03-04 13:03:31 -07:00
FusionPBX
bd18ccb7e6 Delete 520_follow_me_bridge.xml 2019-03-03 15:23:14 -07:00
FusionPBX
acac0f284d Update xml_cdr_inc.php 2019-03-03 12:03:13 -07:00
emaktech
a5ff016ef5 Retrieve gateway names with variables and failover (#4004)
Previously, if a bridge statement was written with prepended variables to be passed, the gateway name would not be parsed and replaced. Additionally, if multiple bridges were used in failover in a single bridge statement separated by a pipe, only the first would be parsed and replaced.

I noticed this after upgrade to FreeSWITCH 1.8.5 (from 1.6.20) which changed failover behavior with multiple separate bridge statements. When network returns 486 BUSY, it will proceed to second bridge statement, initiating a second call. To allow failover and not have this behavior, you must write a single statement and separate your failover bridges with a pipe, this change allows the UI to show all gateway names on the line once saved.

Examples:
{fax_use_ecm=on}sofia/gateway/99b1234c-667c-4b31-9d2f-31d4f396abfa/$1
=> {fax_use_ecm=on}sofia/gateway/Gateway_Name/$1

sofia/gateway/0e70e123-00fd-4f0c-b525-bc7f6283cfa1/$1|sofia/gateway/99b1234c-667c-4b31-9d2f-31d4f396abfa/1$1
=> sofia/gateway/Gateway_One/$1|sofia/gateway/Gateway_Two/1$1
2019-03-03 11:10:15 -07:00
FusionPBX
9a9bbac7f1 Update contact_edit.php 2019-03-01 06:08:47 -07:00
Nate
36b32599f1 Restore Login Reset Password functionality, adjust default SMTP debug level. 2019-02-28 17:32:27 -07:00