bgr_bgr

It is quite possible that this API uses the same original data as ncid ... Another thing to consider is that by using this online API to validate incoming calls , One is actually sharing the list of incoming calls with the company (who ever that is , that is providing this online service ) . (Not great for privacy... ). On the other hand , the NCID tool is fully local , but only updated every release . (Althought manual updates are possible for "advanced" users ) .

could you run the following commands under tclsh (on both win 11 machines ) and give me the results : Tcl_GetEncoding encoding names this is what i get on linux : bgr@triton ~ $ tclsh % encoding system utf-8 % encoding names cp860 cp861 cp862 cp863 cp864 tis-620 cp865 cp866 gb2312-raw gb12345 cp950 cp949 cp869 dingbats ksc5601 cp874 macCentEuro macUkraine gb2312 jis0201 euc-cn euc-jp macThai iso8859-10 iso2022-jp jis0208 iso8859-11 iso2022 macIceland iso8859-13 iso8859-14 jis0212 cp737 iso8859-15...

maybe related to that : https://stackoverflow.com/questions/70201846/windows-11-default-api-and-utf-encoding

As the menu seems to be functionnal , try to use it , to change the font used by NCID .. Maybe , the default font used by ncid is missing on that Win 11 machine ? BGR

Hum strange ... does ncid works correctly on the first windows Machine if you unplug one monitor ? (checking if the pb is caused by the dual monitor setting ..) Another possibility is that the font needed by ncid is absent on that particular Windows Machine . Try removing the config file /~/.ncid or whatever that is called on Windows . Sorry , My Windows skills are mostly non existent , and i have no Windows machine at home to reproduce the bug ... Guess i will pass the bucket to other ncid developpers...

Same for me here , I use only POT , no VOIP , however the go-box 100 is connected to my local IP network , the ip connection is what permits the connection to a local database that matches phone numbers with NCID aliase , every time a phone call is received ( VOIP or POT) if the CID has only a number and no name , the go box 100 consults the database , and fills in the NAME . using only POT is not a problem as long as it has CID . BGR On 7/11/22 01:16, Barry Martin wrote: Hi Bgr! The GoBox 100 won't...

Actually , i reckon that a GoBox 100 would be enough for what you want to do , provided that your handsets are CAT-iq 1.0 (or higher) compliant (to be tested , of course ) https://en.wikipedia.org/wiki/Digital_enhanced_cordless_telecommunications#NG-DECT/CAT-iq "CAT-iq 1.0 – "HD Voice" (ETSI TS 102 527-1): wideband audio, calling party line and name identification (CLIP/CNAP)" Bgr On 7/10/22 17:28, Barry Martin wrote: Hi bgr_bgr! Yes, it sounded like you expected the decline. If just the GoBox 100...

Hi Barry I understand and I expected so . Gigaset (formerly Siemens) DECT handsets are probably the most popular in Europe , so are easily found cheaply/second hand . the Go Box 100 , is an hybrid (POT＋VOIP) DECT base , which has internet connectivity + quite a lot of features (some undocumented ) . However it is not very common in North America . some handsets have bluetooth connectivity and can be "remote controled" (undocumented) , there is also one DECT handset model running Android (SL930)....