Difference between revisions of "Configuration of Trixbox 1.2.3"

Latest revision as of 17:23, 8 March 2007

We followed mostly the instructions from these two forums on the Trixbox site:

There are more forums where people say things about h323 but these seem to be the most helpful.

Following the suggestions we used Trixbox 1.2.3 with asterisk-addons-1.2.3. In order to do this we deleted the current addons:

rpm -qa | grep asterisk-addons
rpm -e asterisk-addons-1.2.4_1.2.12.1-1.294

And loaded the older addons: these can be found here

rpm -i asterisk-addons-1.2.3-1.219.i386.rpm

If this is really necessary we can't tell right now. Once you get everything working it might be worth trying it without these add-ons.

Whenever you edit anyting in the .conf files makes sure to afterwards do

amportal stop
amportal start

at you asterisk prompt. If you then do

asterisk -vvvvr

you get an CLI and here you can type

ooh323 debug
sip debug
exit

to initiate the debugger

Only ooh323.conf needs manual configuration:

@@ Line 10: / Line 10: @@
   rpm -e asterisk-addons-1.2.4_1.2.12.1-1.294
-And loaded the older addons: (these can be found ...............)
+And loaded the older addons:
+these can be found [http://thales.td-er.nl/EtherealDumps/asterisk-addons-1.2.3-1.219.i386.rpm here]
   rpm -i asterisk-addons-1.2.3-1.219.i386.rpm
 If this is really necessary we can't tell right now. Once you get everything working it might be worth trying it without these add-ons.
+Whenever you edit anyting in the .conf files makes sure to afterwards do
+ amportal stop
+ amportal start
+at you asterisk prompt. If you then do
+ asterisk -vvvvr
+you get an CLI and here you can type
+ ooh323 debug
+ sip debug
+ exit
+to initiate the debugger
+Only ooh323.conf needs manual configuration:
 [[ooh323.conf]]
 [[Adding H323 extensions]]