[asterisk-bugs] [Asterisk 0017683]: [patch] I could not find an easy way to access DAHDI channel and span number from the dialplan.
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Jul 27 08:32:31 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17683
======================================================================
Reported By: mrwho
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17683
Category: Channels/chan_dahdi/NewFeature
Reproducibility: always
Severity: tweak
Priority: normal
Status: feedback
Asterisk Version: SVN
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 274530
Request Review:
======================================================================
Date Submitted: 2010-07-22 05:52 CDT
Last Modified: 2010-07-27 08:32 CDT
======================================================================
Summary: [patch] I could not find an easy way to access
DAHDI channel and span number from the dialplan.
Description:
I could not find an easy way to access from the dialplan the span and the
PRI channel being used by an Asterisk channel. As a quick solution I
patched chan_dahdi so that it will populate - if applicable - two
variables:
PRI_CHANNEL: the PRI channel number
PRI_SPAN: the PRI span number
These variables can then be used in the dialplan. The patch it's pretty
simple, even if I don't know how much it could be needed by others.
======================================================================
----------------------------------------------------------------------
(0125111) lmadsen (administrator) - 2010-07-27 08:32
https://issues.asterisk.org/view.php?id=17683#c125111
----------------------------------------------------------------------
Hmmm, I see your point :)
OK so at this point we're at a crossroads and need to make an informed
decision. The way to resolve this is to post something to the asterisk-dev
list and get some of the other developers to weigh in on the decision
making. This way we don't waste any more of your time with implementations
that we can't accept :)
So go ahead and ask on asterisk-dev about this issue, and then we can let
the other community developers help us decide what is best.
Thanks for all your work so far!
Issue History
Date Modified Username Field Change
======================================================================
2010-07-27 08:32 lmadsen Note Added: 0125111
======================================================================
More information about the asterisk-bugs
mailing list