Support for notification popups on computers
jimates:
It would also be great if we could link the PC softphone as an extension of the Obi. Instead of forwarding calls to it, it would be great if it would just ring along with the Obi.
That might also get the caller id to the pc.
QBZappy:
If anyone is interested here is an open source network caller ID (NCID) which can work with the Obi device. It is based on packet sniffing. Works with Linux, Mac, and Windows (using andlinux). Apparently it is safe to use a packet sniffing strategy on your own network.
http://ncid.sourceforge.net/
http://ncid.sourceforge.net/ncid/ncid.html#Screenshots
NCID is Caller ID (CID) distributed over a network to a variety of devices and computers.
NCID supports messages. Clients can send a one line message to all connected clients.
NCID supports outgoing calls if the information is provided by a SIP gateway.
NCID consists of the ncidd server, the ncid universal client, and various client output modules. It also includes NCID, SIP, and YAC gateways.
Another interesting product based on packet sniffing if you want to record incoming and outgoing calss. This one is commercial. Also captures CID. Not a popup app however.
http://www.miarec.com/products/miarec-solo/how-it-works
sundansx:
Anyone using ncid in a home network with the obi110? I presume you would setup routing rules on your router to forward or Tee packets coming to the obi110 from the internet. I am not sure how to do that on my Tomato firmware based router. I didnt find any specific instructions on the internet, just conceptual one. Thanks to all in this thread for the pointers thus far.
QBZappy:
sundansx,
Hi,
I have not had a need to set it up, however in this "how to" there is no mention of setting up routing rules. Author says "Run an ethernet cable from it (Hub) to the system running ncidsip and you're good to go!"
http://www.davidlaporte.org/tutorials/sipcallerid.html
I have used andlinux product. It is amazing to see linux running off a windows computer. It is just as intuitive as Windows, as it is GUI based.
I would be interested in knowing your results. Let us know.
PS
I read over the "How do I configure NCID to use a SIP gateway". I believe the ports you need to setup in the software are the:
SIP----> UDP port 5060 (Default setting) and perhaps the
RTP----> UDP port numbers mentioned in your config under Service Providers->ITSP Profile A/B->RTP->LocalPortMin & LocalPortMax
The rest of the discussion regarding using the "T" seems to be for testing for SIP packets using their sip2ncid application. This shouldn't be necessary since we know what ports the Obi is using by looking at the web config page.
MichiganTelephone:
Quote from: QBZappy on March 08, 2011, 08:45:44 pm
sundansx,
Hi,
I have not had a need to set it up, however in this "how to" there is no mention of setting up routing rules. Author says "Run an ethernet cable from it (Hub) to the system running ncidsip and you're good to go!"
http://www.davidlaporte.org/tutorials/sipcallerid.html
QBZappy, with all due respect, this is NOT the solution most of us are looking for. And the reason is in the paragraph above the one you quoted, which begins:
Quote
Option 2 is even easier, although it will involve an additional piece of equipment. You will need to purchase an ethernet hub and insert it between your cable/DSL modem and your router. If you have an all-in-one model, or are worried about the security implications of connecting a PC outside of your router/firewall, you can also just plug the hub into your router and your VoIP device and sip2ncid box into it. …
(emphasis added)
For me at least, it's not worth it to have yet another device that costs money, takes up space, consumes power, and requires a fair degree of computer knowledge to set up. Do you think the average user is going to do this? Not in a million years! This is a serious nerd type project. As far as it goes, many home users won't have a Linux box, won't want to try and install andlinux, and won't want to get involved with packet sniffing (even if they know what that is). The whole point of these devices is to make VoIP relatively easy to set up and use, which for example is why Obihai gives us tools like the OBiTALK portal and the wizards - if you want to set up the device with one of their "known" providers, you don't even have to touch the configuration of the device. But what you are suggesting goes way beyond that in terms of difficulty.
I personally wish that Obihai would consider including network Growl support. In addition to the original Growl notification system for Mac OS X, there's also Growl for Windows which is easy to install and becoming more popular (and in some ways more capable than the original Mac version). Ans as I said in my original post, even Linux users aren't left out of the party, since they can use Mumbles to receive and display network Growl notifications.
To give you an idea of how simple it can be to send Growl notifications, this is how it's done on an Asterisk system in Perl. The bulk of this code is spent parsing the values passed by Asterisk (caller ID number, caller ID name, called extension number, and target IP address or MAC address of the computer to receive the notification) and then formatting the output. Only the last few lines are actually used to send the notification:
Code:
#!/usr/bin/perl
use strict;
use warnings;
use Net::Growl;
use Asterisk::AGI;
my $agi = new Asterisk::AGI;
my %input = $agi->ReadParse();
my $num = $input{'callerid'};
my $name = $input{'calleridname'};
my $ext = $input{'extension'};
my $ip = $ARGV[0];
if ( $ip =~ /^([0-9a-f]{2}(:|$)){6}$/i ) {
$ip = $agi->database_get('growlsend',uc($ip));
}
unless ( $ip =~ /^(\d+)\.(\d+)\.(\d+)\.(\d+)$/ ) {
exit;
}
if ( $ARGV[2] ne "" ) {
$ext = $ARGV[2];
}
my @months = (
"January", "February", "March", "April", "May", "June",
"July", "August", "September", "October", "November", "December"
);
my @weekdays = (
"Sunday", "Monday", "Tuesday", "Wednesday",
"Thursday", "Friday", "Saturday"
);
my (
$sec, $min, $hour, $mday, $mon,
$year, $wday, $yday, $isdst
) = localtime(time);
my $ampm = "AM";
if ( $hour > 12 ) {
$ampm = "PM";
$hour = ( $hour - 12 );
}
elsif ( $hour eq 12 ) { $ampm = "PM"; }
elsif ( $hour eq 0 ) { $hour = "12"; }
if ( $min < 10 ) { $min = "0" . $min; }
$year += 1900;
my $fulldate =
"$hour:$min $ampm on $weekdays[$wday], $months[$mon] $mday, $year";
# Next two lines normalize NANP numbers, probably not wanted outside of U.S.A./Canada/other NANP places
$num =~ s/^([2-9])(\d{2})([2-9])(\d{2})(\d{4})$/$1$2-$3$4-$5/;
$num =~ s/^(1)([2-9])(\d{2})([2-9])(\d{2})(\d{4})$/$1-$2$3-$4$5-$6/;
register(host => "$ip",
application=>"Incoming Call",
password=>"$ARGV[1]", );
notify(host => "$ip",
application=>"Incoming Call",
title=>"$name",
description=>"$num\nfor $ext\n$fulldate",
priority=>1,
sticky=>'True',
password=>"$ARGV[1]",
);
In addition to the above you do have to use a Perl module for network Growl support (Net::Growl) but I believe there are similar modules for several other languages (you have to be careful, though, to get one that has network support - many Growl modules are intended only for sending notifications to the local machine). I do not know what language the Obihai developers code in, but unless it's a very low level language there's a possibility that there's an existing network Growl module.
According to the Net::Growl source code, it was
Code:
# Derived from Rui Carmo's (http://the.taoofmac.com)
# netgrowl.php (http://the.taoofmac.com/space/Projects/netgrowl.php)
So apparently there's also a PHP module, and the author's comment on that code is very interesting:
Quote
This is the PHP version of netgrowl, which took me all of half an hour to do. With it, you can have your PHP-based web servers notify you instantly of any strange occurrences.
(emphasis added)
My point here is that although I'm not a programmer and therefore not in a position to really judge the difficulty of adding network Growl notifications, I honestly don't think that it would either be very difficult, nor require a huge amount of code. Whether the Obihai developers would be willing to include it is a whole other matter, but given a preference I'd much rather see something like that than a solution that requires external hardware!
Navigation
[0] Message Index
[#] Next page
[*] Previous page