| Summary: | ASTERISK-12484: QueueMember event for QueueStatus action in AMI does not handle memberfilter correctly. | ||
| Reporter: | Alexandru Pirvulescu (sigxcpu) | Labels: | |
| Date Opened: | 2008-07-30 06:08:14 | Date Closed: | 2008-08-01 13:12:36 |
| Priority: | Trivial | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/app_queue |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | When a member with a custom name is added to a queue, it cannot be filtered by its membername, but by its interface name instead. ****** ADDITIONAL INFORMATION ****** Example: AddQueueMember(testqueue,Local/1000@to-agents/n,,,Agent1000,Custom:1000); This agent has an interface named "Local/1000@to-agents/n" but its name is "Agent1000". If I originate a QueueStatus action filtered by this agent name, not QueueMember event is returned. If the action filters by its interface name ("Local/1000....") the things are working as expected. As I've looked in the code of app_queue.c, it checks if the member filter is specified and, if it is, it compares it with interface name only. Wouldn't be easier for the QueueStatus action too look both for interface name and member name? | ||
| Comments: | By: Mark Michelson (mmichelson) 2008-08-01 13:12:33 Hmm, I fixed this already but apparently didn't close the issue. Sorry about that. This was fixed in Asterisk trunk in SVN revision 134598 and in Asterisk 1.6.0 in SVN revision 134599. | ||