You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Note

This object is visible and configurable only for SBC SWe Cloud. Refer to Configuring an SBC SWe Cluster using the EMS for information on configuring SWe Cloud deployments.

SBC SWe systems in an OpenStack cloud environment inter-operate with a third-party transcoding platform called Media Resource Function (MRF) to transcode audio and relay video/T140.

Note

Only distributed SBC (D-SBC) SWe systems on OpenStack supports this feature. 


Prior to release 7.1.0, the SBC 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 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 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 on OpenStack (D-SBC) supports this feature. 

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

Creating an MRF Cluster Type

To establish a connection between an S-SBC Cluster and M-SBC Cluster, create an MRF Cluster Type.

  1. On the navigation pane, click AllSystem > DSBC > Cluster > Type

    Cluster Type

  2. Click New Type. By default, the Create New Type window for Policer is displayed. To create an MRF Type, select the Name as MRF.

    Create New Type - Policer

  3. To create an MRF cluster with a Routing Type of FQDN:
    1. In Name, choose MRF.
    2. Select the State.
    3. Select the MRF Routing Type as FQDN.

      Create New Type - MRF with Routing Type as FQDN

    4. In Mrf TG Name, choose MRF_TG.
    5. Enter the Mrf Request URI.
    6. Enter the Mrf Port number.
    7. In MRF Transport Type, choose the appropriate transport type.
    8. Enter the Mrffqdn.
    9. Click Save.
  4. To create an MRF with the Routing Type of IP Address V4 or V6:
    1. In Name, choose MRF.
    2. Enter the Mrf IP Address.
    3. Select the State.
    4. Select the MRF Routing Type as IP Address V4 or V6.

      Create New Type - MRF with Routing Type as IP Address V4 or V6

    5. In MRF TG Name drop-down menu, choose MRF_TG.
    6. Enter the Mrf Request URI.
    7. Enter the MRF Port number.
    8. In MRF Transport Type, choose the appropriate transport type.
    9. Click Save.
Note:

If you later need to edit or delete an MRF cluster, first set its State to Disabled. Set the State back to Enabled after you edit an MRF cluster.


Creating a Policer Cluster Type

To establish a connection between an SBC and an MRF, create an Policer Cluster Type.

  1. Click AllSystem > DSBC > Cluster > Type.

    Type List

  2. Click New Type. By default, the Create New Type window for Policer is displayed.

    Create New Type - Policer

  3. In Name, choose Policer.
  4. Select the State.
  5. Enter an FQDN.
  6. In DNS Group, choose a DNS Group.
  7. Click Save.
Note:

If you later need to edit or delete a Policer cluster, first set its State to Disabled. Set the State back to Enabled after you edit a Policer cluster.

Creating a DSP Cluster Type

To establish a connection between an S-SBC cluster and a T-SBC cluster, create a DSP Cluster Type.

Note

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

  1. On the navigation pane, click AllSystem > DSBC > Cluster > Type.

    Type List

  2. Click New Type. By default, the Create New Type window for Policer is displayed.

    Create New Type - Policer

  3. In Name, choose DSP.
  4. Select the State.
  5. Enter an FQDN.
  6. In DNS Group, choose a DNS Group.
  7. Click Save.
Note:

If you later need to edit or delete a DSP cluster, first set its State to Disabled. Set the State back to Enabled after you edit a DSP cluster.

  • No labels