RedMax EXtreme EX-LRT Guía para resolver problemas Pagina 114

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 142
  • Tabla de contenidos
  • SOLUCIÓN DE PROBLEMAS
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 113
Oracle SBC Security Guide
The main aspects treated here focused on which traffic is desired under a realm, so each design needs to
consider the following, previous to any configuration:
1. SIP Traffic: SIP over UDP/TCP (unsecured transport) or over TLS (secured transport protocol).
2. Media Traffic: media over RTP, media over SRTP or media over both RTP and SRTP allowed at
the same time. This would differentiate the IP design, since:
a. For media over RTP only or SRTP only, just one IP address will be used for them
b. For media over both RTP/SRTP allowed at the same time, then the recommendation is to
use two different IPs on the same network-interface. One will send RTP traffic and the
other IP will be used for SRTP traffic. This should be considered for correct IP plan
under the network.
Secured/Unsecured Network
By default, the SBC considers that SIP traffic, when SRTP is configured, should run over secured
transport protocol, TLS. If this is not the case, the SBC needs to be instructed to allow SIP traffic over
non-secured transport protocol (UDP/TCP).
sip-interface
state enabled
realm-id access1
description
sip-port
address 11.0.0.11
port 5060
transport-protocol UDP
tls-profile
allow-anonymous all
ims-aka-profile
carriers
secured-network enabled
When secured-network is set to DISABLED under a sip-interface where SRTP is configured, the sip-
interface will only allow SIP over TLS. If SIP is received over UDP/TCP, the SBC will reject the call
with “488 Not Acceptable Here”.
When secured-network is set to ENABLED, the SBC understands the network is secured and it accepts
SIP traffic on UDP/TCP.
Media traffic
Every realm under the configuration should be instructed to the type of media that should handle whether
that be RTP only, SRTP only or both RTP and SRTP. For each realm, it can be differentiated between the
inbound and outbound media type, giving the flexibility of having different protocols for inbound or for
outbound.
The “mode” parameter under the media-sec-policy controls the media protocol defined for each
inbound/outbound flow under a realm.
RTP Only
The “mode” parameter under the inbound/outbound section of the media-sec-policy should be set to RTP.
In this case, no profile should be defined, and the protocol should be set to “None”.
Vista de pagina 113
1 2 ... 109 110 111 112 113 114 115 116 117 118 119 ... 141 142

Comentarios a estos manuales

Sin comentarios