: Friday, February 19, 2010 12:37 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Virtual machine timing (KVM)
To get MeetMe working properly, I know some sort of timing device
provided by the zaptel package is required (even if it means the
zt_dummy
On Sun, Feb 21, 2010 at 10:04 PM, Sean Brady sbr...@gtfservices.com wrote:
I do get choppy audio when playing recordings occasionally. I haven’t had
time to figure that one out, but I haven’t put it into production yet.
You just said you're getting unexplained choppiness.
You also just said
David Backeberg wrote:
Timers are built on the premise that they have access to either a real
timing device, or unobstructed access to a processor which clicks
through a proc cycle at a pre-determined rate. Once you break those
rules, don't be surprised when the timers stop working, and 'bad
On Mon, Feb 22, 2010 at 10:51 AM, Jonathan Addleman j...@redowl.ca wrote:
David Backeberg wrote:
Timers are built on the premise that they have access to either a real
timing device, or unobstructed access to a processor which clicks
through a proc cycle at a pre-determined rate. Once you
On Mon, Feb 22, 2010 at 11:06 AM, David Backeberg dbackeb...@gmail.comwrote:
On Mon, Feb 22, 2010 at 10:51 AM, Jonathan Addleman j...@redowl.ca
wrote:
David Backeberg wrote:
Timers are built on the premise that they have access to either a real
timing device, or unobstructed access to a
I had a system running on Xen in test. I had terrible echo problems with a
SPA3000. As a reference, I swapped to bare metal machine and although I still
had echoing, the echoing was much closer to the original sound. The Xen server
was idle apart from the AsteriskNOW installation. So, this lead
Forgive the possibly stupid question, but do these problems you describe
apply equally to the dom0 as to any domU's in a xen system? I used to
think not, but now I'm starting to realize that I'm probably mistaken...
Dom0 is still a virtual machine, so I would say so.
--
Ian Murray wrote:
Forgive the possibly stupid question, but do these problems you describe
apply equally to the dom0 as to any domU's in a xen system? I used to
think not, but now I'm starting to realize that I'm probably mistaken...
Dom0 is still a virtual machine, so I would say so.
David Backeberg wrote:
On Fri, Feb 19, 2010 at 11:42 AM, Mike A. Leonetti
mleone...@evolutionce.com wrote:
To get MeetMe working properly, I know some sort of timing device
provided by the zaptel package is required (even if it means the
zt_dummy). But, on a virtual machine I know that
Sean Brady wrote:
To get MeetMe working properly, I know some sort of timing device
provided by the zaptel package is required (even if it means the
zt_dummy). But, on a virtual machine I know that the Linux timing won't
work as expected. Is it possible to then dedicate a physical device
On Sun, Feb 21, 2010 at 06:56:04AM -0500, Mike A. Leonetti wrote:
Well, when you're right you're right. If it's really that much of a bad
idea I'll just put in for a real machine. Although virtualizing seems
to be all the buzz lately so I was just wondering if I could consolidate
hardware
Sean Brady wrote:
To get MeetMe working properly, I know some sort of timing device
provided by the zaptel package is required (even if it means the
zt_dummy). But, on a virtual machine I know that the Linux timing won't
work as expected. Is it possible to then dedicate a physical device
To get MeetMe working properly, I know some sort of timing device
provided by the zaptel package is required (even if it means the
zt_dummy). But, on a virtual machine I know that the Linux timing won't
work as expected. Is it possible to then dedicate a physical device
like a USB port or
On Fri, Feb 19, 2010 at 11:42 AM, Mike A. Leonetti
mleone...@evolutionce.com wrote:
To get MeetMe working properly, I know some sort of timing device
provided by the zaptel package is required (even if it means the
zt_dummy). But, on a virtual machine I know that the Linux timing won't
work
David Backeberg wrote:
You could always use ConfBridge(), starting in 1.6.2.*, which does not
require DAHDI/Zaptel, and therefore doesn't require a timer.
It *does* require a timer (all conferencing requires a timer), but it
does not require a DAHDI/Zaptel timer, there are other options
To get MeetMe working properly, I know some sort of timing device
provided by the zaptel package is required (even if it means the
zt_dummy). But, on a virtual machine I know that the Linux timing won't
work as expected. Is it possible to then dedicate a physical device
like a USB port or
16 matches
Mail list logo
