When does sip.conf get replaced? Is it after a freePBX Framework update?
What is the recommended method for preserving sip.conf as I have entries such as externip, localnet and a different bindport - should I put these into a different sip…conf file?
The tail end of that file has some includes for other files, I think it’s standard across the board, mine shows:
[code:1]; #, in this configuration file, is NOT A COMMENT. This is exactly
; how it should be. #include sip_nat.conf #include sip_registrations_custom.conf #include sip_registrations.conf #include sip_custom.conf #include sip_additional.conf
[/code:1]
So if you put your code in sip_custom.conf, it should survive upgrades.
[quote=“dirk”]The tail end of that file has some includes for other files, I think it’s standard across the board, mine shows:
[code:1]; #, in this configuration file, is NOT A COMMENT. This is exactly
; how it should be. #include sip_nat.conf #include sip_registrations_custom.conf #include sip_registrations.conf #include sip_custom.conf #include sip_additional.conf
[/code:1]
So if you put your code in sip_custom.conf, it should survive upgrades.[/quote]
Ah, ok. I’d assumed that it worked the same as extensions.conf and others where if something was already defined that it could not be redefined.
As these includes are at the end and bindport is already set I’d assumed that I couldn’t change it again. I’ll try it…
You’ll have to put the settings under a context heading and call it from the main file.[/quote]
Sorry, I missed that on the copy/paste. I wasn’t sure what context I should use as the normal context is [general] so I put it under the same, [general].
And if I need to add something extra to the main file (sip.conf?) then that will also get overwritten on a module/framework update wouldn’t it?