[asterisk-bugs] [JIRA] Closed: (DAHLIN-166) Support for single freq signaling does not appear to exist
Shaun Ruffell (JIRA)
noreply at issues.asterisk.org
Mon Sep 10 08:47:07 CDT 2012
[ https://issues.asterisk.org/jira/browse/DAHLIN-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shaun Ruffell closed DAHLIN-166.
--------------------------------
Resolution: Won't Fix
Closing this for the same reasons as DAHLIN-265. sf was only available as part of ztcfg_dude which doesn't compile cleanly anymore. I believe for this to move forward someone will need to step forward with a patch.
Please feel free to reopen if anyone wants to debate this.
> Support for single freq signaling does not appear to exist
> ----------------------------------------------------------
>
> Key: DAHLIN-166
> URL: https://issues.asterisk.org/jira/browse/DAHLIN-166
> Project: DAHDI-Linux
> Issue Type: Bug
> Components: Utilities
> Affects Versions: 2.2.0.2
> Reporter: Arlen Raasch
> Severity: Minor
>
> Contrary to what one would expect by reading the system.conf examples, no provision for single frequency signaling appears to exist.
> From system.conf:
> # sf::
> # Channel(s) are signalled using in-band single freq tone.
> # Syntax as follows:
> #
> # channel# => sf:<rxfreq>,<rxbw>,<rxflag>,<txfreq>,<txlevel>,<txflag>
> #
> # rxfreq is rx tone freq in Hz, rxbw is rx notch (and decode)
> # bandwith in hz (typically 10.0), rxflag is either 'normal' or
> # 'inverted', txfreq is tx tone freq in hz, txlevel is tx tone
> # level in dbm, txflag is either 'normal' or 'inverted'. Set
> # rxfreq or txfreq to 0.0 if that tone is not desired.
> However, in dahdi_cfg.c, no such configuration option is tested for, so it is not possible to configure the card to use single frequency signaling.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list