Configuration Overview

Oracle Communications Session Border Controller Virtual Machine (VM) deployments require configuration of the VM environment and, separately, configuration of the SBC itself. VM-specific configuration on the SBC includes boot parameter configuration, enabling functionality and performance tuning.

During VM installation, you can configure vSBC boot parameters, including:

  • IP address
  • Host name

During VM installation, the SBC sets default functionality, assigning cores to signaling and media forwarding. If you need DoS and/or transcoding functionality, you configure the applicable cores after installation. Applicable performance tuning configuration after deployment includes:

  • Media manager traffic/bandwidth utilization tuning
  • Datapath-related CPU core allocation

Note:

For Xen-based hypervisors, the default boot mode uses DHCP to obtain an IP address for the first management interface (wancom0) unless a static IP is provisioned. Note that DHCP on wancom0 does not support lease expiry, so the hypervisor must provide persistent IP address mapping. If persistent IP address mapping is not provided, the user must manually restart the VM whenever the wancom0 IP address changes due to a manual change or DHCP lease expiry.

Beyond installation, VM-related functional support, and VM-related tuning, you perform basic SBC configuration procedures after installation, including:

  • Setting passwords
  • Setup product
  • Setup entitlements
  • Assign Cores
  • Enable hyperthreading for forwarding, DoS and transcoding cores
  • Service configuration