# Introduction

Install, configure, and troubleshoot ProSBC, the TelcoBridges software session border controller, on bare metal, VMware, KVM, or public cloud.

The TelcoBridges ProSBC is our Session Border Controller (SBC) product. It provides a security, an IP network adaptation, and a peering solution. It is entirely software based on can be upgraded from 500 to 60,000 sessions (or 30,000 with 100% transcoding). The ProSBC is the most cost-effective SBC product for service providers and carriers currently available on the market that combines solid protection, IP-to-IP network adaptation and fast setup time in a single solution.

***

#### Quick Access Links

* [Customer Dashboard](https://dashboard.telcobridges.com/) 
* [TelcoBridges Website](https://telcobridges.com/)


# Characteristics

ProSBC and ProSBC+ feature comparison covering security, high availability, media handling, analytics, API access, and encryption pak options.

<table><thead><tr><th width="344">Package</th><th>ProSBC</th><th>ProSBC+</th></tr></thead><tbody><tr><td><strong>Standard Features:</strong></td><td></td><td></td></tr><tr><td>B2BUA, Topology Hiding, SIP Header Manipulation, SIP and RTP Protection, DOS/DDOS Protection, Dynamic Blacklist and Call Access Control, SIP Registration Forwarding, SIP Registration, Scanning Protection, Flexible Call Routing</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td></tr><tr><td><strong>High Availability Pak</strong></td><td></td><td></td></tr><tr><td>High Availability – No Loss of Service, +1 Server License Included</td><td></td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td></tr><tr><td><strong>Media Pak:</strong></td><td></td><td></td></tr><tr><td>Software Transcoding (uLaw to aLaw), Media bypass (No Anchoring), H/W Transcoding†, Media Playback and Recording†, SIPREC**</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td></tr><tr><td><strong>Analytics Pak</strong></td><td></td><td></td></tr><tr><td>Fraudulent Call Removal, Call Trace, Test Call Generation, Live Wireshark Capture, MOS Scoring</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td></tr><tr><td><strong>API/Connector Pak</strong></td><td></td><td></td></tr><tr><td>CDR Text/Radius, Radius AAA, RESTful API, SNMP, Lawful Interception, STIR/SHAKEN Integrations, External HTTP/HTTPS Routing/Robocall</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td></tr><tr><td><strong>Encryption Pak</strong></td><td></td><td></td></tr><tr><td>SIP over TLS, SRTP Pass-through, SRTP Encryption/Decryption</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td></tr><tr><td><strong>Scaling</strong></td><td></td><td></td></tr><tr><td>Maximum Sessions/Server</td><td>60,000††</td><td>60,000††</td></tr><tr><td>Max Endpoint Registrations</td><td>350,000</td><td>350,000</td></tr><tr><td>Max Network Access Points/ Trunk Groups</td><td>1,024</td><td>1,024</td></tr><tr><td><strong>Platform Support</strong></td><td></td><td></td></tr><tr><td>SBC as a Service** (Additional Charge)</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td></tr><tr><td>VMware™, KVM/OpenStack™, Bare metal server, VNF</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td></tr><tr><td>Amazon/AWS™</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td></tr><tr><td>Microsoft Azure™</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td></tr><tr><td><strong>Technical Support</strong></td><td></td><td></td></tr><tr><td>Access to ProSBC Documentation (Free)</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td></tr><tr><td>Online TelcoBridges training on YouTube (Free)</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td></tr><tr><td>Community Support via Forum (Free)</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td></tr><tr><td>Software Upgrades (Free)</td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td></tr><tr><td>Access to Live Support Staff</td><td><p>-Included for customers with >5,000 sessions</p><p></p><p>-Available for purchase for customers with &#x3C;5,000 sessions</p></td><td><p>-Included for customers with >5,000 sessions</p><p></p><p>-Available for purchase for customers with &#x3C;5,000 sessions</p></td></tr><tr><td>Accessibility</td><td>Email, Chat &#x26; Telephone</td><td>Email, Chat &#x26; Telephone</td></tr><tr><td>Professional Services</td><td>Available for purchase</td><td>Available for purchase</td></tr></tbody></table>


# Platforms

ProSBC deployment platforms: certified bare-metal servers with capacity tiers, virtualized VMware and KVM options, and public cloud installations.

Various platforms are available for running the ProSBC software:

## Baremetal

This is ideal for a large number of sessions with high performance. The ProSBC software will use all the server resources to get maximum output. The type of hardware will define what is the maximum capacity of the system. We have certified some platforms in the past (see [SBC Certified Hardware](#prosbc-certified-hardware)), however, since the baremetal servers evolve frequently, please contact our team for recommended configuration.

### ProSBC Certified Hardware

Note: Baremetal server must support the "Legacy BIOS mode with MBR partition"

#### List of Certified baremetal servers

* [Dell high performance server for 60,000 sessions](/initial-installation/1.-instructions-by-platform/baremetal-installation/sbc-certified-hardware/high-performance-baremetal-server)
* [Dell medium performance server for 30,000 sessions](/initial-installation/1.-instructions-by-platform/baremetal-installation/sbc-certified-hardware/medium-performance-baremetal-server)
* [Ciena Virtual Network Function (VNF) Customer Premises Equipment (CPE) for less than 10,000 sessions](/initial-installation/1.-instructions-by-platform/baremetal-installation/sbc-certified-hardware/ciena-3906mvi-server-for-customer-premises-equipment-cpe)
* [Qotom Barebone server Customer Premises Equipment (CPE) for less than 5,000 sessions](/initial-installation/1.-instructions-by-platform/baremetal-installation/sbc-certified-hardware/qotom-barebone-server-for-customer-premises-equipment-cpe)
* [Lanner Barebone server Customer Premises Equipment (CPE) for less than 5,000 sessions](/initial-installation/1.-instructions-by-platform/baremetal-installation/sbc-certified-hardware/lanner-barebone-server-for-customer-premises-equipment-cpe)
* [TelcoSystems Virtual Network Function (VNF) Universal Customer Premises Equipment (uCPE) for less than 4,000 sessions](/initial-installation/1.-instructions-by-platform/baremetal-installation/sbc-certified-hardware/telco-systems-virtualization-platform-on-lanner-nca-2510-server-for-customer-premises-equipment-cpe)

## Virtualized Platforms

*Vmware*, *KVM*: These platforms allow the flexibility to run the ProSBC software along with other services on the same hardware infrastructure. They allow for medium to high performance depending on the resources allocated to the ProSBC.

## Cloud Platforms

*Amazon AWS*, *Microsoft Azure*: These platforms allow for ease of deployment in multiple regions of the world without the need for infrastructure. A ProSBC can be spawned in a matter of minutes to run a voice service.


# 1. Instructions by platform

Choose a ProSBC installation path: bare metal, virtual self-hosted on Proxmox, VMware or KVM, or public cloud, plus sizing and network interface requirements.


# ProSBC Requirements Matrix

ProSBC sizing matrix: session capacity by network interface mode and tested server platform, covering emulated, para-virtualized, and SR-IOV setups.

This matrix lists the session capacities TelcoBridges has measured for ProSBC, and the network interface cards each configuration was tested with. Use it to size a deployment: find the session count you need, then check that your platform and NIC combination appears on that row.

### How to read the networking modes

The **Networking** column describes how the virtual machine reaches the physical network interface. The mode has a large effect on achievable session capacity.

* **Emulation** presents a software-emulated NIC to the guest. It is the most portable option and the slowest, because every packet passes through the hypervisor's emulation layer.
* **Para-virtualized** uses a driver that is aware it is running in a virtual machine (for example VMXNET3 or virtio). It avoids most of the emulation overhead and roughly doubles capacity over emulation on the same hardware.
* **Passthrough / SR-IOV** gives the virtual machine direct access to the physical NIC, bypassing the hypervisor's network stack. SR-IOV divides one physical card into several virtual functions so multiple guests can share it. This is the fastest virtualized option.
* **Physical** is a bare-metal install with no hypervisor in the path.

**RSS** is Receive Side Scaling, a NIC feature that spreads incoming packets across multiple CPU cores instead of interrupting a single core. It is required to reach the highest session counts, which is why it appears only on the larger configurations.

{% hint style="info" %}
**"Not tested" means exactly that.** A cell marked Not tested has not been measured by TelcoBridges in this combination. It is not a statement that the configuration is unsupported or that it will not work — only that no verified capacity figure exists for it. Contact [TelcoBridges support](mailto:support@telcobridges.com) if you need a figure for a combination that is not listed.
{% endhint %}

<table><thead><tr><th width="161">Sessions</th><th width="226">Networking</th><th width="160">Tested Server</th><th width="148">Platform</th><th>RSS</th><th width="150">1G i350, i210</th><th width="182">10G X520, X540</th><th>10G X710</th></tr></thead><tbody><tr><td>1000</td><td>emulation</td><td>R610</td><td>Proxmox/KVM</td><td>Not tested</td><td>Yes</td><td>Yes</td><td>Yes</td></tr><tr><td>1600</td><td>para-virtualized</td><td>R610</td><td>Proxmox/KVM</td><td>Not tested</td><td>Yes</td><td>Yes</td><td>Yes</td></tr><tr><td>4800</td><td>emulation</td><td>m5.10xlarge</td><td>AWS</td><td>Not tested</td><td>Not tested</td><td>Not tested</td><td>Not tested</td></tr><tr><td>5000</td><td>emulation</td><td>R610</td><td>VmWare</td><td>Not tested</td><td>Yes</td><td>Yes</td><td>Yes</td></tr><tr><td>5000</td><td>Physical</td><td>Atom</td><td>Baremetal</td><td>Not tested</td><td>Yes</td><td>Yes</td><td>Yes</td></tr><tr><td>8000</td><td>para-virtualized</td><td>R610</td><td>VmWare</td><td>Not tested</td><td>Not tested</td><td>Yes</td><td>Yes</td></tr><tr><td>13000</td><td>Passthrough/SR-IOV</td><td>R610</td><td>Proxmox/KVM/VmWare</td><td>Not tested</td><td>Not tested</td><td>Yes</td><td>Yes</td></tr><tr><td>25000</td><td>Physical</td><td>R610</td><td>Baremetal</td><td>Not tested</td><td>Not tested</td><td>Yes</td><td>Yes</td></tr><tr><td>26000</td><td>Passthrough/SR-IOV</td><td>R610</td><td>Proxmox/KVM/VmWare</td><td>Yes</td><td>Not tested</td><td>Not tested</td><td>Yes</td></tr><tr><td>42000</td><td>Physical</td><td>R610</td><td>Baremetal</td><td>Yes</td><td>Not tested</td><td>Yes</td><td>Yes</td></tr><tr><td>50000</td><td>Physical</td><td>R330 (MID)</td><td>Baremetal</td><td>Yes</td><td>Not tested</td><td>Yes</td><td>Yes</td></tr><tr><td>60000+</td><td>Physical</td><td>R330 (MID)</td><td>Baremetal</td><td>Yes</td><td>Not tested</td><td>Yes (2 ports)</td><td>Yes (2 ports)</td></tr></tbody></table>

### Related

* [Network Interface Requirements](/initial-installation/1.-instructions-by-platform/network-interface-requirements)
* [List of Supported Network Interface Cards](/initial-installation/1.-instructions-by-platform/baremetal-installation/list-of-supported-network-interface-cards)
* [SBC Certified Hardware](/initial-installation/1.-instructions-by-platform/baremetal-installation/sbc-certified-hardware)

<br>


# Network Interface Requirements

How many network interfaces a ProSBC deployment needs per topology, and how to wire the ctrl0/ctrl1 control interfaces in a 1+1 High Availability system.

This page describes how many network interfaces (NICs) a ProSBC deployment needs for each topology, and how to wire the control interfaces when ProSBC is deployed as a High Availability (1+1) system.

{% hint style="info" %}
**NIC** = Ethernet network interface. Interfaces marked with an asterisk (\*) must use an approved NIC card (for example, Intel I350-T4). See [List of Supported Network Interface Cards](/initial-installation/1.-instructions-by-platform/baremetal-installation/list-of-supported-network-interface-cards).
{% endhint %}

#### Interfaces required per deployment topology

| Deployment topology               | Management | VoIP\*                            | Transcoder RTP\* | Control ports (ctrl0/ctrl1) |
| --------------------------------- | ---------- | --------------------------------- | ---------------- | --------------------------- |
| Standalone                        | 1 NIC      | 1 NIC (or 2 to separate networks) | —                | —                           |
| Standalone with transcoder device | 1 NIC      | 1 NIC (or 2)                      | 2 NICs           | 2 NICs                      |
| 1+1 (per unit)                    | 1 NIC      | 1 NIC (or 2)                      | —                | 2 NICs                      |
| 1+1 with transcoder (per unit)    | 1 NIC      | 1 NIC (or 2)                      | 2 NICs           | 2 NICs                      |

Use two NICs for VoIP when you want to separate networks (for example, an access-side and a core-side network).

#### Connecting the control interfaces in a 1+1 system

When using ProSBC in a 1+1 architecture, you need two interfaces for redundancy, called **ctrl0** and **ctrl1**.

* **Without a transcoding device** — ctrl0 and ctrl1 can be connected **directly** between the two servers (or virtual machines).
* **With a transcoding device** — ctrl0 and ctrl1 **cannot** be connected directly, because these interfaces are also used to control the transcoding devices. They must be on a **private network** between the ProSBC controllers and the transcoding devices. On the transcoding device, these interfaces are named **eth0/eth1** (instead of ctrl0/ctrl1).

#### Related

* [List of Supported Network Interface Cards](/initial-installation/1.-instructions-by-platform/baremetal-installation/list-of-supported-network-interface-cards)
* [ProSBC Requirements Matrix](/initial-installation/1.-instructions-by-platform/prosbc-requirements-matrix)
* [Setting the Role to a Primary Unit in a 1+1 System](/configuration-details/configuration-by-web-portal-category/system-settings/setting-the-role-to-a-primary-unit-in-a-1+1-system)
* [Setting the Role to a Secondary Unit in a 1+1 System](/configuration-details/configuration-by-web-portal-category/system-settings/setting-the-role-to-a-secondary-unit-in-a-1+1-system)
* [Transcoding Unit Configuration](/configuration-details/configuration-by-use-case/transcoding-unit-configuration)


# Baremetal Installation

Minimum server requirements for a bare-metal ProSBC install: 64-bit server, USB or optical boot, management and SBC Ethernet interfaces, legacy BIOS.

### Requirements

Minimal server requirements:

* 64-bit server
* USB key for installation (or Optical disk drive)
* One Ethernet interface for management
* One or more Ethernet interfaces for SBC processing (LAN/WAN). Must be in the [List of supported NICs](/initial-installation/1.-instructions-by-platform/baremetal-installation/list-of-supported-network-interface-cards)
* Two Ethernet interfaces, if a 1+1 configuration is required
* Console access through serial port or keyboard/monitor ports or other (i.e. Dell iDrac)
* Support for the "Legacy BIOS mode with MBR partition" or UEFI (UEFI support new with version 3.1.117)
* BIOS setup for maximum performance (no dynamic CPU throttling)

<table><thead><tr><th width="150">Sessions</th><th width="100">CPU cores</th><th width="100">RAM</th><th width="100">Disk Space (SSD)</th><th width="200">Ethernet ports for SBC (LAN/WAN)**</th></tr></thead><tbody><tr><td>Up to 5,000</td><td>4</td><td>8 GB</td><td>40 GB</td><td>1 Gbps<br>2 X 1Gbps to separate LAN and WAN networks</td></tr><tr><td>5,000-20,000</td><td>6</td><td>16 GB</td><td>60 GB</td><td>1 X 10 Gbps<br>2 X 10Gbps to separate LAN and WAN networks</td></tr><tr><td>20,000-50,000</td><td>8</td><td>32 GB</td><td>80 GB</td><td>1 X 10 Gbps<br>2 X 10Gbps to separate LAN and WAN networks</td></tr><tr><td>Above 50,000</td><td>12</td><td>32 GB</td><td>100 GB</td><td>Multiple 10 Gbps</td></tr></tbody></table>

\*\* See list of supported Network Interface Cards (NICs) here: [List of supported NICs](/initial-installation/1.-instructions-by-platform/baremetal-installation/list-of-supported-network-interface-cards)

\
More details on HW/CPU/NIC requirements can be found here: [Requirements Matrix](/initial-installation/1.-instructions-by-platform/prosbc-requirements-matrix)\
Check here for a list of certified hardware platforms: [SBC Certified Hardware](/initial-installation/1.-instructions-by-platform/baremetal-installation/sbc-certified-hardware)

\
In most cases, a standard configuration will provide sufficient performance. To get maximum performance from a system, please open a case on [TelcoBridges support portal](https://telcobridges.odoo.com/).

### Getting the ISO

Please go to our [Dashboard](http://dashboard.telcobridges.com/) to get a copy of the latest SBC ISO.

### Installing the ISO

The installation process will reformat the server's disks and install all the necessary software.

#### Prepare an ISO onto a bootable USB flash drive or a DVD

Use a software application to burn the ISO image to a USB flash drive. On Windows, [Rufus ](https://rufus.ie/en/)is known to work with the ProSBC ISO, however, any similar application should work.\
When using Rufus, make sure you have these settings:

* Partition scheme: MBR
* Target system: BIOS or UEFI
* Volume label (keep default): "CENTOS 7 X8"
* File system: FAT32

Press START, then select:

* Write in ISO Image Mode (Recommended)

#### Physical installation steps

1. Identify which Ethernet networks you need and connect them to your server. Refer to Networking for more information. For ProSBC Transcoding and associated network setup, please also refer to [ProSBC:Transcoding and Network Setup](/configuration-details/configuration-by-use-case/transcoding-unit-configuration/baremetal-and-virtual-machine).
2. Burn the ISO onto a DVD or a USB flash drive
3. Get access to the console of the server. Usually, this is achieved by connecting a keyboard and screen to the server.
4. Insert the DVD in the optical drive of your server and boot from the DVD drive.
   * Alternatively, plug in your USB flash drive and boot from that drive.
5. The "Virtual Appliance Installer" menu should be displayed:<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/5/59/ISO_install_prompt.jpg/600px-ISO_install_prompt.jpg" alt=""><figcaption></figcaption></figure>

1. Press the 'R' key followed by the 'ENTER' key to start the installation<br>

<figure><img src="https://docs.telcobridges.com/w/images/a/a1/ISO_installing.jpg" alt=""><figcaption></figcaption></figure>

1. Wait for the installation process to complete. When the installation is complete, the server will automatically reboot.
   * Important: Make sure to remove the DVD from the drive while the server is rebooting. If you get back to "Virtual Appliance Installer", just eject the CD or remove the USB flash drive and reboot again.
2. It may take a couple of minutes for the system to be brought up after the first reboot. Until the Web Portal is accessible, you must not reboot the newly created machine to allow the installation to complete properly.

#### Assigning IP address

By default, all detected network interfaces will have DHCP enabled. This means, the server might already have an IP address assigned, if the network has a DHCP server running. In this case, you can display and use it to access the web portal configuration panel.

1. Retrieve an IP address assigned by DHCP

```
 # ifconfig
```

If you want to assign a static IP address, or there is no DHCP on your network, you will need to configure it manually.

1. Use the [tbchangeip](/initial-installation/2.-initial-configuration/initial-setup/sbc-management-ip-configuration), shell command and answer the questions to change your Ethernet interface address:

```
 # tbchangeip
```

Note: tbchangeip command applies for management interface (mgmt) only. This command does not apply for control interface (ctrl) nor voip interfaces (voip).

\
Note: No changes must be done to the repositories on the systems, and no other software should be installed unless written consent from TelcoBridges.

#### Accessing the SBC web portal

1. Open a web browser to the IP of your server, on port 12358. Example if your server address is 192.168.178.30, the URL would be:\
   [http://192.168.178.30:12358](http://192.168.178.30:12358/)
2. The SBC Configuration Wizard is displayed<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/e/e1/TSBC_WebPortal_Configuration_wizard.jpg/350px-TSBC_WebPortal_Configuration_wizard.jpg" alt=""><figcaption></figcaption></figure>

From here, you can go to [Web Portal Initial Configuration Guide](/initial-installation/2.-initial-configuration) to continue the installation, and/or optimize your server to get the maximum out of your server.

### Web Portal Initial Configuration

Click on the following link to pursue installation from the web portal: [Web Portal Initial Configuration](/initial-installation/2.-initial-configuration)


# List of Supported Network Interface Cards

Network interface cards tested with ProSBC in TelcoBridges labs, including Intel I210, I211, I350 and X710 adapters, and how to list adapters on a Linux server.

At least one network interface card (NIC) present on the system must be supported by the ProSBC.\
You can use this command on a linux server to find the list of Ethernet adapters available:

```
 lspci | grep Ethernet
```

Tested interfaces from Intel in TelcoBridges labs:

* I210, 1 Gbps (E1000 drivers)
* I211, 1 Gbps (E1000 drivers)
* I350, 1 Gbps (E1000 drivers)
* X540, 10 Gbps (ixgbe drivers)
* X710, 10 Gbps (i40e drivers)

\
Example of unsupported interfaces:

* Broadcom Limited NetXtreme II BCM5709 Gigabit Ethernet


# SBC Certified Hardware

Servers certified for ProSBC, from Dell platforms at 60,000 and 30,000 sessions down to Ciena, Qotom and Lanner CPE units, all requiring legacy BIOS with MBR.

Note: Baremetal server must support the "Legacy BIOS mode with MBR partition"

### List of certified baremetal servers

* [Dell high performance server for 60,000 sessions](/initial-installation/1.-instructions-by-platform/baremetal-installation/sbc-certified-hardware/high-performance-baremetal-server)
* [Dell medium performance server for 30,000 sessions](/initial-installation/1.-instructions-by-platform/baremetal-installation/sbc-certified-hardware/medium-performance-baremetal-server)
* [Ciena Virtual Network Function (VNF) Customer Premises Equipment (CPE) for less than 10,000 sessions](/initial-installation/1.-instructions-by-platform/baremetal-installation/sbc-certified-hardware/ciena-3906mvi-server-for-customer-premises-equipment-cpe)
* [Qotom Barebone server Customer Premises Equipment (CPE) for less than 5,000 sessions](/initial-installation/1.-instructions-by-platform/baremetal-installation/sbc-certified-hardware/qotom-barebone-server-for-customer-premises-equipment-cpe)
* [Lanner Barebone server Customer Premises Equipment (CPE) for less than 5,000 sessions](/initial-installation/1.-instructions-by-platform/baremetal-installation/sbc-certified-hardware/lanner-barebone-server-for-customer-premises-equipment-cpe)
* [TelcoSystems Virtual Network Function (VNF) Universal Customer Premises Equipment (uCPE) for less than 4,000 sessions](/initial-installation/1.-instructions-by-platform/baremetal-installation/sbc-certified-hardware/telco-systems-virtualization-platform-on-lanner-nca-2510-server-for-customer-premises-equipment-cpe)


# High Performance Baremetal Server

Dell R630 high performance ProSBC server tested to 60,000 sessions and 1,100 calls per second: dual Xeon E5-2643, 24GB RAM, NUMA optimized, iDRAC out-of-band.

This unit has been tested at up to 60,000 sessions, and 1,100 calls per second.

### Model

* Dell R630

### Characteristics

* Dual Xeon E5-2643, 6C/12T (6 cores/12 Threads), 3.4GHz
* 24GB RAM RDIMM, 2400MHz
* NUMA optimized for PCIe faster accesses
* Dell iDRAC6 out-of-band interface

### Network Interfaces

* Management: 2x 1Gbps copper
* Control: 2x 1Gbps copper
* VoIP/SBC interfaces: 4x 10Gbps SFP+ SR optics (850nm)

### High Availability & Redundancy

* Power supply redundancy
* Hardware RAID1 on 2x 200GB SSD

<details>

<summary>Click here for specific BIOS settings on this server</summary>

Upon initial bootup, type "F2" to enter setup

* Boot Settings
  * Boot Mode \[BIOS] (Tested mode was Legacy BIOS. Works with UEFI as well)
* Processor Settings
  * Virtualization Technology -> \[Disabled]
* System Profile Settings
  * CPU Power Management \[Maximum Performance]
  * Turbo Boost \[Disabled]

</details>

### Performance Data

<table><thead><tr><th width="100">vCPU</th><th width="100">vCPU dedicated</th><th width="100">RAM</th><th width="100">CPS</th><th width="100">CAPS</th><th width="100">Sessions</th><th width="100">Sessions with Transcoding</th><th width="100">No Anchoring</th></tr></thead><tbody><tr><td>12</td><td>yes</td><td>24 GB</td><td>1,100</td><td>1,400</td><td>60,000</td><td>30,000</td><td>60,000</td></tr></tbody></table>

### References

[Dell R630 server](https://www.dell.com/en-ca/work/shop/povw/poweredge-r630)


# Medium Performance Baremetal Server

Dell R330 medium performance ProSBC server tested to 30,000 sessions and 1,000 calls per second: single Xeon E3-1240, 16GB RAM, NUMA optimized for PCIe access.

This unit has been tested at up to 30,000 sessions and 1,000 calls per second.

### Model

* Dell R330

### Characteristics

* Single Xeon E3-1240, 4C/8T (4 cores/8 Threads), 3.5GHz
* 16GB RAM RDIMM, 2400MHz
* NUMA optimized for PCIe faster accesses

### Network Interfaces

* Management: 2x 1Gbps copper
* Control: 2x 1Gbps copper
* VoIP/SBC interfaces: 2x 10Gbps SFP+ SR optics (850nm) (or copper)

### High Availability & Redundancy

* Power supply redundancy
* Hardware RAID1 on 2x 200GB SSD

<details>

<summary>Click here for specific BIOS settings on this server</summary>

Upon initial bootup, type "F2" to enter setup

* Boot Settings
  * Boot Mode \[BIOS] (NOt UEFI)
* Processor Settings
  * Virtualization Technology -> \[Disabled]
* System Profile Settings
  * CPU Power Management \[Maximum Performance]
  * Turbo Boost \[Disabled]

</details>

### Performance Data

<table><thead><tr><th width="100">vCPU</th><th width="100">vCPU dedicated</th><th width="100">RAM</th><th width="100">CPS</th><th width="100">CAPS</th><th width="100">Sessions</th><th width="100">Sessions with Transcoding</th><th width="100">No Anchoring</th></tr></thead><tbody><tr><td>8</td><td>yes</td><td>16 GB</td><td>500</td><td>2,000</td><td>30,000</td><td>15,000</td><td>60,000</td></tr></tbody></table>

### References

[Dell R330 server](https://www.dell.com/en-ca/work/shop/povw/poweredge-r330)


# Ciena 3906mvi server for Customer Premises Equipment (CPE)

Ciena 3906mvi CPE platform for ProSBC, tested to 10,000 RTP sessions and 440 calls per second: Xeon D-1548, 32GB RAM, up to six 1Gbps VoIP interfaces.

This unit has been tested at up to 10,000 sessions with RTP and up to 440 calls per second.

### Model

* Ciena 3906mvi

### Characteristics

* Intel(R) Xeon (R) CPU D-1548 @ 2.0GHz, 8C/16T (8 cores/16 Threads)
* 32GB RAM

### Network Interfaces

* Management: 1x 1Gbps copper
* VoIP/SBC interfaces: Up to 6 1Gbps ethernet interface

### High Availability & Redundancy

* Dual power supply
* Single 480GB SSD

### Performance Data

<table><thead><tr><th width="100">vCPU</th><th width="100">vCPU dedicated</th><th width="100">RAM</th><th width="100">CPS</th><th width="100">CAPS</th><th width="100">Sessions</th><th width="100">No Anchoring</th></tr></thead><tbody><tr><td>6</td><td>yes</td><td>8 GB</td><td>440</td><td>790</td><td>10,000</td><td>40,000</td></tr><tr><td>4</td><td>yes</td><td>8 GB</td><td>330</td><td>650</td><td>10,000</td><td>40,000</td></tr><tr><td>2</td><td>yes</td><td>4 GB</td><td>90</td><td>230</td><td>5,000</td><td>5,000</td></tr></tbody></table>

### References

[Ciena 3906](https://www.ciena.com/products/3906)


# Qotom Barebone server for Customer Premises Equipment (CPE)

Qotom Q190G4-S02 barebone CPE for ProSBC, tested to 5,000 sessions and 130 calls per second: Celeron J1900, 4GB RAM, Intel I211 VoIP interfaces.

This unit has been tested at up to 5,000 sessions and 130 calls per second.

### Model

* Qotom-Q190G4-S02

### Characteristics

* Intel(R) Celeron(R) CPU J1900 @ 1.99GHz, 4 cores, no Hyperthreading
* 4GB RAM, 1300Mhz

### Network Interfaces

* Management: 1x 1Gbps copper
* VoIP/SBC interfaces: One or two 1Gbps ethernet interface (Intel I211)

### High Availability & Redundancy

* Single power supply
* Single 60GB SSD

<details>

<summary>Click here for specific BIOS settings on this server</summary>

Upon initial bootup, type "Del" or "Esc" to enter setup

* Main -> Set system date and time
* Advanced
  * ACPI Settings.
    * Restore AC power loss : Last State
    * ACPI Sleep State: Suspend Disable
  * Get Mac addresses
* Boot
  * Quiet boot: disabled
* Boot Override: Choose USB stick with SBC software (See procedure: [Baremetal Installation](/initial-installation/1.-instructions-by-platform/baremetal-installation))

</details>

### Performance Data

<table><thead><tr><th width="100">CPU</th><th width="100">CPU dedicated</th><th width="100">RAM</th><th width="100">Network Interfaces</th><th width="100">CPS</th><th width="100">CAPS</th><th width="100">Sessions</th></tr></thead><tbody><tr><td>4</td><td>yes</td><td>4 GB</td><td>up to 2</td><td>130</td><td>240</td><td>5,000</td></tr></tbody></table>

### References

[Qotom web site](http://www.qotom.net/)

* Note: Other variants of this server can provide better performances


# Lanner Barebone server for Customer Premises Equipment (CPE)

Lanner FW7525C barebone CPE for ProSBC, tested to 5,000 sessions and 100 calls per second: Atom C2518, 4GB RAM, 128GB SSD, 1Gbps management interface.

This unit has been tested at up to 5,000 sessions and 100 calls per second.

### Tested Model

* Lanner FW7525C (See link to Lanner Electronics Inc: [Lanner FW7525](http://www.lannerinc.com/products/network-appliances/x86-desktop-network-appliances/fw-7525) - specify the "FW7525C" when ordering)

### Characteristics

* CPU: Intel(R) Atom(TM) CPU C2518 @ 1.74GHz, 4 cores
* RAM: 4GB, 1300Mhz
* Disk: 128GB SSD

### Network Interfaces

* Management: 1x 1Gbps copper
* VoIP/SBC interfaces: Up to 5x 1Gbps interfaces (Intel I210 and I354)

### High Availability & Redundancy

* Single power supply (screwed in)
* Single 128GB SSD

<details>

<summary>Click here for specific BIOS settings on this server</summary>

Upon initial bootup, type "Del" or "Esc" to enter setup

* InterRCSetup
  * Restore on Power Loss \[Power On]
* Security
  * Administrator Password -> \[New\_password]
* Boot
  * Setup Prompt Timeout \[5]
  * Quiet Boot \[Disabled]

</details>

### Performance Data

<table><thead><tr><th width="100">CPU</th><th width="100">CPU dedicated</th><th width="100">RAM</th><th width="100">Network Interfaces</th><th width="100">CPS (Calls per second)</th><th width="100">CAPS (Call Attempts per second)</th><th width="100">Sessions</th></tr></thead><tbody><tr><td>4</td><td>yes</td><td>4 GB</td><td>2 (up to 5)</td><td>100</td><td>200</td><td>5000</td></tr></tbody></table>

### References

[Lanner web site](http://www.lannerinc.com/products/network-appliances/)


# Telco Systems virtualization platform on Lanner NCA-2510 server for Customer Premises Equipment(CPE)

Telco Systems platform on Lanner NCA-2510 for ProSBC, tested to 4,000 RTP sessions and 300 calls per second: Atom C3758, 16GB RAM, 1G and 10G ports.

This unit has been tested at up to 4,000 sessions with RTP and up to 300 calls per second.

### Model

* NCA-2510B

### Characteristics

* Intel(R) Atom(R) CPU C3758 @ 2.2GHz, 8C/8T (8 cores/8 Threads)
* 16GB RAM

### Network Interfaces

* Management: 1x 1Gbps copper
* VoIP/SBC interfaces: 4x 1Gbps ethernet copper interfaces and 4x 10Gbps ethernet SFP interfaces

### High Availability & Redundancy

* Single power supply
* Single 40GB SSD

### Performance Data

<table><thead><tr><th width="100">vCPU</th><th width="100">vCPU dedicated</th><th width="100">RAM</th><th width="100">CPS</th><th width="100">CAPS</th><th width="100">Sessions</th><th width="100">No Anchoring</th></tr></thead><tbody><tr><td>4</td><td>yes</td><td>8 GB</td><td>180</td><td>300</td><td>4,000</td><td>50,000</td></tr><tr><td>2</td><td>yes</td><td>4 GB</td><td>50</td><td>100</td><td>4,000</td><td>10,000</td></tr></tbody></table>

### References

* [Telco Systems web site](https://www.telco.com/)
* [Lanner Inc NCA2510](http://www.lannerinc.com/products/network-appliances/x86-rackmount-network-appliances/nca-2510)


# Virtual, self-hosted Installation

Deploy ProSBC on self-hosted virtualization: Proxmox KVM images and VMware vSphere, including network interface setup and passthrough configuration.


# Virtual - Proxmox

Install and run the ProSBC KVM image on a Proxmox platform. Requires root-level access to the Proxmox host; the web interface alone is not sufficient.

### Introduction

This step-by-step guide helps you to install and run the ProSBC KVM image on a Proxmox platform. The installation requires root-level access to the Proxmox host, and it cannot be completed with web-interface alone.

### Requirements

Minimal Cloud requirements:

* 64 bits infrastructures only
* Virtio NIC interface
* qemu-kvm CPU exposed as 'host' or minimally 'core2duo'
* One Ethernet adapter for management
* One or more Ethernet adapter(s) for data

<table><thead><tr><th width="150">Sessions</th><th width="100">CPU</th><th width="100">RAM</th><th width="100">Disk Space</th><th width="200">Ethernet ports</th></tr></thead><tbody><tr><td>Up to 5,000</td><td>2</td><td>4 Gb</td><td>40 Gb</td><td>1 Gbps</td></tr><tr><td>5,000-20,000</td><td>4</td><td>8 Gb</td><td>60 Gb</td><td>4 X 1 Gbps or 1 X 10 Gbps</td></tr><tr><td>20,000-50,000</td><td>4**</td><td>16 Gb</td><td>80 Gb</td><td>1 X 10 Gbps</td></tr><tr><td>Above 50,000</td><td>6**</td><td>24+ Gb</td><td>100 Gb</td><td>Multiple 10 Gbps</td></tr></tbody></table>

\*\* The CPU number is based on Intel R630 with Xeon E5-2643. Double the CPU number if your processor is from a earlier generations.

More details on the HW/CPU/NIC requirements can be found here: [RequirementsMatrix](/initial-installation/1.-instructions-by-platform/prosbc-requirements-matrix)

For better performance

* SR-IOV or MacVTap compatible NICs
* Overcommit set to 1:1
* No CPU (including hyperthreading) shared between infrastructure and computing section
* Dedicated memory allocation to VM

### Getting the Image

Go to our [ProSBC Download site](http://freesbc.telcobridges.com/pricing/) to get a copy of the latest ProSBC Image. In the Download Section, while filling out the form, choose the correct platform "KVM". As a result, you should receive freesbc\_kvm\_\[version].qcow2. Please, mention "Product Key" and keep containing email in a safe place.

### Upload Image File to Proxmox cloud

You need an SFTP client to upload ProSBC image to Proxmox. For example, using WinSCP SFTP Client . The next steps assumed that the image file freesbc\_kvm\_\[version].qcow2 resides in the /root directory

### Unzip the file

If you have received a .tar.gz file, unzip it with the command:

tar -xvzf \<filename>

### Create VM for ProSBC

Define the amount of CPUs and RAM according to requirements.

Follow the VM creation process by dialog tabs as indicated below:

1. General: choose VM name and location as usual. This manual uses VM ID 1000 as a reference.\ <br>

2. OS: check Do not use any media, keep default Linux OS with 4.X/3.X/2.6 Kernel.<br>

   <figure><img src="https://docs.telcobridges.com/w/images/thumb/6/67/Proxmox_OS.png/400px-Proxmox_OS.png" alt=""><figcaption></figcaption></figure>

3. Hard Disk: choose your favorite device type and keep all the rest to default.<br>

   <figure><img src="https://docs.telcobridges.com/w/images/thumb/2/2b/Proxmox_HDD.png/400px-Proxmox_HDD.png" alt=""><figcaption></figcaption></figure>

In newer Proxmox versions (screenshot from version 8.2), you can delete the suggested disk by clicking on the trash can.<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/e/ef/Proxmox_installation%2C_step_HDD.png/400px-Proxmox_installation%2C_step_HDD.png" alt=""><figcaption></figcaption></figure>

4\. CPU: choose core count. Important: CPU Type must be set to "host".<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/b/b5/Proxmox_CPU.png/400px-Proxmox_CPU.png" alt=""><figcaption></figcaption></figure>

5\. In the advanced area parameter "CPU units" may be increased to ensure that CPU resources will be allocated to ProSBC with priority.\
\
6\. Memory: Set the memory size

<figure><img src="https://docs.telcobridges.com/w/images/thumb/8/89/Proxmox_Memory.png/400px-Proxmox_Memory.png" alt=""><figcaption></figcaption></figure>

7\. Network: Set up the interface you will use for management according to your network configuration. Model VirtIO tested, any other may work too.<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/1/16/Proxmox_Network.png/400px-Proxmox_Network.png" alt=""><figcaption></figcaption></figure>

### Tune VM for your ProSBC

Go to the "Hardware" tab on your VM, and do the following:

* Remove CD/DVD Drive. We do not need it.
* Detach and delete Hard Disk. We do not need it and we will attach the KVM image later.
* Add network adapters according to your network configuration. Keep in mimd that a standalone ProSBC needs at least one adapter for management and one for voice, in the initial setup.

If you wish to have an HA configuration, then you need at least one more adapter for intra-cluster communications. Although, network adapters may be added at any time, it's a good idea to set up a correct network configuration at the start.

### Attaching image file to VM

Go to Proxmox host shell and copy the image file to VM's directory, root privileges required. For VM ID 1000 and image file, located in /root this will be:

```
  cp -v /root/freesbc_kvm_[version].qcow2 /var/lib/vz/images/1000/
```

After that, we need to force Proxmox to include this image to the VM config file and make it available for web-interface. Do that with shell command qm rescan

```
  # qm rescan
    rescan volumes...
    VM 1000: add unreferenced volume 'local:1000/freesbc_kvm_[version].qcow2' as 'unused0' to config.
  #
```

If qm rescan doesn't have the expected result, you can try following:

```
#
qm importdisk <vmid> <filename> <storage>
#
```

Return to the web-interface and VM's Hardware tab. Now the image referenced as "Unused Disk 0". Select it and press "Edit".

Select bus/device and put "Write through" to the Cache selector. For some bugs, Proxmox VMs can't start with default in this field. Press "Add". Now the image is attached as root drive. Make sure that device reference path is in the "Boot Order" selector of the VM's Options tab.

At this point, the VM is ready to run.

It's highly recommended to move the disk to ZFS storage, and to take a snapshot of this state. This snapshot can be used if you need to rollback, in case of later installation mistakes. If you plan an HA ProSBC installation, at this point it is wise to clone the VM. A cloned VM can be configured as the secondary later on.

### Accessing the web portal

1. Open a web browser to the management IP of the ProSBC, on port 12358. For example, if your server address is 192.168.178.30, the URL would be:\
   [http://192.168.178.30:12358](http://192.168.178.30:12358/)
2. You should get to the ProSBC Configuration Wizard<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/e/e1/TSBC_WebPortal_Configuration_wizard.jpg/350px-TSBC_WebPortal_Configuration_wizard.jpg" alt=""><figcaption></figcaption></figure>

From here, you can go to [Web Portal Initial Configuration Guide](/initial-installation/2.-initial-configuration/initial-setup) to continue the installation.


# Virtual - VMware

ProSBC on VMware: requires ESX 6 or later, 64-bit infrastructure, E1000 or VMXNET3 emulation, and separate management and SIP/RTP Ethernet adapters.

### Requirements

Minimal Cloud requirements:

* Vmware ESX 6 or later
* 64-bit infrastructure only
* E1000 NIC emulation or VMXNET3 interfaces
* One Ethernet adapter for management (mgmt0)
* One or more Ethernet adapter(s) for SIP and RTP traffic according to the table below (LAN/WAN)
* If you are deploying ProSBC in a 1+1 configuration, you need two (2) additional Ethernet adapters to be used as control ports (ctrl0/ctrl1).
* If you are deploying ProSBC with transcoding devices, you will need four (4) additional Ethernet adapters to be used as control and transcoding ports (ctrl0/ctrl1, trans0/trans1).

<table><thead><tr><th width="150">Sessions</th><th width="100">CPU</th><th width="100">RAM</th><th width="100">Disk Space (SSD)</th><th width="200">Data Ethernet ports</th></tr></thead><tbody><tr><td>Up to 5,000</td><td>2 to 4</td><td>4 Gb</td><td>40 Gb</td><td>1 Gbps</td></tr><tr><td>5,001-20,000</td><td>4 to 6</td><td>8 Gb</td><td>60 Gb</td><td>4 X 1 Gbps or 1 X 10 Gbps</td></tr><tr><td>20,001-26,000</td><td>6 to 8</td><td>16 Gb</td><td>80 Gb</td><td>1 X 10 Gbps</td></tr></tbody></table>

\*\* The CPU number is based on Intel R630 with Xeon E5-2643. Double the CPUs number if yours are from a earlier generations.

More details on HW/CPU/NIC requirements can be found here: [Requirements Matrix](/initial-installation/1.-instructions-by-platform/prosbc-requirements-matrix)

For better performance use these settings:

* CPU resource: allocation shares set to 'high'
* CPU resource: reservation set to maximum and no limit (i.e. 'unlimited')
* Memory resource: reserve all guest memory (all locked)
* Disk: shares 'high'
* Advanced CPU: Hyperthread core sharing to 'None'
* Latency Sensitivity: 'High'

### Getting the Image

Please go to our [ProSBC Download site](http://www2.telcobridges.com/ProSBCDownload) to get a copy of the latest SBC Image.

### Installation on VmWare cloud

#### ProBSC VmWare Image

A virtual machine image is a single file that contains a virtual disk that has a bootable operating system installed on it. Images are used to create virtual machine instances within the cloud.

You will need to upload the latest SBC image into your VmWare before you can launch a virtual machine instance running the SBC software.

**Launching an instance**

[Using the ESXi Web client](/initial-installation/1.-instructions-by-platform/virtual-self-hosted-installation/virtual-vmware/deploying-prosbc-on-vmware)

[Using the vSphere client application](/initial-installation/1.-instructions-by-platform/virtual-self-hosted-installation/virtual-vmware/launching-an-instance-of-vmware-vsphere)

If you are installing a standalone SBC, the ProSBC or FreeSBC will need access to LAN/WAN and MGMT networks. For transcoding on TSBC-HW-TRANS, or HA pair installation, the ProSBC will also need access to CTRL0/CTRL1, and TRANS0/TRANS1 networks. In both instance launching methods above, when editing network adaptor, please take reference to ProSBC Networking for details on network requirements.\
For ProSBC Transcoding and associated network setup please also see [Transcoding and Network Setup](/configuration-details/configuration-by-use-case/transcoding-unit-configuration/baremetal-and-virtual-machine).

#### Accessing the SBC

**Accessing console**

You need to use the VMware console to access the system - SSH interface is not activated yet.\
Default username/password is root/root.

**Assigning IP address**

By default, all detect network interfaces will have DHCP enabled. Thus, the server might already have an IP address assigned if the network has a DHCP server running. In such case, you can display and use it to access the web portal configuration panel.

1. Retrieve an IP address assigned by DHCP

```
 # ifconfig
```

If you want to assigned a static IP address or there are no DHCP on your network, you will need to configure it manually.

1. Use [tbchangeip](/initial-installation/2.-initial-configuration/initial-setup/sbc-management-ip-configuration) shell command and answered questions to changed your Ethernet interface address:

```
 # tbchangeip
```

Note: tbchangeip command applies for management interface (mgmt) only. This command does not apply for control interface (ctrl) nor voip interfaces (voip).

\
Note: No changes must be done to the repositories on the systems, and no other software should be installed unless written consent from TelcoBridges.

**Accessing the SBC web portal**

* Open a web browser to the management IP of the SBC, on port 12358. Example if your server address is 192.168.178.30, the URL would be:\
  [http://192.168.178.30:12358](http://192.168.178.30:12358/)

<br>

You should get to the SBC Configuration Wizard<br>

<figure><img src="https://docs.telcobridges.com/w/images/e/e1/TSBC_WebPortal_Configuration_wizard.jpg" alt=""><figcaption></figcaption></figure>

<br>

* If you do not know the IP address, you can find it from the VMware interface:<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/3/3f/FreeSBC_Initial_IP_address.png/700px-FreeSBC_Initial_IP_address.png" alt=""><figcaption></figcaption></figure>

<br>

* From here, you can go to [Web Portal Initial Configuration Guide](/initial-installation/2.-initial-configuration) to continue the installation, and/or optimize your server to get the maximum out of your server.

### Web Portal Initial Configuration

Click on the following link to pursue installation from the web portal: [SBC Initial Configuration](/initial-installation/2.-initial-configuration/initial-setup)


# Launching an Instance of VMware vSphere

Launch a ProSBC instance with the VMware vSphere client by deploying the OVF template supplied by TelcoBridges.

## Launching an Instance of VMware vSphere <a href="#firstheading" id="firstheading"></a>

**Launching an instance of the VMware vSphere client**

1- Log in using the Vmware infrastructure client interface.<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/e/e4/Login_client.png/200px-Login_client.png" alt=""><figcaption></figcaption></figure>

2- Select File->Deploy OVF Template.<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/7/76/Vmware_upload.png/400px-Vmware_upload.png" alt=""><figcaption></figcaption></figure>

3- Browse to the location of the ProSBC image that you obtained from TelcoBridges.<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/7/72/Vmware_ovf_location.png/400px-Vmware_ovf_location.png" alt=""><figcaption></figcaption></figure>

4- Click 'Next' until you need to name the new virtual machine instance.

* Enter the name and click 'Next'<br>

  <figure><img src="https://docs.telcobridges.com/w/images/thumb/0/0e/Vmware_name.png/400px-Vmware_name.png" alt=""><figcaption></figcaption></figure>

5- Select a datastore (if more than one are available).

* Select "Thick Provision Lazy Zeroed" as the disk format and click 'Next' .<br>

  <figure><img src="https://docs.telcobridges.com/w/images/thumb/c/c9/Vmware_disk.png/400px-Vmware_disk.png" alt=""><figcaption></figcaption></figure>

6- Accept all other default settings and wait until the machine is deployed.<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/f/f1/Vmware_installing.png/200px-Vmware_installing.png" alt=""><figcaption></figcaption></figure>

7- Once the machine is deployed, right-click on the new instance and select "Edit Settings..."<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/0/01/Vmware_settings.png/400px-Vmware_settings.png" alt=""><figcaption></figcaption></figure>

8- Press 'OK'.<br>

<figure><img src="https://docs.telcobridges.com/w/images/d/db/Vmware_restricted.png" alt=""><figcaption></figcaption></figure>

9- Edit network adapters to connect to the proper networks. Make sure that at least one of the adapters connects to the private management network of the setup from which WebPortal access will be granted.\
Do not click 'OK' yet!<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/7/7d/Vmware_network.png/400px-Vmware_network.png" alt=""><figcaption></figcaption></figure>

10- Click the 'Resources' tab and select CPU.

* Set 'Shares' to 'high'.
* Slide the 'Reservation' cursor to the maximum (move to the right).
* Make sure the 'Unlimited' option is checked-marked.<br>

Do not click 'OK yet!<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/8/83/Vmware_cpu.png/400px-Vmware_cpu.png" alt=""><figcaption></figcaption></figure>

11- Select 'Memory' and select the 'Reserve all guest memory (All locked)' option.\
Do not click 'OK' yet!<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/4/44/Vmware_mem.png/400px-Vmware_mem.png" alt=""><figcaption></figcaption></figure>

12- Select 'Disk' and set the 'Shares' to 'High'.\
Do not click 'OK' yet!<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/d/d3/Vmware_disk_res.png/400px-Vmware_disk_res.png" alt=""><figcaption></figcaption></figure>

13- Select 'Advanced CPU' and set the 'Mode' to 'None'.\
Do not click 'OK' yet!<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/2/24/Vmware_adv_cpu.png/400px-Vmware_adv_cpu.png" alt=""><figcaption></figcaption></figure>

\
14- Set the 'Latency Sensitivity' to 'High'.\
15- Click 'OK'.\
16- Return to the main screen, and select the newly instantiated virtual machine.<br>

* Right-click and select "Power-->Power On" to start it.<br>

  <figure><img src="https://docs.telcobridges.com/w/images/thumb/c/ca/Vmware_poweron.png/400px-Vmware_poweron.png" alt=""><figcaption></figcaption></figure>

17- Return once again to the main screen, and select the newly instantiated virtual machine and click the 'Summary' tab. Once the virtual machine has started up, the assigned DHCP IP address will be displayed by clicking on the 'View all' button.\
\
Note: This IP address is used to access the Web Portal configuration interface later on.<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/b/b3/Vmware_ip.png/400px-Vmware_ip.png" alt=""><figcaption></figcaption></figure>


# Deploying ProSBC on VMware

Deploy ProSBC on VMware from an OVF or OVA file using the vSphere web interface, through the Create / Register VM wizard.

### Launching an instance using ESXi web interface

1. Log in using the Vmware web interface
2. Select 'Virtual Machines' from the left menu

<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/8/88/Vmware_web_virtual_machines.png/200px-Vmware_web_virtual_machines.png" alt=""><figcaption></figcaption></figure>

3. Click on 'Create / Register VM'<br>

   <figure><img src="https://docs.telcobridges.com/w/images/thumb/e/e5/Vmware_web_create.png/600px-Vmware_web_create.png" alt=""><figcaption></figcaption></figure>

4. Select 'Deploy a virtual machine from an OVF or OVA file' then press 'next'<br>

   <figure><img src="https://docs.telcobridges.com/w/images/thumb/f/f7/Vmware_web_select_type.png/800px-Vmware_web_select_type.png" alt=""><figcaption></figcaption></figure>

5. Enter the name. Drag the file or browse to the location of the FreeSBC-SW image obtained from TelcoBridges. 'Click 'Next'

<figure><img src="https://docs.telcobridges.com/w/images/thumb/8/89/Vmware_web_browse_ova.png/800px-Vmware_web_browse_ova.png" alt=""><figcaption></figcaption></figure>

6. Select a datastore (if more than one are available) then click 'Next'

<figure><img src="https://docs.telcobridges.com/w/images/thumb/a/a8/Vmware_web_select_storage.png/800px-Vmware_web_select_storage.png" alt=""><figcaption></figcaption></figure>

7. Choose your network. Select 'Thick' disk provisioning. Uncheck 'Power on automatically'. Click 'Next'

<figure><img src="https://docs.telcobridges.com/w/images/thumb/b/b0/Vmware_web_deployment_options.png/800px-Vmware_web_deployment_options.png" alt=""><figcaption></figcaption></figure>

8. Click 'Next'

<figure><img src="https://docs.telcobridges.com/w/images/thumb/e/ed/Vmware_web_ready_to_complete.png/800px-Vmware_web_ready_to_complete.png" alt=""><figcaption></figcaption></figure>

9. Do not refresh your browser and wait until the machine is deployed.<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/9/93/Vmware_web_installing.png/800px-Vmware_web_installing.png" alt=""><figcaption></figcaption></figure>

10. Once deployed, edit the VM<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/3/32/Vmware_web_edit_settings.png/800px-Vmware_web_edit_settings.png" alt=""><figcaption></figcaption></figure>

11. Edit network adapters to connect on proper networks. Make sure that at least one of the adapter connects to the private management network of the setup from which WebPortal access will be granted. Do not press the 'Save' button yet.<br>

<figure><img src="https://docs.telcobridges.com/w/images/0/0d/Vmware_web_network.png" alt=""><figcaption></figcaption></figure>

12.

* If system requires 1+1 configuration or more network interfaces follow these steps: [How to add VMware Network Interfaces](/initial-installation/1.-instructions-by-platform/virtual-self-hosted-installation/virtual-vmware/adding-network-interfaces-in-vmware)
* If system requires high performance, Passthrough interface can be configured. See [Configuring VMware Passtrough interfaces](/initial-installation/1.-instructions-by-platform/virtual-self-hosted-installation/virtual-vmware/configuring-passtrough-interfaces-on-vmware)

13. Click on 'CPU' to open the details. Set 'Shares' to 'high', enter the maximum number of MHz corresponding to your number of CPU cores in 'Reservation' (See [Calculating Reserved CPU](#calculating-reserved-cpu-mhz)) and make sure the 'Unlimited' option is selected. Do not press the 'Save' button yet.<br>

<figure><img src="https://docs.telcobridges.com/w/images/4/44/Vmware_web_cpu.png" alt=""><figcaption></figcaption></figure>

14. Open the 'Memory' details and check-mark the 'Reserve all guest memory (All locked)' option, set Limit to 'Unlimited' and Shares to 'High'. Do not press the 'Save' button yet.<br>

<figure><img src="https://docs.telcobridges.com/w/images/4/48/Vmware_web_memory.png" alt=""><figcaption></figcaption></figure>

15. Open the 'Hard disk 1' details and set the 'Shares' to 'High'. Do not press the 'Save' button yet.

<figure><img src="https://docs.telcobridges.com/w/images/4/41/Vmware_web_disk_res.png" alt=""><figcaption></figcaption></figure>

16. Click on the second tab 'VM Options', expand 'Advanced' and set 'Latency Sensitivity' to 'High' then press the 'Save' button.

<figure><img src="https://docs.telcobridges.com/w/images/b/b8/Vmware_web_latency.png" alt=""><figcaption></figcaption></figure>

17. Back to the main screen, click on "Power On" to start the new VM.

<figure><img src="https://docs.telcobridges.com/w/images/thumb/9/91/Vmware_web_poweron.png/800px-Vmware_web_poweron.png" alt=""><figcaption></figcaption></figure>

18. Once the VM had completely booted, its assigned DHCP IPs will be displayed in General Information -> Networking. Note this IP address to access the Web Portal configuration interface later.

<figure><img src="https://docs.telcobridges.com/w/images/thumb/6/68/Vmware_web_ip.png/800px-Vmware_web_ip.png" alt=""><figcaption></figcaption></figure>

#### Calculating Reserved CPU MHz

To get the MHz per core, you need to figure out the total number of available MHz that your system has and divide by the total number of cores.

1. Select 'Host' on the left menu<br>

   <figure><img src="https://docs.telcobridges.com/w/images/thumb/4/43/Vmware_web_host.png/200px-Vmware_web_host.png" alt=""><figcaption></figcaption></figure>
2. Take note of the number of cores this system has. (In this example: 12) Also take a look at the 'CAPACITY', but is is not precise down to the MHz (In this example 36.7 GHz)<br>

   <figure><img src="https://docs.telcobridges.com/w/images/thumb/d/df/Vmware_web_total_cpus.png/800px-Vmware_web_total_cpus.png" alt=""><figcaption></figcaption></figure>
3. When editing the VM, in the disk details, expand the 'Reservation' combobox. There should be a number in exact MHz for the maximum capacity of the system (In this example: 36708)<br>

   <figure><img src="https://docs.telcobridges.com/w/images/c/c9/Vmware_web_total_mhz.png" alt=""><figcaption></figcaption></figure>
4. Calculate your VM CPU MHz Reservation requirement

mhz\_per\_core = total\_system\_mhz / total\_system\_cpus (In this example: 3059 = 36708 / 12 )vm\_reserved\_mhz = vm\_cpus \* mhz\_per\_core (In this example: 12236 = 3059 \* 4 )


# Adding Network Interfaces in VMware

Add network interfaces to ProSBC in VMware by creating port groups for the management network, the two control ports, and every VLAN used on the SBC.

#### Configure VMware Networking

1. Log in using the Vmware web interface
2. Select 'Networking' from the left menu<br>

   <figure><img src="https://docs.telcobridges.com/w/images/thumb/9/9b/VMware_Networking_port_group.png/1000px-VMware_Networking_port_group.png" alt=""><figcaption></figcaption></figure>
3. Select 'Port Group' tab
4. "Add port group" for
   1. The management network
   2. The two control ports (For 1+1 and transcoding)
   3. Every vlan that will be used on the SBC

Note: each port group must be assigned to the appropriate vSwitch. If this needs to connect to an external switch, make sure there is an uplink connected to the vSwitch and that the vlan is configured on the network switch.When connecting with an external 1+1 system, make sure the vlans will match with the secondary system (in this example, we use vlan 700 and 701)

#### Vlans relayed to guest OS

When using vlan ID 4095, all the vlans on this network interface are relayed to the guest OS. In this case the ProSBC needs to configure the vlans as explained here: Configure a vlan on ProSBC\
In this case, you need to have one network interface with vlan ID 4095 in step 4 above.\ <br>

<figure><img src="https://docs.telcobridges.com/w/images/2/2b/VMware_ESXi_vlan_relay.png" alt=""><figcaption></figcaption></figure>

#### Configure VMware Instance

1. Select 'Virtual Machines' from the left menu\ <br>

   <figure><img src="https://docs.telcobridges.com/w/images/8/88/Vmware_web_virtual_machines.png" alt=""><figcaption></figcaption></figure>
2. Once deployed, edit the VM\ <br>

   <figure><img src="https://docs.telcobridges.com/w/images/thumb/3/32/Vmware_web_edit_settings.png/800px-Vmware_web_edit_settings.png" alt=""><figcaption></figcaption></figure>
3. Edit network adapters to connect on proper networks. Make sure that at least one of the adapter connects to the private management network of the setup from which WebPortal access will be granted. Do not press the 'Save' button yet.\ <br>

   <figure><img src="https://docs.telcobridges.com/w/images/0/0d/Vmware_web_network.png" alt=""><figcaption></figcaption></figure>
4. Add network adapters for this SBC instance and Save:
   1. The management network
   2. The two control ports (For 1+1 and transcoding)
   3. Every vlan that will be used on the SBC

For example, if vlan 600, 800 and 802, add three network adapters, each using a different Port Group. The network interfaces must match the Port Group of VMware networks.\ <br>

<figure><img src="https://docs.telcobridges.com/w/images/8/83/VMware_multiple_network_adapters.png" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Virtual adapter type:** When adding a network adapter, choose the adapter type based on your capacity needs. Use **E1000** for deployments of 1000 sessions or less; use **VMXNET3** for higher performance and greater session capacity.
{% endhint %}

1. Note down the MAC address of each interface - This will useful when assigning the VMware network interfaces to the SBC

\ <br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/d/d8/Network_adapters_MAC_Address_primary_1.png/1000px-Network_adapters_MAC_Address_primary_1.png" alt=""><figcaption></figcaption></figure>

#### Useful Links

VMware Installation

Launching a Vmware Instance

[Web Portal Initial configuration](/initial-installation/2.-initial-configuration/initial-setup)


# Configuring Passtrough interfaces on VMware

Enable passthrough mode on network interfaces for high performance ProSBC VMware systems. The process requires a reboot of the VMware host server.

For high performance ProSBC VMware systems, Passthrough mode can be enabled on network interfaces. Performance indications can be viewed here: [Requirements Matrix](/initial-installation/1.-instructions-by-platform/prosbc-requirements-matrix) This process requires a reboot of the host server running the VMware services.

### Configure VMware Passthrough Networking Interface

1. Log in using the Vmware web interface
2. Find MAC address of ethernet interface that will be used for passthrough:
   * Networking -> Physical NICs<br>

     <figure><img src="https://docs.telcobridges.com/w/images/thumb/f/f2/Find_MAC_address_of_Network_Interface.png/1200px-Find_MAC_address_of_Network_Interface.png" alt=""><figcaption></figcaption></figure>
3. enable passthrough mode on interface
   * Host -> Manage -> Hardware -> PCI Devices -> Select Physical Network Interface -> "Toggle Passthrough"<br>

     <figure><img src="https://docs.telcobridges.com/w/images/thumb/e/e5/Set_PCI_to_passthrough.png/1200px-Set_PCI_to_passthrough.png" alt=""><figcaption></figcaption></figure>
4. Reboot the host
   * Host -> Actions -> Reboot<br>

     <figure><img src="https://docs.telcobridges.com/w/images/thumb/e/ec/Reboot_VMware_host.png/800px-Reboot_VMware_host.png" alt=""><figcaption></figcaption></figure>
5. Add PCI device to the ProSBC instance
   * Select the ProSBC instance -> Edit -> "Add Other Device" -> PCI Device<br>

     <figure><img src="https://docs.telcobridges.com/w/images/c/c3/Add_PCI_device_to_VM.png" alt=""><figcaption></figcaption></figure>
   * Select the Ethernet interface to be used in passthrough mode<br>

     <figure><img src="https://docs.telcobridges.com/w/images/6/6a/Select_PCI_device.png" alt=""><figcaption></figcaption></figure>
6. Launch the ProSBC instance
   * When selecting the interfaces in the network interface roles, use the appropriate MAC address from first step for the LAN/WAN interface. You may also notice that the device name is not "E1000" or "VMXNET" but a real Physical interface name.<br>

     <figure><img src="https://docs.telcobridges.com/w/images/thumb/6/67/Select_PCI_Passthrough_device.png/800px-Select_PCI_Passthrough_device.png" alt=""><figcaption></figcaption></figure>


# Cloud Installation

Install ProSBC in the public cloud: AWS via Amazon Machine Image or CloudFormation template, and Microsoft Azure, with interface and upgrade guidance.


# Cloud - AWS

Launch a ProSBC instance on Amazon Web Services from an Amazon Machine Image (AMI), step by step through the EC2 console.

### Introduction

This article provides guidance for people launching an instance of *ProSBC* using an Amazon Machine Image (AMI) on Amazon Web Service (AWS).\
NOTE The old installation guide is located here: [AWS installation](/initial-installation/1.-instructions-by-platform/cloud-installation/cloud-aws/aws-installation)

### Instantiate a ProSBC

* After logging in your Amazon account, click on “EC2” in the main AWS console:

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FwtUbvW27VPcjcGGzbFQA%2F1.jpg?alt=media&amp;token=8c61bebe-2680-4dd6-bd1d-211e5c14b1ea" alt=""><figcaption></figcaption></figure>

* Be sure that you are in the correct region. Consult TelcoBridges if you are unsure which region to locate the AMI. On the left menu click on “AMIs” and select “Private image” to locate FreeSBC/ProSBC AMI:

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FTbOShdW4iUFYSciF4cF3%2F2.jpg?alt=media&amp;token=db119ac5-5419-49cb-87ac-ded7a548f01f" alt=""><figcaption></figcaption></figure>

* Launch the FreeSBC/ProSBC image.

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FF9YvYvdVdmgL7yGNIAHW%2F3.jpg?alt=media&amp;token=b95ce931-bdb7-42a2-9ad5-969cf6cfc30d" alt=""><figcaption></figcaption></figure>

* Name the instance and add any necessary tag

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2Ft02xJIxbh4Mvv7mcjkbr%2F4.jpg?alt=media&amp;token=3335beff-0672-4288-91d1-c3d537d30cba" alt=""><figcaption></figcaption></figure>

* Select the instance type and its resources. The smallest instance type is:

  * m5.large (2 vCPU, 8 GiB)

  The recommended instance type is:

  * m5.xlarge (4 vCPU, 16 GiB)
* Other supported instance type are:
  * C3, D2, I2, and R3 instances ([Supported instances from Amazon documentation](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html))
* This is the list of approximate performances for different AWS instance types. Results may vary according to configuration.

<table><thead><tr><th width="150">EC2 Instance</th><th width="100">AWS CPU cores</th><th width="100">Calls per second (cps)</th><th width="100">Sessions with RTP anchoring</th><th width="200">Sessions with Media bypass</th></tr></thead><tbody><tr><td>m5.large</td><td>2</td><td>50</td><td>400</td><td>32,000</td></tr><tr><td>m5.xlarge</td><td>4</td><td>215</td><td>750</td><td>60,000</td></tr><tr><td>c5.2xlarge</td><td>8</td><td>575</td><td>2,000</td><td>60,000</td></tr><tr><td>m5.4xlarge</td><td>16</td><td>650</td><td>4,000</td><td>60,000</td></tr><tr><td>m5.12xlarge</td><td>48</td><td>650</td><td>4,800</td><td>60,000</td></tr></tbody></table>

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2F8bR4AHJWRumFCaKwIevb%2F5.jpg?alt=media&amp;token=a8d85ca0-dc31-4ab4-a452-ae1c01365e6a" alt=""><figcaption></figcaption></figure>

* For later access to the FreeSBC/ProSBC SSH console you will need to select a Key Pair to secure the login. You can also create a new Key Pair in case you need.

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FEVFn2bKWxk4VlNX4KnQg%2F6.jpg?alt=media&amp;token=74d2f50f-e835-4653-93c2-73896c06dd9f" alt=""><figcaption></figcaption></figure>

* In "Networking Settings" select "Create security group". We recommend that you simply open "All Traffic" on your own IP addresses to whitelist it in AWS firewall on "Source", once all your IPs are listed click on "Add security group rule": (note that the SBC contains its own internal firewall)

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FVzF27lhPnmdRKqUXQTUR%2F7.jpg?alt=media&amp;token=d3ebc019-691d-42d8-83a0-370aaceaa668" alt=""><figcaption></figcaption></figure>

* In "Configure Storage" change the Volume Size to 40Gb and select volume type to GP2.

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FblUrvwYr2anATasQZX7l%2F8.jpg?alt=media&amp;token=4715b20f-0a0e-4641-9c14-45d3975ab8b2" alt=""><figcaption></figcaption></figure>

* Finally review the summary of your instance and start the creation process clicking on "Launch Instance". Be aware, from this moment you will be billed by Amazon for the instance resources:

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FVi9VzfCznWhOqq5RD2yk%2F9.jpg?alt=media&amp;token=8bdeedfb-31f9-44d4-9b09-51bef43d5e63" alt=""><figcaption></figcaption></figure>

* You should receive the confirmation of the launching process, this process will take some minutes until the instance is available, You can view your instance clicking on “View Instances”:

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FsZiNPElLEcI00UBcb223%2F10.jpg?alt=media&amp;token=3b0b726a-c434-425a-b5f9-47bb09f926ea" alt=""><figcaption></figcaption></figure>

* After a few minutes your instance should be running and available to be configured:

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FpDMQbQxzdrs8TCbqItRG%2F11.jpg?alt=media&amp;token=dbde81fb-e255-4a35-98cf-b7cfb119cd6f" alt=""><figcaption></figcaption></figure>

<br>

#### Optional: Elastic IP Creation section

* AWS will automatically provide and allocate a dynamic public IP to your instance, this will allow you to access from the IPs you whitelisted before to the Public IP allocated to your instance. For ProSBC servers the purpose is to interact with other SIP elements as part of a VoIP cloud telecom infrastructure, TelcoBridges strongly recommends associating an Elastic IP to your instance, which is, in short, to associate a fixed public IP to your SBC. For more information about how to associate an Elastic IP to your instance please check the official documentation in AWS [here](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html).

### Enable SR-IOV enhanced networking

By default M5 instances have enhanced networking enabled. If you want to use any other instance, you need to check if enhanced networking is enabled or not.

```
It is very important to enable "enhanced networking" for tbrouter to have access to the network devices on the VM.
```

This must be done before completing the initial web portal configuration. Please shut down the instance before entering the serial number and all other information and set SR-IOV

There are two types of enhanced networking, we need the second one.

1\) Elastic Network Adapter (ENA)

2\) Intel 82599 Virtual Function (VF) interface

#### Install the AWS CLI

<https://aws.amazon.com/cli/>

#### Get security credentials for the command line

On the AWS web portal, click on your account name and choose "My Security Credentials"

Expand the "Access keys" section

Create a new key, you will need the AWSAccessKeyId and AWSSecretKey

#### Open a CLI and execute the aws cli commands

```
 aws configure
```

Paste the access key ID and key that you previously obtained along with your default region.

#### Show if the enhanced networking is enabled

Make sure to replace the example instance ID with your own AWS instance ID

```
 aws ec2 describe-instance-attribute --instance-id i-0123456789abcdef1 --attribute sriovNetSupport
```

Enabled:

```
 {
     "InstanceId": "i-0123456789abcdef1",
     "SriovNetSupport": {
         "Value": "simple"
     }
 }
```

Not enabled:

```
 {
     "InstanceId": "i-0123456789abcdef1",
     "SriovNetSupport": {}
 }
```

To enable the sriov enhanced networking, first turn off the instance then do:

```
 aws ec2 modify-instance-attribute --instance-id i-0123456789abcdef1  --sriov-net-support simple
```

### Accessing the ProSBC

#### Accessing the ProSBC web portal

* Open a web browser to the management IP of the ProSBC, on port 12358. Example if your Instance public IP address is 35.183.126.193, the URL would be:\
  [http://35.183.126.193:12358](http://35.183.126.193:12358/)

<br>

You should get to the ProSBC Configuration Wizard\
![](https://docs.telcobridges.com/w/images/thumb/0/01/AWS_TSBC_WebPortal_Configuration_wizard.jpg/700px-AWS_TSBC_WebPortal_Configuration_wizard.jpg)

<br>

Take note that it may take a while for the ProSBC system to make the Web Portal available (around 3-5 minutes).

* From here, you can go to [Web Portal Initial Configuration Guide](/initial-installation/2.-initial-configuration/initial-setup) to continue the installation.

### Installing AWS Instance with CloudFormation Template

AWS CloudFormation is a service that helps you model and set up your AWS resources so that you can spend less time managing those resources and more time focusing on your applications that run in AWS. Telcobridge created a CloudFormation template to reduce the time spent on ProSBC AWS installation. Click on the following link to the ProSBC CloudFormation installation: [ProSBCAWS CloudFormation Installation](/initial-installation/1.-instructions-by-platform/cloud-installation/cloud-aws/cloud-formation-installation)

### Upgrading the instance type

You can upgrade the instance type in AWS based on your requirements. Click on the following link for instance type upgrade [ProSBC AWS Intance Upgrade](/initial-installation/1.-instructions-by-platform/cloud-installation/cloud-aws/instance-upgrade)

### Adding more interfaces to ProSBC in AWS

You can add more interfaces to ProSBC in AWS based on your requirements. Click on the following link for how to add an interface [ProSBC AWS Additional Interface](/initial-installation/1.-instructions-by-platform/cloud-installation/cloud-aws/aws-additional-interface)

### Web Portal Initial Configuration

Click on the following link to pursue installation from the web portal: [ProSBC Initial Configuration](/initial-installation/2.-initial-configuration)

### AWS using NAT

Since the AWS instance is behind NAT, you must adjust the NAT settings for the SBC: [IP Network Settings](/configuration-details/configuration-by-web-portal-category/ip-network-settings)

### Troubleshooting

* [Installation troubleshooting](/initial-installation/1.-instructions-by-platform/cloud-installation/cloud-aws/aws-installation-troubleshooting)
* [Recovering an Elastic IP address](/initial-installation/1.-instructions-by-platform/cloud-installation/cloud-aws/recovering-an-elastic-ip-address)

### External References

* [Accessing device with SSH and private key using putty](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/connect-to-linux-instance.html)


# AWS Installation

This page is intended to give assistance to people launching an instance of ProSBC using an Amazon Machine Image (AMI) on Amazon Web Service (AWS).

### Instantiate a ProSBC

* After logging in your Amazon account, click on “EC2” in the main AWS console:

<figure><img src="https://docs.telcobridges.com/w/images/thumb/9/96/ConsoleEC2.png/600px-ConsoleEC2.png" alt=""><figcaption></figcaption></figure>

* On the left menu, click on “AMIs”:

<figure><img src="https://docs.telcobridges.com/w/images/thumb/9/95/AMIs.png/100px-AMIs.png" alt=""><figcaption></figcaption></figure>

* Click on the filter drop list and select “Private image” to locate ProSBC AMI:

<figure><img src="https://docs.telcobridges.com/w/images/thumb/9/94/PrivateImages.png/500px-PrivateImages.png" alt=""><figcaption></figcaption></figure>

* Select the region matching the region of the ProSBC AMI you want to test. If you don't know it, try "Canada (Central)".

<figure><img src="https://docs.telcobridges.com/w/images/thumb/d/d3/RegionAMI.png/700px-RegionAMI.png" alt=""><figcaption></figcaption></figure>

* Select the image and click “Launch”:

<figure><img src="https://docs.telcobridges.com/w/images/thumb/f/fa/SelectAMI.png/700px-SelectAMI.png" alt=""><figcaption></figcaption></figure>

<br>

* Select the instance type and its resources.&#x20;

  The smallest instance type is:

  * m5.large (2 vCPU, 8 GiB)

  The recommended instance type is:

  * m5.xlarge (4 vCPU, 16 GiB)
* Supported instance types are:
  * C3, C4, D2, I2, and R3 instances ([Supported instances from Amazon documentation](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html))
* This is the list of approximate performances for different AWS instance types. Results may vary according to configuration.

<table><thead><tr><th width="148">EC2 Instance</th><th width="145">AWS CPU cores</th><th width="152">Sessions with RTP anchoring</th><th width="271">Sessions with Media bypass</th></tr></thead><tbody><tr><td>m5.large</td><td>2</td><td>400</td><td>32,000</td></tr><tr><td>m5.xlarge</td><td>4</td><td>750</td><td>60,000</td></tr><tr><td>m5.4xlarge</td><td>16</td><td>4,000</td><td>60,000</td></tr><tr><td>m5.120xlarge</td><td>48</td><td>4,800</td><td>60,000</td></tr></tbody></table>

<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/9/95/SelectResources.png/800px-SelectResources.png" alt=""><figcaption></figcaption></figure>

<br>

* Click “Add Storage” to proceed to the next page:

<figure><img src="https://docs.telcobridges.com/w/images/thumb/8/8f/ChooseSubnet.png/1000px-ChooseSubnet.png" alt=""><figcaption></figcaption></figure>

<br>

* Change the Volume Size to 40Gb.
* Select "Volume Type": gp2
* Check the box "Delete on Termination"
* Click “Add Tags” to proceed to the next page.

<figure><img src="https://docs.telcobridges.com/w/images/thumb/8/81/NextTag.png/800px-NextTag.png" alt=""><figcaption></figcaption></figure>

<br>

* You can leave the default parameters as they are.
* Click “Configure Security Group” to proceed to the next page:

<figure><img src="https://docs.telcobridges.com/w/images/thumb/f/ff/NextSecurityGroup.png/800px-NextSecurityGroup.png" alt=""><figcaption></figcaption></figure>

* Select "Create a new security group". We recommend that you simply open all ports on your own IP address, since the SBC contains its own internal firewall:

| Rule        | Type        | Port Range | Source IP                |
| ----------- | ----------- | ---------- | ------------------------ |
| All traffic | All traffic | 0 - 65535  | (Use your own public IP) |

<figure><img src="https://docs.telcobridges.com/w/images/thumb/7/71/AddRule.png/600px-AddRule.png" alt=""><figcaption></figcaption></figure>

<br>

* Click “Launch”. Be aware: you will be billed by Amazon for the instance resources:

<figure><img src="https://docs.telcobridges.com/w/images/thumb/6/68/Launch.png/1000px-Launch.png" alt=""><figcaption></figcaption></figure>

<br>

* You will be prompted to create a key pair, allowing you to securely connect to your instance. Select “Create a new key pair” if you do not own one, and give it a name. Then, click on “Download Key Pair” to download a .pem file since it is needed for a SSH connection. (Note: Make sure to not lose it, since you would then lose access the the SSH connection for the instance):

<figure><img src="https://docs.telcobridges.com/w/images/thumb/2/2f/DownloadKey.png/800px-DownloadKey.png" alt=""><figcaption></figcaption></figure>

<br>

* Click on “Launch Instances”:

<figure><img src="https://docs.telcobridges.com/w/images/thumb/b/b3/LaunchWithKey.png/800px-LaunchWithKey.png" alt=""><figcaption></figcaption></figure>

<br>

* You can view your instance by clicking on “View Instances”:

<figure><img src="https://docs.telcobridges.com/w/images/thumb/f/f7/ViewInstance.png/800px-ViewInstance.png" alt=""><figcaption></figcaption></figure>

<br>

* Select the instance you just created and feel free to give it a name:

<figure><img src="https://docs.telcobridges.com/w/images/thumb/b/ba/RenameInstance.png/800px-RenameInstance.png" alt=""><figcaption></figcaption></figure>

#### Optional: Elastic IP Creation section

* If you want to use an associate public IP generated by Amazon (called "Elastic IP"). Click on "Elastic IP" on the left, then click on "Allocate new address":

<figure><img src="https://docs.telcobridges.com/w/images/thumb/8/84/ElasticIP.png/300px-ElasticIP.png" alt=""><figcaption></figcaption></figure>

<br>

* Click on "Allocate IP". A new public IP will be generated by Amazon:

<figure><img src="https://docs.telcobridges.com/w/images/thumb/6/6e/AllocateIP.png/600px-AllocateIP.png" alt=""><figcaption></figcaption></figure>

<br>

* Click on "Close":

<figure><img src="https://docs.telcobridges.com/w/images/thumb/f/f7/NewIP.png/600px-NewIP.png" alt=""><figcaption></figcaption></figure>

#### Optional: Elastic IP association section

* Go to the left pane and click on "Instance". Then select the instance "ProSBC" to display its description:

<figure><img src="https://docs.telcobridges.com/w/images/thumb/1/16/IPforInstance.png/600px-IPforInstance.png" alt=""><figcaption></figcaption></figure>

* Find the eth0 network interface in the instance description:

<figure><img src="https://docs.telcobridges.com/w/images/thumb/3/36/GetTheRightNetworkInterface.png/1100px-GetTheRightNetworkInterface.png" alt=""><figcaption></figcaption></figure>

<br>

* Click on the eth0 Network Interface, then click on the "Interface ID" link:

<figure><img src="https://docs.telcobridges.com/w/images/thumb/4/48/InterfaceID.png/1100px-InterfaceID.png" alt=""><figcaption></figcaption></figure>

<br>

* Right-click on the selected Network Interface, then click "Associate Address":

<figure><img src="https://docs.telcobridges.com/w/images/thumb/3/37/AssociateAddress.png/800px-AssociateAddress.png" alt=""><figcaption></figcaption></figure>

<br>

* In the Address list, select the public IP to associate with the main Network Interface. Then, click on "Associate Address":

<figure><img src="https://docs.telcobridges.com/w/images/thumb/6/6f/SelectAddress.png/800px-SelectAddress.png" alt=""><figcaption></figcaption></figure>

<br>

* Click on "Instances" on the left pane and select "ProSBC" instance. Check if your instance is associated with a public IP:

<figure><img src="https://docs.telcobridges.com/w/images/thumb/e/eb/Ready.png/1100px-Ready.png" alt=""><figcaption></figcaption></figure>

### Enable SR-IOV enhanced networking

It is very important to enable "enhanced networking" for tbrouter to have access to the network devices on the VM.

This must be done before completing the initial web portal configuration. Please shut down the instance before entering the serial number and all other information and set SR-IOV

There are two types of enhanced networking, we need the second one.

1\) Elastic Network Adapter (ENA)

2\) Intel 82599 Virtual Function (VF) interface

#### Install the AWS CLI

<https://aws.amazon.com/cli/>

#### Get security credentials for the command line

On the AWS web portal, click on your account name and choose "My Security Credentials"

Expand the "Access keys" section

Create a new key, you will need the AWSAccessKeyId and AWSSecretKey

#### Open a CLI and execute the aws cli commands

```
 aws configure
```

Paste the access key ID and key that you previously obtained along with your default region.

#### Show if the enhanced networking is enabled

Make sure to replace the example instance ID with your own AWS instance ID

```
 aws ec2 describe-instance-attribute --instance-id i-0123456789abcdef1 --attribute sriovNetSupport
```

Enabled:

```
 {
     "InstanceId": "i-0123456789abcdef1",
     "SriovNetSupport": {
         "Value": "simple"
     }
 }
```

Not enabled:

```
 {
     "InstanceId": "i-0123456789abcdef1",
     "SriovNetSupport": {}
 }
```

To enable the sriov enhanced networking, first turn off the instance then do:

```
 aws ec2 modify-instance-attribute --instance-id i-0123456789abcdef1  --sriov-net-support simple
```

### Accessing the ProSBC

#### Accessing the ProSBC web portal

* Open a web browser to the management IP of the ProSBC, on port 12358. Example if your Instance public IP address is 35.183.126.193, the URL would be:\
  [http://35.183.126.193:12358](http://35.183.126.193:12358/)

You should get to the ProSBC Configuration Wizard<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/0/01/AWS_TSBC_WebPortal_Configuration_wizard.jpg/700px-AWS_TSBC_WebPortal_Configuration_wizard.jpg" alt=""><figcaption></figcaption></figure>

Take note that it may take a while for the ProSBC system to make the Web Portal available (around 3-5 minutes).

* From here, you can go to Web Portal Initial Configuration Guide to continue the installation.

### Web Portal Initial Configuration

Click on the following link to pursue installation from the web portal: ProSBC Initial Configuration

### Troubleshooting

* [Installation troubleshooting](/initial-installation/1.-instructions-by-platform/cloud-installation/cloud-aws/aws-installation-troubleshooting)
* [Recovering an Elastic IP address](/initial-installation/1.-instructions-by-platform/cloud-installation/cloud-aws/recovering-an-elastic-ip-address)

### External References

* [Accessing device with SSH and private key using putty](https://devops.profitbricks.com/tutorials/use-ssh-keys-with-putty-on-windows/#connect-to-server-with-private-key)


# Cloud Formation Installation

Launch ProSBC on AWS with a CloudFormation template: load the JSON stack file, set parameters, and create the stack from the AWS console.

This page guides people launching an instance of ProSBC using an AWS CloudFormation template.

{% file src="/files/zSWpOG2BLlkySAs4yDOU" %}

To load the JSON file:

1\. Log in to AWS with your account

2\. Type CloudFormation in the search field and select it

<figure><img src="https://docs.telcobridges.com/w/images/thumb/d/d0/Cloud_Formation_1.png/800px-Cloud_Formation_1.png" alt=""><figcaption></figcaption></figure>

\
3\. Click Create Stack

<figure><img src="https://docs.telcobridges.com/w/images/thumb/8/8e/Cloud_Formation_2.png/800px-Cloud_Formation_2.png" alt=""><figcaption></figcaption></figure>

\
4\. Select Upload a template file and click Choose File to select the file. When the upload is finished, it will create an URL in the S3 Bucket for that file to store.

* Click Next

<figure><img src="https://docs.telcobridges.com/w/images/thumb/b/b4/Cloud_Formation_3.png/800px-Cloud_Formation_3.png" alt=""><figcaption></figcaption></figure>

\
5\. The Stack Details window is displayed

<figure><img src="https://docs.telcobridges.com/w/images/thumb/a/a3/Cloud_Formation_4.png/800px-Cloud_Formation_4.png" alt=""><figcaption></figcaption></figure>

```
*Stack Name: Enter a name for this newly created stack. 
*Instance Name: Enter a name for the instance that will created. 
*Instance Type: Select an instance type. By default it is m5.large. 
*Key Name: EC2 KeyPair to enable SSH access to the instance. 
```

\
6\. Click Next until the Submit button is shown.


# Instance Upgrade

Upgrade the instance type of a ProSBC deployment in AWS. Changing the instance affects the license, so contact TelcoBridges support for a replacement.

This page guides people to upgrade the ProSBC instance in AWS. Before starting this procedure you must have access to the AWS console. The instance change will affect the license. You need to contact with Telcobridges support team to get the new license.

Before starting to upgrade process, you need to be sure the existing instance supports Enhanced Networking. Please check the following link:

[AWS installation instructions](/initial-installation/1.-instructions-by-platform/cloud-installation/cloud-aws) in section 2 Enable SR-IOV enhanced networking, you will find the documentation.

1\. Login to your AWS account.

2\. Go to EC2 and select the instance that you want to upgrade.

3\. Click on Action and go to Instance Settings -> Change instance type

<figure><img src="https://docs.telcobridges.com/w/images/thumb/5/5e/Instance_Upgrade_1.png/400px-Instance_Upgrade_1.png" alt=""><figcaption></figcaption></figure>

4\. Select the new instance type to upgrade. Before selecting the new instance be sure the new instance is also in our supported instance list.

<figure><img src="https://docs.telcobridges.com/w/images/thumb/6/69/Instance_Upgrade_2.png/400px-Instance_Upgrade_2.png" alt=""><figcaption></figcaption></figure>

5\. Click to Apply.


# AWS Additional Interface

Add extra network interfaces to a ProSBC instance in AWS using the EC2 console, under Network & Security, Network Interfaces.

This page guides people to add additional network interfaces to the ProSBC instance in AWS. Before starting this procedure you must have access to the AWS console.

1\. Login to your AWS account.

2\. Go to EC2 - > Network & Security -> Network Interfaces -> Create Network Interface

<figure><img src="https://docs.telcobridges.com/w/images/thumb/e/ec/Aws_interface_1.png/600px-Aws_interface_1.png" alt=""><figcaption></figcaption></figure>

\
3\. Follow the procedure below to Create a network interface page

<figure><img src="https://docs.telcobridges.com/w/images/thumb/1/1c/Aws_interface_2.png/400px-Aws_interface_2.png" alt=""><figcaption></figcaption></figure>

\
Description: Description of the new interface.

Subnet: In this section select the subnet that is already assigned to ProSBC Interface. You can find that information under the Instance Details.

In the Security groups, assign the correct security group to new interface:

<figure><img src="https://docs.telcobridges.com/w/images/thumb/f/f0/Aws_interface_3.png/400px-Aws_interface_3.png" alt=""><figcaption></figcaption></figure>

\
Click on to Create network interface button.

\
4\. You can assign an Elastic IP address to new created Network Interface. Go to EC2 - > Network & Security -> Network Interfaces -> Elastic IPs. If you already allocate elastic IPs that are not used assign one of them the to newly created interface. If you don’t have any elastic IP click on Allocate Elastic IP address button to get a new Elastic IP address.

\
5\. In the EC2 Instances, choose the one you want to add to the new network interface. Go to Actions -> Networking -> Attach Network Interface

<figure><img src="https://docs.telcobridges.com/w/images/thumb/a/a6/Aws_interface_4.png/400px-Aws_interface_4.png" alt=""><figcaption></figcaption></figure>

\
Select the new interface you created from the Network Interface drop-down menuı and click to Attach button.

<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/e/e2/Aws_interface_5.png/400px-Aws_interface_5.png" alt=""><figcaption></figcaption></figure>

\
6\. To assign the interface in the ProSBC, you need to reboot the instance. You can reboot from CLI or use AWS to reboot it.

<figure><img src="https://docs.telcobridges.com/w/images/2/2c/Aws_interface_6.png" alt=""><figcaption></figcaption></figure>

\
7\. Access the Web Portal to add the new interface in the SBC configuration

<figure><img src="https://docs.telcobridges.com/w/images/thumb/f/f5/Aws_interface_7.png/400px-Aws_interface_7.png" alt=""><figcaption></figcaption></figure>

<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/b/ba/Aws_interface_8.png/400px-Aws_interface_8.png" alt=""><figcaption></figcaption></figure>

<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/6/6e/Aws_interface_9.png/400px-Aws_interface_9.png" alt=""><figcaption></figcaption></figure>

\
8\. Follow the procedure below to configure new IP Interface

* [Configuring IP Interfaces](/configuration-details/configuration-by-web-portal-category/ip-network-settings/configuring-ip-interfaces)


# AWS Installation Troubleshooting

Here is a list of suggestions when encountering issue during AWS installation:

#### Launch Failed after step 4

<figure><img src="https://docs.telcobridges.com/w/images/thumb/5/5d/FailedLaunch.png/800px-FailedLaunch.png" alt=""><figcaption></figcaption></figure>

```
   Follow the link:
```

<figure><img src="https://docs.telcobridges.com/w/images/thumb/c/c1/FailedLaunchLink.png/800px-FailedLaunchLink.png" alt=""><figcaption></figcaption></figure>

* Click on “Continue to Subscribe”:

<figure><img src="https://docs.telcobridges.com/w/images/thumb/5/5e/Subscribe.png/800px-Subscribe.png" alt=""><figcaption></figcaption></figure>

* If you agree with Amazon conditions, click on “Accept Software Terms & Launch with 1-click”. Now, you are ready to launch the instance you need:

<figure><img src="https://docs.telcobridges.com/w/images/thumb/2/22/Accept.png/800px-Accept.png" alt=""><figcaption></figcaption></figure>

<br>

#### Test if ProSBC is up and running in real-time

You can open a session of the image running CentOS7 and check the status of Pro*SBC* in real-time. Depending on your operating system, you can follow the links on Amazon guide to do so:

| Your Computer                                  | Topic                                                                                                                           |
| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| Linux                                          | [Connecting to Your Linux Instance Using SSH](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AccessingInstancesLinux.html) |
| Windows                                        | [Connecting to Your Linux Instance from Windows Using PuTTY](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/putty.html)    |
| All (using Firefox, Edge or Internet Explorer) | [Connecting to Your Linux Instance Using MindTerm](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/mindterm.html)           |


# Recovering an Elastic IP address

Recover an Elastic IP address for ProSBC in AWS. The static IPv4 address can be remapped to another instance to mask an instance or software failure.

An Elastic IP address is a static IPv4 address designed for dynamic cloud computing. By using an Elastic IP address, you can mask the failure of an instance or software by rapidly remapping the address to another instance in your account. An Elastic IP address is allocated to your AWS account and is yours until you release it. If you have released your Elastic IP address, you might be able to recover it. The following rules apply:

* You cannot recover an Elastic IP address if it has been allocated to another AWS account, or if it will result in your exceeding your Elastic IP address limit.
* You cannot recover tags associated with an Elastic IP address.
* You can recover an Elastic IP address using the Amazon EC2 API or a command-line tool only.

### Recovering an Elastic IP address with AWS CLI

You need to install the AWS Command Line Interface (CLI).

1\. For the latest version of the AWS CLI, use the following command block:

```
 $ curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip" 
```

```
 unzip awscliv2.zip 
```

```
 sudo ./aws/install 
```

2\. Confirm the installation.

```
aws --version
aws-cli/2.1.12 Python/3.7.3 Linux/3.10.0-1127.18.2.el7.tb.x86_64 exe/x86_64.centos.7 prompt/off 
```

3\. Type aws configure and press enter. Enter the following when prompted:

```
 AWS Access Key ID [None]: enter the Access Key Id from the credentials.csv file you downloaded in the Create an AWS IAM User part
Note: this should look something like AKIAPWINCOKAO3U4FWTN
AWS Secret Access Key [None]: enter the Secret Access Key from the credentials.csv file you downloaded in the Create an AWS IAM User part
Note: this should look something like 5dqQFBaGuPNf5z7NhFrgou4V5JJNaWPy1XFzBfX3
Default region name [None]: enter us-east-1
Default output format [None]: enter json
```

![](https://docs.telcobridges.com/w/images/thumb/9/96/AWS_CLI_1.png/600px-AWS_CLI_1.png)

4\. Use the allocate-address AWS CLI command and specify the IP address using the --address parameter as follows.

```
 aws ec2 allocate-address --domain vpc --address 203.0.113.3 
```

### Recovering an Elastic IP address with PowerShell

You need to install AWS Tools for PowerShell on computers that are running Windows with Windows PowerShell 5.1, or PowerShell Core 6.0 or later.

1\. Start a PowerShell session. We recommend that you don't run PowerShell as an administrator with elevated permissions except when required by the task at hand. This is because of the potential security risk and is inconsistent with the principle of least privilege.

2\. To install the modularized AWS.Tools package, run the following command.

```
 PS > Install-Module -Name AWS.Tools.Installer

Untrusted repository
You are installing the modules from an untrusted repository. If you trust this repository, change its InstallationPolicy value by running the Set-PSRepository cmdlet. Are you sure
 you want to install the modules from 'PSGallery'?
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "N"): y 
```

If you are notified that the repository is "untrusted", it asks you if you want to install anyway. Enter y to allow PowerShell to install the module. To avoid the prompt and install the module without trusting the repository, you can run the command with the -Force parameter.

```
 PS > Install-Module -Name AWS.Tools.Installer -Force
```

3\. You can now install the module for each AWS service that you want to use by using the Install-AWSToolsModule cmdlet. For example, the following command installs the IAM module. This command also installs any dependent modules that are required for the specified module to work. For example, when you install your first AWS.Tools service module, it also installs AWS.Tools.Common. This is a shared module required by all AWS service modules. It also removes older versions of the modules, and updates other modules to the same newer version.

```
PS > Install-AWSToolsModule AWS.Tools.EC2,AWS.Tools.S3 -CleanUp
  Confirm
  Are you sure you want to perform this action?
  Performing the operation "Install-AWSToolsModule" on target "AWS Tools version 4.0.0.0".
  [Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"):

  Installing module AWS.Tools.Common version 4.0.0.0
  Installing module AWS.Tools.EC2 version 4.0.0.0
  Installing module AWS.Tools.Glacier version 4.0.0.0
  Installing module AWS.Tools.S3 version 4.0.0.0

  Uninstalling AWS.Tools version 3.3.618.0
  Uninstalling module AWS.Tools.Glacier
  Uninstalling module AWS.Tools.S3
  Uninstalling module AWS.Tools.SimpleNotificationService
  Uninstalling module AWS.Tools.SQS
  Uninstalling module AWS.Tools.Common
```

4\. To add a new profile to the AWS SDK store, run the command Set-AWSCredential. It stores your access key and secret key in your default credentials file under the profile name you specify.

```
PS > Set-AWSCredential `
                 -AccessKey AKIA0123456787EXAMPLE `
                 -SecretKey wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY `
                 -StoreAs MyNewProfile
```

* -AccessKey– The access key ID.
* -SecretKey– The secret key.
* -StoreAs– The profile name, which must be unique. To specify the default profile, use the name default.

5\. Use the New-EC2Address AWS Tools for Windows PowerShell command and specify the IP address using the -Address parameter as follows.

```
PS C:\> New-EC2Address -Address 203.0.113.3 -Domain vpc -Region us-east-1
```


# Cloud - Azure

Install and configure ProSBC on Microsoft Azure. Minimum requirements are 2 vCPUs, 7 GB RAM, and a VM size supporting Advanced Networking.

### Introduction

This article provides installation and configuration information for people launching an instance of *ProSBC* on the Microsoft Azure infrastructure.

### Requirements

Minimum Azure cloud Requirements:

* 2 VCPUs
* 7 GB RAM
* VM Size that has a Network interface with Advanced Network capability (Mellanox NIC interface)

The Following table provides recommended VM sizes based on the number of sessions:

<table><thead><tr><th>Requirements</th><th width="150">Sessions</th><th width="150">VM Size</th><th width="100">VCPUs</th><th width="100">RAM</th><th width="100">Advanced Networking Capable</th></tr></thead><tbody><tr><td>Minimum</td><td>Up to 350*</td><td>D2 v2, DS2_v2</td><td>2</td><td>7 Gb</td><td>Yes</td></tr><tr><td>Recommended</td><td>350*-1000*</td><td>D4 v3, D4s_v3</td><td>4</td><td>16 Gb</td><td>Yes</td></tr><tr><td>Recommended</td><td>1000*-2000*</td><td>D8 v3, D8s_v3</td><td>8</td><td>32 Gb</td><td>Yes</td></tr><tr><td>Recommended</td><td>2000*-4000*</td><td>D16 v3, D16s_v3</td><td>16</td><td>64 Gb</td><td>Yes</td></tr></tbody></table>

\*Preliminary estimated values

### Retrieving the Image

Order your ProSBC license and software at the [ProSBC Download site](http://www2.telcobridges.com/ProSBCDownload) (upon completion of your order, a URL of the download image will be sent via email)

### Installation on Azure cloud

#### ProSBC Azure Image

A virtual machine image is a single file that contains a virtual disk that has a bootable operating system installed on it. Images are used to create virtual machine instances in the cloud.

The following sections describe how to upload the latest ProSBC image to your Microsoft Azure account and launch a virtual machine instance running the ProSBC software.

#### Get a Storage Account

You will need a blob container in your Azure storage account. This blob container is required to upload and store a ProSBC VM image. You can either use an existing storage account or create a new one, but make sure that the storage account location matches the location where you plan to create and run your VM.

**Create Resource Group**

If you need to create a storage account to upload the VM image, then you will need a resource group that matches the location where you plan to create and run your VM. If required, create a resource group as follows:

* Log in to the dashboard.
* Select 'Resource groups'.
* From 'Resource groups', click 'Add' item.
* The 'Create a resource group' dialog box appears.
* Provide a name for the resource group.
* Select the appropriate resource group location. This is where you will be creating the VM.
* Click 'Review + Create'.

<figure><img src="https://docs.telcobridges.com/w/images/thumb/9/9d/Az_resource_groups.png/850px-Az_resource_groups.png" alt=""><figcaption></figcaption></figure>

* Wait for completion of the resource group creation before proceeding with the next steps.

**Create Storage Account**

If you require a storage account, do the following:

* Log in to the dashboard.
* Select 'Storage accounts'.
* From 'Storage accounts', click 'Add' item.
* The 'Create a storage account' dialog box appears.
* Select the appropriate resource group.
* Provide a name for the storage account.
* Select the appropriate storage account location. This is where you will be creating the VM.
* For the other parameters, consult <https://docs.microsoft.com/en-us/azure> for more details.
* Click 'Review + Create'.

<figure><img src="https://docs.telcobridges.com/w/images/thumb/2/21/Az_storage_accounts.png/850px-Az_storage_accounts.png" alt=""><figcaption></figcaption></figure>

* Wait for completion of storage account creation before proceeding with the next steps.

**Create Storage Blob Container**

If you require a blob container, do the following:

* Log in to the dashboard.
* Click 'Storage accounts'.
* Select a storage account item to add the blob container.
* Click Blob Services button.

<figure><img src="https://docs.telcobridges.com/w/images/thumb/8/8e/Az_storage_blob_container1.png/850px-Az_storage_blob_container1.png" alt=""><figcaption></figcaption></figure>

* From 'Blobs' top menu, click 'Container' item.
* The 'Blob container' dialog box appears.
* Provide a name for this blob container.
* For the other parameters, consult <https://docs.microsoft.com/en-us/azure> for more details.
* Click 'Ok'.

<figure><img src="https://docs.telcobridges.com/w/images/thumb/f/fb/Az_storage_blob_container2.png/850px-Az_storage_blob_container2.png" alt=""><figcaption></figcaption></figure>

* Wait for completion of storage blob container before proceeding with the next steps.

#### Upload a Virtual Hard Disk (VHD) Image

Follow this procedure to upload the ProSBC image to a storage blob container:

* Before being able to upload the ProSbc image to the storage blob container, you must uncompress (tar.gz) the ProSBC image locally on your PC. You will require at least 40 GB of free space to uncompress the image.
* Log in to the dashboard.
* Click'Storage accounts'.
* Select the appropriate 'storage account' then 'Blobs' container.

<figure><img src="https://docs.telcobridges.com/w/images/thumb/0/02/Az_upload_image1.png/850px-Az_upload_image1.png" alt=""><figcaption></figcaption></figure>

* From the 'Blobs' container top menu, Click 'Upload' menu item.
* The 'Upload blob' dialog box appears.
* Select the Virtual Hard Disk image (sbc\_azure.vhd) to upload from your local disk image location.
* Click 'Upload' button.

<figure><img src="https://docs.telcobridges.com/w/images/thumb/4/4f/Az_upload_image2.png/850px-Az_upload_image2.png" alt=""><figcaption></figcaption></figure>

* Wait until upload completion before proceeding with the next steps. This operation will take a long period of time (40GB to upload).

#### Create a VM Image from the ProSBC storage blob

Follow this procedure to create a VM image from a storage blob:

* Log in to the dashboard.
* Select 'Create a resource'.
* The 'Create resource' dialog box appears.
* Type 'image' in the search text box.
* A list of suggested items appears.
* Click 'Image' item.

<figure><img src="https://docs.telcobridges.com/w/images/e/e4/Az_create_vm_image1.png" alt=""><figcaption></figcaption></figure>

* The 'Create image' dialog box appears.
* Click 'Create'.

<figure><img src="https://docs.telcobridges.com/w/images/c/c3/Az_create_vm_image2.png" alt=""><figcaption></figcaption></figure>

* Provide an image name.
* Select the appropriate resource group.
* Select the appropriate location.
* Click on 'Linux' button for the OS type.
* Browse through storage accounts to select the ProSBC blob.
* Click 'Select' button to complete ProSBC blob selection.
* For the other parameters, consult <https://docs.microsoft.com/en-us/azure> for more details.
* Click 'Create' button.

<figure><img src="https://docs.telcobridges.com/w/images/thumb/0/0f/Az_create_vm_image3.png/850px-Az_create_vm_image3.png" alt=""><figcaption></figcaption></figure>

* Wait until create completion before proceeding with following steps.

#### Create a Virtual Network

If not already available, follow this procedure to create a Virtual Network:

* Log in to the dashboard.
* Select 'Virtual networks'.
* The 'Virtual networks' dialog box appears.
* From 'Virtual networks' top menu, click 'Add' item.
* The 'Create a virtual network' dialog box appears.
* Provide a virtual network name.
* Provide the virtual network's address range in CIDR notation.
* Select appropriate resource group.
* Select appropriate location.
* Provide subnet name and address range.
* For the other parameters, consult <https://docs.microsoft.com/en-us/azure> for more details.
* Click 'Create' button.

<figure><img src="https://docs.telcobridges.com/w/images/thumb/2/28/Az_create_virtual_network.png/700px-Az_create_virtual_network.png" alt=""><figcaption></figcaption></figure>

* Wait until create completion before proceeding with the next steps.

#### Instantiate a ProSBC

Follow this procedure to create a ProSBC instance:

* Log in to the dashboard.
* Select 'Virtual machines'.
* The 'Virtual machines' dialog box appears.
* From 'Virtual machines' top menu, click 'Add' item.
* The 'Create a virtual machine' dialog box appears.
* Select the appropriate resource group.
* Provide a virtual machine name.
* Select the appropriate region. This is where you will be creating the VM.
* Browse VM images to select the appropriate ProSBC VM image.
* Select VM size according to expected performace.
* Select 'SSH public key' option as the Authentification type.
* Type 'tbos' as SSH Authentification Username.
* Provide a SSH public key as SSH Authentification.
* Click 'Next:Disk>'.

<figure><img src="https://docs.telcobridges.com/w/images/thumb/c/c3/Az_create_vm1.png/750px-Az_create_vm1.png" alt=""><figcaption></figcaption></figure>

* The Disks dialog box appears.
* Select the appropriate 'OS disk type' to support your workload or scenario.
* Click 'Next:Networking>'.

<figure><img src="https://docs.telcobridges.com/w/images/thumb/5/59/Az_create_vm2.png/700px-Az_create_vm2.png" alt=""><figcaption></figcaption></figure>

* Select the appropriate Virtual network.
* For the other parameters of this page and the following pages, consult <https://docs.microsoft.com/en-us/azure> for more details.
* Click 'Next:Review + create>'.

<figure><img src="https://docs.telcobridges.com/w/images/thumb/0/00/Az_create_vm3.png/700px-Az_create_vm3.png" alt=""><figcaption></figcaption></figure>

* Wait until create completes before proceeding with the following steps.

**Add Inbound Security Rules**

Follow this procedure to add inbound security rules:

* Log in to the dashboard.
* Select 'Virtual machines'.
* The 'Virtual machines' list dialog box appears.
* Select the appropriate virtual machine to add inbound security rules.
* The virtual machine overview dialog box appears.
* Select 'Networking' item from the virtual machine 'Settings' section.
* Click the 'Add inbound port rule' button.

<figure><img src="https://docs.telcobridges.com/w/images/thumb/8/8d/Az_add_inbound_port_rule1.png/850px-Az_add_inbound_port_rule1.png" alt=""><figcaption></figcaption></figure>

* The 'Add inbound security rule' dialog box appears.
* Fill the different fields in accordance with the expected VM accessibility from public network.
* The security rules must at least allow access to the VM through ports 22 and 12358 for SSH and Web Portal management access.
* The security rules must also allow access to the VM through other ports (i.e. 5060) for signaling and RTP access (ports depend on your system configuration).
* Consult <https://docs.microsoft.com/en-us/azure> for more details.
* Click 'Add' to create the inbound security rule.

<figure><img src="https://docs.telcobridges.com/w/images/thumb/7/70/Az_add_inbound_port_rule2.png/850px-Az_add_inbound_port_rule2.png" alt=""><figcaption></figcaption></figure>

**Advanced Networking**

The Azure GUI does not allow the enabling of the 'Advanced Networking' when creating the VM from a custom image. You must use Azure CLI to do so. Follow this procedure to enable 'Advanced Networking' on a networking interface:

* Log in to the dashboard.
* Select 'Virtual machines'.
* The 'Virtual machines' list dialog box appears.
* Select the appropriate virtual machine.
* The 'Virtual machine' dialog box appears.
* Select 'Networking' item from the virtual machine 'Settings' section.
* Copy to the clipboard the network interface name to modify the 'Accelerated Networking' setting.

<figure><img src="https://docs.telcobridges.com/w/images/thumb/f/fb/Az_advanced_networking1.png/850px-Az_advanced_networking1.png" alt=""><figcaption></figcaption></figure>

* Open a shell command prompt, which is Azure CLI capable (consult <https://docs.microsoft.com/en-us/azure> to install the Azure CLI).
* Enter the following command, using the correct network interface name and resource group, and press enter:

```
 az network nic update --name azure-1if-2801 --resource-group sw_group --accelerated-networking true
```

* The Azure CLI command output will look like the following:

<figure><img src="https://docs.telcobridges.com/w/images/thumb/1/13/Az_advanced_networking2.png/700px-Az_advanced_networking2.png" alt=""><figcaption></figcaption></figure>

* Rebooting will NOT activate the 'Accelarated Networking' on the VM network interface. It is required to do the following operations to complete 'Accelarated Networking' activation:
  * First, 'Stop' the virtual machine (This will take some time to stop the virtual machine).
  * Then, 'Start' the virtual machine.

### Accessing the ProSBC

**ProSBC SSH Access**

By default, there is no root password. You will need to SSH on to the ProSBC using an SSH private key matching the public provided in the SSH public key when #Instantiate a ProSBC instance. Log in using *tbos* as username.

For example, if your ProSBC management IP is 192.168.178.30:

```
 > ssh tbos@192.168.178.30
   ECDSA key fingerprint is 5d:94:a1:93:0f:a4:7a:5d:41:cc:29:49:79:5a:58:f3.
   Are you sure you want to continue connecting (yes/no)? yes
   Warning: Permanently added '192.168.178.30' (ECDSA) to the list of known hosts.
   
   [tbos@prosbc ~]$
```

\
Note: No changes must be done to the repositories on the systems, and no other software should be installed unless written consent from TelcoBridges.

#### Accessing the ProSBC web portal

* Open a web browser to the management IP of the ProSBC, on port 12358. For example, if your server address is 192.168.178.30, the URL would be:\
  [http://192.168.178.30:12358](http://192.168.178.30:12358/)
* You should get to the ProSBC Configuration Wizard<br>

  <figure><img src="https://docs.telcobridges.com/w/images/thumb/b/b7/FreeSBC_WebPortal_Configuration_wizard.png/350px-FreeSBC_WebPortal_Configuration_wizard.png" alt=""><figcaption></figcaption></figure>

From this point, go to [Web Portal Initial Configuration Guide](/initial-installation/2.-initial-configuration/initial-setup) to continue the installation.

### Web Portal Initial Configuration

Click the following link to pursue installation from the web portal: [TSBC-SW:WebPortal:Initial Configuration](/initial-installation/2.-initial-configuration/initial-setup)

### External References

* [Accessing device with SSH and private key using putty](https://devops.profitbricks.com/tutorials/use-ssh-keys-with-putty-on-windows/#connect-to-server-with-private-key)


# 2. Initial Configuration

Configure ProSBC through the Web Portal, the principal interface for telling the session border controller about its available network resources.

### Introduction

The Web Portal is the principal way to interact with the session border controller. It is how the actual configuration of the device takes place. Using the Web Portal you tell the device about its available network resources.

With its operations, maintenance, administration and provisioning (OAM\&P) capabilities, the Web Portal is also the principal interface for day-to-day interactions with the equipment, such as viewing statistics and alarms, providing continuous system performance and health monitoring.

You can also use the Web Portal for more point-in-time requirements, such as performing software upgrades, modifying existing production systems to meet new business requirements, or adding new devices or capacity to existing production systems.

The Web Portal also facilitates configuration management, with the ability to create, validate, and then push out new device configurations. It also supports the ability to easily roll back to previous production configurations as well.

<br>

### Connect to the Web Portal

You connect to the Web Portal with a web browser such as Internet Explorer, Mozilla Firefox or Google Chrome. The address you connect to will be either the LAN machine name or the IP address of the device, followed by the port number. The default port number is 12358.<br>

Example (if the management IP address is 192.168.0.100):

```
 http://192.168.0.100:12358 
```

### Basic configuration

There are many ways to use the SBC. Follow the steps on this page to get a first basic configuration: [SBC Basic configuration](/initial-installation/2.-initial-configuration/basic-configuration)

### ProSBC Versions

Use these links to configure your ProSBC:

* [Version 3.3](/configuration-details/configuration-by-web-portal-category)


# Initial Setup

Run the ProSBC initial setup wizard in a web browser. Have your VTB-format product key and network details ready before you begin.

#### Before You Begin <a href="#before-you-begin" id="before-you-begin"></a>

The initial configuration of the SBC is carried out by accessing a configuration wizard in a web browser (Chrome, Firefox or other). Before you begin, you must have the following information on hand:

* Product key: In the following VTB-XXX-XXXX format. If you do not have this key, please go to our [ProSBC Download site](http://www2.telcobridges.com/ProSBCDownload) .
* Hostname of the unit. It is important to set the host name correctly and to not modify it later, otherwise you will need a new license.
* Will the system be used as a standalone unit or in a Primary/Secondary configuration?
* Does the system require external transcoding? For example, G.711 to G.729a transcoding.
* The role of each of the network interface.

Once you have this information, proceed as described in the following procedures:

#### Initial configuration of ProSBC  <a href="#initial-configuration-of-prosbc-or-freesbc" id="initial-configuration-of-prosbc-or-freesbc"></a>

1- Open a web browser to the IP of your server, on port 12358. For example, if your server address is 192.168.178.30, the URL would be: [http://192.168.178.30:12358](http://192.168.178.30:12358/)&#x20;

2- A Configuration Wizard is displayed.

* Click Continue

<figure><img src="https://telcobridges.gitbook.io/~gitbook/image?url=https%3A%2F%2Fdocs.telcobridges.com%2Fw%2Fimages%2F8%2F80%2F1_recovery_welcome_A.png&#x26;width=300&#x26;dpr=4&#x26;quality=100&#x26;sign=f713f17c&#x26;sv=1" alt=""><figcaption></figcaption></figure>

3- Accept the EULA agreement

&#x20;&#x20;

<figure><img src="https://telcobridges.gitbook.io/~gitbook/image?url=https%3A%2F%2Fdocs.telcobridges.com%2Fw%2Fimages%2Fthumb%2F3%2F3f%2FTSBC_SW_EULA_agreement_1.png%2F700px-TSBC_SW_EULA_agreement_1.png&#x26;width=300&#x26;dpr=4&#x26;quality=100&#x26;sign=3006129&#x26;sv=1" alt=""><figcaption></figcaption></figure>

4- Enter your activation key and hostname Note: You do not need to enter the host name for AWS. &#x20;

<figure><img src="https://telcobridges.gitbook.io/~gitbook/image?url=https%3A%2F%2Fdocs.telcobridges.com%2Fw%2Fimages%2Fthumb%2F0%2F03%2FTSBC_SW_Enter_activation_key_1.png%2F700px-TSBC_SW_Enter_activation_key_1.png&#x26;width=300&#x26;dpr=4&#x26;quality=100&#x26;sign=240b7bda&#x26;sv=1" alt=""><figcaption></figcaption></figure>

5- Enter your SSH and WEB root password Note: You do not need to enter the SSH password for AWS. &#x20;

<figure><img src="https://telcobridges.gitbook.io/~gitbook/image?url=https%3A%2F%2Fdocs.telcobridges.com%2Fw%2Fimages%2Fthumb%2F4%2F46%2FTSBC-SW_Enter_SSH_WEB_Password.png%2F700px-TSBC-SW_Enter_SSH_WEB_Password.png&#x26;width=300&#x26;dpr=4&#x26;quality=100&#x26;sign=3a56ad09&#x26;sv=1" alt=""><figcaption></figcaption></figure>

6- Select the configuration of your SBC. Either standalone, or in a Primary/Secondary configuration Note: This does not apply for AWS.

&#x20;&#x20;

<figure><img src="https://telcobridges.gitbook.io/~gitbook/image?url=https%3A%2F%2Fdocs.telcobridges.com%2Fw%2Fimages%2Fthumb%2F1%2F1f%2FTSBC_SW_standalone_1.png%2F700px-TSBC_SW_standalone_1.png&#x26;width=300&#x26;dpr=4&#x26;quality=100&#x26;sign=90f419d7&#x26;sv=1" alt=""><figcaption></figcaption></figure>

7- If the system requires external transcoding, select it here. As an example, if the system needs G.711 to G.729a transcoding, then select yes. Note: This does not apply for AWS. &#x20;

<figure><img src="https://telcobridges.gitbook.io/~gitbook/image?url=https%3A%2F%2Fdocs.telcobridges.com%2Fw%2Fimages%2Fthumb%2F5%2F58%2FTSBC_SW_transcoding_1.png%2F700px-TSBC_SW_transcoding_1.png&#x26;width=300&#x26;dpr=4&#x26;quality=100&#x26;sign=db79da17&#x26;sv=1" alt=""><figcaption></figcaption></figure>

8- In this window, you define the role of the network adapters in the system. The following is a short description of each type:

* mgmt: Used for management of the system (suggested name: mgmt0)
* ctrl0: Used for communication with the external transcoding devices (suggested name: ctrl0)
* ctrl1: Same as ctrl0. Adds redundancy (suggested name: ctrl1)
* LAN/WAN: SIP/RTP access to private network (suggested name: LAN0) or public network (suggested name: WAN0).

You must configure all IP interfaces. If you are not sure, configure them as management interfaces.&#x20;

<figure><img src="https://telcobridges.gitbook.io/~gitbook/image?url=https%3A%2F%2Fdocs.telcobridges.com%2Fw%2Fimages%2Fthumb%2F0%2F0e%2F2_Recovery_before_bonding_A.png%2F750px-2_Recovery_before_bonding_A.png&#x26;width=300&#x26;dpr=4&#x26;quality=100&#x26;sign=90cce34d&#x26;sv=1" alt=""><figcaption></figcaption></figure>

```
Note: Select the "+" sign to acces more information about an interface.
```

<figure><img src="https://telcobridges.gitbook.io/~gitbook/image?url=https%3A%2F%2Fdocs.telcobridges.com%2Fw%2Fimages%2Fthumb%2Fc%2Fcf%2FTSBC_SW_choose_LAN_interface_role_2.png%2F600px-TSBC_SW_choose_LAN_interface_role_2.png&#x26;width=300&#x26;dpr=4&#x26;quality=100&#x26;sign=4be8ed1c&#x26;sv=1" alt=""><figcaption></figcaption></figure>

```
Note: If 1+1 (control networks ctrl0/ctrl1) or multiple vlan interfaces are needed, make sure all of them are assigned to the appropriate MAC address taken from the Platform (VMware Instance settings or other)  
```

<div align="center"><figure><img src="https://telcobridges.gitbook.io/~gitbook/image?url=https%3A%2F%2Fdocs.telcobridges.com%2Fw%2Fimages%2Fthumb%2Fd%2Fd8%2FNetwork_adapters_MAC_Address_primary_1.png%2F800px-Network_adapters_MAC_Address_primary_1.png&#x26;width=300&#x26;dpr=4&#x26;quality=100&#x26;sign=6f731610&#x26;sv=1" alt="" width="375"><figcaption></figcaption></figure></div>

9- To add an Ethernet Bonding, click Add Bonding.

&#x20;

<figure><img src="https://telcobridges.gitbook.io/~gitbook/image?url=https%3A%2F%2Fdocs.telcobridges.com%2Fw%2Fimages%2Fthumb%2F4%2F43%2F2_Recovery_before_bonding_ClickAddBondingA.png%2F750px-2_Recovery_before_bonding_ClickAddBondingA.png&#x26;width=300&#x26;dpr=4&#x26;quality=100&#x26;sign=7ae28149&#x26;sv=1" alt=""><figcaption></figcaption></figure>

10- Enter a name for the Bonding Pair, followed by the LAN/WAN1 and LAN/WAN 2.

* When you are done, click Continue.

<figure><img src="https://telcobridges.gitbook.io/~gitbook/image?url=https%3A%2F%2Fdocs.telcobridges.com%2Fw%2Fimages%2Fthumb%2Fe%2Fe1%2F3_Recovery_after_bonding_A.png%2F750px-3_Recovery_after_bonding_A.png&#x26;width=300&#x26;dpr=4&#x26;quality=100&#x26;sign=9844e69f&#x26;sv=1" alt=""><figcaption></figcaption></figure>

11- A Confirmation window is displayed.

* If you are satisfied with the configuration, click Confirm.

<figure><img src="https://telcobridges.gitbook.io/~gitbook/image?url=https%3A%2F%2Fdocs.telcobridges.com%2Fw%2Fimages%2Fthumb%2F9%2F96%2F4_Recovery_confirm_bonding_A.png%2F700px-4_Recovery_confirm_bonding_A.png&#x26;width=300&#x26;dpr=4&#x26;quality=100&#x26;sign=65ecbd37&#x26;sv=1" alt=""><figcaption></figcaption></figure>

12- A warning message is displayed alerting you to the possible interruption of the IP interfaces when the change is applied.

* Click OK.

<figure><img src="https://telcobridges.gitbook.io/~gitbook/image?url=https%3A%2F%2Fdocs.telcobridges.com%2Fw%2Fimages%2F9%2F9f%2F5_Recovery_Warning_end_confirm_bonding_A.png&#x26;width=300&#x26;dpr=4&#x26;quality=100&#x26;sign=2d6ae3f1&#x26;sv=1" alt=""><figcaption></figcaption></figure>

13- After the bonding configuration is complete, you must reboot the system.&#x20;

<figure><img src="https://telcobridges.gitbook.io/~gitbook/image?url=https%3A%2F%2Fdocs.telcobridges.com%2Fw%2Fimages%2Fthumb%2Ff%2Ff6%2F6_Following_bonding_configuration_warning_reboot_is_required_A.png%2F700px-6_Following_bonding_configuration_warning_reboot_is_required_A.png&#x26;width=300&#x26;dpr=4&#x26;quality=100&#x26;sign=12e02b43&#x26;sv=1" alt=""><figcaption></figcaption></figure>

#### Configure the IP Interface of the Ethernet Bonded Port <a href="#configure-the-ip-interface-of-the-ethernet-bonded-port" id="configure-the-ip-interface-of-the-ethernet-bonded-port"></a>

To use the newly created Ethernet bonded port, you must configure the VLAN port and IP interface.

1-Select IP Interface from the navigation bar. ![](https://telcobridges.gitbook.io/~gitbook/image?url=https%3A%2F%2Fdocs.telcobridges.com%2Fw%2Fimages%2Fe%2Fef%2F7_IP_Interface_NavBar_A.png\&width=300\&dpr=4\&quality=100\&sign=771efcca\&sv=1)

2-Select the IP Interfaces tab.

* Click Create New IP Interface.

<figure><img src="https://telcobridges.gitbook.io/~gitbook/image?url=https%3A%2F%2Fdocs.telcobridges.com%2Fw%2Fimages%2Fthumb%2F3%2F3a%2F7_Need_to_configure_VLAN_port_and_ip_inetrface_to_use_created_bonding_Before_A.png%2F700px-7_Need_to_configure_VLAN_port_and_ip_inetrface_to_use_created_bonding_Before_A.png&#x26;width=300&#x26;dpr=4&#x26;quality=100&#x26;sign=7e820686&#x26;sv=1" alt=""><figcaption></figcaption></figure>

3-Configure the VLAN port and IP address that will be used to access the Ethernet Bond interface.

* The following image shows the bond0 configured port.

<figure><img src="https://telcobridges.gitbook.io/~gitbook/image?url=https%3A%2F%2Fdocs.telcobridges.com%2Fw%2Fimages%2Fthumb%2F3%2F31%2F7_Need_to_configure_VLAN_port_and_ip_interface_to_use_created_bonding_After_A.png%2F700px-7_Need_to_configure_VLAN_port_and_ip_interface_to_use_created_bonding_After_A.png&#x26;width=300&#x26;dpr=4&#x26;quality=100&#x26;sign=10671d6&#x26;sv=1" alt=""><figcaption></figcaption></figure>

#### &#x20;<a href="#downloading-the-license" id="downloading-the-license"></a>


# SBC Management IP configuration

This article explains how to modify the management network interface of ProSBC

ProSBC will come with a default mgmt0 port after installation. This interface needs to be configured to gain access to the web portal.\
You can use the tbchangeip command to:

* Change the IP address, subnet and gateway of the management port, or select DHCP.
* Change the Domain name servers (DNS) used by the internal host (Used for updating Linux packages or other).

### Command

Type this command from the console:

```
 tbchangeip
```

Follow the instructions.\
\
Note: This command applies for management interface (mgmt) only. This command does not apply for control interface (ctrl) nor voip interfaces (voip).

### Modify static IP address

This example changes the IP address to a static address with no DNS server

* Steps to modify mgmt0 from dhcp to static:

```
Do you want to modify the network settings (enter 'help' for usage) ?[No]                   --> yes
Do you want to modify mgmt0 ?[No]                                                           --> yes
Select network mode (dhcp or static) ?[dhcp]                                                --> static
Enter IP address ?[]                                                                        --> 10.0.0.126
Enter network mask ?[]                                                                      --> 255.255.255.0
```

* Steps to modify the default gateway address (this is necessary to assign an IP address when in static mode.)

```
Would you like to modify the default gateway address ?[No]                                  --> yes
Enter default gateway ip address ?[]                                                        --> 10.0.0.1
```

* Steps to remove the DNS configuration

```
Would you like to modify the DNS configuration ?[No]                                        --> yes
Would you like to reconfigure the DNS (enter 'remove' to erase dns) ?[No]                   --> remove
```

* The script will show you the new configuration. Then you can acknowledge the changes.

```
Do you want to save this new configuration ?[No]                                            --> yes
```

* You can ask the script to restart the network service and apply the new configuration.

```
Would you like to restart the network service now ?[No]                                     --> yes
```

NOTE: For 1+1 systems or when using external transcoding devices, some internal networks are configured. Make sure there is no IP conflict with your management netwokr when configuring these.


# Basic configuration

The basic steps to a working ProSBC configuration: create IP interfaces, enable SIP signaling with a SIP stack, and set up call routing.

These are the basic steps to have a working configuration. For more Use Cases, visit [ProSBC Use Cases](/use-cases/interoperability-examples)

#### IP Interfaces

Create the logical connections and set the IP addresses that the SBC is going to use.\
[Create the IP Interfaces](/configuration-details/configuration-by-web-portal-category/ip-network-settings/configuring-ip-interfaces)

#### Create SIP Stack

Enable SIP signaling for the SBC\
[Creating a SIP Stack](/configuration-details/configuration-by-web-portal-category/sip/creating-a-sip-stack)

#### SIP Transport Server

Configure the ports and protocols for the transport servers of the SIP stack.\
[Create Transport Server](/configuration-details/configuration-by-web-portal-category/sip/creating-a-sip-transport-server)

#### Create NAPs

A Network Access Point or NAP represents the entry point to another network or destination peer (e.g. SIP proxy). A NAP can also be thought of as a trunk group\
Create NAPs for one side ('internal', IP PBX, SIP clients) and another side ('external', SIP trunk). We can create an 'Open' NAP, by specifying a network instead of a specific host.\
[Create NAP ](/configuration-details/configuration-by-web-portal-category/network-access-points-nap)or an [Open NAP](/configuration-details/configuration-by-web-portal-category/network-access-points-nap/allocating-a-sip-open-network-access-point-nap)

#### Create DNS, assign DNS Server

Configure DNS

#### Create Routes

[Create a First Call Route](/configuration-details/configuration-by-web-portal-category/call-routing/creating-a-first-call-route)

For more Use Cases, visit [ProSBC Use Cases](/use-cases/interoperability-examples)


# 3. Uploading a License

TelcoBridges uses licenses to activate ProSBC functions. Get the license file from dashboard.telcobridges.com when installing versions or adding features.

TelcoBridges uses a license-based approach to activate various functions. When installing new versions or adding new features to the system, you may need to add or modify a license. You can get the license file from the dashboard (dashboard.telcobridges.com) or from the TelcoBridges support team.&#x20;

### &#x20;Uploading licenses via the Web portal

1. Click Packages & Licenses from the navigation panel.\
   \ <br>

   <figure><img src="https://docs.telcobridges.com/w/images/b/be/UploadSoftwareLicense_0_A.png" alt=""><figcaption></figcaption></figure>
2. Click Browse and select the software license.<br>
3. Click Upload License.\
   \ <br>

   <figure><img src="https://docs.telcobridges.com/w/images/3/35/UploadSoftwareLicense_2_A.png" alt=""><figcaption></figcaption></figure>
4. Wait for the page to reload and monitor the process by pressing the *now* button, from time to time.

\
For more information see the [host control](/initial-installation/3.-uploading-a-license/host-control) page


# Host-control

The host control panel, available from Toolpack 2.5, provides a common way to run Toolpack-specific tasks on the servers where Toolpack is installed.

#### Host control

Starting with Toolpack 2.5 a series of task are available to run from the host control panel (servers on which Toolpack is installed). The host control panel is accessed from the host status page. Its goal is to provide a common way to run Toolpack specific tasks, such as:

* Upload a license
* Upload a Toolpack package
* Upgrade the host's packages (tblinux only)
* Shutdown a host
* Check control action status

**Upload a license**

Although it is still possible to manually copy the license to the appropriate folder on the host, this Upload action will take care of that task. It enables you to choose the license file to upload, and then install the license. Once this action is completed successfully, the OAM application loads the license and installs it on the appropriate TMedia unit. This will require a reboot of that unit.

* [Add and change licenses](/initial-installation/3.-uploading-a-license/add-change-licenses)

**Upload a Toolpack package**

This task uploads and installs the Toolpack installer on the specified host. You must still create a package and activate it so that the upgrade is applied at a suitable time. The only limitation is that this can only be used for minor upgrades, because the setup parameters will be lost for major upgrades.

*Warning* [*SELinux*](/initial-installation/3.-uploading-a-license/host-control/selinux) *must be disabled (permissive or enforce SELinux will hinder package installation). Click* [*here*](/initial-installation/3.-uploading-a-license/host-control/selinux-management) *to disable SELinux.*

**Upgrade the host's packages**

This task updates all packages of the tblinux distribution to the latest stable version (assuming that the TMG has access to the web). This upgrade is recommended so that you always have the latest fixes. (This may take a while if the tblinux was not recently updated.)

**Shutdown a host**

This task will either reboot or shutdown a host depending on user input. This is especially important for the TMG, becauase it is important to shut it down properly to avoid corruption on the flash-based drive.

**Check control action status**

The status of each of the above actions can be viewed with two fields in the host control panel.

* The *current action* log is the log of the action that is currently executing. This means only one action per host will be allowed at one time, however, you can queue them.
* The *last action* log is the log of the last action that was completed (either successfully or with an error). The status can be refreshed buy pressing the 'now' button at the top of the page.

See this link for error codes description:

<http://tldp.org/LDP/abs/html/exitcodes.html>


# SELinux

SELinux on ProSBC hosts: the Linux Security Modules mechanism that supports mandatory access control security policies in the kernel.

Security-Enhanced Linux (SELinux) is a Linux feature that provides a mechanism for supporting access control security policies, including U.S. Department of Defense style mandatory access controls, through the use of Linux Security Modules (LSM) in the Linux kernel.[en.wikipedia.org/wiki/Security-Enhanced\_Linux](http://en.wikipedia.org/wiki/Security-Enhanced_Linux)<br>

### Toolpack and SELinux<br>

The Toolpack software doesn't support SELinux. Enabling it while Toolpack is running will lead to unexpected behavior.<br>

### References<br>

[How to get SELinux status](/initial-installation/3.-uploading-a-license/host-control/selinux-management)

[How to disable SELinux](/initial-installation/3.-uploading-a-license/host-control/selinux-management)


# SELinux management

Check and change SELinux status on a ProSBC host: read the current mode, set SELINUX=disabled in the config file, then reboot or use setenforce.

### How to get SELinux status<br>

The following command will retreive the SELinux status of your system (output may vary):<br>

```
 sestatus 
```

exemple from CentOS 5.3<br>

```
 SELinux status: enabled
 SELinuxfs mount: /selinux
 Current mode: permissive
 Mode from config file: permissive
 Policy version: 21
 Policy from config file: targeted
```

<br>

### How to disable SELinux<br>

#### Set SELinux to permissive (not truly disabled)<br>

```
 setenforce 0
```

<br>

#### Disable SELinux entirely<br>

Edit the file:<br>

```
 vi /etc/selinux/config
```

Set the line to SELINUX=disabled<br>

```
 # This file controls the state of SELinux on the system.
 # SELINUX= can take one of these three values:
 #       enforcing - SELinux security policy is enforced.
 #       permissive - SELinux prints warnings instead of enforcing.
 #       disabled - SELinux is fully disabled.
 SELINUX=disabled                                            <------ Line to modify
 # SELINUXTYPE= type of policy in use. Possible values are:
 #       targeted - Only targeted network daemons are protected.
 #       strict - Full SELinux protection.
 SELINUXTYPE=targeted
```

Reboot or use the setenforce command:<br>

```
shutdown -r now
or
setenforce 0
```


# Add/Change Licenses

Add or change Toolpack licenses that activate ProSBC software and hardware functions when installing, adding capabilities, or fitting new modules.

TelcoBridges uses a license-based approach to activate software or hardware functions in Toolpack or the underlying Telcobridges hardware. Whether you are installing Toolpack, implementing new software capabilities, or adding new hardware modules, you may be required to add or modify a license. The following instructions will enable you to do so.

### Reference

* [Upload licence for Toolpack v3.2](/maintenance-and-troubleshooting/system-upgrade/uploading-a-license)


# Add/Change Licenses Manually

Install ProSBC licenses by hand: copy the file to the license directory, overwrite the old license, erase the installed marker, or use tbautoinstall.

#### Adding licenses

* Copy the new licenses in the license directory.

```
 cp [MyNewLicense][InstallDir]/toolpack/pkg/licenses/
```

\
Example:

```
 cp ./TB002933_RELEASE_V3_2_license.dat /lib/tb/toolpack/pkg/licenses/
```

#### &#x20;Updating licenses

* Overwrite the old license with the new one.
* Erase the .\[TmediaSerial]\_license\_installed file.

```
 cp [MyNewLicense][InstallDir]/toolpack/pkg/licenses/
 rm [InstallDir]/toolpack/pkg/licenses/.[TmediaSerial]_license_installed
```

\
Example:

```
 cp ./TB002933_RELEASE_V3_2_license.dat /lib/tb/toolpack/pkg/licenses/
 rm /lib/tb/toolpack/pkg/licenses/.[TmediaSerial]_license_installed
```

#### &#x20;Installing licenses manually

Alternatively, you can install the license manually with the tool *tbautoinstall* as instructed [here](https://docs.telcobridges.com/wiki/Tbautoinstall#Installing_a_license).


# Applications

ProSBC applications: carrier and NGN interconnection, SIP trunking, hosted PBX, remote workers, SIP peering, transcoding, STIR/SHAKEN and monitoring.


# Carrier Interconnection

Use ProSBC for carrier interconnection: a safe SIP interface to other IP carriers over dedicated networks or the internet, with high session density.

### Carrier Interconnection Solutions

VoIP Carriers can trust TelcoBridges Session Border Controller products to provide an efficient and safe SIP interconnection interface to other IP carriers over dedicated networks or over the Internet. Our solutions offer high session density, integrated media transcoding with a wide range of vocoders, security gating to filter out undesired traffic and flexible SIP protocol adaptation capabilities all within a cost-effective package. As demands on carrier networks continue to expand, our technology and support offerings are rapidly becoming the solution of choice for tier-1 carriers who require carrier grade equipment with high performance, but with a more reasonable CAPEX and OPEX outlay than what is currently found in today’s market.

#### IP network adaptation

Acting as a SIP Back-to-back User Agent (B2BUA) and including a wide range of SIP header manipulation capabilities, our solutions can normalize SIP traffic between multiple disparate networks. Providing high-density media adaptation within the same product ensures that a single solution can do all the jobs required to interconnect all networks.

#### Security

Distributed Denial-of-Service (DDOS) protection, call admission control and dynamic blacklisting are just a few examples of security features built into our solutions to keep your network safe from undesired traffic and people. We at TelcoBridges want to make sure your resources are spent on your customers’ services, not serving hackers.

#### Carrier Grade

With more than a decade of experience in network adaptation and deployed in over 100 countries, our solutions are designed for solid interworking. Combining our five-nines (99.999%) architecture with international class 24/7 support, we, at TelcoBridges, know what you are expecting of a carrier-grade system. This is what we deliver for your business and customers, every day, to be successful.

#### Cost Effective

Using state-of-the-art components and architecture, TelcoBridges proposes high session density and transcoding solutions that will reduce the capital and operation expenses of your network infrastructure.

ProSBC Session Border Controller is ideal to interconnect carriers


# Monitoring as a Service (MaaS)

Monitoring as a Service is a hosted, fully managed, customizable cloud monitoring solution for ProSBC users.

Monitoring as a Service is a hosted, fully managed, customizable cloud-based monitoring solution designed for ProSBC users. To learn more about MaaS, visit our [Corporate Site](https://telcobridges.com/sbc/products/monitoring-service/).

<figure><img src="https://docs.telcobridges.com/w/images/a/a6/MaaS_cloud_logo_384-300x228.jpg" alt="TelcoBridges Monitoring as a Service (MaaS) cloud logo"><figcaption></figcaption></figure>


# NGN Interconnection

Use ProSBC for NGN interconnection as operators migrate to an all-IP core, whether the packet core is standardized over IMS or built on a softswitch.

### NGN Interconnection Solutions

Network operators have increasingly migrated to next generation networks where the core is all IP. Regardless if the packet core is standardized over IMS or simply using a softswitch infrastructure, operators can trust TelcoBridges Session Border Controller products for the IP interconnection between internal devices and/or demarcation points toward external IP networks. Conversion to all-IP has opened network infrastructure to new services and user innovations but also increased the interoperability challenges that come with the SIP protocol. Requirements for robustness, ease of deployment and maintenance are still very present for tier-1 operators willing to benefit from this new technology without increasing the existing CAPEX and OPEX of their network. TelcoBridges solutions offer a flexible call routing engine, session density, integrated media transcoding, security and extensive protocol adaptation while keeping it all easily manageable and operable to make sure operators keep their focus on customer services, not network equipment.

<figure><img src="https://docs.telcobridges.com/w/images/thumb/e/e5/Sbc_ngn.png/600px-Sbc_ngn.png" alt="SBC in an NGN core: softswitch, media server and PSTN gateway connect through the SBC to an IMS network over G.722.2, a mobile network over AMR and an external NGN over G.711."><figcaption></figcaption></figure>

#### IP network adaptation and routing

TelcoBridges Session Border Controllers benefit from a decade of experience making IP devices that interoperate with each other. As a SIP Back-to-back User Agent (B2BUA), the solution offers a powerful routing engine to receive, inspect, modify and eventually route (or drop) SIP sessions. High-level autonomous routing features such as backup routes, priority, load balancing and more are available for customization to fit the needs of operators. External routing engines such as database and RADIUS/Diameter (ro interface) are also possible to integrate with existing infrastructures.

#### Rapid and ease of deployments

What is a next generation network without an adequate operation and management infrastructure? TelcoBridges’ provisioning and monitoring interfaces allow for quick operations and troubleshooting by a local technician through a web GUI or a console interface while also providing a complete remotely accessible machine-to-machine RESTful language. Supporting these interfaces along with more traditional ways of network provisioning/monitoring such as SNMP or configuration files, TelcoBridges’ SBC are the fastest and easiest network equipment to deploy which can adapt to an operator’s existing operation infrastructure.

#### Security

Whether the interconnections happen within a single private network, between multiple internal networks or straight through the Internet, having a demarcation point with built-in security is always a plus to guarantee your services stability. TelcoBridges’s solution is built to act as such demarcation point and to normalize the incoming SIP and media traffic so an operators’ internal devices don’t have to worry about it. You can trust TelcoBridges’ SBC to be that guardian.

#### Carrier Grade

With the many possible SBC products present in the market today, it is really important for operators to select solutions that fit their demanding environment. Nothing less than carrier grade equipment with five nines redundancy combined with year around 24/7 support is the baseline for worry-free infrastructure. TelcoBridges has been designing and deploying carrier grade solutions for carriers and operators for the last decade in more than 100 countries around the world. We have the solution and the experience operators need.

ProSBC Session Border Controller is ideal to interconnect Next Generation Networks


# Operator Interconnection

Use ProSBC for operator interconnection at access infrastructure and carrier demarcation points, with session density and rapid deployment in mind.

### Operators Interconnection Solutions

Network operators have different interconnection needs whether they are referring to access infrastructure or to other operator/carrier demarcation points. Starting from session density and rapid deployment to extended routing rules, fulfilling these requirements with minimal CAPEX and OPEX is the key to an operators’ success. TelcoBridges’ solution can accomplish these targets with proven state-of-the-art technology and a decade of expertise in bridging traffic between worldwide telcos.

<figure><img src="https://docs.telcobridges.com/w/images/thumb/0/0f/Sbc_operators.png/600px-Sbc_operators.png" alt="SBC for operators: the operator&#x27;s NGN, IP core and IMS reach an enterprise network over MPLS through an SBC at each end, and external carrier networks through the same demarcation point."><figcaption></figcaption></figure>

#### Security

Interconnecting devices and IP networks means filtering out and normalizing incoming traffic to protect the operator’s network. TelcoBridges’s Session Border Controllers (SBCs) act as SIP Back-to-back User Agents (B2BUA) and regulate both signaling and media streams between borders to ensure legitimate traffic goes through while dropping rogue traffic flows. Whether the demarcation point is on a private network segment or the Internet, TelcoBridges’ solution will only let valid customers get through.

#### Rapid and ease of deployments

For operators, deploying innovative services in a fast and efficient manner is crucial for customer satisfaction. TelcoBridges’ solutions offer multiple provisioning and monitoring interfaces allowing for rapid integration into existing operator infrastructures. With legacy console configuration to RESTful API programmatic provisioning and a web interface, the SBC product can satisfy all operation personnel, from on-site technicians to network operations center (NOC) engineers and provisioning department members - TelcoBridges solutions are built to fit in these different environments.

#### Carrier Grade

Operators cannot settle for anything less than five-nines equipment backed-up by a solid 24/7 support program available year round. It is the only way to deliver top quality services to end customers. TelcoBridges is proud to have deployed carrier grade equipment over the last decade in more than 100 countries around the world.

#### Cost effectiveness

Having access to SBC solutions that offer a wide range of session density, without limitation over an extended feature set, is key to keeping operational expenses low as it allows the reuse of the same architecture for multiple locations in the network. TelcoBridges SBC solutions all support the same vast feature set and operational interfaces thus assuring quick return-on-investment (ROI).

#### IP network adaptation and routing

Interconnecting networks invariably implies routing traffic toward proper endpoints and adapting this same traffic for the targeted destination. TelcoBridges solutions offer a highly flexible autonomous, or remotely controlled, routing engine integrated with SIP message analysis and alteration scripting architecture. All the capabilities required to adapt for a mobile network or simply for an IP PBX are present in the products.

ProSBC Session Border Controller is ideal for operators’ interconnection needs


# SIP subscribe notify publish forwarding

ProSBC forwards SIP Subscribe, Notify and Publish messages between users and registrars, following the same rules as SIP registration forwarding.

### SIP Subscribe overview

The SIP SUBSCRIBE method allows users to subscribe to various services, and get notified of events related to these services. Typical services (packages) that phones will register to are:

* Voice mail
* Presence
* Conference

Each user's device can register to various packages, then receive notifications for each of these packages (independently).

### SIP Subscribe/Publish forwarding

ProSBC will forward SUBSCRIBE or PUBLISH requests from users to Registrar (PBX)

<figure><img src="https://docs.telcobridges.com/w/images/thumb/5/5f/Subscribe_request_overview.png/700px-Subscribe_request_overview.png" alt="Bob&#x27;s phone sends SIP SUBSCRIBE to the SBC, which forwards it upstream to the SIP registrar or PBX."><figcaption></figcaption></figure>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/5/54/Subscribe_response_overview.png/700px-Subscribe_response_overview.png" alt="SUBSCRIBE is acknowledged: 200 OK travels back from the registrar through the SBC to Bob&#x27;s phone."><figcaption></figcaption></figure>

### SIP Notify forwarding

ProSBC will forward NOTIFY requests from Registrar (PBX) back to users.

<figure><img src="https://docs.telcobridges.com/w/images/thumb/e/e8/Notify_request_overview.png/700px-Notify_request_overview.png" alt="The registrar sends NOTIFY downstream through the SBC to Bob&#x27;s phone."><figcaption></figcaption></figure>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/a/a8/Notify_response_overview.png/700px-Notify_response_overview.png" alt="NOTIFY is acknowledged: 200 OK travels up from Bob&#x27;s phone through the SBC to the registrar."><figcaption></figcaption></figure>

<br>

### Contact remapping

When forwarding a SIP Subscribe message from a user to the registrar, ProSBC will remap the contact to make itself the contact. This way, the Registrar will send response messages and Notify events through ProSBC, and thus make sure to "hide" private network topology from users (avoid messages being sent directly from registrar to users).

Because the contact's domain is being remapped, ProSBC will also remap the contact's user name to make sure there is not user name conflict between two domains that would have the same user name.

<figure><img src="https://docs.telcobridges.com/w/images/thumb/0/04/Subscribe_topology_hiding.png/700px-Subscribe_topology_hiding.png" alt="Contact remapping: the SBC rewrites each contact to an alias at its own IP, so bob@abc.com and bob@telco.com become bob_ALIAS-1 and bob_ALIAS-2."><figcaption></figcaption></figure>

### SIP authorization

SIP authorization requests (401/407 Unauthorized) are forwarded from Registrar to users, allowing users to send the request again with appropriate credentials.\
ProSBC does not perform authorization by itself, only forwards between users and registrars.

### NAT traversal

* ProSBC handles SIP Subscribe NAT traversal to allow interaction between SIP User Agents from public and private networks.
  * ProSBC detects the actual IP from which users are sending messages, so responses and Notify messages can be forwarded properly, even in case users are unaware that they are behind a NAT

### Configuring

SIP Subscribe/Publish/Notify forwarding is automatically available when configuring SIP Domain for [SIP Registration forwarding](https://prosbcdocs.telcobridges.com/configuration-details/configuration-by-use-case/sip-registration-forwarding):

* [Creating a SIP domain](https://prosbcdocs.telcobridges.com/configuration-details/configuration-by-use-case/sip-registration-forwarding/creating-a-sip-domain)

### References

* [Understanding SIP Subscribe](https://andrewjprokop.wordpress.com/2015/03/11/a-deep-dive-into-sip-subscriptions/)
* [IANA SIP Event types](https://www.iana.org/assignments/sip-events/sip-events.xhtml)


# STIR/SHAKEN

Configure ProSBC with the TransNexus ClearIP server for STIR/SHAKEN signing and verification, including routing scripts, NAPs and route retry actions.

## Network Diagram and Call Scenarios

This section provides the simplified network diagram containing two telephone service providers, and the call scenarios.

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2F1g4Ii9SvLuFs58iqIJBr%2Fimage.png?alt=media&amp;token=e17326f2-7408-4b0c-bbd9-78e791866166" alt="STIR/SHAKEN across two providers: ProSBC-A signs via ClearIP-A, hands the call to ProSBC-B, which verifies via ClearIP-B before delivery."><figcaption></figcaption></figure>

1. Source of ServiceProvider-A sends a call to ProSBC-A.
2. ProSBC-A forwards the call to ClearIP-A, which is a SIP redirect server providing LCR, fraud control, SHAKEN AS (Authentication Service) and other features.
3. ClearIP-A performs LCR, fraud control and SHAKEN AS logic, then sends one of the following responses to ProSBC-A
   1. SIP 404 Not Found: No fraud or SHAKEN AS error is detected, and routing information is unavailable.
   2. SIP 603 Decline: Fraud is detected or SHAKEN AS request fails.
   3. SIP 3xx Redirect: Destination information (ProSBC-B of ServiceProvider-B) and a SIP Identity header including a digitally signed token that includes the calling number (secure caller ID).
4. ProSBC-A processes the response
   1. SIP 404 Not Found: ProSBC-A tries the next destination configured in its local routing policy.
   2. SIP 603 Decline: Proxies the response back to Source to block the call.
   3. SIP 3xx Redirect: Forwards the call to ProSBC-B with the Identity header.
5. ProSBC-B forwards the call to ClearIP-B, which is a SIP redirect server providing fraud control, SHAKEN VS (Verification Service) and other features.
6. ClearIP-B performs fraud control and SHAKEN VS logic, and then sends one of the following SIP responses to ProSBC-B.
   1. SIP 404 Not Found: No fraud or SHAKEN VS error is detected, and routing information is unavailable.
   2. SIP 603 Decline: Fraud is detected or SHAKEN VS request fails.
   3. SIP 3xx Redirect: Destination information (Destination of ServiceProvider-B) is attached.
7. ProSBC-B processes the response
   1. SIP 404 Not Found: ProSBC-B tries the next destination configured in its local routing policy.
   2. SIP 603 Decline: Proxies the response back to ProSBC-A to block the call.
   3. SIP 3xx Redirect: Forwards the call to Destination.

Note: A variant scenario is that Destination of ServiceProvider-B is configured as the next destination in the local routing policy of ServiceProvider-B, ClearIP-B returns SIP 404 Not Found, then ProSBC-B does failover to Destination.

## ProSBC Configuration

This section provides ProSBC configuration for the solution.

### Configure Routing Script

ProSBC is configured to use routing script to handle SIP 3xx Redirect response.

1\. Enable routing script

```
Gateway->Use script
```

2\. Load routing scripts

```
Gateway->Routes->Routing Script->Import Script File
   File->txnx_shaken.rb
   ScriptType->TxNx
   Load on startup->unchecked
Gateway->Routes->Routing Script->Import Script File
   File->txnx_routing.rb
   ScriptType->Txnx
   Load on startup->checked
```

{% file src="/files/vmpEiXakxnAMNw6w8qNd" %}

### Configure NAP (Network Access Point)

ClearIP-A and ClearIP-B are configured as NAP on ProSBC-A and ProSBC-B respectively. A general SIP endpoint, NAP-ANY, is configured on both ProSBC’s.

* On ProSBC-A

```
NAPs->Create New NAP
    Name->NAP_ClearIP_A
    Proxy address->x.x.x.x (IP of ClearIP-A)
NAPs->Create New NAP
    Name->NAP_ANY
Use Proxy Address->Unchecked
```

* On ProSBC-B

```
NAPs->Create New NAP
    Name->NAP_ClearIP_B
    Proxy address->x.x.x.x (IP of ClearIP-B)
NAPs->Create New NAP
    Name->NAP_ANY
    Use Proxy Address->Unchecked
```

Note: To configure local routing policy with other destination NAPs, ClearIP NAPs should have the highest priority alone all destination NAPs.

### Configure NAP Column

NAP column is used to mark ClearIP as redirect server.

```
Gateway->Routes->NAP Column->Create New NAP Column
    Name: server_type 
    Type Attributes: NORMAL|REDIRECT
    Default: NORMAL
```

* Both NAP\_ClearIP-A and NAP\_ClearIP-B are configured with NAP column server\_type REDIRECT.
* NAP\_ANY are configured with NAP column server\_type NORMAL.

### Configure Static Route

A static route to NAP\_ANY should be configured on both ProSBC’s to allow ProSBC to try the destination in the SIP 3xx response.

```
Gateway->Routes->Create New Static Route
    Name->ToEndpoints
    NAP->any
    Remapped_NAP->NAP_ANY
```

### Enable SIP Custom Header

Enable SIP Custom Headers must be checked to pass SHAKEN Identity header and several other headers used by the solution.

```
Profiles->SIP->Enable SIP Custom Headers
```

### Disable Legacy Redirection Mode

Use legacy redirection mode must be unchecked to allow ProSBC to use routing script to handle SIP 3xx response.

```
SIP->Editing SIP Configuration->Header Parameters->Use legacy redirection mode [uncheck]
```

### Configure Route Retry Action

Route retry action of 3xx, 404 and 603 must be configured to allow ProSBC to perform failover, fraud control and SHAKEN AS/VS request.

```
Profiles->Edit Reason Cause Mapping
    300 Multiple Choices->Route retry action->Process call routing
    302 Moved temporarily->Route retry action->Process call routing
    404 Not found->Route retry action->Continue call
    603 Decline->Route retry action->Stop call
```

Notes:

* The default route retry action of 404 is Stop call.
* The default route retry action of 603 is Continue call.

## Download STIR/SHAKEN scripts

{% file src="/files/vmpEiXakxnAMNw6w8qNd" %}
‎(file size: 2 KB, MIME type: application/zip)
{% endfile %}

**Warning:** Please verify the authenticity of all files downloaded from TelcoBridges, to avoid executing foreign code on your system.

STIR/SHAKEN Scripts


# Transcoding

ProSBC transcoding: software G.711 A-law to u-law conversion and hardware capacity per codec pair for TSBC-HW-TRANS-1372 and 2744 cards.

### Transcoding Solutions

The migration from traditional networks to IP core networks has simplified the overall deployment overhead involved with physical equipment interoperability, but it has not reduced the challenges in making these devices understand each other. Signaling compatibility is certainly one of these challenges, but it is also very close to media compatibility, when it comes to making diverse vendor equipment and networks communicate with each other. TelcoBridges transcoding solutions are designed to overcome these challenges in IP networks by offering a wide range of vocoders packed with extensive signaling transcoding capabilities. This ideal combination offers the most efficient solution to fulfill transcoding needs for carriers, operators and enterprises while keeping CAPEX and OPEX within budget without sacrificing agility or rapid deployment.

<figure><img src="https://docs.telcobridges.com/w/images/3/39/Sbc_transcoding.png" alt="Transcoding with an SBC: services using G.711 inbound tones and G.729a/RFC 4733 reach carrier X over AMR-WB and carrier Y over G.722 through ProSBC."><figcaption></figcaption></figure>

#### IP network adaptation

Whether TelcoBridges solutions are required to resolve signaling or complex media stream transcoding, or all of these at the same time, the state-of-the-art architecture and hardware technology of the ProSBC Session Border Controller can tackle these challenges head-on. With a vast list of supported vocoders for wireline, wireless and high-definition media streams, the solution can address all possible transcoding needs. The embedded resource optimization engine included in these solutions dynamically ensures transcoding capabilities are used only when necessary to maximize the system throughput.

#### Rapid and ease of deployments

Deploying transcoding solutions to bridge devices and networks should be a painless and straightforward process for operators, carriers and enterprises. To guarantee this, TelcoBridges solutions offer multiple provisioning and monitoring interfaces for fast integration into existing network infrastructures. From legacy console configuration to RESTful API programmatic and web interface, the SBC access interfaces satisfy all operation personnel from IT network managers and on-site technicians, to Network Operations Center (NOC) engineers. Less time spent managing a network means more time to invest in delivering innovative end-customer services.

#### Carrier Grade

TelcoBridges solutions all benefit from a decade of experience in building and deploying always-on services with the highest industry standards for reliability and up-time. Targeted to carriers, operators and large enterprises around the world, TelcoBridges’ carrier grade portfolio is designed to be a worry-free experience. TelcoBridges is proud to have deployed highly available equipment in more than 100 countries around the world.

#### Cost effectiveness

Budget is always a key consideration when introducing a transcoding solution into a network. TelcoBridges’ scalable approach for transcoding media resources ensures the initial capital expense addresses not only what is required to start a project, but also allows for an adjustment of those needs down the road when the traffic grows and evolves. TelcoBridges’ transcoding solutions provide a fast Return-On-Investment (ROI) to help get more traction with new services and deployments.

### Software Transcoding Capacity

| Supported CODEC Combinations (version 3.3) | Software Transcoding |
| ------------------------------------------ | -------------------- |
| G.711 alaw <-> G.711 ulaw                  | All sessions         |

### Configurations

See [Software Transcoding](/use-cases/applications/transcoding/software-transcoding)

### Hardware Transcoding Capacity

| Popular CODEC Combinations                      | TSBC-HW-TRANS-1372 | TSBC-HW-TRANS-2744 |
| ----------------------------------------------- | ------------------ | ------------------ |
| <p>G.711 DTMF in-band<br><-> G.711 RFC 2833</p> | 1372               | 2744               |
| <p>G.711 fax passthrough<br><-> T.38</p>        | 740                | 1480               |
| G.711 <-> G.723.1                               | 740                | 1480               |
| G.711 <-> G.729ab                               | 848                | 1696               |
| G.711 <-> AMR-NB                                | 574                | 1148               |
| G.711 <-> AMR-WB                                | 404                | 808                |
| G.711 <-> G.722                                 | 404                | 808                |
| G.711 <-> iLBC                                  | 494                | 988                |

ProSBC Session Border Controller is ideal for transcoding needs.

### Configurations

For ProSBC Hardware Transcoding, you need to purchase the hardware and install this in your central office. The network setup is described here:

* [ProSBC:Hardware Transcoding Network Setup](/configuration-details/configuration-by-use-case/transcoding-unit-configuration/baremetal-and-virtual-machine)
* [Transcoding use case with an external transcoding device](/configuration-details/configuration-by-use-case/transcoding-unit-configuration)

### Network interfaces & cabling

For the number of network interfaces (NICs) required per deployment topology — standalone, 1+1, and with or without an external transcoder — and how to wire the ctrl0/ctrl1 control interfaces in a High Availability system, see [Network Interface Requirements](/initial-installation/1.-instructions-by-platform/network-interface-requirements).

### References

* [TSBC-HW-TRANS Datasheet](/appendices/appendix-b-product-datasheets)


# Software Transcoding

Software transcoding performs a-law to u-law conversion in system software instead of dedicated hardware. Requires the SOFTWARE\_TRANSCODE\_CALLS license.

### Overview

Software Transcoding enables call transcoding to be performed directly by the system software, providing an alternative to hardware-based transcoding. This feature offers flexibility in handling different audio codecs during call setup and transmission.

### Key Features

* **Software-Based Processing**: Performs audio transcoding through system software rather than dedicated hardware
* **Codec Support**: Currently supports a-law and u-law audio codec transcoding
* **Automatic Selection**: The system automatically priorities software transcoding when supported and enabled

### Requirements

#### License Requirements

To use Software Transcoding, your license must include the **SOFTWARE\_TRANSCODE\_CALLS** feature.

### How It Works

When a call requires transcoding between different audio codecs, the system:

1. Detects the need for transcoding based on incompatible codecs between endpoints
2. Checks if software transcoding is enabled and supported for the required codecs
3. Automatically routes the call through the software transcoding path when available
4. Processes the audio stream in real-time to ensure seamless communication

The system intelligently determines the optimal transcoding method based on your configuration and the specific codecs involved in each call.

### Benefits

* **Flexibility**: Provides an alternative transcoding method without relying solely on hardware resources
* **Automatic Optimisation**: System automatically selects the best transcoding approach for each call
* **Resource Management**: Helps balance processing load across available system resources

### Configuration

Please note that Software Transcoding is supported in Toolpack release 3.3 onwards.

Software Transcoding must be enabled through the Web Portal interface. When both software and hardware transcoding options are available and configured, the system will automatically prioritise software transcoding when appropriate.

To configure, go to "Profile" settings, choose "Software audio transcoding" and push it to the "Current" box. Please note that you can apply different "Profiles" per NAP.

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2Fd3tp843S4OfnHUh4sP8t%2Fimage.png?alt=media&amp;token=ef44ebc2-d382-4a4c-b07c-e8c4dac1249e" alt="ProSBC Profiles page with Software audio transcoding set as the current Audio Transcoding Type and hardware transcoding available."><figcaption></figcaption></figure>


# SIP Trunking

A SIP trunk delivers the service of traditional phone lines as a virtual line from a SIP trunk provider. See how ProSBC secures and adapts that trunk.

### SIP Trunking

A SIP Trunk provides the same service you get from a traditional phone lines. The difference is, instead of being a physical wire, a SIP Trunk is a “virtual” line which is provided by a SIP trunk provider delivered over IP using the SIP protocol.

### Benefits of SIP Trunking

* Lower circuit costs
* Lower PSTN origination/termination fees
* Better customer service
* Move offices and keep the same number
* Flexibility
* Scalability
* Reliability

### Typical SIP Trunking Sample

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2Fp6xLkRDNXGbZEbSuHckR%2Fimage.png?alt=media&#x26;token=304fba5c-d3b8-4b90-a94f-fc46e4330589" alt="SIP trunking topology: ProSBC sits between the ITSP network and the enterprise LAN carrying the IP-PBX, desk phones and fax server."><figcaption></figcaption></figure>

### Features of the ProSBC

* Back-to-back user agent (B2BUA)
* DOS/DDOS protection, dynamic blacklisting, and call access control
* Easy to deploy, operate and manage through various interfaces including a RESTful API
* Integrated network troubleshooting tools (traces, media/signaling recording, test call generation, etc)
* Up to 60,000 simultaneous signaling and media sessions
* Media transcoding
* Flexible and extensive routing with SIP headers modification capabilities
* Fit to install on virtual machines, clouds, bare-metal servers, or TelcoBriges' hardware.

### Configuration

* [SIP Trunking Configuration Instruction](/configuration-details/configuration-by-use-case/sip-trunking-configuration)
* SIP Trunking Sample Configuration File
* SIP Trunk with Registration

### Troubleshooting

<table><thead><tr><th width="200">Call Trace</th><th width="200">Test Call</th><th width="200">TBReport</th><th width="200">Advanced Troubleshooting of ProSBC</th></tr></thead><tbody><tr><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace">Configure call trace</a></li><li>Retrieve call trace</li></ul></td><td><ul><li>Creating a Test Call</li></ul></td><td><ul><li>Capture a report of the system</li></ul></td><td><ul><li>Advanced Troubleshooting of ProSBC</li></ul></td></tr></tbody></table>

### References

* ProSBC Datasheet
* [Wikipedia SIP Trunking](https://en.wikipedia.org/wiki/SIP_trunking)


# Hosted PBX

Hosted PBX, also called virtual PBX, is a phone system built and managed by a third-party provider. See how ProSBC sits in front of a hosted PBX service.

### Hosted PBX

Hosted private branch exchange (hosted PBX) is a telephone exchange system built, delivered and managed by a third-party service provider. It’s also known as a Virtual PBX and this technology provides small, medium-sized, and enterprise organizations with a sophisticated telephone system, while minimizing equipment costs.

### Benefits of Hosted PBX

* Initial and Ongoing cost savings
* Eliminate office boundaries
* Geographical Flexibility
* Local Presence
* Scalability
* Quick Setup
* Easy to use

### Typical Hosted PBX Sample

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2F89qQgEr62ivhP4BREh4m%2Fimage.png?alt=media&#x26;token=2c5b78dd-dc3f-49ca-bc3a-010b437b2e10" alt="Hosted PBX topology: ProSBC fronts the service provider&#x27;s hosted IP PBX and connects it to the enterprise LAN phones."><figcaption></figcaption></figure>

### Configuration

* Hosted PBX Configuration Instruction

### Troubleshooting

<table><thead><tr><th width="200">Call Trace</th><th width="200">Test Call</th><th width="200">TBReport</th><th width="200">Advanced Troubleshooting of ProSBC</th></tr></thead><tbody><tr><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace">Configure call trace</a></li><li>Retrieve call trace</li></ul></td><td><ul><li>Creating a Test Call</li></ul></td><td><ul><li>Capture a report of the system</li></ul></td><td><ul><li>Advanced Troubleshooting of ProSBC</li></ul></td></tr></tbody></table>

<br>

### References

* ProSBC Datasheet
* [Wikipedia Hosted PBX](https://en.wikipedia.org/wiki/VirtualPBX)


# SIP Network Peering

Use ProSBC for SIP network peering and IP carrier interconnection, with high session density, media transcoding, security gating and SIP adaptation.

### SIP Network Peering / IP Carrier Interconnection

VoIP Carriers can trust ProSBC products to provide an efficient and safe SIP interconnection interface to other IP carriers over dedicated networks or over the Internet. Our solutions offer high session density, integrated media transcoding with a wide range of vocoders, security gating to filter out undesired traffic, and flexible SIP protocol adaptation capabilities all within a cost-effective package. As demands on carrier networks continue to expand, our technology and support offerings are rapidly becoming the solution of choice for tier-1 carriers who require carrier grade equipment with high performance, but with a more reasonable CAPEX and OPEX outlay than what is currently found in today’s market.

### Typical SIP Network Peering / IP Carrier Interconnection Sample

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FR6yVTX5hbDFGsVwav13Q%2Fimage.png?alt=media&amp;token=9f74943a-1fe2-4deb-a40f-16e4c9238da2" alt="SIP peering topology: two ITSP networks interconnect through a ProSBC at each side of the peering link."><figcaption></figcaption></figure>

### Features of the ProSBC

* Back-to-back user agent (B2BUA)
* DOS/DDOS protection, dynamic blacklisting, and call access control
* Easy to deploy, operate and manage through various interfaces including a RESTful API
* Integrated network troubleshooting tools (traces, media/signaling recording, test call generation, etc)
* Up to 60,000 simultaneous signaling and media sessions
* Media transcoding
* Flexible and extensive routing with SIP headers modification capabilities
* Fit to install on virtual machines, clouds, bare-metal servers, or TelcoBriges' hardware.
* Call Detail records and remote monitoring

### Configuration

* [SIP Network Peering / IP Carrier Interconnection Configuration Instruction](/configuration-details/configuration-by-use-case/sip-network-peering-ip-carrier-interconnection)

### Troubleshooting

<table><thead><tr><th width="200">Call Trace</th><th width="200">Test Call</th><th width="200">TBReport</th><th width="200">Advanced Troubleshooting of ProSBC</th></tr></thead><tbody><tr><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace">Configure call trace</a></li><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace/retrieving-call-trace">Retrieve call trace</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/creating-a-test-call">Creating a Test Call</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/tbreport">Capture a report of the system</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-common-problems">Advanced Troubleshooting of ProSBC</a></li></ul></td></tr></tbody></table>

<br>

### References

* [ProSBC Datasheet](/appendices/appendix-b-product-datasheets)


# Remote Workers

Give remote employees the full features of a premise-based PBX. ProSBC adds mobility so staff can work anywhere without losing office phone functionality.

### Remote Office/Workers

Normally, companies that have premise-based PBX's have little to no features they can offer to their remote employees. By adding a ProSBC to your network, you can have a mobility feature that allows your employees the flexibility to work when and where they want without losing the functionality of their office phone system.

### Typical Remote Workers Sample

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2Fyy1IipmBFTxwA9dmk2tu%2Fimage.png?alt=media&amp;token=49d05731-8c43-4dde-abc8-bb663243aef6" alt="Remote worker topology: home and remote-office phones reach the enterprise IP-PBX at 192.168.1.10 across the internet through ProSBC."><figcaption></figcaption></figure>

### Features of the ProSBC

* Back-to-back user agent (B2BUA)
* DOS/DDOS protection, dynamic blacklisting, and call access control
* Easy to deploy, operate and manage through various interfaces including a RESTful API
* Integrated network troubleshooting tools (traces, media/signaling recording, test call generation, etc)
* Up to 60,000 simultaneous signaling and media sessions
* Media transcoding
* Flexible and extensive routing with SIP headers modification capabilities
* Fit to install on virtual machines, clouds, bare-metal servers, or TelcoBriges' hardware.

### Configuration

* [Remote Workers Configuration Instruction](/configuration-details/configuration-by-use-case/remote-workers)
* [Remote Workers Sample Configuration File](/configuration-details/configuration-by-use-case/remote-workers/configuration-files-for-remote-office-workers)

### Troubleshooting

<table><thead><tr><th width="200">Call Trace</th><th width="200">Test Call</th><th width="200">TBReport</th><th width="200">Advanced Troubleshooting of ProSBC</th></tr></thead><tbody><tr><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace">Configure call trace</a></li><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace/retrieving-call-trace">Retrieve call trace</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/creating-a-test-call">Creating a Test Call</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/tbreport">Capture a report of the system</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-common-problems">Advanced Troubleshooting of ProSBC</a></li></ul></td></tr></tbody></table>

### References

* [ProSBC Datasheet](/appendices/appendix-b-product-datasheets)


# Local Site Survivability

Keep local extensions calling each other when a hosted PBX or cloud softswitch becomes unreachable. ProSBC answers already-registered phones from its own contact cache until the softswitch returns.

### Local Site Survivability

Phones and softphones register with a softswitch so they can be reached and can place calls. That softswitch is often not something the customer controls: it may sit at a hosted PBX provider, a cloud communications platform, or a carrier core, reachable only over a link the customer does not own either.

When that softswitch becomes unreachable, what users actually experience is not "a link went down" — registered phones lose their registration and can no longer call each other, even for a call between two desks in the same office, despite nothing on the premises having failed.

Local Site Survivability keeps those already-registered endpoints working. ProSBC recognizes the outage on its own, answers known phones from the registration record it already maintains, and hands control back to the softswitch as soon as it is reachable again — with no manual failover and no second system to maintain on site.

{% hint style="info" %}
Local Site Survivability is a different layer of protection than **SBC redundancy**: redundancy protects against the SBC itself failing, while Local Site Survivability protects against losing the softswitch connection while the SBC keeps running.
{% endhint %}

Throughout this page, *registrar* means the registrar role specifically, because that is the role ProSBC substitutes for. In a typical deployment that role belongs to a softswitch that also handles call routing.

### Typical Local Site Survivability Sample

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FQZf7iKbNDAd1D16TmltA%2FSIP_Registration.png?alt=media&amp;token=532795dd-56b2-4835-9365-7dae4d96d9b5" alt=""><figcaption></figcaption></figure>

### Key Capabilities

* **Local calls keep running** — a call between two locally known users is not dropped when the outage happens.
* **Known users can still call each other** — registered users keep placing and receiving calls between themselves during the outage.
* **Fully automatic** — ProSBC detects both the outage and the recovery on its own; no operator action, no manual failover.
* **One setting to turn on** — a single parameter on the SIP registration domain, with no separate system to maintain.

### How It Works

ProSBC keeps a local copy of every contact registered through a SIP registration domain, whether or not Local Site Survivability is enabled, and it tracks the registrar's reachability continuously. Nothing has to be built when an outage starts.

Local Site Survivability changes what ProSBC does with that record once the registrar stops answering:

| Event during the outage                                                  | Behavior with Local Site Survivability        |
| ------------------------------------------------------------------------ | --------------------------------------------- |
| Refresh from an already-registered contact                               | Answered locally with `200 OK`, not forwarded |
| Call between two locally registered users                                | Connected normally                            |
| Call in progress when the outage begins                                  | Continues normally until it ends              |
| REGISTER from an unknown user, or a contact whose listening port changed | Rejected with `480 Temporarily Unavailable`   |
| Unregister from a known contact                                          | Honored locally, cache entry removed          |
| Call that needs the softswitch (off-site number, softswitch features)    | Not available until the softswitch returns    |

#### Registration caching and throttling

The local contact copy is also what makes registration throttling possible. **Maximum Contact Expiration** caps the `Expires` value granted to the user agent, **Minimum Registrar Expiration** sets the floor on the `Expires` value asked of the registrar, and the two are configured independently — so endpoints can refresh far more often than the registrar ever sees.

User agents do not wait for the grant to run out before refreshing; most refresh well ahead of it, commonly at about half. ProSBC does not wait either: it re-registers toward the registrar once 40% of the `Expires` it was granted has elapsed. With the recommended values — Maximum Contact Expiration at 60 seconds and Minimum Registrar Expiration at 1 hour — the phone refreshes roughly every 30 seconds while the registrar sees one registration roughly every 24 minutes:

```
      Phone                    ProSBC                  Registrar
        |                         |                         |
 00:00  |==== REGISTER ==========>|==== REGISTER ==========>|
        |<========= 200 OK =======|<========= 200 OK =======|
        |     Expires: 60 s       |    Expires: 3600 s      |
        |                         |                         |
 00:30  |---- REGISTER ---------->|                         |  refresh at half the
        |<--------- 200 OK -------|                         |  granted 60 s
 01:00  |---- REGISTER ---------->|                         |
        |<--------- 200 OK -------|                         |  answered from cache
 01:30  |---- REGISTER ---------->|                         |  (not forwarded)
        |<--------- 200 OK -------|                         |
        |             :           |             :           |
        |    (repeats every 30 s) |                         |
        |             :           |             :           |
 24:00  |==== REGISTER ==========>|==== REGISTER ==========>|  40% of the granted
        |<========= 200 OK =======|<========= 200 OK =======|  3600 s has elapsed,
        |                         |                         |  so this one goes on
```

The forward rides a phone refresh. ProSBC does not re-register on a timer of its own, so the registrar side is renewed by whichever refresh happens to arrive once that 40% threshold has passed.

#### The outage lifecycle

From normal forwarding through an outage and back:

```
     Phones                             ProSBC                          Registrar
        |                                  |                                  |
        |                                  |------------ OPTIONS ------------>|
        |                                  |<----------- 200 OK --------------|
        |                                  |                                  |
 User A |-- REGISTER (UserA@example.com)-->|-- REGISTER (UserA@example.com)-->|
        |<--------- 200 OK ----------------|<--------- 200 OK ----------------|
 User B |-- REGISTER (UserB@example.com)-->|-- REGISTER (UserB@example.com)-->|
        |<--------- 200 OK ----------------|<--------- 200 OK ----------------|
        |                                  |                                  |
        |                                  |------------ OPTIONS ------------>|  no response
        |                                  |             :                    |  registrar marked
        |                                  |------------ OPTIONS ------------>|  down, domain
        |                                  |                                  |  enters Survivability
        |                                  |                                  |
 User A |-- REGISTER (UserA@example.com)-->|                                  |
        |<--------- 200 OK ----------------|                                  |  answered from cache,
 User B |-- REGISTER (UserB@example.com)-->|                                  |  not forwarded
        |<--------- 200 OK ----------------|                                  |
 User C |-- REGISTER (UserC@example.com)-->|                                  |
        |<------- 480 Unavailable ---------|                                  |  not in the cache,
        |                                  |                                  |  so rejected
        |                                  |                                  |
        |                                  |------------ OPTIONS ------------>|
        |                                  |<----------- 200 OK --------------|  registrar back up,
        |                                  |                                  |  domain returns to Up
        |                                  |                                  |
 User A |-- REGISTER (UserA@example.com)-->|-- REGISTER (UserA@example.com)-->|  on their own next
        |<--------- 200 OK ----------------|<--------- 200 OK ----------------|  refresh, not pushed
 User B |-- REGISTER (UserB@example.com)-->|-- REGISTER (UserB@example.com)-->|  by ProSBC
        |<--------- 200 OK ----------------|<--------- 200 OK ----------------|
        |                                  |                                  |
```

The diagram shows OPTIONS doing the detecting, which is the clearest case. On a domain with steady refresh traffic the poll is suppressed and a stalled REGISTER detects the outage instead, as described under [Timing](#timing).

#### Outage detection

ProSBC considers a registrar down when it stops answering the requests sent to it, whether the request is a SIP OPTIONS poll or a REGISTER that ProSBC is forwarding.

A REGISTER answered with a 5xx by a reachable registrar is still a response, so it does not itself trigger survivability. A REGISTER that gets no response at all can contribute to the same down-detection timer a poll would.

#### While the registrar is unreachable

* A refresh from an already-cached contact is answered locally with `200 OK` and not forwarded.
* A REGISTER from an unknown user, a new registration dialog, or a contact whose listening port changed is rejected with `480 Temporarily Unavailable`.
* An unregister for a cached contact is honored locally and removes that cache entry.
* A REGISTER that is forwarded but goes unanswered does not evict the cached binding; the endpoint's normal retry still succeeds from cache.
* New calls placed between two locally cached contacts continue to work normally. A new call that needs the registrar's softswitch itself — a number outside the site, or a softswitch feature such as voicemail, conferencing or transfer — does not.

#### New calls during an outage

Caching a registration is necessary to reach a survived contact, but not sufficient: the call route still has to resolve its destination from the registered-user data, which is a routing decision rather than something Local Site Survivability does on its own.

In a static-route configuration, set the call route's destination NAP to **(By registered or DNS user)** and the shipped base routing builds one route per cached contact. No custom script is needed. This is normally already in place, because it is the same setting that makes registered-user calling work while the registrar is up.

#### Recovery

Once the registrar answers again, normal forwarding resumes automatically.

{% hint style="info" %}
ProSBC does not push or resync cached registrations to the registrar on recovery. The registrar only learns about a contact again when that endpoint's own next natural REGISTER refresh reaches it, so until each contact's refresh interval elapses, the registrar's view of who is registered can lag behind ProSBC's cache.
{% endhint %}

### Timing

#### Detecting the outage

**Proxy Polling Interval** on the registrar's NAP (default: 1 minute) is how often ProSBC polls the registrar with SIP OPTIONS while otherwise idle. It is configurable over a wide range, so tune it to the deployment rather than relying on a fixed detection time. See [SIP NAP Polling](/configuration-details/configuration-by-web-portal-category/network-access-points-nap/sip-nap-polling).

The polling interval is not the whole story on a busy domain. ProSBC only sends a poll when it has not recently sent the registrar a request of any kind, so a domain with frequent REGISTER forwarding suppresses the poll and detection is then driven by whichever request stalls first — in practice a REGISTER. In that case detection follows the endpoints' refresh cadence, not the polling interval.

#### Repopulating the registrar after recovery

Because nothing resyncs on recovery, the registrar only learns about a surviving contact again when that endpoint's own next REGISTER refresh is forwarded. The gap between recovery and a correct registrar view is one endpoint refresh interval. Since user agents typically refresh at around half the granted `Expires` value, that interval is a fraction of what is configured — but the user-side registration time is still the parameter that sets it.

This is why the configuration steps shorten the register values from their 1-hour defaults. **Maximum Contact Expiration** caps the `Expires` value granted to the user agent, so it bounds how often the phones refresh and therefore decides how quickly the recovered registrar is repopulated. At 60 seconds, surviving users register anew within seconds of the registrar coming back instead of waiting out a long registration.

The cost of a short value falls on REGISTER traffic between the phones and ProSBC, not between ProSBC and the registrar. Registration throttling forwards a refresh only when the contact is new, has changed, is not yet active, or has passed 40% of the `Expires` the registrar granted, so the registrar side stays paced by **Minimum Registrar Expiration** rather than by the phones.

{% hint style="info" %}
That throttling is only active while **Minimum Contact Expiration** is lower than **Minimum Registrar Expiration**. If it is not, every refresh is forwarded, and shortening the user-side value does reach the registrar. The recommended values — 30 seconds against 1 hour — satisfy this.
{% endhint %}

On a site with many cached endpoints, also review the domain's **Maximum Pending Register Forward** and **Maximum Simultaneous Register Forward** settings: they govern how fast the backlog of REGISTER refreshes reaches the registrar after it comes back up, so reconnection is not needlessly slow.

### Requirements

* A **license** including the *Local Site Survivability* feature. Without it the configuration still saves, but the effective mode is forced to Disabled and the web portal raises a non-blocking warning.
* **Poll Remote Proxy** enabled on the registrar's NAP. This is mandatory — the feature relies on the registrar's up/down state, which is only maintained while the NAP polls the remote proxy.
* The matching call route's destination NAP set to **(By registered or DNS user)**, so calls between survived contacts can still be routed.

Saving a domain with Local Site Survivability enabled while its registrar NAP(s) do not have Poll Remote Proxy enabled fails with:

```
Sip registration domain update failed: Local survivability mode requires
'Poll Remote Proxy' to be enabled on registrar NAP(s)
```

### Configuration

See [Local Site Survivability Configuration Instruction](/configuration-details/configuration-by-use-case/local-site-survivability) for the configuration steps and troubleshooting.

### Routing scripts consideration

Routing scripts that resolve destinations themselves read the same registered-user data as the static routes: `params[:registered_user]` for the called party and `params[:calling_registered_user]` for the calling party, each exposing the contact's host, port and transport, the Contact URI, and which Routing Method is configured. See [Accessing Information about Registered Users](/configuration-details/configuration-by-web-portal-category/routing-scripts/development-guides-and-tutorials/accessing-information-about-registered-users).

That same data source is what Local Site Survivability populates from its cache when the registrar is unreachable, so a routing script already built to resolve destinations from `params[:registered_user]` per that documented pattern keeps working unchanged during an outage.

A script that resolves destinations some other way — by querying the registrar directly, for instance — will not complete a new call during the outage. Confirm which pattern a deployment's script actually uses.

### Limitations

* **No authentication in cached mode.** A previously registered contact is trusted without re-validating credentials.
* **No alias matching.** Matching is by registered Contact/AOR only — no extension numbers, DIDs, or alternate SIP usernames.
* **Cache is not persistent across a restart.** A restart while the registrar is still unreachable clears the cache; previously known users are rejected until the registrar recovers.
* **Not synchronized across an HA 1+1 pair.** Local Site Survivability runs independently on each host; the cache one host builds is not shared or replicated to the other. A failover to the standby host starts with an empty cache.
* **No resync on recovery.** ProSBC does not push cached registrations back to the registrar; the registrar's view catches up as each endpoint's own refresh is forwarded.
* **Down-detection is not limited to OPTIONS polling.** A stalled forwarded REGISTER can drive it too.

### Related Use Cases

* [Hosted PBX](/use-cases/applications/hosted-pbx)
* [Remote Workers](/use-cases/applications/remote-workers)
* [SIP Trunking](/use-cases/applications/sip-trunking)

### References

* [ProSBC Datasheet](/appendices/appendix-b-product-datasheets)
* [SIP Registration](/appendices/appendix-a-glossary/glossary-sip/glossary-sip-registration)


# Interoperability Examples

Configuration manuals for ProSBC interoperability with 3CX, Asterisk, FreePBX, Cisco UCM, Avaya IP Office, Skype for Business, Twilio, VoIP.ms and more.

The following is a list of configuration manuals for ProSBC use cases:

* [ProSBC Configuration for SIP Trunking](/use-cases/applications/sip-trunking)
* [ProSBC Configuration for Hosted PBX](/use-cases/applications/hosted-pbx)
* [ProSBC Multiple Domains/PBXs scenario](/configuration-details/configuration-by-use-case/multiple-domains-hosted-pbxs)
* [ProSBC Configuration for SIP Network Peering / IP Carrier Interconnection](/use-cases/applications/sip-network-peering)
* [ProSBC Configuration for Remote Workers](/use-cases/applications/remote-workers)
* [ProSBC Configuration for Transnexus and ClearIP Solutions](/use-cases/interoperability-examples/stir-shaken-with-transnexus-and-clearip)
* [ProSBC Configuration for YouMail fraud detection](/use-cases/interoperability-examples/fraud-detection-youmail)
* [ProSBC Configuration for Microsoft Skype Connect](/use-cases/interoperability-examples/skype-connect)
* [ProSBC Configuration for Microsoft Skype for Business (S4B) with TCP](/use-cases/interoperability-examples/skype-for-business-s4b-tcp)
* [ProSBC Configuration for Microsoft Skype for Business (S4B) with TLS](/use-cases/interoperability-examples/skype-for-business-s4b-tls)
* [ProSBC Configuration for Asterisk Server](/use-cases/interoperability-examples/asterisk)
* [ProSBC Configuration for 3CX Server](/use-cases/interoperability-examples/3cx)
* [ProSBC Configuration for FreePBX](/use-cases/interoperability-examples/freepbx)
* [ProSBC Configuration for FusionPBX](/use-cases/interoperability-examples/fusionpbx)
* [ProSBC Configuration for FreeSwitch](/use-cases/interoperability-examples/freeswitch)
* [ProSBC Configuration for Twilio Elastic SIP Trunking](/use-cases/interoperability-examples/twilio)
* [ProSBC Configuration for Sippy](/use-cases/interoperability-examples/sippy)
* [ProSBC Configuration for Avaya IP Office](/use-cases/interoperability-examples/avaya-ip-office)
* [ProSBC Configuration for Cisco UCM 12](/use-cases/interoperability-examples/cisco-ucm-12)
* [ProSBC Configuration for Brekeke PBX](/use-cases/interoperability-examples/brekeke-pbx)
* [ProSBC Configuration for VitalPBX](/use-cases/interoperability-examples/vitalpbx)
* [ProSBC Configuration for Yeastar P-Series Cloud Edition](/use-cases/interoperability-examples/yeastar-p-series-cloud)
* [ProSBC Configuration for VoIP.ms](/use-cases/interoperability-examples/voip.ms)
* [ProSBC Configuration for Wildix](/use-cases/interoperability-examples/wildix)

### Basic Configuration

You can follow that page for the basic configuration, that applies to many different Use Cases: [Basic Configuration](/initial-installation/2.-initial-configuration/basic-configuration)

### Related actions

Link to [video libraries](/tools-tips-and-tricks/video-library) that explains some of these Use Cases


# STIR/SHAKEN with Transnexus and ClearIP

TransNexus and ClearIP with ProSBC for STIR/SHAKEN, least cost routing, toll fraud control, and TDoS and robocall prevention.

TransNexus is a leader in providing telecom software for least-cost routing, Toll Fraud Control, TDoS and Robocalling Prevention. Transnexus is partnered with solution providers and interop technology vendors, including TelcoBridges, to deploy solutions that manage and protect telecom service provider networks. An authorized SHAKEN vendor by the Policy Administrator, Transnexus is a Certificate Authority and provides Key Management and Authentication/Verification services

The following is a list of the solutions of TelcoBridges ProSBC/TMG with Transnexus, which have proven successful in the field :

* [ProSBC Configuration for STIR/SHAKEN](/configuration-details/configuration-by-use-case/prosbc-and-clearip-transnexus/configuration-for-stir-shaken-with-transnexus-clearip-service)
* [ProSBC Configuration for CNAM lookup](/configuration-details/configuration-by-use-case/prosbc-and-clearip-transnexus/configuration-for-cnam-verification-and-robocall-analytics-with-transnexus-clearip-service)
* [ProSBC Configuration for Robocall Mitigation](/configuration-details/configuration-by-use-case/prosbc-and-clearip-transnexus/configuration-for-robocall-mitigation-with-transnexus-clearip-service)
* [ProSBC Configuration for ClearIP LCR routing](/configuration-details/configuration-by-use-case/prosbc-and-clearip-transnexus/configuration-for-302-redirect-routing-with-transnexus-clearip-service)
* [ProSBC Configuration for CAPTCHA Authentication](/configuration-details/configuration-by-use-case/prosbc-and-clearip-transnexus/configuration-for-captcha-authentication-302-redirect-with-transnexus-clearip-service)
* [ProSBC Configuration for STIR/SHAKEN (Legacy Method)](/configuration-details/configuration-by-use-case/prosbc-and-clearip-transnexus/configuration-for-stir-shaken-with-transnexus-clearip-service-1)

### Related actions

[Link to video libraries](/tools-tips-and-tricks/video-library) that explains some of these Use Cases.


# Fraud Detection \[YouMail]

Add YouMail fraud protection to ProSBC. Calls trigger an HTTPS lookup of the calling number, returning level 0 valid, 1 spam or 2 fraud for call routing.

## Introduction

This configuration note describes how to set up Telcobridges ProSBC for adding YouMail fraud protection service to any system.

### Prerequisites

* ProSBC devices must be installed with release 3.1.113 or later. Here is a link to the installation guides.
* Need to have an account at [YouMail](https://www.youmail.com/) to get a Security ID (SID) and an API key. Trial accounts are available.
* ProSBC must be configured in one of the [ProSBC Use Cases](/use-cases/interoperability-examples). This script will be an addon to the rest of the configuration.

<br>

### Example Environment for Fraud Protection with YouMail

Calls received on ProSBC will systematically send a HTTPS request to the YouMail service running on the cloud.\
The calling number (ANI) will be verified by the YouMail service and will return a response to the ProSBC with a level.\
Call Routes can be configured to pass valid numbers (level 0), pass or block potential spam numbers (level 1), and block fraudulous calls (level 2)

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2F5aoInAKVYAdgqk8STMNK%2Fimage.png?alt=media&amp;token=bc5b8caf-6e3a-4455-a507-ace8250eee9e" alt="An incoming SIP call triggers an HTTPS lookup of the calling number to YouMail; level 0 continues the call while level 2 returns 603 Decline to the caller."><figcaption></figcaption></figure>

### Example Configuration

The configuration is mainly adding a script to the ProSBC. See [Adding the YouMail Script](/configuration-details/configuration-by-use-case/configuration-for-adding-youmail-script-to-routing-scripts)

### Troubleshooting

<table><thead><tr><th width="200">Call Trace</th><th width="200">Test Call</th><th width="200">TBReport</th><th width="200">Advanced Troubleshooting of FreeSBC</th></tr></thead><tbody><tr><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace">Configure call trace</a></li><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace/retrieving-call-trace">Retrieve call trace</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/creating-a-test-call">Creating a Test Call</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/tbreport">Capture a report of the system</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-common-problems">Advanced Troubleshooting of ProSBC</a></li></ul></td></tr></tbody></table>

### Video guide

We also have a video guide if you prefer: [Youmail configuration video](https://youtu.be/_7Egw3nd6nwtraining)


# Skype Connect

Connect your IP-PBX to the Skype community with Skype Connect and ProSBC, including Click and Call, for low-cost VoIP calls from existing desk phones.

## Introduction

Skype Connect provides connectivity between your business and the Skype community. By adding Skype Connect to your existing SIP-enabled PBX, your business can save on communication costs with little or no additional upgrades required.

With Skype Connect, your business can make great value Skype calls and receive calls from your customers using your desk phones. Customers using Skype can call your company’s Skype number with just a click of a button – using the Click & Call feature – making your company easier to reach.

ProSBC is capable to connect your IP-PBX to Skype for low-cost VoIP calls using Skype Connect. This is a simple how-to connecting ProSBC to Skype.

### Prerequisites

* ProSBC devices must be installed as described in their respective installation guides.
* Skype Connect Account

### Typical Skype Connect Sample

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FeLRqSvXNiSK3X6pKZUUM%2Fimage.png?alt=media&amp;token=1c486c15-e516-4994-baf6-759e2e97cbbb" alt="Skype Connect topology: Skype clients, an online number and Click to call reach the Skype cloud, which links through Skype Connect and ProSBC to the enterprise IP-PBX and LAN."><figcaption></figcaption></figure>

<br>

**SKYPE CONNECT CONFIGURATION**

| <p>(Step 1)<br>Create IP Network</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | <p>(Step 2)<br>Create Protocol Stack</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | <p>(Step 3)<br>Create Call Route</p>                                                                                                                           |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <ul><li><a href="/configuration-details/configuration-by-use-case/rtp-no-anchoring/parameter-allow-low-delay-media-relay/configuring-an-ip-port-range">Configuring an IP Virtual Port</a></li><li><a href="/configuration-details/configuration-by-web-portal-category/ip-network-settings/configuring-a-vlan">Configuring a VLAN</a></li><li><a href="/configuration-details/configuration-by-web-portal-category/ip-network-settings/configuring-ip-interfaces">Configuring IP Interfaces</a></li><li><a href="/configuration-details/configuration-by-use-case/rtp-no-anchoring/parameter-allow-low-delay-media-relay/configuring-an-ip-port-range">Create an IP port range</a></li></ul> | <ul><li><a href="/configuration-details/configuration-by-use-case/rtp-no-anchoring/parameter-allow-low-delay-media-relay/configuring-an-ip-port-range">Create an IP port range</a></li><li><a href="/configuration-details/configuration-by-web-portal-category/sip/creating-a-sip-stack">Create a SIP stack</a></li><li><a href="/configuration-details/configuration-by-web-portal-category/sip/creating-a-sip-transport-server">Create a SIP transport server</a></li><li><a href="/configuration-details/configuration-by-use-case/rtp-no-anchoring/creating-profiles">Modify profile</a></li><li><a href="/configuration-details/configuration-by-web-portal-category/network-access-points-nap">Allocate a SIP NAP</a></li><li><a href="/configuration-details/configuration-by-web-portal-category/network-access-points-nap/allocating-a-sip-open-network-access-point-nap">Allocate an open SIP NAP</a></li></ul> | <ul><li><a href="/configuration-details/configuration-by-web-portal-category/call-routing/creating-a-first-call-route">Create a first call route</a></li></ul> |

### Example Configuration

Step by step example Skype Connect with ProSBC configuration.

* [Skype Connect Example Configuration](/configuration-details/configuration-by-use-case/skype-connect-example-configuration)

### Troubleshooting

<table><thead><tr><th width="200">Call Trace</th><th width="200">Test Call</th><th width="200">TBReport</th><th width="200">Advanced Troubleshooting of ProSBC</th></tr></thead><tbody><tr><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace">Configure call trace</a></li><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace/retrieving-call-trace">Retrieve call trace</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/creating-a-test-call">Creating a Test Call</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/tbreport">Capture a report of the system</a></li></ul></td><td><ul><li><a href="https://docs.telcobridges.com/wiki/FreeSBC_Troubleshooting">Advanced Troubleshooting of ProSBC</a></li></ul></td></tr></tbody></table>


# Skype for Business S4B TCP

Set up ProSBC between an ITSP SIP trunk and a Skype for Business 2015 Mediation Server over a TCP connection. Requires ProSBC release 3.1.x.

## Introduction

This article describes how to set up a Telcobridges ProSBC for interworking between an ITSP’s SIP Trunk and a Skype For Business Mediation Server using a TCP connection.

NOTE: The SIP Trunk uses G.711 in this test. There is no transcoding available.

### Prerequisites

* ProSBC devices must be installed as described in release 3.1.x. Release 3.0.x is not supported for TCP connections installation guides.
* Skype for Business 2015. For additional information on Skype for Business 2015, visit [Microsoft](http://www.microsoft.com/)

### Example Environment

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FHmICHmCjlQXrpFlpo3Jm%2Fimage.png?alt=media&amp;token=2234049b-d917-40cc-aead-7fb354b60f36" alt="A SIP trunk from the PSTN crosses the internet to the enterprise firewall, where ProSBC serves Skype for Business users alongside the AD and Front End servers on the LAN."><figcaption></figcaption></figure>

**ProSBC Configuration for S4B**

| <p>(Step 1)<br>Create IP Network</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | <p>(Step 2)<br>Create Protocol Stack</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | <p>(Step 3)<br>Create Call Route</p>                                                                                                                           |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <ul><li><a href="/configuration-details/configuration-by-web-portal-category/ip-network-settings/configuring-a-virtual-port">Configuring an IP Virtual Port</a></li><li><a href="/configuration-details/configuration-by-web-portal-category/ip-network-settings/configuring-a-vlan">Configuring a VLAN</a></li><li><a href="/configuration-details/configuration-by-web-portal-category/ip-network-settings/configuring-ip-interfaces">Configuring IP Interfaces</a></li><li><a href="/configuration-details/configuration-by-use-case/rtp-no-anchoring/parameter-allow-low-delay-media-relay/configuring-an-ip-port-range">Create an IP port range</a></li></ul> | <ul><li><a href="/configuration-details/configuration-by-use-case/rtp-no-anchoring/parameter-allow-low-delay-media-relay/configuring-an-ip-port-range">Create an IP port range</a></li><li><a href="/configuration-details/configuration-by-web-portal-category/sip/creating-a-sip-stack">Create a SIP stack</a></li><li><a href="/configuration-details/configuration-by-web-portal-category/sip/creating-a-sip-transport-server">Create a SIP transport server</a></li><li><a href="/configuration-details/configuration-by-use-case/rtp-no-anchoring/creating-profiles">Modify profile</a></li><li><a href="/configuration-details/configuration-by-web-portal-category/network-access-points-nap">Allocate a SIP NAP</a></li><li><a href="/configuration-details/configuration-by-web-portal-category/network-access-points-nap/allocating-a-sip-open-network-access-point-nap">Allocate an open SIP NAP</a></li></ul> | <ul><li><a href="/configuration-details/configuration-by-web-portal-category/call-routing/creating-a-first-call-route">Create a first call route</a></li></ul> |

### Example Configuration

ProSBC SIP trunking configuration for Microsoft Skype for Business.

* [Skype for Business Example Configuration - TCP](/configuration-details/configuration-by-use-case/skype-for-business-example-configuration)

### Troubleshooting

<table><thead><tr><th width="200">Call Trace</th><th width="200">Test Call</th><th width="200">TBReport</th><th width="200">Advanced Troubleshooting of ProSBC</th></tr></thead><tbody><tr><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace">Configure call trace</a></li><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace/retrieving-call-trace">Retrieve call trace</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/creating-a-test-call">Creating a Test Call</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/tbreport">Capture a report of the system</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-common-problems">Advanced Troubleshooting of ProSBC</a></li></ul></td></tr></tbody></table>


# Skype for Business S4B TLS

Set up ProSBC between an ITSP SIP trunk and a Skype for Business 2015 Mediation Server over a TLS connection. Requires ProSBC release 3.1.129 or later.

## Introduction

This Configuration Note describes how to set up Telcobridges ProSBC for interworking between ITSP’s SIP Trunk and Skype For Business Mediation Server using a TLS connection.

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

### Prerequisites

* ProSBC devices must be installed as described in their respective with minimum release 3.1.129. Release 3.0.x is not supported for TLS connections installation guides.
* Skype for Business 2015. For additional information on Skype for Business 2015, visit [Microsoft](http://www.microsoft.com/)

### Example Environment

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FKkr6PVvElet5A4gq2Zdu%2Fimage.png?alt=media&amp;token=6eb35925-e8f2-40b0-b5d9-b5b3035e02b3" alt="Enterprise network layout for this deployment: a PSTN SIP trunk enters through the firewall to ProSBC, which serves Skype for Business users with the AD and Front End servers on the LAN."><figcaption></figcaption></figure>

**ProSBC Configuration for S4B**

| <p>(Step 1)<br>Create IP Network</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | <p>(Step 2)<br>Create Protocol Stack</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | <p>(Step 3)<br>Create Call Route</p>                                                                                                                           |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <ul><li><a href="/configuration-details/configuration-by-web-portal-category/ip-network-settings/configuring-a-virtual-port">Configuring an IP Virtual Port</a></li><li><a href="/configuration-details/configuration-by-web-portal-category/ip-network-settings/configuring-a-vlan">Configuring a VLAN</a></li><li><a href="/configuration-details/configuration-by-web-portal-category/ip-network-settings/configuring-ip-interfaces">Configuring IP Interfaces</a></li><li><a href="/configuration-details/configuration-by-use-case/rtp-no-anchoring/parameter-allow-low-delay-media-relay/configuring-an-ip-port-range">Create an IP port range</a></li></ul> | <ul><li><a href="/configuration-details/configuration-by-use-case/rtp-no-anchoring/parameter-allow-low-delay-media-relay/configuring-an-ip-port-range">Create an IP port range</a></li><li><a href="/configuration-details/configuration-by-web-portal-category/sip/creating-a-sip-stack">Create a SIP stack</a></li><li><a href="/configuration-details/configuration-by-web-portal-category">v3.1: TLS Configuration</a></li><li><a href="/configuration-details/configuration-by-web-portal-category/sip/creating-a-sip-transport-server">Create a SIP transport server</a></li><li><a href="/configuration-details/configuration-by-use-case/rtp-no-anchoring/creating-profiles">Modify profile</a></li><li><a href="/configuration-details/configuration-by-web-portal-category/network-access-points-nap">Allocate a SIP NAP</a></li><li><a href="/configuration-details/configuration-by-web-portal-category/network-access-points-nap/allocating-a-sip-open-network-access-point-nap">Allocate an open SIP NAP</a></li></ul> | <ul><li><a href="/configuration-details/configuration-by-web-portal-category/call-routing/creating-a-first-call-route">Create a first call route</a></li></ul> |

### Troubleshooting

<table><thead><tr><th width="200">Call Trace</th><th width="200">Test Call</th><th width="200">TBReport</th><th width="200">Advanced Troubleshooting of ProSBC</th></tr></thead><tbody><tr><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace">Configure call trace</a></li><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace/retrieving-call-trace">Retrieve call trace</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/creating-a-test-call">Creating a Test Call</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/tbreport">Capture a report of the system</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-common-problems">Advanced Troubleshooting of ProSBC</a></li></ul></td></tr></tbody></table>


# Asterisk

Set up ProSBC between an ITSP SIP trunk and an Asterisk server, for SIP trunking or remote client access. Sample extensions.conf and sip.conf included.

## Introduction

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

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

### Prerequisites

* 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 installation guides.
* Asterisk. For additional information on Asterisk, visit [Asterisk official web site](http://www.asterisk.org/).

### Example Environments for SIPTrunking with Asterisk

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FnxnluniyKQ0EQwCC8MI4%2Fimage.png?alt=media&amp;token=3a4c5a68-bf6e-4bd6-b690-7788ba50a2ed" alt="SIP trunking topology: an ITSP cloud connects through ProSBC to an enterprise LAN holding the IP-PBX and a fax server."><figcaption></figcaption></figure>

### Example Configuration

Step by step example SIP Trunk configuration.

* [SIP Trunking Example Configuration](/configuration-details/configuration-by-use-case/sip-trunking-configuration)

### Example Environments for Remote Workers with Asterisk

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FESm1i2lVBhPVTrXaZOfl%2Fimage.png?alt=media&amp;token=81c1bd5b-2757-4e1f-82e4-80b065e24329" alt="Remote workers topology: a remote office and two remote-worker phones cross the internet through ProSBC to the enterprise IP-PBX at 192.168.1.10."><figcaption></figcaption></figure>

### Example Configuration

Step by step example Remote workers configuration.

* [Remote Workers Configuration Instruction](/configuration-details/configuration-by-use-case/remote-workers)

### Asterisk Configuration Files

In this section, you can find basic configuration files for Asterisk PBX.

extensions.conf - The extensions.conf file is one of the most used and most important configuration file in Asterisk PBX - it contains the dialplan.

For more details about the extensions.conf please visit [Asterisk official website](https://wiki.asterisk.org/wiki/display/AST/Contexts%2C+Extensions%2C+and+Priorities/)

{% file src="/files/8eomEFlKeVCw8ic1dDn8" %}

sip.conf - The SIP channels in Asterisk are configured in the sip.conf file.

For more details about the sip.conf file please visit [Asterisk official website](https://wiki.asterisk.org/wiki/display/AST/Creating+SIP+Accounts/)

{% file src="/files/zCXwt8aLP919gzkEo1rg" %}

features.conf - The features.conf file is where you can adjust or define the various feature parameters in Asterisk.

For more details about features.conf file please visit [Asterisk official website](https://wiki.asterisk.org/wiki/display/AST/Asterisk+13+Configuration_features/)

{% file src="/files/HtpwPPoGdh3gXTznkacF" %}

### Troubleshooting

<table><thead><tr><th width="200">Call Trace</th><th width="200">Test Call</th><th width="200">TBReport</th><th width="200">Advanced Troubleshooting of ProSBC</th></tr></thead><tbody><tr><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace">Configure call trace</a></li><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace/retrieving-call-trace">Retrieve call trace</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/creating-a-test-call">Creating a Test Call</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/tbreport">Capture a report of the system</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-common-problems">Advanced Troubleshooting of ProSBC</a></li></ul></td></tr></tbody></table>


# 3CX

Set up ProSBC between an ITSP SIP trunk and a 3CX server, covering SIP trunking, remote client access, phone provisioning and T.38 fax.

## Introduction

This Configuration Instruction describes how to set up a Telcobridges ProSBC for interworking between an ITSP’s SIP Trunk or remote client access for 3CX server.

### Prerequisites

* 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 installation guides.
* 3CX.For additional information on 3CX, visit [3CX official web site](http://www.3cx.com/).

### Example Environments for SIPTrunking with 3CX

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FdtOeQinraQODAJ753BFM%2Fimage.png?alt=media&amp;token=195f9dac-5e2a-46b3-b711-d05b12922d40" alt="SIP trunking topology: an ITSP cloud connects through two ProSBCs in series to the 3CX server."><figcaption></figcaption></figure>

### Example Configuration

Step-by-step example SIP Trunk configuration.

* [Adding ProSBC as a SIP Trunk in 3CX Server](/configuration-details/configuration-by-use-case/3cx-phone-provisioning-configuration/configuration-for-3cx-pbx-server-with-the-prosbc-as-sip-trunk)
* [SIP Trunk Configuration Instruction with 3CX](/configuration-details/configuration-by-use-case/sip-trunking-configuration/sip-trunk-configuration-instruction-with-3cx)
* [T.38 Fax Configuration with 3CX](/configuration-details/configuration-by-use-case/3cx-phone-provisioning-configuration/configuration-for-3cx-pbx-server-with-the-prosbc-to-receive-t38-faxes)

### Example Environments for Remote Workers with 3CX

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FCr297Mq9GVVBlT6U5g7L%2Fimage.png?alt=media&amp;token=70e49aac-a934-445d-ad32-0d77861e9348" alt="Remote workers topology: a remote office and two remote-worker phones reach the 3CX server across the internet through a single ProSBC."><figcaption></figcaption></figure>

### Example Configuration

Step-by-step example Remote workers configuration.

* [3CX Phone Provisioning Settings](/configuration-details/configuration-by-use-case/3cx-phone-provisioning-configuration)
* [Remote Workers Configuration Instruction with 3CX](/configuration-details/configuration-by-use-case/remote-workers/remote-workers-configuration-instruction-with-3cx)

### Troubleshooting

<table><thead><tr><th width="200">Call Trace</th><th width="200">Test Call</th><th width="200">TBReport</th><th width="200">Advanced Troubleshooting of ProSBC</th></tr></thead><tbody><tr><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace">Configure call trace</a></li><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace/retrieving-call-trace">Retrieve call trace</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/creating-a-test-call">Creating a Test Call</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/tbreport">Capture a report of the system</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-common-problems">Advanced Troubleshooting of ProSBC</a></li><li><a href="https://docs.telcobridges.com/wiki/FreeSBC:3CX:CSTA_Calls_never_ends">CSTA calls never ends</a></li></ul></td></tr></tbody></table>


# FreePBX

Set up ProSBC between an ITSP SIP trunk and a FreePBX server, covering SIP trunk creation, extensions and remote worker access.

## Introduction

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

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

### Prerequisites

* 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 installation guides.
* FreePBX.For additional information on FreePBX, visit [FreePBX offical web site](https://www.freepbx.org/).

### Example Environments for SIP Trunking with FreePBX

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FZNJeiqxpOtSiC0voOfQi%2Fimage.png?alt=media&amp;token=7fad1f2f-baa7-4d25-9665-58380dc8e9ff" alt="SIP trunking topology: an ITSP cloud connects through two ProSBCs in series to the FreePBX server."><figcaption></figcaption></figure>

### Example Configuration

Step by step example SIP Trunk configuration.

* [FreePBX Trunk Creation](/configuration-details/configuration-by-use-case/sip-trunking-configuration/configuration-for-adding-prosbc-as-a-sip-trunk-in-the-freepbx-server)
* [SIP Trunking Example Configuration](/configuration-details/configuration-by-use-case/sip-trunking-configuration/sip-trunk-configuration-instruction-with-freepbx)

### Example Environments for Remote Workers with FreePBX

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2F3O1TJNMlt9H3DV744IpZ%2Fimage.png?alt=media&amp;token=c15000c1-327d-4501-af10-2bcec8defe20" alt="Remote workers topology: a remote office and two remote-worker phones reach the FreePBX server across the internet through a single ProSBC."><figcaption></figcaption></figure>

### Example Configuration

Step by step example Remote workers configuration.

* [FreePBX Extension Creation](/configuration-details/configuration-by-use-case/sip-trunking-configuration/freepbx-extension-creation)
* [Remote Workers Configuration Instruction with FreePBX](/configuration-details/configuration-by-use-case/remote-workers/remote-workers-configuration-instruction-with-freepbx)

### Troubleshooting

<table><thead><tr><th width="200">Call Trace</th><th width="200">Test Call</th><th width="200">TBReport</th><th width="200">Advanced Troubleshooting of ProSBC</th></tr></thead><tbody><tr><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace">Configure call trace</a></li><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace/retrieving-call-trace">Retrieve call trace</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/creating-a-test-call">Creating a Test Call</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/tbreport">Capture a report of the system</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-common-problems">Advanced Troubleshooting of ProSBC</a></li></ul></td></tr></tbody></table>


# FusionPBX

Set up ProSBC between an ITSP SIP trunk and a FusionPBX server, covering trunk creation, extensions and remote worker access.

## Introduction

This article describes how to set up a Telcobridges ProSBC for interworking between an ITSP’s SIP Trunk, or remote client access for a FusionPBX server.

NOTE: TheSIP Trunk uses G.711 in this test. There is no transcoding available.

### Prerequisites

* ProSBC devices must be installed as described with respect to release 3.0.x/3.1.x. Release 3.0.x is not supported for TCP connections installation guides.
* FusionPBX. For additional information about FusionPBX, visit [FusionPBX offical web site](https://www.fusionpbx.com/).

### Example Environments for SIP Trunking with FusionPBX

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FvYW8hPKFuhoxnwdLJvu9%2Fimage.png?alt=media&amp;token=d1bed6a9-3606-4028-9daf-f6e75a7dc1db" alt="SIP trunking topology: an ITSP cloud connects through two ProSBCs in series to the FusionPBX server."><figcaption></figcaption></figure>

### Example Configuration

SIP Trunk configuration.

* [FusionPBX Trunk Creation](/configuration-details/configuration-by-use-case/sip-trunking-configuration/fusionpbx-sip-trunk-creation)
* [SIP Trunking Example Configuration](/configuration-details/configuration-by-use-case/sip-trunking-configuration/sip-trunk-configuration-instruction-with-fusionpbx)

### Example Environments for Remote Workers with FusionPBX

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FgVsqo11TJ8245CrlruTc%2Fimage.png?alt=media&amp;token=309b8465-c110-49fb-a912-1d4c5bb0db84" alt="Remote workers topology: a remote office and two remote-worker phones reach the FusionPBX server across the internet through a single ProSBC."><figcaption></figcaption></figure>

### Example Configuration

Remote workers configuration.

* [FusionPBX Extension Creation](/configuration-details/configuration-by-use-case/sip-trunking-configuration/fusionpbx-extension-creation)
* [Remote Workers Configuration Instruction with FusionPBX](/configuration-details/configuration-by-use-case/remote-workers/remote-workers-configuration-instruction-with-fusionpbx)

### Troubleshooting

<table><thead><tr><th width="200">Call Trace</th><th width="200">Test Call</th><th width="200">TBReport</th><th width="200">Advanced Troubleshooting of ProSBC</th></tr></thead><tbody><tr><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace">Configure call trace</a></li><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace/retrieving-call-trace">Retrieve call trace</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/creating-a-test-call">Creating a Test Call</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/tbreport">Capture a report of the system</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-common-problems">Advanced Troubleshooting of ProSBC</a></li></ul></td></tr></tbody></table>


# FreeSWITCH

Set up ProSBC between an ITSP SIP trunk and a FreeSWITCH server, including FreeSWITCH trunk creation and the SIP trunking configuration.

## Introduction

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

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

### Prerequisites

* 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 installation guides.
* For additional information on FreeSWITCH, visit [FreeSWITCH offical web site](https://freeswitch.com/).

### Example Environments for SIP Trunking with FreeSWITCH

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FMAucZWpOBMe1sjeKDEX7%2Fimage.png?alt=media&amp;token=8e0a8fbf-9a8c-41e7-87ba-668385dd0b9d" alt="SIP trunking topology: an ITSP cloud connects through two ProSBCs in series to the FreeSWITCH server."><figcaption></figcaption></figure>

### Example Configuration

Step by step example SIP Trunk configuration.

* [FreeSWITCH Trunk Creation](/configuration-details/configuration-by-use-case/sip-trunking-configuration/freeswitch-sip-trunk-creation)
* [SIP Trunking Example Configuration](/configuration-details/configuration-by-use-case/sip-trunking-configuration/sip-trunk-configuration-instruction-with-freeswitch)

### Troubleshooting

<table><thead><tr><th width="200">Call Trace</th><th width="200">Test Call</th><th width="200">TBReport</th><th width="200">Advanced Troubleshooting of FreeSBC</th></tr></thead><tbody><tr><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace">Configure call trace</a></li><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace/retrieving-call-trace">Retrieve call trace</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/creating-a-test-call">Creating a Test Call</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/tbreport">Capture a report of the system</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-common-problems">Advanced Troubleshooting of ProSBC</a></li></ul></td></tr></tbody></table>


# Twilio

Connect your IP-PBX to Twilio Elastic SIP Trunking through ProSBC for scalable cloud connectivity to the PSTN over any broadband connection.

## Introduction

[Twilio Elastic SIP Trunking](https://www.twilio.com/docs/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 [free Twilio trial](https://www.twilio.com/try-twilio) and learn more about [configuring your Twilio Elastic SIP Trunk](https://www.twilio.com/docs/sip-trunking)

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 devices must be installed as described in their respective installation guides.
* Twilio Elastic SIP Trunking Account. Please visit the following link for more details about [Twilio Elastic SIP Trunking](https://www.twilio.com/docs/sip-trunking)

### Example Environments for SIPTrunking with Twilio

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2F8wCXNloatat7DtQYJafV%2Fimage.png?alt=media&amp;token=8e66f5a7-8ce5-4ffe-aa54-62deef20303b" alt="An enterprise LAN with its IP-PBX and fax server connects through ProSBC to the Twilio platform, which in turn reaches the PSTN."><figcaption></figcaption></figure>

### Example Configuration

Step by step example SIP Trunk configuration.

* [Twilio Elastic SIP Trunking Configuration](/configuration-details/configuration-by-use-case/sip-trunking-configuration/sippy-sip-trunk-creation)
* [ProSBC Configuration for Twilio Elastic SIP Trunking](/configuration-details/configuration-by-use-case/sip-trunking-configuration/sip-trunk-configuration-instruction-with-twilio-elastic-trunking)

### Troubleshooting

<table><thead><tr><th width="200">Call Trace</th><th width="200">Test Call</th><th width="200">TBReport</th><th width="200">Advanced Troubleshooting of ProSBC</th></tr></thead><tbody><tr><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace">Configure call trace</a></li><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace/retrieving-call-trace">Retrieve call trace</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/creating-a-test-call">Creating a Test Call</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/tbreport">Capture a report of the system</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-common-problems">Advanced Troubleshooting of ProSBC</a></li></ul></td></tr></tbody></table>


# Sippy

Set up ProSBC for interworking with the Sippy soft switch, including adding ProSBC as a SIP trunk in the Sippy server.

## Introduction

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

### Prerequisites

* 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 installation guides.
* Sippy Soft Switch. For additional information on Sippysoft, visit [Sippysoft official web site](https://www.sippysoft.com/).

### Example Environments for SIPTrunking with Sippysoft

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FODTgqjoBNPpYfkyZVLfJ%2Fimage.png?alt=media&amp;token=537ef377-1e24-4fc9-90d7-72419ee4b86b" alt="SIP trunking topology: an ITSP cloud connects through ProSBC to the Sippy soft switch."><figcaption></figcaption></figure>

### Example Configuration

Step by step example SIP Trunk configuration.

* [Adding ProSBC as a SIP Trunk in Sippy Server](/configuration-details/configuration-by-use-case/sip-trunking-configuration/sippy-sip-trunk-creation)
* [SIP Trunk Configuration Instruction with Sippy Server](/configuration-details/configuration-by-use-case/sip-trunking-configuration/sip-trunk-configuration-instruction-with-avaya-ip-office)

### Troubleshooting

<table><thead><tr><th width="200">Call Trace</th><th width="200">Test Call</th><th width="200">TBReport</th><th width="200">Advanced Troubleshooting of ProSBC</th></tr></thead><tbody><tr><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace">Configure call trace</a></li><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace/retrieving-call-trace">Retrieve call trace</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/creating-a-test-call">Creating a Test Call</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/tbreport">Capture a report of the system</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-common-problems">Advanced Troubleshooting of ProSBC</a></li></ul></td></tr></tbody></table>


# Avaya IP Office

Set up ProSBC for interworking with Avaya IP Office R11, including adding ProSBC as a SIP trunk and configuring the trunk on both sides.

## Introduction

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

### Prerequisites

* 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 installation guides.
* Avaya IP Office R11. For additional information on Avaya IP Office, visit [Avaya Support](https://support.avaya.com/products/P0160/ip-office-platform/).

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

###

<figure><img src="https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2FES3wnYj4JYru2bNzQVpG%2Fimage.png?alt=media&amp;token=00c2d7f0-21ba-4e21-9ca0-cbe1e8a00c89" alt="SIP trunking topology: an ITSP cloud connects through ProSBC to an Avaya IP Office platform."><figcaption></figcaption></figure>

### Example Configuration

Step by step example SIP Trunk configuration.

* [Adding ProSBC as a SIP Trunk in Avaya IP Office](/configuration-details/configuration-by-use-case/sip-trunking-configuration/avaya-ip-office-trunk-creation)
* [SIP Trunk Configuration Instruction with Avaya IP Office](/configuration-details/configuration-by-use-case/sip-trunking-configuration/sip-trunk-configuration-instruction-with-avaya-ip-office)

### Troubleshooting

<table><thead><tr><th width="200">Call Trace</th><th width="200">Test Call</th><th width="200">TBReport</th><th width="200">Advanced Troubleshooting of ProSBC</th></tr></thead><tbody><tr><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace">Configure call trace</a></li><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace/retrieving-call-trace">Retrieve call trace</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/creating-a-test-call">Creating a Test Call</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/tbreport">Capture a report of the system</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-common-problems">Advanced Troubleshooting of ProSBC</a></li></ul></td></tr></tbody></table>


# Cisco UCM 12

Set up ProSBC for interworking with Cisco Unified Communications Manager 12, including adding ProSBC as a SIP trunk in Cisco UCM.

## Introduction

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

### Prerequisites

* 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 installation guides.
* Cisco Unified Communications Manager 12. For additional information on Cisco UCM, visit [Cisco Support](https://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-version-12-0/model.html).

### Example Environments for SIP Trunking with Cisco UCM

<figure><img src="https://docs.telcobridges.com/w/images/thumb/4/4b/Cisco_ucm.png/800px-Cisco_ucm.png" alt="SIP trunking topology: an ITSP cloud connects through ProSBC to Cisco Unified Communications Manager."><figcaption></figcaption></figure>

### Example Configuration

Step by step example SIP Trunk configuration.

* [Adding ProSBC as a SIP Trunk in Cisco UCM](/configuration-details/configuration-by-use-case/sip-trunking-configuration/cisco-ucm-12-trunk-creation)
* [SIP Trunk Configuration Instruction with Cisco UCM](/configuration-details/configuration-by-use-case/sip-trunking-configuration/sip-trunk-configuration-instruction-with-cisco-ucm)

### Troubleshooting

<table><thead><tr><th width="200">Call Trace</th><th width="200">Test Call</th><th width="200">TBReport</th><th width="200">Advanced Troubleshooting of ProSBC</th></tr></thead><tbody><tr><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace">Configure call trace</a></li><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace/retrieving-call-trace">Retrieve call trace</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/creating-a-test-call">Creating a Test Call</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/tbreport">Capture a report of the system</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-common-problems">Advanced Troubleshooting of ProSBC</a></li></ul></td></tr></tbody></table>


# Brekeke PBX

Set up ProSBC between an ITSP SIP trunk and a Brekeke PBX, for SIP trunking or remote client access.

## 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 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 installation guides.
* Brekeke PBX.For additional information on Brekeke, visit [Brekeke official web site](https://www.brekeke.com/).

### Example Environments for SIPTrunking with Brekeke PBX

<figure><img src="https://docs.telcobridges.com/w/images/thumb/f/f1/Brekeke_SIP_Trunk.png/800px-Brekeke_SIP_Trunk.png" alt="SIP trunking topology: an ITSP cloud connects through ProSBC to a Brekeke PBX."><figcaption></figcaption></figure>

### Example Configuration

Step by step example SIP Trunk configuration.

* [Adding ProSBC as a SIP Trunk in Brekeke PBX](/configuration-details/configuration-by-use-case/sip-trunking-configuration/adding-prosbc-as-a-sip-trunk-in-the-brekeke-pbx)
* [SIP Trunk Configuration Instruction with Brekeke PBX](/configuration-details/configuration-by-use-case/sip-trunking-configuration/sip-trunk-configuration-instruction-with-brekeke-pbx)

### Troubleshooting

<table><thead><tr><th width="200">Call Trace</th><th width="200">Test Call</th><th width="200">TBReport</th><th width="200">Advanced Troubleshooting of ProSBC</th></tr></thead><tbody><tr><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace">Configure call trace</a></li><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace/retrieving-call-trace">Retrieve call trace</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/creating-a-test-call">Creating a Test Call</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/tbreport">Capture a report of the system</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-common-problems">Advanced Troubleshooting of ProSBC</a></li></ul></td></tr></tbody></table>


# VitalPBX

Set up ProSBC between an ITSP SIP trunk and a VitalPBX server, covering trunk creation, extensions and remote worker access.

## 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 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 installation guides.
* VitalPBX.For additional information on VitalPBX, visit [VitalPBX offical web site](https://www.vitalpbx.org/).

### Example Environments for SIP Trunking with VitalPBX

<figure><img src="https://docs.telcobridges.com/w/images/thumb/f/f6/Vitalpbx_Trunking_1.png/800px-Vitalpbx_Trunking_1.png" alt="SIP trunking topology: an ITSP cloud connects through ProSBC to the VitalPBX server."><figcaption></figcaption></figure>

### Example Configuration

Step by step example SIP Trunk configuration.

* [VitalPBX Trunk Creation](/configuration-details/configuration-by-use-case/sip-trunking-configuration/vitalpbx-sip-trunk-creation)
* [SIP Trunking Example Configuration](/configuration-details/configuration-by-use-case/sip-trunking-configuration/sip-trunk-configuration-instruction-with-vitalpbx)

### Example Environments for Remote Workers with VitalPBX

<figure><img src="https://docs.telcobridges.com/w/images/thumb/2/21/VitalPbx_Remote_Workers.png/800px-VitalPbx_Remote_Workers.png" alt="Remote workers topology: a remote office and two remote-worker phones reach the VitalPBX server across the internet through a single ProSBC."><figcaption></figcaption></figure>

### Example Configuration

Step by step example Remote workers configuration.

* [VitalPBX Extension Creation](/configuration-details/configuration-by-use-case/sip-trunking-configuration/vitalpbx-extension-creation)
* [Remote Workers Configuration Instruction with VitalPBX](/configuration-details/configuration-by-use-case/remote-workers/remote-workers-configuration-instruction-with-vitalpbx)

### Troubleshooting

<table><thead><tr><th width="200">Call Trace</th><th width="200">Test Call</th><th width="200">TBReport</th><th width="200">Advanced Troubleshooting of ProSBC</th></tr></thead><tbody><tr><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace">Configure call trace</a></li><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace/retrieving-call-trace">Retrieve call trace</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/creating-a-test-call">Creating a Test Call</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/tbreport">Capture a report of the system</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-common-problems">Advanced Troubleshooting of ProSBC</a></li></ul></td></tr></tbody></table>


# Yeastar P-Series Cloud

Set up ProSBC between an ITSP SIP trunk and Yeastar P-Series Cloud, including adding ProSBC as a SIP trunk in the Yeastar console.

## Introduction

This Configuration Note describes how to set up Telcobridges ProSBC for interworking between ITSP’s SIP Trunk for Yeastar P-Series Cloud.

### Prerequisites

* 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 installation guides.
* Yeastar P-Series Cloud. For additional information on Yeastar P-Series Cloud, visit [Yeastar P-Series Cloud official website](https://www.yeastar.com/cloud-pbx/).

### Example Environments for SIPTrunking with Yeastar P-Series Cloud

<figure><img src="https://docs.telcobridges.com/w/images/thumb/b/b1/Yeastar_P-Series_Cloud_Trunk.png/800px-Yeastar_P-Series_Cloud_Trunk.png" alt="SIP trunking topology: Yeastar P-Series Cloud sends calls into ProSBC, which connects to the ITSP cloud."><figcaption></figcaption></figure>

### Example Configuration

Step-by-step example SIP Trunk configuration.

* [Adding ProSBC as a SIP Trunk in Yeastar P-Series Cloud](/configuration-details/configuration-by-use-case/sip-trunking-configuration/adding-prosbc-as-a-sip-trunk-in-the-yeastar-p-series-cloud)
* [SIP Trunk Configuration Instruction with Yeastar P-Series Cloud](/configuration-details/configuration-by-use-case/sip-trunking-configuration/sip-trunk-configuration-instruction-with-yeastar-p-series-cloud)

### Troubleshooting

<table><thead><tr><th width="200">Call Trace</th><th width="200">Test Call</th><th width="200">TBReport</th><th width="200">Advanced Troubleshooting of ProSBC</th></tr></thead><tbody><tr><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace">Configure call trace</a></li><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace/retrieving-call-trace">Retrieve call trace</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/creating-a-test-call">Creating a Test Call</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/tbreport">Capture a report of the system</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-common-problems">Advanced Troubleshooting of ProSBC</a></li></ul></td></tr></tbody></table>


# VoIP.ms

Connect your IP-PBX to VoIP.ms SIP trunking through ProSBC. VoIP.ms offers DIDs in 60+ countries and termination across more than 125 countries.

[VoIP.ms](https://voip.ms/residential) is a Montreal-based Voice over IP (VoIP) company founded in 2007 that provides a vast range of standard telephony features as well as enhanced communication features to simplify both business and residential communications such as local DID numbers in 60+ countries, it also offers termination (outgoing calls) in over 125 countries across the globe, toll-free numbers, call conferencing and services such as E911, CNAM Lookup, SMS/MMS, virtual fax, virtual PRI and local number portability.

ProSBC connects your IP-PBX to VoIP.ms SIP Trunking. This article describes how to connect ProSBC to VoIP SIP Trunking.

### Prerequisites

* ProSBC devices must be installed as described in their respective installation guides.
* VoIP SIP Trunking Account. Please visit the following link for more details about [VoIP.ms](https://voip.ms/residential)

### Example Environments for SIPTrunking with VoIP.ms

<figure><img src="https://docs.telcobridges.com/w/images/0/01/Voipms_Trunking.png" alt="SIP trunking topology: the VoIP.ms service connects through ProSBC to an enterprise LAN holding the IP-PBX and a fax server."><figcaption></figcaption></figure>

### Example Configuration

Step by step example SIP Trunk configuration.

* [VoIP.ms SIP Trunking Configuration](/configuration-details/configuration-by-use-case/sip-trunking-configuration/sip-trunk-configuration-instruction-with-voip.ms-sip-trunking)
* ProSBC wiki in [VoIP.ms](https://wiki.voip.ms/article/TelcoBridges_SBC) web site

### Troubleshooting

<table><thead><tr><th width="200">Call Trace</th><th width="200">Test Call</th><th width="200">TBReport</th><th width="200">Advanced Troubleshooting of ProSBC</th></tr></thead><tbody><tr><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace">Configure call trace</a></li><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace/retrieving-call-trace">Retrieve call trace</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/creating-a-test-call">Creating a Test Call</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/tbreport">Capture a report of the system</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-common-problems">Advanced Troubleshooting of ProSBC</a></li></ul></td></tr></tbody></table>


# Wildix

Set up ProSBC for interworking with the Wildix Cloud VoIP PBX, including adding ProSBC as a SIP trunk.

## Introduction

This Configuration Note describes how to set up Telcobridges ProSBC for interworking between Wildix Cloud VoIP PBX.

### Prerequisites

* 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 installation guides.
* Wildix Cloud VoIP PBX. For additional information on Wildix, visit [Wildix Cloud VoIP PBX website](https://www.wildix.com/product/cloud-voip-pbx/).

### Example Environments for SIPTrunking with Wildix Cloud VoIP PBX

<figure><img src="https://docs.telcobridges.com/w/images/4/42/Wildix_Cloud_Trunk.png" alt="SIP trunking topology: an ITSP cloud connects through ProSBC to the Wildix Cloud VoIP PBX."><figcaption></figcaption></figure>

### Example Configuration

Step-by-step example SIP Trunk configuration.

* [Adding ProSBC as a SIP Trunk in Wildix Cloud VoIP PBX](/configuration-details/configuration-by-use-case/sip-trunking-configuration/adding-prosbc-as-a-sip-trunk-in-the-wildix-cloud-voip-pbx)
* [SIP Trunk Configuration Instruction with Wildix Cloud VoIP PBX](/configuration-details/configuration-by-use-case/sip-trunking-configuration/sip-trunk-configuration-instruction-with-wildix-cloud-voip-pbx)

### Troubleshooting

<table><thead><tr><th width="200">Call Trace</th><th width="200">Test Call</th><th width="200">TBReport</th><th width="200">Advanced Troubleshooting of ProSBC</th></tr></thead><tbody><tr><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace">Configure call trace</a></li><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace/retrieving-call-trace">Retrieve call trace</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/creating-a-test-call">Creating a Test Call</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-tips-and-actions/tbreport">Capture a report of the system</a></li></ul></td><td><ul><li><a href="/troubleshooting-and-support/troubleshooting-common-problems">Advanced Troubleshooting of ProSBC</a></li></ul></td></tr></tbody></table>


# Configuration By Web Portal Category

The Web Portal Tutorial provides you with a scenario-based approach to configuring and monitoring the status ProSBC systems, using the Web Portal configuration tool. Complete general installation configuration steps, before you begin configuring your specific application.

Web Portal Categories and status topics are grouped into the following major categories. It is recommended that you follow this order.

{% tabs %}
{% tab title="System" %}

* Host Role
* SBC
* Access and User Management
* Database Backup
* SNMP
* Configuration
* Minor Package Upgrade
* Software Licenses
* Statistics
* Audit Logs

[(Configuration)](/configuration-details/configuration-by-web-portal-category/system-settings)
{% endtab %}

{% tab title="IP Network" %}

* IP Network
* DNS
* NAT
* Transcoding Units
* Ethernet Bonding

[(Configuration)](/configuration-details/configuration-by-web-portal-category/ip-network-settings)
{% endtab %}

{% tab title="Protocol Stack" %}

* Certificates and TLS Profiles
* SIP
* Calls
* NAP
  {% endtab %}

{% tab title="CDR" %}

* Text CDR
* RADIUS

[(Configuration)](/configuration-details/configuration-by-web-portal-category/call-detail-records-cdr)
{% endtab %}

{% tab title="Fax" %}

* FAX passthrough (silence suppression)
* FAX T.38
* FAX passthrough (NSE)
* FAX passthrough (VBD)

[(Configuration)](/configuration-details/configuration-by-web-portal-category/nap-profiles/fax-settings)
{% endtab %}

{% tab title="Call Route" %}

* Static Route
* Routing Script
* Label Routing
* RADIUS Authorization and Authentication

[(Configuration)](/configuration-details/configuration-by-web-portal-category/call-routing)
{% endtab %}

{% tab title="Lawful Intercept" %}

* Lawful Interception Prerequisite
* Import a Lawful Interception CSV File
* Create New Routing Script
* Enable Lawful Interception in Routing Script
* Enable Routing Script
* Configure Lawful Agencies

\
[(Configuration)](/configuration-details/configuration-by-web-portal-category/lawful-intercept) [(Status)](/configuration-details/configuration-by-web-portal-category/lawful-intercept/lawful-intercept-status)
{% endtab %}

{% tab title="Troubleshooting" %}

* CallTrace
* Test Call
* Target Recording
* Ethernet Capture
  {% endtab %}
  {% endtabs %}


# System Settings

Applies to ProSBC and Tmedia products

\
*IMPORTANT!* The topics appearing in the following tables are common to all Tsbc installations. Consult this section for configuration tasks.

{% tabs %}
{% tab title="Host Role" %}

<table><thead><tr><th width="200">Standalone</th><th width="200">1+1</th><th width="200">Reset</th></tr></thead><tbody><tr><td><a href="/configuration-details/configuration-by-web-portal-category/system-settings/setting-the-role-to-standalone">Standalone</a></td><td><ul><li><a href="/configuration-details/configuration-by-web-portal-category/system-settings/setting-the-role-to-a-primary-unit-in-a-1+1-system">1+1 Primary</a></li><li><a href="/configuration-details/configuration-by-web-portal-category/system-settings/setting-the-role-to-a-secondary-unit-in-a-1+1-system">1+1 Secondary</a></li></ul></td><td><ul><li><a href="/configuration-details/configuration-by-web-portal-category/system-settings/resetting-the-host-role">Reset the Host Role</a></li><li><a href="/configuration-details/configuration-by-web-portal-category/system-settings/resetting-the-network-device-role">Reset the Network Devices Roles</a></li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="SBC" %}

<table><thead><tr><th width="340">SBC Manual Firewall Entry</th><th width="291">SBC Access Rule</th></tr></thead><tbody><tr><td><a href="/configuration-details/configuration-by-web-portal-category/system-settings/create-session-border-gateway-access-control-list-acl">Create SBC Access Control List (ACL)</a></td><td><a href="/configuration-details/configuration-by-web-portal-category/system-settings/create-session-border-gateway-access-control-list-acl-filters">Create SBC Access Control List (ACL) Filter</a></td></tr></tbody></table>

\
[SBC Advanced Settings](/configuration-details/configuration-by-web-portal-category/system-settings/session-border-gateway-advanced-parameter-settngs)
{% endtab %}

{% tab title="Access and User Management" %}

<table><thead><tr><th width="200">Web Portal Access</th><th width="200">Security Settings</th><th width="200">User Management</th><th></th><th></th><th></th></tr></thead><tbody><tr><td>Add User</td><td>Modify User Permission</td><td>Enable/Disable User</td><td>Delete User</td><td></td><td></td></tr><tr><td><ul><li><a href="/configuration-details/configuration-by-web-portal-category/system-settings/connecting-to-the-web-server-and-logging-on-to-the-web-portal">Connect to the Web Portal</a></li><li><a href="/configuration-details/configuration-by-web-portal-category/system-settings/logging-off">Logging Off</a></li></ul></td><td><a href="/configuration-details/configuration-by-web-portal-category/system-settings/modifying-security-settings">Modifying security settings</a></td><td><ul><li><a href="/configuration-details/configuration-by-web-portal-category/system-settings/creating-web-user-groups">Creating User Groups</a></li><li><a href="/configuration-details/configuration-by-web-portal-category/system-settings/creating-web-users">Creating Users</a></li></ul><p><br></p></td><td><a href="/configuration-details/configuration-by-web-portal-category/system-settings/modifying-web-user-permissions">Modify User Permission</a></td><td><a href="/configuration-details/configuration-by-web-portal-category/system-settings/enabling-and-disabling-a-user">Enable/Disable User</a></td><td><a href="/configuration-details/configuration-by-web-portal-category/system-settings/deleting-a-user">Delete User</a></td></tr></tbody></table>
{% endtab %}

{% tab title="Data Backup" %}

<table><thead><tr><th width="369">Create Database Backup</th><th width="277">Restore Database</th></tr></thead><tbody><tr><td><ul><li><a href="https://app.gitbook.com/o/ciMqFluL2ummjDw5gsc5/s/iK3TemJSDhHz3xNMOvvk/~/changes/137/detailed-configuration-instructions/configuration-by-web-portal-category/system-settings/database-backup">Carrying out a First Database Backup</a></li><li><a href="https://app.gitbook.com/o/ciMqFluL2ummjDw5gsc5/s/iK3TemJSDhHz3xNMOvvk/~/changes/137/detailed-configuration-instructions/configuration-by-web-portal-category/system-settings/downloading-a-database-backup">Downloading a Database Backup</a></li></ul></td><td><ul><li><a href="https://app.gitbook.com/o/ciMqFluL2ummjDw5gsc5/s/iK3TemJSDhHz3xNMOvvk/~/changes/137/detailed-configuration-instructions/configuration-by-web-portal-category/system-settings/uploading-a-database-backup">Uploading a Database</a></li><li><a href="https://app.gitbook.com/o/ciMqFluL2ummjDw5gsc5/s/iK3TemJSDhHz3xNMOvvk/~/changes/137/detailed-configuration-instructions/configuration-by-web-portal-category/system-settings/restoring-a-database">Restoring a Database</a></li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="SNMP" %}

<table><thead><tr><th width="200">Enable SNMP</th><th width="296">SNMP Get/Get Next</th><th width="200">SNMP Traps</th></tr></thead><tbody><tr><td><a href="https://app.gitbook.com/o/ciMqFluL2ummjDw5gsc5/s/iK3TemJSDhHz3xNMOvvk/~/changes/137/detailed-configuration-instructions/configuration-by-web-portal-category/system-settings/enabling-the-snmp-agent">Enabling SNMP</a></td><td><ul><li><a href="https://app.gitbook.com/o/ciMqFluL2ummjDw5gsc5/s/iK3TemJSDhHz3xNMOvvk/~/changes/137/detailed-configuration-instructions/configuration-by-web-portal-category/system-settings/configuring-the-snmp-agent">Configuring SNMP Agent</a></li><li><a href="https://app.gitbook.com/o/ciMqFluL2ummjDw5gsc5/s/iK3TemJSDhHz3xNMOvvk/~/changes/137/detailed-configuration-instructions/configuration-by-web-portal-category/system-settings/creating-an-snmpv1-snmpv2-community">Creating SNMP v1, SNMP v2 communities</a></li></ul><p>or</p><ul><li><a href="https://app.gitbook.com/o/ciMqFluL2ummjDw5gsc5/s/iK3TemJSDhHz3xNMOvvk/~/changes/137/detailed-configuration-instructions/configuration-by-web-portal-category/system-settings/creating-an-snmpv3-user">Creating an SNMP v3 user</a></li></ul></td><td><a href="https://app.gitbook.com/o/ciMqFluL2ummjDw5gsc5/s/iK3TemJSDhHz3xNMOvvk/~/changes/137/detailed-configuration-instructions/configuration-by-web-portal-category/system-settings/creating-an-snmp-trap-destination">Configuring SNMP traps destination</a></td></tr></tbody></table>
{% endtab %}
{% endtabs %}

{% tabs %}
{% tab title="Configuration" %}

<table><thead><tr><th width="347">Activating a Configuration</th><th width="246">Web Portal Profile</th></tr></thead><tbody><tr><td><a href="/configuration-details/configuration-by-web-portal-category/system-settings/activating-the-configuration">Activating the Configuration</a></td><td><a href="/configuration-details/configuration-by-web-portal-category/system-settings/configuring-a-web-portal-profile">Web Portal Profile</a></td></tr></tbody></table>

{% endtab %}

{% tab title="Services" %}

<table><thead><tr><th width="200">Set Date Time</th><th width="200">Set DNS</th><th width="200">Create http service</th><th width="200">Configure ICMP service</th><th width="200">Configure SSH service</th></tr></thead><tbody><tr><td><a href="/configuration-details/configuration-by-web-portal-category/system-settings/configuring-the-date-time-timezone-and-ntp-servers">Set Date Time</a></td><td><a href="/configuration-details/configuration-by-web-portal-category/system-settings/configuring-the-dns">Set DNS</a></td><td><ul><li><a href="/configuration-details/configuration-by-web-portal-category/system-settings/create-http-service">Create HTTP service</a></li><li><a href="/configuration-details/configuration-by-web-portal-category/system-settings/use-https-service">Use HTTPS service</a></li></ul></td><td><a href="/configuration-details/configuration-by-web-portal-category/system-settings/configuring-the-icmp">Configure ICMP service</a></td><td><a href="/configuration-details/configuration-by-web-portal-category/system-settings/configuring-the-ssh">Configure SSH service</a></td></tr></tbody></table>
{% endtab %}

{% tab title="Package Upgrade" %}

<table><thead><tr><th width="587">Installing a Package</th></tr></thead><tbody><tr><td><ul><li><a href="/maintenance-and-troubleshooting/system-upgrade/linux-software-packages-upgrade">Upgrading the operating system with the latest packages</a></li><li><a href="/maintenance-and-troubleshooting/system-upgrade/retrieving-a-software-release">Retrieving a software release</a></li><li><a href="/maintenance-and-troubleshooting/system-upgrade/uploading-a-software-release">Uploading a software release</a></li><li><a href="/maintenance-and-troubleshooting/system-upgrade/activating-a-software-release">Activating a software release</a></li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="Upload License" %}

<table><thead><tr><th width="570">Installing a Package</th></tr></thead><tbody><tr><td><ul><li><a href="/maintenance-and-troubleshooting/system-upgrade/retrieving-a-license">Retrieving a License</a></li><li><a href="/maintenance-and-troubleshooting/system-upgrade/uploading-a-license">Uploading a license</a></li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="Audit Logs" %}

<table><thead><tr><th width="640">Audit Logs</th></tr></thead><tbody><tr><td><a href="/configuration-details/configuration-by-web-portal-category/system-settings/accessing-audit-logs">Working with Audit Logs</a></td></tr></tbody></table>
{% endtab %}
{% endtabs %}


# Setting the Role to Standalone

The first time that you connect to a Tsbc, the web portal setup wizard will be displayed and you will be asked to select how you would like to configure its role. Your choices are standalone, primary, or secondary. Once the role configuration settings are applied, the unit will start up and display the web portal configuration management tool.

To configure the host role of the unit as a standalone unit, do the following:

\
1- When the setup wizard is displayed, click Continue

<figure><img src="https://docs.telcobridges.com/w/images/2/2d/HostRoleStandaloneTsbc_0_A.png" alt=""><figcaption></figcaption></figure>

\
2- Select As a stand-alone unit and click Continue.

<figure><img src="https://docs.telcobridges.com/w/images/8/82/HostRoleStandalone_1_A.png" alt=""><figcaption></figcaption></figure>

\
3- If you need to change the default subnet address or subnet mask, click change internal subnets and proceed to step 3a, otherwise click Continue and go to step 4.

<figure><img src="https://docs.telcobridges.com/w/images/d/d5/HostRolePrimary_4_A.png" alt=""><figcaption></figcaption></figure>

\
3a- Enter the subnet address and subnet mask for each VLAN ID and click Continue.

<figure><img src="https://docs.telcobridges.com/w/images/b/b9/HostRolePrimary_5_A.png" alt=""><figcaption></figcaption></figure>

Allow for the change to take effect.

<figure><img src="https://docs.telcobridges.com/w/images/8/87/HostRoleStandalone_2_A.png" alt=""><figcaption></figcaption></figure>

\
4- The Web Portal Log On page is displayed.

* Enter the user name and password.

<figure><img src="https://docs.telcobridges.com/w/images/d/da/HostRoleStandalone_3_A.png" alt=""><figcaption></figcaption></figure>


# Setting the Role to a Primary Unit in a 1+1 System

The first time that you connect to a SBC, the web portal setup wizard will be displayed and you will be asked to select how you would like to configure its role. Your choices are standalone, primary, or secondary. Once the role configuration settings are applied, the unit will start up and display the web portal configuration management tool.

To configure the host role of the unit as the primary unit in a 1+1 system, do the following:

\
1- When the setup wizard is displayed, click Continue

<figure><img src="https://docs.telcobridges.com/w/images/3/32/HostRolePrimaryTsbc_0_A.png" alt=""><figcaption></figcaption></figure>

\
2- Select As part of a 1+1 redundant system and click Continue.

<figure><img src="https://docs.telcobridges.com/w/images/3/35/HostRolePrimary_1_A.png" alt=""><figcaption></figcaption></figure>

\
3- Select The primary unit and click Continue.

<figure><img src="https://docs.telcobridges.com/w/images/f/fe/HostRolePrimary_2_A.png" alt=""><figcaption></figcaption></figure>

\
4- When you are asked if the unit should get configuration and packages from an existing secondary unit, select No and click Continue.

<figure><img src="https://docs.telcobridges.com/w/images/5/59/HostRolePrimary_3_A.png" alt=""><figcaption></figcaption></figure>

\
5- If you need to change the default subnet address or subnet mask, click change internal subnets and proceed to step 5a, otherwise click Continue and go to step 6.

<figure><img src="https://docs.telcobridges.com/w/images/d/d5/HostRolePrimary_4_A.png" alt=""><figcaption></figcaption></figure>

\
5a- Enter the subnet address and subnet mask for each VLAN ID and click Continue.

<figure><img src="https://docs.telcobridges.com/w/images/b/b9/HostRolePrimary_5_A.png" alt=""><figcaption></figcaption></figure>

\
6- Once you are satisfied with your settings, click Confirm.

<figure><img src="https://docs.telcobridges.com/w/images/c/cf/HostRolePrimary_6_A.png" alt=""><figcaption></figcaption></figure>

\
Allow for the host role changes to take effect.

<figure><img src="https://docs.telcobridges.com/w/images/2/27/HostRolePrimary_7_A.png" alt=""><figcaption></figcaption></figure>

\
7- The Web Portal Log On page is displayed.

* Enter the user name and password.

<figure><img src="https://docs.telcobridges.com/w/images/7/7a/HostRolePrimary_8_A.png" alt=""><figcaption></figcaption></figure>


# Setting the Role to a Secondary Unit in a 1+1 System

The first time that you connect to a SBC, the web portal setup wizard will be displayed and you will be asked to select how you would like to configure the role of the unit. Your choices are standalone, primary, or secondary. Once the role configuration settings are applied, the unit will start up and display the web portal configuration management tool.

To configure the host role of the gateway as the secondary unit in a 1+1 system, do the following:

\
1- When the setup wizard is displayed, click Continue

<figure><img src="https://docs.telcobridges.com/w/images/a/ab/HostRoleSecondaryTsbc_0_A.png" alt=""><figcaption></figcaption></figure>

\
2- Select As part of a 1+1 redundant system and click Continue.

<figure><img src="https://docs.telcobridges.com/w/images/9/9c/HostRoleSecondary_1_A.png" alt=""><figcaption></figcaption></figure>

\
3- Select The secondary unit and click Continue.

<figure><img src="https://docs.telcobridges.com/w/images/6/63/HostRoleSecondary_2_A.png" alt=""><figcaption></figcaption></figure>

\
4- If you need to change the default subnet address or subnet mask, click change internal subnets and proceed to step 4a, otherwise click Continue and go to step 5.

<figure><img src="https://docs.telcobridges.com/w/images/f/fa/HostRoleSecondary_3_A.png" alt=""><figcaption></figcaption></figure>

\
4a- Enter the subnet address and subnet mask for each VLAN ID and click Continue.

<figure><img src="https://docs.telcobridges.com/w/images/f/fa/HostRoleSecondary_4_A.png" alt=""><figcaption></figcaption></figure>

\
5- Follow the onscreen instructions and connect the two units together. When you have completed the connections, click Continue.

<figure><img src="https://docs.telcobridges.com/w/images/c/c5/HostRoleSecondary_5_A.png" alt=""><figcaption></figcaption></figure>

\
6- Once you are satisfied with your settings, click Confirm.

<figure><img src="https://docs.telcobridges.com/w/images/4/4e/HostRoleSecondary_6_A.png" alt=""><figcaption></figcaption></figure>

\
Allow for the host role changes to take effect.

<figure><img src="https://docs.telcobridges.com/w/images/5/53/HostRoleSecondary_7_A.png" alt=""><figcaption></figcaption></figure>

\
7- The Web Portal Log On page is displayed.

* Enter the user name and password.

<figure><img src="https://docs.telcobridges.com/w/images/5/58/HostRoleSecondary_8_A.png" alt=""><figcaption></figcaption></figure>


# Resetting the Host Role

If you need to change internal IP addresses, you must reset the host role settings of the unit.

To reset the host role, do the following:

\
1- Click Hosts in the navigation panel.

<figure><img src="https://docs.telcobridges.com/w/images/f/f4/HostRoleReset_0_A.png" alt=""><figcaption></figcaption></figure>

\
2- Select the serial number of the unit.

<figure><img src="https://docs.telcobridges.com/w/images/4/4e/HostRoleReset_1_A.png" alt=""><figcaption></figcaption></figure>

\
3- Click the Status tab.

<figure><img src="https://docs.telcobridges.com/w/images/0/08/HostRoleReset_2_A.png" alt=""><figcaption></figcaption></figure>

\
4- Select Reset Host Role

* Click Apply action

<figure><img src="https://docs.telcobridges.com/w/images/c/c9/HostRoleReset_3_A.png" alt=""><figcaption></figcaption></figure>

\
5- The Web Portal setup wizard is displayed. (You may need to refresh your web page to see this)

<figure><img src="https://docs.telcobridges.com/w/images/3/3f/HostRoleReset_4_A.png" alt=""><figcaption></figcaption></figure>


# Resetting the Network Device Role

Once the ProSBC is configured, it is possible add or change physical IP interfaces. To do so you must reset the network device role settings of the unit.\
Note: this will reallocate the main network controller and stop the service for a few minutes

To reset the network device role, do the following:

1- Click Hosts in the navigation panel.

<figure><img src="https://docs.telcobridges.com/w/images/f/f4/HostRoleReset_0_A.png" alt=""><figcaption></figcaption></figure>

\
2- Select the serial number of the unit.

<figure><img src="https://docs.telcobridges.com/w/images/4/4e/HostRoleReset_1_A.png" alt=""><figcaption></figcaption></figure>

\
3- Click the Status tab.

<figure><img src="https://docs.telcobridges.com/w/images/0/08/HostRoleReset_2_A.png" alt=""><figcaption></figcaption></figure>

\
4- In the Action drop down box select Change Network Devices Roles

* Click Apply Action

<figure><img src="https://docs.telcobridges.com/w/images/b/b7/Host_action_snapshot_network.png" alt=""><figcaption></figcaption></figure>


# Create Session Border Gateway Access Control List (ACL)

In addition to the default access rules that are included with the SBC, one or more custom rules can be created and their priority in a series of rules can be set. To add a new rule or to change its priority, do the following:

1-Click ACL in the navigation panel.

\ <br>

<figure><img src="https://docs.telcobridges.com/w/images/9/90/ACL_0.png" alt=""><figcaption></figcaption></figure>

2-Click Create New Rule.

\ <br>

<figure><img src="https://docs.telcobridges.com/w/images/d/d5/Sbc_Rule_0.png" alt=""><figcaption></figcaption></figure>

3-Enter values for the rule.

* Click Create

\ <br>

<figure><img src="https://docs.telcobridges.com/w/images/8/85/Sbc_Rule_1.png" alt=""><figcaption></figcaption></figure>

4-Verify that Firewall rules were successfully created message is displayed.

<figure><img src="https://docs.telcobridges.com/w/images/5/59/Sbc_Rule_2.png" alt=""><figcaption></figcaption></figure>


# Session Border Gateway: Advanced Parameter Settngs

The session border gateway feature is enabled by default. To verify or change the setting, do the following:

1-Click SBC in the navigation panel.

\ <br>

<figure><img src="https://docs.telcobridges.com/w/images/0/01/Sbc_Enable_0.png" alt=""><figcaption></figcaption></figure>

### List of Parameters

Advanced Parameters

* [Connection debug mode](/configuration-details/configuration-parameters-all#parameter-sbc-connection-debug-mode)
* [Default ban duration](/configuration-details/configuration-parameters-all#parameter-sbc-default-ban-duration)
* List Sizes
  * [Maximum accept entries](/configuration-details/configuration-parameters-all#parameter-sbc-maximum-accept-entries)
  * [Maximum drop entries](/configuration-details/configuration-parameters-all#parameter-sbc-maximum-drop-entries)
  * [Maximum filters](/configuration-details/configuration-parameters-all#parameter-sbc-maximum-filters)
* Default values for manual rules
  * [Default entry duration](/configuration-details/configuration-parameters-all#parameter-sbc-default-entry-duration)
  * [Default maximum bandwidth](/configuration-details/configuration-parameters-all#parameter-sbc-default-maximum-bandwidth)
  * [Default maximum bandwidth](/configuration-details/configuration-parameters-all#parameter-sbc-default-maximum-bandwidth-pps)
  * [Default temporary ban duration](/configuration-details/configuration-parameters-all#parameter-sbc-default-temporary-ban-duration)
* Default values for OAMP rules
  * [Default entry duration](/configuration-details/configuration-parameters-all#parameter-sbc-oamp-default-entry-duration)
  * [Default maximum bandwidth](/configuration-details/configuration-parameters-all#parameter-sbc-oamp-default-maximum-bandwidth)
  * [Default maximum bandwidth](/configuration-details/configuration-parameters-all#parameter-sbc-oamp-default-maximum-bandwidth-pps)
  * [Default temporary ban duration](/configuration-details/configuration-parameters-all#parameter-sbc-oamp-default-temporary-ban-duration)
* Default values for SIP rules
  * [Default entry duration](/configuration-details/configuration-parameters-all#parameter-sbc-sip-default-entry-duration)
  * [Default maximum bandwidth](/configuration-details/configuration-parameters-all#parameter-sbc-sip-default-maximum-bandwidth)
  * [Default maximum bandwidth](/configuration-details/configuration-parameters-all#parameter-sbc-sip-default-maximum-bandwidth-pps)
  * [Default temporary ban duration](/configuration-details/configuration-parameters-all#parameter-sbc-sip-default-temporary-ban-duration)
* Default values for SIGTRAN rules
  * [Default entry duration](/configuration-details/configuration-parameters-all#parameter-sbc-sigtran-default-entry-duration)
  * [Default maximum bandwidth](/configuration-details/configuration-parameters-all#parameter-sbc-sigtran-default-maximum-bandwidth)
  * [Default maximum bandwidth](/configuration-details/configuration-parameters-all#parameter-sbc-sigtran-default-maximum-bandwidth-pps)
  * [Default temporary ban duration](/configuration-details/configuration-parameters-all#parameter-sbc-sigtran-default-temporary-ban-duration)
* Default values for H.248 rules
  * [Default entry duration](https://prosbcdocs.telcobridges.com/configuration-details/configuration-by-web-portal-category/system-settings/pages/MExpA9KQ1OYkRLRnmtUE#parameter-sbc-h.248-default-entry-duration)
  * [Default maximum bandwidth](https://prosbcdocs.telcobridges.com/configuration-details/configuration-by-web-portal-category/system-settings/pages/MExpA9KQ1OYkRLRnmtUE#parameter-sbc-h.248-default-maximum-bandwidth)
  * [Default maximum bandwidth](https://prosbcdocs.telcobridges.com/configuration-details/configuration-by-web-portal-category/system-settings/pages/MExpA9KQ1OYkRLRnmtUE#parameter-sbc-h.248-default-maximum-bandwidth-pps)
  * [Default temporary ban duration](https://prosbcdocs.telcobridges.com/configuration-details/configuration-by-web-portal-category/system-settings/pages/MExpA9KQ1OYkRLRnmtUE#parameter-sbc-h.248-default-temporary-ban-duration)


# Create Session Border Gateway Access Control List (ACL) Filters

To customize the actions of a firewall rule, you can add a filter to the rule.

1-Click ACL in the navigation panel.

\ <br>

<figure><img src="https://docs.telcobridges.com/w/images/9/90/ACL_0.png" alt=""><figcaption></figcaption></figure>

2-Select a firewall rule.

\ <br>

<figure><img src="https://docs.telcobridges.com/w/images/8/82/Sbc_Filter_0.png" alt=""><figcaption></figcaption></figure>

\
3-To define what the rule will do, click Create New Filter.

Note: The Create New Filter option is available when you create a new Firewall rule and have not yet created a filter. Otherwise, you can select the existing filter to edit it.

\ <br>

<figure><img src="https://docs.telcobridges.com/w/images/a/a2/Sbc_Rule_2a.png" alt=""><figcaption></figcaption></figure>

2-Enter values for the filter.

* Click Create

\ <br>

<figure><img src="https://docs.telcobridges.com/w/images/2/2b/Sbc_Rule_3.png" alt=""><figcaption></figcaption></figure>

\
To change the priority of an access rule, use the arrow icons.

* To increase the priority of an access rule, use either the double or single arrow [![](https://docs.telcobridges.com/w/images/2/29/Sbc_Rule_6.png)](https://docs.telcobridges.com/wiki/File:Sbc_Rule_6.png) to move the rule up by one position, or to the top of the list.
* To decrease the priority of an access rule, use either the double or single arrow [![](https://docs.telcobridges.com/w/images/a/ac/Sbc_Rule_7.png)](https://docs.telcobridges.com/wiki/File:Sbc_Rule_7.png) to move the rule down by one position, or to the bottom of the list.

\
Position of sample rule before it is moved

&#x20;\ <br>

<figure><img src="https://docs.telcobridges.com/w/images/f/f1/Sbc_Rule_4.png" alt=""><figcaption></figcaption></figure>

Position of sample rule after it is moved

&#x20;\ <br>

<figure><img src="https://docs.telcobridges.com/w/images/6/68/Sbc_Rule_5.png" alt=""><figcaption></figcaption></figure>

### List all ACLs

You can use this command on the console to list all ACL entries:

```
tbstatus /firewall/host/entry/entrylist
```

### List of Parameters

SBC Filter

* [Name](https://docs.telcobridges.com/wiki/Parameter:_SBC_Filter_Name)
* [IP Interface](https://docs.telcobridges.com/wiki/Parameter:_SBC_Filter_IP_Interface)
* [Protocol](https://docs.telcobridges.com/wiki/Parameter:_SBC_Filter_Protocol)
* [Source IP](https://docs.telcobridges.com/wiki/Parameter:_SBC_Filter_Source_IP)
* [Source Netmask](https://docs.telcobridges.com/wiki/Parameter:_SBC_Filter_Source_Netmask)
* [Source Port](https://docs.telcobridges.com/wiki/Parameter:_SBC_Filter_Source_Port)
* [Destination IP](https://docs.telcobridges.com/wiki/Parameter:_SBC_Filter_Destination_IP)
* [Destination Netmask](https://docs.telcobridges.com/wiki/Parameter:_SBC_Filter_Destination_Netmask)
* [Destination Port](https://docs.telcobridges.com/wiki/Parameter:_SBC_Filter_Destination_Port)
* [Override Default Thresholds](https://docs.telcobridges.com/wiki/Parameter:_SBC_Filter_Override_Default_Thresholds)


# Connecting to the Web Server and Logging on to the Web Portal

To begin configuring your Tmedia/Tdev system, log on to the Web Portal.\
1\. Connecting to the web server:

Using a web browser, connect to the web portal by typing the following in your address bar:

* http\://\[DEVICE HOST NAME]:12358

or,

* http\://\[DEVICE IP ADDRESS]:12358

2\. Logging on to the Web Portal:

Enter the user name and password. The default values for these parameters are:

* User Name: root
* Password: root

<figure><img src="https://docs.telcobridges.com/w/images/d/d5/Toolpack_Logon_Screen_0.png" alt=""><figcaption></figcaption></figure>


# Logging Off

When you are finished working in the Web Portal, it is recommended that you log out from your session. If you do not log out, the session between the Web Browser on your PC and the Web Portal remains active.

To log out from the Web Portal:

* Select Logout from the navigation panel.

<figure><img src="https://docs.telcobridges.com/w/images/thumb/7/77/Logout_Navigation_Panel_B.png/150px-Logout_Navigation_Panel_B.png" alt=""><figcaption></figcaption></figure>


# Modifying Security Settings

To modify the security settings:

1- Click Web Users in the navigation panel.

<br>

<figure><img src="https://docs.telcobridges.com/w/images/9/91/WebUsers_Navigation_Panel_A.png" alt=""><figcaption></figcaption></figure>

\
2- Select the Security Settings tab, and modify the desired setting.

<figure><img src="https://docs.telcobridges.com/w/images/3/32/Users_Security_Settings_B.png" alt=""><figcaption></figcaption></figure>

### List of Parameters

* [Enable password complexity](https://docs.telcobridges.com/wiki/Parameter:_Enable_password_complexity)
* [Session Timeout](https://docs.telcobridges.com/wiki/Parameter:_Session_Timeout)


# Creating Web User groups

One or more user groups can be created to define access rights, such as read only, read/write, or no access at all. Access rights can be assigned to all regions of the web portal or to specific areas.

\
To create a user group:

1- Click Web Users in the navigation panel.

<br>

<figure><img src="https://docs.telcobridges.com/w/images/9/91/WebUsers_Navigation_Panel_A.png" alt=""><figcaption></figcaption></figure>

\
2- Select the Web User Groups tab and click Create New Web User Groups, to add a new user group.

<br>

<figure><img src="https://docs.telcobridges.com/w/images/1/1f/WebUsers_CreateNewUserGroup_A.png" alt=""><figcaption></figcaption></figure>

\
3- Assign a name to the user group in the Name field.

<br>

<figure><img src="https://docs.telcobridges.com/w/images/4/4d/Users_AssignNewUserGroup_B.png" alt=""><figcaption></figcaption></figure>

\
4- Configure the access for the user group by one of the following two methods:

4a- Select an Authorization type, from the Apply All field , such as:

* Read
* Read/Write
* No access

This will apply the authorization to all regions of the web portal.

\
4b- Customize authorization and access individually by setting the authorization type in each web portal field.

<figure><img src="https://docs.telcobridges.com/w/images/a/a8/Users_CustomizeNewUserGroup_B.png" alt=""><figcaption></figcaption></figure>

\
5- Click Create.


# Creating Web Users

One or more users can be created and given access, which was previously defined by user groups. A user is given a name, a password, and assigned to a user group.

To create a user:

1- Click Web Users in the navigation panel.

<br>

<figure><img src="https://docs.telcobridges.com/w/images/9/91/WebUsers_Navigation_Panel_A.png" alt=""><figcaption></figcaption></figure>

\
2- Select the Web Users tab and click Create New Web User.

<br>

<figure><img src="https://docs.telcobridges.com/w/images/0/09/WebUsers_CreateNewUser_A.png" alt=""><figcaption></figcaption></figure>

\
3- Assign the following to the user:

* Name
* Password
* User Group

<figure><img src="https://docs.telcobridges.com/w/images/7/7d/WebUsers_AssignNewUser_A.png" alt=""><figcaption></figcaption></figure>

\
4- Click Create.

### List of Parameters

* [User Name](/configuration-details/configuration-parameters-all#parameter-user-name)
* [Password](/configuration-details/configuration-parameters-all#parameter-password)
* [Email](/configuration-details/configuration-parameters-all#parameter-email)
* [User Group](/configuration-details/configuration-parameters-all#parameter-user-name)

### How to Create/Update a route with Restful API

You can find how to create/modify a user with Restful API in the following link:

[Creating/Updating a User with Restful API](https://docs.telcobridges.com/wiki/ProSBC:Restful_API_User)


# Modifying Web User Permissions

The access permissions of web users can be modified in two different ways:

* Modify the permission of a single user: If you wish to modify the permissions of a single user, you can assign them to a group to which they are the sole member and then change the permissions of this group.
* Modify the permission of a group of users. If the change in permissions will affect more than one user, then change the permissions of the group to which they are assigned.

Important note

For the best practices regarding security and permissions, refer to [Users](https://docs.telcobridges.com/wiki/Users).

To reassign a user to a different group:

1- Click Web Users in the navigation panel.

<br>

<figure><img src="https://docs.telcobridges.com/w/images/9/91/WebUsers_Navigation_Panel_A.png" alt=""><figcaption></figcaption></figure>

\
2- Select the Web Users tab, followed by the user.

<br>

<figure><img src="https://docs.telcobridges.com/w/images/f/f4/Users_modify_single_B.png" alt=""><figcaption></figcaption></figure>

\
3- Assign the user to a different group with different permissions.

<figure><img src="https://docs.telcobridges.com/w/images/6/65/Users_modify_single2_B.png" alt=""><figcaption></figcaption></figure>

\
4- Click Save.

The user appears in the User list assigned to a different user group.

<figure><img src="https://docs.telcobridges.com/w/images/e/ed/Users_modify_single3_B.png" alt=""><figcaption></figcaption></figure>

<br>

To modify the permission of a user group:

1- Click Users in the navigation panel

<br>

<figure><img src="https://docs.telcobridges.com/w/images/f/fd/Users_Navigation_Panel_B.png" alt=""><figcaption></figcaption></figure>

\
2- Select the User Groups tab, followed by the user group.

<br>

<figure><img src="https://docs.telcobridges.com/w/images/7/7e/UserGroup_modify_B1.png" alt=""><figcaption></figcaption></figure>

\
3- Change one or more options of the group and click Save.

<br>

<figure><img src="https://docs.telcobridges.com/w/images/d/d0/UserGroup_modify_B2.png" alt=""><figcaption></figcaption></figure>


# Enabling and Disabling a User

One or more users can be disabled.

\
To disable a user:

1- Click Web Users in the navigation panel.

<br>

<figure><img src="https://docs.telcobridges.com/w/images/9/91/WebUsers_Navigation_Panel_A.png" alt=""><figcaption></figcaption></figure>

\
2- Select the Users tab, locate the user in the User list, and click Disable.

<br>

<figure><img src="https://docs.telcobridges.com/w/images/5/5c/Users_disable1_A.png" alt=""><figcaption></figcaption></figure>

\
The user is disabled in the User list.

<br>

<figure><img src="https://docs.telcobridges.com/w/images/a/a2/Users_disable2_A.png" alt=""><figcaption></figcaption></figure>

To enable a user:

1- Click Web Users in the navigation panel.

<br>

<figure><img src="https://docs.telcobridges.com/w/images/9/91/WebUsers_Navigation_Panel_A.png" alt=""><figcaption></figcaption></figure>

\
2- Select the Users tab, locate the disabled user in the User list, and click Enable.

The user is now enabled in the User list.

<br>

<figure><img src="https://docs.telcobridges.com/w/images/c/cf/Users_disable1_A1.png" alt=""><figcaption></figcaption></figure>


# Deleting a User

One or more users can be deleted.

\
To delete a user:

1- Click Web Users in the navigation panel.

<br>

<figure><img src="https://docs.telcobridges.com/w/images/9/91/WebUsers_Navigation_Panel_A.png" alt=""><figcaption></figcaption></figure>

\
2- Select the Web Users tab, locate the user in the User list, and click Delete.

<br>

<figure><img src="https://docs.telcobridges.com/w/images/3/3f/Users_delete1_B.png" alt=""><figcaption></figcaption></figure>

\
3- Click OK to confirm the deletion of a user.

<br>

<figure><img src="https://docs.telcobridges.com/w/images/a/a2/Users_delete2a_B.png" alt=""><figcaption></figcaption></figure>

\
The user is removed from the User list.

<br>

<figure><img src="https://docs.telcobridges.com/w/images/5/5f/Users_delete3_B.png" alt=""><figcaption></figcaption></figure>


# Accessing Audit Logs

o access the audit logs:

1-Click Logs in the navigation panel.

<figure><img src="https://docs.telcobridges.com/w/images/e/e8/Audit_0_A.png" alt=""><figcaption></figcaption></figure>

\
An unfiltered view of the Audit Logs is displayed.

<figure><img src="https://docs.telcobridges.com/w/images/f/f5/Audit_1_A.png" alt=""><figcaption></figcaption></figure>

\
2- To filter the view of audit logs based upon certain criteria, fill in one or more query fields.

* Click Apply

<figure><img src="https://docs.telcobridges.com/w/images/9/9c/Audit_2_A.png" alt=""><figcaption></figcaption></figure>

\
The filtered view of the audit logs is displayed.

<figure><img src="https://docs.telcobridges.com/w/images/7/71/Audit_3_A.png" alt=""><figcaption></figcaption></figure>

\
3- Click Show to view the specific changes of a log entry.

<figure><img src="https://docs.telcobridges.com/w/images/c/cd/Audit_4_A.png" alt=""><figcaption></figcaption></figure>


# Activating the Configuration

Changes made to the configurations are stored in the OAM\&P Configuration and Logging database. Any changes to the configuration must be activated, in order for them to be used by the system. This is done at the system level and accessed from the navigation panel.

Note: To activate a configuration, you must be an Admin user or a user with write access to the System menu.

To activate a system configuration:

1\. Select System from the navigation panel.

<figure><img src="https://docs.telcobridges.com/w/images/3/38/Systems_Navigation_Panel_B.png" alt=""><figcaption></figcaption></figure>

<br>

2\. To activate the configuration, click Activate.

Note: Make certain that the Lock active configuration box is unchecked. Failure to do so will prevent the configuration from being saved.

<figure><img src="https://docs.telcobridges.com/w/images/a/ae/Toolpack_Editing_System_B1.png" alt=""><figcaption></figcaption></figure>

\
3\. Verify that an activation confirmation message is displayed. The system will remind you to back up your database when you are done configuring (at top of screen):

<br>

<figure><img src="https://docs.telcobridges.com/w/images/e/e5/Toolpack_System_Edited_B2.png" alt=""><figcaption></figcaption></figure>


# Configuring a Web Portal Profile

Web profiles enables regions of the Web Portal to be hidden from view. Changes to the web profile applies to all users of the web portal.

A web portal profile is applied at the system configuration level. If for example, the basic-sip configuration does not require ISDN signalling, web profiles can remove ISDN as an accessible option from the web portal navigation panel.

The following procedure illustrates this example.

\
To configure a web profile:

1- Click Configurations in the navigation panel

<br>

<figure><img src="https://docs.telcobridges.com/w/images/7/71/WebProfile_Navigation_Panel_B.png" alt=""><figcaption></figcaption></figure>

\
2- Select the desired configuration from the Active configuration list.

<br>

<figure><img src="https://docs.telcobridges.com/w/images/8/87/WebProfile_EditConfiguration_Tsbc_0.png" alt=""><figcaption></figcaption></figure>

\
3- Click Web Profiles to modify the web portal profile..

<br>

<figure><img src="https://docs.telcobridges.com/w/images/6/63/WebProfile_Select_Tsbc_1.png" alt=""><figcaption></figcaption></figure>

\
4- Uncheck/clear any web portal options that you do not wish to see.

5- Click Save. The web portal option is immediately removed from the navigation panel.


# Configuring the Date, Time, Timezone and NTP servers

1-Click Services in the navigation panel.

\ <br>

<figure><img src="https://docs.telcobridges.com/w/images/c/c5/Snmp_cfg_A_0.png" alt=""><figcaption></figcaption></figure>

2-Select the Timezone from where the system is installed.\
3-Select NTP in Time Setting. You can also set the date manually. If you do so, select MANUAL and enter the date and time.\
4- Click Save.\
5-Change the NTP servers if needed. There are default value NTP servers configured. Internet access is required to sync with external NTP servers.<br>

\ <br>

<figure><img src="https://docs.telcobridges.com/w/images/d/db/Date_Time_main.png" alt=""><figcaption></figcaption></figure>

### List of Parameters

* [Timezone](https://docs.telcobridges.com/wiki/Parameter:_Timezone)
* [Time Setting](https://docs.telcobridges.com/wiki/Parameter:_Time_Setting)

Advanced Parameters

* [IP Header Type of Service (ToS)](https://docs.telcobridges.com/wiki/Parameter:_IP_Header_Type_of_Service_\(ToS\))


# Configuring the DNS

1-Click Services in the navigation panel.

\ <br>

<figure><img src="https://docs.telcobridges.com/w/images/c/c5/Snmp_cfg_A_0.png" alt=""><figcaption></figcaption></figure>

2- DNS can be managed by an administrator on the Linux host. You can use the [tbchangeip](https://docs.telcobridges.com/wiki/TMG:Change_Management_IP_Address) command to do this. DNS services can also be managed by the Web portal. To do so, select Managed by Web.\
3- Add the DNS servers IP addresses in the Name Server box and add them to the list using the left double arrow <<.\
4- You can do the same with Domain names<br>

\ <br>

<figure><img src="https://docs.telcobridges.com/w/images/b/b1/DNS_Services_main.png" alt=""><figcaption></figcaption></figure>

### List of Parameters

* [Managed by Web](/configuration-details/configuration-parameters-all#parameter-managed-by-web)

\
Advanced Parameters

* [IP Header Type of Service (ToS)](/configuration-details/configuration-parameters-all#parameter-packet-network-type-of-service)


# Create HTTP Service

To create a new HTTP service:

1\. Select Services from the navigation panel.

<figure><img src="https://docs.telcobridges.com/w/images/1/1e/HTTP_Service_Panel.PNG" alt=""><figcaption></figcaption></figure>

\
2\. Select the HTTP tab.

* Click Create New HTTP Service.

<figure><img src="https://docs.telcobridges.com/w/images/e/e1/HTTP_Service_Tab.PNG" alt=""><figcaption></figcaption></figure>

3\. Edit the various field according to your preferences.

* Enter a Name for the new HTTP service.
* Select a Port for the HTTP service.
* If you wish to restrict the IP addresses from where the Web Portal is accessed, select a specific IP interface, otherwise choose ANY.
* If you would like to use HTTPS when connecting to the Web Portal, select Use HTTPS.
* Click Create.

<figure><img src="https://docs.telcobridges.com/w/images/4/4b/HTTP_Service_Create.PNG" alt=""><figcaption></figcaption></figure>

4\. Apply your changes to the configuration by [activating the new configuration](/configuration-details/configuration-by-web-portal-category/system-settings/activating-the-configuration)

### List of Parameters

* [Name](/configuration-details/configuration-parameters-all#parameter-name)
* [Port](/configuration-details/configuration-parameters-all#parameter-port)
* [IP interfaces to allow](/configuration-details/configuration-parameters-all#parameter-ip-interfaces-to-allow)
* [Use HTTPS](/configuration-details/configuration-by-web-portal-category/system-settings/use-https-service)

Advanced Parameters

* [IP Header Type of Service (ToS)](/configuration-details/configuration-parameters-all#parameter-packet-network-type-of-service)


# Use HTTPS service

If you create a HTTP service using HTTPS, be aware of the following:

### Initial connection

The web server hosting the [Web Portal](/appendices/appendix-a-glossary/glossary-web-portal) does not authenticate itself. As a result, a first connection to a Web Portal using HTTPS will display a message indicating that the security certificate is invalid. This is normal and does not affect encryption security. To proceed, simply add an exception to your web browser to access the Web Portal with HTTPS.

### URL

When connecting with HTTPS to the Web Portal, the prefix https\:// must be explicitly written in the URL, otherwise the connection will try to use HTTP and fail to connect.




---

[Next Page](/llms-full.txt/1)