TBwiki - User contributions [en]

Toolpack:Priority mode

2020-09-15T20:19:16Z

Nicole Tan: NT 20200915 Modified the example to make it clearer.

=== '''''Applies to version v2.10, v3.0, v3.1''''' ===
{{DISPLAYTITLE: Steps to configure label routing for Group of DIDs to multiple outbound NAPs}}
'''Steps to configure label routing for Group of DIDs to a multiple outbound NAPs :'''
*The scenario is a group of the DIDs/Prefix will be sent the a multiple designated outbound NAPs in priority mode with some manipulations:
E.g.
DIDs/Prefix shall be sent to NAP_A and NAP_B with priority 1, NAP_C with priority 2
111
222
333
444
555
666
777
888
999

So a call with called number which has any of the above prefix will be sent to NAP_A and NAP_B in load-sharing mode, and if both NAP_A and NAP_B fail, it will then sent to
NAP_C
Below are the steps to configure that regarding the digitmap file and definition files:

1- Compose the digitmap file - dm.csv, simple make it as below:

[[Image:priority_dm.csv.jpg]]

2- Compose definition file for NAP_A,NAP_B and NAP_C:

[[Image:priority_df.csv.jpg]]

3- Import the dm.csv and the definition files via "File Db" menu

[[Image:priority_filedb.jpg]]

4- Associate NAP_A, NAP_B and NAP_C with the created dm.csv and the definition file, and generate routes

[[Image:priority_Routeset.jpg]]

5- Verify the Routes

[[Image:priority_Routes.jpg]]

6- Activate the configuration

How to Debug Trunk Interfaces

2020-06-30T18:39:39Z

Nicole Tan: NT: Added note about the Cable Type for ISDN User or Network

Connecting a trunk interface should be easy - right? Well it is more complicated than it seems because many conditions have some effect on the final installation.

Here are some examples: 

#Cables 
#Port used on Tmedia units 
#Port used on remote device 
#Framing 
#Line encoding 

In general, cabling makes all the difference when connecting a trunk interface. In most cases, after the local and remote trunk Ports are carefully selected and default configuration is used, cabling is the last thing that can cause a problem. 

To check the status of the trunk : [[Toolpack v2.5:Status Menus:TDM Lines]]

On the web portal : 
<pre>Status -> TDM lines -> click on the trunk -> Click on extended status -> Refresh now
</pre>
Most of these parameters are defined in RFC2495 ([http://www.faqs.org/rfcs/rfc2495.html www.faqs.org/rfcs/rfc2495.html]), but here is a guideline for different errors encountered:

1. If you have LOS (Loss of Signal) -> Check cabling 

2. If you have LOF/OOF (Loss of Frame) -> Check framing and type of trunk (E1 vs T1) 

3. If you have RAI/RRA (Remote Alarm Indication) -> Check cabling 

4. If you have RSP/RSN (Receive Slip) -> Clocking is not set correctly 

5. Other errors, like FEC (Forward Error Correction)  and CVC (Code violations) are usually not critical, but should be verified -> Check cabling

 

You can also reset the status to get fresh information: 
<pre>Click on Reset status -> Refresh now -> Unclick on Reset status -> Refresh now (again)
</pre>
 

You can also test with Trunk Loopbacks. Here is the procedure [[Parameter: Loopback|how to use Loopback]].

 

'''Possibles causes of bad cabling:''' 

1. Straight vs Crossover 

Depending on the installation, the cable required can be a straight one or a crossover. Make sure the right one is used in the installation. This is detected with a LOS signal on the line. 

*Straight E1 cable (same for T1 and J1): pairs 1-2 and 4-5 must be the twisted pairs. This is different than a ethernet cable. It does not affect the system over short distances. 
*Crossover E1 cable: pairs 1-2 and 4-5 must be crossed. 

*Note: In the field, for ISDN configuration on T1/E, we found it clearly expects a specific pinout for ports configured for USER side (i.e. straight cables) and NETWORK side (i.e. cross-over).

2. Only half way is working

This is easy to detect as the RAI/RRA alarm will be set on one end (1) and LOS on the other end (2). This means the path from (1) to (2) is down and path from (2) to (1) is up.

3. Quality of the cable 

If the cable is not perfect, it may causes various errors like Code Violations. In general this will not affect the status of the line, but will generate static on the line and may prevent data communication, like HDLC processing for ISDN and SS7. Reference to other status parameters can be found in RFC 2495

3. 75 ohms E1 connections 

E1 75 ohms/120 ohms conversion requires an external Balun module 

 

'''Default parameters:''' 

E1 

*Line encoding is HDB3 
*Framing is AUTO, which supports both MFRAME (multiframe, or with CRC) and STD (doubleframe without CRC) 
*Line length is SHORT 

T1/J1 

*Line encoding is B8ZS 
*Framing is ESF (extended Super Frame)
*Line length is SHORT

 

Note: Trunk ports on Tmedia 16 E1 and Tmedia 64E1 with patch panels are not in the same order of connection. Please verify in the respective installation guides. 

== References ==

[http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_note09186a00801069ff.shtml T1 Alarm Troubleshooting]

Upgrade CentOS

2020-04-17T17:20:50Z

Nicole Tan: NT: Correction about the Centos7 version

{{DISPLAYTITLE: Upgrade CentOS software packages}}
__FORCETOC__
== Benefits ==
* Obtain the CentOS security updates
* Patch recent vulnerabilities
* Patch SNMP core files

== Applicable Products ==
* TMG800, TMG3200, TMG7800-CTRL, TSBC, FreeSBC
* TSG800, TSG3200
* Tdev Linux server (CentOS or RedHat) running Toolpack software

== TelcoBridges repository ==
The operating system (CentOS) software upgrade is performed using ''yum'' software package manager. The repositories sites providing RPM packages are configured from /etc/yum.repos.d/. TelcoBridges provides a modified CentOS repository copy (http://repo.telcobridges.com) of the official CentOS repository.

If the '''unit or Linux server does not have access to Internet''' (or does not have DNS configured), you should configure an offline CentOS repository on your local machine as explained in the section bellow.

=== Offline repository configuration ===
First, SSH to your unit do determine which version of the OS your system is using:
# cat /etc/redhat-release
'''CentOS release 5'''.11 (Final)

* [[Configure_Offline_Repository_CentOS5_A|Configure a local offline Repository for CentOS5]]

'''CentOS Linux release 7'''(Core)
* [[Configure_Offline_Repository_CentOS7_A|Configure a local offline Repository for CentOS7]]

== CentOS software packages update ==
The operator can use one of the two methods available: GUI/WebPortal or command line interface.

=== WebPortal ===

'''NOTE''': The GUI/WebPortal CentOS packages software upgrade shown below is only offered on ''T''sbc, ''T''media and ''T''sig product. Tdev Linux server with Toolpack must be upgraded using the Command Line procedure.


To upgrade CentOS software packages, follow this procedure from the web interface of the unit:
* Hosts -> Status -> TBxxxxxx -> Action -> Upgrade Linux Packages, then 'Apply Action':
[[Image:Upgrade_Linux_Packages.jpg]]

When the upgrade is in progress, there is no status shown, and you will see the screen like this:

[[Image:Upgrade_Linux_Progress.jpg]]

It may take a while 8-10 mins. You need to refresh the page until you see this:

[[Image:Centos_Upgrade_Complete.jpg]]

Once complete, you need to reboot the host:
Hosts -> Status -> TBxxxxxx -> Action -> Shutdown -> Reboot

=== Command line ===
Alternatively, you can ssh to the unit and run the following command:
# yum clean all
# yum update

Reboot the unit
# reboot

Toolpack:Tsbc Call Routes Settings 3.1

2020-03-05T14:46:48Z

Nicole Tan:

{{DISPLAYTITLE:FreeSBC/ProSBC Web Portal 3.1: Call Routes Settings}}

'''Applies to FreeSBC and Tmedia products'''

=Routes=

==Static Route==
{| 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;" |Add routes
|-
| valign="top" |
*[[Toolpack:Creating_a_First_Call_Route E|Create a first call route]]
|}

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

==Label Routing==

This section assumes:
* '''The routing script is already implemented''' (you just need to add the label routing functionality)
* '''The routeset definition and digimap files are already created'''

{|
|STYLE="vertical-align: top"|
{| 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;" |Add label routing functionality
|-
| valign="top" |
*[[Toolpack:Adding_Label_Routing_to_any_Routing_Script_D|Add Label Routing to script]]
*[[Toolpack:Assign_Routing_Script_DB_Files_to_Gateway_Application_E|Assign Routing/Script Files to the Gateway Application]]
*[[Toolpack:Add_Digitmap_Files_C|Add the Digit Map Files to the System]]
*[[Toolpack:Add_Routeset_Definition_Files_C|Add the Routset Definition Files to the System]]
*[[Toolpack:Assign_Definition_Digitmap_Files_per_NAP_E|Assign Defintion/Digitmap Files on a per NAP Basis]]
*[[Toolpack:Generate_Dynamic_Routes_D|Generate Dynamic Routes]]
*[[Toolpack:Activating_the_Configuration D|Activate configuration]]
|}

|STYLE="vertical-align: top"|
{| 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;" |Update definition/digitmap files
|-
| valign="top" |
*[[Toolpack:Update_Digitmap_Files_C|Update the Digitmap Files]]
*[[Toolpack:Update_Routeset_Definition_Files_C|Update the Routeset Definition Files]]
*[[Toolpack:Generate_Dynamic_Routes_D|Generate Dynamic Routes]]
*[[Toolpack:Activating_the_Configuration D|Activate configuration]]
|}

|STYLE="vertical-align: top"|
{| 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;" |Examples
|-
| valign="top" |
*[[Group of DIDs to a single outbound NAPs|Group of DIDs to a single outbound NAPs]]
*Group of DIDs to multiple outbound NAPs
**[[Toolpack:Load-sharing mode|Load-sharing mode]]
**[[Toolpack:Priority mode|Priority mode]]
|}
|}

==RADIUS Authorization and Authentication (ProSBC only)==
{|
|STYLE="vertical-align: top"|
{| 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;" |RADIUS Authorization
|-
| valign="top" |
*[[Toolpack:Configuring_RADIUS_client_E|Configure RADIUS client]]
*[[Toolpack:Adding_RADIUS_server_D|Add RADIUS authorization server]]
*[[Toolpack:Create_New_Routing_Script_D|Create New Routing Script]]
*[[Toolpack:Configuring_RADIUS_authorization_B|Configure RADIUS Authorization]]
*[[Toolpack:Enable_Routing_Script_E|Enable Routing Script]]
|}
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="300" 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 Authorization (with custom dictionary)
|-
| valign="top" |
*[[Toolpack:Import_RADIUS_Custom_Dictionary_B|Import RADIUS Custom Dictionary]]
*[[Toolpack:Configuring_RADIUS_client_E|Configure RADIUS Client]]
*[[Toolpack:Adding_RADIUS_server_D|Add RADIUS authorization Server]]
*[[Toolpack:Create_New_Routing_Script_D|Create New Routing Script]]
*[[Toolpack:Configuring_RADIUS_authorization_B|Configure RADIUS Authorization]]
*[[Toolpack:Enable_Routing_Script_E|Enable Routing Script]]
|}
|}

Toolpack:Priority mode

2020-03-05T03:09:03Z

Nicole Tan:

=== '''''Applies to version v2.10, v3.0, v3.1''''' ===
{{DISPLAYTITLE: Steps to configure label routing for Group of DIDs to multiple outbound NAPs}}
'''Steps to configure label routing for Group of DIDs to a multiple outbound NAPs :'''
*The scenario is a group of the DIDs/Prefix will be sent the a multiple designated outbound NAPs in priority mode with some manipulations:
E.g.
DIDs/Prefix shall be sent to NAP_A with priority 1
111
222
333
DIDs/Prefix shall be sent to NAP_B with priority 2
444
555
666
DIDs/Prefix shall be sent to NAP_C with priority 2
777
888
999

1- Compose the digitmap file - dm.csv, simple make it as below:

[[Image:priority_dm.csv.jpg]]

2- Compose definition file for NAP_A,NAP_B and NAP_C:

[[Image:priority_df.csv.jpg]]

3- Import the dm.csv and the definition files via "File Db" menu

[[Image:priority_filedb.jpg]]

4- Associate NAP_A, NAP_B and NAP_C with the created dm.csv and the definition file, and generate routes

[[Image:priority_Routeset.jpg]]

5- Verify the Routes

[[Image:priority_Routes.jpg]]

6- Activate the configuration

File:Priority Routes.jpg

2020-03-05T03:08:25Z

Nicole Tan:

File:Priority Routeset.jpg

2020-03-05T03:07:53Z

Nicole Tan:

File:Priority filedb.jpg

2020-03-05T03:07:12Z

Nicole Tan:

File:Priority df.csv.jpg

2020-03-05T03:04:39Z

Nicole Tan:

File:Priority dm.csv.jpg

2020-03-05T03:04:25Z

Nicole Tan:

Toolpack:Priority mode

2020-03-05T03:02:48Z

Nicole Tan: NT: Created new page

=== '''''Applies to version v2.10, v3.0, v3.1''''' ===
{{DISPLAYTITLE: Steps to configure label routing for Group of DIDs to multiple outbound NAPs}}
'''Steps to configure label routing for Group of DIDs to a multiple outbound NAPs :'''
*The scenario is a group of the DIDs/Prefix will be sent the a multiple designated outbound NAPs in priority mode with some manipulations:
E.g.
DIDs/Prefix shall be sent to NAP_A with priority 1
111
222
333
DIDs/Prefix shall be sent to NAP_B with priority 2
444
555
666
DIDs/Prefix shall be sent to NAP_C with priority 2
777
888
999

1- Compose the digitmap file - dm.csv, simple make it as below:

[[Image:priority_dm.csv.jpg]]

2- Compose same definition file for NAP_A,NAP_B and NAP_C:

[[Image:priority_df.csv.jpg]]

3- Import the dm.csv and the definition files via "File Db" menu

[[Image:priority_filedb.jpg]]

4- Associate NAP_A, NAP_B and NAP_C with the created dm.csv and the definition file, and generate routes

[[Image:priority_Routeset.jpg]]

5- Verify the Routes

[[Image:priority_Routes.jpg]]

6- Activate the configuration

Toolpack:Tsbc Call Routes Settings 3.1

2020-03-05T02:17:17Z

Nicole Tan:

{{DISPLAYTITLE:FreeSBC/ProSBC Web Portal 3.1: Call Routes Settings}}

'''Applies to FreeSBC and Tmedia products'''

=Routes=

==Static Route==
{| 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;" |Add routes
|-
| valign="top" |
*[[Toolpack:Creating_a_First_Call_Route E|Create a first call route]]
|}

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

==Label Routing==

This section assumes:
* '''The routing script is already implemented''' (you just need to add the label routing functionality)
* '''The routeset definition and digimap files are already created'''

{|
|STYLE="vertical-align: top"|
{| 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;" |Add label routing functionality
|-
| valign="top" |
*[[Toolpack:Adding_Label_Routing_to_any_Routing_Script_D|Add Label Routing to script]]
*[[Toolpack:Assign_Routing_Script_DB_Files_to_Gateway_Application_E|Assign Routing/Script Files to the Gateway Application]]
*[[Toolpack:Add_Digitmap_Files_C|Add the Digit Map Files to the System]]
*[[Toolpack:Add_Routeset_Definition_Files_C|Add the Routset Definition Files to the System]]
*[[Toolpack:Assign_Definition_Digitmap_Files_per_NAP_E|Assign Defintion/Digitmap Files on a per NAP Basis]]
*[[Toolpack:Generate_Dynamic_Routes_D|Generate Dynamic Routes]]
*[[Toolpack:Activating_the_Configuration D|Activate configuration]]
|}

|STYLE="vertical-align: top"|
{| 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;" |Update definition/digitmap files
|-
| valign="top" |
*[[Toolpack:Update_Digitmap_Files_C|Update the Digitmap Files]]
*[[Toolpack:Update_Routeset_Definition_Files_C|Update the Routeset Definition Files]]
*[[Toolpack:Generate_Dynamic_Routes_D|Generate Dynamic Routes]]
*[[Toolpack:Activating_the_Configuration D|Activate configuration]]
|}

|STYLE="vertical-align: top"|
{| 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;" |Examples
|-
| valign="top" |
*[[Group of DIDs to a single outbound NAPs|Group of DIDs to a single outbound NAPs]]
*Group of DIDs to multiple outbound NAPs
**[[Toolpack:Load-sharing mode|Load-sharing mode]]
**[[Toolpack:Load-sharing mode|Priority mode]]
|}
|}

==RADIUS Authorization and Authentication (ProSBC only)==
{|
|STYLE="vertical-align: top"|
{| 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;" |RADIUS Authorization
|-
| valign="top" |
*[[Toolpack:Configuring_RADIUS_client_E|Configure RADIUS client]]
*[[Toolpack:Adding_RADIUS_server_D|Add RADIUS authorization server]]
*[[Toolpack:Create_New_Routing_Script_D|Create New Routing Script]]
*[[Toolpack:Configuring_RADIUS_authorization_B|Configure RADIUS Authorization]]
*[[Toolpack:Enable_Routing_Script_E|Enable Routing Script]]
|}
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="300" 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 Authorization (with custom dictionary)
|-
| valign="top" |
*[[Toolpack:Import_RADIUS_Custom_Dictionary_B|Import RADIUS Custom Dictionary]]
*[[Toolpack:Configuring_RADIUS_client_E|Configure RADIUS Client]]
*[[Toolpack:Adding_RADIUS_server_D|Add RADIUS authorization Server]]
*[[Toolpack:Create_New_Routing_Script_D|Create New Routing Script]]
*[[Toolpack:Configuring_RADIUS_authorization_B|Configure RADIUS Authorization]]
*[[Toolpack:Enable_Routing_Script_E|Enable Routing Script]]
|}
|}

Toolpack:Tsbc Call Routes Settings 3.1

2020-03-05T02:17:03Z

Nicole Tan:

{{DISPLAYTITLE:FreeSBC/ProSBC Web Portal 3.1: Call Routes Settings}}

'''Applies to FreeSBC and Tmedia products'''

=Routes=

==Static Route==
{| 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;" |Add routes
|-
| valign="top" |
*[[Toolpack:Creating_a_First_Call_Route E|Create a first call route]]
|}

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

==Label Routing==

This section assumes:
* '''The routing script is already implemented''' (you just need to add the label routing functionality)
* '''The routeset definition and digimap files are already created'''

{|
|STYLE="vertical-align: top"|
{| 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;" |Add label routing functionality
|-
| valign="top" |
*[[Toolpack:Adding_Label_Routing_to_any_Routing_Script_D|Add Label Routing to script]]
*[[Toolpack:Assign_Routing_Script_DB_Files_to_Gateway_Application_E|Assign Routing/Script Files to the Gateway Application]]
*[[Toolpack:Add_Digitmap_Files_C|Add the Digit Map Files to the System]]
*[[Toolpack:Add_Routeset_Definition_Files_C|Add the Routset Definition Files to the System]]
*[[Toolpack:Assign_Definition_Digitmap_Files_per_NAP_E|Assign Defintion/Digitmap Files on a per NAP Basis]]
*[[Toolpack:Generate_Dynamic_Routes_D|Generate Dynamic Routes]]
*[[Toolpack:Activating_the_Configuration D|Activate configuration]]
|}

|STYLE="vertical-align: top"|
{| 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;" |Update definition/digitmap files
|-
| valign="top" |
*[[Toolpack:Update_Digitmap_Files_C|Update the Digitmap Files]]
*[[Toolpack:Update_Routeset_Definition_Files_C|Update the Routeset Definition Files]]
*[[Toolpack:Generate_Dynamic_Routes_D|Generate Dynamic Routes]]
*[[Toolpack:Activating_the_Configuration D|Activate configuration]]
|}

|STYLE="vertical-align: top"|
{| 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;" |Examples
|-
| valign="top" |
*[[Group of DIDs to a single outbound NAPs|Group of DIDs to a single outbound NAPs]]
*Group of DIDs to multiple outbound NAPs
**[[Toolpack:Load-sharing mode|Load-sharing mode]]

|}
|}

==RADIUS Authorization and Authentication (ProSBC only)==
{|
|STYLE="vertical-align: top"|
{| 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;" |RADIUS Authorization
|-
| valign="top" |
*[[Toolpack:Configuring_RADIUS_client_E|Configure RADIUS client]]
*[[Toolpack:Adding_RADIUS_server_D|Add RADIUS authorization server]]
*[[Toolpack:Create_New_Routing_Script_D|Create New Routing Script]]
*[[Toolpack:Configuring_RADIUS_authorization_B|Configure RADIUS Authorization]]
*[[Toolpack:Enable_Routing_Script_E|Enable Routing Script]]
|}
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="300" 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 Authorization (with custom dictionary)
|-
| valign="top" |
*[[Toolpack:Import_RADIUS_Custom_Dictionary_B|Import RADIUS Custom Dictionary]]
*[[Toolpack:Configuring_RADIUS_client_E|Configure RADIUS Client]]
*[[Toolpack:Adding_RADIUS_server_D|Add RADIUS authorization Server]]
*[[Toolpack:Create_New_Routing_Script_D|Create New Routing Script]]
*[[Toolpack:Configuring_RADIUS_authorization_B|Configure RADIUS Authorization]]
*[[Toolpack:Enable_Routing_Script_E|Enable Routing Script]]
|}
|}

File:Loadshare Routes.jpg

2020-03-05T02:15:32Z

Nicole Tan:

File:Loadshare Routeset.jpg

2020-03-05T02:15:04Z

Nicole Tan:

File:Loadshare filedb.jpg

2020-03-05T02:14:40Z

Nicole Tan:

File:Loadshare df.csv.jpg

2020-03-05T02:13:57Z

Nicole Tan:

File:Loadshare dm.csv.jpg

2020-03-05T02:13:32Z

Nicole Tan:

Toolpack:Load-sharing mode

2020-03-05T01:42:56Z

Nicole Tan: NT: Created new page

=== '''''Applies to version v2.10, v3.0, v3.1''''' ===
{{DISPLAYTITLE: Steps to configure label routing for Group of DIDs to multiple outbound NAPs}}
'''Steps to configure label routing for Group of DIDs to a multiple outbound NAPs :'''
*The scenario is a group of the DIDs/Prefix will be sent the a multiple designated outbound NAPs in load-sharing mode:
E.g.
DIDs/Prefix shall be sent to NAP_A, NAP_B and NAP_C in load-sharing mode
111
222
333
444

1- Compose the digitmap file - dm.csv, simple make it as below:

[[Image:loadshare_dm.csv.jpg]]

2- Compose same definition file for NAP_A,NAP_B and NAP_C:

[[Image:loadshare_df.csv.jpg]]

3- Import the dm.csv and the definition files via "File Db" menu

[[Image:loadshare_filedb.jpg]]

4- Associate NAP_A, NAP_B and NAP_C with the created dm.csv and the definition file, and generate routes

[[Image:loadshare_Routeset.jpg]]

5- Verify the Routes

[[Image:loadshare_Routes.jpg]]

6- Activate the configuration

Toolpack:Tsbc Call Routes Settings 3.1

2020-03-05T01:36:19Z

Nicole Tan:

{{DISPLAYTITLE:FreeSBC/ProSBC Web Portal 3.1: Call Routes Settings}}

'''Applies to FreeSBC and Tmedia products'''

=Routes=

==Static Route==
{| 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;" |Add routes
|-
| valign="top" |
*[[Toolpack:Creating_a_First_Call_Route E|Create a first call route]]
|}

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

==Label Routing==

This section assumes:
* '''The routing script is already implemented''' (you just need to add the label routing functionality)
* '''The routeset definition and digimap files are already created'''

{|
|STYLE="vertical-align: top"|
{| 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;" |Add label routing functionality
|-
| valign="top" |
*[[Toolpack:Adding_Label_Routing_to_any_Routing_Script_D|Add Label Routing to script]]
*[[Toolpack:Assign_Routing_Script_DB_Files_to_Gateway_Application_E|Assign Routing/Script Files to the Gateway Application]]
*[[Toolpack:Add_Digitmap_Files_C|Add the Digit Map Files to the System]]
*[[Toolpack:Add_Routeset_Definition_Files_C|Add the Routset Definition Files to the System]]
*[[Toolpack:Assign_Definition_Digitmap_Files_per_NAP_E|Assign Defintion/Digitmap Files on a per NAP Basis]]
*[[Toolpack:Generate_Dynamic_Routes_D|Generate Dynamic Routes]]
*[[Toolpack:Activating_the_Configuration D|Activate configuration]]
|}

|STYLE="vertical-align: top"|
{| 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;" |Update definition/digitmap files
|-
| valign="top" |
*[[Toolpack:Update_Digitmap_Files_C|Update the Digitmap Files]]
*[[Toolpack:Update_Routeset_Definition_Files_C|Update the Routeset Definition Files]]
*[[Toolpack:Generate_Dynamic_Routes_D|Generate Dynamic Routes]]
*[[Toolpack:Activating_the_Configuration D|Activate configuration]]
|}

|STYLE="vertical-align: top"|
{| 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;" |Examples
|-
| valign="top" |
*[[Group of DIDs to a single outbound NAPs|Group of DIDs to a single outbound NAPs]]
*Group of DIDs to multiple outbound NAPs
**[[Toolpack:Load-sharing mode|Load-sharing mode]]
**[[Toolpack:Load-sharing mode|Priority mode]]
|}
|}

==RADIUS Authorization and Authentication (ProSBC only)==
{|
|STYLE="vertical-align: top"|
{| 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;" |RADIUS Authorization
|-
| valign="top" |
*[[Toolpack:Configuring_RADIUS_client_E|Configure RADIUS client]]
*[[Toolpack:Adding_RADIUS_server_D|Add RADIUS authorization server]]
*[[Toolpack:Create_New_Routing_Script_D|Create New Routing Script]]
*[[Toolpack:Configuring_RADIUS_authorization_B|Configure RADIUS Authorization]]
*[[Toolpack:Enable_Routing_Script_E|Enable Routing Script]]
|}
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="300" 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 Authorization (with custom dictionary)
|-
| valign="top" |
*[[Toolpack:Import_RADIUS_Custom_Dictionary_B|Import RADIUS Custom Dictionary]]
*[[Toolpack:Configuring_RADIUS_client_E|Configure RADIUS Client]]
*[[Toolpack:Adding_RADIUS_server_D|Add RADIUS authorization Server]]
*[[Toolpack:Create_New_Routing_Script_D|Create New Routing Script]]
*[[Toolpack:Configuring_RADIUS_authorization_B|Configure RADIUS Authorization]]
*[[Toolpack:Enable_Routing_Script_E|Enable Routing Script]]
|}
|}

File:Basic df.csv.jpg

2020-03-04T22:51:29Z

Nicole Tan: uploaded a new version of "File:Basic df.csv.jpg"

File:Basic Routes.jpg

2020-03-04T22:43:33Z

Nicole Tan:

File:Basic Routeset.jpg

2020-03-04T22:43:09Z

Nicole Tan:

File:Basic filedb.jpg

2020-03-04T22:42:51Z

Nicole Tan:

File:Basic df.csv.jpg

2020-03-04T22:41:47Z

Nicole Tan:

Group of DIDs to a single outbound NAPs

2020-03-04T22:41:15Z

Nicole Tan: NT: Correction

=== '''''Applies to version v2.10, v3.0, v3.1''''' ===
{{DISPLAYTITLE: Steps to configure label routing for Group of DIDs to a single outbound NAPs }}
'''Steps to configure label routing for Group of DIDs to a single outbound NAPs :'''
*This is the most basic usage of Label Routing. The scenario is a group of the DIDs/Prefix will be sent the a single designated outbound NAP:
E.g.
DIDs/Prefix shall be sent to NAP_A
111
222
333
DIDs/Prefix shall be sent to NAP_B
444
555
666
DIDs/Prefix shall be sent to NAP_C
777
888
999

1- Compose the digitmap file - dm.csv, simple make it as below:

[[Image:basic_dm.csv.jpg]]

2- Compose definition file for each NAP:

[[Image:basic_df.csv.jpg]]

3- Import the dm.csv and the definition files via "File Db" menu

[[Image:basic_filedb.jpg]]

4- Associate NAP_A, NAP_B and NAP_C with the created dm.csv and the definition files, and generate routes

[[Image:basic_Routeset.jpg]]

5- Verify the Routes

[[Image:basic_Routes.jpg]]

6- Activate the configuration

File:Basic dm.csv.jpg

2020-03-04T22:40:33Z

Nicole Tan:

Group of DIDs to a single outbound NAPs

2020-03-04T22:40:15Z

Nicole Tan: NT: Correction

=== '''''Applies to version v2.10, v3.0, v3.1''''' ===
{{DISPLAYTITLE: Steps to configure label routing for Group of DIDs to a single outbound NAPs }}
'''Steps to configure label routing for Group of DIDs to a single outbound NAPs :'''
*This is the most basic usage of Label Routing. The scenario is a group of the DIDs/Prefix will be sent the a single designated outbound NAP:
E.g.
DIDs/Prefix shall be sent to NAP_A
111
222
333
DIDs/Prefix shall be sent to NAP_B
444
555
666
DIDs/Prefix shall be sent to NAP_C
777
888
999

1- Compose the digitmap file - dm.csv, simple make it as below:
[[Image:basic_dm.csv.jpg]]

2- Compose definition file for each NAP:
[[Image:basic_df.csv.jpg]]

3- Import the dm.csv and the definition files via "File Db" menu
[[Image:basic_filedb.jpg]]

4- Associate NAP_A, NAP_B and NAP_C with the created dm.csv and the definition files, and generate routes
[[Image:basic_Routeset.jpg]]

5- Verify the Routes
[[Image:basic_Routes.jpg]]

6- Activate the configuration

Group of DIDs to a single outbound NAPs

2020-03-04T22:39:32Z

Nicole Tan: NT: Created new page

=== '''''Applies to version v2.10, v3.0, v3.1''''' ===
{{DISPLAYTITLE: Steps to configure label routing for Group of DIDs to a single outbound NAPs }}
'''Steps to configure label routing for Group of DIDs to a single outbound NAPs :'''
*This is the most basic usage of Label Routing. The scenario is a group of the DIDs/Prefix will be sent the a single designated outbound NAP:
E.g.
DIDs/Prefix shall be sent to NAP_A
111
222
333
DIDs/Prefix shall be sent to NAP_B
444
555
666
DIDs/Prefix shall be sent to NAP_C
777
888
999

1- Compose the digitmap file - dm.csv, simple make it as below:
[[Image:basic_dm.csv.jpg]]

2- Compose definition file for each NAP:
[[basic_df.csv.jpg]]

3- Import the dm.csv and the definition files via "File Db" menu
[[basic_filedb.jpg]]

4- Associate NAP_A, NAP_B and NAP_C with the created dm.csv and the definition files, and generate routes
[[basic_Routeset.jpg]]

5- Verify the Routes
[[basic_Routes.jpg]]

6- Activate the configuration

Toolpack:Tsbc Call Routes Settings 3.1

2020-03-04T20:44:36Z

Nicole Tan: NT: Added 3 examples

{{DISPLAYTITLE:FreeSBC/ProSBC Web Portal 3.1: Call Routes Settings}}

'''Applies to FreeSBC and Tmedia products'''

=Routes=

==Static Route==
{| 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;" |Add routes
|-
| valign="top" |
*[[Toolpack:Creating_a_First_Call_Route E|Create a first call route]]
|}

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

==Label Routing==

This section assumes:
* '''The routing script is already implemented''' (you just need to add the label routing functionality)
* '''The routeset definition and digimap files are already created'''

{|
|STYLE="vertical-align: top"|
{| 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;" |Add label routing functionality
|-
| valign="top" |
*[[Toolpack:Adding_Label_Routing_to_any_Routing_Script_D|Add Label Routing to script]]
*[[Toolpack:Assign_Routing_Script_DB_Files_to_Gateway_Application_E|Assign Routing/Script Files to the Gateway Application]]
*[[Toolpack:Add_Digitmap_Files_C|Add the Digit Map Files to the System]]
*[[Toolpack:Add_Routeset_Definition_Files_C|Add the Routset Definition Files to the System]]
*[[Toolpack:Assign_Definition_Digitmap_Files_per_NAP_E|Assign Defintion/Digitmap Files on a per NAP Basis]]
*[[Toolpack:Generate_Dynamic_Routes_D|Generate Dynamic Routes]]
*[[Toolpack:Activating_the_Configuration D|Activate configuration]]
|}

|STYLE="vertical-align: top"|
{| 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;" |Update definition/digitmap files
|-
| valign="top" |
*[[Toolpack:Update_Digitmap_Files_C|Update the Digitmap Files]]
*[[Toolpack:Update_Routeset_Definition_Files_C|Update the Routeset Definition Files]]
*[[Toolpack:Generate_Dynamic_Routes_D|Generate Dynamic Routes]]
*[[Toolpack:Activating_the_Configuration D|Activate configuration]]
|}

|STYLE="vertical-align: top"|
{| 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;" |Examples
|-
| valign="top" |
*[[Group of DIDs to a single outbound NAPs|Group of DIDs to a single outbound NAPs]]
*Same group of DIDs to multiple outbound NAPs
**[[Toolpack:Load-sharing mode|Load-sharing mode]]
**[[Toolpack:Load-sharing mode|Priority mode]]
|}
|}

==RADIUS Authorization and Authentication (ProSBC only)==
{|
|STYLE="vertical-align: top"|
{| 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;" |RADIUS Authorization
|-
| valign="top" |
*[[Toolpack:Configuring_RADIUS_client_E|Configure RADIUS client]]
*[[Toolpack:Adding_RADIUS_server_D|Add RADIUS authorization server]]
*[[Toolpack:Create_New_Routing_Script_D|Create New Routing Script]]
*[[Toolpack:Configuring_RADIUS_authorization_B|Configure RADIUS Authorization]]
*[[Toolpack:Enable_Routing_Script_E|Enable Routing Script]]
|}
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="300" 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 Authorization (with custom dictionary)
|-
| valign="top" |
*[[Toolpack:Import_RADIUS_Custom_Dictionary_B|Import RADIUS Custom Dictionary]]
*[[Toolpack:Configuring_RADIUS_client_E|Configure RADIUS Client]]
*[[Toolpack:Adding_RADIUS_server_D|Add RADIUS authorization Server]]
*[[Toolpack:Create_New_Routing_Script_D|Create New Routing Script]]
*[[Toolpack:Configuring_RADIUS_authorization_B|Configure RADIUS Authorization]]
*[[Toolpack:Enable_Routing_Script_E|Enable Routing Script]]
|}
|}

Toolpack:Tsbc Call Routes Settings 3.1

2020-03-04T20:42:02Z

Nicole Tan: NT: Added Examples for using label routing

{{DISPLAYTITLE:FreeSBC/ProSBC Web Portal 3.1: Call Routes Settings}}

'''Applies to FreeSBC and Tmedia products'''

=Routes=

==Static Route==
{| 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;" |Add routes
|-
| valign="top" |
*[[Toolpack:Creating_a_First_Call_Route E|Create a first call route]]
|}

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

==Label Routing==

This section assumes:
* '''The routing script is already implemented''' (you just need to add the label routing functionality)
* '''The routeset definition and digimap files are already created'''

{|
|STYLE="vertical-align: top"|
{| 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;" |Add label routing functionality
|-
| valign="top" |
*[[Toolpack:Adding_Label_Routing_to_any_Routing_Script_D|Add Label Routing to script]]
*[[Toolpack:Assign_Routing_Script_DB_Files_to_Gateway_Application_E|Assign Routing/Script Files to the Gateway Application]]
*[[Toolpack:Add_Digitmap_Files_C|Add the Digit Map Files to the System]]
*[[Toolpack:Add_Routeset_Definition_Files_C|Add the Routset Definition Files to the System]]
*[[Toolpack:Assign_Definition_Digitmap_Files_per_NAP_E|Assign Defintion/Digitmap Files on a per NAP Basis]]
*[[Toolpack:Generate_Dynamic_Routes_D|Generate Dynamic Routes]]
*[[Toolpack:Activating_the_Configuration D|Activate configuration]]
|}

|STYLE="vertical-align: top"|
{| 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;" |Update definition/digitmap files
|-
| valign="top" |
*[[Toolpack:Update_Digitmap_Files_C|Update the Digitmap Files]]
*[[Toolpack:Update_Routeset_Definition_Files_C|Update the Routeset Definition Files]]
*[[Toolpack:Generate_Dynamic_Routes_D|Generate Dynamic Routes]]
*[[Toolpack:Activating_the_Configuration D|Activate configuration]]
|}

|STYLE="vertical-align: top"|
{| 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;" |Examples
|-
| valign="top" |
*Same DID to multiple outbound NAPs
**[[Toolpack:Load-sharing mode|Load-sharing mode]]
**[[Toolpack:Load-sharing mode|Priority mode]]
|}
|}

==RADIUS Authorization and Authentication (ProSBC only)==
{|
|STYLE="vertical-align: top"|
{| 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;" |RADIUS Authorization
|-
| valign="top" |
*[[Toolpack:Configuring_RADIUS_client_E|Configure RADIUS client]]
*[[Toolpack:Adding_RADIUS_server_D|Add RADIUS authorization server]]
*[[Toolpack:Create_New_Routing_Script_D|Create New Routing Script]]
*[[Toolpack:Configuring_RADIUS_authorization_B|Configure RADIUS Authorization]]
*[[Toolpack:Enable_Routing_Script_E|Enable Routing Script]]
|}
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="300" 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 Authorization (with custom dictionary)
|-
| valign="top" |
*[[Toolpack:Import_RADIUS_Custom_Dictionary_B|Import RADIUS Custom Dictionary]]
*[[Toolpack:Configuring_RADIUS_client_E|Configure RADIUS Client]]
*[[Toolpack:Adding_RADIUS_server_D|Add RADIUS authorization Server]]
*[[Toolpack:Create_New_Routing_Script_D|Create New Routing Script]]
*[[Toolpack:Configuring_RADIUS_authorization_B|Configure RADIUS Authorization]]
*[[Toolpack:Enable_Routing_Script_E|Enable Routing Script]]
|}
|}

Support:public holidays

2019-12-16T16:51:58Z

Nicole Tan: NT: Updated the holidays for 2020 accordingly

{| class="wikitable" width="50%"
|+Montreal, Canada Public Holidays
|Day before Christmas day
|December 24, 2019
|-
|Christmas Day
|December 25, 2019
|-
|Boxing Day
|December 26, 2019
|-
|Day before New Year's day
|December 31, 2019
|-
|New Year's day
|January 1, 2020
|-
|Day after New Year's day
|January 2, 2020
|-
|Good Friday
|April 10, 2020
|-
|Easter Monday
|April 13, 2020
|-
|National Patriots' Day
|May 18, 2020
|-
|Jean Baptiste Day
|June 24, 2020
|-
|Canada Day
|July 1, 2020
|-
|Labour day
|September 7, 2020
|-
|Thanksgiving
|October 12, 2020
|-
|Day before Christmas day
|December 24, 2020
|-
|Christmas Day
|December 25, 2020
|-
|Boxing Day
|December 26, 2020
|-
|Day before New Year's day
|December 31, 2020
|-
|New Year's day
|January 1, 2021
|-
|Day after New Year's day
|January 2, 2021
|}

{| class="wikitable" width="50%"
|+[http://www.gov.hk/en/about/abouthk/holiday/ Hong Kong Public Holidays]
|-
|Christmas Day
|December 25, 2018
|-
|The first weekday after Christmas Day
|December 26, 2018
|-
|The first day of January
|January 1, 2019
|-
|Lunar New Year’s Day
|February 5, 2019
|-
|The second day of Lunar New Year
|February 6, 2019
|-
|The third day of Lunar New Year
|February 7, 2019
|-
|Ching Ming Festival
|April 5, 2019
|-
|Good Friday
|April 19, 2019
|-
|Easter Monday
|April 22, 2019
|-
|Labour Day
|May 1, 2019
|-
|The day following the Birthday of the Buddha
|May 13, 2019
|-
|Tuen Ng Festival
|June 7, 2019
|-
|Hong Kong Special Administrative Region Establishment Day
|July 1, 2019
|-
|The day following the Chinese Mid-Autumn Festival
|September 14, 2019
|-
|National Day
|October 1, 2019
|-
|Chung Yeung Festival
|October 7, 2019
|-
|Christmas Day
|December 25, 2019
|-
|The first weekday after Christmas Day
|December 26, 2019
|-
|New Year's day
|January 1, 2020
|-
|}

Toolpack: How to Get Rid of Sub Optimal

2019-12-02T16:20:24Z

Nicole Tan:

This page shows how to remove the warning of "Sub optimal config sbc list" in the SBC status

="Sub optimal" Waning=
<pre>Gateway -> Routes
</pre>
 
[[File:Sub_Optimal_Config_SBC_List.png|SBC Status]]

= Reason for the Waning=
The reason for this is that some Nics (Azure, vmxnet3, e1000, ixgbe vf) report a RETA size of 0 while reporting multiple rx queues, meaning they can not support multiple CPUs.
However TBRouter is not aware of this limit on those Nics then initiate the Cores on the Nics

==Solutions==
We have ticket 23762 to improve the tbrouter to support RSS when we have a RETA table of 0.
You will experience this warning before the fix.
You can:
1-Just simply ignore the warning.
2- Change the nic.json to remove the section with the extra cores (so those cores can be used for something else) by following the below steps.

==Steps to Get Rid of The Warning ==

:1. ssh to the SBC host and do shell command:
locate nic.json
Output:
/usr/lib/tb/toolpack/setup/12358/3.0/dynamic_nic.json
/usr/lib/tb/toolpack/setup/12358/3.0/nic.json
/usr/lib/tb/toolpack/setup/12358/3.0/validated_nic.json
/usr/lib/tb/toolpack/setup/12358/3.1/current_nic.json
/usr/lib/tb/toolpack/setup/12358/3.1/dynamic_nic.json
/usr/lib/tb/toolpack/setup/12358/3.1/nic.json
/usr/lib/tb/toolpack/setup/12358/3.1/validated_nic.json
/usr/lib/tb/toolpack/tbrouter/current_nic.json

:2. Do a copy of the existing nic.json (only need to operate the version your SBC is running)
e.g. cp /usr/lib/tb/toolpack/setup/12358/3.1/nic.json /usr/lib/tb/toolpack/setup/12358/3.1/nic_bak.json

:3. Edit nic.json
e.g. vim /usr/lib/tb/toolpack/setup/12358/3.1/nic.json

:4. Remove the section with the extra cores
e.g. below is the section for one Nic with 2 cores, simply remove the section of "core": 2,
"00:50:56:95:ba:0e": {
"cores": [
{
"core": 1,
"rx_nb_queues": 2
},
{
"core": 2,
"rx_nb_queues": 2
}
],

Make it simply like this:
"00:50:56:95:ba:0e": {
"cores": [
{
"core": 1,
"rx_nb_queues": 2
}
],

File:Sub Optimal Config SBC List.png

2019-12-02T16:19:47Z

Nicole Tan:

Toolpack: How to Get Rid of Sub Optimal

2019-12-02T16:18:58Z

Nicole Tan: NT: Created new page to explain The Optimal Warning and how to get rid of it

This page shows how to remove the warning of "Sub optimal config sbc list" in the SBC status;.

="Sub optimal" Waning=
<pre>Gateway -> Routes
</pre>
 
[[File:Sub_Optimal_Config_SBC_List.png|SBC Status]]

= Reason for the Waning=
The reason for this is that some Nics (Azure, vmxnet3, e1000, ixgbe vf) report a RETA size of 0 while reporting multiple rx queues, meaning they can not support multiple CPUs.
However TBRouter is not aware of this limit on those Nics then initiate the Cores on the Nics

==Solutions==
We have ticket 23762 to improve the tbrouter to support RSS when we have a RETA table of 0.
You will experience this warning before the fix.
You can:
1-Just simply ignore the warning.
2- Change the nic.json to remove the section with the extra cores (so those cores can be used for something else) by following the below steps.

==Steps to Get Rid of The Warning ==

:1. ssh to the SBC host and do shell command:
locate nic.json
Output:
/usr/lib/tb/toolpack/setup/12358/3.0/dynamic_nic.json
/usr/lib/tb/toolpack/setup/12358/3.0/nic.json
/usr/lib/tb/toolpack/setup/12358/3.0/validated_nic.json
/usr/lib/tb/toolpack/setup/12358/3.1/current_nic.json
/usr/lib/tb/toolpack/setup/12358/3.1/dynamic_nic.json
/usr/lib/tb/toolpack/setup/12358/3.1/nic.json
/usr/lib/tb/toolpack/setup/12358/3.1/validated_nic.json
/usr/lib/tb/toolpack/tbrouter/current_nic.json

:2. Do a copy of the existing nic.json (only need to operate the version your SBC is running)
e.g. cp /usr/lib/tb/toolpack/setup/12358/3.1/nic.json /usr/lib/tb/toolpack/setup/12358/3.1/nic_bak.json

:3. Edit nic.json
e.g. vim /usr/lib/tb/toolpack/setup/12358/3.1/nic.json

:4. Remove the section with the extra cores
e.g. below is the section for one Nic with 2 cores, simply remove the section of "core": 2,
"00:50:56:95:ba:0e": {
"cores": [
{
"core": 1,
"rx_nb_queues": 2
},
{
"core": 2,
"rx_nb_queues": 2
}
],

Make it simply like this:
"00:50:56:95:ba:0e": {
"cores": [
{
"core": 1,
"rx_nb_queues": 2
}
],

VoIP Ethernet Capture FreeSBC A

2019-08-23T14:10:45Z

Nicole Tan:

__NOTOC__
=== '''''Applies to version(s): v3.0, v3.1''''' ===
{{DISPLAYTITLE:VoIP Ethernet Capture on FreeSBC}}

== Capturing VoIP and Ethernet traffic ==

* Connect to the FreeSBC using a ssh connection
* Start tbx_cli_tools_remote (type "tbx_cli_tools_remote")
The following is displayed:
Available remote hosts to control (TBX_GW_PORT=12358, local IPs 172.16.0.1 / 172.18.0.1). Press corresponding letter to
control:
a : TB016634.tbrouter
b : TB016635.gateway
c : TB016635.logtrace
d : TB016635.stream_server
e : TB016635.tboam_app
f : TB016635.tbrouter <------------tbrouter
g : TB016635.tbsnmpagent
h : TB016635.tbsyslog
i : TB016635.tbuctwriter
j : TB016635.toolpack_engine
k : TB016635.toolpack_sys_mgr
l : TB016635.web_server
* Connect to the tbrouter application
* Start capture using the 'p' key (lowercase p), leave default parameters and press 'enter'
* Stop capture using the 'p' key (lowercase p)

== Retrieve VoIP captures ==
VoIP capture files (pcap/Wireshark compatible) are locate here:
/lib/tb/toolpack/tbrouter/pcap
To download the voip capture file, use sFTP on the management port. This can be done on Windows using tools like Filezilla or WinSCP.
'''Note''': There can be multiple capture files per capture session (for example, on systems with 10Gbps network devices, because Ethernet packets on these devices are spread to multiple packets processing/capture cores)

VoIP Ethernet Capture FreeSBC A

2019-08-23T14:10:21Z

Nicole Tan:

__NOTOC__
=== '''''Applies to version(s): v3.0, v3.1''''' ===
{{DISPLAYTITLE:VoIP Ethernet Capture on FreeSBC}}

== Capturing VoIP and Ethernet traffic ==

* Connect to the FreeSBC using a ssh connection
* Start tbx_cli_tools_remote (type "tbx_cli_tools_remote")
The following is displayed:
Available remote hosts to control (TBX_GW_PORT=12358, local IPs 172.16.0.1 / 172.18.0.1). Press corresponding letter to
control:
a : TB016634.tbrouter
b : TB016635.gateway
c : TB016635.logtrace
d : TB016635.stream_server
e : TB016635.tboam_app
f : TB016635.tbrouter <------------tbrouter
g : TB016635.tbsnmpagent
h : TB016635.tbsyslog
i : TB016635.tbuctwriter
j : TB016635.toolpack_engine
k : TB016635.toolpack_sys_mgr
l : TB016635.web_server
* Connect to the tbrouter application
* Start capture using the 'p' key (lowercase p), leave default parameters and press 'enter'
* Stop capture using the 'p' key

== Retrieve VoIP captures ==
VoIP capture files (pcap/Wireshark compatible) are locate here:
/lib/tb/toolpack/tbrouter/pcap
To download the voip capture file, use sFTP on the management port. This can be done on Windows using tools like Filezilla or WinSCP.
'''Note''': There can be multiple capture files per capture session (for example, on systems with 10Gbps network devices, because Ethernet packets on these devices are spread to multiple packets processing/capture cores)

Configure Offline Repository CentOS7 A

2019-06-05T14:23:34Z

Nicole Tan:

{{DISPLAYTITLE:Offline Repository Procedure for CentOS 7}}

This page shows how to configure CentOS packages manager for a system that does not have access to Telcobridges repository (no internet access).

== Download TelcoBridges repository ==
Download the .iso image of TelcoBridges repository on a machine that have access to the system.
http://repo.telcobridges.com/centos/7/isos/x86_64/tb_centos7_x86_64_repo.iso

== Upload TelcoBridges repository to the system ==
Upload the .iso file to the "/root" directory of the system with scp or a SFTP tool like [http://filezilla-project.org/ FileZilla]

== Mount the .iso file on the system ==
Mount the .iso file on your system
# mkdir -p /repo/centos/7
# mount -t iso9660 -o loop /root/tb_centos7_x86_64_repo.iso /repo/centos/7

== Change TelcoBridges repository file ==
Edit the ''TB-Base.repo'' file
# vim /etc/yum.repos.d/TB-Base.repo

Change ''[tb-base]'' '''baseurl''' line to:
baseurl=file:///repo/centos/7/os/$basearch/

== Update CentOS 7 ==
# yum clean metadata
# yum update

== Delete ISO file ==
Since the repository file is quite large, it is better to delete it after the update is complete:
# rm /root/*repo.iso

VoIP Ethernet Capture TSBC-HW

2018-07-09T21:20:31Z

Nicole Tan:

__NOTOC__
=== '''''Applies to version(s): v3.0''''' ===
{{DISPLAYTITLE:VoIP Ethernet Capture SN10500}}

== Capturing using the internal host of the SN10500 unit==
The internal host of the SN10500 can be used for capturing packets that are mirrored from the VOIP0 and/or VOIP1 physical ports. This includes RTP traffic.

=== Start Capture ===
You need '''two''' SSH sessions to capture the traffic: 

'''Step 1'''
*Access the SN10500 management interface using SSH. Then, access the telecom baseboard using telnet:
telnet [eth0 IP address of the telecom unit]

For example

telnet 172.16.123.45

Prompt is now:
0/tbgw>
*Do command "mv88eMonitor" to get the PortMask and PortNumber:
mv88eMonitor

The output should be like this:
Port Mapping:
PortDesc : voip0 voip1 sw6352 fpga mgmt0 mgmt1 eth0 eth1 host sw6321 cpu
PortNumber : 0 1 2 3 4 5 6 7 8 9 10 11 12 13
PortMask : 0x1 0x2 0x4 0x8 0x10 0x20 0x40 0x80 0x100 0x200 0x400 0x800 0x1000 0x2000

*Use this command to capture VoIP0 traffic (for 600 seconds or 10 minutes):
mv88eMonitor 0x8 0x8 11 600
*Use this command to capture VoIP1 traffic:
mv88eMonitor 0x10 0x10 11 600

In the example, the duration is 600 seconds. This will capture traffic for 10 minutes.

Note: We do not recommend to keep capturing for a long time. This is only used for debugging purpose.
 
 

'''Step 2'''

*Access the SN10500 management interface using SSH 
start tbx_cli_tools_remote
[root@TB016635 ~]# tbx_cli_tools_remote

*Connect to tbrouter
(The following is displayed:)
Available remote hosts to control (TBX_GW_PORT=12358, local IPs 172.16.0.1 / 172.18.0.1). Press corresponding letter to
control:
a : TB016634.tbrouter
b : TB016635.gateway
c : TB016635.logtrace
d : TB016635.stream_server
e : TB016635.tboam_app
f : TB016635.tbrouter <------------tbrouter
g : TB016635.tbsnmpagent
h : TB016635.tbsyslog
i : TB016635.tbuctwriter
j : TB016635.toolpack_engine
k : TB016635.toolpack_sys_mgr
l : TB016635.web_server

*Select the tbrouter application. (Letter 'f' in the above example)

*Once you have access to the tbrouter application, press 'p'
Capture circular buffer size (nb of packets)? : 50000 <-- set the number of packets to capture
Capture mode (1:In 2:Out 4:Monitor) (ex: 3=In+out) : 4 <-- Select 4
VLAN id (list, -1:All) (ex:151, 152, 153, 154) : -1
Convert DSA tags to VLAN tags : Yes
Capture only firewall-protected VLANs : Yes

Press Enter to start the capture.

=== Stop Capture ===
Press 'P' (capital letter) to stop the capture.

*Access the telecom baseboard from the SN10500 using telnet.
telnet 172.16.123.45
*Stop the capture
mv88eMonitor 0 0 0

=== Download Capture ===
To download the voip_capture.cap file, use SSH secure copy ("sftp") to the SN10500 management port. This can be done on Windows using tools like [https://filezilla-project.org/ Filezilla] or [http://winscp.net/ WinSCP]. 
The file location of the capture is:
/lib/tb/toolpack/tbrouter/pcap

== References ==
*[[VoIP_Ethernet_Capture|VoIP Ethernet Capture]]
*[[VoIP Ethernet Capture FreeSBC A|FreeSBC VoIP Ethernet Capture]]

VoIP Ethernet Capture TSBC-HW

2018-07-09T21:17:26Z

Nicole Tan: NT: Created new page

__NOTOC__
=== '''''Applies to version(s): v3.0''''' ===
{{DISPLAYTITLE:VoIP Ethernet Capture TSBC5000}}

== Capturing using the internal host of the SN10500 unit==
The internal host of the SN10500 can be used for capturing packets that are mirrored from the VOIP0 and/or VOIP1 physical ports. This includes RTP traffic.

=== Start Capture ===
You need '''two''' SSH sessions to capture the traffic: 

'''Step 1'''
*Access the SN10500 management interface using SSH. Then, access the telecom baseboard using telnet:
telnet [eth0 IP address of the telecom unit]

For example

telnet 172.16.123.45

Prompt is now:
0/tbgw>
*Do command "mv88eMonitor" to get the PortMask and PortNumber:
mv88eMonitor

The output should be like this:
Port Mapping:
PortDesc : voip0 voip1 sw6352 fpga mgmt0 mgmt1 eth0 eth1 host sw6321 cpu
PortNumber : 0 1 2 3 4 5 6 7 8 9 10 11 12 13
PortMask : 0x1 0x2 0x4 0x8 0x10 0x20 0x40 0x80 0x100 0x200 0x400 0x800 0x1000 0x2000

*Use this command to capture VoIP0 traffic (for 600 seconds or 10 minutes):
mv88eMonitor 0x8 0x8 11 600
*Use this command to capture VoIP1 traffic:
mv88eMonitor 0x10 0x10 11 600

In the example, the duration is 600 seconds. This will capture traffic for 10 minutes.

Note: We do not recommend to keep capturing for a long time. This is only used for debugging purpose.
 
 

'''Step 2'''

*Access the SN10500 management interface using SSH 
start tbx_cli_tools_remote
[root@TB016635 ~]# tbx_cli_tools_remote

*Connect to tbrouter
(The following is displayed:)
Available remote hosts to control (TBX_GW_PORT=12358, local IPs 172.16.0.1 / 172.18.0.1). Press corresponding letter to
control:
a : TB016634.tbrouter
b : TB016635.gateway
c : TB016635.logtrace
d : TB016635.stream_server
e : TB016635.tboam_app
f : TB016635.tbrouter <------------tbrouter
g : TB016635.tbsnmpagent
h : TB016635.tbsyslog
i : TB016635.tbuctwriter
j : TB016635.toolpack_engine
k : TB016635.toolpack_sys_mgr
l : TB016635.web_server

*Select the tbrouter application. (Letter 'f' in the above example)

*Once you have access to the tbrouter application, press 'p'
Capture circular buffer size (nb of packets)? : 50000 <-- set the number of packets to capture
Capture mode (1:In 2:Out 4:Monitor) (ex: 3=In+out) : 4 <-- Select 4
VLAN id (list, -1:All) (ex:151, 152, 153, 154) : -1
Convert DSA tags to VLAN tags : Yes
Capture only firewall-protected VLANs : Yes

Press Enter to start the capture.

=== Stop Capture ===
Press 'P' (capital letter) to stop the capture.

*Access the telecom baseboard from the SN10500 using telnet.
telnet 172.16.123.45
*Stop the capture
mv88eMonitor 0 0 0

=== Download Capture ===
To download the voip_capture.cap file, use SSH secure copy ("sftp") to the SN10500 management port. This can be done on Windows using tools like [https://filezilla-project.org/ Filezilla] or [http://winscp.net/ WinSCP]. 
The file location of the capture is:
/lib/tb/toolpack/tbrouter/pcap

== References ==
*[[VoIP_Ethernet_Capture|VoIP Ethernet Capture]]
*[[VoIP Ethernet Capture FreeSBC A|FreeSBC VoIP Ethernet Capture]]

Reset Host Role or Change Internal Subnet for TMG7800

2018-06-22T20:31:00Z

Nicole Tan:

__NoToc__
=== '''''Applies to TMG7800 CTRL server which are NOT manufactured by Telcobridges''''' ===
=== '''''Applies to version v2.8 and above''''' ===
IIf your TMG7800 CTRL are Telcobridges' severs, please refer to [[TMG:Change_Internal_Subnets_Procedure|TMG:Change Internal Subnets Procedure]]
{{DISPLAYTITLE:Reset Host Role for TMG7800 CTRL}}

This procedure describes how to reset the host role for TMG7800 CTRL.

* ssh to the TMG7800 CTRLs
* vim /lib/tb/toolpack/setup/12358/x.y/toolpack.ini
x.y is the toolpack version, e.g. 2.10 or 3.0

For TMG7800 1+1 CTRLs, on both Primary and Secondary CTRL:

TBX_PRIMARY_HOST = 1

TBDB_SERVER_SEC = /

e.g.:
On the Primary:
# Variables related to networking
TBX_GW_PORT = 12358
TBX_GW_ADDRESS_0 = 192.168.10.50
TBX_GW_ADDRESS_1 = 192.168.11.50
TBX_PRIMARY_HOST = 1
# Variables related to database access driver
TBDB_DRIVER = ODBC
TBDB_ODBC_DRIVER = MySQL
# Name of the MySQL database that contains Toolpack configuration
# Note: Current major version is added to the name,
# For example "toolpack" -> "toolpack_2_10"
TBDB_DB_NAME = toolpack
# Variables related to database server configuration
TBDB_SERVER_PRI = 192.168.10.50/192.168.11.50
TBDB_UID_PRI = tbdb
TBDB_PWD_PRI = tbdbpw
TBDB_PORT_PRI = 3306
TBDB_SERVER_SEC = /
TBDB_UID_SEC = tbdb
TBDB_PWD_SEC = tbdbpw
TBDB_PORT_SEC = 3306

On the Secondary:
# Variables related to networking
TBX_GW_PORT = 12358
TBX_GW_ADDRESS_0 = 192.168.10.51
TBX_GW_ADDRESS_1 = 192.168.11.51
TBX_PRIMARY_HOST = 1
# Variables related to database access driver
TBDB_DRIVER = ODBC
TBDB_ODBC_DRIVER = MySQL
# Name of the MySQL database that contains Toolpack configuration
# Note: Current major version is added to the name,
# For example "toolpack" -> "toolpack_2_10"
TBDB_DB_NAME = toolpack
# Variables related to database server configuration
TBDB_SERVER_PRI = 192.168.10.51/192.168.11.51
TBDB_UID_PRI = tbdb
TBDB_PWD_PRI = tbdbpw
TBDB_PORT_PRI = 3306
TBDB_SERVER_SEC = /
TBDB_UID_SEC = tbdb
TBDB_PWD_SEC = tbdbpw
TBDB_PORT_SEC = 3306

Note: One of the above CTRLs now should be moved to a different network.

Reset Host Role or Change Internal Subnet for TMG7800

2018-06-22T20:28:47Z

Nicole Tan: NT completed the reset host role part

__NoToc__
=== '''''Applies to TMG7800 CTRL server which are NOT manufactured by Telcobridges''''' ===
=== '''''Applies to version v2.8 and above''''' ===
IIf your TMG7800 CTRL are Telcobridges' severs, please refer to [[TMG:Change_Internal_Subnets_Procedure|TMG:Change Internal Subnets Procedure]]
{{DISPLAYTITLE:Reset Host Role for TMG7800 CTRL}}

This procedure describes how to reset the host role for changing the TMG7800 CTRL setup, or the 1+1 internal Subnet.

- Convert a TMG7800 CTRL 1+1 to 2 standalone CTRL

- Change the internal Subnet

== Convert a TMG7800 CTRL 1+1 to 2 standalone CTRL ==
* ssh to the TMG7800 CTRLs
* vim /lib/tb/toolpack/setup/12358/x.y/toolpack.ini
x.y is the toolpack version, e.g. 2.10 or 3.0

On both Primary and Secondary CTRL:

TBX_PRIMARY_HOST = 1

TBDB_SERVER_SEC = /

e.g.:
On the Primary:
# Variables related to networking
TBX_GW_PORT = 12358
TBX_GW_ADDRESS_0 = 192.168.10.50
TBX_GW_ADDRESS_1 = 192.168.11.50
TBX_PRIMARY_HOST = 1
# Variables related to database access driver
TBDB_DRIVER = ODBC
TBDB_ODBC_DRIVER = MySQL
# Name of the MySQL database that contains Toolpack configuration
# Note: Current major version is added to the name,
# For example "toolpack" -> "toolpack_2_10"
TBDB_DB_NAME = toolpack
# Variables related to database server configuration
TBDB_SERVER_PRI = 192.168.10.50/192.168.11.50
TBDB_UID_PRI = tbdb
TBDB_PWD_PRI = tbdbpw
TBDB_PORT_PRI = 3306
TBDB_SERVER_SEC = /
TBDB_UID_SEC = tbdb
TBDB_PWD_SEC = tbdbpw
TBDB_PORT_SEC = 3306

On the Secondary:
# Variables related to networking
TBX_GW_PORT = 12358
TBX_GW_ADDRESS_0 = 192.168.10.51
TBX_GW_ADDRESS_1 = 192.168.11.51
TBX_PRIMARY_HOST = 1
# Variables related to database access driver
TBDB_DRIVER = ODBC
TBDB_ODBC_DRIVER = MySQL
# Name of the MySQL database that contains Toolpack configuration
# Note: Current major version is added to the name,
# For example "toolpack" -> "toolpack_2_10"
TBDB_DB_NAME = toolpack
# Variables related to database server configuration
TBDB_SERVER_PRI = 192.168.10.51/192.168.11.51
TBDB_UID_PRI = tbdb
TBDB_PWD_PRI = tbdbpw
TBDB_PORT_PRI = 3306
TBDB_SERVER_SEC = /
TBDB_UID_SEC = tbdb
TBDB_PWD_SEC = tbdbpw
TBDB_PORT_SEC = 3306

Note: One of the above CTRLs now should be moved to a different network.

Reset Host Role or Change Internal Subnet for TMG7800

2018-06-22T20:26:31Z

Nicole Tan:

__NoToc__
=== '''''Applies to TMG7800 CTRL server which are not manufactured by Telcobridges''''' ===
=== '''''Applies to version v2.8 and above''''' ===
IIf your TMG7800 CTRL are Telcobridges' severs, please refer to [[TMG:Change_Internal_Subnets_Procedure|TMG:Change Internal Subnets Procedure]]
{{DISPLAYTITLE:Reset Host Role or Change Internal Subnet for TMG7800}}

This procedure describes how to reset the host role for changing the TMG7800 CTRL setup, or the 1+1 internal Subnet.

- Convert a TMG7800 CTRL 1+1 to 2 standalone CTRL

- Change the internal Subnet

== Convert a TMG7800 CTRL 1+1 to 2 standalone CTRL ==
* ssh to the TMG7800 CTRLs
* vim /lib/tb/toolpack/setup/12358/x.y/toolpack.ini
x.y is the toolpack version, e.g. 2.10 or 3.0
On both Primary and Secondary CTRL:

TBX_PRIMARY_HOST = 1

TBDB_SERVER_SEC = /

e.g.:
On the Primary:
# Variables related to networking
TBX_GW_PORT = 12358
TBX_GW_ADDRESS_0 = 192.168.10.50
TBX_GW_ADDRESS_1 = 192.168.11.50
TBX_PRIMARY_HOST = 1
# Variables related to database access driver
TBDB_DRIVER = ODBC
TBDB_ODBC_DRIVER = MySQL
# Name of the MySQL database that contains Toolpack configuration
# Note: Current major version is added to the name,
# For example "toolpack" -> "toolpack_2_10"
TBDB_DB_NAME = toolpack
# Variables related to database server configuration
TBDB_SERVER_PRI = 192.168.10.50/192.168.11.50
TBDB_UID_PRI = tbdb
TBDB_PWD_PRI = tbdbpw
TBDB_PORT_PRI = 3306
TBDB_SERVER_SEC = /
TBDB_UID_SEC = tbdb
TBDB_PWD_SEC = tbdbpw
TBDB_PORT_SEC = 3306

On the Secondary:
# Variables related to networking
TBX_GW_PORT = 12358
TBX_GW_ADDRESS_0 = 192.168.10.51
TBX_GW_ADDRESS_1 = 192.168.11.51
TBX_PRIMARY_HOST = 1
# Variables related to database access driver
TBDB_DRIVER = ODBC
TBDB_ODBC_DRIVER = MySQL
# Name of the MySQL database that contains Toolpack configuration
# Note: Current major version is added to the name,
# For example "toolpack" -> "toolpack_2_10"
TBDB_DB_NAME = toolpack
# Variables related to database server configuration
TBDB_SERVER_PRI = 192.168.10.51/192.168.11.51
TBDB_UID_PRI = tbdb
TBDB_PWD_PRI = tbdbpw
TBDB_PORT_PRI = 3306
TBDB_SERVER_SEC = /
TBDB_UID_SEC = tbdb
TBDB_PWD_SEC = tbdbpw
TBDB_PORT_SEC = 3306

Note: One of the above CTRLs now should be moved to a different network.
== Change the internal Subnet ==

Reset Host Role or Change Internal Subnet for TMG7800

2018-06-22T15:53:24Z

Nicole Tan: NT: Added new doc for the procedure to rest the host role for non-TMG CTRL

Toolpack:Loggable Statistics C

2018-06-18T21:05:38Z

Nicole Tan:

=== '''''Applies to version(s): v2.10, v3.0.''''' ===
{{DISPLAYTITLE:Loggable Statistics}}

Here is a list of the most useful loggable statistic items.

{| class='wikitable'
|-
! width="100" | Type
! Statistic
! Description
! Path
|-
| rowspan="1" valign="top" | Calls
| active_call_cnt || Number of active calls. || /system/calls
|-
| rowspan="8" valign="top" | Lawful Intercept
| total_interception_call_legs_failed || Total number of interception call legs that failed to provide audio to Law agencies || /intercept
|-
| total_iri_record_files_dropped || Total number of IRI record files dropped upload queue overflow || /intercept
|-
| total_iri_server_connection_failure || Total number of failed connection attempts to the IRI upload server || /intercept
|-
| curr_intercepted_calls || Current number of intercepted calls || /intercept
|-
| total_intercepted_calls || Total number of intercepted calls || /intercept
|-
| total_iri_records || Total number of generated IRI records || /intercept
|-
| curr_iri_record_files_queued || Current number of queued IRI record files pending for upload || /intercept
|-
| curr_iri_record_files_queue_state || Current IRI record files upload queue state || /intercept
|-
| rowspan="10" valign="top" | RADIUS
| acct_queued_records || Current number of queued accounting records waiting to be sent || /radius
|-
| acct_success_record_cnt || Number of accounting records that were successfully sent and acknowledged || /system/radius
|-
| acct_lost_record_cnt || Number of accounting records that were lost either because they didn't fit in a queue or no servers responsed to them || /system/radius
|-
| auth_queued || Current number of queued authorizations waiting to be sent || /radius
|-
| auth_success_cnt || Number of authorizations that were successfully sent and acknowledged || /system/radius
|-
| auth_lost_cnt || Number of authorizations that were lost either because they didn't fit in a queue or no servers responsed to them || /system/radius
|-
| state || RADIUS server activity state current, active or inactive || /radius/server
|-
| availability || RADIUS server availabilty the last time it was used: up, down or unknown not yet used || /radius/server
|-
| acct_all_servers_down || When this is set, this means the RADIUS client was unable to exchange data with any of the provided RADIUS accounting servers. || /radius/server
|-
| auth_all_servers_down || When this is set, this means the RADIUS client was unable to exchange data with any of the provided RADIUS authorization servers. || /radius/server
|-
| rowspan="23" valign="top" | System
| active_configuration || Active Toolpack configuration. || /system
|-
| active_package || Active Toolpack package. || /system
|-
| oam_target_state || OAM target state for the application. || /host/application
|-
| fault_cnt || Number of faulty applications. || /system/host_applications
|-
| up || Tells if the database is up. || /database
|-
| valid || Tells if the database is valid. || /database
|-
| nb_files || Current number of files under this folder. || /host/folder_cleanup
|-
| nb_files_percent || Current percent ratio between number of files and maximum under this folder. || /host/folder_cleanup
|-
| files_size || Current total size in MB of files under this folder. || /host/folder_cleanup
|-
| files_size_percent || Current percent ratio between total files size and maximum under this folder. || /host/folder_cleanup
|-
| nb_deleted_files || Number of files deleted from this folder. || /host/folder_cleanup
|-
| oam_mode || Toolpack OAM mode. || /host
|-
| oam_state || Toolpack OAM state. || /host
|-
| not_ready_cnt || Number of hosts that are not ready in the system. || /system/hosts
|-
| percentage || Percentage of cpu used on host. || /host/pm
|-
| disk_full || Disk full. || /host/pm/file_system
|-
| free_space || Available filesytem space in KB. || /host/pm/file_system
|-
| disk_full_cnt || Number of hosts on which the disk is full. || /system/filesystems
|-
| sent_error_bytes_total || Total bytes with error sent by this network adapter || /host/pm/network
|-
| percentage || Percentage of RAM used on host. || /host/pm/ram
|-
| swap_used_total || Total Swap used on host || /host/pm/ram
|-
| host_virtual_interface_state || Current state of the virtual interface on the host. || /system_virtual_ip_interface
|-
| not_ready_cnt || Number of system virtual interfaces that are not ready in the system. || /system/system_virtual_ip_interfaces
|-
| rowspan="1" valign="top" | Mixer
| count || Number of mixer in the system. || /mixer
|-
| rowspan="53" valign="top" | Nap
| Call congestion || Indicate if NAP is considered locally congested (too many calls dropped due to local congestion in the last period). || /nap
|-
| Call congestion period dropped calls || Instantaneous Count of incoming calls. || /nap
|-
| Firewall blocked || Indicate if NAP is actually blocked (banned) by the firewall (due to bandwidth or packets/s threshold passed) . || /nap
|-
| Firewall blocked cnt || Number of times this NAP has been blocked (banned) by the firewall. || /nap
|-
| inst_incoming_call_cnt || Instantaneous Count of incoming calls. || /nap
|-
| Inst incoming call cnt highest || Highest Instantaneous Count of incoming calls. || /nap
|-
| Inst incoming call cnt in progress || Instantaneous count of incoming in-progress calls (waiting to be answered). || /nap
|-
| Inst incoming call cnt answered || Instantaneous count of incoming answered calls. || /nap
|-
| Inst incoming call cnt terminating|| Instantaneous count of incoming terminating calls. || /nap
|-
| Inst incoming call rate|| Current incoming call rate (calls per second). || /nap
|-
| Inst incoming call rate highest|| Highest incoming call rate (calls per second). || /nap
|-
| Inst incoming call rate answered|| Current incoming answered call rate (calls per second). || /nap
|-
| Inst incoming call rate answered highest|| Highest incoming answered call rate (calls per second). || /nap
|-
| inst_outgoing_call_cnt || Instantaneous Count of outgoing calls. || /nap
|-
| Inst outgoing call cnt highest || Highest Instantaneous Count of outgoing calls. || /nap
|-
| Inst outgoing call cnt in progress || Instantaneous count of outgoing in-progress calls (waiting to be answered). || /nap
|-
| Inst outgoing call cnt answered || Instantaneous count of outgoing answered calls. || /nap
|-
| Inst outgoing call cnt terminating || Instantaneous count of incoming terminating calls. || /nap
|-
| Inst outgoing call rate || Current incoming call rate (calls per second). || /nap
|-
| Inst outgoing call rate highest || Highest incoming call rate (calls per second). || /nap
|-
| Inst outgoing call rate answered || Current incoming answered call rate (calls per second). || /nap
|-
| Inst outgoing call rate answered highest || Highest incoming answered call rate (calls per second). || /nap
|-
| Inst incoming interceptions || Instantaneous count of incoming packet-cable interceptions (there may be more than one per call leg). || /nap
|-
| Inst incoming file playbacks|| Instantaneous count of file playbacks on incoming calls (there may be more than one per call leg). || /nap
|-
| Inst incoming file recordings|| Instantaneous count of file recordings on incoming calls. || /nap
|-
| Total incoming interceptions|| Total (cumulative) count of incoming packet-cable interceptions (there may be more than one per call leg). || /nap
|-
| Total incoming file playbacks|| Total (cumulative) count of file playbacks on incoming calls (there may be more than one per call leg). || /nap
|-
| Total incoming file recordings|| Total (cumulative) count of file recordings on incoming calls. || /nap
|-
| Inst outgoing interceptions|| Instantaneous count of outgoing packet-cable interceptions (there may be more than one per call leg). || /nap
|-
| Inst outgoing file playbacks|| Instantaneous count of file playbacks on outgoing calls (there may be more than one per call leg). || /nap
|-
| Inst outgoing file recordings|| Instantaneous count of file recordings on outgoing calls. || /nap
|-
| Total outgoing interceptions|| Total (cumulative) count of outgoing packet-cable interceptions (there may be more than one per call leg). || /nap
|-
| Total outgoing file playbacks|| Total (cumulative) count of file playbacks on outgoing calls (there may be more than one per call leg). || /nap
|-
| Total outgoing file recordings|| Total (cumulative) count of file recordings on outgoing calls. || /nap
|-
| available_cnt || Number of available circuits or channels. || /nap
|-
| unavailable_cnt || Number of unavailable circuits or channels. || /nap
|-
| availability_percent || Percentage of available circuits or channels. || /nap
|-
| usage_percent || Percentage of used circuits or channels. || /nap
|-
| unused_shared_percent || Percentage of used circuits or channels of this NAP available to make new calls with. This takes into account resources shared with other NAPs (in SIP case, when multiple NAPs use SIP stack or VOIP resources on the same adapters). || /nap
|-
| asr_stats_incoming_struct || Detailed Answer/Seizure Ratio Statistics for incoming calls. || /nap
|-
| global_asr_percent || Global calculated ASR percentage for incoming calls. || /nap
|-
| total_call_cnt || Total cumulative count of incoming calls. || /nap
|-
| total_answered_call_cnt || Total cumulative count of incoming answered calls. || /nap
|-
| current_hour_asr_percent || Calculated ASR percentage in the current hour for incoming calls || /nap
|-
| asr_stats_outgoing_struct || Detailed Answer/Seizure Ratio Statistics for outgoing calls. || /nap
|-
| global_asr_percent || Global calculated ASR percentage for outgoing calls. || /nap
|-
| total_call_cnt || Total cumulative count of outgoing calls. || /nap
|-
| total_answered_call_cnt || Total cumulative count of outgoing answered calls. || /nap
|-
| is_available || Remote proxy actually available or not || /nap
|-
| to_net_nb_arp_failures || Number of ARP failures while trying to send packets to the VOIP network || /nap
|-
| available_nap_cnt || Number of available NAP. || /system/naps
|-
| partially_available_nap_cnt || Number of partially available NAP. || /system/naps
|-
| unavailable_nap_cnt || Number of unavailable NAP. || /system/naps
|-
| rowspan="18" valign="top" | Hardware Units
| oam_target_state || OAM target state: Enabled, Maintenance not used for now, replaced by it's backup, Disabled not used, not replaced by it's backup || /adapter
|-
| oam_target_update_state || OAM target update state for the unit used by OAM system when it requires to update this unit to a new version. || /adapter
|-
| oam_current_state || OAM current state of the unit. || /adapter
|-
| configuration_state || Current configuration state of this unit. || /adapter
|-
| cpu_usage || Current CPU usage of that unit. || /adapter
|-
| absolute_reboot_cnt || Nb of times the unit rebooted since begining of time. || /adapter
|-
| firmware_version || Current version of the unit's firmware. || /adapter
|-
| fault_cnt || Number of units in fault invalid configuration?. || /system/adapters
|-
| down_cnt || Number of units having lost communication with the system. || /system/adapters
|-
| license_expired_cnt || Number of units having an expired license. || /system/adapters
|-
| value_integer || Integer portion of the sensor value. || /adapter/sensor
|-
| cpu_0_usage || Unit's current CPU 0 usage in percent. || /adapter/usage
|-
| cpu_1_usage || Unit's current CPU 1 usage in percent. || /adapter/usage
|-
| dsp_usage || Unit's current DSP usage in percent. || /adapter/usage
|-
| voip_usage || Unit's current VOIP usage in percent. || /adapter/usage
|-
| high_cpu_usage_cnt || Number of adapters with high CPU usage > 90% usage. || /system/adapters_usage
|-
| high_dsp_usage_cnt || Number of adapters with high DSP usage > 90% of capacity. || /system/adapters_usage
|-
| high_voip_usage_cnt || Number of adapters with high VOIP usage > 90% of capacity. || /system/adapters_usage
|-
| rowspan="1" valign="top" | BITS port
| down_cnt || Number of down bits ports. || /system/bits
|-
| rowspan="4" valign="top" | CAS
| signaling_up || Whether or not the state is up. || /adapter/casr2
|-
| down_cnt || Number of CASR2 stack with physical line or signaling down. || /system/casr2_stacks
|-
| idle_cnt || Number of idle circuits. || /adapter/casr2/circuit_group
|-
| down_cnt || Number of circuits in down state. || /adapter/casr2/circuit_group
|-
| rowspan="3" valign="top" | TDM clocking
| clk_src_type || Clock source type. || /adapter/clock
|-
| clk_ref_grade || Clock reference grade. || /clock/ref
|-
| clk_ref_active || Clock reference active. || /clock/ref
|-
| rowspan="8" valign="top" | IP interfaces
| rx_bandwidth_pct || Current Rx bandwidth on this interface in percent of link capacity. || /adapter/ip_interface
|-
| tx_bandwidth_pct || Current Tx bandwidth on this interface in percent of link capacity. || /adapter/ip_interface
|-
| bad_frames_received || The number of bad ethernet frames received. || /adapter/ip_interface
|-
| packets_received || Total number of packets received. || /adapter/ip_interface
|-
| packets_sent || Total number of packets transmitted or attempted to transmit. || /adapter/ip_interface
|-
| link_up || Ethernet link status. || /adapter/ip_interface
|-
| up_cnt || Number of up ip interfaces. || /system/ip_interfaces
|-
| down_cnt || Number of down ip interfaces. || /system/ip_interfaces
|-
| rowspan="8" valign="top" | ISDN
| d_channel_up || Whether or not the state is up. || /adapter/isdn
|-
| nb_d_channel_up_events || Number of D-Channel UP events received || /adapter/isdn
|-
| Call || Call statistics || /adapter/isdn
|-
| nb_initiated_incoming || Number of incoming calls || /adapter/isdn
|-
| nb_initiated_outgoing || Number of outgoing calls || /adapter/isdn
|-
| up_cnt || Number of ISDN stack with D channel up. || /system/isdn_stacks
|-
| down_cnt || Number of ISDN stack with D channel down. || /system/isdn_stacks
|-
| not_configured || No elements configured in the system. || /system/isdn_stacks
|-
| rowspan="15" valign="top" | IUA
| up || IUA Link is Up or Down. || /adapter/iua/sap/cluster/link
|-
| flow_control || IUA Link is in flow-control state. || /adapter/iua/sap/cluster/link
|-
| rx_pdu || Nb of PDUs received. || /adapter/iua/sap/cluster/link
|-
| tx_pdu || Nb of PDUs transmitted. || /adapter/iua/sap/cluster/link
|-
| up_cnt || Number of iua links in 'up' state. || /system/iua_links
|-
| down_cnt || Number of iua links in 'down' state. || /system/iua_links
|-
| peer_state || Peer state. || /adapter/iua/sap/cluster/peer
|-
| inhibited || Inhibited by management. || /adapter/iua/sap/cluster/peer
|-
| active_cnt || Number of iua peers in 'active' state. || /system/iua_peers
|-
| down_cnt || Number of iua peers in 'down' state. || /system/iua_peers
|-
| opened || Is IUA SAP opened. || /adapter/iua/sap
|-
| configured_cnt || Number of IUA sap in 'configured' state. || /system/iua_saps
|-
| unconfigured_cnt || Number of IUA sap in 'unconfigured' state. || /system/iua_saps
|-
| endpoint_opened_cnt || Number of IUA sap with endpoints opened. || /system/iua_saps
|-
| endpoint_closed_cnt || Number of IUA sap with endpoints closed. || /system/iua_saps
|-
| rowspan="5" valign="top" | LAPD
| up || Link is Up or Down. || /adapter/lapd_link
|-
| active_sap_cnt || Number of active SAP. || /adapter/lapd_link
|-
| data_link_conection_cnt || Number of data link connections. || /adapter/lapd_link
|-
| up_cnt || Number of lapd links in 'up' state. || /system/lapd_links
|-
| down_cnt || Number of lapd links in 'down' state. || /system/lapd_links
|-
| rowspan="21" valign="top" | Line Interfaces
| state || Line state. || /adapter/line_interface
|-
| alarm_count || Cumulative count of raised alarms LOS || /adapter/line_interface
|-
| anomaly_count || Cumulative count of all anomalies detected rsp, cvc, etc.... || /adapter/line_interface
|-
| loopback || Line loopback identifier. || /adapter/line_interface
|-
| state || Line state. || /adapter/line_interface
|-
| alarm_count || Cumulative count of raised alarms LOS || /adapter/line_interface
|-
| anomaly_count || Cumulative count of all anomalies detected rsp, cvc, etc.... || /adapter/line_interface
|-
| loopback || Line loopback identifier. || /adapter/line_interface
|-
| tx_state || The line interface transmitter. || /adapter/line_interface
|-
| state || Line state. || /adapter/line_interface
|-
| alarm_count || Cumulative count of raised alarms LOS || /adapter/line_interface
|-
| anomaly_count || Cumulative count of all anomalies detected rsp, cvc, etc.... || /adapter/line_interface
|-
| protection_activated || Whether or not a protection-switch is currently under way. || /adapter/line_interface
|-
| tx_state || The line interface transmitter. || /adapter/line_interface
|-
| loopback || Line loopback identifier. || /adapter/line_interface
|-
| up_cnt || Number of up lines. || /system/line_interfaces
|-
| down_cnt || Number of down lines. || /system/line_interfaces
|-
| alarm_cnt || Number of lines with alarms. || /system/line_interfaces
|-
| defect_cnt || Number of lines with defects. || /system/line_interfaces
|-
| available_trunk_cnt || Number of available line services ready to make TDM calls with. || /system/line_services_leaf
|-
| unavailable_trunk_cnt || Number of unavailable line services not ready to make TDM calls with. || /system/line_services_leaf
|-
| rowspan="6" valign="top" | TMS
| tms0_link_active || Tells if link A is active. || /adapter/mbl_port
|-
| tms1_link_active || Tells if link B is active. || /adapter/mbl_port
|-
| tmp_no_alarm_cnt || Number of unit TMS ports without alarms. || /system/mbl_ports
|-
| tmp_alarm_cnt || Number of unit TMS ports with alarms. || /system/mbl_ports
|-
| tms_no_alarm_cnt || Number of TMS switch ports without alarms. || /system/mbl_ports
|-
| tms_alarm_cnt || Number of TMS switch ports with alarms. || /system/mbl_ports
|-
| rowspan="17" valign="top" | SCTP
| path_active || Is PATH active. || /adapter/sctp_sap
|-
| flow_control || Local congestion flag from SCTP. || /adapter/sctp_sap
|-
| rx_byte || Nb of bytes received. || /adapter/sctp_sap
|-
| tx_byte || Nb of bytes transmitted. || /adapter/sctp_sap
|-
| configured_cnt || Number of sctp sap in 'configured' state. || /system/sctp_sap
|-
| unconfigured_cnt || Number of sctp sap in 'unconfigured' state. || /system/sctp_sap
|-
| path_active_cnt || Number of sctp sap with active path. || /system/sctp_sap
|-
| path_inactive_cnt || Number of sctp sap with inactive path. || /system/sctp_sap
|-
| congested_cnt || Number of sctp sap congested. || /system/sctp_sap
|-
| configured || Is SCTP TSAP configured. || /adapter/sctp_tsap
|-
| tucl_failed || Is Tucl failed. || /adapter/sctp_tsap
|-
| rx_byte || Nb of bytes received. || /adapter/sctp_tsap
|-
| tx_byte || Nb of bytes transmitted. || /adapter/sctp_tsap
|-
| configured_cnt || Number of sctp tsap in 'configured' state. || /system/sctp_tsap
|-
| unconfigured_cnt || Number of sctp tsap in 'unconfigured' state. || /system/sctp_tsap
|-
| tucl_failed_cnt || Number of sctp tsap where tucl failed. || /system/sctp_tsap
|-
| tucl_not_failed_cnt || Number of sctp tsap where tucl did not failed.. || /system/sctp_tsap
|-
| rowspan="19" valign="top" | SIP
| request_in_cnt || Total number of SIP request messages received, including retransmissions. || /sip
|-
| request_out_cnt || Total number of SIP request messages sent out, including retransmissions. || /sip
|-
| response_in_cnt || Total number of SIP response messages received, including retransmissions. || /sip
|-
| response_out_cnt || Total number of SIP response messages sent out, including retransmissions. || /sip
|-
| request_retry_cnt || Total number of SIP request retransmissions sent. || /sip
|-
| response_retry_cnt || Total number of SIP response retransmissions sent. || /sip
|-
| congestion_period_cnt || Number of times the system came in memory congestion. || /sip
|-
| critical_congestion_period_cnt || Number of times the system came in critical memory congestion. || /sip
|-
| call_congestion_period_cnt || Number of times the system came in call congestion. || /sip
|-
| current_mem_status || Current memory status. || /sip
|-
| congestion_drop_from_network_cnt || Number of incoming network messages dropped due to congestion. || /sip
|-
| congestion_drop_from_user_cnt || Number of API messages dropped due to congestion. || /sip
|-
| current_active_call_cnt || Current number of activate calls answered calls that are not terminating. || /sip
|-
| current_transient_call_cnt || Current number of transient calls. || /sip
|-
| cfg_cnt || Number of sip configurations in the system. || /system/sips
|-
| not_configured || No elements configured in the system. || /system/sips
|-
| calls_tx_cnt || The number of calls initiated to the service provider for this SAP. || /sip/sap
|-
| calls_rx_cnt || The number of calls received from the service provider for this SAP. || /sip/sap
|-
| sap_cnt || Number of sip saps in the system. || /system/sip_saps
|-
| rowspan="20" valign="top" | ISUP
| interface_down || Circuit group's interface is down. || /isup/interface/cic_group
|-
| idle_cnt || Number of idle circuits. || /isup/interface/cic_group
|-
| reset_cnt || Number of circuits in reset state. || /isup/interface/cic_group
|-
| idle_cnt || Number of idle circuits. || /system/cic_groups
|-
| locally_blocked_cnt || Number of circuits in locally blocked state. || /system/cic_groups
|-
| remotely_blocked_cnt || Number of circuits in remotely blocked state. || /system/cic_groups
|-
| locally_remotely_blocked_cnt || Number of circuits in locally remotely blocked state. || |/system/cic_groups
|-
| down_cnt || Number of circuits with an interface down. || /system/cic_groups
|-
| reset_cnt || Number of circuits in reset state. || /system/cic_groups
|-
| primary_state || State of Isup stack on pimary unit. || /isup
|-
| secondary_state || State of Isup stack on secondary unit. || /isup
|-
| active_cnt || Number of isup layers in active state. || /system/isups
|-
| standby_cnt || Number of isup layers in standby state. || /system/isups
|-
| oos_cnt || Number of isup layers in Out Of Service state. || /system/isups
|-
| current_state || Interface current state. || /isup/interface
|-
| rx_message_cnt || Total number of received messages i.e. PDUs. || /isup/interface
|-
| tx_message_cnt || Total number of transmitted messages i.e. PDUs. || /isup/interface
|-
| available_cnt || Number of available isup interfaces. || /system/isup_interfaces
|-
| unavailable_cnt || Number of unavailable isup interfaces. || /system/isup_interfaces
|-
| congested_cnt || Number of congested isup interfaces. || /system/isup_interfaces
|-
| rowspan="16" valign="top" | M2PA
| up || Is link Up. || /adapter/m2pa/link
|-
| current_link_disabled || Is link disabled by management. || /adapter/m2pa/link
|-
| rx_msu || Nb of MSUs received. || /adapter/m2pa/link
|-
| tx_msu || Nb of MSUs transmitted. || /adapter/m2pa/link
|-
| rx_current_bandwidth || Bytes received in the last second. || /adapter/m2pa/link
|-
| tx_current_bandwidth || Bytes transmitted in the last second. || /adapter/m2pa/link
|-
| up_cnt || Number of m2pa links in 'up' state. || /system/m2pa_links
|-
| down_cnt || Number of m2pa links in 'down' state. || /system/m2pa_links
|-
| sap_configured || Is M2PA SAP configured. || /adapter/m2pa/sap
|-
| endpoint_opened || Is endpoint opened. || /adapter/m2pa/sap
|-
| rx_pdu || Nb of PDUs received. || /adapter/m2pa/sap
|-
| tx_pdu || Nb of PDUs transmitted. || /adapter/m2pa/sap
|-
| configured_cnt || Number of m2pa sap in 'configured' state. || /system/m2pa_saps
|-
| unconfigured_cnt || Number of m2pa sap in 'unconfigured' state. || /system/m2pa_saps
|-
| endpoint_opened_cnt || Number of m2pa sap with endpoints opened. || /system/m2pa_saps
|-
| endpoint_closed_cnt || Number of m2pa sap with endpoints closed. || /system/m2pa_saps
|-
| rowspan="21" valign="top" | M2UA
| up || M2UA Link is Up or Down. || /adapter/m2ua/sap/cluster/link
|-
| flow_control || M2UA Link is in flow-control state. || /adapter/m2ua/sap/cluster/link
|-
| remote_proc_outage || M2UA Link is in remote processor outage state. || /adapter/m2ua/sap/cluster/link
|-
| rx_pdu || Nb of PDUs received. || /adapter/m2ua/sap/cluster/link
|-
| tx_pdu || Nb of PDUs transmitted. || /adapter/m2ua/sap/cluster/link
|-
| up_cnt || Number of m2ua links in 'up' state. || /system/m2ua_links
|-
| down_cnt || Number of m2ua links in 'down' state. || /system/m2ua_links
|-
| configured || Is M2UA PEER configured. || /adapter/m2ua/sap/cluster/peer
|-
| peer_state || Peer state. || /adapter/m2ua/sap/cluster/peer
|-
| tx_error || Nb of Tx errors. || /adapter/m2ua/sap/cluster/peer
|-
| rx_error || Nb of Rx errors. || /adapter/m2ua/sap/cluster/peer
|-
| configured_cnt || Number of m2ua peers in 'configured' state. || /system/m2ua_peers
|-
| unconfigured_cnt || Number of m2ua peers in 'unconfigured' state. || /system/m2ua_peers
|-
| configured || Is M2UA SAP configured. || /adapter/m2ua/sap
|-
| opened || Is M2UA SAP opened. || /adapter/m2ua/sap
|-
| rx_pdu || Nb of PDUs received. || /adapter/m2ua/sap
|-
| tx_pdu || Nb of PDUs transmitted. || /adapter/m2ua/sap
|-
| configured_cnt || Number of m2ua sap in 'configured' state. || /system/m2ua_saps
|-
| unconfigured_cnt || Number of m2ua sap in 'unconfigured' state. || /system/m2ua_saps
|-
| endpoint_opened_cnt || Number of m2ua sap with endpoints opened. || /system/m2ua_saps
|-
| endpoint_closed_cnt || Number of m2ua sap with endpoints closed. || /system/m2ua_saps
|-
| rowspan="47" valign="top" | M3UA
| lower_interface_rx_pdu || Nb of lower interface PDUs received. || /m3ua
|-
| lower_interface_tx_pdu || Nb of lower interface PDUs transmitted. || /m3ua
|-
| upper_interface_rx_pdu || Nb of upper interface PDUs received. || /m3ua
|-
| upper_interface_tx_pdu || Nb of upper interface PDUs transmitted. || /m3ua
|-
| configured || Is M3UA PSP configured. || /m3ua/psp
|-
| states_available_for_endpoint_ || Is states available. || /m3ua/psp
|-
| current_psp_inhibit_state || Current Psp inhibit state. || /m3ua/psp
|-
| association_state || Association state. || /m3ua/psp
|-
| nb_active_psrv || Nb of active peer server. || /m3ua/psp
|-
| nb_registered_psrv || Nb of registered peer server. || /m3ua/psp
|-
| asp_state || Asp state. || /m3ua/psp
|-
| rx_pdu || Nb of PDUs received. || /m3ua/psp
|-
| tx_pdu || Nb of PDUs transmitted. || /m3ua/psp
|-
| unavailable || Nb of times association was unavailable. || /m3ua/psp
|-
| congested || Nb of times association was congested. || /m3ua/psp
|-
| error_counter_for_endpoint || Error counter for endpoint. || /m3ua/psp
|-
| asp_active_cnt || Number of m3ua asp in 'active' state. || /system/m3ua_psps
|-
| asp_inactive_cnt || Number of m3ua asp in 'inactive' state. || /system/m3ua_psps
|-
| asp_down_cnt || Number of m3ua asp in 'down' state. || /system/m3ua_psps
|-
| configured || Is M3UA PSRV configured. || /m3ua/psrv
|-
| as_state || As state. || /m3ua/psrv
|-
| states_for_endpoint_ || States for endpoint. || /m3ua/psrv
|-
| nb_active_psp || Nb of active PSP. || /m3ua/psrv
|-
| asp_state_ || Asp state. || /m3ua/psrv
|-
| unavailable || Nb of times peer server was unavailable || /m3ua/psrv
|-
| as_active_cnt || Number of m3ua as in 'active' state. || /system/m3ua_psrvs
|-
| as_inactive_cnt || Number of m3ua as in 'inactive' state. || /system/m3ua_psrvs
|-
| as_down_cnt || Number of m3ua as in 'down' state. || /system/m3ua_psrvs
|-
| paused || Is the DPC in pause state. || /m3ua/route
|-
| congested || Is the DPC in congestion state. || /m3ua/route
|-
| unpaused_cnt || Number of m3ua DPC that is not in pause state. || /system/m3ua_routes
|-
| paused_cnt || Number of m3ua DPC in pause state. || /system/m3ua_routes
|-
| uncongested_cnt || Number of m3ua DPC that is not in congestion state. || /system/m3ua_routes
|-
| congested_cnt || Number of m3ua DPC in congestion state. || /system/m3ua_routes
|-
| configured || Is M3UA SAP configured. || /m3ua/sap
|-
| opened || Is M3UA SAP opened. || /m3ua/sap
|-
| rx_pdu || Nb of PDUs received. || /m3ua/sap
|-
| tx_pdu || Nb of PDUs transmitted. || /m3ua/sap
|-
| configured_cnt || Number of m3ua sap in 'configured' state. || /system/m3ua_saps
|-
| unconfigured_cnt || Number of m3ua sap in 'unconfigured' state. || /system/m3ua_saps
|-
| endpoint_opened_cnt || Number of m3ua sap with endpoints opened. || /system/m3ua_saps
|-
| endpoint_closed_cnt || Number of m3ua sap with endpoints closed. || /system/m3ua_saps
|-
| configured || Is M3UA USERPART configured. || /m3ua/userpart
|-
| rx_pdu || Nb of PDUs received. || /m3ua/userpart
|-
| tx_pdu || Nb of PDUs transmitted. || /m3ua/userpart
|-
| configured_cnt || Number of m3ua userpart in 'configured' state. || /system/m3ua_userparts
|-
| unconfigured_cnt || Number of m3ua userpart in 'unconfigured' state. || /system/m3ua_userparts
|-
| rowspan="14" valign="top" | MTP2
| up || Link is Up or Down. || /adapter/mtp2_link
|-
| aligned || Link is aligned or not. || /adapter/mtp2_link
|-
| flow_control || Local congestion flag from MTP2. || /adapter/mtp2_link
|-
| remote_congested || Remote congestion flag. || /adapter/mtp2_link
|-
| dropped_frame_cnt || Number of frame dropped by the layer 1. || /adapter/mtp2_link
|-
| remote_processor_outage || Remote processor outage flag. || /adapter/mtp2_link
|-
| datalink_state || Current datalink state. || /adapter/mtp2_link
|-
| rx_current_bandwidth || Bytes received in the last second. || /adapter/mtp2_link
|-
| tx_current_bandwidth || Bytes transmitted in the last second. || /adapter/mtp2_link
|-
| mtp2_hdlc_statistic_struct || Detailed MTP2 HDLC Statistics. || /adapter/mtp2_link
|-
| frames_to_stack_cnt || Number of HDLC frames sent toward a stack. || /adapter/mtp2_link
|-
| frames_from_stack_cnt || Number of HDLC frames received from a stack. || /adapter/mtp2_link
|-
| up_cnt || Number of mtp2 links in 'up' state. || /system/mtp2_links
|-
| down_cnt || Number of mtp2 links in 'down' state. || /system/mtp2_links
|-
| rowspan="18" valign="top" | MTP3
| msu_drop_for_routing_err_cnt || Number of message dropped because of no route to destination. || /mtp3
|-
| link_state || Current link state. || /mtp3/link
|-
| current_locally_inhibit_state || Whether or not the link is currently locally inhibited. || /mtp3/link
|-
| remotely_inhibited || Whether or not the link is remotely inhibited. || /mtp3/link
|-
| locally_blocked || Whether or not the link is locally blocked. || /mtp3/link
|-
| remotely_blocked || Whether or not the link is remotely blocked. || /mtp3/link
|-
| congested || Whether or not the link is in congestion state. || /mtp3/link
|-
| emergency_indication || Whether or not we are in emergency condition. || /mtp3/link
|-
| rx_invalid_pdu_cnt || Number of invalid PDU received. || /mtp3/link
|-
| up_cnt || Number of mtp3 links in 'up' state. || /system/mtp3_links
|-
| down_cnt || Number of mtp3 links in 'down' state. || /system/mtp3_links
|-
| blocked_cnt || Number of mtp3 links in 'blocked' state. || /system/mtp3_links
|-
| congested_cnt || Number of mtp3 links in 'congested' state. || /system/mtp3_links
|-
| inhibited_cnt || Number of mtp3 links in 'inhibited' conditions. || /system/mtp3_links
|-
| current_linkset_state || Current state of the linkset. || /mtp3/route/linkset
|-
| failure_cnt || Number of linkset failure declarations. || /mtp3/route/linkset
|-
| active_cnt || Number of active Mtp3 linksets. || /system/mtp3_linksets
|-
| inactive_cnt || Number of inactive Mtp3 linksets. || /system/mtp3_linksets
|-
| rowspan="22" valign="top" | SCCP
| primary_state || State of Sccp stack on pimary unit. || /sccp
|-
| secondary_state || State of Sccp stack on secondary unit. || /sccp
|-
| msg_hand_cnt || Total messages handled. || /sccp
|-
| msg_tx_c0_cnt || Total messages sent, class 0. || /sccp
|-
| msg_tx_c1_cnt || Total messages sent, class 1. || /sccp
|-
| msg_rx_c0_cnt || Total messages received, class 0. || /sccp
|-
| msg_rx_c1_cnt || Total messages received, class 1. || /sccp
|-
| active_cnt || Number of sccp layers in active state. || /system/sccps
|-
| standby_cnt || Number of sccp layers in standby state. || /system/sccps
|-
| oos_cnt || Number of sccp layers in Out Of Service state. || /system/sccps
|-
| dpc_state || DPC state. || /sccp/network/route
|-
| remote_state || Remote SCCP state. || /sccp/network/route
|-
| smi_state || Subsystem multiplicity indicator state. || /sccp/network/route
|-
| ssn_state ||Subsystem state. || /sccp/network/route
|-
| pc_available_cnt || Number of route in 'available' state. || /system/sccp_routes
|-
| pc_inaccessible_cnt || Number of route in 'inaccessible' state. || /system/sccp_routes
|-
| pc_congested_cnt || Number of route in 'congested' state. || /system/sccp_routes
|-
| msg_tx_bss_cnt || count of messages sent to backup subsystem. || /sccp/network/userpart
|-
| msg_tx_class_0_cnt || count of class 0 messages sent. || /sccp/network/userpart
|-
| msg_tx_class_1_cnt || count of class 1 messages sent. || /sccp/network/userpart
|-
| msg_rx_class_0_cnt || count of class 0 messages received. || /sccp/network/userpart
|-
| msg_rx_class_1_cnt || count of class 1 messages received. || /sccp/network/userpart
|-
| rowspan="5" valign="top" | TCAP
| primary_state || State of Tcap stack on pimary unit. || /tcap/userpart
|-
| secondary_state || State of Tcap stack on secondary unit. || /tcap/userpart
|-
| active_cnt || Number of tcap layers in active state. || /system/tcaps
|-
| standby_cnt || Number of tcap layers in standby state. || /system/tcaps
|-
| oos_cnt || Number of tcap layers in Out Of Service state. || /system/tcaps
|-
| rowspan="25" valign="top" | Media Server
| current_active_play_file_output || Current number of active 'play file' channels outputs merged playbacks counting as 1. || /mediaserver
|-
| total_play_file || Total cumulative number of 'play file' channels. || /mediaserver
|-
| current_active_record || Current number of recording channels. || /mediaserver
|-
| total_record || Total cumulative number of record channels. || /mediaserver
|-
| disk_read_total || Total cumulative number of disk read operations. || /mediaserver
|-
| disk_read_latency_avg || Average disk read latency. || /mediaserver
|-
| disk_write_total || Total cumulative number of disk write operations. || /mediaserver
|-
| pending_chunk_read || Current number of pending chunk read operations. || /mediaserver
|-
| pending_chunk_read_remote || Current number of pending remote server chunk read from local cache or downloading. || /mediaserver
|-
| pending_chunk_write || Current number of pending disk write operations. || /mediaserver
|-
| disk_read_errors_total || Total cumulative number of disk read operations that failed. || /mediaserver
|-
| disk_write_errors_total || Total cumulative number of disk write operations that failed disk full?. || /mediaserver
|-
| remote_chunk_download_total || Total cumulative number of remote file chunk download from server. || /mediaserver
|-
| remote_chunk_from_cache_total || Total cumulative number of remote file chunk returned from local cache. || /mediaserver
|-
| remote_chunk_latency_avg || Average latency when querying remote file chunks combined from cache and downloaded. || /mediaserver
|-
| remote_chunk_download_error || Total cumulative number of errors downloading remote file chunks from server. || /mediaserver
|-
| tx_data_kb_total || Total cumulative Tx network traffic, in KB kilobyte. || /mediaserver
|-
| tx_skipped_packet_total || Total cumulative skipped tx packets tx queue overflow || /mediaserver
|-
| tx_transcoding_late_packet_total || Total cumulative skipped tx packets transcoding too slow || /mediaserver
|-
| tx_no_subnet_packet_total || Total cumulative kipped tx packets target IP does not match local subnets || /mediaserver
|-
| rx_data_kb_total || Total cumulative Rx network traffic, in KB kilobyte. || /mediaserver
|-
| rx_skipped_packet_total || Total cumulative number of skipped Rx packets rx buffer overflow, lack of CPU power. || /mediaserver
|-
| rx_seq_err_total || Total cumulative number of Rx sequence number errors packet loss on network. || /mediaserver
|-
| rx_ignored_seq_err_total || Total cumulative number of Rx sequence number errors on non-recorded packets. || /mediaserver
|-
| current_ram_usage || Current RAM usage of the media server application, in megabytes. || /mediaserver
|}

Toolpack:Loggable Statistics C

2018-06-18T18:49:17Z

Nicole Tan: Created the new page

=== '''''Applies to version(s): v2.10, v3.0.''''' ===
{{DISPLAYTITLE:Loggable Statistics}}

Here is a list of the most useful loggable statistic items.

{| class='wikitable'
|-
! width="100" | Type
! Statistic
! Description
! Path
|-
| rowspan="1" valign="top" | Calls
| active_call_cnt || Number of active calls. || /system/calls
|-
| rowspan="8" valign="top" | Lawful Intercept
| total_interception_call_legs_failed || Total number of interception call legs that failed to provide audio to Law agencies || /intercept
|-
| total_iri_record_files_dropped || Total number of IRI record files dropped upload queue overflow || /intercept
|-
| total_iri_server_connection_failure || Total number of failed connection attempts to the IRI upload server || /intercept
|-
| curr_intercepted_calls || Current number of intercepted calls || /intercept
|-
| total_intercepted_calls || Total number of intercepted calls || /intercept
|-
| total_iri_records || Total number of generated IRI records || /intercept
|-
| curr_iri_record_files_queued || Current number of queued IRI record files pending for upload || /intercept
|-
| curr_iri_record_files_queue_state || Current IRI record files upload queue state || /intercept
|-
| rowspan="10" valign="top" | RADIUS
| acct_queued_records || Current number of queued accounting records waiting to be sent || /radius
|-
| acct_success_record_cnt || Number of accounting records that were successfully sent and acknowledged || /system/radius
|-
| acct_lost_record_cnt || Number of accounting records that were lost either because they didn't fit in a queue or no servers responsed to them || /system/radius
|-
| auth_queued || Current number of queued authorizations waiting to be sent || /radius
|-
| auth_success_cnt || Number of authorizations that were successfully sent and acknowledged || /system/radius
|-
| auth_lost_cnt || Number of authorizations that were lost either because they didn't fit in a queue or no servers responsed to them || /system/radius
|-
| state || RADIUS server activity state current, active or inactive || /radius/server
|-
| availability || RADIUS server availabilty the last time it was used: up, down or unknown not yet used || /radius/server
|-
| acct_all_servers_down || When this is set, this means the RADIUS client was unable to exchange data with any of the provided RADIUS accounting servers. || /radius/server
|-
| auth_all_servers_down || When this is set, this means the RADIUS client was unable to exchange data with any of the provided RADIUS authorization servers. || /radius/server
|-
| rowspan="23" valign="top" | System
| active_configuration || Active Toolpack configuration. || /system
|-
| active_package || Active Toolpack package. || /system
|-
| oam_target_state || OAM target state for the application. || /host/application
|-
| fault_cnt || Number of faulty applications. || /system/host_applications
|-
| up || Tells if the database is up. || /database
|-
| valid || Tells if the database is valid. || /database
|-
| nb_files || Current number of files under this folder. || /host/folder_cleanup
|-
| nb_files_percent || Current percent ratio between number of files and maximum under this folder. || /host/folder_cleanup
|-
| files_size || Current total size in MB of files under this folder. || /host/folder_cleanup
|-
| files_size_percent || Current percent ratio between total files size and maximum under this folder. || /host/folder_cleanup
|-
| nb_deleted_files || Number of files deleted from this folder. || /host/folder_cleanup
|-
| oam_mode || Toolpack OAM mode. || /host
|-
| oam_state || Toolpack OAM state. || /host
|-
| not_ready_cnt || Number of hosts that are not ready in the system. || /system/hosts
|-
| percentage || Percentage of cpu used on host. || /host/pm
|-
| disk_full || Disk full. || /host/pm/file_system
|-
| free_space || Available filesytem space in KB. || /host/pm/file_system
|-
| disk_full_cnt || Number of hosts on which the disk is full. || /system/filesystems
|-
| sent_error_bytes_total || Total bytes with error sent by this network adapter || /host/pm/network
|-
| percentage || Percentage of RAM used on host. || /host/pm/ram
|-
| swap_used_total || Total Swap used on host || /host/pm/ram
|-
| host_virtual_interface_state || Current state of the virtual interface on the host. || /system_virtual_ip_interface
|-
| not_ready_cnt || Number of system virtual interfaces that are not ready in the system. || /system/system_virtual_ip_interfaces
|-
| rowspan="1" valign="top" | Mixer
| count || Number of mixer in the system. || /mixer
|-
| rowspan="20" valign="top" | Nap
| Call congestion || Indicate if NAP is considered locally congested (too many calls dropped due to local congestion in the last period). || /nap
|-
| Call congestion period dropped calls || Instantaneous Count of incoming calls. || /nap
|-
| Firewall blocked || Indicate if NAP is actually blocked (banned) by the firewall (due to bandwidth or packets/s threshold passed) . || /nap
|-
| Firewall blocked cnt || Number of times this NAP has been blocked (banned) by the firewall. || /nap
|-
| inst_incoming_call_cnt || Instantaneous Count of incoming calls. || /nap
|-
| Inst incoming call cnt highest || Highest Instantaneous Count of incoming calls. || /nap
|-
| Inst incoming call cnt in progress || Instantaneous count of incoming in-progress calls (waiting to be answered). || /nap
|-
| Inst incoming call cnt answered || Instantaneous count of incoming answered calls. || /nap
|-
| Inst incoming call cnt terminating|| Instantaneous count of incoming terminating calls. || /nap
|-
| Inst incoming call rate|| Current incoming call rate (calls per second). || /nap
|-
| Inst incoming call rate highest|| Highest incoming call rate (calls per second). || /nap
|-
| Inst incoming call rate answered|| Current incoming answered call rate (calls per second). || /nap
|-
| Inst incoming call rate answered highest|| Highest incoming answered call rate (calls per second). || /nap
|-

| inst_outgoing_call_cnt || Instantaneous Count of outgoing calls. || /nap
|-
| available_cnt || Number of available circuits or channels. || /nap
|-
| unavailable_cnt || Number of unavailable circuits or channels. || /nap
|-
| availability_percent || Percentage of available circuits or channels. || /nap
|-
| usage_percent || Percentage of used circuits or channels. || /nap
|-
| unused_shared_percent || Percentage of used circuits or channels of this NAP available to make new calls with. This takes into account resources shared with other NAPs (in SIP case, when multiple NAPs use SIP stack or VOIP resources on the same adapters). || /nap
|-
| asr_stats_incoming_struct || Detailed Answer/Seizure Ratio Statistics for incoming calls. || /nap
|-
| global_asr_percent || Global calculated ASR percentage for incoming calls. || /nap
|-
| total_call_cnt || Total cumulative count of incoming calls. || /nap
|-
| total_answered_call_cnt || Total cumulative count of incoming answered calls. || /nap
|-
| current_hour_asr_percent || Calculated ASR percentage in the current hour for incoming calls || /nap
|-
| asr_stats_outgoing_struct || Detailed Answer/Seizure Ratio Statistics for outgoing calls. || /nap
|-
| global_asr_percent || Global calculated ASR percentage for outgoing calls. || /nap
|-
| total_call_cnt || Total cumulative count of outgoing calls. || /nap
|-
| total_answered_call_cnt || Total cumulative count of outgoing answered calls. || /nap
|-
| is_available || Remote proxy actually available or not || /nap
|-
| to_net_nb_arp_failures || Number of ARP failures while trying to send packets to the VOIP network || /nap
|-
| available_nap_cnt || Number of available NAP. || /system/naps
|-
| partially_available_nap_cnt || Number of partially available NAP. || /system/naps
|-
| unavailable_nap_cnt || Number of unavailable NAP. || /system/naps
|-
| rowspan="18" valign="top" | Hardware Units
| oam_target_state || OAM target state: Enabled, Maintenance not used for now, replaced by it's backup, Disabled not used, not replaced by it's backup || /adapter
|-
| oam_target_update_state || OAM target update state for the unit used by OAM system when it requires to update this unit to a new version. || /adapter
|-
| oam_current_state || OAM current state of the unit. || /adapter
|-
| configuration_state || Current configuration state of this unit. || /adapter
|-
| cpu_usage || Current CPU usage of that unit. || /adapter
|-
| absolute_reboot_cnt || Nb of times the unit rebooted since begining of time. || /adapter
|-
| firmware_version || Current version of the unit's firmware. || /adapter
|-
| fault_cnt || Number of units in fault invalid configuration?. || /system/adapters
|-
| down_cnt || Number of units having lost communication with the system. || /system/adapters
|-
| license_expired_cnt || Number of units having an expired license. || /system/adapters
|-
| value_integer || Integer portion of the sensor value. || /adapter/sensor
|-
| cpu_0_usage || Unit's current CPU 0 usage in percent. || /adapter/usage
|-
| cpu_1_usage || Unit's current CPU 1 usage in percent. || /adapter/usage
|-
| dsp_usage || Unit's current DSP usage in percent. || /adapter/usage
|-
| voip_usage || Unit's current VOIP usage in percent. || /adapter/usage
|-
| high_cpu_usage_cnt || Number of adapters with high CPU usage > 90% usage. || /system/adapters_usage
|-
| high_dsp_usage_cnt || Number of adapters with high DSP usage > 90% of capacity. || /system/adapters_usage
|-
| high_voip_usage_cnt || Number of adapters with high VOIP usage > 90% of capacity. || /system/adapters_usage
|-
| rowspan="1" valign="top" | BITS port
| down_cnt || Number of down bits ports. || /system/bits
|-
| rowspan="4" valign="top" | CAS
| signaling_up || Whether or not the state is up. || /adapter/casr2
|-
| down_cnt || Number of CASR2 stack with physical line or signaling down. || /system/casr2_stacks
|-
| idle_cnt || Number of idle circuits. || /adapter/casr2/circuit_group
|-
| down_cnt || Number of circuits in down state. || /adapter/casr2/circuit_group
|-
| rowspan="3" valign="top" | TDM clocking
| clk_src_type || Clock source type. || /adapter/clock
|-
| clk_ref_grade || Clock reference grade. || /clock/ref
|-
| clk_ref_active || Clock reference active. || /clock/ref
|-
| rowspan="8" valign="top" | IP interfaces
| rx_bandwidth_pct || Current Rx bandwidth on this interface in percent of link capacity. || /adapter/ip_interface
|-
| tx_bandwidth_pct || Current Tx bandwidth on this interface in percent of link capacity. || /adapter/ip_interface
|-
| bad_frames_received || The number of bad ethernet frames received. || /adapter/ip_interface
|-
| packets_received || Total number of packets received. || /adapter/ip_interface
|-
| packets_sent || Total number of packets transmitted or attempted to transmit. || /adapter/ip_interface
|-
| link_up || Ethernet link status. || /adapter/ip_interface
|-
| up_cnt || Number of up ip interfaces. || /system/ip_interfaces
|-
| down_cnt || Number of down ip interfaces. || /system/ip_interfaces
|-
| rowspan="8" valign="top" | ISDN
| d_channel_up || Whether or not the state is up. || /adapter/isdn
|-
| nb_d_channel_up_events || Number of D-Channel UP events received || /adapter/isdn
|-
| Call || Call statistics || /adapter/isdn
|-
| nb_initiated_incoming || Number of incoming calls || /adapter/isdn
|-
| nb_initiated_outgoing || Number of outgoing calls || /adapter/isdn
|-
| up_cnt || Number of ISDN stack with D channel up. || /system/isdn_stacks
|-
| down_cnt || Number of ISDN stack with D channel down. || /system/isdn_stacks
|-
| not_configured || No elements configured in the system. || /system/isdn_stacks
|-
| rowspan="15" valign="top" | IUA
| up || IUA Link is Up or Down. || /adapter/iua/sap/cluster/link
|-
| flow_control || IUA Link is in flow-control state. || /adapter/iua/sap/cluster/link
|-
| rx_pdu || Nb of PDUs received. || /adapter/iua/sap/cluster/link
|-
| tx_pdu || Nb of PDUs transmitted. || /adapter/iua/sap/cluster/link
|-
| up_cnt || Number of iua links in 'up' state. || /system/iua_links
|-
| down_cnt || Number of iua links in 'down' state. || /system/iua_links
|-
| peer_state || Peer state. || /adapter/iua/sap/cluster/peer
|-
| inhibited || Inhibited by management. || /adapter/iua/sap/cluster/peer
|-
| active_cnt || Number of iua peers in 'active' state. || /system/iua_peers
|-
| down_cnt || Number of iua peers in 'down' state. || /system/iua_peers
|-
| opened || Is IUA SAP opened. || /adapter/iua/sap
|-
| configured_cnt || Number of IUA sap in 'configured' state. || /system/iua_saps
|-
| unconfigured_cnt || Number of IUA sap in 'unconfigured' state. || /system/iua_saps
|-
| endpoint_opened_cnt || Number of IUA sap with endpoints opened. || /system/iua_saps
|-
| endpoint_closed_cnt || Number of IUA sap with endpoints closed. || /system/iua_saps
|-
| rowspan="5" valign="top" | LAPD
| up || Link is Up or Down. || /adapter/lapd_link
|-
| active_sap_cnt || Number of active SAP. || /adapter/lapd_link
|-
| data_link_conection_cnt || Number of data link connections. || /adapter/lapd_link
|-
| up_cnt || Number of lapd links in 'up' state. || /system/lapd_links
|-
| down_cnt || Number of lapd links in 'down' state. || /system/lapd_links
|-
| rowspan="21" valign="top" | Line Interfaces
| state || Line state. || /adapter/line_interface
|-
| alarm_count || Cumulative count of raised alarms LOS || /adapter/line_interface
|-
| anomaly_count || Cumulative count of all anomalies detected rsp, cvc, etc.... || /adapter/line_interface
|-
| loopback || Line loopback identifier. || /adapter/line_interface
|-
| state || Line state. || /adapter/line_interface
|-
| alarm_count || Cumulative count of raised alarms LOS || /adapter/line_interface
|-
| anomaly_count || Cumulative count of all anomalies detected rsp, cvc, etc.... || /adapter/line_interface
|-
| loopback || Line loopback identifier. || /adapter/line_interface
|-
| tx_state || The line interface transmitter. || /adapter/line_interface
|-
| state || Line state. || /adapter/line_interface
|-
| alarm_count || Cumulative count of raised alarms LOS || /adapter/line_interface
|-
| anomaly_count || Cumulative count of all anomalies detected rsp, cvc, etc.... || /adapter/line_interface
|-
| protection_activated || Whether or not a protection-switch is currently under way. || /adapter/line_interface
|-
| tx_state || The line interface transmitter. || /adapter/line_interface
|-
| loopback || Line loopback identifier. || /adapter/line_interface
|-
| up_cnt || Number of up lines. || /system/line_interfaces
|-
| down_cnt || Number of down lines. || /system/line_interfaces
|-
| alarm_cnt || Number of lines with alarms. || /system/line_interfaces
|-
| defect_cnt || Number of lines with defects. || /system/line_interfaces
|-
| available_trunk_cnt || Number of available line services ready to make TDM calls with. || /system/line_services_leaf
|-
| unavailable_trunk_cnt || Number of unavailable line services not ready to make TDM calls with. || /system/line_services_leaf
|-
| rowspan="6" valign="top" | TMS
| tms0_link_active || Tells if link A is active. || /adapter/mbl_port
|-
| tms1_link_active || Tells if link B is active. || /adapter/mbl_port
|-
| tmp_no_alarm_cnt || Number of unit TMS ports without alarms. || /system/mbl_ports
|-
| tmp_alarm_cnt || Number of unit TMS ports with alarms. || /system/mbl_ports
|-
| tms_no_alarm_cnt || Number of TMS switch ports without alarms. || /system/mbl_ports
|-
| tms_alarm_cnt || Number of TMS switch ports with alarms. || /system/mbl_ports
|-
| rowspan="17" valign="top" | SCTP
| path_active || Is PATH active. || /adapter/sctp_sap
|-
| flow_control || Local congestion flag from SCTP. || /adapter/sctp_sap
|-
| rx_byte || Nb of bytes received. || /adapter/sctp_sap
|-
| tx_byte || Nb of bytes transmitted. || /adapter/sctp_sap
|-
| configured_cnt || Number of sctp sap in 'configured' state. || /system/sctp_sap
|-
| unconfigured_cnt || Number of sctp sap in 'unconfigured' state. || /system/sctp_sap
|-
| path_active_cnt || Number of sctp sap with active path. || /system/sctp_sap
|-
| path_inactive_cnt || Number of sctp sap with inactive path. || /system/sctp_sap
|-
| congested_cnt || Number of sctp sap congested. || /system/sctp_sap
|-
| configured || Is SCTP TSAP configured. || /adapter/sctp_tsap
|-
| tucl_failed || Is Tucl failed. || /adapter/sctp_tsap
|-
| rx_byte || Nb of bytes received. || /adapter/sctp_tsap
|-
| tx_byte || Nb of bytes transmitted. || /adapter/sctp_tsap
|-
| configured_cnt || Number of sctp tsap in 'configured' state. || /system/sctp_tsap
|-
| unconfigured_cnt || Number of sctp tsap in 'unconfigured' state. || /system/sctp_tsap
|-
| tucl_failed_cnt || Number of sctp tsap where tucl failed. || /system/sctp_tsap
|-
| tucl_not_failed_cnt || Number of sctp tsap where tucl did not failed.. || /system/sctp_tsap
|-
| rowspan="19" valign="top" | SIP
| request_in_cnt || Total number of SIP request messages received, including retransmissions. || /sip
|-
| request_out_cnt || Total number of SIP request messages sent out, including retransmissions. || /sip
|-
| response_in_cnt || Total number of SIP response messages received, including retransmissions. || /sip
|-
| response_out_cnt || Total number of SIP response messages sent out, including retransmissions. || /sip
|-
| request_retry_cnt || Total number of SIP request retransmissions sent. || /sip
|-
| response_retry_cnt || Total number of SIP response retransmissions sent. || /sip
|-
| congestion_period_cnt || Number of times the system came in memory congestion. || /sip
|-
| critical_congestion_period_cnt || Number of times the system came in critical memory congestion. || /sip
|-
| call_congestion_period_cnt || Number of times the system came in call congestion. || /sip
|-
| current_mem_status || Current memory status. || /sip
|-
| congestion_drop_from_network_cnt || Number of incoming network messages dropped due to congestion. || /sip
|-
| congestion_drop_from_user_cnt || Number of API messages dropped due to congestion. || /sip
|-
| current_active_call_cnt || Current number of activate calls answered calls that are not terminating. || /sip
|-
| current_transient_call_cnt || Current number of transient calls. || /sip
|-
| cfg_cnt || Number of sip configurations in the system. || /system/sips
|-
| not_configured || No elements configured in the system. || /system/sips
|-
| calls_tx_cnt || The number of calls initiated to the service provider for this SAP. || /sip/sap
|-
| calls_rx_cnt || The number of calls received from the service provider for this SAP. || /sip/sap
|-
| sap_cnt || Number of sip saps in the system. || /system/sip_saps
|-
| rowspan="20" valign="top" | ISUP
| interface_down || Circuit group's interface is down. || /isup/interface/cic_group
|-
| idle_cnt || Number of idle circuits. || /isup/interface/cic_group
|-
| reset_cnt || Number of circuits in reset state. || /isup/interface/cic_group
|-
| idle_cnt || Number of idle circuits. || /system/cic_groups
|-
| locally_blocked_cnt || Number of circuits in locally blocked state. || /system/cic_groups
|-
| remotely_blocked_cnt || Number of circuits in remotely blocked state. || /system/cic_groups
|-
| locally_remotely_blocked_cnt || Number of circuits in locally remotely blocked state. || |/system/cic_groups
|-
| down_cnt || Number of circuits with an interface down. || /system/cic_groups
|-
| reset_cnt || Number of circuits in reset state. || /system/cic_groups
|-
| primary_state || State of Isup stack on pimary unit. || /isup
|-
| secondary_state || State of Isup stack on secondary unit. || /isup
|-
| active_cnt || Number of isup layers in active state. || /system/isups
|-
| standby_cnt || Number of isup layers in standby state. || /system/isups
|-
| oos_cnt || Number of isup layers in Out Of Service state. || /system/isups
|-
| current_state || Interface current state. || /isup/interface
|-
| rx_message_cnt || Total number of received messages i.e. PDUs. || /isup/interface
|-
| tx_message_cnt || Total number of transmitted messages i.e. PDUs. || /isup/interface
|-
| available_cnt || Number of available isup interfaces. || /system/isup_interfaces
|-
| unavailable_cnt || Number of unavailable isup interfaces. || /system/isup_interfaces
|-
| congested_cnt || Number of congested isup interfaces. || /system/isup_interfaces
|-
| rowspan="16" valign="top" | M2PA
| up || Is link Up. || /adapter/m2pa/link
|-
| current_link_disabled || Is link disabled by management. || /adapter/m2pa/link
|-
| rx_msu || Nb of MSUs received. || /adapter/m2pa/link
|-
| tx_msu || Nb of MSUs transmitted. || /adapter/m2pa/link
|-
| rx_current_bandwidth || Bytes received in the last second. || /adapter/m2pa/link
|-
| tx_current_bandwidth || Bytes transmitted in the last second. || /adapter/m2pa/link
|-
| up_cnt || Number of m2pa links in 'up' state. || /system/m2pa_links
|-
| down_cnt || Number of m2pa links in 'down' state. || /system/m2pa_links
|-
| sap_configured || Is M2PA SAP configured. || /adapter/m2pa/sap
|-
| endpoint_opened || Is endpoint opened. || /adapter/m2pa/sap
|-
| rx_pdu || Nb of PDUs received. || /adapter/m2pa/sap
|-
| tx_pdu || Nb of PDUs transmitted. || /adapter/m2pa/sap
|-
| configured_cnt || Number of m2pa sap in 'configured' state. || /system/m2pa_saps
|-
| unconfigured_cnt || Number of m2pa sap in 'unconfigured' state. || /system/m2pa_saps
|-
| endpoint_opened_cnt || Number of m2pa sap with endpoints opened. || /system/m2pa_saps
|-
| endpoint_closed_cnt || Number of m2pa sap with endpoints closed. || /system/m2pa_saps
|-
| rowspan="21" valign="top" | M2UA
| up || M2UA Link is Up or Down. || /adapter/m2ua/sap/cluster/link
|-
| flow_control || M2UA Link is in flow-control state. || /adapter/m2ua/sap/cluster/link
|-
| remote_proc_outage || M2UA Link is in remote processor outage state. || /adapter/m2ua/sap/cluster/link
|-
| rx_pdu || Nb of PDUs received. || /adapter/m2ua/sap/cluster/link
|-
| tx_pdu || Nb of PDUs transmitted. || /adapter/m2ua/sap/cluster/link
|-
| up_cnt || Number of m2ua links in 'up' state. || /system/m2ua_links
|-
| down_cnt || Number of m2ua links in 'down' state. || /system/m2ua_links
|-
| configured || Is M2UA PEER configured. || /adapter/m2ua/sap/cluster/peer
|-
| peer_state || Peer state. || /adapter/m2ua/sap/cluster/peer
|-
| tx_error || Nb of Tx errors. || /adapter/m2ua/sap/cluster/peer
|-
| rx_error || Nb of Rx errors. || /adapter/m2ua/sap/cluster/peer
|-
| configured_cnt || Number of m2ua peers in 'configured' state. || /system/m2ua_peers
|-
| unconfigured_cnt || Number of m2ua peers in 'unconfigured' state. || /system/m2ua_peers
|-
| configured || Is M2UA SAP configured. || /adapter/m2ua/sap
|-
| opened || Is M2UA SAP opened. || /adapter/m2ua/sap
|-
| rx_pdu || Nb of PDUs received. || /adapter/m2ua/sap
|-
| tx_pdu || Nb of PDUs transmitted. || /adapter/m2ua/sap
|-
| configured_cnt || Number of m2ua sap in 'configured' state. || /system/m2ua_saps
|-
| unconfigured_cnt || Number of m2ua sap in 'unconfigured' state. || /system/m2ua_saps
|-
| endpoint_opened_cnt || Number of m2ua sap with endpoints opened. || /system/m2ua_saps
|-
| endpoint_closed_cnt || Number of m2ua sap with endpoints closed. || /system/m2ua_saps
|-
| rowspan="47" valign="top" | M3UA
| lower_interface_rx_pdu || Nb of lower interface PDUs received. || /m3ua
|-
| lower_interface_tx_pdu || Nb of lower interface PDUs transmitted. || /m3ua
|-
| upper_interface_rx_pdu || Nb of upper interface PDUs received. || /m3ua
|-
| upper_interface_tx_pdu || Nb of upper interface PDUs transmitted. || /m3ua
|-
| configured || Is M3UA PSP configured. || /m3ua/psp
|-
| states_available_for_endpoint_ || Is states available. || /m3ua/psp
|-
| current_psp_inhibit_state || Current Psp inhibit state. || /m3ua/psp
|-
| association_state || Association state. || /m3ua/psp
|-
| nb_active_psrv || Nb of active peer server. || /m3ua/psp
|-
| nb_registered_psrv || Nb of registered peer server. || /m3ua/psp
|-
| asp_state || Asp state. || /m3ua/psp
|-
| rx_pdu || Nb of PDUs received. || /m3ua/psp
|-
| tx_pdu || Nb of PDUs transmitted. || /m3ua/psp
|-
| unavailable || Nb of times association was unavailable. || /m3ua/psp
|-
| congested || Nb of times association was congested. || /m3ua/psp
|-
| error_counter_for_endpoint || Error counter for endpoint. || /m3ua/psp
|-
| asp_active_cnt || Number of m3ua asp in 'active' state. || /system/m3ua_psps
|-
| asp_inactive_cnt || Number of m3ua asp in 'inactive' state. || /system/m3ua_psps
|-
| asp_down_cnt || Number of m3ua asp in 'down' state. || /system/m3ua_psps
|-
| configured || Is M3UA PSRV configured. || /m3ua/psrv
|-
| as_state || As state. || /m3ua/psrv
|-
| states_for_endpoint_ || States for endpoint. || /m3ua/psrv
|-
| nb_active_psp || Nb of active PSP. || /m3ua/psrv
|-
| asp_state_ || Asp state. || /m3ua/psrv
|-
| unavailable || Nb of times peer server was unavailable || /m3ua/psrv
|-
| as_active_cnt || Number of m3ua as in 'active' state. || /system/m3ua_psrvs
|-
| as_inactive_cnt || Number of m3ua as in 'inactive' state. || /system/m3ua_psrvs
|-
| as_down_cnt || Number of m3ua as in 'down' state. || /system/m3ua_psrvs
|-
| paused || Is the DPC in pause state. || /m3ua/route
|-
| congested || Is the DPC in congestion state. || /m3ua/route
|-
| unpaused_cnt || Number of m3ua DPC that is not in pause state. || /system/m3ua_routes
|-
| paused_cnt || Number of m3ua DPC in pause state. || /system/m3ua_routes
|-
| uncongested_cnt || Number of m3ua DPC that is not in congestion state. || /system/m3ua_routes
|-
| congested_cnt || Number of m3ua DPC in congestion state. || /system/m3ua_routes
|-
| configured || Is M3UA SAP configured. || /m3ua/sap
|-
| opened || Is M3UA SAP opened. || /m3ua/sap
|-
| rx_pdu || Nb of PDUs received. || /m3ua/sap
|-
| tx_pdu || Nb of PDUs transmitted. || /m3ua/sap
|-
| configured_cnt || Number of m3ua sap in 'configured' state. || /system/m3ua_saps
|-
| unconfigured_cnt || Number of m3ua sap in 'unconfigured' state. || /system/m3ua_saps
|-
| endpoint_opened_cnt || Number of m3ua sap with endpoints opened. || /system/m3ua_saps
|-
| endpoint_closed_cnt || Number of m3ua sap with endpoints closed. || /system/m3ua_saps
|-
| configured || Is M3UA USERPART configured. || /m3ua/userpart
|-
| rx_pdu || Nb of PDUs received. || /m3ua/userpart
|-
| tx_pdu || Nb of PDUs transmitted. || /m3ua/userpart
|-
| configured_cnt || Number of m3ua userpart in 'configured' state. || /system/m3ua_userparts
|-
| unconfigured_cnt || Number of m3ua userpart in 'unconfigured' state. || /system/m3ua_userparts
|-
| rowspan="14" valign="top" | MTP2
| up || Link is Up or Down. || /adapter/mtp2_link
|-
| aligned || Link is aligned or not. || /adapter/mtp2_link
|-
| flow_control || Local congestion flag from MTP2. || /adapter/mtp2_link
|-
| remote_congested || Remote congestion flag. || /adapter/mtp2_link
|-
| dropped_frame_cnt || Number of frame dropped by the layer 1. || /adapter/mtp2_link
|-
| remote_processor_outage || Remote processor outage flag. || /adapter/mtp2_link
|-
| datalink_state || Current datalink state. || /adapter/mtp2_link
|-
| rx_current_bandwidth || Bytes received in the last second. || /adapter/mtp2_link
|-
| tx_current_bandwidth || Bytes transmitted in the last second. || /adapter/mtp2_link
|-
| mtp2_hdlc_statistic_struct || Detailed MTP2 HDLC Statistics. || /adapter/mtp2_link
|-
| frames_to_stack_cnt || Number of HDLC frames sent toward a stack. || /adapter/mtp2_link
|-
| frames_from_stack_cnt || Number of HDLC frames received from a stack. || /adapter/mtp2_link
|-
| up_cnt || Number of mtp2 links in 'up' state. || /system/mtp2_links
|-
| down_cnt || Number of mtp2 links in 'down' state. || /system/mtp2_links
|-
| rowspan="18" valign="top" | MTP3
| msu_drop_for_routing_err_cnt || Number of message dropped because of no route to destination. || /mtp3
|-
| link_state || Current link state. || /mtp3/link
|-
| current_locally_inhibit_state || Whether or not the link is currently locally inhibited. || /mtp3/link
|-
| remotely_inhibited || Whether or not the link is remotely inhibited. || /mtp3/link
|-
| locally_blocked || Whether or not the link is locally blocked. || /mtp3/link
|-
| remotely_blocked || Whether or not the link is remotely blocked. || /mtp3/link
|-
| congested || Whether or not the link is in congestion state. || /mtp3/link
|-
| emergency_indication || Whether or not we are in emergency condition. || /mtp3/link
|-
| rx_invalid_pdu_cnt || Number of invalid PDU received. || /mtp3/link
|-
| up_cnt || Number of mtp3 links in 'up' state. || /system/mtp3_links
|-
| down_cnt || Number of mtp3 links in 'down' state. || /system/mtp3_links
|-
| blocked_cnt || Number of mtp3 links in 'blocked' state. || /system/mtp3_links
|-
| congested_cnt || Number of mtp3 links in 'congested' state. || /system/mtp3_links
|-
| inhibited_cnt || Number of mtp3 links in 'inhibited' conditions. || /system/mtp3_links
|-
| current_linkset_state || Current state of the linkset. || /mtp3/route/linkset
|-
| failure_cnt || Number of linkset failure declarations. || /mtp3/route/linkset
|-
| active_cnt || Number of active Mtp3 linksets. || /system/mtp3_linksets
|-
| inactive_cnt || Number of inactive Mtp3 linksets. || /system/mtp3_linksets
|-
| rowspan="22" valign="top" | SCCP
| primary_state || State of Sccp stack on pimary unit. || /sccp
|-
| secondary_state || State of Sccp stack on secondary unit. || /sccp
|-
| msg_hand_cnt || Total messages handled. || /sccp
|-
| msg_tx_c0_cnt || Total messages sent, class 0. || /sccp
|-
| msg_tx_c1_cnt || Total messages sent, class 1. || /sccp
|-
| msg_rx_c0_cnt || Total messages received, class 0. || /sccp
|-
| msg_rx_c1_cnt || Total messages received, class 1. || /sccp
|-
| active_cnt || Number of sccp layers in active state. || /system/sccps
|-
| standby_cnt || Number of sccp layers in standby state. || /system/sccps
|-
| oos_cnt || Number of sccp layers in Out Of Service state. || /system/sccps
|-
| dpc_state || DPC state. || /sccp/network/route
|-
| remote_state || Remote SCCP state. || /sccp/network/route
|-
| smi_state || Subsystem multiplicity indicator state. || /sccp/network/route
|-
| ssn_state ||Subsystem state. || /sccp/network/route
|-
| pc_available_cnt || Number of route in 'available' state. || /system/sccp_routes
|-
| pc_inaccessible_cnt || Number of route in 'inaccessible' state. || /system/sccp_routes
|-
| pc_congested_cnt || Number of route in 'congested' state. || /system/sccp_routes
|-
| msg_tx_bss_cnt || count of messages sent to backup subsystem. || /sccp/network/userpart
|-
| msg_tx_class_0_cnt || count of class 0 messages sent. || /sccp/network/userpart
|-
| msg_tx_class_1_cnt || count of class 1 messages sent. || /sccp/network/userpart
|-
| msg_rx_class_0_cnt || count of class 0 messages received. || /sccp/network/userpart
|-
| msg_rx_class_1_cnt || count of class 1 messages received. || /sccp/network/userpart
|-
| rowspan="5" valign="top" | TCAP
| primary_state || State of Tcap stack on pimary unit. || /tcap/userpart
|-
| secondary_state || State of Tcap stack on secondary unit. || /tcap/userpart
|-
| active_cnt || Number of tcap layers in active state. || /system/tcaps
|-
| standby_cnt || Number of tcap layers in standby state. || /system/tcaps
|-
| oos_cnt || Number of tcap layers in Out Of Service state. || /system/tcaps
|-
| rowspan="25" valign="top" | Media Server
| current_active_play_file_output || Current number of active 'play file' channels outputs merged playbacks counting as 1. || /mediaserver
|-
| total_play_file || Total cumulative number of 'play file' channels. || /mediaserver
|-
| current_active_record || Current number of recording channels. || /mediaserver
|-
| total_record || Total cumulative number of record channels. || /mediaserver
|-
| disk_read_total || Total cumulative number of disk read operations. || /mediaserver
|-
| disk_read_latency_avg || Average disk read latency. || /mediaserver
|-
| disk_write_total || Total cumulative number of disk write operations. || /mediaserver
|-
| pending_chunk_read || Current number of pending chunk read operations. || /mediaserver
|-
| pending_chunk_read_remote || Current number of pending remote server chunk read from local cache or downloading. || /mediaserver
|-
| pending_chunk_write || Current number of pending disk write operations. || /mediaserver
|-
| disk_read_errors_total || Total cumulative number of disk read operations that failed. || /mediaserver
|-
| disk_write_errors_total || Total cumulative number of disk write operations that failed disk full?. || /mediaserver
|-
| remote_chunk_download_total || Total cumulative number of remote file chunk download from server. || /mediaserver
|-
| remote_chunk_from_cache_total || Total cumulative number of remote file chunk returned from local cache. || /mediaserver
|-
| remote_chunk_latency_avg || Average latency when querying remote file chunks combined from cache and downloaded. || /mediaserver
|-
| remote_chunk_download_error || Total cumulative number of errors downloading remote file chunks from server. || /mediaserver
|-
| tx_data_kb_total || Total cumulative Tx network traffic, in KB kilobyte. || /mediaserver
|-
| tx_skipped_packet_total || Total cumulative skipped tx packets tx queue overflow || /mediaserver
|-
| tx_transcoding_late_packet_total || Total cumulative skipped tx packets transcoding too slow || /mediaserver
|-
| tx_no_subnet_packet_total || Total cumulative kipped tx packets target IP does not match local subnets || /mediaserver
|-
| rx_data_kb_total || Total cumulative Rx network traffic, in KB kilobyte. || /mediaserver
|-
| rx_skipped_packet_total || Total cumulative number of skipped Rx packets rx buffer overflow, lack of CPU power. || /mediaserver
|-
| rx_seq_err_total || Total cumulative number of Rx sequence number errors packet loss on network. || /mediaserver
|-
| rx_ignored_seq_err_total || Total cumulative number of Rx sequence number errors on non-recorded packets. || /mediaserver
|-
| current_ram_usage || Current RAM usage of the media server application, in megabytes. || /mediaserver
|}

How To Convert RTP into WAV file

2018-06-18T13:14:23Z

Nicole Tan: NT: adjusted the page

Sometimes we need to convert the RTP packets extracted from Wireshark into .wav file, so anyone can listen the call easily for troubleshooting audio issue.
Below describe the steps to convert the RTP streams into .wav audio file:

== Open the extracted SIP/RTP capture of the call you want to analyze with wireshark ==
=== Go to Telephony -> RTP -> RTP Streams ===

[[Image:Telephony_RTP_RTP Streams.png]]

=== Click “Analyze” button ===

[[Image:Analyze.png]]

=== Save it to “Unsynchronized Forward Stream Audio” ===

[[Image:Save.png]]

=== And Save as type: Raw ===

[[Image:Save_Raw.png]]

Now you have the rtp streams in raw format. You can use a free tool called Audacity to reformat it to .wav file

== Use Audacity to reformat it to .wav file ==
=== Import the raw data to Audacity ===

[[Image:Audacity_Import.png]]

=== Export it and change the encoding and Sample rate ===

[[Image:Export.png]]
[[Image:Change_Encoding_Sample Rate.png]]

=== Save it as WAV file ===

[[Image:Audacity_Import.png]]

How To Convert RTP into WAV file

2018-06-18T13:05:06Z

Nicole Tan:

Sometimes we need to convert the RTP packets extracted from Wireshark into .wav file, so anyone can listen the call easily for troubleshooting audio issue.
Below describe the steps to convert the RTP streams into .wav audio file:

**Open the extracted SIP/RTP capture of the call you want to analyze with wireshark:
Go to Telephony -> RTP -> RTP Streams
[[Image:Telephony_RTP_RTP Streams.png]]

Click “Analyze” button:

[[Image:Analyze.png]]

 

Save it to “Unsynchronized Forward Stream Audio”

[[Image:Save.png]]

 

And Save as type: Raw

[[Image:Save_Raw.png]]

 

2- Now you have the rtp streams in raw format. You can use a free tool called Audacity to reformat it to .wav file.
Import the raw data to Audacity:

[[Image:Audacity_Import.png]]

 

Export it and change the encoding and Sample rate:

[[Image:Export.png]]
[[Image:Change_Encoding_Sample Rate.png]]

 

Save it as WAV file:

[[Image:Audacity_Import.png]]

How To Convert RTP into WAV file

2018-06-15T21:31:23Z

Nicole Tan:

Sometimes we need to convert the RTP packets extracted from Wireshark into .wav file, so anyone can listen the call easily for troubleshooting audio issue.
Below describe the steps to convert the RTP streams into .wav audio file:

1- Open the extracted SIP/RTP capture of the call you want to analyze with wireshark:
Go to Telephony -> RTP -> RTP Streams
[[Image:Telephony_RTP_RTP Streams.png]]

Click “Analyze” button:

[[Image:Analyze.png]]

 

Save it to “Unsynchronized Forward Stream Audio”

[[Image:Save.png]]

 

And Save as type: Raw

[[Image:Save_Raw.png]]

 

2- Now you have the rtp streams in raw format. You can use a free tool called Audacity to reformat it to .wav file.
Import the raw data to Audacity:

[[Image:Audacity_Import.png]]

 

Export it and change the encoding and Sample rate:

[[Image:Export.png]]
[[Image:Change_Encoding_Sample Rate.png]]

 

Save it as WAV file:

[[Image:Audacity_Import.png]]

File:Audacity Import.png

2018-06-15T21:29:50Z

Nicole Tan: uploaded a new version of "File:Audacity Import.png"

File:Export.png

2018-06-15T21:28:08Z

Nicole Tan: