<div dir="ltr"><div>I second this request for clarification on the state of messaging today. I'm specifically interested in P2P binds for true consumer traffic and keeping my customers away from the campaign registry.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Feb 8, 2023 at 3:25 PM Peter Beckman via VoiceOps <<a href="mailto:voiceops@voiceops.org">voiceops@voiceops.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I built and ran operations for a Ringtone company back in 2004-2005, so I<br>
have some experience with SMSCs, DLRs, and how SMS generally works.<br>
<br>
However, over the years, there seems to be a lot of different players in<br>
the game, some aggregators, some called something else, and honestly I<br>
cannot seem to find any good, well-written, recent information on how and<br>
where SMS messages flow in the US.<br>
<br>
The players I am talking about are NOT the Tier 0 carriers (e.g. Verizon<br>
Wireless, T-Mobile, AT&T, US Mobile), and not the CLECs/ILECs we all might work<br>
with (Level3, Bandwidth, Inteliquent/Sinch).<br>
<br>
I'm looking for what companies/vendors might touch SMS messaging that runs<br>
between the 3 major US Wireless networks (I believe THEY are all<br>
interconnected directly, but maybe not) and all the other SMS-enabled DIDs<br>
and Short Codes that are outside of those wireless networks.<br>
<br>
Here are players I know about, but I do not know what they do<br>
and what other carriers use these players and why:<br>
<br>
- NetNumber<br>
- Syniverse<br>
- Neustar<br>
- SAP<br>
- Sybase<br>
- TNS<br>
<br>
Then we have the confusing SMS routing side: ESPID, AltSPID, VSPID, NetNumberID.<br>
<br>
Back in 2015 a post to VoiceOps stated:<br>
<br>
"Syniverse and SAP are working with NeuStar to make use of the AltSPID field<br>
in NPAC for SMS routing as an alternative to NetNumber. This is expected by<br>
the end of the year. If you have wireline number block assignments which<br>
are SMS enabled, you may be facing a monthly per-number fee from NetNumber<br>
come January 1st. I suggest anyone in this position contact their SMS<br>
peering hub and the NPAC Helpdesk for more information."<br>
<br>
<a href="https://puck.nether.net/pipermail/voiceops/2015-November/006074.html" rel="noreferrer" target="_blank">https://puck.nether.net/pipermail/voiceops/2015-November/006074.html</a><br>
<br>
I run a few SMSCs and pass messages through them directly to my carriers.<br>
With one carrier I use a shared NNID, and with another I have a<br>
dedicated/hosted NNID.<br>
<br>
Here are my questions:<br>
<br>
- How would one find out through which Vendors an SMS passes, in order<br>
to troubleshoot deliverability or receivability issues?<br>
- Does anyone what vendor/aggregator that Verizon Wireless uses?<br>
- Are the major US wireless carriers interconnected directly, or<br>
through yet another vendor?<br>
- Has NetNumberID won out over AltSPID?<br>
- Why would long code SMS messages NOT generate DLRs from the receiving<br>
carrier through these SMS aggregators/vendors?<br>
<br>
I acknowledge my limited understanding of all the SMS players and the<br>
technical functionality here. Any new knowledge is appreciated.<br>
<br>
Beckman<br>
---------------------------------------------------------------------------<br>
Peter Beckman Internet Guy<br>
<a href="mailto:beckman@angryox.com" target="_blank">beckman@angryox.com</a> <a href="https://www.angryox.com/" rel="noreferrer" target="_blank">https://www.angryox.com/</a><br>
---------------------------------------------------------------------------<br>
_______________________________________________<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" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</blockquote></div></div>