April 2012 - h323plus - lists.packetizer.com

does H323Plus support H,239? Thanks!
by Bo Xu 13 Jun '12

13 Jun '12

Hello, could you tell me id H323Plus support H,239? Thanks! Regards, Bo

2 5

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

H323plus Problem Reg G722 plugin loading.
by Ashwani Kumar 12 Apr '12

12 Apr '12

Hi All, I am not able to see G722 support in H323plus, When I am using simph323 application. I have also copied all the " *g7221_audio_pwplugin.so g7222_audio_pwplugin.so g722_audio_pwplugin.so* to the simph323 dir. I am only able to see *G.722.1-24k{sw} <3> G.722.1-32k{sw} <4>* support in Codec table. Below is the few line of log; Codecs (in preference order): Table: G.711-uLaw-64k <2> G.711-ALaw-64k <1> G.722.1-24k{sw} <3> G.722.1-32k{sw} <4> H.264-720{sw} <5> H.264-CIF{sw} <6> H.239(H.264{sw} <1>) <7> H.239 Control <8> Please find pointers to solve the problem. -- Regards. *Ashwani*

1 1

H323plus support for UDP signalling
by J.C Mercier 12 Apr '12

12 Apr '12

Hi all, Just curious, does H323plus support signalling via UDP? If not, what are the advantages of using TCP signalling over UDP, aside from it being reliable (considering UDP packets doesn't exceed the UDP size limit for each message sent, if it's even possible with H323 messages) ? Another question, is it possible to include generic messages within the signalling messages (setup, process, alert, connect, facility etc) just as we can with the h.245 OLC messages? Thanks in advance for your help and suggestions. Josh C. M

3 3

Does H323Plus support Intra-frame Request?
by Ashwani Kumar 11 Apr '12

11 Apr '12

Hi Simon, Does H323Plus signaling support Intra-frame Request for Video? -- Regards. *Ashwani Kumar *

1 0

Re: [h323plus] H323plus problem : Use of non IP transport address: " "
by Ashwani Kumar 09 Apr '12

09 Apr '12

On Mon, Apr 9, 2012 at 3:27 PM, Ashwani Kumar <ash1412(a)gmail.com> wrote: > I tried to set local address (IP & port number) > > external.SetExternalAddress(H323TransportAddress(addr, port), > H323TransportAddress(addr, port+1)); > > but problem remain same. > > > > On Sat, Apr 7, 2012 at 6:35 PM, Ashwani Kumar <ash1412(a)gmail.com> wrote: > >> Hi Simon, >> >> I have implemented the code to read remote parameters as given in >> h323con.h +1517 >> >> >> >> * H323Channel * MyConnection::CreateRealTimeLogicalChannel( >> const H323Capability & capability, >> H323Channel::Directions dir, >> unsigned sessionID, >> const >> H245_H2250LogicalChannelParameters * param, >> RTP_QOS * rtpqos) >> { >> return new H323_ExternalRTPChannel(*this, capability, dir, >> sessionID, >> externalIpAddress, >> externalPort); >> } >> >> PBoolean OnStartLogicalChannel(H323Channel & channel) >> { >> H323_ExternalRTPChannel & external = (H323_ExternalRTPChannel >> &)channel; >> external.GetRemoteAddress(remoteIpAddress, remotePort); >> } >> >> >> *I am able to read remote end ip and port numbers. >> >> But After implementation of the above code, I am not able to set my local >> Ip and port numbers. >> Both IP and port number in H.245 message are showing 0 value. Below is >> the h323 message: >> >> >> *2012/04/07 18:24:40.873 4 h323.cxx(4253) H323 >> OnOpenLogicalChannel >> 2012/04/07 18:24:40.873 3 channels.cxx(1042) H323RTP >> OnSendOpenAck >> 2012/04/07 18:24:40.873 2 transports.cxx(433) H323 Use of >> non IP transport address: "" >> 2012/04/07 18:24:40.873 2 transports.cxx(433) H323 Use of >> non IP transport address: "" >> 2012/04/07 18:24:40.873 2 channels.cxx(1064) H323RTP Sending >> open logical channel ACK: sessionID=1 >> 2012/04/07 18:24:40.873 2 h323ep.cxx(2321) H323 Started >> receiving logical channel: G.711-uLaw-64k <2> >> 2012/04/07 18:24:40.874 3 h323pdu.cxx(630) H245 Sending >> PDU [ip$192.168.7.87:5500/ip$192.168.7.63:63622] : >> response openLogicalChannelAck { >> forwardLogicalChannelNumber = 4 >> forwardMultiplexAckParameters = h2250LogicalChannelAckParameters { >> sessionID = 1 >> mediaChannel = unicastAddress iPAddress { >> network = 4 octets { >> 00 00 00 00 .... >> } >> tsapIdentifier = 0 >> } >> mediaControlChannel = unicastAddress iPAddress { >> network = 4 octets { >> 00 00 00 00 .... >> } >> tsapIdentifier = 0 >> } >> flowControlToZero = false >> } >> } >> >> >> * >> Please help to solve above problem. >> >> >> >> Regards, >> Ashwani >> > > > > > -- Regards. *Ashwani Kumar Embedded Engg. Mob:+91-9880631584 *

1 0

H323plus problem : Use of non IP transport address: " "
by Ashwani Kumar 07 Apr '12

07 Apr '12

Hi Simon, I have implemented the code to read remote parameters as given in h323con.h +1517 * H323Channel * MyConnection::CreateRealTimeLogicalChannel( const H323Capability & capability, H323Channel::Directions dir, unsigned sessionID, const H245_H2250LogicalChannelParameters * param, RTP_QOS * rtpqos) { return new H323_ExternalRTPChannel(*this, capability, dir, sessionID, externalIpAddress, externalPort); } PBoolean OnStartLogicalChannel(H323Channel & channel) { H323_ExternalRTPChannel & external = (H323_ExternalRTPChannel &)channel; external.GetRemoteAddress(remoteIpAddress, remotePort); } *I am able to read remote end ip and port numbers. But After implementation of the above code, I am not able to set my local Ip and port numbers. Both IP and port number in H.245 message are showing 0 value. Below is the h323 message: *2012/04/07 18:24:40.873 4 h323.cxx(4253) H323 OnOpenLogicalChannel 2012/04/07 18:24:40.873 3 channels.cxx(1042) H323RTP OnSendOpenAck 2012/04/07 18:24:40.873 2 transports.cxx(433) H323 Use of non IP transport address: "" 2012/04/07 18:24:40.873 2 transports.cxx(433) H323 Use of non IP transport address: "" 2012/04/07 18:24:40.873 2 channels.cxx(1064) H323RTP Sending open logical channel ACK: sessionID=1 2012/04/07 18:24:40.873 2 h323ep.cxx(2321) H323 Started receiving logical channel: G.711-uLaw-64k <2> 2012/04/07 18:24:40.874 3 h323pdu.cxx(630) H245 Sending PDU [ip$192.168.7.87:5500/ip$192.168.7.63:63622] : response openLogicalChannelAck { forwardLogicalChannelNumber = 4 forwardMultiplexAckParameters = h2250LogicalChannelAckParameters { sessionID = 1 mediaChannel = unicastAddress iPAddress { network = 4 octets { 00 00 00 00 .... } tsapIdentifier = 0 } mediaControlChannel = unicastAddress iPAddress { network = 4 octets { 00 00 00 00 .... } tsapIdentifier = 0 } flowControlToZero = false } } * Please help to solve above problem. Regards, Ashwani

1 0

Re: [h323plus] Need help to read Remote Port numbers in simph323
by Ashwani Kumar 05 Apr '12

05 Apr '12

On Thu, Apr 5, 2012 at 7:11 PM, Ashwani Kumar <ash1412(a)gmail.com> wrote: > Hi Simon. > > I implement the code as follows: > > H323_ExternalRTPChannel *a = (H323_ExternalRTPChannel *)&channel; > PIPSocket::Address x; > WORD y; > if (a->GetSessionID()==1) { > a->GetRemoteAddress(x, y); > } > if (a->GetSessionID()==2) { > a->GetRemoteAddress(x, y); > } > > > inside the "PBoolean > SimpleH323Connection::OnStartLogicalChannel(H323Channel & channel) " > > > function. but I am not able to compile the code. > Getting following errors: > > main.cxx: In member function 'virtual PBoolean > SimpleH323Connection::OnStartLogicalChannel(H323Channel&)': > main.cxx:1563:27: error: 'a' was not declared in this scope > main.cxx:1563:57: error: expected primary-expression before ')' token > > > > > Please help to rectify the problem/suggest code to read remote address & > port number. > > Regards, > Ashwani > > > On Thu, Apr 5, 2012 at 4:19 PM, Ashwani Kumar <ash1412(a)gmail.com> wrote: > >> Hi simon, >> >> I want to implement code to read remote end audio and video port numbers >> in simph323 (when call established). >> >> Can you please suggest the code added to be in simph323 application. >> >> >> >> -- >> >> >> Thanks in Advance. >> *Ashwani Kumar >> * >> > > > > -- >

1 1

OpenMCU Virtual Machine working out-of-the-box
by Andrei Varnavskiy 03 Apr '12

03 Apr '12

Hi, All. What are you want to know about openmcu.ru? And how can I help? Andrey Varnavskiy. >Hi, > >I ran the virtual machine using KVM and had to twiddle with the network >config a bit to get it going within my local network, but their version >of OpenMCU seems to be quite a bit improved indeed. > >Its pretty picky about codecs, but I did get a 2 party conference with >2 Spranto clients going using H.263 in 4CIF. Its actually the first time >I ever got OpenMCU to mix video for me. Kudos! > >Do we have anybody on the list who speaks Russian and can get us in >contact with the programmers ? I think it would be great if we could >get their changes into the H323Plus CVS. The source is included in the >torrent, but I think it would be best to talk with them first. > >Regards, >Jan

3 2