[asterisk-bugs] [Asterisk 0015291]: Received invalid event that had no device IE
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Dec 10 06:13:15 CST 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=15291
======================================================================
Reported By: kaoe
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 15291
Category: CDR/General
Reproducibility: always
Severity: minor
Priority: normal
Status: acknowledged
Asterisk Version: SVN
JIRA:
Regression: Yes
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-06-08 18:52 CDT
Last Modified: 2009-12-10 06:13 CST
======================================================================
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.
======================================================================
----------------------------------------------------------------------
(0115012) davidw (reporter) - 2009-12-10 06:13
https://issues.asterisk.org/view.php?id=15291#c115012
----------------------------------------------------------------------
The Channel: side. AMI Originate establishes a call to the channel before
running the application or calling the extension. It is a failure to
establish that channel that takes it down the path that eventually produces
this message. Failures on the application or extension are handled
normally.
The failure to establish the channel is either a support issue, or
requires a new bug report. The current issue is only about how that
failure gets reported. In our cases the actual failure is not Asterisk's
fault.
Issue History
Date Modified Username Field Change
======================================================================
2009-12-10 06:13 davidw Note Added: 0115012
======================================================================
More information about the asterisk-bugs
mailing list