Including custom contexts


#1

Quick question, I like to create custom conf files to organize my contexts by client.
For example, my extensions_custom.conf file looks like this:

#include custom_client1.conf
#include custom_client2.conf

Is there any negative impact to doing things this way v.s. having everything in the extensions_custom.conf file?

What if these sub-files also have include statements in them?

Thanks!


(Communication Technologies) #2

We do this exactly. Each call treatment is in its own conf file in /etc/asterisk/apps

It is great for managing complex call flows. It also makes it easy to migrate conf files from PBX to PBX.


(system) closed #3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.