It’s pretty likely those are coming from our numbers. We’ve seen a dramatic increase in fraudsters using our phone numbers (both vacant and assigned) to make fraud calls. Then, the called parties often lookup the number and end up calling us to complain even though the fraudster doesn’t own the number and isn’t our customer.
So, while there’s nothing we can do to prevent them from using our assigned numbers, we’ve started populating CNAM for all of our unassigned numbers nationwide with “Probably Fraud” since no legitimate outbound calls are made from those numbers. Then when the number IS assigned, we overwrite the CNAM entry with the correct one. This has dramatically helped with the problem; far fewer people answer the fraud calls when the callerID says that. Mike Mike Ray, MBA, CNE, CTE Astro Companies, LLC 11523 Palm Brush Trail #401 Lakewood Ranch, FL 34202 DIRECT: call or text 941 600-0207 <http://www.astrocompanies.com> http://www.astrocompanies.com From: VoiceOps [mailto:voiceops-boun...@voiceops.org] On Behalf Of Glen Gerhard Sent: Friday, April 13, 2018 4:43 PM To: voiceops@voiceops.org Subject: Re: [VoiceOps] Wireless Carrier Lookups: CNAM DIPS SLIGHTLY OFF TOPIC: Lately I've been getting calls to my Tmobile cell phone with CNAMs such as Scam Likely and Nuisance Call. Even without the CNAM I know they are call centers so don't pick up, but I'm wondering who assigns that CNAM? I'd expect Tmobile to dip the CNAM but doubt the official database would flag the number this way. If it's coming from the call center app it's pretty funny. I don't know anywhere else along the call path it would be changed. ~Glen On 3/26/2018 8:05 AM, Eric Wieling wrote: I use data24-7.com Request: https://api.data24-7.com/v/2.0?user=**** <https://api.data24-7.com/v/2.0?user=****&pass=****&out=json&api=C&p1=18504901495&addfields=sms_address,mms_address,ocn> &pass=****&out=json&api=C&p1=18504901495&addfields=sms_address,mms_address,ocn Response: { "response": { "results": [ { "status": "OK", "number": "18504901495", "wless": "y", "carrier_name": "Verizon Wireless", "carrier_id": "5", "country": "United States", "sms_address": <mailto:8504901...@vtext.com> "8504901...@vtext.com", "mms_address": <mailto:8504901...@vzwpix.com> "8504901...@vzwpix.com", "ocn": "6006" } ] } } On 03/26/2018 09:29 AM, Shripal Daphtary wrote: everyoneapi.com might be useful. Thanks, Shripal On Mar 26, 2018, at 9:14 AM, Ivan Kovacevic <mailto:ivan.kovace...@startelecom.ca> <ivan.kovace...@startelecom.ca> wrote: Hi Everyone, We are looking for an API provider for real-time carrier lookups. Specifically because we need to determine the Canadian wireless carrier (Rogers, Bell, Telus, etc.) to know where to direct a text message. I see Twillio has a real-time API, but it's quite pricy. When I looked at this about a decade ago, Telcordia used to have monopoly on this type of data, hoping things have changed. Thanks in advance. Ivan Kovacevic VP Client Services STAR TELECOM www.startelecom.ca <http://www.startelecom.ca> -- NOTE: This email message and any attachments are for the sole use of the intended recipient(s) and may contain confidential and/or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by replying to this email, and destroy all copies of the original message. _______________________________________________ VoiceOps mailing list VoiceOps@voiceops.org <mailto:VoiceOps@voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops _______________________________________________ VoiceOps mailing list VoiceOps@voiceops.org <mailto:VoiceOps@voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops