Making Permanent changes to SARK/SAIL controlled .conf files

There is a solution to this issue in 2.2.3-13 and 2.3.1-17. Sail references a set of include files when it generates the major .conf files. They are called....

sark_customer_iax_devices.conf - included at the end of the IAX devices section
sark_customer_iax_headers.conf - included immediately after the headers and still inside the [general] section
sark_customer_iax_registrations.conf - included immediately after SARK's registration entries
sark_customer_sip_devices.conf - included at the end of the SIP devices section
sark_customer_sip_headers.conf - included immediately after the headers and still inside the [general] section
sark_customer_sip_registrations.conf - included immediately after SARK's registration entries
sark_customer_manager.conf - included at the end of SARK's entries
sark_customer_queues.conf - included at the end of SARK's entries
sark_customer_voicemail_header.conf - included at the end of SARK's entries
sark_customer_voicemail_main.conf - included at the end of SARK's entries

You can edit these files from the general edit panel and you can put anything you want into them. They will survive SARK/Sail release updates. The empty files will be created the first time you issue a commit from globals after you have installed the relevant release. Using these include files, together with custom-apps, SARK/Sail is now completely open in that you can add your own trunks, extensions and extensions.conf code completely outside of SARK/Sail control if that's what you want to do.

-- TWikiAdminUser - 29 Jun 2009