[VoiceOps] Curious Caller ID issues

Darren Schreiber darren at 2600hz.com
Fri Oct 12 23:29:25 EDT 2018

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-phone-issue.html . 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/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg1pNv9jW4Y9g1C4WzrgKW8p-VB856dMnQf5gC6rg02?t=http%3A%2F%2Fwww.2600hz.com%2F&si=6465517321846784&pi=aef7deed-ee30-44a3-bd13-576d851e6e04>

[cid:image004.png at 01D39B61.C995D850]<http://t.sidekickopen61.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg1pNv9jW4Y9g1C4WzrgKW8p-VB856dMnQf5gC6rg02?t=https%3A%2F%2Ftwitter.com%2F2600hertz&si=6465517321846784&pi=aef7deed-ee30-44a3-bd13-576d851e6e04>   [cid:image005.gif at 01D39B61.C995D850] <https://www.facebook.com/2600hzOfficial/>    [cid:image006.png at 01D39B61.C995D850] <http://t.sidekickopen61.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg1pNv9jW4Y9g1C4WzrgKW8p-VB856dMnQf5gC6rg02?t=https%3A%2F%2Fwww.youtube.com%2Fuser%2F2600hzOfficial&si=6465517321846784&pi=aef7deed-ee30-44a3-bd13-576d851e6e04>    [cid:image007.gif at 01D39B61.C995D850] <http://t.sidekickopen61.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg1pNv9jW4Y9g1C4WzrgKW8p-VB856dMnQf5gC6rg02?t=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2F2600hz&si=6465517321846784&pi=aef7deed-ee30-44a3-bd13-576d851e6e04>    [cid:image008.png at 01D39B61.C995D850] <http://t.sidekickopen61.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg1pNv9jW4Y9g1C4WzrgKW8p-VB856dMnQf5gC6rg02?t=https%3A%2F%2Fplus.google.com%2F%2B2600hzvoip&si=6465517321846784&pi=aef7deed-ee30-44a3-bd13-576d851e6e04>
Check out our recent cover story: Revolutionizing  Business Communications<https://beyondexclamation.com/revolutionizing-business-communications/?utm_content=75018798&utm_content=65254598&utm_medium=social&utm_medium=email&utm_source=twitter&utm_source=hs_email&utm_campaign=Newsletters&_hsenc=p2ANqtz-81o1gccaD1UBrB0xdzbW>
Learn how KAZOO<https://2600hz.com/architecture> is disrupting the UCaaS & CPaaS landscape.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20181013/718febcb/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5707 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20181013/718febcb/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 513 bytes
Desc: image002.png
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20181013/718febcb/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.gif
Type: image/gif
Size: 1321 bytes
Desc: image003.gif
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20181013/718febcb/attachment-0002.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 2215 bytes
Desc: image004.png
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20181013/718febcb/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.gif
Type: image/gif
Size: 1299 bytes
Desc: image005.gif
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20181013/718febcb/attachment-0003.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 2654 bytes
Desc: image006.png
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20181013/718febcb/attachment-0007.png>

More information about the VoiceOps mailing list