Commit Graph

1394 Commits

Author SHA1 Message Date
agree ad24e3131f Update index.lua (#4753)
* Update index.lua

* Update index.lua
2019-10-06 11:05:16 -07:00
Andy-Seattle b024bab1cc Update record_message.lua (#4731)
When we have MP3 enabled we want ALL voicemails to be MP3 EXCEPT the ones that need to be transcribed, which will be WAV.

When transcribe_enabled is set to true, ALL voicemails currently become WAV even when MP3 is set.

This change ensures that ALL voicemails remain MP3 except the extensions that have voicemail_transcription_enabled set to true.

Note: The reason this was not working is because setting transcribe_enabled to true also sets voicemail_transcription_enabled to false for ALL extensions BUT it is not written into the database. Therefore a SAVE is required for ALL voicemails to ensure this field is written to the database. Changing to ~=true gets around this problem.
2019-10-04 08:45:45 -07:00
FusionPBX 74798ca686 Update index.lua 2019-10-02 14:08:49 -06:00
FusionPBX 51a527b292 Update index.lua 2019-10-02 12:06:39 -06:00
FusionPBX 110d5ef979 Update index.lua 2019-10-02 02:46:57 -06:00
FusionPBX f79f4f3d48 Update disa.lua 2019-10-01 17:02:41 -06:00
FusionPBX 79aa57abbf Update disa.lua 2019-10-01 13:05:36 -06:00
FusionPBX 094b5f9c25 Update disa.lua 2019-10-01 12:58:16 -06:00
Stephen Forster d72718ea9f Fix table name, variables and syntax Follow me Lua (#4609)
* Fix table name, variables and syntax Follow me Lua

Correct the wrong table name on line 123. Correct the param on line 126 and correct the syntax on line 347.

* Update index.lua

Missing AND in where clause.

* Change order of preference Caller ID

Changed order of preference for Caller ID. If user exists should take preference over Follow Me override select caller ID.

This is my preference and my opinion only. May not be the desired effect of others. Perhaps a select option to choose a preference like the following options: Set caller ID override all, Local user else Caller ID
2019-09-30 17:18:27 -07:00
FusionPBX 49e254794d Update disa.lua 2019-09-29 15:35:26 -06:00
FusionPBX d8ecdaf503 Update directory.lua 2019-09-27 20:45:32 -06:00
FusionPBX d68159d0f9 Update directory.lua 2019-09-27 18:36:15 -06:00
agree de7f341d5f Update index.lua (#4663) 2019-09-26 15:31:57 -06:00
FusionPBX 1f8cca5217 Update recordings.lua 2019-09-25 16:46:52 -06:00
Luis Daniel Lucio Quiroz 52dd233fbf [4.5] Fix the cidlookup script (#4630)
* [4.5] Fix the cidlookup script

same as 4.4

* Update cidlookup.lua
2019-09-20 10:38:15 -06:00
FusionPBX fbd61b2e1a Update do_not_disturb.lua 2019-09-11 13:26:37 -06:00
agree c94e46b009 Update page.lua (#4510)
* Update page.lua

* Update page.lua
2019-09-11 02:40:56 -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
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
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 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
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
FusionPBX b9f22994b5 Delete index.php 2019-08-31 01:46:26 -06:00
FusionPBX 33571292bb Create index.lua 2019-08-31 01:44:46 -06:00
FusionPBX 0f27db7a45 Create index.php 2019-08-29 09:11:42 -06:00
konradSC 8f139bcb89 Watson Transcription (#4420)
The following PR is for voicemail transcription using IBM Watson.
https://cloud.ibm.com/catalog/services/speech-to-text

The following values need to be configured in Default Settings:

Category: Voicemail
Subcategory: watson_key
type: text
Value: [Your Watson api key ]

Category: Voicemail
Subcategory: json_enabled
type: boolean
Value: true

Category: Voicemail
Subcategory: transcibe_language
type: text
Value: en-US

Category: Voicemail
Subcategory: transcribe_provider
type: text
Value: watson

Category: Voicemail
Subcategory: watson_url
type: text
Value: https://stream.watsonplatform.net/speech-to-text/api/v1/recognize?model=en-US_NarrowbandModel

Category: Voicemail
Subcategory: transcribe_enabled
type: boolean
Value: true


Reload Default Settings. I Flushed Cache and Reloaded XML just for good measure.

Also make sure transcription is set to TRUE in your voicemail box.
2019-08-19 09:17:03 -06:00
FusionPBX b8e0ccb2c2 Update recordings.lua 2019-08-17 15:49:15 -06:00
FusionPBX eb7b589ccc Update record_greeting.lua 2019-08-17 15:30:41 -06:00
FusionPBX 5bb48c9d8e Update record_message.lua 2019-08-17 15:22:06 -06:00
FusionPBX 339337a668 Update record_greeting.lua 2019-08-17 14:58:06 -06:00
FusionPBX 4cb8916d90 Update recordings.lua 2019-08-17 14:37:08 -06:00
FusionPBX 9f23fcf6f5 Update recordings.lua 2019-08-17 14:28:26 -06:00
FusionPBX 8354f2409b Update recordings.lua 2019-08-17 14:18:25 -06:00
FusionPBX 8fa25d86d8 Update 010_get_domain.lua.noload 2019-08-11 17:10:00 -06:00