ACME

Home / SBC / ACME

ACME SBC ACLI Command Tree

ACME SBC ACLI Command Tree

The ACLI is an administrative interface that communicates with other components of the ACME Net-Net system. The ACLI is a single DOS or Linux-like, line-by-line entry interface.

You can access the ACLI either through a direct console connection, a Telnet connection or an SSH connection.

 

acme_conf_terminal_tree_1s

[…]

H.323 PBX with ACME SBC

H.323 PBX with ACME SBC

H.323 PBX with ACME SBC : This example shows connecting an H.323 PBX to a SIP trunk with ACME SBC. The SD performs the conversion of H.323 to SIP.

 

H323_PBX_img1

 

Example Configuration : 

 

access-control

realm-id SIPtrunk
description
source-address 172.16.122.101:5060
destination-address 0.0.0.0
application-protocol SIP
transport-protocol UDP

[…]

Multi-site PBX Connectivity in ACME SBC

Multi-site PBX Connectivity in ACME SBC

Multi-site PBX Connectivity in ACME SBC : Consider the scenario where the Enterprise has multiple branch offices, each with one or more PBXs deployed. Should there be an ACME Net-Net SD on the network edge of each of the branch offices, then the Basic PBX Connectivity approach in the section above should be used at each office location.
However, should the ACME Net-Net SD be deployed in a data center as an aggregation point for many or all branch offices, then a multi-realm approach is recommended.
Typically, routing per branch office would be on a separate VLAN id. There is a one-to-one correlation of VLAN id and realm. Additionally, there is a one-to-one correlation of realm and sip-interface. Hence, the simplest model of multi-site PBX connectivity would require the Net-Net SD be configured with as […]

Topology Hiding in ACME SBC

Topology Hiding in ACME SBC

SIP Manipulation

You can do almost any SIP header manipulation in SIP Manipulation section in ACME SBC. I will show how to do topology hiding in Acme SBC with Header Manipulation Rules (HMRs).

HMR_manip1

[…]

ACME SBC Functions & Features

ACME SBC Functions & Features

Security :

  • SBC DoS/DDoS protection
    • Protect SBC from DoS/DDoS attack and other malicious attacks
    • Protect SBC from non-malicious overloads
    • Allow trusted/authenticated users access while under DoS attack
    • Dynamically accept or reject traffic based on device behavior
  • Access control
    • Filter specific devices or whole networks on a per application basis
    • Permit access to known devices or networks
    • Permit access to from authorized/registered users; permit or deny access to mask users
    • Dynamically accept or reject traffic based on device behavior
    • Accept media only for authorized sessions
  • Topology hiding & privacy
    • Hide core topology to prevent directed attacks and preserve confidentiality
    • Mask user information for privacy and confidentality
    • Protect users and service provider infrastracture from eavesdroppers, identity thieves and fraud
    • Secure L2 and L3 VPN customers by maintaining security isolation between VPNs ; support inter-VPN sessions
    • Support for inter-VPN […]
Go to Top