Franklin wrote: > ztdummy can give you issues as a timing device. Yes and no. See below
> Any way you could try using a Digium card just > as a timing device to see if this helps? Tomasz wrote: >> I am using Debian OS kernel 2.6.22-3-amd64 >> and zaptel driver 1.4 with ztdummy module for meetme >> application. I use meetme with SIP channels. Your kernel is new enough that you should be able to leverage hi-res timers (you might need to patch ztdummy), or at least a RTC set to 8192 ticks/sec. What does dmesg show after ztdummy is loaded? >> I have such problem that when one connects to the >> conference voice is "cut". Each voice sequence is >> disturbed. Do you have internal_timing=yes in asterisk.conf? This option allows Asterisk to time the RTP stream based on zaptel/ztdummy clock and not on the received RTP stream. In a MeetMe, where callers might mute themselves, the received RTP stream is all but useless for timing. Dan _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
