[asterisk-bugs] [Asterisk 0014014]: DAHDI group dials/members broken with AddQueueMember / queue member add

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14014 
====================================================================== 
Reported By:                kebl0155
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   14014
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.6.0.1 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-12-03 09:44 CST
Last Modified:              2008-12-17 11:20 CST
====================================================================== 
Summary:                    DAHDI group dials/members broken with AddQueueMember
/ queue member add
Description: 
We have Queues, and we dial the agent's phones directly over ZAP (now
DAHDI).  The agents are dynamic, and we used to add and remove them to/from
the queue using:

add queue member ZAP/r2/0008 to CustServ

Having upgraded to DAHDI and Asterisk 1.6.0.1, we now use:

add queue member DAHDI/r2/0008 to CustServ

This does add the member to the queue, but after a single call is placed
to the agent, the agent becomes invalid and cannot receive further calls.

Furthermore, the member cannot be removed from the queue without restart.
====================================================================== 

---------------------------------------------------------------------- 
 (0096548) putnopvut (administrator) - 2008-12-17 11:20
 http://bugs.digium.com/view.php?id=14014#c96548 
---------------------------------------------------------------------- 
I've uploaded two patches to the issue.

The first patch, 14014.patch contains a fix that will prevent the name of
the interface from changing from "DAHDI/r2/0008" to just "DAHDI/r2." That
much is certain. Because I'm not 100% sure of the method by which device
state reporting is done in chan_dahdi, I also am placing a second patch,
14014_number2.patch, here as well, which should handle the reporting in
case 14014.patch is not enough.

In answer to blitzrage's initial question, this would be a problem which
would effect any interface with multiple '/' characters in it, such as a
DAHDI channel which specified a group and extension. The code in question
appears to be there to deal with Local channels that have a /n on the end
of them, so that the /n is  stripped from the string when comparing to the
interface provided.

So in summary, I suggest trying 14014.patch first, and if the problem is
not completely solved, then try using 14014_number2.patch. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-12-17 11:20 putnopvut      Note Added: 0096548                          
======================================================================