|
Hardware Support Discussions related to using various hardware setups with SageTV products. Anything relating to capture cards, remotes, infrared receivers/transmitters, system compatibility or other hardware related problems or suggestions should be posted here. |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
|||
|
|||
Caller ID modem for voip
I currently have a TRENDnet TFM-PCIV92A pci modem in my pc that worked pretty well with Yac that sent caller id messages to all my pc's on my lan. My problem is that I recently changed from conventional phone service to digital phone service (VOIP) through my cable company & now the caller id doesn't work. The caller id on my phone works, it just doesn't work using my phone modem. Is there a modem I can buy that will provide caller id with digital phone service? I did a search & came up with nothing.
|
#2
|
|||
|
|||
I am using Vonage and a Best Data 56HP92-SL modem for caller ID withYac. If your phone works with it, I would think your modem would also.
|
#3
|
||||
|
||||
the modem should work fine as caller ID is a stanard for all phones.
Do you have the modem plugged into the same phone line as your phone? |
#4
|
|||
|
|||
Yes. I will experiment with some different modems & see if I can find one that works.
|
#5
|
|||
|
|||
I thought I was using a Trendnet modem, but it turned out to be an AOpen FM56PX modem. For whatever reason caller id worked with this modem until I switched from conventional phone service to VOIP. I had a generic modem laying around that I tried, but caller id didn't work with it either. One of my old pc's had a US Robotics USR5699B modem in it, so I took that out & tried it & sure enough caller id works.
My AOpen modem made a clicking noise whenever Yac started up or whenever a call came in & my US Robotics modem doesn't do this, so maybe that has something to do with caller id through VOIP not working on the AOpen modem. Thanks to everybody for reassuring me that caller id works with VOIP. I was about ready to give up. |
#6
|
|||
|
|||
It still seems wrong on a very basic level to me that we cannot get caller ID on the PC over voip without converting the IP-based digital signal into analog, then into a modem...
Does anyone know a way to get caller ID to display directly from the IP signal without going through an analog modem??
__________________
m2 |
#7
|
|||
|
|||
Caller ID with digital phone line
Quote:
|
#8
|
||||
|
||||
Quote:
saw this link: http://www.asteriskvoipnews.com/voip..._released.html
__________________
Server: Ubuntu 16.04 running Sage for Linux v9 |
#9
|
|||
|
|||
I have been reading up on this as well.
I was planning on using sip2ncid: Code:
http://ncid.sourceforge.net/ncid/ncid.html I have ordered a NETGEAR DS104 for this purpose (waiting for it to arrive). If someone had some *real* skills, they could likely port ncid to run as a service on wrt54g router running openwrt/dd-wrt. Then the hub wouldn't be necessary. But I'll leave that challenge to someone else. Last edited by SilentBob; 10-22-2009 at 12:37 AM. |
#10
|
||||
|
||||
So apparently you can run a softphone on a computer and also run the sniffer on that computer. this avoids the whole hub issue because the VOIP traffic *is* going to the computer (softphone) already.
What I'd want is to have an applet that is a softphone in name only, and all it does is collect VOIP packets with the sole intend to use the caller ID data. Not sure if I can have a softphone (as I describe above or otherwise) and an actual SIP adapter running at the same time. I wouldn't want to use the softphone for calls. (VOIP is one of those things that I use, but since it (almost always) just works, I haven't learned too much about it. Maybe I should start reading up on it...)
__________________
Server: Ubuntu 16.04 running Sage for Linux v9 |
#11
|
|||
|
|||
You used to be able to use VonageTalk, so you didn't need a modem, but they dropped support for that in Sept. They have a new softphone, http://www.vonage.com/features_avail..._nav_softphone not sure if it works the same, I haven't tried it yet.
|
#12
|
|||
|
|||
Quote:
The way around that would be to set up an asterisk box. Asterisk would then register with your voip provider and you could then register multiple SIP phones (hard, soft, whatever) to your asterisk box. When the call came in you could ring all of your phones at the same time. Of course if you are going to go to the trouble of setting up and running asterisk you could just run ncid on your asterisk box and you'd be done. If I only wanted to run 1 phone with 1 VOIP provider, asterisk would be overkill for that, especially if all you are accomplishing is to avoid having to install a $20 hub. If you could take advantage of multiple trunks, custom call routing, full PBX capability, etc, then it might make sense at that point. Although, this gets me thinking.... If you didn't want to fool with installing a hub and you had a wrt54g compatible router, you could run asterisk on the wrt and then use one of these scripts: Code:
http://www.voip-info.org/wiki/view/Asterisk+NetCID http://www.thrallingpenguin.com/resources/app_networkclid.htm You'd of course still have to get asterisk configured, but you could avoid having to add any hardware and depending on how your network is physically laid out it might be easier than having to relocate things or pull additional cable. I may decide to give this a try, if I do I'll let you know how it works out, but I've got several bigger problems that I need to resolve first. |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
ISDN CAPI for Caller Display | pbelcl | SageTV Customizations | 3 | 01-11-2008 01:21 AM |
SageMC 16x9 v6 Caller ID Plugin Help | sportera | SageMC Custom Interface | 5 | 07-16-2007 10:13 AM |
YAC - Caller ID - Call Log within SageTV | Armondole | SageTV Customizations | 0 | 02-22-2007 07:51 AM |
Using Serial Modem to Update Guide | hmca | SageTV EPG Service | 1 | 11-06-2006 02:47 AM |
SageMC and Caller ID plugin help... | mrrrl | SageMC Custom Interface | 3 | 01-12-2006 08:29 AM |