[asterisk-bugs] [Asterisk-GUI 0017727]: Bridge with channel fails; channel format 0x0 (nothing)
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Jul 28 03:55:14 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17727
======================================================================
Reported By: jacco
Assigned To:
======================================================================
Project: Asterisk-GUI
Issue ID: 17727
Category: General
Reproducibility: sometimes
Severity: major
Priority: normal
Status: new
Asterisk GUI Version: I did not set the version :(
Asterisk Version: 1.6.2.10
JIRA:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2010-07-27 10:59 CDT
Last Modified: 2010-07-28 03:55 CDT
======================================================================
Summary: Bridge with channel fails; channel format 0x0
(nothing)
Description:
about once evey ten times, when trying to bridge an active sip channel with
an active sip channel on a trunk, it fails with the following warning:
[Jul 27 17:28:42] WARNING[5064]: features.c:4583 bridge_exec: Bridge
failed because channel SIP/xxx.xxx.xxx.xxx-000000xx does not exists or we
cannot get its lock (where SIP/xxx.xxx.xxx.xxx-000000xx is SU201 in the
additional information)
======================================================================
----------------------------------------------------------------------
(0125178) jacco (reporter) - 2010-07-28 03:55
https://issues.asterisk.org/view.php?id=17727#c125178
----------------------------------------------------------------------
the same thing happens in version 1.6.2.11-rc2
Issue History
Date Modified Username Field Change
======================================================================
2010-07-28 03:55 jacco Note Added: 0125178
======================================================================
More information about the asterisk-bugs
mailing list