[asterisk-bugs] [Zaptel 0009496]: [patch] include channel type in channel name

[noreply at bugs.digium.com]

The following issue has been CLOSED 
====================================================================== 
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:                     closed
Zaptel Version:              SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 2394 
Disclaimer on File?:        No 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             04-07-2007 03:09 CDT
Last Modified:              09-06-2007 11:41 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.
====================================================================== 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
09-06-07 11:41  Corydon76      Status                   new => closed       
09-06-07 11:41  Corydon76      Resolution               open => fixed       
======================================================================