Asterisk in container with Debian stable - Revision history

Kir: Reverted edits by StevenCook (talk) to last revision by Kir

2012-08-04T20:46:03Z

Reverted edits by StevenCook (talk) to last revision by Kir

Kir: Reverted edits by ThomasKelly (talk) to last revision by Narcisgarcia

2012-08-03T06:08:49Z

Reverted edits by ThomasKelly (talk) to last revision by Narcisgarcia

Narcisgarcia: Debian category

2009-02-01T15:55:20Z

Debian category

Kir: fixed link to host system

2008-04-09T11:31:02Z

fixed link to host system

Kir: vps, ve -> container

2008-04-09T11:30:37Z

vps, ve -> container

Kir: Asterisk in VE with debian stable moved to Asterisk in container with Debian stable: VE->container

2008-04-09T11:28:33Z

Asterisk in VE with debian stable moved to Asterisk in container with Debian stable: VE->container

Kirshil at 11:36, 14 January 2008

2008-01-14T11:36:18Z

Kirshil: how to compile asterisk inside CT

2008-01-11T14:25:10Z

how to compile asterisk inside CT

Dim at 08:08, 17 July 2006

2006-07-17T08:08:40Z

New page

Below is an example of how to install Asterisk into OpenVZ VE based on debian stable aka. "sarge":

<pre>
$ apt-get install asterisk

$ nano /etc/defaults/asterisk
</pre>

change:
<pre>
RUNASTERISK=no -> yes
AST_REALTIME=yes -> no (for realtime, you need

$ /etc/init.d/asterisk start
</pre>
modify the config files for asterisk, and done!

if you need capi or/and zaptel/zaphfc:

* for capi: you need the /dev files on you hw-node and vps:
<pre>
crw-rw---- 1 root dialout 68, 0 Jan 3 2006 /dev/capi20
crw-rw---- 1 root dialout 68, 1 Jan 3 2006 /dev/capi20.00
crw-rw---- 1 root dialout 68, 2 Jan 3 2006 /dev/capi20.01
crw-rw---- 1 root dialout 68, 3 Jan 3 2006 /dev/capi20.02
[...]
</pre>
/* if the files doesn' exist use mknod for creating it*/

and in your vps config add for directly access:
<pre>
DEVICES="c:68:0:rw, c:68:1:rw, c:68:2:rw"
</pre>
* for zaptel/zaphfc:
<pre>
crw-rw---- 1 root dialout 196, 0 Jan 4 2006 ctl
crw-rw---- 1 root dialout 196, 1 Jan 4 2006 1
crw-rw---- 1 root dialout 196, 2 Jan 4 2006 2
crw-rw---- 1 root dialout 196, 3 Jan 4 2006 3
crw-rw---- 1 root dialout 196, 4 Jan 4 2006 4
[...]
crw-rw---- 1 root dialout 196, 253 Jan 4 2006 timer
crw-rw---- 1 root dialout 196, 255 Jan 4 2006 pseudo
crw-rw---- 1 root dialout 196, 254 Jan 4 2006 channel
</pre>
/* if the files doesn' exist use mknod for creating it*/

and in your vps config
<pre>
DEVICES="c:196:0:rw, c:196:2:rw, c:196:1:rw, c:196:253:rw,c:196:254:rw,c:196:255:rw"
</pre>

if need both (capi and zaphfc)
<pre>
DEVICES="c:68:0:rw, c:68:1:rw, c:68:2:rw c:196:0:rw, c:196:2:rw, c:196:1:rw, c:196:253:rw,c:196:254:rw,c:196:255:rw"
</pre>

[[category:HOWTO]]

← Older revision		Revision as of 15:55, 1 February 2009
Line 59:		Line 59:

	[[Category:HOWTO]]		[[Category:HOWTO]]
		+	[[Category:Debian]]

@@ Line 18: / Line 18: @@
 If you need capi or/and zaptel/zaphfc:
-* for capi: you need the /dev files on you host [[system]] and in container:
+* for capi: you need the /dev files on you [[host system]] and in container:
 <pre>
 crw-rw---- 1 root dialout 68, 0 Jan 3 2006 /dev/capi20

← Older revision		Revision as of 11:36, 14 January 2008
Line 1:		Line 1:
−	~~Asterisk is free and open source code to create software PBX server. See [http://www.asterisk.org] for details.~~
−	~~This package perfectly runs in side OpenVZ container. Some users run up to 60 containers with Asterisk deployed for~~
−	~~production per single hardware node. Although the easiest way to install Asterisk into container is to use pre-build package~~
−	~~from Linux distribution, occasionally one may need to have a possibility to build it from source tarball available on developer's site.~~
−
−	~~In order to do it the following remarks are worth reading:~~
−
−	~~Asterisk PBX server itself is compiled out of the shelf in CT provided that develop application template is installed for this CT.~~
−	~~The functionality of the resulting executable is enough to support simple VoIP telephony.~~
−
−	~~Unfortunately, one particular module called MeetMe (conferencing tool) will be switched off from compilation. This happens due to external dependency on 'zaptel' package.~~
−	This package provides support for some hardware cards for FXO/FXS analog telephony marketed by Digium (the company behind Asterisk), and on top of that supplies so called ztdummy kernel module. Ztdummy works like a simple metronome which is required to synchronize multiple sound streams in case of conference call. Initially this module requires 1 kHz clock which is avail for example on all Digium cards.
−
−	If you do not have this card (or equivalent from other vendors) as in case if you do not plan to use analog telephone lines, nothing is lost. You just need to play a little trick with Asterisk make system and HN ovz kernel.
−	~~First one needs to download zaptel tarball from the same location as Asterisk itself, and copy it's header zaptel.h to location~~
−	~~/usr/include/zaptel/zaptel.h in the CT where you plan to build Asterisk. This tweaks MeetMe for installation. Then you need to build~~
−	~~ztdummy.ko in HN and make it auto-loaded.~~
−
	Below is an example of how to install Asterisk into OpenVZ VE based on debian stable aka. "sarge":		Below is an example of how to install Asterisk into OpenVZ VE based on debian stable aka. "sarge":

← Older revision		Revision as of 14:25, 11 January 2008
Line 1:		Line 1:
		+	Asterisk is free and open source code to create software PBX server. See [http://www.asterisk.org] for details.
		+	This package perfectly runs in side OpenVZ container. Some users run up to 60 containers with Asterisk deployed for
		+	production per single hardware node. Although the easiest way to install Asterisk into container is to use pre-build package
		+	from Linux distribution, occasionally one may need to have a possibility to build it from source tarball available on developer's site.
		+
		+	In order to do it the following remarks are worth reading:
		+
		+	Asterisk PBX server itself is compiled out of the shelf in CT provided that develop application template is installed for this CT.
		+	The functionality of the resulting executable is enough to support simple VoIP telephony.
		+
		+	Unfortunately, one particular module called MeetMe (conferencing tool) will be switched off from compilation. This happens due to external dependency on 'zaptel' package.
		+	This package provides support for some hardware cards for FXO/FXS analog telephony marketed by Digium (the company behind Asterisk), and on top of that supplies so called ztdummy kernel module. Ztdummy works like a simple metronome which is required to synchronize multiple sound streams in case of conference call. Initially this module requires 1 kHz clock which is avail for example on all Digium cards.
		+
		+	If you do not have this card (or equivalent from other vendors) as in case if you do not plan to use analog telephone lines, nothing is lost. You just need to play a little trick with Asterisk make system and HN ovz kernel.
		+	First one needs to download zaptel tarball from the same location as Asterisk itself, and copy it's header zaptel.h to location
		+	/usr/include/zaptel/zaptel.h in the CT where you plan to build Asterisk. This tweaks MeetMe for installation. Then you need to build
		+	ztdummy.ko in HN and make it auto-loaded.
		+
	Below is an example of how to install Asterisk into OpenVZ VE based on debian stable aka. "sarge":		Below is an example of how to install Asterisk into OpenVZ VE based on debian stable aka. "sarge":

← Older revision	Revision as of 20:46, 4 August 2012
(No difference)

← Older revision	Revision as of 06:08, 3 August 2012
(No difference)

@@ Line 1: / Line 1: @@
-Below is an example of how to install Asterisk into OpenVZ VE based on debian stable aka. "sarge":
+Below is an example of how to install Asterisk into OpenVZ container based on Debian stable aka "Sarge".
 <pre>
@@ Line 7: / Line 7: @@
 </pre>
-change:
+Change:
 <pre>
 RUNASTERISK=no -> yes
@@ Line 14: / Line 14: @@
 $ /etc/init.d/asterisk start
 </pre>
-modify the config files for asterisk, and done!
+Modify the config files for asterisk, and done!
-if you need capi or/and zaptel/zaphfc:
+If you need capi or/and zaptel/zaphfc:
-* for capi: you need the /dev files on you hw-node and vps:
+* for capi: you need the /dev files on you host [[system]] and in container:
 <pre>
 crw-rw---- 1 root dialout 68, 0 Jan 3 2006 /dev/capi20
@@ Line 26: / Line 26: @@
 [...]
 </pre>
-and in your vps config add for directly access:
+''If the files doesn' exist use mknod for creating it.''
 <pre>
 DEVICES="c:68:0:rw, c:68:1:rw, c:68:2:rw"
 </pre>
 * for zaptel/zaphfc:
 <pre>
@@ Line 46: / Line 48: @@
 /* if the files doesn' exist use mknod for creating it*/
-and in your vps config
+and in your container config
 <pre>
 DEVICES="c:196:0:rw, c:196:2:rw, c:196:1:rw, c:196:253:rw,c:196:254:rw,c:196:255:rw"
 </pre>
-if need both (capi and zaphfc)
+* If need both (capi and zaphfc)
 <pre>
 DEVICES="c:68:0:rw, c:68:1:rw, c:68:2:rw c:196:0:rw, c:196:2:rw, c:196:1:rw, c:196:253:rw,c:196:254:rw,c:196:255:rw"
 </pre>
-[[category:HOWTO]]
+[[Category:HOWTO]]

← Older revision	Revision as of 11:28, 9 April 2008
(No difference)