Search results

Line 1 is for account 1 on the accounts page of the phone's web GUI. Setting it to line 1 connects the call park key to your extension 101 as you have the phone programmed. Use line 2 for account number 2.

Run this SQL to make sure you can generate v4 before incorporating SELECT uuid_generate_v4();

I seem to remember there are default settings for MFA

use version 4 uuids uuid_generate_v4()

The first item I see as an issue in your sql is the last line where you update extension 3333. Add a where clause of domain_uuid = . You do not want to update all extensions 3333

Ah! You have an interesting configuration @dcitelecom. The issue becomes more clear. Are most of your DIDs all on the same domain? Your design of numbers has been created with thoughtfulness which greatly reduces the potential of "collisions". I am thinking of a modified copy of the is_local...

Thank you both for your comments

I would never use >= 10 digit length numbers for extensions, ivrs, anything else. >= 10 digits length is reserved for DIDs in North America. And if you do any smart dialing that prepends the area code on a 7 digit dial out you would not use >= seven digits length for anything other than DIDs...

I see fusion does not yet have a provisioning template for the new T44U. https://github.com/fusionpbx/fusionpbx/tree/master/resources/templates/provision/yealink you threw me off for a minute.

whuuuut? on a domain if you dial the number of an IVR, time condition, ring group, et cetera, you will be directly dialing that said item. The call remains local and remains on the domain. Equally, when you select any one of these entities as the action from a dropdown, your call still remains...

tut tut good sir or madam! Try it like this in the domain-variables dialplan, flush cache. If that works perfectly for you then move the record_ext to the global-variables dialplan to apply to all domains for all future recordings.

Is there no one using least cost routing?

The maintenance application does allow for domain level. When using it you will need to carefully review what it is handling and what your maintenance script is handling. Maintenance application keeping ABC domain call recordings for 365 days and maintenance script keeping for 180 will yield...

switch variables page has record_ext set to wav by default. You can change to mp3 for mp3 compression. Restart freeswitch if you modify here. Also know that mp3 is smaller file size but takes more CPU to compress and uncompress. I do not know how heavy that load is to the CPU. You could run a...

Not for follow me and the follow me destinations. That requires 2 more tables. You can import and export extensions/destinations for call forward, on busy, no answer, and not registered.

Use the speech application to go in the opposite direction; text to speech https://github.com/fusionpbx/fusionpbx-app-speech

Voicemail transcription has moved to the newish transcription application. It is confusing if you have voicemail transcribe settings, which I believe, are no longer used. https://github.com/fusionpbx/fusionpbx-app-transcribe

How to implement least cost routing in fusionpbx? I know you need to add the LCR module and that you need to load rate sheet(s). Where and how to you load rate sheets? What is the full implementation of LCR in fusionpbx?

When you use the fusion maintenance script you can easily adjust it to "delete CDRs, call recordings, etc at N days old except where the domain is X, Y, or Z. Delete "mikeme" domain CDRs and call recording at X days old" There are 12 items or more that fusion is maintaining out of the box with...

I believe you would want to set the caller ID in both groups of conditions. As you have it set I would interpret CID to only be set when you do not dial *8. With that, I would set the CID to the *8 group/block. Which points to dutifully test both the `group-intercept` and the `intercept-ext`...