| Summary: | ASTERISK-12365: Setting toneduration in zapata.conf causes chan_zap not load any more | ||
| Reporter: | Marcin Kowalczyk (kowalma) | Labels: | |
| Date Opened: | 2008-07-13 14:08:29 | Date Closed: | 2011-06-07 14:02:54 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_zap |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| 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. | ||
| Comments: | By: Mark Michelson (mmichelson) 2008-07-14 17:10:27 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? By: Marcin Kowalczyk (kowalma) 2008-07-18 09:29:55 Zaptel 1.4.10, I'll try to upgrade to 1.4.11 but I can do upgrade durring the night only. By: Marcin Kowalczyk (kowalma) 2008-07-20 03:14:59 I've upgraded to 1.4.11 and problem was solved. I'm prety sure, that I've recompiled zaptel durring * upgrade 1.4 -> 1.6. I think isse can be put into status solved. By: Mark Michelson (mmichelson) 2008-07-21 08:38:58 Closing at the request of the reporter. | ||