March 2012 - h323plus - lists.packetizer.com

GNU Gatekeeper 3.0 released
by Jan Willamowius 04 May '12

04 May '12

I'm pleased to announce a new major release of the GNu Gatekeeper. Version 3.0 has many new features that will allow even your legacy endpoints to move to a new age of H.323 audio and video communications. You can download the new version at http://www.gnugk.org/h323download.html New features: - full traversal zone support (gatekeeper-to-gatekeeper H.460.18/.19) Now you can place one GnuGk behind a firewall and let it tunnel out the calls for all other devices behind the firewall eg. to a VCS or to another GnuGk. This was probably the most request feature in the past. - full IPv6 support (incl. IPv4-IPv6 proxying) With the proxy function, you can let GnuGk manage a network of IPv6 endpoints and connect them to the IPv4 network or make legacy endpoints reachable for IPv6 calls. - RTP multiplexing (all calls to and from devices supporting H.460.19 will only use 2 sockets total) - rewrite destination IPs into aliases - ENUM, SRV and RDS routing policies extended for LRQs, in case the calling gatekeeper isn't able to do this - notifications when GnuGk opens listen ports This allows you to update firewall rules on the fly, so you only have the minimum amount of ports open. - improved H.235 password authentication with neighbors - massive performance improvement when (re-)loading large numbers of GW rewrites - interop fixes for Polycom m100 and Sorenson endpoints - fixes in the underlying libraries so *BSD systems can get the latest GnuGk features - a few bug fixes We provide executables for Linux (32 and 64 bit), Windows, MacOS X, FreeBSD, OpenBSD, NetBSD and Solaris. Regards, Jan -- Jan Willamowius, Founder of the GNU Gatekeeper Project EMail : jan(a)willamowius.de Website: http://www.gnugk.org Support: http://www.willamowius.com/gnugk-support.html

1 2

Re: [h323plus] H323-SIP Gateway with H264 Support
by Simon Horne 02 May '12

02 May '12

Diego Sorry for delay in replying With Reference to the document you linked to The plugin codec exports 2 functions for capability registration unsigned int PWLibPlugin_GetAPIVersion() <http://www.voxgratia.org/docs/codec_plugins.html#PluginCodec_Definition> PluginCodec_Definition * OpalCodecPlugin_GetCodecs(unsigned * count, unsigned version) The OpalCodecPlugin_GetCodecs function returns all the information you need on the signaling side. Simply supply the codec definitions and the codec will be available in h323plus. You DO NOT need to create the Codec Methods which link to FFMPEG/x264. For only supplying the codecs you need rather than removing them for the call. Clone the Capability List then remove all the orginal and add back the ones you want. In your derived void H323Connection::OnSetLocalCapabilities() H323Capabilities * myCapabilities(localCapabilities); localCapabilities.RemoveAll(); H323Capability * cap = myCapabilities.FindCapability("H.264*"); If (cap) LocalCapabilities.Add(cap); Simon From: Diego Carvalho [mailto:diego.cdomingos2010@gmail.com] Sent: 28 March 2012 06:37 To: Simon Horne Subject: [h323plus] H323-SIP Gateway with H264 Support Hi Simon, thanks for answering again. Today I could establish SIP -> H323 audio calls. So now I only need to deal with the 2 points below. I'm really interested in being able to add H.264 in the capability set without having to link the library with FFMPEG/X264, but I couldn't understand what you explained. I searched on the internet and found this: http://www.voxgratia.org/docs/codec_plugins.html that I believe is related to what you explained but even with this page I couldn't realize what I have to do. Is it possible to configure the plugin that comes with the source in this way? I mean, use the plugin in h323plus/plugin/video/H.264 for only signaling, without have to link with FFMPEG/X264. Another question is again about the capabilities. You said that I can remove the capabilities that aren't supported by the SIP endpoint. But this way, I will have to add all possible capabilities to my gateway and them remove the ones that SIP doesn't support. It would be much easier if my gateway could start without any capabilities and then I add the ones that SIP supports. Is that possible? If not, I will have to do what you explained but when I will add all the capabilities again to be ready to handle the next call? Again, thanks for all the help. 2012/3/23 Simon Horne <s.horne(a)packetizer.com> Diego There is some issues with changes in FFMPEG v54 and a number of function names changed and others were depreciated recommend v52. I am currently working through issues with v54. Again X264 is a moving target but last I looked it compiled on Linux. On Windows is a whole different story unfortunately. If you are only using the codec for signaling there should be no need to link to either FFMPEG or X264 and you can gut the plugins and only define the PluginCodec_Definitions, Plugin_Codec_Implementation() and PLUGIN_CODEC_GET_CODEC_FN. These are the signaling parts of the codec. The Encoder/Decoder contexts can be removed. There is some changes in the CVS to also allow you to load these plugins statically see the openh323buildopt.h.in. To filter capabilities on a call by call basis you can do this by overriding H323Capabilities::OnSetLocalCapabilities() and use the localCapabilities.Remove() function to remove the capabilities not used on the SIP side. Simon From: h323plus-bounces(a)lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com] On Behalf Of Diego Carvalho Sent: 23 March 2012 22:44 To: h323plus(a)lists.packetizer.com Subject: Re: [h323plus] H323-SIP Gateway with H264 Support Hi Simon and "chr_cb". First of all, thanks for your help. Today I was able to establish an audio only call between H323 and SIP using the gateway I'm developing. This is great but I still have some problems and I appreciate any help on this: 1) Like I said, it was an audio only call. I was able to compile the plugins with the packages from Ubuntu repositories (libx264-dev, libavcodec-dev and libavutil-dev) but my project also uses ffmpeg and x264 so I would like to compile with the latest source code from git we use. The config.log shows some errors and on the internet I saw somebody saying that only a specific version of ffmpeg allows the compilation. Is that true? If so, what would be the version of ffmpeg and x264 I should use? Again, I would like to reiterate that I only want to have H264 on my capabilities list (I don't want to capture/render video). Do I indeed need the plugin? Is there another way? 2) If I set the gateway capabilities in the beginning it works but I want so set them in a later time. Specifically, I receive the call and send an invite on hold to SIP. Then it will answer with 200 OK with SDP. In this moment, when I have the SIP SDP, I want to set the gateway capabilities based on what the SIP side supports. How can I do this? If I try to add in this moment it simply doesn't add them. Thanks in advance. 2012/3/13 Simon Horne <s.horne(a)packetizer.com> Diego The plugins load default capability instances into the H323Endpoint. When the H323Connection is created these capabilities are cloned In H323Connection::OnSetLocalCapabilities() Simply remove the unmatched capabilities localCapabilities.Remove("H.264*"); The H323_ExternalRTPChannel does not handle RTP but can be used to not use the internal RTP system. You can have your own external RTP stack or not have one at all. You needed to read and populate H245_H2250LogicalChannelParameters in the send and receive message of the class with those of the SIP Client. I do have serious doubts what you are planning will work not because it can't technically work but because of the differences in H.323 and SIP with Video. H.323 is very strict on rules while SIP is very loose on interpretations. Here are the problems 1. RTP packetization H.323 says strictly single NAL SIP is undefined 2 options (Single NAL/Fragmented units) . You will get video on the H.323 side just fine but your SIP side with some devices may not be able to decode. 2. Payload Type for H.264 is specified as being flexible but a lot of SIP implementations have them fixed (usually 96 or 97) so H.323 requests 103 SIP always ends 97 no video on the H.323 side. There is no way you can fix this with signaling as SIP tells the other party what it is going to send and H.323 tells the party what it wants to receive. You have to proxy the media to fix the payload type number. Good luck. Simon ============================================================================ ============================================= From: Diego Carvalho [mailto:diego.cdomingos2010@gmail.com] Sent: 14 March 2012 06:09 To: Simon Horne Subject: Re: [h323plus] H323-SIP Gateway with H264 Support Hi Simon, thanks for answering but I still have some doubts: You said that this plugin will add the capability automatically. Actually, as I said, I'm building a H323-SIP gateway so, for instance, when the SIP endpoint is making a call I want to add the H264 capability only if the SIP endpoint offers it. Will I be able to add the capability manually? For instance, using localCapabilities.Add(new H323_H264Capability()). To sumarize, I want to be able to add (or remove if it was automatically added and the current call does not offer it) manualy the H264 capability. Also I don't know if the H323_ExternalRTPChannel applies to my situation. It's used to pass the RTP to another device. I don't want to handle the RTP at all (to be clear: I don't want RTP arriving on the gateway's network card). I want to send to h323 the RTP address/port SIP offered and vice-versa, so the RTP will flow directly between the endpoints. Any thoughts? Thanks in advance. 2012/3/13 Simon Horne <s.horne(a)packetizer.com> Diego H.264 is a video plugin in the plugin/video directory. You will need X264 and FFMPEG. For Ubuntu they are libx264-dev libavcodec-dev and libavutil-dev. You build the plugin .so and the helper (in the gpl subdirectory) and place them both in the same directory as you app. The application will load them at startup and automatically add the capability to the capabilityset etc If you don't want to use the plugin for RTP then have a look at the H323_ExternalRTPChannel. This will bypass the RTP handling in the codec to whatever you want. http://www.voxgratia.org/docs/external_rtp.html (its from 2004 but still current) Simon From: h323plus-bounces(a)lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com] On Behalf Of Diego Carvalho Sent: 14 March 2012 03:05 To: h323plus(a)lists.packetizer.com Subject: [h323plus] H323-SIP Gateway with H264 Support Hi all, I'm working on a h323-sip gateway with video (H264) support and I'm facing some problems. I'm new with H323plus and with h323 protocol itself (I'm learning as I go) so excuse me if I say something stupid. First of all, I believe that the stack can be used to build a gateway but it seems that it's more focused on terminals. Am I right? So is it possible or not to build a gateway using it? Second, there is no native support for H264. The documentation shows the class hierarchy. For audio we have, for instance, H323Cabability -> H323RealTimeCapability -> H323AudioCapability -> H323_G711Cabability but we don't have H323Cabability -> H323RealTimeCapability -> H323VideoCapability -> H323_H264Cabability. I tried to create this one, extending from H323Cabability -> H323RealTimeCapability -> H323VideoCapability -> H323GenericVideoCabability and then I discovered that I would need to override a function called CreateCodec to return a codec that handles the video. But I don't want to handle the RTP media. I just want to put H264 in the terminal capability set and establish a connection in a way that the H323 and SIP terminals can exchange the media directly. I've heard about a H264 plugin but it seems that it is for handling the media, so I don't know if it fits my purpose. How can I achieve this? Is there any plan to support H264 natively on H323plus? Also I need to get the remote RTP port. The only way I found to do this is trough H323Connection::OnStartLocicalChannel but this is called after a channel to handle the data is created and again, I don't want to handle the RTP data. I appreciate any help. Thanks.

2 7

OpenMCU Virtual Machine working out-of-the-box
by Pablo Sotomayor 01 Apr '12

01 Apr '12

I downloaded this virtual machine from the russian openmcu fork (http://openmcu.ru) and got surprised with the results. I sucessfully tested video-conference features with Ekiga and NetMeeting software clients. Can anyone test this with real endpoint cameras ? The zip file with the virtual machine is availble on this torrent. http://openmcu.ru/public/OpenMCU%5brutracker%5d.torrent Pablo

3 3

H323plus - no audio is being transmitted
by J.C Mercier 29 Mar '12

29 Mar '12

Hi Simon and all, I've noticed a recent with the latest trunk of H323plus that i'm not able to transmit any sound using the simpleplus application that comes with it. Wen i make calls to or receive calls from myphone2 or the lite version of spranto, I can hear incoming audio but the simpleplus doesn't seem to be transmitting any sound regardless of which machine i've tried on (All windows 7 / Vista). I tried debugging a little to determine the cause but so far no luck. I've also had issues compiling the code due to unresolved external errors coming from the h460p.cxx but have not really looked much into it and for it to work I had to disable H323_H460P. Your help would be greatly appreciated. Josh

2 2

Compilation problems.
by Francisco Olarte (M) 28 Mar '12

28 Mar '12

When we compile and install OpenH233 (1.24 or HEAD) with an installed version of PTLIB (2.10.1) both installed local on a user home dir we end with the following directory structure: $ ls -l ~/include total 48 drwxr-xr-x 9 gay gay 4096 Mar 26 16:55 openh323 -r--r--r-- 1 gay gay 21475 Feb 29 09:57 ptbuildopts.h drwxr-xr-x 2 gay gay 4096 Feb 29 09:57 ptclib drwxr-xr-x 3 gay gay 4096 Feb 29 09:57 ptlib -r--r--r-- 1 gay gay 4794 Feb 29 09:57 ptlib.h drwxr-xr-x 2 gay gay 4096 Mar 26 17:02 yate When we compila yate, which uses openh323, it includes openh323buildopts.h, which it finds in ~/include/openh323/openh323buildopts.h This file, in stock form, starts with: #ifndef _OPENH323_BUILDOPTS_H #define _OPENH323_BUILDOPTS_H #include <ptbuildopts.h> #include <ptlib/../../revision.h> #if PTLIB_MAJOR == 2 && PTLIB_MINOR < 10 #define PTLIB_VER ( PTLIB_MAJOR*100 + PTLIB_MINOR*10 + PTLIB_BUILD ) #else #define PTLIB_VER ( PTLIB_MAJOR*1000 + PTLIB_MINOR*10 + PTLIB_BUILD ) #endif #define PTLIB_SVN_REVISION SVN_REVISION which has two problems, the first one is the " #include <ptlib/../../revision.h> " which does not work ( it would resolve to ~/include/ptlib/../../revision.h => ~/revision.h ). It works when compiling against the uninstalled version of ptlib because it has a file ~/src/ptlib-2.10.1/revision.h ( we unpack in ~/src ). We solve the problem by zapping the offending include. The second, minor problem, is the "#define PTLIB_SVN_REVISION SVN_REVISION" which fails when zapping the include, we zap this too and it works. I think BOTH lines should be deleted, they seem like some kind of testing stuff. If we do it after installing every h323plus code we compile builds without any problem. Francisco Olarte.

2 1

Re: [h323plus] H323-SIP Gateway with H264 Support
by Diego Carvalho 26 Mar '12

26 Mar '12

Hi Simon, thanks for answering again. I'm really interested in being able to add H.264 in the capability set without having to link the library with FFMPEG/X264, but I couldn't understand what you explained. I searched on the internet and found this: http://www.voxgratia.org/docs/codec_plugins.html that I believe is related to what you explained but even with this page I couldn't realize what I have to do. Is it possible to configure the plugin that comes with the source in this way? I mean, use the plugin in h323plus/plugin/video/H.264 for only signaling, without have to link with FFMPEG/X264. Another question is again about the capabilities. You said that I can remove the capabilities that aren't supported by the SIP endpoint. But this way, I will have to add all possible capabilities to my gateway and them remove the ones that SIP doesn't support. It would be much easier if my gateway could start without any capabilities and then I add the ones that SIP supports. Is that possible? If not, I will have to do what you explained but when I will add all the capabilities again to be ready to handle the next call? Again, thanks for all the help. 2012/3/23 Simon Horne <s.horne(a)packetizer.com> > Diego**** > > ** ** > > There is some issues with changes in FFMPEG v54 and a number of function > names changed and others were depreciated recommend v52. I am currently > working through issues with v54. Again X264 is a moving target but last I > looked it compiled on Linux. On Windows is a whole different story > unfortunately.**** > > ** ** > > If you are only using the codec for signaling there should be no need to > link to either FFMPEG or X264 and you can gut the plugins and only define > the PluginCodec_Definitions, Plugin_Codec_Implementation() and > PLUGIN_CODEC_GET_CODEC_FN. These are the signaling parts of the codec. The > Encoder/Decoder contexts can be removed. There is some changes in the CVS > to also allow you to load these plugins statically see the > openh323buildopt.h.in.**** > > ** ** > > To filter capabilities on a call by call basis you can do this by > overriding H323Capabilities::OnSetLocalCapabilities() and use the > localCapabilities.Remove() function to remove the capabilities not used on > the SIP side.**** > > ** ** > > Simon**** > > ** ** > > *From:* h323plus-bounces(a)lists.packetizer.com [mailto: > h323plus-bounces(a)lists.packetizer.com] *On Behalf Of *Diego Carvalho > *Sent:* 23 March 2012 22:44 > *To:* h323plus(a)lists.packetizer.com > > *Subject:* Re: [h323plus] H323-SIP Gateway with H264 Support**** > > ** ** > > Hi Simon and "chr_cb". First of all, thanks for your help. Today I was > able to establish an audio only call between H323 and SIP using the gateway > I'm developing. This is great but I still have some problems and I > appreciate any help on this: > 1) Like I said, it was an audio only call. I was able to compile the > plugins with the packages from Ubuntu repositories (libx264-dev, > libavcodec-dev and libavutil-dev) but my project also uses ffmpeg and x264 > so I would like to compile with the latest source code from git we use. The > config.log shows some errors and on the internet I saw somebody saying that > only a specific version of ffmpeg allows the compilation. Is that true? If > so, what would be the version of ffmpeg and x264 I should use? Again, I > would like to reiterate that I only want to have H264 on my capabilities > list (I don't want to capture/render video). Do I indeed need the plugin? > Is there another way? > 2) If I set the gateway capabilities in the beginning it works but I want > so set them in a later time. Specifically, I receive the call and send an > invite on hold to SIP. Then it will answer with 200 OK with SDP. In this > moment, when I have the SIP SDP, I want to set the gateway capabilities > based on what the SIP side supports. How can I do this? If I try to add in > this moment it simply doesn't add them. > Thanks in advance.**** > > 2012/3/13 Simon Horne <s.horne(a)packetizer.com>**** > > Diego > > The plugins load default capability instances into the H323Endpoint. > When the H323Connection is created these capabilities are cloned > In H323Connection::OnSetLocalCapabilities() > Simply remove the unmatched capabilities > localCapabilities.Remove("H.264*"); > > The H323_ExternalRTPChannel does not handle RTP but can be used to not use > the internal RTP system. You can have your own external RTP stack or not > have one at all. > You needed to read and populate H245_H2250LogicalChannelParameters in the > send and receive message of the class with those of the SIP Client. > > I do have serious doubts what you are planning will work not because it > can't technically work but because of the differences in H.323 and SIP with > Video. H.323 is very strict on rules while SIP is very loose on > interpretations. > Here are the problems > 1. RTP packetization H.323 says strictly single NAL SIP is undefined 2 > options (Single NAL/Fragmented units) . You will get video on the H.323 > side > just fine but your SIP side with some devices may not be able to decode. > 2. Payload Type for H.264 is specified as being flexible but a lot of SIP > implementations have them fixed (usually 96 or 97) so H.323 requests 103 > SIP always ends 97 no video on the H.323 side. There is no way you can fix > this with signaling as SIP tells the other party what it is going to send > and H.323 tells the party what it wants to receive. You have to proxy the > media to fix the payload type number. > > Good luck. > > Simon > > > ============================================================================ > ============================================= > > From: Diego Carvalho [mailto:diego.cdomingos2010@gmail.com] > Sent: 14 March 2012 06:09 > To: Simon Horne > Subject: Re: [h323plus] H323-SIP Gateway with H264 Support**** > > > Hi Simon, thanks for answering but I still have some doubts: > You said that this plugin will add the capability automatically. Actually, > as I said, I'm building a H323-SIP gateway so, for instance, when the SIP > endpoint is making a call I want to add the H264 capability only if the SIP > endpoint offers it. Will I be able to add the capability manually? For > instance, using localCapabilities.Add(new H323_H264Capability()). To > sumarize, I want to be able to add (or remove if it was automatically added > and the current call does not offer it) manualy the H264 capability. > Also I don't know if the H323_ExternalRTPChannel applies to my situation. > It's used to pass the RTP to another device. I don't want to handle the RTP > at all (to be clear: I don't want RTP arriving on the gateway's network > card). I want to send to h323 the RTP address/port SIP offered and > vice-versa, so the RTP will flow directly between the endpoints. Any > thoughts? Thanks in advance. > 2012/3/13 Simon Horne <s.horne(a)packetizer.com> > Diego > > H.264 is a video plugin in the plugin/video directory. You will need X264 > and FFMPEG. For Ubuntu they are libx264-dev libavcodec-dev and > libavutil-dev. > > You build the plugin .so and the helper (in the gpl subdirectory) and place > them both in the same directory as you app. The application will load them > at startup and automatically add the capability to the capabilityset etc > > If you don’t want to use the plugin for RTP then have a look at the > H323_ExternalRTPChannel. This will bypass the RTP handling in the codec to > whatever you want. > http://www.voxgratia.org/docs/external_rtp.html > (its from 2004 but still current) > > Simon > > > From: h323plus-bounces(a)lists.packetizer.com > [mailto:h323plus-bounces@lists.packetizer.com] On Behalf Of Diego Carvalho > Sent: 14 March 2012 03:05 > To: h323plus(a)lists.packetizer.com > Subject: [h323plus] H323-SIP Gateway with H264 Support > > Hi all, > I'm working on a h323-sip gateway with video (H264) support and I'm facing > some problems. I'm new with H323plus and with h323 protocol itself (I'm > learning as I go) so excuse me if I say something stupid. > First of all, I believe that the stack can be used to build a gateway but > it > seems that it's more focused on terminals. Am I right? So is it possible or > not to build a gateway using it? > Second, there is no native support for H264. The documentation shows the > class hierarchy. For audio we have, for instance, H323Cabability -> > H323RealTimeCapability -> H323AudioCapability -> H323_G711Cabability but we > don't have H323Cabability -> H323RealTimeCapability -> H323VideoCapability > -> H323_H264Cabability. I tried to create this one, extending from > H323Cabability -> H323RealTimeCapability -> H323VideoCapability -> > H323GenericVideoCabability and then I discovered that I would need to > override a function called CreateCodec to return a codec that handles the > video. But I don't want to handle the RTP media. I just want to put H264 in > the terminal capability set and establish a connection in a way that the > H323 and SIP terminals can exchange the media directly. I've heard about a > H264 plugin but it seems that it is for handling the media, so I don't know > if it fits my purpose. How can I achieve this? Is there any plan to support > H264 natively on H323plus? Also I need to get the remote RTP port. The only > way I found to do this is trough H323Connection::OnStartLocicalChannel but > this is called after a channel to handle the data is created and again, I > don't want to handle the RTP data. I appreciate any help. Thanks. > > **** > > ** ** >

1 0

Re: [h323plus] H323-SIP Gateway with H264 Support
by Simon Horne 23 Mar '12

23 Mar '12

Diego The plugins load default capability instances into the H323Endpoint. When the H323Connection is created these capabilities are cloned In H323Connection::OnSetLocalCapabilities() Simply remove the unmatched capabilities localCapabilities.Remove("H.264*"); The H323_ExternalRTPChannel does not handle RTP but can be used to not use the internal RTP system. You can have your own external RTP stack or not have one at all. You needed to read and populate H245_H2250LogicalChannelParameters in the send and receive message of the class with those of the SIP Client. I do have serious doubts what you are planning will work not because it can't technically work but because of the differences in H.323 and SIP with Video. H.323 is very strict on rules while SIP is very loose on interpretations. Here are the problems 1. RTP packetization H.323 says strictly single NAL SIP is undefined 2 options (Single NAL/Fragmented units) . You will get video on the H.323 side just fine but your SIP side with some devices may not be able to decode. 2. Payload Type for H.264 is specified as being flexible but a lot of SIP implementations have them fixed (usually 96 or 97) so H.323 requests 103 SIP always ends 97 no video on the H.323 side. There is no way you can fix this with signaling as SIP tells the other party what it is going to send and H.323 tells the party what it wants to receive. You have to proxy the media to fix the payload type number. Good luck. Simon ============================================================================ ============================================= From: Diego Carvalho [mailto:diego.cdomingos2010@gmail.com] Sent: 14 March 2012 06:09 To: Simon Horne Subject: Re: [h323plus] H323-SIP Gateway with H264 Support Hi Simon, thanks for answering but I still have some doubts: You said that this plugin will add the capability automatically. Actually, as I said, I'm building a H323-SIP gateway so, for instance, when the SIP endpoint is making a call I want to add the H264 capability only if the SIP endpoint offers it. Will I be able to add the capability manually? For instance, using localCapabilities.Add(new H323_H264Capability()). To sumarize, I want to be able to add (or remove if it was automatically added and the current call does not offer it) manualy the H264 capability. Also I don't know if the H323_ExternalRTPChannel applies to my situation. It's used to pass the RTP to another device. I don't want to handle the RTP at all (to be clear: I don't want RTP arriving on the gateway's network card). I want to send to h323 the RTP address/port SIP offered and vice-versa, so the RTP will flow directly between the endpoints. Any thoughts? Thanks in advance. 2012/3/13 Simon Horne <s.horne(a)packetizer.com> Diego H.264 is a video plugin in the plugin/video directory. You will need X264 and FFMPEG. For Ubuntu they are libx264-dev libavcodec-dev and libavutil-dev. You build the plugin .so and the helper (in the gpl subdirectory) and place them both in the same directory as you app. The application will load them at startup and automatically add the capability to the capabilityset etc If you dont want to use the plugin for RTP then have a look at the H323_ExternalRTPChannel. This will bypass the RTP handling in the codec to whatever you want. http://www.voxgratia.org/docs/external_rtp.html (its from 2004 but still current) Simon From: h323plus-bounces(a)lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com] On Behalf Of Diego Carvalho Sent: 14 March 2012 03:05 To: h323plus(a)lists.packetizer.com Subject: [h323plus] H323-SIP Gateway with H264 Support Hi all, I'm working on a h323-sip gateway with video (H264) support and I'm facing some problems. I'm new with H323plus and with h323 protocol itself (I'm learning as I go) so excuse me if I say something stupid. First of all, I believe that the stack can be used to build a gateway but it seems that it's more focused on terminals. Am I right? So is it possible or not to build a gateway using it? Second, there is no native support for H264. The documentation shows the class hierarchy. For audio we have, for instance, H323Cabability -> H323RealTimeCapability -> H323AudioCapability -> H323_G711Cabability but we don't have H323Cabability -> H323RealTimeCapability -> H323VideoCapability -> H323_H264Cabability. I tried to create this one, extending from H323Cabability -> H323RealTimeCapability -> H323VideoCapability -> H323GenericVideoCabability and then I discovered that I would need to override a function called CreateCodec to return a codec that handles the video. But I don't want to handle the RTP media. I just want to put H264 in the terminal capability set and establish a connection in a way that the H323 and SIP terminals can exchange the media directly. I've heard about a H264 plugin but it seems that it is for handling the media, so I don't know if it fits my purpose. How can I achieve this? Is there any plan to support H264 natively on H323plus? Also I need to get the remote RTP port. The only way I found to do this is trough H323Connection::OnStartLocicalChannel but this is called after a channel to handle the data is created and again, I don't want to handle the RTP data. I appreciate any help. Thanks.

2 1

Compile H264
by Talita Ferraz Roberti 15 Mar '12

15 Mar '12

Hi all, I'm new on h323plus. First of all I need to compile H323plus with the H264 plugin. I searched a document or any tutorial on how to do it, but didn't find any. Can anyone help me, please? Is there any documentation on how to compile H323 in general? Thank you! Talita

2 1

H323-SIP Gateway with H264 Support
by Diego Carvalho 14 Mar '12

14 Mar '12

Hi all, I'm working on a h323-sip gateway with video (H264) support and I'm facing some problems. I'm new with H323plus and with h323 protocol itself (I'm learning as I go) so excuse me if I say something stupid. First of all, I believe that the stack can be used to build a gateway but it seems that it's more focused on terminals. Am I right? So is it possible or not to build a gateway using it? Second, there is no native support for H264. The documentation shows the class hierarchy. For audio we have, for instance, H323Cabability -> H323RealTimeCapability -> H323AudioCapability -> H323_G711Cabability but we don't have H323Cabability -> H323RealTimeCapability -> H323VideoCapability -> H323_H264Cabability. I tried to create this one, extending from H323Cabability -> H323RealTimeCapability -> H323VideoCapability -> H323GenericVideoCabability and then I discovered that I would need to override a function called CreateCodec to return a codec that handles the video. But I don't want to handle the RTP media. I just want to put H264 in the terminal capability set and establish a connection in a way that the H323 and SIP terminals can exchange the media directly. I've heard about a H264 plugin but it seems that it is for handling the media, so I don't know if it fits my purpose. How can I achieve this? Is there any plan to support H264 natively on H323plus? Also I need to get the remote RTP port. The only way I found to do this is trough H323Connection::OnStartLocicalChannel but this is called after a channel to handle the data is created and again, I don't want to handle the RTP data. I appreciate any help. Thanks.

3 3

NAT /Firewall Document
by Simon Horne 12 Mar '12

12 Mar '12

Guys Apologies for cross posting Over the last couple of months Jan and I have been committing a lot of H.460 NAT support into H323plus and GnuGk . H.460.18/.19, Multiplexing, Traversal Zones and H.460.23/.24/.24A/.24B and just recently H.460.17. I have written with Jan's assistance an ordinary person guide to NAT, the types of NAT and the logic behind H.323 NAT Traversal solutions. It briefly explains exactly what all these standards mean and how they fit together to provide a complete NAT Traversal solution. h323_nat_fw_solution.pdf <http://hive.packetizer.com/users/h323forum/specifications/h323_nat_fw_solut ion.pdf> Simon

1 0