Difference between revisions of "Assignment 2: H323 (by Fabio & Anneke)"

From TD-er's Wiki
Jump to navigationJump to search
m
 
(66 intermediate revisions by 4 users not shown)
Line 1: Line 1:
We use '''gnomemeeting''' softphones and a '''gnugk''' gatekeeper.
+
<big>'''2.1 H323'''</big>
=== Configuration of Gnomemeeting ===
 
'''Edit -> Preferences'''
 
  
* General: You can fill in your personal data and leave everything default
+
'''[[H323 analysis]]'''
* H323 Settings: Gatekeeper:
 
  
Registering method: Gatekeeper host
+
'''[[Our Architecture]]'''
Gatekeeper host: 129.125.71.173:1719
 
Gatekeeper alias: 601
 
 
''Gatekeeper host'' is the IP address and port of the gatekeeper. Port 1720 is the standard h323 port but in our case the h323 client was on the same computer so the 1720 port was already occupied.
 
  
''Gatekeeper alias'' is the primary alias with the gatekeeper, also the extension number in Asterisk to keep things simple.
+
'''[[HOWTO SET UP TRIXBOX AS H323 GATEWAY]]'''
  
Tick the "Register this alias as the primary alias with the gatekeeper" box and Apply (sorry, this is of course after you've installed the gk) :).
+
<big>'''2.2 Connection to regular telephone network'''</big>
* H323 Settings: Gateway - Do not use a gateway
+
* [[VoIPBuster]]
* Codecs: Audio Codecs - We enabled all available codecs.
+
* [[ZapTel]]
* Codecs: Video Codecs - We have not been able to spend time on this
+
<big>'''2.3 Configuring videoconferencing'''</big>
* Devices:
+
* [[Videoswitch support for MeetMe]]
** Audio Devices:
+
* [[app_conference]]
*** Audio Plugin ALSA
+
<big>'''2.4 Intercom'''</big>
*** Output device: Intel ICH5
 
*** Input device: Intel ICH5
 
**'''Detect Devices'''
 
  
(All the audio and video devices settings are of course depending on your local system, this is more for our own reference) :)
+
<big>'''2.5 Updating to newer versions of Trixbox'''</big>
 
+
* [[Regarding H323]]
=== GnuGk Gatekeeper ===
 
Packages for this gatekeeper are not available for CentOS. We found out that this gatekeeper was already installed in Etch. (System administration provided us with two machines with etch so we could get the sound working).
 
 
 
Almost no configuring here. Just enable PROXY.
 
 
 
We are still playing with the gatekeeper so this section is under construction.
 
 
 
=== Configuration of Trixbox 1.2.3 ===
 
 
 
We followed mostly the instructions from these two forums on the [http://www.trixbox.org/ Trixbox] site:
 
* [http://www.trixbox.org/modules/newbb/viewtopic.php?viewmode=flat&order=ASC&topic_id=2865&forum=6 here is the working configuration & tips for oh323]
 
* [http://www.trixbox.org/modules/newbb/viewtopic.php?topic_id=3228&forum=2#forumpost41741 H323, SIP and Gatekeeper]
 
 
 
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 ...............)
 
 
 
rpm -i asterisk-addons-1.2.3-1.219.i386.rpm
 
 
 
If this is really necessary we can't tell right now. We got things working when changing other things as well so later on we can try if it still works without this step.
 
 
 
Next thing was to edit the ooh323.conf file. This file needs to be copied from the samples first:
 
cp /etc/asterisk-1.2.8-samples/ooh323.conf /etc/asterisk
 
 
 
Here is our ooh323.conf:
 
 
 
 
 
 
 
amportal stop
 
amportal start
 
 
 
then it works perfect.
 

Latest revision as of 16:55, 16 March 2007

2.1 H323

H323 analysis

Our Architecture

HOWTO SET UP TRIXBOX AS H323 GATEWAY

2.2 Connection to regular telephone network

2.3 Configuring videoconferencing

2.4 Intercom

2.5 Updating to newer versions of Trixbox