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

Compare with Current View Page History

Version 1 Next »


RAMP support only

Beginning with SBC Core release 12.0, the SBC interoperates with the Ribbon Application Management Platform (RAMP), replacing the Insight EMS.

However, the EMA, CLI and API will continue to include EMS-labeled parameters and screens to facilitate SBC migrations from older releases. Accordingly, any references to "EMS" in this documentation apply to the RAMP platform.

In this section:

Related articles:

Unable to show "metadata-from": No such page "_space_variables"
uses the EMS CALEA user role for all LI configuration operations and the admin user for communicating over netconf to the SBC.
Unable to show "metadata-from": No such page "_space_variables"
creates the SBC CALEA user credentials automatically when an SBC registers to the
Unable to show "metadata-from": No such page "_space_variables"
. Distributed SBC instances are registered dynamically in
Unable to show "metadata-from": No such page "_space_variables"
.

Note:

A single Call Data Channel (CDC) configuration is supported per cluster.

Prerequisites

To configure the CDC for an M-SBC instance:

Configuring CDC using the EMS CALEA User Account

For LI, CDC configuration is performed using the CDC Configuration Manager through the

Unable to show "metadata-from": No such page "_space_variables"
. You can create CDC information only when logged in as the EMS CALEA user from the EMS CDC configuration window.

Configure Cluster CDC for M-SBC Nodes

To configure a cluster CDC for M-SBC nodes:

  1. Log into
    Unable to show "metadata-from": No such page "_space_variables"
    as an admin user.
  2. Click Network > Cluster Management. The Cluster Management / Manage VNFs window opens listing the SBC clusters created on the

    Unable to show "metadata-from": No such page "_space_variables"
    .


  3. Click the radio button adjacent to the name of the cluster you want to configure. The Details tab for the selected cluster opens by default. 
  4. Click the Configurations tab.


  5. Launch another
    Unable to show "metadata-from": No such page "_space_variables"
    session as the CALEA user.
  6. Under Monitoring, click Lawful Intercept. The Lawful Intercept window is displayed.
  7. Click Cluster CDC. The Lawful Intercept/Cluster CDC window is displayed.


  8. Select the M-SBC cluster.
  9. Click Launch CDC Configuration Manager. The SBC Configuration Manager window is displayed.

  10. Create a call data channel for the M-SBC as described in the following procedure.

Creating a Call Data Channel for the M-SBC

The SBC SWe provides the ability to configure the IP address, TCP port, and other parameters used for communication towards the mediation server.

To create a new call data channel:

  1. In the SBC Configuration Manager window, navigate to Configuration > Intercept > Call Data Channel. The Call Data Channel window is displayed.


  2. Select default from the Address Context drop-down menu. You can configure LI using the default Address Context only.


  3. Click New Call Data Channel. The Create New Call Data Channel window is displayed.

  4. Specify the following values:
    1. Name: Type the name of the call data channel.

    2. Intercept Standard: Select packetcable from the drop-down menu.

    3. Vendor ID: Select ss8 from the drop-down menu.

    4. RTCP Interception: Select Enabled.
    5. Media IP Interface Group Name: Select the name of the media IP interface group you want to use from the drop-down menu.


       ParameterDescription
      NameSpecifies the name of the CDC configuration object.
      Intercept StandardSpecifies the intercept standard to use.
      Vendor IdSpecifies the vendor of the LI server.
      RTCP InterceptionSpecifies whether to intercept RTCP data. The values are:
      • Disabled (default) 
      • Enabled
      Media IP interface Group NameSelect a Media IP interface Group Name.
  5. Click Save

  6. Click OK.

  7. Click Close at the top-right of the SBC Configuration Manager window.

Creating Mediation Servers

After the call data channel is created, you must create mediation server objects associated with the call data channel. The CDC configuration supports up to eight mediation servers.

To create a mediation server object:

  1. Navigate to Configuration > Intercept > Call Data Channel > Mediation Server. The Mediation Server window is displayed.


  2. Select default from the Address Context drop-down menu.

  3. Select the Call Data Channel you created for the M-SBC from the drop-down menu.

  4. Click New Mediation Server. The Create New Mediation Server window is displayed.

  5. Type a mediation server name in Msname.


  6. Click Save. The object is created successfully. You can repeat the steps to create up to eight mediation servers for the M-SBC.

Mediation Server - Media - TCP

This screen includes the LI Mediation Server TCP Media intercept parameters.

To view TCP parameters:

  1. Navigate to Configuration Intercept > Call Data Channel > Mediation Server > Media > TCP. The TCP window is displayed.


  2. Select default from the Address Context drop-down menu.

  3. Select the Call Data Channel from the drop down menu.

  4. Select the Mediation Server from the drop-down menu. The configuration for the selected server opens.


  5. Use the following table to configure the server parameters.

    Note:

    The mediation server parameters can only be updated when its State is Disabled and Mode is Out Of Service.

    Table 2: TCP Parameters

    Parameter Description
    IP Address V4 or V6

    IPV4/IPV6 address of the mediation server for media interception over TCP.


    Port NumberSpecifies the port number of the mediation server for media interception over TCP. Range is 0 - 65535.
    DSCP ValueSpecifies the DSCP value for intercepted media packets sent on TCP port. Default value is 16 and range is 0 - 63.
    Mode

    Specifies the mode of the TCP connection towards the mediation server for media interception. The options are:

    • In Service
    • Out of service (default)
    State

    Specifies the state of the TCP connection towards the mediation server for media interception. The options are:

    • Disabled (default) 
    • Enabled
    KA TimeSpecifies the duration between two keep alive transmissions while in idle condition. The default value is 180.
    KA IntervalSpecifies the duration between two successive keep alive re-transmissions, if acknowledgement to the previous keep alive transmission is not received. The default value is 30.
    KA ProbeSpecifies the number of re-transmissions to be carried out before declaring that the remote end is not available. The default value is 4.
  6. Click Save.
  7. Click OK.
  8. Enable the mediation server by changing its State to Enabled and Mode to In Service.
  9. Click Save to save the configuration.
  10. Return to the

    Unable to show "metadata-from": No such page "_space_variables"
    session containing the SBC Configuration Manager for the OAM node and then click Apply Saved Changes and Close.

  11. When prompted, confirm that you want to save and activate your configuration changes. 

Viewing Statistics for M-SBC 

To view mediation server media statistics:

  1. Log onto
    Unable to show "metadata-from": No such page "_space_variables"
    as the CALEA user.
  2. Under Monitoring, click Lawful Intercept. The Lawful Intercept window is displayed.
  3. Click Cluster CDC. The Lawful Intercept/Cluster CDC window is displayed.

  4. Select the M-SBC cluster.
  5. Click View Nodes. The nodes list in the cluster is displayed.


  6. Select the node to view the mediation server media status and click Launch Node LI Stats. The Mediation Server Media Status window is displayed.


  • No labels