TB Wiki - User contributions [en]

Parameter: Number of Worker Threads

2024-03-28T08:31:38Z

Joshua Puckett:

Enter the number of worker threads available to parallelize H248 Transactions.

*Increasing this number increases the amount of RAM used for the H248 stack.
*On Higher capacity systems this value may need to be increased to avoid H248 transaction delays. (Mainly the [[Tmedia_Overview#tab=TMG7800|TMG7800]])
*Monitor available RAM during peak hours after modifying this setting
*Decrease this value if RAM usage becomes concerning

[[Category: Parameters]]

Parameter: Number of Worker Threads

2024-03-28T08:26:44Z

Joshua Puckett: Created page with "Enter the number of worker threads available to parallelize H248 Transactions. *Increasing this number increases the amount of RAM used for the H248 stack *On Higher capacity systems this value may need to be increased to avoid H248 delays. (Mainly the TMG7800) *Monitor available RAM during peak hours after modifying this setting *Decrease this value if RAM usage becomes concerning Category: Parameters"

Enter the number of worker threads available to parallelize H248 Transactions.

*Increasing this number increases the amount of RAM used for the H248 stack
*On Higher capacity systems this value may need to be increased to avoid H248 delays. (Mainly the [[Tmedia_Overview#tab=TMG7800|TMG7800]])
*Monitor available RAM during peak hours after modifying this setting
*Decrease this value if RAM usage becomes concerning

[[Category: Parameters]]

Parameter: Seizure Bytes Used before Mark Bytes

2024-03-28T08:21:41Z

Joshua Puckett: Created page with "Enter the number of seizure bytes to use before the FSK Mark Bytes. Category: Parameters"

Enter the number of seizure bytes to use before the FSK Mark Bytes.

[[Category: Parameters]]

Parameter: Mark Bytes sent before FSK message

2024-03-28T08:20:25Z

Joshua Puckett: Created page with "Enter the number of Mark Bytes the system shoudl send before sending FSK Data. Category: Parameters"

Enter the number of Mark Bytes the system shoudl send before sending FSK Data.

[[Category: Parameters]]

Parameter: FSK Level

2024-03-28T08:19:46Z

Joshua Puckett: Created page with "Select the signaling level to be used for Frequency-shift Keying. Category: Parameters"

Select the signaling level to be used for Frequency-shift Keying.

[[Category: Parameters]]

Parameter: FSK Variant

2024-03-28T08:18:50Z

Joshua Puckett: Created page with "Select between [https://en.wikipedia.org/wiki/ITU-T_V.23 ITU V.23] and [https://en.wikipedia.org/wiki/Bell_202_modem Bell 202 Modem] Frequency-shift Keying(FSK) variant. Category: Parameters"

Select between [https://en.wikipedia.org/wiki/ITU-T_V.23 ITU V.23] and [https://en.wikipedia.org/wiki/Bell_202_modem Bell 202 Modem] Frequency-shift Keying(FSK) variant.

[[Category: Parameters]]

Parameter: Observe default CAS events

2024-03-28T08:14:37Z

Joshua Puckett: Created page with "If checked a default event descriptor is used to detect CAS seizure events on CAS terminations in the NULL context. Category: Parameters"

If checked a default event descriptor is used to detect CAS seizure events on CAS terminations in the NULL context.
 

[[Category: Parameters]]

Toolpack:Protocol Stack Settings E

2024-03-28T08:11:14Z

Joshua Puckett: /* H.248 MEGACO */

{{DISPLAYTITLE:Tmedia, Tdev, and Tsig Web Portal 3.2: Protocol Stacks}}
__NOTOC__
=ISDN FAS and NFAS=

{| 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) 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 2) Configure ISDN-PRI Signaling

! 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) 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 4) 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" |
*[[Toolpack:Configuring_an_ISDN_Stack F|Configure an ISDN stack]]
OR 
*[[Toolpack:Configuraing_NFAS D|Configure NFAS]]

| valign="top" |
*[[Toolpack:Modify_NAP_profile F|Modify profile]]

| valign="top" |
*[[Toolpack:Allocating_an_ISDN_Network_Access_Point_(NAP) F|Allocate an ISDN NAP]]

|}

'''ISDN Advanced Features'''

{| 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;" |ISDN Overlap Sending
|-
| valign="top" |
*[[Toolpack:Configuring_Overlap C|ISDN NFAS Overlap Parameters]]
|}

=CAS=

{| 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) 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 2) Configuring a CAS stack
! 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) 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 4) 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" |
*[[Toolpack:Copy variant script D|Copy variant script]]
*[[Toolpack:Create CAS R2 stack E|Create CAS stack]]
*Edit the [[CASr1_scripting|CAS R1]] or [[CAS R2 scripting|CAS R2]] script to adapt the variant
**[[CASr1_scripting#TONE_USE_DTMF|Select CAS R1 tone type]]
**[[Toolpack:Setting CAS R2 BACK DIGITS variable D|Set CAS R2 backward digits string]]
| valign="top" |
*[[Toolpack:Modify_NAP_profile F|Modify profile]]
| valign="top" |
*[[Toolpack:Creating_a_CAS_R2_NAP D|Create a CAS NAP]]

|}

=SIP=

{| 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) Configure IP port range
! 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) Configure SIP Signaling
! 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) 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 4) Configure Network Access Points (NAPs)
|-
| valign="top" |
*[[Toolpack:Creating_an_IP_Port_Range D|Create an IP port range]]

| valign="top" |
*[[Toolpack:Creating_a_SIP_Stack D|Create a SIP stack]]
*[[Toolpack:Creating_a_SIP_Transport_Server D|Create a SIP transport server]]

| valign="top" |
*[[Toolpack:Modify_NAP_profile F|Modify profile]]

| valign="top" |
*[[Toolpack:Allocating_a_SIP_Network_Access_Point_(NAP) F|Allocate a SIP NAP]]

|}

'''SIP Advanced Features'''
{| 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;" | SIP-I SIP-T
|-
| valign="top" |
*[[Enabling_SIP_I_SIP_T D|Enable SIP-I SIP-T]]
|}

{| 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;" | SIP Spiral and other SIP quirks
|-
| valign="top" |
*[[Enabling_SIP_Spiral D|Enable SIP Spiral]]
|}

{| 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;" | Remote NAT Traversal
! 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;" | Local NAT Traversal
|-
| valign="top" |
*[[Enabling_Remote_NAT_Traversal_C|Enable Remote NAT Traversal]]

| valign="top" |
*[[Enabling_Local_NAT_Traversal_C|Enable Local NAT Traversal]]
|}

{| 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;" | DNS
|-
| valign="top" |
*[[Toolpack:Configuring_DNS_Parameters_C|Enable DNS]]
|}

{| 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;" | SIP Authentication
|-
| valign="top" |
*[[Toolpack:Configuring_SIP_Authentication_A|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

=SS7 ISUP=

'''MTP2-MTP3-ISUP'''

{| 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) 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 2) Configuring the MTP2 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) 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 4) 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 5) 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 6) 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" |
*[[Toolpack:Creating_an_MTP2_Configuration D|Create an MTP2 Configuration]]
*[[Toolpack:Creating_MTP2_Links C|Create MTP2 Links]]

| valign="top" |
*[[Toolpack:Creating_an_MTP3_Configuration E|Create an MTP3 Configuration]]
*[[Toolpack:Creating_an_MTP3_Network D|Create an MTP3 Network Network]]
**[[Toolpack:Creating_SS7_Point_Codes E|Create an MTP3 Point Code]]
**[[Toolpack:Creating_an_MTP3_Linkset C|Create an MTP3 Linkset]]
***[[Toolpack:Creating_MTP3_Links C|Create MTP3 Links]]
**[[Toolpack:Creating_an_MTP3_Route C|Create an MTP3 Route]]

| valign="top" |
*[[Toolpack:Creating_an_ISUP_Stack D|Create an ISUP Stack]]
*[[Toolpack:Creating_an_ISUP_Network C|Create an ISUP Network]]
*[[Toolpack:Creating_an_ISUP_User_Part C|Create an ISUP User Part]]
*[[Toolpack:Creating_an_ISUP_Interface C|Create an ISUP Interface]]
*[[Toolpack:Creating ISUP CIC Groups C|Create ISUP CIC Groups]]

| valign="top" |
*[[Toolpack:Modify_NAP_profile F|Modify profile]]

| valign="top" |
*[[Toolpack:Creating_a_NAP_(SIGTRAN)_D|Create an ISUP NAP]]

|}

'''M2PA-MTP3-ISUP'''

{| 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) 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 2) 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 3) 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 4) 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 5) 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 6) 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" |
*[[Toolpack:Creating the SCTP Configuration D|Create the SCTP Configuration]]
*[[Toolpack:Creating the M2PA Configuration D|Create an M2PA Configuration]]
**[[Toolpack:Creating an M2PA SAP D|Create an M2PA SAP]]
**[[Toolpack:Adding M2PA Links C|Add M2PA Links]]

| valign="top" |
*[[Toolpack:Creating_an_MTP3_Configuration E|Create an MTP3 Configuration]]
*[[Toolpack:Creating_an_MTP3_Network D|Create an MTP3 Network]]
**[[Toolpack:Creating_SS7_Point_Codes E|Create an MTP3 Point Code]]
**[[Toolpack:Creating_an_MTP3_Linkset C|Create an MTP3 Linkset]]
***[[Toolpack:Creating_MTP3_Links C|Create MTP3 Links]]
**[[Toolpack:Creating_an_MTP3_Route C|Create an MTP3 Route]]

| valign="top" |
*[[Toolpack:Creating_an_ISUP_Stack D|Create an ISUP Stack]]
*[[Toolpack:Creating_an_ISUP_Network C|Create an ISUP Network]]
*[[Toolpack:Creating_an_ISUP_User_Part C|Create an ISUP User Part]]
*[[Toolpack:Creating_an_ISUP_Interface C|Create an ISUP Interface]]
*[[Toolpack:Creating ISUP CIC Groups C|Create ISUP CIC Groups]]

| valign="top" |
*[[Toolpack:Modify_NAP_profile F|Modify profile]]

| valign="top" |
*[[Toolpack:Creating_a_NAP_(SIGTRAN)_D|Create an ISUP NAP]]

|}

'''MTP2-MTP3-M2PA (TDM/IP STP)'''

{| 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) 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 2) Create MTP2 links
! 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) 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 4) Configuring the MTP3 Layer

|-
| 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" |

*[[Toolpack:Creating_an_MTP2_Configuration D|Create an MTP2 Configuration]]
**[[Toolpack:Creating_MTP2_Links C|Create MTP2 Links]]

| valign="top" |
*[[Toolpack:Creating the SCTP Configuration D|Create the SCTP Configuration]]
*[[Toolpack:Creating the M2PA Configuration D|Create an M2PA Configuration]]
**[[Toolpack:Creating an M2PA SAP D|Create an M2PA SAP]]
**[[Toolpack:Adding M2PA Links C|Add M2PA Links]]

| valign="top" |
*[[Toolpack:Creating_an_MTP3_Configuration_for_STP|Create an MTP3 Configuration for STP]]
*[[Toolpack:Creating_an_MTP3_Network D|Create an MTP3 Network]]
**[[Toolpack:Creating_SS7_Point_Codes E|Create an MTP3 Point Code]]
**[[Toolpack:Creating_an_MTP3_Linkset C|Create an MTP3 Linkset]]
***[[Toolpack:Creating_MTP3_Links C|Create MTP3 Links]]
**[[Toolpack:Creating_an_MTP3_Route_for_STP|Create an MTP3 Route for STP]]

|}

'''M2UA-MTP2 Relay'''

{| 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) Create Line 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 2) Create MTP2 links
! 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) Create M2UA configuration
|-

| 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" |

*[[Toolpack:Creating_an_MTP2_Configuration D|Create an MTP2 Configuration]]
**[[Toolpack:Creating_MTP2_Links C|Create MTP2 Links]]

| valign="top" |

*[[Toolpack:Creating the SCTP Configuration D|Create the SCTP Configuration]]
*[[Toolpack:Creating the M2UA Configuration D|Create an M2UA Configuration]]
**[[Toolpack:Creating an M2UA SAP C|Create an M2UA SAP]]
**[[Toolpack:Creating an M2UA Cluster C|Create an M2UA Cluster]]
**[[Toolpack:Creating M2UA Links C|Create M2UA Links]]
**[[Toolpack:Creating M2UA Peers C|Create M2UA Peers]]
|}

'''M2UA-MTP3-ISUP'''

{| 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) Create M2UA configuration
! 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) 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) 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) 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) Configure Network Access Points (NAPs)
|-

| valign="top" |

*[[Toolpack:Creating the SCTP Configuration D|Create the SCTP Configuration]]
*[[Toolpack:Creating the M2UA Configuration D|Create an M2UA Configuration]]
**[[Toolpack:Creating an M2UA SAP C|Create an M2UA SAP]]
**[[Toolpack:Creating an M2UA Cluster C|Create an M2UA Cluster]]
**[[Toolpack:Creating M2UA Links C|Create M2UA Links]]
**[[Toolpack:Creating M2UA Peers C|Create M2UA Peers]]

| valign="top" |
*[[Toolpack:Creating_an_MTP3_Configuration E|Create an MTP3 Configuration]]
*[[Toolpack:Creating_an_MTP3_Network D|Create an MTP3 Network]]
**[[Toolpack:Creating_SS7_Point_Codes E|Create an MTP3 Point Code]]
**[[Toolpack:Creating_an_MTP3_Linkset C|Create an MTP3 Linkset]]
***[[Toolpack:Creating_MTP3_Links C|Create MTP3 Links]]
**[[Toolpack:Creating_an_MTP3_Route C|Create an MTP3 Route]]

| valign="top" |
*[[Toolpack:Creating_an_ISUP_Stack D|Create an ISUP Stack]]
*[[Toolpack:Creating_an_ISUP_Network C|Create an ISUP Network]]
*[[Toolpack:Creating_an_ISUP_User_Part C|Create an ISUP User Part]]
*[[Toolpack:Creating_an_ISUP_Interface C|Create an ISUP Interface]]
*[[Toolpack:Creating ISUP CIC Groups C|Create ISUP CIC Groups]]

| valign="top" |
*[[Toolpack:Modify_NAP_profile F|Modify profile]]

| valign="top" |
*[[Toolpack:Creating_a_NAP_(SIGTRAN)_D|Create an ISUP NAP]]
|}

'''M3UA-ISUP'''

{| 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) 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 2a) Configuring the M3UA Layer - IPSP
! 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 2b) Configuring the M3UA Layer - ASP
! 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 2c) Configuring the M3UA Layer - SGP
! 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) 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) 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) 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" |
*[[Toolpack:Creating the SCTP Configuration D|Create the SCTP Configuration]]
*[[Toolpack:Creating SS7 Point Codes E|Create SS7 Point Codes]]
*[[Toolpack:Creating an M3UA Configuration (IPSP) D|Create an M3UA Configuration]]
**[[Toolpack:Creating an M3UA SAP (IPSP) C|Create an M3UA SAP]]
**[[Toolpack:Creating an M3UA Network (IPSP) C|Create an M3UA Network]]
**[[Toolpack:Creating_an_M3UA_User_Part_(IPSP)_C|Create an M3UA User Part]]
**[[Toolpack:Creating an M3UA Peer Signalling Process (IPSP) C|Create an M3UA Peer Signalling Process]]
**[[Toolpack:Creating_an_M3UA_Peer_Server_(IPSP)_C|Create an M3UA Peer Server]]
**[[Toolpack:Creating an M3UA Route (IPSP) C|Create an M3UA Route]]

| valign="top" |
*[[Toolpack:Creating the SCTP Configuration D|Create the SCTP Configuration]]
*[[Toolpack:Creating SS7 Point Codes E|Create SS7 Point Codes]]
*[[Toolpack:Creating an M3UA Configuration ASP D|Create an M3UA Configuration]]
**[[Toolpack:Creating an M3UA SAP (ASP)|Create an M3UA SAP]]
**[[Toolpack:Creating an M3UA Network (ASP) |Create an M3UA Network]]
**[[Toolpack:Creating an M3UA User Part (ASP) C|Create an M3UA User Part]]
**[[Toolpack:Creating an M3UA Peer Signalling Process (ASP) C|Create an M3UA Peer Signalling Process]]
**[[Toolpack:Creating an M3UA Peer Server (ASP) C|Create an M3UA Peer Server]]
**[[Toolpack:Creating an M3UA Route (ASP) C|Create an M3UA Route]]

| valign="top" |
*[[Toolpack:Creating the SCTP Configuration D|Create the SCTP Configuration]]
*[[Toolpack:Creating SS7 Point Codes E|Create SS7 Point Codes]]
*[[Toolpack:Creating an M3UA Configuration SGP D|Create an M3UA Configuration]]
**[[Toolpack:Creating an M3UA SAP (SGP)|Create an M3UA SAP]]
**[[Toolpack:Creating an M3UA Network (SGP) |Create an M3UA Network]]
**[[Toolpack:Creating an M3UA User Part (SGP) C|Create an M3UA User Part]]
**[[Toolpack:Creating an M3UA Peer Signalling Process (SGP) C|Create an M3UA Peer Signalling Process]]
**[[Toolpack:Creating an M3UA Peer Server (SGP) C|Create an M3UA Peer Server]]
**[[Toolpack:Creating an M3UA Route (SGP) C|Create an M3UA Route]]

| valign="top" |
*[[Toolpack:Creating_an_ISUP_Stack D|Create an ISUP Stack]]
*[[Toolpack:Creating_an_ISUP_Network C|Create an ISUP Network]]
*[[Toolpack:Creating_an_ISUP_User_Part C|Create an ISUP User Part]]
*[[Toolpack:Creating_an_ISUP_Interface C|Create an ISUP Interface]]
*[[Toolpack:Creating ISUP CIC Groups C|Create ISUP CIC Groups]]

| valign="top" |
*[[Toolpack:Modify_NAP_profile F|Modify profile]]

| valign="top" |
*[[Toolpack:Creating_a_NAP_(SIGTRAN)_D|Create an ISUP NAP]]

|}

'''SS7 Advanced Features'''

{| 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;" | Configuring SPIROU
|-
| valign="top" |
*[[Toolpack:Modifying_Profile_for_SPIROU B|Modifying Profile]]
*[[Toolpack:Modifying_Gateway_Configurations_for_SPIROU C|Modifying Gateway Configurations]]
*[[Toolpack:Modifying_ISUP_Stack_for_SPIROU B|Modifying ISUP Stack]]
*[[Toolpack:Modifying_ISUP_Userpart_for_SPIROU B|Modifying ISUP Userpart]]
*[[Toolpack:Optional_configurations_for_SPIROU A|Optional modifications]]
|}

'''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

=SCCP-TCAP=

'''MTP2-MTP3-SCCP-TCAP'''

{| 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) 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 2) Configuring the MTP2 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) 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 4) Configuring the SCCP 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 5) Configuring the TCAP Layer (optional)

|-

| 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" |
*[[Toolpack:Creating_an_MTP2_Configuration D|Create an MTP2 Configuration]]
*[[Toolpack:Creating_MTP2_Links C|Create an MTP2 Link]]

| valign="top" |
*[[Toolpack:Creating_an_MTP3_Configuration E|Create an MTP3 Configuration]]
*[[Toolpack:Creating_an_MTP3_Network D|Create an MTP3 Network]]
**[[Toolpack:Creating_SS7_Point_Codes E|Create an MTP3 Point Code]]
**[[Toolpack:Creating_an_MTP3_Linkset C|Create an MTP3 Linkset]]
***[[Toolpack:Creating_MTP3_Links C|Create MTP3 Links]]
**[[Toolpack:Creating_an_MTP3_Route C|Create an MTP3 Route]]

| valign="top" |
*[[Toolpack:Creating_an_SCCP_Stack C| Create an SCCP Stack]]
*[[Toolpack:Creating_an_SCCP_Network C|Create an SCCP Network]]
**[[Toolpack:Creating_an_SCCP_Userpart C|Create an SCCP Userpart]]
**[[Toolpack:Creating_an_SCCP_LSAP C|Create an SCCP LSAP]]
***[[Toolpack:Creating_an_SCCP_Route C|Create an SCCP Route]]
****[[Toolpack:Creating_an_SCCP_SSN C|Create an SCCP SSN]]
*[[Toolpack:Creating_an_SCCP_GTT_Association C|Create an SCCP GTT Association]]
**[[Toolpack:Creating_an_SCCP_GTT_Association_Action A|Create an SCCP GTT Association Action]]
**[[Toolpack:Creating_an_SCCP_GTT_Address_Map C|Create an SCCP GTT Address Map]]

| valign="top" |
*[[Toolpack:Creating_a_TCAP_Stack C|Create a TCAP Stack]]
**[[Toolpack:Creating_a_TCAP_Userpart C| Create a TCAP Userpart]]
*[[Toolpack:Activating_the_Configuration D|Activating the Configuration]]

|}

'''M2PA-MTP3-SCCP-TCAP'''

{| 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) 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 2) 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 3) 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 4) Configuring the SCCP 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 5) Configuring the TCAP Layer (optional)

|-
| 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" |
*[[Toolpack:Creating the SCTP Configuration D|Create the SCTP Configuration]]
*[[Toolpack:Creating the M2PA Configuration D|Create an M2PA Configuration]]
**[[Toolpack:Creating an M2PA SAP D|Create an M2PA SAP]]
**[[Toolpack:Adding M2PA Links C|Add M2PA Links]]

| valign="top" |
*[[Toolpack:Creating_an_MTP3_Configuration E|Create an MTP3 Configuration]]
*[[Toolpack:Creating_an_MTP3_Network D|Create an MTP3 Network]]
**[[Toolpack:Creating_SS7_Point_Codes E|Create an MTP3 Point Code]]
**[[Toolpack:Creating_an_MTP3_Linkset C|Create an MTP3 Linkset]]
***[[Toolpack:Creating_MTP3_Links C|Create MTP3 Links]]
**[[Toolpack:Creating_an_MTP3_Route C|Create an MTP3 Route]]

| valign="top" |
*[[Toolpack:Creating_an_SCCP_Stack C| Create an SCCP Stack]]
*[[Toolpack:Creating_an_SCCP_Network C|Create an SCCP Network]]
**[[Toolpack:Creating_an_SCCP_Userpart C|Create an SCCP Userpart]]
**[[Toolpack:Creating_an_SCCP_LSAP C|Create an SCCP LSAP]]
***[[Toolpack:Creating_an_SCCP_Route C|Create an SCCP Route]]
****[[Toolpack:Creating_an_SCCP_SSN C|Create an SCCP SSN]]
*[[Toolpack:Creating_an_SCCP_GTT_Association C|Create an SCCP GTT Association]]
**[[Toolpack:Creating_an_SCCP_GTT_Association_Action A|Create an SCCP GTT Association Action]]
**[[Toolpack:Creating_an_SCCP_GTT_Address_Map C|Create an SCCP GTT Address Map]]

| valign="top" |
*[[Toolpack:Creating_a_TCAP_Stack C|Create a TCAP Stack]]
**[[Toolpack:Creating_a_TCAP_Userpart C| Create a TCAP Userpart]]
*[[Toolpack:Activating_the_Configuration D|Activating the Configuration]]

|}

'''M3UA-SCCP-TCAP'''

{| 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) 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 2) Configuring the M3UA 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) Configuring the SCCP 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) Configuring the TCAP Layer (optional)

|-

| 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" |
*[[Toolpack:Creating the SCTP Configuration D|Create the SCTP Configuration]]
*[[Toolpack:Creating SS7 Point Codes E|Create SS7 Point Codes]]
*[[Toolpack:Creating an M3UA Configuration E|Create an M3UA Configuration]]
**[[Toolpack:Creating an M3UA SAP D|Create an M3UA SAP]]
**[[Toolpack:Creating an M3UA Network D|Create an M3UA Network]]
**[[Toolpack:Creating an M3UA User Part D|Create an M3UA User Part]]
**[[Toolpack:Creating an M3UA Peer Signalling Process D|Create an M3UA Peer Signalling Process]]
**[[Toolpack:Creating an M3UA Peer Server D|Create an M3UA Peer Server]]
**[[Toolpack:Creating an M3UA Route D|Create an M3UA Route]]

| valign="top" |
*[[Toolpack:Creating_an_SCCP_Stack C| Create an SCCP Stack]]
*[[Toolpack:Creating_an_SCCP_Network C|Create an SCCP Network]]
**[[Toolpack:Creating_an_SCCP_Userpart C|Create an SCCP Userpart]]
**[[Toolpack:Creating_an_SCCP_LSAP C|Create an SCCP LSAP]]
***[[Toolpack:Creating_an_SCCP_Route C|Create an SCCP Route]]
****[[Toolpack:Creating_an_SCCP_SSN C|Create an SCCP SSN]]
*[[Toolpack:Creating_an_SCCP_GTT_Association C|Create an SCCP GTT Association]]
**[[Toolpack:Creating_an_SCCP_GTT_Address_Map C|Create an SCCP GTT Address Map]]

| valign="top" |
*[[Toolpack:Creating_a_TCAP_Stack C|Create a TCAP Stack]]
**[[Toolpack:Creating_a_TCAP_Userpart C| Create a TCAP Userpart]]
*[[Toolpack:Activating_the_Configuration D|Activating the Configuration]]

|}

=SIGTRAN=
Sigtran relays TDM signaling over IP.

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

'''M2UA'''

{| 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) Create Line 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 2) Create MTP2 links
! 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) Create M2UA configuration

|-

| 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" |

*[[Toolpack:Creating_an_MTP2_Configuration D|Create an MTP2 Configuration]]
**[[Toolpack:Creating_MTP2_Links C|Create MTP2 Links]]

| valign="top" |

*[[Toolpack:Creating the SCTP Configuration D|Create the SCTP Configuration]]
*[[Toolpack:Creating the M2UA Configuration D|Create an M2UA Configuration]]
**[[Toolpack:Creating an M2UA SAP C|Create an M2UA SAP]]
**[[Toolpack:Creating an M2UA Cluster C|Create an M2UA Cluster]]
**[[Toolpack:Creating M2UA Links C|Create M2UA Links]]
**[[Toolpack:Creating M2UA Peers C|Create M2UA Peers]]

|}

'''M3UA'''

{| 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) Create Line 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 2) Create MTP2 links
! 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) Create MTP3 configuration
! 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) Create M3UA configuration
|-

| 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" |
*[[Toolpack:Creating_an_MTP2_Configuration D|Create an MTP2 Configuration]]
*[[Toolpack:Creating_MTP2_Links C|Create MTP2 Links]]

| valign="top" |
*[[Toolpack:Creating SS7 Point Codes E|Create SS7 Point Codes]]
*[[Toolpack:Creating an MTP3 Configuration E|Create an MTP3 Configuration]]
**[[Toolpack:Creating an MTP3 Network D|Create an MTP3 Network]]
**[[Toolpack:Creating an MTP3 Linkset C|Create an MTP3 Linkset]]
**[[Toolpack:Creating MTP3 Links (M3UA) C|Create MTP3 Links]]
**[[Toolpack:Creating an MTP3 Route C|Create an MTP3 Route]]

| valign="top" |
*[[Toolpack:Creating the SCTP Configuration D|Edit the SCTP Configuration]]
*[[Toolpack:Creating an M3UA Configuration E|Create an M3UA Configuration]]
**[[Toolpack:Creating an M3UA SAP D|Create an M3UA SAP]]
**[[Toolpack:Creating an M3UA Network D|Create an M3UA Network]]
**[[Toolpack:Creating an M3UA User Part D|Create an M3UA User Part]]
**[[Toolpack:Creating an M3UA Peer Signalling Process D|Create an M3UA Peer Signalling Process]]
**[[Toolpack:Creating an M3UA Peer Server D|Create an M3UA Peer Server]]
**[[Toolpack:Creating an M3UA Route D|Create an M3UA Route]] 

|}

'''IUA'''

{| 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) Create Line 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 2) Create IUA Configuration

|-

| 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" |
*[[Toolpack:Creating the SCTP Configuration D|Create the SCTP Configuration]]
*[[Toolpack:Creating the IUA Configuration D|Create an IUA Configuration]]
**[[Toolpack:Creating an IUA SAP C|Create an IUA SAP]]
**[[Toolpack:Creating an IUA Cluster C|Create an IUA Cluster]]
**[[Toolpack:Creating IUA Links C|Create IUA Links]]
**[[Toolpack:Creating IUA Peers C|Create IUA Peers]]

|}

<div class="mw-collapsible mw-collapsed" data-collapsetext="Sigtran Service Affecting Parameters" data-expandtext="Click here for Sigtran Service Affecting Parameters" style="width: 400px;">
 
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)
</div>

=H.248 MEGACO=
H.248 is a protocol used to interface a softswitch with a media gateway.

'''Media'''

'''TDM NAP (for ISUP/ISDN)'''

{| 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) Allocate TDM 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 2) 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 3) 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" |
*[[Toolpack:Modify_NAP_profile F|Modify profile]]
| valign="top" |
*[[Toolpack:Allocating_a_TDM_Network_Access_Point_(NAP) D|Allocate a TDM NAP]]
|}

'''VOIP NAP (for SIP)'''

{| 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) Create IP Port Ranges
! 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) 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 3) Configure Network Access Points (NAPs)
|-
| valign="top" |
*[[Toolpack:Creating_an_IP_Port_Range D|Create IP port ranges]]
| valign="top" |
*[[Toolpack:Modify_NAP_profile F|Modify profile]]
| valign="top" |
*[[Toolpack:Allocating_a_VoIP_Network_Access_Point_(NAP) D|Allocate a VoIP NAP]]
|}

'''CAS NAP'''
{| 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) 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 2) Configuring a CAS stack
! 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) 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 4) Configure Network Access Points (NAPs)

|-
| valign="top" |
*[[Toolpack:Creating_a_Line_Interface D|Create Line Interfaces]]
*[[Toolpack:Creating_a_Line_Service D|Create Line Service]]
*[[Toolpack:Creating_a_System_Clock A|Create System Clock]]
| valign="top" |
*[[Toolpack:Copy variant script D|Copy variant script]]
*[[Toolpack:Create CAS R2 stack D|Create CAS stack]]
*Edit the [[CASr1_scripting|CAS R1_A]] or [[CAS R2 scripting|CAS R2_A]] script to adapt the variant
**[[CASr1_scripting#TONE_USE_DTMF_A|Select CAS R1 tone type]]
**[[Toolpack:Setting CAS R2 BACK DIGITS variable D|Set CAS R2 backward digits string]]
| valign="top" |
*[[Toolpack:Modify_NAP_profile F|Modify profile]]
| valign="top" |
*[[Toolpack:Creating_a_CAS_R2_NAP D|Create a CAS NAP]]

|}

'''Media Gateway'''

{| 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) Configure Media Gateway for H.248 mode
! 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) Add a New Media Gateway Controller
! 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) Associate NAPs Resources to H.248 Configuration

|-

| valign="top" |
*[[Toolpack:Creating_an_H.248_Configuration D|Create a new H.248 configuration]]
| valign="top" |
*[[Toolpack:Adding_a_Media_Gateway_Controller_(MGC) C|Add a new media gateway controller (MGC)]]
| valign="top" |
*[[Toolpack:Associating_NAPs_with_an_H.248_Configuration D|Associate the NAPs with the H.248 configuration]]
*[[Toolpack:Selecting_Timeslots_for_TDM_Interfaces C|Select timeslots for the TDM interfaces ]]

|}

Please note when modifying '''[[Toolpack: H248 Service Affecting Parameters|H.248 Service Affecting Parameters]]''' the H.248 stack will be deallocated and reallocated, resulting in a loss of active calls. Be careful when changing these parameters

=Protocol Interoperability=

'''Early Media'''

{| cellpadding="5" border="1" class="wikitable"
! width="240" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Q.1912.5 Profile A-B
|-
| valign="top" |
*[[Toolpack:Configure_Early_Media_Q1912_A_B_NAP__A|Configure NAP ]]
*[[Toolpack:Configure_Early_Media_Q1912_A_B_Profile_A_|Configure Profile]]
|}

<headertabs/>

'''{{#switchtablink:Protocol Stack|Return to Web Portal 3.2 Home Page|Tmedia_Tsig_Tdev_Tutorial_Guide_v3.2}}'''

Toolpack: H248 Service Affecting Parameters

2024-03-28T08:06:25Z

Joshua Puckett: Created page with "{{DISPLAYTITLE:H.248 Service Affecting Parameters}} {| class="wikitable" |- |rowspan="3"|This article applies to: |'''Product''' |'''Version''' |- |Tmedia |3.0, 3.2 |} ==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: Image:Edit_H248_0.png *Transport Protocol **Parameter: Transport Protocol Type|Tr..."

{{DISPLAYTITLE:H.248 Service Affecting Parameters}}
{| class="wikitable"
|-
|rowspan="3"|This article applies to:
|'''Product'''
|'''Version'''
|-
|Tmedia
|3.0, 3.2
|}
==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: 

[[Image:Edit_H248_0.png]]

 
*Transport Protocol
**[[Parameter: Transport Protocol Type|Transport Protocol Type]]
**[[Parameter: Public IP Address|Public IP Address]]
**[[Parameter: Use IP interface|Use IP interface]]
**[[Parameter: Local IP Address|Local IP Address]]
**[[Parameter: Local Port to Receive for Text Encoding|Local Port to Receive for Text Encoding]]
**[[Parameter: IP ToS value|IP ToS value]]
 
*Advanced Parameters
**[[Parameter: Maximum Number of TDM Terminations|Maximum Number of TDM Terminations]]
**[[Parameter: Maximum Number of Ephemeral Terminations|Maximum Number of Ephemeral Terminations]]
**[[Parameter: Default MEGACO version|Default MEGACO version]]
**[[Parameter: Maximum Number of DNS Pending Requests|Maximum Number of DNS Pending Requests]]
**[[Parameter: Ephemeral Termination Identifier Root|Ephemeral Termination Identifier Root]]
**[[Parameter: Ephemeral Termination Identifier Maximum Value|Ephemeral Termination Identifier Maximum Value]]
**[[Parameter: Number of Worker Threads|Number of Worker Threads]]
 
*Profile
**[[Parameter: Enabled|Enabled]]
**[[Parameter: Profile Name|Profile Name]]
**[[Parameter: Profile Version|Profile Version]]
 
*Timers
**[[Parameter: Dialing Start Timer Value|Dialing Start Timer Value]]
**[[Parameter: Dialing Short Timer Value|Dialing Short Timer Value]]
**[[Parameter: Dialing Long Timer Value|Dialing Long Timer Value]]
**[[Parameter: Dialing Duration Timer Value|Dialing Duration Timer Value]]
**[[Parameter: Restart Timer Value to Retry Controller Association|Restart Timer Value to Retry Controller Association]]
**[[Parameter: Local Response Timer Value|Local Response Timer Value]]
**[[Parameter: Inactivity Timer Value|Inactivity Timer Value]]

Toolpack:Creating an H.248 Configuration D

2024-03-28T07:35:24Z

Joshua Puckett: Add new options, Improve layout, add slight narrative.

{{DISPLAYTITLE:Creating an H.248 Configuration}}
{| class="wikitable"
|-
|rowspan="3"|This article applies to:
|'''Product'''
|'''Version'''
|-
|Tmedia
|2.9, 2.10, 3.0, 3.2
|}

After you create the necessary VoIP and TDM NAPs, you can create an H.248 configuration. 

1- Click '''H248''' in the navigation panel

[[Image:Create_H248_0.png]]

2- Create the new configuration:

* Select a '''transport protocol type'''
* Enter a '''public IP address'''
* Enter a '''private IP address'''
* Click '''Create'''

[[Image:Create_H248_1.png]]

3- For 1+1 systems, open the "Advanced Parameters" and then "Behavior" section and make sure this option is checked:
No failover service changes

4- Verify that the '''"TbgwH248Cfg was successfully created"''' message appears

[[Image:Create_H248_2.png]]

NOTE: After creating the H.248 Configuration the Advanced Parameters will split into two sections to indicate which parameters will cause active calls to drop. These are labled as [[Toolpack: H248 Service Affecting Parameters|H.248 Service Affecting Parameters]]

Please reference the complete list of Paramters below before adding [[Toolpack:Adding_a_Media_Gateway_Controller_(MGC) C|Adding a media gateway controller (MGC)]] and [[Toolpack:Associating_NAPs_with_an_H.248_Configuration D|Associating the NAPs with the H.248 configuration]]

[[Image:Edit_H248_0.png]]

==Full List of Parameters==
*[[Parameter: Enabled|Enabled]]
'''Transport Protocol''' 
*[[Parameter: Transport Protocol Type|Transport Protocol Type]]
*[[Parameter: Public IP Address|Public IP Address]]
*[[Parameter: Use IP interface|Use IP interface]]
*[[Parameter: Local IP Address|Local IP Address]]
*[[Parameter: Local Port to Receive for Text Encoding|Local Port to Receive for Text Encoding]]
*[[Parameter: IP ToS value|IP ToS value]] 
'''Advanced Parameters''' 
*Behavior
**[[Parameter: Relay Unknown H248 Parameters|Relay Unknown H248 Parameters]]
**[[Parameter: Compact H248 Descriptor Headers|Compact H248 Descriptor Headers]]
**[[Parameter: Send Transaction Response Acks|Send Transaction Response Acks]]
**[[Parameter: Send Transaction Response Acks Immediately|Send Transaction Response Acks Immediately]]
**[[Parameter: Send Transaction Pending Automatically|Send Transaction Pending Automatically]]
**[[Parameter: No Remote Response|No Remote Response]]
**[[Parameter: Null Terminating H248 Message|Null Terminating H248 Message]]
**[[Parameter: No Only Ephemeral|No Only Ephemeral]]
**[[Parameter: Loose H248 Message Decoding|Loose H248 Message Decoding]]
**[[Parameter: Transparent SDP|Transparent SDP]]
**[[Parameter: No SCTP Send Acknowledge|No SCTP Send Acknowledge]]
**[[Parameter: No failover service changes|No failover service changes]]
**[[Parameter: Observe default CAS events|Observe default CAS events]] 
*Analog display
**[[Parameter: FSK Variant|FSK Variant]]
**[[Parameter: FSK Level|FSK Level]]
**[[Parameter: Mark Bytes sent before FSK message|Mark Bytes sent before FSK message]]
**[[Parameter: Seizure Bytes Used before Mark Bytes|Seizure Bytes Used before Mark Bytes]] 
*[[Parameter: Maximum Number of Retransmissions|Maximum Number of Retransmissions]]
*[[Parameter: Serialize null context commands|Serialize null context commands]]
*[[Parameter: Allow wildcard in service change|Allow wildcard in service change]]
*[[Parameter: Switch to Passthrough on tdm/ec=OFF|Switch to Passthrough on tdm/ec=OFF]]
*[[Parameter: IP Lawful Interception ToS value|IP Lawful Interception ToS value]]
*[[Parameter: Maximum Number of TDM Terminations|Maximum Number of TDM Terminations]]
*[[Parameter: Maximum Number of Ephemeral Terminations|Maximum Number of Ephemeral Terminations]]
*[[Parameter: Default MEGACO version|Default MEGACO version]]
*[[Parameter: Maximum Number of DNS Pending Requests|Maximum Number of DNS Pending Requests]]
*[[Parameter: Ephemeral Termination Identifier Root|Ephemeral Termination Identifier Root]]
*[[Parameter: Ephemeral Termination Identifier Maximum Value|Ephemeral Termination Identifier Maximum Value]]
*[[Parameter: Number of Worker Threads|Number of Worker Threads]] 
*Profile
**[[Parameter: Enabled|Enabled]]
**[[Parameter: Profile Name|Profile Name]]
**[[Parameter: Profile Version|Profile Version]] 
*Timers
**[[Parameter: Default Sent Transaction Timer Value|Default Sent Transaction Timer Value]]
**[[Parameter: Maximum Sent Transaction Timer Value|Maximum Sent Transaction Timer Value]]
**[[Parameter: Provisional Reply Transaction Timer Value|Provisional Reply Transaction Timer Value]]
**[[Parameter: Saved Replied Transaction Timer Value|Saved Replied Transaction Timer Value]]
**[[Parameter: Dialing Start Timer Value|Dialing Start Timer Value]]
**[[Parameter: Dialing Short Timer Value|Dialing Short Timer Value]]
**[[Parameter: Dialing Long Timer Value|Dialing Long Timer Value]]
**[[Parameter: Dialing Duration Timer Value|Dialing Duration Timer Value]]
**[[Parameter: Restart Timer Value to Retry Controller Association|Restart Timer Value to Retry Controller Association]]
**[[Parameter: Local Response Timer Value|Local Response Timer Value]]
**[[Parameter: Inactivity Timer Value|Inactivity Timer Value]] 

<div class="mw-collapsible mw-collapsed" data-collapsetext="Click to Collapse H248 API and Northbound Interface Configuration" data-expandtext="Click to Expand H248 API and Northbound Interface Configuration">

'''Path'''
<pre>
/configurations/@[configuration_name]/h248_stacks/@[h248_stack]
</pre>

'''Parameters (text)'''
<pre>
/configurations/@[configuration_name]/h248_stacks/@[h248_stack]
enabled = true
naps = [ ]

/configurations/@[configuration_name]/h248_stacks/@[h248_stack]/advanced_parameters
allow_wildcard_in_service_change = true
default_megaco_version = 2
ephemeral_termination_identifier_maximum_value = 4294967295
ephemeral_termination_identifier_root = "IP/"
maximum_number_of_dns_pending_requests = 5
maximum_number_of_ephemeral_terminations = 2048
maximum_number_of_retransmissions = 11
maximum_number_of_tdm_terminations = 2048
serialize_null_context_commands = false
switch_to_passthrough_on_tdm_ec_off = true

/configurations/@[configuration_name]/h248_stacks/@[h248_stack]/advanced_parameters/behavior
compact_h248_descriptor_headers = false
loose_h248_message_decoding = false
no_only_ephemeral = false
no_remote_response = false
no_sctp_send_acknowledge = false
no_warm_service_change = false
null_terminating_h248_message = false
relay_unknown_h248_parameters = false
send_transaction_pending_automatically = false
send_transaction_response_acks = false
send_transaction_response_acks_immediately = true
transparent_sdp = true

/configurations/@[configuration_name]/h248_stacks/@[h248_stack]/advanced_parameters/profile
profile_enabled = false
profile_name = ""
profile_version = ""

/configurations/@[configuration_name]/h248_stacks/@[h248_stack]/timers
default_sent_transaction_timer = "500 milliseconds"
dialing_duration_timer = "5 seconds"
dialing_long_timer = "15 seconds"
dialing_short_timer = "5 seconds"
dialing_start_timer = "30 seconds"
inactivity_timer = "30 seconds"
local_response_timer = "10 seconds"
maximum_sent_transaction_timer = "4 seconds"
provisional_reply_transaction_timer = "6 seconds"
restart_timer_value_to_retry_controller_association = "30 seconds"
saved_replied_transaction_timer = "30 seconds"

/configurations/@[configuration_name]/h248_stacks/@[h248_stack]/transport_protocol
ip_interface = ""
ip_tos_value = 0
local_ip_address = "@[address_number]"
local_port_to_receive_for_text_encoding = 2944
public_ip_address = "@[address_number]"
transport_protocol_type = "UDP"
use_ip_interface = false

/configurations/@[configuration_name]/h248_stacks/@[h248_stack]/transport_protocol/sctp_parameters
checksum_type = "AUTODETECT"
maximum_number_of_association_per_instance = 5
maximum_number_of_init_cookie_echo_chunk_retransmission = 8
maximum_number_of_input_sctp_streams = 32
maximum_number_of_instance_sapi = 2
maximum_number_of_ip_address_per_instance = 2
maximum_number_of_output_sctp_streams = 5
maximum_number_of_packets_sent_when_transmitting_new_data_chunks = 4
maximum_number_of_retransmission_per_association = 10
maximum_number_of_retransmission_per_path = 5
maximum_number_of_sctp_responses_waiting_for_acknowledge = 5
maximum_number_of_streams_per_association = 4
number_of_network_interface_card = 2
</pre>

'''Parameters (json)'''
<pre>
{
"advanced_parameters" : {
"allow_wildcard_in_service_change" : true,
"behavior" : {
"compact_h248_descriptor_headers" : false,
"loose_h248_message_decoding" : false,
"no_only_ephemeral" : false,
"no_remote_response" : false,
"no_sctp_send_acknowledge" : false,
"no_warm_service_change" : false,
"null_terminating_h248_message" : false,
"relay_unknown_h248_parameters" : false,
"send_transaction_pending_automatically" : false,
"send_transaction_response_acks" : false,
"send_transaction_response_acks_immediately" : true,
"transparent_sdp" : true
},
"default_megaco_version" : 2,
"ephemeral_termination_identifier_maximum_value" : 4294967295,
"ephemeral_termination_identifier_root" : "IP/",
"maximum_number_of_dns_pending_requests" : 5,
"maximum_number_of_ephemeral_terminations" : 2048,
"maximum_number_of_retransmissions" : 11,
"maximum_number_of_tdm_terminations" : 2048,
"profile" : {
"profile_enabled" : false,
"profile_name" : "",
"profile_version" : ""
},
"serialize_null_context_commands" : false,
"switch_to_passthrough_on_tdm_ec_off" : true
},
"enabled" : true,
"naps" : [
],
"timers" : {
"default_sent_transaction_timer" : "500 milliseconds",
"dialing_duration_timer" : "5 seconds",
"dialing_long_timer" : "15 seconds",
"dialing_short_timer" : "5 seconds",
"dialing_start_timer" : "30 seconds",
"inactivity_timer" : "30 seconds",
"local_response_timer" : "10 seconds",
"maximum_sent_transaction_timer" : "4 seconds",
"provisional_reply_transaction_timer" : "6 seconds",
"restart_timer_value_to_retry_controller_association" : "30 seconds",
"saved_replied_transaction_timer" : "30 seconds"
},
"transport_protocol" : {
"ip_interface" : "",
"ip_tos_value" : 0,
"local_ip_address" : "@[address_number]",
"local_port_to_receive_for_text_encoding" : 2944,
"public_ip_address" : "@[address_number]",
"sctp_parameters" : {
"checksum_type" : "AUTODETECT",
"maximum_number_of_association_per_instance" : 5,
"maximum_number_of_init_cookie_echo_chunk_retransmission" : 8,
"maximum_number_of_input_sctp_streams" : 32,
"maximum_number_of_instance_sapi" : 2,
"maximum_number_of_ip_address_per_instance" : 2,
"maximum_number_of_output_sctp_streams" : 5,
"maximum_number_of_packets_sent_when_transmitting_new_data_chunks" : 4,
"maximum_number_of_retransmission_per_association" : 10,
"maximum_number_of_retransmission_per_path" : 5,
"maximum_number_of_sctp_responses_waiting_for_acknowledge" : 5,
"maximum_number_of_streams_per_association" : 4,
"number_of_network_interface_card" : 2
},
"transport_protocol_type" : "UDP",
"use_ip_interface" : false
}
}
</pre>
</div>

Toolpack:Protocol Stack Settings E

2024-03-28T07:01:38Z

Joshua Puckett: /* H.248 MEGACO */

{{DISPLAYTITLE:Tmedia, Tdev, and Tsig Web Portal 3.2: Protocol Stacks}}
__NOTOC__
=ISDN FAS and NFAS=

{| 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) 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 2) Configure ISDN-PRI Signaling

! 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) 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 4) 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" |
*[[Toolpack:Configuring_an_ISDN_Stack F|Configure an ISDN stack]]
OR 
*[[Toolpack:Configuraing_NFAS D|Configure NFAS]]

| valign="top" |
*[[Toolpack:Modify_NAP_profile F|Modify profile]]

| valign="top" |
*[[Toolpack:Allocating_an_ISDN_Network_Access_Point_(NAP) F|Allocate an ISDN NAP]]

|}

'''ISDN Advanced Features'''

{| 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;" |ISDN Overlap Sending
|-
| valign="top" |
*[[Toolpack:Configuring_Overlap C|ISDN NFAS Overlap Parameters]]
|}

=CAS=

{| 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) 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 2) Configuring a CAS stack
! 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) 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 4) 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" |
*[[Toolpack:Copy variant script D|Copy variant script]]
*[[Toolpack:Create CAS R2 stack E|Create CAS stack]]
*Edit the [[CASr1_scripting|CAS R1]] or [[CAS R2 scripting|CAS R2]] script to adapt the variant
**[[CASr1_scripting#TONE_USE_DTMF|Select CAS R1 tone type]]
**[[Toolpack:Setting CAS R2 BACK DIGITS variable D|Set CAS R2 backward digits string]]
| valign="top" |
*[[Toolpack:Modify_NAP_profile F|Modify profile]]
| valign="top" |
*[[Toolpack:Creating_a_CAS_R2_NAP D|Create a CAS NAP]]

|}

=SIP=

{| 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) Configure IP port range
! 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) Configure SIP Signaling
! 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) 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 4) Configure Network Access Points (NAPs)
|-
| valign="top" |
*[[Toolpack:Creating_an_IP_Port_Range D|Create an IP port range]]

| valign="top" |
*[[Toolpack:Creating_a_SIP_Stack D|Create a SIP stack]]
*[[Toolpack:Creating_a_SIP_Transport_Server D|Create a SIP transport server]]

| valign="top" |
*[[Toolpack:Modify_NAP_profile F|Modify profile]]

| valign="top" |
*[[Toolpack:Allocating_a_SIP_Network_Access_Point_(NAP) F|Allocate a SIP NAP]]

|}

'''SIP Advanced Features'''
{| 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;" | SIP-I SIP-T
|-
| valign="top" |
*[[Enabling_SIP_I_SIP_T D|Enable SIP-I SIP-T]]
|}

{| 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;" | SIP Spiral and other SIP quirks
|-
| valign="top" |
*[[Enabling_SIP_Spiral D|Enable SIP Spiral]]
|}

{| 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;" | Remote NAT Traversal
! 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;" | Local NAT Traversal
|-
| valign="top" |
*[[Enabling_Remote_NAT_Traversal_C|Enable Remote NAT Traversal]]

| valign="top" |
*[[Enabling_Local_NAT_Traversal_C|Enable Local NAT Traversal]]
|}

{| 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;" | DNS
|-
| valign="top" |
*[[Toolpack:Configuring_DNS_Parameters_C|Enable DNS]]
|}

{| 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;" | SIP Authentication
|-
| valign="top" |
*[[Toolpack:Configuring_SIP_Authentication_A|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

=SS7 ISUP=

'''MTP2-MTP3-ISUP'''

{| 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) 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 2) Configuring the MTP2 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) 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 4) 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 5) 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 6) 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" |
*[[Toolpack:Creating_an_MTP2_Configuration D|Create an MTP2 Configuration]]
*[[Toolpack:Creating_MTP2_Links C|Create MTP2 Links]]

| valign="top" |
*[[Toolpack:Creating_an_MTP3_Configuration E|Create an MTP3 Configuration]]
*[[Toolpack:Creating_an_MTP3_Network D|Create an MTP3 Network Network]]
**[[Toolpack:Creating_SS7_Point_Codes E|Create an MTP3 Point Code]]
**[[Toolpack:Creating_an_MTP3_Linkset C|Create an MTP3 Linkset]]
***[[Toolpack:Creating_MTP3_Links C|Create MTP3 Links]]
**[[Toolpack:Creating_an_MTP3_Route C|Create an MTP3 Route]]

| valign="top" |
*[[Toolpack:Creating_an_ISUP_Stack D|Create an ISUP Stack]]
*[[Toolpack:Creating_an_ISUP_Network C|Create an ISUP Network]]
*[[Toolpack:Creating_an_ISUP_User_Part C|Create an ISUP User Part]]
*[[Toolpack:Creating_an_ISUP_Interface C|Create an ISUP Interface]]
*[[Toolpack:Creating ISUP CIC Groups C|Create ISUP CIC Groups]]

| valign="top" |
*[[Toolpack:Modify_NAP_profile F|Modify profile]]

| valign="top" |
*[[Toolpack:Creating_a_NAP_(SIGTRAN)_D|Create an ISUP NAP]]

|}

'''M2PA-MTP3-ISUP'''

{| 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) 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 2) 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 3) 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 4) 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 5) 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 6) 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" |
*[[Toolpack:Creating the SCTP Configuration D|Create the SCTP Configuration]]
*[[Toolpack:Creating the M2PA Configuration D|Create an M2PA Configuration]]
**[[Toolpack:Creating an M2PA SAP D|Create an M2PA SAP]]
**[[Toolpack:Adding M2PA Links C|Add M2PA Links]]

| valign="top" |
*[[Toolpack:Creating_an_MTP3_Configuration E|Create an MTP3 Configuration]]
*[[Toolpack:Creating_an_MTP3_Network D|Create an MTP3 Network]]
**[[Toolpack:Creating_SS7_Point_Codes E|Create an MTP3 Point Code]]
**[[Toolpack:Creating_an_MTP3_Linkset C|Create an MTP3 Linkset]]
***[[Toolpack:Creating_MTP3_Links C|Create MTP3 Links]]
**[[Toolpack:Creating_an_MTP3_Route C|Create an MTP3 Route]]

| valign="top" |
*[[Toolpack:Creating_an_ISUP_Stack D|Create an ISUP Stack]]
*[[Toolpack:Creating_an_ISUP_Network C|Create an ISUP Network]]
*[[Toolpack:Creating_an_ISUP_User_Part C|Create an ISUP User Part]]
*[[Toolpack:Creating_an_ISUP_Interface C|Create an ISUP Interface]]
*[[Toolpack:Creating ISUP CIC Groups C|Create ISUP CIC Groups]]

| valign="top" |
*[[Toolpack:Modify_NAP_profile F|Modify profile]]

| valign="top" |
*[[Toolpack:Creating_a_NAP_(SIGTRAN)_D|Create an ISUP NAP]]

|}

'''MTP2-MTP3-M2PA (TDM/IP STP)'''

{| 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) 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 2) Create MTP2 links
! 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) 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 4) Configuring the MTP3 Layer

|-
| 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" |

*[[Toolpack:Creating_an_MTP2_Configuration D|Create an MTP2 Configuration]]
**[[Toolpack:Creating_MTP2_Links C|Create MTP2 Links]]

| valign="top" |
*[[Toolpack:Creating the SCTP Configuration D|Create the SCTP Configuration]]
*[[Toolpack:Creating the M2PA Configuration D|Create an M2PA Configuration]]
**[[Toolpack:Creating an M2PA SAP D|Create an M2PA SAP]]
**[[Toolpack:Adding M2PA Links C|Add M2PA Links]]

| valign="top" |
*[[Toolpack:Creating_an_MTP3_Configuration_for_STP|Create an MTP3 Configuration for STP]]
*[[Toolpack:Creating_an_MTP3_Network D|Create an MTP3 Network]]
**[[Toolpack:Creating_SS7_Point_Codes E|Create an MTP3 Point Code]]
**[[Toolpack:Creating_an_MTP3_Linkset C|Create an MTP3 Linkset]]
***[[Toolpack:Creating_MTP3_Links C|Create MTP3 Links]]
**[[Toolpack:Creating_an_MTP3_Route_for_STP|Create an MTP3 Route for STP]]

|}

'''M2UA-MTP2 Relay'''

{| 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) Create Line 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 2) Create MTP2 links
! 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) Create M2UA configuration
|-

| 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" |

*[[Toolpack:Creating_an_MTP2_Configuration D|Create an MTP2 Configuration]]
**[[Toolpack:Creating_MTP2_Links C|Create MTP2 Links]]

| valign="top" |

*[[Toolpack:Creating the SCTP Configuration D|Create the SCTP Configuration]]
*[[Toolpack:Creating the M2UA Configuration D|Create an M2UA Configuration]]
**[[Toolpack:Creating an M2UA SAP C|Create an M2UA SAP]]
**[[Toolpack:Creating an M2UA Cluster C|Create an M2UA Cluster]]
**[[Toolpack:Creating M2UA Links C|Create M2UA Links]]
**[[Toolpack:Creating M2UA Peers C|Create M2UA Peers]]
|}

'''M2UA-MTP3-ISUP'''

{| 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) Create M2UA configuration
! 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) 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) 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) 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) Configure Network Access Points (NAPs)
|-

| valign="top" |

*[[Toolpack:Creating the SCTP Configuration D|Create the SCTP Configuration]]
*[[Toolpack:Creating the M2UA Configuration D|Create an M2UA Configuration]]
**[[Toolpack:Creating an M2UA SAP C|Create an M2UA SAP]]
**[[Toolpack:Creating an M2UA Cluster C|Create an M2UA Cluster]]
**[[Toolpack:Creating M2UA Links C|Create M2UA Links]]
**[[Toolpack:Creating M2UA Peers C|Create M2UA Peers]]

| valign="top" |
*[[Toolpack:Creating_an_MTP3_Configuration E|Create an MTP3 Configuration]]
*[[Toolpack:Creating_an_MTP3_Network D|Create an MTP3 Network]]
**[[Toolpack:Creating_SS7_Point_Codes E|Create an MTP3 Point Code]]
**[[Toolpack:Creating_an_MTP3_Linkset C|Create an MTP3 Linkset]]
***[[Toolpack:Creating_MTP3_Links C|Create MTP3 Links]]
**[[Toolpack:Creating_an_MTP3_Route C|Create an MTP3 Route]]

| valign="top" |
*[[Toolpack:Creating_an_ISUP_Stack D|Create an ISUP Stack]]
*[[Toolpack:Creating_an_ISUP_Network C|Create an ISUP Network]]
*[[Toolpack:Creating_an_ISUP_User_Part C|Create an ISUP User Part]]
*[[Toolpack:Creating_an_ISUP_Interface C|Create an ISUP Interface]]
*[[Toolpack:Creating ISUP CIC Groups C|Create ISUP CIC Groups]]

| valign="top" |
*[[Toolpack:Modify_NAP_profile F|Modify profile]]

| valign="top" |
*[[Toolpack:Creating_a_NAP_(SIGTRAN)_D|Create an ISUP NAP]]
|}

'''M3UA-ISUP'''

{| 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) 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 2a) Configuring the M3UA Layer - IPSP
! 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 2b) Configuring the M3UA Layer - ASP
! 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 2c) Configuring the M3UA Layer - SGP
! 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) 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) 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) 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" |
*[[Toolpack:Creating the SCTP Configuration D|Create the SCTP Configuration]]
*[[Toolpack:Creating SS7 Point Codes E|Create SS7 Point Codes]]
*[[Toolpack:Creating an M3UA Configuration (IPSP) D|Create an M3UA Configuration]]
**[[Toolpack:Creating an M3UA SAP (IPSP) C|Create an M3UA SAP]]
**[[Toolpack:Creating an M3UA Network (IPSP) C|Create an M3UA Network]]
**[[Toolpack:Creating_an_M3UA_User_Part_(IPSP)_C|Create an M3UA User Part]]
**[[Toolpack:Creating an M3UA Peer Signalling Process (IPSP) C|Create an M3UA Peer Signalling Process]]
**[[Toolpack:Creating_an_M3UA_Peer_Server_(IPSP)_C|Create an M3UA Peer Server]]
**[[Toolpack:Creating an M3UA Route (IPSP) C|Create an M3UA Route]]

| valign="top" |
*[[Toolpack:Creating the SCTP Configuration D|Create the SCTP Configuration]]
*[[Toolpack:Creating SS7 Point Codes E|Create SS7 Point Codes]]
*[[Toolpack:Creating an M3UA Configuration ASP D|Create an M3UA Configuration]]
**[[Toolpack:Creating an M3UA SAP (ASP)|Create an M3UA SAP]]
**[[Toolpack:Creating an M3UA Network (ASP) |Create an M3UA Network]]
**[[Toolpack:Creating an M3UA User Part (ASP) C|Create an M3UA User Part]]
**[[Toolpack:Creating an M3UA Peer Signalling Process (ASP) C|Create an M3UA Peer Signalling Process]]
**[[Toolpack:Creating an M3UA Peer Server (ASP) C|Create an M3UA Peer Server]]
**[[Toolpack:Creating an M3UA Route (ASP) C|Create an M3UA Route]]

| valign="top" |
*[[Toolpack:Creating the SCTP Configuration D|Create the SCTP Configuration]]
*[[Toolpack:Creating SS7 Point Codes E|Create SS7 Point Codes]]
*[[Toolpack:Creating an M3UA Configuration SGP D|Create an M3UA Configuration]]
**[[Toolpack:Creating an M3UA SAP (SGP)|Create an M3UA SAP]]
**[[Toolpack:Creating an M3UA Network (SGP) |Create an M3UA Network]]
**[[Toolpack:Creating an M3UA User Part (SGP) C|Create an M3UA User Part]]
**[[Toolpack:Creating an M3UA Peer Signalling Process (SGP) C|Create an M3UA Peer Signalling Process]]
**[[Toolpack:Creating an M3UA Peer Server (SGP) C|Create an M3UA Peer Server]]
**[[Toolpack:Creating an M3UA Route (SGP) C|Create an M3UA Route]]

| valign="top" |
*[[Toolpack:Creating_an_ISUP_Stack D|Create an ISUP Stack]]
*[[Toolpack:Creating_an_ISUP_Network C|Create an ISUP Network]]
*[[Toolpack:Creating_an_ISUP_User_Part C|Create an ISUP User Part]]
*[[Toolpack:Creating_an_ISUP_Interface C|Create an ISUP Interface]]
*[[Toolpack:Creating ISUP CIC Groups C|Create ISUP CIC Groups]]

| valign="top" |
*[[Toolpack:Modify_NAP_profile F|Modify profile]]

| valign="top" |
*[[Toolpack:Creating_a_NAP_(SIGTRAN)_D|Create an ISUP NAP]]

|}

'''SS7 Advanced Features'''

{| 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;" | Configuring SPIROU
|-
| valign="top" |
*[[Toolpack:Modifying_Profile_for_SPIROU B|Modifying Profile]]
*[[Toolpack:Modifying_Gateway_Configurations_for_SPIROU C|Modifying Gateway Configurations]]
*[[Toolpack:Modifying_ISUP_Stack_for_SPIROU B|Modifying ISUP Stack]]
*[[Toolpack:Modifying_ISUP_Userpart_for_SPIROU B|Modifying ISUP Userpart]]
*[[Toolpack:Optional_configurations_for_SPIROU A|Optional modifications]]
|}

'''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

=SCCP-TCAP=

'''MTP2-MTP3-SCCP-TCAP'''

{| 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) 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 2) Configuring the MTP2 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) 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 4) Configuring the SCCP 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 5) Configuring the TCAP Layer (optional)

|-

| 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" |
*[[Toolpack:Creating_an_MTP2_Configuration D|Create an MTP2 Configuration]]
*[[Toolpack:Creating_MTP2_Links C|Create an MTP2 Link]]

| valign="top" |
*[[Toolpack:Creating_an_MTP3_Configuration E|Create an MTP3 Configuration]]
*[[Toolpack:Creating_an_MTP3_Network D|Create an MTP3 Network]]
**[[Toolpack:Creating_SS7_Point_Codes E|Create an MTP3 Point Code]]
**[[Toolpack:Creating_an_MTP3_Linkset C|Create an MTP3 Linkset]]
***[[Toolpack:Creating_MTP3_Links C|Create MTP3 Links]]
**[[Toolpack:Creating_an_MTP3_Route C|Create an MTP3 Route]]

| valign="top" |
*[[Toolpack:Creating_an_SCCP_Stack C| Create an SCCP Stack]]
*[[Toolpack:Creating_an_SCCP_Network C|Create an SCCP Network]]
**[[Toolpack:Creating_an_SCCP_Userpart C|Create an SCCP Userpart]]
**[[Toolpack:Creating_an_SCCP_LSAP C|Create an SCCP LSAP]]
***[[Toolpack:Creating_an_SCCP_Route C|Create an SCCP Route]]
****[[Toolpack:Creating_an_SCCP_SSN C|Create an SCCP SSN]]
*[[Toolpack:Creating_an_SCCP_GTT_Association C|Create an SCCP GTT Association]]
**[[Toolpack:Creating_an_SCCP_GTT_Association_Action A|Create an SCCP GTT Association Action]]
**[[Toolpack:Creating_an_SCCP_GTT_Address_Map C|Create an SCCP GTT Address Map]]

| valign="top" |
*[[Toolpack:Creating_a_TCAP_Stack C|Create a TCAP Stack]]
**[[Toolpack:Creating_a_TCAP_Userpart C| Create a TCAP Userpart]]
*[[Toolpack:Activating_the_Configuration D|Activating the Configuration]]

|}

'''M2PA-MTP3-SCCP-TCAP'''

{| 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) 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 2) 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 3) 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 4) Configuring the SCCP 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 5) Configuring the TCAP Layer (optional)

|-
| 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" |
*[[Toolpack:Creating the SCTP Configuration D|Create the SCTP Configuration]]
*[[Toolpack:Creating the M2PA Configuration D|Create an M2PA Configuration]]
**[[Toolpack:Creating an M2PA SAP D|Create an M2PA SAP]]
**[[Toolpack:Adding M2PA Links C|Add M2PA Links]]

| valign="top" |
*[[Toolpack:Creating_an_MTP3_Configuration E|Create an MTP3 Configuration]]
*[[Toolpack:Creating_an_MTP3_Network D|Create an MTP3 Network]]
**[[Toolpack:Creating_SS7_Point_Codes E|Create an MTP3 Point Code]]
**[[Toolpack:Creating_an_MTP3_Linkset C|Create an MTP3 Linkset]]
***[[Toolpack:Creating_MTP3_Links C|Create MTP3 Links]]
**[[Toolpack:Creating_an_MTP3_Route C|Create an MTP3 Route]]

| valign="top" |
*[[Toolpack:Creating_an_SCCP_Stack C| Create an SCCP Stack]]
*[[Toolpack:Creating_an_SCCP_Network C|Create an SCCP Network]]
**[[Toolpack:Creating_an_SCCP_Userpart C|Create an SCCP Userpart]]
**[[Toolpack:Creating_an_SCCP_LSAP C|Create an SCCP LSAP]]
***[[Toolpack:Creating_an_SCCP_Route C|Create an SCCP Route]]
****[[Toolpack:Creating_an_SCCP_SSN C|Create an SCCP SSN]]
*[[Toolpack:Creating_an_SCCP_GTT_Association C|Create an SCCP GTT Association]]
**[[Toolpack:Creating_an_SCCP_GTT_Association_Action A|Create an SCCP GTT Association Action]]
**[[Toolpack:Creating_an_SCCP_GTT_Address_Map C|Create an SCCP GTT Address Map]]

| valign="top" |
*[[Toolpack:Creating_a_TCAP_Stack C|Create a TCAP Stack]]
**[[Toolpack:Creating_a_TCAP_Userpart C| Create a TCAP Userpart]]
*[[Toolpack:Activating_the_Configuration D|Activating the Configuration]]

|}

'''M3UA-SCCP-TCAP'''

{| 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) 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 2) Configuring the M3UA 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) Configuring the SCCP 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) Configuring the TCAP Layer (optional)

|-

| 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" |
*[[Toolpack:Creating the SCTP Configuration D|Create the SCTP Configuration]]
*[[Toolpack:Creating SS7 Point Codes E|Create SS7 Point Codes]]
*[[Toolpack:Creating an M3UA Configuration E|Create an M3UA Configuration]]
**[[Toolpack:Creating an M3UA SAP D|Create an M3UA SAP]]
**[[Toolpack:Creating an M3UA Network D|Create an M3UA Network]]
**[[Toolpack:Creating an M3UA User Part D|Create an M3UA User Part]]
**[[Toolpack:Creating an M3UA Peer Signalling Process D|Create an M3UA Peer Signalling Process]]
**[[Toolpack:Creating an M3UA Peer Server D|Create an M3UA Peer Server]]
**[[Toolpack:Creating an M3UA Route D|Create an M3UA Route]]

| valign="top" |
*[[Toolpack:Creating_an_SCCP_Stack C| Create an SCCP Stack]]
*[[Toolpack:Creating_an_SCCP_Network C|Create an SCCP Network]]
**[[Toolpack:Creating_an_SCCP_Userpart C|Create an SCCP Userpart]]
**[[Toolpack:Creating_an_SCCP_LSAP C|Create an SCCP LSAP]]
***[[Toolpack:Creating_an_SCCP_Route C|Create an SCCP Route]]
****[[Toolpack:Creating_an_SCCP_SSN C|Create an SCCP SSN]]
*[[Toolpack:Creating_an_SCCP_GTT_Association C|Create an SCCP GTT Association]]
**[[Toolpack:Creating_an_SCCP_GTT_Address_Map C|Create an SCCP GTT Address Map]]

| valign="top" |
*[[Toolpack:Creating_a_TCAP_Stack C|Create a TCAP Stack]]
**[[Toolpack:Creating_a_TCAP_Userpart C| Create a TCAP Userpart]]
*[[Toolpack:Activating_the_Configuration D|Activating the Configuration]]

|}

=SIGTRAN=
Sigtran relays TDM signaling over IP.

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

'''M2UA'''

{| 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) Create Line 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 2) Create MTP2 links
! 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) Create M2UA configuration

|-

| 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" |

*[[Toolpack:Creating_an_MTP2_Configuration D|Create an MTP2 Configuration]]
**[[Toolpack:Creating_MTP2_Links C|Create MTP2 Links]]

| valign="top" |

*[[Toolpack:Creating the SCTP Configuration D|Create the SCTP Configuration]]
*[[Toolpack:Creating the M2UA Configuration D|Create an M2UA Configuration]]
**[[Toolpack:Creating an M2UA SAP C|Create an M2UA SAP]]
**[[Toolpack:Creating an M2UA Cluster C|Create an M2UA Cluster]]
**[[Toolpack:Creating M2UA Links C|Create M2UA Links]]
**[[Toolpack:Creating M2UA Peers C|Create M2UA Peers]]

|}

'''M3UA'''

{| 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) Create Line 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 2) Create MTP2 links
! 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) Create MTP3 configuration
! 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) Create M3UA configuration
|-

| 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" |
*[[Toolpack:Creating_an_MTP2_Configuration D|Create an MTP2 Configuration]]
*[[Toolpack:Creating_MTP2_Links C|Create MTP2 Links]]

| valign="top" |
*[[Toolpack:Creating SS7 Point Codes E|Create SS7 Point Codes]]
*[[Toolpack:Creating an MTP3 Configuration E|Create an MTP3 Configuration]]
**[[Toolpack:Creating an MTP3 Network D|Create an MTP3 Network]]
**[[Toolpack:Creating an MTP3 Linkset C|Create an MTP3 Linkset]]
**[[Toolpack:Creating MTP3 Links (M3UA) C|Create MTP3 Links]]
**[[Toolpack:Creating an MTP3 Route C|Create an MTP3 Route]]

| valign="top" |
*[[Toolpack:Creating the SCTP Configuration D|Edit the SCTP Configuration]]
*[[Toolpack:Creating an M3UA Configuration E|Create an M3UA Configuration]]
**[[Toolpack:Creating an M3UA SAP D|Create an M3UA SAP]]
**[[Toolpack:Creating an M3UA Network D|Create an M3UA Network]]
**[[Toolpack:Creating an M3UA User Part D|Create an M3UA User Part]]
**[[Toolpack:Creating an M3UA Peer Signalling Process D|Create an M3UA Peer Signalling Process]]
**[[Toolpack:Creating an M3UA Peer Server D|Create an M3UA Peer Server]]
**[[Toolpack:Creating an M3UA Route D|Create an M3UA Route]] 

|}

'''IUA'''

{| 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) Create Line 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 2) Create IUA Configuration

|-

| 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" |
*[[Toolpack:Creating the SCTP Configuration D|Create the SCTP Configuration]]
*[[Toolpack:Creating the IUA Configuration D|Create an IUA Configuration]]
**[[Toolpack:Creating an IUA SAP C|Create an IUA SAP]]
**[[Toolpack:Creating an IUA Cluster C|Create an IUA Cluster]]
**[[Toolpack:Creating IUA Links C|Create IUA Links]]
**[[Toolpack:Creating IUA Peers C|Create IUA Peers]]

|}

<div class="mw-collapsible mw-collapsed" data-collapsetext="Sigtran Service Affecting Parameters" data-expandtext="Click here for Sigtran Service Affecting Parameters" style="width: 400px;">
 
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)
</div>

=H.248 MEGACO=
H.248 is a protocol used to interface a softswitch with a media gateway.

'''Media'''

'''TDM NAP (for ISUP/ISDN)'''

{| 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) Allocate TDM 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 2) 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 3) 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" |
*[[Toolpack:Modify_NAP_profile F|Modify profile]]
| valign="top" |
*[[Toolpack:Allocating_a_TDM_Network_Access_Point_(NAP) D|Allocate a TDM NAP]]
|}

'''VOIP NAP (for SIP)'''

{| 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) Create IP Port Ranges
! 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) 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 3) Configure Network Access Points (NAPs)
|-
| valign="top" |
*[[Toolpack:Creating_an_IP_Port_Range D|Create IP port ranges]]
| valign="top" |
*[[Toolpack:Modify_NAP_profile F|Modify profile]]
| valign="top" |
*[[Toolpack:Allocating_a_VoIP_Network_Access_Point_(NAP) D|Allocate a VoIP NAP]]
|}

'''CAS NAP'''
{| 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) 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 2) Configuring a CAS stack
! 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) 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 4) Configure Network Access Points (NAPs)

|-
| valign="top" |
*[[Toolpack:Creating_a_Line_Interface D|Create Line Interfaces]]
*[[Toolpack:Creating_a_Line_Service D|Create Line Service]]
*[[Toolpack:Creating_a_System_Clock A|Create System Clock]]
| valign="top" |
*[[Toolpack:Copy variant script D|Copy variant script]]
*[[Toolpack:Create CAS R2 stack D|Create CAS stack]]
*Edit the [[CASr1_scripting|CAS R1_A]] or [[CAS R2 scripting|CAS R2_A]] script to adapt the variant
**[[CASr1_scripting#TONE_USE_DTMF_A|Select CAS R1 tone type]]
**[[Toolpack:Setting CAS R2 BACK DIGITS variable D|Set CAS R2 backward digits string]]
| valign="top" |
*[[Toolpack:Modify_NAP_profile F|Modify profile]]
| valign="top" |
*[[Toolpack:Creating_a_CAS_R2_NAP D|Create a CAS NAP]]

|}

'''Media Gateway'''

{| 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) Configure Media Gateway for H.248 mode
! 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) Add a New Media Gateway Controller
! 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) Associate NAPs Resources to H.248 Configuration

|-

| valign="top" |
*[[Toolpack:Configure the Media_Gateway_for_H248_Mode E|Configure the Media Gateway for H.248 mode ]]
*[[Toolpack:Creating_an_H.248_Configuration D|Create a new H.248 configuration]]
| valign="top" |
*[[Toolpack:Adding_a_Media_Gateway_Controller_(MGC) C|Add a new media gateway controller (MGC)]]
| valign="top" |
*[[Toolpack:Associating_NAPs_with_an_H.248_Configuration D|Associate the NAPs with the H.248 configuration]]
*[[Toolpack:Selecting_Timeslots_for_TDM_Interfaces C|Select timeslots for the TDM interfaces ]]

|}

Please note when modifying '''[[Toolpack: H248 Service Affecting Parameters|H.248 Service Affecting Parameters]]''' the H.248 stack will be deallocated and reallocated, resulting in a loss of active calls. Be careful when changing these parameters

=Protocol Interoperability=

'''Early Media'''

{| cellpadding="5" border="1" class="wikitable"
! width="240" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Q.1912.5 Profile A-B
|-
| valign="top" |
*[[Toolpack:Configure_Early_Media_Q1912_A_B_NAP__A|Configure NAP ]]
*[[Toolpack:Configure_Early_Media_Q1912_A_B_Profile_A_|Configure Profile]]
|}

<headertabs/>

'''{{#switchtablink:Protocol Stack|Return to Web Portal 3.2 Home Page|Tmedia_Tsig_Tdev_Tutorial_Guide_v3.2}}'''

File:Edit H248 0.png

2024-03-28T06:54:59Z

Joshua Puckett: Advanced Parameter configuration after H248 Configuration has been create

== Summary ==
Advanced Parameter configuration after H248 Configuration has been create

Toolpack:Certificates

2023-08-22T07:38:08Z

Joshua Puckett: /* Create a CSR (certificate signing request) from a private key */

This page provides useful shell commands and instructions to create and manipulate certificates with ProSBC.

== Installing a custom private key and local certificate on ProSBC ==

[[Create_A_SIP_Certificate_A#Upload_local_certificates_.28optional.29|See WEB Portal configuration documentation]]

== Use ProSBC (or Linux) shell to manipulate certificates ==
You can use ProSBC's shell (or most Linux hosts' shell as long as OpenSSL is installed) to create and view private keys, certificates and CSRs (certificate signing requests).

=== Create new private key ===
openssl genrsa -aes256 -out MY_PRIVATE_KEY.pem 2048

You will be prompted to enter a pass phrase:
Generating RSA private key, 2048 bit long modulus
.....................+++
..............................+++
e is 65537 (0x10001)
Enter pass phrase for MY_PRIVATE_KEY.pem:
Verifying - Enter pass phrase for MY_PRIVATE_KEY.pem:

Resulting file:
-rw-r--r-- 1 root root 1704 Mar 14 09:15 MY_PRIVATE_KEY.pem

=== Create a self-signed certificate from a private key ===
openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout MY_PRIVATE_KEY.pem -out MY_CERTIFICATE.crt

You will be prompted to answer questions regarding the certificate:
Generating a 2048 bit RSA private key
.........................................................+++
........................................................................................................................................................................................+++
writing new private key to 'MY_PRIVATE_KEY.pem'
-----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [XX]:CA
State or Province Name (full name) []:Quebec
Locality Name (eg, city) [Default City]:Boucherville
Organization Name (eg, company) [Default Company Ltd]:TelcoBridges
Organizational Unit Name (eg, section) []:
Common Name (eg, your name or your server's hostname) []:MySBC
Email Address []:support@telcobridges.com

Resulting files:
-rw-r--r-- 1 root root 1415 Mar 14 09:15 MY_CERTIFICATE.crt
-rw-r--r-- 1 root root 1751 Mar 14 09:14 MY_PRIVATE_KEY.pem

=== Create a CSR (certificate signing request) from a private key ===
openssl req -new -newkey rsa:2048 -nodes -keyout my_local_cert.key -out MY_CSR.csr
You will be prompted to answer questions regarding the certificate:
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [XX]:CA
State or Province Name (full name) []:Quebec
Locality Name (eg, city) [Default City]:Boucherville
Organization Name (eg, company) [Default Company Ltd]:TelcoBridges
Organizational Unit Name (eg, section) []:
Common Name (eg, your name or your server's hostname) []:MySBC
Email Address []:support@telcobridges.com

Please enter the following 'extra' attributes
to be sent with your certificate request
A challenge password []:my_password
An optional company name []:TelcoBridges

Resulting files:
-rw-r--r-- 1 root root 1127 Mar 14 09:20 MY_CSR.csr

=== View the contents of the certificate ===
openssl x509 -noout -text -in MY_CERTIFICATE.crt

Resulting output:
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
f3:fc:c5:72:ea:a9:50:a6
Signature Algorithm: sha256WithRSAEncryption
Issuer: C=CA, ST=Quebec, L=Boucherville, O=TelcoBridges, CN=MySBC/emailAddress=support@telcobridges.com
Validity
Not Before: Mar 14 13:15:53 2019 GMT
Not After : Mar 13 13:15:53 2020 GMT
Subject: C=CA, ST=Quebec, L=Boucherville, O=TelcoBridges, CN=MySBC/emailAddress=support@telcobridges.com
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
Public-Key: (2048 bit)
Modulus:
00:dc:38:85:9f:75:ce:cf:7c:3b:60:20:11:d1:47:
00:39:6e:10:5c:3b:72:6e:26:09:70:7a:df:14:b3:
f4:60:fb:0d:73:69:a9:4c:4f:a0:34:12:83:1a:9b:
ce:f0:61:59:bd:f1:fb:a3:cb:84:be:a5:3b:86:e5:
e0:66:82:53:fd:69:c3:f1:cf:85:73:2d:30:a9:a5:
82:4e:e2:0f:20:de:88:9d:7a:42:d3:19:7b:09:08:
68:75:c4:36:46:23:f2:c6:05:49:e6:79:06:ce:f8:
9f:66:11:ad:e3:41:6c:f5:cb:df:3a:a4:77:a3:b3:
9b:55:f4:fc:5a:5a:c1:ae:c5:5d:0b:de:b1:1a:bc:
3d:02:b9:0c:5d:d8:57:33:66:b2:a8:c0:c2:74:16:
20:32:63:0f:8b:8f:aa:f4:aa:bc:8a:12:1b:54:e1:
87:c7:10:79:ea:1d:f3:e2:4b:b3:b5:70:d5:ec:27:
24:d3:f2:37:20:7e:f7:2c:69:21:63:50:4a:fe:a2:
98:4f:bc:c8:4b:3c:74:68:95:8e:0a:0b:42:39:d3:
cb:88:1d:55:c1:e1:61:f3:b0:64:42:6f:ec:c5:6f:
8f:f8:1c:a8:d9:5b:fc:d7:54:91:3b:0a:c4:1a:82:
d1:96:11:ca:16:b8:44:f0:48:3a:1e:e4:78:d0:14:
f5:1d
Exponent: 65537 (0x10001)
X509v3 extensions:
X509v3 Subject Key Identifier:
9C:DA:43:3C:BC:E6:B1:8B:E7:B4:1C:AB:39:14:66:72:F5:C2:D6:25
X509v3 Authority Key Identifier:
keyid:9C:DA:43:3C:BC:E6:B1:8B:E7:B4:1C:AB:39:14:66:72:F5:C2:D6:25

X509v3 Basic Constraints:
CA:TRUE
Signature Algorithm: sha256WithRSAEncryption
4c:96:41:e8:ff:d8:79:e0:db:22:ec:a2:10:1b:c0:88:f3:83:
60:b1:2d:91:06:15:a4:96:4a:9a:fb:3c:39:a4:48:04:a9:55:
1b:b5:c2:c8:08:e0:70:d7:03:c5:e1:1d:f7:0c:3d:38:49:aa:
9b:85:1f:d2:6b:61:f5:10:9a:c7:0a:ff:34:a4:e9:d5:0b:cd:
2a:90:84:07:ac:74:7f:d9:e1:dd:33:dd:ae:8c:5a:61:ec:20:
d3:6e:7c:e5:be:46:94:b4:bc:da:54:80:12:28:5b:12:80:a1:
ad:86:6a:f9:dc:1f:f8:a5:cb:ab:2a:30:5d:f8:19:9f:e8:82:
9b:32:b7:cc:d5:f9:7d:3b:35:51:8b:a5:39:e3:71:84:37:09:
20:e0:d9:6c:6f:37:76:49:3a:01:ea:ce:8b:71:74:fe:29:2c:
84:3d:3b:9e:6c:50:64:53:36:90:6e:49:ce:40:fd:80:c7:25:
31:d5:49:42:0f:c7:37:9a:9e:99:6b:37:3e:9a:71:a7:a2:87:
19:1d:a3:44:48:b8:c3:65:c1:55:b2:0c:57:e8:0f:a6:f2:a5:
b4:d3:50:04:fe:fd:86:2c:c2:0a:c2:20:aa:81:26:48:34:3a:
3d:a6:2e:1b:eb:d7:b9:f1:a2:ad:7a:42:37:81:63:02:ac:3b:
e6:01:6b:10

=== View the signing request of a certificate (CSR) ===
openssl req -text -noout -verify -in MY_CSR.csr

Resulting output:
verify OK
Certificate Request:
Data:
Version: 0 (0x0)
Subject: C=CA, ST=Quebec, L=Boucherville, O=TelcoBridges, CN=MySBC/emailAddress=support@telcobridges.com
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
Public-Key: (2048 bit)
Modulus:
00:dc:38:85:9f:75:ce:cf:7c:3b:60:20:11:d1:47:
00:39:6e:10:5c:3b:72:6e:26:09:70:7a:df:14:b3:
f4:60:fb:0d:73:69:a9:4c:4f:a0:34:12:83:1a:9b:
ce:f0:61:59:bd:f1:fb:a3:cb:84:be:a5:3b:86:e5:
e0:66:82:53:fd:69:c3:f1:cf:85:73:2d:30:a9:a5:
82:4e:e2:0f:20:de:88:9d:7a:42:d3:19:7b:09:08:
68:75:c4:36:46:23:f2:c6:05:49:e6:79:06:ce:f8:
9f:66:11:ad:e3:41:6c:f5:cb:df:3a:a4:77:a3:b3:
9b:55:f4:fc:5a:5a:c1:ae:c5:5d:0b:de:b1:1a:bc:
3d:02:b9:0c:5d:d8:57:33:66:b2:a8:c0:c2:74:16:
20:32:63:0f:8b:8f:aa:f4:aa:bc:8a:12:1b:54:e1:
87:c7:10:79:ea:1d:f3:e2:4b:b3:b5:70:d5:ec:27:
24:d3:f2:37:20:7e:f7:2c:69:21:63:50:4a:fe:a2:
98:4f:bc:c8:4b:3c:74:68:95:8e:0a:0b:42:39:d3:
cb:88:1d:55:c1:e1:61:f3:b0:64:42:6f:ec:c5:6f:
8f:f8:1c:a8:d9:5b:fc:d7:54:91:3b:0a:c4:1a:82:
d1:96:11:ca:16:b8:44:f0:48:3a:1e:e4:78:d0:14:
f5:1d
Exponent: 65537 (0x10001)
Attributes:
challengePassword :my_password
unstructuredName :TelcoBridges
Signature Algorithm: sha256WithRSAEncryption
85:98:17:25:45:42:f6:44:f0:51:ca:42:32:92:e6:0e:a6:9d:
59:73:1c:82:c6:9b:c1:b7:17:00:77:f3:42:52:86:d6:08:a8:
30:99:02:41:c6:c2:22:b2:98:b9:f7:83:b9:b0:ab:5b:59:95:
9c:32:3b:9b:15:1c:4c:90:d1:bb:cf:fb:85:c4:5d:df:df:9e:
18:1b:f8:5b:b5:68:60:0f:d8:c6:5d:29:0c:54:b3:63:88:0c:
05:59:34:ad:c0:11:5b:e9:fb:e8:8c:c1:b5:5f:83:60:78:05:
b7:7e:66:d7:1a:59:5a:2e:b3:9c:c2:38:68:29:bf:44:51:da:
c9:2b:c3:f1:47:3c:d4:ce:4a:b2:8f:7d:6a:72:46:13:a8:97:
18:7e:bf:b0:33:14:ee:61:ed:94:c6:c0:19:92:14:2d:a0:8c:
b1:a2:c1:61:40:62:90:7c:64:09:52:ec:b6:fd:cb:fe:56:3f:
6e:de:e3:38:93:ee:e4:26:33:59:6c:3f:4f:36:87:de:96:4d:
c4:bd:ce:35:b2:79:16:38:f5:84:c8:ce:4a:27:11:6b:4b:0d:
9b:9f:dd:63:87:ca:23:12:8c:64:3b:c7:f0:46:e8:bd:e0:e7:
35:9d:b9:fb:aa:60:e2:48:8f:9b:6b:fb:69:2f:a5:7c:94:5a:
70:4d:a6:d1

=== Check that a certificate and a CSR match the private key ===
openssl x509 -noout -modulus -in MY_CERTIFICATE.crt | openssl md5
openssl rsa -noout -modulus -in MY_PRIVATE_KEY.pem | openssl md5
openssl req -noout -modulus -in MY_CSR.csr | openssl md5

All 3 commands should display the same MD5 hash:
(stdin)= 41c46eddc15580673fe4adb8f5255634

Live signalling capture by tbsigtrace

2023-01-27T10:37:18Z

Joshua Puckett:

'''''Applies to version(s) v2.7 and up'''''
{{DISPLAYTITLE:Live Signaling Capture with tbsigtrace}}
You can now activate tbsigtrace and pipe it directly in wireshark through SSH to get a live capture of SS7, ISDN, SIP, Sigtran and H.248 (not all in the same wireshark window). This page provides the procedure for a Windows base operating system using plink and wireshark tools.

'''WARNING: tbsigtrace application should not be used all the time, otherwise it might reduce performance. Also we suggest to do the live capture on only one Tmedia at a time'''.

The procedure is as following:

==== Download plink ====
Download 64 bit plink at https://the.earth.li/~sgtatham/putty/latest/w64/plink.exe 
Download 32 bit plink at https://the.earth.li/~sgtatham/putty/latest/w32/plink.exe 
Place it in '''C:\Program Files\Putty''' directory

=== Execute the command to capture the signalling accordingly ===
This is the structure of the command:
plink.exe -batch -ssh root@[IP_of_management_port] -P [ssh_port] -pw [ssh_password] "tbsigtrace -stdout -[protocol]" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For SS7 capture =====
plink.exe -batch -ssh root@10.10.10.10 -pw mypassword "tbsigtrace -stdout -ss7" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For ISDN capture =====
plink.exe -batch -ssh root@10.10.10.10 -pw mypassword "tbsigtrace -stdout -isdn" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For SIP or SIGTRAN capture =====
plink.exe -batch -ssh root@10.10.10.10 -pw mypassword "tbsigtrace -stdout -ip" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For H.248 capture =====
plink.exe -batch -ssh root@10.10.10.10 -pw mypassword "tbsigtrace -stdout -h248" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For Radius or SNMP capture =====
plink.exe -batch -ssh root@10.10.10.10 -pw mypassword "tcpdump -i mgmt0 -s 0 -w - -f 'not tcp port 22'" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -
 
Link to [[Toolpack Debug Application:Tbsigtrace|Signaling Trace Capture Tool]] page: [[Toolpack Debug Application:Tbsigtrace|tbsigtrace]]

Live signalling capture by tbsigtrace

2023-01-27T10:36:32Z

Joshua Puckett: /* Download plink */

'''''Applies to version(s) v2.7 and up'''''
{{DISPLAYTITLE:Live Signaling Capture with tbsigtrace}}
You can now activate tbsigtrace and pipe it directly in wireshark through SSH to get a live capture of SS7, ISDN, SIP, Sigtran and H.248 (not all in the same wireshark window). This page provides the procedure for a Windows base operating system using plink and wireshark tools.

'''WARNING: tbsigtrace application should not be used all the time, otherwise it might reduce performance. Also we suggest to do the live capture on only one Tmedia at a time'''.

The procedure is as following:

==== Download plink ====
Download 64 bit plink at https://the.earth.li/~sgtatham/putty/latest/w64/plink.exe 
Download 32 bit plink at https://the.earth.li/~sgtatham/putty/latest/w32/plink.exe 
Place it in '''C:\Program Files\Putty''' directory

=== Execute the command to capture the signalling accordingly ===
This is the structure of the command:
plink.exe -ssh root@[IP_of_management_port] -P [ssh_port] -pw [ssh_password] "tbsigtrace -stdout -[protocol]" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For SS7 capture =====
plink.exe -ssh root@10.10.10.10 -pw mypassword "tbsigtrace -stdout -ss7" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For ISDN capture =====
plink.exe -ssh root@10.10.10.10 -pw mypassword "tbsigtrace -stdout -isdn" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For SIP or SIGTRAN capture =====
plink.exe -ssh root@10.10.10.10 -pw mypassword "tbsigtrace -stdout -ip" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For H.248 capture =====
plink.exe -ssh root@10.10.10.10 -pw mypassword "tbsigtrace -stdout -h248" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For Radius or SNMP capture =====
plink.exe -ssh root@10.10.10.10 -pw mypassword "tcpdump -i mgmt0 -s 0 -w - -f 'not tcp port 22'" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -
 
Link to [[Toolpack Debug Application:Tbsigtrace|Signaling Trace Capture Tool]] page: [[Toolpack Debug Application:Tbsigtrace|tbsigtrace]]

Live signalling capture by tbsigtrace

2023-01-27T09:06:11Z

Joshua Puckett: /* Download plink */

'''''Applies to version(s) v2.7 and up'''''
{{DISPLAYTITLE:Live Signaling Capture with tbsigtrace}}
You can now activate tbsigtrace and pipe it directly in wireshark through SSH to get a live capture of SS7, ISDN, SIP, Sigtran and H.248 (not all in the same wireshark window). This page provides the procedure for a Windows base operating system using plink and wireshark tools.

'''WARNING: tbsigtrace application should not be used all the time, otherwise it might reduce performance. Also we suggest to do the live capture on only one Tmedia at a time'''.

The procedure is as following:

==== Download plink ====
''Note: There is a compatibility issue with Wireshark in plink versions 0.71 - 0.76 and 0.78, please use version 0.77 until this issue is solved.'' 
Download 64 bit plink at https://the.earth.li/~sgtatham/putty/0.77/w64/plink.exe 
Download 32 bit plink at https://the.earth.li/~sgtatham/putty/0.77/w32/plink.exe 
Place it in '''C:\Program Files\Putty''' directory

=== Execute the command to capture the signalling accordingly ===
This is the structure of the command:
plink.exe -ssh root@[IP_of_management_port] -P [ssh_port] -pw [ssh_password] "tbsigtrace -stdout -[protocol]" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For SS7 capture =====
plink.exe -ssh root@10.10.10.10 -pw mypassword "tbsigtrace -stdout -ss7" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For ISDN capture =====
plink.exe -ssh root@10.10.10.10 -pw mypassword "tbsigtrace -stdout -isdn" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For SIP or SIGTRAN capture =====
plink.exe -ssh root@10.10.10.10 -pw mypassword "tbsigtrace -stdout -ip" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For H.248 capture =====
plink.exe -ssh root@10.10.10.10 -pw mypassword "tbsigtrace -stdout -h248" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For Radius or SNMP capture =====
plink.exe -ssh root@10.10.10.10 -pw mypassword "tcpdump -i mgmt0 -s 0 -w - -f 'not tcp port 22'" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -
 
Link to [[Toolpack Debug Application:Tbsigtrace|Signaling Trace Capture Tool]] page: [[Toolpack Debug Application:Tbsigtrace|tbsigtrace]]

Live signalling capture by tbsigtrace

2023-01-27T08:58:37Z

Joshua Puckett: /* Download plink */

'''''Applies to version(s) v2.7 and up'''''
{{DISPLAYTITLE:Live Signaling Capture with tbsigtrace}}
You can now activate tbsigtrace and pipe it directly in wireshark through SSH to get a live capture of SS7, ISDN, SIP, Sigtran and H.248 (not all in the same wireshark window). This page provides the procedure for a Windows base operating system using plink and wireshark tools.

'''WARNING: tbsigtrace application should not be used all the time, otherwise it might reduce performance. Also we suggest to do the live capture on only one Tmedia at a time'''.

The procedure is as following:

==== Download plink ====
''Note: There is a compatibility issue with Wireshark in plink versions 0.71 - 0.76 and 0.78, please use version 0.77 until this issue is solved.'' 
Download 64 bit plink at https://the.earth.li/~sgtatham/putty/0.77/w64/plink.exe 
Download 32 bit plink at https://the.earth.li/~sgtatham/putty/0.77/w32/plink.exe 
Place it in '''C:\Program Files\Putty directory'''

=== Execute the command to capture the signalling accordingly ===
This is the structure of the command:
plink.exe -ssh root@[IP_of_management_port] -P [ssh_port] -pw [ssh_password] "tbsigtrace -stdout -[protocol]" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For SS7 capture =====
plink.exe -ssh root@10.10.10.10 -pw mypassword "tbsigtrace -stdout -ss7" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For ISDN capture =====
plink.exe -ssh root@10.10.10.10 -pw mypassword "tbsigtrace -stdout -isdn" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For SIP or SIGTRAN capture =====
plink.exe -ssh root@10.10.10.10 -pw mypassword "tbsigtrace -stdout -ip" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For H.248 capture =====
plink.exe -ssh root@10.10.10.10 -pw mypassword "tbsigtrace -stdout -h248" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For Radius or SNMP capture =====
plink.exe -ssh root@10.10.10.10 -pw mypassword "tcpdump -i mgmt0 -s 0 -w - -f 'not tcp port 22'" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -
 
Link to [[Toolpack Debug Application:Tbsigtrace|Signaling Trace Capture Tool]] page: [[Toolpack Debug Application:Tbsigtrace|tbsigtrace]]

SNMP

2022-06-23T06:39:07Z

Joshua Puckett: /* SNMP Trap/Notification */

The Simple Network Management Protocol (SNMP) is used in network management systems to monitor attached hardware for changes in operation activity. SNMP provides a standardized approach to monitoring and managing network systems.
 For information on configuring your TMedia product to use the SNMP protocol, see the section labeled [[SNMP#Related Tasks|"'''Related Tasks'''"]].
 
== TelcoBridges and SNMP ==
TelcoBridges offers basic support for SNMP versions 1, 2, and 3. '''Toolpack supports SNMP V2 and V3 since release 2.5.80''' (see [[TMG-CONTROL_Version_2.5| Tctrl version history]]). This grants users the ability to remotely poll (or GET) system variables, known as Managed Objects, which are represented in files known as MIB modules. TelcoBridges currently offers polling on '''standard''' MIB modules (RTP, SONET, DS1, DS3, ISDN, etc...) and on the TelcoBridges '''privately defined''' module ([[TB-MIB|'''TB-MIB''']]). 
 
== Supported SNMP MIB modules ==
#[http://tools.ietf.org/html/rfc1213 RFC 1213 MIB II (RFC1213-MIB)]
#*All tables of the RFC1213-MIB are supported, '''with the exception of''':
#**ipRouteTable
#**EGP group
#**atTable
#[http://tools.ietf.org/html/rfc1573.txt RFC 1573 Evolution of Interfaces Group of MIB-II (IF-MIB)]
#*The following tables are supported:
#**ifTable
#**ifStackTable
#[http://tools.ietf.org/html/rfc2495 RFC 2495 DS1, J1, E1, DS2, and E2 Interfaces (DS1-MIB)]
#*The following tables of the DS1-MIB are supported:
#**Dsx1ConfigTable
#**Dsx1CurrentTable
#**Dsx1IntervalTable
#**Dsx1TotalTable
#[http://tools.ietf.org/html/rfc2496 RFC 2496 - Definitions of Managed Object for the DS3/E3 Interface Type (DS3-MIB)]
#*The following tables of the DS3-MIB are supported:
#**Dsx3ConfigTable
#**Dsx3CurrentTable
#**Dsx3IntervalTable
#**Dsx3TotalTable
#[http://tools.ietf.org/html/rfc1595 RFC 1595 - Definitions of Managed Object for the SONET/SDH Interface Type (SONET-MIB)]
#*The following tables of the SONET-MIB are supported:
#**sonetMediumTable
#**sonetSectionCurrentTable
#**sonetSectionIntervalTable
#**sonetLineCurrentTable
#**sonetLineIntervalTable
#**sonetFarendLineCurrentTable
#**sonetFarendLineIntervalTable
#**sonetPathCurrentTable
#**sonetPathIntervalTable
#**sonetFarendPathCurrentTable
#**sonetFarendPathIntervalTable
#**sonetVtCurrentTable
#**sonetVtIntervalTable
#**sonetFarendVtCurrentTable
#**sonetFarendVtIntervalTable
#[http://tools.ietf.org/html/rfc2127 RFC 2127 - ISDN Management Information Base using SMIv2 (ISDN-MIB)]
#*The following tables of the ISDN-MIB are supported:
#**isdnBearerGroup
#**isdnSignalingGroup
#[[TB-MIB|Telcobridges Private MIB module (TB-MIB)]]
#*tbHwCommon
#**tbHwIdentTable (Hardware Identification)
#**tbHwVersionTable (Hardware Version)
#**tbHwTempTable (Hardware Temperature)
#**tbHwPowerSupplyTable (Hardware Power Supply)
#**tbHwFanTable (Hardware Fan)
#*tbSwCommon
#**tbFeatureTable (Software Features Supported)
#**tbSwVersionTable (Software Version)
#**tbSwPerfTable (CPU Usage)
#*tbSignaling
#**tbMtp2
#**tbM2pa
#**tbM2ua
#**tbM3ua
#**tbIua
#**tbIsdn
#**tbCas
#**tbSip
#**tbH248
#*tbCalls
#*tbNAP
#*tbHaNp1
#*tbHaApp
#*tbClock

=== SNMP IF-MIB ifTable interface type ===
The following table provides the interfaces type supported by TelcoBridges (IF-MIB ifTable described in [https://tools.ietf.org/html/rfc1573 RFC1573]) with their corresponding description. The ifType are described in Internet Assigned Number Authority (IANA) in [http://www.iana.org/assignments/ianaiftype-mib IANAifType-MIB]
{| cellpadding="0" border="0" style="width: 820px;" class="wikitable"
|-
! IANA ifType
! TelcoBridges Interface description
|-
| ethernetCsmacd(6)
| Baseboard Ethernet interfaces
|-
| ds1(18)
| Trunks Line Interface
|-
| ds3(30)
| DS3 Line Interface
|-
| sonet(39)
| SONET/SDH Line Interface
|-
| sonetPath(50)
| SONET/SDH Line Service PATH (VC4/VC3/STS1/DS3)
|-
| sonetVT(51)
| SONET/SDH Line Service SECTION (VC11/VC12/VT15/VT2)
|-
| isdn(63)
| ISDN Stack
|-
| lapd(77)
| ISDN LAPD Link (Primary)
|-
| lapd(77)
| ISDN LAPD Link (Backup)
|-
| isdn(63)
| IUA Link
|-
| isdn(63)
| IUA Peer
|-
| lapd(77)
| LAPD Link
|-
| ss7SigLink (156)
| SS7 M2PA Link
|-
| ss7SigLink (156)
| SS7 M2UA Link
|-
| ss7SigLink (156)
| SS7 M2UA Peer
|-
| ss7SigLink (156)
| Ss7 M3ua Sap
|-
| ss7SigLink (156)
| Ss7 M3ua Psp
|-
| ss7SigLink (156)
| Ss7 M3ua Psrv
|-
| ss7SigLink (156)
| Ss7 Mtp2 Link
|}

=== SNMP traps ===
The '''SNMP traps''' module of TelcoBridges products monitor the operation status of some MIBS OIDs and generates notifications when the states change. The default monitoring polling period is set to 1 minute. This value can be modified in the [[SNMP#Configuration|SNMP configuration]].

====SNMP Trap/Notification====

{| cellpadding="0" border="0" style="width: 1200px;" class="wikitable"
|-
! Trap Name
! MIB
! OID
! OBJECTS
! CONSIDERED AS AN ALARM
! RFC
! RELEASE
|-
| linkDown
| IF-MIB
| 1.3.6.1.6.3.1.1.5.3
| { ifIndex, ifAdminStatus, ifOperStatus, ifDescr }
| When ifAdminStatus=1 & ifOperStatus=2, In certain conditions could be critical, this trap should raise an alarm.
| RFC1573
| 2.8+
|-
| linkUp
| IF-MIB
| 1.3.6.1.6.3.1.1.5.4
| { ifIndex, ifAdminStatus, ifOperStatus, ifDescr }
| Transition from network interface Down state. Normal clear trap for linkDown alarm
| RFC1573
| 2.8+
|-
| ColdStart
| IF-MIB
| 1.3.6.1.6.3.1.1.5.1
| { OID }
| Per RFC3418 a ColdStart signifies that some configuration changes may have been made. However the TMG does not report Configuration changes via this OID. ColdStart is expected even when no changes have been made to the configuration. User should not be alerted, alarms should not be raised.
| RFC3418
| 3.2+
|-
| WarmStart
| IF-MIB
| 1.3.6.1.6.3.1.1.5.2
| { OID }
| The TMG will resort to ColdStart in most cases as the configuration changes are not reported via this OID.
| RFC3418
| 3.2+
|-
| nsNotifyStart
| NET-SNMP-MIB
| 1.3.6.1.4.1.8072.4.0.1
| { OID }
| A notification that the agent has started running
| (see www.net-snmp.org)
| 3.2+
|-
| nsNotifyShutdown
| NET-SNMP-MIB
| 1.3.6.1.4.1.8072.4.0.2
| { OID }
| Shutdown notification, should raise and alarm until nsNotifyStart cleared
| (see www.net-snmp.org)
| 3.2+
|-
| nsNotifyRestart
| NET-SNMP-MIB
| 1.3.6.1.4.1.8072.4.0.3
| { OID }
| Reboot notification, should raise and alarm until nsNotifyStart cleared
| (see www.net-snmp.org)
| 3.2+
|}

====[[TB-MIB|TB-MIB SNMP Trap/Notification]]====

{| cellpadding="0" border="0" style="width: 820px;" class="wikitable"
|-
! Trap Name
! Details
! OID
! OBJECTS
! CONSIDERED AS AN ALARM
! RELEASE
|-
| tbNapAvailability
| The network access point has a new percentage of availability for calls
# For TDM networks (tbNapSignalingType='''isdn'''(1), '''ss7'''(2), '''casr2'''(6)) this means there are a percentage of channels available for calls. ss7 includes sigtran signaling type. 
# For SIP networks (tbNapSignalingType='''sip'''(3)), this means the remote SIP device is answering or not SIP OPTIONS polling messages and calls can be or can`t be made to this network. 
# When using H.248 (tbNapSignalingType='''tdmMedia'''(5), '''voipMedia'''(4)) this means there are TDM channels or RTP ports available or not for calls.
| 1.3.6.1.4.1.21776.1.1.2.1.0.1
| { tbNapName, tbNapSignalingType, tbNapAvailablePercent }
| When tbNapAvailablePercent=0
| 2.8+
|-
| tbPwrSupplyState
| The redundant power supply has a new state. tbHwPwrSupplyStatus can be: '''good'''(0) '''failure'''(1)
| 1.3.6.1.4.1.21776.1.1.2.1.0.2
| { tbHwPwrSupplyName, tbHwPwrSupplyStatus }
| When tbHwPwrSupplyStatus=1
| 2.8+
|-
| tbNp1State
| The N+1 patch panel has a new state. tbHaNp1FunctionalState can be: '''unknown'''(-1) '''fault'''(0): There is no access to the N+1 patch panel '''unprotected'''(1): Standby unit is not available '''unprotectedSwitched'''(2): Standby unit is active and replaced primary unit is not ready to take over '''healthy'''(3): N+1 unit is normal and standby unit is available '''healthySwitched'''(4): N+1 unit is switched to the standby unit and replaced primary is available
| 1.3.6.1.4.1.21776.1.1.2.1.0.3
| { tbHaNp1Name, tbHaNp1FunctionalState }
| When tbHaNp1FunctionalState=0 OR tbHaNp1FunctionalState=1 OR tbHaNp1FunctionalState=2, it is major.
| 2.8+
|-
| tbAppState
| This toolpack application has a new state. tbHaAppCurrentState can be: '''unknown'''(100) '''notRunning'''(101) '''starting'''(102) '''ready'''(103) '''shuttingDown'''(104) '''goingManagement'''(105) '''fault'''(106)
| 1.3.6.1.4.1.21776.1.1.2.1.0.4
| { tbHaAppName, tbHaAppCurrentState, tbHaAppHostName }
| All tbHaAppCurrentState states are alarms except 103
| 2.8+
|-
| tbAppHaState
| This toolpack high availability application has changed state. tbHaAppHaCurrentState can be: '''notPresent'''(0) '''active'''(1) '''standby'''(2)
| 1.3.6.1.4.1.21776.1.1.2.1.0.5
| { tbHaAppName, tbHaAppHaCurrentState, tbHaAppHostName }
| Value 0 is an alarm only in 1+1 mode
| 2.8+
|-
| tbClkGradeState
| The network synchronization clock from this interface has a new grade. tbClockType can be: '''none'''(1) '''osc'''(2) '''trunk'''(3) '''netRef1'''(4) '''netRef2'''(5) '''ptmc1'''(6) '''ptmc2'''(7) '''ct8a'''(8) '''ct8b'''(9) '''mbl'''(10) '''bits'''(11) '''ds3'''(12) '''sonetSdh'''(13) '''holdover'''(14) tbClockGrade can be: '''unqualified'''(0) '''beingQualified'''(1) '''qualified'''(2) '''qualifiedForRecovery'''(3)
| 1.3.6.1.4.1.21776.1.1.2.1.0.6
| { tbClockName, tbClockType, tbClockGrade }
| When Object 'tbClockGrade=0' or 'tbClockGrade=1' Cleared by 'tbClockGrade=2' or 'tbClockGrade=3'
| 2.8+
|-
| tbClkActiveState
| This interface has been selected or not to provide the network synchronization clock for the whole system. tbClockActive can be: '''no'''(0) '''yes'''(1)
| 1.3.6.1.4.1.21776.1.1.2.1.0.7
| { tbClockName, tbClockType, tbClockActive }
| When ALL OBJECTS report tbClockActive=0
| 2.8+
|-
| tbIsdnDChannelState
| The signaling channel for this ISDN interface has changed. tbIsdnDChannelUp can be: '''no'''(0) '''yes'''(1)
| 1.3.6.1.4.1.21776.1.1.2.1.0.8
| { tbIsdnDescription, tbIsdnDChannelUp }
| When tbIsdnDChannelUp=0
| 2.8+
|-
| tbCASPhysicalLineState
| The interface for this CAS stack has changed. tbCasPhysicalLineUp can be: '''no'''(0) '''yes'''(1)
| 1.3.6.1.4.1.21776.1.1.2.1.0.9
| { tbCasDescription, tbCasPhysicalLineUp }
| When tbCasPhysicalLineUp=0
| 2.8+
|-
| tbSipState
| The SIP stack state has changed. tbSipCurrentState can be: '''no'''(0) '''yes'''(1)
| 1.3.6.1.4.1.21776.1.1.2.1.0.10
| { tbSipDescription, tbSipCurrentState }
| When tbSipCurrentState=0
| 2.8+
|-
| tbH248MgcState
| The H.248 communication state between this unit and the Media Gateway Controller has changed. tbH248MgcCurrentState can be: '''up'''(1) '''down'''(2) '''unknown'''(3)
| 1.3.6.1.4.1.21776.1.1.2.1.0.11
| { tbH248MgcName, tbH248MgcCurrentState }
| When tbH248MgcCurrentState=2 OR tbH248MgcCurrentState=3
| 2.8+
|-
| tbHostUpdateAvailableState
| The availability state of the host update has changed. tbHostUpdateAvailable can be: '''false'''(0) '''true'''(1) '''notSupported'''(2) '''unknown'''(3) '''disabled'''(4)
| 1.3.6.1.4.1.21776.1.1.2.1.0.12
| { tbHostName, tbHostUpdateAvailable }
| '''__'''
| 2.8+
|}

 Example of packet capture:
tcpdump port 162 -i mgmt0 -s 0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on mgmt0, link-type EN10MB (Ethernet), capture size 65535 bytes
14:08:51.491789 IP 10.7.0.13.37452 > 10.7.0.221.snmptrap: V2Trap(144) system.sysUpTime.0=9546160 S:1.1.4.1.0=S:1.1.5.4
interfaces.ifTable.ifEntry.ifIndex.452160.26=26 interfaces.ifTable.ifEntry.ifAdminStatus.452160.26=1
interfaces.ifTable.ifEntry.ifOperStatus.452160.26=1 S:1.1.4.3.0=E:8072.3.2.10

== Note ==
The '''ifIndex''' is a random value that can change after configuring the system, or adding new elements. This should not be relied on as a reference value. Please use the '''ifDescr''' instead.

=== SNMP SET ===
The '''SNMP SET''' command is not supported by TelcoBridges products. However, a [[Northbound_interface:RESTful|RESTful API]] can be used to change the configuration remotely.

 

== Configuration ==

*[[Toolpack:System_Settings_D#SNMP|Configuring SNMP for version 3.2]]
*[[Toolpack:System_Settings_D#SNMP|Configuring SNMP for version 3.0]]

*[[ProSBC:Zabbix configuration with Telcobridges products|Zabbix Configuration]]
<div class="mw-collapsible mw-collapsed" data-collapsetext="other versions" data-expandtext="Click here for other versions" style="width: 400px;">
*[[Toolpack:System_Settings_C#SNMP|Configuring SNMP for version 2.10]]
*[[Toolpack:System_Settings_B#SNMP|Configuring SNMP for version 2.9]]
*[[Toolpack:System_Settings_A#SNMP|Configuring SNMP for version 2.8]]
*[[tbSnmpAgent Configuration|Configuring SNMP for version 2.7]]
''The below procedures should be used to support SNMP v1 '''ONLY''' for '''Toolpack systems previous to 2.5.80''':
*[[Installing NetSNMP from an External Host]]
*[[TMG SNMP support|How to relay SNMP on TMG products]]

 
</div>

== Helpful resources ==
*[[Npp_tools|Notepad ++ tools for SNMP]]

== External Sources ==
*[http://en.wikipedia.org/wiki/Simple_Network_Management_Protocol Wikipedia article on SNMP]
*[http://www.net-snmp.org/ NetSNMP implementation of the SNMP protocol]
 

[[Category:Glossary]]
[[Category:Revise on Major]]

SNMP

2022-06-23T06:14:11Z

Joshua Puckett: /* TB-MIB SNMP Trap/Notification */

The Simple Network Management Protocol (SNMP) is used in network management systems to monitor attached hardware for changes in operation activity. SNMP provides a standardized approach to monitoring and managing network systems.
 For information on configuring your TMedia product to use the SNMP protocol, see the section labeled [[SNMP#Related Tasks|"'''Related Tasks'''"]].
 
== TelcoBridges and SNMP ==
TelcoBridges offers basic support for SNMP versions 1, 2, and 3. '''Toolpack supports SNMP V2 and V3 since release 2.5.80''' (see [[TMG-CONTROL_Version_2.5| Tctrl version history]]). This grants users the ability to remotely poll (or GET) system variables, known as Managed Objects, which are represented in files known as MIB modules. TelcoBridges currently offers polling on '''standard''' MIB modules (RTP, SONET, DS1, DS3, ISDN, etc...) and on the TelcoBridges '''privately defined''' module ([[TB-MIB|'''TB-MIB''']]). 
 
== Supported SNMP MIB modules ==
#[http://tools.ietf.org/html/rfc1213 RFC 1213 MIB II (RFC1213-MIB)]
#*All tables of the RFC1213-MIB are supported, '''with the exception of''':
#**ipRouteTable
#**EGP group
#**atTable
#[http://tools.ietf.org/html/rfc1573.txt RFC 1573 Evolution of Interfaces Group of MIB-II (IF-MIB)]
#*The following tables are supported:
#**ifTable
#**ifStackTable
#[http://tools.ietf.org/html/rfc2495 RFC 2495 DS1, J1, E1, DS2, and E2 Interfaces (DS1-MIB)]
#*The following tables of the DS1-MIB are supported:
#**Dsx1ConfigTable
#**Dsx1CurrentTable
#**Dsx1IntervalTable
#**Dsx1TotalTable
#[http://tools.ietf.org/html/rfc2496 RFC 2496 - Definitions of Managed Object for the DS3/E3 Interface Type (DS3-MIB)]
#*The following tables of the DS3-MIB are supported:
#**Dsx3ConfigTable
#**Dsx3CurrentTable
#**Dsx3IntervalTable
#**Dsx3TotalTable
#[http://tools.ietf.org/html/rfc1595 RFC 1595 - Definitions of Managed Object for the SONET/SDH Interface Type (SONET-MIB)]
#*The following tables of the SONET-MIB are supported:
#**sonetMediumTable
#**sonetSectionCurrentTable
#**sonetSectionIntervalTable
#**sonetLineCurrentTable
#**sonetLineIntervalTable
#**sonetFarendLineCurrentTable
#**sonetFarendLineIntervalTable
#**sonetPathCurrentTable
#**sonetPathIntervalTable
#**sonetFarendPathCurrentTable
#**sonetFarendPathIntervalTable
#**sonetVtCurrentTable
#**sonetVtIntervalTable
#**sonetFarendVtCurrentTable
#**sonetFarendVtIntervalTable
#[http://tools.ietf.org/html/rfc2127 RFC 2127 - ISDN Management Information Base using SMIv2 (ISDN-MIB)]
#*The following tables of the ISDN-MIB are supported:
#**isdnBearerGroup
#**isdnSignalingGroup
#[[TB-MIB|Telcobridges Private MIB module (TB-MIB)]]
#*tbHwCommon
#**tbHwIdentTable (Hardware Identification)
#**tbHwVersionTable (Hardware Version)
#**tbHwTempTable (Hardware Temperature)
#**tbHwPowerSupplyTable (Hardware Power Supply)
#**tbHwFanTable (Hardware Fan)
#*tbSwCommon
#**tbFeatureTable (Software Features Supported)
#**tbSwVersionTable (Software Version)
#**tbSwPerfTable (CPU Usage)
#*tbSignaling
#**tbMtp2
#**tbM2pa
#**tbM2ua
#**tbM3ua
#**tbIua
#**tbIsdn
#**tbCas
#**tbSip
#**tbH248
#*tbCalls
#*tbNAP
#*tbHaNp1
#*tbHaApp
#*tbClock

=== SNMP IF-MIB ifTable interface type ===
The following table provides the interfaces type supported by TelcoBridges (IF-MIB ifTable described in [https://tools.ietf.org/html/rfc1573 RFC1573]) with their corresponding description. The ifType are described in Internet Assigned Number Authority (IANA) in [http://www.iana.org/assignments/ianaiftype-mib IANAifType-MIB]
{| cellpadding="0" border="0" style="width: 820px;" class="wikitable"
|-
! IANA ifType
! TelcoBridges Interface description
|-
| ethernetCsmacd(6)
| Baseboard Ethernet interfaces
|-
| ds1(18)
| Trunks Line Interface
|-
| ds3(30)
| DS3 Line Interface
|-
| sonet(39)
| SONET/SDH Line Interface
|-
| sonetPath(50)
| SONET/SDH Line Service PATH (VC4/VC3/STS1/DS3)
|-
| sonetVT(51)
| SONET/SDH Line Service SECTION (VC11/VC12/VT15/VT2)
|-
| isdn(63)
| ISDN Stack
|-
| lapd(77)
| ISDN LAPD Link (Primary)
|-
| lapd(77)
| ISDN LAPD Link (Backup)
|-
| isdn(63)
| IUA Link
|-
| isdn(63)
| IUA Peer
|-
| lapd(77)
| LAPD Link
|-
| ss7SigLink (156)
| SS7 M2PA Link
|-
| ss7SigLink (156)
| SS7 M2UA Link
|-
| ss7SigLink (156)
| SS7 M2UA Peer
|-
| ss7SigLink (156)
| Ss7 M3ua Sap
|-
| ss7SigLink (156)
| Ss7 M3ua Psp
|-
| ss7SigLink (156)
| Ss7 M3ua Psrv
|-
| ss7SigLink (156)
| Ss7 Mtp2 Link
|}

=== SNMP traps ===
The '''SNMP traps''' module of TelcoBridges products monitor the operation status of some MIBS OIDs and generates notifications when the states change. The default monitoring polling period is set to 1 minute. This value can be modified in the [[SNMP#Configuration|SNMP configuration]].

====SNMP Trap/Notification====

{| cellpadding="0" border="0" style="width: 1200px;" class="wikitable"
|-
! Trap Name
! MIB
! OID
! OBJECTS
! CONSIDERED AS AN ALARM
! RFC
! RELEASE
|-
| linkDown
| IF-MIB
| 1.3.6.1.6.3.1.1.5.3
| { ifIndex, ifAdminStatus, ifOperStatus, ifDescr }
| When ifAdminStatus=1 & ifOperStatus=2, In certain conditions could be critical, this trap should raise an alarm.
| RFC1573
| 2.8+
|-
| linkUp
| IF-MIB
| 1.3.6.1.6.3.1.1.5.4
| { ifIndex, ifAdminStatus, ifOperStatus, ifDescr }
| Transition from network interface Down state. Normal clear trap for linkDown alarm
| RFC1573
| 2.8+
|-
| ColdStart
| IF-MIB
| 1.3.6.1.6.3.1.1.5.1
| { OID }
| Notify some configuration changes, normally when the system is loading, Noncritical
| RFC3418
| 3.2+
|-
| WarmStart
| IF-MIB
| 1.3.6.1.6.3.1.1.5.2
| { OID }
| Notify some configuration changes, normally when the system is running, Noncritical
| RFC3418
| 3.2+
|-
| nsNotifyStart
| NET-SNMP-MIB
| 1.3.6.1.4.1.8072.4.0.1
| { OID }
| A notification that the agent has started running
| (see www.net-snmp.org)
| 3.2+
|-
| nsNotifyShutdown
| NET-SNMP-MIB
| 1.3.6.1.4.1.8072.4.0.2
| { OID }
| Shutdown notification, should raise and alarm until nsNotifyStart cleared
| (see www.net-snmp.org)
| 3.2+
|-
| nsNotifyRestart
| NET-SNMP-MIB
| 1.3.6.1.4.1.8072.4.0.3
| { OID }
| Reboot notification, should raise and alarm until nsNotifyStart cleared
| (see www.net-snmp.org)
| 3.2+
|}

====[[TB-MIB|TB-MIB SNMP Trap/Notification]]====

{| cellpadding="0" border="0" style="width: 820px;" class="wikitable"
|-
! Trap Name
! Details
! OID
! OBJECTS
! CONSIDERED AS AN ALARM
! RELEASE
|-
| tbNapAvailability
| The network access point has a new percentage of availability for calls
# For TDM networks (tbNapSignalingType='''isdn'''(1), '''ss7'''(2), '''casr2'''(6)) this means there are a percentage of channels available for calls. ss7 includes sigtran signaling type. 
# For SIP networks (tbNapSignalingType='''sip'''(3)), this means the remote SIP device is answering or not SIP OPTIONS polling messages and calls can be or can`t be made to this network. 
# When using H.248 (tbNapSignalingType='''tdmMedia'''(5), '''voipMedia'''(4)) this means there are TDM channels or RTP ports available or not for calls.
| 1.3.6.1.4.1.21776.1.1.2.1.0.1
| { tbNapName, tbNapSignalingType, tbNapAvailablePercent }
| When tbNapAvailablePercent=0
| 2.8+
|-
| tbPwrSupplyState
| The redundant power supply has a new state. tbHwPwrSupplyStatus can be: '''good'''(0) '''failure'''(1)
| 1.3.6.1.4.1.21776.1.1.2.1.0.2
| { tbHwPwrSupplyName, tbHwPwrSupplyStatus }
| When tbHwPwrSupplyStatus=1
| 2.8+
|-
| tbNp1State
| The N+1 patch panel has a new state. tbHaNp1FunctionalState can be: '''unknown'''(-1) '''fault'''(0): There is no access to the N+1 patch panel '''unprotected'''(1): Standby unit is not available '''unprotectedSwitched'''(2): Standby unit is active and replaced primary unit is not ready to take over '''healthy'''(3): N+1 unit is normal and standby unit is available '''healthySwitched'''(4): N+1 unit is switched to the standby unit and replaced primary is available
| 1.3.6.1.4.1.21776.1.1.2.1.0.3
| { tbHaNp1Name, tbHaNp1FunctionalState }
| When tbHaNp1FunctionalState=0 OR tbHaNp1FunctionalState=1 OR tbHaNp1FunctionalState=2, it is major.
| 2.8+
|-
| tbAppState
| This toolpack application has a new state. tbHaAppCurrentState can be: '''unknown'''(100) '''notRunning'''(101) '''starting'''(102) '''ready'''(103) '''shuttingDown'''(104) '''goingManagement'''(105) '''fault'''(106)
| 1.3.6.1.4.1.21776.1.1.2.1.0.4
| { tbHaAppName, tbHaAppCurrentState, tbHaAppHostName }
| All tbHaAppCurrentState states are alarms except 103
| 2.8+
|-
| tbAppHaState
| This toolpack high availability application has changed state. tbHaAppHaCurrentState can be: '''notPresent'''(0) '''active'''(1) '''standby'''(2)
| 1.3.6.1.4.1.21776.1.1.2.1.0.5
| { tbHaAppName, tbHaAppHaCurrentState, tbHaAppHostName }
| Value 0 is an alarm only in 1+1 mode
| 2.8+
|-
| tbClkGradeState
| The network synchronization clock from this interface has a new grade. tbClockType can be: '''none'''(1) '''osc'''(2) '''trunk'''(3) '''netRef1'''(4) '''netRef2'''(5) '''ptmc1'''(6) '''ptmc2'''(7) '''ct8a'''(8) '''ct8b'''(9) '''mbl'''(10) '''bits'''(11) '''ds3'''(12) '''sonetSdh'''(13) '''holdover'''(14) tbClockGrade can be: '''unqualified'''(0) '''beingQualified'''(1) '''qualified'''(2) '''qualifiedForRecovery'''(3)
| 1.3.6.1.4.1.21776.1.1.2.1.0.6
| { tbClockName, tbClockType, tbClockGrade }
| When Object 'tbClockGrade=0' or 'tbClockGrade=1' Cleared by 'tbClockGrade=2' or 'tbClockGrade=3'
| 2.8+
|-
| tbClkActiveState
| This interface has been selected or not to provide the network synchronization clock for the whole system. tbClockActive can be: '''no'''(0) '''yes'''(1)
| 1.3.6.1.4.1.21776.1.1.2.1.0.7
| { tbClockName, tbClockType, tbClockActive }
| When ALL OBJECTS report tbClockActive=0
| 2.8+
|-
| tbIsdnDChannelState
| The signaling channel for this ISDN interface has changed. tbIsdnDChannelUp can be: '''no'''(0) '''yes'''(1)
| 1.3.6.1.4.1.21776.1.1.2.1.0.8
| { tbIsdnDescription, tbIsdnDChannelUp }
| When tbIsdnDChannelUp=0
| 2.8+
|-
| tbCASPhysicalLineState
| The interface for this CAS stack has changed. tbCasPhysicalLineUp can be: '''no'''(0) '''yes'''(1)
| 1.3.6.1.4.1.21776.1.1.2.1.0.9
| { tbCasDescription, tbCasPhysicalLineUp }
| When tbCasPhysicalLineUp=0
| 2.8+
|-
| tbSipState
| The SIP stack state has changed. tbSipCurrentState can be: '''no'''(0) '''yes'''(1)
| 1.3.6.1.4.1.21776.1.1.2.1.0.10
| { tbSipDescription, tbSipCurrentState }
| When tbSipCurrentState=0
| 2.8+
|-
| tbH248MgcState
| The H.248 communication state between this unit and the Media Gateway Controller has changed. tbH248MgcCurrentState can be: '''up'''(1) '''down'''(2) '''unknown'''(3)
| 1.3.6.1.4.1.21776.1.1.2.1.0.11
| { tbH248MgcName, tbH248MgcCurrentState }
| When tbH248MgcCurrentState=2 OR tbH248MgcCurrentState=3
| 2.8+
|-
| tbHostUpdateAvailableState
| The availability state of the host update has changed. tbHostUpdateAvailable can be: '''false'''(0) '''true'''(1) '''notSupported'''(2) '''unknown'''(3) '''disabled'''(4)
| 1.3.6.1.4.1.21776.1.1.2.1.0.12
| { tbHostName, tbHostUpdateAvailable }
| '''__'''
| 2.8+
|}

 Example of packet capture:
tcpdump port 162 -i mgmt0 -s 0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on mgmt0, link-type EN10MB (Ethernet), capture size 65535 bytes
14:08:51.491789 IP 10.7.0.13.37452 > 10.7.0.221.snmptrap: V2Trap(144) system.sysUpTime.0=9546160 S:1.1.4.1.0=S:1.1.5.4
interfaces.ifTable.ifEntry.ifIndex.452160.26=26 interfaces.ifTable.ifEntry.ifAdminStatus.452160.26=1
interfaces.ifTable.ifEntry.ifOperStatus.452160.26=1 S:1.1.4.3.0=E:8072.3.2.10

== Note ==
The '''ifIndex''' is a random value that can change after configuring the system, or adding new elements. This should not be relied on as a reference value. Please use the '''ifDescr''' instead.

=== SNMP SET ===
The '''SNMP SET''' command is not supported by TelcoBridges products. However, a [[Northbound_interface:RESTful|RESTful API]] can be used to change the configuration remotely.

 

== Configuration ==

*[[Toolpack:System_Settings_D#SNMP|Configuring SNMP for version 3.2]]
*[[Toolpack:System_Settings_D#SNMP|Configuring SNMP for version 3.0]]

*[[ProSBC:Zabbix configuration with Telcobridges products|Zabbix Configuration]]
<div class="mw-collapsible mw-collapsed" data-collapsetext="other versions" data-expandtext="Click here for other versions" style="width: 400px;">
*[[Toolpack:System_Settings_C#SNMP|Configuring SNMP for version 2.10]]
*[[Toolpack:System_Settings_B#SNMP|Configuring SNMP for version 2.9]]
*[[Toolpack:System_Settings_A#SNMP|Configuring SNMP for version 2.8]]
*[[tbSnmpAgent Configuration|Configuring SNMP for version 2.7]]
''The below procedures should be used to support SNMP v1 '''ONLY''' for '''Toolpack systems previous to 2.5.80''':
*[[Installing NetSNMP from an External Host]]
*[[TMG SNMP support|How to relay SNMP on TMG products]]

 
</div>

== Helpful resources ==
*[[Npp_tools|Notepad ++ tools for SNMP]]

== External Sources ==
*[http://en.wikipedia.org/wiki/Simple_Network_Management_Protocol Wikipedia article on SNMP]
*[http://www.net-snmp.org/ NetSNMP implementation of the SNMP protocol]
 

[[Category:Glossary]]
[[Category:Revise on Major]]

SNMP

2022-06-23T06:07:47Z

Joshua Puckett: /* TB-MIB SNMP Trap/Notification */

The Simple Network Management Protocol (SNMP) is used in network management systems to monitor attached hardware for changes in operation activity. SNMP provides a standardized approach to monitoring and managing network systems.
 For information on configuring your TMedia product to use the SNMP protocol, see the section labeled [[SNMP#Related Tasks|"'''Related Tasks'''"]].
 
== TelcoBridges and SNMP ==
TelcoBridges offers basic support for SNMP versions 1, 2, and 3. '''Toolpack supports SNMP V2 and V3 since release 2.5.80''' (see [[TMG-CONTROL_Version_2.5| Tctrl version history]]). This grants users the ability to remotely poll (or GET) system variables, known as Managed Objects, which are represented in files known as MIB modules. TelcoBridges currently offers polling on '''standard''' MIB modules (RTP, SONET, DS1, DS3, ISDN, etc...) and on the TelcoBridges '''privately defined''' module ([[TB-MIB|'''TB-MIB''']]). 
 
== Supported SNMP MIB modules ==
#[http://tools.ietf.org/html/rfc1213 RFC 1213 MIB II (RFC1213-MIB)]
#*All tables of the RFC1213-MIB are supported, '''with the exception of''':
#**ipRouteTable
#**EGP group
#**atTable
#[http://tools.ietf.org/html/rfc1573.txt RFC 1573 Evolution of Interfaces Group of MIB-II (IF-MIB)]
#*The following tables are supported:
#**ifTable
#**ifStackTable
#[http://tools.ietf.org/html/rfc2495 RFC 2495 DS1, J1, E1, DS2, and E2 Interfaces (DS1-MIB)]
#*The following tables of the DS1-MIB are supported:
#**Dsx1ConfigTable
#**Dsx1CurrentTable
#**Dsx1IntervalTable
#**Dsx1TotalTable
#[http://tools.ietf.org/html/rfc2496 RFC 2496 - Definitions of Managed Object for the DS3/E3 Interface Type (DS3-MIB)]
#*The following tables of the DS3-MIB are supported:
#**Dsx3ConfigTable
#**Dsx3CurrentTable
#**Dsx3IntervalTable
#**Dsx3TotalTable
#[http://tools.ietf.org/html/rfc1595 RFC 1595 - Definitions of Managed Object for the SONET/SDH Interface Type (SONET-MIB)]
#*The following tables of the SONET-MIB are supported:
#**sonetMediumTable
#**sonetSectionCurrentTable
#**sonetSectionIntervalTable
#**sonetLineCurrentTable
#**sonetLineIntervalTable
#**sonetFarendLineCurrentTable
#**sonetFarendLineIntervalTable
#**sonetPathCurrentTable
#**sonetPathIntervalTable
#**sonetFarendPathCurrentTable
#**sonetFarendPathIntervalTable
#**sonetVtCurrentTable
#**sonetVtIntervalTable
#**sonetFarendVtCurrentTable
#**sonetFarendVtIntervalTable
#[http://tools.ietf.org/html/rfc2127 RFC 2127 - ISDN Management Information Base using SMIv2 (ISDN-MIB)]
#*The following tables of the ISDN-MIB are supported:
#**isdnBearerGroup
#**isdnSignalingGroup
#[[TB-MIB|Telcobridges Private MIB module (TB-MIB)]]
#*tbHwCommon
#**tbHwIdentTable (Hardware Identification)
#**tbHwVersionTable (Hardware Version)
#**tbHwTempTable (Hardware Temperature)
#**tbHwPowerSupplyTable (Hardware Power Supply)
#**tbHwFanTable (Hardware Fan)
#*tbSwCommon
#**tbFeatureTable (Software Features Supported)
#**tbSwVersionTable (Software Version)
#**tbSwPerfTable (CPU Usage)
#*tbSignaling
#**tbMtp2
#**tbM2pa
#**tbM2ua
#**tbM3ua
#**tbIua
#**tbIsdn
#**tbCas
#**tbSip
#**tbH248
#*tbCalls
#*tbNAP
#*tbHaNp1
#*tbHaApp
#*tbClock

=== SNMP IF-MIB ifTable interface type ===
The following table provides the interfaces type supported by TelcoBridges (IF-MIB ifTable described in [https://tools.ietf.org/html/rfc1573 RFC1573]) with their corresponding description. The ifType are described in Internet Assigned Number Authority (IANA) in [http://www.iana.org/assignments/ianaiftype-mib IANAifType-MIB]
{| cellpadding="0" border="0" style="width: 820px;" class="wikitable"
|-
! IANA ifType
! TelcoBridges Interface description
|-
| ethernetCsmacd(6)
| Baseboard Ethernet interfaces
|-
| ds1(18)
| Trunks Line Interface
|-
| ds3(30)
| DS3 Line Interface
|-
| sonet(39)
| SONET/SDH Line Interface
|-
| sonetPath(50)
| SONET/SDH Line Service PATH (VC4/VC3/STS1/DS3)
|-
| sonetVT(51)
| SONET/SDH Line Service SECTION (VC11/VC12/VT15/VT2)
|-
| isdn(63)
| ISDN Stack
|-
| lapd(77)
| ISDN LAPD Link (Primary)
|-
| lapd(77)
| ISDN LAPD Link (Backup)
|-
| isdn(63)
| IUA Link
|-
| isdn(63)
| IUA Peer
|-
| lapd(77)
| LAPD Link
|-
| ss7SigLink (156)
| SS7 M2PA Link
|-
| ss7SigLink (156)
| SS7 M2UA Link
|-
| ss7SigLink (156)
| SS7 M2UA Peer
|-
| ss7SigLink (156)
| Ss7 M3ua Sap
|-
| ss7SigLink (156)
| Ss7 M3ua Psp
|-
| ss7SigLink (156)
| Ss7 M3ua Psrv
|-
| ss7SigLink (156)
| Ss7 Mtp2 Link
|}

=== SNMP traps ===
The '''SNMP traps''' module of TelcoBridges products monitor the operation status of some MIBS OIDs and generates notifications when the states change. The default monitoring polling period is set to 1 minute. This value can be modified in the [[SNMP#Configuration|SNMP configuration]].

====SNMP Trap/Notification====

{| cellpadding="0" border="0" style="width: 1200px;" class="wikitable"
|-
! Trap Name
! MIB
! OID
! OBJECTS
! CONSIDERED AS AN ALARM
! RFC
! RELEASE
|-
| linkDown
| IF-MIB
| 1.3.6.1.6.3.1.1.5.3
| { ifIndex, ifAdminStatus, ifOperStatus, ifDescr }
| When ifAdminStatus=1 & ifOperStatus=2, In certain conditions could be critical, this trap should raise an alarm.
| RFC1573
| 2.8+
|-
| linkUp
| IF-MIB
| 1.3.6.1.6.3.1.1.5.4
| { ifIndex, ifAdminStatus, ifOperStatus, ifDescr }
| Transition from network interface Down state. Normal clear trap for linkDown alarm
| RFC1573
| 2.8+
|-
| ColdStart
| IF-MIB
| 1.3.6.1.6.3.1.1.5.1
| { OID }
| Notify some configuration changes, normally when the system is loading, Noncritical
| RFC3418
| 3.2+
|-
| WarmStart
| IF-MIB
| 1.3.6.1.6.3.1.1.5.2
| { OID }
| Notify some configuration changes, normally when the system is running, Noncritical
| RFC3418
| 3.2+
|-
| nsNotifyStart
| NET-SNMP-MIB
| 1.3.6.1.4.1.8072.4.0.1
| { OID }
| A notification that the agent has started running
| (see www.net-snmp.org)
| 3.2+
|-
| nsNotifyShutdown
| NET-SNMP-MIB
| 1.3.6.1.4.1.8072.4.0.2
| { OID }
| Shutdown notification, should raise and alarm until nsNotifyStart cleared
| (see www.net-snmp.org)
| 3.2+
|-
| nsNotifyRestart
| NET-SNMP-MIB
| 1.3.6.1.4.1.8072.4.0.3
| { OID }
| Reboot notification, should raise and alarm until nsNotifyStart cleared
| (see www.net-snmp.org)
| 3.2+
|}

====[[TB-MIB|TB-MIB SNMP Trap/Notification]]====

{| cellpadding="0" border="0" style="width: 820px;" class="wikitable"
|-
! Trap Name
! Details
! OID
! OBJECTS
! CONSIDERED AS AN ALARM
! RELEASE
|-
| tbNapAvailability
| The network access point has a new percentage of availability for calls
# For TDM networks (tbNapSignalingType='''isdn'''(1), '''ss7'''(2), '''casr2'''(6)) this means there are a percentage of channels available for calls. ss7 includes sigtran signaling type. 
# For SIP networks (tbNapSignalingType='''sip'''(3)), this means the remote SIP device is answering or not SIP OPTIONS polling messages and calls can be or can`t be made to this network. 
# When using H.248 (tbNapSignalingType='''tdmMedia'''(5), '''voipMedia'''(4)) this means there are TDM channels or RTP ports available or not for calls.
| 1.3.6.1.4.1.21776.1.1.2.1.0.1
| { tbNapName, tbNapSignalingType, tbNapAvailablePercent }
| When tbNapAvailablePercent=0
| 2.8+
|-
| tbPwrSupplyState
| The redundant power supply has a new state. tbHwPwrSupplyStatus can be: '''good'''(0) '''failure'''(1)
| 1.3.6.1.4.1.21776.1.1.2.1.0.2
| { tbHwPwrSupplyName, tbHwPwrSupplyStatus }
| When tbHwPwrSupplyStatus=1
| 2.8+
|-
| tbNp1State
| The N+1 patch panel has a new state. tbHaNp1FunctionalState can be: '''unknown'''(-1) '''fault'''(0): There is no access to the N+1 patch panel '''unprotected'''(1): Standby unit is not available '''unprotectedSwitched'''(2): Standby unit is active and replaced primary unit is not ready to take over '''healthy'''(3): N+1 unit is normal and standby unit is available '''healthySwitched'''(4): N+1 unit is switched to the standby unit and replaced primary is available
| 1.3.6.1.4.1.21776.1.1.2.1.0.3
| { tbHaNp1Name, tbHaNp1FunctionalState }
| When tbHaNp1FunctionalState=0 OR tbHaNp1FunctionalState=1 OR tbHaNp1FunctionalState=2, it is major.
| 2.8+
|-
| tbAppState
| This toolpack application has a new state. tbHaAppCurrentState can be: '''unknown'''(100) '''notRunning'''(101) '''starting'''(102) '''ready'''(103) '''shuttingDown'''(104) '''goingManagement'''(105) '''fault'''(106)
| 1.3.6.1.4.1.21776.1.1.2.1.0.4
| { tbHaAppName, tbHaAppCurrentState, tbHaAppHostName }
| All tbHaAppCurrentState states are alarms except 103
| 2.8+
|-
| tbAppHaState
| This toolpack high availability application has changed state. tbHaAppHaCurrentState can be: '''notPresent'''(0) '''active'''(1) '''standby'''(2)
| 1.3.6.1.4.1.21776.1.1.2.1.0.5
| { tbHaAppName, tbHaAppHaCurrentState, tbHaAppHostName }
| Value 0 is an alarm only in 1+1 mode
| 2.8+
|-
| tbClkGradeState
| The network synchronization clock from this interface has a new grade. tbClockType can be: '''none'''(1) '''osc'''(2) '''trunk'''(3) '''netRef1'''(4) '''netRef2'''(5) '''ptmc1'''(6) '''ptmc2'''(7) '''ct8a'''(8) '''ct8b'''(9) '''mbl'''(10) '''bits'''(11) '''ds3'''(12) '''sonetSdh'''(13) '''holdover'''(14) tbClockGrade can be: '''unqualified'''(0) '''beingQualified'''(1) '''qualified'''(2) '''qualifiedForRecovery'''(3)
| 1.3.6.1.4.1.21776.1.1.2.1.0.6
| { tbClockName, tbClockType, tbClockGrade }
| '''__'''
| 2.8+
|-
| tbClkActiveState
| This interface has been selected or not to provide the network synchronization clock for the whole system. tbClockActive can be: '''no'''(0) '''yes'''(1)
| 1.3.6.1.4.1.21776.1.1.2.1.0.7
| { tbClockName, tbClockType, tbClockActive }
| When tbClockActive=0
| 2.8+
|-
| tbIsdnDChannelState
| The signaling channel for this ISDN interface has changed. tbIsdnDChannelUp can be: '''no'''(0) '''yes'''(1)
| 1.3.6.1.4.1.21776.1.1.2.1.0.8
| { tbIsdnDescription, tbIsdnDChannelUp }
| When tbIsdnDChannelUp=0
| 2.8+
|-
| tbCASPhysicalLineState
| The interface for this CAS stack has changed. tbCasPhysicalLineUp can be: '''no'''(0) '''yes'''(1)
| 1.3.6.1.4.1.21776.1.1.2.1.0.9
| { tbCasDescription, tbCasPhysicalLineUp }
| When tbCasPhysicalLineUp=0
| 2.8+
|-
| tbSipState
| The SIP stack state has changed. tbSipCurrentState can be: '''no'''(0) '''yes'''(1)
| 1.3.6.1.4.1.21776.1.1.2.1.0.10
| { tbSipDescription, tbSipCurrentState }
| When tbSipCurrentState=0
| 2.8+
|-
| tbH248MgcState
| The H.248 communication state between this unit and the Media Gateway Controller has changed. tbH248MgcCurrentState can be: '''up'''(1) '''down'''(2) '''unknown'''(3)
| 1.3.6.1.4.1.21776.1.1.2.1.0.11
| { tbH248MgcName, tbH248MgcCurrentState }
| When tbH248MgcCurrentState=2 OR tbH248MgcCurrentState=3
| 2.8+
|-
| tbHostUpdateAvailableState
| The availability state of the host update has changed. tbHostUpdateAvailable can be: '''false'''(0) '''true'''(1) '''notSupported'''(2) '''unknown'''(3) '''disabled'''(4)
| 1.3.6.1.4.1.21776.1.1.2.1.0.12
| { tbHostName, tbHostUpdateAvailable }
| '''__'''
| 2.8+
|}

 Example of packet capture:
tcpdump port 162 -i mgmt0 -s 0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on mgmt0, link-type EN10MB (Ethernet), capture size 65535 bytes
14:08:51.491789 IP 10.7.0.13.37452 > 10.7.0.221.snmptrap: V2Trap(144) system.sysUpTime.0=9546160 S:1.1.4.1.0=S:1.1.5.4
interfaces.ifTable.ifEntry.ifIndex.452160.26=26 interfaces.ifTable.ifEntry.ifAdminStatus.452160.26=1
interfaces.ifTable.ifEntry.ifOperStatus.452160.26=1 S:1.1.4.3.0=E:8072.3.2.10

== Note ==
The '''ifIndex''' is a random value that can change after configuring the system, or adding new elements. This should not be relied on as a reference value. Please use the '''ifDescr''' instead.

=== SNMP SET ===
The '''SNMP SET''' command is not supported by TelcoBridges products. However, a [[Northbound_interface:RESTful|RESTful API]] can be used to change the configuration remotely.

 

== Configuration ==

*[[Toolpack:System_Settings_D#SNMP|Configuring SNMP for version 3.2]]
*[[Toolpack:System_Settings_D#SNMP|Configuring SNMP for version 3.0]]

*[[ProSBC:Zabbix configuration with Telcobridges products|Zabbix Configuration]]
<div class="mw-collapsible mw-collapsed" data-collapsetext="other versions" data-expandtext="Click here for other versions" style="width: 400px;">
*[[Toolpack:System_Settings_C#SNMP|Configuring SNMP for version 2.10]]
*[[Toolpack:System_Settings_B#SNMP|Configuring SNMP for version 2.9]]
*[[Toolpack:System_Settings_A#SNMP|Configuring SNMP for version 2.8]]
*[[tbSnmpAgent Configuration|Configuring SNMP for version 2.7]]
''The below procedures should be used to support SNMP v1 '''ONLY''' for '''Toolpack systems previous to 2.5.80''':
*[[Installing NetSNMP from an External Host]]
*[[TMG SNMP support|How to relay SNMP on TMG products]]

 
</div>

== Helpful resources ==
*[[Npp_tools|Notepad ++ tools for SNMP]]

== External Sources ==
*[http://en.wikipedia.org/wiki/Simple_Network_Management_Protocol Wikipedia article on SNMP]
*[http://www.net-snmp.org/ NetSNMP implementation of the SNMP protocol]
 

[[Category:Glossary]]
[[Category:Revise on Major]]

Application trace level

2022-05-31T05:32:30Z

Joshua Puckett:

{{DISPLAYTITLE:How to Lower The Trace Level on an Application}}
Sometimes a lower level log trace than default is needed in troubleshooting an issue. Each application has it's own trace level that can be changed via the  the CLI. When creating a [[TBReport|TBReport]] past logs are fetched and compressed, if the trace levels were lowered during troubleshooting the report will include the more detailed logs. 

== Lowering Application Trace Level via CLI ==
<ol>
<li value="1">Log into your TelcoBridges unit via SSH and type 'tbx_cli_tools_remote'
This should present you with the following screen, which is a list of applications running on this system.
[[Image:tbxtools_list.png]]</li>
<li value="2">Select the application to open. (In our example we will use Gateway)
[[Image:Gateway_app.png]]</li>
<li value="3">Every app will have a slightly different set of commands as there are some application specific functions. To see the available actions you can press '?' at any time. For ALL applications the character 'T' will prompt you to enter a new trace level. Note the 'T' is capital, a lower-case 't' is assigned to a different action ex. Terminate Call in the 'gateway' application 
[[Image:tracelevel_prompt.png]]</li>
<li value="4">The application will show the current trace level in the format <nowiki>0x3</nowiki> where '<nowiki>3</nowiki>' is the current level. 
[[Image:tracelevel_seta.png]]</li>
<li value="5">Disregard this formatting and type the desired level as a single integer.
[[Image:tracelevel_setb.png]]</li>
<li value="6">Press "enter" and your change will be applied. You can check the logs for confirmation.
[[Image:tracelevel_setc.png]]
</li>
</ol>

Application trace level

2022-05-31T05:29:27Z

Joshua Puckett: Created page with "{{DISPLAYTITLE:How to Lower The Trace Level on an Application}} Sometimes a lower level log trace than default is needed in troubleshooting an issue. Each application has it's..."

{{DISPLAYTITLE:How to Lower The Trace Level on an Application}}
Sometimes a lower level log trace than default is needed in troubleshooting an issue. Each application has it's own trace level that can be changed via the  the CLI. When creating a [[TBReport|TBReport]] past logs are fetched and compressed, if the trace levels were lowered during troubleshooting the report will include the more detailed logs. 

== Lowering Application Trace Level via CLI ==
<ol>
<li value="1">Log into your TelcoBridges unit via SSH and type 'tbx_cli_tools_remote'
This should present you with the following screen, which is a list of applications running on this system.
[[Image:tbxtools_list.png]]</li>
<li value="2">Select the application to open. (In our example we will use Gateway)
[[Image:Gateway_app.png]]</li>
<li value="3">Every app will have a slightly different set of commands as there are some application specific functions. To see the available actions you can press '?' at any time. For ALL applications the character 'T' will prompt you to enter a new trace level. Note the 'T' is capital, a lower-case 't' is assigned to a different action ex. Terminate Call in the 'gateway' application 
[[Image:tracelevel_prompt.png]]</li>
<li value="4">The application will show the current trace level in the format <nowiki>0x3</nowiki> where '<nowiki>3</nowiki>' is the current level. Disregard this formatting and type the desired level as a single integer.
[[Image:tracelevel_seta.png]]
[[Image:tracelevel_setb.png]]
[[Image:tracelevel_setc.png]]
</li>
</ol>

File:Tracelevel setb.png

2022-05-31T05:29:16Z

Joshua Puckett: Joshua Puckett uploaded a new version of File:Tracelevel setb.png

File:Tracelevel seta.png

2022-05-31T05:29:05Z

Joshua Puckett: Joshua Puckett uploaded a new version of File:Tracelevel seta.png

File:Tracelevel setc.png

2022-05-31T05:27:50Z

Joshua Puckett:

File:Tracelevel setb.png

2022-05-31T05:27:41Z

Joshua Puckett:

File:Tracelevel seta.png

2022-05-31T05:27:33Z

Joshua Puckett:

File:Tracelevel prompt.png

2022-05-31T05:26:27Z

Joshua Puckett: Joshua Puckett uploaded a new version of File:Tracelevel prompt.png

File:Tracelevel prompt.png

2022-05-31T05:25:02Z

Joshua Puckett:

File:Gateway app.png

2022-05-31T05:23:53Z

Joshua Puckett:

File:Tbxtools list.png

2022-05-31T05:23:38Z

Joshua Puckett:

How to troubleshoot call routing

2022-05-31T03:59:47Z

Joshua Puckett:

{{DISPLAYTITLE:How to Troubleshoot Call Routing}}
To debug calls, different methods can be used: 

== Using the Call Detail Records ==

This can be done in the configuration database, using RADIUS or in text files. See [[Call_detail_record|Call Detail Records (CDR)]]

== Using the Call Trace Tool  ==

Call Trace was created to trace the callflow from any incoming call through the Tmedia system. It allows to see the incoming call, outgoing calls, TDM channel, SIP SDP and more. This can be accessed from the Web Portal. You can create a filter to see call information. See [[Using Unique call trace|Using Call Trace]]. 

== Using the web portal status ==
<pre>Status -> NAP -> Edit</pre>
You can see how many instantaneous calls incoming, outgoing, in the last hour, in the last 24 hours, etc.

== Using the applications log files ==
 Brief details on the application:

*'''gateway''' application is for high-level call routing, like called number, Network Access Points, routing scripts, regular expressions.
*'''toolpack_engine''' handles the protocols (SS7, SIP, ISDN, CAS, Sigtran, etc.) and media (RTP, TDM, tones, etc) 
*'''toolpack_sys_manager''' handles the configuration of the system
*'''tboamapp''' controls the startup of the applications and system upgrades 
*'''tbstreamserver''' is used for playing and recording files; by default this application is not started. See How to Start Stream Server
*'''tblogtrace''' are low-level logs coming from the Telecom platform
*'''tbsnmpagent/tbsnmpmux''' allows SNMP queries to unit
*'''tbuctwriter''' captures call traces

=== Change an Application log trace level ===
 You can change the trace level of the application here:
<pre>Applications-> [Application name] -> Advanced parameters -> Default Trace Level -> Save</pre>
And then activate the new configuration. Trace level 3 for '''gateway '''and '''toolpack_engine''' application will give most of the required information. 
For a more detailed walk-through see: [[Application_trace_level|How to change an application's trace level]]

=== Get log files from web portal ===
<pre>Maintenance -> Logs -> Select filename -> 2000 lines -> select Read</pre>

=== Get the log files from the server ===
You can get the files directly from the server running Toolpack. Connect sFTP (for example using Winscp or filezilla) to the management port of the unit and get the files at this location:
<pre>/lib/tb/toolpack/setup/12358/2.9/apps/</pre>

== Using the signaling traces ==

You can get the signaling traces (SS7, ISDN and SIP) using the tbsigtrace program: [[Toolpack Debug Application:Tbsigtrace|using tbsigtrace]]

== Using the Toolpack programs backdoor tool ==

You can access to the toolpack applications directly by using the tbx_cli_tools_remote application. This application allows full control over any Toolpack application. This allows for example to view real time calls going through the Toolpack Engine.

Select this to learn [[How to use tbx cli tools remote program|How to use tbx cli tools remote program]]. 

Typical errors:

404 not found

How to troubleshoot call routing

2022-05-31T03:19:28Z

Joshua Puckett: /* Change an Application log trace level */

{{DISPLAYTITLE:How to Troubleshoot Call Routing}}
To debug calls, different methods can be used: 

== Using the Call Detail Records ==

This can be done in the configuration database, using RADIUS or in text files. See [[Call_detail_record|Call Detail Records (CDR)]]

== Using the Call Trace Tool  ==

Call Trace was created to trace the callflow from any incoming call through the Tmedia system. It allows to see the incoming call, outgoing calls, TDM channel, SIP SDP and more. This can be accessed from the Web Portal. You can create a filter to see call information. See [[Using Unique call trace|Using Call Trace]]. 

== Using the web portal status ==
<pre>Status -> NAP -> Edit</pre>
You can see how many instantaneous calls incoming, outgoing, in the last hour, in the last 24 hours, etc.

== Using the applications log files ==
 Brief details on the application:

*'''gateway''' application is for high-level call routing, like called number, Network Access Points, routing scripts, regular expressions.
*'''toolpack_engine''' handles the protocols (SS7, SIP, ISDN, CAS, Sigtran, etc.) and media (RTP, TDM, tones, etc) 
*'''toolpack_sys_manager''' handles the configuration of the system
*'''tboamapp''' controls the startup of the applications and system upgrades 
*'''tbstreamserver''' is used for playing and recording files; by default this application is not started. See How to Start Stream Server
*'''tblogtrace''' are low-level logs coming from the Telecom platform
*'''tbsnmpagent/tbsnmpmux''' allows SNMP queries to unit
*'''tbuctwriter''' captures call traces

=== Change an Application log trace level ===
 You can change the trace level of the application here:
<pre>Applications-> [Application name] -> Advanced parameters -> Default Trace Level -> Save</pre>
And then activate the new configuration. Trace level 3 for '''gateway '''and '''toolpack_engine''' application will give most of the required information. 
For a more detailed walk-through see: [[Application_log_level|How to change an application's log level]]

=== Get log files from web portal ===
<pre>Maintenance -> Logs -> Select filename -> 2000 lines -> select Read</pre>

=== Get the log files from the server ===
You can get the files directly from the server running Toolpack. Connect sFTP (for example using Winscp or filezilla) to the management port of the unit and get the files at this location:
<pre>/lib/tb/toolpack/setup/12358/2.9/apps/</pre>

== Using the signaling traces ==

You can get the signaling traces (SS7, ISDN and SIP) using the tbsigtrace program: [[Toolpack Debug Application:Tbsigtrace|using tbsigtrace]]

== Using the Toolpack programs backdoor tool ==

You can access to the toolpack applications directly by using the tbx_cli_tools_remote application. This application allows full control over any Toolpack application. This allows for example to view real time calls going through the Toolpack Engine.

Select this to learn [[How to use tbx cli tools remote program|How to use tbx cli tools remote program]]. 

Typical errors:

404 not found

File:UDL-MIB.zip

2022-05-20T02:25:22Z

Joshua Puckett: Contains two User Defined Languages for Notepad++ for MIB files, one for Dark Mode and one for Light Mode. Both naming conventions are correct, just extract and copy contents to the UDL folder.

== Summary ==
Contains two User Defined Languages for Notepad++ for MIB files, one for Dark Mode and one for Light Mode. Both naming conventions are correct, just extract and copy contents to the UDL folder.

Npp tools

2022-05-20T02:22:10Z

Joshua Puckett:

{{DISPLAYTITLE:Notepad ++ tools for SNMP}}

__NOTOC__

== Explenation ==
Notepad++ is a powerful text editor that implements some basic tagging and formatting that gives it some limited IDE Functionality. It is equipped with many languages by default and can format their text automatically based on the file extension. It also allows you to create your own User Defined Languages (UDLs) to format other filetypes in a custom manner. This page includes two UDLs for viewing MIB files in NotePad++, both UDLs are identical in function but one has the colors modified for better viewing for those who prefer Notepad++'s 'darkmode' view.

== Installation ==
* For installation open your UserDefinedLanguage folder, generally found at: <pre>.\AppData\Roaming\Notepad++\userDefineLangs</pre>

* Or find it via the NotePad++ drop down menu under: <pre>Languages -> User Defined Languages -> Open User Defined Language Folder</pre>

* Unzip the zipped folder below and find two .xml files 'userDefineLang-MIB.xml' for Lightmode users, and 'userDefineLang-MIB-DM.xml' for Darkmode users.

* Copy both, or just the desired UDL from that zipped folder into the UserDefinedLanguage folder mentioned above.

* Restart your Notepad++ Application

* Open the desired file and apply the language through the same menu. <pre>Languages -> MIB/MIB (Dark Mode)</pre>

For more information please reference: [https://npp-user-manual.org/docs/user-defined-language-system/ Notepad++ User Manual on UDLs]

[[Media:UDL-MIB.zip|User Defined Languages Light Mode and DarkMode]]

Npp tools

2022-05-20T02:20:32Z

Joshua Puckett: /* Installation */

Npp tools

2022-05-18T08:58:00Z

Joshua Puckett: /* MIB UDL Files */

Npp tools

2022-05-18T08:53:13Z

Joshua Puckett: Replaced content with "{{DISPLAYTITLE:Notepad ++ tools for SNMP}} __NOTOC__ =Explanation= Notepad++ is a powerful text editor that implements some basic tagging and formatting that gives it so..."

File:Black white list.csv

2022-05-12T16:33:03Z

Joshua Puckett:

Adding White or Black listing to Routing Script

2022-05-11T04:55:52Z

Joshua Puckett: /* White and black listing file */

{{DISPLAYTITLE:Adding White or Black listing to Routing Script}}

This shows how to add White or Black listing to any Routing scripts. With this script, any called or calling number prefix can be blacklisted or whitelisted. This script can be assigned globally, or per NAP. For this you choose the "scope" to be "global" or "per_nap". It also reads a .csv file which has the called and calling number list (default name 'black_white_list.csv').
A blacklisted called number set globally will block anyone trying to reach that number (or number prefix). A whitelisted calling number will only allow calls from these calling numbers in the system - all other calls will be dropped.
 

== Setting up White and Black Listing Scripts ==

To setup a Filter, the main script needs to be modified. The main script can be either simple_routing.rb, or any other script. 

First, go to the routing script section of the Web portal
<pre>Gateway -> Routing scripts -> Example Scripts -> simple_routing.rb [Edit]
</pre>
Three things need to be added. At the start of the script: 
<pre>require 'black_white_listing'
</pre>
In the main class: 
<pre>include BlackWhiteListing
</pre>
<pre>before_filter :method => :black_white_listing, :scope => :global
</pre>
 
The final script will look like this:
<pre>
require 'base_routing'
require 'black_white_listing'

class NapGroupAndWeightRouting < BaseRouting
include BlackWhiteListing

before_filter :method => :black_white_listing, :scope => :global

route_match :call_field_name => :called
route_match :call_field_name => :calling
route_match :call_field_name => :nap
route_match :method => :match_nap_availability
route_remap :call_field_name => :called, :route_field_name => :remapped_called
route_remap :call_field_name => :calling, :route_field_name => :remapped_calling
route_remap :call_field_name => :nap, :route_field_name => :remapped_nap
end
</pre>
== White and black listing file ==

The '[[Media:black_white_list.csv|black_white_list.csv]]' file needs to be formatted in a specific way. There are 4 columns: The first one is indicating the calling number (or calling number prefix). The second one indicates to whitelist 'w' or blacklist 'b' the number. The third one is indicating the called number (or called number prefix). The last one indicates to whitelist 'w' or blacklist 'b' the number. 
This example will blacklist the calling numbers 148240000 and 148240707, and also any calls that try to reach numbers starting with 450 or 514 :
{| class="wikitable"
|-
! calling !! calling_params !! called !! called_params
|-
| 148240707 || b || ||
|-
| 148240000 || b || ||
|-
| || || 450 || b
|-
| || || 514 || b
|}

== To add the white and black listing file to the system ==

# Click '''FileDB''' in the navigation panel
# Click '''Import new file'''
# Click '''Browse''' and select the 'black_white_list.csv' you wish to import.
# Click '''Import'''

[[Image:Import_new_file_black_white_listing.png]]

== To assign a white and black listing to a NAP ==
The scope needs to be set to "per_nap"
<pre> before_filter :method => :black_white_listing, :scope => :per_nap </pre>
And you need to add new NAP colums to assign the files to the NAPs:
<pre>Gateway -> Routes -> NAP Columns -> Create New NAP Column</pre>
'''Name''': black_white_list '''Type attributes''': dbfile '''Default''': black_white_list.csv 
[[Image:NAP black white listing.png]]

Npp tools

2022-05-06T04:57:40Z

Joshua Puckett:

{{DISPLAYTITLE:Notepad ++ tools for SNMP}}

__NOTOC__

=Explanation=
Notepad++ is a powerful text editor that implements some basic tagging and formatting that gives it some limited IDE Functionality. It is equipped with many languages by default and can format their text automatically based on the file extension. It also allows you to create your own User Defined Languages (UDLs) to format other filetypes in a custom manner. This page includes two UDLs for viewing MIB files in NotePad++, both UDLs are identical in function but one has the colors modified for better viewing for those who prefer Notepad++'s 'darkmode' view.

=Installation=
* For installation open your UserDefinedLanguage folder, generally found at: <pre>.\AppData\Roaming\Notepad++\userDefineLangs</pre>

* Or find it via the NotePad++ drop down menu under: <pre>Languages -> User Defined Languages -> Open User Defined Language Folder</pre>

* Copy the Text in the adjacent tabs 'Standard MIB UDL' for Lightmode users, and 'Darkmode MIB UDL' for Darkmode users.

* Save the copied text in a new file named 'userDefineLang-MIB.xml'

* Restart your Notepad++ Application

* Open the desired file and apply the language through the same menu. <pre>Languages -> MIB/MIB (Dark Mode)</pre>

For more information please reference: [https://npp-user-manual.org/docs/user-defined-language-system/ Notepad++ User Manual on UDLs]

=Standard MIB UDL=
<pre>
<NotepadPlus>
<UserLang name="MIB" ext="mib my" udlVersion="2.1">
<Settings>
<Global caseIgnored="no" allowFoldOfComments="no" foldCompact="no" forcePureLC="0" decimalSeparator="0" />
<Prefix Keywords1="no" Keywords2="no" Keywords3="no" Keywords4="no" Keywords5="no" Keywords6="no" Keywords7="no" Keywords8="no" />
</Settings>
<KeywordLists>
<Keywords name="Comments">00-- 01 02 03-- 04</Keywords>
<Keywords name="Numbers, prefix1"></Keywords>
<Keywords name="Numbers, prefix2">0x</Keywords>
<Keywords name="Numbers, extras1">A B C D E F a b c d e f</Keywords>
<Keywords name="Numbers, extras2"></Keywords>
<Keywords name="Numbers, suffix1"></Keywords>
<Keywords name="Numbers, suffix2"></Keywords>
<Keywords name="Numbers, range">..</Keywords>
<Keywords name="Operators1">, ;  ::= ( ) { } |</Keywords>
<Keywords name="Operators2"></Keywords>
<Keywords name="Folders in code1, open"></Keywords>
<Keywords name="Folders in code1, middle"></Keywords>
<Keywords name="Folders in code1, close"></Keywords>
<Keywords name="Folders in code2, open"></Keywords>
<Keywords name="Folders in code2, middle"></Keywords>
<Keywords name="Folders in code2, close"></Keywords>
<Keywords name="Folders in comment, open"></Keywords>
<Keywords name="Folders in comment, middle"></Keywords>
<Keywords name="Folders in comment, close"></Keywords>
<Keywords name="Keywords1">" OBJECT IDENTIFIER"  
 " TYPE NOTATION"  
 " VALUE NOTATION"  
 AGENT-CAPABILITIES 
 MACRO 
 MODULE-COMPLIANCE 
 MODULE-IDENTITY 
 NOTATION 
 NOTIFICATION-GROUP 
 NOTIFICATION-TYPE 
 OBJECT-GROUP 
 OBJECT-IDENTITY 
 OBJECT-TYPE 
 TEXTUAL-CONVENTION 
 TRAP-TYPE 
 </Keywords>
<Keywords name="Keywords2">accessible-for-notify 
 not-accessible 
 not-implemented 
 read-create 
 read-only 
 read-write 
 write-only 
 </Keywords>
<Keywords name="Keywords3">" OCTET STRING"  
 ApplicationSyntax 
 at 
 AutonomousType 
 begemot 
 BIT 
 BITS 
 BridgeId 
 cisco 
 CiscoAbsZeroBasedCounter32 
 CiscoIpProtocol 
 ciscoMgmt 
 CiscoNetworkAddress 
 CiscoNetworkProtocol 
 CiscoPort 
 CiscoSnapShotAbsCounter32 
 Counter 
 Counter32 
 Counter64 
 CounterBasedGauge64 
 CountryCode 
 DateAndTime 
 directory 
 DisplayString 
 dlink 
 dns 
 DnsName 
 DnsType 
 dod 
 dot1dBasePort 
 egp 
 EnabledStatus 
 enterprises 
 experimental 
 Float 
 freeBSD 
 Gauge 
 Gauge32 
 Gauge64 
 host 
 hrDevice 
 hrDeviceTypes 
 hrFSTypes 
 hrStorage 
 hrStorageTypes 
 hrSystem 
 hrSystemUptime 
 ianaifType 
 IANAipRouteProtocol 
 IANAtunnelType 
 icmp 
 ifMIB 
 InetAddress 
 InetAddressDNS 
 InetAddressIPv4 
 InetAddressIPv4z 
 InetAddressIPv6 
 InetAddressIPv6z 
 InetAddressPrefixLength 
 InetAddressType 
 InetAutonomousSystemNumber 
 InetPortNumber 
 InetVersion 
 InetZoneIndex 
 InstancePointer 
 INTEGER 
 Integer32 
 Integer64 
 intel 
 intellan 
 InterfaceIndex 
 InterfaceIndexOrZero 
 interfaces 
 internet 
 ip 
 IpAddress 
 Ipv6Address 
 Ipv6AddressIfIdentifier 
 Ipv6AddressPrefix 
 IPv6FlowLabel 
 IPv6FlowLabelOrAny 
 ipv6IfEntry 
 Ipv6IfIndex 
 Ipv6IfIndexOrZero 
 iso 
 KBytes 
 MacAddress 
 mgmt 
 mib-2 
 NetNumber 
 netSnmp 
 netSnmpAgentOIDs 
 netSnmpDomains 
 netSnmpEnumerations 
 netSnmpExamples 
 netSnmpExperimental 
 netSnmpGroups 
 netSnmpModuleIDs 
 netSnmpNotifications 
 netSnmpObjects 
 NetworkAddress 
 NotificationName 
 nsExtendGroups 
 nsExtendObjects 
 ObjectName 
 ObjectSyntax 
 OCTET 
 Opaque 
 org 
 OwnerString 
 Percents 
 Percent 
 PhysAddress 
 PortList 
 private 
 rmon 
 RmonGauge64 
 RowPointer 
 RowStatus 
 security 
 SimpleSyntax 
 snmp 
 SnmpAdminString 
 snmpAuthProtocols 
 snmpDomains 
 snmpEngineID 
 snmpEngineTime 
 snmpMIBObjects 
 snmpModules 
 snmpPrivProtocols 
 snmpProxys 
 SnmpSecurityLevel 
 SnmpSecurityModel 
 SnmpTagValue 
 snmpTraps 
 snmpV2 
 StorageType 
 STRING 
 switch001 
 synology 
 system 
 sysUpTime 
 TAddress 
 tcp 
 TDomain 
 TestAndIncr 
 TimeInterval 
 Timeout 
 TimeStamp 
 TimeTicks 
 transmission 
 TruthValue 
 ucdavis 
 UCDErrorFix 
 UCDErrorFlag 
 ucdExperimental 
 ucdInternal 
 udp 
 Unsigned32 
 Unsigned64 
 URLString 
 VariablePointer 
 VlanId 
 VlanIndex 
 VlanPriority 
 VlanType 
 ZeroBasedCounter32 
 ZeroBasedCounter64 
 zeroDotZero 
 </Keywords>
<Keywords name="Keywords4">current 
 deprecated 
 mandatory 
 obsolete 
 optional 
 </Keywords>
<Keywords name="Keywords5">" SEQUENCE OF"  
 ACCESS 
 BEGIN 
 CHOICE 
 CONTACT-INFO 
 CREATION-REQUIRES  
 DEFINITIONS 
 DEFVAL  
 DESCRIPTION 
 DISPLAY-HINT 
 END 
 ENTERPRISE 
 EXPORTS 
 FROM 
 GROUP  
 IMPLICIT 
 IMPORTS 
 INCLUDES 
 INDEX 
 LAST-UPDATED 
 MANDATORY-GROUPS  
 MAX 
 MAX-ACCESS 
 MIN 
 MIN-ACCESS  
 MODULE  
 NOTIFICATIONS 
 OBJECT 
 OBJECTS 
 OF 
 ORGANIZATION 
 PRODUCT-RELEASE 
 REFERENCE 
 REVISION 
 SEQUENCE 
 SIZE 
 STATUS  
 SUPPORTS  
 SYNTAX  
 UNITS 
 VARIABLES 
 VARIATION  
 WRITE-SYNTAX  
 </Keywords>
<Keywords name="Keywords6"></Keywords>
<Keywords name="Keywords7"></Keywords>
<Keywords name="Keywords8">ATM-MIB 
 ATM-TC-MIB 
 ATM2-MIB 
 BEGEMOT-ATM-FREEBSD-MIB 
 BEGEMOT-ATM-MIB 
 BEGEMOT-BRIDGE-MIB 
 BEGEMOT-HAST-MIB 
 BEGEMOT-HOSTRES-MIB 
 BEGEMOT-IP-MIB 
 BEGEMOT-MIB 
 BEGEMOT-MIB2-MIB 
 BEGEMOT-NETGRAPH-MIB 
 BEGEMOT-PF-MIB 
 BEGEMOT-WIRELESS-MIB 
 BRIDGE-MIB 
 CISCO-CDP-MIB 
 CISCO-SMI 
 CISCO-TC 
 CISCO-VTP-MIB 
 CISCOSB-1-BONJOUR-SERVICE-MIB 
 CISCOSB-AAA 
 CISCOSB-BANNER-MIB 
 CISCOSB-BONJOUR-MIB 
 CISCOSB-BRGMACSWITCH-MIB 
 CISCOSB-BRIDGE-SECURITY 
 CISCOSB-BRIDGEMIBOBJECTS-MIB 
 CISCOSB-CDP-MIB 
 CISCOSB-CLI-MIB 
 CISCOSB-COPY-MIB 
 CISCOSB-CPU-COUNTERS-MIB 
 CISCOSB-DEBUGCAPABILITIES-MIB 
 CISCOSB-DEVICEPARAMS-MIB 
 CISCOSB-DHCP-MIB 
 CISCOSB-DHCPCL-MIB 
 CISCOSB-DHCPv6 
 CISCOSB-DHCPv6-CLIENT 
 CISCOSB-DHCPv6-RELAY 
 CISCOSB-DNSCL-MIB 
 CISCOSB-DOT1X-MIB 
 CISCOSB-ENDOFMIB-MIB 
 CISCOSB-EVENTS-MIB 
 CISCOSB-GVRP-MIB 
 CISCOSB-IP 
 CISCOSB-JUMBOFRAMES-MIB 
 CISCOSB-MIB 
 CISCOSB-MIR-MIB 
 CISCOSB-MULTISESSIONTERMINAL-MIB 
 CISCOSB-SECSD-MIB 
 CISCOSB-SMARTPORTS-MIB 
 CISCOSB-SMON-MIB 
 CISCOSB-STORMCTRL-MIB 
 CISCOSB-TELNET-MIB 
 CISCOSB-TRACEROUTE-MIB 
 CISCOSB-TRAPS-MIB 
 CISCOSB-TRUNK-MIB 
 DISMAN-PING-MIB 
 DNS-RESOLVER-MIB 
 DNS-SERVER-MIB 
 EtherLike-MIB 
 FOKUS-MIB 
 FRAME-RELAY-DTE-MIB 
 FREEBSD-MIB 
 HC-RMON-MIB 
 HOST-RESOURCES-MIB 
 HOST-RESOURCES-TYPES 
 IANA-RTPROTO-MIB 
 IANAifType-MIB 
 IEEE8021-PAE-MIB 
 IEEE8023-LAG-MIB 
 IF-INVERTED-STACK-MIB 
 IF-MIB 
 INET-ADDRESS-MIB 
 INTEL-DCB-MIB 
 INTEL-LAN-ADAPTERS-MIB 
 IP-FORWARD-MIB 
 IP-MIB 
 IPV6-FLOW-LABEL-MIB 
 IPV6-ICMP-MIB 
 IPV6-MIB 
 IPV6-TC 
 IPV6-TCP-MIB 
 IPV6-UDP-MIB 
 LLDP-EXT-DOT1-MIB 
 LLDP-EXT-MED-MIB 
 LLDP-MIB 
 LM-SENSORS-MIB 
 MTA-MIB 
 NET-SNMP-AGENT-MIB 
 NET-SNMP-EXAMPLES-MIB 
 NET-SNMP-EXTEND-MIB 
 NET-SNMP-MIB 
 NET-SNMP-MONITOR-MIB 
 NET-SNMP-PASS-MIB 
 NET-SNMP-SYSTEM-MIB 
 NET-SNMP-TC 
 NET-SNMP-VACM-MIB 
 NETWORK-SERVICES-MIB 
 NOTIFICATION-LOG-MIB 
 OLD-RFC1213-SUPPL-MIB 
 P-BRIDGE-MIB 
 PerfHist-TC-MIB 
 PowerNet-MIB 
 Q-BRIDGE-MIB 
 RFC-1212 
 RFC-1215 
 RFC1155-SMI 
 RFC1213-MIB 
 RFC1215 
 RFC1215-TRAP 
 RIPv2-MIB 
 RMON-MIB 
 RMON2-MIB 
 SCTP-MIB 
 SMON-MIB 
 SMUX-MIB 
 SNMP-COMMUNITY-MIB 
 SNMP-FRAMEWORK-MIB 
 SNMP-MPD-MIB 
 SNMP-NOTIFICATION-MIB 
 SNMP-PROXY-MIB 
 SNMP-TARGET-MIB 
 SNMP-TLS-TM-MIB 
 SNMP-TSM-MIB 
 SNMP-USER-BASED-SM-MIB 
 SNMP-USM-AES-MIB 
 SNMP-USM-DH-OBJECTS-MIB 
 SNMP-VIEW-BASED-ACM-MIB 
 SNMPv2-CONF 
 SNMPv2-MIB 
 SNMPv2-SMI 
 SNMPv2-TC 
 SNMPv2-TM 
 SYNOLOGY-DISK-MIB 
 SYNOLOGY-EBOX-MIB 
 SYNOLOGY-FLASHCACHE-MIB 
 SYNOLOGY-ISCSILUN-MIB 
 SYNOLOGY-RAID-MIB 
 SYNOLOGY-SERVICES-MIB 
 SYNOLOGY-SHA-MIB 
 SYNOLOGY-SMART-MIB 
 SYNOLOGY-SPACEIO-MIB 
 SYNOLOGY-STORAGEIO-MIB 
 SYNOLOGY-SYSTEM-MIB 
 SYNOLOGY-UPS-MIB 
 TCP-MIB 
 TOKEN-RING-RMON-MIB 
 TRANSPORT-ADDRESS-MIB 
 TUNNEL-MIB 
 UCD-DEMO-MIB 
 UCD-DISKIO-MIB 
 UCD-DLMOD-MIB 
 UCD-IPFILTER-MIB 
 UCD-IPFWACC-MIB 
 UCD-SNMP-MIB 
 UCD-SNMP-MIB-OLD 
 UDP-MIB 
 </Keywords>
<Keywords name="Delimiters">00"  01 02"  03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23</Keywords>
</KeywordLists>

<Styles>
<WordsStyle name="DEFAULT" fgColor="000000" bgColor="FFFFFF" fontName="" fontStyle="0" nesting="0" />
<WordsStyle name="COMMENTS" fgColor="408080" bgColor="FFFFFF" fontName="" fontStyle="2" nesting="0" />
<WordsStyle name="LINE COMMENTS" fgColor="408080" bgColor="FFFFFF" fontName="" fontStyle="2" nesting="0" />
<WordsStyle name="NUMBERS" fgColor="FF8040" bgColor="FFFFFF" fontName="" fontStyle="1" nesting="0" />
<WordsStyle name="KEYWORDS1" fgColor="000000" bgColor="FFFFFF" fontName="" fontStyle="1" nesting="0" />
<WordsStyle name="KEYWORDS2" fgColor="8080FF" bgColor="FFFFFF" fontName="" fontStyle="3" nesting="0" />
<WordsStyle name="KEYWORDS3" fgColor="808040" bgColor="FFFFFF" fontName="" fontStyle="5" nesting="0" />
<WordsStyle name="KEYWORDS4" fgColor="008080" bgColor="FFFFFF" fontName="" fontStyle="3" nesting="0" />
<WordsStyle name="KEYWORDS5" fgColor="0080C0" bgColor="FFFFFF" fontName="" fontStyle="1" nesting="0" />
<WordsStyle name="KEYWORDS6" fgColor="000000" bgColor="FFFFFF" fontName="" fontStyle="1" nesting="0" />
<WordsStyle name="KEYWORDS7" fgColor="000000" bgColor="FFFFFF" fontName="" fontStyle="1" nesting="0" />
<WordsStyle name="KEYWORDS8" fgColor="808080" bgColor="FFFFFF" fontName="" fontStyle="2" nesting="0" />
<WordsStyle name="OPERATORS" fgColor="8080C0" bgColor="FFFFFF" fontName="" fontStyle="0" nesting="0" />
<WordsStyle name="FOLDER IN CODE1" fgColor="FF0000" bgColor="FFFFFF" fontName="" fontStyle="1" nesting="0" />
<WordsStyle name="FOLDER IN CODE2" fgColor="000000" bgColor="FFFFFF" fontName="" fontStyle="2" nesting="0" />
<WordsStyle name="FOLDER IN COMMENT" fgColor="000000" bgColor="FFFFFF" fontName="" fontStyle="2" nesting="0" />
<WordsStyle name="DELIMITERS1" fgColor="400000" bgColor="FFFFFF" fontName="" fontStyle="2" nesting="1" />
<WordsStyle name="DELIMITERS2" fgColor="408080" bgColor="FFFFFF" fontName="" fontStyle="0" nesting="117702400" />
<WordsStyle name="DELIMITERS3" fgColor="800000" bgColor="FFFFFF" fontName="" fontStyle="2" nesting="0" />
<WordsStyle name="DELIMITERS4" fgColor="000000" bgColor="FFFFFF" fontName="" fontStyle="0" nesting="0" />
<WordsStyle name="DELIMITERS5" fgColor="000000" bgColor="FFFFFF" fontName="" fontStyle="0" nesting="0" />
<WordsStyle name="DELIMITERS6" fgColor="000000" bgColor="FFFFFF" fontName="" fontStyle="0" nesting="0" />
<WordsStyle name="DELIMITERS7" fgColor="000000" bgColor="FFFFFF" fontName="" fontStyle="0" nesting="0" />
<WordsStyle name="DELIMITERS8" fgColor="000000" bgColor="FFFFFF" fontName="" fontStyle="0" nesting="0" />
</Styles>
</UserLang>
</NotepadPlus>
</pre>

=Darkmode MIB UDL=

[[Toolpack:Tsbc_System_Settings_3.1|Use this page as an example of Tabbed Headers]]

<headertabs/>