looks like a good idea, only question is that i was under the impression that every time i do a module update or an “Apply Changes” update that extensions.conf will get regenerated and that i shouldnt be placing anything in extension.conf
Let me know if i am wrong about the above
however if i also understand correctly, if this macro-dialout-trunk-predial-hook gets integrated permanently into FreePbx, then in the future re-declaring it in extensions_custom.conf will be the solution. Yes 100% agree if thats the case, just right now i am afriad anything i do in my current release of FreePbx can easily get destroyed with an update (Apply Changes, Re-Read configs, or updating a module through module admin), not concerned of FreePBX upgrade, this i will be on the lookout for the code and will just re-insert it manually if i ever upgrade.
extensions.conf may get overwritten when core is updated. You would not put it in extensions.conf. As long as you declare it in extension_custom.conf which is included at the top of extensions.conf you will override the ‘dummy’ macro that we have declared. Since extensions_custom.conf is yours to do with what you please, you are safe to put it in there and nothing will happen to it. That is its purpose.
Philippe Lindheimer - FreePBX Project Lead
http//freepbx.org - IRC #freepbx
yes it will be in the next core and redeclaring means you define your own function:
[macro-dialout-trunk-predial-hook]
exten => s,1,Noop(this is my first instruction)
exten => s,n,Noop(this is my next step)
exten => s,n,Noop(now that I have done nothing, return)
Philippe Lindheimer - FreePBX Project Lead
http//freepbx.org - IRC #freepbx