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.
- 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.
- Install the Hardware. Please see Installing SBC 5000 Series Hardware page.
- 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.
- Install SBC Application software. This should be done from the Platform Manager Web page. See Installing SBC Application Software for step-by-step instructions.
- 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:
How to Access
Default User ID / PW
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
"admin / admin"
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
From web browser, enter IP address of SBC FSP.
"root / superuser"
Access the web based Platform Manager.
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.
Access the web based configuration via existing Sonus Insight EMS.
Access the command line CLI.
Access the BMC (Baseboard Management Controller).
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.
Unit #1 of HA name
The System name with an "a" appended on it
Unit #2 of HA name
The System name with an "b" appended on it
IP Interface Group
Represent the type of far ends.
TRUST_IPIG, UNTRUST_IPIG Or
Include the packet port number and VLAN tag (if used) in the name
INTERNAL, EXTERNAL, CUSTOMER_A
CORE, PEER, CUSTOMER_A
Packet Service Profile
Create a unique one for each customer type. Append "PSP" at the end.
Lower case "peer" prefixing the trunk group
IP Signaling Profile
Link Detection Groups
The names should include the IP Interface Group.
UNTRUST_LDG_A, UNTRUST_LDG_B, TRUST_LDG_A, TRUST_LDG_B, MGT_LDG_A,
In this section: