| Summary: | ASTERISK-24421: [ARI] appArgs not passed to both legs of local channel | ||
| Reporter: | Jan Svoboda (jan.svoboda) | Labels: | |
| Date Opened: | 2014-10-14 18:05:04 | Date Closed: | 2014-10-14 18:12:36 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Resources/res_ari_channels |
| Versions: | 12.5.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | CentOS Linux 6.5 | Attachments: | |
| Description: | 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@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@default-000000b0;2 . Also, I noticed that if the Local/123@default-000000b0;2 is answered, I receive StasisStart event for Local/123@default-000000b0;1, where the args are present. | ||
| Comments: | By: Joshua C. Colp (jcolp) 2014-10-14 18:12:36.797-0500 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. | ||