[asterisk-bugs] [DAHDI-linux 0016048]: [patch] wcbxxp fails reading signalling

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16048 
====================================================================== 
Reported By:                Odicha
Assigned To:                mattf
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   16048
Category:                   wcb4xxp
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     assigned
JIRA:                        
Reviewboard Link:            
====================================================================== 
Date Submitted:             2009-10-08 20:39 CDT
Last Modified:              2009-11-23 13:38 CST
====================================================================== 
Summary:                    [patch] wcbxxp fails reading signalling
Description: 
The problem is detected in the calls that the package CONNECT includes an
information element type number connected "(in calls to the bedside of a
call center can inform the caller of the number that really has heeded the
call).
The error is not due to the ease, but the size of the package.
By placing an analyzer monitoring basic access, we see that  the operator
sends the package (correct) and that the receiver asterisk (namely dahdi)
has invented a character.
We get at log something like this chan_dahdi.c:10710 dahdi_pri_error: XXX
Message longer than it should be?? XXX
-- Processing IE 41 (cs0, Date/Time)
-- Processing IE 76 (cs0, Connected Number)
chan_dahdi.c:10710 dahdi_pri_error: XXX Message longer than it should be??
XXX
====================================================================== 

---------------------------------------------------------------------- 
 (0114162) alecdavis (reporter) - 2009-11-23 13:38
 https://issues.asterisk.org/view.php?id=16048#c114162 
---------------------------------------------------------------------- 
Although I haven't got a router that causes this anymore :(
The patch while the router was alive did fix the problem, for a number of
test calls.

Regarding the success rate reported in
https://issues.asterisk.org/view.php?id=16048#c112929 of 'once' after a console
'dahdi restart', I'm not so sure now, as the configuration I had, was to
echocancelwhenbridged=yes, which would never have worked as reported in
https://issues.asterisk.org/view.php?id=16151 

Speculation: I guess it's possible the chan_dahdi variable p->digital was
uninitialised for the first call and worked. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-11-23 13:38 alecdavis      Note Added: 0114162                          
======================================================================