Skip to end of metadata
Go to start of metadata

On this page:

Getting Started

Congratulations on receiving your SBC 5000 series server! Below is a summary of the steps to follow to get your SBC 5000 series server functional.

  1. Create an IP plan. This plan lays out what the IP address the SBC 5000 series will use for its management ports (2 per unit), media ports (4 per unit for SBC 5200 and 2 per unit for SBC 5100), and its next hop router. The media ports are used for SIP and RTP traffic. See IP Plan page.
  2. Install the Hardware. Please see Installing SBC 5000 Series Hardware page.
  3. Configure the Field Service Port and Management Port IP address. The Field Service Port (FSP) is an Ethernet port located on the back of the SBC. This port allows you to access the SBC Baseboard Management Controller (BMC) web page. The BMC allows for system monitoring, power control, and configuring the Management Ports of the SBC. See Configuring the SBC Platform.
  4. Install SBC Application software. This should be done from the Platform Manager Web page. See Installing SBC Application Software for step-by-step instructions.
  5. You are now ready to configure your SBC 5000 series server for processing! See How to Set up a Basic Call Flow to get started quickly.

Background on SIP Trunking and Access

The SBC 5000 series server always acts as a SIP B2BUA (Back to Back User Agent). An important concept on the SBC is that all signaling and routing is based upon Trunk Groups.

SIP Trunk Groups are a logical connection between the SBC and a far end. A SIP Trunk can be one to one or one to many with the SBC always being a single point. A SIP Trunk for end point (phones) access will be one IP address on the SBC with the far end consisting of many different end points. A SIP Trunk for a carrier or PBX will generally be a one to one connection.

Access configurations involve end points (SIP phones, IADs, Soft Clients, etc.) that Register via the SBC to their feature server (Class 5, PBX, Hosted PBX, etc.). The SBC can cache Registrations in order to reduce the processing time the feature server spends on them. Even in Access configurations, a set of endpoints is represented by a trunk group.

From an SBC viewpoint, all calls (SIP sessions) involve two trunk groups on the SBC. For example, if Party A wished to connect to Party B via the SBC 5000 series, there are two trunk groups on the SBC involved, one to Party A and one to Party B.

There are generally two types of SIP Trunks that are point to point: Interconnect between two carriers and Interconnect between a PBX and a carrier. Interconnection between carriers is static and do not require registrations.
In the case of interconnection between a carrier and a PBX the amount of Registrations that can take place vary.

  • In a static trunking environment, no registrations take place. This is similar to two carriers interconnecting.
  • PBX can use Group registration for its endpoints.
  • When a pilot number is Registered, calls are routed (via the feature server) to that pilot number (which would include the extension in the INVITE) on the PBX.
  • Each endpoint can Register

Both SIP Trunking and Access configurations may be implemented on the same SBC 5000 series server.

How to Access the SBC: Five Ways

In normal day to day operations, you will primarily use the GUI based Embedded Management Application or the CLI to configure the system. However, the SBC is made up of several other components. Each of these components is accessed in a different manner.

Summary of Access Methods and Default Passwords:

Method

Purpose

How to Access

Default User ID / PW

Platform Manager

Web based Graphical Interface that allows for system level functions (ping, etc.) and monitoring (SBC application state, log viewing and downloading)

From web browser, enter https:// <IP address of SBC 5000 series MGMT interface>:444

"admin / Sonus12345"

Embedded Management Application (EMA) & Navigator

  • Web based Graphical Interface that allows for viewing and configuring the system for calls. This is the most frequently used access method.
  • The Navigator shows a graphical representation of the system data.
  • From web browser, enter IP address of SBC MGMT interface (or the virtual management interface IP address).
  • The Navigator is launched from the EMA.

"admin / admin"

Sonus EMS

Same function as the Embedded Management Application above, but launched from the Sonus EMS

From the EMS Element Manager

"admin / admin"

CLI: Command Line Interface

Allows for viewing and configuring the system for calls via a command line interface.

From putty, enter the IP address of the MGMT interface (or virtual management interface), using SSH, port 22

"admin /admin"

BMC: Baseboard
Manager Control

  • Web based GUI access to the FSP (Field Service Port). This is a different Ethernet port than the management ports.
  • Allows for remote powering of the server, and other initial installation functions. Not used during day to day operations.

From web browser, enter IP address of SBC FSP.

"root / superuser"

  
1. 

Access the web based Platform Manager.

  • From web browser, enter "https://" plus IP address of SBC MGMT interface plus ":444". For example "https://10.35.64.55:444".
  • Default user id/password are admin/Sonus12345. This id/password is only for the Platform Manager (NOT shared with CLI or web based configuration manager).
  • The Platform Manager gives the operator an easy to use visual interface to manage the platform. Please see Using Platform Manager for full details.
  • The functions include:
    • System Status 
    • Perform Software Upgrades 
    • Statistics 
    • View system logs 
    • Tools such as Ping
 2.

Access the web based Embedded Management Application (EMA) stand alone.

This will be the most commonly used access method for day to day operation of the system.

  • From web browser, enter IP address of SBC MGMT interface. In most cases the virtual management IP address would be used, so that the operator will automatically be connected to the active unit.
  • Default user id/password are admin/admin
  • On the top right corner, press the "Navigator" button to launch a visual representation of all the configured data.
3.

Access the web based configuration via existing Sonus Insight EMS.

  • For Sonus Insight EMS to access to the SBC, under "Element Management", select the SBC, and a new window launches with the SBC 5000 series web interface.
  • As with other nodes managed by the Insight EMS, the SBC must be configured as a Managed Node. Use the Insight Administration tab to add the SBC as a Managed Node.
4.

Access the command line CLI.

  • The CLI allows you to do the same functions as in the Embedded Management Application (EMA).
  • From putty, enter the IP address of the MGMT interface, using SSH, port 22. In most cases the virtual management IP address would be used, so that the operator will automatically be connected to the active unit.
  • Default user id/password are admin/admin.
  • Press "?" for list of commands, use "Show" to display data.
5.

Access the BMC (Baseboard Management Controller).

  • From web browser, enter IP address of SBC FSP. Can power down the system from this GUI
  • Ability to re-install the OS, upgrade the firmware

Commonly Used Element Names

Below is a list of commonly used element names on the SBC 5000 series platforms.

To see hostname conventions and restrictions, go to System Name and Hostname Conventions page.

Name

Description

Examples


System Name

  • Should be in all CAPS.
  • On a HA system the units are referred to as one name. This name is used in billing,
  • external PSX queries (if done), and system logs.
  • The 1st 3 letters describer the physical location of the system, for example Dallas = DAL
  • The 2nd 3 letters are NBS or SBC to indicate what this machine is.
  • The last two characters are numerical, indicating which number NBS at this particular location

DALNBS01
DALSBC01

Unit #1 of HA name

The System name with an "a" appended on it

DALNBS01a

Unit #2 of HA name

The System name with an "b" appended on it

DALNBS01b

IP Interface Group

Represent the type of far ends.

TRUST_IPIG, UNTRUST_IPIG Or
INTERNAL_IPIG, EXTERNAL_IPIG

IP Interface

Include the packet port number and VLAN tag (if used) in the name

IPIF0
IPIF1
IPIF2_200

Zone

All CAPS

Describes the far end.

INTERNAL, EXTERNAL, CUSTOMER_A

Trunk Groups

  • All CAPS
  • Can use underscores
  • Describes the far end. Will show up in billing records, so discuss with your downstream billing team

CORE, PEER, CUSTOMER_A

Packet Service Profile

Create a unique one for each customer type. Append "PSP" at the end.

SIP_PEER_PSP

Signaling Peer

Lower case "peer" prefixing the trunk group

peerCUSTOMER_A

Routing Label

  • The text "rlTo" prefixing the trunk group.
  • Or prefix "TO_" to the trunk group name.
  • Appears in the billing record

rlToCUSTOMER_A, TO_CUSTOMER_A

IP Signaling Profile

  • Describers the signaling flags associated with the customer. Could be re-used among multiple customers
  • Leave the DEFAULT unmodified, create a new ones as needed.
  • Append "_IPSP" to the trunk group name or type of peer.

CUSTOMER_A_IPSP, ALLPEERS_PSP

Link Detection Groups

The names should include the IP Interface Group.

Include an "A" or "B" to indicate the unit.

UNTRUST_LDG_A, UNTRUST_LDG_B, TRUST_LDG_A, TRUST_LDG_B, MGT_LDG_A,
MGT_LDG_B

 


In this section:

  • No labels