Search results

Run update 2, 2B, 3, & 5

You will want to set the default setting variable to be your desired length. The longest/widest option is being overwritten when you provision or re-provision the phone. The Yealink variable name is in my previous response. For other manufactures you will need to investigate by finding...

The intercept-ext dialplan is already using **. **[ext]

This is what I do. But I also add a comment in line with the ip addresses to better keep track.

Fail2ban recommends that you never edit the .conf files. The recommendation is to make the edits in your .local files instead. This works very well.

Are you using the variable created for the label length? yealink_dsskey_length

I like the EEP/HEP : Details page. Will you provide more details on the phone dialer in your first image? How to open the dialer?

That Midnight Commander screenshot takes me back in history. Ah, the 'good old days'... VS Code works very well for multiple file manipulations. An SFTP GUI is excellent for moving directories and files.

Good catch. I would add the action to a dialplan instead of where you have in your screenshot.

You are pulling my b-leg! I don't know for certain, but look at bind_target variable in the call_recording_on_demand dialplan. dtmf_target_leg and event_target_leg also look promising https://developer.signalwire.com/freeswitch/FreeSWITCH-Explained/Modules/mod-dptools/6586414/

Start by changing to a feature code that is not already in use. The group-intercept dialplan has *8 the assignment.

Review the already included emergency application. https://github.com/fusionpbx/fusionpbx/tree/master/app/emergency

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...