Liviu: /* Other documentation */

2017-10-26T13:22:17Z

‎Other documentation

Liviu: /* Other configuration steps */

2017-10-26T09:23:21Z

‎Other configuration steps

Liviu: /* Other configuration steps */

2017-10-26T09:19:47Z

‎Other configuration steps

Liviu: /* Other configuration steps */

2017-10-26T09:19:32Z

‎Other configuration steps

Liviu: Created page with "== Mediant configuration== It is possible to configure a Mediant gateway either from the Web interface or by editing the ''BOARD.ini'' configuration file (accessible from the..."

2017-10-26T09:17:30Z

Created page with "== Mediant configuration== It is possible to configure a Mediant gateway either from the Web interface or by editing the ''BOARD.ini'' configuration file (accessible from the..."

New page

== Mediant configuration==

It is possible to configure a Mediant gateway either from the Web interface or by editing the ''BOARD.ini'' configuration file (accessible from the Management menu).

The settings layout here apply to Mediant firmware version 5.80, other versions may differ. Version 4.x had a radically different layout.

Please make sure you select '''Full''' view mode (not Basic) or you will not find all settings described here.

=== TDM Trunk configuration===

First settings that you are going to make are the boards. This setting is common for everything using the trunk, voice or signaling.

From the ''Configuration'' menu select ''PSTN Settings'' => ''Trunk Settings''. For each trunk you configure for SS7/MGCP select ''Protocol Type'' => ''E1 transparent 31'' or ''T1 TRANSPARENT'' or ''J1 TRANSPARENT''.

You may need to reboot the Mediant to activate changes to the board configuration so be sure to select the correct line parameters.

=== SCTP Settings===

From the ''Configuration'' menu select ''Network Settings'' => ''SCTP Settings''
* SCTP Checksum method => Crc
* SCTP Associations Number => '''N'''
* Enable SCTP as Control => Enable
Set '''N''' to at least one plus the maximum number of ASPs that will ever connect. For example if you will have 2 M2UA Groups (each with 1 ASP) and one IUA (with 2 ASPs) you will need at least 5 associations. There are model dependent limits on how many associations a Mediant supports.

If you made any changes to SCTP you will need to reboot the Mediant before you can proceed further.

===SIGTRAN Groups configuration===

You need to create one SIGTRAN Group for each set of interfaces controlled by an Application Server Process. Multiple ASPs may connect to the same group but only one will be active at a time.

Each group has its own STCP port and will use one association for each connecting ASP. If you define more than one group for same type of group you will need to specify custom port values.

From the ''Configuration'' menu select ''SIGTRAN Configuration'' => ''Sigtran Group IDs''
* Group ID => Same as selected ''Group Number''
* UAL Group Function => SG
* Group Layer => M2UA
* Group Traffic Mode => Override
* Group Minimal ASP Number => 1
* Group Local SCTP Port => 2904 (this is the standard M2UA but you need an unique port for each group)
* Inbound Streams Number => 2
* Outbound Streams Number => 2
After that click on '''Create''' and make sure you received no errors.

Repeat to create all groups you need. In this example create just one group number 0 port 2904.

=== SIGTRAN Interfaces configuration===

The interface numbers are abstractions that identify any interface on the gateway.

'''IMPORTANT''': All Mediant gateways support only unique interface numbers across all groups so you need to plan about this.
On other gateways you may create interface IDs unique only inside the group.

From the ''Configuration'' menu select ''SIGTRAN Configuration'' => ''Sigtran Interface IDs''
* Interface ID => Same as selected ''Interface Number''
* Interface ID Name => Something unique, best include the ''Interface Number'' (not used by Yate)
* Owner Group => The ID of the group that will own the interface (0)
* Sigtran Layer Type => M2UA
* IF ID NAI => Same as selected ''Interface Number''
After that click on '''Create''' and make sure you received no errors.

Repeat to create all interfaces you need. In this example create interfaces 0 named ''if0'' and 1 named ''if1''.

=== SS7 Links configuration===

This is where you finally attach MTP2 to TDM timeslots and associate them to interface IDs.

From the ''Configuration'' menu select ''SS7 Configuration'' => ''Links''

Click on an usused link number to select it:
* Name => Something unique, best include the selected ''Link Number'' (not used by Yate)
* Layer 2 Type => MTP2
* Layer 3 Type => M2UA SG
* Trunk Number => Number of trunk on which the link is located
* Timeslot Number => Number of signaling timeslot in trunk
* Group ID => The ID of the group that owns the interface ID (from Groups configuration)
* Interface ID => ID of the interface to assign (from Interfaces configuration)
After that click on '''Create''' and make sure you received no errors.

Repeat to create all links you need. In this example create link 0 attached to group 0 interface 0 and link 1 attached to group 0 interface 1.

After creating all links select each one in turn and click on '''In Service''' to start MTP2 on them.

== Yate configuration==

The matching ysigchan.conf on the Yate side would look like this:

[mediant_g0]
type=ss7-m2ua-client
sig=mediant_g0
aspid=1

[link1]
type=ss7-m2ua
client=mediant_g0
iid=0

[link2]
type=ss7-m2ua
client=mediant_g0
iid=1

The signaling needs to be defined in sigtransport.conf like this:

[mediant_g0]
type=sctp
stream=true
local=a.b.c.d
remote=w.x.y.z:2904
endpoint=true

Replace ''a.b.c.d'' with your desired local IP address on the Yate machine. Replace ''w.x.y.z'' with the address of Mediant. The default port for M2UA is 2904 but you will need to specify it if you set up multiple groups as all but one will be on a non-default port.

== Status on Mediant==

=== Check the status of the TDM trunks===

From the ''Status & Diagnostics'' menu select ''Status & Diagnostics'' => ''Trunks & Channels Status''

Each trunk is '''light green''' if up and running. Any other color indicates misconfiguration or some operational fault.

Note that SS7 links timeslots are indicated as '''magenta''' but their state is not shown.

===Check the status of each link===

From the ''Configuration'' menu select ''SS7 Configuration'' => ''Links''

Each link is '''red''' if not operational, '''green''' if aligned, '''dark blue''' if not in service, '''light blue''' if not configured at all.

== Status on Yate==

The state of Mediant M2UA links is displayed in rmanager just like any type of link:

status sig links

%%+status:sig links
module=sig,format=Type|Status;count=2;link1=ss7-m2ua|Normal Alignment,link2=ss7-m2ua|Out Of Alignment
%%-status

== Other configuration steps==

* [[Configure Mediant MGCP|Configuring Mediant MGCP]]
* [[Configure SCTP|Configuring SCTP]]
* [[Configure MTP3|Configuring MTP3]]
* [[Configure ISUP|Configuring ISUP]]

== Other documentation==

← Older revision		Revision as of 13:22, 26 October 2017
Line 144:		Line 144:
	* [[Configure MTP3\|Configuring MTP3]]		* [[Configure MTP3\|Configuring MTP3]]
	* [[Configure ISUP\|Configuring ISUP]]		* [[Configure ISUP\|Configuring ISUP]]
−
−	~~== Other documentation==~~

@@ Line 141: / Line 141: @@
 * [[Configure Mediant MGCP|Configuring Mediant MGCP]]
-* [[Configure SCTP|Configuring SCTP]]
+* [[Configuring SCTP|Configuring SCTP]]
 * [[Configure MTP3|Configuring MTP3]]
 * [[Configure ISUP|Configuring ISUP]]
 == Other documentation==

Configure Mediant M2UA - Revision history

Liviu: /* Other documentation */

Liviu: /* Other configuration steps */

Liviu: /* Other configuration steps */

Liviu: /* Other configuration steps */

Liviu: Created page with "== Mediant configuration== It is possible to configure a Mediant gateway either from the Web interface or by editing the ''BOARD.ini'' configuration file (accessible from the..."