Stasis continueInDialplan - control remains in ARI app?

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

 



Hi dear developers!
I have a question like this.
Imagine that I call to 10:

exten => 10,1,Set(CONNECT_TO_CONTEXT=01@public-in)
exten => 10,2,Stasis(test)

My  test ARI app:



def ari_app_connect_to_context(channel, event):
result = channel.getChannelVar(variable='CONNECT_TO_CONTEXT')
context_exten = result.get('value')
if context_exten:
extension, context = context_exten.split('@')
channel.continueInDialplan(context=context, extension=extension, priority=1)


And 01@public-in is:

exten => 01,1,Answer
exten => 01,n,Queue(support)

What I am trying to do is to keep control over the channel in my Stasis app.

So when I accept a call to Stasis and then pass it over to dialplan - should not that channel stay in Stasis controlled channels?

Why not keep it there to have control from ARI app?

Is it possible to implement or breaks ARI philosophy ?

Thanks.

Regards,
Max.






_______________________________________________
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