Question on implementation of "assigned" uniqueid when creating channels.

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

 



Hi all-

I'm working on the ability to set the uniqueid on channel creation via ami and ari, and I've run into a quandary:

When Asterisk dials over chan_local, it creates a LOCAL/something;1 channel, and another LOCAL/something;2 channel to handle the other end of the call.  If I'm specifying the uniqueid when I originate the call, I would presume it would be set to the ;1 channel, as that's the one I'm actually talking to.  But should there be something identifiable (rather than the standard 012345678.123 uniqueid format) on the ;2 channel?  For example, if I create the ;1 channel as 'MyCustomId', would it be useful to have the uniqueid of the ;2 channel be 'MyCustomId;2' ?

Although it's probably not a good idea, it's not technically impossible to set the same 'MyCustomId' to both channels.  Any other ideas on how best to handle this?

--
Digium logo
Scott Griepentrog
Digium, Inc · Software Developer
445 Jan Davis Drive NW · Huntsville, AL 35806 · US
direct/fax: +1 256 428 6239 · mobile: +1 317 507 4029
Check us out at: http://digium.com · http://asterisk.org
_______________________________________________
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