On Thu, Dec 20, 2018, at 2:14 PM, Corey Farrell wrote: > How will the ARI/dialplan integration handle specific extensions? For > example if I have a stasis app which registers itself to dialplan as > 'somecontext', how does this integration decide which extensions are > handled by the app? Does that app get calls for all extensions or only > specific extensions? Do we create a new type of ARI app which would > respond to PBX switch callbacks where all calls go to the stasis router > app which then accepts or rejects calls based on the ARI apps own > extension list? For example if we have a context: > > [from-outside] > exten => 7002052000,1,Stasis(myapp) > exten => 7002052001,1,Stasis(myapp) > How do you envision replicating having these two extensions handled but > all other extensions being invalid?
The context would send all calls to that application (except for the h extension). That application would then be able to move that channel to another application according to its own routing logic if it wanted. -- Joshua C. Colp Digium - A Sangoma Company | Senior Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - US Check us out at: www.digium.com & www.asterisk.org -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
