
Oracle SBC Security Guide
Software Requirements
S-CX6.2.0 software image or higher is required to support SRTP termination on the SD. It is always
recommended to use the latest S-CX6.2.0 image available on the Oracle customer support portal
(http://www.oracle.com/us/corporate/acquisitions/acmepacket/support/index.html).
Licenses Requirements
No additional licenses are required.
Bootloader requirements
Due to the implementation of a more efficient compression mechanism for software files, S-C(X)6.2.0
and later images compress files using the XZ format (*.xz file extension), as opposed to the previous
practice of GZ compression (*.gz file extension). To recognize image files compressed in the new *.xz
format, a new bootloader was required for the Acme Packet 4250, Acme Packet 4500, and Acme Packet
3800 platforms. The minimum bootloader needed is dated “08/11/2009”, and began shipping with all new
Acme Packet 4500 and Acme Packet 3800 systems as of Sept 22nd, 2009.
810-0086-00 - 09-22-09 - Image C62 Requires Bootloader Upgrade
Design Aspects
Due to the flexibility in the configuration for different SRTP modes, it is needed to consider different
aspects of the desired design for proper configuration.
Configuration Elements
Here is a brief explanation on the elements needed for SRTP configuration. This is just a basic reference,
the configuration of each element will depend on the desired design and will be described in the following
sections.
Security media-security sdes-profile/mikey-profile
This is the first element to configure, where the algorithm and the cryptos to be used are
configured.
For sdes-profile, it is required to define the crypto-suites accepted, and also whether or not
authentication and/or encryption are used for SRTP and if encryption is used for SRTCP. The
“use-ingress-session-params” attribute is used to override previous parameters, specifying that the
SBC will accept encryption/no-encryption, authentication/no-authentication in SRTP/SRTCP,
using in the egress SDP the same session parameter that was received in the ingress SDP.
Finally “egress-offer-format” is used to instruct the SBC on how to build the egress SDP in the
case of both RTP and SRTP are supported at the same time. This is further explained in the next
section.
# show running-config sdes-profile
sdes-profile
name sdes1
crypto-list AES_CM_128_HMAC_SHA1_80
AES_CM_128_HMAC_SHA1_32
srtp-auth enabled
Comentarios a estos manuales