Re: [asterisk-users] Playback / Background / Read choppy, but musiconhold fine, even with ztdummy
http://www.openvox.com.cn/products_detail.php?genre_id=9id=28 If you can get the bare card, you can use it for timing with a little magic that can be found via google. If not, get one with an FXO or FXS and you will add a little flexibility and have real hardware timing. If you continue to have issues, then you can eliminate timing and focus on processes I would think. I had a client running spamassassin on their Asterisk box which doubled as their corporate email server, geewhiz, I wonder why they were having issues. Another odd thing Tzafrir helped me to notice was (I don't remember what version of CentOS) that the time was jumping ahead a couple of minutes and then back. Running top, you could tell something was up because it was refreshing way too fast. Then typing date on the command line repeatedly showed the time jumping all over the place. Might want to check that out too. Thanks, Steve Totaro Thanks again guys. the 'watch -d -n 1 cat /proc/interrupts' showed things to be ok.. the rtc cycles increasing by 1024+ per second. In the process of cleaning up unnecesary processes, I came across this line : /usr/sbin/vmware-guestd --background /var/run/vmware-guestd.pid GASP so does this mean this is a virtual machine?? I have got no idea about virtualization yet. So how do I confirm if this is a virtual machine or not?? And is it advised to run asterisk on a virtual machine? - Ben. Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ ___ -- 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
Re: [asterisk-users] Playback / Background / Read choppy, but musiconhold fine, even with ztdummy
On Mon, Apr 28, 2008 at 3:18 AM, Benjamin Jacob [EMAIL PROTECTED] wrote: http://www.openvox.com.cn/products_detail.php?genre_id=9id=28 If you can get the bare card, you can use it for timing with a little magic that can be found via google. If not, get one with an FXO or FXS and you will add a little flexibility and have real hardware timing. If you continue to have issues, then you can eliminate timing and focus on processes I would think. I had a client running spamassassin on their Asterisk box which doubled as their corporate email server, geewhiz, I wonder why they were having issues. Another odd thing Tzafrir helped me to notice was (I don't remember what version of CentOS) that the time was jumping ahead a couple of minutes and then back. Running top, you could tell something was up because it was refreshing way too fast. Then typing date on the command line repeatedly showed the time jumping all over the place. Might want to check that out too. Thanks, Steve Totaro Thanks again guys. the 'watch -d -n 1 cat /proc/interrupts' showed things to be ok.. the rtc cycles increasing by 1024+ per second. In the process of cleaning up unnecesary processes, I came across this line : /usr/sbin/vmware-guestd --background /var/run/vmware-guestd.pid GASP so does this mean this is a virtual machine?? I have got no idea about virtualization yet. So how do I confirm if this is a virtual machine or not?? And is it advised to run asterisk on a virtual machine? - Ben. Ben, Who is providing your server? I assume it is in a colo. Ask them or see if they mention it in their agreement or sales material. Finally, you can just ask them. If they claimed a dedicated server, complain. It seems you are running on a virtual machine and no, that is not advisable. Thanks, Steve Totaro ___ -- 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
Re: [asterisk-users] Playback / Background / Read choppy, but musiconhold fine, even with ztdummy
- In the process of cleaning up unnecesary processes, I came across this line : /usr/sbin/vmware-guestd --background /var/run/vmware-guestd.pid GASP so does this mean this is a virtual machine?? I have got no idea about virtualization yet. So how do I confirm if this is a virtual machine or not?? And is it advised to run asterisk on a virtual machine? - Ben. Ben, Who is providing your server? I assume it is in a colo. Ask them or see if they mention it in their agreement or sales material. Finally, you can just ask them. If they claimed a dedicated server, complain. It seems you are running on a virtual machine and no, that is not advisable. Thanks, Steve Totaro Steve, Naa.. it's not co-lo. It's a dedicated server for sure, but my client wants to make the most out of one box, it seems. Talked to the client today and confirmed that it is indeed a virtual machine. They said they had previously installed asterisk around a year back on a virtual machine with no issues. I did not have any solid convincing response to that. I do understand about virtualization not being a recommended thing to do. Now to convince the client. Also, if I put in a fxo/fxs card, i've read somewhere that virtual machines won't be able to access the card n hence the timing provided by it. Is it true? thanks again Steve and the rest of you. - Ben. Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ ___ -- 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
Re: [asterisk-users] Playback / Background / Read choppy, but musiconhold fine, even with ztdummy
OK, I think you need to home in on the differences between the server(s) that work fine and the one that doesn't. As I said in my other mail, the faulty one is a .. mono processor machine, with SMP turned on .. running CentOS 5 .. with kernel : 2.6.18-53.1.13.el5 There are other kernels too(2.6.18-8, etc.), will be trying those kernels too. The local working machine is : .. dual processor, with SMP ofcourse .. running Fedora Core 7, if I remember it correctly. .. kernel definitely 2.6.13 Have looked at all parameters, be it the kernel timer frequency(1000 HZ), enhanced timer support, etc. Everything seems to be set right. (Then again, I hope I am looking at the correct places, i.e. .config files and using make menuconfig). Try watch -dn 1 cat /proc/interrupts and check that the RTC interrupts are going up by 1024 per second. This is with ztdummy running. This I gotta try. What if it isn't? And worse, what if it is and I am still getting the choppy playbacks!! What else is going on on this server? Does it have any virtual machines on it? Does it have X Windows running? What does top show? Unfortunately a lot of other processes are running too on the server, one of them being httpd and other sundry needed by the client (this inspite of suggesting him to otherwise). This is an Asterisk install not done by me, I just added the zaptel installation and ztdummy module. Was brazenly confident of things working in a jiffy(does this count as a pun?), when I stepped in. cheerz :-( - Ben. Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ ___ -- 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
Re: [asterisk-users] Playback / Background / Read choppy, but musiconhold fine, even with ztdummy
On Sat, Apr 26, 2008 at 9:14 AM, Benjamin Jacob [EMAIL PROTECTED] wrote: OK, I think you need to home in on the differences between the server(s) that work fine and the one that doesn't. As I said in my other mail, the faulty one is a .. mono processor machine, with SMP turned on .. running CentOS 5 .. with kernel : 2.6.18-53.1.13.el5 There are other kernels too(2.6.18-8, etc.), will be trying those kernels too. The local working machine is : .. dual processor, with SMP ofcourse .. running Fedora Core 7, if I remember it correctly. .. kernel definitely 2.6.13 Have looked at all parameters, be it the kernel timer frequency(1000 HZ), enhanced timer support, etc. Everything seems to be set right. (Then again, I hope I am looking at the correct places, i.e. .config files and using make menuconfig). Try watch -dn 1 cat /proc/interrupts and check that the RTC interrupts are going up by 1024 per second. This is with ztdummy running. This I gotta try. What if it isn't? And worse, what if it is and I am still getting the choppy playbacks!! What else is going on on this server? Does it have any virtual machines on it? Does it have X Windows running? What does top show? Unfortunately a lot of other processes are running too on the server, one of them being httpd and other sundry needed by the client (this inspite of suggesting him to otherwise). This is an Asterisk install not done by me, I just added the zaptel installation and ztdummy module. Was brazenly confident of things working in a jiffy(does this count as a pun?), when I stepped in. cheerz :-( - Ben. http://www.openvox.com.cn/products_detail.php?genre_id=9id=28 If you can get the bare card, you can use it for timing with a little magic that can be found via google. If not, get one with an FXO or FXS and you will add a little flexibility and have real hardware timing. If you continue to have issues, then you can eliminate timing and focus on processes I would think. I had a client running spamassassin on their Asterisk box which doubled as their corporate email server, geewhiz, I wonder why they were having issues. Another odd thing Tzafrir helped me to notice was (I don't remember what version of CentOS) that the time was jumping ahead a couple of minutes and then back. Running top, you could tell something was up because it was refreshing way too fast. Then typing date on the command line repeatedly showed the time jumping all over the place. Might want to check that out too. Thanks, Steve Totaro ___ -- 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
[asterisk-users] Playback / Background / Read choppy, but musiconhold fine, even with ztdummy
Hello ppl, One on my clients' machine had Asterisk 1.4.4. installed. The complained of choppy Playback of gsm files. So scouring the internet gave me the solution of installing ztdummy and loading it as a module. Did it (using zaptel-1.4.1) , but to no effect. Re-compiled asterisk and re-installed. Sill no effect. Do I have to specify any parameter in the Asterisk compilation to look at ztdummy/rtc? As far as I remember (am coming back to Asterisk after quite some time now), you don't really need to set anything over there for any zaptel specific compilation? And yes, all the files are gsm files and the codec used for the calls is ulaw. I even tried converting those gsm files to wav using sox and then playing them, but the behaviour is the same. Any ideas anyone.. something I am missing ?? TiA, - Ben. - Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.___ -- 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
[asterisk-users] Playback / Background / Read choppy, but musiconhold fine, even with ztdummy
Are my messages getting through? This is urgent!! Any pointers? Benjamin Jacob [EMAIL PROTECTED] wrote: Date: Thu, 24 Apr 2008 23:23:08 -0700 (PDT) From: Benjamin Jacob [EMAIL PROTECTED] Subject: Playback / Background / Read choppy, but musiconhold fine, even with ztdummy To: asterisk-users@lists.digium.com Hello ppl, One on my clients' machine had Asterisk 1.4.4. installed. The complained of choppy Playback of gsm files. So scouring the internet gave me the solution of installing ztdummy and loading it as a module. Did it (using zaptel-1.4.1) , but to no effect. Re-compiled asterisk and re-installed. Sill no effect. Do I have to specify any parameter in the Asterisk compilation to look at ztdummy/rtc? As far as I remember (am coming back to Asterisk after quite some time now), you don't really need to set anything over there for any zaptel specific compilation? And yes, all the files are gsm files and the codec used for the calls is ulaw. I even tried converting those gsm files to wav using sox and then playing them, but the behaviour is the same. Any ideas anyone.. something I am missing ?? TiA, - Ben. - Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. - Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.___ -- 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
Re: [asterisk-users] Playback / Background / Read choppy, but musiconhold fine, even with ztdummy
In article [EMAIL PROTECTED], Benjamin Jacob [EMAIL PROTECTED] wrote: One on my clients' machine had Asterisk 1.4.4. installed. The complained of choppy Playback of gsm files. So scouring the internet gave me the solution of installing ztdummy and loading it as a module. Did it (using zaptel-1.4.1) , but to no effect. Re-compiled asterisk and re-installed. Sill no effect. Do I have to specify any parameter in the Asterisk compilation to look at ztdummy/rtc? As far as I remember (am coming back to Asterisk after quite some time now), you don't really need to set anything over there for any zaptel specific compilation? And yes, all the files are gsm files and the codec used for the calls is ulaw. I even tried converting those gsm files to wav using sox and then playing them, but the behaviour is the same. Any ideas anyone.. something I am missing ?? Firstly, check whether Asterisk has chan_zap loaded and access to zaptel: *CLI zap show channels Chan Extension Context Language MusicOnHold pseudodefault *CLI If you don't get pseudo shown, then you are not getting the benefit of ztdummy. However, the probably main cause of choppy sound is poor timing from the SIP client (I'm assuming SIP), because Asterisk by default uses the incoming stream to generate timing for the outbound stream. There are two main things to try: 1. Make sure that the SIP clients are NOT using silence suppression (may be referred to as VAD, bandwidth saving, or something similar). 2. If ztdummy is running ok, edit /etc/asterisk/asterisk.conf and enable the line internal_timing=yes. That should make it play out based on internal zaptel timing instead of timing off the incoming stream, I think. Cheers Tony -- Tony Mountifield Work: [EMAIL PROTECTED] - http://www.softins.co.uk Play: [EMAIL PROTECTED] - http://tony.mountifield.org ___ -- 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
Re: [asterisk-users] Playback / Background / Read choppy, but musiconhold fine, even with ztdummy
Tony Mountifield wrote: 2. If ztdummy is running ok, edit /etc/asterisk/asterisk.conf and enable the line internal_timing=yes. That should make it play out based on One other thing comes to mind, make sure you compile with 'Don't optimize' if you're using gcc 4.2.2 Doug -- Ben Franklin quote: Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety. ___ -- 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
Re: [asterisk-users] Playback / Background / Read choppy, but musiconhold fine, even with ztdummy
Tony Mountifield [EMAIL PROTECTED] wrote: In article [EMAIL PROTECTED], Benjamin Jacob wrote: One on my clients' machine had Asterisk 1.4.4. installed. The complained of choppy Playback of gsm files. So scouring the internet gave me the solution of installing ztdummy and loading it as a module. Did it (using zaptel-1.4.1) , but to no effect. Re-compiled asterisk and re-installed. Sill no effect. Do I have to specify any parameter in the Asterisk compilation to look at ztdummy/rtc? As far as I remember (am coming back to Asterisk after quite some time now), you don't really need to set anything over there for any zaptel specific compilation? And yes, all the files are gsm files and the codec used for the calls is ulaw. I even tried converting those gsm files to wav using sox and then playing them, but the behaviour is the same. Any ideas anyone.. something I am missing ?? Firstly, check whether Asterisk has chan_zap loaded and access to zaptel: *CLI zap show channels Chan Extension Context Language MusicOnHold pseudodefault *CLI If you don't get pseudo shown, then you are not getting the benefit of ztdummy. However, the probably main cause of choppy sound is poor timing from the SIP client (I'm assuming SIP), because Asterisk by default uses the incoming stream to generate timing for the outbound stream. There are two main things to try: 1. Make sure that the SIP clients are NOT using silence suppression (may be referred to as VAD, bandwidth saving, or something similar). 2. If ztdummy is running ok, edit /etc/asterisk/asterisk.conf and enable the line internal_timing=yes. That should make it play out based on internal zaptel timing instead of timing off the incoming stream, I think. Cheers Tony -- Tony Mountifield Work: [EMAIL PROTECTED] - http://www.softins.co.uk Play: [EMAIL PROTECTED] - http://tony.mountifield.org Thanks Tony for the response. zap show channels shows that things are fine, as you said : *CLI zap show channels Chan Extension Context Language MOH Interpret pseudodefaultdefault Tried setting internal_timing to yes as well. Still no difference. Also, I don't think my SIP gateway uses Silence suppression, because the same SIP gateway connections work fine with another Asterisk server. This is getting seriously irritating now!!! Have tried all the tricks and tips I've been finding on the net. Yeah, btw, even Meetme playback is choppy. So, I think its somehow related to timing. But I am not the expert. - Ben. - Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.___ -- 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
Re: [asterisk-users] Playback / Background / Read choppy, but musiconhold fine, even with ztdummy
In article [EMAIL PROTECTED], Benjamin Jacob [EMAIL PROTECTED] wrote: Also, I don't think my SIP gateway uses Silence suppression, because the same SIP gateway connections work fine with another Asterisk server. OK, I think you need to home in on the differences between the server(s) that work fine and the one that doesn't. What version of kernel is it running? If it less than 2.6.13, make sure you change #if 0 to #if 1 in ztdummy.c so that USE_RTC still gets enabled. Try watch -dn 1 cat /proc/interrupts and check that the RTC interrupts are going up by 1024 per second. This is with ztdummy running. What else is going on on this server? Does it have any virtual machines on it? Does it have X Windows running? What does top show? Cheers Tony -- Tony Mountifield Work: [EMAIL PROTECTED] - http://www.softins.co.uk Play: [EMAIL PROTECTED] - http://tony.mountifield.org ___ -- 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
Re: [asterisk-users] Playback / Background / Read choppy, but musiconhold fine, even with ztdummy
On Fri, Apr 25, 2008 at 03:02:14PM +, Tony Mountifield wrote: In article [EMAIL PROTECTED], Benjamin Jacob [EMAIL PROTECTED] wrote: Also, I don't think my SIP gateway uses Silence suppression, because the same SIP gateway connections work fine with another Asterisk server. OK, I think you need to home in on the differences between the server(s) that work fine and the one that doesn't. What version of kernel is it running? If it less than 2.6.13, make sure you change #if 0 to #if 1 in ztdummy.c so that USE_RTC still gets enabled. RTC is available (and used) as of kernel 2.6.15 . The thing that has changed in 2.6.13 is that the default of HZ became 250 (but still tunable). So unless you build your own kernel, without using RTC you would not really get a steady rate of 1000 interrupts per second. And then again, on kernels = 2.6.22 you have hi-resolution timers which generally work better. Try watch -dn 1 cat /proc/interrupts and check that the RTC interrupts are going up by 1024 per second. This is with ztdummy running. And if using something other than RTC: 1000 interrupts per second. Anyway, close to 1000 is easy to spot there. -- Tzafrir Cohen icq#16849755 jabber:[EMAIL PROTECTED] +972-50-7952406 mailto:[EMAIL PROTECTED] http://www.xorcom.com iax:[EMAIL PROTECTED]/tzafrir ___ -- 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
Re: [asterisk-users] Playback / Background / Read choppy, but musiconhold fine, even with ztdummy
Benjamin Jacob [EMAIL PROTECTED] wrote: Tony Mountifield [EMAIL PROTECTED] wrote: In article [EMAIL PROTECTED], Benjamin Jacob wrote: One on my clients' machine had Asterisk 1.4.4. installed. The complained of choppy Playback of gsm files. So scouring the internet gave me the solution of installing ztdummy and loading it as a module. Did it (using zaptel-1.4.1) , but to no effect. Re-compiled asterisk and re-installed. Sill no effect. Do I have to specify any parameter in the Asterisk compilation to look at ztdummy/rtc? As far as I remember (am coming back to Asterisk after quite some time now), you don't really need to set anything over there for any zaptel specific compilation? And yes, all the files are gsm files and the codec used for the calls is ulaw. I even tried converting those gsm files to wav using sox and then playing them, but the behaviour is the same. Any ideas anyone.. something I am missing ?? Firstly, check whether Asterisk has chan_zap loaded and access to zaptel: *CLI zap show channels Chan Extension Context Language MusicOnHold pseudodefault *CLI If you don't get pseudo shown, then you are not getting the benefit of ztdummy. However, the probably main cause of choppy sound is poor timing from the SIP client (I'm assuming SIP), because Asterisk by default uses the incoming stream to generate timing for the outbound stream. There are two main things to try: 1. Make sure that the SIP clients are NOT using silence suppression (may be referred to as VAD, bandwidth saving, or something similar). 2. If ztdummy is running ok, edit /etc/asterisk/asterisk.conf and enable the line internal_timing=yes. That should make it play out based on internal zaptel timing instead of timing off the incoming stream, I think. Cheers Tony -- Tony Mountifield Work: [EMAIL PROTECTED] - http://www.softins.co.uk Play: [EMAIL PROTECTED] - http://tony.mountifield.org Thanks Tony for the response. zap show channels shows that things are fine, as you said : *CLI zap show channels Chan Extension Context Language MOH Interpret pseudodefaultdefault Tried setting internal_timing to yes as well. Still no difference. Also, I don't think my SIP gateway uses Silence suppression, because the same SIP gateway connections work fine with another Asterisk server. This is getting seriously irritating now!!! Have tried all the tricks and tips I've been finding on the net. Yeah, btw, even Meetme playback is choppy. So, I think its somehow related to timing. But I am not the expert. - Ben. - Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.___ -- 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-usersBtw, I am on CentOS 5, with uname showing as: Linux mserver.org 2.6.18-53.1.13.el5 #1 SMP Tue Feb 12 13:01:45 EST 2008 i686 i686 i386 GNU/Linux And it is not a multiprocessor machine. Will the SMP option affect the working in any way? - Ben. - Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.___ -- 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
Re: [asterisk-users] Playback / Background / Read choppy, but musiconhold fine, even with ztdummy
In article [EMAIL PROTECTED], Tzafrir Cohen [EMAIL PROTECTED] wrote: RTC is available (and used) as of kernel 2.6.15 . The thing that has changed in 2.6.13 is that the default of HZ became 250 (but still tunable). So unless you build your own kernel, without using RTC you would not really get a steady rate of 1000 interrupts per second. Well, I'm not familiar with the later 2.6 kernels (most of my systems are at 2.6.12 (FC3) or 2.6.9 (RHEL4 clones)). However, the USE_RTC code was my creation, so I'm very familiar with the issues as they were at the time. See http://bugs.digium.com/view.php?id=4301 The issue was that the original 2.6 version of ztdummy ran off the 1000Hz kernel jiffy counter. This had a tendency to miss ticks. Having successfully used the zaprtc module in 2.4, I re-implemented it for 2.6 using the rtc hooks that the 2.6 kernel provided. It sets the 146818 RTC chip to generate 1024Hz interrupts (it can't do 1000Hz), and then skips 3 every 128, evenly spaced. This was a huge improvement over the jiffy counter. Unfortunately, when the patch was applied to CVS, someone screwed up and missed out ztdummy.h, only doing ztdummy.c. This broke compilation and caused BKW to throw a fit. The knee-jerk reaction was to slap an #if 0 around the #define USE_RTC, rather than understand the cause of the problem. Once ztdummy.h was patched correctly, the #if 0 should have been removed, but it never was, so most people continued to build it with the inferior jiffy clock. When kernel 2.6.13 came along, the jiffy clock no longer defaulted to 1000Hz, so USE_RTC was made the default for those versions. I will never understand why it was never just enabled for *all* 2.6 kernels at that time, like it should have been in the first place. The only dependency it has is that the kernel must have been built with CONFIG_RTC and not CONFIG_GENRTC. And then again, on kernels = 2.6.22 you have hi-resolution timers which generally work better. I have yet to experience these, but it sounds promising. Cheers Tony -- Tony Mountifield Work: [EMAIL PROTECTED] - http://www.softins.co.uk Play: [EMAIL PROTECTED] - http://tony.mountifield.org ___ -- 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
