Telephony
(→SS7 Protocol suite) |
|||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 157: | Line 157: | ||
* [[Terminology_for_Yate_implementation_of_SS7 | Terminology]] | * [[Terminology_for_Yate_implementation_of_SS7 | Terminology]] | ||
Terminology for Yate implementation of SS7 | Terminology for Yate implementation of SS7 | ||
| − | * [[Implementation]] | + | * [[SS7 Implementation]] |
| − | SS7 | + | List on SS7 components inplemented in Yate. |
| − | * [[Interconnecting]] | + | * [[Interconnecting on SS7]] |
To connect to another SS7 network you will need to configure some parameters so the two sides speak the same language. | To connect to another SS7 network you will need to configure some parameters so the two sides speak the same language. | ||
* [[Signalling]] | * [[Signalling]] | ||
| Line 166: | Line 166: | ||
|class="yate-content-right"| | |class="yate-content-right"| | ||
* [[How_To's#SS7_Setups | Usage Scenarios]] | * [[How_To's#SS7_Setups | Usage Scenarios]] | ||
| − | + | Miscellaneous setups with various features: MTP2, MTP3, ISUP, CAMEL MAP, M3UA etc. | |
* [[M2PA VS M2UA]] | * [[M2PA VS M2UA]] | ||
A comparison between M2UA and M2PA | A comparison between M2UA and M2PA | ||
* [[SCCP_Introduction | SCCP]] | * [[SCCP_Introduction | SCCP]] | ||
SCCP represents a layer 4 protocol from SS7 signaling stack. It runs over a SS7 layer 3 protocol like MTP3 or M3UA | SCCP represents a layer 4 protocol from SS7 signaling stack. It runs over a SS7 layer 3 protocol like MTP3 or M3UA | ||
| + | * [[SS7 MTP2 in Yate | MTP2]] | ||
| + | MTP2 links are the classic way of interconnecting SS7 over TDM. | ||
| + | * [[Configure M3UA | M3UA]] | ||
| + | This is a SIGTRAN protocol and it was designed for remote processing of SS7 messages above MTP3 protocol, mostly ISUP and SCCP. | ||
| + | * [[Configuring_M2PA | M2PA]] | ||
| + | M2PA is a peer to peer SS7 layer 2 protocol. It was designed to replace MTP2 protocol in the IP scenarios. | ||
| + | * [[Configure_M2UA | M2UA]] | ||
| + | This is a SIGTRAN protocol allowing to access a remote MTP2 implementation on a Signaling Gateway. | ||
|} | |} | ||
Latest revision as of 13:49, 27 October 2017
Contents |
[edit] 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. Example on how to handle custom SIP requests. |
[edit] H323 Protocol
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.
| About | Features |
|
Configuration file used to configure H323 protocol in Yate Installing and compiling OpenH323 - stable version to use with Yate How to compile Yate with H323plus support - unstable version to use with Yate |
Configure H323 Gatekeeper And Multiple Endpoint Server Configure in Yate H323 To SIP Signalling Proxy Describes DTMFs send related to h323 channel. |
[edit] 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).
| About | Features |
|
This module implements the Call Agent part of MGCP allowing Yate to control analog or digital Media Gateways |
[edit] Inter-Asterisk eXchange(IAX/IAX2)
IAX2 is a VoIP protocol that carries both signaling and media on the same port.
| About | Features |
|
Main configuration file for IAX channel module in Yate. |
Setup to configure Yate as a IAX Server and YateClient as a IAX client |
[edit] JINGLE Protocol
Jingle - Google talk/Google voice.
| About | Features |
|
How to configure JINGLE module in Yate |
How to configure a Jabber Client with Jingle Yate Server Learn how to route calls to contacts using Gmail account in accfile.conf |
[edit] 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).
| About | Features |
|
Configuring Yate as a Jabber Client Configuring Yate as a Jabber Server |
The features for Jabber Server Describes the steps to follow to build a Jabber server using Yate. |
[edit] SS7 Protocol suite
Signaling System #7 (also known as C7) is a suite of communication protocols used in national and international telephony networks to provide signaling of calls and additional services.
Please read our Introduction to SS7 to get the basic concepts. This can help you find out what components exist in a SS7 network, how they interact and which ones you need.
| About | Features |
|
SS7 Introduction Terminology for Yate implementation of SS7 List on SS7 components inplemented in Yate. To connect to another SS7 network you will need to configure some parameters so the two sides speak the same language. This is a brief introduction on how the PSTN signalling modules are working together in Yate. |
Miscellaneous setups with various features: MTP2, MTP3, ISUP, CAMEL MAP, M3UA etc. A comparison between M2UA and M2PA SCCP represents a layer 4 protocol from SS7 signaling stack. It runs over a SS7 layer 3 protocol like MTP3 or M3UA MTP2 links are the classic way of interconnecting SS7 over TDM. This is a SIGTRAN protocol and it was designed for remote processing of SS7 messages above MTP3 protocol, mostly ISUP and SCCP. M2PA is a peer to peer SS7 layer 2 protocol. It was designed to replace MTP2 protocol in the IP scenarios. This is a SIGTRAN protocol allowing to access a remote MTP2 implementation on a Signaling Gateway. |
[edit] Miscellaneous
Various articles that apply to more than one protocol
| Articles |
|
Description of call end causes and errors in various protocols |
See also
