[asterisk-bugs] [JIRA] (ASTERISK-24421) [ARI] appArgs not passed to both legs of local channel

Joshua Colp (JIRA) noreply at issues.asterisk.org
Tue Oct 14 18:13:29 CDT 2014


     [ https://issues.asterisk.org/jira/browse/ASTERISK-24421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua Colp closed ASTERISK-24421.
----------------------------------

    Resolution: Not A Bug

I've answered your email (sorry, I thought I already had) but this is not a bug. In my email I've presented two ways you can make it do what you want.

> [ARI] appArgs not passed to both legs of local channel
> ------------------------------------------------------
>
>                 Key: ASTERISK-24421
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24421
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_ari_channels
>    Affects Versions: 12.5.0
>         Environment: CentOS Linux 6.5
>            Reporter: Jan Svoboda
>
> In my ARI app I am using local channels to route calls back to the app in certain conditions.
> The process is as follows:
> 1. Channel (phone) calls an extension and enters into stasis
> 2. Based on channel variables, extension, accountcode, … it is determined what to do with the channel
> 3. New channel is created (endpoint: LOCAL/123, appArgs: ‘abc')
> 4. App receives StasisStart event with channel Local/123 at default-000000b0;2 and empty args.
> The problem is identifying those (local) channels when they arrive in Stasis, since passed appArgs to the originate action for local channel don’t appear in the StasisStart event for channel Local/123 at default-000000b0;2 .
> Also, I noticed that if the Local/123 at default-000000b0;2 is answered, I receive StasisStart event for Local/123 at default-000000b0;1, where the args are present.



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list