-
* [[How to configure Yate as IAX server|Yate as IAX server and YateClient as IAX client]]
For basic setups configure yate to write single cdr entry per call, instead of entry for each call leg
9 KB (1,376 words) - 10:01, 27 October 2017
-
How to configure Yate to handle a SIP attended call transfer for an unknown call leg in the
Configuration file used to configure H323 protocol in Yate
8 KB (1,083 words) - 11:49, 27 October 2017
-
A SLT [[Configure Cisco SLT|configuration example]] is available in the [[SS7_Support_in_Yate
; The name of the section is referenced as link= from a MTP3 configuration
3 KB (474 words) - 12:05, 26 October 2017
-
This is a short example on how to configure MTP2 in Yate.
==Configure MTP2 in Yate==
975 B (160 words) - 08:57, 27 October 2017
-
You will need to configure the SCTP stack of the operating system yate is running on if you plan to us
To use SCTP in yate you must configure it in [[SigTransport|sigtransport]] module.
2 KB (253 words) - 09:27, 26 October 2017
-
After all this messages were exchanged the MTP3 traffic can start.
M2UA is designed to run over [[Configure SCTP|SCTP]] transport.<br>
13 KB (2,284 words) - 11:12, 13 December 2017
-
...ocol stack and it was designed for remote processing of SS7 messages above MTP3 protocol, mostly ISUP and SCCP.<br>
*Network Type (MTP3 Network Indicator)
11 KB (1,842 words) - 09:53, 27 October 2017
-
MTP3 is associated to the Signalling Link Functional Level in MTP. It is used to
MTP3 can be used over the following data links:
7 KB (1,115 words) - 10:47, 27 October 2017
-
Let's assume that SEP 1 uses MTP3 linksets.
[mtp3_ls1]
883 B (132 words) - 10:50, 27 October 2017
-
Cisco#configure terminal
receive-rtcp configure RTCP receive timer- '''available for h323/sip only''' at this time
6 KB (921 words) - 11:10, 26 October 2017
-
...be referenced from ''ysigchan.conf'' in sections type [[Configure MTP3|ss7-mtp3]].
* [[Configure Cisco MGCP|Configuring Cisco MGCP]]
10 KB (1,328 words) - 09:09, 26 October 2017
-
...ge will be read at each level in the order shown in the image: SCTP, M2PA, MTP3, ISUP and then routed in SIP and send to the destination.
:Yate needs to be configured with command: ./configure --enable-sctp=yes.
5 KB (643 words) - 12:23, 26 October 2017
-
It is possible to configure a Mediant gateway either from the Web interface or by editing the ''BOARD.i
...'' menu select ''PSTN Settings'' => ''Trunk Settings''. For each trunk you configure for SS7/MGCP select ''Protocol Type'' => ''E1 transparent 31''.
5 KB (761 words) - 09:12, 26 October 2017
-
==Configure SCCP and enable GTT support==
type=ss7-mtp3
2 KB (268 words) - 09:22, 27 October 2017
-
It is possible to configure a Mediant gateway either from the Web interface or by editing the ''BOARD.i
...'' menu select ''PSTN Settings'' => ''Trunk Settings''. For each trunk you configure for SS7/MGCP select ''Protocol Type'' => ''E1 transparent 31'' or ''T1 TRAN
6 KB (975 words) - 13:22, 26 October 2017
-
...document describes the differences between [[Configuring M2PA|M2PA]] and [[Configure M2UA|M2UA]].
Both links have a MTP3 layer above them, and this implies the allocation of an point code for this
4 KB (697 words) - 09:54, 26 October 2017
-
It runs over a SS7 layer 3 protocol like MTP3 or M3UA.
...ATE instance is an "on demand" component. Basically this means that if you configure a SCCP section in ysigchan.conf but you do not reference it from a SCCP ap
11 KB (1,757 words) - 09:19, 27 October 2017
-
To configure a SCCP layer on a STP you need the following:
Below is the schema of the network we are trying to configure. We'll be configuring STP2.
9 KB (1,276 words) - 14:12, 26 October 2017
-
To configure a SCCP layer on a SEP you need the following:
Below is the schema of the network we are trying to configure. We'll be configuring SEP1. <br/>
2 KB (275 words) - 14:09, 26 October 2017
-
To configure SCCP address translation you must define:
type=ss7-mtp3
3 KB (434 words) - 14:13, 26 October 2017
