Actions

Difference between revisions of "Toolpack:Protocol Stack Settings D"
(Removed the line interface part for M2PA-MTP3 configuration)
 
Line 217: Line 217:
 
{| cellpadding="5" border="1" class="wikitable"
 
{| cellpadding="5" border="1" class="wikitable"
 
|-
 
|-
−
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 1) <br>Allocate Physical Interfaces
+
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 1) <br>Configuring the M2PA Layer  
−
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 2) <br>Configuring the M2PA Layer  
+
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 2) <br>Configuring the MTP3 Layer
−
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 3) <br>Configuring the MTP3 Layer
+
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 3) <br>Configuring the ISUP Layer
−
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 4) <br>Configuring the ISUP Layer
+
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 4) <br>Modify NAP profile
−
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 5) <br>Modify NAP profile
+
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 5) <br>Configure Network Access Points (NAPs)
−
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 6) <br>Configure Network Access Points (NAPs)
 
  
 
|-
 
|-
−
| valign="top" |
 
−
*[[Toolpack:Creating_a_Line_Interface D|Create Line Interfaces]]
 
−
*[[Toolpack:Creating_a_Line_Service D|Create Line Services]]
 
−
*[[Toolpack:Creating_a_System_Clock A|Create System Clock]]
 
  
 
| valign="top" |
 
| valign="top" |

Latest revision as of 21:22, 9 May 2022



[edit]
(Step 1)
Allocate Physical Interfaces 		(Step 2)
Configure ISDN-PRI Signaling 		(Step 3)
Modify NAP profile 		(Step 4)
Configure Network Access Points (NAPs)

OR
[edit]
ISDN Overlap Sending
[edit]
(Step 1)
Allocate Physical Interfaces 		(Step 2)
Configuring a CAS stack 		(Step 3)
Modify NAP profile 		(Step 4)
Configure Network Access Points (NAPs)
[edit]
(Step 1)
Configure IP port range 		(Step 2)
Configure SIP Signaling 		(Step 3)
Modify NAP profile 		(Step 4)
Configure Network Access Points (NAPs)

SIP Advanced Features

SIP-I SIP-T
SIP Spiral
Remote NAT Traversal Local NAT Traversal


DNS
SIP Authentication


SIP Service Affecting Parameters

When modifying the following parameters, the SIP stack will be deallocated and reallocated, resulting in a loss of active calls. Be careful when changing these parameters:

Quirks

  • All Parameters

Header Parameters

  • Domain Name
  • Add rPort

DNS Parameters

  • Enabled
  • Use Cache
  • Cache Expire Time
  • Address and Port
[edit]

MTP2-MTP3-ISUP


(Step 1)
Allocate Physical Interfaces 		(Step 2)
Configuring the MTP2 Layer 		(Step 3)
Configuring the MTP3 Layer 		(Step 4)
Configuring the ISUP Layer 		(Step 5)
Modify NAP profile 		(Step 6)
Configure Network Access Points (NAPs)




M2PA-MTP3-ISUP

(Step 1)
Configuring the M2PA Layer 		(Step 2)
Configuring the MTP3 Layer 		(Step 3)
Configuring the ISUP Layer 		(Step 4)
Modify NAP profile 		(Step 5)
Configure Network Access Points (NAPs)


M2UA-MTP2 Relay

(Step 1)
Create Line Interfaces 		(Step 2)
Create MTP2 links 		(Step 3)
Create M2UA configuration

M2UA-MTP3-ISUP

(Step 1)
Create Line Interfaces 		(Step 2)
Create MTP2 links 		(Step 3)
Create M2UA configuration 		(Step 3)
Configuring the MTP3 Layer 		(Step 4)
Configuring the ISUP Layer 		(Step 5)
Modify NAP profile 		(Step 6)
Configure Network Access Points (NAPs)


M3UA-ISUP

(Step 1)
Allocate Physical Interfaces 		(Step 2a)
Configuring the M3UA Layer - IPSP 		(Step 2b)
Configuring the M3UA Layer - ASP 		(Step 2c)
Configuring the M3UA Layer - SGP 		(Step 3)
Configuring the ISUP Layer 		(Step 4)
Modify NAP profile 		(Step 5)
Configure Network Access Points (NAPs)

SS7 Advanced Features

Configuring SPIROU

SS7 Service Affecting Parameters

When modifying the following parameters, some modules of the SS7 stack will be deallocated and reallocated, resulting in a loss of active calls. Be careful when changing these parameters:

MTP2:

  • Connection Mode
  • Protocol Type
  • DPC Length
  • Timeslot Rate
  • Error Correction
  • Max Outstanding Frames
  • Discard Frame In Congestion
  • Cyclic Error: Nb of MSUs to retransmit
  • Cyclic Error: Nb of bytes to retransmit

MTP3 Network

  • Sub Service Field
  • Link type
  • Point code length

MTP3 Linkset

  • OPC
  • APC

MTP3 Link

  • MTP2 Link
  • Priority
  • MTP3 Route
  • DPC
  • Route To Adjacent
  • Sls Range

ISUP:

  • Primary Unit
  • Secondary unit

ISUP Interface

  • OPC, OPC length
  • DPC, DPC length
  • Available Test
  • UserPart
  • Network

ISUP Circuit Group:

  • First CIC
  • Line Service
  • Skip timeslot 16 CIC
  • Timeslots
  • CIC Options
[edit]

MTP2-MTP3-SCCP-TCAP


(Step 1)
Allocate Physical Interfaces 		(Step 2)
Configuring the MTP2 Layer 		(Step 3)
Configuring the MTP3 Layer 		(Step 4)
Configuring the SCCP Layer 		(Step 5)
Configuring the TCAP Layer (optional)




M2PA-MTP3-SCCP-TCAP


(Step 1)
Allocate Physical Interfaces 		(Step 2)
Configuring the M2PA Layer 		(Step 3)
Configuring the MTP3 Layer 		(Step 4)
Configuring the SCCP Layer 		(Step 5)
Configuring the TCAP Layer (optional)


M3UA-SCCP-TCAP

(Step 1)
Allocate Physical Interfaces 		(Step 2)
Configuring the M3UA Layer 		(Step 3)
Configuring the SCCP Layer 		(Step 4)
Configuring the TCAP Layer (optional)
[edit]

If the Tmedia is used to forward signalling messages to the SSW, you will require to configure M2UA, M3UA or IUA before configuring H.248.

If the Tmedia is used to only connect to media, go directly to Media Gateway Configuration


M2UA

(Step 1)
Create Line Interfaces 		(Step 2)
Create MTP2 links 		(Step 3)
Create M2UA configuration

M3UA

(Step 1)
Create Line Interfaces 		(Step 2)
Create MTP2 links 		(Step 3)
Create MTP3 configuration 		(Step 4)
Create M3UA configuration

IUA

(Step 1)
Create Line Interfaces 		(Step 2)
Create IUA Configuration

Sigtran Service Affecting Parameters


When modifying the following parameters, some modules of the Sigtran stack will be deallocated and reallocated, resulting in a loss of active calls. Be careful when changing these parameters:
SCTP

  • Service Type
  • udp_tunneling_port
  • Initial window space
  • MTU size
  • Domain name

M2UA

  • Node Type

M2UA SAP

  • SCTP Source Port
  • Maximum ACK delay
  • Edit IP Interfaces

M2UA LINK

  • MTP2 Link
  • Protocol Type
  • Interface Id

M2UA CLUSTER

  • Traffic Mode
  • Load Share Mode

M2UA PEER

  • Destination Port
  • Number of SCTP Streams
  • Self ASP Id
  • IP Header Type of Service (ToS)
  • Edit Destination Addresses

IUA SAP

  • SCTP Source Port
  • SCTP Primitive Timeout
  • Maximum ACK delay
  • Edit IP Interfaces

IUA CLUSTER

  • Traffic Mode
  • Load Share Mode
  • Minimum number of simultaneously active peer
  • IUA message queue size

IUA LINK

  • Interface Id
  • Line service
  • Variant
  • Side

IUA PEER

  • Destination Port
  • Valid ASP id required
  • Number of SCTP Streams
  • Edit Destination Addresses
  • Primitive timeout
  • IP Header Type of Service (ToS)


Media

TDM NAP (for ISUP/ISDN)

(Step 1)
Allocate TDM Physical Interfaces 		(Step 2)
Modify NAP profile 		(Step 3)
Configure Network Access Points (NAPs)

VOIP NAP (for SIP)

(Step 1)
Create IP Port Ranges 		(Step 2)
Modify NAP profile 		(Step 3)
Configure Network Access Points (NAPs)

CAS NAP

(Step 1)
Allocate Physical Interfaces 		(Step 2)
Configuring a CAS stack 		(Step 3)
Modify NAP profile 		(Step 4)
Configure Network Access Points (NAPs)

Media Gateway

(Step 1)
Configure Media Gateway for H.248 mode 		(Step 2)
Add a New Media Gateway Controller 		(Step 3)
Associate NAPs Resources to H.248 Configuration

H.248 Service Affecting Parameters


When modifying the following parameters, the H.248 stack will be deallocated and reallocated, resulting in a loss of active calls. Be careful when changing these parameters:
Transport Protocol

  • All Parameters

Advanced Parameters

  • Maximum Number of TDM Terminations
  • Maximum Number of Ephemeral Terminations
  • Default MEGACO version
  • Maximum Number of DNS Pending Requestslmorissette
  • Ephemeral Termination Identifier Root
  • Ephemeral Termination Identifier Maximum Value

Profile

  • All Parameters

Timers

  • Dialing Start Timer Value
  • Dialing Short Timer Value
  • Dialing Long Timer Value
  • Dialing Duration Timer Value
  • Restart Timer Value to Retry Controller Association
  • Local Response Timer Value
  • Inactivity Timer Value


Return to Web Portal 3.0 Home Page

Retrieved from "https://docs.telcobridges.com/mediawiki/index.php?title=Toolpack:Protocol_Stack_Settings_D&oldid=31610"