Asterisk from source - Revision history

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

2012-08-04T20:46:05Z

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

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

2012-08-03T06:08:54Z

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

Jholladay at 19:16, 22 January 2009

2009-01-22T19:16:18Z

Bbhenry at 01:57, 18 December 2008

2008-12-18T01:57:41Z

Bbhenry at 01:56, 18 December 2008

2008-12-18T01:56:59Z

Eongaro: added debian dependencies

2008-10-16T22:43:17Z

added debian dependencies

Kir: terms used are linked to; fixed english; fixed external links; fixed cd command

2008-01-15T11:41:06Z

terms used are linked to; fixed english; fixed external links; fixed cd command

Finist: Asterisk tuning moved to Asterisk from source: obvious

2008-01-14T12:18:33Z

Asterisk tuning moved to Asterisk from source: obvious

Kirshil at 12:15, 14 January 2008

2008-01-14T12:15:04Z

Kirshil at 12:00, 14 January 2008

2008-01-14T12:00:06Z

@@ Line 42: / Line 42: @@
 modprobe ztdummy
 vzctl set 240 --devnodes zap/pseudo:rw --save
 </pre>
 [[Category:HOWTO]]

@@ Line 29: / Line 29: @@
 Since Digium is retiring Zaptel with the use of Dahdi, the header you will use to build meetme module to work with Dahdi is called user.h. Just copy this file to /usr/include/dahdi/user.h in CT then build your Asterisk , you should get the MeetMe working.
-==TTY Problem==
+===TTY Problem===
 After I have installed asterisk, the service wouldn't start and give me the following error:
- Starting asterisk: Cannot find your TTY
+Starting asterisk: Cannot find your TTY
 The solution is to edit /usr/sbin/safe_asterisk , comment out the TTY=  line. I found my at the very top of the file, about the 5th line. Now I am able to start, stop, restart the asterisk service all I want.

← Older revision		Revision as of 01:56, 18 December 2008
Line 26:		Line 26:

	If you do not plan to use analog telephone lines, hence don't like in install the hardware, nothing is lost provided you run your HN with 2.6.XX kernel. You just need to play a little trick with Asterisk make system: 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 CT where you plan to build Asterisk. This tweaks MeetMe for installation.		If you do not plan to use analog telephone lines, hence don't like in install the hardware, nothing is lost provided you run your HN with 2.6.XX kernel. You just need to play a little trick with Asterisk make system: 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 CT where you plan to build Asterisk. This tweaks MeetMe for installation.
		+
		+	Since Digium is retiring Zaptel with the use of Dahdi, the header you will use to build meetme module to work with Dahdi is called user.h. Just copy this file to /usr/include/dahdi/user.h in CT then build your Asterisk , you should get the MeetMe working.
		+
		+	==TTY Problem==
		+
		+	After I have installed asterisk, the service wouldn't start and give me the following error:
		+
		+	Starting asterisk: Cannot find your TTY
		+
		+	The solution is to edit /usr/sbin/safe_asterisk , comment out the TTY= line. I found my at the very top of the file, about the 5th line. Now I am able to start, stop, restart the asterisk service all I want.

	== HN configuration ==		== HN configuration ==

@@ Line 6: / Line 6: @@
 == Building Asterisk in a [[CT]] ==
 Asterisk PBX server itself is compiled out of the shelf in a [[container]] provided that development tools are installed. The functionality of the resulting executable is enough to support simple VoIP telephony.
+=== Debian Dependencies ===
 <pre>
 wget http://downloads.digium.com/pub/asterisk/releases/asterisk-x.x.xx.tar.gz
@@ Line 20: / Line 22: @@
 To configure Asterisk itself see, for example, http://downloads.oreilly.com/books/9780596510480.pdf.
-== MeetMe problem ==
+=== MeetMe problem ===
 Unfortunately, one particular module called MeetMe (conferencing tool) will be switched off from compilation. This happens due to external dependency on 'zaptel' package. Zaptel 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 <code>ztdummy</code> kernel module. Ztdummy works like a simple metronome which is required to synchronize multiple sound streams in case of conference call.

@@ Line 1: / Line 1: @@
 ==General==
-Asterisk is free and open source code to create software PBX server. See [http://www.asterisk.org] for details. This package perfectly runs inside 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.
+Asterisk is free and open source code to create software PBX server. See http://www.asterisk.org/ for details. The package runs perfectly  inside an 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 a 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:
+In order to do so the following remarks are worth reading.
-==Building Asterisk in CT==
+== Building Asterisk in a [[CT]] ==
-Asterisk PBX server itself is compiled out of the shelf in CT provided that develop application template is installed on this CT. The functionality of the resulting executable is enough to support simple VoIP telephony.
+Asterisk PBX server itself is compiled out of the shelf in a [[container]] provided that development tools are installed. The functionality of the resulting executable is enough to support simple VoIP telephony.
 <pre>
 wget http://downloads.digium.com/pub/asterisk/releases/asterisk-x.x.xx.tar.gz
 tar xzf asterisk-x.x.xx.tar.gz
-cd asterisk-x.x.xx.tar.gz
+cd asterisk-x.x.xx
 ./configure
 make
@@ Line 18: / Line 18: @@
 The last command is not needed in case you have your own configuration as it installs some sample configuration files.
-To configure Asterisk itself see for example [http://www.digium.com/elqNow/elqRedir.htm?ref=http://downloads.oreilly.com/books/9780596510480.pdf].
+To configure Asterisk itself see, for example, http://downloads.oreilly.com/books/9780596510480.pdf.
-==MeetMe problem==
+== MeetMe problem ==
-Unfortunately, one particular module called MeetMe (conferencing tool) will be switched off from compilation. This happens due to external dependency on 'zaptel' package. Zaptel 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.
+Unfortunately, one particular module called MeetMe (conferencing tool) will be switched off from compilation. This happens due to external dependency on 'zaptel' package. Zaptel 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 <code>ztdummy</code> kernel module. Ztdummy works like a simple metronome which is required to synchronize multiple sound streams in case of conference call.
 If you do not plan to use analog telephone lines, hence don't like in install the hardware, nothing is lost provided you run your HN with 2.6.XX kernel. You just need to play a little trick with Asterisk make system: 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 CT where you plan to build Asterisk. This tweaks MeetMe for installation.
-==HN configuration==
+== HN configuration ==
-Finally you need to make sure that on HN ztdummy kernel module is loaded and the access to /dev/zap/pseudo device file is granted to
+Finally you need to make sure that on [[HN]] ztdummy kernel module is loaded and the access to <code>/dev/zap/pseudo</code> device file is granted to the container:
 <pre>
 modprobe ztdummy

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

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

← Older revision	Revision as of 12:18, 14 January 2008
(No difference)

← Older revision		Revision as of 12:15, 14 January 2008
Line 18:		Line 18:

	The last command is not needed in case you have your own configuration as it installs some sample configuration files.		The last command is not needed in case you have your own configuration as it installs some sample configuration files.
		+	To configure Asterisk itself see for example [http://www.digium.com/elqNow/elqRedir.htm?ref=http://downloads.oreilly.com/books/9780596510480.pdf].

	==MeetMe problem==		==MeetMe problem==