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
January 2026
- 10 participants
- 23 messages
Re: Services that rely on Caller ID spoofing?
by Calvin E.
I can second this from a company that both receives forwarded calls and
forwards calls. It is perfectly normal and standard to forward the caller
ID that you received. This is exactly what the Diversion header and div
passport were designed to do.
Diversion has been around forever as the SIP indication that a call was
forwarded. The major wireless carriers are now also using div passports now
when they forward calls. I know this because I receive forwarded calls from
them all day, every day. You should be completely in the clear, assuming
you signal correctly. Your platform will need to preserve the original
shaken passport and P-Asserted-Identity when appending your own div
passport and Diversion header.
Some platforms may not be updated to the current div passport standard, so
you'll need to confirm that first.
On Wed, Jan 7, 2026, 10:02 AM Kidd Filby via VoiceOps <voiceops(a)voiceops.org>
wrote:
> If memory serves me correctly, when I was testing all the variations of *Call
> Forwarding* during FoA testing of *Caller ID* in the 90's, The only CF
> feature that actually changed the calling number received by the
> terminating party was RCF ( Remote Call Forwarding ). This was done
> primarily for call vectoring. However, as I have mentioned before, there
> are legit reasons for doing so. For instance, Shelters, who have a PRI,
> will normally invoke Station ID Restriction in their PBX. This is done for
> the callers' protection.
>
> JM2C from an old guy.
>
> On Tue, Jan 6, 2026 at 8:25 PM David Frankel via VoiceOps <
> voiceops(a)voiceops.org> wrote:
>
>> Aaron,
>>
>>
>>
>> If I understand you correctly, you are dealing with a fairly conventional
>> call-forwarding situation, and that is addressed in the SHAKEN standards.
>> It does not have anything to do with an FCC “crackdown.”
>>
>>
>>
>> The standards (ATIS 1000085) define something called a DIV passport –
>> this is an additional signature (IDENTITY header) that is generated by the
>> service provider responsible for forward (DIVerting) the call. It generally
>> is used in conjunction with the SIP DIVERSION header.
>>
>>
>>
>> Sansay has a nice write-up about it here:
>>
>> https://support.sansay.com/t/p8hctyw/diversion-div-passport
>>
>>
>>
>> I do see mention of the DIV passport on this Twilio page:
>>
>> https://www.twilio.com/docs/voice/trusted-calling-with-shakenstir
>>
>>
>>
>> Whether your systems (and those of the provider receiving the forwarded
>> call) support DIV ppt is another matter.
>>
>>
>>
>> Forwarding is (still) perfectly legal and you don’t need to “spoof”
>> anything when following the standards.
>>
>>
>>
>> David
>>
>>
>>
>> *From:* Aaron C. de Bruyn via VoiceOps <voiceops(a)voiceops.org>
>> *Sent:* Tuesday, January 6, 2026 3:54 PM
>> *To:* Mary Lou Carey <marylou(a)backuptelecom.com>
>> *Cc:* Pinchas Neiman <neimanpinchas(a)gmail.com>; Mark R Lindsey, ECG <
>> lindsey(a)e-c-group.com>; voiceops(a)voiceops.org
>> *Subject:* [VoiceOps] Re: Services that rely on Caller ID spoofing?
>>
>>
>>
>> Unfortunately in this situation the 3rd-party company expects us to
>> receive calls from patients and instead of sending them to voicemail
>> after-hours, we forward the call on to them.
>>
>> That would require us to get permission to "spoof" numbers from tens of
>> thousands of patients.
>>
>>
>>
>> ...or...if the 3rd-party company wasn't completely incompetent, have us
>> set up a SIP or IAX trunk directly to them that does allow us to pass the
>> call to them without going over the PSTN.
>>
>>
>>
>> -A
>>
>>
>>
>>
>>
>> On Tue, Jan 6, 2026 at 2:50 PM Mary Lou Carey <marylou(a)backuptelecom.com>
>> wrote:
>>
>> There are certain circumstances where caller ID spoofing is allowed. For
>> example, in the situation where a doctor may be calling a patient after
>> hours. They can change the doctor's cell phone number to be the phone
>> number of the medical office the doctor works for. What people are not
>> allowed to do is to spoof a number that they do not have permission to use.
>>
>> What carrier "owns" the number is highly debatable these days because
>> there's multiple players.
>>
>> 1. The ILEC / CLEC / IPES / Wireless carrier that the NPA-NXX-X was
>> assigned to.
>>
>> 2. The carrier who manages the TN under their LRN. (In ported TN
>> situations)
>>
>> 3. The reseller who pays an upstream carrier for the DID service. (The
>> DID may have been resold multiple times so the OCN associated with the LRN
>> does not necessarily match the OCN of the carrier that manages the
>> assignment of TNs.
>>
>> Whoever has the direct connection with the end user customer has the
>> responsibility of ensuring that the TN is not spoofed in situations that
>> are illegal.
>>
>>
>>
>> MARY LOU CAREY
>> BackUP Telecom Consulting
>> Office: 615-791-9969
>> Cell: 615-796-1111
>>
>>
>>
>> On 2025-11-24 12:00 PM, Pinchas Neiman via VoiceOps wrote:
>>
>> 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
>>
>>
>>
>> _______________________________________________
>> 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
>>
>
>
> --
> Kidd Filby
> 661.557.5640 (C)
> http://www.linkedin.com/in/kiddfilby
>
>
> _______________________________________________
> 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
Jan. 8, 2026
Re: FYI: TDM Disconnections
by Mary Lou Carey
I just mentioned the LERG piece because a lot of people forget that step
and then their project gets shelved until they handle that piece. Since
you already made changes in the LERG and it sounds like your TDM trunks
have no more traffic coming in on them, then you just have to get a
project ID from the RBOC before you issue the disconnects. Lumen and
Verizon are not always as picky about getting a project ID first, but
AT&T definitely is.
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2026-01-07 11:21 AM, Mike Hammett wrote:
> In this particular case, it was a migration from TDM to a common IP-based solution for tandem access. The LERG effective date has passed and the TDM trunks flowed zero calls.
>
> ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com
> -------------------------
>
> From: "Mary Lou Carey via VoiceOps" <voiceops(a)voiceops.org>
> To: "voiceops" <voiceops(a)voiceops.org>
> Cc: "Kidd Filby" <kiddfilby(a)gmail.com>, "Mike Hammett" <voiceops(a)ics-il.net>, "Jeff Shultz" <jeffshultz(a)sctcweb.com>
> Sent: Tuesday, January 6, 2026 4:44 PM
> Subject: [VoiceOps] Re: FYI: TDM Disconnections
>
> I'm not sure what the question was that started this thread about disconnecting TDM trunks, but I specialize in writing ASRs for SS7 trunk groups (local, wireless, and FGD). Turning down the SS7 network doesn't start with disconnecting the trunk groups. The NPA-NXX codes all have to be returned or re-routed to a different switch in BIRRDS before the RBOC/ILEC will even assign a project ID. If the traffic is being routed to a different trunk group that was set up by a third party, the translations page on the ASR also needs to be completed so they change the NXX translations before they remove the trunks.
>
> There's not many of us dinosaurs left out there who know how the SS7 network is set up, muchless how to track down the information from the bills / system and write the orders for the trunks, transport, SS7 routes, and links. If you need help, you can reach out to me privately.
>
> MARY LOU CAREY
> BackUP Telecom Consulting
> Office: 615-791-9969
> Cell: 615-796-1111
>
> On 2026-01-06 02:40 PM, Jeff Shultz via VoiceOps wrote:
> You'll definitely want to be working with whoever manages SS7 for you, as there will likely be SS7 route sets involved that you will need to remove from your switch, particularly if the reason you are disconnecting the circuit is because the switch you were talking to is going away.
>
> On Tue, Jan 6, 2026 at 11:39 AM Kidd Filby via VoiceOps <voiceops(a)voiceops.org> wrote:
>
> Having done this numerous times across the country, this work order (Disco of Trunks &/or Facilities) is usually considered a PROJECT by the ILEC's, so be expecting an additional charge for it. Be diligent on their billing and estimates for the work. Make sure it makes sense. It is also a very good idea to validate each T1 to ensure you are both working on the same ones at the same time, before the cut-over or disco. I know SS7 usually does a great job keeping things straight but... I have found record discrepancies.... on both sides. Best to be safe than sorry.
>
> Good luck to all and congrats on being able to do it.
>
> On Tue, Jan 6, 2026 at 11:55 AM Mike Hammett via VoiceOps <voiceops(a)voiceops.org> wrote:
>
> FYI: If you're disconnecting TDM circuits from the tandem or other ILEC voice switches, you first need to put in disconnect orders for the trunk groups before you can disconnect the underlying DS1s or DS3s. Also, those trunk group identifications aren't on your bill, so you've got to work with the ILEC to get the information you need to be able to cancel circuits.
>
> -----
>
> Mike Hammett
>
> Intelligent Computing Solutions
>
> Midwest Internet Exchange
>
> DNA Communications
>
> _______________________________________________
> 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
>
> --
>
> Kidd Filby
> 661.557.5640 (C)
> http://www.linkedin.com/in/kiddfilby
>
> _______________________________________________
> 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
--
Jeff Shultz
Central Office Technician
SCTC
(503) 769-2125
Go Big - Ask for 5 Gig
Like us on Social Media for News, Promotions, and other information!!
[1] [2] [3] [4]
_*** This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you should
not disseminate, distribute or copy this e-mail. Please notify the
sender immediately by e-mail if you have received this e-mail by mistake
and delete this e-mail from your system. E-mail transmission cannot be
guaranteed to be secure or error-free as information could be
intercepted, corrupted, lost, destroyed, arrive late or incomplete, or
contain viruses. The sender therefore does not accept liability for any
errors or omissions in the contents of this message, which arise as a
result of e-mail transmission. ***_
_______________________________________________
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
Links:
------
[1] https://www.facebook.com/SCTCWEB/
[2] https://www.instagram.com/sctc_sctc/
[3] https://www.yelp.com/biz/sctc-stayton-3
[4] https://www.youtube.com/c/sctcvideos
Jan. 7, 2026
Re: Services that rely on Caller ID spoofing?
by Kidd Filby
If memory serves me correctly, when I was testing all the variations of *Call
Forwarding* during FoA testing of *Caller ID* in the 90's, The only CF
feature that actually changed the calling number received by the
terminating party was RCF ( Remote Call Forwarding ). This was done
primarily for call vectoring. However, as I have mentioned before, there
are legit reasons for doing so. For instance, Shelters, who have a PRI,
will normally invoke Station ID Restriction in their PBX. This is done for
the callers' protection.
JM2C from an old guy.
On Tue, Jan 6, 2026 at 8:25 PM David Frankel via VoiceOps <
voiceops(a)voiceops.org> wrote:
> Aaron,
>
>
>
> If I understand you correctly, you are dealing with a fairly conventional
> call-forwarding situation, and that is addressed in the SHAKEN standards.
> It does not have anything to do with an FCC “crackdown.”
>
>
>
> The standards (ATIS 1000085) define something called a DIV passport – this
> is an additional signature (IDENTITY header) that is generated by the
> service provider responsible for forward (DIVerting) the call. It generally
> is used in conjunction with the SIP DIVERSION header.
>
>
>
> Sansay has a nice write-up about it here:
>
> https://support.sansay.com/t/p8hctyw/diversion-div-passport
>
>
>
> I do see mention of the DIV passport on this Twilio page:
>
> https://www.twilio.com/docs/voice/trusted-calling-with-shakenstir
>
>
>
> Whether your systems (and those of the provider receiving the forwarded
> call) support DIV ppt is another matter.
>
>
>
> Forwarding is (still) perfectly legal and you don’t need to “spoof”
> anything when following the standards.
>
>
>
> David
>
>
>
> *From:* Aaron C. de Bruyn via VoiceOps <voiceops(a)voiceops.org>
> *Sent:* Tuesday, January 6, 2026 3:54 PM
> *To:* Mary Lou Carey <marylou(a)backuptelecom.com>
> *Cc:* Pinchas Neiman <neimanpinchas(a)gmail.com>; Mark R Lindsey, ECG <
> lindsey(a)e-c-group.com>; voiceops(a)voiceops.org
> *Subject:* [VoiceOps] Re: Services that rely on Caller ID spoofing?
>
>
>
> Unfortunately in this situation the 3rd-party company expects us to
> receive calls from patients and instead of sending them to voicemail
> after-hours, we forward the call on to them.
>
> That would require us to get permission to "spoof" numbers from tens of
> thousands of patients.
>
>
>
> ...or...if the 3rd-party company wasn't completely incompetent, have us
> set up a SIP or IAX trunk directly to them that does allow us to pass the
> call to them without going over the PSTN.
>
>
>
> -A
>
>
>
>
>
> On Tue, Jan 6, 2026 at 2:50 PM Mary Lou Carey <marylou(a)backuptelecom.com>
> wrote:
>
> There are certain circumstances where caller ID spoofing is allowed. For
> example, in the situation where a doctor may be calling a patient after
> hours. They can change the doctor's cell phone number to be the phone
> number of the medical office the doctor works for. What people are not
> allowed to do is to spoof a number that they do not have permission to use.
>
> What carrier "owns" the number is highly debatable these days because
> there's multiple players.
>
> 1. The ILEC / CLEC / IPES / Wireless carrier that the NPA-NXX-X was
> assigned to.
>
> 2. The carrier who manages the TN under their LRN. (In ported TN
> situations)
>
> 3. The reseller who pays an upstream carrier for the DID service. (The DID
> may have been resold multiple times so the OCN associated with the LRN does
> not necessarily match the OCN of the carrier that manages the assignment of
> TNs.
>
> Whoever has the direct connection with the end user customer has the
> responsibility of ensuring that the TN is not spoofed in situations that
> are illegal.
>
>
>
> MARY LOU CAREY
> BackUP Telecom Consulting
> Office: 615-791-9969
> Cell: 615-796-1111
>
>
>
> On 2025-11-24 12:00 PM, Pinchas Neiman via VoiceOps wrote:
>
> 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
>
>
>
> _______________________________________________
> 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
>
--
Kidd Filby
661.557.5640 (C)
http://www.linkedin.com/in/kiddfilby
Jan. 7, 2026
Re: FYI: TDM Disconnections
by Kidd Filby
Great job Mike
On Wed, Jan 7, 2026 at 10:21 AM Mike Hammett <voiceops(a)ics-il.net> wrote:
> In this particular case, it was a migration from TDM to a common IP-based
> solution for tandem access. The LERG effective date has passed and the TDM
> trunks flowed zero calls.
>
>
> ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com
> Midwest Internet Exchange http://www.midwest-ix.com
> ------------------------------
> *From:* "Mary Lou Carey via VoiceOps" <voiceops(a)voiceops.org>
> *To:* "voiceops" <voiceops(a)voiceops.org>
> *Cc:* "Kidd Filby" <kiddfilby(a)gmail.com>, "Mike Hammett" <
> voiceops(a)ics-il.net>, "Jeff Shultz" <jeffshultz(a)sctcweb.com>
> *Sent:* Tuesday, January 6, 2026 4:44 PM
> *Subject:* [VoiceOps] Re: FYI: TDM Disconnections
>
> I'm not sure what the question was that started this thread about
> disconnecting TDM trunks, but I specialize in writing ASRs for SS7 trunk
> groups (local, wireless, and FGD). Turning down the SS7 network doesn't
> start with disconnecting the trunk groups. The NPA-NXX codes all have to be
> returned or re-routed to a different switch in BIRRDS before the RBOC/ILEC
> will even assign a project ID. If the traffic is being routed to a
> different trunk group that was set up by a third party, the translations
> page on the ASR also needs to be completed so they change the NXX
> translations before they remove the trunks.
>
> There's not many of us dinosaurs left out there who know how the SS7
> network is set up, muchless how to track down the information from the
> bills / system and write the orders for the trunks, transport, SS7 routes,
> and links. If you need help, you can reach out to me privately.
>
> MARY LOU CAREY
> BackUP Telecom Consulting
> Office: 615-791-9969
> Cell: 615-796-1111
>
>
>
> On 2026-01-06 02:40 PM, Jeff Shultz via VoiceOps wrote:
>
> You'll definitely want to be working with whoever manages SS7 for you, as
> there will likely be SS7 route sets involved that you will need to remove
> from your switch, particularly if the reason you are disconnecting the
> circuit is because the switch you were talking to is going away.
>
>
> On Tue, Jan 6, 2026 at 11:39 AM Kidd Filby via VoiceOps <
> voiceops(a)voiceops.org> wrote:
>
>> Having done this numerous times across the country, this work order
>> (Disco of Trunks &/or Facilities) is usually considered a PROJECT by the
>> ILEC's, so be expecting an additional charge for it. Be diligent on their
>> billing and estimates for the work. Make sure it makes sense. It is also
>> a very good idea to validate each T1 to ensure you are both working on the
>> same ones at the same time, before the cut-over or disco. I know SS7
>> usually does a great job keeping things straight but... I have found record
>> discrepancies.... on both sides. Best to be safe than sorry.
>>
>> Good luck to all and congrats on being able to do it.
>>
>> On Tue, Jan 6, 2026 at 11:55 AM Mike Hammett via VoiceOps <
>> voiceops(a)voiceops.org> wrote:
>>
>>> FYI: If you're disconnecting TDM circuits from the tandem or other ILEC
>>> voice switches, you first need to put in disconnect orders for the trunk
>>> groups before you can disconnect the underlying DS1s or DS3s. Also, those
>>> trunk group identifications aren't on your bill, so you've got to work with
>>> the ILEC to get the information you need to be able to cancel circuits.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> -----
>>>
>>> Mike Hammett
>>>
>>> Intelligent Computing Solutions
>>>
>>> Midwest Internet Exchange
>>>
>>> DNA Communications
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>>
>>
>> --
>> Kidd Filby
>> 661.557.5640 (C)
>> http://www.linkedin.com/in/kiddfilby
>>
>>
>> _______________________________________________
>> 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
>
>
>
> --
> Jeff Shultz
> Central Office Technician
> SCTC
> (503) 769-2125
> Go Big - Ask for 5 Gig
>
> Like us on Social Media for News, Promotions, and other information!!
>
> <https://www.facebook.com/SCTCWEB/> [image:
> https://www.instagram.com/sctc_sctc/]
> <https://www.instagram.com/sctc_sctc/>
> <https://www.yelp.com/biz/sctc-stayton-3>
> <https://www.youtube.com/c/sctcvideos>
>
>
>
>
>
>
>
> **** This message contains confidential information and is intended only
> for the individual named. If you are not the named addressee you should not
> disseminate, distribute or copy this e-mail. Please notify the sender
> immediately by e-mail if you have received this e-mail by mistake and
> delete this e-mail from your system. E-mail transmission cannot be
> guaranteed to be secure or error-free as information could be intercepted,
> corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.
> The sender therefore does not accept liability for any errors or omissions
> in the contents of this message, which arise as a result of e-mail
> transmission. ****
>
> _______________________________________________
> 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
>
>
--
Kidd Filby
661.557.5640 (C)
http://www.linkedin.com/in/kiddfilby
Jan. 7, 2026
Re: FYI: TDM Disconnections
by Mike Hammett
In this particular case, it was a migration from TDM to a common IP-based solution for tandem access. The LERG effective date has passed and the TDM trunks flowed zero calls.
----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com
From: "Mary Lou Carey via VoiceOps" <voiceops(a)voiceops.org>
To: "voiceops" <voiceops(a)voiceops.org>
Cc: "Kidd Filby" <kiddfilby(a)gmail.com>, "Mike Hammett" <voiceops(a)ics-il.net>, "Jeff Shultz" <jeffshultz(a)sctcweb.com>
Sent: Tuesday, January 6, 2026 4:44 PM
Subject: [VoiceOps] Re: FYI: TDM Disconnections
I'm not sure what the question was that started this thread about disconnecting TDM trunks, but I specialize in writing ASRs for SS7 trunk groups (local, wireless, and FGD). Turning down the SS7 network doesn't start with disconnecting the trunk groups. The NPA-NXX codes all have to be returned or re-routed to a different switch in BIRRDS before the RBOC/ILEC will even assign a project ID. If the traffic is being routed to a different trunk group that was set up by a third party, the translations page on the ASR also needs to be completed so they change the NXX translations before they remove the trunks.
There's not many of us dinosaurs left out there who know how the SS7 network is set up, muchless how to track down the information from the bills / system and write the orders for the trunks, transport, SS7 routes, and links. If you need help, you can reach out to me privately.
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2026-01-06 02:40 PM, Jeff Shultz via VoiceOps wrote:
You'll definitely want to be working with whoever manages SS7 for you, as there will likely be SS7 route sets involved that you will need to remove from your switch, particularly if the reason you are disconnecting the circuit is because the switch you were talking to is going away.
On Tue, Jan 6, 2026 at 11:39 AM Kidd Filby via VoiceOps <voiceops(a)voiceops.org> wrote:
Having done this numerous times across the country, this work order (Disco of Trunks &/or Facilities) is usually considered a PROJECT by the ILEC's, so be expecting an additional charge for it. Be diligent on their billing and estimates for the work. Make sure it makes sense. It is also a very good idea to validate each T1 to ensure you are both working on the same ones at the same time, before the cut-over or disco. I know SS7 usually does a great job keeping things straight but... I have found record discrepancies.... on both sides. Best to be safe than sorry.
Good luck to all and congrats on being able to do it.
On Tue, Jan 6, 2026 at 11:55 AM Mike Hammett via VoiceOps <voiceops(a)voiceops.org> wrote:
FYI: If you're disconnecting TDM circuits from the tandem or other ILEC voice switches, you first need to put in disconnect orders for the trunk groups before you can disconnect the underlying DS1s or DS3s. Also, those trunk group identifications aren't on your bill, so you've got to work with the ILEC to get the information you need to be able to cancel circuits.
-----
Mike Hammett
Intelligent Computing Solutions
Midwest Internet Exchange
DNA Communications
_______________________________________________
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
--
Kidd Filby
661.557.5640 (C)
http://www.linkedin.com/in/kiddfilby
_______________________________________________
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
--
Jeff Shultz
Central Office Technician
SCTC
(503) 769-2125
Go Big - Ask for 5 Gig
Like us on Social Media for News, Promotions, and other information!!
*** This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. ***
_______________________________________________
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
Jan. 7, 2026
Re: Services that rely on Caller ID spoofing?
by David Frankel
Aaron,
If I understand you correctly, you are dealing with a fairly conventional call-forwarding situation, and that is addressed in the SHAKEN standards. It does not have anything to do with an FCC “crackdown.”
The standards (ATIS 1000085) define something called a DIV passport – this is an additional signature (IDENTITY header) that is generated by the service provider responsible for forward (DIVerting) the call. It generally is used in conjunction with the SIP DIVERSION header.
Sansay has a nice write-up about it here:
https://support.sansay.com/t/p8hctyw/diversion-div-passport
I do see mention of the DIV passport on this Twilio page:
https://www.twilio.com/docs/voice/trusted-calling-with-shakenstir
Whether your systems (and those of the provider receiving the forwarded call) support DIV ppt is another matter.
Forwarding is (still) perfectly legal and you don’t need to “spoof” anything when following the standards.
David
From: Aaron C. de Bruyn via VoiceOps <voiceops(a)voiceops.org>
Sent: Tuesday, January 6, 2026 3:54 PM
To: Mary Lou Carey <marylou(a)backuptelecom.com>
Cc: Pinchas Neiman <neimanpinchas(a)gmail.com>; Mark R Lindsey, ECG <lindsey(a)e-c-group.com>; voiceops(a)voiceops.org
Subject: [VoiceOps] Re: Services that rely on Caller ID spoofing?
Unfortunately in this situation the 3rd-party company expects us to receive calls from patients and instead of sending them to voicemail after-hours, we forward the call on to them.
That would require us to get permission to "spoof" numbers from tens of thousands of patients.
...or...if the 3rd-party company wasn't completely incompetent, have us set up a SIP or IAX trunk directly to them that does allow us to pass the call to them without going over the PSTN.
-A
On Tue, Jan 6, 2026 at 2:50 PM Mary Lou Carey <marylou(a)backuptelecom.com <mailto:marylou@backuptelecom.com> > wrote:
There are certain circumstances where caller ID spoofing is allowed. For example, in the situation where a doctor may be calling a patient after hours. They can change the doctor's cell phone number to be the phone number of the medical office the doctor works for. What people are not allowed to do is to spoof a number that they do not have permission to use.
What carrier "owns" the number is highly debatable these days because there's multiple players.
1. The ILEC / CLEC / IPES / Wireless carrier that the NPA-NXX-X was assigned to.
2. The carrier who manages the TN under their LRN. (In ported TN situations)
3. The reseller who pays an upstream carrier for the DID service. (The DID may have been resold multiple times so the OCN associated with the LRN does not necessarily match the OCN of the carrier that manages the assignment of TNs.
Whoever has the direct connection with the end user customer has the responsibility of ensuring that the TN is not spoofed in situations that are illegal.
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2025-11-24 12:00 PM, Pinchas Neiman via VoiceOps wrote:
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 <mailto:voiceops@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 <mailto:voiceops@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 <mailto:VoiceOps@voiceops.org>
https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
To unsubscribe send an email to voiceops-leave(a)voiceops.org <mailto:voiceops-leave@voiceops.org>
_______________________________________________
VoiceOps mailing list -- VoiceOps(a)voiceops.org <mailto:VoiceOps@voiceops.org>
https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
To unsubscribe send an email to voiceops-leave(a)voiceops.org <mailto:voiceops-leave@voiceops.org>
_______________________________________________
VoiceOps mailing list -- VoiceOps(a)voiceops.org <mailto:VoiceOps@voiceops.org>
https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
To unsubscribe send an email to voiceops-leave(a)voiceops.org <mailto:voiceops-leave@voiceops.org>
--
Pinchas S. Neiman
Software Engineer At ESEQ Technology Corp.
Providing you reliable software solutions for any matter.
845.213.1229 #2
_______________________________________________
VoiceOps mailing list -- VoiceOps(a)voiceops.org <mailto:VoiceOps@voiceops.org>
https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
To unsubscribe send an email to voiceops-leave(a)voiceops.org <mailto:voiceops-leave@voiceops.org>
Jan. 7, 2026
Re: Services that rely on Caller ID spoofing?
by Mary Lou Carey
If they want you to do that for them, I would have them sign an LOA for
each client that they want this service for. It should detail what
numbers are assigned to each customer and which of their customer
numbers can be spoofed to replace another number in the customer's list
of DIDs. That way if someone files a complaint, at least you're
protected because you followed the instructions of the customer's
carrier.
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2026-01-06 04:53 PM, Aaron C. de Bruyn wrote:
> Unfortunately in this situation the 3rd-party company expects us to receive calls from patients and instead of sending them to voicemail after-hours, we forward the call on to them.
> That would require us to get permission to "spoof" numbers from tens of thousands of patients.
>
> ...or...if the 3rd-party company wasn't completely incompetent, have us set up a SIP or IAX trunk directly to them that does allow us to pass the call to them without going over the PSTN.
>
> -A
>
> On Tue, Jan 6, 2026 at 2:50 PM Mary Lou Carey <marylou(a)backuptelecom.com> wrote:
>
> There are certain circumstances where caller ID spoofing is allowed. For example, in the situation where a doctor may be calling a patient after hours. They can change the doctor's cell phone number to be the phone number of the medical office the doctor works for. What people are not allowed to do is to spoof a number that they do not have permission to use.
>
> What carrier "owns" the number is highly debatable these days because there's multiple players.
>
> 1. The ILEC / CLEC / IPES / Wireless carrier that the NPA-NXX-X was assigned to.
>
> 2. The carrier who manages the TN under their LRN. (In ported TN situations)
>
> 3. The reseller who pays an upstream carrier for the DID service. (The DID may have been resold multiple times so the OCN associated with the LRN does not necessarily match the OCN of the carrier that manages the assignment of TNs.
>
> Whoever has the direct connection with the end user customer has the responsibility of ensuring that the TN is not spoofed in situations that are illegal.
>
> MARY LOU CAREY
> BackUP Telecom Consulting
> Office: 615-791-9969
> Cell: 615-796-1111
>
> On 2025-11-24 12:00 PM, Pinchas Neiman via VoiceOps wrote:
>
> 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
_______________________________________________
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
Jan. 6, 2026
Re: Services that rely on Caller ID spoofing?
by Aaron C. de Bruyn
Unfortunately in this situation the 3rd-party company expects us to receive
calls from patients and instead of sending them to voicemail after-hours,
we forward the call on to them.
That would require us to get permission to "spoof" numbers from tens of
thousands of patients.
...or...if the 3rd-party company wasn't completely incompetent, have us set
up a SIP or IAX trunk directly to them that does allow us to pass the call
to them without going over the PSTN.
-A
On Tue, Jan 6, 2026 at 2:50 PM Mary Lou Carey <marylou(a)backuptelecom.com>
wrote:
> There are certain circumstances where caller ID spoofing is allowed. For
> example, in the situation where a doctor may be calling a patient after
> hours. They can change the doctor's cell phone number to be the phone
> number of the medical office the doctor works for. What people are not
> allowed to do is to spoof a number that they do not have permission to use.
>
> What carrier "owns" the number is highly debatable these days because
> there's multiple players.
>
> 1. The ILEC / CLEC / IPES / Wireless carrier that the NPA-NXX-X was
> assigned to.
>
> 2. The carrier who manages the TN under their LRN. (In ported TN
> situations)
>
> 3. The reseller who pays an upstream carrier for the DID service. (The DID
> may have been resold multiple times so the OCN associated with the LRN does
> not necessarily match the OCN of the carrier that manages the assignment of
> TNs.
>
> Whoever has the direct connection with the end user customer has the
> responsibility of ensuring that the TN is not spoofed in situations that
> are illegal.
>
>
> MARY LOU CAREY
> BackUP Telecom Consulting
> Office: 615-791-9969
> Cell: 615-796-1111
>
>
> On 2025-11-24 12:00 PM, Pinchas Neiman via VoiceOps wrote:
>
> 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
>
> _______________________________________________
> 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
>
>
Jan. 6, 2026
Re: Services that rely on Caller ID spoofing?
by Mary Lou Carey
There are certain circumstances where caller ID spoofing is allowed. For
example, in the situation where a doctor may be calling a patient after
hours. They can change the doctor's cell phone number to be the phone
number of the medical office the doctor works for. What people are not
allowed to do is to spoof a number that they do not have permission to
use.
What carrier "owns" the number is highly debatable these days because
there's multiple players.
1. The ILEC / CLEC / IPES / Wireless carrier that the NPA-NXX-X was
assigned to.
2. The carrier who manages the TN under their LRN. (In ported TN
situations)
3. The reseller who pays an upstream carrier for the DID service. (The
DID may have been resold multiple times so the OCN associated with the
LRN does not necessarily match the OCN of the carrier that manages the
assignment of TNs.
Whoever has the direct connection with the end user customer has the
responsibility of ensuring that the TN is not spoofed in situations that
are illegal.
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2025-11-24 12:00 PM, Pinchas Neiman via VoiceOps wrote:
> 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
_______________________________________________
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
Jan. 6, 2026
Re: FYI: TDM Disconnections
by Mary Lou Carey
I'm not sure what the question was that started this thread about
disconnecting TDM trunks, but I specialize in writing ASRs for SS7 trunk
groups (local, wireless, and FGD). Turning down the SS7 network doesn't
start with disconnecting the trunk groups. The NPA-NXX codes all have to
be returned or re-routed to a different switch in BIRRDS before the
RBOC/ILEC will even assign a project ID. If the traffic is being routed
to a different trunk group that was set up by a third party, the
translations page on the ASR also needs to be completed so they change
the NXX translations before they remove the trunks.
There's not many of us dinosaurs left out there who know how the SS7
network is set up, muchless how to track down the information from the
bills / system and write the orders for the trunks, transport, SS7
routes, and links. If you need help, you can reach out to me privately.
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2026-01-06 02:40 PM, Jeff Shultz via VoiceOps wrote:
> You'll definitely want to be working with whoever manages SS7 for you, as there will likely be SS7 route sets involved that you will need to remove from your switch, particularly if the reason you are disconnecting the circuit is because the switch you were talking to is going away.
>
> On Tue, Jan 6, 2026 at 11:39 AM Kidd Filby via VoiceOps <voiceops(a)voiceops.org> wrote:
>
> Having done this numerous times across the country, this work order (Disco of Trunks &/or Facilities) is usually considered a PROJECT by the ILEC's, so be expecting an additional charge for it. Be diligent on their billing and estimates for the work. Make sure it makes sense. It is also a very good idea to validate each T1 to ensure you are both working on the same ones at the same time, before the cut-over or disco. I know SS7 usually does a great job keeping things straight but... I have found record discrepancies.... on both sides. Best to be safe than sorry.
>
> Good luck to all and congrats on being able to do it.
>
> On Tue, Jan 6, 2026 at 11:55 AM Mike Hammett via VoiceOps <voiceops(a)voiceops.org> wrote:
>
> FYI: If you're disconnecting TDM circuits from the tandem or other ILEC voice switches, you first need to put in disconnect orders for the trunk groups before you can disconnect the underlying DS1s or DS3s. Also, those trunk group identifications aren't on your bill, so you've got to work with the ILEC to get the information you need to be able to cancel circuits.
>
> -----
>
> Mike Hammett
>
> Intelligent Computing Solutions
>
> Midwest Internet Exchange
>
> DNA Communications
>
> _______________________________________________
> 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
>
> --
>
> Kidd Filby
> 661.557.5640 (C)
> http://www.linkedin.com/in/kiddfilby
>
> _______________________________________________
> 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
--
Jeff Shultz
Central Office Technician
SCTC
(503) 769-2125
Go Big - Ask for 5 Gig
Like us on Social Media for News, Promotions, and other information!!
[1] [2] [3] [4]
_*** This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you should
not disseminate, distribute or copy this e-mail. Please notify the
sender immediately by e-mail if you have received this e-mail by mistake
and delete this e-mail from your system. E-mail transmission cannot be
guaranteed to be secure or error-free as information could be
intercepted, corrupted, lost, destroyed, arrive late or incomplete, or
contain viruses. The sender therefore does not accept liability for any
errors or omissions in the contents of this message, which arise as a
result of e-mail transmission. ***_
_______________________________________________
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
Links:
------
[1] https://www.facebook.com/SCTCWEB/
[2] https://www.instagram.com/sctc_sctc/
[3] https://www.yelp.com/biz/sctc-stayton-3
[4] https://www.youtube.com/c/sctcvideos
Jan. 6, 2026