Configuring MTP2
From Yate Documentation
(Difference between revisions)
(→Control) |
|||
Line 1: | Line 1: | ||
− | |||
− | |||
− | + | This is a short example on how to configure MTP2 in Yate. | |
− | MTP2 | + | |
− | == | + | ==Installing sangoma cards== |
Follow [http://docs.yate.ro/wiki/VoIP_PSTN_Gateway#Installing_Sangoma_cards_under_Linux this guide] to install sangoma cards under Linux. | Follow [http://docs.yate.ro/wiki/VoIP_PSTN_Gateway#Installing_Sangoma_cards_under_Linux this guide] to install sangoma cards under Linux. | ||
+ | |||
+ | ==Configure MTP2 in Yate== | ||
The MTP2 link is created on demand. To define a MTP2 link you must define the MTP3 linkset that uses it. | The MTP2 link is created on demand. To define a MTP2 link you must define the MTP3 linkset that uses it. | ||
In ysigchan.conf: | In ysigchan.conf: | ||
+ | |||
[mtp3] | [mtp3] | ||
type=ss7-mtp3 | type=ss7-mtp3 | ||
Line 36: | Line 36: | ||
voicegroup=w1g2 | voicegroup=w1g2 | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Revision as of 10:56, 27 October 2017
This is a short example on how to configure MTP2 in Yate.
Installing sangoma cards
Follow this guide to install sangoma cards under Linux.
Configure MTP2 in Yate
The MTP2 link is created on demand. To define a MTP2 link you must define the MTP3 linkset that uses it.
In ysigchan.conf:
[mtp3] type=ss7-mtp3 netind2pctype=ITU netindicator=national local=ITU,0-0-6 adjacent=ITU,0-0-5 link=mtp2 [mtp2] type=ss7-mtp2 autostart=yes emergency=yes autoemergency=yes sig=wanpipe1 filllink=no
Note: According to standards filllink should be 'yes'. We usually set it to 'no' because most of the times the underlying layers don't have support for it (unless when support was added in the hardware and then it's ok to configure filllink='yes').
In wpcard.conf
[wanpipe1] type=E1 siggroup=w1g1 voicegroup=w1g2
See also