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
August 2021
- 17 participants
- 27 messages
Wholesale Platforms - 2021 Edition
by marylou@backuptelecom.com
I got about 4-5 responses. I guess I will need to do a search on the old
discussions even though a lot has changed.
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2021-08-22 06:09 PM, Colton Conor wrote:
> Calvin,
>
> Did you receive any responses to this email? Last time when I asked
> the same question there was quite a bit of discussion in 2019 if I
> remember correctly.
>
> On Mon, Jul 26, 2021 at 8:13 PM Calvin Ellison
> <calvin.ellison at voxox.com> wrote:
>
>> This question comes up every few years, let's get an update for the
>> cloud era!
>>
>> Looking for a wholesale voice & SMS routing, billing, and analytics
>> platform that can meet these requirements:
>>
>> * Cloud or Hosted solution for everything but the call path
>> * Scale is billions of call attempts per month, dozens of vendors
>> with full NPA-NXX or A-Z detailed breakouts
>> * Intelligent, performance-based rate generation, "better than LCR"
>> * Realtime intelligence in call routing (performance-based routing)
>> * Support for DID/Toll-Free inventory with forwarding/failover
>> routing
>> * Proper rating and costing for inbound, outbound, on-net,
>> toll-free, reciprocal comp, dips, commissions
>>
>> * Call routing engines go next to our SBCs to minimize latency
>> * Call routing engines can operate disconnected from the main
>> database
>>
>> * Call routing engines scale is up to 10,000 calls/messages per
>> second
>> * Management APIs for administrators and clients
>> * Client portal to manage trunks/binds, make payments, download
>> CDRs, view reporting/analytics
>> * Admin portal for provisioning, analytics, billing
>> * Agent portal for monitoring clients, commissions, payouts
>> * SMS must support SMPP and REST API for messaging
>> * MMS protocols supported
>> * No database license that costs more than the actual product
>> * Easy to use analytics - better than we can do with
>> Elasticsearch/Kibana
>>
>> Bonus:
>>
>> * Support for Sansay VSXi external routing queries
>> * Support for Sansay VSXi provisioning
>> * STIR/SHAKEN features including enterprise extensions like
>> Delegated Certificates, DLT, Central TN, Registered Caller, etc.
>> * Ready for Rich Call Data/Branded Call Display
>>
>> Calvin Ellison
>>
>> Systems Architect
>>
>> calvin.ellison at voxox.com
>>
>> [1]
>>
>> [2] [3] [4] [5]
>> The information contained herein is confidential and privileged
>> information or work product intended only for the individual or
>> entity to whom it is addressed. Any unauthorized use, distribution,
>> or copying of this communication is strictly prohibited. If you have
>> received this communication in error, please notify me immediately.
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>
>
> Links:
> ------
> [1] http://voxox.com
> [2] https://www.facebook.com/VOXOX/
> [3] https://www.instagram.com/voxoxofficial/
> [4] https://www.linkedin.com/company/3573541/admin/
> [5] https://twitter.com/Voxox
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Aug. 25, 2021
Wholesale Platforms - 2021 Edition
by colton.conor@gmail.com
Calvin,
Did you receive any responses to this email? Last time when I asked the
same question there was quite a bit of discussion in 2019 if I remember
correctly.
On Mon, Jul 26, 2021 at 8:13 PM Calvin Ellison <calvin.ellison at voxox.com>
wrote:
> This question comes up every few years, let's get an update for the cloud
> era!
>
> Looking for a wholesale voice & SMS routing, billing, and analytics
> platform that can meet these requirements:
>
> - Cloud or Hosted solution for everything but the call path
> - Scale is billions of call attempts per month, dozens of vendors with
> full NPA-NXX or A-Z detailed breakouts
> - Intelligent, performance-based rate generation, "better than LCR"
> - Realtime intelligence in call routing (performance-based routing)
> - Support for DID/Toll-Free inventory with forwarding/failover routing
> - Proper rating and costing for inbound, outbound, on-net, toll-free,
> reciprocal comp, dips, commissions
> - Call routing engines go next to our SBCs to minimize latency
> - Call routing engines can operate disconnected from the main database
> - Call routing engines scale is up to 10,000 calls/messages per second
> - Management APIs for administrators and clients
> - Client portal to manage trunks/binds, make payments, download CDRs,
> view reporting/analytics
> - Admin portal for provisioning, analytics, billing
> - Agent portal for monitoring clients, commissions, payouts
> - SMS must support SMPP and REST API for messaging
> - MMS protocols supported
> - No database license that costs more than the actual product
> - Easy to use analytics - better than we can do with
> Elasticsearch/Kibana
>
> Bonus:
>
> - Support for Sansay VSXi external routing queries
> - Support for Sansay VSXi provisioning
> - STIR/SHAKEN features including enterprise extensions like Delegated
> Certificates, DLT, Central TN, Registered Caller, etc.
> - Ready for Rich Call Data/Branded Call Display
>
>
>
> Calvin Ellison
>
> Systems Architect
>
> calvin.ellison at voxox.com
>
> <http://voxox.com>
>
> <https://www.facebook.com/VOXOX/>
> <https://www.instagram.com/voxoxofficial/>
> <https://www.linkedin.com/company/3573541/admin/>
> <https://twitter.com/Voxox>
>
> The information contained herein is confidential and privileged
> information or work product intended only for the individual or entity to
> whom it is addressed. Any unauthorized use, distribution, or copying of
> this communication is strictly prohibited. If you have received this
> communication in error, please notify me immediately.
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
Aug. 22, 2021
STIR/SHAKEN concerns
by marylou@backuptelecom.com
Thanks to all who responded! If you would like to reply privately rather
than publicly just send your message to marylou at backuptelecom.com.
I always like to keep my ear to the ground for what's going on and as
usual you all are the best sources of information because you see it
playing out in real time!
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2021-08-19 09:22 PM, Mary Lou Carey wrote:
> I am doing some research for an article so I wanted to ask all of you
> some questions about STIR/SHAKEN and the upcoming implementation in
> late September when traffic will start getting blocked. I personally
> envision the first few months will be a nightmare! Ironically this
> will all hit just as elections are about to take place......how
> convenient! When the industry missed so many steps on the
> implementation phase, there's sure to be things they've missed in this
> phase so let's think ahead so we can address as many problems as we
> can before they happen! I specifically want to focus on the effect the
> changes are having and will have on end user customers. Not only
> residential and small business customers, but enterprise customers
> such as schools, hospitals, banks, political organizations, and other
> industries that use call centers. Please respond to the questions
> below and let me know your thoughts.
>
> 1. Have you seen any changes in the industry since the June 30th
> implementation date. I have witnessed a few odd routing issues that
> have never happened in the past. I'm not sure if they are a fluke or a
> trend. Have you experienced anything out of the ordinary?
>
> 2. If your network is partially TDM and partially VOIP, have you
> experienced any issues with either of them? What are your future
> concerns since STIR/SHAKEN does not work with TDM?
>
> 3. My biggest complaint as a residential consumer is that caller ID no
> longer shows up like it did. Unless I have the number in my phone, I
> only see something along the lines of Scam Likely or a phone number
> with no caller ID. I find this quite irritating since it prevents me
> from determining if its a friend whose carrier hasn't implemented it
> yet or an actual scammer. Anyone else have complaints about what
> information is being passed?
>
> 4. Are you getting more complaints from your customers about anything
> related to STIR/SHAKEN? What are the nature of the complaints? Is
> there a recurring theme?
>
> 5. What is your customer's impression of what a Robocall is? My son
> claims he's getting more SCAM calls than he was before but I'm not
> sure he understands what a Robocall is. He may consider any
> advertisement or donation request a robocall, but some things are
> allowed while others aren't. What are you doing to help your customers
> understand what's allowed and what's not allowed?
>
> 6. If you're hearing from customers about scam calls they are getting,
> are you reporting those calls to anyone? If so, who are you reporting
> them to?
>
> 6. Criminals always seem to be creative. Have you seen any new methods
> scammers are using to get around STIR/SHAKEN process?
>
> 7. One of my greatest concerns I have about the September
> implementation is that carriers will get no warning if/when they are
> going to be blocked. I haven't seen anything that states a terminating
> carrier or intermediate carrier has to give a warning muchless
> disclose that they will start blocking another carrier's traffic.
> Maybe there is a hotline to call if your traffic is being blocked
> unjustly, but I haven't heard of any. Have you? Normal routing issues
> are already a nightmare to deal with. Hopefully this will not make it
> worse or just another method for anti-competitive carriers to take out
> their competition!
>
> 8. The last question leads me to the next one. I know there are some
> carriers using their underlying carrier's certificate so they didn't
> register for the Robocall Mitigation Database. I didn't recommend
> this, but I heard through the grapevine some consultants / underlying
> carriers did. If those who didn't sign up for the Robocall Mitigation
> Database have legitimate traffic shut down, what will happen to all
> their legitimate customers? Will they be out of service until the ITG
> gets around to figuring it out? Has anyone heard of a plan to address
> the impact on consumers displaced by this?
>
> 9. Has anyone heard of a centralized contact to deal with unjust
> blocking complaints? We all know nothing goes perfectly but I would
> think it will be important for everyone to know what number to call
> should they have problems BEFORE this change is implemented. Have any
> of you heard anything? I haven't!
>
>
> 10. I tried to keep my list simple but I would love to hear your
> thoughts on anything I missed.
>
>
> Thanks for all your input,
>
> MARY LOU CAREY
> BackUP Telecom Consulting
> Office: 615-791-9969
> Cell: 615-796-1111
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Aug. 21, 2021
STIR/SHAKEN concerns
by karl@piratel.com
I'm just enjoying (not really) sending calls to VZ/ATT mobile numbers and
getting the response back from both that the SIP calls are going into their
TDM network so, oops, token gone.
On Fri, Aug 20, 2021 at 10:51 AM Mike Johnston <mjohnston at wiktel.com> wrote:
> > 2. If your network is partially TDM and partially VOIP, have you
> experienced any issues with either of them? What are your future concerns
> since STIR/SHAKEN does not work with TDM?
>
> We have a mix of TDM and SIP. We are continuing to work towards an all
> SIP network. However, our aging management is still stuck in the legacy
> mindset where TDM made us money (subsidies). There are other reasons as
> well, such as simply a resistance to change, lack of knowing how
> something works can lead to a fear of it, etc. I am hoping and praying
> that STIR/SHAKEN _NEVER_ works with TDM, so it forces our hand to an all
> SIP environment.
>
> We have both SIP and TDM trunking with Inteliquent for toll sort of
> stuff. All of our EAS trunks with neighboring telcos is still TDM only.
>
> > 10. I tried to keep my list simple but I would love to hear your
> thoughts on anything I missed.
>
> For whatever reason, some telcos are simply marking everything as "A".
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
--
Karl Douthit
10572 Calle Lee #123
Los Alamitos Ca. 90720
(562) 257-3590 (Desk)
(562) 824-0757 <%28562%29%20827-0757> (Mobile)
*www.piratel.com <http://www.piratel.com/>*
Aug. 20, 2021
STIR/SHAKEN concerns
by mjohnston@wiktel.com
> 2. If your network is partially TDM and partially VOIP, have you experienced any issues with either of them? What are your future concerns since STIR/SHAKEN does not work with TDM?
We have a mix of TDM and SIP. We are continuing to work towards an all
SIP network. However, our aging management is still stuck in the legacy
mindset where TDM made us money (subsidies). There are other reasons as
well, such as simply a resistance to change, lack of knowing how
something works can lead to a fear of it, etc. I am hoping and praying
that STIR/SHAKEN _NEVER_ works with TDM, so it forces our hand to an all
SIP environment.
We have both SIP and TDM trunking with Inteliquent for toll sort of
stuff. All of our EAS trunks with neighboring telcos is still TDM only.
> 10. I tried to keep my list simple but I would love to hear your thoughts on anything I missed.
For whatever reason, some telcos are simply marking everything as "A".
Aug. 20, 2021
STIR/SHAKEN concerns
by glen@cognexus.net
>
> 2. If your network is partially TDM and partially VOIP, have you
> experienced any issues with either of them? What are your future
> concerns since STIR/SHAKEN does not work with TDM?
This will certainly weaken the benefits of S/S since the ID Header will
be stripped off along many paths. Out Of Band S/S is slow moving but may
help in the long run. In the mean time it's no worse than before S/S of
course....
>
> 3. My biggest complaint as a residential consumer is that caller ID no
> longer shows up like it did. Unless I have the number in my phone, I
> only see something along the lines of Scam Likely or a phone number
> with no caller ID. I find this quite irritating since it prevents me
> from determining if its a friend whose carrier hasn't implemented it
> yet or an actual scammer. Anyone else have complaints about what
> information is being passed?
As Paul said this is a function of the CVT and your carrier. RCD might
help a little although the CVT will still control the CNAM delivery display.
>
>
>
> 7. One of my greatest concerns I have about the September
> implementation is that carriers will get no warning if/when they are
> going to be blocked. I haven't seen anything that states a terminating
> carrier or intermediate carrier has to give a warning muchless
> disclose that they will start blocking another carrier's traffic.
> Maybe there is a hotline to call if your traffic is being blocked
> unjustly, but I haven't heard of any. Have you? Normal routing issues
> are already a nightmare to deal with. Hopefully this will not make it
> worse or just another method for anti-competitive carriers to take out
> their competition!
You need to monitor you calls for Cause Code 608s. Although it's not
always passed end-end the tracking is helpful and you won't know until
the calls are being rejected.
>
> 8. The last question leads me to the next one. I know there are some
> carriers using their underlying carrier's certificate so they didn't
> register for the Robocall Mitigation Database. I didn't recommend
> this, but I heard through the grapevine some consultants / underlying
> carriers did. If those who didn't sign up for the Robocall Mitigation
> Database have legitimate traffic shut down, what will happen to all
> their legitimate customers? Will they be out of service until the ITG
> gets around to figuring it out? Has anyone heard of a plan to address
> the impact on consumers displaced by this?
It sounds a bit like Delegated Certs before they're adopted. I wouldn't
want to bet my business that those calls will go through for long.
Good luck,
~Glen
Cognexus, LLC
7891 Avenida Kirjah
San Diego, CA 92037
Aug. 20, 2021
STIR/SHAKEN concerns
by abalashov@evaristesys.com
> On Aug 19, 2021, at 11:24 PM, Paul Timmins <paul at timmins.net> wrote:
>
>> 3. My biggest complaint as a residential consumer is that caller ID no longer shows up like it did. Unless I have the number in my phone, I only see something along the lines of Scam Likely or a phone number with no caller ID. I find this quite irritating since it prevents me from determining if its a friend whose carrier hasn't implemented it yet or an actual scammer. Anyone else have complaints about what information is being passed?
>
> ... This has nothing to do with STIR/SHAKEN. CNAM is either dipped or passed in the From or P-Asserted-Identity field. You might want to reach out to your (cellular) carrier and see why you aren't getting caller id.
My experience of this phenomenon, as an iPhone user, is that the phone number is buried in the call log ? if you take special steps to pull it up. However, what shows up on the screen by default is just the CNAM. That?s been very frustrating to me, too, since, like many telephony professionals on this list, I can often tell a lot about a caller if I can actually see their number.
That behaviour did change at some point from presenting the calling number as well. I?m not sure if it?s an aspect of carrier settings.
? Alex
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
Aug. 20, 2021
STIR/SHAKEN concerns
by paul@timmins.net
> On Aug 19, 2021, at 10:22 PM, Mary Lou Carey <marylou at backuptelecom.com> wrote:
>
> I am doing some research for an article so I wanted to ask all of you some questions about STIR/SHAKEN and the upcoming implementation in late September when traffic will start getting blocked. I personally envision the first few months will be a nightmare! Ironically this will all hit just as elections are about to take place......how convenient! When the industry missed so many steps on the implementation phase, there's sure to be things they've missed in this phase so let's think ahead so we can address as many problems as we can before they happen! I specifically want to focus on the effect the changes are having and will have on end user customers. Not only residential and small business customers, but enterprise customers such as schools, hospitals, banks, political organizations, and other industries that use call centers. Please respond to the questions below and let me know your thoughts.
>
> 1. Have you seen any changes in the industry since the June 30th implementation date. I have witnessed a few odd routing issues that have never happened in the past. I'm not sure if they are a fluke or a trend. Have you experienced anything out of the ordinary?
I've seen some invalid signatures, and largely reaching out has been successful in getting them fixed. No other issues, really.
> 2. If your network is partially TDM and partially VOIP, have you experienced any issues with either of them? What are your future concerns since STIR/SHAKEN does not work with TDM?
My concern is that some carriers will never switch away from TDM and I'll be forced to maintain these trunks forever, with a nonresponsive ILEC who doesn't want to be providing the service either.
> 3. My biggest complaint as a residential consumer is that caller ID no longer shows up like it did. Unless I have the number in my phone, I only see something along the lines of Scam Likely or a phone number with no caller ID. I find this quite irritating since it prevents me from determining if its a friend whose carrier hasn't implemented it yet or an actual scammer. Anyone else have complaints about what information is being passed?
... This has nothing to do with STIR/SHAKEN. CNAM is either dipped or passed in the From or P-Asserted-Identity field. You might want to reach out to your (cellular) carrier and see why you aren't getting caller id.
> 4. Are you getting more complaints from your customers about anything related to STIR/SHAKEN? What are the nature of the complaints? Is there a recurring theme?
They're mostly concerned about being flagged by reputation services. We help them reach out to all of them to register their activity. I'd love if the reputation services went away because STIR/SHAKEN was universally deployed and we could get accountability into the system and shut down bad actors.
> 5. What is your customer's impression of what a Robocall is? My son claims he's getting more SCAM calls than he was before but I'm not sure he understands what a Robocall is. He may consider any advertisement or donation request a robocall, but some things are allowed while others aren't. What are you doing to help your customers understand what's allowed and what's not allowed?
Not much we can do. I wish we could easily block political and fundraising calls. Our customers universally don't want them.
> 6. If you're hearing from customers about scam calls they are getting, are you reporting those calls to anyone? If so, who are you reporting them to?
If we get actionable data, we traceback to originating carrier and report. So far it's been dead air calls that are accidental misconfigurations of supposedly legitimate calling campaigns. The calls stopped at least.
> 6. Criminals always seem to be creative. Have you seen any new methods scammers are using to get around STIR/SHAKEN process?
Continuing to deal with carriers who are non-compliant.
> 7. One of my greatest concerns I have about the September implementation is that carriers will get no warning if/when they are going to be blocked. I haven't seen anything that states a terminating carrier or intermediate carrier has to give a warning muchless disclose that they will start blocking another carrier's traffic. Maybe there is a hotline to call if your traffic is being blocked unjustly, but I haven't heard of any. Have you? Normal routing issues are already a nightmare to deal with. Hopefully this will not make it worse or just another method for anti-competitive carriers to take out their competition!
Ultimately, the blocking will be implemented by next hop carriers, not companies 4 hops out closest to the end user. The question won't be "why did you ring this through to the end user", it will be "why did level 3 provide transit to this downstream consumer who isn't listed in the compliance database" so I'm sure carriers will be reaching out, or they themselves will be non-compliant.
The death penalty process has safeguards and notifications from the FCC. I'm camping and using a mifi suspended on a rope 30 feet up in a tree to catch a verizon EV-DO signal so I can't easily point them out, but the lines don't just go instantly dead without warning, there's a process.
> 8. The last question leads me to the next one. I know there are some carriers using their underlying carrier's certificate so they didn't register for the Robocall Mitigation Database. I didn't recommend this, but I heard through the grapevine some consultants / underlying carriers did. If those who didn't sign up for the Robocall Mitigation Database have legitimate traffic shut down, what will happen to all their legitimate customers? Will they be out of service until the ITG gets around to figuring it out? Has anyone heard of a plan to address the impact on consumers displaced by this?
I hope so. Maybe the threat of collateral damage will force people to do the right thing.
> 9. Has anyone heard of a centralized contact to deal with unjust blocking complaints? We all know nothing goes perfectly but I would think it will be important for everyone to know what number to call should they have problems BEFORE this change is implemented. Have any of you heard anything? I haven't!
If my calls were blocked by a carrier, i'd reach out to that carrier's contact in the robocall mitigation database, because if they weren't the person in charge of it, they'd know who was.
> 10. I tried to keep my list simple but I would love to hear your thoughts on anything I missed.
Personally, my fear is we'll deal with the garbage and call it good, and we'll have similar volumes of "legal" calls that anger people. PoliceOfficerOrg can stop calling my desk line twice a day. I've been assured their traffic is legitimate, but it remains ludicrously unwanted and comes from what must be easily dozens of unique source numbers so I can't just block it. What do they think they're accomplishing here? Do they not realize they're next against the wall with such hostile calling patterns?
-Paul
Not officially speaking for my employer, though they're known to share quite a few opinions of mine.
> Thanks for all your input,
>
> MARY LOU CAREY
> BackUP Telecom Consulting
> Office: 615-791-9969
> Cell: 615-796-1111
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Aug. 20, 2021
STIR/SHAKEN concerns
by brooks@firestormnetworks.net
"6. Criminals always seem to be creative. Have you seen any new methods
scammers are using to get around STIR/SHAKEN process?"
Not exactly criminal and not really "getting around" the process, but
I've seen a few calls across different networks I run that they've set
"Verified" as the CNAM for the number, so it *kind of* looks like it's
S/S validated if you're not paying that close of attention.? Of course,
it was a shady payday loan shop, not really a "scam" but not far from it
either IMO...
On 8/19/2021 7:22 PM, Mary Lou Carey wrote:
> I am doing some research for an article so I wanted to ask all of you
> some questions about STIR/SHAKEN and the upcoming implementation in
> late September when traffic will start getting blocked. I personally
> envision the first few months will be a nightmare! Ironically this
> will all hit just as elections are about to take place......how
> convenient! When the industry missed so many steps on the
> implementation phase, there's sure to be things they've missed in this
> phase so let's think ahead so we can address as many problems as we
> can before they happen! I specifically want to focus on the effect the
> changes are having and will have on end user customers. Not only
> residential and small business customers, but enterprise customers
> such as schools, hospitals, banks, political organizations, and other
> industries that use call centers. Please respond to the questions
> below and let me know your thoughts.
>
> 1. Have you seen any changes in the industry since the June 30th
> implementation date. I have witnessed a few odd routing issues that
> have never happened in the past. I'm not sure if they are a fluke or a
> trend. Have you experienced anything out of the ordinary?
>
> 2. If your network is partially TDM and partially VOIP, have you
> experienced any issues with either of them? What are your future
> concerns since STIR/SHAKEN does not work with TDM?
>
> 3. My biggest complaint as a residential consumer is that caller ID no
> longer shows up like it did. Unless I have the number in my phone, I
> only see something along the lines of Scam Likely or a phone number
> with no caller ID. I find this quite irritating since it prevents me
> from determining if its a friend whose carrier hasn't implemented it
> yet or an actual scammer. Anyone else have complaints about what
> information is being passed?
>
> 4. Are you getting more complaints from your customers about anything
> related to STIR/SHAKEN? What are the nature of the complaints? Is
> there a recurring theme?
>
> 5. What is your customer's impression of what a Robocall is? My son
> claims he's getting more SCAM calls than he was before but I'm not
> sure he understands what a Robocall is. He may consider any
> advertisement or donation request a robocall, but some things are
> allowed while others aren't. What are you doing to help your customers
> understand what's allowed and what's not allowed?
>
> 6. If you're hearing from customers about scam calls they are getting,
> are you reporting those calls to anyone? If so, who are you reporting
> them to?
>
> 6. Criminals always seem to be creative. Have you seen any new methods
> scammers are using to get around STIR/SHAKEN process?
>
> 7. One of my greatest concerns I have about the September
> implementation is that carriers will get no warning if/when they are
> going to be blocked. I haven't seen anything that states a terminating
> carrier or intermediate carrier has to give a warning muchless
> disclose that they will start blocking another carrier's traffic.
> Maybe there is a hotline to call if your traffic is being blocked
> unjustly, but I haven't heard of any. Have you? Normal routing issues
> are already a nightmare to deal with. Hopefully this will not make it
> worse or just another method for anti-competitive carriers to take out
> their competition!
>
> 8. The last question leads me to the next one. I know there are some
> carriers using their underlying carrier's certificate so they didn't
> register for the Robocall Mitigation Database. I didn't recommend
> this, but I heard through the grapevine some consultants / underlying
> carriers did. If those who didn't sign up for the Robocall Mitigation
> Database have legitimate traffic shut down, what will happen to all
> their legitimate customers? Will they be out of service until the ITG
> gets around to figuring it out? Has anyone heard of a plan to address
> the impact on consumers displaced by this?
>
> 9. Has anyone heard of a centralized contact to deal with unjust
> blocking complaints? We all know nothing goes perfectly but I would
> think it will be important for everyone to know what number to call
> should they have problems BEFORE this change is implemented. Have any
> of you heard anything? I haven't!
>
>
> 10. I tried to keep my list simple but I would love to hear your
> thoughts on anything I missed.
>
>
> Thanks for all your input,
>
> MARY LOU CAREY
> BackUP Telecom Consulting
> Office: 615-791-9969
> Cell: 615-796-1111
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Aug. 20, 2021
STIR/SHAKEN concerns
by marylou@backuptelecom.com
I am doing some research for an article so I wanted to ask all of you
some questions about STIR/SHAKEN and the upcoming implementation in late
September when traffic will start getting blocked. I personally envision
the first few months will be a nightmare! Ironically this will all hit
just as elections are about to take place......how convenient! When the
industry missed so many steps on the implementation phase, there's sure
to be things they've missed in this phase so let's think ahead so we can
address as many problems as we can before they happen! I specifically
want to focus on the effect the changes are having and will have on end
user customers. Not only residential and small business customers, but
enterprise customers such as schools, hospitals, banks, political
organizations, and other industries that use call centers. Please
respond to the questions below and let me know your thoughts.
1. Have you seen any changes in the industry since the June 30th
implementation date. I have witnessed a few odd routing issues that have
never happened in the past. I'm not sure if they are a fluke or a trend.
Have you experienced anything out of the ordinary?
2. If your network is partially TDM and partially VOIP, have you
experienced any issues with either of them? What are your future
concerns since STIR/SHAKEN does not work with TDM?
3. My biggest complaint as a residential consumer is that caller ID no
longer shows up like it did. Unless I have the number in my phone, I
only see something along the lines of Scam Likely or a phone number with
no caller ID. I find this quite irritating since it prevents me from
determining if its a friend whose carrier hasn't implemented it yet or
an actual scammer. Anyone else have complaints about what information is
being passed?
4. Are you getting more complaints from your customers about anything
related to STIR/SHAKEN? What are the nature of the complaints? Is there
a recurring theme?
5. What is your customer's impression of what a Robocall is? My son
claims he's getting more SCAM calls than he was before but I'm not sure
he understands what a Robocall is. He may consider any advertisement or
donation request a robocall, but some things are allowed while others
aren't. What are you doing to help your customers understand what's
allowed and what's not allowed?
6. If you're hearing from customers about scam calls they are getting,
are you reporting those calls to anyone? If so, who are you reporting
them to?
6. Criminals always seem to be creative. Have you seen any new methods
scammers are using to get around STIR/SHAKEN process?
7. One of my greatest concerns I have about the September implementation
is that carriers will get no warning if/when they are going to be
blocked. I haven't seen anything that states a terminating carrier or
intermediate carrier has to give a warning muchless disclose that they
will start blocking another carrier's traffic. Maybe there is a hotline
to call if your traffic is being blocked unjustly, but I haven't heard
of any. Have you? Normal routing issues are already a nightmare to deal
with. Hopefully this will not make it worse or just another method for
anti-competitive carriers to take out their competition!
8. The last question leads me to the next one. I know there are some
carriers using their underlying carrier's certificate so they didn't
register for the Robocall Mitigation Database. I didn't recommend this,
but I heard through the grapevine some consultants / underlying carriers
did. If those who didn't sign up for the Robocall Mitigation Database
have legitimate traffic shut down, what will happen to all their
legitimate customers? Will they be out of service until the ITG gets
around to figuring it out? Has anyone heard of a plan to address the
impact on consumers displaced by this?
9. Has anyone heard of a centralized contact to deal with unjust
blocking complaints? We all know nothing goes perfectly but I would
think it will be important for everyone to know what number to call
should they have problems BEFORE this change is implemented. Have any of
you heard anything? I haven't!
10. I tried to keep my list simple but I would love to hear your
thoughts on anything I missed.
Thanks for all your input,
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
Aug. 20, 2021