VoiceOps
By thread
voiceops@voiceops.org
By month
Messages by month
- ----- 2026 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
November 2025
- 19 participants
- 37 messages
Re: Services that rely on Caller ID spoofing?
by Pinchas Neiman
I think it's pretty clear that we are victims of crediting the holder
instead of the owner, the definition of number ownership, the "Deed", must
be decoupled from holding it. This should not be a matter of provider to
provider verification, but a global record that entity X may use that phone
number for caller ID.
Side note, hackers are hackers because they view themselves as experienced
troublemakers, the standard cowboy will not give up his career just because
a tech person earns more than him, although some smarter do, and some
hackers are getting smarter in prison.
On Mon, Nov 24, 2025 at 3:30 PM Mary Lou Carey via VoiceOps <
voiceops(a)voiceops.org> wrote:
> I think the intent to block spoofing is to prevent people from using
> telephone numbers they do not own. I once had a client that had the FBI
> show up on his doorstep because they said they traced a call back to his
> company. The number they were interested in was an unallocated TN in his
> PBX. Apparently someone had gotten ahold of that TN and was using it for
> nefarious purposes.
>
> Hackers are creative, I'll give them that. However, I'll never understand
> why they can't use their skills to make money legally. Why does one need to
> make mountains of money illegally when they can make enough to support
> themselves legally? Many create such a boatload of damage within a small
> amount of time that their poor innocent victims are detrimentally impacted
> by. I guess they don't care who they hurt. One can only hope Karma comes
> calling for them one day and reimburses them ten fold.
>
> MARY LOU CAREY
> BackUP Telecom Consulting
> Office: 615-791-9969
> Cell: 615-796-1111
>
>
> On 2025-11-22 08:11 PM, Mark R Lindsey, ECG via VoiceOps wrote:
>
> "Spoofing" is the standard term, even used in FCC docs, to mean that a
> person is placing a call from telephone number X using a voice service S,
> where calls placed from the PSTN to X don't always traverse service S.
>
> Of course this happens in conventional SIP trunking and wholesale
> interconnect *all the time. *It's so prevalent and normal that it's hard
> to even wrap your telecom head around what the FCC and the US congress even
> means. Why would you assume S is a symmetrical service for both placing and
> receiving calls? Does someone really think UPS or Bank Of America or even
> then local Memorial Hospital are seriously placing calls from exactly one
> place, or using a different "phone line" for each outbound call?
>
> And they do understand that it's extremely common. Read some discussion in
> the latest FNRPM from last month —
> https://docs.fcc.gov/public/attachments/FCC-25-76A1.pdf
> Attending conferences in this space and listening to FCC staffers, there
> is actually no push that I perceive to eliminate spoofing. But, there IS a
> push to eliminate the blind trust that anybody has the right to call from a
> telephone number, simply because they use it to populate the From header.
> In the latest suggestions from the FCC, what we might see are additional
> steps of vetting to determine you do have the right to place calls from a
> telephone number and the proper name that should be provided on that
> number.
>
> As of today, the "Know Your Customer" policy and practices of legitimate
> service providers will ensure the SP takes steps to confirm the right to
> place calls from the telephone numbers they use as the calling part number
> for outbound calls.
>
> In your example, Twilio was screening your calling party numbers. They
> probably have a list of telephone numbers from which you can call. I'm
> almost certain they have a process by which you can provide evidence you
> have the right to call from those numbers, and they'll update the screen
> list.
>
> Mark R Lindsey
> Member of Technical Staff / VP
> +1-229-316-0013
> https://info.ecg.co/lindsey
>
>
> On Wed, Nov 19, 2025 at 11:13 Aaron C. de Bruyn via VoiceOps <
> voiceops(a)voiceops.org> 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 -- VoiceOps(a)voiceops.org
>> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
>> To unsubscribe send an email to voiceops-leave(a)voiceops.org
>
>
> _______________________________________________
> VoiceOps mailing list -- VoiceOps(a)voiceops.org
> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
> To unsubscribe send an email to voiceops-leave(a)voiceops.org
>
> _______________________________________________
> VoiceOps mailing list -- VoiceOps(a)voiceops.org
> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
> To unsubscribe send an email to voiceops-leave(a)voiceops.org
--
*Pinchas S. Neiman*
Software Engineer At ESEQ Technology Corp.
Providing you reliable software solutions for any matter.
845.213.1229 #2
Nov. 24, 2025
Re: Services that rely on Caller ID spoofing?
by Mary Lou Carey
I think the intent to block spoofing is to prevent people from using
telephone numbers they do not own. I once had a client that had the FBI
show up on his doorstep because they said they traced a call back to his
company. The number they were interested in was an unallocated TN in his
PBX. Apparently someone had gotten ahold of that TN and was using it for
nefarious purposes.
Hackers are creative, I'll give them that. However, I'll never
understand why they can't use their skills to make money legally. Why
does one need to make mountains of money illegally when they can make
enough to support themselves legally? Many create such a boatload of
damage within a small amount of time that their poor innocent victims
are detrimentally impacted by. I guess they don't care who they hurt.
One can only hope Karma comes calling for them one day and reimburses
them ten fold.
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2025-11-22 08:11 PM, Mark R Lindsey, ECG via VoiceOps wrote:
> "Spoofing" is the standard term, even used in FCC docs, to mean that a person is placing a call from telephone number X using a voice service S, where calls placed from the PSTN to X don't always traverse service S.
>
> Of course this happens in conventional SIP trunking and wholesale interconnect _all the time. _It's so prevalent and normal that it's hard to even wrap your telecom head around what the FCC and the US congress even means. Why would you assume S is a symmetrical service for both placing and receiving calls? Does someone really think UPS or Bank Of America or even then local Memorial Hospital are seriously placing calls from exactly one place, or using a different "phone line" for each outbound call?
>
> And they do understand that it's extremely common. Read some discussion in the latest FNRPM from last month --
>
> https://docs.fcc.gov/public/attachments/FCC-25-76A1.pdf
> Attending conferences in this space and listening to FCC staffers, there is actually no push that I perceive to eliminate spoofing. But, there IS a push to eliminate the blind trust that anybody has the right to call from a telephone number, simply because they use it to populate the From header. In the latest suggestions from the FCC, what we might see are additional steps of vetting to determine you do have the right to place calls from a telephone number and the proper name that should be provided on that number.
>
> As of today, the "Know Your Customer" policy and practices of legitimate service providers will ensure the SP takes steps to confirm the right to place calls from the telephone numbers they use as the calling part number for outbound calls.
>
> In your example, Twilio was screening your calling party numbers. They probably have a list of telephone numbers from which you can call. I'm almost certain they have a process by which you can provide evidence you have the right to call from those numbers, and they'll update the screen list.
>
> Mark R Lindsey
> Member of Technical Staff / VP
> +1-229-316-0013
> https://info.ecg.co/lindsey
>
> On Wed, Nov 19, 2025 at 11:13 Aaron C. de Bruyn via VoiceOps <voiceops(a)voiceops.org> 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 -- VoiceOps(a)voiceops.org
>> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
>> To unsubscribe send an email to voiceops-leave(a)voiceops.org
>
> _______________________________________________
> VoiceOps mailing list -- VoiceOps(a)voiceops.org
> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
> To unsubscribe send an email to voiceops-leave(a)voiceops.org
Nov. 24, 2025
Re: Services that rely on Caller ID spoofing?
by Kidd Filby
There have been reasons for legitimate spoofing. I have first-hand
experience with this related to PRI service over the decades. PRI
translations allow for overriding the calling TN, for situations like
battered women shelters and other humanity organizations so they cannot be
traced back.
However, I would have to admit.. I have been approached for such a service
way more times for sketchy situations than legit.
Kidd Filby
661.557.5640 (C)
http://www.linkedin.com/in/kiddfilby
On Sat, Nov 22, 2025 at 19:16 Mark R Lindsey, ECG via VoiceOps <
voiceops(a)voiceops.org> wrote:
> “Spoofing” is the standard term, even used in FCC docs, to mean that a
> person is placing a call from telephone number X using a voice service S,
> where calls placed from the PSTN to X don’t always traverse service S.
>
> Of course this happens in conventional SIP trunking and wholesale
> interconnect *all the time. *It’s so prevalent and normal that it’s hard
> to even wrap your telecom head around what the FCC and the US congress even
> means. Why would you assume S is a symmetrical service for both placing and
> receiving calls? Does someone really think UPS or Bank Of America or even
> then local Memorial Hospital are seriously placing calls from exactly one
> place, or using a different “phone line” for each outbound call?
>
> And they do understand that it’s extremely common. Read some discussion in
> the latest FNRPM from last month —
> https://docs.fcc.gov/public/attachments/FCC-25-76A1.pdf
>
> Attending conferences in this space and listening to FCC staffers, there
> is actually no push that I perceive to eliminate spoofing. But, there IS a
> push to eliminate the blind trust that anybody has the right to call from a
> telephone number, simply because they use it to populate the From header.
> In the latest suggestions from the FCC, what we might see are additional
> steps of vetting to determine you do have the right to place calls from a
> telephone number and the proper name that should be provided on that
> number.
>
> As of today, the “Know Your Customer” policy and practices of legitimate
> service providers will ensure the SP takes steps to confirm the right to
> place calls from the telephone numbers they use as the calling part number
> for outbound calls.
>
> In your example, Twilio was screening your calling party numbers. They
> probably have a list of telephone numbers from which you can call. I’m
> almost certain they have a process by which you can provide evidence you
> have the right to call from those numbers, and they’ll update the screen
> list.
>
> Mark R Lindsey
> Member of Technical Staff / VP
> +1-229-316-0013
> https://info.ecg.co/lindsey
>
>
> On Wed, Nov 19, 2025 at 11:13 Aaron C. de Bruyn via VoiceOps <
> voiceops(a)voiceops.org> 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 -- VoiceOps(a)voiceops.org
>> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
>> To unsubscribe send an email to voiceops-leave(a)voiceops.org
>
> _______________________________________________
> VoiceOps mailing list -- VoiceOps(a)voiceops.org
> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
> To unsubscribe send an email to voiceops-leave(a)voiceops.org
Nov. 23, 2025
Re: Services that rely on Caller ID spoofing?
by Mark R Lindsey, ECG
“Spoofing” is the standard term, even used in FCC docs, to mean that a
person is placing a call from telephone number X using a voice service S,
where calls placed from the PSTN to X don’t always traverse service S.
Of course this happens in conventional SIP trunking and wholesale
interconnect *all the time. *It’s so prevalent and normal that it’s hard to
even wrap your telecom head around what the FCC and the US congress even
means. Why would you assume S is a symmetrical service for both placing and
receiving calls? Does someone really think UPS or Bank Of America or even
then local Memorial Hospital are seriously placing calls from exactly one
place, or using a different “phone line” for each outbound call?
And they do understand that it’s extremely common. Read some discussion in
the latest FNRPM from last month —
https://docs.fcc.gov/public/attachments/FCC-25-76A1.pdf
Attending conferences in this space and listening to FCC staffers, there is
actually no push that I perceive to eliminate spoofing. But, there IS a
push to eliminate the blind trust that anybody has the right to call from a
telephone number, simply because they use it to populate the From header.
In the latest suggestions from the FCC, what we might see are additional
steps of vetting to determine you do have the right to place calls from a
telephone number and the proper name that should be provided on that
number.
As of today, the “Know Your Customer” policy and practices of legitimate
service providers will ensure the SP takes steps to confirm the right to
place calls from the telephone numbers they use as the calling part number
for outbound calls.
In your example, Twilio was screening your calling party numbers. They
probably have a list of telephone numbers from which you can call. I’m
almost certain they have a process by which you can provide evidence you
have the right to call from those numbers, and they’ll update the screen
list.
Mark R Lindsey
Member of Technical Staff / VP
+1-229-316-0013
https://info.ecg.co/lindsey
On Wed, Nov 19, 2025 at 11:13 Aaron C. de Bruyn via VoiceOps <
voiceops(a)voiceops.org> 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 -- VoiceOps(a)voiceops.org
> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
> To unsubscribe send an email to voiceops-leave(a)voiceops.org
Nov. 23, 2025
Re: Services that rely on Caller ID spoofing?
by Aaron C. de Bruyn
I appreciate all the replies.
I talked with some "engineer" higher up at the company and they were
blissfully unaware of the Caller ID changes.
(Probably because they weren't from the US)
On somewhat of a side note, I don't get the unrelenting pressure in the
healthcare industry to offshore everything to places that don't have the
same data protection laws as us.
Eventually someone's going to get bit hard when they realize they've been
sending all their patients' voices off shore to help train an AI or to
gather data and that service gets breached with zero recourse.
In this particular situation, I don't understand why a simple voicemail box
won't work.
No one wants to talk to AI. Least of all to talk to AI to have it
summarize what a caller wants only to get an email attachment of the
summary along with an audio attachment via email.
-A
On Wed, Nov 19, 2025 at 8:07 AM Aaron C. de Bruyn <aaron(a)heyaaron.com>
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
>
Nov. 22, 2025
Re: Services that rely on Caller ID spoofing?
by Alex Balashov
Ha ha.
But there's no concerted industry and regulatory scheme to block fax per se.
> On Nov 21, 2025, at 5:12 PM, Carlos Alvarez via VoiceOps <voiceops(a)voiceops.org> wrote:
>
> Also, fax will be dead by 2005 at the latest.
>
>
> On Nov 21, 2025 at 3:10:30 PM, Alex Balashov <abalashov(a)evaristesys.com> 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 <voiceops(a)voiceops.org> 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 <voiceops(a)voiceops.org> 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 -- VoiceOps(a)voiceops.org
>>> > https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
>>> > To unsubscribe send an email to voiceops-leave(a)voiceops.org
>>> _______________________________________________
>>> VoiceOps mailing list -- VoiceOps(a)voiceops.org
>>> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
>>> To unsubscribe send an email to voiceops-leave(a)voiceops.org
>>
>>
>> --
>> Alex Balashov
>> Principal Consultant
>> Evariste Systems LLC
>> Web: https://evaristesys.com, https://www.csrpswitch.com
>> Tel: +1-706-510-6800
>>
> _______________________________________________
> VoiceOps mailing list -- VoiceOps(a)voiceops.org
> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
> To unsubscribe send an email to voiceops-leave(a)voiceops.org
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com, https://www.csrpswitch.com
Tel: +1-706-510-6800
Nov. 21, 2025
Re: Services that rely on Caller ID spoofing?
by Aryn Nakaoka 808.356.2901
What happens is a patient doesn't show caller ID now? Eventually the
service will ask for an patient ID of some sort or just treat all incoming
calls from scratch.
But eventually you'll just have B Attestation:
*B — Partial Attestation*
*Meaning:*
The originating service provider *knows the caller* but *cannot confirm
that the caller is entitled to use the phone number*.
*Common scenarios:*
-
Calls coming from a PBX or VoIP provider *upstream*, where the
terminating carrier knows the upstream provider but *not the end user*.
-
Calls where caller-ID numbers are provided by the customer and not
verified.
*Example:*
A carrier receives a call from a SIP trunk reseller who authenticates the
customer but *does not verify* the specific caller-ID.
*Confidence level:* Medium.
On Fri, Nov 21, 2025 at 12:24 PM Alex Balashov via VoiceOps <
voiceops(a)voiceops.org> 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 <
> voiceops(a)voiceops.org> 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 <
> voiceops(a)voiceops.org> 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 -- VoiceOps(a)voiceops.org
> >> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
> >> To unsubscribe send an email to voiceops-leave(a)voiceops.org
> > _______________________________________________
> > VoiceOps mailing list -- VoiceOps(a)voiceops.org
> > https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
> > To unsubscribe send an email to voiceops-leave(a)voiceops.org
>
>
> --
> Alex Balashov
> Principal Consultant
> Evariste Systems LLC
> Web: https://evaristesys.com, https://www.csrpswitch.com
> Tel: +1-706-510-6800
>
> _______________________________________________
> VoiceOps mailing list -- VoiceOps(a)voiceops.org
> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
> To unsubscribe send an email to voiceops-leave(a)voiceops.org
Nov. 21, 2025
Re: Services that rely on Caller ID spoofing?
by Carlos Alvarez
Also, fax will be dead by 2005 at the latest.
On Nov 21, 2025 at 3:10:30 PM, Alex Balashov <abalashov(a)evaristesys.com>
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 <
> voiceops(a)voiceops.org> 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 <
> voiceops(a)voiceops.org> 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 -- VoiceOps(a)voiceops.org
>
> > https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
>
> > To unsubscribe send an email to voiceops-leave(a)voiceops.org
>
> _______________________________________________
>
> VoiceOps mailing list -- VoiceOps(a)voiceops.org
>
> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
>
> To unsubscribe send an email to voiceops-leave(a)voiceops.org
>
>
>
> --
> Alex Balashov
> Principal Consultant
> Evariste Systems LLC
> Web: https://evaristesys.com, https://www.csrpswitch.com
> Tel: +1-706-510-6800
>
>
Nov. 21, 2025
Re: Services that rely on Caller ID spoofing?
by Alex Balashov
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 <voiceops(a)voiceops.org> 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 <voiceops(a)voiceops.org> 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 -- VoiceOps(a)voiceops.org
>> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
>> To unsubscribe send an email to voiceops-leave(a)voiceops.org
> _______________________________________________
> VoiceOps mailing list -- VoiceOps(a)voiceops.org
> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
> To unsubscribe send an email to voiceops-leave(a)voiceops.org
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com, https://www.csrpswitch.com
Tel: +1-706-510-6800
Nov. 21, 2025
Re: Services that rely on Caller ID spoofing?
by Carlos Alvarez
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 <
voiceops(a)voiceops.org> 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 -- VoiceOps(a)voiceops.org
> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
> To unsubscribe send an email to voiceops-leave(a)voiceops.org
>
Nov. 21, 2025