-
Notifications
You must be signed in to change notification settings - Fork 0
Description
It appears (unconfirmed) that if Interlocutor is running in a remote SSH session, i.e., from the SSH command line, Interlocutor is unable to access the microphone. The observed symptom is that Interlocutor sends a PTT_START control message when PTT is asserted from the web UI, and then sends a PTT_END control message when PTT is deasserted, but does not send any voice frames in between.
If this is true, Interlocutor needs to detect this case and explain it to the user.
Another symptom I'm even less sure about is that if Interlocutor is invoked with --setup-audio in a remote SSH session, the microphone test will detect very low audio levels, and refuse to use the microphone. I wasn't actually speaking into the microphone for this test, though, so maybe it was a legitimate detection of low audio.
I speculate this is a security measure to prevent remote eavesdropping. If so, it's not a very thorough one, because I can run Interlocutor remotely from a Screen Sharing session without having this problem.