dbxe
/
fusionpbx
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
14,005 Commits 3 Branches 10 Tags 224 MiB
Commit Graph

5451 Commits

Author SHA1 Message Date
Len cfa38e48e9 Update {$mac}.xml (#4507) 
* Update {$mac}.xml

* Update {$mac}.xml

* Update {$mac}.xml

* Update {$mac}.xml
 2019-09-11 08:30:12 -06:00
Len ab04709f6d Update {$mac}.xml (#4508) 
* Update {$mac}.xml

* Update {$mac}.xml

* Update {$mac}.xml

* Update {$mac}.xml
 2019-09-11 08:29:24 -06:00
agree c94e46b009 Update page.lua (#4510) 
* Update page.lua

* Update page.lua
 2019-09-11 02:40:56 -06:00
FusionPBX 1f78ecca5e Update header.php 2019-09-10 23:19:46 -06:00
Nate 911a43219e Users: Prevent duplicate usernames. 2019-09-10 19:23:14 -06:00
FusionPBX 19e8305a8e Update schema.php 2019-09-10 17:50:41 -06:00
benwiesner1 3fd92801bb Update {$mac}.cfg (#4534) 
changed analog headset to if isset
if its not set within the device settings itself then polycom errors this as invalid
 2019-09-10 14:29:06 -06:00
benwiesner1 9f962e4f18 Update {$mac}.cfg (#4531) 
added syslog as (IF SET)
changed video settings to (if set) VVX and 600 only
updated bluetooth to (IF Set) VVX 600 only
 2019-09-10 13:53:16 -06:00
FusionPBX c37f2958e5 Update destinations.php 2019-09-10 13:50:42 -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
konradSC 33d4ad0685 Fix delay for external follow-me calls (#4526) 
This is related to 9dcaddd814 (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
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
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
Nate d6b2e883f4 Update functions.php 2019-09-09 06:06:53 -06:00
benwiesner1 9a089df460 Update {$mac}.cfg (#4514) 2019-09-06 13:36:45 -06:00
FusionPBX 0102349269 Update index.lua 2019-09-06 03:37:07 -06:00
FusionPBX f220784841 Update do_not_disturb.lua 2019-09-05 13:43:49 -06:00
Len 7082a83cb8 Update {$mac}.xml (#4499) 2019-09-05 12:44:49 -06:00
FusionPBX 415672084f Update {$mac}.xml 2019-09-05 12:23:57 -06:00
FusionPBX eaf00cfbc9 Update {$mac}.xml 2019-09-05 12:23:17 -06:00
FusionPBX 098acbf83d Update {$mac}.xml 2019-09-05 12:22:54 -06:00
FusionPBX c6b89f846d Update {$mac}.xml 2019-09-05 12:21:43 -06:00
FusionPBX baa7c08eb5 Update {$mac}.xml 2019-09-05 12:20:41 -06:00
FusionPBX 80b0a9d070 Update {$mac}.xml 2019-09-05 12:19:42 -06:00
FusionPBX b12eff14da Update {$mac}.xml 2019-09-05 12:16:22 -06:00
FusionPBX 919786db51 Update {$mac}.xml 2019-09-05 12:14:29 -06:00
FusionPBX e6cb8d61a4 Update {$mac}.xml 2019-09-05 12:13:47 -06:00
FusionPBX c198ff607e Update {$mac}.xml 2019-09-05 12:12:58 -06:00
FusionPBX db646da590 Update do_not_disturb.lua 2019-09-05 11:01:59 -06:00
konradSC e0b29d031d Populate toll-allow for Enterprise Ring Groups (#4496) 
Add toll_allow to dialstring for external numbers
 2019-09-04 13:05:57 -06:00
konradSC 9e301a0c97 Toll-allow into dialstring for external calls (#4495) 
Insert toll-allow from the original extension into the dialstring for external calls.
 2019-09-04 11:30:51 -06:00
FusionPBX 536be5bdb9 Update header.php 2019-09-04 11:20:27 -06:00
FusionPBX 6d14afffea Update header.php 2019-09-04 11:11:04 -06:00
FusionPBX f7c1235381 Update follow_me.lua 2019-09-04 10:22:11 -06:00
FusionPBX 78b57a8d29 Update follow_me.lua 2019-09-04 10:01:26 -06:00
FusionPBX c644994cee Update follow_me.lua 2019-09-04 09:42:42 -06:00
agree 08cbbc86ba Update follow_me.lua (#4491) 2019-09-04 09:35:05 -06:00
Nate 37b5713c4b Misc Classes: Database class integration. 2019-09-04 06:44:50 -06:00
FusionPBX cda306a2d2 Update {$mac}.cfg 2019-09-03 16:56:25 -06:00
FusionPBX d7f30cf930 Update {$mac}.cfg 2019-09-03 16:49:25 -06:00
Nate 07cb911e70 Menu Class: Database class integration. 2019-09-03 09:59:37 -06:00
Nate 836fb87136 Misc Classes: Database class integration. 2019-09-02 15:57:18 -06:00
FusionPBX 601198e01a Update index.lua 2019-09-02 08:32:50 -06:00
FusionPBX 5cddd37b85 Update index.lua 2019-09-02 08:29:25 -06:00
FusionPBX 0fa4daf938 Update index.lua 2019-09-01 08:05:43 -06:00
FusionPBX 254a62c0a7 Update index.lua 2019-09-01 07:41:57 -06:00
FusionPBX db53713f5f Update index.lua 2019-08-31 13:05:01 -06:00
FusionPBX 2c934bdb2b Update index.lua 2019-08-31 12:54:03 -06:00
FusionPBX 9b57fc5bff Update index.lua 2019-08-31 11:28:31 -06:00
FusionPBX 7196e20e50 Update index.lua 2019-08-31 04:03:59 -06:00