Summary: | ASTERISK-26117: [patch] app_queue: Agent gets auto-paused if SIP client re-registers when call is placed | ||
Reporter: | Richard Miller (ulogic) | Labels: | patch |
Date Opened: | 2016-06-16 13:35:18 | Date Closed: | |
Priority: | Minor | Regression? | No |
Status: | Open/New | Components: | Applications/app_queue |
Versions: | 11.22.0 13.9.1 | Frequency of Occurrence | Occasional |
Related Issues: | |||
Environment: | Attachments: | ( 0) app_queue-11.22.0.diff ( 1) app_queue-13.9.1.diff | |
Description: | If a SIP client happens to be re-registering at the very instant a call is being dispatched, an agent can get put on auto-pause. Rather than trying to address this in the SIP channel driver, a simple workaround is to not enable the auto-pause option unless the elapsed time is greater than one second.
[06-03 07:19:51.004] VERBOSE[4040] chan_sip.c: [06-03 07:19:51.004] -- Registered SIP '6341' at 4.26.209.2:14238 [06-03 07:19:51.062] VERBOSE[28491][C-00000bc4] netsock2.c: [06-03 07:19:51.062] == Using SIP RTP TOS bits 184 [06-03 07:19:51.062] VERBOSE[28491][C-00000bc4] netsock2.c: [06-03 07:19:51.062] == Using SIP RTP CoS mark 5 [06-03 07:19:51.063] VERBOSE[28491][C-00000bc4] app_queue.c: [06-03 07:19:51.063] -- Called SIP/6341 [06-03 07:19:51.103] VERBOSE[28491][C-00000bc4] app_queue.c: [06-03 07:19:51.103] -- Nobody picked up in 0 ms [06-03 07:19:51.108] VERBOSE[4040] chan_sip.c: [06-03 07:19:51.108] -- Unregistered SIP '6341' [06-03 07:19:51.225] VERBOSE[4040] chan_sip.c: [06-03 07:19:51.225] -- Registered SIP '6341' at 4.26.209.2:14238 [06-03 07:19:51.276] VERBOSE[28491][C-00000bc4] app_queue.c: [06-03 07:19:51.276] -- Auto-Pausing Queue Member SIP/6341 in all queues since they failed to answer on queue XXXXX | ||
Comments: | By: Asterisk Team (asteriskteam) 2016-06-16 13:35:19.699-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. 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: Richard Miller (ulogic) 2016-06-16 14:38:16.732-0500 Don't auto-pause on no answer unless more than a second has elapsed. By: Rusty Newton (rnewton) 2016-06-16 17:38:47.379-0500 I see you marked the issue as regression, though I don't see an indication that previous versions worked the way you want it to work (which is probably a good way for it to work). Are you sure this was working differently in previous versions of 11 or 13? Was the regression mark a mistake? Once you've followed the Code Review process [1] and submitted your code to Gerrit [2] be sure to edit this JIRA issue and add the Gerrit review URL in the appropriate field. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Code+Review [2] https://wiki.asterisk.org/wiki/display/AST/Gerrit+Usage By: Richard Miller (ulogic) 2016-06-16 19:22:01.013-0500 I did not mean to mark this as a regression. Changed regression status to No. |