Very pleased with NCID – so much quiter here with the spam calls being
sent to ‘ground’! Looking for an option and not sure what is called so
makes it difficult to find. What I would like to do is display the
output from ncidd.alias to the CID units on the landline. The alias
displays fine on the computer but I would like it to the physical
telephones. I realize this will either need a second USB modem or some
sort of external adapter (provide enough power for REN 5 and all that).
Software concept:
Incoming ==> ncid.alias ==> New output to telephones
| WIRELESS CALLER | Barry -cell phn | Barry -cell phn |
| 563-319-1234 | | 563-319-1234 |
Hardware concept:
Telephone service ==> Modem 1 ==> Raspberry Pi with NCID ==> Modem 2 →
telephones
Would be nice (less expensive!) to be able to plug all the house phones
into Modem 2 but probably insufficient power (the REN stuff), so
probably Modem 2 into a box to power the phones. (And yes, so now what
is that box called, and any U.S. version suggestions.)
TIA – apologizing for the vagueness – just don’t know some of the
terminology.
Barry,
I am not aware of any currently available devices that can cost effectively accomplish the manipulation of CID data via NCID for for "standard" CID devices on a landline.
The idea has been bounced around the NCID dev team on several occasions and there are a couple ideas that are currently being pursued. The one I am working on is a USB connected device that has IN (landline from phone company) and OUT (to phones in home) RJ11 connectors and one of the features is the circuitry needed to inject CID information from NCID to the downstream phones. How well "CID injection" will work remains to be seen as it is not known how picky existing "standard" CID display devices will tolerate (perceived) deviations from the Bellcore Caller ID (Type I and II) specifications.
In the meantime, I currently use NCIDdisplay, ncid-prowl, and NCIDwebclient for displaying NCID information on devices that are easily accessible depending on my location. There are lots of other output modules that may be more suitable for your preferences.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
(My drawing really got schmooshed!!) Yes, 'inject' was a term I was also considering when creating my inquiry. Actually your device sound precisely like what I want -- can I volunteer to be a guinea pig?! :) Here have several variants of Caller ID displays: cordless phones of various brands, Caller ID Boxes -- (trying to present selectable resume [grin]).
The outputs to other devices all look to require a second device: monitor, cell phone, etc. , which to me sort of defeats the purpose of carrying the cordless phone. Right for some occasions, just not right for here. The 'injector' seems like it would be the right one.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi BTodCox!
Quickly found my experiment to eventually inject NCID’s alias information into the telephone line isn’t nearly as as as it appears on the surface! Getting a text stream out is easy. Putting it in a format usable by the CID equipment: not so easy! Frequency shift keying, checksums, … Made me appreciate more what the people engineering this stuff go through! And yes, I still wish to be a volunteer tester where the time comes.
Barry
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It is doable ( i do it) . (in a round about way (meaning i do not alter CID , but get the handset to display the alias ) )ut you need Gigaset DECT handsets ( some specific models eg :sl450 , s850, etc , other gigaset TDECT handsets are possible , )
and a gigaset "go box 100" base as DECT base 。
If you are willing to invest into a Gigaset setup (or already have one )
i can explain how to do it and provide the software and scripts .
otherwise , not much point ,unless you just want to know how , it is done .
let me know if you are interested , if yes , i will make the effort to explain in detail :
[phone call with CID = NUMBER]
|
|
|
|
[local database fed with ncid aliases, accessible via http ]<-----> [ GO 100 DECT base ]
|
|
| [ gigaset handset displays NCID alias ]
PS : suppressing the first ring is a completely different subject and involves using "Digitone pro serie blocker"set in "business mode" (the way i do it ) .
BGR (NCID dev )
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi bgr_bgr!
I’m going to respectfully decline – Amazon U.S. does appear to sell the U.S. version of the cordless phone and so possibly also a Go Box, just don’t need to nor have the spare cash to replace the house phone system. Your project looks interesting - - you and BTodCox look to be doing similar – at least from the surface.
Barry
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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).
In case other people are interested ,
Here is a suitable Gigaset handsets+base pack available on amazon.com
(C530 IP) . The DECT base is a rebranded GO 100 box , but the handsets
have no bluetooth
(not needed for NCID alias display)
Other DECT brands popular in US (Yealink , Panasonic ) might offer
similar functionnalities , but , i am not familiar .
BGR
On 7/10/22 02:52, Barry Martin wrote:
Hi bgr_bgr!
I’m going to respectfully decline – Amazon U.S. does appear to sell
the U.S. version of the cordless phone and so possibly also a Go Box,
just don’t need to nor have the spare cash to replace the house phone
system. Your project looks interesting - - you and BTodCox look to be
doing similar – at least from the surface.
Barry
Yes, it sounded like you expected the decline. If just the GoBox 100 (U.S. equivalent, of course) probably would have considered; switching over the entire telephone system in the house -- just too pricey.
Barry
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"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
(U.S. equivalent, of course) probably would have considered; switching
over the entire telephone system in the house -- just too pricey.
Hi Bgr!
The GoBox 100 won't work here: have plain ol' POTS ( which is partially redundant!). "Advanced" part is the system feed is VoIP, but after the converter box it's very basic.
Barry
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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 work here: have plain ol' POTS ( which is
partially redundant!). "Advanced" part is the system feed is VoIP, but
after the converter box it's very basic.
Barry
Looks like a very good system, just not sufficiently compatible wih the thrown together over the years system here: about half is wired phones, some with built-in Caller ID, some with external Caller ID devices. Remainder are cordless phones but not of the DECT version.
Did come across a decent technical description at the Conrad site (even better: a few years ago shopped there with my late Aunt when visiting her in Vienna – replaced her microwave and a few other items). Anyway, doesn’t appear to have a ‘wired output’ which is what I need to connect to the wired phone system I have here.
Barry
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi!
Very pleased with NCID – so much quiter here with the spam calls being
sent to ‘ground’! Looking for an option and not sure what is called so
makes it difficult to find. What I would like to do is display the
output from ncidd.alias to the CID units on the landline. The alias
displays fine on the computer but I would like it to the physical
telephones. I realize this will either need a second USB modem or some
sort of external adapter (provide enough power for REN 5 and all that).
Software concept:
Incoming ==> ncid.alias ==> New output to telephones
| WIRELESS CALLER | Barry -cell phn | Barry -cell phn |
| 563-319-1234 | | 563-319-1234 |
Hardware concept:
Telephone service ==> Modem 1 ==> Raspberry Pi with NCID ==> Modem 2 →
telephones
Would be nice (less expensive!) to be able to plug all the house phones
into Modem 2 but probably insufficient power (the REN stuff), so
probably Modem 2 into a box to power the phones. (And yes, so now what
is that box called, and any U.S. version suggestions.)
TIA – apologizing for the vagueness – just don’t know some of the
terminology.
Barry
Barry,
I am not aware of any currently available devices that can cost effectively accomplish the manipulation of CID data via NCID for for "standard" CID devices on a landline.
The idea has been bounced around the NCID dev team on several occasions and there are a couple ideas that are currently being pursued. The one I am working on is a USB connected device that has IN (landline from phone company) and OUT (to phones in home) RJ11 connectors and one of the features is the circuitry needed to inject CID information from NCID to the downstream phones. How well "CID injection" will work remains to be seen as it is not known how picky existing "standard" CID display devices will tolerate (perceived) deviations from the Bellcore Caller ID (Type I and II) specifications.
In the meantime, I currently use NCIDdisplay, ncid-prowl, and NCIDwebclient for displaying NCID information on devices that are easily accessible depending on my location. There are lots of other output modules that may be more suitable for your preferences.
Hi BTodCox!
(My drawing really got schmooshed!!) Yes, 'inject' was a term I was also considering when creating my inquiry. Actually your device sound precisely like what I want -- can I volunteer to be a guinea pig?! :) Here have several variants of Caller ID displays: cordless phones of various brands, Caller ID Boxes -- (trying to present selectable resume [grin]).
The outputs to other devices all look to require a second device: monitor, cell phone, etc. , which to me sort of defeats the purpose of carrying the cordless phone. Right for some occasions, just not right for here. The 'injector' seems like it would be the right one.
Barry,
I will make a note to reach out to you when we have prototypes that have reasonable functionality. Probably late this year or early next year.
OK, thanks! In the meantime I'll probably play with stuff here from the hobbyist viewpoint. As long as the smoke doesn't get let out!
Hi BTodCox!
Quickly found my experiment to eventually inject NCID’s alias information into the telephone line isn’t nearly as as as it appears on the surface! Getting a text stream out is easy. Putting it in a format usable by the CID equipment: not so easy! Frequency shift keying, checksums, … Made me appreciate more what the people engineering this stuff go through! And yes, I still wish to be a volunteer tester where the time comes.
Barry
It is doable ( i do it) . (in a round about way (meaning i do not alter CID , but get the handset to display the alias ) )ut you need Gigaset DECT handsets ( some specific models eg :sl450 , s850, etc , other gigaset TDECT handsets are possible , )
and a gigaset "go box 100" base as DECT base 。
https://www.gigaset.com/de_de/gigaset-go-box-100/
https://www.gigaset.com/hq_en/gigaset-sl450hx-metal-black/
https://www.gigaset.com/hq_en/cms/home/press/news-detail/news/detail/News/the-new-gigaset-s850-the-smart-all-rounder.html
If you are willing to invest into a Gigaset setup (or already have one )
i can explain how to do it and provide the software and scripts .
otherwise , not much point ,unless you just want to know how , it is done .
let me know if you are interested , if yes , i will make the effort to explain in detail :
[local database fed with ncid aliases, accessible via http ]<-----> [ GO 100 DECT base ]
|
|
|
[ gigaset handset displays NCID alias ]
PS : suppressing the first ring is a completely different subject and involves using "Digitone pro serie blocker"set in "business mode" (the way i do it ) .
BGR (NCID dev )
Hi bgr_bgr!
I’m going to respectfully decline – Amazon U.S. does appear to sell the U.S. version of the cordless phone and so possibly also a Go Box, just don’t need to nor have the spare cash to replace the house phone system. Your project looks interesting - - you and BTodCox look to be doing similar – at least from the surface.
Barry
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).
In case other people are interested ,
Here is a suitable Gigaset handsets+base pack available on amazon.com
(C530 IP) . The DECT base is a rebranded GO 100 box , but the handsets
have no bluetooth
(not needed for NCID alias display)
https://www.amazon.com/Gigaset-C530-IP-Cordless-Businesses/dp/B08M6C4T2R/ref=pd_rhf_se_s_pd_sbs_rvi_sccl_2_2/145-8500283-1735222?pd_rd_w=PwFmm&content-id=amzn1.sym.80dc3982-f1a9-4e70-830e-7a37a0660538&pf_rd_p=80dc3982-f1a9-4e70-830e-7a37a0660538&pf_rd_r=CDCT9BCRDKADNHR5J881&pd_rd_wg=WRWPt&pd_rd_r=e4dc2139-eb5c-439c-823f-1a29b6b7868d&pd_rd_i=B08M6C4T2R&psc=1
The .
Other DECT brands popular in US (Yealink , Panasonic ) might offer
similar functionnalities , but , i am not familiar .
BGR
On 7/10/22 02:52, Barry Martin wrote:
Hi bgr_bgr!
Yes, it sounded like you expected the decline. If just the GoBox 100 (U.S. equivalent, of course) probably would have considered; switching over the entire telephone system in the house -- just too pricey.
Barry
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!
The GoBox 100 won't work here: have plain ol' POTS ( which is partially redundant!). "Advanced" part is the system feed is VoIP, but after the converter box it's very basic.
Barry
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!
Looks like a very good system, just not sufficiently compatible wih the thrown together over the years system here: about half is wired phones, some with built-in Caller ID, some with external Caller ID devices. Remainder are cordless phones but not of the DECT version.
Did come across a decent technical description at the Conrad site (even better: a few years ago shopped there with my late Aunt when visiting her in Vienna – replaced her microwave and a few other items). Anyway, doesn’t appear to have a ‘wired output’ which is what I need to connect to the wired phone system I have here.
Barry