SOLVED: callerid from obi110 to my USR modem
QBZappy:
sundansx,
Cool. Thanks for the reply. You should mention it in this thread:
Alternate uses for the Line Port for people who don't need it for POTS line
http://www.obitalk.com/forum/index.php?topic=85.0
MichiganTelephone:
Quote from: QBZappy on March 07, 2011, 07:08:53 pm
Hi,
Look here: General Support > Feature Requests > Support for notification popups on computers
You will find an open source project which captures CID from info contained in SIP. Uses packet sniffing approach. There are a couple of links if you are interested. Clever use of packet analysis. To date it seems the only method anyone has suggested that might work which is ready made.
Not to be a nitpicker, but some of us don't care for the packet sniffing approach. At the end of the thread you mentioned, both AndroidsOfTara and I separately posted Perl scripts that would extract the Caller ID and allow one to create a popup notification.
I'm not sure why the OP would need to or want to run a separate modem to perform this function, unless perhaps it's just a case of being extremely familiar with that method and not really wanting to dip your toe into the uncharted waters of a different method. Been there, done that.
QBZappy:
MichiganTelephone,
???
What is this all about? Why are quoting a post from another thread into this one? No one in this thread is mentioning anything about packet sniffing. That was another discussion unrelated to this thread. As far as I'm concerned I wont be talking about that anymore for fear of anyone accusing me of hijacking that thread. Congrats on the Perl script, FWIW it still is too tecky for some. I think that YAK+CID modem is another clever way of getting the same results if all you want is CID over the lan. Keep an open mind about other ways of achieving results. It may or may not be the most elegant/efficient way of accomplishing network CID, but there is no way of denying that it is a proven solution that works with little effort.
I think you are misunderstanding this thread. There is no packet sniffing involved with this solution.
No need to bring this up anymore. I agree with you that you are coming off as a nitpicker.
MichiganTelephone:
Quote from: QBZappy on May 10, 2011, 10:59:36 am
MichiganTelephone,
???
What is this all about? Why are quoting a post from another thread into this one? .....
Excuse me? Who is quoting a post from another thread? Read the second message in this thread - that is the one I quoted. Is that or is that not your message?
I'll admit that I sometimes screw up in online forums and accidentally misquote someone, but this was not one of those times.
Could it be that you originally intended to post your message in a different thread? Because it does seem a bit out of place here.
QBZappy:
MichiganTelephone,
Quote from: MichiganTelephone on May 10, 2011, 10:08:05 am
I'm not sure why the OP would need to or want to run a separate modem to perform this function, unless perhaps it's just a case of being extremely familiar with that method and not really wanting to dip your toe into the uncharted waters of a different method. Been there, done that.
Hi, I was addressing this part of your reply. His solution does not require packet sniffing. I got the impression that you were thinking "packet sniffing" when you saw the words modem+CID in the same sentence. We should stop this now as this is serioulsy off topic.
Peace.
Navigation
[0] Message Index
[#] Next page
[*] Previous page