Page History
Ribbon offers different
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
- I-SBC: "Integrated
" with signaling, media, and (optional) transcoding functionality within a single node. AnSpacevars 0 product
instantiated without a personality type defaults to I-SBC. This personality type is analogous to theSpacevars 0 product
hardware platforms.Spacevars 0 series4 - D-SBC: "Distributed
" 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:Spacevars 0 product S-SBC: "Signaling
" in a distributedSpacevars 0 product
deployment. AnSpacevars 0 product
must be instantiated with the Signaling " personality " to behave as an S-SBC.Spacevars 0 product Info 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
" in a distributedSpacevars 0 product
deployment. AnSpacevars 0 product
must be instantiated with the Media " personality " to behave as an M-SBC.Spacevars 0 product - T-SBC: "Transcoding-handling
" in a distributedSpacevars 0 product
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.Spacevars 0 product
- T-SBC: "Transcoding-handling
- SO-SBC: "Signaling Only
" is not anSpacevars 0 product
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.Spacevars 0 product
Overview
Content Tools