-
-
![image](https://user-images.githubusercontent.com/1320252/58152555-6f45cb00-7c9f-11e9-89e4-a7cff8d2404b.png)
![image](https://user-images.githubusercontent.com/1320252/58152540-63f29f80-7c9f-11e9-91…
-
I propose that if shadowsocks server receives a (TCP/UDP) connection to 0.0.0.0:53 or [::]:53, it should redirect the connection to current default DNS resolver (on Linux, this might be handled by `re…
-
This is a FAQ/POLL that needs to be ongoing.
The current website instructions allow us to track who has done them by looking at [forks](/../../cgm-remote-monitor/network/members) of [cgm-remote-monit…
-
```
What steps will reproduce the problem?
1. Attempt to register a sipML client to webrtc2sip 2.6.0 with DTLS/SRTP
enabled.
What is the expected output? What do you see instead?
Expected response …
-
```
What steps will reproduce the problem?
1. Attempt to register a sipML client to webrtc2sip 2.6.0 with DTLS/SRTP
enabled.
What is the expected output? What do you see instead?
Expected response …
-
```
What steps will reproduce the problem?
1. Attempt to register a sipML client to webrtc2sip 2.6.0 with DTLS/SRTP
enabled.
What is the expected output? What do you see instead?
Expected response …
-
```
What steps will reproduce the problem?
1. Attempt to register a sipML client to webrtc2sip 2.6.0 with DTLS/SRTP
enabled.
What is the expected output? What do you see instead?
Expected response …
-
```
What steps will reproduce the problem?
1. Attempt to register a sipML client to webrtc2sip 2.6.0 with DTLS/SRTP
enabled.
What is the expected output? What do you see instead?
Expected response …
-