[SR-Users] Configuration to use rtpengine for SRTP

Richard Fuchs rfuchs at sipwise.com
Mon Jul 31 13:47:35 CEST 2017


On 30/07/17 11:01 PM, David Cunningham wrote:
> Hi Richard,
>
> Thank you for the reply, it makes sense. We're using a line like this 
> for calls from plain RTP to SRTP, however the SDP arrives at the TLS 
> phone with no mention of encryption. Have you any idea what's wrong?
>
> rtpengine_manage( "force trust-address replace-origin 
> replace-session-connection rtcp-mux-accept rtcp-mux-offer ICE=force 
> RTP/SAVPF" );

It must be getting its SDP from somewhere else then :)

The log clearly shows rtpengine translating the incoming SDP:

...
m=audio 12242 RTP/AVP 0 9 8 10 3 111 5 7 110 97 101
...

to an outgoing SRTP SDP:

...
m=audio 48144 RTP/SAVPF 0 9 8 10 3 111 5 7 110 97 101
...
a=crypto:1 AES_CM_128_HMAC_SHA1_80 
inline:8kPQ4PUH3WRN/kALaLWkBh82FX2WW0WVRVMuAb1O
a=setup:actpass
a=fingerprint:sha-1 
8E:5F:0B:B1:BA:AC:62:3C:C7:A6:F5:04:23:DA:0F:90:48:A3:C6:EF
...

Cheers



More information about the sr-users mailing list