Also, fax will be dead by 2005 at the latest.
On Nov 21, 2025 at 3:10:30 PM, Alex Balashov <[email protected]> wrote: > Unfounded speculation, but I think this is a short-term hack and will > ultimately go the way of the dodo. > > Yes, services like this will go the way of the dodo. You can't impersonate > the original caller per se. There will be some other way to pass the > identity of the caller, or other enriched call data that would be relevant > to a database lookup. It won't be by presenting CID of a number you don't > own. > > -- Alex > > On Nov 21, 2025, at 5:02 PM, Carlos Alvarez via VoiceOps < > [email protected]> wrote: > > > I’ve just deployed something similar to this via Telin. I’m sure others > can do it too. They have an automated system that verifies your > ownership/permission to use a phone number, and from then on, you can use > it and get either B or A attestation. The most common interpretation of > the current regs is that this is the only way you can send off-net CLID in > the future. If you want to have a live conversation about this I’m open to > a call. It’s something I’ve been doing since the 90s and constantly > fighting the changing landscape on CLID. > > > If you’d like to talk to someone at Telin I can make an intro. Great > people, solid service. > > > > On Nov 19, 2025 at 9:07:54 AM, Aaron C. de Bruyn via VoiceOps < > [email protected]> wrote: > > > I'm not entirely up on the whole FCC Caller ID Spoofing crackdown that's > going on, but I just ran into a 3rd party service for medical offices that > expects us to spoof Caller ID. > > > > > > The service works like this: > > > * I grab my cell phone (123-456-7890) and call my > doctor/dentist/medical office > > > * It's after hours and they are busy with other calls > > > * Their phone system turns around and forwards my call to a 3rd-party > number (say 111-222-3333) emitting my Caller ID info ("Aaron" <1234567890>) > > > * They see a call come in on 111-222-3333 and know it's for "Dr. Bob's > Office", so their system accesses his patient database and looks for my > patient record with the phone number 123-456-7890 and someone answers the > call saying "Thanks for calling Dr. Bob's office". > > > > > > My understanding is the ability to spoof Caller ID info across the PSTN > is going away. > > > > > > I tested, and I certainly can't do it with a Twilio SIP trunk. > > > > > > The main reason I'm curious is I have a customer that has their own > phone system that I help them manage (FreePBX linked to Twilio). They just > purchased an office that uses a 3rd-party phone provider (Weave) along with > this 3rd-party answering service, and they are somewhat upset that I can't > make it work with their existing phone system. The third-party answering > service doesn't have any way of interconnecting other than spoofing Caller > ID over the PSTN to a random number they assigned to the medical office. > > > > > > Are services like this going the way of the dodo? Are they having to > set up private SIP trunks between clients to get this functionality? Do > some VoIP providers allow you to spoof Caller ID for this purpose under > some sort of agreement? > > > > > > Thanks, > > > > > > -A > > > _______________________________________________ > > > VoiceOps mailing list -- [email protected] > > > https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/ > > > To unsubscribe send an email to [email protected] > > _______________________________________________ > > VoiceOps mailing list -- [email protected] > > https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/ > > To unsubscribe send an email to [email protected] > > > > -- > Alex Balashov > Principal Consultant > Evariste Systems LLC > Web: https://evaristesys.com, https://www.csrpswitch.com > Tel: +1-706-510-6800 > >
_______________________________________________ VoiceOps mailing list -- [email protected] https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/ To unsubscribe send an email to [email protected]
