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

Compare with Current View Page History

« Previous Version 3 Next »

In this section:

Related articles:

 

EMA is a Web-Based Interface management system for configuring Sonus Session Border Controllers (

Unable to show "metadata-from": No such page "_space_variables"
s). The Embedded Management Application (EMA) User Guide provides complete set of operational instructions covering all aspects of the EMA Web-Based Interface. EMA enables to rapidly deploy and easily manage 
Unable to show "metadata-from": No such page "_space_variables"
 
Unable to show "metadata-from": No such page "_space_variables"
s. As an embedded management system, EMA supports configuration, fault, and security management functions through an intuitive, easy-to-use, browser-based user interface.

The EMA offers feature-rich management framework that supports fault management, configuration and security. It covers all areas vital for the efficient operation, administration, management and provisioning (OAMP) of Sonus 

Unable to show "metadata-from": No such page "_space_variables"
s . EMA supports all operations that are available from the 
Unable to show "metadata-from": No such page "_space_variables"
Command Line Interface (CLI) and, in addition, provides specialized functionality that is intended to facilitate common device management operations.

If the web browser crashes, hangs or is manually closed while logged into the EMA GUI, the EMA session will still remain open. Manual intervention by the administrator is required to terminate the session from the EMA GUI. To terminate the hanging session, refer to Users and Application Management - User and Session Management page.

This User Guide does not reflect the latest GUI images. The images will be replaced gradually.

Audience

This guide is intended for operators and system administrators responsible for provisioning, maintaining, and administering the

Unable to show "metadata-from": No such page "_space_variables"
. It is assumed that the end user of this document will have basic understanding and working knowledge of the following technical aspects:

  • VoIP
  • SIP protocol
  • H323 protocol
  • IP-to-IP networking
  • Linux operating system
  • Packet networking.

This guide also requires specific knowledge of the 

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

Characteristics of EMA

 The following are the EMA key characteristics:

  • EMA supports the following functionality:
    • Fault management
    • Configuration management
    • Security management
  • A web-based interface for better usability
  • Certificate management
  • Support to upgrade/downgrade software
  • Service Provisioning workflows
  • Monitoring alarms

Supported Browsers and Client Computer Requirements

The minimum recommended requirements for each user's computer are outlined below. Configurations that do not meet these recommendations may experience excessively poor performance. Also note that slow network connections can also result in poor performance.

Client Computers

The minimum recommended memory/processor requirements of a client computer/workstation when accessing EMA is following:

  • 2.4 GHz with Dual Core processor
  • 2 GB RAM

Supported Browsers and Platforms

The platform/browser combinations supported are listed in the table below.

The minimum browser resolution that is supported is 1024 x 768 pixels.

Supported Platforms and Browsers

Browser

Version

Platform and OS

Internet Explorer

9, 10, and 11

  • Microsoft Windows (XP, Vista, 7)

Firefox

31 and later

  • Microsoft Windows (XP, Vista, 7)
  • Intel-based Mac (10.5 and later)
Chrome32 and later
  • Microsoft Windows (XP, Vista, 7)

EMA Cross-context Queries

The EMA provides the ability to view status and statistics across contexts. For example, it is possible to view trunk group status across all zones and address contexts.  For large configurations, however, performance may be impacted when viewing status and statistics across contexts. This is especially true for configurations with more than 20 zones.

To address this problem, Sonus provides a script to disable cross-context queries. If you experience performance issues when viewing status and statistics, run this script to alleviate this issue.

Running this script disables all cross-context functionality forcing you to specify the object context before viewing status, statistics or configuration information for an object.  For example, after running this script you will need to first select a specific address context and zone in order to view trunk group status or a list of trunk groups.

Disabling Cross-Context Queries

To disable cross-context queries, perform the following steps:

  1. Open the BMC for the SBC.
  2. In the BMC, select the Remote Control tab, then click the Console Redirection button.
  3. Launch the redirection console.
  4. In the redirection console, login using an Administrator username and password for the SBC.

  5. Enter the following command and press Enter.:

    /opt/sonus/ema/updateCrossContextDisabledValue.sh true

  6. Log out of the redirection console and close it

  7. Log out of the BMC.

If the
Unable to show "metadata-from": No such page "_space_variables"
is part of an HA pair, perform these steps on both the primary and secondary
Unable to show "metadata-from": No such page "_space_variables"
.

Re-enabling Cross-Context Queries

To re-enable cross context queries, follow the steps above substituting the following command with the one in step 5:

/opt/sonus/ema/updateCrossContextDisabledValue.sh false

  • No labels