TBwiki - New pages [en]

ProSBC:ProSBC Configuration Twilio Trunking:Example A

2021-03-25T06:54:38Z

Serdar Civici: /* NAP Configuration for Twilio Elastic Trunking */

{{DISPLAYTITLE:SIP Trunk Configuration Instruction with Twilio Elastic trunking}}

=Introduction=
This article provides you with a step-by-step SIP Trunk Configuration of [[FreeSBC|ProSBC]] with Twilio Elastic Trunking, using the Web Portal configuration tool. Complete the general installation configuration steps, before you begin configuring your specific scenario. In this guide FQDN is ('''telcobridges.pstn.twilio.com''') configured in the Twilio console. You can find more details about how to create an Elastic Trunking in Twilio from the following link [https://www.twilio.com/docs/sip-trunking#configure-trunks Create and Configure Trunks]

=Twilio Elastic SIP Trunk Example=
[[Image:Twilio_Trunking.png|800px]]
====Configuration Steps====

{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 1) Create IP Network
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 2) Create Protocol Stack
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 3) Create Call Route
|-

| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_C|Configuring an IP Virtual Port]]
*[[Toolpack:Configuring_Vlan_SBC_A|Configuring a VLAN]]
*[[Toolpack:Configuring_IP_Interface_SBC_A|Configuring IP Interfaces]]
*[[Toolpack:Creating_an_IP_Port_Range_SBC_A|Create an IP port range]]

| valign="top" |
*[[Toolpack:Creating_an_IP_Port_Range_SBC A|Create an IP port range]]
*[[Toolpack:Creating_a_SIP_Stack_SBC A|Create a SIP stack]]
*[[Toolpack:Creating_a_SIP_Transport_Server_SBC A|Create a SIP transport server]]
*[[Toolpack:Modify_Profile_Sbc_A|Modify profile]]
*[[Toolpack:Allocating_a_SIP_Network_Access_Point_(NAP)_SBC A|Allocate a SIP NAP]]

| valign="top" |
*[[Toolpack:Creating_a_First_Call_Route E|Create a first call route]]

|}

= NAP Configuration for Twilio Elastic Trunking =

* See [[Toolpack:Allocating a SIP Network Access Point (NAP) SBC A|Create SIP NAP]]
In this example, we will use telcobridges.pstn.twilio.com trunk information

[[Image:twilio_nap.png]]

'''NOTE: Connection to Twilio Elastic SIP Trunking is available in multiple geographic edge locations. If you wish to manually connect to a specific geographic edge location that is closest to the location of your communications infrastructure, you may do so by pointing your communications infrastructure to any of the following localized Termination SIP URIs:'''
* {example}.pstn.ashburn.twilio.com (North America Virginia)
* {example}.pstn.umatilla.twilio.com (North America Oregon)
* {example}.pstn.dublin.twilio.com (Europe Ireland)
* {example}.pstn.frankfurt.twilio.com (Europe Frankfurt)
* {example}.pstn.singapore.twilio.com (Asia Pacific Singapore)
* {example}.pstn.tokyo.twilio.com (Asia Pacific Tokyo)
* {example}.pstn.sao-paulo.twilio.com (South America São Paulo)
* {example}.pstn.sydney.twilio.com (Asia Pacific Sydney)

'''[https://www.twilio.com/docs/sip-trunking/ip-addresses Click here for more information on Twilio Elastic SIP Trunking IP Addresses]'''

* [[Parameter: Name|Name]]
* [[Parameter: Default Profile|Default Profile]]
* [[Parameter: Proxy Address|Proxy Address]]
* [[Parameter: Proxy Port Type|Proxy Port Type]]
* [[Parameter: Proxy Port|Proxy Port]]
* [[Parameter: Poll Remote Proxy|Poll Remote Proxy]]
* [[Parameter: Accept only authorized users|Accept only authorized users]]

= Route Configuration for Twilio Elastic Trunking =

* See [[Toolpack:Creating_a_First_Call_Route E|Create a first call route]]
In this example, we will create an outgoing and incoming routes for Twilio Elastic Trunk

== Route for outgoing to Twilio ==
[[Image:route_2_twilio.png]]

== Route for incoming from Twilio ==
[[Image:route_from_twilio.png]]

==List of Parameters==
* [[Parameter: Name|Name]]
* [[Parameter: Routeset Name|Routeset Name]]
* [[Parameter: Called|Called]]
* [[Parameter: Calling|Calling]]
* [[Parameter: NAP|NAP]]
* [[Parameter: Remapped Called|Remapped Called]]
* [[Parameter: Remapped Calling|Remapped Calling]]
* [[Parameter: Remapped NAP|Remapped NAP]]
* [[Parameter: Source call leg remapped Profile|Source call leg remapped Profile]]
* [[Parameter: Destination call leg remapped Profile|Destination call leg remapped Profile]]

Custom Parameters
* [[Parameter: prio|prio (or priority)]]
* [[Parameter: additonal_naps|additonal_naps]]
* [[Parameter: domain|domain]]

ProSBC:VitalPBX Phone Configuration:VitalPBX Phone Configuration

2021-03-23T12:33:42Z

Serdar Civici:

{{DISPLAYTITLE:VitalPBX Extension Creation}}

=Introduction=
This document provides instructions on how to add an extension to VitalPBX Server to work with the ProSBC.
Please visit the following link for more details about [https://wiki.vitalpbx.org/documentation/vitalpbx-manual/pbx/extensions/extensions/ Creating an Extensions in VitalPBX Server]

=VitalPBX Extension Configuration=
1. Login into the administration portal via the IP address of the machine that is running VitelPBX.

2. Select the '''Admin -> Network''' From the left menu to set the hostname of the device. In our example, it is set to '''sip.telcobridges.com'''

 [[Image:VitalPbx_Remote_Workers_2.png|800px| ]] 

*'''Hostname''', hostname of the system.

3. Select the '''PBX''' tab at the top left and then from the drop-down menu click '''Extensions->Extensions'''.

 [[Image:VitalPbx_Remote_Workers_1.png|800px| ]] 

* '''Extension''', number to dial in order to reach this extension. The extension number must be unique, and should not conflict with an existing extension number, or any other number that is assigned to any other entity within the system, such as a conference, queue, ring group, feature code, etc. The value of this field cannot be changed after the extension has been saved.
* '''Name''', name to identify this extension.
* '''User Device''', username to be used when registering this device.
* '''Password''', password (secret) associated with this device.
* '''Device Description''', a short (optional) description to identify this device.
* '''Codecs''', list of allowed codecs. The order in which the codecs are listed determines their order of preference.

ProSBC:VitalPBX Remote Workers:Configuration A

2021-03-23T12:13:33Z

Serdar Civici: Created page with "=== '''''Applies to version: v3.1''''' === {{DISPLAYTITLE:Remote Workers Configuration Instruction with VitalPBX}} =Introduction= Remote Workers Configuration Instruction wi..."

=== '''''Applies to version: v3.1''''' ===

{{DISPLAYTITLE:Remote Workers Configuration Instruction with VitalPBX}}

=Introduction=
Remote Workers Configuration Instruction with VitalPBX Example Configuration provides you with a step-by-step Remote workers Configuration of [[ProSBC|ProSBC]] with VitalPBX systems, using the Web Portal configuration tool. Complete general installation configuration steps, before you begin configuring your specific scenario. In this guide, FQDN ('''sip.telcobridges.com''') configured in the VitalPBX server and registration forwarding used in ProSBC.

=VitalPBX Remote Workers Example=

[[Image:VitalPbx_Remote_Workers.png|800px| ]]

====Configuration Steps====

{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 1) Create IP Network
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 2) Create Protocol Stack
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 3) Create Call Route
|-

| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_C|Configuring an IP Virtual Port]]
*[[Toolpack:Configuring_Vlan_SBC_A|Configuring a VLAN]]
*[[Toolpack:Configuring_IP_Interface_SBC_A|Configuring IP Interfaces]]
*[[Toolpack:Creating_an_IP_Port_Range_SBC_A|Create an IP port range]]

| valign="top" |
*[[Toolpack:Creating_an_IP_Port_Range_SBC A|Create an IP port range]]
*[[Toolpack:Creating_a_SIP_Stack_SBC A|Create a SIP stack]]
*[[Toolpack:Creating_a_SIP_Transport_Server_SBC A|Create a SIP transport server]]
*[[Toolpack:Modify_Profile_Sbc_A|Modify profile]]
*[[Toolpack:Allocating_a_SIP_Network_Access_Point_(NAP)_SBC A|Allocate a SIP NAP]]
*[[Toolpack:Allocating_a_SIP_Open_Network_Access_Point_(NAP)_SBC A|Allocate an open SIP NAP]]

| valign="top" |
*[[Toolpack:Creating_a_First_Call_Route E|Create a first call route]]

|}

= NAP Configuration =

* See [[Toolpack:Allocating a SIP Network Access Point (NAP) SBC A|Create SIP NAP]] and [[Toolpack:Allocating a SIP Open Network Access Point (NAP) SBC A|Create Open NAP]]
** Here, SIP NAP will be VitalPBX NAP and Open NAP will be from Remote Clients

= SIP Domain Configuration =

* See [[Toolpack:Creating_a_SIP_Domain_SBC B|Create a SIP domain]]
** Here domain name will be FQDN of the VitalPBX server. In our example, it will be '''sip.telcobridges.com'''

ProSBC:VitalPBX Trunk Configuration:VitalPBX Trunk Configuration

2021-03-23T09:12:47Z

Serdar Civici:

{{DISPLAYTITLE:VitalPBX SIP Trunk Creation}}

=Introduction=
This document provides instructions on how to add a SIP Trunk to VitalPBX Server to work with the ProSBC.
Please visit the following link for more details about [https://wiki.vitalpbx.org/documentation/vitalpbx-manual/pbx/external/trunks/ Creating a SIP Trunk in VitalPBX Server]

=VitalPBX SIP Trunk Configuration=
1. Login into the administration portal via the IP address of the machine that is running VitalPBX.

2. Select the '''PBX''' tab at the top left and then from the drop-down menu click '''External -> Trunks'''.

 [[Image:vitalpbx_trunk_1.png|500px]] 

3. Select the '''SIP'''

 [[Image:vitalpbx_trunk_2.png|500px]] 

4. As shown below image there are very few fields to configure. We will explain the fields that need to configure the trunk.

 [[Image:vitalpbx_trunk_3.png|800px]] 

*'''Description''' Short description to identify this trunk
*'''Remote Host''' Address for all SIP communications (inbound and outbound). ProSBC FQDN/IP Address must be entered in this area.
*'''Remote Port''' Destination SIP Port. It must be the same as the ProSBC Transport Server port.

5. We need to create an outbound route for this new trunk. Select the '''PBX''' tab at the top left and then from the drop-down menu click '''External -> Outbound Routes'''.

 [[Image:vitalpbx_trunk_4.png|500px]] 

6. Enter the Outbound Route details

 [[Image:vitalpbx_trunk_5.png|500px]] 

*'''Description''' Short description to identify this outbound route
*'''Trunks''' Select the SIP Trunk created for ProSBC
*'''Dial Patterns''' Add the Dial Patterns to use this Outbound Route

7. We need to create an inbound route for this new trunk. Select the '''PBX''' tab at the top left and then from the drop-down menu click '''External -> Inbound Routes'''.

 [[Image:vitalpbx_trunk_6.png|500px]] 

8. Enter the Inbound Route details

 [[Image:vitalpbx_trunk_7.png|500px]] 

*'''Description''' Short description to identify this inbound route
*'''DID Pattern''' If you have DIDs coming with the trunk please enter the DID pattern
*'''Inbound Destination''' Select where to send incoming calls from the DID

ProSBC:SIP Trunking VitalPBX:Example A

2021-03-23T08:18:04Z

Serdar Civici: /* Introduction */

=== '''''Applies to version: v3.1''''' ===

{{DISPLAYTITLE:SIP Trunk Configuration Instruction with VitalPBX}}

=Introduction=
SIP Trunk Configuration Instruction with VitalPBX Example Configuration provides you with a step-by-step SIP Trunk Configuration of [[FreeSBC|ProSBC]] with VitalPBX systems, using the Web Portal configuration tool. Complete general installation configuration steps, before you begin configuring your specific scenario. In this guide FQDN ('''vitalpbx.telcobridges.com''') configured in the VitalPBX server. If you don't use FQDN, you can use the VitalPBX IP address too. Please check how to configure the SIP Trunk in VitalPBX for ProSBC from [[ProSBC:VitalPBX Trunk Configuration:VitalPBX_Trunk_Configuration|VitalPBX Trunk Creation]]

=VitalPBX SIP Trunk Example=

[[Image:vitalpbx_Trunking_1.png|800px]]

====Configuration Steps====

{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 1) Create IP Network
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 2) Create Protocol Stack
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 3) Create Call Route
|-

| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_C|Configuring an IP Virtual Port]]
*[[Toolpack:Configuring_Vlan_SBC_A|Configuring a VLAN]]
*[[Toolpack:Configuring_IP_Interface_SBC_A|Configuring IP Interfaces]]
*[[Toolpack:Creating_an_IP_Port_Range_SBC_A|Create an IP port range]]

| valign="top" |
*[[Toolpack:Creating_an_IP_Port_Range_SBC A|Create an IP port range]]
*[[Toolpack:Creating_a_SIP_Stack_SBC A|Create a SIP stack]]
*[[Toolpack:Creating_a_SIP_Transport_Server_SBC A|Create a SIP transport server]]
*[[Toolpack:Modify_Profile_Sbc_A|Modify profile]]
*[[Toolpack:Allocating_a_SIP_Network_Access_Point_(NAP)_SBC A|Allocate a SIP NAP]]

| valign="top" |
*[[Toolpack:Creating_a_First_Call_Route E|Create a first call route]]

|}

= NAP Configuration =

* See [[Toolpack:Allocating a SIP Network Access Point (NAP) SBC A|Create SIP NAP]]
**Here, You must create two NAPs, one SIP NAP will be VitalPBX NAP and the other NAP will be for the SIP trunk provided by ITSP

ProSBC:VitalPBX

2021-03-23T08:14:43Z

Luc Morissette: /* Troubleshooting */

{{DISPLAYTITLE:ProSBC:VitalPBX}}

=Introduction=

This Configuration Note describes how to set up Telcobridges ProSBC for interworking between ITSP’s SIP Trunk or remote client access for VitalPBX server.

'''NOTE:''' SIP Trunk use G.711 in this test. There is no transcoding available.

==Prerequisites==
*[[ProSBC|ProSBC]] devices must be installed as described in their respective with release 3.0.x/3.1.x. Release 3.0.x is not supported for TCP connections [[Product_Installation_SBC|installation guides]].
*VitalPBX.For additional information on VitalPBX, visit [https://www.vitalpbx.org/ VitalPBX offical web site].

==Example Environments for SIP Trunking with VitalPBX==

[[Image:vitalpbx_Trunking_1.png|800px]]

==Example Configuration==

Step by step example SIP Trunk configuration.
*[[ProSBC:VitalPBX Trunk Configuration:VitalPBX_Trunk_Configuration|VitalPBX Trunk Creation]]
*[[ProSBC:SIP Trunking VitalPBX:Example_A|SIP Trunking Example Configuration]]
== Example Environments for Remote Workers with VitalPBX ==

[[Image:vitalPbx_Remote_Workers.png|800px| ]]

==Example Configuration==

Step by step example Remote workers configuration.
*[[ProSBC:VitalPBX Phone Configuration:VitalPBX_Phone_Configuration|VitalPBX Extension Creation]]
*[[ProSBC:VitalPBX Remote Workers:Configuration_A|Remote Workers Configuration Instruction with VitalPBX]]

==Troubleshooting==

{| 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;" | Call Trace
! 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;" | Test Call
! 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;" | TBReport
! 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;" | Advanced Troubleshooting of ProSBC
|-

| valign="top" |
*[[Toolpack:Configuring_Call_Trace_D|Configure call trace]]
*[[Toolpack:Retrieving_Call_Trace_C|Retrieve call trace]]

| valign="top" |
*[[Creating_A_Test_Call_B|Creating a Test Call]]

| valign="top" |
*[[TBReport|Capture a report of the system]]

| valign="top" |
*[[FreeSBC_Troubleshooting|Advanced Troubleshooting of ProSBC]]
|}

ProSBC:Brekeke SIP Trunk Configuration:Brekeke SIP Trunk

2021-03-15T08:42:10Z

Serdar Civici:

{{DISPLAYTITLE:Adding ProSBC as a SIP Trunk in the Brekeke PBX}}

=Introduction=
This document provides instructions on how to configure Brekeke PBX Server with the ProSBC as SIP trunk.
Please visit the following link for more details about [https://www.brekeke.com/support/pbx_document.php Brekeke PBX documentation]

=Brekeke PBX SIP Trunk Configuration=

The Brekeke PBX includes the Brekeke SIP Server. The SIP server of the Brekeke PBX includes several dial plan rules. In order to establish the communication between ProSBC and the Brekeke PBX Server using the
SIP protocol, you need to declare the necessary dial plan rules with their matching patterns.

1 - Go to '''SIP SERVER -> Dial Plan''' and click to '''New Rule''' button

 [[Image:brekeke_add_new_rule.png|600px|]] 

2 - Please create two new rules with the following criteria
:A. FromProSBC

<code>
::'''[Matching Patterns]'''
::$request = ^INVITE
::$addr = <'''ProSBC_IP_Address'''>
::To = sip:(.+)@
::'''[Deploy Patterns]'''
::To = sip:%1@
::$auth = false
</code>

 [[Image:brekeke_from_pro_sbc_rule.png|600px|]] 
:B. To ProSBC

<code>
::'''[Matching Patterns]'''
::$request = ^INVITE
::$registered = false
::To = sip:(.+)@

::'''[Deploy Patterns]'''
::$auth = false
::To = sip:%1@<'''ProSBC_IP_Address'''>
::$transport = udp
</code>

 [[Image:brekeke_to_pro_sbc_rule.png|600px|]] 

3 - PBX settings are used with their default values.

 [[Image:brekeke_sip_options.png|600px|]] 

4 - You need to create a new ARS pattern for registered users to call out from ProSBC. Go to '''PBX -> ARS''' and click to '''New Route'''

 [[Image:brekeke_add_ars.png|600px|]] 

5 - In the '''Route Template''' windows click to '''New''' button near to '''Patterns - OUT'''

 [[Image:brekeke_patterns_out.png|600px|]] 

6 - Add the following parameters in the ''' Matching patterns To''' and '''Deploy Patterns To'''

 [[Image:brekeke_ars_pattern.png|600px|]]

ProSBC:Brekeke SIP Trunk:Configuration A

2021-03-15T07:58:54Z

Serdar Civici: /* Introduction */

=== '''''Applies to version: v3.1''''' ===

{{DISPLAYTITLE:SIP Trunk Configuration Instruction with Brekeke PBX}}

=Introduction=
SIP Trunk Configuration Instruction with Brekeke PBX Example Configuration provides you with a step-by-step SIP Trunk Configuration of [[FreeSBC|ProSBC]] with Brekeke PBX systems, using the Web Portal configuration tool. Complete general installation configuration steps, before you begin configuring your specific scenario. In this guide, the ProSBC IP address is 192.168.35 and the Brekeke PBC IP address is 192.168.1.45. Please check how to configure the SIP Trunk in Brekeke PBX for ProSBC from [[ProSBC:Brekeke SIP Trunk Configuration:Brekeke_SIP_Trunk|Adding ProSBC as a SIP Trunk in Brekeke PBX]]

=Brekeke PBX SIP Trunk Example=

[[Image:Brekeke_SIP_Trunk.png|800px| ]]
====Configuration Steps====

{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 1) Create IP Network
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 2) Create Protocol Stack
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 3) Create Call Route
|-

| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_C|Configuring an IP Virtual Port]]
*[[Toolpack:Configuring_Vlan_SBC_A|Configuring a VLAN]]
*[[Toolpack:Configuring_IP_Interface_SBC_A|Configuring IP Interfaces]]
*[[Toolpack:Creating_an_IP_Port_Range_SBC_A|Create an IP port range]]

| valign="top" |
*[[Toolpack:Creating_an_IP_Port_Range_SBC A|Create an IP port range]]
*[[Toolpack:Creating_a_SIP_Stack_SBC A|Create a SIP stack]]
*[[Toolpack:Creating_a_SIP_Transport_Server_SBC A|Create a SIP transport server]]
*[[Toolpack:Modify_Profile_Sbc_A|Modify profile]]
*[[Toolpack:Allocating_a_SIP_Network_Access_Point_(NAP)_SBC A|Allocate a SIP NAP]]

| valign="top" |
*[[Toolpack:Creating_a_First_Call_Route E|Create a first call route]]

|}

= NAP Configuration =

* See [[Toolpack:Allocating a SIP Network Access Point (NAP) SBC A|Create SIP NAP]]
** Here, You must create two NAPs, one SIP NAP will be Brekeke PBX NAP and the other NAP will be for the SIP trunk provided by ITSP

ProSBC:Brekeke PBX

2021-03-15T07:53:48Z

Luc Morissette: /* Troubleshooting */

{{DISPLAYTITLE:ProSBC:Brekeke PBX Configuration with ProSBC}}

=Introduction=

This Configuration Note describes how to set up Telcobridges ProSBC for interworking between ITSP’s SIP Trunk or remote client access for Brekeke PBX.

==Prerequisites==
*[[ProSBC|ProSBC]] devices must be installed as described in their respective with release 3.0.x/3.1.x. Release 3.0.x is not supported for TCP connections [[Product_Installation_SBC|installation guides]].
*Brekeke PBX.For additional information on Brekeke, visit [https://www.brekeke.com/ Brekeke official web site].

==Example Environments for SIPTrunking with Brekeke PBX==

[[Image:Brekeke_SIP_Trunk.png|800px| ]]

==Example Configuration==

Step by step example SIP Trunk configuration.
*[[ProSBC:Brekeke SIP Trunk Configuration:Brekeke_SIP_Trunk|Adding ProSBC as a SIP Trunk in Brekeke PBX]]
*[[ProSBC:Brekeke SIP Trunk:Configuration_A|SIP Trunk Configuration Instruction with Brekeke PBX]]

==Troubleshooting==

{| 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;" | Call Trace
! 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;" | Test Call
! 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;" | TBReport
! 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;" | Advanced Troubleshooting of ProSBC
|-

| valign="top" |
*[[Toolpack:Configuring_Call_Trace_D|Configure call trace]]
*[[Toolpack:Retrieving_Call_Trace_C|Retrieve call trace]]

| valign="top" |
*[[Creating_A_Test_Call_B|Creating a Test Call]]

| valign="top" |
*[[TBReport|Capture a report of the system]]

| valign="top" |
*[[FreeSBC_Troubleshooting|Advanced Troubleshooting of ProSBC]]
|}

ProSBC processor Usage

2021-03-11T16:32:51Z

Luc Morissette: Updated TOC and formatting

{{DISPLAYTITLE:ProSBC Processor Usage}}
__TOC__
This procedure is used to check the Processor usage of the ProSBC. 

== How to check processor usage from the web portal ==
From the web interface you can see the processor usage: 
Hosts -> Status -> Select Host -> Processor Usage tab
 
Totals view show the global processor usage, and processor usage divided between applications and SBC processing 
[[image:SBC_Processor_usage.png]] 
 
Packet Processing shows processor usage of each IP interfaces 
[[image:SBC_Processor_usage_pkt.png]] 
 
Applications shows the processor usage of the individual applications and their theoretical maximums 
[[image:SBC_Processor_usage_app.png]] 
 

== Processor usage from SNMP ==
You can retrieve the processor usage from [[SNMP]] GET, using the [[TB-MIB]] TelcoBridges enterprise MIB. 
The value is located in the tbSwPerfTable (OID: 1.3.6.1.4.1.21776.1.2.2.3)
 

== Periodic logs on processor usage ==
Processor and memory usage are logged on the system. You can get access to these logs in this folder:
/lib/tb/toolpack/setup/12358/3.1/apps/tboamapp/log
It is also available in the [[TBReport]]
 

== Accessing from the console ==
From the [[Accessing_Device#SSH|SSH access]], here are the available commands. 
With the '''top''' command you can see the total CPU usage (and Memory usage) of the host:
[root@prosbc-vm-a1]# top
 
top - 07:27:40 up 13 days, 17:50, 1 user, load average: 1.29, 1.38, 1.54
Tasks: 140 total, 1 running, 139 sleeping, 0 stopped, 0 zombie
%Cpu(s): 26.0 us, 3.6 sy, 0.0 ni, 70.2 id, 0.0 wa, 0.0 hi, 0.2 si, 0.0 st
KiB Mem : 8042848 total, 1864328 free, 3560852 used, 2617668 buff/cache
KiB Swap: 2097148 total, 2097148 free, 0 used. 4157628 avail Mem

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
708 root 20 0 65.1g 240676 17260 S 101.3 3.0 20052:50 tbrouter
863 root 20 0 0 0 0 S 8.0 0.0 1636:13 kni_single
8276 root 20 0 2046568 146152 5808 S 1.7 1.8 214:46.81 tbsip
3495 root 20 0 1996260 127884 5972 S 1.3 1.6 258:41.70 toolpack_engine
3690 root 20 0 2543928 109644 6904 S 1.3 1.4 320:42.86 gateway
3181 root 20 0 10876 672 536 S 1.0 0.0 224:56.18 ipwatchd
 
Here we see the processor usage is 70% idle. 
We also see the tbrouter application is at 101% CPU, which is normal. You can have more details here: [[Toolpack_Application:tbrouter]]

ProSBC:Cisco SIP Trunk Configuration:Cisco UCM Trunk

2021-03-11T12:38:00Z

Serdar Civici:

{{DISPLAYTITLE:Cisco UCM 12 Trunk Creation}}

=Introduction=
This document provides instructions on how to add a SIP Trunk to Cisco UCM 12 to work with the ProSBC.
Please visit the following link for more details [https://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-version-12-0/model.html Cisco Support].

=Cisco UCM 12 SIP Trunk Configuration=
In order to establish the communication between the Cisco Unified Communications Manager and the created ProSBC NAP, a SIP trunk must be created. This enables ProSBC to be recognized as a device handler for the Cisco environment. After creating the SIP trunk, a Route Pattern must be created for proper call-legs and call routings. The SIP trunk must be related to some SIP and SIP Security Profiles. Some examples will be described in the following sections.

1. First of all it is necessary to specify a SIP Trunk Security Profile which has to be applied to the ProSBC SIP trunk. The '''SIP Trunk Security Profile''' can be created or changed through the '''Security''' submenu of the '''System''' tab

 [[Image:security_profile.png|500px|]] 

2. The '''Security Profile Settings''' shown below

 [[Image:security_profile_details.png|500px|]] 

* '''Name''' Give a name to this profile
* '''Device Security Mode''' mus be selected as '''Non Secure'''
* '''Outgoing Transport Type''' in this example we use as UDP, you can select TCP too
* '''Incoming Port''' Set the incoming SIP port

3. A new SIP trunk can be created by selecting the '''Trunk''' entry through the Cisco Unified Communications Manager '''Device''' menu.

 [[Image:cisco_trunk.png|500px|]] 

4. According to the selected protocol and the ProSBC, the '''Trunk Type''' must be assigned to '''SIP'''. The '''Device Protocol''' parameter will be automatically set to '''SIP''' and the '''Trunk Service Type''' is used with '''None (Default)'''.

 [[Image:cisco_sip_trunking_1.png|500px|]] 

5. The shown '''Trunk Configuration''' is basically used with the system given defaults. The '''Device Name''' identifier as well as the '''Description''' is set to prosbc.telcobridges.com, the hostname of the ProSBC assigned Ethernet interface IP address.

 [[Image:cisco_sip_trunking_2.png|500px|]] 

6. For the '''Call Routing Information (Inbound and Outbound Call)''' the parameter '''Redirecting Diversion Header Delivery''' has to be set. This enables the delivery of the origin and redirecting number through SIP. All other parameters are used with their defaults.

 [[Image:cisco_sip_trunking_3.png|500px|]] 

7. In this example the '''Destination Address''' is set to the hostname prosbc.telcobridges.com. The SIP Trunk Security Profile is set to ProSBC Non Secure SIP Trunk Profile. The DTMF Signaling Method is used with RFC 2833.

 [[Image:cisco_sip_trunking_4.png|500px|]] 

8. Define ProSBC’s SIP trunk required '''Route Pattern''' through the '''Call Routing''' menu.

 [[Image:cisco_route_pattern.png|500px|]] 

9. In this example the route pattern '''80.!''' is used for ProSBC’s SIP trunk '''prosbc.telcobridges.com'''.

 [[Image:cisco_route_pattern_details.png|500px|]] 

10. A SIP profile can be configured through Cisco’s '''Device''' '''Device Settings''' menu. You can specify a set of SIP attributes (timings, ports etc.) to the appropriate SIP trunks and SIP
endpoints.

 [[Image:cisco_sip_profile.png|500px|]] 

11. In this example the '''Standard SIP Profile''' is used and assigned to ProSBC’s SIP trunk

 [[Image:cisco_sip_profile_Details.png|500px|]]

ProSBC:Cisco SIP Trunk:Configuration A

2021-03-11T12:36:29Z

Serdar Civici: /* NAP Configuration */

=== '''''Applies to version: v3.1''''' ===

{{DISPLAYTITLE:SIP Trunk Configuration Instruction with Cisco UCM}}

=Introduction=
SIP Trunk Configuration Instruction with Cisco Unified Communications Manager Example Configuration provides you with a step-by-step SIP Trunk Configuration of [[FreeSBC|ProSBC]] with Cisco UCM 12 systems, using the Web Portal configuration tool. Complete general installation configuration steps, before you begin configuring your specific scenario. Please check how to configure the SIP Trunk in Cisco UCM for ProSBC from [[ProSBC:Cisco SIP Trunk Configuration:Cisco_UCM_Trunk|Adding ProSBC as a SIP Trunk in Cisco UCM]]

=Cisco UCM SIP Trunk Example=

[[Image:Cisco_ucm.png|800px| ]]

====Configuration Steps====

{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 1) Create IP Network
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 2) Create Protocol Stack
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 3) Create Call Route
|-

| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_C|Configuring an IP Virtual Port]]
*[[Toolpack:Configuring_Vlan_SBC_A|Configuring a VLAN]]
*[[Toolpack:Configuring_IP_Interface_SBC_A|Configuring IP Interfaces]]
*[[Toolpack:Creating_an_IP_Port_Range_SBC_A|Create an IP port range]]

| valign="top" |
*[[Toolpack:Creating_an_IP_Port_Range_SBC A|Create an IP port range]]
*[[Toolpack:Creating_a_SIP_Stack_SBC A|Create a SIP stack]]
*[[Toolpack:Creating_a_SIP_Transport_Server_SBC A|Create a SIP transport server]]
*[[Toolpack:Modify_Profile_Sbc_A|Modify profile]]
*[[Toolpack:Allocating_a_SIP_Network_Access_Point_(NAP)_SBC A|Allocate a SIP NAP]]

| valign="top" |
*[[Toolpack:Creating_a_First_Call_Route E|Create a first call route]]

|}

= NAP Configuration =

* See [[Toolpack:Allocating a SIP Network Access Point (NAP) SBC A|Create SIP NAP]]
** Here, You must create two NAPs, one SIP NAP will be Cisco UCM NAP and the other NAP will be for the SIP trunk provided by ITSP

ProSBC:Avaya SIP Trunk:Configuration A

2021-03-11T12:29:30Z

Serdar Civici: /* NAP Configuration */

=== '''''Applies to version: v3.1''''' ===

{{DISPLAYTITLE:SIP Trunk Configuration Instruction with Avaya IP Office}}

=Introduction=
SIP Trunk Configuration Instruction with Avaya IP Office Example Configuration provides you with a step-by-step SIP Trunk Configuration of [[FreeSBC|ProSBC]] with Avaya IP Office systems, using the Web Portal configuration tool. Complete general installation configuration steps, before you begin configuring your specific scenario. Please check how to configure the SIP Trunk in Avaya IP Office for ProSBC from *[[ProSBC:Avaya SIP Trunk Configuration:Avaya_IPOffice_Trunk|Adding ProSBC as a SIP Trunk in Avaya IP Office]]

=Avaya IP Office SIP Trunk Example=

[[Image:avaya_ip_office.png|800px| ]]

====Configuration Steps====

{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 1) Create IP Network
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 2) Create Protocol Stack
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 3) Create Call Route
|-

| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_C|Configuring an IP Virtual Port]]
*[[Toolpack:Configuring_Vlan_SBC_A|Configuring a VLAN]]
*[[Toolpack:Configuring_IP_Interface_SBC_A|Configuring IP Interfaces]]
*[[Toolpack:Creating_an_IP_Port_Range_SBC_A|Create an IP port range]]

| valign="top" |
*[[Toolpack:Creating_an_IP_Port_Range_SBC A|Create an IP port range]]
*[[Toolpack:Creating_a_SIP_Stack_SBC A|Create a SIP stack]]
*[[Toolpack:Creating_a_SIP_Transport_Server_SBC A|Create a SIP transport server]]
*[[Toolpack:Modify_Profile_Sbc_A|Modify profile]]
*[[Toolpack:Allocating_a_SIP_Network_Access_Point_(NAP)_SBC A|Allocate a SIP NAP]]

| valign="top" |
*[[Toolpack:Creating_a_First_Call_Route E|Create a first call route]]

|}

= NAP Configuration =

* See [[Toolpack:Allocating a SIP Network Access Point (NAP) SBC A|Create SIP NAP]]
** Here, You must create two NAPs, one SIP NAP will be Avaya IP Office NAP and the other NAP will be for the SIP trunk provided by ITSP

ProSBC:Avaya SIP Trunk Configuration:Avaya IPOffice Trunk

2021-03-11T12:28:20Z

Serdar Civici:

{{DISPLAYTITLE:Avaya IP Office Trunk Creation}}

=Introduction=
This document provides instructions on how to add a SIP Trunk to Avaya IP Office to work with the ProSBC.
Please visit the following link for more details [https://support.avaya.com/products/P0160/ip-office-platform Avaya Support].

=Avaya IP Office SIP Trunk Configuration=

1. First, please ensure that the '''Avaya IP Office SIP Trunk Channels''' license key is available to allow SIP trunking.

 [[Image:avaya_license.png|500px]] 

2. The '''Avaya IP Office''' LAN settings in this example are shown below. The IP address in the one that was set for the ProSBC NAP as shown in the '''LAN Settings -> IP Address'''. Ensure that '''SIP Trunks Enable''' option is set to allow SIP trunking. Ensure that '''Firewall/NAT Type''' configurations are set to your local requirements.

 [[Image:avaya_system_settings.png|500px]] 

3. The '''Telephony''' settings are öostly use defaults. The '''Inhibit Off-Switch Forward/Transfer''' must be disabled to allow call forwarding or call transferring towards the SIP Trunk of the Avaya IP Office.

 [[Image:avaya_telephony_settings.png|500px]] 

4. Please ensure that at minimum the G.711 codecs are set and the RFC2833 Default payload value conforms to the one set in the ProSBC Profile

 [[Image:avaya_voip_settings.png|500px]] 

5. The ProSBC related SIP Line here is used as follows

 [[Image:avaya_sip_settings.png|500px]] 

* The '''ITSP Domain Name''' is left blank as this allows using the provided '''ITSP Proxy Address''' field value that will be set in the '''Transport''' tab.
* '''In Service''' must be selected for enabling the '''SIP Line'''.
* '''Check OOS''' is also set for enabling '''SIP Options''' as a keep alive.

6. The '''ITSP Proxy Address''' is set to the ProSBC IP address. You can change the '''Network Configuration''' values or leave as their defaults.

 [[Image:avaya_transport_settings.png|500px]] 

7. The '''Call Details'' of the ProSBC related SIP line are used as shown below

 [[Image:avaya_calldetails_settings.png|500px]] 

8. The '''Codec Selection''' is used with a '''Custom''' codec selection.In our example, we used G.711 codec. You can select other codecs too. But you need to be sure the ITSP must support other codecs too. Otherwise, you will need to use a transcoding device. You can select '''Re-Invite Supported''' and other parameters too

 [[Image:avaya_codec_settings.png|500px]] 

9. '''Short Code''' Section you can configure which codes will passthrough through ProSBC.

 [[Image:avaya_shortcode_settings.png|500px]] 

10. The '''Incoming Call Route''' entry for the ProSBC is shown next. The dot symbol for the '''Destination''' value matches the '''Incoming Number''' field. In this example this field is blank, so any destination value will match.

 [[Image:avaya_incomingroute_settings.png|500px]]

ProSBC:Cisco UCM

2021-03-11T12:26:23Z

Luc Morissette: /* Troubleshooting */

{{DISPLAYTITLE:ProSBC:Cisco UCM 12 with ProSBC}}

=Introduction=

This Configuration Note describes how to set up Telcobridges ProSBC for interworking with Cisco Unified Telecommunications Manager 12.

==Prerequisites==
*[[ProSBC|ProSBC]] devices must be installed as described in their respective with release 3.0.x/3.1.x. Release 3.0.x is not supported for TCP connections [[Product_Installation_SBC|installation guides]].
*Cisco Unified Communications Manager 12. For additional information on Cisco UCM, visit [https://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-version-12-0/model.html Cisco Support].

==Example Environments for SIP Trunking with Cisco UCM==

[[Image:Cisco_ucm.png|800px| ]]

==Example Configuration==

Step by step example SIP Trunk configuration.
*[[ProSBC:Cisco SIP Trunk Configuration:Cisco_UCM_Trunk|Adding ProSBC as a SIP Trunk in Cisco UCM]]
*[[ProSBC:Cisco SIP Trunk:Configuration_A|SIP Trunk Configuration Instruction with Cisco UCM]]

==Troubleshooting==

{| 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;" | Call Trace
! 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;" | Test Call
! 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;" | TBReport
! 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;" | Advanced Troubleshooting of ProSBC
|-

| valign="top" |
*[[Toolpack:Configuring_Call_Trace_D|Configure call trace]]
*[[Toolpack:Retrieving_Call_Trace_C|Retrieve call trace]]

| valign="top" |
*[[Creating_A_Test_Call_B|Creating a Test Call]]

| valign="top" |
*[[TBReport|Capture a report of the system]]

| valign="top" |
*[[FreeSBC_Troubleshooting|Advanced Troubleshooting of ProSBC]]
|}

ProSBC:Sippy SIP Trunk Configuration:Avaya IPOffice Trunk

2021-03-11T08:56:33Z

Serdar Civici:

{{DISPLAYTITLE:Avaya IP Office Trunk Creation}}

=Introduction=
This document provides instructions on how to add a SIP Trunk to Avaya IP Office to work with the ProSBC.
Please visit the following link for more details [https://www.sippysoft.com/ Avaya Support].

=Avaya IP Office SIP Trunk Configuration=

1. First, please ensure that the '''Avaya IP Office SIP Trunk Channels''' license key is available to allow SIP trunking.

[[Image:avaya_license.png|500px]]

2. The '''Avaya IP Office''' LAN settings in this example are shown below. The IP address in the one that was set for the ProSBC NAP as shown in the '''LAN Settings -> IP Address'''. Ensure that '''SIP Trunks Enable''' option is set to allow SIP trunking. Ensure that '''Firewall/NAT Type''' configurations are set to your local requirements.

[[Image:avaya_system_settings.png|500px]]

3. The '''Telephony''' settings are öostly use defaults. The '''Inhibit Off-Switch Forward/Transfer''' must be disabled to allow call forwarding or call transferring towards the SIP Trunk of the Avaya IP Office.

[[Image:avaya_telephony_settings.png|500px]]

4. Please ensure that at minimum the G.711 codecs are set and the RFC2833 Default payload value conforms to the one set in the ProSBC Profile

[[Image:avaya_voip_settings.png|500px]]

5. The ProSBC related SIP Line here is used as follows

[[Image:avaya_sip_settings.png|500px]]

* The '''ITSP Domain Name''' is left blank as this allows using the provided '''ITSP Proxy Address''' field value that will be set in the '''Transport''' tab.
* '''In Service''' must be selected for enabling the '''SIP Line'''.
* '''Check OOS''' is also set for enabling '''SIP Options''' as a keep alive.

6. The '''ITSP Proxy Address''' is set to the ProSBC IP address. You can change the '''Network Configuration''' values or leave as their defaults.

[[Image:avaya_transport_settings.png|500px]]

7. The '''Call Details'' of the ProSBC related SIP line are used as shown below

[[Image:avaya_calldetails_settings.png|500px]]

8. The '''Codec Selection''' is used with a '''Custom''' codec selection.In our example, we used G.711 codec. You can select other codecs too. But you need to be sure the ITSP must support other codecs too. Otherwise, you will need to use a transcoding device. You can select '''Re-Invite Supported''' and other parameters too

[[Image:avaya_codec_settings.png|500px]]

9. '''Short Code''' Section you can configure which codes will passthrough through ProSBC.

[[Image:avaya_shortcode_settings.png|500px]]

10. The '''Incoming Call Route''' entry for the ProSBC is shown next. The dot symbol for the '''Destination''' value matches the '''Incoming Number''' field. In this example this field is blank, so any destination value will match.

[[Image:avaya_incomingroute_settings.png|500px]]

ProSBC:Avaya IP Office

2021-03-11T08:09:36Z

Luc Morissette: /* Troubleshooting */

{{DISPLAYTITLE:ProSBC:Avaya IP Office with ProSBC}}

=Introduction=

This Configuration Note describes how to set up Telcobridges ProSBC for interworking with Avaya IP Office.

==Prerequisites==
*[[ProSBC|ProSBC]] devices must be installed as described in their respective with release 3.0.x/3.1.x. Release 3.0.x is not supported for TCP connections [[Product_Installation_SBC|installation guides]].
*Avaya IP Office R11. For additional information on Avaya IP Office, visit [https://support.avaya.com/products/P0160/ip-office-platform/ Avaya Support].

==Example Environments for SIP Trunking with Avaya IP Office==

 [[Image:avaya_ip_office.png|800px| ]] 

==Example Configuration==

Step by step example SIP Trunk configuration.
*[[ProSBC:Avaya SIP Trunk Configuration:Avaya_IPOffice_Trunk|Adding ProSBC as a SIP Trunk in Avaya IP Office]]
*[[ProSBC:Avaya SIP Trunk:Configuration_A|SIP Trunk Configuration Instruction with Avaya IP Office]]

==Troubleshooting==

{| 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;" | Call Trace
! 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;" | Test Call
! 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;" | TBReport
! 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;" | Advanced Troubleshooting of ProSBC
|-

| valign="top" |
*[[Toolpack:Configuring_Call_Trace_D|Configure call trace]]
*[[Toolpack:Retrieving_Call_Trace_C|Retrieve call trace]]

| valign="top" |
*[[Creating_A_Test_Call_B|Creating a Test Call]]

| valign="top" |
*[[TBReport|Capture a report of the system]]

| valign="top" |
*[[FreeSBC_Troubleshooting|Advanced Troubleshooting of ProSBC]]
|}

ProSBC:Sippy SIP Trunk Configuration:Sippy Trunk

2021-03-10T08:30:00Z

Serdar Civici:

{{DISPLAYTITLE:Sippy SIP Trunk Creation}}

=Introduction=
This document provides instructions on how to add a SIP Trunk to Sippy Server to work with the ProSBC.
Please visit the following link for more details about [https://support.sippysoft.com/support/solutions Creating a SIP Trunk in Sippy Server]

=Sippy SIP Trunk Configuration=
1. Login into the administration portal via the IP address of the machine that is running Sippy.

2. Select the '''Vendors -> My Vendors -> Vendors'''.

 [[Image:vendors_1.png|500px]] 

3. Click to '''Add''' button under the '''Add Vendor''' section

 [[Image:vendors_add.png|500px]] 

4. You will be required to fill in the following fields in order to create a new vendor

 [[Image:vendors_details.png|500px]] 

*'''Vendor Name:''' Give a name to this vendor. We used Telcobridges.

5. You can fill in other pieces of information too and click on '''Save&Close''' button
6. Find the newly created vendor in the Vendors list and click on '''Open Connections''' link

 [[Image:open_connection.png|500px]] 

7. Click to '''Add''' button under the '''Add Connection''' section

 [[Image:add_connection.png|500px]] 

8. You will be required to fill in the following fields in order to create a new connection

 [[Image:connection_details.png|500px]] 

*'''Connection Name''' Give a name to this connection. We used Telcobridges - ProSBC
*'''Protocol''' Select the protocol for this connection. ProSBC only use '''SIP''' protocol
*'''Destination''' Destination of this connection. It can be IP address or FQDN of the ProSBC
*You can also fill other parts as your requirements and click on '''Save&Close''' button
9. To route the calls to ProSBC, you need to add a '''Destination Sets''' and assign a route. To add a Destination Set please go to '''Vendors -> Routing -> Destination Sets'''

 [[Image:destination_sets.png|500px]] 

10. Click to '''Add''' button under the '''Add Destination Set''' section

 [[Image:add_destination_sets.png|500px]] 

11. You will be required to fill in the following fields in order to create new destinations sets

 [[Image:destination_sets_details.png|500px]] 
*'''Name''' Give a name to this destination set.
*You can also fill other parts as your requirements and click on '''Save&Close''' button

12. Find the newly created destination set in the Vendors list and click on '''Open Routes''' link
13. Click to '''Add''' button under the '''Add Route''' section

 [[Image:add_destination_sets_routes.png|500px]] 

14. You will be required to fill in the following fields in order to create a new route
 [[Image:destination_sets_routes_details.png|500px]] 
*'''Prefix'' Enter the prefix for this route. You can add multiple routes to send multiple prefixes from the same Route.
15. You need to assign the Routing Group for Vendor and the Destination set. To do that, go to '''Vendors -> Routing -> Routing Groups'''

 [[Image:routing_groups.png|500px]] 

16.Click to '''Add''' button under the '''Add Routing Group''' section

 [[Image:add_routing_groups.png|500px]] 

17. You will be required to fill in the following fields in order to create a new routing group

 [[Image:routing_groups_details.png|500px]] 
*''' Group Name'' Give a name to this group
* From the Routing Entries drop-down menus select the newly created vendor from '''Vendor''' and select newly created destination set from '''Destination Set'''

Until now, you configured a connection in Sippy to send calls outside from ProSBC. To receive calls from ProSBC to Sippy you need to the following

1. You need to create a new account. To create a new account go to '''Customers -> My Customers -> Accounts'''

 [[Image:accounts.png|500px]] 

2. Click to '''Add''' button under the '''Add Account''' section

 [[Image:add_account.png|500px]] 

3. You will be required to fill in the following fields in order to create a new account

 [[Image:account_details.png|500px]] 

*'''Account Name''' Give a name to this account
*'''VoIP Login''' It is the same as the account name.
*'''VoIP Password''' If you are going to use registration to this trunk, you need to set a password.
* You can also fill other parts as your requirements and click on '''Save&Close''' button
4. Find the newly created account in the Account list. You can use '''Filter''' section to search.

 [[Image:account_search.png|500px]] 

5. Use the Action menu to enter '''Authentication Rules''' for the new account

 [[Image:account_authentication_rules.png|500px]] 

6. Click to '''Add''' button under the '''Add Authentication Rule''' section

 [[Image:add_authentication_rule.png|500px]] 

7. You will be required to fill in the following fields in order to create an Authentication Rule

 [[Image:account_authentication_rules_details.png|500px]] 

*'''Protocol''' Select the protocol for this connection. ProSBC only use '''SIP''' protocol
*'''Remote IP Address''' IP address of ProSBC. The Sippy will accept the calls if received from this IP address
* You can also fill other parts as your requirements and click on '''Save&Close''' button

8.The next step is to create an incoming trunk. Use the Action menu to enter '''Trunk''' for the new trunk configuration

 [[Image:trunks.png|500px]] 

9. Click to '''Add New''' button under the '''Add Trunk''' section

 [[Image:add_trunks.png|500px]] 

10. You will be required to fill in the following fields in order to create a Trunk

 [[Image:Trunks_details.png|500px]] 

*'''Name''' Give a name to this trunk
*'''Main Destination''' Enter ProSBC IP address in this section
* You can also fill other parts as your requirements and click on '''Save&Close''' button

11. The last step is to modify the incoming routing. To modify the routing, use the Action menu to enter '''Incoming Routing'''

 [[Image:incoming_routing.png|500px]] 

12. Use '''Action''' symbol to modify this routing

 [[Image:incoming_routing_modify.png|500px]] 

13. Select the trunk for this route

 [[Image:incoming_routing_trunk_select.png|500px]] 

* Select the newly created trunk from '''Trunk''' drop-down menu

ProSBC:Sippy SIP Trunk:Configuration A

2021-03-10T07:49:45Z

Serdar Civici:

=== '''''Applies to version: v3.1''''' ===

{{DISPLAYTITLE:SIP Trunk Configuration Instruction with Avaya IP Office}}

=Introduction=
SIP Trunk Configuration Instruction with Avaya IP Office Example Configuration provides you with a step-by-step SIP Trunk Configuration of [[FreeSBC|ProSBC]] with Avaya IP Office systems, using the Web Portal configuration tool. Complete general installation configuration steps, before you begin configuring your specific scenario. Please check how to configure the SIP Trunk in Avaya IP Office for ProSBC from [[ProSBC:Sippy SIP Trunk Configuration:Avaya_IPOffice_Trunk|Adding ProSBC as a SIP Trunk in Avaya IP Office]]

=Avaya IP Office SIP Trunk Example=

[[Image:avaya_ip_office.png|800px| ]]

====Configuration Steps====

{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 1) Create IP Network
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 2) Create Protocol Stack
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 3) Create Call Route
|-

| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_C|Configuring an IP Virtual Port]]
*[[Toolpack:Configuring_Vlan_SBC_A|Configuring a VLAN]]
*[[Toolpack:Configuring_IP_Interface_SBC_A|Configuring IP Interfaces]]
*[[Toolpack:Creating_an_IP_Port_Range_SBC_A|Create an IP port range]]

| valign="top" |
*[[Toolpack:Creating_an_IP_Port_Range_SBC A|Create an IP port range]]
*[[Toolpack:Creating_a_SIP_Stack_SBC A|Create a SIP stack]]
*[[Toolpack:Creating_a_SIP_Transport_Server_SBC A|Create a SIP transport server]]
*[[Toolpack:Modify_Profile_Sbc_A|Modify profile]]
*[[Toolpack:Allocating_a_SIP_Network_Access_Point_(NAP)_SBC A|Allocate a SIP NAP]]

| valign="top" |
*[[Toolpack:Creating_a_First_Call_Route E|Create a first call route]]

|}

= NAP Configuration =

* See [[Toolpack:Allocating a SIP Network Access Point (NAP) SBC A|Create SIP NAP]]
** Here, You must create two NAPs, one SIP NAP will be Sippy NAP and the other NAP will be for the SIP trunk provided by ITSP

ProSBC:Sippy

2021-03-10T07:46:11Z

Luc Morissette: /* Troubleshooting */

{{DISPLAYTITLE:ProSBC:Sippy Configuration with ProSBC}}

=Introduction=

This Configuration Note describes how to set up Telcobridges ProSBC for interworking with Sippy Soft Switch.

==Prerequisites==
*[[ProSBC|ProSBC]] devices must be installed as described in their respective with release 3.0.x/3.1.x. Release 3.0.x is not supported for TCP connections [[Product_Installation_SBC|installation guides]].
*Sippy Soft Switch. For additional information on Sippysoft, visit [https://www.sippysoft.com/ Sippysoft official web site].

==Example Environments for SIPTrunking with Sippysoft==

[[Image:sippysoft_Trunk.png|800px| ]]

==Example Configuration==

Step by step example SIP Trunk configuration.
*[[ProSBC:Sippy SIP Trunk Configuration:Sippy_Trunk|Adding ProSBC as a SIP Trunk in Sippy Server]]
*[[ProSBC:Sippy SIP Trunk:Configuration_A|SIP Trunk Configuration Instruction with Sippy Server]]

==Troubleshooting==

{| 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;" | Call Trace
! 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;" | Test Call
! 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;" | TBReport
! 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;" | Advanced Troubleshooting of ProSBC
|-

| valign="top" |
*[[Toolpack:Configuring_Call_Trace_D|Configure call trace]]
*[[Toolpack:Retrieving_Call_Trace_C|Retrieve call trace]]

| valign="top" |
*[[Creating_A_Test_Call_B|Creating a Test Call]]

| valign="top" |
*[[TBReport|Capture a report of the system]]

| valign="top" |
*[[FreeSBC_Troubleshooting|Advanced Troubleshooting of ProSBC]]
|}

ProSBC:Twilio Trunking:Example A

2021-03-04T06:59:49Z

Serdar Civici:

{{DISPLAYTITLE:Twilio Elastic SIP Trunking Configuration}}

=Introduction=
This article provides you with a step-by-step Elastic SIP Trunk Configuration on Twilio. In this guide FQDN is ('''telcobridges.pstn.twilio.com''') configured in the Twilio console. You can find more details about how to create an Elastic Trunking in Twilio from the following link [https://www.twilio.com/docs/sip-trunking#configure-trunks Create and Configure Trunks]

=Twilio Elastic SIP Trunk Configuration=

From your [https://www.twilio.com/console Twilio Console], navigate to the [https://www.twilio.com/console/sip-trunking/dashboard Elastic SIP Trunking] area ( or click on the [[Image:twilio_sip_icon.png|20px]] icon on the left vertical navigation bar)

 [[Image:twilio_trunk.png|300px]] 

==Create a new IP-ACL==

Click on [https://www.twilio.com/console/sip-trunking/authentication/ip-acls Authentication] in the left navigation, and then click on [https://www.twilio.com/console/sip-trunking/authentication/ip-acls IP Access Control Lists].

 [[Image:twilio_sip_acl.png|300px]] 

In this example, an IP-ACL is created with the name: "MyExampleACL". Add your SBCs IP addresses to the IP-ACL you create.

 [[Image:twilio_myexample_acl.png|800px]] 

==Create a new Trunk==
For each geographical region desired (e.g., North America, Europe), create a new Elastic SIP Trunk.

Now click on [[Image:twilio_trunk_icon.png|40px]] again on the left vertical navigation bar, and create a new Trunk.
 [[Image:twilio_new_trunk.png|500px]] 
Under the '''General Settings''' you can enable different features as desired
 [[Image:twilio_features.png|500px]] 
In the '''Termination section''', select a Termination SIP URI.
 [[Image:twilio_termination.png|500px]] 
Click on '''"Show localized URI's"''' and copy and paste this information as you will use this on your SBC to configure your Trunk.
 [[Image:twilio_localized.png|500px]] 
or
Assign the IP ACL ("MyExampleACL" ) that you created in the previous step.
 [[Image:twilio_authentication.png|500px]] 
In the '''Origination''' section, we'll add Origination URI's to route traffic towards your TelcoBridges SBC. The recommended practice is to configure a redundant mesh per geographic region (in this context a region is one of North America, Europe, etc). In this case, we configure two Origination URIs, each egressing from a different Twilio Edge.

Click on ‘Add New Origination URI’, we'll depict the configuration for North America:
 [[Image:twilio_orgination_url.png|500px]] 
Continue to add the other Origination URIs if desired. Origination URIs are listed as follows:
 [[Image:twilio_orgination_url_1.png|500px]] 
In this example, Origination traffic is routed via Twilio’s Ashburn edge, if that fails then we'll route from Twilio’s Umatilla edge.

==Associate Phone Numbers on your Trunk==
In the '''Numbers''' section of your Trunk, add the Phone Numbers that you want to associate with each Trunk. Remember to associate the Numbers from a given country in the right Trunk. For example, associate US & Canada Numbers with the North American Trunk and European Numbers with the European Trunk etc.
 [[Image:twilio_numbers.png|500px]]

ProSBC:Twilio

2021-03-04T06:42:46Z

Luc Morissette: /* Troubleshooting */

=Introduction=

[https://www.twilio.com/docs/sip-trunking Twilio Elastic SIP Trunking] is a cloud-based solution that provides connectivity for IP-based communications infrastructure to connect to the PSTN for making and receiving telephone calls to the rest of the world via any broadband internet connection. Twilio’s Elastic SIP Trunking service automatically scales, up or down, to meet your traffic needs with unlimited capacity. In just minutes you can deploy globally with Twilio’s easy-to-use self-service tools without having to rely on slow providers.

Sign up for a [https://www.twilio.com/try-twilio free Twilio trial] and learn more about [https://www.twilio.com/docs/sip-trunking configuring your Twilio Elastic SIP Trunk]

[[ProSBC|ProSBC]] is connects your IP-PBX to Twilio Elastic SIP Trunking. This article describes how to connect ProSBC to Twilio Elastic SIP Trunking.

==Prerequisites==
*[[ProSBC|ProSBC]] devices must be installed as described in their respective [[Product_Installation_SBC|installation guides]].
*Twilio Elastic SIP Trunking Account. Please visit the following link for more details about [https://www.twilio.com/docs/sip-trunking Twilio Elastic SIP Trunking]

==Example Environments for SIPTrunking with Twilio==

[[Image:Twilio_Trunking.png|800px| ]]

==Example Configuration==

Step by step example SIP Trunk configuration.
*[[ProSBC:Twilio Trunking:Example_A|Twilio Elastic SIP Trunking Configuration]]
*[[ProSBC:ProSBC Configuration Twilio Trunking:Example_A|ProSBC Configuration for Twilio Elastic SIP Trunking]]

==Troubleshooting==

{| 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;" | Call Trace
! 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;" | Test Call
! 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;" | TBReport
! 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;" | Advanced Troubleshooting of ProSBC
|-

| valign="top" |
*[[Toolpack:Configuring_Call_Trace_D|Configure call trace]]
*[[Toolpack:Retrieving_Call_Trace_C|Retrieve call trace]]

| valign="top" |
*[[Creating_A_Test_Call_B|Creating a Test Call]]

| valign="top" |
*[[TBReport|Capture a report of the system]]

| valign="top" |
*[[FreeSBC_Troubleshooting|Advanced Troubleshooting of ProSBC]]
|}

Adding Benchmarking to your Routing scripts

2021-02-22T15:12:50Z

Luc Morissette: Updated the display function

{{DISPLAYTITLE:Adding benchmarking to any script}}
{| class="wikitable"
|-
|rowspan="3"|This article applies to:
|'''Product'''
|'''Version'''
|-
|ProSBC
|3.1
|-
|Tmedia
|2.9, 2.10, 3.0, 3.2
|}

Routing scripts need to be well designed to allow for maximum performance of a system. 
To help evaluating the performance of a script (or part of a script), you can use this benchmarking tool. 

Three lines need to be added. 
At the start of the script: 
require 'benchmark'
In the main class, before the function to evaluate: 
# Start benchmarking
bm = Benchmark.measure do
In the main class, after the function to evaluate: 
end #End benchamrking
log_trace 3, "It took #{'%.6f' % bm.real} seconds to do this function"
This will print in the gateway application log the time it took to run this function.

 
Click here to know [[How_to_troubleshoot_call_routing#Using_the_applications_log_files|how to get the log files]]

Tmonitor Support Page

2021-02-18T18:40:54Z

Allyntree:

{{DISPLAYTITLE:Tmonitor Support}}
__NOTOC__
<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Tmonitor _Overview_Page|'''Overview''']] | [[Tmonitor _Features_Page|'''Features''']] | [[Tmonitor _Solutions_Page|'''Solutions''']] | [[Tmonitor _Installation_Page|'''Installation''']] | [[Tmonitor _Configuration_Page|'''Configuration''']] | [[Tmonitor _Support_Page|'''Support''']]

*[[Media:TB_Support_Services_for_endusers_wiki_20180815.pdf‎|TB Support Services (.pdf)]]
*[[Media:TB_Return_and_Repair_Procedure_2018.pdf|TB Return and Repair procedure(.pdf)]]
*[[Support:Contacting TelcoBridges technical support|Contacting TB Support]]
*[[Support:Online_Training|Online Training]]
*[[Support:License_server|License Server]]
*[[Support:Time_tracking_tool|Time Tracking Tool]]
*[[:Category:FAQ|Frequently Asked Questions]]
*[[Support:Forums|Support Forums]]
*[[Support:How To Submit A Problem|Submitting an Issue]]
*[[Tmedia_Version_History|Tmedia Software Version History]]

'''Important Notices'''
*[[Field_notices|Field Notices]]
*[[Security_advisories |Security Advisories]]

'''Legal'''

*[[Media:TB_Product_Warranty_2018.pdf|Product Warranty]]
*[[Media:Terms & Conditions.pdf|Standard Terms & Conditions]]

'''Interoperability'''

*[[Interoperability:Vendors|Vendors]]
*[[Interoperability:Certifications|Certifications]]

'''Policies'''

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

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

Tmonitor Configuration Page

2021-02-18T18:40:44Z

Allyntree:

{{DISPLAYTITLE:Tmonitor Configuration}}
__NOTOC__
<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Tmonitor _Overview_Page|'''Overview''']] | [[Tmonitor _Features_Page|'''Features''']] | [[Tmonitor _Solutions_Page|'''Solutions''']] | [[Tmonitor _Installation_Page|'''Installation''']] | [[Tmonitor _Configuration_Page|'''Configuration''']] | [[Tmonitor _Support_Page|'''Support''']]

*[[Toolpack_Web_Portal|Provisioning]]

Tmonitor Installation Page

2021-02-18T18:40:32Z

Allyntree:

{{DISPLAYTITLE:Tmonitor Installation}}
__NOTOC__
<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Tmonitor _Overview_Page|'''Overview''']] | [[Tmonitor _Features_Page|'''Features''']] | [[Tmonitor _Solutions_Page|'''Solutions''']] | [[Tmonitor _Installation_Page|'''Installation''']] | [[Tmonitor _Configuration_Page|'''Configuration''']] | [[Tmonitor _Support_Page|'''Support''']]

*[[Installing Toolpack|Installing]]
*[[Upgrading Toolpack|Upgrading]]

Tmonitor Solutions Page

2021-02-18T18:40:19Z

Allyntree:

{{DISPLAYTITLE:Tmonitor Solutions}}
__NOTOC__
<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Tmonitor _Overview_Page|'''Overview''']] | [[Tmonitor _Features_Page|'''Features''']] | [[Tmonitor _Solutions_Page|'''Solutions''']] | [[Tmonitor _Installation_Page|'''Installation''']] | [[Tmonitor _Configuration_Page|'''Configuration''']] | [[Tmonitor _Support_Page|'''Support''']]

*[[Location-based services|Location-Based Services (LBS)]]
*[[Network monitoring|Network Monitoring]]

Tmonitor Features Page

2021-02-18T18:40:08Z

Allyntree:

{{DISPLAYTITLE:Tmonitor Features}}
__NOTOC__
<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Tmonitor _Overview_Page|'''Overview''']] | [[Tmonitor _Features_Page|'''Features''']] | [[Tmonitor _Solutions_Page|'''Solutions''']] | [[Tmonitor _Installation_Page|'''Installation''']] | [[Tmonitor _Configuration_Page|'''Configuration''']] | [[Tmonitor _Support_Page|'''Support''']]

*[[Tmonitor_Lawful_Intercept|Lawful Intercept]]
*[[Network_monitoring|Network Monitoring]]

Tmonitor Overview Page

2021-02-18T18:39:53Z

Allyntree:

{{DISPLAYTITLE:Tmonitor Overview}}
__NOTOC__

[[File:Tmonitor_grid.png|link=Tmonitor_Overview_Page|420px]]

<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Tmonitor _Overview_Page|'''Overview''']] | [[Tmonitor _Features_Page|'''Features''']] | [[Tmonitor _Solutions_Page|'''Solutions''']] | [[Tmonitor _Installation_Page|'''Installation''']] | [[Tmonitor _Configuration_Page|'''Configuration''']] | [[Tmonitor _Support_Page|'''Support''']]

*[[TM1000]]
*[[TM3000]]

Tdev Support Page

2021-02-18T18:39:07Z

Allyntree:

{{DISPLAYTITLE:Tdev Support}}
__NOTOC__
<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Tdev _Overview_Page|'''Overview''']] | [[Tdev _Features_Page|'''Features''']] | [[Tdev _Solutions_Page|'''Solutions''']] | [[Tdev _Installation_Page|'''Installation''']] | [[Tdev _Configuration_Page|'''Configuration''']] | [[Tdev _Support_Page|'''Support''']]

*[[Media:TB_Support_Services_for_endusers_wiki_20180815.pdf‎|TB Support Services (.pdf)]]
*[[Media:TB_Return_and_Repair_Procedure_2018.pdf|TB Return and Repair procedure(.pdf)]]
*[[Support:Contacting TelcoBridges technical support|Contacting TB Support]]
*[[Support:Online_Training|Online Training]]
*[[Support:License_server|License Server]]
*[[Support:Time_tracking_tool|Time Tracking Tool]]
*[[:Category:FAQ|Frequently Asked Questions]]
*[[Support:Forums|Support Forums]]
*[[Support:How To Submit A Problem|Submitting an Issue]]
*[[Tmedia_Version_History|Tmedia Software Version History]]

'''Important Notices'''
*[[Field_notices|Field Notices]]
*[[Security_advisories |Security Advisories]]

'''Legal'''

*[[Media:TB_Product_Warranty_2018.pdf|Product Warranty]]
*[[Media:Terms & Conditions.pdf|Standard Terms & Conditions]]

'''Interoperability'''

*[[Interoperability:Vendors|Vendors]]
*[[Interoperability:Certifications|Certifications]]

'''Policies'''

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

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

Tdev Configuration Page

2021-02-18T18:38:58Z

Allyntree:

{{DISPLAYTITLE:Tdev Configuration}}
__NOTOC__
<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Tdev _Overview_Page|'''Overview''']] | [[Tdev _Features_Page|'''Features''']] | [[Tdev _Solutions_Page|'''Solutions''']] | [[Tdev _Installation_Page|'''Installation''']] | [[Tdev _Configuration_Page|'''Configuration''']] | [[Tdev _Support_Page|'''Support''']]

*[[Toolpack_Web_Portal|Provisioning]]

Tdev Installation Page

2021-02-18T18:38:46Z

Allyntree:

{{DISPLAYTITLE:Tdev Installation}}
__NOTOC__
<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Tdev _Overview_Page|'''Overview''']] | [[Tdev _Features_Page|'''Features''']] | [[Tdev _Solutions_Page|'''Solutions''']] | [[Tdev _Installation_Page|'''Installation''']] | [[Tdev _Configuration_Page|'''Configuration''']] | [[Tdev _Support_Page|'''Support''']]

*[[Installing Toolpack|Installing]]
*[[Upgrading Toolpack|Upgrading]]
[[:Category:Tdev_OAM%26P|...more]]

Tdev Solutions Page

2021-02-18T18:38:33Z

Allyntree:

{{DISPLAYTITLE:Tdev Solutions}}
__NOTOC__
<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Tdev _Overview_Page|'''Overview''']] | [[Tdev _Features_Page|'''Features''']] | [[Tdev _Solutions_Page|'''Solutions''']] | [[Tdev _Installation_Page|'''Installation''']] | [[Tdev _Configuration_Page|'''Configuration''']] | [[Tdev _Support_Page|'''Support''']]

*[[Prepaid & postpaid calling|Prepaid & Postpaid Calling]]
*[[Ringback tones|Ringback Tones]]
*[[Unified communications|Unified Communications]]
[[:Category:Tdev_Solutions|...more]]

Tdev Features Page

2021-02-18T18:38:22Z

Allyntree:

{{DISPLAYTITLE:Tdev Features}}
__NOTOC__
<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Tdev _Overview_Page|'''Overview''']] | [[Tdev _Features_Page|'''Features''']] | [[Tdev _Solutions_Page|'''Solutions''']] | [[Tdev _Installation_Page|'''Installation''']] | [[Tdev _Configuration_Page|'''Configuration''']] | [[Tdev _Support_Page|'''Support''']]

*[[High_Availability_Overview|Redundancy & High Availability]]
*[[Tdev_Signaling_Protocols|Signaling Protocols]]
*[[Voice_codecs|Voice Codecs]]
[[:Category:Tdev_Features|...more]]

Tdev Overview Page

2021-02-18T18:38:12Z

Allyntree:

{{DISPLAYTITLE:Tdev Overview}}
__NOTOC__

[[File:Tdev_grid.png|link=Tdev_Overview_Page|400px]]

<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Tdev _Overview_Page|'''Overview''']] | [[Tdev _Features_Page|'''Features''']] | [[Tdev _Solutions_Page|'''Solutions''']] | [[Tdev _Installation_Page|'''Installation''']] | [[Tdev _Configuration_Page|'''Configuration''']] | [[Tdev _Support_Page|'''Support''']]

*[[TMP800]]
*[[TMP6400]]
*[[TMP6400-CTRL]]
*[[TMP6400-TMS]]

Tsig Support Page

2021-02-18T18:37:29Z

Allyntree:

{{DISPLAYTITLE:Tsig Support}}
__NOTOC__
<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Tsig_Overview_Page|'''Overview''']] | [[Tsig_Features_Page|'''Features''']] | [[Tsig_Solutions_Page|'''Solutions''']] | [[Tsig_Installation_Page|'''Installation''']] | [[Tsig_Configuration_Page|'''Configuration''']] | [[Tsig_Support_Page|'''Support''']]

*[[Media:TB_Support_Services_for_endusers_wiki_20180815.pdf‎|TB Support Services (.pdf)]]
*[[Media:TB_Return_and_Repair_Procedure_2018.pdf|TB Return and Repair procedure(.pdf)]]
*[[Support:Contacting TelcoBridges technical support|Contacting TB Support]]
*[[Support:Online_Training|Online Training]]
*[[Support:License_server|License Server]]
*[[Support:Time_tracking_tool|Time Tracking Tool]]
*[[:Category:FAQ|Frequently Asked Questions]]
*[[Support:Forums|Support Forums]]
*[[Support:How To Submit A Problem|Submitting an Issue]]
*[[Tmedia_Version_History|Tmedia Software Version History]]

'''Important Notices'''
*[[Field_notices|Field Notices]]
*[[Security_advisories |Security Advisories]]

'''Legal'''

*[[Media:TB_Product_Warranty_2018.pdf|Product Warranty]]
*[[Media:Terms & Conditions.pdf|Standard Terms & Conditions]]

'''Interoperability'''

*[[Interoperability:Vendors|Vendors]]
*[[Interoperability:Certifications|Certifications]]

'''Policies'''

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

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

Tsig Configuration Page

2021-02-18T18:37:18Z

Allyntree:

{{DISPLAYTITLE:Tsig Configuration}}
__NOTOC__
<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Tsig_Overview_Page|'''Overview''']] | [[Tsig_Features_Page|'''Features''']] | [[Tsig_Solutions_Page|'''Solutions''']] | [[Tsig_Installation_Page|'''Installation''']] | [[Tsig_Configuration_Page|'''Configuration''']] | [[Tsig_Support_Page|'''Support''']]

*[[Web Portal|Configuration: Web Portal]]

Tsig Installation Page

2021-02-18T18:37:05Z

Allyntree:

{{DISPLAYTITLE:Tsig Installation}}
__NOTOC__
<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Tsig_Overview_Page|'''Overview''']] | [[Tsig_Features_Page|'''Features''']] | [[Tsig_Solutions_Page|'''Solutions''']] | [[Tsig_Installation_Page|'''Installation''']] | [[Tsig_Configuration_Page|'''Configuration''']] | [[Tsig_Support_Page|'''Support''']]

*[[Datasheet|Datasheet]]
*[[Product_Installation|Installing]]
*[[Gateway_Upgrade|Upgrading]]
*[[Troubleshooting]]
*[[Product_Maintenance|Product Maintenance]]
*[[Gateway_Management|Gateway Management]]
[[:Category:Gateway_OAM&P|...more]]

Tsig Solutions Page

2021-02-18T18:36:54Z

Allyntree:

{{DISPLAYTITLE:Tsig Solutions}}
__NOTOC__
<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Tsig_Overview_Page|'''Overview''']] | [[Tsig_Features_Page|'''Features''']] | [[Tsig_Solutions_Page|'''Solutions''']] | [[Tsig_Installation_Page|'''Installation''']] | [[Tsig_Configuration_Page|'''Configuration''']] | [[Tsig_Support_Page|'''Support''']]

*[[Signaling_Gateway_Solutions|Signaling]]

Tsig Features Page

2021-02-18T18:36:44Z

Allyntree:

{{DISPLAYTITLE:Tsig Features}}
__NOTOC__
<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Tsig_Overview_Page|'''Overview''']] | [[Tsig_Features_Page|'''Features''']] | [[Tsig_Solutions_Page|'''Solutions''']] | [[Tsig_Installation_Page|'''Installation''']] | [[Tsig_Configuration_Page|'''Configuration''']] | [[Tsig_Support_Page|'''Support''']]

*[[Signaling_protocols|Signaling Protocols]]

Tsig Overview Page

2021-02-18T18:36:32Z

Allyntree:

{{DISPLAYTITLE:Tsig Overview}}
__NOTOC__

[[File:Tsig_grid.png|link=Tsig_Overview_Page|400px]]

<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Tsig_Overview_Page|'''Overview''']] | [[Tsig_Features_Page|'''Features''']] | [[Tsig_Solutions_Page|'''Solutions''']] | [[Tsig_Installation_Page|'''Installation''']] | [[Tsig_Configuration_Page|'''Configuration''']] | [[Tsig_Support_Page|'''Support''']]

*[[TSG800]]
*[[TSG3200]]

Trans Support Page

2021-02-18T18:35:53Z

Allyntree:

{{DISPLAYTITLE:Ttrans Support}}
__NOTOC__
<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Ttrans_Overview_Page|'''Overview''']] | [[Ttrans_Features_Page|'''Features''']] | [[Ttrans_Solutions_Page|'''Solutions''']] | [[Ttrans_Installation_Page|'''Installation''']] | [[Ttrans_Configuration_Page|'''Configuration''']] | [[Trans_Support_Page|'''Support''']]

*[[Media:TB_Support_Services_for_endusers_wiki_20180815.pdf‎|TB Support Services (.pdf)]]
*[[Media:TB_Return_and_Repair_Procedure_2018.pdf|TB Return and Repair procedure(.pdf)]]
*[[Support:Contacting TelcoBridges technical support|Contacting TB Support]]
*[[Support:Online_Training|Online Training]]
*[[Support:License_server|License Server]]
*[[Support:Time_tracking_tool|Time Tracking Tool]]
*[[:Category:FAQ|Frequently Asked Questions]]
*[[Support:Forums|Support Forums]]
*[[Support:How To Submit A Problem|Submitting an Issue]]
*[[Tmedia_Version_History|Tmedia Software Version History]]

'''Important Notices'''
*[[Field_notices|Field Notices]]
*[[Security_advisories |Security Advisories]]

'''Legal'''

*[[Media:TB_Product_Warranty_2018.pdf|Product Warranty]]
*[[Media:Terms & Conditions.pdf|Standard Terms & Conditions]]

'''Interoperability'''

*[[Interoperability:Vendors|Vendors]]
*[[Interoperability:Certifications|Certifications]]

'''Policies'''

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

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

Ttrans Configuration Page

2021-02-18T18:35:44Z

Allyntree:

{{DISPLAYTITLE:Ttrans Configuration}}
__NOTOC__
<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Ttrans_Overview_Page|'''Overview''']] | [[Ttrans_Features_Page|'''Features''']] | [[Ttrans_Solutions_Page|'''Solutions''']] | [[Ttrans_Installation_Page|'''Installation''']] | [[Ttrans_Configuration_Page|'''Configuration''']] | [[Trans_Support_Page|'''Support''']]

*[[Web Portal|Configuration: Web Portal]]

Ttrans Installation Page

2021-02-18T18:35:31Z

Allyntree:

{{DISPLAYTITLE:Ttrans Installation}}
__NOTOC__
<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Ttrans_Overview_Page|'''Overview''']] | [[Ttrans_Features_Page|'''Features''']] | [[Ttrans_Solutions_Page|'''Solutions''']] | [[Ttrans_Installation_Page|'''Installation''']] | [[Ttrans_Configuration_Page|'''Configuration''']] | [[Trans_Support_Page|'''Support''']]

*[[Datasheet|Datasheet]]
*[[Product_Installation|Installing]]
*[[Gateway_Upgrade|Upgrading]]
*[[Troubleshooting]]
*[[Product_Maintenance|Product Maintenance]]
*[[Gateway_Management|Gateway Management]]
[[:Category:Gateway_OAM&P|...more]]

Ttrans Solutions Page

2021-02-18T18:35:18Z

Allyntree:

{{DISPLAYTITLE:Ttrans Solutions}}
__NOTOC__
<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Ttrans_Overview_Page|'''Overview''']] | [[Ttrans_Features_Page|'''Features''']] | [[Ttrans_Solutions_Page|'''Solutions''']] | [[Ttrans_Installation_Page|'''Installation''']] | [[Ttrans_Configuration_Page|'''Configuration''']] | [[Trans_Support_Page|'''Support''']]

*[[Transcoding_Gateway_Solutions|Transcoding]]

Ttrans Features Page

2021-02-18T18:35:07Z

Allyntree:

{{DISPLAYTITLE:Ttrans Features}}
__NOTOC__
<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Ttrans_Overview_Page|'''Overview''']] | [[Ttrans_Features_Page|'''Features''']] | [[Ttrans_Solutions_Page|'''Solutions''']] | [[Ttrans_Installation_Page|'''Installation''']] | [[Ttrans_Configuration_Page|'''Configuration''']] | [[Trans_Support_Page|'''Support''']]

*[[Voice_codecs|Voice Codecs]]
*[[Network_monitoring|Network Monitoring]]

Ttrans Overview Page

2021-02-18T18:34:55Z

Allyntree:

{{DISPLAYTITLE:Ttrans Overview}}
__NOTOC__
[[File:Ttrans_grid.png|link=Ttrans_Overview_Page|420px]]

<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Ttrans_Overview_Page|'''Overview''']] | [[Ttrans_Features_Page|'''Features''']] | [[Ttrans_Solutions_Page|'''Solutions''']] | [[Ttrans_Installation_Page|'''Installation''']] | [[Ttrans_Configuration_Page|'''Configuration''']] | [[Trans_Support_Page|'''Support''']]

*[[TMGIP800]]
*[[TMGIP3200]]
*[[TMGIP7800]]

Tmedia Support Page

2021-02-18T18:33:46Z

Allyntree:

{{DISPLAYTITLE:Tmedia Support}}
__NOTOC__
<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Tmedia_Overview_Page|'''Overview''']] | [[Tmedia_Features_Page|'''Features''']] | [[Tmedia_Solutions_Page|'''Solutions''']] | [[Tmedia_Installation_Page|'''Installation''']] | [[Tmedia_Configuration_Page|'''Configuration''']] | [[Tmedia_Support_Page|'''Support''']]

*[[Media:TB_Support_Services_for_endusers_wiki_20180815.pdf‎|TB Support Services (.pdf)]]
*[[Media:TB_Return_and_Repair_Procedure_2018.pdf|TB Return and Repair procedure(.pdf)]]
*[[Support:Contacting TelcoBridges technical support|Contacting TB Support]]
*[[Support:Online_Training|Online Training]]
*[[Support:License_server|License Server]]
*[[Support:Time_tracking_tool|Time Tracking Tool]]
*[[:Category:FAQ|Frequently Asked Questions]]
*[[Support:Forums|Support Forums]]
*[[Support:How To Submit A Problem|Submitting an Issue]]
*[[Tmedia_Version_History|Tmedia Software Version History]]

'''Important Notices'''
*[[Field_notices|Field Notices]]
*[[Security_advisories |Security Advisories]]

'''Legal'''

*[[Media:TB_Product_Warranty_2018.pdf|Product Warranty]]
*[[Media:Terms & Conditions.pdf|Standard Terms & Conditions]]

'''Interoperability'''

*[[Interoperability:Vendors|Vendors]]
*[[Interoperability:Certifications|Certifications]]

'''Policies'''

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

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

Tmedia Configuration Page

2021-02-18T18:33:37Z

Allyntree:

{{DISPLAYTITLE:Tmedia Configuration}}
__NOTOC__
<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Tmedia_Overview_Page|'''Overview''']] | [[Tmedia_Features_Page|'''Features''']] | [[Tmedia_Solutions_Page|'''Solutions''']] | [[Tmedia_Installation_Page|'''Installation''']] | [[Tmedia_Configuration_Page|'''Configuration''']] | [[Tmedia_Support_Page|'''Support''']]

*[[Web Portal|Configuration: Web Portal]]

Tmedia Installation Page

2021-02-18T18:33:25Z

Allyntree:

{{DISPLAYTITLE:Tmedia Installation}}
__NOTOC__
<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Tmedia_Overview_Page|'''Overview''']] | [[Tmedia_Features_Page|'''Features''']] | [[Tmedia_Solutions_Page|'''Solutions''']] | [[Tmedia_Installation_Page|'''Installation''']] | [[Tmedia_Configuration_Page|'''Configuration''']] | [[Tmedia_Support_Page|'''Support''']]

*[[Datasheet|Datasheet]]
*[[Product_Installation|Installing]]
*[[Gateway_Upgrade|Upgrading]]
*[[Troubleshooting]]
*[[Product_Maintenance|Product Maintenance]]
*[[Gateway_Management|Gateway Management]]
[[:Category:Gateway_OAM&P|...more]]

Tmedia Solutions Page

2021-02-18T18:33:14Z

Allyntree:

{{DISPLAYTITLE:Tmedia Solutions}}
__NOTOC__
<div style='text-align: right;'>[[Main_Page_N|'''Return to main product page''']]</div>
[[Tmedia_Overview_Page|'''Overview''']] | [[Tmedia_Features_Page|'''Features''']] | [[Tmedia_Solutions_Page|'''Solutions''']] | [[Tmedia_Installation_Page|'''Installation''']] | [[Tmedia_Configuration_Page|'''Configuration''']] | [[Tmedia_Support_Page|'''Support''']]

*[[Carrier_Solutions|Carriers]]
*[[Operator_Solutions|Operators]]
*[[MVNO_&_MVNE_Solutions|MVNO & MVNE]]
*[[Call_Center_Solutions| Call Centers]]