[Home]

Summary:ASTERISK-30084: Agent status in queue is wrong
Reporter:adria vidal (adriavidal)Labels:
Date Opened:2022-05-26 10:26:21Date Closed:2022-05-31 06:29:14
Priority:MajorRegression?
Status:Closed/CompleteComponents:Applications/app_queue
Versions:16.23.0 Frequency of
Occurrence
Constant
Related
Issues:
Environment:debian 10,vanilla asteriskAttachments:( 0) debug_log_123456
( 1) messages.queue.broken.agent.02
Description:Using a Queue like these
{noformat}
[test2]
music=default
strategy=ringall
autofill=yes

setinterfacevar=no
setqueueentryvar=no
setqueuevar=no

member => PJSIP/1042
{noformat}
and doing a Queue show test2 via the CLI, system report agent as Busy when is really free :
{noformat}
test2 has 0 calls (max unlimited) in 'ringall' strategy (0s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0%, SL2:0.0% within 0s
  Members:
     PJSIP/1042 (ringinuse enabled)^[0m^[0m^[0m (^[1;32;40mBusy^[0m) has taken no calls yet ^[1;33;40m(login was 1245 secs ago)^[0m
  No Callers
{noformat}
and doing a {{*CLI> asterisk -rx 'core show hints'|grep 1042}}
{noformat}
1042@BLF_Group      : PJSIP/1042            State:Idle            Presence:not_set         Watchers  0
{noformat}
or Ringing when is not.
{noformat}
test2 has 0 calls (max unlimited) in 'ringall' strategy (0s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0%, SL2:0.0% within 0s
  Members:
     PJSIP/1042 (ringinuse enabled)^[0m^[0m^[0m (^[1;32;40mRinging^[0m) has taken no calls yet ^[1;33;40m(login was 1445 secs ago)^[0m
  No Callers
{noformat}
and nothing at hint side neither
{noformat}
1042@BLF_Group      : PJSIP/1042            State:Idle            Presence:not_set         Watchers  0
{noformat}
System have a slow loadaverage

load average: 0.17, 0.11, 0.09


Comments:By: Asterisk Team (asteriskteam) 2022-05-26 10:26:22.197-0500

The severity of this issue has been automatically downgraded from "Blocker" to "Major". The "Blocker" severity is reserved for issues which have been determined to block the next release of Asterisk. This severity can only be set by privileged users. If this issue is deemed to block the next release it will be updated accordingly during the triage process.

By: Asterisk Team (asteriskteam) 2022-05-26 10:26:22.424-0500

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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

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].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

By: Joshua C. Colp (jcolp) 2022-05-26 10:41:08.177-0500

We require additional debug to continue with triage of your issue. Please follow the instructions on the wiki [1] for how to collect debugging information from Asterisk. For expediency, where possible, attach the debug with a '.txt' file extension so that the debug will be usable for further analysis.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information

Please also provide details on the PJSIP usage. For example, is realtime in use? What is the pjsip.conf configuration?

By: adria vidal (adriavidal) 2022-05-26 10:58:58.207-0500

Nothing is detected in the console or in a sngrep when the status changes to Ringing or Busy.

The system is indeed working with PJSIP under realtime.

[system]
threadpool_idle_timeout=20
threadpool_max_size=2048

[global]
user_agent=myPbx 2.1.4
remove_existing=yes
qualify_frequency=300
endpoint_identifier_order=ip,username,anonymous,header,auth_username

[0.0.0.0-udp]
type=transport
protocol=udp
domain=mi.domain.com
bind=0.0.0.0:5060
local_net=10.0.0.0/8
local_net=172.16.0.0/12
local_net=192.168.0.0/16
external_media_address=HIDDEN_PUBLIC_IP
external_signaling_address=HIDDEN_PUBLIC_IP
external_signaling_port=5060
allow_reload=no
tos=cs3
cos=3


What additional debug info can collect? messages or cli with pjsip set logger on show nothing about the extension changing is state from a call

By: Joshua C. Colp (jcolp) 2022-05-26 11:13:16.764-0500

Instructions are linked for getting a full debug log.

By: adria vidal (adriavidal) 2022-05-26 11:26:24.582-0500

moving the agent to a SIP extension (not registered):

rasterisk -rx 'queue show test2'
test2 has 0 calls (max unlimited) in 'ringall' strategy (0s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0%, SL2:0.0% within 0s
  Members:
     SIP/1042 (ringinuse enabled) (Not in use) has taken no calls yet (login was 260 secs ago)
  No Callers

And only after a few minutes


test2 has 0 calls (max unlimited) in 'ringall' strategy (0s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0%, SL2:0.0% within 0s
  Members:
     SIP/1042 (ringinuse enabled) (Unavailable) has taken no calls yet (login was 408 secs ago)
  No Callers





By: adria vidal (adriavidal) 2022-05-26 11:28:32.877-0500

messages log

By: adria vidal (adriavidal) 2022-05-26 11:29:52.692-0500

second messages file

By: Joshua C. Colp (jcolp) 2022-05-26 11:29:58.418-0500

Did you follow the instructions for creating the debug log? As the attached does not contain any debug, or really anything.

By: adria vidal (adriavidal) 2022-05-26 11:35:28.608-0500

activated log as guidelines, attaching new log file


By: Balkrishna Rola (balkrishnar@intellicon.in) 2022-05-26 23:14:41.063-0500

This is fresh installation with Debian 9.9 mate amd

By: adria vidal (adriavidal) 2022-05-27 02:29:28.524-0500

debian 10.12, 8 cores Intel Xeon Virtualized (VMware)

By: Kevin Harwell (kharwell) 2022-05-27 13:08:23.173-0500

I'm still not seeing any debug information in the logs. Please be sure "debug" is listed in the log file channel in _logger.conf_. Also, that at least debug level 5 is set in Asterisk (either set in _asterisk.conf_ or from {{*CLI> core set debug 5}}).

Also what's the output of the following: {{*CLI> pjsip show endpoint 1042}}

It looks like you also have _chan_sip_ configured. Can you post endpoint/peer information from that too? Do you have a peer/host of 1042 defined there too?


By: adria vidal (adriavidal) 2022-05-31 06:26:25.561-0500

after upgrading to Asterisk 16.26.1 Queue reflects ok agent/extension status.

By: Asterisk Team (asteriskteam) 2022-05-31 06:26:25.998-0500

This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable.