Summary: | DAHLIN-00166: Support for single freq signaling does not appear to exist | ||||||
Reporter: | Arlen Raasch (araasch) | Labels: | |||||
Date Opened: | 2009-12-09 08:48:46.000-0600 | Date Closed: | 2012-09-10 08:46:03 | ||||
Priority: | Minor | Regression? | No | ||||
Status: | Closed/Complete | Components: | Utilities | ||||
Versions: | 2.2.0.2 | Frequency of Occurrence | |||||
Related Issues: |
| ||||||
Environment: | Attachments: | ||||||
Description: | 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. | ||||||
Comments: | By: Leif Madsen (lmadsen) 2009-12-09 09:58:20.000-0600 After talking to Russell, we feel either there is a bug here, or there needs to be some sort of sample file update to indicate that single freq support is not available. Sending this over to the DAHDI people to further prioritize! By: Tzafrir Cohen (tzafrir) 2009-12-09 09:58:33.000-0600 dahdi_cfg.c does not have handling of "sf". ztcfg-dude.c in zaptel does have it (but not the standard ztcfg.c). By: Shaun Ruffell (sruffell) 2012-09-10 08:46:03.135-0500 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. |