[My first attempts to send this to the list seems not to have worked; I apologize for any duplicates.]
Hello: I've been playing a bit with the AddQueueMember application and have realized that its handling of SIP interfaces (and probably other types that use a similar channel naming convention) is a bit wrong. Basically, if you don't specify an interface to be added to the queue, it will take the name of the calling channel and add that to the queue. In the case of a SIP channel, this is something like "SIP/blah-XXXX" where XXXX is some random string to differentiate between various calls to/from the same entity. Adding this whole thing I've put together a fix to this that looks for SIP interfaces and truncates the name beginning with the final "-". This works fine, but won't work for other types of channels that use similar naming conventions unless I manually add similar logic for each of them. So, finally, to a question: is there a generalized way to derive the callable name of a given channel other than stripping off some of the text, as I've been doing? I was hoping that the ast_channel structure would contain something useful, but I don' t see anything that will obviously help me out. Jordyn _______________________________________________ Asterisk-Dev mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-dev
