Trixbox - Revision history

Gijs: /* Things to know */

2007-03-06T11:16:54Z

Things to know

Gijs at 11:16, 6 March 2007

2007-03-06T11:16:21Z

Gijs at 11:15, 6 March 2007

2007-03-06T11:15:41Z

Gijs at 19:49, 20 February 2007

2007-02-20T19:49:29Z

Anneke: /* Editors */

2007-02-09T13:38:24Z

Editors

Anneke: /* Editors */

2007-02-09T13:37:34Z

Editors

Anneke: /* Things to know */

2007-02-09T13:35:34Z

Things to know

129.125.21.174: /* NAT - Update (29/01/2007) */

2007-01-30T11:55:55Z

NAT - Update (29/01/2007)

Fabio: /* Update (29/01/2007) */

2007-01-29T15:53:41Z

Update (29/01/2007)

Fabio: /* Network Bridging */

2007-01-29T15:53:24Z

Network Bridging

← Older revision		Revision as of 11:16, 6 March 2007
Line 21:		Line 21:

	=== Things to know ===		=== Things to know ===
−
−	~~* document the startup of VMware *~~

	Once the Trixbox Linux is up and running, the following things hold:		Once the Trixbox Linux is up and running, the following things hold:

@@ Line 5: / Line 5: @@
 ==The Limitations of TrixBox==
 ([http://www.packtpub.com/trixbox/book Source, sample chapters, p.34])
 Die-hard Asterisk purists will insist that by using TrixBox we are seriously crippling the abilities of the system. The reality is that we can do almost anything with a TrixBox installation just as we can with a bare Asterisk installation. The main limitation we have is that FreePBX requires a specific layout of configuration files, and any hand editing could be overwritten or could break the FreePBX interface.
 TrixBox also locks us down to one machine. When it comes to having multiple machines handling our telephony, it can be difficult to migrate from TrixBox to multiple Asterisk boxes as the TrixBox interface only allows for single machine architecture. This can be manageable as long as the administrators configuring the telephone system are aware of the need to log in to multiple interfaces in order to make changes. As the telephony infrastructure and required capacity grows, it can become quite difficult to manage. It's worth considering moving directly to multiple Asterisk systems rather than trying to run concurrent TrixBox systems.
 Basically, as our needs grow towards those of a large business TrixBox becomes less useful to us. However, for small and medium businesses it can perform well and meet most needs, from small shops to busy call centres.

← Older revision		Revision as of 11:15, 6 March 2007
Line 2:		Line 2:

	[[Links#Trixbox_links\|Trixbox related links]]		[[Links#Trixbox_links\|Trixbox related links]]
		+
		+	==The Limitations of TrixBox==
		+	([http://www.packtpub.com/trixbox/book Source, sample chapters, p.34])
		+	Die-hard Asterisk purists will insist that by using TrixBox we are seriously crippling the abilities of the system. The reality is that we can do almost anything with a TrixBox installation just as we can with a bare Asterisk installation. The main limitation we have is that FreePBX requires a specific layout of configuration files, and any hand editing could be overwritten or could break the FreePBX interface.
		+	TrixBox also locks us down to one machine. When it comes to having multiple machines handling our telephony, it can be difficult to migrate from TrixBox to multiple Asterisk boxes as the TrixBox interface only allows for single machine architecture. This can be manageable as long as the administrators configuring the telephone system are aware of the need to log in to multiple interfaces in order to make changes. As the telephony infrastructure and required capacity grows, it can become quite difficult to manage. It's worth considering moving directly to multiple Asterisk systems rather than trying to run concurrent TrixBox systems.
		+	Basically, as our needs grow towards those of a large business TrixBox becomes less useful to us. However, for small and medium businesses it can perform well and meet most needs, from small shops to busy call centres.

	== Running Trixbox in VMware on Windows ==		== Running Trixbox in VMware on Windows ==

← Older revision		Revision as of 19:49, 20 February 2007
Line 1:		Line 1:
	[http://www.trixbox.org/ Tribox homepage]		[http://www.trixbox.org/ Tribox homepage]

		+	[[Links#Trixbox_links\|Trixbox related links]]

	== Running Trixbox in VMware on Windows ==		== Running Trixbox in VMware on Windows ==

@@ Line 31: / Line 31: @@
 These can be edited through the GUI (in administrator mode) under '''Asterisk -> ConfigEdit'''.
 Editing those files with the installed editor vi, is rather tedious. Therefore we installed Emacs to do the editing.
 Since Trixbox is based on CentOS, it is possible to use the CentOS RPM's to install Emacs.

← Older revision		Revision as of 13:37, 9 February 2007
Line 28:		Line 28:

	The config files of Asterisk are located in /etc/asterisk/		The config files of Asterisk are located in /etc/asterisk/
		+
		+	These can be edited through the GUI (in administrator mode) under '''Asterisk -> ConfigEdit'''.

	Editing those files with the installed editor vi, is rather tedious. Therefore we installed Emacs to do the editing.		Editing those files with the installed editor vi, is rather tedious. Therefore we installed Emacs to do the editing.

@@ Line 22: / Line 22: @@
 * Each instance of VMware player running this version of Trixbox will take on average about 250 MB of RAM.
 * Each VMware image of this version of Trixbox needs about 1.66 GiB of hard disk space. This can increase up to a max. of 7.3 GiB (max size of virtual filesystem + 256 MiB VMEM-file) The VMware-images can be compressed for transport to about 570 - 600 MB
+* The GUI can be used to configure TrixBox. Remember to enable the necessary modules (at least '''core'''). This can be done through '''FreePBX -> Tools -> Module Administration'''.
+* Extensions can now be added under '''FreePBX -> Setup'''
 === Editors ===

@@ Line 243: / Line 243: @@
 In this case the virtual machine has the ip 192.168.5.128 and a series op network port are mapped to it; unfortunately it doesn't seem to work:
 * from the outside world it is not possible to open any connection towards the TrixBox, i.e. not by usig the real machine's ip and port 8888 nor using the "VMware router" at adress 192.168.5.2 and port 8888
-* from the local Linux OS it is possible to connect to the TrixBox through it's ip; this is not sufficient as it's not possible to connect from ''another'' machine.
+* from the local Linux OS it is possible to connect to the TrixBox through its ip; this is not sufficient as it's not possible to connect from ''another'' machine.
 === Network Bridging ===

@@ Line 139: / Line 139: @@
 As far as we know, such NAT configuration does '''not''' ''forward'' any connection to the TrixBox running within VMware, therefore at this moment this solution doesn't allow any incoming connection.
-=== Update (29/01/2007) ===
+=== NAT - Update (29/01/2007) ===
 Further investigation made us discover a quite complex situation.