Configure an Acme Packet SBC with Telnyx

What is Acme Packet?

Acme Packet produces and markets session border controllers (SBCs) to protect SIP-based VoIP networks.

This guide will go through specific configuration for use with your Telnyx Trunk. A good place to start is by reading the entire ACME SBC guide for details of the full setup.

Acme Packet Configuration Guide

Configuring your Telnyx Mission Control Portal

Step-by-Step Guide

For step by step instructions on each of the requirements on the Telnyx Mission Control Portal, please follow this guide.

Once your portal is up and running, you can start configuring your ACME Packet E-SBC.

Configuring Your Acme Packet E-SBC

Step-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:

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:

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

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 policy 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:

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

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 Resources

Take a look at our getting started guide to help with any issues you encounter when setting up your Telnyx Mission Control Portal.

ACME's full configuration guide will also give you more detailed instructions.

Still stuck? Talk to our support team.

Was this page helpful?