Support intercepting incoming calls and message
It would be great if we will get some support for intercepting incoming calls and smss
Hi, as part of Windows Phone 8.1, it is possible for some apps can register to receive system events, including incoming SMS messages, and then act upon them.
It’s important to note that these APIs and events are intended for use by device manufacturers primarily. In order for the APIs to be used in your Windows Phone Store app, your Windows Phone Store publisher account needs to be provided with permission to use these device capabilities (open up a Dev Center support ticket with your request).
For more information…
Using SMS events: Check out the Build 2014 session (http://channel9.msdn.com/Events/Build/2014/2-518) or MSDN docs on background tasks (http://msdn.microsoft.com/en-us/library/windowsphone/develop/hh977056.aspx)
Seyyed Soroosh Hosseinalipour commented
where is Incoming calls?!!!
There is no call intercepting API. Only block exact phones. Please allow interact with calls same way as with Messages. I need access to incoming calls to proceed tracking of possible fake/scam calls without blocking. For example I know VOIP-company that allow use their range to some scam calls, but this can be valid calls also. So I need notify user about threat but not block
Hi, I've trying to get this access via a support ticket as suggested for about a 2 weeks now. The support guys are saying that I need to write the app and submit it and just see if it passes. The problem there is that I would need to sink time into developing an app without knowing if it would be accepted and even bigger issue is I wouldn't be able to test it. Would someone from Microsoft be able to supply what we need to ask for or what the name of the permission is? Thanks
Daniel Halan commented
Daniel Halan commented
@JesperBalle and all, regarding Intercepting / Logging Phone call. There are few requests available (that would benefit of being merged)
and possibly more...
Hey Folks, at least we can develop GAMES and other IMPORTANT apps for WP8. Who needs features like RSAP for in-car-use or phonecall-events for feeding business apps. Just code GAMES. For all others, move on to android, there's more care for the 'developer ecosystem'.
Don't think you can get credit for this one yet, since it isn't available to all developers.
That is not done at all. The API is just for SMS not for incoming calls. I want the phone number of the callee as it is available on Android and iOS. Can that be done with this API?
I cannot open such a Dev Center support ticket. How can I do that?
All I want is a simple "SMS recieved" or "SMS unread" flag so my app can sound a custom alarm. This Information this would open up a few more much needed app possibilities. Surely making this available would not create any privacy issues?
Costin Morariu commented
Can you please be a little bit more specific on "open up a Dev Center ticket ...". We are trying for couple of days to get those permissions without success so far.
We opened up an App submission and certification ticket on Certifications policies category. They were not able to help on this and asked to drop an email to Sysdev@Microsoft.com. Seems that they are unsure about how to handle this too.
Jesper Balle commented
@nami have you created a new suggestion for handling incoming calls?
I would really like to see apps like Truecaller on Windows Phone
Ben Edwards commented
The app I had in mind was for customer billing. "How much time did I talk to a customer"? "How many SMS messages did I have with a particular customer?" "What was said?" I just want readonly access to my phones call history and sms history. I would be happy with just a way to query those guys. It would be nice to do other things as well but couldn't you just start with something simple like that? That doesn't seem like a huge ask that would require a ton of engineering.
Also as an aside "what would iPhone/Android do" should never enter into you guys decisions on whats best for the platform. Just do whats best for your users and developers and the rest will take care of itself. That message just leaves me with a bad taste in my mouth.
Nami Zarringhalam commented
@Cliff, I Think it is really a shame that the model Microsoft has chosen to follow right now limits the developers. The best solution would be one which at least has the same options as the background image - let the user chose one application which has access to the Caller ID or incoming SMS and let the developers work to create the best app for the user... That would be a win - win, don't you agree?
Also none of the OEMs aside from Nokia that we have spoken to actually know anything about giving access to these features to app developers they want to pre-load. I'm one of the founders of Truecaller app which is why I know this.
Ian Ringrose commented
So does that allow an app to display the customer record for the person that is calling my phone? And to keep to displayed while I talk.
Hi folks, weighing in on this thread a bit with some color commentary. Engineering has been looking at this for some time, and the API was added for mobile operators and hardware manufacturers for obvious reasons.
And while third party app-directed SMS scenarios are nice to have for obvious reasons, they also bump into a few issues: (a) they can run into customer billing issues for sending SMS silently and (b) obvious potential privacy issues for receiving SMS. And while the capability is available on Android (but I don't believe Android operates under the caveat emptor model), it isn't available on iOS.
Digging into this a bit further, app devs tend to want the capability to receive messages on specific “filters” exclusively (only the app gets the message rather than it being broadcast to every application). However, this type of exclusive delivery would require assignment/gating of “filters” at the OS level that runs into all sorts of problems (who gets to register for a filter first? is registration static or dynamic? how are collisions handled? how are revocations handled? what about non-store or side-loaded apps? etc.).
As a result, the team doesn't have plans to provide this capability at this time to the broad developer ecosystem, but please feel free to chime in with additional thoughts on the topic.
Intercepting calls still seems impossible. MSFT: why restricting developers so much?
Please help developers in stead of restricting them. I think Microsoft need good developers for the current lack of apps. Restricting is not a good practive to motivate developers to make great apps.
Ashish Sharma commented
How to intercept incoming calls like truecaller do in other phones??
I watched the video and read the documentation you provided. But I didn't see how to register to intercept incoming calls. Can you be more specific on the link. thanks
Jakob Andersen commented
There is still no support for intercepting SMS messages since the "SystemTriggerType.SmsReceived" is not available for 3rd party applications. So no change from wp8.
Ehad Akeila commented
Great effort. However, I didnt see there is a trigger for an incoming call