[Asterisk-Users] RE: ztdummy/rtc
make -C /lib/modules/2.6.11.11/build SUBDIRS=/usr/src/zaptel modules make[1]: Entering directory `/usr/src/linux-2.6.11.11' Building modules, stage 2. MODPOST *** Warning: rtc_unregister [/usr/src/zaptel/ztdummy.ko] undefined! *** Warning: rtc_control [/usr/src/zaptel/ztdummy.ko] undefined! *** Warning: rtc_register [/usr/src/zaptel/ztdummy.ko] undefined! make[1]: Leaving directory `/usr/src/linux-2.6.11.11' when I run make linux26 Also, I do not have RTC support in the kernel since the headers are included from ztdummy, I thought that Tony said that it is not required. Do I need RTC support compiled into the kernel? Kevin ___ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[Asterisk-Users] Re: ztdummy/rtc
In article [EMAIL PROTECTED], Kevin Bockman [EMAIL PROTECTED] wrote: make -C /lib/modules/2.6.11.11/build SUBDIRS=/usr/src/zaptel modules make[1]: Entering directory `/usr/src/linux-2.6.11.11' Building modules, stage 2. MODPOST *** Warning: rtc_unregister [/usr/src/zaptel/ztdummy.ko] undefined! *** Warning: rtc_control [/usr/src/zaptel/ztdummy.ko] undefined! *** Warning: rtc_register [/usr/src/zaptel/ztdummy.ko] undefined! make[1]: Leaving directory `/usr/src/linux-2.6.11.11' when I run make linux26 Also, I do not have RTC support in the kernel since the headers are included from ztdummy, I thought that Tony said that it is not required. Do I need RTC support compiled into the kernel? You do need RTC support in the Kernel, because it is the hooks in the rtc.c driver that the new ztdummy requires. So firstly, you need to compile your kernel with either CONFIG_RTC=m or CONFIG_RTC=y (I only tried ztdummy on a kernel compiled with CONFIG_RTC=m, which is the default on Fedora). Then after that, you don't need to put -DUSE_RTC in the Makefile, all you need to do is remove the #if 0 from around the #define of USE_RTC in ztdummy.c. (The #if 0 was added in a hurry because someone forgot to include the ztdummy.h update in CVS, which made the compilation of ztdummy.c fail - the correct fix was not to put in #if 0, but to add the ztdummy.h update instead, and allow just the small minority of people without RTC support in the kernel to comment out the #define USE_RTC). Cheers Tony -- Tony Mountifield Work: [EMAIL PROTECTED] - http://www.softins.co.uk Play: [EMAIL PROTECTED] - http://tony.mountifield.org ___ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] RE: ztdummy/rtc
Also, I do not have RTC support in the kernel since the headers are included from ztdummy, I thought that Tony said that it is not required. Do I need RTC support compiled into the kernel? I was going to reply to your first message, but then I thought I'd see if you'd figured it out yourself. Yes. You need RTC support in the kernel if you want to use RTC, the same way you need SCSI support in the kernel if you want to use SCSI. --Rob ___ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Re: ztdummy/rtc
Hi Tony, You do need RTC support in the Kernel, because it is the hooks in the rtc.c driver that the new ztdummy requires. That's what I thought. That was going to be my next step but I hate messing with the kernel remotely. I just made it as a module like you did and it worked. Thanks. I'm still having my (apparantly) timing problem, but I'll do some more testing and make a separate thread for that. I'm generating an outbound call through Asterisk. The inbound audio is good, but the outbound audio is sometimes staticy. This seems to happen only at the start of the call. These are short test calls, just playing a weasels ate our phone system catted together 4 times. The call is ulaw and so are the audio files. I don't think I have this problem if I have it call my SIP phone and play MOH. Cheers Tony Thanks, Kevin ___ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Re: ztdummy/rtc - staticy audio
I'm still having my (apparantly) timing problem, but I'll do some more testing and make a separate thread for that. I'm generating an outbound call through Asterisk. The inbound audio is good, but the outbound audio is sometimes staticy. This seems to happen only at the start of the call. These are short test calls, just playing a weasels ate our phone system catted together 4 times. The call is ulaw and so are the audio files. I don't think I have this problem if I have it call my SIP phone and play MOH. I would also like to make a quick note: output of zttest: Opened pseudo zap interface, measuring accuracy... 99.938965% 99.951172% 99.938965% 99.963379% 99.963379% 99.951172% 99.951172% 99.938965% 99.963379% 99.951172% 99.963379% 99.951172% 99.938965% 99.951172% 99.951172% 99.963379% 99.951172% 99.963379% 99.963379% 99.951172% 99.963379% 99.951172% 99.951172% 99.963379% 99.951172% 99.963379% 99.951172% 99.963379% 99.951172% 99.963379% 99.963379% 99.951172% 99.963379% 99.951172% 99.963379% 99.951172% 99.951172% 99.963379% 99.951172% --- Results after 39 passes --- Best: 99.963379 -- Worst: 99.938965 -- Average: 99.954928 /proc/interrupts CPU0 0:6042207 XT-PIC timer 1: 8 XT-PIC i8042 2: 0 XT-PIC cascade 4:899 XT-PIC serial 8:1733413 XT-PIC rtc 11:1227054 XT-PIC eth0 15: 44568 XT-PIC qla1280 NMI: 0 LOC:6042233 ERR: 7578 MIS: 0 This is a AMD Sempron 3000+ on Linux 2.6.11.11. Thanks, Kevin ___ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Re: ztdummy/rtc - staticy audio
output of zttest: Opened pseudo zap interface, measuring accuracy... 99.938965% 99.951172% 99.938965% 99.963379% 99.963379% 99.951172% 99.951172% Ah. Don't be scared. This is actually -correct- when using RTC. Let me demonstrate: [EMAIL PROTECTED] zaptel]# ./zttest -v Opened pseudo zap interface, measuring accuracy... 8192 samples in 8195 sample intervals 99.963379% 8192 samples in 8195 sample intervals 99.963379% 8192 samples in 8187 sample intervals 99.938965% 8192 samples in 8195 sample intervals 99.963379% 8192 samples in 8187 sample intervals 99.938965% 8192 samples in 8195 sample intervals 99.963379% 8192 samples in 8187 sample intervals 99.938965% 8192 samples in 8195 sample intervals 99.963379% --- Results after 8 passes --- Best: 99.963379 -- Worst: 99.938965 -- Average: 99.952916 Note how it's bouncing below _and_ above 8192? That's the important bit. With RTC it can do the equivalent of 'catching up'. (Not really, I know, but lets pretend it works that way) Now lets see what happens when we average it out: [EMAIL PROTECTED] zaptel]# bc bc 1.06 Copyright 1991-1994, 1997, 1998, 2000 Free Software Foundation, Inc. This is free software with ABSOLUTELY NO WARRANTY. For details type `warranty'. (8195+8195+8187+8195+8187+8195+8187+8195)/8 8192 Exactly 100% spot on, and it should stay that way indefinitely. Note, of course, that timing is only used for Meetme, MOH and IAX Trunking. So this isn't your problem - although you did say that MOH was working perfectly, so you can at least take comfort in that! --Rob ___ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
