SBC-SW:Networking - Revision history

Luc Morissette at 16:40, 12 December 2018

2018-12-12T16:40:30Z

Cbilodeau: moved TSBC-SW:Networking to SBC-SW:Networking: change Tsbc to sbc

2017-11-08T16:43:38Z

moved TSBC-SW:Networking to SBC-SW:Networking: change Tsbc to sbc

Cboulanger: typo

2017-05-01T20:46:07Z

typo

Cboulanger: Added network discovery

2017-05-01T20:44:48Z

Added network discovery

Cboulanger: draft

2017-05-01T19:01:05Z

draft

Cboulanger: draft

2017-05-01T18:51:16Z

draft

Cboulanger: draft

2017-05-01T18:41:10Z

draft

Cboulanger at 18:09, 1 May 2017

2017-05-01T18:09:25Z

Cboulanger: Draft

2017-05-01T17:31:03Z

Draft

Cboulanger: Create empty page

2017-04-25T13:54:07Z

Create empty page

New page

← Older revision		Revision as of 16:40, 12 December 2018
Line 1:		Line 1:
−	{{DISPLAYTITLE:~~TSBC-SW~~:Networking}}	+	{{DISPLAYTITLE:FreeSBC:Networking}}

	== Requirements ==		== Requirements ==

@@ Line 53: / Line 53: @@
 Once all networks have been physically (or virtually) connected to the TSBC-SW instance, the system can be started.  Upon first bootup (or after an operator initiated 'network device role' reset), the TSBC-SW web portal will show a network device assignation page.   As the TSBC-SW cannot guess what type of traffic the operator wants to process on any given network, this page is used to identify the role of each detected devices.  As described above, the role can be any of the following three: control, management or VoIP traffic (named LAN/WAN).   Once the role is selected, the operator can enter a name for each.  Every configured/detected physical network device will then appear as a 'physical port' in the 'IP Interace' tab in the web portal.
-The operator can click on the '+' sign to get more information about the network device.  These information are helpful to match detected networks with the real network based on these characteristics (IP, driver type, etc).
+The operator can click on the '+' sign to get more information about a specific network device.  These information are helpful to match detected networks with the real network based on these characteristics (IP, driver type, etc).
 [[File:network_discovery.png‎‎|500px]]

@@ Line 51: / Line 51: @@
 == Network device discovery ==
-Once all networks have been physically (or virtually) connected to the TSBC-SW instance, the system can be startup.  Upon first bootup or after an operator initiated 'network device role' reset, the TSBC-SW web portal will show a configuration page
+Once all networks have been physically (or virtually) connected to the TSBC-SW instance, the system can be started.  Upon first bootup (or after an operator initiated 'network device role' reset), the TSBC-SW web portal will show a network device assignation page.   As the TSBC-SW cannot guess what type of traffic the operator wants to process on any given network, this page is used to identify the role of each detected devices.  As described above, the role can be any of the following three: control, management or VoIP traffic (named LAN/WAN).   Once the role is selected, the operator can enter a name for each.  Every configured/detected physical network device will then appear as a 'physical port' in the 'IP Interace' tab in the web portal.
 [[File:network_discovery.png‎‎|500px]]

← Older revision		Revision as of 19:01, 1 May 2017
Line 50:		Line 50:

	== Network device discovery ==		== Network device discovery ==
		+
		+	Once all networks have been physically (or virtually) connected to the TSBC-SW instance, the system can be startup. Upon first bootup or after an operator initiated 'network device role' reset, the TSBC-SW web portal will show a configuration page
		+
		+
		+	[[File:network_discovery.png‎‎\|500px]]

@@ Line 17: / Line 17: @@
 === Redundancy ===
-==== Standalone without transcoding ===
+==== Standalone without transcoding ====
 In this configuration, the TSBC-SW does not have any backup instances nor is using any transcoding equipment.  Thus, the only networks needed are the management network along with one or many VoIP networks to carry the data streams.  In the example below, the TSBC-SW was deployed with one "public" network named 'wan0' and one "private" network named 'lan0'.
@@ Line 25: / Line 25: @@
 ==== 1+1 without transcoding ====
-In this configuration, the TSBC-SW system is deployed with two instances providing an active/standby redundancy scheme without any transcoding equipment.  In addition to the regular networks required shown in the previous example (management and VoIP networks), the two instances need access to two control separate networks allowing to exchange check-pointing information.  Although a single control network is sufficient to achieve the 1+1 function, it is not recommended by TelcoBridges unless the operator fully controls all network segments and can guarantee it can never fail at both the physical and routing (IP) layer.  In most cases, having two separate control networks going through independent network devices, switches and routers is the only way to ensure 'no single point of failure'.
+In this configuration, the TSBC-SW system is deployed with two instances providing an active/standby redundancy scheme without any transcoding equipment.  In addition to the regular networks required shown in the previous example (management and VoIP networks), the two instances need access to two control separate networks allowing to exchange check-pointing information.  These networks are private to the TSBC-SW and should never be shared or be visible to non-TelcoBridges equipment.
 [[File:Tsbc-sw-1p1-notrans.png‎]]
@@ Line 31: / Line 33: @@
 === Transcoding ===
-The TSBC-SW session border controller should be the only equipment facing the different networks to ensure proper protection and monitoring. In that sense, any transcoding units deployed (TSBC-HW-TRANS) will never be visible from data networks handled by the SBC.
+The TSBC-SW session border controller should be the only equipment facing the different networks to ensure proper protection and monitoring. In that sense, any transcoding units deployed (TSBC-HW-TRANS) will never be visible from data networks handled by the SBC.  The TSBC-SW will require three internal networks to reach the transcoding units: two control networks and one media network.  The control networks are the same as those deployed for redundant systems while the media network will contain all the VoIP traffic coming in or out of the transcoding units.
 [[File:Transcoding.png]]
 ==== Standalone with transcoding ====
 [[File:Tsbc-sw-standalone-withtrans.png‎‎]]
 ==== 1+1 with transcoding ====
 [[File:Tsbc-sw-1p1-withtrans.png‎‎]]
 == Network device discovery ==

← Older revision		Revision as of 18:09, 1 May 2017
Line 1:		Line 1:
	{{DISPLAYTITLE:TSBC-SW:Networking}}		{{DISPLAYTITLE:TSBC-SW:Networking}}
		+
		+	[[File:Tsbc-sw-minimal_networks.png‎]]
		+	[[File:Tsbc-sw-any-networks.png‎‎]]
		+	[[File:Tsbc-sw-standalone-notrans.png‎]]
		+	[[File:Tsbc-sw-standalone-withtrans.png‎‎]]
		+	[[File:Tsbc-sw-1p1-notrans.png‎]]
		+	[[File:Tsbc-sw-1p1-withtrans.png‎‎]]

	== Requirements ==		== Requirements ==

← Older revision		Revision as of 17:31, 1 May 2017
Line 1:		Line 1:
	{{DISPLAYTITLE:TSBC-SW:Networking}}		{{DISPLAYTITLE:TSBC-SW:Networking}}
		+
		+	== Requirements ==
		+
		+	== Network configurations ==
		+
		+	=== Standalone without transcoding ===
		+
		+	=== Standalone with transcoding ===
		+
		+
		+	=== 1+1 without transcoding ===
		+
		+
		+	=== 1+1 with transcoding ===