Replies: 1 comment
-
The answer is: sipsorcery does not include mDNS resolver, but it has an extension point for one: rtcPeerConnectionInstance.GetRtpChannel().MdnsResolve += mDNSResolve; All modern versions of Windows will simply resolve mDNS .local addresses for you if you call So basically IMHO SIPSorcery should default to using the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Same machine and remote connections work fine, but intranet connection (192.168.x.x behind NAT) fails most of the time.
From the log I suspect SIPSorcery completely ignores the ice candidate with .local mDNS name that Chrome sends, so it seems the same as #743 except I don't get any errors regarding this candidate.
Are mDNS candidates like this supported/implemented at all (e.g. should the issue 743 be considered a feature request)?
Can something be done to let the browser drive the connection somehow (if that makes sense)? As seen from the log my app sends out an ice candidate with a local IP, and Chrome client should be able to connect to it.
Here's the example log:
Beta Was this translation helpful? Give feedback.
All reactions