Home

Resources

Products

Developers

Main • SIPRegistrationServer

Main.SIPRegistrationServer History

Hide minor edits - Show changes to markup

June 08, 2011, at 06:30 PM by Ana Barbu -
Changed lines 10-12 from:
* The user agent sends a REGISTER request to the server.
* The server sends back an acknowledgement message.
to:
ē The user agent sends a REGISTER request to the server.
ē The server sends back an acknowledgement message.
June 08, 2011, at 06:30 PM by Ana Barbu -
Changed lines 9-15 from:

The actual registration of a SIP user agent on a registration server is made using a pretty simple message flow like it follows. The user agent sends a REGISTER request to the server and this one sends back an acknowledgement message. By changing some fields in the message the registration canceling is performed. Also interrogation of the server to identify contacts associated with a SIP url are made in the same way. But from now these are technical details about SIP, which you can find better explained in the appendix.

to:

The actual registration of a SIP user agent on a registration server is made using a pretty simple message flow like it follows.

* The user agent sends a REGISTER request to the server.
* The server sends back an acknowledgement message.

By changing some fields in the message the registration canceling is performed. Also interrogation of the server to identify contacts associated with a SIP url are made in the same way.

But from now these are technical details about SIP, which you can find better explained in the appendix.

June 08, 2011, at 06:26 PM by Ana Barbu -
Changed lines 5-6 from:

Letís make some light about this register notion. The Session Initiation Protocol provides a REGISTER functionality that is used mainly in a proxy configuration case. For what reason?

to:

Letís make some light about this register notion.
The Session Initiation Protocol provides a REGISTER functionality that is used mainly in a proxy configuration case. For what reason? \\

June 08, 2011, at 06:25 PM by Ana Barbu -
Changed lines 5-6 from:

Letís make some light about this register notion. The Session Initiation Protocol provides a REGISTER functionality that is used mainly in a proxy configuration case. For what reason? The answer is quite simple. Itís about locating individual users in case of a call, which is similar to an INVITE message sent to the server.

to:

Letís make some light about this register notion. The Session Initiation Protocol provides a REGISTER functionality that is used mainly in a proxy configuration case. For what reason? The answer is quite simple. Itís about locating individual users in case of a call, which is similar to an INVITE message sent to the server.

June 08, 2011, at 06:24 PM by Ana Barbu -
Changed lines 3-4 from:

The registration serverís functionality typically stands in setting up and tearing down functionality with a client by using the registration and invite requests as well as clearing and retrieving registrations from a SIP url.
Letís make some light about this register notion. The Session Initiation Protocol provides a REGISTER functionality that is used mainly in a proxy configuration case. For what reason? The answer is quite simple. Itís about locating individual users in case of a call, which is similar to an INVITE message sent to the server. \\

to:

The registration serverís functionality typically stands in setting up and tearing down functionality with a client by using the registration and invite requests as well as clearing and retrieving registrations from a SIP url.

Letís make some light about this register notion. The Session Initiation Protocol provides a REGISTER functionality that is used mainly in a proxy configuration case. For what reason? The answer is quite simple. Itís about locating individual users in case of a call, which is similar to an INVITE message sent to the server.

February 24, 2006, at 10:21 PM by emi -
Added lines 1-5:

SIP registration server

The registration serverís functionality typically stands in setting up and tearing down functionality with a client by using the registration and invite requests as well as clearing and retrieving registrations from a SIP url.
Letís make some light about this register notion. The Session Initiation Protocol provides a REGISTER functionality that is used mainly in a proxy configuration case. For what reason? The answer is quite simple. Itís about locating individual users in case of a call, which is similar to an INVITE message sent to the server.
The actual registration of a SIP user agent on a registration server is made using a pretty simple message flow like it follows. The user agent sends a REGISTER request to the server and this one sends back an acknowledgement message. By changing some fields in the message the registration canceling is performed. Also interrogation of the server to identify contacts associated with a SIP url are made in the same way. But from now these are technical details about SIP, which you can find better explained 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