We are using openVZ with FreeSWITCH running in a container. In another situation, I successfully installed DAHDI in the host node, exported the devices to the container and installed libpri in the container. FS could access the card without any problems. We are moving to a Sangoma A101D and an A200. I have installed the wanpipe drivers in the host node (make freetdm and make install), exported the devices to the container and installed the signaling in the container (make install_pri). However, that is not quite enough for the container, because mod_freetdm looks for libsangoma, which is in the host node. wancfg_fs does too much, because it attempts to configure wanrouter and FS at the same time. I've looked through the FS wiki and the FS section of the Sangoma wiki, but all of the directions are for a combined installation. Is there a set of steps to install the wanpipe drivers separately from the signaling and do the individual configuration for each? Thanks. Russell
Its basically the same thing.. let the VE have access to the hardware. /b On Oct 4, 2010, at 7:18 AM, Russell Mosemann wrote:
We are using openVZ with FreeSWITCH running in a container. In another situation, I successfully installed DAHDI in the host node, exported the devices to the container and installed libpri in the container. FS could access the card without any problems.
We are moving to a Sangoma A101D and an A200. I have installed the wanpipe drivers in the host node (make freetdm and make install), exported the devices to the container and installed the signaling in the container (make install_pri). However, that is not quite enough for the container, because mod_freetdm looks for libsangoma, which is in the host node. wancfg_fs does too much, because it attempts to configure wanrouter and FS at the same time.
I've looked through the FS wiki and the FS section of the Sangoma wiki, but all of the directions are for a combined installation. Is there a set of steps to install the wanpipe drivers separately from the signaling and do the individual configuration for each? Thanks.
Russell
Its basically the same thing.. let the VE have access to the hardware.
If you carefully read my previous message, that part is already done. The issue is installing the required signaling files and libraries in the VE without also compiling the drivers in the VE. -- Russell Mosemann ________________________________________________________ Concordia University, Nebraska See http://www.cune.edu/ for the latest news and events!
Hi Russell, On Mon, Oct 4, 2010 at 8:18 AM, Russell Mosemann <Russell.Mosemann@cune.org> wrote:
We are moving to a Sangoma A101D and an A200. I have installed the wanpipe drivers in the host node (make freetdm and make install), exported the devices to the container and installed the signaling in the container (make install_pri). However, that is not quite enough for the container, because mod_freetdm looks for libsangoma, which is in the host node. wancfg_fs does too much, because it attempts to configure wanrouter and FS at the same time.
I have no experience with openVZ, but I know some of our support staff got it working with xen just fine. I think openVZ should not be a problem. You can configure in the host and start devices on the host, then configure FreeSWITCH/FreeTDM manually on the container (given that wancfg_fs does too much).
I've looked through the FS wiki and the FS section of the Sangoma wiki, but all of the directions are for a combined installation. Is there a set of steps to install the wanpipe drivers separately from the signaling and do the individual configuration for each? Thanks.
No tools to do it automatically if you want to do it separate. wancfg_fs is meant for newbie users and as a convenience tool. If you are playing with openVZ, you have to configure manually, or configure everything on the host and then just move the signaling configuration to the container. Drop by #sangoma at irc.freenode.org if you need a hand from our support staff. Moises Silva Senior Software Engineer Sangoma Technologies Inc. | 100 Renfrew Drive, Suite 100, Markham ON L3R 9R6 Canada t. 1 905 474 1990 x128 | e. moy@sangoma.com
Moises Silva <moises.silva@gmail.com> said:
I have no experience with openVZ, but I know some of our support staff got it working with xen just fine. I think openVZ should not be a problem.
I don't think there will be any problems. I have gotten this arrangement to work nicely with a different manufacturer's card. The devices are exported to the container so that they show up in /dev, as one would normally expect. The difference is that the drivers are in the host node, and the signaling is in the container.
No tools to do it automatically if you want to do it separate.
Darn, I was hoping it would be as simple a "make install_driver". I will dig into the installation files and figure out how to do it manually. Thanks. -- Russell Mosemann ________________________________________________________ Concordia University, Nebraska See http://www.cune.edu/ for the latest news and events!
participants (4)
-
Brian West
-
Moises Silva
-
Russell Mosemann
-
Russell.Mosemann＠cune.org