Re: How does incoming caller ID work - and more specifically - can caller ID source data be controlled?

On Mon, 1 Jun 2020 15:31:11 +1000, Gary R. Schmidt wrote:

> This is part of the relevant telephony standards, this is a basic how it 
> does it on GSM, ignoring ACKs and errors and stuff.

Hi Gary,

I appreciate that you provided expert information

Thanks for reminding me there are multiple layers of mobile caller ID:
a. The incoming carrier signal "Calling Number Identification" packet 
b. The default "Phone app" lookup into the system contacts sqlite db

Hence, "control" of the displayed caller ID has at least two levels.
A. The default "Phone app" recognizing the carrier CNI (if any), and, 
B. The default "Phone app" reading the sqlite contacts database (if any).

My goal in understanding is so that I can control the result, such that I
can point the default "Phone app" CID lookup to a desired _local_ database.
-- 
This thread is an offshoot of the sqlilte caller id problems outlined here:
o Does anyone know how the PHONE ties to CONTACTS tiies to SMS on Android 9
<https://groups.google.com/d/msg/comp.mobile.android/EvXtsP9radE/B1wg5WhfAQAJ>