Hey Matt,
I have to be a bother, but is there anything I can do to help the issue move forward? I'm sure the core dev team is busy with many other things. Is there a bug bounty we can set that may help?
Thanks,
--
KB
On Tuesday, July 15, 2014 at 2:55 PM, Krandon wrote:
--KBOn Monday, July 14, 2014 at 6:35 PM, Krandon wrote:
No problem! On it--KBOn Monday, July 14, 2014 at 6:23 PM, Matthew Jordan wrote:
On Mon, Jul 14, 2014 at 5:54 PM, Krandon <krandon.bruse@xxxxxxxxx> wrote:I am getting StasisEnd (which is to be expected when using the /continuewith the query arguments of context default, priority 1 and exten amdme) -then getting a ChannelDialplan event with the application AppDial2 (not surehow exactly) - followed immediately by a channel destruction. In theChannelDestroyed event, it even shows the right area of the dial plan:([context] => default[priority] => 1[exten] => amdme)However, it never reaches amdme. It's difficult to track down what ishappening from the Asterisk console as well. Even with verbose 10 and debug10 it just shows:-- Called vendor/12565551323-- SIP/vendor-00000007 is making progress-- SIP/flowroute-00000007 answered> Launching Stasis(vb,{"Lots of json arguments":"woo"}) onSIP/vendor-00000007It doesn't show the call being hung up/any errors. A little help please!That actually looks like a legitimate bug. I don't think we arestarting up a pbx stack on channels that were originated into Stasisdirectly (as opposed to first going into the dialplan).It shouldn't be a terribly hard fix - mind opening an issue for it? Alog illustrating it would be helpful, just to make sure we aren'tcrazy.--Matthew JordanDigium, Inc. | Engineering Manager445 Jan Davis Drive NW - Huntsville, AL 35806 - USACheck us out at: http://digium.com & http://asterisk.org_______________________________________________asterisk-app-dev mailing list
_______________________________________________ asterisk-app-dev mailing list asterisk-app-dev@xxxxxxxxxxxxxxxx http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev
