[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
Fri Mar 4 09:22:08 CST 2011
The following issue has been RESOLVED.
======================================================================
https://issues.asterisk.org/view.php?id=17683
======================================================================
Reported By: mrwho
Assigned To: rmudgett
======================================================================
Project: Asterisk
Issue ID: 17683
Category: Channels/chan_dahdi
Reproducibility: always
Severity: minor
Priority: normal
Status: resolved
Asterisk Version: SVN
JIRA: SWP-2859
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 274530
Request Review:
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 2010-07-22 05:52 CDT
Last Modified: 2011-03-04 09:22 CST
======================================================================
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.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0018603 [patch] Get Real Channel of a Dahdi Call
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2011-03-04 09:22 svnbot Status assigned => resolved
2011-03-04 09:22 svnbot Resolution open => fixed
======================================================================
More information about the asterisk-bugs
mailing list