Configuring MTP2

From Yate Documentation
(Difference between revisions)
Jump to: navigation, search
(Configure MTP2 in Yate)
 
Line 9: Line 9:
 
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]
Line 29: Line 29:
 
  '''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').
 
  '''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
+
In '''wpcard.conf'''
  
 
  [wanpipe1]
 
  [wanpipe1]

Latest revision as of 10:57, 27 October 2017

This is a short example on how to configure MTP2 in Yate.

[edit] Installing sangoma cards

Follow this guide to install sangoma cards under Linux.

[edit] 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

Personal tools
Namespaces

Variants
Actions
Preface
Configuration
Administrators
Developers