<div>
<span style="font-size: 14px;">Created - </span><a href="https://issues.asterisk.org/jira/browse/ASTERISK-24043">https://issues.asterisk.org/jira/browse/ASTERISK-24043</a>
</div>
<div><div><br></div><div>-- </div><div>KB<br></div><div><br></div></div>
<p style="color: #A0A0A8;">On Monday, July 14, 2014 at 6:35 PM, Krandon wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div>
<div>
<span style="font-size: 14px;">No problem! On it</span>
</div>
<div><div><br></div><div>-- </div><div>KB<br></div><div><br></div></div>
<p style="color: #A0A0A8;">On Monday, July 14, 2014 at 6:23 PM, Matthew Jordan wrote:</p><blockquote type="cite"><div>
<span><div><div><div>On Mon, Jul 14, 2014 at 5:54 PM, Krandon <<a href="mailto:krandon.bruse@gmail.com">krandon.bruse@gmail.com</a>> wrote:</div><blockquote type="cite"><div><div>I am getting StasisEnd (which is to be expected when using the /continue</div><div>with the query arguments of context default, priority 1 and exten amdme) -</div><div>then getting a ChannelDialplan event with the application AppDial2 (not sure</div><div>how exactly) - followed immediately by a channel destruction. In the</div><div>ChannelDestroyed event, it even shows the right area of the dial plan:</div><div><br></div><div> (</div><div> [context] => default</div><div> [priority] => 1</div><div> [exten] => amdme</div><div> )</div><div><br></div><div>However, it never reaches amdme. It's difficult to track down what is</div><div>happening from the Asterisk console as well. Even with verbose 10 and debug</div><div>10 it just shows:</div><div><br></div><div> -- Called vendor/12565551323</div><div><br></div><div> -- SIP/vendor-00000007 is making progress</div><div> -- SIP/flowroute-00000007 answered</div><div> > Launching Stasis(vb,{"Lots of json arguments":"woo"}) on</div><div>SIP/vendor-00000007</div><div><br></div><div>It doesn't show the call being hung up/any errors. A little help please!</div></div></blockquote><div><br></div><div>That actually looks like a legitimate bug. I don't think we are</div><div>starting up a pbx stack on channels that were originated into Stasis</div><div>directly (as opposed to first going into the dialplan).</div><div><br></div><div>It shouldn't be a terribly hard fix - mind opening an issue for it? A</div><div>log illustrating it would be helpful, just to make sure we aren't</div><div>crazy.</div><div><br></div><div>-- </div><div>Matthew Jordan</div><div>Digium, Inc. | Engineering Manager</div><div>445 Jan Davis Drive NW - Huntsville, AL 35806 - USA</div><div>Check us out at: <a href="http://digium.com">http://digium.com</a> & <a href="http://asterisk.org">http://asterisk.org</a></div><div><br></div><div>_______________________________________________</div><div>asterisk-app-dev mailing list</div><div><a href="mailto:asterisk-app-dev@lists.digium.com">asterisk-app-dev@lists.digium.com</a></div><div><a href="http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev">http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev</a></div></div></div></span>
</div></blockquote><div>
<br>
</div>
</div></div></span>
</blockquote>
<div>
<br>
</div>