search for: res_timing_timerfd

Hi all Sometimes (about every three months) some of my Asterisk 1.8 boxes will start running this message thousands of times in the CLI: [Feb 12 14:18:23] ERROR[28129]: res_timing_timerfd.c:180 timerfd_timer_ack: Call to timerfd_gettime() error: Invalid argument [Feb 12 14:18:23] ERROR[28129]: res_timing_timerfd.c:180 timerfd_timer_ack: Call to timerfd_gettime() error: Invalid argument [Feb 12 14:18:23] ERROR[28129]: res_timing_timerfd.c:180 timerfd_timer_ack: Call to timerfd_gettim...

Carlos and Stefan (and other who have helped): I DON'T HAVE the res_timing_timerfd.so file. Can I build it? Recompiling Asterisk is unrealistic in my position but I wonder if I can build the one module. Here's what I do have: apbx:~ $ locate *res_timing_timerfd* /usr/src/asterisk-1.8.23.1/res/.res_timing_timerfd.makeopts /usr/src/asterisk-1.8.23.1/res/.res_timing_timerfd.mo...

hi: my current system is 1.6.2. I have dahdi hardware card. I must disable res_timing_timerfd module or sometimes phone calls would become silent suddenly. I don't know the situation in 1.8. I heard that timing is still a problem in 1.8. should I keep using "res_timing_dahdi" or I can use "res_timing_timerfd" to get some benefit if I upgrade to 1.8? thank a lot f...

...th an active conference (95% idle doesn't mean that >some core isn't pegged) > - Any potential transcoding issues or codec issues >Matt Hi Matt - thanks. Looks like I am ONLY loading: res_timing_pthread res_timing_dahdi But I dont think the res_timing(x) is working on CentOS 5. res_timing_timerfd does not even seem to be compiled on this box. How do I tell for sure what its using and if its good. All I saw in the asterisk log was the two res_timing_pthread and res_timing_dadhi being loaded. Everything else is fine actually. It worked with the card, and withthout the card just sending aud...

...onds, then hangs up the call. My initial thought was jitter problems, but that doesn't seem to be the case. I believe I found the cause while looking at the asterisk logs. I am finding hundreds of entries like this when they report audio problems. [08/19 15:04:17.176] DEBUG[4062][C-00000076] res_timing_timerfd.c: Expected to acknowledge 1 ticks but got 4 instead [08/19 15:04:17.173] DEBUG[4008][C-0000005b] res_timing_timerfd.c: Expected to acknowledge 1 ticks but got 3 instead [08/19 15:04:17.180] DEBUG[4008][C-0000005b] res_timing_timerfd.c: Expected to acknowledge 1 ticks but got 2 instead [08/19 15:04...

...odule Description                              Use Count  Status Support Level res_timing_dahdi.so            DAHDI Timing Interface                   0          Running              core res_timing_pthread.so          pthread Timing Interface                 0          Running          extended res_timing_timerfd.so          Timerfd Timing Interface                 1          Running              core 3 modules loaded     This will show you what module Asterisk is using for timing. You can try doing a noload on the two you do not need. -- Telecomunicaciones Abiertas de México S.A. de C.V. Carlos Cháv...

...0fto SIP/210-0000170e [Mar 4 17:29:38] NOTICE[25790] app_chanspy.c: Attaching SIP/209-00001715 to SIP/210-00001714 [Mar 4 17:31:06] NOTICE[25812] app_chanspy.c: Attaching SIP/209-0000171c to SIP/210-0000171a [Mar 4 17:31:19] ERROR[25818] acl.c: Cannot create socket [Mar 4 17:31:19] ERROR[25818] res_timing_timerfd.c: Failed to create timerfd timer: Too many open files [Mar 4 17:31:19] WARNING[25818] channel.c: Channel allocation failed: Can't create alert pipe! Try increasing max file descriptors with ulimit -n [Mar 4 17:31:19] WARNING[25818] chan_sip.c: Unable to allocate AST channel structure for SIP...

...so load => codec_gsm.so load => codec_lpc10.so load => codec_ulaw.so load => format_gsm.so load => format_pcm.so load => format_wav.so load => format_wav_gsm.so load => res_agi.so load => res_clioriginate.so load => res_fax.so load => res_musiconhold.so load => res_timing_timerfd.so load => func_callerid.so load => func_cdr.so load => func_channel.so load => func_cut.so load => func_math.so load => func_rand.so load => func_strings.so load => func_global.so load => cdr_csv.so Regards -------------- next part -------------- An HTML attachment w...

...83, ASTERISK-17870, ASTERISK-17430, ASTERISK-17452, ASTERISK-17452, ASTERISK-15792. Reported by: David Cabrejos, Remi Quezada, Philippe Lindheimer, David Woolley, Mat Murdock. Patched by: rmudgett) * Numerous issues have been reported for deadlocks that are caused by a blocking read in res_timing_timerfd on a file descriptor that will never be written to. A change to Asterisk adds some checks to make sure that the timerfd is both valid and armed before calling read(). Should fix: ASTERISK-18142, ASTERISK-18197, ASTERISK-18166 and possibly others. (In essence, this change should make...

...83, ASTERISK-17870, ASTERISK-17430, ASTERISK-17452, ASTERISK-17452, ASTERISK-15792. Reported by: David Cabrejos, Remi Quezada, Philippe Lindheimer, David Woolley, Mat Murdock. Patched by: rmudgett) * Numerous issues have been reported for deadlocks that are caused by a blocking read in res_timing_timerfd on a file descriptor that will never be written to. A change to Asterisk adds some checks to make sure that the timerfd is both valid and armed before calling read(). Should fix: ASTERISK-18142, ASTERISK-18197, ASTERISK-18166 and possibly others. (In essence, this change should make...

...#39;s causing the problem? I've looked at various upgrade instructions and haven't seen anything, but it's easy to miss details in the reams of info out there! In any case, the log looks like this: == Manager 'veco' logged on from 127.0.0.1 [Feb 10 14:14:36] ERROR[15569]: res_timing_timerfd.c:105 timerfd_timer_open: Failed to create timerfd timer: Function not implemented [Feb 10 14:14:36] ERROR[15569]: res_timing_timerfd.c:105 timerfd_timer_open: Failed to create timerfd timer: Function not implemented -- Executing [conference at veco:1] Answer("Local/conference at veco-...

Thank you for a quick answer, Dmitry! We have tried the settings you suggested but nothing helped. The machine is running 4.4.0-104 kernel, 4 cores, Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz, clocksource is hyperv_clocksource_tsc_page, timing module is res_timing_timerfd.so. We have also tried to set 50% Reserve - no luck :(. ??, 18 ???. 2017 ?. ? 10:49, Dmitriy Ermakov <demonihin at gmail.com>: > Hi, Kseniya! > > I have three installations of Asterisk (as FreePBX but I think it is not > important). They work fine. > > I have made some set...

...Thank you for a quick answer, Dmitry! We have tried the settings you suggested but nothing helped. The machine is running?4.4.0-104 kernel, 4 cores,?Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz, clocksource is?hyperv_clocksource_tsc_page, timing module is res_timing_timerfd.so. We have also tried to set 50% Reserve - no luck :(.? ??, 18 ???. 2017 ?. ? 10:49, Dmitriy Ermakov <demonihin at gmail.com <mailto:demonihin at gmail.com>>: Hi, Kseniya! I have three installations of Asterisk (as FreePBX but I...

Folks, I've read some sources claiming that Asterisk does not need DAHDI for timing in 1.6.1. Is this true? Searching the web, all I can find is pages celebrating the fact but no actual documentation on which version it was introduced in and how one would go about configuring an external time source. I'm having a devil of a job trying to compile DAHDI on a hosted Xen VM and thought I

Hi! I have Asterisk 1.6.1 installed on OpenSuSE 11.0 running with choppy sound. One specialist on the forums asked me if I have DAHDI configured, he assumed that this could be cause of choppy sound problem. > dahdi_test Unable to open dahdi interface: No such file or directory Do I need to configure DAHDI even if I do not have any Zaptel devices? Is there any guide for configuring

Hello, i just made the reproducible watching: I send a Fax from asterisk (trunk) with spandsp (latest snapshot) via T.38 -> Audiocodes Mediant 2000 (FW 5.60.43.5) -> PSTN Fax With Internal timing Enabled, the Fax break after the first quarter from the first page is transfered. With Internal timing Disabled, the fax is transferred flawless. Both test with pthread timing module on a QEMU

Hi All Just finished setting up a vm with centos 5.5 and asterisk 1.8.3 Using timerfd as a timing source. Has anyone got a similar setup in production ? How's performance? Thanks, Neeraj?

Greetings list, Has anyone compiled (or could point me at) a list of the minimum required modules and conf files for a very basic 1.8 deployment? We have lots of 1.4 boxes in production, and I'm currently setting up a pair of 1.8 boxes to bounce calls coming in via IAX over IPv6 over to the existing 1.4 boxes. All the new installs need to do is receive calls via IAX and send them out via

...r is just a symptom of something else, possibly centered around a timing issue. I tried res_timing_dahdi and that worked for about a week, then suddenly things went haywire and calls wouldn't last for more than a few seconds before being dropped. A restart didn't help. I switched over to res_timing_timerfd.so, and it seems to be working ok, but I'm worried this will happen again after some time (it never seems to be immediate). There is no dahdi hardware installed in this machine and... it's actually a VM. However it's never really been starved for CPU or RAM - the CPU barely goes above...

...ors we get are: ERROR[6518] res_timing_dahdi.c: Failed to configure DAHDI timing fd for 0 sample timer ticks WARNING[22024] app_meetme.c: Unable to write frame to channel Right now, dahdi in our setup uses the software timer (with res_timing_dahdi.so which gives much better results compared to res_timing_timerfd.so). On an idle system (Centos 6, Asterisk 1.8.7, dahdi 2.5), dahdi_test results are pretty good at about %99.99. However, when loaded, the numbers fluctuate between %99.90 and %99.99 which seem to cause the above errors. We tried Sangoma UT50 as a timing device (it's USB based), but the test...