Juha Heinanen writes: > rtpengine source code, however, seems to know also these DTLS ones: > > daemon/call.c: .name = "UDP/TLS/RTP/SAVP", > daemon/call.c: .name = "UDP/TLS/RTP/SAVPF", > > can they be used in rtpengine_offer/answer calls even when they are > missing from README?
i made a test where invite has m=audio 50152 UDP/TLS/RTP/SAVP 96 97 8 0 101 and i call rtpengine_offer on it like this: rtpengine_offer(ICE=force replace-session-connection replace-origin via-branch=1 RTP/AVP trust-address) and on 200 OK from callee which has m=audio 50162 RTP/AVP 96 97 8 0 101 i call rtpengine_answer like this: rtpengine_answer(ICE=force UDP/TLS/RTP/SAVP via-branch=2 trust-address) rtpengine complains about it: Nov 17 15:07:32 rautu rtpengine[29718]: Unknown flag encountered: 'UDP/TLS/RTP/SAVP' but still it has converted m line of the 200 OK to caller to this: m=audio 50180 UDP/TLS/RTP/SAVP 96 97 8 0 101 and audio works fine between the RTP/AVP UA (sems) and UDP/TLS/RTP/SAVP UA (baresip). why the unknown flag message? -- juha _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
