Hi folks, About three weeks ago we began receiving random reports from different customers that inbound calls were displaying the Caller ID 845-789-0000. This is not the real caller ID of the originating caller, and does not appear to be their LRN, either. It is also not a scam call ? these are real, regular calls from normal humans / conversational traffic. In addition, the calls appear to originate from many different origins ? i.e. it?s not always the same caller, or destination, or city/state. The calls are real, legitimate calls, and the conversations proceed normally. But the CLID is wrong. The one thing we have narrowed down is that these calls all seem to terminate with one of our carriers ? Peerless. None of the reports we?ve received are for calls on Inteliquent, bandwidth.com, O1, etc. Peerless does not seem to be aware of any routing issue and is asking for more examples to investigate, but they?re hard to get, since it involves not only the receiving party noticing the incorrect Caller ID then prompting the caller for their real phone number and recording the date/time. (Of course, this is impossible to get clients to actually do). Oddly, a search for this number online reveals only this somewhat entertaining email thread on a Subaru mailing list https://www.subaruoutback.org/forums/138-gen-5-2015-2019/497927-curious-cell... . It describes the same symptom, and seems to equate it to an iPhone update with bluetooth, which I have a hard time believing makes any sense. If I had to really guess, it could be the rollout of VoLTE and some misconfiguration on a wireless carrier network that is only invoked when using Bluetooth to make calls ? but boy, that seems like one helluva stretch. Anyone seen this before and/or have any other ideas how to track this down? We?re running out of ideas and are tempted to just port offending DIDs away to another carrier to see if it ?fixes? the problem, but Peerless has generally been good to us so I?d really rather leave the numbers there and just sort out the issue. But, we?re short on time ? the customers are becoming irritated and don?t like providing this information to us each time the Caller ID is wrong. Any advice is appreciated. Thanks in advance! Darren Schreiber CEO / Co-Founder 415 886 7901 darren at 2600hz.com<mailto:darren at 2600hz.com> [cid:image003.png at 01D39B61.C995D850]<http://t.sidekickopen61.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg1p...> [cid:image004.png at 01D39B61.C995D850]<http://t.sidekickopen61.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg1p...> [cid:image005.gif at 01D39B61.C995D850] <https://www.facebook.com/2600hzOfficial/> [cid:image006.png at 01D39B61.C995D850] <http://t.sidekickopen61.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg1p...> [cid:image007.gif at 01D39B61.C995D850] <http://t.sidekickopen61.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg1p...> [cid:image008.png at 01D39B61.C995D850] <http://t.sidekickopen61.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg1p...> NEWS + ANNOUNCEMENTS Check out our recent cover story: Revolutionizing Business Communications<https://beyondexclamation.com/revolutionizing-business-communications/?utm_c...> Learn how KAZOO<https://2600hz.com/architecture> is disrupting the UCaaS & CPaaS landscape.
Am 13.10.2018 um 05:29 schrieb Darren Schreiber:
??????????????? About three weeks ago we began receiving random reports from different customers that inbound calls were displaying the Caller ID 845-789-0000. This is not the real caller ID of the originating caller, and does not appear to be their LRN, either. It is also not a scam call ? these are real, regular calls from normal humans / conversational traffic. In addition, the calls appear to originate from many different origins ? i.e. it?s not always the same caller, or destination, or city/state. The calls are real, legitimate calls, and the conversations proceed normally. But the CLID is wrong.
It would be interesting to know which service the callers are making their calls through. Is it from their US cell phone directly via their cell provider? Is it from a landline in the US? Because, if it is some kind of VoIP service or if these calls originate from people living abroad or if they are currently roaming, it could be that the CLI is simply forged by the originating carrier or somewhere along the path and was set to some spontaneously made up value (789-0000 = 7 8 9 0 <- may be legit but since the digits are consecutive... it is something that I would type if I had to make up a number quickly). If it really from their cell phone or landline then I would also go with the misconfiguration theory.
Thanks Markus & John for the replies. The mystery remains but that thread you sent John from 3 years ago appears to be similar re: symptoms. We'll keep hunting this down with our carrier. ?On 10/13/18, 6:17 AM, "VoiceOps on behalf of Markus" <voiceops-bounces at voiceops.org on behalf of universe at truemetal.org> wrote: Am 13.10.2018 um 05:29 schrieb Darren Schreiber: > About three weeks ago we began receiving random reports > from different customers that inbound calls were displaying the Caller > ID 845-789-0000. This is not the real caller ID of the originating > caller, and does not appear to be their LRN, either. It is also not a > scam call ? these are real, regular calls from normal humans / > conversational traffic. In addition, the calls appear to originate from > many different origins ? i.e. it?s not always the same caller, or > destination, or city/state. The calls are real, legitimate calls, and > the conversations proceed normally. But the CLID is wrong. It would be interesting to know which service the callers are making their calls through. Is it from their US cell phone directly via their cell provider? Is it from a landline in the US? Because, if it is some kind of VoIP service or if these calls originate from people living abroad or if they are currently roaming, it could be that the CLI is simply forged by the originating carrier or somewhere along the path and was set to some spontaneously made up value (789-0000 = 7 8 9 0 <- may be legit but since the digits are consecutive... it is something that I would type if I had to make up a number quickly). If it really from their cell phone or landline then I would also go with the misconfiguration theory. _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
This sounds like ordinary refiling on termination into the US from the second-rate/cheap international route industry, which is vast. -- Sent from mobile. Apologies for brevity and errors.
Any way to confirm that for sure? ?On 10/13/18, 9:58 AM, "VoiceOps on behalf of Alex Balashov" <voiceops-bounces at voiceops.org on behalf of abalashov at evaristesys.com> wrote: This sounds like ordinary refiling on termination into the US from the second-rate/cheap international route industry, which is vast. -- Sent from mobile. Apologies for brevity and errors. _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Am 13.10.2018 um 19:35 schrieb Darren Schreiber:
Any way to confirm that for sure?
Kind of. Find out which service the callers are using and sign up for the same service, then play around with that service (call yourself through your various suppliers - Inteliquent, Peerless etc.)
Peerless should be able to pull the SS7 traces and figure out where the call comes in on their network. It'll show if the call came in via an International gateway if they take the time to do it. I think they only keep 3 days of detailed records though. ~Jared On Sat, Oct 13, 2018 at 2:35 PM Markus <universe at truemetal.org> wrote:
Am 13.10.2018 um 19:35 schrieb Darren Schreiber:
Any way to confirm that for sure?
Kind of. Find out which service the callers are using and sign up for the same service, then play around with that service (call yourself through your various suppliers - Inteliquent, Peerless etc.) _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
it shouldn't be that hard to get information to send over to peerless pull traces from your system ? filter for all calls that had that Caller ID. BTW do you see the real caller ID information in any headers ? or they all have the "845-789-0000" number ? On Sun, Oct 14, 2018 at 5:53 AM Jared Geiger <jared at compuwizz.net> wrote:
Peerless should be able to pull the SS7 traces and figure out where the call comes in on their network. It'll show if the call came in via an International gateway if they take the time to do it. I think they only keep 3 days of detailed records though.
~Jared
On Sat, Oct 13, 2018 at 2:35 PM Markus <universe at truemetal.org> wrote:
Am 13.10.2018 um 19:35 schrieb Darren Schreiber:
Any way to confirm that for sure?
Kind of. Find out which service the callers are using and sign up for the same service, then play around with that service (call yourself through your various suppliers - Inteliquent, Peerless etc.) _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
-- Izzy Goldstein Chief Technology Officer Main: (212) 477-1000 x 2085 <(212)%20477-1000> Direct: (929) 477-2085 Website: www.telego.com <http://www.telego.net/> <http://www.telego.com/> Confidentiality Notice: This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error please notify us immediately by email reply and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of TeleGo (T). Employees of TeleGo are expressly required not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is contrary to TeleGo policy and outside the scope of the employment of the individual concerned. TeleGo will not accept any liability in respect of such communication, and the employee responsible will be personally liable for any damages or other liability arising. TeleGo Hosted PBX <https://youtu.be/DaT8YAZ4V0w>
Hi all, In case anyone runs into the same issue or cares, I will follow-up when this is resolved. Thanks for those of you who replied with ideas on and off list. Also, to set the record straight, I?m an idiot ? The issue is on calls originating via Inteliquent, not Peerless. I had the info wrong from my tech. And I?m not trying to throw either under the bus ? both vendors have been awesome to work with. - Darren From: Darren Schreiber <darren at 2600hz.com> Date: Friday, October 12, 2018 at 8:29 PM To: "voiceops at voiceops.org" <voiceops at voiceops.org> Subject: Curious Caller ID issues Hi folks, About three weeks ago we began receiving random reports from different customers that inbound calls were displaying the Caller ID 845-789-0000. This is not the real caller ID of the originating caller, and does not appear to be their LRN, either. It is also not a scam call ? these are real, regular calls from normal humans / conversational traffic. In addition, the calls appear to originate from many different origins ? i.e. it?s not always the same caller, or destination, or city/state. The calls are real, legitimate calls, and the conversations proceed normally. But the CLID is wrong. The one thing we have narrowed down is that these calls all seem to terminate with one of our carriers ? Peerless. None of the reports we?ve received are for calls on Inteliquent, bandwidth.com, O1, etc. Peerless does not seem to be aware of any routing issue and is asking for more examples to investigate, but they?re hard to get, since it involves not only the receiving party noticing the incorrect Caller ID then prompting the caller for their real phone number and recording the date/time. (Of course, this is impossible to get clients to actually do). Oddly, a search for this number online reveals only this somewhat entertaining email thread on a Subaru mailing list https://www.subaruoutback.org/forums/138-gen-5-2015-2019/497927-curious-cell... . It describes the same symptom, and seems to equate it to an iPhone update with bluetooth, which I have a hard time believing makes any sense. If I had to really guess, it could be the rollout of VoLTE and some misconfiguration on a wireless carrier network that is only invoked when using Bluetooth to make calls ? but boy, that seems like one helluva stretch. Anyone seen this before and/or have any other ideas how to track this down? We?re running out of ideas and are tempted to just port offending DIDs away to another carrier to see if it ?fixes? the problem, but Peerless has generally been good to us so I?d really rather leave the numbers there and just sort out the issue. But, we?re short on time ? the customers are becoming irritated and don?t like providing this information to us each time the Caller ID is wrong. Any advice is appreciated. Thanks in advance! Darren Schreiber CEO / Co-Founder 415 886 7901 darren at 2600hz.com<mailto:darren at 2600hz.com> [cid:image003.png at 01D39B61.C995D850]<http://t.sidekickopen61.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg1p...> [cid:image004.png at 01D39B61.C995D850]<http://t.sidekickopen61.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg1p...> [cid:image005.gif at 01D39B61.C995D850] <https://www.facebook.com/2600hzOfficial/> [cid:image006.png at 01D39B61.C995D850] <http://t.sidekickopen61.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg1p...> [cid:image007.gif at 01D39B61.C995D850] <http://t.sidekickopen61.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg1p...> [cid:image008.png at 01D39B61.C995D850] <http://t.sidekickopen61.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg1p...> NEWS + ANNOUNCEMENTS Check out our recent cover story: Revolutionizing Business Communications<https://beyondexclamation.com/revolutionizing-business-communications/?utm_c...> Learn how KAZOO<https://2600hz.com/architecture> is disrupting the UCaaS & CPaaS landscape.
participants (6)
-
abalashov＠evaristesys.com -
darren＠2600hz.com -
ghenry＠suretec.co.uk -
igoldstein＠telego.net -
jared＠compuwizz.net -
universe＠truemetal.org