Home

Resources

Products

Developers

Main • H323 Gatekeeper & multiple endpoint server

H323 Gatekeeper and multiple endpoint server

First, let’s say a few words about H323. We have seen that SIP is a signaling protocol used for VoIP communication. Over the Internet are many more then one debates about H323 vs. SIP, that may lead to the conclusion that H323 is pretty much the same thing as SIP. Often H323 is associated only with the call signaling part of a VoIP transmission. Actually it’s a bit more complicated then this.

H323 is composed from an entire suite of protocols. The exact definition of H323 states that H323 is a recommendation published by the International Telecommunications Union (ITU) defining the internetworking of elements and protocols with the purpose of multimedia communications over an unreliable packet-based network.

The elements of an H323 system are as follows:

• Terminals

A H323 Terminal can be any of a telephone, videophone, IVR device or other kind of endpoint inside a network, which can communicate with another endpoint or with a Multipoint Control Unit or with a Gateway using various types of media ranging from audio to video or other data.

• Multipoint Control Units

Yate acting like a multiple endpoint server resembles such an element. A Multipoint Control Unit provides services needed by more endpoints to take part in a conference call. This is done through a Multipoint Controller that manages the call signaling. Optional Multipoint Processors can be present to handle the various media types exchange and processing during a conference.

• Gateways

The main purpose of the gateway is to make possible the protocol conversion between the endpoints that support H323 and the endpoints that use other protocols for VoIP communication including interfacing to PSTN. Typically a H323 gateway is formed from a Media Gateway for media handling and a Media Gateway Controller for call signaling and other functions.

• Gatekeepers

Like the way it sounds a gatekeeper's use is actually to “guard” a network area. Yate acts like a H323 Gatekeeper providing basic admission control by permitting or denying communication between different endpoints in its zone of control. It also provides an address resolution service. A gatekeeper manages calls in the way that permits them to be placed directly between terminals or routes the signaling through it to perform different kinds of functions like follow me, find me, forward on busy and others. There are also gatekeepers that integrate proxy solutions.

The protocols that H323 unites under its specifications vary from G.7xx codecs to various others descriptions. The most important protocols comprised under the H323 specifications are:

• H225 protocol which in fact parts itself in three specifications more exactly RAS – Registration, Admission and Status, Call Signaling and Text Telephony. This has a direct relation with a gatekeeper – component which Yate is used as, more exactly specifies the modes by which an endpoint can register through the gatekeeper and be allowed to pass it to reach the network.

• H245 is multimedia control protocol used between endpoints to establish the channels for media transmission.

• RTP and RTCP are the protocols concerned with the media transport

• Q931 is the call signaling protocol for ISDN networks. The information included in the H225 data which also like stated is concerned with call signaling is used to complete the info carried by Q931 messages which is missing certain important things for a H323 transmission like the IP address.

This is a short overview of the protocols implied by the H323 recommendation. A more detailed view about some of them and the complete list are included in the Appendix.

July 2014:
Yate 5.4 and YateBTS 4 launched. Added JSON and DNS support in Javascript, Handover support in YateBTS.

March 2014:
YateBTS 2.0 launched. Added authentication and WebGUI. Added USSD support in commercial version.

March 2014:
Yate 5.2 launched. Better JavaScript support and a fixed memory leak.

Jan 2014:
YateBTS 1.0 launched. The first GSM Basestation which works with an IMS/VoLTE core network.

Jan 2014:
Yate 5.1 launched. Better JavaScript support and added libygsm. Elisa chatbot added in RManager

Oct 2013:
OpenHSS is the Yate based HLR/HSS solution for MVNO and LTE carriers.

Oct 2013:
Yate 5 released. Added IPv6 support in SIP for LTE. Improved JavaScript support. Download NOW

Jan 2013:
Yate 4.3 released: Added XML support in Javascript. SCCP - GTT routing between different networks. Stability improvements.
Download NOW

Aug 2012:
Yate 4.2 released: SIP flood protection. Better Jabber/Google Voice support. Usable Javascript. Fixed SIGTRAN links fluctuations.
Download NOW

Apr 2012:
YateClient was accepted in the Mac Store.

Yate 4.1 released: better Gvoice support, iSAC codec, support for new Wanpipe drivers. Fixes – T.38 and Mac client issues.

Mar 2012:
SS7Cloud is launched today, 1st March, 2012, by NullTeam, Yate creators. Having all you need to be a US CLEC, it brings SS7 services in a cloud.

Feb 2012:
Yate 4.0 released.
SCCP, TCAP, MAP and CAMEL, TCP and TLS in SIP, Javascript fast prototyping of telephony applications and brand new face for YateClient.

Nov 2011:
Here is a video that, quote "demonstrates the truly awesome power of the YATE engine, as it easily handles 3 simultaneous calls to an audio player application including dtmf (button press) handling "(from PaintedRockComm).

Nov 2011:
Yate will attend ORR - OPENRHEINRUHR (November 12 - 13).

04 May 2011:
sipgate chooses open source project Yate for core infrastructure.

12 Apr 2011:
Yate 3.3.2 released.
Fix for Jingle calls to Google Voice dropping after 5 minutes.
4 Apr 2011:
Yate 3.3 released.
Support for GMail chat conference, fixes for internal microphone in MacOS. Minor fixes in SS7 M2PA and ANSI. Fixes in H.323, SIP and RTP.

9 Mar 2011:
Yate 3.2 released.
Bug fixes in SIGTRAN/MGCP/SS7 and added support for CNAM/LNP lookup by SIP INVITE/3xx.

Feb 2011:
Yate will attend FOSDEM and XMPP summit.

31 Jan 2011:
Yate 3.1 released.
Yate client support for Google Voice. Support for any country tones in tonegen.

20 Dec 2010:
Yate 3.0 released.
SS7 ITU certified. SS7 STP added. Client supports Jabber IM (Google Talk + Facebook).

3 May 2010:
Yate 3.0.0 alpha 3 released. Featuring the new Jabber server and wideband audio.

8 March 2010:
Yate 2.2 released. Mostly bug fixes. Dahdi compatible. Latest 2 release before 3.0.

6-7 February 2010:
Yate booth at FOSDEM 2010. Free CD with Freesentral available.

2 Nov 2009:
Yate 2.1 launched. Can replace a Cisco PGW2200 to control a Cisco AS54xx.

6 Aug 2008:
Yate and OpenSIPS (former OpenSER) join to build IP based clusters.

4 Aug 2008:
Yate 2 launched.


EditHistoryBacklinksRecent ChangesSearch