mirror of https://github.com/sipwise/rtpengine.git
If we receive an SDP with a DTLS fingerprint, by default we adopt the
hash function used for that fingerprint in subsequent communication with
that peer. However, if the SDP is an answer, and we previously used a
different hash function in the offer towards that peer, then a later
re-invite offer would be sent with a different fingerprint, causing an
unexpected DTLS restart. Instead, make sure we don't change fingerprints
if one was already sent.
Change-Id: I603bb86ce2d7121556c161749ed08128dd0b63b2
(cherry picked from commit 8029a4d1cd)
mr9.3.1
parent
ff0009a518
commit
9f9a4dbda1
Loading…
Reference in new issue