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

Open SidemenuDocs
Docs
Close Sidemenu

Configure an Acme Packet SBC with Telnyxconfigure-an-acme-packet-sbc-with-telnyx

What is Acme Packet?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 guideTelnyx Developers for details of the full setup.

Acme Packet Configuration Guideacme-packet-configuration-guide

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 your portal is up and running, you can start configuring your ACME Packet E-SBC.

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-

sip-interface 
state                enabled 
realm-id             OUTSIDE 
description 
sip-port 
address              X.X.X.X 
port                 5060 
transport-protocol   UDP 
tls-profile 
allow-anonymous      agents-only 
ims-aka-profile 
carriers 
trans-expire         0 
...

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

session-agent 
hostname              sip.telnyx.com 
ip-address             
port                  5060 
state enabled 
app-protocol          SIP 
app-type 
transport-method      UDP 
realm-id              OUTSIDE 
egress-realm-id 
description           Telnyx 
carriers 
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.

session-translation 
id                    includeCallingPlus 
rules-calling         includePlus
rules-called  

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

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

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

realm-config 
identifier            OUTSIDE 
... 
in-translationid 
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.

realm-config 
identifier             clients 
... 
options                preferred-codec=PCMU 
...

Additional Resourcesadditional-resources

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

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


Still stuck? Talk to our support teamTelnyx Developers.

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