Ribbon offers different
personalities
for on the
and platforms platform, as summarized below:
- I-SBC: "Integrated " with signaling, media, and (optional) transcoding functionality within a single node. An instantiated without a personality type defaults to I-SBC. This personality type is analogous to the hardware platforms, and can be deployed on and platforms.
- D-SBC: "Distributed " refers to the architecture where the signaling, media, and (optional) transcoding functions are handled by dedicated SBC nodes or clusters, as described and includes the personalities below:
- S-SBC: "Signaling " in a distributed deployment. An must be instantiated with the Signaling "personality" to behave as an S-SBC.
- M-SBC: "Media-handling " in a distributed deployment. An must be instantiated with the Media "personality" to behave as an M-SBC.
- T-SBC: "Transcoding-handling " in a distributed deployment
, where Transcoding denotes a configuration setting, and not a "personality". - . 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 " is not an personality, but denotes a configuration setting dedicated to handling Signalingsignaling 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.
{"serverDuration": 84, "requestCorrelationId": "44c7ced63f9d5508"}