STV Import: CallerID/Message popup plugin

[KJake]

Yup, I can look at pulling in the pre-reqs for the perl into ActiveState perl for windows and compile it to an .exe and see if it will work with WinPcap (or something). Only an idea, but worth it. Just know that since you are sniffing traffic that you will need your network setup to be able to capture the packets. One way of doing it is using a hub between your vonage adapter and server that sniffs, or the other is to have two network cards in the server, bridged and one interface connected to the network and the other connected to the vonage adapter (I did the latter since I have switches instead of hubs).

[KJake]

Here is my first try. I've commented out all the Unix stuff for now, focusing on getting the sniffing working instead. I don't have a way to test this since the only windows system close to my vonage adapter only has 1 network card in it, so I did the best I could blindly

If it does detect the SIP Invite, it will grab the data and print out the YAC formatted string and it will attempt to send the message to a YAC listener. I have not tested whether the TCP connect capability is still working (again, just want to get the sniffer working).

So, download and install the latest WinPcap, then run the attached. Run it first as vonageSniff.exe -h to see the options that can be set, then run it once without the -h to have it tell you the list of network adapters in your system that it can use.

Then you would run a command similar to:
vonageSniff -d=\Device\NPF_{GUID} -ip=ip.of.your.yac.listener

To test, you can leave out the -i (ignore) option that I added and it should detect an outgoing call (calling voicemail even) and display your own phone number as the caller. When I'm running this fulltime I use the ignore and place my own phone number there as 2125553322 and then it will ignore all outgoing calls.

In anycase, if someone can get this to print out something other than an error, I will be pleased.

Again, do note that you need a fairly specific network setup for this to work in general. Your sniffing system needs to be able to see all the traffic from the vonage adapter and switches will block that.

If this does work, I do plan on trying to add the Unix stuff back in as there are similar perl modules in Windows.

[file removed - we've branched this topic off into a thread of its own]

[shadeblue.com]

Just posting a progress report for those interested on the companion plug-in for Nielm's InfoPopup to get caller ID working on the HD extenders ...

So far the alpha testing is going well and seems to be working for all the testers. A few relatively minor issues to resolve and this project should be ready for a BETA release which I will post publicly.

PS: Custom caller images are working.

I'll post a note here when this plugin gets released, probably in one or two weeks.


Thank You,
shadeBlue

[computer33]

Originally Posted by shadeblue.com

I'll post a note here when this plugin gets released, probably in one or two weeks.

shadeBlue

Looking forward to this being released. I missed this plug in when I got my HD extender.

Thank you!

[shadeblue.com]

Originally Posted by computer33

Looking forward to this being released. I missed this plug in when I got my HD extender.

Thank you!

Hi computer33,

I just released rev ALPHA-05 to the BETA test group. I'm keeping my fingers crossed that this will be the final ALPHA release and we can move this to a public BETA release very soon.

If you are interested in testing the current ALPHA release, just PM me and I'll get the info to you.

Thanks, shadeBlue

[wvpolekat]

I just whipped up a quick shell script to form an e-mail interface of sorts to this plugin.

The geek level on this is fairly high, but it may be of use to some of you. The same concept can be used for a million things. Netcat is also available for Windows, so similar functionality could be built into a batch file.

In theory, this could be done over the Internet almost as a service, but the security aspect of it could be a nightmare. If this traffic was allowed from anywhere on the internet, I suspect that you would get tons of garbage popping up. And, I am not sure that this was written to be robust enough to be exposed to that. I know I saw somewhere in the documentation that you needed to be careful allowing connections from other hosts, which is very true.

It requires the tool "netcat", which it uses to send the message to the sage machine.

#To make it cron friendly we make sure it doesn't send mail
MAILTO=
#Get a list of e-mail messages for the user running the script
for INMSG in `ls ~/Maildir/new/`
do
#Parse out just the subject line and remove the header field name
MSGSUBJ=`grep "Subject: " ~/Maildir/new/$INMSG|cut -f 2 -d ":"`
#Send the subject to sage via netcat
echo "$MSGSUBJ"|nc sage.hostname.here 10629
#Remove the message
rm -f ~/Maildir/new/$INMSG
done

The uses for this are almost endless, but some easy notifications are:

1) When a backup or other task completes
2) Sports/News alerts
3) A million other things.

The beauty is that it isn't just limited to email. Anything you can parse, you can send via netcat.

My alarm system sends e-mails when events happen. Using this, I can have it display on the screen when these events happen.

I have no idea of someone already posted something like this in the thread, but this IMO is just about one of the best uses of this plugin.

[wvpolekat]

Ok, so I have been tweaking on this. I made some changes to the script to remove some of the delay so it is running as a daemon instead of every min.

My outlook also watches for certain words and shoots an alert to the TV if they occur.

Now, what I would DEARLY love from this plugin is the ability to have 2 instances. One that pauses TV and one that just displays the message. I will have to look at the XML and see if I can do this. I imagine it wouldn't be too hard. Just make them unique names and ports.

Also, for those of you scripting to this... I learned that when netcat makes a connection to it, it will stay open until the on screen message goes away. This is only an issue if trying to send multiple messages at one time. I ran into a problem where my script was stepping on itself when it looped because of this. The simple solution was to throw a & at the end of the nc command to put it in the background. Once you do this, it will accept the other connection and cycle through the messages on the screen.

[QueOnda]

@Kjake,

Have you used Vonage click2call app? It let's you log into your account, then you select a number to call, then your phone would ring, so you pick it up then starts ringing the number you want to call. This will be cool if someone could write something to take advantage of this. You could set up a phone book in sagetv and select a number to call. I wish I could program!

[shadeblue.com]

I have just released the shadeBlue-SageInfoPopup plug-in to the public. You can download it and obtain more information here. This is an alternate implementation for obtaining YAC caller ID messages and displaying the information in SageTV. This alternate version was specifically targeted at overcoming the issues and fully supporting the HD extenders.

I don't want to hijack this thread, so please direct any comments or questions related to the shadeBlue-SageInfoPopup plug-in to this new support thread.

Thank You,
shadeBlue

[KJake]

Originally Posted by KJake

If this does work, I do plan on trying to add the Unix stuff back in as there are similar perl modules in Windows.

Just checking in to see if anyone tried this and had success. I will gladly add more debugging/logging capabilities to it if anyone is going to use it. If not, I'll leave the attachment there as-is.

[Steve52]

Originally Posted by KJake

Just checking in to see if anyone tried this and had success. I will gladly add more debugging/logging capabilities to it if anyone is going to use it. If not, I'll leave the attachment there as-is.

I definitely plan to try it. I just opened a new HD200 extender, and want to be able to get caller ID on it. It may be several days before I get the extender installed and can try it however.

[nstocke]

Originally Posted by KJake

Here is my first try. I've commented out all the Unix stuff for now, focusing on getting the sniffing working instead. I don't have a way to test this since the only windows system close to my vonage adapter only has 1 network card in it, so I did the best I could blindly

If it does detect the SIP Invite, it will grab the data and print out the YAC formatted string and it will attempt to send the message to a YAC listener. I have not tested whether the TCP connect capability is still working (again, just want to get the sniffer working).

So, download and install the latest WinPcap, then run the attached. Run it first as vonageSniff.exe -h to see the options that can be set, then run it once without the -h to have it tell you the list of network adapters in your system that it can use.

Then you would run a command similar to:
vonageSniff -d=\Device\NPF_{GUID} -ip=ip.of.your.yac.listener

To test, you can leave out the -i (ignore) option that I added and it should detect an outgoing call (calling voicemail even) and display your own phone number as the caller. When I'm running this fulltime I use the ignore and place my own phone number there as 2125553322 and then it will ignore all outgoing calls.

In anycase, if someone can get this to print out something other than an error, I will be pleased.

Again, do note that you need a fairly specific network setup for this to work in general. Your sniffing system needs to be able to see all the traffic from the vonage adapter and switches will block that.

If this does work, I do plan on trying to add the Unix stuff back in as there are similar perl modules in Windows.

Would this work with other VOIP providers besides Vonage? I have VIATalk and I have been looking for a Caller ID program that would work on the network packets.

[nstocke]

Originally Posted by KJake

Here is my first try. I've commented out all the Unix stuff for now, focusing on getting the sniffing working instead. I don't have a way to test this since the only windows system close to my vonage adapter only has 1 network card in it, so I did the best I could blindly

If it does detect the SIP Invite, it will grab the data and print out the YAC formatted string and it will attempt to send the message to a YAC listener. I have not tested whether the TCP connect capability is still working (again, just want to get the sniffer working).

So, download and install the latest WinPcap, then run the attached. Run it first as vonageSniff.exe -h to see the options that can be set, then run it once without the -h to have it tell you the list of network adapters in your system that it can use.

Then you would run a command similar to:
vonageSniff -d=\Device\NPF_{GUID} -ip=ip.of.your.yac.listener

To test, you can leave out the -i (ignore) option that I added and it should detect an outgoing call (calling voicemail even) and display your own phone number as the caller. When I'm running this fulltime I use the ignore and place my own phone number there as 2125553322 and then it will ignore all outgoing calls.

In anycase, if someone can get this to print out something other than an error, I will be pleased.

Again, do note that you need a fairly specific network setup for this to work in general. Your sniffing system needs to be able to see all the traffic from the vonage adapter and switches will block that.

If this does work, I do plan on trying to add the Unix stuff back in as there are similar perl modules in Windows.

I think it has become obvious to myself that I don't know what I'm doing. I decided to give it a try. Downloaded and extracted VonageSniff. When I tried to run it I got and error that it couldn't find "Perl58.dll" I installed active perl and tried again. Still same error. The perl folder was in the path but no per58.dll. I located some odd perl58.dll files in some old temp directories on my system. Put the perl58.dll file in the current perl directory and I get the following error dialog box.

VonageSniff.exe - Entry Point Not Found
The procedure entry point Perl_hv_common_key_len could not be located in the dynamic link library per58.dll

Any ideas on what I need to do?

[simonk1969]

Originally Posted by shadeblue.com

I have just released the shadeBlue-SageInfoPopup plug-in to the public. You can download it and obtain more information here. This is an alternate implementation for obtaining YAC caller ID messages and displaying the information in SageTV. This alternate version was specifically targeted at overcoming the issues and fully supporting the HD extenders.

I don't want to hijack this thread, so please direct any comments or questions related to the shadeBlue-SageInfoPopup plug-in to this new support thread.

Thank You,
shadeBlue

I've installed shadeBlue-SageInfoPopup to replace neilms info popup because I could not get it to work succesfully or reliably on my MPV and this has worked straight away after setup and consistently since.

Thanks
Simon

[nstocke]

Originally Posted by nstocke

I think it has become obvious to myself that I don't know what I'm doing. I decided to give it a try. Downloaded and extracted VonageSniff. When I tried to run it I got and error that it couldn't find "Perl58.dll" I installed active perl and tried again. Still same error. The perl folder was in the path but no per58.dll. I located some odd perl58.dll files in some old temp directories on my system. Put the perl58.dll file in the current perl directory and I get the following error dialog box.

VonageSniff.exe - Entry Point Not Found
The procedure entry point Perl_hv_common_key_len could not be located in the dynamic link library per58.dll

Any ideas on what I need to do?

I determined that the perl58.dll it was looking for was based on the version of PERL. I had installed Perl 5.10 after installing an older version of PERL version 5.8.8 I got the script to run. I have gotten it to detect incoming calls and to send the CALLER ID to a YAC listener. There are still a few problems. I get errors when I try to use the Daemon option -D and the only way I can get it to detect incoming calls is to use the -f (filter option) but when I do the screen fills with "Use of uninitialized value in pattern match (m//) at vonageSniff.pl line 275." messages. It is functioning but the screen just streams that message.

I would love to hear from anyone else using the VonageSniff script.

[nstocke]

I started a new thread to discuss the VonageSniff Script that KJake contributed.

New Thread is Here

[KJake]

Originally Posted by nstocke

I started a new thread to discuss the VonageSniff Script that KJake contributed.

New Thread is Here

Sorry about your questions going unanswered, I must have accidentally unsubscribed from this thread somehow.

[KJake]

Originally Posted by nstocke

Would this work with other VOIP providers besides Vonage? I have VIATalk and I have been looking for a Caller ID program that would work on the network packets.

My guess is that this program will work with anything that uses proper SIP protocol formatting.

[KJake]

Originally Posted by QueOnda

@Kjake,

Have you used Vonage click2call app? It let's you log into your account, then you select a number to call, then your phone would ring, so you pick it up then starts ringing the number you want to call. This will be cool if someone could write something to take advantage of this. You could set up a phone book in sagetv and select a number to call. I wish I could program!

I hadn't seen that, sounds pretty cool - and Vonage actually has a neat third party integration site up so we wouldn't have to create a wrapper or anything for this program.

They have a nice Java example on the site that could be extended with an STVi nicely...however, I really don't want to get into STVi development. My personality and the Studio do not mix and I quickly get frustrated with it.

https://secure.click2callu.com

[QueOnda]

Originally Posted by KJake

I hadn't seen that, sounds pretty cool - and Vonage actually has a neat third party integration site up so we wouldn't have to create a wrapper or anything for this program.

They have a nice Java example on the site that could be extended with an STVi nicely...however, I really don't want to get into STVi development. My personality and the Studio do not mix and I quickly get frustrated with it.

https://secure.click2callu.com

OH, COOL. I didn't look long enough at that page.