In this section:
Related articles:
The EMA GUI is available via TLS-secured (https) access either directly through port 443 or indirectly through port 80 to 443. ACL rules are not applicable to prevent unsecured (http) access.
A sample X.509 certificate, which is a copy of the BMC and the EMA Platform Mode certificate, is shipped along with the SBC shipment. The size of this certificate is 2,000 bytes.
The BMC is not applicable to SBC SWe.
The EMA uses the common Local Cert store of the SBC Core (used also for SIP/TLS) rather than having its own separate certificate store. The operator may replace that sample certificate at any time. The replacement mechanism is implemented with post installation/upgrade scripts.
Certificates with RSA keys up to 4,096 bits are supported.
Sonus recommends using only 2,048 bit certificates with release 3.1 and discourages the use of 4,096 bit certificates in 3.1 due to anticipated upgrade issues with the current software.
Enter the following URL in the browser to access the SBC EMA:
https://<hostname>
where, the <host name> is one of the management IP addresses of the SBC, or the equivalent DNS name. For example, https://10.54.41.8
.
The EMA uses a self-signed certificate which may produce a warning message by Internet Explorer and Firefox. These messages may be ignored.
The SBC Core is delivered with sample self-signed X.509 certificates. Please be aware that even though these sample certificates will allow you to use HTTPS to access the SBC from EMA, BMC and EMA Platform Mode interfaces, using this protocol with the sample certificates is not a truly secure access method. If your organization requires a more secure access, refer to Generating PKI Certificates.
The SBC Core supports SHA-256 for certificate verification.
Refer to
for a listing of supported browsers and client platforms when accessing EMA.Following are the steps to log into the Embedded Management Application (EMA):
Enter the SBC EMA URL <ip address/device name>
Sometimes, when using Internet Explorer/Mozilla Firefox browser, website security issue may prevent you from going directly to the SBC application login screen as shown in example below.
Click Advanced.
Click Add Exception.
The Login window appears as shown below:
Enter Username and Password. Your Username and the Password will be supplied along with the SBC installation package. Once you have successfully logged in to SBC, you temporary password expires and you are prompted to change your password.
This change password screen appears only for the first log on of the new user.
Ensure the following criteria are met to successfully change the password:
If you enter incorrect Username-Password combination, the following error message is displayed:
The Login window displays the following:
The following table describes the login window components.
After you log on to the EMA, you may get one of the following messages:
If you enter the correct login credentials:
If you make mistake, or someone had tried to unsuccessfully log on using your username but gave the wrong password:
The last login date of the user is displayed during the login time. When a user logs into the CLI/EMA, his/her last successful and failed login date and the IP address is displayed. The user evaluates this information to check illegal activities in the account.The information which are displayed at login:
Number of failed attempts after successful login.
Items 3, 4 and 5 display only when the last successful login date is older than the last unsuccessful login date. See the figure Login Message - Previous Unsuccessful Attempts.
The Last Login Information also displays for a new user for the first login. The new user is first authenticated and then allowed to change the system generated password.
To log out of the EMA:
Hover the mouse pointer over <your_username> on the menu bar. and click Log Out.
Confirm logging out by clicking Yes on the dialog-box.
This security enhancement is available beginning with SBC Core version 06.02.00R000.
This enhancement enables the EMA application (including EMA in platform mode) to disable concurrent user login sessions. Once a new session is established, any existing session is terminated immediately. When an EMA user attempts to log on, the system validates for any open sessions with the same username. If any existing user session is identified, the user is immediately logged out from the application and allows the new user to log on to the system.
This feature is applicable to all EMA users (local users, radius users, PKI Certificate based users, and CAC users).