Hi,
when a call comes in, the device's phone application will - somehow - try to display the name of the caller by using the addressbook. How could I add my application as a primary resource for that, i.e. how can I supply the caller's name for an incoming call (WM2003/WM5 both PPC and SmartPhone)
I've been looking at the RTC documentation, but it is unclear whether this will work.
Thanks in advance for any pointers,
Daniel

Supplying name for incoming call
xRuntime
Yes, this should be working for both platforms.
Michael
OscarKwok
Hi Daniel
I doupt that this is possible.
The RTC Client API is not avaliable on the Windows Mobile platform (this is currently only avaliable on the embedded versions of Windows CE). So this won't work
I see the following solution that might work: Create an Outlook Mobile contact containing number and name you want the phone app to display. This should work - povided that you're able to write the contact earlier than the phone app is reading it.
Using SIM phonebook entry instead may work as well.
Does this sound reasonable
Michael
Baris ERGUN
thanks for your help. I think I will have to evaluate which of the two options is better.
Not sure about rewriting the phone app, I am concerned I would have to make a lot of changes for new devices or if a user misses a special functionality.
Daniel
Biswanath Saha
Quick question: if I use the 2003 approach to monitor the GSM TAPI line, will this code also work on Windows Mobile 5
Daniel
Philip Jaques
Yes, it was among the possible solutions I had. Mainly I thought of getting notification when a call was coming in (you suggested the notification broker, would RegNotifyChangeKeyValue work on Windows Mobile 2003 and 5 as well ) and then ...
- ... quickly add the number to Outlook or
- ... display my own popup
In case of (1) it would probably depend when exactly I am notified - i.e. it should be deterministically before the device queries Outlook for the name. In case of (2) I am not sure that this is actually feasible (wouldn't my popup overlap the system one - or can I disable the system one in this case )I currently tend to (2), do you have any professional opinions on that one
Either way, I consider both options sub-optimal and I was hoping there was a better solution like having the device query my application instead.
Daniel
*Rick*
Hi Daniel
The registry notification APIs are new to Windows Mobile 5.0. To support Windows Mobile 2003 as well you'd need to monitor the GSM TAPI line directly.There are a bunch of forum thread dealing with this.
There's a good chance that your notification baloon (popup) will overlap the 'Incomming Call' notification.
Instead of suppressing system notifications why not replace the entire builtn phone application with your own app . I've seen solutions doing this.
Other that these options, I'm not aware of any other way to solve this problem.
Michael
Dika
I should have mentioned that I am using C++ for development.
Also, your solution is the wrong way round :-) It is me who is trying to tell the phone application the name of the caller. I.e. when a call comes in at the moment, I want the device to ask my application for the name of the caller. You could think of my application as a replacement address book.
TIA,
Daniel
NewbieDude
Hi Daniel
For Windows Mobile 5.0 the State and Notification Broker directly provides what you are looking for. Have a look at SystemState.PhoneIncomingCallerName property.
The Windows Mobile 2003 is more complicated:
Go get the number see here: http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=821270&SiteID=1
The use POOM to get the name. More see here: http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=6336&SiteID=1
Hope this helps
Michael