[asterisk-bugs] [Asterisk 0014877]: pri_resolve_span assumes span's channels have consecutive numbers
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Nov 10 08:51:58 CST 2009
The following issue has been CLOSED
======================================================================
https://issues.asterisk.org/view.php?id=14877
======================================================================
Reported By: tzafrir
Assigned To: jpeeler
======================================================================
Project: Asterisk
Issue ID: 14877
Category: Channels/chan_dahdi
Reproducibility: have not tried
Severity: minor
Priority: normal
Status: closed
Asterisk Version: SVN
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 187963
Request Review:
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 2009-04-11 09:01 CDT
Last Modified: 2009-11-10 08:51 CST
======================================================================
Summary: pri_resolve_span assumes span's channels have
consecutive numbers
Description:
pri_resolve-span assumes that the the D channel of a span is at channel
number <base> + 16 / 24 / 3 (for E1/ T1/J1 / BRI, respectively).
This is normalyl the case. But does not apply if channels of the span do
not have consecutive numbers. Which is something that can happen with the
right order of modules loading / unloading sequence in a multi-device
system.
Furthermore, when the function is called it is called with the following
value for the parameter 'offset':
channel - p.chanpos
Thus making this assumption again.
======================================================================
----------------------------------------------------------------------
(0113542) lmadsen (administrator) - 2009-11-10 08:51
https://issues.asterisk.org/view.php?id=14877#c113542
----------------------------------------------------------------------
I'm closing this as unable to reproduce, however feel free to reopen this
issue should you have any further comments. Thanks!
Issue History
Date Modified Username Field Change
======================================================================
2009-11-10 08:51 lmadsen Note Added: 0113542
2009-11-10 08:51 lmadsen Status feedback => closed
======================================================================
More information about the asterisk-bugs
mailing list