This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] Re: Please share your asterisk domU configurations ( config

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Re: Please share your asterisk domU configurations ( config file, firewalling, etc)
From: "Christopher Isip" <cmisip@xxxxxxxxx>
Date: Sun, 18 May 2008 01:39:47 -0400
Delivery-date: Sat, 17 May 2008 22:40:19 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=Mav5Xc+wQs1YhTFMK0JBjoeo01R5wq/EZffAcYSeHZQ=; b=iXIh1xg1LrRT2rcGdSQy6Bt+iURFq+3Uup0unw/oH0BARI++VRX2l1KkxWaUl6vp9rLhk3hIJtLrCHTvoRAFBOoW7xk5AIgdl45K06c401ZbhlBDNBy0S+3zuwYvNeKo1G57Nht9ZETmlpY+zpffRc7yFLefc0oIYCOcOY6D7ko=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=pdnS7K7M9sxa/SJ/M5cMTNffGfEHCwZaCDuF5MBaHml3KwgVQHY5xEAnVXP05jY7X2r8yOf6SU5d2+Q7H45md5ZDbJqxLVG+1lDFEX+G+ONGVxYEbAj8flZZJVcGennhyH5Fob0uAHzIvsSh0v2lZqdR5mYeVIDT6R5uKnFBrVA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4bca5f6c0805170724p6410c4d6u3a3860dd8ad0a204@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4bca5f6c0805170724p6410c4d6u3a3860dd8ad0a204@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

On Sat, May 17, 2008 at 10:24 AM, Christopher Isip <cmisip@xxxxxxxxx> wrote:
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.


Duh!  Duh! Duh!  Duh! to the nth power.

I managed to get scenario 3 up and running.  The issue was not routing at all.  I copied my update dyndns script from the older system and didn't realize that the interface has changed in the new xenified system. Thus it was registering my internal ip with dyndns.  No wonder anonymous calls didn't work.  Since I have the external interface and the vif in the Asterisk domU, the NAT issue went away and i have 2 way audio.




Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>