In this section:

Related articles:

D-SBC Cluster

In a Distributed SBC configuration, each component scales independently in its own cluster depending upon call needs and the overall implemented traffic model.

  • S-SBC cluster – The Signaling component is scaled based on the traffic requirements.
  • M-SBC cluster – Media-based traffic such as video calls require instantiating more instances in the media cluster.
  • T-SBC cluster – The Transcoding-based traffic model require instantiating more instances in the transcoding cluster.

Note

 Currently, the SBC does not support T-SBC cluster (DSP profile).

The S-SBC cluster instances discover the server instances using standard DNS resolution of policing and DSP services that are provided by the respective M-SBC and T-SBC cluster.

Command Syntax

% set system dsbc cluster
	type <dsp, mrf, policer>

Command Parameter

D-SBC Cluster Type DSP Parameters

Parameter
Description
type

Use this parameter to configure the D-SBC cluster profile types.

  • dsp
  • mrf
  • policer

See D-SBC Cluster Type section below for configuration details.

D-SBC Cluster Type

The SBC supports the following cluster profiles to resolve inter-cluster FQDN port communication for the M-SBC and T-SBC nodes involving instances communicating with other clusters:

  • Policer—The D-SBC uses the Policer cluster of type M-SBC to provide policing services that include DoS/DDoS protection, Topology Hiding [IPv4, IPv6, IPv4/IPv6 inter-working], Media Rate limiting, VLAN Tagging, Far end NA(P)T Learning, RTP Inactivity detection, SRTP Relay, ACLs and Micro Flows.
  • DSP—The D-SBC uses the Signaling IP address of the T-SBC hosting the DSP to provide services that include Transcoding/tone detection, Secured transport connection (crypto) like SRTP (Media), RTCP generation, FMTD detection, Legal Interception, Recording and Transcoding, Transrating or Tran-sizing flows.
  • MRF—The D-SBC uses the MRF cluster to user a third-party platform (MRF) to transcode audio and relay video/T.140. The MRF cluster is configured in a private SBC network and uses RFC-4117 interface to communicate with S-SBC.
 

DSP Profile

The D-SBC uses the Signaling IP address of the T-SBC hosting the DSP to provide services that include Transcoding/tone detection, Secured transport connection (crypto) like SRTP (Media), RTCP generation, FMTD detection, Legal Interception, Recording and Transcoding, Trans-rating or Tran-sizing flows.

Command Syntax

% set system dsbc cluster type dsp
	dnsGroup <DNS group name> 
	fqdn <FQDN: 1-63>
	state <disabled | enabled> 

Note

 Currently, the SBC does not support T-SBC cluster (DSP profile).

Command Parameters

D-SBC Cluster Type DSP Parameters

Parameter
Description
dnsGroup<dnsGroup name> – The default DNS Server Group for this zone.
fqdn<FQDN value> – The FQDN value to associate with this dsp profile.
state

The administrative state of this D-SBC cluster.

  • disabled (default)
  • enabled
 

Media Resource Function Profile

The SBC SWe Cloud inter-operates with a third-party transcoding platform called Media Resource Function (MRF) to transcode audio and relay video/T140.

Note

Only the SBC SWe Cloud on OpenStack (D-SBC) supports this feature. 


Prior to release 7.1.0, the SBC SWe Cloud invoked MRF only for audio streams to achieve transcoding. Non-audio streams were relayed end-to-end even when the audio was sent to the MRF. Teletype (TTY) as the legacy service offered through encoding text characters as tones that are embedded in a carrier (PCMU, PCMA, or EVRC) media stream. The T.140 streams carry text as a separate payload.

Henceforth, the SBC SWe Cloud invokes MRF for T.140 and TTY interworking to achieve transcoding. When T.140 and TTY interwork, text characters exchange between the T.140 stream and the tones carried inband with the audio. If the audio is pass-through and T.140 requires transcoding, the SBC does not invoke MRF and instead rejects the text stream on the offer leg (see the following call flow). Keep in mind that T.140 pass-through scenarios are supported without any MRF interaction.

Note

This feature does not support sessions that only have a T.140 stream.

The SBC SWe Cloud does not invoke T.140 and TTY interworking when T.140 is present on both legs and has different transmission rates, or a difference in redundancy packet support.

Note

Only the SBC SWe Cloud on OpenStack (D-SBC) supports this feature. 

For additional feature functionality details, refer to Invoke MRF as a Transcoder for D-SBC.

The CLI syntax, parameter descriptions and command examples for configuring a MRF profile on a S-SBC is provided below.

Note

Use the global callRemoteMediaStatus and callResourceDetailStatus commands to see when MRF is used for transcoding a call (resType = "dresMrf").

 

Command Syntax

% set system dsbc cluster type mrf
    mrfFqdn <domanin name>
	mrfIpAddress <IP address>
	mrfPort <0-65535>
	mrfRequestUri <Request URI>
	mrfRoutingType <IpAddress | fqdn>
	mrfTgName <trunking group name>
	mrfTransportType <TCP| TLS| UDP>
	state <disabled | enabled> 

 

Command Parameters

Note

The MRF server is configured as either FQDN or IP address based on the mrfRoutingType setting.

D-SBC Cluster Type MRF Parameters

Parameter

Length/Range

Parameter Description

Mandatory /
Optional
mrfFqdn1-63

<domain name> – The domain name of the MRF server.

When mrfRoutingType = fqdn, configure the DNS Group on the zone in which mrfTgName exists.

M
mrfIpAddressN/A

<IP address> – One or more IP addresses of the MRF server. When mrfRoutingType = ipAddress, a minimum of one IP address must be configured. If more than one IP address is entered, separate each IP address by a comma (,). The SBC supports a maximum of four IP addresses.

M
mrfPort0-65535

<port number> – The port number of the MRF server. The default value is based on the mrRoutingType setting. (Default = 5060)

  • When the mrfRoutingType is fqdn, mrfPort default value is "0". In this case, you must configure the desired port in the DNS server for the SRV record.
  • When the mrfRoutingType is IpAddress, mrfPort .
O
mrfRequestUri1-63<request uri> – Request URI sent in an Invite towards MRF server.M
mrfRoutingTypeN/A

The routing type used to send invites towards MRF server.

  • fqdn (default)
  • IpAddress
O
mrfTgName1-24<TG name> – The Trunk Group name used for MRF signaling.M
mrfTransportTypeN/A

The transport type used to communicate to the MRF server.

  • TCP
  • TLS
  • UDP (default)
O
stateN/A

The admin state of the MRF cluster.

  • disabled (default)
  • enabled
M

Policer Profile

The D-SBC uses the policer cluster of type M-SBC to provide policing services that include DoS/DDoS Protection, Topology Hiding (IPv4, IPv6, IPv4/IPv6 inter-working), Media Rate Limiting, VLAN Tagging, Far End NA(P)T Learning, RTP Inactivity Detection, SRTP Relay, ACLs and Micro Flows. 

Note

This cluster configuration is applicable only to the S-Node, and helps it identify the seed node of the M-Cluster with a FQDN. The DNS Group configuration tells which DNS Group to use to resolve the specified FQDN.

 

Command Syntax

% set system dsbc cluster type policer
	dnsGroup <DNS group name> 
	fqdn <FQDN: 1-63>
	state <disabled | enabled>


Command Parameters

D-SBC Cluster Type Policer Parameters

Parameter
Description
dnsGroup<dnsGroup name> – The default DNS Server Group for this zone.
fqdn<FQDN value> – The FQDN value to associate with this policer profile.
state

The administrative state of this D-SBC cluster.

  • disabled (default)
  • enabled

Command Examples

To configure a DSP cluster profile:

set system dsbc cluster type dsp dnsGroup SWeDNS fqdn tsbc.tcluster.com state enabled
commit

 

To configure an MRF as IP address:

set system dsbc cluster type mrf mrfRoutingType IpAddress mrfPort 5060 mrfIpAddress 10.54.1.1 mrfTgName SBX_55461_IMS_TG mrfRequestUri MRF-SERVER mrfTransportType UDP state enabled
commit

 

To configure an MRF as fqdn:

set system dsbc cluster type mrf mrfRoutingType fqdn mrfPort 5060 mrffqdn sonusnet.com mrfTgName SBX_55461_IMS_TG mrfRequestUri MRF-SERVER mrfTransportType UDP state enabled 
commit