H323 configuration

From TD-er's Wiki
Jump to: navigation, search

First of all, we need to open a shell on a standard TrixBox installation. In order to check the status of all the managed connections, first increase Asterisk's verbose output by executing

[root@asterisk1 ~]# asterisk -vvvr

The Asterisk daemon on the TrixBox will show some output like

Asterisk comes with ABSOLUTELY NO WARRANTY; type 'show warranty' for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type 'show license' for details.
=========================================================================
Connected to Asterisk 1.2.13 svn rev 47264 currently running on asterisk1 (pid = 2347)
Verbosity was 1 and is now 3
asterisk1*CLI>

the last line shows a command prompt; this is Asterisk's own CLI. Now we can execute

show channeltypes

And Asterisk will generate a response like

Type        Description                    Devicestate  Indications  Transfer    
----------  -----------                    -----------  -----------  --------    
OOH323      Objective Systems H323 Channel no           yes          no          
MGCP        Media Gateway Control Protocol no           yes          no          
Zap         Zapata Telephony Driver w/PRI  no           yes          no          
Agent       Call Agent Proxy Channel       yes          yes          no          
Local       Local Proxy Channel Driver     no           yes          no          
Skinny      Skinny Client Control Protocol no           yes          no          
SIP         Session Initiation Protocol (S yes          yes          yes         
Feature     Feature Proxy Channel Driver   no           yes          no          
IAX2        Inter Asterisk eXchange Driver yes          yes          yes         
Phone       Standard Linux Telephony API D no           no           no

This is an overview of the channels Asterisk listens to.

So far this does not seem to work; the used system is trixbox 2.0. After looking at the TrixBox support fora, it is clear that the trixBox project has no big experience with the h323 protocol; in general TrixBox relies on the OpenH323 project for the h323 protocol stack implementation. This implementation is known to work only for some peculiar combinantions of packages for Asterisk and it's addons (see Trixbox v2 ooH323 broken?)


ooh323 debug

Debugger outputs

examples of config files found on the net