Does the ncidd server allow for any kind of authentication/authorization? I installed the server and connected my phone and it just works... which is great in some ways, but I don't want to have my call list available for read/write on the open internet.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Alternately, perhaps a backend that has this built in (kinto, gun.js, feathers.js,....) with frontends for clients which speak the existing non-secured protocol?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There has not been any work done to change the open messaging.
I think most of us run it in private households, behind a NAT firewall, and don't have it exposed to the entire internet.
Changing this would require significant change to the server and all of the clients.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Emiliano,
For a less abrupt answer, I thank you for pointing me to stunnel, I didn't know it existed.
I am also looking into DTLS.
Some work was done earlier to try Firebase Messaging Service for the android devices, but it seemed to require a shared central server that would require registration of users.
Were you really wanting to see caller information outside of a home network or intranet?
Ed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That's what I was looking for, yes. I want caller ID for our corporate
directory for Android phones. I can download a copy of the directory, now I
just need a way to get caller ID from it. Given that it's our full company
phone list, I'd rather not put it out there for anyone to trawl through.
Hi Emiliano,
For a less abrupt answer, I thank you for pointing me to stunnel, I didn't
know it existed.
I am also looking into DTLS.
Some work was done earlier to try Firebase Messaging Service for the
android devices, but it seemed to require a shared central server that
would require registration of users.
Were you really wanting to see caller information outside of a home
network or intranet?
If I'm reading this right, there are two ways you can add your phone list to ncid, one is to add the phone numbers to the /etc/ncid/ncidd.whitelist with "#=" comments to associate the names with the numbers. e.g. 6137631234 #= Fred Smith will pass Fred's name to the Android when a call comes from that number. This can also be done with an alias.
Since I'm open to suggestions, how were you picturing authenticating a host of android devices with the server? Options seem to include simple password, device id + password, and device id alone. (And how many is "a host" ?)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In my specific case, "a host" would be around 4k if I get it beyond POC
(not a given, our IT dept is very conservative, for good reasons). But
right now, I'm just trying to get it to work for myself.
A simple, global password would be OK for a poc. Device ID would be better
if I can build a way to register people without too much technical
complexity; this would be done by our service desk. If the device ID can't
be readily spoofed, a device ID would suffice. A bearer token would also
do.
For per-user passwords, PAM would be the ideal, or LDAP, but a simple
passwd style file would do.
Hi Emiliano, sorry no one replied to your two June 13, 2017 postings. I checked and I never got a notification from SourceForge that you'd done so. We weren't ignoring you, promise!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm thinking that NCID does something different from what you're looking for.
You seem to be looking for a company-wide way of getting callerid onto 4000 android clients devices -- presumably from 4000 individual desktop phones, and also out to a similar number of desktop clients. I expect that this would be each person wanting caller ID for their own phone.
NCID is built to get caller ID from a small number of devices, like a single modem and a few SIP lines, and to share it with all of the clients. Each call and message is broadcast to every client device.
You probably don't want all of the incoming calls sent to all of the client devices.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ah, right. I don't need anything on the desktop, indeed just many mobile
phones that can get calls from colleagues, and we want caller ID from the
corporate directory without putting the corporate directory in every
individual person's contact list.
If I understand this right, you were hoping for a tool that would add name information to a call when one of your many android devices calls another.
Right now, when Alfred calls Beth, Beth only sees a number. You were hoping to dip into a central list of names to add the name "Alfred" to the call to Beth.
NCID does not do this. It is meant to watch a small number of phone lines and tell every subscribed client about an incoming call.
For my example, it would tell all 4000 of your devices that Alfred was calling Beth.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If I understand this right, you were hoping for a tool that would add name
information to a call when one of your many android devices calls another.
Right now, when Alfred calls Beth, Beth only sees a number. You were
hoping to dip into a central list of names to add the name "Alfred" to the
call to Beth.
NCID does not do this. It is meant to watch a small number of phone lines
and tell every subscribed client about an incoming call.
For my example, it would tell all 4000 of your devices that Alfred was
calling Beth.
All three of the above seem to have search capability in case Alfred doesn't know Beth's number.
To do the equivalent in NCID, the NCID Android app would need modifying as well as the NCID server to essentially use NCID's alias file, plus add a secure connection or login/password that you were originally asking about. I'm not sure how well this would scale for 4K Android phones but it's doable in theory -- difficult but not impossible.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I appreciate you looking into this. Imanami from the looks of it may not do caller id, but the other two do. I'm trying to set up an LDAP server and will see how they work out -- thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Does the ncidd server allow for any kind of authentication/authorization? I installed the server and connected my phone and it just works... which is great in some ways, but I don't want to have my call list available for read/write on the open internet.
Hi Emiliano,
No, but establishing a secure connection to the server is something we know we need to add eventually. It will be quite involved to add it.
Wouldn't it suffice to add a command to allow login and then stick stunnel in front of ncid?
Alternately, perhaps a backend that has this built in (kinto, gun.js, feathers.js,....) with frontends for clients which speak the existing non-secured protocol?
Has any progress been made in this issue?
There has not been any work done to change the open messaging.
I think most of us run it in private households, behind a NAT firewall, and don't have it exposed to the entire internet.
Changing this would require significant change to the server and all of the clients.
Hi Emiliano,
For a less abrupt answer, I thank you for pointing me to stunnel, I didn't know it existed.
I am also looking into DTLS.
Some work was done earlier to try Firebase Messaging Service for the android devices, but it seemed to require a shared central server that would require registration of users.
Were you really wanting to see caller information outside of a home network or intranet?
Ed
That's what I was looking for, yes. I want caller ID for our corporate
directory for Android phones. I can download a copy of the directory, now I
just need a way to get caller ID from it. Given that it's our full company
phone list, I'd rather not put it out there for anyone to trawl through.
On Thu, Apr 19, 2018, 03:57 Ed Attfield ed_attfield@users.sourceforge.net
wrote:
If I'm reading this right, there are two ways you can add your phone list to ncid, one is to add the phone numbers to the /etc/ncid/ncidd.whitelist with "#=" comments to associate the names with the numbers. e.g. 6137631234 #= Fred Smith will pass Fred's name to the Android when a call comes from that number. This can also be done with an alias.
Since I'm open to suggestions, how were you picturing authenticating a host of android devices with the server? Options seem to include simple password, device id + password, and device id alone. (And how many is "a host" ?)
In my specific case, "a host" would be around 4k if I get it beyond POC
(not a given, our IT dept is very conservative, for good reasons). But
right now, I'm just trying to get it to work for myself.
A simple, global password would be OK for a poc. Device ID would be better
if I can build a way to register people without too much technical
complexity; this would be done by our service desk. If the device ID can't
be readily spoofed, a device ID would suffice. A bearer token would also
do.
For per-user passwords, PAM would be the ideal, or LDAP, but a simple
passwd style file would do.
Hi Emiliano, sorry no one replied to your two June 13, 2017 postings. I checked and I never got a notification from SourceForge that you'd done so. We weren't ignoring you, promise!
I'm thinking that NCID does something different from what you're looking for.
You seem to be looking for a company-wide way of getting callerid onto 4000 android clients devices -- presumably from 4000 individual desktop phones, and also out to a similar number of desktop clients. I expect that this would be each person wanting caller ID for their own phone.
NCID is built to get caller ID from a small number of devices, like a single modem and a few SIP lines, and to share it with all of the clients. Each call and message is broadcast to every client device.
You probably don't want all of the incoming calls sent to all of the client devices.
Ah, right. I don't need anything on the desktop, indeed just many mobile
phones that can get calls from colleagues, and we want caller ID from the
corporate directory without putting the corporate directory in every
individual person's contact list.
If I understand this right, you were hoping for a tool that would add name information to a call when one of your many android devices calls another.
Right now, when Alfred calls Beth, Beth only sees a number. You were hoping to dip into a central list of names to add the name "Alfred" to the call to Beth.
NCID does not do this. It is meant to watch a small number of phone lines and tell every subscribed client about an incoming call.
For my example, it would tell all 4000 of your devices that Alfred was calling Beth.
That was what I was looking for. Thanks for the clarification.
On Thu, Apr 26, 2018, 02:30 Ed Attfield ed_attfield@users.sourceforge.net
wrote:
Hi Emiliano,
Maybe one of these Android apps would work for you:
All three of the above seem to have search capability in case Alfred doesn't know Beth's number.
To do the equivalent in NCID, the NCID Android app would need modifying as well as the NCID server to essentially use NCID's alias file, plus add a secure connection or login/password that you were originally asking about. I'm not sure how well this would scale for 4K Android phones but it's doable in theory -- difficult but not impossible.
Hi Todd,
I appreciate you looking into this. Imanami from the looks of it may not do caller id, but the other two do. I'm trying to set up an LDAP server and will see how they work out -- thanks!