On 04/21/2010 07:13 PM, bruce bruce wrote:
How can I find out what the source of the problem is guys?
As I said I didn't change anything, except for making few minor changes
to the firewall today and that was at Amazon firewall level and not
within CentOS.
What causes these bad dahdi_test
Hi Everyone,
I have a weired situation where calls in and out are proceessed all right
but when I dial *97 Asterisk is literally choking when it comes to
announcements like Password or Call from 205-456-. Each one of those
announcements can take like 10+ seconds to finish with most of it not
Are your sound files being transcoded or played back in their native
formats?
On 04/21/2010 12:25 PM, bruce bruce wrote:
Hi Everyone,
I have a weired situation where calls in and out are proceessed all
right but when I dial *97 Asterisk is literally choking when it comes to
announcements
Yes, it's all g.711 ulaw.
On Wed, Apr 21, 2010 at 1:37 PM, Darrick Hartman (lists)
dhart...@djhsolutions.com wrote:
Are your sound files being transcoded or played back in their native
formats?
On 04/21/2010 12:25 PM, bruce bruce wrote:
Hi Everyone,
I have a weired situation where
Are you running asterisk in a virtual machine?
--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
yes, it's on Amazon.
On Wed, Apr 21, 2010 at 2:26 PM, Ryan Bullock rrb3...@gmail.com wrote:
Are you running asterisk in a virtual machine?
--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to
Then use a timing source if the version is correct (1.6.1 or 2), or install
dahdi-dummy, which can
be quite some amount of work
On Wed, Apr 21, 2010 at 12:35 PM, bruce bruce bruceb...@gmail.com wrote:
yes, it's on Amazon.
On Wed, Apr 21, 2010 at 2:26 PM, Ryan Bullock rrb3...@gmail.com wrote:
So I be it sounds like all the recordings are underwater.
Are you using dahdi for timing? Can you run dahdi_test?
Asterisk needs a good timing source, in the case when you don't have a
physical card providing it, it relies on kernel ticks or the RTC (or HPET).
Because of the nature of virtual
Thanks for the input.
I am going to check this once I get access to system again tonight.
But I thought the timing source dahdi_dummy is only good for features like
MeetMe or conference rooms? or am I wrong and it has an effect on any type
of calls and checking voice messages?
Thanks
On Wed,
Here are result of dahdi_test:
[r...@ip-10-251-123-3 ~]# dahdi_test
Opened pseudo dahdi interface, measuring accuracy...
99.725% 96.018% 99.532% 91.934% 99.923% 99.923% 99.628% 99.434%
-434.763% 99.239% 93.770% 99.141% 99.822% 91.232% 99.727% 93.770%
99.726% -403.227% 98.069% 98.458% 95.136%
On 22 Apr 2010, at 00:36, bruce bruce wrote:
Opened pseudo dahdi interface, measuring accuracy...
99.725% 96.018% 99.532% 91.934% 99.923% 99.923% 99.628% 99.434%
-434.763% 99.239% 93.770% 99.141% 99.822% 91.232% 99.727% 93.770%
99.726% -403.227% 98.069% 98.458% 95.136% 98.749% 91.229% 87.622%
On 04/21/2010 05:36 PM, bruce bruce wrote:
Here are result of dahdi_test:
[r...@ip-10-251-123-3 ~]# dahdi_test
Opened pseudo dahdi interface, measuring accuracy...
99.725% 96.018% 99.532% 91.934% 99.923% 99.923% 99.628% 99.434%
-434.763% 99.239% 93.770% 99.141% 99.822% 91.232% 99.727% 93.770%
It's running on an Amazon instance. No changes to system made and it was
working find previously.
Here is an output of top:
[r...@ip-10-251-123-3 ~]# top
top - 19:59:48 up 6:52, 1 user, load average: 0.78, 0.95, 0.99
Tasks: 49 total, 2 running, 47 sleeping, 0 stopped, 0 zombie
Cpu(s):
On Wed, 2010-04-21 at 19:36 -0400, bruce bruce wrote:
Here are result of dahdi_test:
[r...@ip-10-251-123-3 ~]# dahdi_test
Opened pseudo dahdi interface, measuring accuracy...
99.725% 96.018% 99.532% 91.934% 99.923% 99.923% 99.628% 99.434%
-434.763% 99.239% 93.770% 99.141% 99.822% 91.232%
I know that anything lower than 99% is bad. But *-400 *?
Anything care of comment?
Thanks,
On Wed, Apr 21, 2010 at 7:45 PM, Steve Howes steve-li...@geekinter.netwrote:
On 22 Apr 2010, at 00:36, bruce bruce wrote:
Opened pseudo dahdi interface, measuring accuracy...
99.725% 96.018% 99.532%
How can I find out what the source of the problem is guys?
As I said I didn't change anything, except for making few minor changes to
the firewall today and that was at Amazon firewall level and not within
CentOS.
What causes these bad dahdi_test values?
P.S. there is only few calls load at
On Wed, 21 Apr 2010, bruce bruce wrote:
It's running on an Amazon instance. No changes to system made and it was
working find previously.
Maybe you could correlate the fluctuations in your timing source with the
attacks on Randy and Fred's systems.
--
Thanks in advance,
On Wed, Apr 21, 2010 at 6:13 PM, bruce bruce bruceb...@gmail.com wrote:
How can I find out what the source of the problem is guys?
As I said I didn't change anything, except for making few minor changes to
the firewall today and that was at Amazon firewall level and not within
CentOS.
What
18 matches
Mail list logo
