This is the API V2 documentation. To switch out of beta revert back to our API V1.

Open SidemenuDocs
Close Sidemenu

Configuring an Acme Packet SBC with Telnyxconfiguring-an-acme-packet-sbc-with-telnyx

What is Acme Packet?what-is-acme-packet-

Acme Packet is an Enterprise Session Border Controller (E-SBC), used to protect SIP-based VoIP networks.


Assuming you have your SBC already set up with your IP-PBX, with one or more clients configured and running calls between them, the following guide highlights specific configuration for use with your Telnyx trunk. We recommend reviewing the entire ACME SBC guide hereTelnyx Developers for full setup.


Video Walk-throughvideo-walk-through

Coming soon! This walk-through will demonstrate setting up an IP based connection with ACME SBC. We'll also show you how to assign this connection to a newly purchased DID which will allow you to receive inbound calls. Then we'll walk you through how to assign the connection to an outbound profile such that you can make outbound calls!

Configuring your Telnyx Mission Control Portalconfiguring-your-telnyx-mission-control-portal

Step-by-Step Guidestep-by-step-guide

For step by step instructions on each of the requirements on the Telnyx Mission Control Portal, please follow this guideTelnyx Developers. Once you've configured your Telnyx account, you can now proceed to setup ACME SBC following the guide below.

Configuring Your Acme Packet E-SBCconfiguring-your-acme-packet-e-sbc

Step-by-Step Guidestep-by-step-guide

You are now all set on the Mission Control Portal side and are ready to configure your Telnyx trunk within your ACME SBC system.

Configure your Trunk SIP Interface towards Telnyx:configure-your-trunk-sip-interface-towards-telnyx-

state                enabled 
realm-id             OUTSIDE 
address              X.X.X.X 
port                 5060 
transport-protocol   UDP 
allow-anonymous      agents-only 
trans-expire         0 

Configure your Session Agent towards Telnyx:configure-your-session-agent-towards-telnyx-

port                  5060 
state enabled 
app-protocol          SIP 
transport-method      UDP 
realm-id              OUTSIDE 
description           Telnyx 
allow-next-hop-lp     enabled 
constraints           disabled 

Number TranslationTelnyx Developers:number-translation-

Telnyx accepts the called number on outbound calls in 10 digit, 11 digit and +11 digit format, so there is no need to modify rules for the called number.

However, we have a caller ID policyTelnyx Developers and require the calling number to be in +E.164 number format.

The example below helps append a +1 for US calling numbers. This is the session translation rule on the calling number.

id                    includeCallingPlus 
rules-calling         includePlus

Then define the rule to append +1 to the calling number:

id                    includePlus 
type                  add 
add-string            +1 
add-index             0 
delete-index          0

Then apply the translation rule to take effect on the outside realm:

identifier            OUTSIDE 
out-translationid     includeCallingPlus 

Codecs and setting an example:codecs-and-setting-an-example-

In the ACME SBC, you can set your codec policyTelnyx Developers as you wish. Please see a list of supported codecs on our websiteTelnyx Developers.

In the example below, the SBC will change the codec list for all clients that make outbound calls through the SBC's realm, such that PCMU will be preferred codec offered.

identifier             clients 
options                preferred-codec=PCMU 

Additional Resourcesadditional-resources

Review our getting started guideTelnyx Developers to make sure your Telnyx Mission Control Portal account is setup correctly!

Check out ACME's SBC full guideTelnyx Developers for detailed instructions

Can't find what you're looking for? Chat to our expertsTelnyx Developers.

Was this page helpful?was-this-page-helpful