SBC Core Tips

In this section:

 

This section describes general tips and other useful information for the

.

 

Congratulations on obtaining your 

platform! Below is a summary of the steps to follow to get your SBC functional.

1. Create an IP plan. This plan lays out what the IP addresses the 
   Unable to show "metadata-from": No such page "_space_variables"
   will use for its management ports, media ports and next hop router. The media ports are used for SIP and RTP traffic. Example IP plans:
   
   1. SBC 5000/7000 series: Creating an IP Plan
   2. SBC SWe: Creating an IP Plan for SBC SWe on VMware or KVM Hypervisor).
2. Install the Hardware. See Installing SBC 5000 Series Hardware or Installing SBC 7000 Series Hardware.
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
   Unable to show "metadata-from": No such page "_space_variables"
   . This port allows you to access the 
   Unable to show "metadata-from": No such page "_space_variables"
   Baseboard Management Controller (BMC) web page. The BMC allows for system monitoring, power control, and configuring the Management Ports of the
   Unable to show "metadata-from": No such page "_space_variables"
   . 
4. Install SBC Application software. This is accomplished from the EMA. See Installing SBC 5000 and 7000 Series Software.

You are now ready to configure your 

platform for processing! See How to Set up a Basic Call Flow.

Background on SIP Trunking and Access

The 

basically acts as a SIP B2BUA (Back to Back User Agent). An important concept on the  is that all signaling and routing is based upon Trunk Groups.

SIP Trunk Groups are a logical connection between the 

and a far end. A SIP Trunk can be one to one or one to many with the  always being a single point. A SIP Trunk for end point (phones) access will be one IP address on the  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 

to their feature server (Class 5, PBX, Hosted PBX, etc.). The  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 

viewpoint, all calls (SIP sessions) involve two trunk groups on the . For example, if Party A wished to connect to Party B via the , two trunk groups on the  are involved, one to Party A and one to Party B. There are generally two types of point-to-point SIP Trunks: 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 

server.

Commonly Used Element Names

Below is a list of commonly used element names on the 

platforms.

To see system name and hostname conventions and restrictions, see System Name and Hostname Naming Conventions page.