VonageSniff VOIP Caller ID Script

[nstocke]

I was unable to unpack the newly zipped file. It is also working. I am able to detect incoming calls and send to multiple listeners and at different ports.

I'm stilling having problems with the filter options. If I don't change anything I don't get the error messages but I don't get it to detect incoming or outgoing calls. If I change the filter option I am still getting the error message:

Use of uninitialized value in pattern match (m//) at vonageSniff.pl line 183.

But it does detect calls. I have not been able to get it detect and send messages when it is running as a service.

[KJake]

Originally Posted by KJake

Also, nstocke, if the default filter setting doesn't work for you, try 'udp and tcp 5060' - i think that's the standard SIP port and it may work for Vonage too. If it does, I'll change that to be the default in the next release.

Did you try this? Setting a filter will make the program use a little less resources since it will only be scanning specific traffic.

[nstocke]

yes, My line in the config file is:

filter='udp and tcp 5060'

I really don't know why I get the error line. It's like what ever is put in the filter it doesn't like. But I think it causes it to look at everything and that is why I get it working.

I agree that if I could get the filter to work it would use less resources and I think it would then work as a service.

Could I have something messed up in my PERL installation?

[KJake]

Originally Posted by nstocke

Could I have something messed up in my PERL installation?

Nope, this shouldn't use your perl installation...it was all my fault

• I was wrong and we need to use double quotes (") instead of single quotes (') around the filter string, so I've corrected the Help text to show that.
• I told you to change your filter string to something that wouldn't work, it should have been "udp and port 5060", but it wouldn't have worked then either since I had you use single quotes.
• That error message you were getting was a little misleading, but I've captured it now.
• If you set a blank filter string, Pcap isn't going to be happy about that, so I've told the script to skip compiling a filter if one isn't set.

I think that takes care of your issues and cleaned up the script quite a bit, thank you!

I also set the default port to 5060 now (so you shouldn't even need to define filter - leave it out of your config or command line completely). Let me know if that works for you. Vonage uses 5061 instead for SIP, 10000 is usually the actual voice data.

http://kjake.net/vonageSniff.zip

[nstocke]

It's working good for me. Multiple IPs and ports, No filter string. No error messages. It's doing what I need it to do.

I did a quick test of running it as a service but didn't have success. It's doing what I need it to do so I'll try to test it as a service a little later.

Thanks again for the great work. This has been great getting the CallerID to popup before the phone rings.

[KJake]

Originally Posted by nstocke

It's working good for me. Multiple IPs and ports, No filter string. No error messages. It's doing what I need it to do.

I did a quick test of running it as a service but didn't have success. It's doing what I need it to do so I'll try to test it as a service a little later.

Thanks again for the great work. This has been great getting the CallerID to popup before the phone rings.

Awesome, good to hear. When you say, "No filter string", does that mean that you didn't define one, so that it is using the default? At the very beginning it will print out its settings so that you can see what it is doing, what does that say?

[nstocke]

Sorry, I should have stated that better. I am just using the default string. It shows udp and port 5060. As the filter when I run the script. In my config file it just has:
filter=

[KJake]

Originally Posted by nstocke

Sorry, I should have stated that better. I am just using the default string. It shows udp and port 5060. As the filter when I run the script.

Cool, I will work more on the service part then and then start promoting this as a general SIP companion to the InfoPopup/YAC. I might need to stop calling it vonageSniff though

[KJake]

Originally Posted by nstocke

I did a quick test of running it as a service but didn't have success. It's doing what I need it to do so I'll try to test it as a service a little later.

Give this new version a try for running as a service. It should start/stop as you would expect now. You will though see two processes running. This was the only way that I could make it work; the first process starts the second process and then watches for a STOP command from Windows and kills off the second process and exits. This unfortunately means a little more memory wasted.

I did not have a chance to test whether this was sending YAC notifications or not, so save your current version in case I broke it completely.

http://kjake.net/vonageSniff.zip

[toricred]

I'm trying to set this up using the bridge network connection on an XP box. After creating the bridge my vonage adapter won't connect and establish the dial tone. Any help?

More information: The VTA is not getting a DHCP address.

I looked into using their softphone software, but it looks like it can only be used for a separate line. Is there something I'm missing here?

How about a suggestion for place to buy a hub and not a switch.

[KJake]

Originally Posted by toricred

I'm trying to set this up using the bridge network connection on an XP box. After creating the bridge my vonage adapter won't connect and establish the dial tone. Any help?

Might try disabling any firewall on the XP machine.

Originally Posted by toricred

How about a suggestion for place to buy a hub and not a switch.

There's a bunch on eBay right now. http://is.gd/hdU7

[Diginerd]

Hubs are a bad idea if you plan on streaming any video out from your Sage server, 2nd NIC bridged is the way to go here if possible.

Hubs require half duplex configuration on the NIC which severely limits your throughput, as well as causing lots of collisions which are a "Really Bad Thing" if having any respectable level of throughput is a parameter.

[toricred]

I have no intention of having the hub on the server. It will be on a separate system (my teenager's) that is running the sniffing script and sending the information to the server.

I'd actually rather use the bridging, but I can't figure out how to get it to work. My second choice would be their softphone, but it doesn't look like I can use that for my primary line.

[toricred]

I got it working by adding their software that is for the primary line (Vonage Pro).

The only problem, at least on outgoing calls, is that it sends pop-ups with the second one being blank.

One other question. When I install it as a service, how do I tell it to use the config file?

[toricred]

On incoming calls there is only one pop-up so that's good. I'm still having problems getting it to use the config file when I try to run it as a service. This is great.

[swift_gti]

Just stumbled upon this thread, and it looks like it may be what I've been looking for!

Could someone clarify how this actually works.. from what I've read I'm guessing it's setup as follows ;

• Vonage VTA Adaptor (Mines a little D-Link box) into NIC 1
• Router into NIC 2
  
• Bridge the connection within XP
  
• Install WinPCap, YAC? and run VonageSniff (with appropriate switches)
  
• Then when I receive a call VonageSniff will push alerts to YAC listeners?

If thats correct then this is perfect for what I have been looking for!

Definatley going to play with this when I get home.

[swift_gti]

Update;

Ok tried it out this evening, bridged the NIC's on my PC and put the Vonage VTA into one and the other into my switch, followed the instructions for setting up vonagesniff and its working like a charm!!

Kevin I could probably kiss you right now!!
I've been playing with old modems for the last couple of weeks trying to get caller id with patchy success. Within 20 minutes I was up and running using your solution, really great work!!

Currently I've got it going via console window as the service doesn't seem to honour the filter settings in my config.. I installed the service using;
vonagesniff.exe --install -C="C:\Vonagesniff\Vonagesniff.config"
Which seems to give the service all of my config settings (according to event viewer) except the filter which seems to be ignored.. my config is set to udp and port 10000 but the service uses udp and port 5060

Also noticed the console spits out (detects the call fine though!);
Use of uninitialized value in regexp compilation at vonageSniff.pl line 227.
Detected incoming call: ..calling no..

All in all superb work, look forward to seeing this develop further (maybe we can have a txt file which can associate names to the numbers for YAC?)

Cheers!

[toricred]

I tried the bridge thing on my server (didn't want to mess with it until I was sure it would work) last night and it works perfectly. I'm still having the problem where it won't recognize the filter when run as a service. From the post above it looks like I'm not the only one with the issue.

[toricred]

I resolved the issue with running as a service. I used instsrv and srvany that come with the Windows 2003 Resource Kit to set it up instead of the program itself as a method to install the service.

[swift_gti]

Thanks for the update, I was just thinking of using srvany last night but haven't got around to trying it yet.

All we need now is the ability to resolve numbers to names and this app would be a 100% YAC replacement