Use Cases:HW Transcoding Configuration UseCase2 A

This article applies to:	Product	Version
	SBC	3.1, 3.3

Perequisites

Perequisites ProSBC Host Network device name Network device role Network Config ------------------- ------------------- ------------------- mgmt0 mgmt Untagged wan0 LAN/WAN Tagged 1650 lan0 LAN/WAN Tagged 1651 ctrl0 ctrl0 Tagged 750 ctrl1 ctrl1 Tagged 751 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: Initial Configuration (Search for "Bonding") Hardware Unit - TB002177 is the TSBC-HW-TRANS unit in the below setup. Network device name Network device role Network Config ------------------- ------------------- ------------------- voip0 LAN/WAN Tagged 752 voip1 LAN/WAN Tagged 752 eth0 ctrl0 Untagged PVID 750 ** eth1 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 Baremetal Configuration ProSBC Network configuration Configure IP Network for trans Create vp_trans virtual port: Name: vp_trans Ethernet Ports: trans VLAN name: vlan_752 VLAN id: 752 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 Show transcoding unit Add TB002177 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