3 ms·
My point was that this is one way to detect the IP where the client connects to for calls as call signalling, call media transfer and chat messaging all connect
by DominikR 10y ago
My point was that this is one way to detect the IP where the client connects to for calls as call signalling, call media transfer and chat messaging all connect to different IP's.
Once you have that you can block media transfer, or if the clients use peer to peer media transfer at least block the call signalling.
After this it is only a matter of keeping the list of IP's updated which you could easily do by ongoing logging of bandwidth used.
Bandwidth usage pops up in your logs that somehow resembles the profile of a call - investigate by doing a simple test and then block the IP.
- iamdave 10y agoAfter this it is only a matter of keeping the list of IP's updated which you could easily do by ongoing logging of bandwidth used. Erm, well...I suppose this could be done if you're fond of the "navigating through the digestive terminus to arrive at the synovial hinge" method[1]. There are several much easier and much less lossy ways of blocking voice transmissions streams that doesn't involve continuous and arduous logging of IP addresses or even blocks of IP addresses. --- [1] also known as "going through your ass to get to your elbow"
- DominikR 10y agoI wrote myself that there are surely more advanced ways to do that but I'm not a professional in this particular area as I'm not in the business of censoring people or blocking communication. Still my point remains valid I believe: The OP claimed with certainty that no one could know if a call is being made which is wrong. But you can outline your ideas on how to detect a call attempt without "going through your ass to get to your elbow" as you put it. I still feel that blocking IP's or ports is an easy solution for governments that feel the need to censor.