[asterisk-bugs] [Asterisk 0013067]: Setting toneduration in zapata.conf causes chan_zap not load any more

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13067 
====================================================================== 
Reported By:                kowalma
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13067
Category:                   Channels/chan_zap
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.0-beta9 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             07-13-2008 14:08 CDT
Last Modified:              07-14-2008 17:10 CDT
====================================================================== 
Summary:                    Setting toneduration in zapata.conf causes chan_zap
not load any more
Description: 
I've found bug in chan_zap. I've added toneduration=300 to zapata.conf and
my zap stop working:

[Jul 13 21:06:10] ERROR[25495]: chan_zap.c:14024 process_zap: Invalid tone
duration: 300 ms at line 28.
[Jul 13 21:06:10] ERROR[25495]: chan_zap.c:14024 process_zap: Invalid tone
duration: 300 ms at line 28.

I've tried with several values and it didn't solve problem. Adding same
line to asterisk 1.4.19 does not have affect on chan_zap loading.
====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 07-14-08 17:10  
---------------------------------------------------------------------- 
Interesting. That's the only option when loading chan_zap that uses an
ioctl to set a parameter in Zaptel.

This makes me suspect that there's some incompatibility between your
Asterisk and Zaptel versions. Did you update to the latest 1.4 release of
Zaptel and recompile both Zaptel and Asterisk when you switched to
1.6.0-beta9? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-14-08 17:10  putnopvut      Note Added: 0090255                          
======================================================================