If it was not clear, adding transport-protocol=RTP/SAVP is to rtpengine_manage() parameter.

Cheers, Daniel

On 02.03.18 09:58, Daniel-Constantin Mierla wrote:

Hello,

what UAC is there and what version of freeswitch you are using?

According to RFC 5764 the token shall be UDP/TLS/RTP/SAVPF:

8 Session Description for RTP/SAVP over DTLS

This specification defines new tokens to describe the protocol
used in SDP media descriptions ("m=" lines and their associated
parameters). The new values defined for the proto field are:

o When a RTP/SAVP or RTP/SAVPF [RFC5124] stream is transported over
DTLS with the Datagram Congestion Control Protocol (DCCP), then
the token SHALL be DCCP/TLS/RTP/SAVP or DCCP/TLS/RTP/SAVPF
respectively.

o When a RTP/SAVP or RTP/SAVPF stream is transported over DTLS with
UDP, the token SHALL be UDP/TLS/RTP/SAVP or UDP/TLS/RTP/SAVPF
respectively.

Can you try adding transport-protocol=RTP/SAVP ?

I will try to see what solution can be added to make it flexible to work in both cases...

Cheers, Daniel

On 02.03.18 09:38, Anthony Alba wrote:

...

Hi list, upgrade to 5.1.2 broke my setup due to some different behaviour in rtpengine.so.

I use:

rtpengine_manage("DTLS=off ICE=remove");

1. I don't send any rtpengine_manage flags (RTP UDP SAVP). UAC sends

RTP/SAVP in SDP, rtpengine changes to UDP/TLS/RTP/SAVP.

Reverted to 5.1.1, and see that rtpengine sends RTP/SAVP

2. To SDP body, rtpengine is adding:

a=setup:actpass a=fingerprint:sha-1 D6:D7:DA:AA:2D:DB:AD:94:29:46:FA:C4:D8:AE:0F:03:96:6F:8A:4F

For some reason this broke FreeSWITCH which does not like this.

Anthony

---

Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

I compared the commands from kamailio->rtpengine between 5.1.1 and 5.1.2.

5.1.2 is ignoring DTLS=off:

5.1.1 "Good" SDP b'record-call': b'on', b'DTLS': b'off', b'ICE': b'remove', b'transport-protocol': b'RTP/SAVP', b'call-id': b'9074afcb-0c7d-4b0d-b99f-e97634d077dd', b'received-from': [b'IP4', b'10.13.20.14'], b'from-tag': b'45a0d471-4ab2-48c6-b4fc-0b932ce90195', b'command': b'offer'}

5.1.2 "Bad" SDP b'record-call': b'on', b'ICE': b'remove', b'transport-protocol': b'UDP/TLS/RTP/SAVP', b'call-id': b'be76321a-0072-4d91-a691-d1ab7a8ae46e', b'received-from': [b'IP4', b'10.13.20.14'], b'from-tag': b'cec50da3-e024-4915-bb7a-cd5822c23b09', b'command': b'offer'}

Anthony

It is the same on master branch -- I decided to do the backport after PR 1460:

* https://github.com/kamailio/kamailio/pull/1460

Open an issue on Kamailio's github tracker so it can be analyzed by the developer of rtpengine and come up with the best solution here.

Thanks for all the troubleshooting!

Cheers, Daniel

On 02.03.18 11:27, Anthony Alba wrote:

I think I understand the issue: previously rtpengine module will pass-thru the command DTLS=off.

In 5.1.2 we have, diff from 5.1.1 to 5.1.2:

•                           else if (str_eq(&key, "DTLS"))
  

•                                   ng_flags->transport |= 0x104;
  
  

now 5.1.2 no longer pass-thru DTLS=off, so rtpengine has different behaviour.

DTLS=off is treated as UDP/TLS/RTP/SAVP.

This could be considered a regression as rtpengine uses the DTLS key for its own purposes.

Thanks Anthony

---

Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users