Encryption on SIP trunk to 3rd party peer

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • patdunne
    Aspiring Member
    • May 2014
    • 1

    Encryption on SIP trunk to 3rd party peer

    Having an issue enabling encryption on a SIP trunk to an IVR with Asterick telephony services at the front end. We have the control channel successfully encrypted but cannot get the Bearer(media) channel encrypted - see below.

    SRTP and SRTCP packet payloads are encrypted by default. The UNENCRYPTED_SRTCP and UNENCRYPTED_SRTP session parameters modify the default behavior of the crypto-suites with which they are used: * UNENCRYPTED_SRTCP signals that the SRTCP packet payloads are not encrypted. * UNENCRYPTED_SRTP signals that the SRTP packet payloads are not encrypted. In the offer/answer model, these parameters are negotiated. If UNENCRYPTED_SRTCP is signaled for the session, then the SRTCP E bit MUST be clear (0) in all SRTCP messages. If the default is used, all SRTCP messages are encrypted, and the E bit MUST be set (1) on all SRTCP messages.
    The problem is that the Avaya SIP component does not support encrypted SRTCP. It is the offerer in the scenario above and it is setting the parameter in the INVITE and there is no way to stop it so the implication is that it cannot support it. RFC4568 however says that SRTCP payloads are encrypted by default making the Avaya the exception by not supporting encrypted SRTCP.
    All help greatly appreciated.
  • vchitramohan
    Aspiring Member
    .
    • Mar 2011
    • 2

    #2
    Avaya design documentation says the following:
    Avaya endpoints which cannot support secure RTCP must properly negotiate it out in the answer using rules from RFC3264 and RFC4568.This is achieved by adding the UNENCRYPTED_SRTCP parameter to the offer or answer. UNENCRYPTED_SRTCP is a negotiated parameter per RFC4568. Rules for this negotiation are as follows:
    Offerer:
    Media aware network elements that support encrypted SRTCP generate offers without the
    UNENCRYPTED_SRTCP parameter.
    Media aware network elements that do not support encrypted SRTCP generate offers with the
    UNENCRYPTED_SRTCP parameter.
    Answerer:
    Media aware network elements that support encrypted SRTCP and receive offers with the
    UNENCRYPTED_SRTCP parameter, echo the UNENCRYPTED_SRTCP parameter in the answer on the chosen crypto set. Unencrypted SRTCP is used in both directions.
    Media aware network elements that support encrypted SRTCP and receive offers without the
    UNENCRYPTED_SRTCP parameter, use encrypted SRTCP in both directions
    Media aware network elements that do not support encrypted SRTCP and receive offers with the
    UNENCRYPTED_SRTCP parameter, echo the UNENCRYPTED_SRTCP parameter in the answer on the chosen crypto set. Unencrypted SRTCP is used in both directions.
    Media aware network elements that do not support encrypted SRTCP and receive offers without the
    UNENCRYPTED_SRTCP parameter, add the UNENCRYPTED_SRTCP parameter in the answer on
    the chosen crypto set. Unencrypted SRTCP is used in both directions.

    Comment

    Loading