<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=white lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><a name="_MailEndCompose"><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></a></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>>> </span>Sean Brady
wrote: <o:p></o:p></p>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>To get MeetMe working properly, I know some sort of timing device<o:p></o:p></pre><pre>provided by the zaptel package is required (even if it means the<o:p></o:p></pre><pre>zt_dummy). But, on a virtual machine I know that the Linux timing won't<o:p></o:p></pre><pre>work as expected. Is it possible to then dedicate a physical device<o:p></o:p></pre><pre>like a USB port or something to the virtual machine to use for the<o:p></o:p></pre><pre>timing interrupts?<o:p></o:p></pre><pre> <o:p></o:p></pre></blockquote>
<pre><o:p> </o:p></pre><pre><span style='color:#1F497D'>>></span>The 2.2.1 version of DAHDI using DAHDI dummy seems to be working adequately in a Xen environment on CentOS for me, although I haven't been using MeetMe. Have you run into issues with it specifically? Which version of DAHDI are you using? If there are some issues that you have found I would like to know...<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><span
style='color:#1F497D'>>> </span>Thanks,<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><span
style='color:#1F497D'>>> </span>Sean<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> <o:p></o:p></pre>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='color:#1F497D'>></span>To
be honest I haven't tried it with Asterisk version 1.4 or higher. I only
tried it with 1.2 and when the DAHDI was called "Zaptel". I
have been a little <span style='color:#1F497D'>></span>afraid to upgrade to
1.6 from 1.2 just in case there are<br>
<span style='color:#1F497D'>></span>some incompatibilities in my config
that'll bring down the phone system here at the office for a while.<br>
<br>
<span style='color:#1F497D'>> </span>The issue that I had was that the even
the calls were choppy. Not even specifically just the MeetMe ones.
But that was on VirtualBox. I am using<span style='color:#1F497D'> ></span>KVM
now. I'm not sure if that matters.<br>
<br>
<span style='color:#1F497D'>> </span>What is your timer frequency set to in
the kernel btw?<span style='color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>With DAHDI dummy in 2.2.1 you
don’t have to even do that, AFAIK. At least I didn’t on my
test box. <o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>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. <o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>I have been told repeatedly
that Asterisk shouldn’t be virtualized, and that timing was an issue,
however I have never been given a reason that I consider acceptable to preclude
me from doing so. I have also seen presentations talking about using
Asterisk in Xen environments as well as Amazon’s EC2 (also Xen). So
there is some real contradictions and FUD surrounding Asterisk virtualized.
Perhaps I am just stubborn, but I am determined to run Asterisk virtualized in
production with conferencing (be it meetme or confbridge) until it’s been
proven without doubt that it just doesn’t work. <o:p></o:p></span></p>
</div>
</body>
</html>