[asterisk-bugs] [DAHDI-linux 0016048]: [patch] wcbxxp fails reading signalling
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Oct 30 05:09:45 CDT 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=16048
======================================================================
Reported By: Odicha
Assigned To:
======================================================================
Project: DAHDI-linux
Issue ID: 16048
Category: wcb4xxp
Reproducibility: always
Severity: crash
Priority: normal
Status: confirmed
JIRA:
Reviewboard Link:
======================================================================
Date Submitted: 2009-10-08 20:39 CDT
Last Modified: 2009-10-30 05:09 CDT
======================================================================
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
======================================================================
----------------------------------------------------------------------
(0112929) alecdavis (reporter) - 2009-10-30 05:09
https://issues.asterisk.org/view.php?id=16048#c112929
----------------------------------------------------------------------
I'm having problems (see https://issues.asterisk.org/view.php?id=16151) with
DIGITAL calls connected to a NT port
on B410P and with this patch my success rate changes from none, to once,
then a dahdi restart is required.
before patch I see both as below, call appears to setup, but no data
transfer.
3 !! Unknown IE 207 (cs0, Unknown Information Element)
-- Executing [8200 at phones:1] Dial("DAHDI/ISDN-3-1", "DAHDI/G3/8200")
in new stack
-- Accepting call from '8100' to '8200' on channel 0/2, span 3
-- Requested transfer capability: 0x08 - DIGITAL
-- Called G3/8200
-- DAHDI/ISDN-3-2 is ringing
-- DAHDI/ISDN-3-2 answered DAHDI/ISDN-3-1
-- Native bridging DAHDI/ISDN-3-1 and DAHDI/ISDN-3-2
-- Channel 0/1, span 3 got hangup request, cause 16
-- Hungup 'DAHDI/ISDN-3-2'
or
-- Hungup 'DAHDI/ISDN-3-1'
-- Accepting call from '8100' to '8200' on channel 0/2, span 3
-- Executing [8200 at phones:1] Dial("DAHDI/ISDN-3-3", "DAHDI/G3/8200")
in new stack
-- Requested transfer capability: 0x08 - DIGITAL
-- Called G3/8200
-- DAHDI/ISDN-3-4 is ringing
-- DAHDI/ISDN-3-4 answered DAHDI/ISDN-3-3
-- Native bridging DAHDI/ISDN-3-3 and DAHDI/ISDN-3-4
-- Channel 0/2, span 3 got hangup request, cause 16
-- Hungup 'DAHDI/ISDN-3-4'
== Spawn extension (phones, 8200, 1) exited non-zero on
'DAHDI/ISDN-3-3'
-- Hungup 'DAHDI/ISDN-3-3'
[Oct 30 22:43:47] ERROR[17372]: chan_dahdi.c:13178 dahdi_pri_error: 3 XXX
Message longer than it should be?? XXX
Issue History
Date Modified Username Field Change
======================================================================
2009-10-30 05:09 alecdavis Note Added: 0112929
======================================================================
More information about the asterisk-bugs
mailing list