What is Yate
From Yate Documentation
(Difference between revisions)
(→Yate's arhitecture) |
|||
| (35 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | Yate stands for '''Y'''et '''A'''nother '''T'''elephony '''E'''ngine, and like the name states it is mainly a telephony engine; while currently focused on | + | Yate stands for '''Y'''et '''A'''nother '''T'''elephony '''E'''ngine, and like the name states it is mainly a telephony engine; while currently focused on [http://www.fcc.gov/voip/ Voice over Internet Protocol (VoIP)] and [http://www.webopedia.com/TERM/P/PSTN.html PSTN], its power lies in its ability to be easily extended. Voice, video, data and instant messenging can all be unified under Yate's flexible routing engine, maximizing communications efficiency and minimizing infrastructure costs for businesses. |
| − | Yate | + | ==Yate usability== |
| − | * [[VoIP | + | |
| − | * [[ | + | * [[VoIP_Server|VoIP Server]] |
| − | * Conference server - with up to 200 channels in a single conference. [[ | + | * [[VoIP_Client|VoIP client]] |
| − | + | * [[Yate as a Conference Server|Conference server]] - with up to 200 channels in a single conference. | |
| + | * [[VoIP_PSTN_Gateway|VoIP to PSTN gateway]] | ||
* PC2Phone and Phone2PC gateway | * PC2Phone and Phone2PC gateway | ||
* IP Telephony server and/or client | * IP Telephony server and/or client | ||
| − | ** [[ | + | ** [[Yate as H323 GateKeeper and YateClient as H323 client|H.323 gatekeeper]] |
| − | ** [[ | + | ** [[H323_Gatekeeper_And_Multiple_Endpoint_Server|H.323 multiple endpoint server]] |
| − | ** H.323<->SIP Proxy | + | ** [[H323_To_SIP_Signalling_Proxy|H.323<->SIP Proxy]] |
| − | ** | + | ** [[SIP Router]] |
| − | ** [[ | + | ** [[SIP_Session_Border_Controller|SIP session border controller]] |
| − | ** [[ | + | ** [[SIP_Registration_Server|SIP registration server]] |
| − | ** IAX server | + | ** [[How to configure Yate as IAX server|IAX Server]] |
| − | ** Jingle client or server | + | ** [[IAX Client]] |
| + | ** [[Jabber_Client_With_Jingle_Yate_Server|Jingle client or server]] | ||
** MGCP server (Call Agent) | ** MGCP server (Call Agent) | ||
* ISDN passive and active recorder | * ISDN passive and active recorder | ||
| Line 24: | Line 26: | ||
* Prepaid and/or postpaid cards system | * Prepaid and/or postpaid cards system | ||
| − | The software is | + | == About Yate's software== |
| + | |||
| + | The software is ''written in C++'' and it supports scripting in various programming languages (such as those supported by the currently implemented PHP, Python, Perl and Javascript libraries) and even any Unix shell. The PHP, Python, Perl and Javascript libraries have been developed and made available in order to ease development of external functionalities for Yate. | ||
Yate is production-ready software and is easily extensible. | Yate is production-ready software and is easily extensible. | ||
| − | Yate is licensed under the | + | == Yate's license== |
| + | |||
| + | Yate is licensed under the [http://www.fsf.org/licenses/gpl.html GPL]. | ||
| + | |||
| + | ==Yate's arhitecture== | ||
| + | |||
| + | The architecture of Yate is based on a message passing system. The architecture can be divided into 4 main parts: | ||
| + | |||
| + | * Core, where encapsulations for sockets, threads and others primitives can be found | ||
| + | * Message Engine, message related classes, used to exchange data between modules | ||
| + | * Telephony Engine, the telephony related classes | ||
| + | * Yate Modules, modules extending the functionality of Yate | ||
| + | |||
| + | Find more about Yate's [[Yate_architecture|architecture]]. | ||
| + | |||
| + | |||
| + | '''See also''' | ||
| + | |||
| + | * [[A Brief History of Yate]] | ||
| + | |||
| + | [[Category:Server]] [[Category:Client]] [[Category:Design]] | ||
Latest revision as of 14:42, 4 November 2013
Yate stands for Yet Another Telephony Engine, and like the name states it is mainly a telephony engine; while currently focused on Voice over Internet Protocol (VoIP) and PSTN, its power lies in its ability to be easily extended. Voice, video, data and instant messenging can all be unified under Yate's flexible routing engine, maximizing communications efficiency and minimizing infrastructure costs for businesses.
Contents |
[edit] Yate usability
- VoIP Server
- VoIP client
- Conference server - with up to 200 channels in a single conference.
- VoIP to PSTN gateway
- PC2Phone and Phone2PC gateway
- IP Telephony server and/or client
- ISDN passive and active recorder
- ISDN, RBS, analog passive recorder
- SS7 switch
- Call center server
- IVR engine
- Prepaid and/or postpaid cards system
[edit] About Yate's software
The software is written in C++ and it supports scripting in various programming languages (such as those supported by the currently implemented PHP, Python, Perl and Javascript libraries) and even any Unix shell. The PHP, Python, Perl and Javascript libraries have been developed and made available in order to ease development of external functionalities for Yate.
Yate is production-ready software and is easily extensible.
[edit] Yate's license
Yate is licensed under the GPL.
[edit] Yate's arhitecture
The architecture of Yate is based on a message passing system. The architecture can be divided into 4 main parts:
- Core, where encapsulations for sockets, threads and others primitives can be found
- Message Engine, message related classes, used to exchange data between modules
- Telephony Engine, the telephony related classes
- Yate Modules, modules extending the functionality of Yate
Find more about Yate's architecture.
See also
