Support for mDNS candidate SDP and resolve mdns if config have option #927
+41
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Webrtc is pushing mDNS support for private IP leak. So if the SDP candidate have mDNS then freeswitch breaking the call saying INCOMPATIBLE_DESTINATION.
mDNS : https://bloggeek.me/psa-mdns-and-local-ice-candidates-are-coming/
Candidate in SDP offer
Freeswitch log Error
Created a patch, which will try to check if the candidate is an IP address. If it is not IP address, then it will check a new config option ice-resolve-candidate set or not. If the flag is set then will try to resolve the mDNS or just drop the candidate and try the other one.
The new flag option ice-resolve-candidate in switch.conf.xml to resolve the candidate.
Can you please review this PR ?.