Confused, so many SIP conf files in new FreePBX/Trixbox

there is a problem which I opened a freePBX ticket for a few weeks ago that you cannot control thinks like the address and bind port without it being overwritten the next time you "click the redbar". [http://www.freepbx.org/trac/ticket/2747] there are parameters that are currently being set in sip_additional.conf which belong elsewhere. there are workarounds, such as manually editing sip.conf and then marking it read only or manually editing the template files that freePBX uses to generate sip.conf each time. neither are particularly good but sometime, you have to do something or you are just plain stuck.

I, too, am having problems with this.

I need to enter:

nat=yes
externip=external ip address
localnet=local ip/netmask

I have done this, manually, in the sip_general_additional.conf file, which works fine....until I create another new extension, at which time, this file (sip_general_additional.conf) is overwritten with the original 'default' information and my additions are lost.

Where else can I put the necessary information, where it won't be overwritten?

Oh, and sip_nat.conf is not anywhere to be found.

John

if it has _additonal in the name, don't touch it. If it has _custom in the name, you can edit it. The _post version is a very special case file and is unlikely you would ever need it. It is there for people who want to add values to auto-generated extension contexts as there exists a notation for sip.conf that lets you append to an already existing sip section definition.

Thanks for everyones response, it would seem the way to go is with the custom file

However there is still the remaining question of context

We already have context defined in sip_additional.conf however what about putting context=from-trunk in this custom file, can we have context defined in two places? If so does one take precedence over the other or can we define two context=xxxx fields?

The point is again that even if we find a file which wont overwrite itself, sip_additional.conf will always have context=from-sip-external and thats problematic for some that need from-trunk specified instead.

Sorry Phillipe, that was a typo, I did mean _custom.

The first set of brackets is the new context from a sip.conf perspective.

The include refers to the context in the extensions.conf world

You can do all sorts of interesting things, if you look at each context in extensions_additional.conf (don't edit it) you will see the first line of every context is an include. This include is unreferenced, you can use it in the custom file to extend that context.

Example:

To extend the functionality of the CID lookup script we can look at the FreePBX code:

[cidlookup]
include => cidlookup-custom
exten => cidlookup_return,1,LookupCIDName
exten => cidlookup_return,n,Return()

So if we add the following to extensions_custom.conf

[cid-lookup]
exten => s,n,Playback(My-Message)

This would playback My-Message and then return to the original context.

Does this make sense?

Scott