Not Logged in - No Account?

Don't have an account? Registering an account with us allows you to post to the forums, easily track new posts, subscribe to threads, pm (private message) other forum members, and receive periodic news letters (you can opt out if you desire). Once you are logged in this message will no longer appear. If you don't have an account, you can create one by registering here. Lost your password, request a new password. We respect your privacy which means we collect minimal information when you register and we do not resell that information or use it in any objectionable way. You can review our privacy policy for full details.


Invalid Conference

Invalid Conference Number

This is caused by not having a zaptel timing source. Often, this
will happen when you've upgraded your kernel, but haven't recompiled
your zaptel to suit

.

Quick Fix

cd /usr/src/zaptel

make install

/etc/init.d/zaptel stop

/etc/init.d/zaptel start

Or modprobe ztdummy, which provides the timing souce if you don't have any hardware installed.

http://www.voip-info.org/wiki-Asterisk+timer+ztdummy

Important Note for RedHat? Enterprise Linux, CentOS 4.2 or similar.

There is a BUG in the latest kernel from RedHat?, that causes
zaptel to fail to compile. The way to fix this is to edit the file
/usr/src/kernels/2.6.9-3

4.EL-i686/include/linux/spinlock.h and change 'rw_lock_t' on line 407 to 'rwlock_t'.


‹ Common ProblemsupEcho Info ›