Actions

Use Cases:HW Transcoding Configuration UseCase2 A: Difference between revisions
No edit summary
Line 1: Line 1:
{{DISPLAYTITLE:IP Transcoding Unit Configuration Use Case: Baremetal}}
{{DISPLAYTITLE:IP Transcoding Unit Configuration Use Case: Baremetal and Virtual Machine}}


{| class="wikitable"
{| class="wikitable"
Line 11: Line 11:
|}
|}


 
== Transcoding Unit Configuration ==
== Perequisites ==
{|
{|
|STYLE="vertical-align: top"|
|STYLE="vertical-align: top"|
Line 19: Line 18:
|-
|-
|
|
*ProSBC Host
*ProSBC Host Configuration
Network device name   Network device role   Network Config
{|
-------------------    -------------------    -------------------
|STYLE="vertical-align: top"|
mgmt0                 mgmt                   Untagged
{| border="1" class="wikitable"
wan0                   LAN/WAN               Tagged 1650
! width="300" style="background: none repeat scroll 0% 0% rgb(0, 83, 139);" | Network device name
lan0                   LAN/WAN               Tagged 1651
! width="300" style="background: none repeat scroll 0% 0% rgb(0, 83, 139);" | Purpose
ctrl0                 ctrl0                 Tagged 750
! width="300" style="background: none repeat scroll 0% 0% rgb(0, 83, 139);" | Network device role
ctrl1                 ctrl1                 Tagged 751            
! width="600" style="background: none repeat scroll 0% 0% rgb(0, 83, 139);" | Network Config
trans                 LAN/WAN               Tagged 752    
|-
'''NOTE:''' The 'Network device name' for transcoding must be '''trans'''. To have redundancy, the '''trans''' port bonding (using trans0 and trans1 physical ports) needs to be created at initialization time. You can look here for reference: [[TSBC-SW:WebPortal:Initial_Configuration|Initial Configuration]]  (Search for "Bonding")
| mgmt0 || Management port || mgmt|| Untagged
|-
| wan0 || SBC port || LAN/WAN || Tagged 1650 (or other)
|-
| lan0 || SBC port || LAN/WAN || Tagged 1651 (or other)
|-
| ctrl0 || control port || ctrl0 || Tagged 750
|-
| ctrl1 || control port || ctrl1 || Tagged 751
|-
| trans || transcoding port || LAN/WAN || Tagged 752
|}
'''NOTES:'''  
* The 'Network device name' for transcoding must be '''trans'''. To have redundancy, the '''trans''' port bonding (using trans0 and trans1 physical ports) needs to be created at initialization time.
* For baremetal, the '''trans''' port bonding, using trans0 and trans1 physical ports must be bonded at initialization time. You can look here for reference: [[TSBC-SW:WebPortal:Initial_Configuration|Initial Configuration]]  (Search for "Bonding")
* For virtual machines, the virtual ports trans0 and trans1 are bonded in the Hypervisor layer of the virtual machine (optional) and the '''tran''' interface is presented to the guest (the ProSBC).




*Hardware Unit - TB002177 is the TSBC-HW-TRANS unit in the below setup.  
*Hardware Unit - TB002177 is the TSBC-HW-TRANS unit in the below setup.  
  Network device name   Network device role   Network Config
{|
-------------------    -------------------    -------------------
|STYLE="vertical-align: top"|
voip0                   LAN/WAN                Tagged 752
{| border="1" class="wikitable"
voip1                   LAN/WAN                Tagged 752
! width="300" style="background: none repeat scroll 0% 0% rgb(0, 83, 139);" | Network device name
eth0                   ctrl0                 Untagged PVID 750  **
! width="300" style="background: none repeat scroll 0% 0% rgb(0, 83, 139);" | Purpose
eth1                   ctrl1                 Untagged PVID 751  **
! width="300" style="background: none repeat scroll 0% 0% rgb(0, 83, 139);" | Network device role
! width="600" style="background: none repeat scroll 0% 0% rgb(0, 83, 139);" | Network Config
|-
| voip0 || transcoding port || trans || Tagged 752 (Bonded with voip1)
|-
| voip1 || transcoding port || trans || Tagged 752 (Bonded with voip0)
|-
| eth0 || control port || ctrl0 || Untagged PVID 750  **
|-
| eth1 || control port || ctrl1 || Untagged PVID 751  **
|-
|}


'''NOTE:''' Since the control ports on the device cannot be tagged, this must be done by the network switch. The control ports need to be configure with Link Type: Access
'''NOTE:''' Since the control ports on the device cannot be tagged, this must be done by the network switch. The control ports need to be configure with Link Type: Access
Line 43: Line 68:
|}
|}


== Baremetal Configuration  ==
== Configuration  ==


[[File:UseCase_TsbcHwTranscoding.png|link=]]
[[File:UseCase_TsbcHwTranscoding.png|link=]]

Revision as of 13:27, 3 January 2025


This article applies to: Product Version
SBC 3.1, 3.3

Transcoding Unit Configuration

Perequisites
  • ProSBC Host Configuration
Network device name Purpose Network device role Network Config
mgmt0 Management port mgmt Untagged
wan0 SBC port LAN/WAN Tagged 1650 (or other)
lan0 SBC port LAN/WAN Tagged 1651 (or other)
ctrl0 control port ctrl0 Tagged 750
ctrl1 control port ctrl1 Tagged 751
trans transcoding port LAN/WAN Tagged 752

NOTES:

  • The 'Network device name' for transcoding must be trans. To have redundancy, the trans port bonding (using trans0 and trans1 physical ports) needs to be created at initialization time.
  • For baremetal, the trans port bonding, using trans0 and trans1 physical ports must be bonded at initialization time. You can look here for reference: Initial Configuration (Search for "Bonding")
  • For virtual machines, the virtual ports trans0 and trans1 are bonded in the Hypervisor layer of the virtual machine (optional) and the tran interface is presented to the guest (the ProSBC).


  • Hardware Unit - TB002177 is the TSBC-HW-TRANS unit in the below setup.
Network device name Purpose Network device role Network Config
voip0 transcoding port trans Tagged 752 (Bonded with voip1)
voip1 transcoding port trans Tagged 752 (Bonded with voip0)
eth0 control port ctrl0 Untagged PVID 750 **
eth1 control port ctrl1 Untagged PVID 751 **

NOTE: Since the control ports on the device cannot be tagged, this must be done by the network switch. The control ports need to be configure with Link Type: Access

Configuration

ProSBC Network configuration

Configure IP Network for trans
  • Create trans IP Address:
    • Name: trans
    • Service to use: RTP
    • Host VLAN: vp_trans:vlan_752
    • IP address: 192.168.152.1
    • Netmask: 255.255.255.0

Transcoding unit configuration

Add transcoding unit


Transcoding unit network configuration

Configure IP Network for voip ports
  • Modify voip virtual port:
    • Name: vp_voip
    • Untagged: unselect
    • VLAN id: 752
    • Physical Ports: Use voip0 and voip1 (ctrl-click)
  • Modify voip IP Address:
    • Interface Name: voip
    • Service to use: RTP
    • Virtual port: TB002177:vp_voip
    • IP address: 192.168.152.10
    • Netmask: 255.255.255.0
Retrieved from "https://docs.telcobridges.com/w/index.php?title=Use_Cases:HW_Transcoding_Configuration_UseCase2_A&oldid=34635"