Ribbon offers different SBC personalities on the SBC SWe platform:

  • I-SBC: "Integrated SBC" with signaling, media, and (optional) transcoding functionality within a single node. An SBC instantiated without a personality type defaults to I-SBC. This personality type is analogous to the SBC Core hardware platforms.

  • D-SBC: "Distributed SBC" refers to the architecture where the signaling, media, and (optional) transcoding functions are handled by dedicated SBC nodes or clusters, and includes the personalities below:

    • S-SBC: "Signaling SBC" in a distributed SBC deployment. An SBC must be instantiated with the Signaling personality to behave as an S-SBC.

      You can configure the S-SBC behind the SIP-aware front-end Load-Balancer (SLB). Refer to SIP-Aware Front-End Load Balancer for details.

    • M-SBC: "Media-handling SBC" in a distributed SBC deployment. An SBC must be instantiated with the Media personality to behave as an M-SBC.
      • T-SBC: "Transcoding-handling SBC" in a distributed SBC deployment. T-SBC is a special case for an M-SBC. "Transcoding-handling" requires specific configuration settings, but not a completely distinct personality. Only an M-SBC can be configured as a T-SBC.

  • SO-SBC: "Signaling Only SBC" is not an SBC personality, but denotes a configuration setting dedicated to handling signaling only. Either an I-SBC or an S-SBC can be configured as an SO-SBC, which is the primary difference between S-SBC and SO-SBC.