[asterisk-bugs] [JIRA] (ASTERISK-28354) Queue call to Unavailable member

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-28354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=246665#comment-246665 ] 

Asterisk Team commented on ASTERISK-28354:
------------------------------------------

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

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.

> Queue call to Unavailable member
> --------------------------------
>
>                 Key: ASTERISK-28354
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28354
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: 16.2.0
>         Environment: Asterisk 16.2.0
> PJSIP
> CentOS 7
>            Reporter: Vyrva Igor
>              Labels: pjsip
>
> If the Queue parameters are set to ringinuse=yes, then the call occurs including on the Members with the status "unavailable". 
> This leads to Errors in the CLI / logs with the content that these Membranes have the wrong contact
> For example:
> queue.conf:
> [test]
> ringinuse=yes
> member => PJSIP/666,1,Test User
> test extenion
> exten => *666,1,NoOp(Test call)
>  same => n,Queue(test,ct,,,15)
>  same => n,NoOp(${QUEUESTATUS})
>  same => n,Hangup()
> queue show test
> test 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/115 with penalty 1 (ringinuse enabled) (dynamic) (Not in use) has taken no calls yet
>       Test User (PJSIP/666) with penalty 1 (ringinuse enabled) (Unavailable) has taken no calls yet
>    No Callers
> Call
>    -- Executing [*666 at local:1] NoOp("PJSIP/423-00000000", "Test call") in new stack
>     -- Executing [*666 at local:2] Queue("PJSIP/423-00000000", "test,ct,,,15") in new stack
>     -- Started music on hold, class 'default', on channel 'PJSIP/423-00000000'
> [2019-03-27 14:50:52] ERROR[24233]: res_pjsip.c:3500 ast_sip_create_dialog_uac: Endpoint '666': Could not create dialog to invalid URI '666'.  Is endpoint registered and reachable?
> [2019-03-27 14:50:52] ERROR[24233]: chan_pjsip.c:2498 request: Failed to create outgoing session to endpoint '666'
>     -- Called PJSIP/115
> However, if all Members in the Queue are not available, the call is not assigned.
> queue show test
> test has 0 calls (max unlimited) in 'ringall' strategy (0s holdtime, 0s talktime), W:0, C:0, A:1, SL:0.0%, SL2:0.0% within 0s
>    Members: 
>       PJSIP/115 with penalty 1 (ringinuse enabled) (dynamic) (Unavailable) has taken no calls yet
>       Test User (PJSIP/666) with penalty 1 (ringinuse enabled) (Unavailable) has taken no calls yet
>    No Callers
> Call:
>     -- Executing [*666 at local:1] NoOp("PJSIP/423-00000002", "Test call") in new stack
>     -- Executing [*666 at local:2] Queue("PJSIP/423-00000002", "test,ct,,,15") in new stack
>     -- Started music on hold, class 'default', on channel 'PJSIP/423-00000002'
>     -- Stopped music on hold on PJSIP/423-00000002
>     -- Executing [*666 at local:3] NoOp("PJSIP/423-00000002", "TIMEOUT") in new stack
>     -- Executing [*666 at local:4] Hangup("PJSIP/423-00000002", "") in new stack
> In queue_log:
> '2019-03-27 14:50:52.942106', '1553687452.0', 'test', 'NONE', 'ENTERQUEUE', NULL, '', '423', '1', '', ''
> '2019-03-27 14:50:58.066067', '1553687452.0', 'test', 'PJSIP/115', 'RINGCANCELED', NULL, '5121', '', '', '', ''
> '2019-03-27 14:50:58.067558', '1553687452.0', 'test', 'NONE', 'ABANDON', NULL, '1', '1', '6', '', ''
> '2019-03-27 15:02:53.852089', '1553688173.2', 'test', 'NONE', 'ENTERQUEUE', NULL, '', '423', '1', '', ''
> '2019-03-27 15:03:08.867865', '1553688173.2', 'test', 'NONE', 'EXITWITHTIMEOUT', NULL, '1', '1', '15', '', ''
> Although in normal operation we need to only call on those Members that have a status other than "unavailable."
> If you remove ringinuse=yes then the call to the Members with the status "unavailable" is not made. But at the same time the call of Members with the status "in use" is also not made.



--
This message was sent by Atlassian JIRA
(v6.2#6252)