<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.7600.16490"></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Segoe UI">
<DIV>Hi Michael</DIV>
<DIV> </DIV>
<DIV>I'm trying to get the possibility of transfering an incoming call from one extension to another, and give the possibility of turning it into a conference.</DIV>
<DIV>I don't have a 'transfer' button.</DIV>
<DIV>I do have an 'R' button on the Siemens handsets, and a 'Flash' button on the Sipura. The 'Flash' button gives me a new dialtone, gives the caller MOH, and then I can dial the new extension, and transfer the call, but not create a conference.</DIV>
<DIV>But the Siemens handset does not have a 'flash', and pressing the R doesn't do anything.</DIV>
<DIV> </DIV>
<DIV>It might be two different features 'transfer' and 'conference'...</DIV>
<DIV><BR>But I thought that using the bind_meta_app would accomplish both.</DIV>
<DIV> </DIV>
<DIV>It's on an incoming call from the outside.</DIV>
<DIV>So the situation:</DIV>
<DIV>The Public folder has an entry that matches the dialed number, and does a transfer to 8202.</DIV>
<DIV>Then the dialplan matches the 8202 with a group, and the phone rings.</DIV>
<DIV>Somebody picks it up, finds out that it needs to be transferred to another extension, or transferred to a conference with a second extension.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>
<DIV>Best regards</DIV>
<DIV>Fribse</DIV>
<DIV> </DIV>
<DIV>/Running Freeswitch on pfSense running on a VMWare ESXi 4.0</DIV></DIV>
<DIV><BR>>>> 02-02-2010 kl. 01:47 skrev Michael Collins <msc@freeswitch.org> i meddelelsen <87f2f3b91002011647k792d2fdbyf4eaa7c2a41d9ab5@mail.gmail.com>:<BR></DIV>
<TABLE style="MARGIN: 0px 0px 0px 15px; FONT-SIZE: 1em" border=0 bgColor=#f3f3f3>
<TBODY>
<TR>
<TD>
<DIV style="BORDER-LEFT: #050505 1px solid; PADDING-LEFT: 7px"><BR><BR>
<DIV class=gmail_quote>On Mon, Feb 1, 2010 at 5:37 AM, mailinglist <SPAN dir=ltr><<A href="mailto:mailinglist@fribert.dk">mailinglist@fribert.dk</A>></SPAN> wrote:<BR>
<BLOCKQUOTE style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex" class=gmail_quote>
<DIV style="MARGIN: 4px 4px 1px; FONT: 10pt Segoe UI; font-size-adjust: none; font-stretch: normal">
<DIV>Hmm, I've just downloaded the default.xml under conf/dialplan from the SVN just to be on the safe side.</DIV>
<DIV>Line 758 is the last </include>, but I did find some examples on line 249-251.</DIV>
<DIV></DIV>
<DIV>So I've changed my dialplan entry handling calls from the outside to this:</DIV>
<DIV>
<DIV class=im><BR><extension name="PrivateIn"><BR><condition field="destination_number" expression="^(8202)$"><BR></DIV>
<DIV class=im><action application="bind_meta_app" data="1 b s execute_extension::att_xfer XML features"/><BR></DIV><action application="bind_meta_app" data="2 b s record_session::$${recordings_dir}/${caller_id_number}.${strftime(%Y-%m-%d-%H-%M-%S)}.wav"/>
<DIV class=im><BR><action application="set" data="call_timeout=45"/><BR><action application="set" data="domain_name=10.11.12.25"/><BR><action application="set" data="continue_on_fail=true"/><BR><action application="set" data="hangup_after_bridge=true"/><BR><action application="set" data="transfer_ringback=$${hold_music}"/><BR><action application="bridge" data="<A href="mailto:group/private@$%7Bdomain_name%7D%22/" target=_blank>group/private@${domain_name}"/</A>><BR><action application="answer" data=""/><BR><action application="sleep" data="1000"/><BR><action application="voicemail" data="default 10.11.12.25 45"/><BR></condition><BR></extension><BR></DIV></DIV>
<DIV>As I understand the bind_meta_app it listens for *1 and then it runs the att_xfer, *2 to record the call.</DIV>
<DIV>I've included the att_xfer in the XML features.</DIV>
<DIV></DIV>
<DIV>Question is, will it work at all when I bridge to a group?</DIV>
<DIV></DIV>
<DIV>Nothing happens when I press *1 and an extension.</DIV></DIV></BLOCKQUOTE>
<DIV><BR>Fribse,<BR><BR>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:<BR><BR><action application="bind_meta_app" data="2 b s record_session::$${recordings_
<DIV>dir}/${caller_id_number}.${strftime(%Y-%m-%d-%H-%M-%S)}.wav"/><BR><BR>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. <BR><BR>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?<BR><BR>-MC<BR></DIV><BR></DIV></DIV><BR></DIV></TD></TR></TBODY></TABLE></BODY></HTML>