[asterisk-app-dev] WebSocket Stasis Control Best Practice
Krandon
krandon.bruse at gmail.com
Tue Jul 15 19:22:22 CDT 2014
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:
> Created - https://issues.asterisk.org/jira/browse/ASTERISK-24043
>
> --
> KB
>
>
> On Monday, July 14, 2014 at 6:35 PM, Krandon wrote:
>
> > No problem! On it
> >
> > --
> > KB
> >
> >
> > On Monday, July 14, 2014 at 6:23 PM, Matthew Jordan wrote:
> >
> > > On Mon, Jul 14, 2014 at 5:54 PM, Krandon <krandon.bruse at gmail.com (mailto:krandon.bruse at gmail.com)> wrote:
> > > > I am getting StasisEnd (which is to be expected when using the /continue
> > > > with the query arguments of context default, priority 1 and exten amdme) -
> > > > then getting a ChannelDialplan event with the application AppDial2 (not sure
> > > > how exactly) - followed immediately by a channel destruction. In the
> > > > ChannelDestroyed 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 is
> > > > happening from the Asterisk console as well. Even with verbose 10 and debug
> > > > 10 it just shows:
> > > >
> > > > -- Called vendor/12565551323
> > > >
> > > > -- SIP/vendor-00000007 is making progress
> > > > -- SIP/flowroute-00000007 answered
> > > > > Launching Stasis(vb,{"Lots of json arguments":"woo"}) on
> > > > SIP/vendor-00000007
> > > >
> > > > It 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 are
> > > starting up a pbx stack on channels that were originated into Stasis
> > > directly (as opposed to first going into the dialplan).
> > >
> > > It shouldn't be a terribly hard fix - mind opening an issue for it? A
> > > log illustrating it would be helpful, just to make sure we aren't
> > > crazy.
> > >
> > > --
> > > Matthew Jordan
> > > Digium, Inc. | Engineering Manager
> > > 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
> > > Check us out at: http://digium.com & http://asterisk.org
> > >
> > > _______________________________________________
> > > asterisk-app-dev mailing list
> > > asterisk-app-dev at lists.digium.com (mailto:asterisk-app-dev at lists.digium.com)
> > > http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev
> > >
> > >
> > >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-app-dev/attachments/20140715/852dfb33/attachment.html>
More information about the asterisk-app-dev
mailing list