Telephony
(→Session Initiation Protocol(SIP)) |
(→Session Initiation Protocol(SIP)) |
||
Line 80: | Line 80: | ||
|class="telephony-content-left"| | |class="telephony-content-left"| | ||
<div class="bullet"> </div><font class="tel-title">[[SIP in Yate]]</font><br/> | <div class="bullet"> </div><font class="tel-title">[[SIP in Yate]]</font><br/> | ||
− | <div class="tel-desc">SIP protocol in Yate</div | + | <div class="tel-desc">SIP protocol in Yate</div> |
<div class="bullet"> </div><font class="tel-title">[[SIP Security in Yate]]</font><br/> | <div class="bullet"> </div><font class="tel-title">[[SIP Security in Yate]]</font><br/> | ||
− | < | + | <div class="tel-desc">TLS and SRTP in Yate</div> |
<div class="bullet"> </div><font class="tel-title">[[SIP Configuration File]]</font><br/> | <div class="bullet"> </div><font class="tel-title">[[SIP Configuration File]]</font><br/> | ||
− | < | + | <div class="tel-desc">Main configuration file for SIP module in Yate.</div> |
<div class="bullet"> </div><font class="tel-title">[[SIP Methods]]</font><br/> | <div class="bullet"> </div><font class="tel-title">[[SIP Methods]]</font><br/> | ||
<div class="tel-desc">How Yate processes SIP request methods and how to enable methods that are not handled by default.</div> | <div class="tel-desc">How Yate processes SIP request methods and how to enable methods that are not handled by default.</div> | ||
<div class="bullet"> </div><font class="tel-title">[[SIP Features Module]]</font><br/> | <div class="bullet"> </div><font class="tel-title">[[SIP Features Module]]</font><br/> | ||
− | < | + | <div class="tel-desc">SIP features module that implements SUBSCRIBE and NOTIFY Methods.</div> |
<div class="bullet"> </div><font class="tel-title">[[SIP Routing in Yate]]</font><br/> | <div class="bullet"> </div><font class="tel-title">[[SIP Routing in Yate]]</font><br/> | ||
− | < | + | <div class="tel-desc">Route to a SIP channel and a SIP Line.</div> |
<div class="bullet"> </div><font class="tel-title">[[SIP Client]]</font><br/> | <div class="bullet"> </div><font class="tel-title">[[SIP Client]]</font><br/> | ||
− | < | + | <div class="tel-desc"> Implementation and SIP Client features in Yate </div> |
|class="telephony-content-right"| | |class="telephony-content-right"| | ||
<div class="bullet"> </div><font class="tel-title">[[SIP Features Module]]</font><br/> | <div class="bullet"> </div><font class="tel-title">[[SIP Features Module]]</font><br/> | ||
− | < | + | <div class="tel-desc">SIP features module that implements SUBSCRIBE and NOTIFY methods </div> |
<div class="bullet"> </div><font class="tel-title">[[SIP Send DTMFs]]</font><br/> | <div class="bullet"> </div><font class="tel-title">[[SIP Send DTMFs]]</font><br/> | ||
− | < | + | <div class="tel-desc">How to do configurations related to DTMFs in SIP channel.</div> |
<div class="bullet"> </div><font class="tel-title">[[SIP Attended Call Transfer In Cluster]]</font><br/> | <div class="bullet"> </div><font class="tel-title">[[SIP Attended Call Transfer In Cluster]]</font><br/> | ||
− | < | + | <div class="tel-desc">How to configure Yate to handle a SIP attended call transfer for an unknown call leg in the cluster node</div> |
<div class="bullet"> </div><font class="tel-title">[[SIP Flood Protection]]</font><br/> | <div class="bullet"> </div><font class="tel-title">[[SIP Flood Protection]]</font><br/> | ||
− | < | + | <div class="tel-desc">Yate provides a protection mechanism against several types of SIP flood attacks.</div> |
<div class="bullet"> </div><font class="tel-title">[[SIP SBC]]</font><br/> | <div class="bullet"> </div><font class="tel-title">[[SIP SBC]]</font><br/> | ||
− | < | + | <div class="tel-desc">Describes how Yate can be used as a SIP session border controller.</div> |
<div class="bullet"> </div><font class="tel-title">[[xsip.generate]]</font><br/> | <div class="bullet"> </div><font class="tel-title">[[xsip.generate]]</font><br/> | ||
− | < | + | <div class="tel-desc">Use this message to initiate the transmission of a SIP request.</div> |
<div class="bullet"> </div><font class="tel-title">[[SIP query for CNAM and LNP]]</font><br/> | <div class="bullet"> </div><font class="tel-title">[[SIP query for CNAM and LNP]]</font><br/> | ||
− | < | + | <div class="tel-desc"> Feature used in a routing module that allows Yate to query CNAM and LNP databases over the SIP protocol.</div> |
<div class="bullet"> </div><font class="tel-title">[[SIP NAT|SIP with NAT]]</font><br/> | <div class="bullet"> </div><font class="tel-title">[[SIP NAT|SIP with NAT]]</font><br/> | ||
− | < | + | <div class="tel-desc">Resolving SIP traversal problem by Yate.</div> |
|} | |} | ||
Revision as of 16:44, 26 November 2012
Yate is a telephony engine who's main function is to connect together call legs to external devices or to internal server resources. It uses a variety of VoIP protocols(as SIP, H.323, IAX2 or Jingle) that can be used without the need of special hardware. In the next chapters you will find more informations about configuring each telephony protocol and the features supported by Yate.
Contents |
Session Initiation Protocol(SIP)
The Session Initiation Protocol(SIP) is an signaling protocol widely used for controlling communication sessions such as voice and video calls over Internet Protocol(IP).
About | Features |
SIP protocol in Yate
TLS and SRTP in Yate
Main configuration file for SIP module in Yate.
How Yate processes SIP request methods and how to enable methods that are not handled by default.
SIP features module that implements SUBSCRIBE and NOTIFY Methods.
Route to a SIP channel and a SIP Line.
Implementation and SIP Client features in Yate
|
SIP features module that implements SUBSCRIBE and NOTIFY methods
How to do configurations related to DTMFs in SIP channel.
How to configure Yate to handle a SIP attended call transfer for an unknown call leg in the cluster node
Yate provides a protection mechanism against several types of SIP flood attacks.
Describes how Yate can be used as a SIP session border controller.
Use this message to initiate the transmission of a SIP request.
Feature used in a routing module that allows Yate to query CNAM and LNP databases over the SIP protocol.
Resolving SIP traversal problem by Yate.
|
H323
H.323 is a standard that specifies the components, protocols and procedures that provide multimedia communication services - real-time audio, video, and data communications - over packet-based networks.
|
Media Gateway Control Protocol(MGCP)
Media Gateway Control Protocol is a signalling and call control protocol used within Voice over IP (VoIP) systems that typically inter-operate with the public switched telephone network (PSTN).
|
Inter-Asterisk eXchange(IAX/IAX2)
IAX2 is a VoIP protocol that carries both signaling and media on the same port.
|
JINGLE
Jingle is an extension to the Extensible Messaging and Presence Protocol (XMPP) which adds peer-to-peer (P2P) session control (signaling) for multimedia interactions such as in Voice over IP (VoIP) or videoconferencing communications.
|
JABBER or XMPP(Extensible Messaging and Presence Protocol)
Extensible Messaging and Presence Protocol(XMPP) is a communications protocol for message-oriented middleware based on XML(Extensible Markup Language).
|
See also