Recent content by whut

Good points to consider. voicemail transcriptions are very short and are only a tiny consideration for STT. Long recordings would be a paramount consideration.

I have seen a very small set of occurrences with the transcription service providers returning results too slowly where the transcriptions are not included in a voicemail to email notifications. Otherwise the module has worked very well with multiple STT service providers. I believe tou do bring...

Fusionpbx does transcription https://github.com/fusionpbx/fusionpbx-app-transcribe

@agree thanks again for the PL SQL I am finding it very useful. I have been testing it have have a couple of changes here - mostly executing the deletes in table order A-Z. Image below of the delete in A-Z table name order. CREATE OR REPLACE FUNCTION delete_domain(id UUID) RETURNS void AS $$...

I removed the duplicate `AND table_schema = 'public'` in your WHERE clause in the below. CREATE OR REPLACE FUNCTION delete_domain(id UUID) RETURNS void AS $$ DECLARE r RECORD; BEGIN FOR r IN SELECT table_schema, table_name FROM information_schema.columns JOIN...

nicely done. This could easily be adapted for other purposes too. :cool:

That is nice PL SQL agree. But pressing the delete domain(s) button in the fusionpbx GUI will perform all of the deletes for you.O do not remember if it also deletes the recordings, messages, and others. It has been a long time since I have needed to remove a domain.

FusionPBX has multi-factor authentication. You may want to investigate that. Check default settings for this. By default a valid user with X failed login attempts will be blocked for X minutes. Check default settings for this. I would not allow any unauthenticated visitors with access to the...

Which version of FusionPBX are your webpages resting upon?

I do not know of any proven correlation that would exclude you from updating FusionPBX and that would stop the CDRs from updating. Run every FusionPBX update option 1 at a time in successsion. Do not skip any upgrade options. If you watch the changes in github you will notice there have been...

No. this has nothing to do with one of the few paid member feature. It is solely incorrectly setting user permissions and user extension associations.

Fusionpbx already has this. It looks like you are assigning accounts to have super admin permissions group. Very not good. Assign the user group, assign the user to the appropriate extensions. Read any dcumentation you have access to.

Have you set all extensions to have CID name and CID number? You do need these set for outbound calls

<action application="set" data="valet_info_park=${valet_info park@${valet_context}}|\*${park_lot}" inline="true"/> <action application="set" data="park_in_use=${regex ${valet_info park@${valet_context}}|\*${park_lot}}" inline="true"/>

:cool::cool: I had to do a lot of investigation when building my first dashboard widget. It is much easier to display every widget after the first one! :)