Thanks, I solved it using channel variables passed to originate action and also added this option to the asterisk-ari-client ruby gem.
Jan Svoboda
Software Architect
On Wednesday 15 October 2014 at 01:11, Joshua Colp wrote:
Jan Svoboda wrote:Hi,Kia ora,I have a question regarding local channel identification in ARI.In my ARI app I am using local channels to route calls back to the appin certain conditions.The process is as follows:1. Channel (phone) calls an extension and enters into stasis2. Based on channel variables, extension, accountcode, … it isdetermined what to do with the channel3. New channel is created (endpoint: LOCAL/123, appArgs: ‘abc')4. App receives StasisStart event with channelLocal/123@default-000000b0;2 and empty args.The problem is identifying those (local) channels when they arrive inStasis, since passed appArgs to the originate action for local channeldon’t appear in the StasisStart event. Is this the expected behaviour ?Yes - You've actually got 2 legs. When you specify the appArgs that onlycontrols the leg which executes the Stasis application upon the outgoingleg being answered. It is not passed on to the outgoing leg. Toaccomplish what you want though you can either use inherited channelvariables to pass this information on to the other leg OR you canspecify the identifier for each leg when originating and store thatinformation in your application. When your application is invoked oneach channel you can check using the identifier and know to do somethingelse.Cheers,--Joshua ColpDigium, Inc. | Senior Software Developer445 Jan Davis Drive NW - Huntsville, AL 35806 - USCheck us out at: www.digium.com & www.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
