Page tree
Skip to end of metadata
Go to start of metadata
Introduction

Some platforms require the "Mediasec" functionality.

For the successful use of an encrypted VoIP connection, in addition to a TLS connection for SIP signaling and SRTP for the encryption of the voice, additional SIP headers and SDP attributes are required. When registering (SIP REGISTER), the additional SIP header informs the platform about the use of the encryption type and when establishing a call (SIP INVITE), the encryption type and the range of the encryption (edge ​​to access edge, encryption between the PBX and registration server ) must be included. The SIP headers are based on an IETF draft (https://tools.ietf.org/html/draft-dawes-sipcore-mediasec-parameter-10) but can be seen as a static addition to the SIP signaling.

From software 2.38 or higher, this feature is implemented and needs to be enabled via auto-provisioning.

Auto-provisioning
ParameterDescription
SipProvider.<0-9>.MediasecSupport

0 = Disabled (Default)

1 = Enabled

Example:

<?xml version="1.0" encoding="UTF-8"?>
<provisioning version="1.1" productID="e2">

<nvm>

<param name="SipProvider.0.MediasecSupport" value="1"/>

</nvm>
</provisioning>


  • No labels