Bugzilla – Bug 153702
Zaptel sysconfig file unusable in YAST
Last modified: 2006-03-09 10:41:27 UTC
The sysconfig file containing ZAPTEL_MODULES has it as type "sting" instead of "string", so YAST won't let you enter a value. In addition the default is blank. Really the default should be "ztdummy". This is because Asterisk always requires some Zaptel (etc.) hardware to give it a source of timing. If you have no specific hardware then you have to use ztdummy.ko to provide this - most people don't know that - so that IAX and music-on-hold work. Note that ztdummy isn't even in the list of possibles and it should be right at the front.
Which file is that?
Ladislav: I suppose this has to be corrected in the YaST module rather than in sysconfig? If not, assign it back to us.
No. It's the file "zaptel" in /etc/sysconfig. Just the text in that file needs changing, not Yast itself.
## Directory: Hardware/Telephony ## Description: Zaptel Modules ## Type: string ## Default: "ztdummy" ## Config "" ## ServiceRestart: zaptel # # This is a space saparated list of zaptel modules to be # loaded. Valid module names are: # # ztdummy, qozap, tor2, torisa, wcfxo, wcfxs, wct1xxp, # wct4xxp, wcusb, zaphfc, ztd-eth. # ZAPTEL_MODULES="ztdummy"
Michael, no the bug is in zaptel itself. See comment #4, there is corrected sysconfig file. (Nigel, thank you!)
OK, I'll fix the typo in the type field, but making ztdummy the default is useless, as it requires the kernel's HZ value to be 1000, and our kernels have 250. AFAIK the zaptel timing is only needed for conferencing (meetme), but not for MoH and IAX.
Nigel: Please don't assign bugs (back) to me but to the screening-team to avoid unwanted stalls. Reassigning to Reinhard.
Fixed for BETA8.