[asterisk-bugs] [Asterisk 0014877]: pri_resolve_span assumes span's channels have consecutive numbers
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Oct 2 13:08:38 CDT 2009
A NOTE has been added to this issue.
======================================================================
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: assigned
Asterisk Version: SVN
JIRA:
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 187963
Request Review:
======================================================================
Date Submitted: 2009-04-11 09:01 CDT
Last Modified: 2009-10-02 13:08 CDT
======================================================================
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.
======================================================================
----------------------------------------------------------------------
(0111803) jpeeler (administrator) - 2009-10-02 13:08
https://issues.asterisk.org/view.php?id=14877#c111803
----------------------------------------------------------------------
Can you provide a chan_dahdi.conf sample (and system.conf if necessary) to
demonstrate this issue? It seems to me that any surprises from module load
order would be found when running dahdi_cfg, which enforces consecutive
channel order.
Issue History
Date Modified Username Field Change
======================================================================
2009-10-02 13:08 jpeeler Note Added: 0111803
======================================================================
More information about the asterisk-bugs
mailing list