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
- 14 participants
- 10512 messages
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
Re: Level 3 Porting Speed
by Mike Hammett
*nods* In this particular case, this operator has ported this customer's numbers from us before. They're just now finishing the migration 10 years later. ;-)
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
----- Original Message -----
From: "Greg Stone" <Greg.Stone(a)race.com>
To: "Mike Hammett" <voiceops(a)ics-il.net>, "voiceops" <voiceops(a)voiceops.org>, "Ben Fullerton" <Benjamin.Fullerton(a)sinch.com>
Sent: Thursday, November 20, 2025 2:30:06 PM
Subject: Re: Level 3 Porting Speed
It's totally possible that the gaining carrier gave them a date to check a box in the process and the date will change.
10-15 business days to cut over to a hi-cap circuit including the port isn't too crazy.
The port is usually the last thing I would submit after all interop testing has completed. I lose 4 business days for the port to process, on a project port maybe more, but this ensures Ive had a chance to also confirm all the numbers with the PBX Vendor.
Since they are using L3 and arent a carrier themselves its probably safest to confirm all your numbers first, because as soon as you have to start SUPing requests to move dates or remove/add numbers it can get messy really quickly.
Their timeline is probably more like the idiom "theres always enough time to do it twice when you dont take the time to do it right the first time", however, we dont live in a vacuum so theres probably some time built in there for some disorganization.
Greg Stone
Senior Voice Network Engineer
Race Communications
E : Greg.Stone(a)race.com
P : 4153763306
Web : Visit Race.com
From: Ben Fullerton via VoiceOps <voiceops(a)voiceops.org>
Sent: Thursday, November 20, 2025 11:34 AM
To: Mike Hammett <voiceops(a)ics-il.net>; voiceops <voiceops(a)voiceops.org>
Subject: [VoiceOps] Re: Level 3 Porting Speed
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Depends on complexity, here is their site with their porting info: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.lumen…
Porting request types: simple, complex, and projects
A simple porting request is defined as a single phone number on a single account. Simple requests are processed within four hours of the request and can be ported within one business day.
A non-simple or complex porting request is defined as any request involving more than one phone number. Non-simple/complex requests are processed within 24 hours of the request and can be ported out in four business days.
Ben Fullerton | Director, Portability Ops | Sinch Voice | 406-532-3603
-----Original Message-----
From: Mike Hammett via VoiceOps <voiceops(a)voiceops.org>
Sent: Thursday, November 20, 2025 11:39 AM
To: voiceops <voiceops(a)voiceops.org>
Subject: [VoiceOps] Level 3 Porting Speed
How quickly does the Level 3 ecosystem work ports?
One of our customers is leaving (we're dropping their PRI and they didn't want to switch to our fiber). The gaining provider (who uses Level 3) told the customer it would be December 9th. We haven't received an LSR yet.
Is Level 3 that slow, or is my competitor just that disorganized?
-----
Mike Hammett
Intelligent Computing Solutions
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ics-il…
Midwest Internet Exchange
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.midwes…
_______________________________________________
VoiceOps mailing list -- VoiceOps(a)voiceops.org
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.voi…
To unsubscribe send an email to voiceops-leave(a)voiceops.org
_______________________________________________
VoiceOps mailing list -- VoiceOps(a)voiceops.org
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.voi…
To unsubscribe send an email to voiceops-leave(a)voiceops.org
Nov. 20, 2025
Re: Level 3 Porting Speed
by Greg Stone
It's totally possible that the gaining carrier gave them a date to check a box in the process and the date will change.
10-15 business days to cut over to a hi-cap circuit including the port isn't too crazy.
The port is usually the last thing I would submit after all interop testing has completed. I lose 4 business days for the port to process, on a project port maybe more, but this ensures Ive had a chance to also confirm all the numbers with the PBX Vendor.
Since they are using L3 and arent a carrier themselves its probably safest to confirm all your numbers first, because as soon as you have to start SUPing requests to move dates or remove/add numbers it can get messy really quickly.
Their timeline is probably more like the idiom "theres always enough time to do it twice when you dont take the time to do it right the first time", however, we dont live in a vacuum so theres probably some time built in there for some disorganization.
[cid:d74817f2-8290-49eb-abff-e7354e9358da]
Greg Stone
Senior Voice Network Engineer
Race Communications
E : Greg.Stone(a)race.com
P : 4153763306
Web : Visit Race.com<https://www.race.com/>
________________________________
From: Ben Fullerton via VoiceOps <voiceops(a)voiceops.org>
Sent: Thursday, November 20, 2025 11:34 AM
To: Mike Hammett <voiceops(a)ics-il.net>; voiceops <voiceops(a)voiceops.org>
Subject: [VoiceOps] Re: Level 3 Porting Speed
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Depends on complexity, here is their site with their porting info: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.lumen…<https://www.lumen.com/help/en-us/porting/port-out-request-tool.html>
Porting request types: simple, complex, and projects
A simple porting request is defined as a single phone number on a single account. Simple requests are processed within four hours of the request and can be ported within one business day.
A non-simple or complex porting request is defined as any request involving more than one phone number. Non-simple/complex requests are processed within 24 hours of the request and can be ported out in four business days.
Ben Fullerton | Director, Portability Ops | Sinch Voice | 406-532-3603
-----Original Message-----
From: Mike Hammett via VoiceOps <voiceops(a)voiceops.org>
Sent: Thursday, November 20, 2025 11:39 AM
To: voiceops <voiceops(a)voiceops.org>
Subject: [VoiceOps] Level 3 Porting Speed
How quickly does the Level 3 ecosystem work ports?
One of our customers is leaving (we're dropping their PRI and they didn't want to switch to our fiber). The gaining provider (who uses Level 3) told the customer it would be December 9th. We haven't received an LSR yet.
Is Level 3 that slow, or is my competitor just that disorganized?
-----
Mike Hammett
Intelligent Computing Solutions
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ics-il…<http://www.ics-il.com/>
Midwest Internet Exchange
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.midwes…<http://www.midwest-ix.com/>
_______________________________________________
VoiceOps mailing list -- VoiceOps(a)voiceops.org
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.voi…<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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.voi…<https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/>
To unsubscribe send an email to voiceops-leave(a)voiceops.org
Nov. 20, 2025
Re: Level 3 Porting Speed
by Ben Fullerton
My apologies, I misread and gave you the reverse timelines fro porting away from L3. If they are using L3 for port ins its going to take a bit longer, how long depends on the losing carrier and how L3 has it setup. As a general rule I would 5-7 business day intervals but there can be some nuance.
Ben Fullerton | Director, Portability Ops | Sinch Voice | 406-532-3603
-----Original Message-----
From: Mike Hammett <voiceops(a)ics-il.net>
Sent: Thursday, November 20, 2025 1:04 PM
To: Ben Fullerton <Benjamin.Fullerton(a)sinch.com>
Cc: voiceops <voiceops(a)voiceops.org>
Subject: Re: Level 3 Porting Speed
Would it be reasonable to assume that port-ins have a similar interval?
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com/
Midwest Internet Exchange
http://www.midwest-ix.com/
----- Original Message -----
From: "Ben Fullerton" <Benjamin.Fullerton(a)sinch.com>
To: "Mike Hammett" <voiceops(a)ics-il.net>, "voiceops" <voiceops(a)voiceops.org>
Sent: Thursday, November 20, 2025 1:34:47 PM
Subject: RE: Level 3 Porting Speed
Depends on complexity, here is their site with their porting info: https://www.lumen.com/help/en-us/porting/port-out-request-tool.html
Porting request types: simple, complex, and projects
A simple porting request is defined as a single phone number on a single account. Simple requests are processed within four hours of the request and can be ported within one business day.
A non-simple or complex porting request is defined as any request involving more than one phone number. Non-simple/complex requests are processed within 24 hours of the request and can be ported out in four business days.
Ben Fullerton | Director, Portability Ops | Sinch Voice | 406-532-3603
-----Original Message-----
From: Mike Hammett via VoiceOps <voiceops(a)voiceops.org>
Sent: Thursday, November 20, 2025 11:39 AM
To: voiceops <voiceops(a)voiceops.org>
Subject: [VoiceOps] Level 3 Porting Speed
How quickly does the Level 3 ecosystem work ports?
One of our customers is leaving (we're dropping their PRI and they didn't want to switch to our fiber). The gaining provider (who uses Level 3) told the customer it would be December 9th. We haven't received an LSR yet.
Is Level 3 that slow, or is my competitor just that disorganized?
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com/
Midwest Internet Exchange
http://www.midwest-ix.com/
_______________________________________________
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. 20, 2025