iax_general_additional.conf iax_general_custom.conf iaxprov.conf
iax_registrations.conf iax_registrations_custom.conf indications.conf localprefixes.conf logger.conf
manager_additional.conf manager.conf
manager_custom.conf meetme.conf
meetme_additional.conf mgcp.conf modem.conf modules.conf
musiconhold_additional.conf musiconhold.conf
musiconhold_custom.conf oss.conf
parking_additional.inc (should no longer be used as parking was moved to features) phone.conf phpagi.conf privacy.conf queues.conf
o Do not edit this file in any way. Anything you can think of putting in this file can be
placed into one of the _custom.comf files where it will not get removed or replaced.
queues_additional.conf o Do not edit this file in any way. Anything you can think of putting in this file can be
placed into one of the _custom.conf files where it will not get removed or replaced.
queues_custom.conf
o This is the proper location for placing any of the context specific options and lines
that you might need to add before the processing of the queues_additional.conf file for your queues setup.
queues_custom_general.conf
o This is the proper location for placing any of the [general] context option lines that
you might need to add to your queues setup.
queues_general_additional.conf o Do not edit this file in any way. Anything you can think of putting in this file can be
placed into one of the _custom.comf files where it will not get removed or replaced.
queues_post_custom.conf
o This is the proper location for placing any of the context specific options that you
might need to add to the end queues setup.
This is the file that allows you to add or remove values to those entries found in the
auto-generated queue_additional.conf file. So for example you have a queue 79 that need a additional parameter added. create a context line: [79](+) then on the next line add the item(s) you need to add. To remove use (-) instead followed by the line(s) you want removed.
res_mysql.conf rtp.conf sip.conf
o Do not edit this file in any way. Anything you can think of putting in this file can be
placed into one of the _custom.comf files where it will not get removed or replaced. If you are looking to do nat'ing, see sip_general_custom.conf or if it is a legacy system sip_nat.conf. If you want to add additional setup parameters for your sip device see sip_custom_post.conf, etc. If you need to adjust sip jitter or something else it will be sip_general_custom.conf (if it is for the general context) or sip_custom.conf. If you do edit this file and place something new in it, it will get overwritten at some point and next time you restart your system you will suddenly wonder why things stopped working.
sip_general_additional.conf
o This is where FreePBX places all of it's general context settings. If you need to
override one of these or add a new one please do so in sip_general_custom.conf.
sip_general_custom.conf
o This is the proper location for placing any of the [general] context option lines that
you might need to add to your setup. This is also the place to add those lines needed to enable the nat'ing of SIP when you go through a firewall.
Some of the required lines for nat'ing are externip=, nat=, localnet= (you can have more then one occurrence of this line), and optionally fromdomain=. The first three are needed to properly setup a box on protected network behind a firewall that is providing nat to a public IP. If you have a legacy system these lines might have been placed in sip_nat.conf in the past, if so that is ok as long as the lines only exist in one file and not both (or a big debugging mess will occur along with hair loss as you pull it out while tracking it all down). See sip_nat.conf for more info.
configurations with multiple subnets:
For those setups with internal networks that have multiple subnets you will need to add a localnet= line for each subnet that the phone system should have direct access to. If you don't do this the phone system will assume that phones on those other subnets are external and thus provide the External IP of the box in the SIP headers instead of the internal IP. This then becomes a routing problem for the phone as it should not be attempting to talk external IP of the internal box (most firewalls can not handle the looping back of IP traffic).
Example:
Server 192.168.1.2 on a 192.168.1.0/255.255.255.0 network
Phones inside the office are on the 192.168.2.0/255.255.255.0 subnet
Requires these two lines in the either sip_general_custom.conf or sip_nat.conf file localnet=192.168.1.0/255.255.255.0 localnet=192.168.2.0/255.255.255.0
sip_nat.conf