Commit Graph

6127 Commits

Author SHA1 Message Date
FusionPBX 50a5893425
Update app_config.php 2019-03-24 08:57:10 -06:00
FusionPBX fe7fd158fb
Update app_config.php 2019-03-24 08:30:34 -06:00
FusionPBX 3730a8fe3e
Update app_config.php 2019-03-24 08:28:16 -06:00
FusionPBX 2babe1d322
Update app_config.php 2019-03-24 08:26:29 -06:00
FusionPBX e12e31a1d6
Update app_config.php 2019-03-24 08:21:26 -06:00
FusionPBX 913fc9dfa5
Update app_config.php 2019-03-24 08:07:38 -06:00
FusionPBX 0a68b4472f
Update app_config.php 2019-03-24 08:06:01 -06:00
FusionPBX a6b30f6245
Update app_config.php 2019-03-24 08:04:45 -06:00
FusionPBX de797d480b
Update app_config.php 2019-03-24 08:02:01 -06:00
FusionPBX 9e8677d3e6
Update app_config.php 2019-03-24 07:56:12 -06:00
FusionPBX 2819f615f5
Update app_config.php 2019-03-24 07:54:22 -06:00
FusionPBX a783b1b1b5
Update app_config.php 2019-03-23 22:37:49 -06:00
FusionPBX d30fcbb6d1
Update follow_me.php 2019-03-21 21:06:07 -06:00
FusionPBX 9e326e8a39
Update follow_me.php 2019-03-21 20:05:48 -06:00
FusionPBX 9b595ebc90
Update follow_me.php 2019-03-21 16:56:00 -06:00
FusionPBX 78014385c5
Update call_block_edit.php 2019-03-21 14:06:42 -06:00
FusionPBX b231c1ac81
Update app_config.php 2019-03-21 14:04:16 -06:00
Len 4bcf09c306 Update app_config.php (#4039) 2019-03-20 08:23:58 -06:00
FusionPBX a22a7e1bac
Update 400_recordings.xml 2019-03-19 17:29:57 -06:00
FusionPBX bcfc97a978
Update app_config.php 2019-03-18 09:37:30 -06:00
FusionPBX 75182f2ee1
Update xml_cdr.php 2019-03-17 00:55:09 -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 79e42aafef
Update app_config.php 2019-03-16 04:18:21 -06:00
FusionPBX bb5e79572e
Update v_xml_cdr_import.php 2019-03-16 04:17:01 -06:00
FusionPBX 47b0b0da6e
Update call_center_agent_edit.php 2019-03-15 00:02:20 -06:00
FusionPBX 4a9826866b
Update fax_edit.php 2019-03-15 00:01:21 -06:00
FusionPBX 3f428583ef
Update app_config.php 2019-03-14 23:54:59 -06:00
FusionPBX 4924676825
Update app_defaults.php 2019-03-14 23:53:15 -06:00
FusionPBX 9cebeb75b7
Update 400_recordings.xml 2019-03-14 23:42:09 -06:00
FusionPBX e8cd217b58
Update v_xml_cdr_import.php 2019-03-14 14:57:46 -06:00
Nate 4bc43fb60e Password Reset: Add email message to Email Templates. 2019-03-13 23:30:39 -06:00
FusionPBX db6f070a19
Update xml_cdr.php 2019-03-13 20:15:19 -06:00
FusionPBX e6a790da96
Update app_config.php 2019-03-13 20:14:32 -06:00
FusionPBX 14951a48cc
Update app_config.php 2019-03-12 08:23:11 -06:00
FusionPBX c25db66ee5
Update gateway_delete.php 2019-03-08 14:13:16 -07:00
FusionPBX 8737af841a
Update destination_edit.php 2019-03-08 08:48:38 -07:00
FusionPBX a213aa7a20
Update gateway_delete.php 2019-03-07 16:44:09 -07:00
FusionPBX 2585949b3d
Update app_defaults.php 2019-03-07 16:37:47 -07:00
Nate ca74e8591c 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 8be372fd6f Update app_config.php (#4009)
fix duplicate uuid
2019-03-05 20:00:00 -07:00
FusionPBX a478765738
Update app_config.php 2019-03-05 18:34:52 -07:00
FusionPBX 9b2b93c900
Update app_config.php 2019-03-05 18:17:42 -07:00
ednt e3ce695f92 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 ddc46f8901
Update follow_me.php 2019-03-04 13:03:31 -07:00
FusionPBX ca0ba0ec39
Delete 520_follow_me_bridge.xml 2019-03-03 15:23:14 -07:00
FusionPBX 2dc5c30ffd
Update xml_cdr_inc.php 2019-03-03 12:03:13 -07:00
emaktech f30457b12b 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 db13ae9cf0
Update contact_edit.php 2019-03-01 06:08:47 -07:00
Nate 6470afb3d0 Restore Login Reset Password functionality, adjust default SMTP debug level. 2019-02-28 17:32:27 -07:00