On Thu, Feb 13, 2014 at 5:38 AM, Joshua Colp wrote:
> On 14-02-12 03:26 AM, George Joseph wrote:
> > In the process of creating the dialplan function AST_SORCERY (a
> > companion to AST_CONFIG) I've run into an issue with how AMI interacts
> > with sorcery particularly related to objects that can
On 14-02-12 03:26 AM, George Joseph wrote:
> In the process of creating the dialplan function AST_SORCERY (a
> companion to AST_CONFIG) I've run into an issue with how AMI interacts
> with sorcery particularly related to objects that can have multiple
> occurrences of the same field like contact in
In the process of creating the dialplan function AST_SORCERY (a companion
to AST_CONFIG) I've run into an issue with how AMI interacts with sorcery
particularly related to objects that can have multiple occurrences of the
same field like contact in aor and match in identify. Take a look at the
fol
