Hello,

I am in the peculiar situation to have to set up a PBX for two
independent sites, but operated by the same entity. Yes, I could set
up two VPSs and install Asterisk to each, put common stuff (e.g.
conferencing setup) into Git and share between both using includes,
but for various reasons (among them simplicity and cost), I'd prefer
a single Asterisk instance.

I know I can #include files from sip.conf and extensions.conf, so
making a extensions.conf that consists of

  #include ext-common.conf
  #include foo/extensions.conf
  #include bar/extensions.conf

is trivial. Unfortunately, the contexts in each of these files must
not clash, and so I will be forced to use e.g. [bar-incoming] in
bar/extensions.conf.

That's a bit of redundancy here (which I am always trying to avoid
like the plague) and I am wondering if there are better ways. Do you
know of any, short of writing a script to "compile" the files and
change the contexts based on path (which will be dirty and hard to
get right)?

Thanks,

-- 
@martinkrafft | http://madduck.net/ | http://two.sentenc.es/
 
"oh what a tangled web we weave,
 when first we practice to deceive.
 but my how we improve the score,
 as we practice more and more."
                                                   -- sir walter scott
 
spamtraps: [email protected]

Attachment: digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

-- 
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
               http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to