[asterisk-bugs] [JIRA] Closed: (DAHLIN-102) [patch] Specify default signaling for FXS and FXO modules

[Shaun Ruffell (JIRA)]

     [ https://issues.asterisk.org/jira/browse/DAHLIN-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shaun Ruffell closed DAHLIN-102.
--------------------------------

    Resolution: Fixed

Kinsey: In an effort to close out some of the old issues each day, I'm going to close this.  a) As written it might prevent the chanconfig callback in the board driver from writing if dahdi_cfg doesn't believe the configuration needs updating and b) The move is for this information to be determined via sysfs. I believe what will happen is that the signalling capabilities will be exported there.

If you disagree, please feel free to reopen.

> [patch] Specify default signaling for FXS and FXO modules
> ---------------------------------------------------------
>
>                 Key: DAHLIN-102
>                 URL: https://issues.asterisk.org/jira/browse/DAHLIN-102
>             Project: DAHDI-Linux
>          Issue Type: New Feature
>          Components: wctdm24xxp
>            Reporter: Kinsey Moore
>         Attachments: defsig.diff
>
>
> Currently, when FXS and FXO modules are loaded, they are not assigned a signaling, and so none is shown in the /proc/dahdi interface.  With this small patch which applies cleanly against trunk and 2.1.0.4 (and I assume the 2.2.0 RCs as well), the kewlstart signaling variant is selected as a default.  This allows configuration generators, such as dahdi_genconf, to discover the type and required signaling of each channel without resorting to complicated techniques such as parsing dmesg output or probing with dahdi_cfg.  The only other sane default would be the loopstart variant, but it seems to me that kewlstart is pre prevalent.  If I'm wrong about that, the patch can easily be changed to reflect that.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira