Baremetal and Virtual Machine
Transcoding Unit Configuration
ProSBC Host Configuration
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 75
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.
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
ProSBC Network configuration
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
Transcoding unit network configuration
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
Last updated
Was this helpful?