Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conference calls not supported #3

Open
DjArt opened this issue Jul 21, 2019 · 1 comment
Open

Conference calls not supported #3

DjArt opened this issue Jul 21, 2019 · 1 comment
Assignees

Comments

@DjArt
Copy link
Owner

DjArt commented Jul 21, 2019

No description provided.

@DjArt DjArt self-assigned this Jul 21, 2019
@0p3r8
Copy link

0p3r8 commented May 12, 2020

@DjArt Hello,
First of all, many thanks for your Windows.Internal.Calls project - this is really a great job!
I am now trying to use it in Windows 10 running on ARM. A thing that I have noticed, is that there is no proper way for the app to react on incoming call - CallOriginDataRequest PhoneTrigger or CommunicationBlockingAppSetAsActiveTrigger are not working, and portions of UWP extensions for Mobile, like PhoneCallOriginManager.ShowPhoneCallOriginSettingsUI or CommunicationBlockingAppManager.ShowCommunicationBlockingSettingsUI do not seem to work for Universal. However, in your Windows.Internal.Calls project I have noticed some endpoints of interest in PhoneOm exports, like IsCallOriginManagerSupported or PhoneGetActiveAppByType. These imports look like stubs at the moment. Provided that the standard Phone app on Windows 10 reacts on incoming calls, I hope there is a possibility that PhoneOm has proper functions to support this functionality and properly declare an app as a valid call origin provider or communications filter.
I wonder if creating a separate issue would be a more proper place for this discussion?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants