FusionPBX
0e885d730f
Merge pull request #4555 from Len-PGH/patch-132
...
Update y000000000069.cfg
2019-09-11 13:54:59 -06:00
FusionPBX
e1a4e86e20
Merge pull request #4556 from Len-PGH/patch-133
...
Update y000000000045.cfg
2019-09-11 13:54:29 -06:00
FusionPBX
f7149ab4b3
Merge pull request #4557 from Len-PGH/patch-134
...
Update y000000000000.cfg
2019-09-11 13:54:06 -06:00
FusionPBX
a5ba12ddf5
Merge pull request #4558 from Len-PGH/patch-135
...
Update y000000000032.cfg
2019-09-11 13:53:50 -06:00
FusionPBX
4b4981ede0
Merge pull request #4559 from Len-PGH/patch-136
...
Update y000000000038.cfg
2019-09-11 13:52:58 -06:00
FusionPBX
3c320bd548
Update y000000000076.cfg ( #4561 )
2019-09-11 13:52:24 -06:00
Len
d57c43eb3d
Update y000000000054.cfg ( #4562 )
2019-09-11 13:52:04 -06:00
FusionPBX
fbd61b2e1a
Update do_not_disturb.lua
2019-09-11 13:26:37 -06:00
Len
bcd945dcd5
Update y000000000076.cfg
2019-09-11 14:25:31 -04:00
Len
cccb415871
Update y000000000038.cfg
2019-09-11 14:23:26 -04:00
Len
e0de0a228a
Update y000000000032.cfg
2019-09-11 14:21:38 -04:00
Len
eeb9742288
Update y000000000000.cfg
2019-09-11 14:17:42 -04:00
Len
eb7f07948b
Update y000000000045.cfg
2019-09-11 14:15:48 -04:00
Len
ca8b2432bf
Update y000000000069.cfg
2019-09-11 14:13:15 -04:00
mtghr
ab726f009b
Update y000000000046.cfg ( #4540 )
...
* Update y000000000046.cfg
* Update y000000000046.cfg
2019-09-11 08:38:04 -06:00
mtghr
8c2f375b7d
Update y000000000046.cfg ( #4538 )
2019-09-11 08:37:26 -06:00
Len
bd23bde2cd
Update {$mac}.xml ( #4503 )
...
* Update {$mac}.xml
* Update {$mac}.xml
2019-09-11 08:33:36 -06:00
Len
fc2bb604b6
Update {$mac}.xml ( #4504 )
...
* Update {$mac}.xml
* Update {$mac}.xml
* Update {$mac}.xml
* Update {$mac}.xml
2019-09-11 08:32:42 -06:00
Len
296ab02f4e
Update {$mac}.xml ( #4505 )
...
* Update {$mac}.xml
* Update {$mac}.xml
* Update {$mac}.xml
* Update {$mac}.xml
2019-09-11 08:31:41 -06:00
Len
d164ced67c
Update {$mac}.xml ( #4506 )
...
* Update {$mac}.xml
* Update {$mac}.xml
* Update {$mac}.xml
* Update {$mac}.xml
2019-09-11 08:30:58 -06:00
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)
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
