FreeSBC:Transcoding and Network Setup - Revision history

Allyntree: Minor. Just changed to active voice. Nothing at all major

2024-06-28T21:18:18Z

Minor. Just changed to active voice. Nothing at all major

← Older revision		Revision as of 17:18, 28 June 2024
Line 3:		Line 3:
	== Requirements ==		== Requirements ==

	ProSBC supports ~~'''~~software~~'''~~ and ~~'''~~hardware~~'''~~ transcoding see [[ProSBC_Transcoding_Solution\|ProSBC transcoding solution]]. <br>		ProSBC supports software and hardware transcoding see [[ProSBC_Transcoding_Solution\|ProSBC transcoding solution]]. <br>
	In the case ~~were '''~~software~~'''~~ transcoding is needed, you need to configure the ProSBC to allow this. ~~<br>~~		In the case in which software transcoding is needed, you need to configure the ProSBC to allow this.
	In the case were ~~'''~~hardware~~'''~~ transcoding is needed, ProSBC requires ~~and~~ external hardware transcoding unit supplied by TelcoBridges to do transcoding between different codecs used in SIP/RTP communications. It is also used to play announcements or record media. ~~Please see~~ [[ProSBC]] for more information on transcoding unit.		In the case were hardware transcoding is needed, ProSBC requires an external hardware transcoding unit supplied by TelcoBridges to do transcoding between different codecs used in SIP/RTP communications. It is also used to play announcements or record media. See [[ProSBC]] for more information on transcoding unit.

	ProSBC with transcoding deployments require a minimum of three networks for initial configuration. The first network will be used as a local management interface to access the instance using the web portal (HTTP/HTTPS) and SSH access. The second network ~~will transport~~ the actual incoming and outgoing VoIP streams (signaling and media) that the ProSBC and transcoding unit ~~will~~ process. The third network ~~will be~~ used as a control interface connecting to another host in ProSBC 1+1 configuration and transcoding unit in the system for control purpose.		ProSBC with transcoding deployments require a minimum of three networks for initial configuration. The first network will be used as a local management interface to access the instance using the web portal (HTTP/HTTPS) and SSH access. The second network transports the actual incoming and outgoing VoIP streams (signaling and media) that the ProSBC and transcoding unit process. The third network is used as a control interface connecting to another host in ProSBC 1+1 configuration and transcoding unit in the system for control purpose.

	[[File:Tsbc-sw-any-networks_with_transcoding_V2.png\|700px]]		[[File:Tsbc-sw-any-networks_with_transcoding_V2.png\|700px]]
Line 17:		Line 17:
	=== Transcoding ===		=== Transcoding ===

	The ProSBC 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 ProSBC 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.		The ProSBC session border controller should be the only equipment facing various 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 ProSBC 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 contains all VoIP traffic coming in or out of the transcoding units.

	[[File:Transcoding.png]]		[[File:Transcoding.png]]

Luc Morissette at 21:09, 28 June 2024

2024-06-28T21:09:32Z

← Older revision		Revision as of 17:09, 28 June 2024
Line 4:		Line 4:

	ProSBC supports '''software''' and '''hardware''' transcoding see [[ProSBC_Transcoding_Solution\|ProSBC transcoding solution]]. <br>		ProSBC supports '''software''' and '''hardware''' transcoding see [[ProSBC_Transcoding_Solution\|ProSBC transcoding solution]]. <br>
	In the case were '''software''' transcoding is needed, you need to configure the ProSBC to allow this.		In the case were '''software''' transcoding is needed, you need to configure the ProSBC to allow this. <br>
	In the case were '''hardware''' transcoding is needed, ProSBC requires and external hardware transcoding unit supplied by TelcoBridges to do transcoding between different codecs used in SIP/RTP communications. It is also used to play announcements or record media. Please see [[ProSBC]] for more information on transcoding unit.		In the case were '''hardware''' transcoding is needed, ProSBC requires and external hardware transcoding unit supplied by TelcoBridges to do transcoding between different codecs used in SIP/RTP communications. It is also used to play announcements or record media. Please see [[ProSBC]] for more information on transcoding unit.

Luc Morissette at 21:09, 28 June 2024

2024-06-28T21:09:16Z

← Older revision		Revision as of 17:09, 28 June 2024
Line 3:		Line 3:
	== Requirements ==		== Requirements ==

	ProSBC supports software and hardware transcoding see [[ProSBC_Transcoding_Solution\|ProSBC transcoding solution]]. <br>		ProSBC supports '''software''' and '''hardware''' transcoding see [[ProSBC_Transcoding_Solution\|ProSBC transcoding solution]]. <br>
	In the case were software transcoding is needed, you need to configure the ProSBC to allow this.		In the case were '''software''' transcoding is needed, you need to configure the ProSBC to allow this.
	In the case were hardware transcoding is needed, ProSBC requires and external hardware transcoding unit supplied by TelcoBridges to do transcoding between different codecs used in SIP/RTP communications. It is also used to play announcements or record media. Please see [[ProSBC]] for more information on transcoding unit.		In the case were '''hardware''' transcoding is needed, ProSBC requires and external hardware transcoding unit supplied by TelcoBridges to do transcoding between different codecs used in SIP/RTP communications. It is also used to play announcements or record media. Please see [[ProSBC]] for more information on transcoding unit.

	ProSBC with transcoding deployments require a minimum of three networks for initial configuration. The first network will be used as a local management interface to access the instance using the web portal (HTTP/HTTPS) and SSH access. The second network will transport the actual incoming and outgoing VoIP streams (signaling and media) that the ProSBC and transcoding unit will process. The third network will be used as a control interface connecting to another host in ProSBC 1+1 configuration and transcoding unit in the system for control purpose.		ProSBC with transcoding deployments require a minimum of three networks for initial configuration. The first network will be used as a local management interface to access the instance using the web portal (HTTP/HTTPS) and SSH access. The second network will transport the actual incoming and outgoing VoIP streams (signaling and media) that the ProSBC and transcoding unit will process. The third network will be used as a control interface connecting to another host in ProSBC 1+1 configuration and transcoding unit in the system for control purpose.

Luc Morissette: Added a mention to specify hardware transcoding

2024-06-28T21:08:30Z

Added a mention to specify hardware transcoding

← Older revision		Revision as of 17:08, 28 June 2024
Line 3:		Line 3:
	== Requirements ==		== Requirements ==

	ProSBC requires external hardware transcoding unit supplied by ~~Telcobridges~~ to do transcoding between different codecs used in SIP/RTP communications. It is also used to play ~~and~~ record. Please see [[ProSBC]] for more information on transcoding unit.		ProSBC supports software and hardware transcoding see [[ProSBC_Transcoding_Solution\|ProSBC transcoding solution]]. <br>
			In the case were software transcoding is needed, you need to configure the ProSBC to allow this.
			In the case were hardware transcoding is needed, ProSBC requires and external hardware transcoding unit supplied by TelcoBridges to do transcoding between different codecs used in SIP/RTP communications. It is also used to play announcements or record media. Please see [[ProSBC]] for more information on transcoding unit.

	ProSBC with transcoding deployments require a minimum of three networks for initial configuration. The first network will be used as a local management interface to access the instance using the web portal (HTTP/HTTPS) and SSH access. The second network will transport the actual incoming and outgoing VoIP streams (signaling and media) that the ProSBC and transcoding unit will process. The third network will be used as a control interface connecting to another host in ProSBC 1+1 configuration and transcoding unit in the system for control purpose.		ProSBC with transcoding deployments require a minimum of three networks for initial configuration. The first network will be used as a local management interface to access the instance using the web portal (HTTP/HTTPS) and SSH access. The second network will transport the actual incoming and outgoing VoIP streams (signaling and media) that the ProSBC and transcoding unit will process. The third network will be used as a control interface connecting to another host in ProSBC 1+1 configuration and transcoding unit in the system for control purpose.

Luc Morissette: /* Configuring Transcoding Unit(s) */

2023-06-26T19:17:52Z

Configuring Transcoding Unit(s)

← Older revision		Revision as of 15:17, 26 June 2023
Line 41:		Line 41:
	== Configuring Transcoding Unit(s) ==		== Configuring Transcoding Unit(s) ==

	For configuring Transcoding unit on ProSBC, please see [[Toolpack:Tsbc IP Network Settings 3.0]]		For configuring Transcoding unit on ProSBC, please see [[Toolpack:Tsbc IP Network Settings 3.1\|ProSBC Web Portal 3.1: IP Network Settings]]

Allyntree: Changed the link to a new image

2023-06-05T14:39:57Z

Changed the link to a new image

← Older revision		Revision as of 10:39, 5 June 2023
Line 7:		Line 7:
	ProSBC with transcoding deployments require a minimum of three networks for initial configuration. The first network will be used as a local management interface to access the instance using the web portal (HTTP/HTTPS) and SSH access. The second network will transport the actual incoming and outgoing VoIP streams (signaling and media) that the ProSBC and transcoding unit will process. The third network will be used as a control interface connecting to another host in ProSBC 1+1 configuration and transcoding unit in the system for control purpose.		ProSBC with transcoding deployments require a minimum of three networks for initial configuration. The first network will be used as a local management interface to access the instance using the web portal (HTTP/HTTPS) and SSH access. The second network will transport the actual incoming and outgoing VoIP streams (signaling and media) that the ProSBC and transcoding unit will process. The third network will be used as a control interface connecting to another host in ProSBC 1+1 configuration and transcoding unit in the system for control purpose.

	[[File:Tsbc-sw-any-~~networks_with_transcoding~~.png\|700px]]		[[File:Tsbc-sw-any-networks_with_transcoding_V2.png\|700px]]

	== Network setups ==		== Network setups ==

Luc Morissette: Updated for ProSBC

2019-07-16T21:24:40Z

Updated for ProSBC

← Older revision		Revision as of 17:24, 16 July 2019
Line 1:		Line 1:
	{{DISPLAYTITLE:~~FreeSBC~~:Transcoding and Network Setup}}		{{DISPLAYTITLE:ProSBC:Transcoding and Network Setup}}

	== Requirements ==		== Requirements ==

	~~FreeSBC~~ requires external hardware transcoding unit supplied by Telcobridges to do transcoding between different codecs used in RTP ~~traffic~~. Please see [[~~FreeSBC~~]] for more information ~~of trancoding~~ unit.		ProSBC requires external hardware transcoding unit supplied by Telcobridges to do transcoding between different codecs used in SIP/RTP communications. It is also used to play and record. Please see [[ProSBC]] for more information on transcoding unit.

	~~FreeSBC~~ with transcoding deployments require a minimum of three networks for initial configuration. The first network will be used as a local management interface to access the instance using the web portal (HTTP/HTTPS) and SSH access. The second network will transport the actual incoming and outgoing VoIP streams (signaling and media) that the ~~FreeSBC~~ and transcoding unit will process. The third network will be used as a control interface connecting to another host in ~~FreeSBC~~ 1+1 configuration and transcoding unit in the system for control purpose.		ProSBC with transcoding deployments require a minimum of three networks for initial configuration. The first network will be used as a local management interface to access the instance using the web portal (HTTP/HTTPS) and SSH access. The second network will transport the actual incoming and outgoing VoIP streams (signaling and media) that the ProSBC and transcoding unit will process. The third network will be used as a control interface connecting to another host in ProSBC 1+1 configuration and transcoding unit in the system for control purpose.

	[[File:Tsbc-sw-any-networks_with_transcoding.png\|700px]]		[[File:Tsbc-sw-any-networks_with_transcoding.png\|700px]]
Line 11:		Line 11:
	== Network setups ==		== Network setups ==

	Depending on the technical requirements of a particular deployment, a ~~FreeSBC~~ can be installed as a standalone or protected (1+1) system. These options have different network needs to fulfill their functions. In addition to redundancy, the support of external transcoding equipment with the ~~FreeSBC~~ also adds to the network requirements. The following sections depict the different supported network configurations.		Depending on the technical requirements of a particular deployment, a ProSBC can be installed as a standalone or protected (1+1) system. These options have different network needs to fulfill their functions. In addition to redundancy, the support of external transcoding equipment with the ProSBC also adds to the network requirements. The following sections depict the different supported network configurations.

	=== Transcoding ===		=== Transcoding ===

	The ~~FreeSBC~~ 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 ~~FreeSBC~~ 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.		The ProSBC 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 ProSBC 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]]		[[File:Transcoding.png]]
Line 33:		Line 33:
	== Network device discovery ==		== Network device discovery ==

	Once all networks have been physically (or virtually) connected to the ~~FreeSBC~~ instance, the system can be started. Upon first bootup with indication for requirment to connect transcoding unit to the ~~FreeSBC~~ system (or after an operator initiated 'network device role' reset), the ~~FreeSBC~~ web portal will show a network device assignation page. 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.		Once all networks have been physically (or virtually) connected to the ProSBC instance, the system can be started. Upon first bootup with indication for requirment to connect transcoding unit to the ProSBC system (or after an operator initiated 'network device role' reset), the ProSBC web portal will show a network device assignation page. 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 a specific 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).
Line 41:		Line 41:
	== Configuring Transcoding Unit(s) ==		== Configuring Transcoding Unit(s) ==

	For configuring Transcoding unit on ~~FreeSBC~~, please see [[Toolpack:Tsbc IP Network Settings 3.0]]		For configuring Transcoding unit on ProSBC, please see [[Toolpack:Tsbc IP Network Settings 3.0]]

William Wong: /* Requirements */

2018-02-22T07:19:14Z

Requirements

← Older revision		Revision as of 03:19, 22 February 2018
Line 6:		Line 6:

	FreeSBC with transcoding deployments require a minimum of three networks for initial configuration. The first network will be used as a local management interface to access the instance using the web portal (HTTP/HTTPS) and SSH access. The second network will transport the actual incoming and outgoing VoIP streams (signaling and media) that the FreeSBC and transcoding unit will process. The third network will be used as a control interface connecting to another host in FreeSBC 1+1 configuration and transcoding unit in the system for control purpose.		FreeSBC with transcoding deployments require a minimum of three networks for initial configuration. The first network will be used as a local management interface to access the instance using the web portal (HTTP/HTTPS) and SSH access. The second network will transport the actual incoming and outgoing VoIP streams (signaling and media) that the FreeSBC and transcoding unit will process. The third network will be used as a control interface connecting to another host in FreeSBC 1+1 configuration and transcoding unit in the system for control purpose.

			[[File:Tsbc-sw-any-networks_with_transcoding.png\|700px]]

	== Network setups ==		== Network setups ==

William Wong: /* Requirements */

2018-02-22T07:18:48Z

Requirements

← Older revision		Revision as of 03:18, 22 February 2018
Line 5:		Line 5:
	FreeSBC requires external hardware transcoding unit supplied by Telcobridges to do transcoding between different codecs used in RTP traffic. Please see [[FreeSBC]] for more information of trancoding unit.		FreeSBC requires external hardware transcoding unit supplied by Telcobridges to do transcoding between different codecs used in RTP traffic. Please see [[FreeSBC]] for more information of trancoding unit.

	FreeSBC with transcoding deployments require a minimum of three networks for initial configuration. The first network will be used as a local management interface to access the instance using the web portal (HTTP/HTTPS) and SSH access. The second network will transport the actual incoming and outgoing VoIP streams (signaling and media) that the FreeSBC and transcoding unit will process. The third network will be used as a control interface connecting to another host in FreeSBC 1+1 configuration and transcoding unit in the system for control purpose.		FreeSBC with transcoding deployments require a minimum of three networks for initial configuration. The first network will be used as a local management interface to access the instance using the web portal (HTTP/HTTPS) and SSH access. The second network will transport the actual incoming and outgoing VoIP streams (signaling and media) that the FreeSBC and transcoding unit will process. The third network will be used as a control interface connecting to another host in FreeSBC 1+1 configuration and transcoding unit in the system for control purpose.

	~~[[File:Tsbc-sw-any-networks_with_transcoding.png\|700px]]~~

	== Network setups ==		== Network setups ==

William Wong: /* Requirements */

2018-02-20T07:56:22Z

Requirements

← Older revision		Revision as of 03:56, 20 February 2018
Line 5:		Line 5:
	FreeSBC requires external hardware transcoding unit supplied by Telcobridges to do transcoding between different codecs used in RTP traffic. Please see [[FreeSBC]] for more information of trancoding unit.		FreeSBC requires external hardware transcoding unit supplied by Telcobridges to do transcoding between different codecs used in RTP traffic. Please see [[FreeSBC]] for more information of trancoding unit.

	FreeSBC with transcoding deployments require a minimum of three networks for initial configuration. The first network will be used as a local management interface to access the instance using the web portal (HTTP/HTTPS) and SSH access. The second network will transport the actual incoming and outgoing VoIP streams (signaling and media) that the FreeSBC and transcoding unit will process. The third network will be used as a control interface connecting to another host in FreeSBC 1+1 configuration /and transcoding unit in the system for control purpose.		FreeSBC with transcoding deployments require a minimum of three networks for initial configuration. The first network will be used as a local management interface to access the instance using the web portal (HTTP/HTTPS) and SSH access. The second network will transport the actual incoming and outgoing VoIP streams (signaling and media) that the FreeSBC and transcoding unit will process. The third network will be used as a control interface connecting to another host in FreeSBC 1+1 configuration and transcoding unit in the system for control purpose.

	[[File:Tsbc-sw-any-networks_with_transcoding.png\|700px]]		[[File:Tsbc-sw-any-networks_with_transcoding.png\|700px]]