<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I concur and was just about to respond with the same counter-argument. I read this paragraph, and I still do not come away with an understanding that one is required to disclose other carriers <i><u>qua</u></i><u> carriers</u> that you peer with in your RMD filing.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Now, if you happen to only peer with a single carrier who is also providing you with a turn-key, all-in-one solution (they do all of your origination, termination, they host your S/S cert, they sign your term calls for you using your cert on your behalf [also known as STI-AS], maybe they are even your S/S CA that you obtained your cert from in the first place, AND they do call analytics & run an STI-VS for you on your origination traffic), then sure, in that case I can see the potential confidentiality weakness and the objection.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>On the other hand, since a VoIP provider only technically needs to name the vendors whose products (whether in the cloud or hosted on prem) they use to implement their robocall mitigation strategy, one cannot necessarily deduce from such a list whether that vendor is doing more for the VoIP provider than just the analytics part. Though admittedly a smart enough cookie who knows the carrier landscape in the U.S. could probably take a glance at such a list and make a pretty good guess.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-- Nathan<o:p></o:p></span></p><p class=MsoNormal><a name="_MailEndCompose"><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></a></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Jeff Bilyk [mailto:jbilyk@gmail.com] <br><b>Sent:</b> Thursday, December 12, 2024 15:53<br><b>To:</b> Mary Lou Carey<br><b>Cc:</b> Nathan Anderson; Voiceops<br><b>Subject:</b> Re: [VoiceOps] FCC RMD Naughty List<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>To be clear, I am not for or against the policies, I am just stating my understanding, namely: the requirement highlighted in the document you attached only mandates disclosure of 3rd party vendors used for analytics. I do not believe that sentence requires disclosure of upstreams used simply for voice traffic, <o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Jeff<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Thu, Dec 12, 2024, 6:26 PM Mary Lou Carey <<a href="mailto:marylou@backuptelecom.com">marylou@backuptelecom.com</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>How is it fair that if you use your upstream carrier for analytics that you have to list their name? The FCC has no business asking that. Especially when they don't force everyone who uses a separate analytic provider to list their upstream vendor's name? I have no problem with explaining the processes used, but asking for any vendor name is just not appropriate. <o:p></o:p></span></p><div><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>MARY LOU CAREY <br>BackUP Telecom Consulting <br>Office: 615-791-9969 <br>Cell: 615-796-1111<o:p></o:p></span></p></div><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>On 2024-12-12 05:15 PM, Jeff Bilyk wrote:<o:p></o:p></span></p><blockquote style='border:none;border-left:solid #1010FF 1.0pt;padding:0in 0in 0in 5.0pt;margin-left:0in;margin-right:0in'><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Perhaps I'm misunderstanding the verbiage, but that appears to relate only to vendors of call analytics 3rd parties, and not all upstreams?<o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>On Thu, Dec 12, 2024, 6:03 PM Mary Lou Carey via VoiceOps <<a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a>> wrote:<o:p></o:p></span></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>See the attached document. I highlighted the verbiage that states you must provide the names of your 3rd party vendors. A lot of companies have their upstream providers sign their calls and do their analytics for them.<o:p></o:p></span></p><div><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>MARY LOU CAREY <br>BackUP Telecom Consulting <br>Office: 615-791-9969 <br>Cell: 615-796-1111<o:p></o:p></span></p></div><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>On 2024-12-11 07:23 PM, Nathan Anderson via VoiceOps wrote:<o:p></o:p></span></p><blockquote style='border:none;border-left:solid #1010FF 1.0pt;padding:0in 0in 0in 5.0pt;margin-left:0in;margin-right:0in'><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I agree with your stance on this, assuming this is in fact a requirement. However...I must be dense, because I have now skimmed over the Sixth, Seventh, and Eighth "Caller ID Authentication Report and Orders", the "Improving the Effectiveness of the Robocall Mitigation Database" docket, the updated RMD deadlines and compliance info in DA 24-73 posted in January, and I re-read paragraph II.3 of the so-called "naughty list" document that kick-started this thread. And I can find zero mention anywhere that supplying a detailed and accurate itemized list of your upstreams is any sort of requirement in one's RMD filing. There seems to be plenty of talk about having "<em><u><span style='font-family:"Calibri","sans-serif"'>know</span></u></em> your upstreams" procedures, but that is not defined as <em><u><span style='font-family:"Calibri","sans-serif"'>disclosing</span></u></em> your upstreams.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>So what am I missing? I'm sure I am just ignorant about where I should be looking ("I'm a <s>doctor</s>engineer, not a lawyer, dammit!"), but this is a rather well-hidden requirement...</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-- Nathan</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a name="m_-2974809383567822184_m_318354617910076"></a><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><strong><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></strong><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Mary Lou Carey [mailto:<a href="mailto:marylou@backuptelecom.com" target="_blank">marylou@backuptelecom.com</a>] <br><strong><span style='font-family:"Tahoma","sans-serif"'>Sent:</span></strong> Wednesday, December 11, 2024 09:09<br><strong><span style='font-family:"Tahoma","sans-serif"'>To:</span></strong> Nathan Anderson<br><strong><span style='font-family:"Tahoma","sans-serif"'>Cc:</span></strong> Voiceops<br><strong><span style='font-family:"Tahoma","sans-serif"'>Subject:</span></strong> Re: [VoiceOps] FCC RMD Naughty List</span><o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>The requirement to disclose who your underlying carriers and additional contact information were just added THIS YEAR. If you're up to date on everything else, you might not have made the list because there were so many less complaint than you, I wouldn't take that as a sign that the FCC won't ever contact you about missing information.<o:p></o:p></span></p><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>I'm a consultant so I'm exposed to a lot more problems than one company may run into. I personally spoke with the FCC and FBI about the scamming situation because someone approached us for help when they realized someone had contacted one of their upstream carriers and was impersonating them. The FCC and FBI had no answers......I'm the one that made the connection between the information scammers got and where they could have gotten it from.<o:p></o:p></span></p><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <o:p></o:p></span></p><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>I was helping carriers with STIR/SHAKEN compliance long before the RMD was required. The FCC came up with it as a work around because not every carrier could qualify for a STIR/SHAKEN certificate under the original requirements. (The original requirement the RMD replaced was having access to numbering resources. As in NXXs - not DIDs). <o:p></o:p></span></p><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>In my opinion what started out as a method to identify all the players in the industry has turned into an information grab that should not be happening. Not only because it would be a nightmare to keep the upstream carrier list updated, but because it creates way too much temptation for fraudsters and the anti-competitive to abuse it. <o:p></o:p></span></p><div><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>MARY LOU CAREY <br>BackUP Telecom Consulting <br>Office: 615-791-9969 <br>Cell: 615-796-1111<o:p></o:p></span></p></div><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <o:p></o:p></span></p><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>On 2024-12-10 08:09 PM, Nathan Anderson via VoiceOps wrote:<o:p></o:p></span></p><blockquote style='border:none;border-left:solid #1010FF 1.0pt;padding:0in 0in 0in 5.0pt;margin-left:0in;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Wait, say what now? I'm not even sure I understand how that kind of hijacking is possible. You'd have to be able to deduce who that provider's underlying carriers are before you could attempt to engage in that kind of social engineering with them, and as an IPES, there's nowhere either in our 499 filings or in the RMD filing where we are required to disclose that, either publicly or privately/redacted. (Unless I'm missing something? We have never disclosed that in any FCC filings, and yet we didn't get added to this "naughty" list. Furthermore, a read through of the required information listed in this notice under II.3 absolutely does not say anywhere that you are required to itemize who your specific upstreams are.) I suppose you could voluntarily disclose it in your RMD plan write-up, but...why would you, as that just unnecessarily ties your hands and results in a bunch of self-inflicted busy work (if you're going to list it, then you either have to maintain that list, avoid bringing up new or tearing down old SIP trunks with various underlying carriers, or risk having the disclosure become "stale").</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Also, on a different but related note, this whole incomplete-RMD-filing issue is a problem that the FCC kinda/sorta created themselves, and then decided shirk their responsibility for doing so and saddle all of us with the downstream consequences and threats. Just to remind everybody of the history here, this database as originally conceived by the brilliant minds in Washington required that filers EITHER certified themselves as being wholly S/S compliant, OR if not, then they had to supply a written mitigation plan. If you selected the "I am 100% S/S compliant" checkbox, it would NOT allow you to upload a document attachment with any kind of written plan. And if you first filed as only partially compliant or not-yet-compliant, and added such a document/attachment to your filing, and then after finishing your S/S implementation you went back and UPDATED your filing to reflect your new compliance, the system would DELETE your previous attachment from your filing, and not give you any option to submit a new one. If you filed as 100% compliant, you could not add an attachment, PERIOD. 100% compliance and document attachments were <u>mutually exclusive</u>.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Then one day they decided that maybe that was a bad idea, and required everybody who was 100% complaint to drop everything & go back and add written mitigation plans to their filings.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>So far in the (admittedly few) minutes I've taken to check out a handful of companies on this "naughty" list, virtually all of them are in the boat of having checked the "100% compliant" checkbox, but not having gone back after the rule change to submit a written RM plan document attachment to their filing.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-- Nathan</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><strong><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></strong><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> VoiceOps [<a href="mailto:voiceops-bounces@voiceops.org" target="_blank">mailto:voiceops-bounces@voiceops.org</a>] <strong><span style='font-family:"Tahoma","sans-serif"'>On Behalf Of </span></strong>Mary Lou Carey via VoiceOps<br><strong><span style='font-family:"Tahoma","sans-serif"'>Sent:</span></strong> Tuesday, December 10, 2024 14:08<br><strong><span style='font-family:"Tahoma","sans-serif"'>To:</span></strong> <a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a><br><strong><span style='font-family:"Tahoma","sans-serif"'>Subject:</span></strong> Re: [VoiceOps] FCC RMD Naughty List</span><o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>The requirements for RMD changed and you now need to add a lot more information. You only have 14 days to respond to the FCC, but MAKE SURE YOU FILE YOUR 499 CONFIDENTIALLY! We have already learned of incidents where scammers got ahold of company information and attempted to get the company's underlying carriers to change the IP addresses for their SIP trunks so they could hijack their network. We've brought this to the attention of the FBI and FCC, but the FCC's only offer was to file them confidentially. I personally think they're asking for way too much information and stupid to allow anyone's information to be listed on a public site, but until they fix the problem its up to carriers themselves to make sure their information is secure.<o:p></o:p></span></p><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Ashley (with Equitel Compliance) and I (BackUP Telecom can help anyone that needs to update their RMDs or get STIR/SHAKEN certified. <o:p></o:p></span></p><div><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>MARY LOU CAREY <br>BackUP Telecom Consulting <br>Office: 615-791-9969 <br>Cell: 615-796-1111<o:p></o:p></span></p></div><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <o:p></o:p></span></p><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>On 2024-12-10 03:42 PM, Dave Russo via VoiceOps wrote:<o:p></o:p></span></p><blockquote style='border:none;border-left:solid #1010FF 1.0pt;padding:0in 0in 0in 5.0pt;margin-left:0in;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Here is the FCC order & list mentioned: <a href="https://docs.fcc.gov/public/attachments/DA-24-1235A1.pdf" target="_blank">https://docs.fcc.gov/public/attachments/DA-24-1235A1.pdf</a></span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Also somewhat related, I'm curious how some companies that claim to be STIR/SHAKEN compliant and are listed on iconectiv's authorized provider list get away with not being fully FCC compliant?</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>For example when we were looking for a new provider it came to my attention that Atheral is 5 years behind on its FCC 499 filings... Looks like it last filed in 2019: <a href="https://apps.fcc.gov/cgb/form499/499detail.cfm?FilerNum=832820" target="_blank">https://apps.fcc.gov/cgb/form499/499detail.cfm?FilerNum=832820</a></span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Does this mean it can get shut down any time the FCC decides to do that? Will resellers that use them be at risk of losing service or subject to some FCC action themselves?</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>-dr</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>On Tue, Dec 10, 2024, at 2:17 PM, Mike Hammett via VoiceOps wrote:</span><o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt' id="m_-2974809383567822184m_3183546179100767809qt"><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>How many of you are on the Robocall Mitigation Database naughty list that the FCC just sent out?</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'> </span><o:p></o:p></p></div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>It'd be nice if they told you *WHY* your filing was deficient. Instead, they just generically list broad categories that you may or may not fit into.</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'> </span><o:p></o:p></p></div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>-----</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>Mike Hammett</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>Intelligent Computing Solutions</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><a href="http://www.ics-il.com" target="_blank">http://www.ics-il.com</a></span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>Midwest Internet Exchange</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><a href="http://www.midwest-ix.com" target="_blank">http://www.midwest-ix.com</a></span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'> </span><o:p></o:p></p></div></div></div></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>_______________________________________________</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>VoiceOps mailing list</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a></span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a></span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> </span><o:p></o:p></p></div></blockquote><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> </span><o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> </span><o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Courier New"'>_______________________________________________<br>VoiceOps mailing list<br><a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br><a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a></span><o:p></o:p></p></div></blockquote></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> </span><o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Courier New"'>_______________________________________________<br>VoiceOps mailing list<br><a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br><a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a></span><o:p></o:p></p></div></blockquote></div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>_______________________________________________<br>VoiceOps mailing list<br><a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br><a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><o:p></o:p></span></p></div></blockquote></div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>_______________________________________________<br>VoiceOps mailing list<br><a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br><a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><o:p></o:p></span></p></blockquote></div></blockquote></div></blockquote></div></div></body></html>><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>I was helping carriers with STIR/SHAKEN compliance long before the RMD was required. The FCC came up with it as a work around because not every carrier could qualify for a STIR/SHAKEN certificate under the original requirements. (The original requirement the RMD replaced was having access to numbering resources. As in NXXs - not DIDs). <o:p></o:p></span></p><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>In my opinion what started out as a method to identify all the players in the industry has turned into an information grab that should not be happening. Not only because it would be a nightmare to keep the upstream carrier list updated, but because it creates way too much temptation for fraudsters and the anti-competitive to abuse it. <o:p></o:p></span></p><div><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>MARY LOU CAREY <br>BackUP Telecom Consulting <br>Office: 615-791-9969 <br>Cell: 615-796-1111<o:p></o:p></span></p></div><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <o:p></o:p></span></p><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>On 2024-12-10 08:09 PM, Nathan Anderson via VoiceOps wrote:<o:p></o:p></span></p><blockquote style='border:none;border-left:solid #1010FF 1.0pt;padding:0in 0in 0in 5.0pt;margin-left:0in;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Wait, say what now? I'm not even sure I understand how that kind of hijacking is possible. You'd have to be able to deduce who that provider's underlying carriers are before you could attempt to engage in that kind of social engineering with them, and as an IPES, there's nowhere either in our 499 filings or in the RMD filing where we are required to disclose that, either publicly or privately/redacted. (Unless I'm missing something? We have never disclosed that in any FCC filings, and yet we didn't get added to this "naughty" list. Furthermore, a read through of the required information listed in this notice under II.3 absolutely does not say anywhere that you are required to itemize who your specific upstreams are.) I suppose you could voluntarily disclose it in your RMD plan write-up, but...why would you, as that just unnecessarily ties your hands and results in a bunch of self-inflicted busy work (if you're going to list it, then you either have to maintain that list, avoid bringing up new or tearing down old SIP trunks with various underlying carriers, or risk having the disclosure become "stale").</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Also, on a different but related note, this whole incomplete-RMD-filing issue is a problem that the FCC kinda/sorta created themselves, and then decided shirk their responsibility for doing so and saddle all of us with the downstream consequences and threats. Just to remind everybody of the history here, this database as originally conceived by the brilliant minds in Washington required that filers EITHER certified themselves as being wholly S/S compliant, OR if not, then they had to supply a written mitigation plan. If you selected the "I am 100% S/S compliant" checkbox, it would NOT allow you to upload a document attachment with any kind of written plan. And if you first filed as only partially compliant or not-yet-compliant, and added such a document/attachment to your filing, and then after finishing your S/S implementation you went back and UPDATED your filing to reflect your new compliance, the system would DELETE your previous attachment from your filing, and not give you any option to submit a new one. If you filed as 100% compliant, you could not add an attachment, PERIOD. 100% compliance and document attachments were <u>mutually exclusive</u>.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Then one day they decided that maybe that was a bad idea, and required everybody who was 100% complaint to drop everything & go back and add written mitigation plans to their filings.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>So far in the (admittedly few) minutes I've taken to check out a handful of companies on this "naughty" list, virtually all of them are in the boat of having checked the "100% compliant" checkbox, but not having gone back after the rule change to submit a written RM plan document attachment to their filing.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-- Nathan</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-outline-level:1'><strong><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></strong><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> VoiceOps [<a href="mailto:voiceops-bounces@voiceops.org" target="_blank">mailto:voiceops-bounces@voiceops.org</a>] <strong><span style='font-family:"Tahoma","sans-serif"'>On Behalf Of </span></strong>Mary Lou Carey via VoiceOps<br><strong><span style='font-family:"Tahoma","sans-serif"'>Sent:</span></strong> Tuesday, December 10, 2024 14:08<br><strong><span style='font-family:"Tahoma","sans-serif"'>To:</span></strong> <a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a><br><strong><span style='font-family:"Tahoma","sans-serif"'>Subject:</span></strong> Re: [VoiceOps] FCC RMD Naughty List</span><o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>The requirements for RMD changed and you now need to add a lot more information. You only have 14 days to respond to the FCC, but MAKE SURE YOU FILE YOUR 499 CONFIDENTIALLY! We have already learned of incidents where scammers got ahold of company information and attempted to get the company's underlying carriers to change the IP addresses for their SIP trunks so they could hijack their network. We've brought this to the attention of the FBI and FCC, but the FCC's only offer was to file them confidentially. I personally think they're asking for way too much information and stupid to allow anyone's information to be listed on a public site, but until they fix the problem its up to carriers themselves to make sure their information is secure.<o:p></o:p></span></p><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Ashley (with Equitel Compliance) and I (BackUP Telecom can help anyone that needs to update their RMDs or get STIR/SHAKEN certified. <o:p></o:p></span></p><div><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>MARY LOU CAREY <br>BackUP Telecom Consulting <br>Office: 615-791-9969 <br>Cell: 615-796-1111<o:p></o:p></span></p></div><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <o:p></o:p></span></p><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>On 2024-12-10 03:42 PM, Dave Russo via VoiceOps wrote:<o:p></o:p></span></p><blockquote style='border:none;border-left:solid #1010FF 1.0pt;padding:0in 0in 0in 5.0pt;margin-left:0in;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Here is the FCC order & list mentioned: <a href="https://docs.fcc.gov/public/attachments/DA-24-1235A1.pdf" target="_blank">https://docs.fcc.gov/public/attachments/DA-24-1235A1.pdf</a></span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Also somewhat related, I'm curious how some companies that claim to be STIR/SHAKEN compliant and are listed on iconectiv's authorized provider list get away with not being fully FCC compliant?</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>For example when we were looking for a new provider it came to my attention that Atheral is 5 years behind on its FCC 499 filings... Looks like it last filed in 2019: <a href="https://apps.fcc.gov/cgb/form499/499detail.cfm?FilerNum=832820" target="_blank">https://apps.fcc.gov/cgb/form499/499detail.cfm?FilerNum=832820</a></span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Does this mean it can get shut down any time the FCC decides to do that? Will resellers that use them be at risk of losing service or subject to some FCC action themselves?</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>-dr</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>On Tue, Dec 10, 2024, at 2:17 PM, Mike Hammett via VoiceOps wrote:</span><o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt' id="m_-2974809383567822184m_3183546179100767809qt"><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>How many of you are on the Robocall Mitigation Database naughty list that the FCC just sent out?</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'> </span><o:p></o:p></p></div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>It'd be nice if they told you *WHY* your filing was deficient. Instead, they just generically list broad categories that you may or may not fit into.</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'> </span><o:p></o:p></p></div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>-----</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>Mike Hammett</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>Intelligent Computing Solutions</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><a href="http://www.ics-il.com" target="_blank">http://www.ics-il.com</a></span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>Midwest Internet Exchange</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><a href="http://www.midwest-ix.com" target="_blank">http://www.midwest-ix.com</a></span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'> </span><o:p></o:p></p></div></div></div></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>_______________________________________________</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>VoiceOps mailing list</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a></span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a></span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> </span><o:p></o:p></p></div></blockquote><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> </span><o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> </span><o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Courier New"'>_______________________________________________<br>VoiceOps mailing list<br><a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br><a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a></span><o:p></o:p></p></div></blockquote></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> </span><o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Courier New"'>_______________________________________________<br>VoiceOps mailing list<br><a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br><a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a></span><o:p></o:p></p></div></blockquote></div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-font-family:"Times New Roman"'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New";mso-fareast-font-family:"Times New Roman"'>_______________________________________________<br>VoiceOps mailing list<br><a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br><a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><o:p></o:p></span></p></div></blockquote></div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-font-family:"Times New Roman"'>_______________________________________________<br>VoiceOps mailing list<br><a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br><a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><o:p></o:p></span></p></blockquote></div></blockquote></div></blockquote></div></div></body></html>