UnigramDev
There is no "accept incoming call" button when installing Unigram 11.9.5 on Windows Server 2022 or 2025
When installing Unigram 11.9.5 on Windows Server 2022 or 2025, when there is an incoming voice call, opens some system? window (not correspondind with Win 10/11 window), in which there is no "Accept call" button.
Hi! First off - your Windows Audio service is off.
I've played around with VHD Microsoft providers for evaluation, but couldn't forward my microphone from local device.
So, my suggestion is - enable audio, try to forward your microphone and see again.
I've played around with VHD Microsoft providers for evaluation, but couldn't forward my microphone from local device.
This is very simple: 1 - You need enable mic. and run Windows Audio Service (Audiosrv) on the Terminal Server. 2 - In the RDP connection You must select - Remote Audio selection: Record from this computer After this Your local mic. will be forwarded to the Terminal Server.
My local mic. is forvrded to TS, and Telegram is working on the TS. After I install all dependences on TS, I can run Unigram. I can make outgoing call, but can't receive incoming call.
@ank1965 Unigram can’t use virtual microphones and webcams, this is a UWP limitation and there are no workarounds.
Unigram can’t use virtual microphones and webcams
This is not quite correct... I can make an outgoing voice call from the terminal server
Making a call != having a working camera/microphone.
For some reason you can make a call, and not receive one in Unigram under these conditions, but I don't think it matters all that much for practical purposes. (i.e - communicating with the other person)
this is a UWP limitation
some strange limitation... I can make an outgoing Unigram voice call from the terminal server (and everything is fine with the voice), but for an incoming call - there is no "Accept call" button... In the incoming call window, I can click the "Settings" button in the upper left corner. I see the "Default" audio device, which is selected, and the "Remote Audio" device, which I cannot select. So incoming calls (voice) do not see the "Remote Audio" device and cannot be redirected to it? It seems to be a limitation of Unigram :)
this is a UWP limitation and there are no workarounds.
but WhatsApp is also a UWP app and it works fine on a terminal server without any limitations...
Making a call != having a working camera/microphone.
@makisukurisu Outgoing call with correctly redirected (incoming and outgoing) voice = working microphone. but with an incoming call - the microphone is not redirected and is unavailable... Accordingly (I think) - the call accept button is unavailable.
@ank1965 Yeah I think some confusion has been made here: the issue is that (I guess) Windows Server (or whatever you’re using) doesn’t have integration for VoIP calls system wise and consequently the app call window is spawned right away, although this has never been fully implemented as it is was unclear (due to Microsoft terrible documentation) if this could ever happen or not. Currently, around 0.6% of calls fail to bind with system VoIP, but this is an issue only for incoming ones (and in this case I don’t have statistics)
Windows Server doesn’t have integration for VoIP calls
@FrayxRulez - maybe... but in my opinion - Unigram installed on Windows Terminal Server does not see the client microphone and speaker during an incoming call, but Unigram has some settings to change the "server" microphone to a microphone that is redirected from the local computer to the terminal server (TS) ... That's why TS does not allow accepting incoming voice calls and does not show the "Accept" button. It seems that in the Unigram interface you cannot select a redirected microphone and speaker for an incoming call, although this option is there. However, such redirection works for an outgoing call.
- ALL and ALWAYS - incoming calls on the terminal server cannot be accepted because there is no "Accept" button.
@ank1965 There is no accept button because it doesn’t exist, that screen is not supposed to show up until you accept the call, but since Windows Server doesn’t support calls, it falls back to that screen directly. Microphone has nothing to do with this.
@ank1965 If you can’t accept the call it’s obvious that incoming/outgoing audio isn’t going to work: the call isn’t connected in the first place.
If you can’t accept the call it’s obvious that incoming/outgoing audio isn’t going to work: the call isn’t connected in the first place.
@FrayxRulez 100% That's right. The first window with the "Accept" call button does not appear on the terminal server. The second window appears immediately as indicated above. It seems as Windows Server limitation.