dbxe/fusionpbx
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
13,979 Commits 3 Branches 10 Tags
8a6eecd20aea22897e5df2a3ef82abc461a24eea
Commit Graph
13979 Commits
This Branch
This Branch
All Branches
Author SHA1 Message Date
Nate 8a6eecd20a Extensions: Fix paging. 2019-09-10 12:54:06 -06:00
Nate 86ac504ee0 Contacts: Fix QR code. 2019-09-10 12:08:54 -06:00
Nate e73d84118c Bridges: Fix Show All, Use languages for Enabled label. 2019-09-10 09:24:59 -06:00
FusionPBX 88c8c7e03d Update device_profile_copy.php 2019-09-10 09:07:45 -06:00
FusionPBX 2e41862b4c Update dialplan_xml.php 2019-09-10 08:23:24 -06:00
Nate 8fdb26e3f1 Destinations: Make show all and search persistent when switching type/direction. 2019-09-10 08:15:12 -06:00
FusionPBX f7ce68a202 Update destination_edit.php 2019-09-10 08:06:34 -06:00
Nate 95bc79c039 Recordings: Add data size when displaying base64 recordings, other misc minor issues. Phrases: Removed escaping on Recording options in select. 2019-09-10 07:59:37 -06:00
frytimo 8068a89a3a Update fax_emails.php (#4529) 
Change $array to $result
 2019-09-09 19:10:22 -06:00
konradSC cf9d049292 Calculate timeout for Follow-me (#4528) 
* Calculate timeout for Follow-me

Need to calculate the timeout for Enterprise RG members that have extensions with follow-me. 

The RG timeout should always take precedence over a follow-me timeout value. What we do is take the delay of the follow-me destination and subtract that from the ring group timeout to give us the total timeout of the destination. 

Example: 
RG 1: x1000 (Delay=0, Timeout=10)
RG 2: x2000 (Delay=10, Timeout=10)

x2000 has follow-me enabled
FM 1: x2000 (Delay=0, Timeout=15)
FM 2: x3000 (Delay=5, Timeout=20)

In this example we would want x2000 ring for 10 seconds and x3000 to ring for 5 seconds. 

What if we changed this... FM 2: x3000 (Delay 15, Timeout=20)

In this example we wouldn't want x3000 to ring at all because it would start to ring after the RG timeout has expired. Our calculated value would be a negative value, -5. These negative values don't work as leg_timeouts in the dialstring, so we need to test for them.

* Update index.lua

* Update index.lua
 2019-09-09 14:05:53 -06:00
Nate faadda843e Update fax_to_email.php 2019-09-09 12:48:36 -06:00
Nate 0654ae8f38 Revert: Domain Edit: Prevent special characters (including hyphen) in domain name. 2019-09-09 12:45:09 -06:00
Nate c2e19afc79 Domain Edit: Prevent special characters (including hyphen) in domain name. 2019-09-09 12:09:25 -06:00
FusionPBX a9910847a9 Update contact_addresses.php 2019-09-09 11:29:47 -06:00
chansizzle c14789616f Update contact_addresses.php (#4527) 2019-09-09 11:29:02 -06:00
konradSC 33d4ad0685 Fix delay for external follow-me calls (#4526) 
This is related to https://github.com/fusionpbx/fusionpbx/commit/9dcaddd81422bb46d940a2a3105112b30debcafa#diff-b1f5588538149bd825603176ff81d714.

For internal calls the delay needs to be "Delay In Seconds * 500".
For external calls the delay needs to be "Delay In Seconds * 10000". 

For external calls I'm am just doubling the value set prior in the script.
 2019-09-09 11:22:35 -06:00
Nate f8b6ba17c0 Update app_defaults.php 
Change destination encoding from ASCII to UTF8 in convert_to function, used inside pgsql natural_sort function on Extensions page.
 2019-09-09 12:53:47 -04:00
emaktech 1b3f740568 Modified fr-ca / fr-fr translation. (#4525) 2019-09-09 10:50:58 -06:00
konradSC fe532d04d2 Enterprise RG with Follow-Me (#4524) 
We need to make sure that the delay for the leg takes into account the delay from the RG and from Follow-me. 

Also, let's use the timeout from the RG instead of the follow-me member
 2019-09-09 10:50:31 -06:00
Nate 3da266f003 Update dialplan_xml.php 2019-09-09 10:28:55 -06:00
Nate 67b45f550f Dialplan XML: Integrate editor. 2019-09-09 10:20:54 -06:00
emaktech 0c9e315a82 Modified fr-ca / fr-fr translation. (#4522) 2019-09-09 09:52:45 -06:00
emaktech d31bacf0c0 Modified fr-ca / fr-fr translation. (#4523) 2019-09-09 09:52:27 -06:00
konradSC 62a9b26452 Use original_destination_number for timeout (#4521) 
Need to lookup the timeout values for the original destination. The variable "destination_number" is being clobbered later in the script.
 2019-09-09 08:40:54 -06:00
konradSC b5eb053780 Unset Call_timeout (#4520) 
I believe that call_timeout from the original destination should be unset, so that call_timeouts of the various follow-me destinations can work properly.
 2019-09-09 08:27:19 -06:00
Nate 86c32484ea Extensions: Add natural sorting for PostgreSQL (Upgrade > App Defaults to create required function). 2019-09-09 08:21:58 -06:00
Nate a86721df36 Fix XML Back button to Dialplan Manager. 2019-09-09 06:35:11 -06:00
Nate d6b2e883f4 Update functions.php 2019-09-09 06:06:53 -06:00
FusionPBX 26fbe226b4 Update install.php 2019-09-08 10:31:14 -06:00
FusionPBX e4a3091ea8 Update template.htm 2019-09-08 10:23:23 -06:00
FusionPBX 1c5c343ca0 Update template.htm 2019-09-08 10:01:13 -06:00
FusionPBX 0d5d2a2775 Update template.htm 2019-09-08 09:55:57 -06:00
FusionPBX b8e23d1974 Update install.php 2019-09-08 09:44:56 -06:00
Nate 3f943df8d5 Update user_setting_edit.php 2019-09-07 20:14:48 -06:00
Nate eab1a5179e Update exec.php 2019-09-07 11:33:39 -06:00
FusionPBX 480aee4dda Update music_on_hold.php 2019-09-07 01:48:39 -06:00
FusionPBX f6d2591800 Update destination_imports.php 2019-09-07 01:21:34 -06:00
FusionPBX 1f20caec61 Update device_imports.php 2019-09-07 01:17:20 -06:00
FusionPBX c20838b4d4 Update user_imports.php 2019-09-07 01:11:15 -06:00
FusionPBX 53e9ee5683 Update voicemail_imports.php 2019-09-07 01:08:48 -06:00
FusionPBX a7c8fdab2b Update recording_play.php 2019-09-07 00:49:39 -06:00
FusionPBX 7153383535 Update recordings.php 2019-09-07 00:29:25 -06:00
FusionPBX 7429453f7e Update recording_play.php 2019-09-07 00:21:36 -06:00
FusionPBX 910aaff11b Update conference_sessions.php 2019-09-07 00:18:06 -06:00
FusionPBX a4e8490d41 Update xml_cdr_details.php 2019-09-07 00:16:05 -06:00
FusionPBX e17904c272 Update conference_session_details.php 2019-09-07 00:12:42 -06:00
FusionPBX c7fe77b328 Update xml_cdr_inc.php 2019-09-06 18:46:50 -06:00
FusionPBX 5f4da9ca1b Update access_control_nodes.php 2019-09-06 18:27:51 -06:00
FusionPBX 10f05554fd Update call_broadcast_edit.php 2019-09-06 18:20:01 -06:00
chansizzle 0558f7efc1 Update call_edit.php (#4517) 2019-09-06 13:58:57 -06:00