[sr-dev] RTPEngine - No support for kernel packet forwarding available
Richard Fuchs
rfuchs at sipwise.com
Tue Mar 2 19:12:54 CET 2021
On 01/03/2021 05.02, Suresh Talasaniya wrote:
> Hello folks,
>
> RTPEngine - No support for kernel packet forwarding available, please
> find the below information/logs.
>
> Mar 1 01:46:45 sp201 rtpengine[14973]: INFO:
> [9ca2e714-95d0-9662-82e9-e89659024d66]: [control] Received command
> 'offer' from 127.0.0.1:52657 <http://127.0.0.1:52657>
> Mar 1 01:46:45 sp201 rtpengine[14973]: NOTICE:
> [9ca2e714-95d0-9662-82e9-e89659024d66]: [core] Creating new call
> Mar 1 01:46:45 sp201 rtpengine[14973]: */ERR:
> [9ca2e714-95d0-9662-82e9-e89659024d66]: [crypto] Failed to init DTLS
> connection: srtp unknown protection profile/*
> Mar 1 01:46:45 sp201 rtpengine[14973]: ERR:
> [9ca2e714-95d0-9662-82e9-e89659024d66]: [crypto] Failed to init DTLS
> connection: srtp unknown protection profile
> Mar 1 01:46:45 sp201 rtpengine[14973]: ERR:
> [9ca2e714-95d0-9662-82e9-e89659024d66]: [crypto] Failed to init DTLS
> connection: srtp unknown protection profile
> Mar 1 01:46:45 sp201 rtpengine[14973]: ERR:
> [9ca2e714-95d0-9662-82e9-e89659024d66]: [crypto] Failed to init DTLS
> connection: srtp unknown protection profile
Maybe your OpenSSL doesn't support AEAD-AES-GCM. Try with a newer
OpenSSL, or try commenting out the two lines:
crypto.c:47: .dtls_name = "SRTP_AEAD_AES_256_GCM",
crypto.c:70: .dtls_name = "SRTP_AEAD_AES_128_GCM",
Cheers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-dev/attachments/20210302/14eac382/attachment.htm>
More information about the sr-dev
mailing list