| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] Xen and Asterisk/Zapata WORKING!!
I require to install various Asterisk on a same Xen host
So I need to share timer caps across VMs
Jason a écrit :
I haven't used the conference module because my asterisk is mostly a
glorified answering machine and used to PSTN/IAX/SIP outbound calls.
But the FXO card should provide a solid timing interface for you. Im
using Zaptel 1.2.7 and Asterisk 1.2.10 . I don't use the ztdummy
module at all, only zaptel and wcfxo.
Sébastien CRAMATTE wrote:
Hi,
Do you don't use ztdummy driver isn't ? Conference module works well ?
Have you get the lastest zaptel drivers from svn trunk ?
Regards
Jason a écrit :
Hey there, Im on 3.0-unstable change set Fri Mar 31 00:26:07 2006
+0100 9494:8a8361994904
I did set the timer to 1kHz and Im using pci passthru to my domU. My
card is just one of those FXO cards off ebay that can be had for 12
bucks. Hardware wise, Im on a Celeron 2.4ghz with 2 gig of RAM and 6
other VMs running (including MythTV with 3 tuners running pretty
much non stop) . I did have some RTC trouble when I first attempted
this, but the latest version of the zaptel drivers seemed to clear
that up. As for sound and stability, it has been rock solid for me
on the PSTN and SIP. I have had some trouble with an IAX tunnel to a
IAX/PSTN provider, but that ended up being the providers hardware.
I use the asterisk machine everyday, record every call and use it
for voicemail on the road. as for CPU time, this VM is almost
always at 0.00 load. Memory usage is usually around 64M total out of
256M dedicated to this VM, no swap partition. The one time it seems
to flake is when my myth box does commercial flagging on several
recordings at once and eats up all of my disk IO.
Here are an xm info and my asterisk.conf file for that vm.
-->asterisk.conf
kernel = "/boot/vmlinuz-2.6.16-xenU"
memory = 256
name = "asterisk"
pci = ['02:03.0']
vif = [ 'ip=10.0.0.129, vifname=asterisk' ]
disk = [ 'phy:vm-vg/asterisk-lv,hda1,w' ]
root = "/dev/hda1 ro"
-->xm info
host : hive
release : 2.6.16-xen0
version : #13 Sat Apr 29 09:22:22 CDT 2006
machine : i686
nr_cpus : 1
nr_nodes : 1
sockets_per_node : 1
cores_per_socket : 1
threads_per_core : 1
cpu_mhz : 2660
hw_caps : bfebfbff:00000000:00000000:00000180:0000441d
total_memory : 2048
free_memory : 359
xen_major : 3
xen_minor : 0
xen_extra : -unstable
xen_caps : xen-3.0-x86_32
platform_params : virt_start=0xfc000000
xen_changeset : Fri Mar 31 00:26:07 2006 +0100
9494:8a8361994904
cc_compiler : gcc version 3.4.3
cc_compile_by : root
cc_compile_domain : [unknown]
cc_compile_date : Thu Mar 30 22:59:18 CST 2006
Duncan Gibb wrote:
On Sun, 2006-08-13 at 23:56, Jason wrote:
J> thought I would post how I got asterisk playing well
J> in a DomU with an X100P FXO card.
Good to know someone else is also playing with this. Could you post a
bit more detail about when your Xen snapshot was taken, the config
options and the hardware you're using, please?
I have a 600MHz P-III system on which I want to use a Xen domU to
develop zaptel modules without worrying about bringing down the
machine
when I get it wrong.
Using Xen 3.0.2-2 and the standard 2.6.16-xen kernel lightly
reconfigured (1000Hz, serial enabled) almost worked, but the jitter
was
so bad voicemails were incomprehensible (even when left by SIP).
Dialling out on an analogue line with a clone wcfxo card worked only
intermittently because the DTMF synthesis broke up towards the end
of a
10-digit UK number.
CPU load didn't seem to be the problem, and Googling around
suggested a
working RTC might help. I have therefore rebuilt with the Xen nightly
snapshot from Sunday and 2.6.16.13-xen. I'm not convinced that the
RTC
does actually work (still get IRQ 8 not free sometimes), and wcfxo
frequently reports it can't init the DAA (ie interrupts are
probably not
working in the domU).
I've tried both passthrough and vpci pci backend drivers. And I've
turned on permissive mode after seeing warnings when doing modprobe
wcfxo in the domU.
J> The first thing I did was to give up trying to get the zaptel
J> modules to compile in a DomU. I never did get that part working.
My solution to this was to copy the linux build tree from the dom0
over
to /usr/src in the domU, along with the xen tree and the
linux-2.6-xen-sparse tree and symlinking as you did.
Cheers
Duncan
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home