Sandbox:Web portal tutorial guide

From TBwiki
(Difference between revisions)
Jump to: navigation, search
(add sip)
(add status + cdr + system)
Line 9: Line 9:
 
</span>
 
</span>
  
 +
= System configuration =
  
= Protocol stacks configuration =
+
{| cellpadding="5" border="1" class="wikitable"
 +
|-
 +
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Log-on and User Access Levels
 +
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Database Backup
 +
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Configure IP Interfaces
 +
|-
 +
| valign="top" |
 +
*[[Toolpack:Connecting to the Web Server and logging on to the web portal A|Connect to the web server and log on to the Web Portal]]
 +
*[[Toolpack:User access A|User Access]]
 +
**[[Toolpack:Viewing the User List A|Viewing the User List]]
 +
**[[Toolpack:Creating a New User A|Creating a New User]]
 +
**[[Toolpack:Deleting a User A|Deleting a User]]
 +
**[[Toolpack:Logging Off A|Logging Off]]
 +
*[https://forums.telcobridges.com/viewtopic.php?f=12&t=248&p=1101&hilit=privilege#p1101 User privilege level]
 +
 
 +
| valign="top" |
 +
*[[Toolpack:Database Backup A|Carrying out a First Database Backup]]
 +
*[[Toolpack:Downloading a Database Backup A|Downloading a Database Backup]]
 +
*[[Toolpack:Uploading a Database Backup A|Uploading a Database Backup]]
 +
*[[Toolpack:Restoring a Database Backup A|Restoring a Database Backup]]
 +
 
 +
| valign="top" |
 +
*[[Configuring IP Interfaces|Configure IP Interfaces]]
 +
 
 +
|}
 +
 
 +
= Configuring protocol stacks =
  
== ISDN/NFAS Configuration ==
+
== ISDN/NFAS ==
  
 
{| cellpadding="5" border="1" class="wikitable"
 
{| cellpadding="5" border="1" class="wikitable"
Line 41: Line 68:
  
  
== CASR2 Configuration ==
+
== CASR2 ==
 
Toolpack v2.5 allows you to configure CAS R2 signaling stacks. The following table lists the basic steps that must be followed in order to configure CAS R2.
 
Toolpack v2.5 allows you to configure CAS R2 signaling stacks. The following table lists the basic steps that must be followed in order to configure CAS R2.
  
Line 65: Line 92:
  
  
== ISUP Configuration ==
+
== SS7/ISUP ==
  
 
To configure the ISUP stack.
 
To configure the ISUP stack.
Line 194: Line 221:
 
|}
 
|}
  
== SCCP/TCAP Configuration ==
+
== SCCP/TCAP ==
  
  
Line 338: Line 365:
 
|}
 
|}
  
== SIP Configuration ==
+
== SIP ==
  
 
{| cellpadding="5" border="1" class="wikitable"
 
{| cellpadding="5" border="1" class="wikitable"
Line 363: Line 390:
 
|}
 
|}
  
== H.248 Configuration ==
+
== H.248 ==
  
 
If the Tmedia is used to forward signalling messages to the SSW, you will require to configure M2UA, M3UA or IUA before configuring H.248.
 
If the Tmedia is used to forward signalling messages to the SSW, you will require to configure M2UA, M3UA or IUA before configuring H.248.
Line 498: Line 525:
 
*[[Toolpack:Associating_NAPs_with_an_H.248_Configuration A|Associate the NAPs with the H.248 configuration]]
 
*[[Toolpack:Associating_NAPs_with_an_H.248_Configuration A|Associate the NAPs with the H.248 configuration]]
 
*[[Toolpack:Selecting_Timeslots_for_TDM_Interfaces A|Select timeslots for the TDM interfaces]]
 
*[[Toolpack:Selecting_Timeslots_for_TDM_Interfaces A|Select timeslots for the TDM interfaces]]
 +
 +
|}
 +
 +
 +
= CDR =
 +
 +
{| 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;" |Text CDR
 +
! 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;" |RADIUS
 +
|-
 +
 +
| valign="top" |
 +
*[[Sandbox:Text CDR|Text CDR]]
 +
 +
| valign="top" |
 +
*[[Toolpack:Configuring_RADIUS A|Configuring RADIUS]]
 +
 +
|}
 +
 +
 +
= Fax =
 +
 +
{| 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;" |FAX passthrough
 +
! 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;" |FAX T.38
 +
|-
 +
| valign="top" |
 +
*[[Configure_Fax_Relay_A|Configure Fax Relay]]
 +
*[[Configure_Fax_Passthrough_A|Configure Fax Passthrough]]
 +
| valign="top" |
 +
*[[Configure_Fax_Relay_A|Configure Fax Relay]]
 +
*[[Configure_Fax_T38_A|Configure Fax T38]]
 +
|}
 +
 +
 +
= Routing script =
 +
TelcoBridges provides a wide variety of routing script examples which customers can apply directly in their web configuration according to their needs by following just a few simple steps. Please select one of the following examples according to your needs. You may modify it when necessary.
 +
 +
 +
'''*Flexible NOA:''' Remap the Calling/Called NOA flexibly based on the routes. It should cover most of the NOA requests since the routes include the calling/called remapping as well.
 +
 +
'''*Prefix NOA:''' Remapp Calling/Called NOA according to the prefix of the calling/called number, manipulate calling/called number. For calling number, if it is a privacy call, use the number in P-Asserted-Identity line or Remote-Party-ID line as the calling number to remap the NOA and do the manipulation.
 +
 +
{| 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;" |Flexible NOA
 +
! 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;" |Prefix NOA
 +
|-
 +
| valign="top" |
 +
 +
*[[Create_New_Routing_Script_A|Create new routing script]]
 +
*[[Import_Customized_Routing_Script_A|Import customized routing script]]
 +
*[[Add_NOA_Columns_in_Routes_A|Add NOA columns in routes]]
 +
*[[Enable_Routing_Script_A|Enable routing script]]
 +
*[[Activate_Configuration_A|Activate configuration]]
 +
 +
| valign="top" |
 +
 +
*[[Create_New_Routing_Script_A|Create new routing script]]
 +
*[[Import_Customized_Routing_Script_A|Import customized routing script]]
 +
*[[Enable_Routing_Script_A|Enable routing script]]
 +
*[[Activate_Configuration_A|Activate configuration]]
 +
 +
|}
 +
 +
 +
= Status Menus =
 +
 +
{| 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;" | (A) <br>Menus Overview
 +
! 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;" | (B) <br>Individual Menu Descriptions
 +
 +
|-
 +
| valign="top" |
 +
 +
*[[Toolpack:Tmedia_Status_Menus A|Tmedia Status Menus]]
 +
**[[Toolpack:Status_Menus:Navigation A|Navigation]]
 +
**[[Toolpack:Status_Menus:Screen_Conventions A|Status Screen Conventions]]
 +
 +
| valign="top" |
 +
 +
*[[Toolpack:Status_Menus:System A|System]]
 +
*[[Toolpack:Status_Menus:Adapters_and_IP_Interfaces A|Adapters and IP Interfaces]]
 +
*[[Toolpack:Status_Menus:Hosts A|Hosts]]
 +
*[[Toolpack:Status_Menus:Applications A|Applications]]
 +
*[[Toolpack:Status_Menus:TDM_Lines A|TDM Lines]]
 +
*[[Toolpack:Status_Menus:SCTP A|SCTP]]
 +
*[[Toolpack:Status_Menus:SS7_MTP2 A|SS7 MTP2]]
 +
*[[Toolpack:Status_Menus:SS7_M2UA A|SS7 M2UA]]
 +
*[[Toolpack:Status_Menus:SS7_IUA A|SS7 IUA]]
 +
*[[Toolpack:Status_Menus:SS7_M2PA A|SS7 M2PA]]
 +
*[[Toolpack:Status_Menus:SS7_M3UA A|SS7 M3UA]]
 +
*[[Toolpack:Status_Menus:SS7_MTP3 A|SS7 MTP3]]
 +
*[[Toolpack:Status_Menus:SS7_ISUP A|SS7 ISUP]]
 +
*[[Toolpack:Status_Menus:SS7_SCCP A|SS7 SCCP]]
 +
*[[Toolpack:Status_Menus:SS7_TCAP A|SS7 TCAP]]
 +
*[[Toolpack:Status_Menus:ISDN A|ISDN]]
 +
**[[Toolpack:Status_Menus:NFAS A|NFAS]]
 +
*[[Toolpack:Status_Menus:CAS R2 A|CAS R2]]
 +
*[[Toolpack:Status_Menus:SIP A|SIP]]
 +
*[[Toolpack:Status_Menus:Clock A|Clock]]
 +
*[[Toolpack:Status_Menus:TMS A|TMS]]
 +
*[[Toolpack:Status_Menus:NAP A|NAP]]
 +
*[[Toolpack:Status_Menus:H.248 A|H.248]]
 +
*[[Toolpack:Status_Menus:CDR A|CDR]]
  
 
|}
 
|}

Revision as of 13:16, 7 August 2012

This page is only a test page to verify different format.

We must change the name of the article 'Toolpack:Creating_a_NAP_(SIGTRAN)_A'

Do not use as Web portal tutorial guide reference

Contents

System configuration

Log-on and User Access Levels Database Backup Configure IP Interfaces

Configuring protocol stacks

ISDN/NFAS

(Step 1)
Allocate Physical Interfaces
(Step 2)
Configure ISDN-PRI Signaling
(Step 3)
Configure Network Access Points (NAPs)

OR


CASR2

Toolpack v2.5 allows you to configure CAS R2 signaling stacks. The following table lists the basic steps that must be followed in order to configure CAS R2.

(Step 1)
Allocate Physical Interfaces
(Step 2)
Configuring a CAS R2 stack
(Step 3)
Configure Network Access Points (NAPs)


SS7/ISUP

To configure the ISUP stack.

MTP2-MTP3-ISUP

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




M2PA-MTP3-ISUP

(Step 1)
Allocate Physical Interfaces
(Step 2)
Configuring the M2PA Layer
(Step 3)
Configuring the MTP3 Layer
(Step 4)
Configuring the ISUP Layer
(Step 5)
Configure Network Access Points (NAPs)



M3UA-ISUP

(Step 1)
Allocate Physical Interfaces
(Step 2)
Configuring the M3UA Layer
(Step 3)
Configuring the ISUP Layer
(Step 4)
Configure Network Access Points (NAPs)

SCCP/TCAP

MTP2-MTP3-SCCP/TCAP

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




M2PA-MTP3-SCCP/TCAP

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



M3UA-SCCP/TCAP

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

SIP

(Step 1)
Configure IP port range
(Step 2)
Configure SIP Signaling
(Step 3)
Configure Codecs and Tone Detection
(Step 4)
Configure Network Access Points (NAPs)

H.248

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

If the Tmedia is used to connect media only, then you can go straight to H.248 Configuration

M2UA

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


M3UA

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

IUA

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

H.248

(Step 1)
Allocate Physical Interfaces
(Step 2)
Create IP Port Ranges
(Step 3)
Configure Network Access Points (NAPs)


(Step 4)
Configure Media Gateway for H.248 mode
(Step 5)
Add a New Media Gateway Controller
(Step 6)
Associate NAPs Resources to H.248 Configuration


CDR

Text CDR RADIUS


Fax

FAX passthrough FAX T.38


Routing script

TelcoBridges provides a wide variety of routing script examples which customers can apply directly in their web configuration according to their needs by following just a few simple steps. Please select one of the following examples according to your needs. You may modify it when necessary.


*Flexible NOA: Remap the Calling/Called NOA flexibly based on the routes. It should cover most of the NOA requests since the routes include the calling/called remapping as well.

*Prefix NOA: Remapp Calling/Called NOA according to the prefix of the calling/called number, manipulate calling/called number. For calling number, if it is a privacy call, use the number in P-Asserted-Identity line or Remote-Party-ID line as the calling number to remap the NOA and do the manipulation.

Flexible NOA Prefix NOA


Status Menus

(A)
Menus Overview
(B)
Individual Menu Descriptions
Personal tools