[Home]

Summary:ASTERISK-14891: [patch] Asterisk ignores changes to realtime queue member table after initial startup
Reporter:agjohnson (agjohnson)Labels:
Date Opened:2009-09-25 14:52:09Date Closed:2011-11-02 20:04:58
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Applications/app_queue
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) 15967.diff
Description:On startup the member polycom1 was a member of the queue frish.  I then updated the queue member table to change the member to polycom2.  This change is not picked up, even though Asterisk does query the table.

pbx2*CLI> queue show frish
frish        has 0 calls (max unlimited) in 'ringall' strategy (0s holdtime, 0s talktime), W:0, C:0, A:1, SL:0.0% within 0s
  Members:
     polycom1 (SIP/polycom1) with penalty 1 (realtime) (Not in use) has taken no calls yet
  No Callers

pbx2*CLI>

Queries that realtime does:

                  1516 Query       SELECT * FROM queue_member_table WHERE interface LIKE '%' AND queue_name = 'frish' ORDER BY interface
                  1516 Query       SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED
                  1516 Query       SELECT * FROM queue_table WHERE name = 'frish'
                  1516 Query       SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED
                  1516 Query       SELECT * FROM queue_member_table WHERE interface LIKE '%' AND queue_name = 'frish' ORDER BY interface


Actual information in the table:
uniqueid, membername, queue_name, interface, penalty, paused
1, 'polycom2', 'Frish', 'SIP/polycom2', 1, 0

Reloading the extconfig and app_queue.so module does not result in the right information being picked up.  Restarting Asterisk results in the correct member being shown as part of the queue.
Comments:By: agjohnson (agjohnson) 2009-10-21 12:19:51

In 1.6.1.6, modifying the queue table does not result in the changes being recognized until app_queue.so is unloaded and loaded again.  Issueing a module reload app_queue.so does not cause the changes to be recognized.
By: agjohnson (agjohnson) 2009-10-21 12:43:24

This problem does not show up in Asterisk 1.6.0.15
By: agjohnson (agjohnson) 2009-10-21 13:04:00

Problem is in Asterisk 1.6.2.0-rc3
By: agjohnson (agjohnson) 2009-10-21 13:10:37

Problem is in Asterisk 1.6.1.7-rc2
By: agjohnson (agjohnson) 2009-10-21 13:19:04

Issue is not in Asterisk 1.6.0.16-rc2
By: Elazar Broad (ebroad) 2009-10-21 13:52:50

Per my discussion with the reporter on #asterisk-bugs, the attached patch seems to resolve the issue.
By: agjohnson (agjohnson) 2009-10-26 14:59:57

The patch resolves the issue on my server.
By: Richard Mudgett (rmudgett) 2011-10-05 12:43:11.497-0500

Is this still a problem in Asterisk v1.8?

Also the attached patch [^15967.diff] cannot be correct as it disables rt_uniqueid processing.
By: Richard Mudgett (rmudgett) 2011-10-26 16:33:14.840-0500

Any status update?
By: Richard Mudgett (rmudgett) 2011-11-02 20:04:58.428-0500

No response from reporter.