[asterisk-bugs] [Zaptel 0009496]: [patch] include channel type in channel name
noreply at bugs.digium.com
noreply at bugs.digium.com
Sun Jul 29 00:48:18 CDT 2007
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=9496
======================================================================
Reported By: tzafrir
Assigned To:
======================================================================
Project: Zaptel
Issue ID: 9496
Category: wctdm
Reproducibility: N/A
Severity: feature
Priority: normal
Status: new
Zaptel Version: SVN
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 2394
Disclaimer on File?: No
Request Review:
======================================================================
Date Submitted: 04-07-2007 03:09 CDT
Last Modified: 07-29-2007 00:48 CDT
======================================================================
Summary: [patch] include channel type in channel name
Description:
Currently there is no simple method to figure out which slot in a wctdm
card has an FXS module, an FXO module or none at all.
The suggested patch adds this information to the card name. Instead of
WCTDM/x/y
(where x is the card number and y is the position in the card), set:
For an empty slot:
WCTDM/x/y:empty
For an FXO module:
WCTDM/x/y:FXO
For an FXS module:
WCTDM/x/y:FXS
This information will then be availble in e.g. the /proc/zaptel interface
and allow automated settings.
Note: the real solution for this would actually be a proper sysfs
interface.
======================================================================
----------------------------------------------------------------------
juggie - 07-29-07 00:48
----------------------------------------------------------------------
So we can close this now?
Issue History
Date Modified Username Field Change
======================================================================
07-29-07 00:48 juggie Note Added: 0068023
======================================================================
More information about the asterisk-bugs
mailing list