TBwiki - User contributions [en]

Toolpack:Adding a custom RADIUS dictionary A

2015-06-25T15:29:14Z

Martin Provencher: Fix link for the Linux Radius documentation (the pipe was present in the link)

=== '''''Applies to version(s): v2.7.''''' ===
{{DISPLAYTITLE:Adding a Custom RADIUS Dictionary}}
This page describes how to add a custom RADIUS dictionary to use vendor-specific RADIUS attributes.

'''Note:''' The format of a RADIUS dictionary is based on the following article: [http://linux.die.net/man/5/dictionary | Linux Man Page: Radius Dictionary]

1- Select '''File Db''' from the navigation panel.

[[Image:FileDB 0 B.png|border]]

2- In the '''RADIUS dictionaries''' section, click '''Import new RADIUS dictionary'''.

[[Image:RADIUS-file-db-dictionary-2_7.PNG|border]]

3- Click the '''Browse...''' button to select the RADIUS dictionary to add. When the file is selected, click '''Import'''.

[[Image:RADIUS-file-db-dictionary-import-2_7.PNG|border]]

4- Verify that the '''File was successfully imported.''' message appears.

Tone definitions

2015-01-20T16:07:30Z

Martin Provencher: Fix the link under "section" for tone definition

=== Tone definitions ===

It is possible through the [[Toolpack]] [[Web Portal]] to specify the parameters of ringing, busy, congestion (or fast busy) and warning call progress tones. These settings are available in
<pre>Profiles -> Tone Profile Params </pre>
The tones are described using a programmable string of characters as defined in the [[H.248]] Dynamic Tone Definition Package. To learn more about tone description strings, see the [[CAF: Working With Cmc Call Legs#Play_Tone_with_Signal_Id_String|section]] related to this subject.

=== Examples of Call Progress tones ===

The following table contains a few call progress tone definition strings that can be used to replace the default ones in the Toolpack Web Portal.

{| cellspacing="1" cellpadding="2" border="1"
|-
! 
! Ring
! Busy
! Congestion
! Warning
|-
! Australia 
| ((((#400)+(#450)),400),(#0,200),(((#400)+(#450)),400),(#0,2000))*0 
| ((#425,375),(#0,375))*0 
| ((#425,375),(#0,375))*0 
| ((#900),500) 
|-
! Bangladesh 
| ((#425,1000),(#0,4000))*0 
| ((#450,200),(#0,300),(#450,700),(#0,800))*0 
| ((#425,250),(#0,250))*0 
| ((#450,200),(#0,20),(#450,200),(#0,140))*0 
|-
! Brazil
| ((#425,1000),(#0,4000))*0
| ((#425,250),(#0,250))*0
| ((#425,750),(#0,250),(#425,250),(#0,250))*0
| ''unused''
|-
! China
| ((#450,1000),(#0,4000))*0
| ((#450,350),(#0,350))*0
| ((#450,700),(#0,700))*0
| ''unused''
|-
! France
| ((#440,1500),(#0,3500))*0
| ((#440,500),(#0,500))*0
| ((#440,250),(#0,250))*0
| ''unused''
|-
! Germany
| ((#425,1000),(#0,4000))*0
| ((#425,480),(#0,480))*0
| ((#425,240),(#0,240))*0
| ((#425,240),(#0,240),(#425,240),(#0,1280))*0
|-
! Hong Kong
| ((((#440)+(#480)),400),(#0,200),(((#440)+(#480)),400),(#0,3000))*0
| ((((#480)+(#620)),500),(#0,500))*0
| ((((#480)+(#620)),250),(#0,250))*0
| ''unused''
|-
! Netherlands 
| ((#425,1000),(#0,4000))*0 
| ((#425,500),(#0,500))*0 
| ((#425,250),(#0,250))*0 
| ''unused'' 
|-
! North America
| ((((#440)+(#480)),2000),(#0,4000))*0
| ((((#480)+(#620)),500),(#0,500))*0
| ((((#480)+(#620)),250),(#0,250))*0
| ((#1400),500)
|-
! Spain
| ((#425,1500),(#0,3000))*0
| ((#425,200),(#0,200))*0
| ((#425,200),(#0,200),(#425,200),(#0,200),(#425,200),(#0,600))*0
| (((#1400),400),(#0,5000))*0
|-
! United Kingdom
| ((((#400)+(#450)),400),(#0,200),(((#400)+(#450)),400),(#0,2000))*0
| ((#400,375),(#0,375))*0
| ((#400,400),(#0,350),(#400,225),(#0,525))*0
| ''unused''
|}

{| cellspacing="1" cellpadding="2" border="1"
|-
! The Moon...
| ((#262,2000),(#391,2000),(#523,4000),(((#659)+(#523)),250),(((#622)+(#523)),3750),(#262,400),(#196,400),(#262,400),(#196,400),(#262,400),(#196,400),(#262,400),(#196,400),(#262,420),(#196,460),(#262,540),(#196,620))*0
|}

=== Playing and collecting tones ===

To learn how to play these tones using the [[CAF: Working With Call Legs|Call Leg API]], refer to the [[CAF:_Working_With_Cmc_Call_Legs#Playing_and_Collecting_Tones|Playing and Collecting Tones section]].

For example, to play the '''ringing''' tone, one could pass either directly <code>((((#440)+(#480)),2000),(#0,4000))*0</code> or <code>cg/rt</code> to the '''AddToneString()''' function. The <code>cg/rt</code> string refers to the current Tone Profile Params ringing tone setting from the Web Portal.

=== Tone volume ===

It is possible to change the ring tone volume. According to the syntax, you need to specify the desired volume after the tone duration. Here is an example:
((((#440)+(#480)),2000,'''-15'''),(#0,4000))*0

The possible values are: -19, -15, -10, -5 and 0 dB.

=== Available tones ===

Below is a comprehensive list of all the tone strings that can be passed to the '''AddToneString()''' function.

{|
|-
| valign="top" |
{| cellspacing="1" cellpadding="2" border="1"
|+ '''Tone generation'''
|-
! Package
! Signal
! String
|-
| valign="top" rowspan="16" | Basic DTMF generation
| 0
| dg/d0
|-
| 1
| dg/d1
|-
| 2
| dg/d2
|-
| 3
| dg/d3
|-
| 4
| dg/d4
|-
| 5
| dg/d5
|-
| 6
| dg/d6
|-
| 7
| dg/d7
|-
| 8
| dg/d8
|-
| 9
| dg/d9
|-
| *
| dg/ds
|-
| #
| dg/do
|-
| A
| dg/da
|-
| B
| dg/db
|-
| C
| dg/dc
|-
| D
| dg/dd
|-
| valign="top" rowspan="4" | Call Progress generation
| Ring
| cg/rt
|-
| Busy
| cg/bt
|-
| Congestion
| cg/ct
|-
| Warning
| cg/wt
|-
| valign="top" rowspan="12" | MF tone generation
| 0
| mfg/mf0
|-
| 1
| mfg/mf1
|-
| 2
| mfg/mf2
|-
| 3
| mfg/mf3
|-
| 4
| mfg/mf4
|-
| 5
| mfg/mf5
|-
| 6
| mfg/mf6
|-
| 7
| mfg/mf7
|-
| 8
| mfg/mf8
|-
| 9
| mfg/mf9
|-
| KP
| mfg/mfa
|-
| ST
| mfg/mfe
|-
| valign="top" rowspan="3" | Telcofax
| CNG
| telcofax/cng
|-
| g164
| telcofax/g164
|-
| g165
| telcofax/g165
|}

| valign="top" |
{| cellspacing="1" cellpadding="2" border="1"
|+ '''Tone detection'''
|-
! Package
! Signal
! String
|-
| valign="top" rowspan="16" | Basic DTMF detection
| 0
| dd/d0
|-
| 1
| dd/d1
|-
| 2
| dd/d2
|-
| 3
| dd/d3
|-
| 4
| dd/d4
|-
| 5
| dd/d5
|-
| 6
| dd/d6
|-
| 7
| dd/d7
|-
| 8
| dd/d8
|-
| 9
| dd/d9
|-
| *
| dd/ds
|-
| #
| dd/do
|-
| A
| dd/da
|-
| B
| dd/db
|-
| C
| dd/dc
|-
| D
| dd/dd
|-
| valign="top" rowspan="12" | MF tone generation
| 0
| mfd/mf0
|-
| 1
| mfd/mf1
|-
| 2
| mfd/mf2
|-
| 3
| mfd/mf3
|-
| 4
| mfd/mf4
|-
| 5
| mfd/mf5
|-
| 6
| mfd/mf6
|-
| 7
| mfd/mf7
|-
| 8
| mfd/mf8
|-
| 9
| mfd/mf9
|-
| KP
| mfd/mfa
|-
| ST
| mfd/mfe
|-
| valign="top" rowspan="7" | Telcofax
| CNG
| telcofax/cng
|-
| g164
| telcofax/g164
|-
| g165
| telcofax/g165
|-
| ansam
| telcofax/ansam
|-
| phase_rev_ansam
| telcofax/phase_rev_ansam
|-
| v21_flags
| telcofax/v21_flags
|-
| bell_ans
| telcofax/bell_ans
|}

|}

=== References ===

*[http://www.itu.int/publ/T-SP-E.180-2003/en Various tones used in national networks]
*[http://www.itu.int/rec/T-REC-H.248.6-200011-I/en H.248 Gateway Control Protocol Dynamic Tone Definition Package]
*[http://www.itu.int/rec/T-REC-H.248.1-200509-I/en H.248 Gateway Control Protocol] section E.7 (Call Progress Tone Definitions Package)

[[Category:Needs_revising]]

VoIP Bonding

2014-10-20T08:35:38Z

Martin Provencher: Fix the table display

VoIP Bonding refers to the capability of Tmedia units to use the two available VoIP Ethernet ports as a bonding pair. When the active port becomes unusable (cable disconnected, limited connectivity), the other port is used to transport Ethernet traffic.

Starting with Toolpack release 2.7.34, VoIP Bonding is available as a feature for Tmedia units. Detection of offline ports is currently achieved through two methods:
# Ethernet PHY polling to quickly discover if a cable is connected or not to the unit;
# Sending IPv4 ping requests to a known host to ensure that a logical IP path is available to the unit.

The voip0 (first VoIP port) MAC and IP addresses are used on both VoIP ports of the Tmedia unit when VoIP bonding is activated. However, in that mode, the voip1 port MAC and IP address are not usable (i.e. protocol stacks assigned to voip1 will not work and voip1 will not respond to ICMP requests). Therefore, IP services and stacks (such as SIP, SIGTRAN and port ranges) must be assign to voip0 only.

The VoIP Bonding feature also makes the Tmedia units report the bonding state as the voip0 port state. For instance, the IPv4 statistics reported by the Web Portal for voip0 are actually for the bonding pair. The PHY state is also for the bonding pair (so it would only be down if both voip ports are down). To know the true state of the physical voip0 and voip1 ports, the SNMP protocol must be used.

The feature has no effect on Virtual IP Interfaces configured in the Web Portal. Virtual IP Interfaces configured on either voip0 or voip1 physical ports still work exactly the same whether VoIP Bonding is activated.

== Web Portal Display ==

==== VoIP0 Port Status ====
Since VoIP0 and VoIP1 are bonded together, VoIP0 represents an aggregated status of the bonded ports. This means VoIP0 will be shown as "RED" only if both VoIP0 and VoIP1 ports are unavailable.

==== VoIP1 Port Status ====
VoIP1 port status represents its own physical connectivity.

==== Web Portal Ports Display Status ====
{| cellspacing="0" cellpadding="4" border="1" class="wikitable"
|-
! scope="col" |
! scope="col" colspan="4" | Physical Connectivity
|-
! bgcolor="#DDDDDD" rowspan="1" scope="row" | VoIP0 Interface
| scope="col" | UP
| scope="col" | UP
| scope="col" | DOWN
| scope="col" | DOWN
|-
! bgcolor="#DDDDDD" rowspan="1" scope="row" | VoIP1 Interface
| scope="row" | UP
| scope="row" | DOWN
| scope="row" | UP
| scope="row" | DOWN
|-
! scope="col" |
! bgcolor="#DDDDDD" colspan="4" scope="col" | Web Portal Port Status
|-
! bgcolor="#DDDDDD" rowspan="1" scope="row" | VoIP0 (Bonded Status)
| scope="col" | GREEN
| scope="col" | GREEN
| scope="col" | GREEN
| scope="col" | RED
|-
! bgcolor="#DDDDDD" rowspan="1" scope="row" | VoIP1
| scope="row" | GREEN
| scope="row" | RED
| scope="row" | GREEN
| scope="row" | RED
|}

== Configuration ==

*[[Web_Portal_Tutorial_Guide_v2.7#VoIP_Bonding|Toolpack 2.7: VoIP Bonding]]

Tctrl Version 2.8

2014-09-19T16:06:25Z

Martin Provencher: Fix english syntax

== 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;" | SNMP: Support new MIBs and traps
| -
| 2.8
|-
| style="text-align:left;" | Support for VLAN
| -
| 2.8
|-
| style="text-align:left;" | Support IP Bonding from Webportal
| -
| 2.8
|-
| style="text-align:left;" | Support Multiple IP Addresses per IP port
| -
| 2.8
|-
| style="text-align:left;" | Unlock eth0/eth1 IP ports for calls
| -
| 2.8
|-
| style="text-align:left;" | NAT: More services on same IP address
| -
| 2.8
|-
| style="text-align:left;" | PPPoE Tunnel
| 15958
| 2.8
|-
! colspan="3" | H.248
|-
| style="text-align:left;" | Support Digitmap Package
| -
| 2.8
|-
! colspan="3" | Fax
|-
| style="text-align:left;" | Support V.152: Autoswitch to VBD (gpmd)
| -
| 2.8
|-
! colspan="3" | Operation, Administration and Maintenance (OAM)
|-
| style="text-align:left;" | New Look & Feel for Web Configuration Tool
| -
| 2.8
|-
| style="text-align:left;" | Major Upgrade
| 13773
| 2.8
|-
| style="text-align:left;" | Tone Definition Profile
| -
| 2.8
|-
! colspan="3" | Routing
|-
! colspan="3" | Protocol Adaptation
|-
! colspan="3" | Development Platform
|-
! colspan="3" | New Products
|}

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

Tctrl Version 2.8

2014-09-19T15:49:36Z

Martin Provencher: Create de Toolpack 2.8 page for new main features

== 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;" | SNMP: Support new MIBs and traps
| -
| 2.8
|-
| style="text-align:left;" | Support for VLAN
| -
| 2.8
|-
| style="text-align:left;" | Support IP Bonding from Webportal
| -
| 2.8
|-
| style="text-align:left;" | Support Multiple IP Address per IP port
| -
| 2.8
|-
| style="text-align:left;" | Unlock eth0/eth1 IP ports for calls
| -
| 2.8
|-
| style="text-align:left;" | NAT: More services on same IP address
| -
| 2.8
|-
| style="text-align:left;" | PPPoE Tunnel
| 15958
| 2.8
|-
! colspan="3" | H.248
|-
| style="text-align:left;" | Support Digitmap Package
| -
| 2.8
|-
! colspan="3" | Fax
|-
| style="text-align:left;" | Support V.152: Autoswitch to VBD (gpmd)
| -
| 2.8
|-
! colspan="3" | Operation, Administration and Maintenance (OAM)
|-
| style="text-align:left;" | New Look & Feel for Web Configuration Tool
| -
| 2.8
|-
| style="text-align:left;" | Major Upgrade
| 13773
| 2.8
|-
| style="text-align:left;" | Tone Definition Profile
| -
| 2.8
|-
! colspan="3" | Routing
|-
! colspan="3" | Protocol Adaptation
|-
! colspan="3" | Development Platform
|-
! colspan="3" | New Products
|}

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

Live signalling capture by tbsigtrace

2014-09-02T17:37:28Z

Martin Provencher: Change the tbsigtrace_2_7_10 to use the default tbsigtrace command on all new units

You can now activate tbsigtrace and pipe it directly in wireshark through SSH to get a live capture SS7, ISDN or IP (not all in the same wireshark window).

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

The procedure is as following:

==== Download plink ====

Download plink - http://the.earth.li/~sgtatham/putty/latest/x86/plink.exe
Place it in C:\Program Files\Putty directory

==== Download tbsigtrace version 2.7 ====
If not using at least version 2.7, download the attached tbsigtrace on unit (/root directory or any other valid directory)
{| 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;" |CentOS version
! 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;" |ppc version
|-
| valign="top" |
*[[Media:tbsigtrace_2_7_10_centos.rar|tbsigtrace_2_7_10_centos ]]
| valign="top" |
*[[Media:tbsigtrace_2_7_10_ppc.rar|tbsigtrace_2_7_10_ppc]]
|}
'''Note:''' Unzip the file so that it gives you the executable file tbsigtrace_2_7_10_centos or tbsigtrace_2_7_10_ppc.

===== Upload tbsigtrace to toolpack server =====

Rename tbsigtrace_2_7_10_centos or tbsigtrace_2_7_10_ppc to "tbsigtrace_2_7" and upload it to the toolpack server /root directory or any other valid directory. In the command below, replace ''tbsigtrace'' by ''/root/tbsigtrace_2_7''

=== Execute the command to capture the signalling accordingly ===
===== For SS7 capture =====
plink.exe -ssh root@[IP_of_management_port] -P [ssh_port] -pw [ssh_password] "tbsigtrace -adapter TB00xxxx -stdout -ss7" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

ex.
plink.exe -ssh root@10.10.10.10 -P 22 -pw mypassword "tbsigtrace -adapter TB005052 -stdout -ss7" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For ISDN capture =====
plink.exe -ssh root@[IP_of_management_port] -P [ssh_port] -pw [ssh_password] "tbsigtrace -adapter TB00xxxx -stdout -isdn" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

ex.
plink.exe -ssh root@10.10.10.10 -P 22 -pw mypassword "tbsigtrace -adapter TB005052 -stdout -isdn" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For SIP or SIGTRAN capture =====
plink.exe -ssh root@[IP_of_management_port] -P [ssh_port] -pw [ssh_password] "tbsigtrace -adapter TB00xxxx -stdout -ip" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

ex.
plink.exe -ssh root@10.10.10.10 -P 22 -pw mypassword "tbsigtrace -adapter TB005052 -stdout -ip" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For Radius, SNMP or H.248 capture =====
plink.exe -ssh root@[IP_of_management_port] -P [ssh_port] -pw [ssh_password] "tcpdump -i mgmt0 -s 0 -w -" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

ex.
plink.exe -ssh root@10.10.10.10 -P 22 -pw mypassword "tcpdump -i mgmt0 -s 0 -w -" | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

Support:Submitting An Issue

2014-09-02T17:29:34Z

Martin Provencher: Revert last "bugzilla" changes

TelcoBridges supports a wide variety of [[Supported operating systems|operating systems]] and versions. However, with such variety comes a certain amount of complexity. Consequently, when submitting a problem, your ability to provide relevant information about your system will greatly help the TelcoBridges support team in its efforts to bring to you a quick resolution.

 

== Required information: System configuration ==

Please provide the following required information:

 '''Description of the issue'''
*Describe the issue and clearly as possible and with as much details possible.
*Describe the steps or context in which the issues was experienced.
*Provide steps to reproduce the issue, if possible.
*Tracking number (If one was already provided to you by TelcoBridges TB Support)

 '''System information'''
*Type of TelcoBridges hardware device(s) (ex. [[TMP6400]], [[TMG3200]], etc.)
*Serial numbers of TelcoBridges hardware units (ex. TB00xxxxx)
*Topology diagram, call flow diagram, IP network and connectivity diagram, etc. Depending on the issue reported, those information could be critical for the team to properly understand the environment in which you system is working.

 '''System configuration / set-up'''

*Configuration summary (ex. SIP to SS7, MGC + H.248, SIP to ISDN, ect.).
**Provide the system configuration (see https://docs.telcobridges.com/tbwiki/Troubleshooting_Toolpack#System_configuration_backup).
*Toolpack/TMG-CONTROL software release number (ex. 2.3.8)
*Operating system version and architecture upon which the TelcoBridges software is running (e.g., CentOS 5.2 32bits, Debian 4 64bits, TMG3200(TBLinux), etc.)

 '''Troubleshooting capture '''

*Call trace, low-level signalling capture, Toolpack applications logs, etc. See https://docs.telcobridges.com/tbwiki/Troubleshooting

 '''Application information ''(for TDev customer and Solution developers)'''''

*What does your application do? (e.g., [[Transcoding]], [[Ringback tones]], [[IVR]], etc.)
*Are you using [[Toolpack]] for telephony functions?
**If 'Yes', are you using your own application?
**If 'No', do you use callctrl libs?, ha_manager?
*Application schematic
**Please provide a complete diagram that explains with boxes, arrows, and text, how the system works. Please provide IP addresses, point codes of each component when applicable

 

== Logging the issue in TBsupport tracking system ==

Once you have gathered all of the information required above, please log it in the TBsupport tracking system (bugzilla) here: 

[https://support.telcobridges.com https://support.telcobridges.com] 

This will assign to you a tracking number to follow the progress of the issue. Your account e-mail will receive an update on each comment that is logged. 

If you do not have a TBsupport tracking system account, please request one at support@telcobridges.com at the same time as sending the information for the issue.

 

== Providing remote access to your system ==

If you choose to provide TelcoBridges with remote access to your system for the purpose of issue analysis and resolution, please be prepared to provide us with the following information:

*Type of connection (VPN, Microsoft Remote Desktop, SSH, GoToMeeting, etc.)
*IP Address, if applicable
*User name, if applicable
*Password, if applicable

Support:Submitting An Issue

2014-09-02T17:27:31Z

Martin Provencher: Add "bugzilla" test 2

TelcoBridges supports a wide variety of [[Supported operating systems|operating systems]] and versions. However, with such variety comes a certain amount of complexity. Consequently, when submitting a problem, your ability to provide relevant information about your system will greatly help the TelcoBridges support team in its efforts to bring to you a quick resolution.

 

== Required information: System configuration ==

Please provide the following required information:

 '''Description of the issue'''
*Describe the issue and clearly as possible and with as much details possible.
*Describe the steps or context in which the issues was experienced.
*Provide steps to reproduce the issue, if possible.
*Tracking number (If one was already provided to you by TelcoBridges TB Support)

 '''System information'''
*Type of TelcoBridges hardware device(s) (ex. [[TMP6400]], [[TMG3200]], etc.)
*Serial numbers of TelcoBridges hardware units (ex. TB00xxxxx)
*Topology diagram, call flow diagram, IP network and connectivity diagram, etc. Depending on the issue reported, those information could be critical for the team to properly understand the environment in which you system is working.

 '''System configuration / set-up'''

*Configuration summary (ex. SIP to SS7, MGC + H.248, SIP to ISDN, ect.).
**Provide the system configuration (see https://docs.telcobridges.com/tbwiki/Troubleshooting_Toolpack#System_configuration_backup).
*Toolpack/TMG-CONTROL software release number (ex. 2.3.8)
*Operating system version and architecture upon which the TelcoBridges software is running (e.g., CentOS 5.2 32bits, Debian 4 64bits, TMG3200(TBLinux), etc.)

 '''Troubleshooting capture '''

*Call trace, low-level signalling capture, Toolpack applications logs, etc. See https://docs.telcobridges.com/tbwiki/Troubleshooting

 '''Application information ''(for TDev customer and Solution developers)'''''

*What does your application do? (e.g., [[Transcoding]], [[Ringback tones]], [[IVR]], etc.)
*Are you using [[Toolpack]] for telephony functions?
**If 'Yes', are you using your own application?
**If 'No', do you use callctrl libs?, ha_manager?
*Application schematic
**Please provide a complete diagram that explains with boxes, arrows, and text, how the system works. Please provide IP addresses, point codes of each component when applicable

 

== Logging the issue in TBsupport tracking system ==

Once you have gathered all of the information required above, please log it in the TBsupport tracking system ( bugzilla ) here: 

[https://support.telcobridges.com https://support.telcobridges.com] 

This will assign to you a tracking number to follow the progress of the issue. Your account e-mail will receive an update on each comment that is logged. 

If you do not have a TBsupport tracking system account, please request one at support@telcobridges.com at the same time as sending the information for the issue.

 

== Providing remote access to your system ==

If you choose to provide TelcoBridges with remote access to your system for the purpose of issue analysis and resolution, please be prepared to provide us with the following information:

*Type of connection (VPN, Microsoft Remote Desktop, SSH, GoToMeeting, etc.)
*IP Address, if applicable
*User name, if applicable
*Password, if applicable

Support:Submitting An Issue

2014-09-02T17:26:51Z

Martin Provencher: Add "bugzilla"

Support:Contacting TelcoBridges technical support

2014-07-21T18:58:13Z

Martin Provencher: Bolded telephone numbers

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 2014
|-
|New Year's day
|January 1, 2014
|-
|Day After New Year's day
|January 2, 2014
|-
|Good Friday
|April 18, 2014
|-
|Easter Monday
|April 21, 2014
|-
|Patriotes
|May 19, 2014
|-
|St-Jean
|June 24, 2014
|-
|Canada Day
|July 1, 2014
|-
|Labour day
|September 1, 2014
|-
|Thanksgiving
|October 13, 2014
|-
|Christmas
|December 25, 2014
|-
|Boxing Day
|December 26, 2014
|}

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

Live signalling capture by tbsigtrace

2014-07-10T15:39:18Z

Martin Provencher: Split code into multiple 'pre' + layout

You can now activate tbsigtrace and pipe it directly in wireshark through SSH to get a live capture SS7, ISDN or IP (not all in the same wireshark window).

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

The procedure is as following:

==== Download plink ====

Download plink - http://the.earth.li/~sgtatham/putty/latest/x86/plink.exe
Place it in C:\Program Files\Putty directory

==== Download tbsigtrace version 2.7 ====
If not using version 2.7, download the attached tbsigtrace on unit (/root directory or any other valid directory)
{| 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;" |CentOS version
! 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;" |ppc version
|-
| valign="top" |
*[[Media:tbsigtrace_2_7_10_centos.rar|tbsigtrace_2_7_10_centos ]]
| valign="top" |
*[[Media:tbsigtrace_2_7_10_ppc.rar|tbsigtrace_2_7_10_ppc]]
|}
'''Note:''' Unzip the file so that it gives you the executable file tbsigtrace_2_7_10_centos or tbsigtrace_2_7_10_ppc.

==== Upload tbsigtrace to toolpack server ====

Rename tbsigtrace_2_7_10_centos or tbsigtrace_2_7_10_ppc to "tbsigtrace_2_7_10" and upload it to the toolpack server /root directory or any other valid directory.

==== Execute the command to capture the signalling accordingly ====
===== For SS7 capture =====
plink.exe -ssh root@[IP_of_management_port] -P [ssh_port] -pw [ssh_password] [dir]/tbsigtrace_2_7_10 -adapter TB00xxxx -stdout -ss7 | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

ex.
plink.exe -ssh root@10.10.10.10 -P 22 -pw mypassword /root/tbsigtrace_2_7_10 -adapter TB005052 -stdout -ss7 | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For ISDN capture =====
plink.exe -ssh root@[IP_of_management_port] -P [ssh_port] -pw [ssh_password] [dir]/tbsigtrace_2_7_10 -adapter TB00xxxx -stdout -isdn | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

ex.
plink.exe -ssh root@10.10.10.10 -P 22 -pw mypassword /root/tbsigtrace_2_7_10 -adapter TB005052 -stdout -isdn | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For SIP or SIGTRAN capture =====
plink.exe -ssh root@[IP_of_management_port] -P [ssh_port] -pw [ssh_password] [dir]/tbsigtrace_2_7_10 -adapter TB00xxxx -stdout -ip | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

ex.
plink.exe -ssh root@10.10.10.10 -P 22 -pw mypassword /root/tbsigtrace_2_7_10 -adapter TB005052 -stdout -ip | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

===== For Radius, SNMP or H.248 capture =====
plink.exe -ssh root@[IP_of_management_port] -P [ssh_port] -pw [ssh_password] tcpdump -i mgmt0 -s 0 -w - | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

ex.
plink.exe -ssh root@10.10.10.10 -P 22 -pw mypassword tcpdump -i mgmt0 -s 0 -w - | "C:\Program Files\Wireshark\wireshark.exe" -k -i -

Toolpack version history

2014-06-06T19:53:21Z

Martin Provencher: Add Revise on Major

Release notes for the following versions of Toolpack are available:
*[[Toolpack version 2.5|Version 2.5]] (Released September 2010)
*[[Toolpack version 2.4|Version 2.4]] (Released November 2009)
*[[Toolpack version 2.3|Version 2.3]] (Released July 2009)

[[Category:Tdev_OAM%26P|Version History]]
[[Category:Revise on Major]]

Toolpack: How to Use RegEx in Remapped Called and Calling Number Mask

2014-02-18T14:35:58Z

Martin Provencher: Add an example for independent regex (example 3)

== Regular Expressions ==
A regular expression is a sequence of characters that forms a search and replace pattern. This is useful to modify the called or calling number digit strings. The version used in the TelcoBridges units is based on PERL regular expression.

== The Rule ==
The remapped called number mask or remapped calling number mask must have 2 regular expressions, and it must be in the form of '/regexWithCapturingGroup/replaceString/'. In the first regular expression, you specify capturing groups using parentheses (...) while in the second regular expression, you specify how to remap the number by referencing the capturing group using \1, \2, etc.

Please refer to [[Toolpack: Commonly Used Regular Expression Pattern|Commonly Used Regular Expression Pattern]] for the patterns usually used.

=== Example 1 ===
If you need to match a called number starts with the digits 450 and then 7 other digits, please put this in the called number mask:

/^450[0-9]{7}$/

^ means the matching is done from the beginning of the number. 
$ means the matching is done to the end of then number. 
450 is the exact prefix to match. 
[0-9]{7} means there should be 7 occurrences of the digits 0 to 9. [1-9]{7} would mean 7 digits, excluding 0.

=== Example 2 ===
In this example, we have to match a called number starts with optional 1, then digits 450 and then 7 other digits.

/^1?450[0-9]{7}$/

? means the preceding pattern, i.e. the digit '1', is optional.

=== Example 3 ===
In this example, we have to match a called number with 4 possible prefixes followed by 7 other digits.

/^(800|888|877|866)[0-9]{7}/

In this example, we have 2 independent regular expression. The first one match prefix '800' with 7 digits, second match prefix '88' with 8 digits.

/^800[0-9]{7}$|^88[0-9]{8}$/

The | (pipe character) means "or"

=== Example 4 ===
In this example, we have to match a called number with a prefix followed by 6 to 11 digits.

/^880([0-9]{6,11})$/

=== Example 5 ===
In this example, we want to match any digit string that doesn't start with 080.

/^(?!080)([0-9]*)$/
The ?! is the not operator (everything except this)

=== Example 6 ===
In the remapped called number mask, the following is specified:

/^(1?)450([0-9]{7})$/\1514\2/

The first regular expression is '^(1?)450([0-9]{7})$'. There are 2 capturing groups. The first one is '(1?)', the optional digit '1'. The second one is '([0-9]{7})', the 7 digits following '450'.

The second regular expression is '\1514\2' which specifies how the remapped number is composed.
In this example, let us suppose that the incoming call has the called number as '15141234567'. The digit '1' in the beginning matches the first capturing group '(1?)' and the digits '1234567' match the second capturing group '([0-9]{7})'. Therefore, the remapped called number would be '1' followed by '514' followed by '1234567', that is '15141234567'.

=== Example 7 ===
This is a simpler example in which the remapped called number mask would remove the prefix '852' while keeping the 8 digits following the prefix.

/^852([0-9]{8})$/\1/
First group between parenthesis are the 8 digits after the 852. The output number will be the 8 digits after 852 (represented by the first group "\1" used in the seconds section of the regex)

== Related Links ==
*[[Toolpack: Commonly Used Regular Expression Pattern|Commonly Used Regular Expression Pattern]]
*[http://www.cs.tut.fi/~jkorpela/perl/regexp.html Regular expressions in Perl]

== Caution ==

It is recommended to use ^ and $ to specify the matching of beginning and end of the number if it is appropriate so as to avoid ambiguity in matching.
For example, if you specify the mask as /450[0-9]{7}/, the following numbers would match this mask and that may not be desirable.
*864501234567 (the later part of the number matches the mask)
*4501234567890 (more than 7 digits after '450' is still a match)

Voice codecs

2014-01-29T14:59:42Z

Martin Provencher: Fix the table colors with the new CSS

TelcoBridges products support the following voice codecs.

=== Supported codecs ===
 

*'''Universal codecs'''
**[http://en.wikipedia.org/wiki/G.711 G.711] - Supported packet durations: 20,30,40,50 and 60 msec
**[http://en.wikipedia.org/wiki/G.723.1 G.723.1] - Supported packet durations: 30,60 and 90 msec
**[http://en.wikipedia.org/wiki/G.726 G.726] - Supported packet durations: 20,30,40,50 and 60 msec
**[http://en.wikipedia.org/wiki/G.729 G.729a/ab] - Supported packet durations: 20,30,40,50,60,70 and 80 msec
**[http://en.wikipedia.org/wiki/T.38 T.38]

*'''Wireline codecs'''
**[http://en.wikipedia.org/wiki/G.728 G.728] - Supported packet durations: 20,30,40,50 and 60 msec
**[http://en.wikipedia.org/wiki/G.729 G.729eg] - Supported packet durations: 20,30,40,50,60,70 and 80 msec
**[http://en.wikipedia.org/wiki/Internet_Low_Bit_Rate_Codec iLBC] - Supported packet durations: [13kbps] 30 and 60 msec, [15kpbs] 20 and40 msec

*'''Wireless codecs''' '''1'''
**[http://en.wikipedia.org/wiki/Adaptive_multi-rate_compression AMR] - Supported packet durations: 20,40,60 and 80 msec
**[http://en.wikipedia.org/wiki/Full_Rate GSM-FR] - Supported packet durations: 20 and 30 msec
**[http://en.wikipedia.org/wiki/Enhanced_Full_Rate GSM-EFR] - Supported packet durations: 20,40 and 60 msec
**[http://en.wikipedia.org/wiki/EVRC EVRC] - Supported packet durations: 20,40 and 60 msec
**[http://en.wikipedia.org/wiki/QCELP QCELP] - Supported packet durations: 20,40 and 60 msec
**[[G.722.2 (AMR-WB)]] - Supported packet durations: 20,40,60 and80 msec

=== Codec density ===
 

==== Mixed mode ====

The following density can be achieve when codec mix is dynamically negotiated.
{| cellpadding="5" border="1" class="wikitable" style="text-align: center"
|-
! width="150" rowspan="2" | Type of
VoIP mezzanine
! width="400" colspan="5" | Universal codecs
! width="240" colspan="3" | Other codecs
! width="320" colspan="4" | Wireless codecs'''1'''
|-
! width="80" | G.711
! width="80" | G.723.1
! width="80" | G.726
! width="80" | G.729ab
! width="80" | T.38
! width="80" | G.728
! width="80" | G.729eg
! width="80" | iLBC
! width="80" | AMR
! width="80" | AMR-WB
! width="80" | GSM-FR/GSM-EFR
! width="80" | EVRC/QCELP
|-
| TM-VOIP-1
| 341
| 127
| 169
| 154
| 127
| 58
| 64
| 75
| 91
| 59
| 107
| 95
|-
| TM-VOIP-2
| 682
| 254
| 338
| 308
| 254
| 116
| 128
| 150
| 182
| 118
| 214
| 190
|-
| TM-VOIP-3
| 1023
| 381
| 507
| 462
| 381
| 174
| 192
| 225
| 273
| 177
| 321
| 285
|-
| TM-VOIP-4
| 1364
| 508
| 676
| 616
| 508
| 232
| 256
| 300
| 364
| 236
| 428
| 380
|}

==== Fixed mode ====

The following density can be achieve when codec mix is predefined.
{| cellpadding="5" border="1" class="wikitable" style="text-align: center"
|-
! width="150" rowspan="2" | Type of.
VoIP mezzanine
! width="400" colspan="5" | Universal codecs
! width="240" colspan="3" | Other codecs
! width="320" colspan="4" | Wireless codecs'''1'''
|-
! width="80" | G.711.
! width="80" | G.723.1
! width="80" | G.726
! width="80" | G.729ab
! width="80" | T.38
! width="80" | G.728
! width="80" | G.729eg
! width="80" | iLBC
! width="80" | AMR
! width="80" | AMR-WB
! width="80" | GSM-FR/GSM-EFR
! width="80" | EVRC/QCELP
|-
| TM-VOIP-1
| 404
| 128
| 200
| 168
| 128
| 66
| 72
| 84
| 102
| 60
| 120
| 96
|-
| TM-VOIP-2
| 808
| 256
| 400
| 336
| 256
| 132
| 144
| 168
| 204
| 120
| 240
| 192
|-
| TM-VOIP-3
| 1212
| 384
| 600
| 504
| 384
| 198
| 216
| 252
| 306
| 180
| 360
| 288
|-
| TM-VOIP-4
| 1616
| 512
| 800
| 672
| 512
| 264
| 288
| 336
| 408
| 240
| 480
| 384
|}

['''1'''] May require additional licenses

[[Category:Glossary]]
[[Category:Tmedia_Features|Voice Codecs]]
[[Category:Tdev_Features|Voice Codecs]]
[[Category:Needs_revising]]

Tmedia Comparison

2014-01-17T20:26:24Z

Martin Provencher: Clean the header of the tables

The following tables campare the similarities and differences between the various models within the Tmedia family of VoIP gateways.

== Hardware Capacities ==
Each model has been designed to address different system size; small (32-256 bridges), mid (256-2016) and large (256-32768).

Here is comparison table, presenting the different Tmedia models and their capacities:

{| cellpadding="5" border="1" class="wikitable" style="text-align: center;"
|-
! rowspan="2" style="border-right: none" |
! colspan="3" style="border-left: none" | Models
|-
| [[TMG800]]
| [[TMG3200]]
| [[TMG7800]]
|-
| width="210" | [[T1,_E1,_and_J1_interfaces|T1/E1]]
| width="210" | 1-8
| width="210" | 8-64
| width="210" | 16-1024
|-
| [[DS3_interfaces|DS3]]
| {{Check_X_Mark|}}
| 1-3
| 1-48
|-
| [[SONET/SDH_interfaces|STM1/OC3]]
| {{Check_X_Mark|}}
| 1
| 1-16
|-
| VoIP Channels Capacity
| 32 - 256
| 256 - 2016
| 512 - 32768
|-
| VoIP Gigabit Port
| 2
| 2
| 2
|-
| Managment Port
| 1
| 1
| 2
|-
| Form Factors
| 1 U
| 2 U
| 4-39 U
|-
| Redundant Power Supplies
(AC or DC)
| Optional
| Standard
| Standard
|}

== Unified Platform ==

Other than capacity, all Tmedia models share the same feature sets.

{| cellpadding="5" border="1" class="wikitable" style="text-align: center"
|-
! rowspan="2" style="border-right: none" |
! colspan="3" style="border-left: none" | Models
|-
| [[TMG800]]
| [[TMG3200]]
| [[TMG7800]]
|-
| width="210" | [[H.248]] and/or
[[TMG call control]]
| width="210" | {{Check_X_Mark| Y}}
| width="210" | {{Check_X_Mark| Y}}
| width="210" | {{Check_X_Mark| Y}}
|-
| [[Text_Call_Detail_Records_(CDR)|Text CDR]]
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
|-
| [[RADIUS]]
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
|-
| [[Web Base OAM&P]]
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
|-
| [[Voice_codecs|Universal Codecs]]
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
|-
| Protocols run on the same device
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
|-
| [[SIP]]
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
|-
| [[SIGTRAN]]
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
|-
| [[SS7]]
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
|-
| [[ISDN|ISDN PRI]]
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
|-
| [[CAS|CAS R2]]
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
|}

Tmedia Comparison

2014-01-17T20:21:10Z

Martin Provencher: FIx the layout by removing the colors in CSS and cleaning non-needed CSS

The following tables campare the similarities and differences between the various models within the Tmedia family of VoIP gateways.

== Hardware Capacities ==
Each model has been designed to address different system size; small (32-256 bridges), mid (256-2016) and large (256-32768).

Here is comparison table, presenting the different Tmedia models and their capacities:

{| cellpadding="5" border="1" class="wikitable" style="text-align: center;"
|-
| rowspan="2" |
! colspan="3" | Models
|-
| [[TMG800]]
| [[TMG3200]]
| [[TMG7800]]
|-
| width="210" | [[T1,_E1,_and_J1_interfaces|T1/E1]]
| width="210" | 1-8
| width="210" | 8-64
| width="210" | 16-1024
|-
| [[DS3_interfaces|DS3]]
| {{Check_X_Mark|}}
| 1-3
| 1-48
|-
| [[SONET/SDH_interfaces|STM1/OC3]]
| {{Check_X_Mark|}}
| 1
| 1-16
|-
| VoIP Channels Capacity
| 32 - 256
| 256 - 2016
| 512 - 32768
|-
| VoIP Gigabit Port
| 2
| 2
| 2
|-
| Managment Port
| 1
| 1
| 2
|-
| Form Factors
| 1 U
| 2 U
| 4-39 U
|-
| Redundant Power Supplies
(AC or DC)
| Optional
| Standard
| Standard
|}

== Unified Platform ==

Other than capacity, all Tmedia models share the same feature sets.

{| cellpadding="5" border="1" class="wikitable" style="text-align: center"
|-
| rowspan="2" |
! colspan="3" | Models
|-
| [[TMG800]]
| [[TMG3200]]
| [[TMG7800]]
|-
| width="210" | [[H.248]] and/or
[[TMG call control]]
| width="210" | {{Check_X_Mark| Y}}
| width="210" | {{Check_X_Mark| Y}}
| width="210" | {{Check_X_Mark| Y}}
|-
| [[Text_Call_Detail_Records_(CDR)|Text CDR]]
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
|-
| [[RADIUS]]
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
|-
| [[Web Base OAM&P]]
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
|-
| [[Voice_codecs|Universal Codecs]]
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
|-
| Protocols run on the same device
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
|-
| [[SIP]]
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
|-
| [[SIGTRAN]]
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
|-
| [[SS7]]
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
|-
| [[ISDN|ISDN PRI]]
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
|-
| [[CAS|CAS R2]]
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
| {{Check_X_Mark| Y}}
|}

Tctrl Version 2.5

2014-01-17T19:58:52Z

Martin Provencher: FIx the layout by removing the colors in CSS and cleaning non-needed CSS

== New Features ==

[[TMG-CONTROL]] provides the following new features:

{| cellpadding="0" border="1" class="wikitable" style="text-align: center"
|-
! width="500" | Features
! width="150" | Enhancement'''1'''
! width="150" | Minor Release
|-
! colspan="3" | VoIP
|-
| style="text-align:left;" | Web portal parameter to enable V34 Faxes
| 10980
| 2.5.85
|-
! colspan="3" | Signaling
|-
| style="text-align:left;" | H.248 No-loss-of-service
| -
| 2.5.11
|-
| style="text-align:left;" | [[CAS|CAS R2]]
| -
| 2.5.11
|-
|style="text-align:left;" | [[Configure NFAS|ISDN NFAS]]
| -
| 2.5.100
|-
| style="text-align:left;" | [[Web_Portal_Tutorial_Guide_v2.5#SIGTRAN_Application_Scenarios|SIGTRAN IUA]]
| -
| 2.5.100
|-
| style="text-align:left;" | MTP3 support for multiple networks with same sub-service
| 11845
| 2.5.111
|-
| style="text-align:left;" | CAS R2 support dynamic changes of C and D bits
| 12311
| 2.5.120
|-
! colspan="3" | Network Redundancy
|-
| style="text-align:left;" | [[H.248 Network Redundancy|H.248 1+1 Network Redundancy]]
| 11287
| 2.5.104
|-
! colspan="3" | Signaling Interworking
|-
| style="text-align:left;" | Implement outgoing SS7 Continuity Testing (H.248 only)
| 6337
| 2.5.11
|-
| style="text-align:left;" | Add option to prevent 183 from generating alert
| 10239
| 2.5.23
|-
| style="text-align:left;" | Call progress tones playback
| 8150
| 2.5.43
|-
| style="text-align:left;"| Cause code mapping
| 10255
| 2.5.43
|-
| style="text-align:left;" | Support of text (ascii) format for UUI
| 10920
| 2.5.53
|-
| style="text-align:left;" | Configurable SS7/ISDN information transfer capability
| 11001
| 2.5.63
|-
| style="text-align:left;" | Blind (Unattended) Call Transfer for ISDN/ISUP to SIP
| -
| 2.5.80
|-
| style="text-align:left;" | Local number portability mapping
| 6263
| 2.5.100
|-
! colspan="3" | OAM/WEB
|-
| style="text-align:left;" | Helper to configure KLM or ITU ISUP CICS for STM/SONET
| 9411
| 2.5.66
|-
| style="text-align:left;" | [[SNMP|Support SNMP V2 and V3]]
| -
| 2.5.80
|-
| style="text-align:left;" | [[SNMP|Add SNMP ISDN MIB]]
| -
| 2.5.80
|-
| style="text-align:left;" | Support SNMP for multiple TMedia units
| -
| 2.5.89
|-
! colspan="3" | Routing
|-
| style="text-align:left;" | Tandem switch routing script
| 8222
| 2.5.11
|-
| style="text-align:left;" | [[Route retry|Route retry]]
| 6819
| 2.5.11
|-
| style="text-align:left;" | Add "redirecting number" to routing script
| 7937
| 2.5.28
|-
| style="text-align:left;" | Add SIP Custom Header insertion to routing script
| 11864
| 2.5.117
|-
|}

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

== Latest Detailed Release ==
The latest detailed release note is available at TelcoBridges forum.
*[http://forums.telcobridges.com/viewforum.php?f=23&sid=0b6d56e6e0b395824678a8f03e81e280 Release Status Forum]

== Minor Upgrades ==

It is considered a '''minor upgrade ''' when moving, for example, from upgrading a minor point release (e.g., v2.5.1 to v2.5.2).

*[[Tmedia_Minor_Upgrade|Minor upgrade procedure for TMG-CONTROL release v2.5]]

 

== License Upgrades ==

A '''license upgrade''' activates new functionality or capacity in the system. Example of license upgrades include adding or unlocking additional capabilities.

*[[Add/Change Licenses|License upgrade procedure for TMG-CONTROL release v2.5 (same as v2.3)]]

 

 

[[Category:Toolpack]]

Tctrl Version 2.7

2014-01-17T19:30:21Z

Martin Provencher: FIx the layout by removing the colors in CSS and cleaning non-needed CSS

== 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" | Minor 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;" | Outgoing COT testing
| 8710
| 2.7.26
|-
| style="text-align:left;" | [[VoIP_Bonding|VoIP Bonding]]
| 14595
| 2.7.34
|-
! colspan="3" | Fax
|-
| 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;" | [[NSE]]
| 12665
| 2.7.26
|-
! colspan="3" | OAM&P
|-
| 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
|-
! 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
|-
! 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
|}

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

CAS

2014-01-14T19:35:22Z

Martin Provencher: Fix a bad copy paste (CAS R1 => CAS R2) + Add space over CAS R2 title

Channel Associated Signaling is a signaling protocol for the set-up and tear-down of phone calls. It is different from other signaling protocols such as [[SS7]] in that it is not message/packet-based but rather based on bit transition for state changing, and tone transmission for information and state information exchange. In many parts of the world, CAS was first replaced by [[ISDN]] and in many cases, was ultimately replaced by SS7. Today, CAS is often used with low density trunks.

 

== CAS and TelcoBridges ==

TelcoBridges provides support for various CAS R1 and CAS R2 variants. Please contact TelcoBridges regarding support for additional CAS variants.

Please note that CAS support is limited to E1/T1/J1 interfaces. It is not compatible with DS-3 or STM-1 interfaces.

 

== CAS R1 ==
Toolpack supports various CASR1 variants, on T1 and E1 line interfaces.

The TelcoBridges CAS R1 stack features a scriptable register signaling engine that allows the complete customization of CAS R1 variants and call flows, including creation of new variants that are not provided with Toolpack.

Please refer to the following page for detailed information about [[CASr1_scripting|CASR1 script]]

Note: Support for CAS R1 has been introduced in Toolpack release 2.7.42. Please refer to [[Web Portal Tutorial Guide v2.7|Toolpack Web Portal v2.7]].

=== Supported CAS R1 variants ===
The following CAS variants are currently supported by the Toolpack:

*[[CAS_R1_E%26M|E&M "Wink start"]] (delay start, 1 wink or 2 winks)
*[[CAS_R1_LOOPSTART_USER|Loop start user side]]
*[[CAS_R1_LOOPSTART_NETWORK|Loop start network side]]

 

== CAS R2 ==
Toolpack supports various CASR2 variants E1 line interfaces.

The TelcoBridges CAS R2 stack features a scriptable register signaling engine that, in practice, allows the complete customization of communication processes using tones. More specifically, it is possible to modify the timing(s) of the tone exchanges, change the meaning(s) of each tone and dynamically specify the sequence in which the tones are played. The CAS R2 stack also provides integrated interoperability between variants and between other signaling types. For instance, the calling party category can be converted between variants and propagated to a SS7 call leg.

Note: Support for CAS R2 has been introduced in Toolpack release 2.5. Please refer to [[Web Portal Tutorial Guide v2.5|Toolpack Web Portal v2.5]].

=== Supported CAS R2 variants ===
The following CAS variants are currently supported by the Toolpack:

*Generic (ITU spec base)
*Brazil
*Mexico

Using Toolpack's script-based approach to the management of regional variants, variants supplied Toolpack can be adapted to address specific requirements and new variant scripts can be created from scratch, without to need to 'patch' or update the underlying system software version.

== References ==

*[[CASr1_scripting|CAS R1 Scripting guide]]
**[[CAS_R1_E%26M|CAS R1 E&M script]]
*[[CAS R2 scripting|CAS R2 Scripting guide]]
*[[Toolpack CAS R2 troubleshooting|CAS R2 Troubleshooting guide]]
*[http://en.wikipedia.org/wiki/Channel_Associated_Signaling Wikipedia article]
*[http://www.itu.int/rec/T-REC-Q.400-Q.490-198811-I ITU Q.400-Q.490 Specification]

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

Main Page

2013-12-18T16:15:44Z

Martin Provencher: FAQ is not an external link

__NoToC__'''Welcome to the TBwiki! [http://www.telcobridges.com TelcoBridges] has developed this wiki to help you with your product and service questions.'''

{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="210" style="background: none repeat scroll 0% 0% rgb(0, 83, 139);" colspan="2" |

Products

! width="210" style="background: none repeat scroll 0% 0% rgb(0, 83, 139);" |

OAM&P

! width="210" style="background: none repeat scroll 0% 0% rgb(0, 83, 139);" |

Features

! width="210" style="background: none repeat scroll 0% 0% rgb(0, 83, 139);" |

Solutions

|-

| width="80" style="background: none repeat scroll 0% 0% rgb(0, 83, 139); height: 121px" |
[[Tmedia|''T''media]]

| width="130" style="background: none repeat scroll 0% 0% rgb(255, 255, 255);" |
*[[TMG800]]
*[[TMG3200]]
*[[TMG7800]]
| style="background: none repeat scroll 0% 0% rgb(255, 255, 255);" rowspan="3"|

*[[Gateway_Installation|Installing]]
*[[Gateway_Upgrade|Upgrading]]
*[[Web Portal]]
[[:Category:Gateway_OAM&P|...more]]
| style="background: none repeat scroll 0% 0% rgb(255, 255, 255);" |

*[[Signaling_protocols|Signaling Protocols]]
*[[Redundancy_&_High_Availability|Redundancy & High Availability]]
*[[Tmedia_Routing|Routing]]
[[:Category:Tmedia_Features|...more]]
| style="background: none repeat scroll 0% 0% rgb(255, 255, 255);" |

*[[Carrier_Solutions|Carriers]]
*[[Operator_Solutions|Operators]]
*[[MVNO_&_MVNE_Solutions|MVNO & MVNE]]
*[[Call_Center_Solutions| Call Centers]]
|-
| width="80" style="background: none repeat scroll 0% 0% rgb(0, 83, 139); height: 80px" |
[[Ttrans|''T''trans]]

| width="130" style="background: none repeat scroll 0% 0% rgb(255, 255, 255);" |
*[[TMGIP800]]
*[[TMGIP3200]]
| style="background: none repeat scroll 0% 0% rgb(255, 255, 255);" |
*[[Voice_codecs|Voice Codecs]]
| style="background: none repeat scroll 0% 0% rgb(255, 255, 255);" |
*[[Transcoding_Gateway_Solutions|Transcoding]]
|-
| width="80" style="background: none repeat scroll 0% 0% rgb(0, 83, 139); height: 80px" |
[[Tsig|''T''sig]]

| width="130" style="background: none repeat scroll 0% 0% rgb(255, 255, 255);" |
*[[TSG800]]
*[[TSG3200]]
| style="background: none repeat scroll 0% 0% rgb(255, 255, 255);" |
*[[Signaling_protocols|Signaling Protocols]]
| style="background: none repeat scroll 0% 0% rgb(255, 255, 255);" |
*[[Signaling_Gateway_Solutions|Signaling]]
|-

| width="80" style="background: none repeat scroll 0% 0% rgb(0, 83, 139); height: 105px" |
[[Tdev|''T''dev]]

| width="130" style="background: none repeat scroll 0% 0% rgb(255, 255, 255);" |
*[[TMP800]]
*[[TMP6400]]
*[[TMP6400-CTRL]]
*[[TMP6400-TMS]]
| style="background: none repeat scroll 0% 0% rgb(255, 255, 255);" |
*[[Installing Toolpack|Installing]]
*[[Upgrading Toolpack|Upgrading]]
*[[Toolpack_Web_Portal|Provisioning]]
[[:Category:Tdev_OAM%26P|...more]]
| style="background: none repeat scroll 0% 0% rgb(255, 255, 255);" |
*[[High_Availability_Overview|Redundancy & High Availability]]
*[[Tdev_Signaling_Protocols|Signaling Protocols]]
*[[Voice_codecs|Voice Codecs]]
[[:Category:Tdev_Features|...more]]
| style="background: none repeat scroll 0% 0% rgb(255, 255, 255);" |
*[[Prepaid & postpaid calling|Prepaid & Postpaid Calling]]
*[[Ringback tones|Ringback Tones]]
*[[Unified communications|Unified Communications]]
[[:Category:Tdev_Solutions|...more]]
|-
| width="80" style="background: none repeat scroll 0% 0% rgb(0, 83, 139); height: 80px" |
[[Tmonitor|''T''monitor]]

| width="130" style="background: none repeat scroll 0% 0% rgb(255, 255, 255);" |
*[[TM1000]]
*[[TM3000]]
| style="background: none repeat scroll 0% 0% rgb(255, 255, 255);" |
*[[Installing Toolpack|Installing]]
| style="background: none repeat scroll 0% 0% rgb(255, 255, 255);" |
*[[Tmonitor_Lawful_Intercept|Lawful Intercept]]
| style="background: none repeat scroll 0% 0% rgb(255, 255, 255);" |
*[[Location-based services|Location-Based Services (LBS)]]
*[[Network monitoring|Network Monitoring]]
|}
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="210" style="background: none repeat scroll 0% 0% rgb(0, 83, 139);" |

Support

|-
| valign="top" style="background: none repeat scroll 0% 0% rgb(255, 255, 255); height: 466px" |
'''TBSupport'''
*[[TB Support Standard]]
*[[TB Support A la Carte]]
*[[Media:TB Support (Sales doc).pdf|TB Support (.pdf)]]
*[[Media:TB_Support_Full_length.pdf|TB Support Details]]
*[[Support:Contacting TelcoBridges technical support|Contacting TB Support]]
*[[Support:License_server|License Server]]
*[[Support:Time_tracking_tool|Time Tracking Tool]]
*[[:Category:FAQ|Frequently Asked Questions]]
*[http://forums.telcobridges.com Support Forums]
*[[Support:How To Submit A Problem|Submitting an Issue]]

'''Legal'''

*[[Media:Product Warranty.pdf|Product Warranty]]
*[[Media:Terms & Conditions 03-02-2011.pdf|Standard Terms & Conditions]]

'''Interoperability'''

*[[Interoperability:Deployments|Deployments]]
*[[Interoperability:Certifications|Certifications]]
*[[Partners]]

'''Policies'''

*[[End-of-Life (EOL) policy|End-of-Life (EOL)]]

'''Other'''
*[[Regulatory compliance|Regulatory Compliance]]

|}
|}

== Using TBwiki ==

Please note that the TBWiki is a living document, where the navigation and naming of content evolves over time.

There are various ways to search for information in the TBWiki...You can choose to search in the table above, use the glossary in the navigation bar or use the search box on the left hand side of each page.

== Disclaimer ==

The information on the TBwiki web site is subject to change without notice. No part of this web site may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of TelcoBridges Inc. TelcoBridges may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this web site or associated documents. The furnishing of access to this web site does not give you license to these patents, trademarks, copyrights, or other intellectual property except as expressly provided in any written agreement from TelcoBridges.

The information provided in this web site is intended as a guide. No responsibility is implied and the terms of your agreement with TelcoBridges will continue to claim precedence. For the latest detailed engineering specifications, please contact TelcoBridges. TelcoBridges is committed to continually improving product designs, as a result, product specifications may be subject to change without notification.

== Copyright ==

*This web site and its content, as well as any external links to content on TelcoBridges servers, is ©2002-2013 TelcoBridges Inc. All rights reserved.

Sigtrace

2013-10-23T16:13:53Z

Martin Provencher: Redirected page to Toolpack Debug Application:Tbsigtrace

#REDIRECT [[Toolpack_Debug_Application:Tbsigtrace]]

Toolpack Debug Application:sigtrace

2013-10-23T16:12:54Z

Martin Provencher: Add redirect from sigtrace to tbsigtrace

#REDIRECT [[Toolpack_Debug_Application:Tbsigtrace]]

RADIUS

2013-07-08T18:22:28Z

Martin Provencher: Only added the "AAA" string

Remote Authentication Dial In User Service, more popularly known as RADIUS, is used by telecom service providers for the purpose of authenticating, authorizing, and accounting (AAA) for the use of services by subscribers. A RADIUS server is an application server that provides this functionality. It can take as input as well as output [[Call detail record]] (CDR) data.

 

== TelcoBridges and RADIUS ==

Starting with release [[Toolpack_version_2.3|v2.3]] of [[Toolpack]], explicit support for the accounting function of RADIUS is now offered. Previously, Toolpack stored [[Call detail record]] (CDR) data in a local database. Starting with Toolpack v2.3, CDR data is stored on a dedicated, external server running an implementation of the RADIUS standard. Configuration of the location of the RADIUS server is performed through the Toolpack web portal.

Starting with release [[TMG-CONTROL_Version_2.6|v2.6]] of [[Toolpack]], multiple RADIUS servers can now be configured for backup purposes.

Starting with release [[TMG-CONTROL_Version_2.7|v2.7]] of [[Toolpack]], calls can now be validated through a RADIUS server with authentication and authorization. The RADIUS server may also change routing parameters for calls.

[[File:Radius_High-level_drawing_v2.jpg]]

=== Prerequisites ===

In order to enable RADIUS functionality in Toolpack, you must have a RADIUS server already up and running. It is highly recommended that the RADIUS server software being running on a separate machine from the one running the Toolpack software. Before configuring Toolpack, you will need the IP address of the RADIUS server(s). You will need to specify a ‘secret key’ which will authenticate the Toolpack server so that it can send accounting, authentication and authorization data and to the RADIUS server and the RADIUS server will accept it.

== Configuration ==

=== Accounting ===
*[[Web_Portal_Tutorial_Guide_v2.7#CDR|Toolpack v2.7: RADIUS configuration]]
*[[Web_Portal_Tutorial_Guide_v2.6#CDR|Toolpack v2.6: RADIUS configuration]]
*[[Toolpack:Configuring_RADIUS_A|Toolpack v2.5: RADIUS configuration]]
*[[Toolpack:Configuring_RADIUS_A|Toolpack v2.4: RADIUS configuration]]
*[[Toolpack:Configuring_RADIUS_A|Toolpack v2.3: RADIUS configuration]]

=== Authorization/Authentication ===

*[[Web_Portal_Tutorial_Guide_v2.7#RADIUS Authorization/Authentication|Toolpack v2.7: RADIUS configuration]]

== Toolpack to RADIUS CDR attributes remapping ==
When Toolpack sends ''Access-Request'' messages to a RADIUS server, some specific attributes are included in the message. These attributes have been improved through Toolpack releases to better meet accounting services requirements.

*[[Toolpack:RADIUS_CDR_attributes_C|Toolpack v2.7: RADIUS CDR attributes]]
*[[Toolpack:RADIUS_CDR_attributes_B|Toolpack v2.6: RADIUS CDR attributes]]
*[[Toolpack:RADIUS_CDR_attributes_A|Toolpack v2.5 and earlier: RADIUS CDR attributes]]

== Dealing with incoherent CDR entries ==
In some situations (during HA switchover for example), some CDR entries may be lost.

The following guide lines provide information on how to deal with these corner cases:

[[Call_Detail_Records_Entry_Loss|Deal with CDR entries loss]]

== References ==

*[[Toolpack:Status_Menus:RADIUS_A|Radius status in TMG web portal]]
*[http://en.wikipedia.org/wiki/RADIUS Radius Wikipedia article]
*[http://www.ietf.org/rfc/rfc2866.txt Link to RFC 2866 – Radius Accounting]
*[http://www.freeradius.net FreeRADIUS website]

[[Category:Glossary]]

Signaling protocols

2013-07-08T18:21:33Z

Martin Provencher:

Signaling refers to the system of messages required to set up and tear down telephone calls between the calling and the called parties.

 

== TelcoBridges and Signaling Protocols ==

TelcoBridges provides support for the following signaling protocols:

 

*'''PSTN'''
**[[SS7]]/C7
***(20+ variants) [[MTP2 Layer|MTP2]], [[MTP3 Layer|MTP3]] and [[ISUP]]
**[[ISDN]] PRI
***(14+ variants), National ISDN-2, Euro ISDN, DMS100, DMS250, 4ESS, 5ESS, Japan INS-NET1500
**[[CAS]] (Script-oriented approach):
***built-in scripts: generic(ITU base specification), Brazil

 

*'''IP'''
**[[SIP]] RFC 3261 User Agent, SIP Authentication
**[[SIGTRAN]]
***[[M2UA]], [[M2PA]] and [[M3UA]]

 

== Important Notes ==

*TelcoBridges Tmedia devices also offer the conversion of signaling messages between nodes that use different signaling protocols
*All supported protocols can be used simultaneously.

[[Category:Glossary]] [[Category:Tmedia_Features]] [[Category:RevisionV2]] [[category:Needs revising]]

AuditLogs A

2013-06-03T15:38:52Z

Martin Provencher: Adding Availability

Audit Log allow the user to easily and rapidly know what happened on the system configuration to accelerate the maintenance and troubleshooting of its TelcoBridges system.

== Availability ==
Audit Log is available since Toolpack 2.7.

== Features ==
All the actions made on the TelcoBridges Web Portal are logged in the database.

Each audit log contains:
* The time of the action
* The user who did the action
* The kind of action done
* The old and new values of the resource modified

To help the user to faster isolate the problem, each package and configuration activations are highlighted in green. This helps to know without hassle what changed since the last running configuration.

AuditLogs A

2013-06-03T15:34:33Z

Martin Provencher: Really write something in the Audit Log page

Audit Log allow the user to easily and rapidly know what happened on the system configuration to accelerate the maintenance and troubleshooting of its TelcoBridges system.

== Features ==
All the actions made on the TelcoBridges Web Portal are logged in the database.
Each audit log contains:
* The time of the action
* The user who did the action
* The kind of action done
* The old and new values of the resource modified

To help the user to faster isolate the problem, each package and configuration activations are highlighted in green. This helps to know without hassle what changed since the running configuration.

Users

2013-03-27T18:34:08Z

Martin Provencher: Adding whitespaces

Users and User Groups are the basis of authentication and authorization forToolpack systems.

Proper implementation of Users and User Groups increases efficiency and reduce costs by:
* Reducing Human Error,
* Mitigating Risks,
* Improving Security,
* Speeding up & Simplifying Maintenance and Debugging.

== Users ==

Every person using the Toolpack Web Portal should have their own user.
Users are defined by a username and a password.

== User Groups ==

User Groups define a list of authorized actions applied to each item on the left-hand Toolpack Web Portal menu (resources).

There are 3 authorization levels per resource:
'''Read/Write'''
Full access to the resource.
'''Read'''
Only view access to the resource. The action commands will be hidden.
'''None'''
No access to the resource. It won't be displayed in the left menu.

Each User needs to be in a User Group.
To modify a User access to a resource, you need to modify its User Group or create a new User Group with the required authorization.

The ''Admin'' User Group is not modifiable, and each User in this group gets access to all the resources in the Web Portal.

Users

2013-03-27T18:33:06Z

Martin Provencher: Moving the benefices outside Users

Users

2013-03-27T17:33:23Z

Martin Provencher: Create the users/user groups page

Users and user groups are the base of the authentication and the authorization on Toolpack systems.

== Users ==

Users are defined by a username and a password. Every person using the Toolpack Web Portal should have its own user. This facilitate the debugging of the system with the audit logs and the management of authorization with the user groups.

== User Groups ==

User groups define a group of authorized actions on each resources of the Toolpack Web Portal. Resources are defined by their presence in the left menu of the application.

There is 3 authorization levels per resource:
'''Read/Write'''
Full access to the resource.
'''Read'''
Only consultation access to the resource. The action commands will be hidden.
'''None'''
No access to the resource. It won't be displayed in the left menu.

Each users need to be in a user group. To modify a user access to a resource, you need to modify its user group or create a new user group with the required authorization.

The ''Admin'' user group is not modifiable and each users in this group get access to all the resource in the Web Portal.

Routing script tutorial:Mini Development Guide

2011-02-17T14:13:23Z

Martin Provencher: Modify UUI Hex to UUI Byte array

== Call object ==

=== Get ===

Those function are used to get the call parameters. The possible parameters are described in the section "Call parameters"

called_number = caf_call.get :called

=== List_params ===

This function is used to retrieve the list of supported call parameters. For example to extract all the possible call params from the the call object and put it in hash.

caf_call.list_params.each {|param| call[param] = caf_call.get param }

=== Accept ===

This function is used to accept a call. It takes 2 arguments, the call parameters (hash) and the route parameters (hash).

Apply route remapping rules

caf_call.accept out_call, route

=== Refuse ===

This function is used to refuse a call with a reason code argument parameters :

caf_call.refuse :reason => :temporary_failure

The supported values are described in the section "Reason values".

== Call parameters ==

The following call parameters are available in the call object:

*calling
*calling_noa
*calling_npi
*calling_display_type
*calling_display
*calling_presentation
*calling_screening
*calling_category
*private_display
*private_display_type
*private_address
*called
*called_noa
*called_npi
*redirecting_number_forward_enabled
*redirecting_number_noa
*redirecting_number_npi
*redirecting_number_presentation
*redirecting_number_screening
*redirecting_number_reason
*redirecting_number_counter
*original_called_number
*original_called_number_noa
*original_called_number_npi
*original_called_number_presentation
*original_called_number_screening
*original_called_number_reason
*original_called_number_counter
*nap
*uui
*uui_forward_enabled
*oli
*request_uri
*request_uri_forward_enabled

'''Notice:''' All values are documented in the '''noa_npi_remap.rb''' script and may change between major release.

=== Noa values ===

*<tt>unknown_number</tt>
*<tt>international_number</tt>
*<tt>national_number</tt>
*<tt>subscriber_number</tt>
*<tt>network_specific</tt>
*<tt>network_routing_national_format</tt>
*<tt>network_routing_international_format</tt>
*<tt>abbreviated_number</tt>
*<tt>subscriber_number_operator_requested</tt>
*<tt>national_number_operator_requested</tt>
*<tt>international_number_operator_requested</tt>
*<tt>no_number_present_operator_requested</tt>
*<tt>no_number_present_cut_through_call_to_carrier</tt>
*<tt>test_line_test_code</tt>
*<tt>non_unique_subscriber_number</tt>
*<tt>non_unique_national_number</tt>
*<tt>non_unique_international_number</tt>
*<tt>call_950_number</tt>

Those values will be remapped to the protocol specific NOA value. To provide protocol specific value:

*<tt>call_params[:called_noa] = 0x70</tt>

or

*<tt>call_params[:called_noa] = 112</tt>

=== Npi values ===

*<tt>unknown_number</tt>
*<tt>isdn</tt>
*<tt>telephony</tt>
*<tt>private</tt>
*<tt>data</tt>
*<tt>telex</tt>
*<tt>national</tt>

=== Calling Display Type values ===

*<tt>unspecified</tt> => Type is unspecified.
*<tt>calling_party_name</tt> => Type is 0xB1.

Those values will be remapped to the protocol specific Display Information Type value. To provide protocol specific value:

*<tt>call_params[:calling_display_type] = 0xB1</tt>

or

*<tt>call_params[:calling_display_type] = 177</tt>

=== Calling Display value ===

*<tt>call_params[:calling_display] = "Roger Fluffy"</tt>

=== Presentation values ===

*<tt>unspecified</tt>
*<tt>not_available</tt>
*<tt>allowed</tt>
*<tt>restricted</tt>
*<tt>addr_restricted</tt>
*<tt>name_restricted</tt>

=== Screening values ===

*<tt>unspecified</tt>
*<tt>no</tt>
*<tt>pass</tt>
*<tt>fail</tt>
*<tt>network_provided</tt>

=== Redirecting number reason values ===

ISDN:

*<tt>unknown</tt>
*<tt>busy</tt>
*<tt>no_reply</tt>
*<tt>deflection</tt>
*<tt>dte_out_of_order</tt>
*<tt>forwarding_by_called_dte</tt>
*<tt>unconditional</tt>

SS7:

*<tt>unknown</tt>
*<tt>busy</tt>
*<tt>no_reply</tt>
*<tt>unconditional</tt>
*<tt>deflection</tt>
*<tt>deflection_immediate</tt>
*<tt>mobile_not_reachable</tt>

=== UUI (user-to-user indication) values ===

Byte array represented as ruby String. Use ''call.get(:uui).each_byte'' to access the data in case the UUI contains non printable character.

=== OLI (originating line information) values ===

The OLI parameter is a string that represents an integer value from 0 to 255.

=== redirecting_number_forward_enabled values ===

Controls forwarding or discarding of redirecting number to outgoing call leg.

Values for this parameter are "0", "1", "false" or "true. 0/false: Redirecting number (and original called number) is not forwarded to outgoing call leg 1/true: Redirecting number (and original called number) is forwarded to outgoing call leg The value for this parameter at input of routing script depends on the "Forward redirecting number" parameter in the "Advanced" section of the Gateway configuration page of the Web Portal. The script may change this value to override the Gateway configuration.

 

=== uui_forward_enabled values ===

Controls forwarding or discarding of UUI to outgoing call leg.

Values for this parameter are "0", "1", "false" or "true. 0/false: UUI is not forwarded to outgoing call leg 1/true: UUI is forwarded to outgoing call leg The value for this parameter at input of routing script depends on the "Forward UUI" parameter in the "Advanced" section of the Gateway configuration page of the Web Portal. The script may change this value to override the Gateway configuration.

=== request_uri ===

Enables access to the Request-Line URI. 

For example, if the Request-Line is:
<pre>Request-Line: INVITE sip:4175162082@172.22.45.13:5060;user=phone;transport=udp SIP/2.0</pre>
Then the retrieved request_uri will be "sip:4175162082@172.22.45.13:5060;user=phone;transport=udp SIP/2.0". 

In the routing scripts, to retrieve only the called number, this script can be used: 
<pre> if call_params[:request_uri] && call_params[:request_uri] =~ /sip:(.*)@.*/
call_params[:called] = $1
end
</pre>

=== request_uri_forward_enabled values ===

Controls forwarding or discarding of request uri to outgoing call leg.The request uri is the information in the "Request-Line:" of the SIP INVITE message. 

Values for this parameter are "0", "1", "false" or "true. 

0/false: Request uri is not forwarded to outgoing call leg 

1/true: Request uri is forwarded to outgoing call leg 

The value for this parameter at input of routing script is always false.
 
== Route parameters ==

All route may have these parameters:

*calling
*called
*nap
*remapped_calling
*remapped_called
*remapped_nap
*remapped_profile

Additionally it is possible to add dynamic route attributes in the web portal. These can be referenced by their name.

== Reason values ==

All CMC reason codes are available for use by the routing scripts. See the TBCMC_CALL_REASON_CODE enum in the tbcmc_call.h file.

'''Notice:''' These values may change between major release.

/* isdn/ss7 reason code style */
/* Toolpack engine will convert reason code from sip to isdn/ss7 or isdn/ss7 to sip according to RFC3398 */
UNALLOCATED_NUMBER
NO_ROUTE_TO_NETWORK
NO_ROUTE_TO_DESTINATION
SEND_SPECIAL_TONE
MISDIALLED_TRUNK_PREFIX
CHANNEL_UNACCEPTABLE
CALL_AWARDED_IN_ESTABLISHED_CHANNEL
PREEMPTION
REATTEMPT
NORMAL_CALL_CLEARING
USER_BUSY
NO_USER_RESPONDING
NO_ANSWER_FROM_USER
SUBSCRIBER_ABSENT
CALL_REJECTED
NUMBER_CHANGED
REDIRECTION
EXCHANGE_ROUTING_ERROR
NON_SELECTED_USER_CLEARING
DESTINATION_OUT_OF_ORDER
ADDRESS_INCOMPLETE
FACILITY_REJECTED
RESPONSE_TO_STATUS_ENQUIRY
NORMAL_UNSPECIFIED
NO_CIRCUIT_AVAILABLE
NETWORK_OUT_OF_ORDER
FRAME_MODE_OUT_OF_SERVICE
FRAME_MODE_CONN_OPERATIONAL
TEMPORARY_FAILURE
SWITCHING_EQUIP_CONGESTION
ACCESS_INFO_DISCARDED
REQUESTED_CIRCUIT_NOT_AVAILABLE
PRECEDENCE_CALL_BLOCKED
RESOURCE_UNAVAILABLE
QOS_NOT_AVAILABLE
REQUESTED_FACILITY_NOT_SUBSCRIBED
OUTGOING_CALLS_BARRED
OUTGOING_CALLS_BARRED_WITHIN_CUG
INCOMING_CALLS_BARRED
INCOMING_CALLS_BARRED_WITHIN_CUG
BEARER_CAP_NOT_AUTHORIZED
BEARER_CAP_NOT_AVAILABLE
INCONSISTENCY_ACCESS_INFO
SERVICE_NOT_AVAILABLE
BEARER_CAP_NOT_IMPLEMENTED
CHANNEL_TYPE_NOT_IMPLEMENTED
REQUESTED_FACILITY_NOT_IMPLEMENTED
ONLY_RESTRICTED_DIGITAL_INFO
SERVICE_NOT_IMPLEMENTED
INVALID_CALL_REFERENCE
CHANNEL_DOES_NOT_EXIST
CALL_IDENTITY_DOES_NOT_EXIST
CALL_IDENTITY_IN_USE
NO_CALL_SUSPENDED
CALL_HAS_BEEN_CLEARED
USER_NOT_MEMBER_OF_CUG
INCOMPATIBLE_DESTINATION
NON_EXISTANT_CUG
INVALID_TRANSIT_NETWORK
INVALID_MESSAGE_UNSPECIFIED
MANDATORY_IE_MISSING
MESSAGE_TYPE_NON_EXISTENT
MESSAGE_NOT_COMPATIBLE_WITH_CALL_STATE
IE_NON_EXISTENT
INVALID_IE_CONTENT
MSG_NOT_COMPATIBLE_WITH_CALL_STATE
RECOVERY_ON_TIMER_EXPIRY
PARAMETER_NON_EXISTENT_PASSED_ON
MESSAGE_WITH_NON_RECOGNIZED_PARAMETERS_DISCARDED
PROTOCOL_ERROR
INTERWORKING_UNSPECIFIED

/* Toolpack specific errors */
NORMAL
RESOURCE_ERROR
TIMEOUT
NO_ROUTE
CALL_COLLISION
SYNC_DROP
SIGNALING_ERROR
LOCALLY_REJECTED
INTERFACE_NOT_AVAILABLE
RESET_IN_PROGRESS
ADAPTER_REJECT
MISSING_INVALID_IE
INCOMING_ONLY
SYSTEM_CONFIGURATION_CHANGED
RESOURCE_NO_MORE_AVAILABLE
INCOMPATIBLE_MEDIA
RES_ALLOC_FAILED
DATA_PATH_NOT_AVAILABLE

 

== Nap status ==

All the status fields of the NAPs are provided for use by the routing scripts. See the nap status provider for more details on which fields are available in the CEngineStatTransNap.hpp file.

'''Notice:''' These values may change between major release.

#define NAP_STATS_FIELDS \
/* Field, szName, szDescription, szOptions */ \
( SIGNALING_TYPE, "signaling_type", "Signaling type.", "" ) \
( INCOMING_CALL_CNT, "inst_incoming_call_cnt", "Instantaneous Count of incoming calls.", "" ) \
( OUTGOING_CALL_CNT, "inst_outgoing_call_cnt", "Instantaneous Count of outgoing calls.", "" ) \
( AVAILABLE_CNT, "available_cnt", "Number of available circuits or channels.", "" ) \
( UNAVAILABLE_CNT, "unavailable_cnt", "Number of unavailable circuits or channels.", "" ) \
( AVAILABILITY_PCT, "availability_percent", "Percentage of available circuits or channels.", "" ) \
( USAGE_PCT, "usage_percent", "Percentage of used circuits or channels.", "" ) \
( TOTAL_INCOMING_CALL_CNT, "total_incoming_call_cnt", "Total Count of incoming calls.", "" ) \
( ASR_STRUCT, "asr_statistics_struct", "Detailed Answer-Seizure Rate Statistics.", "" ) \
( GLOBAL_ASR_PCT, "global_asr_percent", "Global calculated ASR percentage.", "" ) \
( TOTAL_OUTGOING_CALL_CNT, "total_outgoing_call_cnt", "Total Count of outgoing calls.", "" ) \
( LAST_24H_ASR_PCT, "last_24h_asr_percent", "Last 24 hours calculated ASR percentage.", "" ) \
( LAST_24H_OUTGOING_CALL_CNT, "last_24h_outgoing_call_cnt", "Last 24 hours outgoing calls.", "" ) \
( HOUR_ASR_PCT, "current_hour_asr_percent", "Current hour calculated ASR percentage.", "" ) \
( HOUR_OUTGOING_CALL_CNT, "current_hour_outgoing_call_cnt", "Current hour outgoing calls.", "" ) \
( LAST_HOUR_ASR_PCT, "last_hour_asr_percent", "Last hour calculated ASR percentage.", "" ) \
( LAST_HOUR_OUTGOING_CALL_CNT, "last_hour_outgoing_call_cnt", "Last hour outgoing calls.", "" ) \
( AVAILABILITY_DETECTION_STRUCT, "availability_detection_struct", "Detailed availibility detection Statistics", "" ) \
( POLL_REMOTE_PROXY, "poll_remote_proxy", "Remote proxy polling enabled", "" ) \
( IS_AVAILABLE, "is_available", "Remote proxy actually available or not", "" ) \
( TIME_SINCE_POLLING, "time_since_polling", "Time since the last availibility polling", "" ) \
( TIME_AVAILABLE_SECONDS, "time_available_seconds", "Number of seconds since the NAP is available", "x" ) \
( TIME_UNAVAILABLE_SECONDS, "time_unavailable_seconds", "Number of seconds since the NAP is unavailable", "x" ) \
( REGISTRATION_STRUCT, "registration_struct", "Detailed registration Statistics", "" ) \
( REGISTER_TO_PROXY, "register_to_proxy", "Register to proxy enabled", "" ) \
( IS_REGISTERED, "registered", "Actually registered or not", "" ) \
( TIME_SINCE_REFRESH, "time_since_refresh", "Time since the last refresh", "" ) \
( TIME_REGISTERED_SECONDS, "time_registered_seconds", "Number of seconds since the NAP is registered", "x" ) \
( TIME_NOT_REGISTERED_SECONDS, "time_not_registered_seconds", "Number of seconds since the NAP is not registered", "x" ) \
/*!< Nap Status Fields */

 If the nap status is part of a substructure, it's name in the routing scripts must be composed of the structure name appended by an underscore and the field name.

For example the name to use for the global [[ASR]] percentage is:

asr_statistics_struct_global_asr_percent

 It is also possible to add dynamic nap attributes in the web portal. These can be referenced by their name.

== Test parameters ==

=== @call_params ===

That variable should contain a hash of call parameters that will passed to the routing script. This is equivalent to the incoming call parameters.

 

=== @nap_list ===

A list of hash containing the nap statuses. This is equivalent to the nap statuses at the time the call is to be routed.

'''The nap list is hashed by the nap names in UPPERCASE.''' It is important to consider this when creating new dynamic route or nap attributes that may nap names that will be used to fetch a status.

 

----

 Back to [[Routing script tutorial|Routing Script Tutorial]].

File:Tbh323 example network.png

2010-06-16T17:29:35Z

Martin Provencher: uploaded a new version of "File:Tbh323 example network.png": Bad names and IP addresses

Network configuration for H.323 Signaling Converter example

File:Tbh323 example network.png

2010-06-16T17:23:17Z

Martin Provencher: Network configuration for H.323 Signaling Converter example

Network configuration for H.323 Signaling Converter example