[Home]

Summary:ASTERISK-26512: app_queue: DAHDI queue member isn't delivered calls after the first
Reporter:Daniel (danielp)Labels:
Date Opened:2016-10-27 17:06:24Date Closed:2017-12-25 09:06:04.000-0600
Priority:MajorRegression?Yes
Status:Closed/CompleteComponents:Applications/app_queue
Versions:11.23.0 11.24.1 Frequency of
Occurrence		Constant
Related
Issues:
Environment:Attachments:
Description:I have one DAHDI and some SIP members in my queue. After a fresh start of an asterisk instance and calling this queue, all members are ringing, as it should be.

But after the DAHDI member answer the phone one time, this member didn't ringing for all following calls.

This problem exists since 11.23.0. Last working version was 11.22.0. I think it has something to do with this change: ASTERISK-26133

Here my queue configuration:

{code:title=queues.conf}
[verkauf]
strategy = ringall
timeout = 40
retry = 20
ringinuse = no
servicelevel = 20
member => DAHDI/g2/0
member => SIP/11F
member => SIP/13M
member => SIP/16F
member => SIP/18M
{code}

And here some log. First call coming in, DAHDI member answer the call and hang up. New call coming in. But now, the DAHDI member didn't ringing.

{code:title=log}
telefon*CLI>
[Oct 26 15:40:55]     -- Executing [2390060@Ext:4] Queue("DAHDI/i1/0171987654321-a", "verkauf,rt,300") in new stack
...snip...
[Oct 26 16:40:55]     -- SIP/11F-00000005 is ringing
[Oct 26 16:40:55]     -- DAHDI/i3/0-1 is ringing
[Oct 26 16:40:59]     -- DAHDI/i3/0-1 connected line has changed. Saving it until answer for DAHDI/i1/0171987654321-a
[Oct 27 16:40:59]     -- DAHDI/i3/0-1 answered DAHDI/i1/0171987654321-a
[Oct 26 16:41:53]     -- Hungup 'DAHDI/i3/0-1'
...snip...

telefon*CLI> queue show verkauf
verkauf has 0 calls (max unlimited) in 'ringall' strategy (5s holdtime, 54s talktime), W:0, C:1, A:1, SL:100.0% within 20s
  Members:
     SIP/16F (ringinuse disabled) (Not in use) has taken no calls yet
     DAHDI/g2/0 (ringinuse disabled) (Unknown) has taken 1 calls (last was 199 secs ago)
     SIP/18M (ringinuse disabled) (Not in use) has taken no calls yet
     SIP/11F (ringinuse disabled) (Not in use) has taken no calls yet
     SIP/13M (ringinuse disabled) (Not in use) has taken no calls yet
  No Callers

telefon*CLI>
[Oct 26 15:42:10]     -- Accepting call from '0171987654321' to '2390060' on channel 0/1, span 1
[Oct 26 15:42:10]     -- Executing [2390060@Ext:1] Answer("DAHDI/i1/0171987654321-b", "") in new stack
[Oct 26 15:42:10]     -- Executing [2390060@Ext:2] Queue("DAHDI/i1/0171987654321-b", "verkauf,rt,300") in new stack
[Oct 26 15:42:10]     -- SIP/11F-00000012 is ringing
[Oct 26 15:42:10]     -- SIP/16F-00000013 is ringing
[Oct 26 15:42:11]     -- SIP/18M-00000014 is ringing
[Oct 26 15:42:11]     -- SIP/13M-00000015 is ringing
[Oct 26 15:42:13]     -- Span 1: Channel 0/1 got hangup request, cause 16
[Oct 26 15:42:13]   == Spawn extension (Ext, 2390060, 4) exited non-zero on 'DAHDI/i1/0171987654321-b'
[Oct 26 15:42:13]     -- Hungup 'DAHDI/i1/0171987654321-b'
telefon*CLI>
{code}


With this workaround the DAHDI member will be called on every call.

{code:title=queues.conf}
[verkauf]
;member => DAHDI/g2/0
member => Local/0@queuedahdifix
{code}

{code:title=extensions.conf}
[queuedahdifix]
exten => 0,1,Dial(DAHDI/g2/0,,tT)
{code}
Comments:By: Asterisk Team (asteriskteam) 2016-10-27 17:06:24.477-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: Joshua C. Colp (jcolp) 2017-12-18 05:40:41.392-0600

Is this issue still applicable in Asterisk 13 with the last round of changes that occurred to app_queue for device state changes? If so please attach a fresh log showing the issue and the state of things.
By: Daniel (danielp) 2017-12-25 09:06:05.265-0600

Problem no longer occurs with Asterisk 15. Asterisk 13 i don't know.

I don't use dahdi channels in queue any more. And I have new server-hardware, new version of Ubuntu and Asterisk, now with pjsip (and still dahdi).

But I tested a dahdi channel in queue today. My problem described above no longer occurs.

srv*CLI> core show version
Asterisk 15.1.5 built by root @ srv on a x86_64 running Linux on 2017-12-24 13:54:47 UTC
srv*CLI> queue show verkauf
verkauf has 0 calls (max unlimited) in 'ringall' strategy (9s holdtime, 8s talktime), W:0, C:3, A:0, SL:100.0%, SL2:100.0% within 20s
  Members:
     PJSIP/12F (ringinuse disabled) (Not in use) has taken no calls yet
     DAHDI/g2/0 (ringinuse disabled) (Unknown) has taken 3 calls (last was 3 secs ago)
  No Callers