<html 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=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Well, this is all new to me so I apologize for misleading or incorrect information. I’m going through the CSP process now and it has been pretty quick/easy. I’ve registered one brand ($4) and one campaign ($2/month).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’m using Inteliquent as my interconnect, they charge fees per SMS/MMS. I don’t believe I will be receiving invoices from individual carriers (ala CABS)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Peter Beckman <beckman@angryox.com><br>
<b>Date: </b>Wednesday, May 4, 2022 at 7:08 PM<br>
<b>To: </b>Matthew Crocker <matthew@corp.crocker.com><br>
<b>Cc: </b>VoiceOps <voiceops@voiceops.org><br>
<b>Subject: </b>Re: [VoiceOps] Carriers / TCR requiring NetNumber ID for SMS, even P2P<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal">CAUTION: This email originated from outside of Crocker. Do not click links or open attachments unless you recognize the sender and know the content is safe.<br>
<br>
<br>
Your statement is misleading, borderline wrong.<br>
<br>
It's $200 just to sign up with TCR.<br>
<br>
Then it is a variable fee based on how many DIDs you are attempting to<br>
register.<br>
<br>
Low Volume: $2 per MONTH per DID (non-time-sensitive)<br>
<br>
Undisclosed how much it costs if NOT Low Volume.<br>
<br>
Then carriers can add on their own per-DID and per-campaign fees.<br>
<br>
And this is ONLY for 10DLC A2P SMS -- BUSINESS or BULK SMS, not P2P,<br>
person-to-person SMS.<br>
<br>
Look at the pricing Commio is putting out regarding T-Mobile:<br>
<a href="https://www.thinq.com/blog/t-mobile-10dlc-text-messaging-fee-changes/">https://www.thinq.com/blog/t-mobile-10dlc-text-messaging-fee-changes/</a><br>
<br>
- $50 Campaign Service Activation Fee<br>
- $50 Campaign Migration Fee<br>
- $2,000 one-time NNID Registration<br>
- $10,000 pass-through fee if T-Mobile doesn't like your SMS<br>
- $1,000 pass-through fee if they think you're evading the rules<br>
<br>
Bandwidth increasing per-SMS fees too:<br>
<a href="https://support.bandwidth.com/hc/en-us/articles/1500002422242-10DLC-Overview">https://support.bandwidth.com/hc/en-us/articles/1500002422242-10DLC-Overview</a><br>
<br>
Can you imagine your cost basis as a small carrier, to increase your direct<br>
costs of a DID by 10x or more, just to allow your customer to send and<br>
receive SMS messages?<br>
<br>
<br>
<br>
Please note:<br>
I am discussing P2P -- PERSON-TO-PERSON -- NOT A2P, BUSINESS-TO-PERSON<br>
<br>
See the CTIA Best Practices for the difference between the content of the<br>
two.<br>
<br>
Beckman<br>
<br>
On Wed, 4 May 2022, Matthew Crocker wrote:<br>
<br>
><br>
> <a href="http://www.campaignregistry.com%3chttp:/www.campaignregistry.com%3e">www.campaignregistry.com<http://www.campaignregistry.com></a> The process is quick,painless and a campaign costs a small one time fee ($4 I think)<br>
><br>
><br>
> From: VoiceOps <voiceops-bounces@voiceops.org> on behalf of Peter Beckman <beckman@angryox.com><br>
> Date: Wednesday, May 4, 2022 at 5:09 PM<br>
> To: VoiceOps <voiceops@voiceops.org><br>
> Subject: [VoiceOps] Carriers / TCR requiring NetNumber ID for SMS, even P2P<br>
> CAUTION: This email originated from outside of Crocker. Do not click links or open attachments unless you recognize the sender and know the content is safe.<br>
><br>
><br>
> I'm hearing from one of my carriers that in order to continue sending P2P<br>
> (NOT A2P) SMS from our DIDs, my $dayjob needs to purchase and maintain a<br>
> NetNumber ID to use as the SPID for SMS.<br>
><br>
> I'm also hearing that ALT-SPIDs are being discontinued.<br>
><br>
> Does anyone else know about this change, who is driving it, and why? Anyone<br>
> want to share costs involved in getting and maintaining an NNID for this<br>
> purpose?<br>
><br>
> This feels more like pay-to-play than a solution to reduce unwanted SMS.<br>
><br>
> Beckman<br>
> ---------------------------------------------------------------------------<br>
> Peter Beckman Internet Guy<br>
> beckman@angryox.com <a href="https://www.angryox.com/">
https://www.angryox.com/</a><br>
> ---------------------------------------------------------------------------<br>
> _______________________________________________<br>
> VoiceOps mailing list<br>
> VoiceOps@voiceops.org<br>
> <a href="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
><br>
<br>
---------------------------------------------------------------------------<br>
Peter Beckman Internet Guy<br>
beckman@angryox.com <a href="https://www.angryox.com/">
https://www.angryox.com/</a><br>
---------------------------------------------------------------------------<o:p></o:p></p>
</div>
</div>
</body>
</html>