On Mon, Feb 1, 2010 at 5:37 AM, mailinglist <mailinglist@fribert.dk> wrote:
Hmm, I've just downloaded the default.xml under conf/dialplan from the SVN just to be on the safe side.
Line 758 is the last </include>, but I did find some examples on line 249-251.
 
So I've changed my dialplan entry handling calls from the outside to this:

<extension name="PrivateIn">
   <condition field="destination_number" expression="^(8202)$">
       <action application="bind_meta_app" data="1 b s execute_extension::att_xfer XML features"/>
       <action application="bind_meta_app" data="2 b s record_session::$${recordings_dir}/${caller_id_number}.${strftime(%Y-%m-%d-%H-%M-%S)}.wav"/>

       <action application="set" data="call_timeout=45"/>
       <action application="set" data="domain_name=10.11.12.25"/>
       <action application="set" data="continue_on_fail=true"/>
       <action application="set" data="hangup_after_bridge=true"/>
       <action application="set" data="transfer_ringback=$${hold_music}"/>
       <action application="bridge" data="group/private@${domain_name}"/>
       <action application="answer" data=""/>
       <action application="sleep" data="1000"/>
       <action application="voicemail" data="default 10.11.12.25 45"/>
   </condition>
</extension>
As I understand the bind_meta_app it listens for *1 and then it runs the att_xfer, *2 to record the call.
I've included the att_xfer in the XML features.
 
Question is, will it work at all when I bridge to a group?
 
Nothing happens when I press *1 and an extension.

Fribse,

I think your confusion might be from the purpose of the bind_meta_app application. The *1 or *2, etc. must be dialed after the call has been established. In other words, bind_meta_app sits there on an existing call, listening for *1 or *2 (etc.) and if the person on the appropriate call leg dials it then the application in bind_meta_app gets executed. Example:

<action application="bind_meta_app" data="2 b s record_session::$${recordings_
dir}/${caller_id_number}.${strftime(%Y-%m-%d-%H-%M-%S)}.wav"/>

The "2 b s" part of that means: Listen for *2 on the b leg and execute the app on the s leg. So, the b leg could dial *2 and it would initiate call recording.

Let's take a step back... are you sure you need bind_meta_app? What exactly is your use case here? In general terms, what are you trying to accomplish with your dialplan extension?

-MC