Child pages
  • Software SIP - H.323 gateway
Skip to end of metadata
Go to start of metadata

A short foreword:

Many installed PBX’s are capable of H.323, but it will be difficult to upgrade them to understand SIP. So a challenge to interconnect sipx with existing PBX via H.323 protocol appears. Below is an example implementation via freeswitch/mod_h323.

The principal idea (Thanks Josh) of how to do it documented here:

The goal:

The goal is to make the following scheme to work.

sipX  =====sip=====  FS  =====h323=====  PBX


  1. Compile FS with mod_h323 on the sipx server.
  2. Create separate FS sofia profile and dial plan.
  3. Configure sipx dialplan.

Step 1. Compile FS with mod_h323.

The main idea of recompiling FS on the sipx server is documented here:

The difference is that before actually compiling FS with mod_h323 one should compile prerequisite libraries (ptlib, and h323plus). It is documented here:

So the whole sequence will be:

  • In FS source directory edit file modules.conf and uncomment endpoints/mod_h323 line
  • Configure FS with different prefix like this:
    ./configure \--prefix=/usr/local/freeswitch_custom
  • Run make, verify that mod_h323 is compiled.
  • Run make install to install FS into configured “prefix” directory.
  • Edit file /usr/bin/ so that sipx startup scripts will start this newly compiled FS.
  • /usr/local/freeswitch should be changed to /usr/local/freeswitch_custom on lines 47, 118, 120:
    47: {{FS_EXEC="/usr/local/freeswitch_custom/bin/freeswitch \}}
    118: {{if \[WikiWelcome: \! \-x /usr/local/freeswitch_custom/bin/freeswitch \]}}
    120: {{echo "Error: FreeSWITCH executable is not at /usr/local/freeswitch_custom/bin/freeswitch" >&2}}
  • Backup original /usr/bin/ file with different name, you’ll be able to return to default FS instance at any time.

Now you should be able to stop old and then start new FS instance by

  • No labels