TSBC-SW:WebPortal:Initial Configuration

From TBwiki
(Difference between revisions)
Jump to: navigation, search
 
(47 intermediate revisions by 3 users not shown)
Line 1: Line 1:
=== '''''Applies to version(s): v3.0''''' ===
+
__FORCETOC__
{{DISPLAYTITLE:FreeSBC Initial Configuration}}
+
<div style="font-size: 132%;"><span style="color:#00538a">'''''Applies to version(s): v3.0, v3.1'''''</span></div>
Initial configuration of the FreeSBC is done through a web browser (Chrome, Firefox or other).
+
{{DISPLAYTITLE:ProSBC/FreeSBC Initial Configuration}}
Before starting, you need the following information:
+
* '''Product key''': it has the format VTB-XXX-XXXX. If you do not have this key, please contact [mailto:sales@telcobridges.com our sales team]
+
* '''Hostname''' of the unit. It is important to set the hostname correctly and not modify it later, otherwise you will need a new license
+
* Is the system used as a '''standalone''' unit or is it used in a '''Primary/Secondary''' configuration?
+
* Does the system require '''external transcoding'''? As an example, G.711 to G.729a transcoding
+
* Role of each of the '''network interfaces'''
+
Then, follow the procedure below.
+
  
== Initial configuration of the FreeSBC ==
+
== Before You Begin ==
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: <br/> http://192.168.178.30:12358 <br/>  
+
 
2- You will get the SBC Configuration Wizard and click on Continue <br/>  
+
The initial configuration of the SBC is carried out by accessing a configuration wizard in a web browser (Chrome, Firefox or other).
[[File:TSBC_WebPortal_Configuration_wizard.jpg|600px]] <br/> <br/>
+
Before you begin, you must have the following information on hand:
3- You need to accept the EULA agreement<br/>
+
* '''Product key''': In the following VTB-XXX-XXXX format. If you do not have this key, please go to our [http://www2.telcobridges.com/ProSBCDownload ProSBC Download site] .
[[Image:TSBC_SW_EULA_agreement_1.png|600px]] <br/> <br/>
+
* '''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 or FreeSBC ==
 +
 
 +
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: <br/> http://192.168.178.30:12358 <br/><br/>  
 +
2- A Configuration Wizard is displayed.
 +
* Click '''Continue''' <br/>  
 +
[[File:1_recovery_welcome_A.png|700px]] <br/> <br/>
 +
3- Accept the EULA agreement<br/>
 +
[[Image:TSBC_SW_EULA_agreement_1.png|700px]] <br/> <br/>
 
4- Enter your activation key and hostname <br/>
 
4- Enter your activation key and hostname <br/>
[[Image:TSBC_SW_Enter_activation_key_1.png|600px]] <br/> <br/>
+
Note: You do not need to enter the host name for AWS. <br/>
5- Select the configuration of your SBC - either standalone, or in a Primary/Secondary configuration<br/>
+
[[Image:TSBC_SW_Enter_activation_key_1.png|700px]] <br/> <br/>
[[Image:TSBC_SW_standalone_1.png|600px]] <br/> <br/>
+
5- Enter your SSH and WEB root password <br/>
6- 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.<br/>
+
Note: You do not need to enter the SSH password for AWS. <br/>
[[Image:TSBC_SW_transcoding_1.png|600px]] <br/> <br/>
+
[[Image:TSBC-SW Enter SSH WEB Password.png|700px]] <br/> <br/>
7- Here you will choose the role of the network adapters in the system here is a short description of each type:<br/>
+
6- Select the configuration of your SBC. Either standalone, or in a Primary/Secondary configuration<br/>
 +
Note: This does not apply for AWS. <br/>
 +
[[Image:TSBC_SW_standalone_1.png|700px]] <br/> <br/>
 +
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.<br/>
 +
Note: This does not apply for AWS. <br/>
 +
[[Image:TSBC_SW_transcoding_1.png|700px]] <br/> <br/>
 +
8- In this window, you define the role of the network adapters in the system. The following is a short description of each type:<br/>
 
* mgmt: Used for management of the system (suggested name: mgmt0)
 
* mgmt: Used for management of the system (suggested name: mgmt0)
 
* ctrl0: Used for communication with the external transcoding devices (suggested name: ctrl0)
 
* ctrl0: Used for communication with the external transcoding devices (suggested name: ctrl0)
Line 28: Line 41:
 
* LAN/WAN: SIP/RTP access to private network (suggested name: LAN0) or public network (suggested name: WAN0).
 
* LAN/WAN: SIP/RTP access to private network (suggested name: LAN0) or public network (suggested name: WAN0).
  
You need to configure all IP interfaces. In case of doubt, configure them as management interfaces.<br/>
+
You must configure all IP interfaces. If you are not sure, configure them as management interfaces.<br/>
[[Image:TSBC_SW_choose_LAN_interface_role_1.png|600px]] <br/> <br/>
+
[[Image:2_Recovery_before_bonding_A.png|750px]] <br/> <br/>
8- You can select the "+" sign to get more information on this interface<br/>
+
 
 +
Note: Select the "+" sign to acces more information about an interface.<br/>
 
[[Image:TSBC_SW_choose_LAN_interface_role_2.png|600px]] <br/> <br/>
 
[[Image:TSBC_SW_choose_LAN_interface_role_2.png|600px]] <br/> <br/>
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)  
+
 
<br/>[[Image:Initial_screen_Match_MAC_1.png|600px]][[File:Network_adapters_MAC_Address_primary_1.png|800px]]<br/>
+
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) <br/>
9- Once completed, you will be asked get the license seed of this unit to allow for license installation. Please go here for instructions: [[Toolpack:Retreiving_a_License_TSBC_A]]<br/>
+
[[Image:Initial_screen_Match_MAC_1.png|600px]][[File:Network_adapters_MAC_Address_primary_1.png|800px]]<br/><br/>
To get help, please contact [mailto:support@telcobridges.com TelcoBridges TB Support].  
+
 
 +
9- To add an Ethernet Bonding, click '''Add Bonding'''.<br/>
 +
[[Image:2_Recovery_before_bonding_ClickAddBondingA.png|750px]] <br/> <br/>
 +
 
 +
10- Enter a name for the Bonding Pair, followed by the LAN/WAN1 and LAN/WAN 2.
 +
*When you are done, click '''Continue'''.<br/>
 +
[[Image:3_Recovery_after_bonding_A.png|750px]] <br/> <br/>
 +
 
 +
11- A '''Confirmation''' window is displayed.
 +
*If you are satisfied with the configuration, click '''Confirm'''. <br/>
 +
[[Image:4_Recovery_confirm_bonding_A.png|700px]] <br/> <br/>
 +
 
 +
12- A warning message is displayed alerting you to the possible interruption of the IP interfaces when the change is applied.
 +
*Click '''OK'''. <br/>
 +
[[Image:5_Recovery_Warning_end_confirm_bonding_A.png|700px]] <br/> <br/>
 +
 
 +
13- After the bonding configuration is complete, you must reboot the system.<br/>
 +
[[Image:6_Following_bonding_configuration_warning_reboot_is_required_A.png|700px]] <br/> <br/>
 +
 
 +
== Configure the IP Interface of the Ethernet Bonded Port ==
 +
 
 +
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.<br/>
 +
[[Image:7_IP_Interface_NavBar_A.png]] <br/> <br/>
 +
 
 +
2-Select the '''IP Interfaces''' tab.
 +
*Click '''Create New IP Interface'''.<br/>
 +
[[Image:7_Need_to_configure_VLAN_port_and_ip_inetrface_to_use_created_bonding_Before_A.png|700px]] <br/> <br/>
 +
 
 +
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.<br/>
 +
[[Image:7_Need_to_configure_VLAN_port_and_ip_interface_to_use_created_bonding_After_A.png|700px]] <br/> <br/>
 +
 
 +
 
 +
Note: Once the configuration is completed, you will be asked retrieve the license seed of this unit to allow for the installation of the license. <br/>
 +
To learn how to do this, refer tos: [[Toolpack:Retreiving_a_License_TSBC_A| Retrieving a License for SBC Units]]<br/>
 +
To get help, please contact [mailto:support@telcobridges.com TelcoBridges TB Support].  
  
 
<br>
 
<br>

Latest revision as of 15:10, 30 March 2020

Applies to version(s): v3.0, v3.1


Contents

Before You Begin

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 .
  • 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 or FreeSBC

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

2- A Configuration Wizard is displayed.

  • Click Continue

1 recovery welcome A.png

3- Accept the EULA agreement
TSBC SW EULA agreement 1.png

4- Enter your activation key and hostname
Note: You do not need to enter the host name for AWS.
TSBC SW Enter activation key 1.png

5- Enter your SSH and WEB root password
Note: You do not need to enter the SSH password for AWS.
TSBC-SW Enter SSH WEB Password.png

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

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.
TSBC SW transcoding 1.png

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.
2 Recovery before bonding A.png

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

TSBC SW choose LAN interface role 2.png

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)  

Initial screen Match MAC 1.pngNetwork adapters MAC Address primary 1.png

9- To add an Ethernet Bonding, click Add Bonding.
2 Recovery before bonding ClickAddBondingA.png

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

  • When you are done, click Continue.

3 Recovery after bonding A.png

11- A Confirmation window is displayed.

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

4 Recovery confirm bonding A.png

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

  • Click OK.

5 Recovery Warning end confirm bonding A.png

13- After the bonding configuration is complete, you must reboot the system.
6 Following bonding configuration warning reboot is required A.png

Configure the IP Interface of the Ethernet Bonded Port

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.
7 IP Interface NavBar A.png

2-Select the IP Interfaces tab.

  • Click Create New IP Interface.

7 Need to configure VLAN port and ip inetrface to use created bonding Before A.png

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.

7 Need to configure VLAN port and ip interface to use created bonding After A.png


Note: Once the configuration is completed, you will be asked retrieve the license seed of this unit to allow for the installation of the license. 
To learn how to do this, refer tos: Retrieving a License for SBC Units
To get help, please contact TelcoBridges TB Support.


Personal tools