<br><br><div class="gmail_quote">On Wed, Jan 20, 2010 at 11:44 AM, Dave Stevenson <span dir="ltr"><<a href="mailto:stevendt@primrosebank.net">stevendt@primrosebank.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="word-wrap: break-word;" bgcolor="#ffffff">
<div><font face="Arial" size="2">Brian,</font></div>
<div><font face="Arial" size="2"></font> </div>
<div><font face="Arial" size="2">Following on from before, there's one item that I
can't see how to do outside of modifying the directory\default.xml file, and
that is setting up call groups.</font></div>
<div><font face="Arial" size="2"></font> </div>
<div><font face="Arial" size="2">I thought that I'd perhaps be able to do something
similar to creating user dial plans and create a new file in
directory\default\ which would be loaded before the other extensions,
i.e., called something like 00_groups.xml and have the call group created there.
(My test file is shown below). That did not seem to work, am I on the right
lines or should custom groups get created somewhere else ?</font></div>
<div><font face="Arial" size="2"></font> </div></div></blockquote><div><br>This leads to the bigger question of where people should put their customizations without breaking the defaults. A good example of the issue is with ivr.conf.xml and the corresponding phrase macros in conf/lang/en/en.xml. In some cases it is impossible to add customizations without modifying the default config files. <br>
<br>I will bring this up on tomorrow's conference call. If you want to be heard on this topic then please join us on the call. I will get the agenda posted ASAP.<br><br>-MC<br><br></div></div>