[asterisk-bugs] [Asterisk 0017435]: Strange warning from dahdi channels
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Jun 1 08:49:58 CDT 2010
The following issue has been UPDATED.
======================================================================
https://issues.asterisk.org/view.php?id=17435
======================================================================
Reported By: mtryfoss
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17435
Category: Channels/chan_dahdi
Reproducibility: random
Severity: major
Priority: normal
Status: closed
Asterisk Version: 1.6.1 - SECURITY ONLY! Test 1.6.2
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
Resolution: won't fix
Fixed in Version:
======================================================================
Date Submitted: 2010-06-01 07:01 CDT
Last Modified: 2010-06-01 08:49 CDT
======================================================================
Summary: Strange warning from dahdi channels
Description:
I'm getting these warnings:
[Jun 1 12:49:48] WARNING[25987] chan_dahdi.c: Can't fix up channel from
89 to 90 because 90 is already in use
[Jun 1 12:49:48] WARNING[25987] chan_dahdi.c: Answer requested on channel
0/28 not in use on span 3
[Jun 1 12:49:49] WARNING[25987] chan_dahdi.c: Can't fix up channel from
89 to 90 because 90 is already in use
[Jun 1 12:49:49] WARNING[25987] chan_dahdi.c: Hangup on bad channel 0/28
on span 3
[Jun 1 12:49:50] WARNING[25987] chan_dahdi.c: Whoa, there's no owner,
and we're having to fix up channel 90 to c
hannel 89
[Jun 1 12:49:53] WARNING[25987] chan_dahdi.c: Call specified, but not
found?
[Jun 1 12:49:53] WARNING[25987] chan_dahdi.c: Hangup on bad channel 0/28
on span 3
What's this all about? Asterisk is trying to use a channel which is in
use, or being told so by the telco? Seems to be triggered by an ALERTING
message. Can't find much info on these warnings on google, so I'm trying
here.
I'm using Dahdi 2.3.0 and Libpri 1.4.11.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2010-06-01 08:49 pabelanger Status new => closed
2010-06-01 08:49 pabelanger Resolution open => won't fix
======================================================================
More information about the asterisk-bugs
mailing list