<br><br><div class="gmail_quote">On Thu, Mar 29, 2012 at 2:16 PM, Mikhail Lischuk <span dir="ltr"><<a href="mailto:mlischuk@itx.com.ua">mlischuk@itx.com.ua</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<u></u>
<div>
<p>Warren Selby ΠΙΣΑΜ 29.03.2012 20:20:</p><div class="im">
<blockquote type="cite" style="padding-left:5px;border-left:#1010ff 2px solid;margin-left:5px;width:100%">
<div class="gmail_quote">
<div>I'd be really curious to see the entire CLI log of the call, with verbose set to 6 and AGI debug enabled, from when the call first comes in to when it's hung up, including the execution of the *9 feature code. Also, knowing which version of Asterisk and DAHDI we're dealing with here couldn't hurt<br>
<br></div>
</div>
</blockquote>
</div><div class="gmail_quote">The output is pretty same. I can enable DTMF debugging, but can't imagine how could it help us:</div>
<div class="gmail_quote">
<p>-- Launched AGI Script /etc/asterisk/agi/<a href="http://map.pl" target="_blank">map.pl</a></p><br></div></div></blockquote><div><br>What I meant was, let's see the CLI output of the entire call, from the time it starts, to the time it stops. Something like the following:<br>
<br> -- Accepting call from 'XXXXXXXXXX' to 'YYYYYYYYYY' on channel 0/16, span 1<br> -- Executing [YYYYYYYYYY@incoming-pri:1] Wait("DAHDI/16-1", "2") in new stack<br> -- Executing [YYYYYYYYYY@incoming-pri:2] Verbose("DAHDI/16-1", "Incoming call from XXXXXXXXXX to Main Line YYYYYYYYYY on 03/29/12 at 14:39:15.") in new stack<br>
-- Executing [YYYYYYYYYY@incoming-pri:3] Goto("DAHDI/16-1", "remote-phones,7999,1") in new stack<br> -- Goto (remote-phones,7999,1)<br> -- Executing [7999@remote-phones:1] Verbose("DAHDI/16-1", "Trying extension 7999 on remote host remote.") in new stack<br>
-- Executing [7999@remote-phones:2] Dial("DAHDI/16-1", "SIP/7999@pbx-remote") in new stack<br> == Using SIP RTP CoS mark 5<br> == Using UDPTL CoS mark 5<br> -- Called 7999@pbx-remote<br> -- SIP/pbx-remote-00000405 answered DAHDI/16-1<br>
-- Channel 0/16, span 1 got hangup request, cause 16<br> == Spawn extension (remote-phones, 7999, 2) exited non-zero on 'DAHDI/16-1'<br> -- Hungup 'DAHDI/16-1'<br><br>But with the AGI debug thrown in the middle where appropriate.<br>
</div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div class="gmail_quote"><p></p>
</div><div class="im">
<blockquote type="cite" style="padding-left:5px;border-left:#1010ff 2px solid;margin-left:5px;width:100%">
<div class="gmail_quote">
<div><br>To the OP - just trying to think outside the box here, but what if instead of calling the AGI directly from the features.conf feature code, you wrote a Macro or GoSub that you could then use as your application, and within the Macro / GoSub you executed your AGI?</div>
</div>
</blockquote>
</div><p>I'd love to, but I need that script to run only when user hits some key combo during call. All I was able to find regarding that, was using features.conf and dynamic application. If you can advise me some workaround - I would appreciate.</p>
<br clear="all"></div></blockquote><div><br>To do this, you change your features.conf setting like so:<br><br>parse => *9,peer/both,Macro,Parse<br><br>And you add something like this to your extensions.conf:<br><br>[macro-Parse]<br>
exten => s,1,Verbose(Parsing AGI variables)<br>exten => s,n,AGI(<a href="http://map.pl">map.pl</a>)<br><br>Assuming your <a href="http://map.pl">map.pl</a> is in the place where your asterisk looks for agi (by default this is /var/lib/asterisk/agi-bin), otherwise include the entire path to the file.<br>
<br></div></div><br>-- <br>Thanks,<br>--Warren Selby, dCAP<br><a href="http://www.selbytech.com" target="_blank">http://www.SelbyTech.com</a><br><br>