Local channel identification in ARI

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

 



Hi,

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 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. Is this the expected behaviour ?

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.

The reason to use local channels in the app is to maintain the routing logic in the app more clean.

     Jan Svoboda
     Software Architect

_______________________________________________
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