Keypad
Advanced Configuration
Advanced Configuration
Add your own options to a PJSIP object, a group of them or a section of another Asterisk file, create PJSIP objects AiPBX does not generate, or write a file part as raw text. They are kept in the database, so regenerating the configuration and updating AiPBX do not lose them. For your own dialplan, use Custom Dialplan.
Limits to know
- Only option names are checked. Asterisk accepts a wrong value without an error, so test what you changed.
- Files under /etc/asterisk/pbx are replaced on Apply and on updates, so a change made by hand does not last. Use this page or Custom Dialplan.
- For rtp, queues, voicemail, musiconhold, logger, manager and indications Asterisk offers no option list and ignores an unknown name, so only the format and the load result are checked.
- Options that run a program, open the management interface to others or have their own page cannot be set here, such as mailcmd, the RTP port range and [applicationmap].
- In rtp, voicemail and logger Asterisk uses the first value it finds, so a line cannot replace a value the file already has. The list says so.
- A new transport opens on a reload, but changing or removing one takes effect only after a restart.
- Objects you add here do not appear on the Trunks or Extensions pages, and routes do not offer them.
- An export can contain passwords you typed here, so keep the file safe.
No options added yet.
Earlier versions
The list is saved before every change. Restoring puts it back, and it takes effect after Apply.
Generated files changed by hand
Files under /etc/asterisk/pbx are generated and are replaced on Apply and on updates. If one was changed by hand, a copy is kept here when it is replaced. Move what you need to this page or to Custom Dialplan.
None found.