Ribbon offers different SBC personalities for the SBC SWe and SBC SWe Cloud  platforms, as summarized below:

  • 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 is analogous to the SBC Core hardware platforms, and can be deployed on SBC SWe and SBC SWe Cloud 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, as described 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.
    • 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, where Transcoding denotes a configuration setting, and not a "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. 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.