>Information on timing sources can be found here:>https://wiki.asterisk.org/wiki/display/AST/Timing+Interfaces>As noted on that page, ConfBridge can use any timing interface Asterisk >provides, and is not limited to the DAHDI timing interface. Generally, >timerfd is a good timing interface.>That aside, I would try to rule out external issues with the garbled audio >before changing the timing source. Things like: > - Analysis of the RTP traffic (along with potential jitter) > - CPU utilization with an active conference (95% idle doesn't mean that >some core isn't pegged) > - Any potential transcoding issues or codec issues>MattHi 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 audio to one endpoint has audio issues in a conference. The machine is doing nothign else at that time. Thanks, Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20161111/3ce14d06/attachment.html>
On Fri, Nov 11, 2016 at 10:46 AM, Jerry Geis <jerry.geis at gmail.com> wrote:> >Information on timing sources can be found here: > > >https://wiki.asterisk.org/wiki/display/AST/Timing+Interfaces > > >As noted on that page, ConfBridge can use any timing interface Asterisk > >provides, and is not limited to the DAHDI timing interface. Generally, > >timerfd is a good timing interface. > > >That aside, I would try to rule out external issues with the garbled audio > >before changing the timing source. Things like: > > - Analysis of the RTP traffic (along with potential jitter) > > - CPU utilization with 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 audio to > one endpoint has audio issues in a conference. The machine is doing > nothign else at that time. > > >You're probably running a version of the Linux kernel that doesn't support timerfd, hence why it isn't available. res_timing_pthread is ... not very good. It exists as an absolute, last ditch fall-back for Asterisk to provide a source of timing when none exists. As such, and assuming you have ruled out all other sources of the garbled audio, then I'm really not surprised that it isn't very effective. Your best bet would be to: - Provide a hardware timing source that res_timing_dahdi can use. IIRC, this should work even without a specific card, but does require the dahdi kernel module to be installed and available. (I could be wrong on the need for a physical card however, so your mileage may vary.) - Upgrade to a version of the kernel that res_timing_timerfd supports. That should be Linux 2.6.26 and glibc 2.8 or later. Personally, if I were in your shoes, I'd go with the latter. CentOS 6 should be good out of the box, and CentOS 5 is pretty long in the tooth. Matt -- Matthew Jordan Digium, Inc. | CTO 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: http://digium.com & http://asterisk.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20161111/936f10e8/attachment.html>
Hi, How can I double check which timer is currently is use in a running system ? core show settings doesn't tell anything, if I'm not mistaken. Regards 2016-11-11 21:02 GMT+01:00 Matthew Jordan <mjordan at digium.com>:> > > On Fri, Nov 11, 2016 at 10:46 AM, Jerry Geis <jerry.geis at gmail.com> wrote: > >> >Information on timing sources can be found here: >> >> >https://wiki.asterisk.org/wiki/display/AST/Timing+Interfaces >> >> >As noted on that page, ConfBridge can use any timing interface Asterisk >> >provides, and is not limited to the DAHDI timing interface. Generally, >> >timerfd is a good timing interface. >> >> >That aside, I would try to rule out external issues with the garbled >> audio >> >before changing the timing source. Things like: >> > - Analysis of the RTP traffic (along with potential jitter) >> > - CPU utilization with 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 audio to >> one endpoint has audio issues in a conference. The machine is doing >> nothign else at that time. >> >> >> > You're probably running a version of the Linux kernel that doesn't support > timerfd, hence why it isn't available. > > res_timing_pthread is ... not very good. It exists as an absolute, last > ditch fall-back for Asterisk to provide a source of timing when none > exists. As such, and assuming you have ruled out all other sources of the > garbled audio, then I'm really not surprised that it isn't very effective. > > Your best bet would be to: > - Provide a hardware timing source that res_timing_dahdi can use. IIRC, > this should work even without a specific card, but does require the dahdi > kernel module to be installed and available. (I could be wrong on the need > for a physical card however, so your mileage may vary.) > - Upgrade to a version of the kernel that res_timing_timerfd supports. > That should be Linux 2.6.26 and glibc 2.8 or later. > > Personally, if I were in your shoes, I'd go with the latter. CentOS 6 > should be good out of the box, and CentOS 5 is pretty long in the tooth. > > Matt > -- > Matthew Jordan > Digium, Inc. | CTO > 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA > Check us out at: http://digium.com & http://asterisk.org > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > Check out the new Asterisk community forum at: https://community.asterisk. > org/ > > New to Asterisk? Start here: > https://wiki.asterisk.org/wiki/display/AST/Getting+Started > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20161115/08812fc3/attachment.html>
module show like timing
Module 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 0
Running core
3 modules loaded
This is on asterisk 11.24.1 and dahdi-linux-complete 2.11.1, CentOS 7.2
lsmod | grep dahdi
dahdi 228088 0
crc_ccitt 12707 1 dahdi
PBX Core settings
-----------------
Version: 11.24.1
Build Options: LOADABLE_MODULES, BUILD_NATIVE
Maximum calls: Not set
Maximum open file handles: 1024
Root console verbosity: 0
Current console verbosity: 5
Debug level: 0
Maximum load average: 0.000000
Minimum free memory: 0 MB
Startup time: 16:23:00
Last reload time: 16:23:00
System: Linux/2.6.32-642.6.2.el6.x86_64 built by
root on x86_64 2016-10-30 20:40:02 UTC
System name:
Entity ID: b0:83:fe:d1:af:5d
Default language: en
Language prefix: Enabled
User name and group: /
Executable includes: Disabled
Transcode via SLIN: Enabled
Transmit silence during rec: Disabled
Generic PLC: Enabled
Min DTMF duration:: 80
* Subsystems
-------------
Manager (AMI): Enabled
Web Manager (AMI/HTTP): Disabled
Call data records: Enabled
Realtime Architecture (ARA): Disabled
* Directories
-------------
Configuration file:
Configuration directory: /etc/asterisk
Module directory: /usr/lib/asterisk/modules
Spool directory: /var/spool/asterisk
Log directory: /var/log/asterisk
Run/Sockets directory: /var/run
PID file: /var/run/asterisk.pid
VarLib directory: /var/lib/asterisk
Data directory: /var/lib/asterisk
ASTDB: /var/lib/asterisk/astdb
IAX2 Keys directory: /var/lib/asterisk/keys
AGI Scripts directory: /var/lib/asterisk/agi-bin
So I dont think I have a timing source ?????
How do I get one ?
Jerry
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20161117/aa113d0f/attachment.html>
Hi, Am 17.11.2016 um 13:51 schrieb Jerry Geis:> PBX Core settings > ----------------- > Version: 11.24.1 > Build Options: LOADABLE_MODULES, BUILD_NATIVE > Maximum calls: Not set > Maximum open file handles: 1024 > Root console verbosity: 0 > Current console verbosity: 5 > Debug level: 0 > Maximum load average: 0.000000 > Minimum free memory: 0 MB > Startup time: 16:23:00 > Last reload time: 16:23:00 > System: Linux/2.6.32-642.6.2.el6.x86_64 built by root on x86_64 2016-10-30 20:40:02 UTC > System name: > Entity ID: b0:83:fe:d1:af:5d > Default language: en > Language prefix: Enabled > User name and group: / > Executable includes: Disabled > Transcode via SLIN: Enabled > Transmit silence during rec: Disabled > Generic PLC: Enabled > Min DTMF duration:: 80That's a bit odd... On my Asterisk 11 setup, I see an entry "Internal timing" which is totally missing on your installation. You might want to try adding internal_timing = yes to the [general] section of your asterisk.conf and then stop and start your Asterisk. You can also try to unload all timing modules but "res_timing_timerfd.so" and try if it makes things better. If it does, you can prevent res_timing_dahdi from being loaded in your modules.conf. Max -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20161117/d08334f5/attachment.pgp>
I found this comment:
2014-04-08 21:20 +0000 [r411944-411974] Richard Mudgett <
rmudgett at digium.com>
* main/asterisk.c, /: Internal timing: Add notice that the -I and
internal_timing option are no longer needed. Add notice messages
during execution that the -I command line option and the
astersik.conf internal_timing option are no longer needed. The
internal timing functionality is now always enabled if there is a
timing module loaded. NOTE: Since the command line options and
the asterisk.conf config file are processed before the logging
system is initialized, the messages are output to stderr. Change
requested as a result of asterisk-dev list comments about the
commit for ASTERISK-22846 that removed the -I and internal_timing
options. Review: https://reviewboard.asterisk.org/r/3423/
........ Merged revisions 411964 from
http://svn.asterisk.org/svn/asterisk/branches/1.8
So on my 11.24.1 I dont think there is any such option any more.
So now what??
Thanks,
Jerry
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20161117/d43d3194/attachment.html>
On a newly installed idle 11.13.1 enabled system, I do also have: CLI> module show like timing Module Description Use Count res_timing_pthread.so pthread Timing Interface 0 res_timing_timerfd.so Timerfd Timing Interface 0 2 modules loaded but when a call is ongoing : CLI> module show like timing Module Description Use Count res_timing_pthread.so pthread Timing Interface 0 res_timing_timerfd.so Timerfd Timing Interface 1 2 modules loaded @Max: Thanks for mentioning "module show like timing" 2016-11-17 13:51 GMT+01:00 Jerry Geis <jerry.geis at gmail.com>:> module show like timing > Module 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 0 > Running core > 3 modules loaded > > This is on asterisk 11.24.1 and dahdi-linux-complete 2.11.1, CentOS 7.2 > > lsmod | grep dahdi > dahdi 228088 0 > crc_ccitt 12707 1 dahdi > > > PBX Core settings > ----------------- > Version: 11.24.1 > Build Options: LOADABLE_MODULES, BUILD_NATIVE > Maximum calls: Not set > Maximum open file handles: 1024 > Root console verbosity: 0 > Current console verbosity: 5 > Debug level: 0 > Maximum load average: 0.000000 > Minimum free memory: 0 MB > Startup time: 16:23:00 > Last reload time: 16:23:00 > System: Linux/2.6.32-642.6.2.el6.x86_64 built by > root on x86_64 2016-10-30 20:40:02 UTC > System name: > Entity ID: b0:83:fe:d1:af:5d > Default language: en > Language prefix: Enabled > User name and group: / > Executable includes: Disabled > Transcode via SLIN: Enabled > Transmit silence during rec: Disabled > Generic PLC: Enabled > Min DTMF duration:: 80 > > * Subsystems > ------------- > Manager (AMI): Enabled > Web Manager (AMI/HTTP): Disabled > Call data records: Enabled > Realtime Architecture (ARA): Disabled > > * Directories > ------------- > Configuration file: > Configuration directory: /etc/asterisk > Module directory: /usr/lib/asterisk/modules > Spool directory: /var/spool/asterisk > Log directory: /var/log/asterisk > Run/Sockets directory: /var/run > PID file: /var/run/asterisk.pid > VarLib directory: /var/lib/asterisk > Data directory: /var/lib/asterisk > ASTDB: /var/lib/asterisk/astdb > IAX2 Keys directory: /var/lib/asterisk/keys > AGI Scripts directory: /var/lib/asterisk/agi-bin > > > > So I dont think I have a timing source ????? > How do I get one ? > > Jerry > > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > Check out the new Asterisk community forum at: https://community.asterisk. > org/ > > New to Asterisk? Start here: > https://wiki.asterisk.org/wiki/display/AST/Getting+Started > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20161118/6baf61e5/attachment.html>