Series 3 caller ID: NCID

[rcflyer]

If the test works fine, then all of the files are in the right spot. When you say that you can't get it to work, do you mean that caller-id doesn't come up when you get a call? How are you calling the program?

I think the modem was hung. I started getting socket errors. I'll do a cold reboot and try again. Yes call-id didn't come up when making a call. Tests were fine.

[djl]

Be sure to keep in mind the previous couple of messages. As written, you have to issue ncid-fly with an absolute path:
ncid --no-gui --program /path_to/ncid-fly &

I think the modem was hung. I started getting socket errors. I'll do a cold reboot and try again. Yes call-id didn't come up when making a call. Tests were fine.

[jlc]

This NCID (Network Caller ID) release adds some fixes and some scripts

The ncidd server fix removes a blank space in front of a phone number caused by some modems not in complete compliance to the specification. The fix was applied to all Caller ID text lines received from modems.

The sip2ncid gateway has a fix to label outgoing and incoming calls correctly when a PBX does not support the SIP REGISTER packet, which is normally used to determine incoming and outgoing calls.

Specific to the TiVo distribution:
Removed the "rmpid" option in the startncid shell script.
A new stopncid shell script was added to terminate all NCID programs that are running.
Fix for the ncid-tivo module that eliminates @stdout from being displayed after the screen is cleared on TiVo HD's.
Updated comments on the ncid-fly display module (which is HME safe) in the startncid script.
The initmodem shell script was modified to use pgrep instead of ps.

[rcflyer]

It still will not display a call when a call comes in. Test runs fine and displays proper output. Both log files show call came in, so issue has to be with the client. I'm starting with ncid --no-gui --program /var/hack/share/ncid/ncid-fly & in the rc.sysinit.author file. I've tried killing the services and starting by hand, still no display on screen. All files are in proper places. I know it's something simple. What am I missing? Thanks in advance.

[djl]

Are the server and client running on the same server? If not, you need to add the address of the ncid server to the command line:

ncid 192.168.1.whatever --no-gui --message --program /path_to/ncid-fly &

What does ncid-fly.log say? Also, try running it in an open command window and making a call. Paste the output here, it really should be something simple...

It still will not display a call when a call comes in. Test runs fine and displays proper output. Both log files show call came in, so issue has to be with the client. I'm starting with ncid --no-gui --program /var/hack/share/ncid/ncid-fly & in the rc.sysinit.author file. I've tried killing the services and starting by hand, still no display on screen. All files are in proper places. I know it's something simple. What am I missing? Thanks in advance.

[Soapm]

Was tired and losing my mind... All fine now.

[rcflyer]

Test works fine. Now ncid will not start. I get the following message below. What next?

bash-2.02# ncid --no-gui --program /var/hack/share/ncid/ncid-fly
127.0.0.1:3333 - error reading "sock17": connection refused

[Soapm]

Test works fine. Now ncid will not start. I get the following message below. What next?

bash-2.02# ncid --no-gui --program /var/hack/share/ncid/ncid-fly
127.0.0.1:3333 - error reading "sock17": connection refused

I don't use fly but I'm getting the sock17 error also until I reboot the Tivo. There has to be a way to refresh the modem without a reboot.

[jlc]

See NCID News and see NCID files and release notes

Specific to the TiVo distribution:

The startncid script has been improved and simplified somewhat. This is the recommend method of starting NCID because it also sets up the complete environment. It still defaults to starting tivoncid and ncidd. It gives you complete control of starting or not starting the server, client, gateway, and output modules supported for the TiVo . This includes the new client module called ncid-notify that will send a NCID notification to any iOS or Andriod device, or both. It requires "curl" which is part of the TiVo distribution.

The stopncid script was updated so it stops all running NCID programs and scripts added by this release.

The ncid-fly module is supported but you should install the attached ncid-fly-mips-tivo.tgz from /var and replace rsyslog with rsyslog-5-8-4. The tar archive places all the supporting files, libraries, and icons in the proper directories for NCID. In addition the ncid-fly module was updated for this release and includes a configuration module. The ncid-fly module was written by djl and is described in these posts:
http://www.dealdatabase.com/forum/sh...346#post308346
http://www.dealdatabase.com/forum/sh...y2osd&p=315611

[jlc]

See NCID NEWS and see NCID Files & Release Notes.