[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Please share your asterisk domU configurations ( config file, firewalling, etc)

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Christopher Isip" <cmisip@xxxxxxxxx>
  • Date: Sat, 17 May 2008 10:24:14 -0400
  • Delivery-date: Sat, 17 May 2008 07:24:44 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=IToMwDrMeg8bMKR7YV/vY65InGywq9pP9cPHJjujrkC2gVJL09wMXbB2t1LkOE1U5qwlZ5x4Uip06XIbzps8zfT2GJ0pxioyDMIz+NFrEUIqfh9f0cGDOsreTNoJa3/D2Hdl2Y5MC0QjnhamG5xgkEhrm/WEeZJ7P3TgNiBWODQ=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I cant seem to be able to get an Asteisk domU to work for anonymous inbound calls.  ( Have not tested yet for external sip calls from registered clients)  It is not a freepbx issue, but rather some routing issue particular to a xen setup. Outbound calls work fine.


1. The asterisk domU can answer calls with 2 way audio if I use another machine on the lan as a linux router/gateway forwarding to the domU.

2. The asterisk domU can answer calls with 1 way audio if I use the netgear router as the gateway port forwarding to the domU.

3. The asterisk domU cannot answer calls If it is assigned a PCI card and a vif interface, basically turning it into a firewall router.  I would have assumed that eliminating NAT by using this config would work the best.

4. The asterisk domU cannot answer calls if it has a single vif interface and another firewall domU  is portforwarding to it.

IP masquerading works in all scenarios and firewalls have been cleared in the asterisk domU.  I have tried iptables to route packets to the asterisk domU as well as shorewall with no luck.  The fact that the vif is part of a bridge is probably the reason its not working.  

I have not been able to configure dom0 as a router yet to route sip calls to the asterisk domU.  I have to look into this yet.  The fact that xend renames the bridge to eth0 complicates matters as shorewall is complaining about the peth0 interface if I designate that in /etc/shorewall/interfaces.

My preferred scenario is to have a singe vif interface to an asterisk domU and have another firewall domU port forward to it.  If it is not possible,  then setup dom0 as the router.  If not, that then purchase a router that can route with 2 way audio to the asterisk domU.

I have thought about completely removing the vif interface from the asterisk domU and assigning it a physical nic to connect to the netgear router.  I will try that next to see if it fixes the 1 way audio problem.

Any help is appreciated.


Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.