Page History
In this section:
Panel | |
---|---|
|
This section describes general tips and other useful information for the
Spacevars | ||
---|---|---|
|
Note |
---|
Hardware and BMC-related topics do not apply to the SBC SWe platform. |
Congratulations on obtaining your
Spacevars | ||
---|---|---|
|
- Create an IP plan. This plan lays out what the IP addresses the
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:Spacevars 0 product - SBC 7000 series: Creating an IP Plan
- SBC SWe: Creating an IP Plan for SBC SWe on VMware or KVM Hypervisor).
- Install the Hardware. See Installing SBC 5400 Hardware or Installing SBC 7000 Hardware.
- 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
. This port allows you to access theSpacevars 0 product
Baseboard Management Controller (BMC) web page. The BMC allows for system monitoring, power control, and configuring the Management Ports of theSpacevars 0 product
.Spacevars 0 product - Install SBC Application software. This is accomplished from the EMA. See Installing SBC 7000 Series Software.
You are now ready to configure your
Spacevars | ||
---|---|---|
|
Background on SIP Trunking and Access
The
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
SIP Trunk Groups are a logical connection between the
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Access configurations involve end points (SIP phones, IADs, Soft Clients, etc.) that Register via the
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
From an
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
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
Spacevars | ||
---|---|---|
|
Commonly Used Element Names
Below is a list of commonly used element names on the
Spacevars | ||
---|---|---|
|
To see system name and hostname conventions and restrictions, see System Name and Hostname Naming Conventions page.
Name | Description | Examples |
---|---|---|
|
| DALNBS01 |
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 |
IP Interface | Include the packet port number and VLAN tag (if used) in the name | IPIF0 |
Zone | All CAPS | INTERNAL, EXTERNAL, CUSTOMER_A |
Trunk Groups |
| 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 |
| rlToCUSTOMER_A, TO_CUSTOMER_A |
IP Signaling Profile |
| CUSTOMER_A_IPSP ALLPEERS_PSP |
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, |