Configuring SBC


At present, the challenge to remain competitive and prevent the loss of customers is great. Telecommunications company must have at their disposal a range of services that can provide reliable communications to their customers. These services include SIP trunk connectivity for clients with existing local IP-PBX or a unified communications solution for Cloud services.


One of the most important services to consider by customers is the High Availability of their connections guaranteed by the provider without the need to establish any additional manual switching or networking or failover rules, we talk about a 1 + 1 protection for all connections of the clients. The APOLOCORE PROXY HA solution offers failover and traffic protection to provide an excellent service.

Alt for image

 

SBC Cluster Configuration

To configure SBC, the first thing we must do is define the routes (cluster routes) that are made up of main and backup, generating the 1 + 1 configuration for switching services.

Alt for image

Perform the following steps:

  • Click on the SBC / Routes Menu. Enter the IP of your main server with the form: sip: ip address: port. Example: sip: 10.90.10.15: 5060.
  • Define if it is Primary or Backup.
  • Enter description.

Consider that in this option you can only declare 2 servers to perform the 1 + 1.

    In the SIP Status column you can monitor the status of the connection between SBC Apolocore and the declared SIP server.

Configuring Trunks

Clients that are configured SBC Menu / Trunks and will be routed to the Primary Server taking into account the prefix to identify the client on SIP servers (Softswitch).

You should consider that the same IP cannot be repeated.

Alt for image

SBC Register Management

In the SBC Registration menu, you can view the registered customers with very useful information for the management.

Additionally you can execute actions by selecting a client or several with multiple selection to perform security actions.

All SIP packets will be sent to the main server and if there is a failure of the main server, it will switch over 30 seconds to the backup server.

When the main server is re-established, the switching will be done instantly without impact on the clients.

Alt for image

 


Getting Started
Product Features
Security
General
Help