817-385-7121
TX, US
 | anon 2014-03-19 20:15:27 Unknown |
call but no msg from this #;
| ANonieMouse 2013-10-29 03:54:17 Unknown |
I don't think that either of the two sources you site have substantially different information than is available here at 800notes.com . There may be some differences, but I am rather skeptical that the combination of what they might disclose and what you may be able to find out by looking at IP addresses on your Internet connection will be prove useful at all. And that's especially the case if they are calling your Google Voice Number, which uses a proprietary protocol and depends upon your forwarding calls to another phone number.
There is a relatively accessible introduction to SIP calling and signalling written in four parts on a blog in Switzerland that may be of some use to you, especially in regards to something called a "proxy server," which basically makes it impossible to trace the real source of your calls without a court subpoena to a VoIP provider. The URL of the first part of the introduction is:
http://toncar.cz/Tutorials/VoIP/VoIP_Protocols_Introducing_SIP.html
There is a relatively accessible introduction to SIP calling and signalling written in four parts on a blog in Switzerland that may be of some use to you, especially in regards to something called a "proxy server," which basically makes it impossible to trace the real source of your calls without a court subpoena to a VoIP provider. The URL of the first part of the introduction is:
http://toncar.cz/Tutorials/VoIP/VoIP_Protocols_Introducing_SIP.html
| ANON 2013-10-28 23:13:31 Unknown |
The number that is getting these "JUNK" calls is my Google Voice number.
Two of of my many tools to trace possible VOIP based numbers & get further information about number are from
http://www.verifyphone.com/
- and -
http://www.phoneaddressdirectory.com/
Some times it will list one or more IP address for a number, other times it does not. Just like now, NEITHER one shows any IP address tied to this number.
I do not know how they trace the suspected VOIP connection.
Two of of my many tools to trace possible VOIP based numbers & get further information about number are from
http://www.verifyphone.com/
- and -
http://www.phoneaddressdirectory.com/
Some times it will list one or more IP address for a number, other times it does not. Just like now, NEITHER one shows any IP address tied to this number.
I do not know how they trace the suspected VOIP connection.
| ANonieMouse 2013-10-28 05:05:33 Unknown |
I don't know what you did to "trace" the numbers you said were calling you or what kind of phone service you are using (e.g., VoIP/SIP, such as CallCentric; VoIP/proprietary, such as Google voice and many cable Internet phones; Skype proprietary, etc.), so it is difficult to make sense of your trace.
The Googlebot entry is just Google trying to index your web page, or trying to see that you even have one. See:
https://support.google.com/webmasters/answer/182072?hl=en
It isn't the source of any of your calls.
Similarly, the MSNbot entry also isn't the source of your calls. See:
http://en.wikipedia.org/wiki/Msnbot
The Charter Communications entry is somewhat interesting because it shows that your caller MAY (repeat: MAY) be using the Charter Communications service to connect to the Internet via a DHCP connection, which suggests that he (like almost all non-business customers) is connected to the Internet and assigned a dynamic IP address (i.e., one that changes at regular or irregular intervals). That means that, by the time you realize what his IP address is, it may have changed, and that you would need to convince a court to issue a subpoena to get Charter's records of who was assigned that IP address at the actual time of the incident.
I don't know what proprietary protocol Charter may use for setting up and tearing down a VoIP call, but it is likely that, at your end of the call, you are using a SIP phone, a SIP PBX, or an FXS adapter. If so, it is unlikely that the IP address from Charter is of much significance, anyway. You would be alerted to an incoming call when a SIP "setup" protocol is completed. It has been my observation that the setup messages use the IP address of the caller's phone company server and that the server's IP address is shared by all of that company's customers who are registered on that switch. The actual voice or multimedia server that exchanges the voice (or other multimedia data) stream is sent in the setup message. The multimedia server is either a server operated by the caller's phone company or a third party server operating under contract with the phone company to reduce call latency and improve phone quality.
The calling party's real IP address, static or dynamic, is never revealed to you in such cases. At best, you will only get the phone company's setup server's IP address and that of the server relaying the voice stream. The only other information you receive about the caller is the number assigned to him by the phone company, if the caller does not choose to block it from you. The caller name can be sent with the setup protocol, but usually isn't. Your own phone company can look this information in a commercial database for you for a fee (usually less than 1 cent per call), and, in some cases, charge you extra for doing so or just absorb it into the cost of your own service. In any case, there are a lot of different databases your own service might be using, and many of them are poorly maintained and/or do not share information with one another, even if the caller's phone company actually makes a good faith effort to provide a caller name for the number in any database at all. And many phone companies do not make this effort.
So tell us more about your setup and how you concluded these calls were coming from the IP addresses you said they were calling from. I'm anxious to learn any new tracing methods I can.
The Googlebot entry is just Google trying to index your web page, or trying to see that you even have one. See:
https://support.google.com/webmasters/answer/182072?hl=en
It isn't the source of any of your calls.
Similarly, the MSNbot entry also isn't the source of your calls. See:
http://en.wikipedia.org/wiki/Msnbot
The Charter Communications entry is somewhat interesting because it shows that your caller MAY (repeat: MAY) be using the Charter Communications service to connect to the Internet via a DHCP connection, which suggests that he (like almost all non-business customers) is connected to the Internet and assigned a dynamic IP address (i.e., one that changes at regular or irregular intervals). That means that, by the time you realize what his IP address is, it may have changed, and that you would need to convince a court to issue a subpoena to get Charter's records of who was assigned that IP address at the actual time of the incident.
I don't know what proprietary protocol Charter may use for setting up and tearing down a VoIP call, but it is likely that, at your end of the call, you are using a SIP phone, a SIP PBX, or an FXS adapter. If so, it is unlikely that the IP address from Charter is of much significance, anyway. You would be alerted to an incoming call when a SIP "setup" protocol is completed. It has been my observation that the setup messages use the IP address of the caller's phone company server and that the server's IP address is shared by all of that company's customers who are registered on that switch. The actual voice or multimedia server that exchanges the voice (or other multimedia data) stream is sent in the setup message. The multimedia server is either a server operated by the caller's phone company or a third party server operating under contract with the phone company to reduce call latency and improve phone quality.
The calling party's real IP address, static or dynamic, is never revealed to you in such cases. At best, you will only get the phone company's setup server's IP address and that of the server relaying the voice stream. The only other information you receive about the caller is the number assigned to him by the phone company, if the caller does not choose to block it from you. The caller name can be sent with the setup protocol, but usually isn't. Your own phone company can look this information in a commercial database for you for a fee (usually less than 1 cent per call), and, in some cases, charge you extra for doing so or just absorb it into the cost of your own service. In any case, there are a lot of different databases your own service might be using, and many of them are poorly maintained and/or do not share information with one another, even if the caller's phone company actually makes a good faith effort to provide a caller name for the number in any database at all. And many phone companies do not make this effort.
So tell us more about your setup and how you concluded these calls were coming from the IP addresses you said they were calling from. I'm anxious to learn any new tracing methods I can.
| ANON_1 2013-10-28 04:06:56 Telemarketer |
Still Receiving calls almost daily from this number.... Found some additional informataion out tonight:
IP trace results for 817-385-7121
This phone number was traced from the following IP addresses: 75.142.160.244, 66.249.66.228, 157.56.92.175
======
IP Information for 75.142.160.244
IP Location: United States / Fort Worth, TX / Charter Communications
ASN: United States AS20115 CHARTER-NET-HKY-NC - Charter Communications (registered Mar 26, 2001)
Resolve Host: 75-142-160-244.dhcp.ftwo.tx.charter.com
===
IP Information for 66.249.66.228
IP Location United States / Mountain View, CA / Google Inc.
ASN: United States AS15169 GOOGLE - Google Inc. (registered Mar 30, 2000)
Resolve Host: crawl-66-249-66-228.googlebot.com
===
IP Information for 157.56.92.175
IP Location: United States / Chicago, IL / Microsoft Corporation
ASN: United States AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation (registered Mar 31, 1997)
Resolve Host: msnbot-157-56-92-175.search.msn.com
IP trace results for 817-385-7121
This phone number was traced from the following IP addresses: 75.142.160.244, 66.249.66.228, 157.56.92.175
======
IP Information for 75.142.160.244
IP Location: United States / Fort Worth, TX / Charter Communications
ASN: United States AS20115 CHARTER-NET-HKY-NC - Charter Communications (registered Mar 26, 2001)
Resolve Host: 75-142-160-244.dhcp.ftwo.tx.charter.com
===
IP Information for 66.249.66.228
IP Location United States / Mountain View, CA / Google Inc.
ASN: United States AS15169 GOOGLE - Google Inc. (registered Mar 30, 2000)
Resolve Host: crawl-66-249-66-228.googlebot.com
===
IP Information for 157.56.92.175
IP Location: United States / Chicago, IL / Microsoft Corporation
ASN: United States AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation (registered Mar 31, 1997)
Resolve Host: msnbot-157-56-92-175.search.msn.com
| ANON_1 2013-10-09 15:43:54 Unknown |
Looking over my BLOCKED CALL LIST I see they have called TWO (2) more times from this number to my Google Voice# yesterday - @12:52 &14:25.
Still receiving calls from 817-389-9060, 817-789-6002, 817-984-5626, 817-984-5656, 817-984-5687, 817-803-4620 at my Google Voice# for 4+ weeks now. ALL NUMBERS HAVE BEEN ADDED TO BLOCK LIST.
----
Primary TELCO of Prefix 817-385-xxxx: Southwestern Bell
Switch Name: DLLSTXMCDS0
Phone Type: Landline
OCN: 6114
817-385-7xxx TELCO Information: LEVEL 3 COMMUNICATIONS, LLC - TX
Still receiving calls from 817-389-9060, 817-789-6002, 817-984-5626, 817-984-5656, 817-984-5687, 817-803-4620 at my Google Voice# for 4+ weeks now. ALL NUMBERS HAVE BEEN ADDED TO BLOCK LIST.
----
Primary TELCO of Prefix 817-385-xxxx: Southwestern Bell
Switch Name: DLLSTXMCDS0
Phone Type: Landline
OCN: 6114
817-385-7xxx TELCO Information: LEVEL 3 COMMUNICATIONS, LLC - TX
| ANON 2013-09-27 00:03:25 Unknown |
Looking over my BLOCKED CALL LIST I see they have called THREE (3) more times from this number to my Google Voice#.
Also been receiving calls from 817-389-9060, 817-789-6002, 817-984-5626, 817-984-5656, 817-984-5687, 817-803-4620 at my Google Voice# for almost 3 weeks now. ALL NUMBERS HAVE BEEN ADDED TO BLOCK LIST.
Also been receiving calls from 817-389-9060, 817-789-6002, 817-984-5626, 817-984-5656, 817-984-5687, 817-803-4620 at my Google Voice# for almost 3 weeks now. ALL NUMBERS HAVE BEEN ADDED TO BLOCK LIST.
| ANON_1 2013-09-14 15:54:10 Unknown |
Received call from this number at 10:12 AM today. Don't know who it is and they did not leave a message.. so I have added it to my BLOCK LIST.
Service Provider Southwestern Bell
Switch Abbreviation: DLLSTXMCDS0
Switch name: Mid Cities
Phone Type: Landline
Location: Grand Prairie, TX
817-984-5xxx is a LEVEL 3 COMMUNICATIONS, LLC EXCHANGE.
----
Phone companies who have numbers in this exchange: METROTEL; SOUTHWESTERN BELL; SPRINT SPECTRUM L.P; TELETOUCH COMMUNICATIONS, INC.
*-*---
Details from
http://www.localcallingguide.com/lca_prefix.p ... ys=0&nextdays=0
PA-NXX-X Rate Centre Region Switch OCN LATA Eff date Disc date Map
817-984 Fort Worth TX IRNGTXLBDS0 7249 BROOKS FIBER PROPERTIES OF TEXAS - TX [link] 552 map
817-984-0 Fort Worth TX 7249 BROOKS FIBER PROPERTIES OF TEXAS - TX [link] 552 map
817-984-1 Fort Worth TX 353D CHARTER FIBERLINK TX-CCO, LLC - TX [link] 552 2012-12-17
817-984-2 Fort Worth TX 7249 BROOKS FIBER PROPERTIES OF TEXAS - TX [link] 552
817-984-3 Fort Worth TX 177F PEERLESS NETWORK OF TEXAS, LLC - TX [link] 552 2012-10-01
817-984-4 Fort Worth TX 6114 LEVEL 3 COMMUNICATIONS, LLC - TX [link] 552 2007-07-26
817-984-5 Fort Worth TX 6114 LEVEL 3 COMMUNICATIONS, LLC - TX [link] 552 2007-09-24
817-984-6 Fort Worth TX 2152 CBEYOND COMMUNICATIONS OF TEXAS, LP-TX [link] 552 2009-04-17
817-984-7 Fort Worth TX 2152 CBEYOND COMMUNICATIONS OF TEXAS, LP-TX [link] 552 2009-04-17
817-984-8 Fort Worth TX 2152 CBEYOND COMMUNICATIONS OF TEXAS, LP-TX [link] 552 2009-04-17
817-984-9 Fort Worth TX 6114 LEVEL 3 COMMUNICATIONS, LLC - TX [link] 552 2007-11-07
-----
Service Provider Southwestern Bell
Switch Abbreviation: DLLSTXMCDS0
Switch name: Mid Cities
Phone Type: Landline
Location: Grand Prairie, TX
817-984-5xxx is a LEVEL 3 COMMUNICATIONS, LLC EXCHANGE.
----
Phone companies who have numbers in this exchange: METROTEL; SOUTHWESTERN BELL; SPRINT SPECTRUM L.P; TELETOUCH COMMUNICATIONS, INC.
*-*---
Details from
http://www.localcallingguide.com/lca_prefix.p ... ys=0&nextdays=0
PA-NXX-X Rate Centre Region Switch OCN LATA Eff date Disc date Map
817-984 Fort Worth TX IRNGTXLBDS0 7249 BROOKS FIBER PROPERTIES OF TEXAS - TX [link] 552 map
817-984-0 Fort Worth TX 7249 BROOKS FIBER PROPERTIES OF TEXAS - TX [link] 552 map
817-984-1 Fort Worth TX 353D CHARTER FIBERLINK TX-CCO, LLC - TX [link] 552 2012-12-17
817-984-2 Fort Worth TX 7249 BROOKS FIBER PROPERTIES OF TEXAS - TX [link] 552
817-984-3 Fort Worth TX 177F PEERLESS NETWORK OF TEXAS, LLC - TX [link] 552 2012-10-01
817-984-4 Fort Worth TX 6114 LEVEL 3 COMMUNICATIONS, LLC - TX [link] 552 2007-07-26
817-984-5 Fort Worth TX 6114 LEVEL 3 COMMUNICATIONS, LLC - TX [link] 552 2007-09-24
817-984-6 Fort Worth TX 2152 CBEYOND COMMUNICATIONS OF TEXAS, LP-TX [link] 552 2009-04-17
817-984-7 Fort Worth TX 2152 CBEYOND COMMUNICATIONS OF TEXAS, LP-TX [link] 552 2009-04-17
817-984-8 Fort Worth TX 2152 CBEYOND COMMUNICATIONS OF TEXAS, LP-TX [link] 552 2009-04-17
817-984-9 Fort Worth TX 6114 LEVEL 3 COMMUNICATIONS, LLC - TX [link] 552 2007-11-07
-----
© WHOSCALL.IN 2011-2024 - Privacy