Summary:	ASTERISK-25692: app_queue: shared_lastcall does not work when using realtime queues and Local channels
Reporter:	User User (smnv)	Labels:
Date Opened:	2016-01-13 01:26:25.000-0600	Date Closed:
Priority:	Major	Regression?
Status:	Open/New	Components:	Applications/app_queue Channels/chan_local
Versions:	13.6.0	Frequency of Occurrence
Related Issues:	is related to ASTERISK-22589 shared_lastcall is not reliable with realtime queues
Environment:	Ubuntu SMP x86_64, Linux 3.13.0-74-generic PostgreSQL (9.4.4)	Attachments:	( 0) configs.zip ( 1) myDebugLog.txt ( 2) sc_1.png ( 3) screen.zip
Description:	I have the following configuration: - multiple realtime queues and dynamic members of the queue - shared_lastcall is set to "yes" - wrapuptime=7 is set in all queues The problem is that when using local channels, the value of the "last was ХХХ secs ago" of each member of the queue in all queues different. When using SIP channels, the value "last was ХХХ secs ago" of the queue member in all queues are the same.
Comments:	By: Asterisk Team (asteriskteam) 2016-01-13 01:26:26.229-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Rusty Newton (rnewton) 2016-01-14 07:30:05.498-0600 Please attach complete configuration files to the issue. You can attach database dumps (or at a minimum screenshots of the field values) where you don't have static configuration. Can you point out where the issue is demonstrated in your log file? It is quite large. Probably a good idea to include some examples of the CLI output in the scenarios you mention. By: Rusty Newton (rnewton) 2016-01-26 17:26:18.975-0600 How extensive has your testing been with SIP channels? {noformat} When using SIP channels, the value "last was ХХХ secs ago" of the queue member in all queues are the same. {noformat} I'm assuming you have tried this more than a few times? I wonder if ASTERISK-22589 is still an issue in 13.. By: Rusty Newton (rnewton) 2016-02-04 19:00:01.070-0600 Re-attaching reporters myDebugLog file with a .txt extension. By: Sébastien Couture (sysreq) 2016-05-31 14:54:12.882-0500 Looking at your screenshot, your queue members have different "interfaces" and thus would be seen as separate members by your queues. Take the following: {{SIP/1851 (Local/1851-914@queue from SIP/1851)}} The first {{SIP/1851}} on the left is the *member name*, which is more often used as a display name. You could have set it to "914", or "Agent 914", it doesn't matter; the queue won't use that information to actually distribute the call. The {{Local/1851-914@queue}} is the *interface*, which is the entity to which a queue will distribute a call; this is what the "calls taken" and "last call" values are tied to, so if your interfaces are different, those values will also be different. The last {{SIP/1851}} is the *state interface*, which is used by the queue to determine the state of a member; this can be a SIP device, a hint, or nothing; in the latter scenario, the state of the Local channel would then be used. I'm under Asterisk 11 with realtime queues and realtime members that are also Local channels, and when the "interface" part is the same throughout, the "calls taken" and "last call" values will be the same across all queues where the member is logged in. By: Marek Cervenka (cervajs) 2016-12-28 02:52:58.280-0600 duplicate of ASTERISK-22589 ?