| Summary: | ASTERISK-25729: [patch] Extension to device state translations are missing some extension states | ||||
| Reporter: | PK (k-paulius) | Labels: | |||
| Date Opened: | 2016-01-27 00:04:33.000-0600 | Date Closed: | 2020-01-14 11:13:34.000-0600 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | Applications/app_queue | ||
| Versions: | 13.7.0 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | CentOS 6.7 FreePBX FreePBX 12.0.76.2 | Attachments: | |||
| Description: | I have a queue with strategy set to ringall, leavewhenempty set to strict, ringinuse set to yes and all queue members using hints for state_interface. When all available queue agents are on the call, any callers left on the queue get kick out and queue log shows event EXITEMPTY.
When agent is on the phone and there are no callers waiting on the queue "queue show" displays agent status as (In use), but when agent is on the phone + that phone is ringing "queue show" displays status as (Invalid). Turns out extensionstate2devicestate does not have translations for device states "AST_EXTENSION_INUSE | AST_EXTENSION_RINGING" and "AST_EXTENSION_INUSE | AST_EXTENSION_ONHOLD". Complete queue config: {noformat} [1234] announce-frequency=180 announce-holdtime=no announce-position=yes answered_elsewhere=1 autofill=no autopause=no autopausebusy=no autopausedelay=0 autopauseunavail=no joinempty=strict leavewhenempty=strict maxlen=0 memberdelay=0 monitor-join=yes music=inherit penaltymemberslimit=0 periodic-announce-frequency=240 queue-callswaiting=queue-callswaiting queue-thankyou=queue-thankyou queue-thereare=queue-thereare queue-youarenext=queue-youarenext reportholdtime=no retry=1 ringinuse=yes servicelevel=15 strategy=ringall timeout=16 timeoutpriority=conf timeoutrestart=no weight=0 wrapuptime=0 eventmemberstatus=no member=Local/5000@from-queue/n,0,Agent1,hint:5000@ext-local member=Local/5001@from-queue/n,0,Agent2,hint:5001@ext-local member=Local/5002@from-queue/n,0,Agent3,hint:5002@ext-local {noformat} | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2016-01-27 00:04:35.557-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: PK (k-paulius) 2016-01-27 00:09:19.999-0600 Patch By: Joshua C. Colp (jcolp) 2016-01-27 06:36:08.068-0600 If you would like to get this patch in sooner I would suggest following the Patch Contribution Process linked by the initial comment on this issue. By: Rusty Newton (rnewton) 2016-01-27 07:36:11.324-0600 I had to delete your patch since you didn't mark it as a contribution. Patches must be submitted as contribution (and you must have already signed the submission license agreement in order to do that). Please follow the patch contribution process as linked. Thanks! By: Asterisk Team (asteriskteam) 2016-02-10 12:00:20.557-0600 Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines | ||||