[asterisk-bugs] [DAHDI-linux 0015291]: Received invalid event that had no device IE
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Aug 20 13:07:28 CDT 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=15291
======================================================================
Reported By: kaoe
Assigned To:
======================================================================
Project: DAHDI-linux
Issue ID: 15291
Category: wct4xxp
Reproducibility: always
Severity: major
Priority: normal
Status: new
======================================================================
Date Submitted: 2009-06-08 18:52 CDT
Last Modified: 2009-08-20 13:07 CDT
======================================================================
Summary: Received invalid event that had no device IE
Description:
I use Asterisk whith TE410P and 3 weeks ago a upgrade my driver to DAHDI
2.1.0.4, but now I receive error in my E1 dials:
ERROR[26709]: pbx.c:8330 device_state_cb: Received invalid event that had
no device IE
ERROR[26709]: app_queue.c:856 device_state_cb: Received invalid event that
had no device IE
This errors ocurrer after 20 or more simultaneos calls, i use 4 PTSN
connected in this card and the errors ocurer in all. In the other point of
E1 (PSTN) the information is error in E1 frame.
I test to downgrade de version of dahdi or upgrade dahdi to RCx versions
but the error persist in all version tested.
======================================================================
----------------------------------------------------------------------
(0109357) davidw (reporter) - 2009-08-20 13:07
https://issues.asterisk.org/view.php?id=15291#c109357
----------------------------------------------------------------------
For 1.6.1.0, at least, this will happen if the first side of an AMI
Originate, or, presumably the channel side of a call file call, fails.
ast_pbx_outgoing_exten calls ast_pbx_outgoing_cdr_failed to create a call
detail record, after destroying the original channel. This creates a
temporary channel structure in order to issue the CDR, but never gives it a
name. It then calls ast_channel_free, which tries to report a device state
change to INVALID, which has no associated device name. The error isn't
detected until two process switches later.
Either ast_pbx_outgoing_cdr_failed should provide a dummy name, or
ast_channel_free should recognize a special case and not try to report a
device state change.
I discovered this whilst debugging https://issues.asterisk.org/view.php?id=15314
against Asterisk 1.6.1.0,
although it was unrelated to the real problem there.
Issue History
Date Modified Username Field Change
======================================================================
2009-08-20 13:07 davidw Note Added: 0109357
======================================================================
More information about the asterisk-bugs
mailing list