Re: [Asterisk-Dev] Bug 4301 - ztdummy accuracy problem
BJ Weschke wrote:
Are you using the name/record playback option?
Sorry... I don't understand...
Do you mean the meetme options?
I only use p option.
Here is my dialplan:
[macro-conf]
exten = s,1,Set(LANGUAGE()=${LOCAL_LANGUAGE})
exten = s,2,MeetMe(${MACRO_EXTEN}|p)
and I call the macro by
exten = 111,1,Macro(conf)
Do you mean the options will affect the delay problem?
I'll try other options later...
On 10/18/05, Chih-Wei Huang [EMAIL PROTECTED] wrote:
BJ Weschke wrote:
The bug was closed because the ztdummy behavior is not the specific
cause
for the delay problem. That patch with USE_RTC was intended to make use
of
the real time resource available within the kernel = 2.6.13 instead of
relying on a OHCI USB resource which was the case previously.
But USE_RTC also compile for kernel 2.6.13..
(at least, 2.6.9 in my system)
Is kernel = 2.6.13 necessary?
If you're looking for a fix in MeetMe, some have reported success with
applying the patches available in bug 5374.
Thank you for the info.
I tried that patch.
Unfortunately, it seems not improve the increasing delay problem
of meetme.
Any suggestion or experience for the delay problem?
especially using with OH323 channel driver.
___
Asterisk-Dev mailing list
Asterisk-Dev@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] Bug 4301 - ztdummy accuracy problem
On Mon, Oct 17, 2005 at 07:53:55AM -0400, BJ Weschke wrote: Chih, The bug was closed because the ztdummy behavior is not the specific cause for the delay problem. That patch with USE_RTC was intended to make use of the real time resource available within the kernel = 2.6.13 instead of relying on a OHCI USB resource which was the case previously. ztdummy uses the kernel's internal clock for kernel 2.6 even without USE_RTC . with USE_RTC you should expect to get better accuracy, though. -- Tzafrir Cohen icq#16849755 +972-50-7952406 [EMAIL PROTECTED] http://www.xorcom.com ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] Bug 4301 - ztdummy accuracy problem
Tzafrir Cohen wrote: On Mon, Oct 17, 2005 at 07:53:55AM -0400, BJ Weschke wrote: Chih, The bug was closed because the ztdummy behavior is not the specific cause for the delay problem. That patch with USE_RTC was intended to make use of the real time resource available within the kernel = 2.6.13 instead of relying on a OHCI USB resource which was the case previously. ztdummy uses the kernel's internal clock for kernel 2.6 even without USE_RTC . with USE_RTC you should expect to get better accuracy, though. I see. Thank you! But I have further questions: * Do I need USE_RTC for better accuracy to eliminate the delay problem? * Do I need kernel = 2.6.13 to enable USE_RTC ? I have also tried patch from bug 4252 (app_meetme-HEAD.diff). But the audio quality degraded evidently, while the delay problem still existed... Sigh... ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] Bug 4301 - ztdummy accuracy problem
On Tue, 2005-10-18 at 17:07 +0800, Chih-Wei Huang wrote: Tzafrir Cohen wrote: On Mon, Oct 17, 2005 at 07:53:55AM -0400, BJ Weschke wrote: Chih, The bug was closed because the ztdummy behavior is not the specific cause for the delay problem. That patch with USE_RTC was intended to make use of the real time resource available within the kernel = 2.6.13 instead of relying on a OHCI USB resource which was the case previously. ztdummy uses the kernel's internal clock for kernel 2.6 even without USE_RTC . with USE_RTC you should expect to get better accuracy, though. I see. Thank you! But I have further questions: * Do I need USE_RTC for better accuracy to eliminate the delay problem? * Do I need kernel = 2.6.13 to enable USE_RTC ? Yes you need USE_RTC for better timing. And you maybe need kernel 2.6.13 to get the USE_RTC functionality because it depends on the kernel. My FC4 box has a 2.6.12 kernel which contains the upstream USE_RTC stuff so I patch the asterisk source to enable it on 2.6.12 too. If you use a plain vanilla unpatched kernel than yes you will need 2.6.13. rant The delay issue in meetme has been present for a long time now and it seems Digium is not interested in fixing it. Afaik a patch was offered that solved the issue but was rejected by Mark because he felt the extra thread it used would not work on embedded systems with no memory/cpu power. Fine if it doesn't but why isn't it then possible to just do: #ifdef normal_pc_or_server_99.999%_of_people_use finally_fix_meetme_delay #endif /rant Regards, Patrick ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] Bug 4301 - ztdummy accuracy problem
Hi, I am also getting same problem with zaptel 1.20-beta1 version tar.gz file. It's running on linux 2.4. For this, kernel timer is changed to 1ms and ztdummy is modified accordingly. Is there 4301 bug with tar.gz file from asterisk.org? Is it needed to check out 1.2.0-beta1. Thanks, Surendra. Tzafrir Cohen wrote: On Mon, Oct 17, 2005 at 07:53:55AM -0400, BJ Weschke wrote: Chih, The bug was closed because the ztdummy behavior is not the specific cause for the delay problem. That patch with USE_RTC was intended to make use of the real time resource available within the kernel = 2.6.13 instead of relying on a OHCI USB resource which was the case previously. ztdummy uses the kernel's internal clock for kernel 2.6 even without USE_RTC . with USE_RTC you should expect to get better accuracy, though. ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] Bug 4301 - ztdummy accuracy problem
Patrick wrote: Yes you need USE_RTC for better timing. And you maybe need kernel 2.6.13 to get the USE_RTC functionality because it depends on the kernel. My FC4 box has a 2.6.12 kernel which contains the upstream USE_RTC stuff so I patch the asterisk source to enable it on 2.6.12 too. If you use a plain vanilla unpatched kernel than yes you will need 2.6.13. Thank you for the clarification. I use Scientific Linux 4, which probably equal to RHEL4, with its default kernel 2.6.9. I don't know if it has new rtc stuff. I'll try a new kernel later, anyway. rant The delay issue in meetme has been present for a long time now and it seems Digium is not interested in fixing it. Afaik a patch was offered that solved the issue but was rejected by Mark because he felt the extra thread it used would not work on embedded systems with no memory/cpu power. Fine if it doesn't but why isn't it then possible to just do: #ifdef normal_pc_or_server_99.999%_of_people_use finally_fix_meetme_delay #endif /rant Totally agreed! The increasing delay issue in meetme is a *really problem*. After ten minutes or so conversation, the delay can increase to 3-4 seconds, which is *unaccetable* for most people. All my customers have complains about it. I really hope it can be solved before 1.2 release. So where can I find the patch you mentioned? ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] Bug 4301 - ztdummy accuracy problem
On Tue, 2005-10-18 at 18:37 +0800, Chih-Wei Huang wrote: [snip] I use Scientific Linux 4, which probably equal to RHEL4, with its default kernel 2.6.9. I don't know if it has new rtc stuff. I'll try a new kernel later, anyway. It may be possible that Update 2 of RHEL4 has the USE_RTC patch. Maybe you can find it out by downloading the SRPM and check the specfile to see if it is mentioned. Or ask on a CentOS mailinglist or in #centos (CentOS is a clone of RHEL4 and have just released Update 2 also). rant The delay issue in meetme has been present for a long time now and it seems Digium is not interested in fixing it. Afaik a patch was offered that solved the issue but was rejected by Mark because he felt the extra thread it used would not work on embedded systems with no memory/cpu power. Fine if it doesn't but why isn't it then possible to just do: #ifdef normal_pc_or_server_99.999%_of_people_use finally_fix_meetme_delay #endif /rant Totally agreed! The increasing delay issue in meetme is a *really problem*. After ten minutes or so conversation, the delay can increase to 3-4 seconds, which is *unaccetable* for most people. All my customers have complains about it. I really hope it can be solved before 1.2 release. So where can I find the patch you mentioned? I don't know. I don't even know if it was ever posted somewhere like on bugs.digium.com so I can't help you there. Sure would be nice if the patch would surface. Regards, Patrick ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] Bug 4301 - ztdummy accuracy problem
On 10/18/05, Chih-Wei Huang [EMAIL PROTECTED] wrote: BJ Weschke wrote: The bug was closed because the ztdummy behavior is not the specific cause for the delay problem. That patch with USE_RTC was intended to make use of the real time resource available within the kernel = 2.6.13 instead of relying on a OHCI USB resource which was the case previously.But USE_RTC also compile for kernel 2.6.13..(at least, 2.6.9 in my system)Is kernel = 2.6.13 necessary? If you're looking for a fix in MeetMe, some have reported success with applying the patches available in bug 5374.Thank you for the info.I tried that patch.Unfortunately, it seems not improve the increasing delay problem of meetme. Patch in bug # 5374 only makes a difference if Asterisk gets complied with -DZAPTEL_OPTIMIZATIONS. When compiling Asterisk, can you tell if -DZAPTEL_OPTIMIZATIONS is being used? After Asterisk is compliled this way, ztdummy needs to be running. Carlos ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
[Asterisk-Dev] Bug 4301 - ztdummy accuracy problem
Since the bug has been closed, I sent the question here. I saw patch for bug 4301 has been included in zaptel 1.2-beta1, but with a limitation kernel version = 2.6.13. Does it mean USE_RTC will not work for kernel version 2.6.13? I tested meetme with OH323 driver and encountered the increasing delay problem. My kernel is 2.6.9. I removed the kernel limitation by hand and recompile ztdummy, but the delay problem is not solved. Should I upgrade kernel and test again? ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] Bug 4301 - ztdummy accuracy problem
Are you using the name/record playback option? On 10/18/05, Chih-Wei Huang [EMAIL PROTECTED] wrote: BJ Weschke wrote: The bug was closed because the ztdummy behavior is not the specific cause for the delay problem. That patch with USE_RTC was intended to make use of the real time resource available within the kernel = 2.6.13 instead of relying on a OHCI USB resource which was the case previously. But USE_RTC also compile for kernel 2.6.13..(at least, 2.6.9 in my system)Is kernel = 2.6.13 necessary? If you're looking for a fix in MeetMe, some have reported success with applying the patches available in bug 5374.Thank you for the info.I tried that patch.Unfortunately, it seems not improve the increasing delay problemof meetme.Any suggestion or experience for the delay problem? especially using with OH323 channel driver.___Asterisk-Dev mailing listAsterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-devTo UNSUBSCRIBE or update options visit:http://lists.digium.com/mailman/listinfo/asterisk-dev ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
