TBwiki - User contributions [en]

FN17753

2015-07-02T03:28:42Z

Candy Chan: Adding patch references

{{DISPLAYTITLE:FN17753 - Net-SNMP restarts and is generating core files}}

= Affected Products =
* TMG800, TMG3200, TMG7800-CTRL
* Tdev Linux server with (CentOS, RedHat, etc) running Toolpack software

= Problem Description =
* snmpd process continuously restarts in a loop.
* System which are shipped before April 2015 requires this fix.
* This fix is applicable if you have an older net-snmp version than below. To verify:
[root@TB011107 tbsnmpagent]# rpm -qa | grep snmp
net-snmp-libs-5.3.2.2-25.el5.tb
net-snmp-utils-5.3.2.2-25.el5.tb
net-snmp-5.3.2.2-25.el5.tb

If you have version previous to this one (5.3.2.2-25), you are affected by this Field Notice.

= Problem Symptoms =
* core files are observed in tbsnmpagent directory:
/mnt/.0/tb/toolpack/setup/12358/2.8/apps/tbsnmpagent

= Solution =
== Online Procedures ==
Applicable if the system has internet access with proper DNS configuration and is able to reach the TelcoBridges repositories server.

* Stop Toolpack
tbtoolpack stop
* Make sure your system is pointing to the TelcoBridges repositories. Verify the following TelcoBridges repository file:
vim /etc/yum.repos.d/TB-Base.repo

# TelcoBridges-Base.repo
#
# This repository is using TelcoBridges frozen version of CentOS
# to help client installing the required version of the
# applications required to run Toolpack
#

[tb-base]
name=TelcoBridges-$releasever - Base
baseurl=http://repo.telcobridges.com/centos/5/os/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5

#released updates
[tb-updates]
name=TelcoBridges-$releasever - Updates
baseurl=http://repo.telcobridges.com/centos/5/updates/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5-tb

* Get TelcoBridges repository key. If you don't already have them.
cd /etc/pki/rpm-gpg/
wget http://repo.telcobridges.com/centos/RPM-GPG-KEY-CentOS-5
wget http://repo.telcobridges.com/centos/RPM-GPG-KEY-CentOS-5-tb
* Update your net-snmp to the latest version
yum update net-snmp*
* Verify the updated net-snmp version. You should see:
[root@TB011107 tbsnmpagent]# yum list net-snmp
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* tb-base: repo.telcobridges.com
* tb-updates: repo.telcobridges.com
Excluding Packages in global exclude list
Finished
Installed Packages
net-snmp.x86_64 1:5.3.2.2-25.el5.tb installed
* Start Toolpack
tbtoolpack start

== Offline Procedures ==
Applicable for systems which are behind the firewall in a private network without internet access.

* Stop Toolpack
tbtoolpack stop
* Remove net-snmp. Confirm removal with "Y" when prompted.
yum remove net-snmp
* Manually install below RPMs:
rpm -ivhU net-snmp-libs-5.3.2.2-25.el5.tb.x86_64.rpm
rpm -ivhU net-snmp-5.3.2.2-25.el5.tb.x86_64.rpm
rpm -ivhU net-snmp-utils-5.3.2.2-25.el5.tb.x86_64.rpm
* Above files can be found at:
http://repo.telcobridges.com/centos/5/os/x86_64/CentOS/
* Verify the updated net-snmp version. You should see:
[root@TB011107 tbsnmpagent]# yum list net-snmp
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* tb-base: repo.telcobridges.com
* tb-updates: repo.telcobridges.com
Excluding Packages in global exclude list
Finished
Installed Packages
net-snmp.x86_64 1:5.3.2.2-25.el5.tb installed
* Start Toolpack
tbtoolpack start

= References =
RPM release note for net-snmp-utils-5.3.2.2-25
http://rpmfind.net/linux/RPM/centos/updates/5.11/x86_64/RPMS/net-snmp-utils-5.3.2.2-25.el5_11.x86_64.html

FN17753

2015-05-26T09:48:14Z

Candy Chan: First Field Notice for Trk#17753

{{DISPLAYTITLE:Net-SNMP restarts and is generating core files}}

= Affected Products =
* TMG800, TMG3200, TMG7800-CTRL
* Tdev Linux server with (CentOS, RedHat, etc) running Toolpack software

= Problem Description =
* snmpd process continuously restarts in a loop.
* System which are shipped before April 2015 requires this fix.
* This fix is applicable if you have an older net-snmp version than below. To verify:
[root@TB011107 tbsnmpagent]# rpm -qa | grep snmp
net-snmp-libs-5.3.2.2-25.el5.tb
net-snmp-utils-5.3.2.2-25.el5.tb
net-snmp-5.3.2.2-25.el5.tb

= Problem Symptoms =
* core files are observed in tbsnmpagent directory:
/mnt/.0/tb/toolpack/setup/12358/2.8/apps/tbsnmpagent

= Solution =
== Online Procedures ==
Applicable if the system has internet access with proper DNS configuration and is able to reach the TelcoBridges repositories server.

* Stop Toolpack
tbtoolpack stop
* Make sure your system is pointing to the TelcoBridges repositories. Verify the following TelcoBridges repository file:
vim /etc/yum.repos.d/TB-Base.repo

# TelcoBridges-Base.repo
#
# This repository is using TelcoBridges frozen version of CentOS
# to help client installing the required version of the
# applications required to run Toolpack
#

[tb-base]
name=TelcoBridges-$releasever - Base
baseurl=http://repo.telcobridges.com/centos/5/os/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5

#released updates
[tb-updates]
name=TelcoBridges-$releasever - Updates
baseurl=http://repo.telcobridges.com/centos/5/updates/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5-tb

* Get TelcoBridges repository key. If you don't already have them.
cd /etc/pki/rpm-gpg/
wget http://repo.telcobridges.com/centos/RPM-GPG-KEY-CentOS-5
wget http://repo.telcobridges.com/centos/RPM-GPG-KEY-CentOS-5-tb
* Update your system to the latest version
yum update
* Verify the updated net-snmp version. You should see:
[root@TB011107 tbsnmpagent]# yum list net-snmp
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* tb-base: repo.telcobridges.com
* tb-updates: repo.telcobridges.com
Excluding Packages in global exclude list
Finished
Installed Packages
net-snmp.x86_64 1:5.3.2.2-25.el5.tb installed
* Start Toolpack
tbtoolpack start

== Offline Procedures ==
Applicable for systems which are behind the firewall in a private network without internet access.

* Stop Toolpack
tbtoolpack stop
* Remove net-snmp. Confirm removal with "Y" when prompted.
yum remove net-snmp
* Manually install below RPMs:
rpm -ivhU net-snmp-libs-5.3.2.2-25.el5.tb.x86_64.rpm
rpm -ivhU net-snmp-5.3.2.2-25.el5.tb.x86_64.rpm
rpm -ivhU net-snmp-utils-5.3.2.2-25.el5.tb.x86_64.rpm
* Above files can be found at:
http://repo.telcobridges.com/centos/5.5/updates/x86_64/RPMS/
* Verify the updated net-snmp version. You should see:
[root@TB011107 tbsnmpagent]# yum list net-snmp
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* tb-base: repo.telcobridges.com
* tb-updates: repo.telcobridges.com
Excluding Packages in global exclude list
Finished
Installed Packages
net-snmp.x86_64 1:5.3.2.2-25.el5.tb installed
* Start Toolpack
tbtoolpack start

Field notices

2015-05-26T08:48:08Z

Candy Chan: Main page for advertising Field Notices - Trk#17654

{{DISPLAYTITLE:Field Notices}}
The purpose of this page is to provide information on the important updates needed to ensure the correct workings of TelcoBridges product features.

'''May 26th, 2015'''
* [[FN:17753|Net-SNMP restarts and is generating core files]]

[[category:FAQ]]

How to troubleshoot call routing

2015-05-15T10:15:51Z

Candy Chan: Add the required step to "Save" the config

To debug calls, different methods can be used: 

== Using the Call Detail Records ==

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

== Using the Call Trace Tool  (UCT or Unique Call Trace) ==

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

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

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

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

=== Change an Application log trace level ===
 You can change the trace level of the application here:
<pre>Applications-> Configurations -> edit -> Log Params -> Default Trace Level -> Save</pre>
And then activate the new configuration. Trace level 3 for '''gateway '''and '''toolpack_engine''' application will give most of the required information. 

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

=== Get the log files from the server ===
You can get the files directly from the server running Toolpack. Connect SSH to the management port of the unit and get the files at this location:
<pre>/lib/tb/toolpack/setup/12358/2.7/apps/</pre>
or
<pre>C:\TelcoBridges\toolpack\setup\12358\2.7\apps\</pre>

== Using the signaling traces ==

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

== Using the Toolpack programs backdoor tool ==

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

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

Typical errors:

404 not found

Support:Time tracking tool

2015-04-28T08:15:52Z

Candy Chan: Picture size, description adjustments

Every month, TelcoBridges partners receive a report showing the balance of their Support Bank hours. A negative value means that the account is in deficit. In such a case, we invite our Partners to promptly contact a sales representative to acquire new TB support hour banks.

 

To consult their TB Support activities, our partners can access TelcoBridges TB Support Time tracking tool:

https://timetracking.telcobridges.com

 

= Login =

The login/password is the same as that used for license server access. For partners who do not have a login for the above site, please contact [mailto:support@telcobridges.com TelcoBridges TB Support].

 

= Export view =

Once you are logged in, choose the Export tab. This view shows the support Bank hour units withdrawn from your account and also the units deposited to your account.

[[File:Kimai_export_tab.png|1024px]]

==Columns definition ==

{| class="wikitable"
|-
! Column Name !! Definition
|-
| '''Date''' || Date when support was provided
|-
| '''In''' || Start time (EST timezone)
|-
| '''Out''' || End time (EST timezone)
|-
| '''h'm''' || Duration in hours:minutes
|-
| '''Time''' || A chargeable task is rated at '-1' (per hour) and a non-chargeable task is rated at '0'
|-
| '''Rate/Total''' || Number of bank units withdrawn from the support bank account
|-
| '''Customer''' || Customer name
|-
| '''Project''' || Support bank (9-5 or 24-7). See [[TB_Support_A_la_Carte|TB Support A la Carte]] for more information
|-
| '''Task''' || Task that was performed : Configuration, Installation, Troubleshooting, and more.
|-
| '''Comment''' || Provide detail on the the nature of the task that was performed
|}

==Selecting the report date range ==

By default, when you log in, the Date range will show the current month only. Select the report period by changing the start date.

[[File:Kimai_export_date_range.png|1024px]]

 

== Changing the report date format ==

By default, the report ''Dateformat'' is 'd.m.'. To change it and include the year:
# Click the '''clock''' icon ((upper left, just below the Export tab)
# Set the date format to 'D' (m/d/y).

[[File:Kimai_export_dateformat.png|1024px]]

 

== Changing the view filter ==

The view entries can be filtered by Project and by Tasks. You can also choose what type of entries to view.
'''Note''': ''Expenses'' entries represent TB support bank hours units that have been added to the support account
# Click the '''funnel''' shaped icon (upper left, just below the Export tab)
# Select ''times and expenses'' to view all entries

[[File:Kimai_export_filter.png|1024px]]

 

== Exporting or printing ==

The view entries can be exported to a file or printed (see icons locate at the upper right).

The supported export files are : PDF, XLS and CSV

[[File:Kimai_export_exporting_report.png]]

 

== Suggested export options ==
Make sure to use below options on export to get the full report

[[File:Kimai_export_exporting_options.png|400px]]

 

= Current balance of hours =

# Select the '''report date range with a start date that includes all the entries of your account since its creation'''
# Set the view filter to show all the entries ('times and expenses'')
# Set the view filter to either your 5-9 or 24-7 project (click the funnel shapes icon of the project name to filter)
# Export into a .xls or .csv
# Open the file in your favourite spreadsheet editor and perform a summation on all the entries of the ''Rate/Total'' column
# The summation should match your support account balance

[[Category:Needs_revising]]

File:Kimai export exporting options.png

2015-04-28T08:12:01Z

Candy Chan:

Support:Time tracking tool

2015-04-28T08:11:44Z

Candy Chan: Added export report options suggestion

Every month, TelcoBridges partners receive a report showing the balance of their Support Bank hours. A negative value means that the account is in deficit. In such a case, we invite our Partners to promptly contact a sales representative to acquire new TB support hour banks.

 

To consult their TB Support activities, our partners can access TelcoBridges TB Support Time tracking tool:

https://timetracking.telcobridges.com

 

= Login =

The login/password is the same as that used for license server access. For partners who do not have a login for the above site, please contact [mailto:support@telcobridges.com TelcoBridges TB Support].

 

= Export view =

Once you are logged in, choose the Export tab. This view shows the support Bank hour units withdrawn from your account and also the units deposited to your account.

[[File:Kimai_export_tab.png|1024px]]

==Columns definition ==

{| class="wikitable"
|-
! Column Name !! Definition
|-
| '''Date''' || Date when support was provided
|-
| '''In''' || Start time (EST timezone)
|-
| '''Out''' || End time (EST timezone)
|-
| '''h'm''' || Duration in hours:minutes
|-
| '''Time''' || A chargeable task is rated at '-1' (per hour) and a non-chargeable task is rated at '0'
|-
| '''Rate/Total''' || Number of bank units withdrawn from the support bank account
|-
| '''Customer''' || Customer name
|-
| '''Project''' || Support bank (9-5 or 24-7). See [[TB_Support_A_la_Carte|TB Support A la Carte]] for more information
|-
| '''Task''' || Task that was performed : Configuration, Installation, Troubleshooting, and more.
|-
| '''Comment''' || Provide detail on the the nature of the task that was performed
|}

==Selecting the report date range ==

By default, when you log in, the Date range will show the current month only. Select the report period by changing the start date.

[[File:Kimai_export_date_range.png|1024px]]

 

== Changing the report date format ==

By default, the report ''Dateformat'' is 'd.m.'. To change it and include the year:
# Click the '''clock''' icon ((upper left, just below the Export tab)
# Set the date format to 'D' (m/d/y).

[[File:Kimai_export_dateformat.png|1024px]]

 

== Changing the view filter ==

The view entries can be filtered by Project and by Tasks. You can also choose what type of entries to view.
'''Note''': ''Expenses'' entries represent TB support bank hours units that have been added to the support account
# Click the '''funnel''' shaped icon (upper left, just below the Export tab)
# Select ''times and expenses'' to view all entries

[[File:Kimai_export_filter.png|1024px]]

 

== Exporting or printing ==

The view entries can be exported to a file or printed (see icons locate at the upper right).

The supported export files are : PDF, XLS and CSV

[[File:Kimai_export_exporting_report.png]]

 

= Suggested export options =
# Make sure to use below options on export to get the full report

[[File:Kimai_export_exporting_options.png]]

= Current balance of hours =

# Select the '''report date range with a start date that includes all the entries of your account since its creation'''
# Set the view filter to show all the entries ('times and expenses'')
# Set the view filter to either your 5-9 or 24-7 project (click the funnel shapes icon of the project name to filter)
# Export into a .xls or .csv
# Open the file in your favourite spreadsheet editor and perform a summation on all the entries of the ''Rate/Total'' column
# The summation should match your support account balance

[[Category:Needs_revising]]

Tmedia Major Upgrade

2015-04-10T08:50:36Z

Candy Chan: Add clearer notes on the decision of each step.

This article shows how to do a major upgrade.

== Web Portal Upgrade ==
'''Important: You need to run version 2.7.148 or later, to do a major upgrade through the web'''.

The procedure is the same as a minor upgrade.

*[[Toolpack:System_Settings_A#Package_Upgrade|Toolpack v2.8 package upgrades]]
*[[Web_Portal_Tutorial_Guide_v2.7#Minor_Package_Upgrade|Toolpack v2.7 package upgrades]]

== Manual Upgrade ==
'''Important: You need to use this procedure if your system runs version before 2.7.148'''.

'''Warning:''' Major upgrades require service interruption.

'''Note:''' For high availability systems, all the following commands needs to be executed on both units (for 1+1 systems) and both TMG7800-CTRL (for TMG7800 systems)

==== Stop Toolpack Service ====

tbtoolpack stop

==== Lawful Intercept prerequisites ====

'''Note:''' Only applicable for units shipped before to February 7th 2013 needs to install the following gems.

===== Install prerequisites =====

Verify Ruby gem version:
gem –v
Result:
1.3.6 (or later release)

Verify Ruby gem folder:
which gem
Result:
/usr/bin/gem

If both of these are ok, continue with the pre-requisites, otherwise, contact support@telcobridges.com

wget http://download.distribution.telcobridges.com/3rdparty/prerequisite/bin/linux/bundler-1.2.3.gem
gem install --local ./bundler-1.2.3.gem

wget http://download.distribution.telcobridges.com/3rdparty/prerequisite/bin/linux/json-1.7.7.gem
gem install --local ./json-1.7.7.gem

===== Validate prerequisites installation =====

Execute the following command:
gem list

If installed properly, you should see the following:
*** LOCAL GEMS ***

bundler (1.2.3) <--- bundler 1.2.3
fcgi (0.8.7)
json (1.7.7) <--- json 1.7.7

'''Note:''' If the results deviates from the above, please contact TelcoBridges Support.

==== Install package ====

*Transfer new installer using sftp on the Tmedia unit
*Run installer on the unit

Verify that the system will run on the correct version:

cat /lib/tb/toolpack/setup/12358/service/config.txt | grep tb/toolpack

Example of a v2.7 system configuration

application= /lib/tb/toolpack/setup/12358/2.7/apps/tboamapp/tboamapp_wd_cfg.ini

==== Install licenses ====

If not already done through the installer, copy the licenses in the licenses directory

/lib/tb/toolpack/pkg/licenses/

==== Copy audio files from [[TB_StreamServer|StreamServer]] (optional) ====

'''Note:''' Only applicable if you have custom audio files.

Customs audio files played by the [[TB_StreamServer|StreamServer]] are not copied automatically by the system. Therefore, it must be done manually.

Example of copying custom audio files from a v2.6 to v2.7 system:
cp /lib/tb/toolpack/setup/12358/2.6/apps/tbstreamserver/*.wav /lib/tb/toolpack/setup/12358/2.7/apps/tbstreamserver
cp /lib/tb/toolpack/setup/12358/2.6/apps/tbstreamserver/prompts/*.wav /lib/tb/toolpack/setup/12358/2.7/apps/tbstreamserver/prompts

==== Start Toolpack Service ====

tbtoolpack start

Toolpack:Starting an Application B

2015-04-10T08:31:41Z

Candy Chan: Starting an Application for 2.7 & 2.8

=== '''''Applies to version(s): v2.7, v2.8.''''' ===
{{DISPLAYTITLE:Starting an Application}}
In order to be able to load and start an application, it will need to have been installed
on the Toolpack application server. In addition, at least one Tmedia unit must have
been configured on the Toolpack application server so that you are able to connect to
it.

When you first log on to the Web Portal, your system application will have been installed on the
Toolpack application server, and it will be in a management state. This means that the application is not
yet operating and controlling your system. In order to start an application, its state must be changed
from Management to Run.

'''To start an application:'''

1. Select '''Applications''' from the navigation panel.

[[Image:Toolpack_v2.7_Navigation_Panel_Applications.png]]

2. Click the '''Status''' tab. Select the application that you wish to start/stop and click on its name.

[[Image:Toolpack_v2.7_Edit_Application.png|700px]]

3. Start/Stop the application:

*Set the '''Oam target state''' to '''Run''' or '''Don't Run'''.
* Click '''Apply States'''

[[Image:Toolpack_v2.7_Editing_Application_State.png]]

File:Toolpack v2.7 Navigation Panel Applications.png

2015-04-10T08:26:56Z

Candy Chan:

File:Toolpack v2.7 Editing Application State.png

2015-04-10T08:26:48Z

Candy Chan:

File:Toolpack v2.7 Edit Application.png

2015-04-10T08:26:21Z

Candy Chan:

Tmedia Major Upgrade

2015-04-02T02:12:32Z

Candy Chan: The minimum web portal major upgrade release is 2.7.148 but not 2.7.145.

This article shows how to do a major upgrade.

== Web Portal Upgrade ==
'''Important: You need to run version 2.7.148 or later, to do a major upgrade through the web'''.

The procedure is the same as a minor upgrade.

*[[Toolpack:System_Settings_A#Package_Upgrade|Toolpack v2.8 package upgrades]]
*[[Web_Portal_Tutorial_Guide_v2.7#Minor_Package_Upgrade|Toolpack v2.7 package upgrades]]

== Manual Upgrade ==
'''Important: You need to use this procedure if your system runs version before 2.7.148'''.

'''Warning:''' Major upgrades require service interruption.

'''Note:''' For high availability systems, all the following commands needs to be executed on both units (for 1+1 systems) and both TMG7800-CTRL (for TMG7800 systems)

==== Stop Toolpack Service ====

tbtoolpack stop

==== Lawful Intercept prerequisites ====

Units shipped before to February 7th 2013, needs to install the following gems.

===== Install prerequisites =====

Verify Ruby gem version:
gem –v
Result:
1.3.6 (or later release)

Verify Ruby gem folder:
which gem
Result:
/usr/bin/gem

If both of these are ok, continue with the pre-requisites, otherwise, contact support@telcobridges.com

wget http://download.distribution.telcobridges.com/3rdparty/prerequisite/bin/linux/bundler-1.2.3.gem
gem install --local ./bundler-1.2.3.gem

wget http://download.distribution.telcobridges.com/3rdparty/prerequisite/bin/linux/json-1.7.7.gem
gem install --local ./json-1.7.7.gem

===== Validate prerequisites installation =====

Execute the following command:
gem list

If installed properly, you should see the following:
*** LOCAL GEMS ***

bundler (1.2.3) <--- bundler 1.2.3
fcgi (0.8.7)
json (1.7.7) <--- json 1.7.7

==== Install package ====

*Transfer new installer using sftp on the Tmedia unit
*Run installer on the unit

Verify that the system will run on the correct version:

cat /lib/tb/toolpack/setup/12358/service/config.txt | grep tb/toolpack

Example of a v2.7 system configuration

application= /lib/tb/toolpack/setup/12358/2.7/apps/tboamapp/tboamapp_wd_cfg.ini

==== Install licenses ====

If not already done through the installer, copy the licenses in the licenses directory

/lib/tb/toolpack/pkg/licenses/

==== Copy audio files from [[TB_StreamServer|StreamServer]] (optional) ====
Customs audio files played by the [[TB_StreamServer|StreamServer]] are not copied automatically by the system. Therefore, it must be done manually.

Example of copying custom audio files from a v2.6 to v2.7 system:
cp /lib/tb/toolpack/setup/12358/2.6/apps/tbstreamserver/*.wav /lib/tb/toolpack/setup/12358/2.7/apps/tbstreamserver
cp /lib/tb/toolpack/setup/12358/2.6/apps/tbstreamserver/prompts/*.wav /lib/tb/toolpack/setup/12358/2.7/apps/tbstreamserver/prompts

==== Start Toolpack Service ====

tbtoolpack start

Support:Contacting TelcoBridges technical support

2015-03-09T06:31:48Z

Candy Chan: Minor edit

Support:Contacting TelcoBridges technical support

2015-03-09T06:30:44Z

Candy Chan: Separate contacting TBSupport and the public holidays page

Support:public holidays

2015-03-09T06:28:27Z

Candy Chan: Separate contacting TBSupport and the public holidays page

{| class="wikitable" width="50%"
|+Montreal, Canada Public Holidays
|-
|New Year's day
|January 1, 2015
|-
|Day After New Year's day
|January 2, 2015
|-
|Good Friday
|April 3, 2015
|-
|Easter Monday
|April 6, 2015
|-
|Patriotes
|May 18, 2015
|-
|St-Jean
|June 24, 2015
|-
|Canada Day
|July 1, 2015
|-
|Labour day
|September 7, 2015
|-
|Thanksgiving
|October 12, 2015
|-
|Day before Christmas day
|December 24, 2015
|-
|Christmas
|December 25, 2015
|-
|Boxing Day
|December 26, 2015
|-
|Day before New Year's day
|December 31, 2015
|-
|New Year's day
|January 1, 2016
|-
|Day after New Year's day
|January 2, 2016
|}

{| class="wikitable" width="50%"
|+[http://www.gov.hk/en/about/abouthk/holiday Hong Kong Public Holidays]
|-
|First day of January
|January 1, 2015
|-
|Day After New Year's day
|January 2, 2015
|-
|Lunar New Year's Day
|February 19, 2015
|-
|The second day of the Lunar New Year
|February 20, 2015
|-
|The third day of the Lunar New Year
|February 21, 2015
|-
|Good Friday
|April 3, 2015
|-
|The day following Good Friday
|April 4, 2015
|-
|The day following Ching Ming Festival
|April 6, 2015
|-
|The day following Easter Monday
|April 7, 2015
|-
|Labour Day
|May 1, 2015
|-
|The Birthday of the Buddha
|May 25, 2015
|-
|Tuen Ng Festival
|June 20, 2015
|-
|HKSAR Establishment Day
|July 1, 2015
|-
|The day following Chinese Mid-Autumn Festival
|September 28, 2015
|-
|National Day
|October 1, 2015
|-
|Chung Yeung Festival
|October 21, 2015
|-
|Day before Christmas day
|December 24, 2015
|-
|Christmas Day
|December 25, 2015
|-
|The first weekday after Christmas Day
|December 26, 2015
|-
|Day before New Year's day
|December 31, 2015
|-
|First day of January
|January 1, 2016
|-
|Day after First day of January
|January 2, 2016
|}

GHOST

2015-02-18T05:24:56Z

Candy Chan: Added the timezone reset procedures

{{DISPLAYTITLE:GHOST: The glibc's gethostbyname vulnerability}}

On January 27, 2015, a vulnerability named "GHOST" in the glibc library was publicly announced. GHOST is also referred as '''CVE-2015-0235'''. The vulnerability is a buffer overflow in the gethostbyname family of functions that can allow arbitrary code execution.

= Affected Products =
* TMG800, TMG3200, TMG7800-CTRL
* Tdev Linux server with (CentOS, RedHat, etc) running Toolpack software

= Details =
The impact of this vulnerability on TelcoBridges products depends on their configuration. The vulnerability may only be triggered through requests for domain name resolution. Therefore, only units that enable such services may be exposed to the issue.

= Software Versions and Fixes =
The TelcoBridges CentOS 5 repository has been updated with the latest glibc version. Services that use glibc must be restarted. Because glibc is thoroughly used in the Linux operating system, it is highly recommended to reboot the unit.

= Update procedure =
The operator can use one of the two methods available: GUI/WebPortal or command line interface.

== WebPortal - TMG unit or Linux server '''with access to Internet''' (i.e. with DNS configured) ==
* login onto the WebPortal
* Select the 'Hosts' section
* Click on the hostname
* Click on the 'Status' tab
* Select 'Upgrade Linux packages' into the host 'Action'
* Click on the 'Apply action' button
* Refresh the page until the packages are updated as indicated in the 'Action Log' (you may use the 'Now' button to update the page). The results should appear within a minute.
* Select 'Shutdown' into the host 'Action'
* Select 'Reboot' into the 'Shutdown Type'
* Click on the 'Apply action' button
* Repeat the process for all hosts listed

== Command line interface ==

* login with root account
[root@TB011107 ~]# uname -m
x86_64
* If the result is not "x86_64", [[Support:Contacting TelcoBridges technical support|please contact TelcoBridges]] support, otherwise you can proceed with either method below.
* Follow one of the two options depending if Internet is accessible from the unit

=== Option #1 - TMG unit or Linux server '''with access to Internet''' (i.e. with DNS configured) ===

* update OS packages with yum
yum clean all
yum update
* reboot the unit
reboot

=== Option #2 - TMG unit or Linux server '''without access to Internet''' ===
* download the following packages to your PC:
** http://repo.telcobridges.com/centos/5.7/updates/x86_64/RPMS/glibc-2.5-123.el5_11.1.x86_64.rpm
** http://repo.telcobridges.com/centos/5.7/updates/x86_64/RPMS/glibc-common-2.5-123.el5_11.1.x86_64.rpm
** http://repo.telcobridges.com/centos/5.7/updates/x86_64/RPMS/glibc-devel-2.5-123.el5_11.1.x86_64.rpm
** http://repo.telcobridges.com/centos/5.7/updates/x86_64/RPMS/glibc-headers-2.5-123.el5_11.1.x86_64.rpm
** http://repo.telcobridges.com/centos/5.7/updates/x86_64/RPMS/nscd-2.5-123.el5_11.1.x86_64.rpm
* Using WinSCP or similar tool, upload the files to the TMG unit using the root account
* login with root account
* Install packages
yum localinstall glibc-2.5-123.el5_11.1.x86_64.rpm \
glibc-common-2.5-123.el5_11.1.x86_64.rpm \
glibc-devel-2.5-123.el5_11.1.x86_64.rpm \
glibc-headers-2.5-123.el5_11.1.x86_64.rpm \
nscd-2.5-123.el5_11.1.x86_64.rpm
* '''Note''': that operation might take a long time since yum will probably experience timeouts when trying to access the external repositories.
* Reboot the unit
reboot

= How to verify if the vulnerability is fixed? =
* login with root account
* execute the following to create a test script
cat > rhel-GHOST-test.sh << FOF
#!/bin/bash
# rhel-GHOST-test.sh - GHOST vulnerability tester. Only for CentOS/RHEL based servers. #
# Version 3
# Credit : Red Hat, Inc - https://access.redhat.com/labs/ghost/ #
echo "Installed glibc version(s)"

rv=0
for glibc_nvr in \$( rpm -q --qf '%{name}-%{version}-%{release}.%{arch}\n' glibc ); do
glibc_ver=\$( echo "\$glibc_nvr" | awk -F- '{ print \$2 }' )
glibc_maj=\$( echo "\$glibc_ver" | awk -F. '{ print \$1 }')
glibc_min=\$( echo "\$glibc_ver" | awk -F. '{ print \$2 }')

echo -n "- \$glibc_nvr: "
if [ "\$glibc_maj" -gt 2 -o $ "\$glibc_maj" -eq 2 -a "\$glibc_min" -ge 18 $ ]; then
# fixed upstream version
echo 'not vulnerable'
else
# all RHEL updates include CVE in rpm %changelog
if rpm -q --changelog "\$glibc_nvr" | grep -q 'CVE-2015-0235'; then
echo "not vulnerable"
else
echo "vulnerable"
rv=1
fi
fi
done

if [ \$rv -ne 0 ]; then
cat <<EOF

This system is vulnerable to CVE-2015-0235. <https://access.redhat.com/security/cve/CVE-2015-0235>
Please refer to <https://access.redhat.com/articles/1332213> for remediation steps
EOF
fi

exit \$rv

FOF
* Execute the script
chmod +x rhel-GHOST-test.sh
./rhel-GHOST-test.sh
* '''You should not see the 'vulnerable' string displayed'''

= Verify system timezone =
We found that some systems got the timezone reset to EST time after the GHOST patch procedures
* Verify the timezone on the system
date

If it differs from the original, reset the timezone using the [[TMG:Change_Time_Zone|tbtimezone]] script.

= References =
* https://www.qualys.com/research/security-advisories/GHOST-CVE-2015-0235.txt
* https://access.redhat.com/articles/1332213
* http://www.cyberciti.biz/faq/cve-2015-0235-patch-ghost-on-debian-ubuntu-fedora-centos-rhel-linux/

TMG:Change Time Zone

2015-02-18T05:18:19Z

Candy Chan:

This article shows how to modify the timezone of a TMG unit.


'''NOTE''': Remember to restart Toolpack after modifying the timezone


== TMG shell command ==

tbtimezone

=== Example ===

This example explains how to change the TMG timezone the Hong Kong timezone.

[root@TB006882 x86_64-linux64]# tbtimezone
Please identify a location so that time zone rules can be set correctly.
Please select a continent or ocean.
1) Africa
2) Americas
3) Antarctica
4) Arctic Ocean
5) Asia
6) Atlantic Ocean
7) Australia
8) Europe
9) Indian Ocean
10) Pacific Ocean
11) none - I want to specify the time zone using the Posix TZ format.
#? 5
Please select a country.
1) Afghanistan 18) Israel 35) Palestine
2) Armenia 19) Japan 36) Philippines
3) Azerbaijan 20) Jordan 37) Qatar
4) Bahrain 21) Kazakhstan 38) Russia
5) Bangladesh 22) Korea (North) 39) Saudi Arabia
6) Bhutan 23) Korea (South) 40) Singapore
7) Brunei 24) Kuwait 41) Sri Lanka
8) Cambodia 25) Kyrgyzstan 42) Syria
9) China 26) Laos 43) Taiwan
10) Cyprus 27) Lebanon 44) Tajikistan
11) East Timor 28) Macau 45) Thailand
12) Georgia 29) Malaysia 46) Turkmenistan
13) Hong Kong 30) Mongolia 47) United Arab Emirates
14) India 31) Myanmar (Burma) 48) Uzbekistan
15) Indonesia 32) Nepal 49) Vietnam
16) Iran 33) Oman 50) Yemen
17) Iraq 34) Pakistan
#? 13

The following information has been given:

Hong Kong

Therefore TZ='Asia/Hong_Kong' will be used.
Local time is now: Mon Jan 24 22:56:39 HKT 2011.
Universal Time is now: Mon Jan 24 14:56:39 UTC 2011.
Is the above information OK?
1) Yes
2) No
#? 1
Changes are now applied, please restart Toolpack.

== Restart Toolpack ==

tbtoolpack stop
tbtoolpack start

Support:Contacting TelcoBridges technical support

2015-01-07T02:23:37Z

Candy Chan: Added a missing day for HK holidays

Wordwide technical support is available via either of the following channels:

 '''Americas & Europe Technical Support Centre (GMT-05:00,  Montreal, Canada)'''
 Office hours: Monday to Friday from 09:00 to 17:00 Eastern Time

Telephone: '''+1-450-655-8993 x131 or x102 '''

E-mail: [mailto:support@telcobridges.com support@telcobridges.com]

TBsupport tracking system: https://support.telcobridges.com 

Supported languages: English, French, Mandarin, Cantonese 

'''Asia Technical Support Centre (GMT +08:00, Hong Kong)'''
 Office hours: Monday to Friday from 09:00 to 17:00 Hong Kong Time

Telephone: '''+852-3749-9818'''

E-mail: [mailto:support@telcobridges.com support@telcobridges.com]

Supported languages: English, French, Mandarin, Cantonese

 

'''24/7 Support''' '''International''' (Public Holiday and non-office hours) 

Telephone: '''+1-866-438-4703 '''

Supported languages: English

Note: For customers for who have purchased 24/7 TBSupport bank of hours, please contact TBSupport via this 24/7 hotline for emergency

 

'''Instant Messenger/chat (Windows live messenger/Skype)'''

Send request to [mailto:support@telcobridges.com support@telcobridges.com] for contacts

 
'''Please kindly note that Telcobridges office is closed during the following public holidays.''' 
'''Please call 24/7 Support International for emergency if you have purchased 24/7 TBSupport bank of hours'''

{| class="wikitable" width="50%"
|+Montreal, Canada Public Holidays
|-
|New Year's day
|January 1, 2015
|-
|Day After New Year's day
|January 2, 2015
|-
|Good Friday
|April 3, 2015
|-
|Easter Monday
|April 6, 2015
|-
|Patriotes
|May 18, 2015
|-
|St-Jean
|June 24, 2015
|-
|Canada Day
|July 1, 2015
|-
|Labour day
|September 7, 2015
|-
|Thanksgiving
|October 12, 2015
|-
|Day before Christmas day
|December 24, 2015
|-
|Christmas
|December 25, 2015
|-
|Boxing Day
|December 26, 2015
|-
|Day before New Year's day
|December 31, 2015
|-
|New Year's day
|January 1, 2016
|-
|Day after New Year's day
|January 2, 2016
|}

{| class="wikitable" width="50%"
|+[http://www.gov.hk/en/about/abouthk/holiday Hong Kong Public Holidays]
|-
|First day of January
|January 1, 2015
|-
|Day After New Year's day
|January 2, 2015
|-
|Lunar New Year's Day
|February 19, 2015
|-
|The second day of the Lunar New Year
|February 20, 2015
|-
|The third day of the Lunar New Year
|February 21, 2015
|-
|Good Friday
|April 3, 2015
|-
|The day following Good Friday
|April 4, 2015
|-
|The day following Ching Ming Festival
|April 6, 2015
|-
|The day following Easter Monday
|April 7, 2015
|-
|Labour Day
|May 1, 2015
|-
|The Birthday of the Buddha
|May 25, 2015
|-
|Tuen Ng Festival
|June 20, 2015
|-
|HKSAR Establishment Day
|July 1, 2015
|-
|The day following Chinese Mid-Autumn Festival
|September 28, 2015
|-
|National Day
|October 1, 2015
|-
|Chung Yeung Festival
|October 21, 2015
|-
|Day before Christmas day
|December 24, 2015
|-
|Christmas Day
|December 25, 2015
|-
|The first weekday after Christmas Day
|December 26, 2015
|-
|Day before New Year's day
|December 31, 2015
|-
|First day of January
|January 1, 2016
|-
|Day after First day of January
|January 2, 2016
|}

Toolpack system systemId reconfiguration 2-7

2014-12-04T08:03:35Z

Candy Chan: Minor text edits

This procedure explains how to change the [[System_Id|SystemId]] of a Toolpack system.

=== Step 1: Backup the current database ===
* [[Toolpack:Database_Backup_B|Backup and download]] the database dump from the Web Portal

=== Step 2: Stop the Toolpack service ===
* Stop the service
tbtoolpack stop OldSystemId

=== Step 3: Install Toolpack with new [[System_Id|SystemId]] ===
* Use the Toolpack installer to install Toolpack on the new [[System_Id|SystemId]]:

[[toolpack_system_reconfiguration_2-3|System reconfiguration procedure for Toolpack release v2.3]]

=== Step 4: Update database system ID ===
* Connect to the database.
mysql -utbdb -p -h 'MyHostName' toolpack_0
* Modify the system_infos table
UPDATE system_infos SET gw_port='NewSystemId' where gw_port='OldSystemId';
* Exit
exit

=== Step 5: Change the [[System_Id|SystemId]] of all the Tmedia and TMS ===
* Telnet to a Tmedia
** For example, on a TMG, "telnet 172.31.1.1"

* Enter the 'set_boot' command

* Press enter until you see the following line:
gateway port (TBX_GW_PORT=OldSystemId)? :

* Enter the new [[System_Id|SystemId]] value

* Press the Enter key

* Press Ctrl + c

* Reboot the Tmedia
reboot

* Repeat those steps for all the Tmedia and TMS of your system

=== Step 6: Start the Toolpack service ===
* Start the new service
tbtoolpack start NewSystemId

=== Step 7: Uninstall the old Toolpack service ===
* Uninstall the old Toolpack service (NOTE: uninstalling the service will not erase the [InstallDir]/toolpack/setup/[OldSystemId] directory)
tbtoolpack uninstall OldSystemId

=== Step 8: Enable the new Toolpack service at startup ===
* If you want the Toolpack service to start when the host boot, enter the following command:
tbtoolpack enable NewSystemId

Toolpack system systemId reconfiguration 2-7

2014-12-04T08:00:22Z

Candy Chan: Toolpack system systemId reconfiguration 2-7

This procedure explains how to change the [[System_Id|SystemId]] of a Toolpack system.

=== Step 1: Backup the current database ===
* [[Toolpack:Database_Backup_B|Backup and download]] the database dump from the Web Portal

=== Step 2: Stop the Toolpack service ===
* Stop the service
tbtoolpack stop OldSystemId

=== Step 3: Install the new [[System_Id|SystemId]] ===
* Use the Toolpack installer to install the [[System_Id|SystemId]]:

[[toolpack_system_reconfiguration_2-3|System reconfiguration procedure for Toolpack release v2.3]]

=== Step 4: Update database system ID ===
* Connect to the database.
mysql -utbdb -p -h 'MyHostName' toolpack_0
* Modify the system_infos table
UPDATE system_infos SET gw_port='NewSystemId' where gw_port='OldSystemId';
* Exit
exit

=== Step 5: Change the [[System_Id|SystemId]] of all the Tmedia and TMS ===
* Telnet to a Tmedia
** For example, on a TMG, "telnet 172.31.1.1"

* Enter the 'set_boot' command

* Press enter until you see the following line:
gateway port (TBX_GW_PORT=OldSystemId)? :

* Enter the new [[System_Id|SystemId]] value

* Press the Enter key

* Press Ctrl + c

* Reboot the Tmedia
reboot

* Repeat those steps for all the Tmedia and TMS of your system

=== Step 6: Start the Toolpack service ===
* Start the new service
tbtoolpack start NewSystemId

=== Step 7: Uninstall the old Toolpack service ===
* Uninstall the old Toolpack service (NOTE: uninstalling the service will not erase the [InstallDir]/toolpack/setup/[OldSystemId] directory)
tbtoolpack uninstall OldSystemId

=== Step 8: Enable the new Toolpack service at startup ===
* If you want the Toolpack service to start when the host boot, enter the following command:
tbtoolpack enable NewSystemId

Tctrl Version 2.8

2014-10-22T01:32:06Z

Candy Chan:

Tctrl Version 2.7

2014-10-22T01:31:08Z

Candy Chan: Remove H.248 CAS which we don't support in 2.7

== Features ==

The [[TMG-CONTROL]] provides the following [[:category:Tmedia Features|features]].

 

{| cellpadding="0" border="0" style="width: 820px; height: 383px; text-align: center;" class="wikitable"
|-
! width="500" | Features
! width="150" | Enhancement'''1'''
! width="150" | Release
|-
! colspan="3" | TMG Product
|-
| style="text-align:left;" | [[N+1]]
| -
| 2.7.26
|-
| style="text-align:left;" | [[Symmetric_NAT_Traversal|NAT Traversal]]
| 5656
| 2.7.26
|-
| style="text-align:left;" | [[Lawful_intercept|Lawful Intercept]]
| 12894
| 2.7.26
|-
| style="text-align:left;" | [[RADIUS AAA]] (authorization and authentication support)
| 7984
| 2.7.26
|-
| style="text-align:left;" | [[Radius_Acct_Auth_Association|RADIUS accounting and authorization association]]
| 14344
| 2.7.31
|-
| style="text-align:left;" | [[Outgoing COT testing]]
| 8710
| 2.7.26
|-
| style="text-align:left;" | [[VoIP_Bonding|VoIP Bonding]]
| 14595
| 2.7.34
|-
| style="text-align:left;" | [[Toolpack:Creating_an_ISUP_User_Part_A|SS7 ISUP NTT variant]]
| 13921
| 2.7.39
|-
| style="text-align:left;" | [[SPIROU|SS7 SPIROU variant]]
| width="150" style="background: none repeat scroll 0% 0% rgb(255, 255, 255);" | 6337
| width="150" style="background: none repeat scroll 0% 0% rgb(255, 255, 255);" | 2.7.26
|-
| style="text-align:left;" | [[CAS#CAS_R1|Support CASR1]]
| 12075
| 2.7.34
|-
| style="text-align:left;" | [[CAS#CAS_R2|Support CASR2 for DS3/STM-1]]
| 10177
| 2.7.101
|-
| style="text-align:left;" | [[CAS_R2_scripting|CAS R2 metering on incoming calls]]
| 14574
| 2.7.31
|-
| style="text-align:left;" | [[How_to_channelize_STM-1_to_E1_Channel_Mapping:_KLM_vs_ITU-T_vs_Alcatel|New STM-1 to E1 Channel Mapping: Alcatel-Lucent]]
| 15097
| 2.7.51
|-
! colspan="3" | H.248
|-
| style="text-align:left;" | [[Support H.248 Local NAT traversing for RTP streams]]
| 14869
| 2.7.43
|-
| style="text-align:left;" | [[H.248|Support Q.1950 call progress tone generator package (bcg) for H.248]]
| 15427
| 2.7.76
|-
! colspan="3" | Fax
|-
| style="text-align:left;" | [[NSE]]
| 12665
| 2.7.26
|-
! colspan="3" | Operation, Administration and Maintenance (OAM)
|-
| style="text-align:left;" | [[Web Profile]]
| -
| 2.7.26
|-
| style="text-align:left;" | [[Test_Call|Test Call]]
| -
| 2.7.26
|-
| style="text-align:left;" | [[Target_Recording|Target Recording]]
| -
| 2.7.26
|-
| style="text-align:left;" | [[System_Statistics|System Statistics]]
| -
| 2.7.26
|-
| style="text-align:left;" | [[Users|User authentication and permissions]]
| -
| 2.7.26
|-
| style="text-align:left;" | [[Audit_Log|Audit Logs]]
| 10838
| 2.7.26
|-
| style="text-align:left;" | [[Toolpack:RADIUS_CDR_attributes_C|RTCP/TDM stats in Call Trace, Radius accounting]] and [[Text_Call_Detail_Records#Statistics|text CDR]]
| 12948
| 2.7.120
|-
| style="text-align:left;" | [[Global call statistics available in the web portal]]
| 14908
| 2.7.45
|-
| style="text-align:left;" | [[Toolpack:Retrieving_Call_Trace_A|Call trace now shows chosen routes]]
| 14473
| 2.7.62
|-
| style="text-align:left;" | [[Gateway_Upgrade|Allow Major Upgrade from Web Portal]]
| 13773
| 2.8
|-
! colspan="3" | Routing
|-
| style="text-align:left;" | [[Routing_script_tutorial:Mini_Development_Guide#Script_parameters_protocol_mapping|Incoming NAP, trunk and timeslot available in routing script]]
| 16056
| 2.7.125
|-
| style="text-align:left;" | [[Incoming NAP available to label routing]]
| 13268
| 2.7.125
|-
! colspan="3" | Protocol Adaptation
|-
| style="text-align:left;" | [[SS7_Backward_Call_Indicator|Set SS7 Backward Call Indicator (BCI) to a specific value]]
| 16360
| 2.7.127
|-
| style="text-align:left;" | [[SS7_Backward_Call_Indicator|Send SS7 Backward Call Indicator (BCI) in ANM]]
| 16361
| 2.7.127
|-
| style="text-align:left;" | [[Multilevel precedence and preemption|Add Emergency Call handling (MLPP)]]
| 13698
| 2.7.125
|-
| style="text-align:left;" | [[Routing_script_tutorial:Mini_Development_Guide#Information_Transfer_Capability_values|Transfer bearer capability relay to/from SIP]]
| 15400
| 2.7.125
|-
| style="text-align:left;" | [[Routing_script_tutorial:Mini_Development_Guide#ISUB_subaddress_information_values|ISUB (ISDN subaddress) relay to/from SIP]]
| 15432
| 2.7.125
|-
| style="text-align:left;" | [[Modify_Early_Media_Relay_and_Ring_Tone_Generation_profile_B|Allow bidirectional Early Media]]
| 16257
| 2.7.124
|-
| style="text-align:left;" | [[Toolpack_v2.7:_clearmode_configuration|Support configurable packetization times for RFC 4040]]
| 15313
| 2.7.121
|-
| style="text-align:left;" | [[Tmedia_Routing#Incoming_call_parameters_remapping|Allow remapping of incoming leg profile per route]]
| 13698
| 2.7.101
|-
| style="text-align:left;" | [[Routing_script_tutorial:Mini_Development_Guide#Script_parameters_protocol_mapping|Support ISDN CNAM (caller name) using facility IE]]
| 13380
| 2.7.89
|-
! colspan="3" | Development Platform
|-
| style="text-align:left;" | [[CAF:_Working_With_Caf_Call_Legs|Mixing API]] (for conferencing and other functions)
| 4850
| 2.7.12
|-
| style="text-align:left;" | [[CAF:_Caf_Mixer_Events|Allow to control mixers resize-down timer]] (for conferencing and other functions)
| 16100
| 2.7.121
|-
! width="800" style="background: none repeat scroll 0% 0% rgb(239, 239, 239);" colspan="3" | New Products
|-
| style="text-align:left;" | [[TM3000]]
| -
| 2.7.15
|-
| style="text-align:left;" | [[TM3000|TM3000 supports 1024 HDLC controllers]]
| -
| 2.7.64
|}

[1] Customer's RFC (Request For Change) tracking number.

Toolpack:Retrieving Call Trace A

2014-10-20T05:58:18Z

Candy Chan: Unhide important session.

=== '''''Applies to version v2.7''''' ===
{{DISPLAYTITLE:Retrieving Call Trace}}

==== Getting calls from memory ====
1- Click '''Call Trace''' in the navigation panel

[[Image:CallTrace_0_0.png]]

2- Set various parameters for the call trace, such as
*Time and date range
*Called or calling number
*Network Access Point (NAP)
*Incoming or outgoing calls
*Call Duration, Reason Code

[[Image:ConfigureCallTrace_1_A.png]]

Once you are satisfied with the filter criteria, click '''Apply'''

The filter results are displayed.

3-Select a call in the results window to display further information about the call.

[[Image:ConfigureCallTrace_1_A.png]]

4- Choose the concerned call entry to view the details.

[[Image:ConfigureCallTrace_7_A.png]]

5- You can click export to save the call trace as a HTML file.

[[Image:ConfigureCallTrace_8_A.png]]

==== Getting calls from files ====
To search for calls that are no longer in memory, do the following:

By default, the system stores up to 10,000 call legs in memory. If the call is no longer in memory, it may be retrieved by using information from the uctdata log files.

By default the file is located in the following path:
<pre>/lib/tb/toolpack/setup/12358/2.6/apps/tbuctwriter/uctdata*</pre>

1- Start [[How_to_use_tbx_cli_tools_remote_program|tbx_cli_tools_remote]] 
2- Select tbuctwriter 
3- To know which files are available, as well as the start and end time of each file, use the following options:
* 'p' to print all uctdata files on disk

To load a file into memory for viewing with the Web Portal: 
* Option 'o' followed by the data filename (uctdata*)

Use the Web Portal to search for calls using the appropriate filter criteria. The memory will not be overwritten until you restore normal process.

To restore normal process: 

*Option ‘c’ to clear memory
*Option ‘l’ to have calls put in memory again

Support:How To extract backtrace from coredump

2014-10-07T03:04:13Z

Candy Chan: Added debugging example.

When a fault happens in toolpack, developers may need to get more useful information to fix the problem.

== Running GNU Debuger (GDB) ==
How to give useful information related to a fault in the code:

# Log to the primary server (ssh)
# Type tbsetup
#: Usually all core files goes into the application's working directory.
# Type cd APPLICATION
#:where:
#:
#:*APPLICATION is the application that crashes
#: In this example, we'll suppose APPLICATION is toolpack_engine
#:
# Execute command: <pre>gdb -se "APPLICATION" -ex "bt full" -ex "thread apply all bt" --batch -c CORE > /tmp/backtrace.txt</pre>
#:where:
#:
#:*APPLICATION is the application that crashes (Full path of the application)
#:
#:*CORE is the core file. (core.xxxx)
#:
#:
#:for example:
#:<pre>gdb -se "/lib/tb/toolpack/pkg/2.8.5/bin/release/x86_64-linux64/toolpack_engine" -ex "bt full" -ex "thread apply all bt" --batch -c core.17900 > /tmp/backtrace.txt</pre>
#:
#:In this specific example, the crash happened at:
#:<code> Program terminated with signal 11, Segmentation fault. #0 0x000000000043ce59 in CallBridgingSampleDisplayMenu () #0 0x000000000043ce59 in CallBridgingSampleDisplayMenu () No symbol table info available.
#:</code>
#:
# Attach the file /tmp/backtrace.txt in the TBSupport Tracking System (ticket that you opened to report the problem).

== Troubleshooting ==
Possible Error 1:
# gdb
-bash: gdb: command not found

This is because you did not install the gdb package.
You can do:
yum install gdb

Possible Error 2:
warning: exec file is newer than core file.
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fffa11ec000

This is because the core dump file (CORE) was not generated by the pointed application (APPLICATION). It was generated by an older version of toolpack application. Make sure the core dump file matches the application that you gave as an argument to GDB.

If you prefer to run the application in gdb, consult this [[Support:How_To_Run_Toolpack_Application_In_gdb|page]]

Support:How To extract backtrace from coredump

2014-10-07T02:19:25Z

Candy Chan:

When a fault happens in toolpack, developers may need to get more useful informations to fix the problem.

How to give useful informations related to a fault in the code:

# Log to the primary server (ssh)
# Type tbsetup
#: Usually all core files goes into the application's working directory.
# Type cd APPLICATION
#:where:
#:
#:*APPLICATION is the application that crashes
#: In this example, we'll suppose APPLICATION is toolpack_engine
#:
# Execute command: <pre>gdb -se "APPLICATION" -ex "bt full" -ex "thread apply all bt" --batch -c CORE > /tmp/backtrace.txt</pre>
#:where:
#:
#:*APPLICATION is the application that crashes
#:
#:*CORE is the core file.
#:
#:for example:
#:<pre>gdb -se "/lib/tb/toolpack/pkg/2.8.5/bin/release/x86_64-linux64/toolpack_engine" -ex "bt full" -ex "thread apply all bt" --batch -c core.17900 > /tmp/backtrace.txt</pre>
#:
#:If you are not sure about which application caused the crash, you can look in the created file for:
#:
#:Core was generated by `./release/x86_64-linux64/toolpack_engine -gw 12358'.
#:
#:For example, in that specific example, the crash happened at:
#:<code> Program terminated with signal 11, Segmentation fault. #0 0x000000000043ce59 in CallBridgingSampleDisplayMenu () #0 0x000000000043ce59 in CallBridgingSampleDisplayMenu () No symbol table info available.
#:</code>
#:
# Attach the file /tmp/backtrace.txt in the TBSupport Tracking System (ticket that you opened to report the problem).

Troubleshooting:

if you see:
# gdb
-bash: gdb: command not found

This is because you did not install the gdb package.
You can do:
yum install gdb

If you prefer to run the application in gdb, consult this [[Support:How_To_Run_Toolpack_Application_In_gdb|page]]

Support:How To extract backtrace from coredump

2014-10-07T02:19:03Z

Candy Chan: wording modification

When a fault happens in toolpack, developers may need to get more useful informations to fix the problem.

How to give useful informations related to a fault in the code:

# Log to the primary server (ssh)
# Type tbsetup
#: Usually all core files goes into the application's working directory.
# Type cd APPLICATION
#:where:
#:
#:*APPLICATION is the application that crashes
#: In this example, we'll suppose APPLICATION is toolpack_engine
#:
# Execute command: <pre>gdb -se "APPLICATION" -ex "bt full" -ex "thread apply all bt" --batch -c CORE > /tmp/backtrace.txt</pre>
#:where:
#:
#:*APPLICATION is the application that crashes
#:
#:*CORE is the core file.
#:
#:for example:
#:<pre>gdb -se "/lib/tb/toolpack/pkg/2.8.5/bin/release/x86_64-linux64/toolpack_engine" -ex "bt full" -ex "thread apply all bt" --batch -c core.17900 > /tmp/backtrace.txt</pre>
#:
#:If you are not sure about which application caused the crash, you can look in the created file for:
#:
#:Core was generated by `./release/x86_64-linux64/toolpack_engine -gw 12358'.
#:
#:For example, in that specific example, the crash happened at:
#:<code> Program terminated with signal 11, Segmentation fault. #0 0x000000000043ce59 in CallBridgingSampleDisplayMenu () #0 0x000000000043ce59 in CallBridgingSampleDisplayMenu () No symbol table info available.
#:</code>
#:
# Attach the file /tmp/backtrace.txt in your TBSupport Tracking System (ticket that you opened to report the problem).

Troubleshooting:

if you see:
# gdb
-bash: gdb: command not found

This is because you did not install the gdb package.
You can do:
yum install gdb

If you prefer to run the application in gdb, consult this [[Support:How_To_Run_Toolpack_Application_In_gdb|page]]

2014-04-29T09:52:41Z

Candy Chan: Created page with "Tbstatus monitoring is a ruby script which makes use of the tbstatus application to gather statistics on a system. It calls tbstatus periodically with parameters according to ..."

File:Tbstatus monitor.zip

2014-04-29T09:37:55Z

Candy Chan: Tbstatus Monitoring Script

Tbstatus Monitoring Script

Add/Change Licenses 2-5

2014-02-19T09:56:08Z

Candy Chan: Added a link to "Verify_Licenses".

=== '''''Applies to version(s): v2.5, v2.6, v2.7.''''' ===
{{DISPLAYTITLE:Add/Change Licenses}}
TelcoBridges uses a license-based approach to activate various software or hardware functions in [[Toolpack]] or the underlying hardware. When installing Toolpack, implementing new software capabilities, or following the addition of a hardware module, you may be required to add or modify a license. The following instructions will enable you to do so.

== Uploading licenses via the Web portal ==
# Got to the primary host edit status page [[Image:Add Change Licenses 1.png|800px]] 
# Select the primary host [[Image:Add Change Licenses 2.png|800px]] 
# Choose 'Upload license' in the host control action combo box [[Image:Add Change Licenses 3.png|800px]] 
# Select the license file and click the 'Apply action' button
# Wait for the page to reload and then monitor the process by pressing the ''now'' button from time to time
# After license update, click [[Verify_Licenses|here]] to see how to verify the license installation status
 
'''IMPORTANT: You will need to restart the Tmedia unit(s) to apply the changes after installing a new license, except if it is for extending the end date, or to make it permanent.'''

To do this, reboot the unit (will drop active calls)
Status -> Hardware Units -> Click on the unit Serial Number -> Reboot unit
It will take about 1.5 minutes to restart the unit.

 For more information see the [[Host-control|host control]] page

Verify Licenses

2014-02-19T09:52:18Z

Candy Chan: /* Applies to version(s): v2.5, v2.6, v2.7. */

=== '''''Applies to version(s): v2.5, v2.6, v2.7.''''' ===
{{DISPLAYTITLE:Verify Licenses}}
TelcoBridges uses a license-based approach to activate various software or hardware functions in [[Toolpack]] or the underlying hardware. When installing Toolpack, implementing new software capabilities, or following the addition of a hardware module. After you have installed the license, you need to verify the license installation result.

== Verifying licenses via the Web portal ==
# Got to the Hardware Unit's Status page [[Image:Verify Licenses 1.png|700px]] 
# Select the hardware serial number 
# In the "States" tab, look for the below fields:
## Oam last license install result
## Oam last license install time
## License about to expire
## License expired
## License days left [[Image:Verify Licenses 2.png|400px]] 
# Try to reload the page in case if the license installation is still in progress. Monitor the process by pressing the ''now'' button from time to time. [[Image:Verify Licenses 3.png|700px]] 
# Check the license details in the "Licensed features" tab [[Image:Verify Licenses 4.png|600px]]

Verify Licenses

2014-02-19T09:47:53Z

2013-10-29T09:14:04Z

Candy Chan:

This page shows the Toolpack 2-5, 2-6 and 2-7 prerequisites for CentOS 5.5, 5.6, 5.7 and 5.8.


''WARNING'': The host MUST have CentOS 5.5, 5.6, 5.7 or 5.8 installed. If you don't want to update your host, please follow the [[Toolpack prerequisite CentOS5 2-5 manual| manual procedure]] instead.



''WARNING'': If you followed the [[Toolpack prerequisite CentOS5 2-5 manual| manual procedure]] on the system before, you '''MUST NOT''' use the steps on this page before doing a cleanup of the previously installed files. You should ask Telcobridges support for help with the cleanup.



''WARNING'': This procedure requires internet access and a DNS configured on your unit.


== Stop toolpack system (if it is running) ==

tbtoolpack stop

== TelcoBridges repository ==

Add TelcoBridges repository file

vim /etc/yum.repos.d/TB-Base.repo

Paste the following information in that file:

# TelcoBridges-Base.repo
#
# This repository is using TelcoBridges frozen version of CentOS
# to help client installing the required version of the
# applications required to run Toolpack
#

[tb-base]
name=TelcoBridges-$releasever - Base
baseurl=http://repo.telcobridges.com/centos/5/os/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5

#released updates
[tb-updates]
name=TelcoBridges-$releasever - Updates
baseurl=http://repo.telcobridges.com/centos/5/updates/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5-tb

== Get TelcoBridges repository key ==

cd /etc/pki/rpm-gpg/
wget http://repo.telcobridges.com/centos/RPM-GPG-KEY-CentOS-5-tb

== CentOS update ==

Update your system to CentOS 5.8

yum clean metadata
yum update

=== Reply to ARP only on local interfaces ===

Modify the file /etc/sysctl.conf to add the following lines:

net.ipv4.conf.default.arp_ignore=1
net.ipv4.conf.all.arp_ignore=1

Then restart network interfaces using the following command:

/etc/init.d/network restart

=== Disabling SELinux ===

Check SELinux status

sestatus

If SELinux is enable, see the [[SELinux_management|Disabling SELinux]] article to disable it.

== Install Toolpack Prerequisites ==

When asked to 'Importing GPG key', answer yes.

yum groupinstall Toolpack-Prerequisites

==== Possible Dependencies Issue ====
If you meet an issue which blocks the installation with error that is related to "dovecot". Do the following and retry the "groupinstall" command to restart installation.

yum remove dovecot

=== Install Gem ===

wget http://download.distribution.telcobridges.com/3rdparty/prerequisite/bin/linux/bundler-1.2.3.gem
gem install --local ./bundler-1.2.3.gem

wget http://download.distribution.telcobridges.com/3rdparty/prerequisite/bin/linux/json-1.7.7.gem
gem install --local ./json-1.7.7.gem

== Apply kernel patches (if any) ==

shutdown -r now

Once rebooted, be sure that Toolpack system is stopped before manipulating MySQL.

tbtoolpack stop

=== Configure ODBC ===

vim /etc/odbcinst.ini

Remove the '#' in front of each lines of the [MySQL] section Modify the 'Driver' line to set the correct driver

Example for 32 bits system:

[MySQL]
Description = ODBC for MySQL
Driver = /usr/lib/libmyodbc5.so
Setup = /usr/lib/libodbcmyS.so
FileUsage = 1

 Example for 64 bits system:

[MySQL]
Description = ODBC for MySQL
Driver = /usr/lib64/libmyodbc5.so
Setup = /usr/lib/libodbcmyS.so
FileUsage = 1

=== Configure MySQL ===

vim /etc/my.cnf

Add these variables in the file under the [mysqld] section:

*log-bin
*server-id=''[UniqueId]''

The server-id needs to be a non-zero unique value (do not use 0). If you use the host redundancy feature, the value needs to be different on each host .

 Add max_allowed_packet to increase the maximum size of binary blobs in the database. Make sure it is in the [mysqld] section AND [mysqldump] section

max_allowed_packet = 200MB

 Add below to remove database dependencies with DNS servers '''(**Applicable to TMG users only)'''

skip-name-resolve

Example:

[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
log-bin
server-id=5876
max_allowed_packet = 200MB

# Default to using old password format for compatibility with mysql 3.x
# clients (those using the mysqlclient10 compatibility package).
old_passwords=1

# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

# Added so that problems with DNS servers don't cause problems with the mysql DB
# Note: This is applicable only if you are using a TMG
skip-name-resolve

[mysqldump]
max_allowed_packet = 200MB

=== Start MySQL ===

service mysqld start

=== Configure MySQL Users ===

*Set password for the root user to 'tbdbpw' (TelcoBridges recommends that you set your own password for root)
*Enable root connection from localhost only
*Create a tbdb user (required by Toolpack)
*Remove anonymous connection

Example:

/usr/bin/mysqladmin -u root password tbdbpw

mysql -uroot -ptbdbpw
DELETE FROM mysql.user WHERE !(Host = 'localhost' AND User = 'root');
FLUSH PRIVILEGES;
CREATE USER 'tbdb'@'%' IDENTIFIED BY 'tbdbpw';
GRANT ALL PRIVILEGES ON *.* TO 'tbdb'@'%' IDENTIFIED BY 'tbdbpw';
FLUSH PRIVILEGES;
exit

== Toolpack Development Prerequisite (Optional) ==

The Toolpack System Development prerequisite section is only required for customers that will develop their own application using the Toolpack API:

yum install gcc-c++ libxml2-devel libpcap-devel unixODBC-devel libaio libaio-devel

== Validation Guide (highly recommended) ==

If you would like to verify your installation go to the [[Toolpack Installation:Validate Toolpack Installation 2-5|Toolpack Validation Guide]]

 

== Toolpack System installation ==

Now that the prerequisite are installed, now it is time to install the [[Toolpack installer 2-4|Toolpack system]]