Page History

In this section:

This section describes general tips and other useful information for the

Congratulations on obtaining your 

1. Create an IP plan. This plan lays out what the IP addresses the 

   Spacevars
   0 product

   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

   Spacevars
   0 product

   . This port allows you to access the 

   Spacevars
   0 product

   Baseboard Management Controller (BMC) web page. The BMC allows for system monitoring, power control, and configuring the Management Ports of the

   Spacevars
   0 product

   . 
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 

Background on SIP Trunking and Access

The 

SIP Trunk Groups are a logical connection between the 

Access configurations involve end points (SIP phones, IADs, Soft Clients, etc.) that Register via the 

From an 

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 

Commonly Used Element Names

Below is a list of commonly used element names on the 

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