Re: WebSocket Stasis Control Best Practice

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



We had a similar discussion a while back about executing dialplan applications from within ARI. Please see: http://lists.digium.com/pipermail/asterisk-app-dev/2014-February/000367.html

Although this doesn't provide you with an answer, it may help you to understand the current thinking of the asterisk/ari development team

Ben

> Max Wrote:
Very good question as I too encountered these difficultiy of not beign able to call all other Asterisk commands.
My solution was calling /channel/continue and returning from Stasis back to dialplan and then going again into Stasis.
But I feel we need a more integral solution like we had in AGI.
IMHO.

Regards,
Max.
2014-06-16 6:24 GMT+04:00 Krandon <krandon.bruse@xxxxxxxxx>:
Hello Asterisk friends, 

I am currently interfacing with Asterisk through ARI and loving the experience so far. I have successfully originated calls and dumped them into my Stasis app. I am trying to figure out what the best way is to send a channel into an Application. The current architecture for /channels/{id}/play works well for the majority of my app, but I am running into a block figuring out how to interact with Asterisk dialplan applications.

To give an example - I submit an originate to go to SIP/vendor/phoneNumber - with the other leg going to App: myStasisApp, {"soundFile":"blah"}. That works fine (with the proper quote escaping). Now my Stasis app has received the channelID to which we can do a lot of neat stuff. Say I play a sound to the user but then want to call the app WaitForSilence. What's the best way to do this? I may be misinterpreting the intended use of both Stasis and ARI - but I am curious to see what your thoughts are.

Also, for the stasis app to get a list of arguments, I am passing it through as JSON. So far that is working fine - but I wanted to see if there was a better way to get a list/array of app args to Stasis.

Forgive me if there is an easy solution - through digging and poking the last few days, I have not been able to find the intended use case or even a use case.

Thanks!

-- 
KB

_______________________________________________
asterisk-app-dev mailing list
asterisk-app-dev@xxxxxxxxxxxxxxxx
http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev

_______________________________________________
asterisk-app-dev mailing list
asterisk-app-dev@xxxxxxxxxxxxxxxx
http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev





[Index of Archives]     [Asterisk SS7]     [Asterisk Announcements]     [Asterisk Users]     [PJ SIP]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Linux API]

  Powered by Linux