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
February 2023
- 23 participants
- 55 messages
Alarm panels and how they dial DTMF digits - pots migration from DMS to Metaswitch issue
by myaklin@firstlight.net
Hello All,
I guess I have an old school question for the list. The question is we are having trouble with alarm panels dialing and our gear collecting the DTMF digits properly. Only from a company ran by a single alarm panel guy who is not terribly helpful. At least 7 different sites are having the same problem on different copper pairs/T1s. Different gear. Etc...
It seems we are always migrating off old DMS switches. In this case a DMS 100 with your typical line drawers with cards in them for pots lines or GR303 groups. We are migrating to a Metaswitch using different types of connections. In this case GR303 for some and SIP for others. ADTRAN gear in this case. TA4303 and a TA5000. We have been a Metaswitch shop for quite a long time now.
Pretty vanilla stuff we rely on in many regions that has always "just worked" for legacy clients.
Metaswitch -> GR303 to a TA4303 -> drop T1 to a TA3000 -> build a T1 on our copper plant -> Smart jack -> TA750 at customer location -> customer fire alarm panel
Or...
Metaswitch -> SIP -> TA5k with RPOTS cards in SIP mode -> copper plant -> demarc -> customer fire alarm panel
What I am seeing is that the DMS was collecting the digits properly before the cutover. Yet our migrated to setup is having trouble. We see missing digits in most cases or other oddities. It does appear the alarm panels are dialing within DTMF specs. Duration of the DTMF is approx 95 ms. A DTMF signal separated by a 150-200 ms pause.
Any other type of customer is working flawlessly. 100s and 100s of pots line migrated with no complaints except a single guy who manages fire alarm panels of a few different types. "Contact id Edwards". " Contact id ES4 Kidde".
Naturally, a tech sent on site can dial out fine with his butt set. The copper pairs test fine. T1 is error free. Hardware has been swapped out. Moved to different fxs ports. You name it we probably tried it.
Does anyone have a suggestion what could be the cause for this? Something I am not aware of DMS wise when it came to fire alarm panels? Some change that can be adjusted in the fire panel configuration that might solve this? When we port/move the customer back to the DMS it just starts working again in the case of the TA5000. There is no going back for the GR303 subs which were moved all at once.
Any tips are welcome!
Thank you,
Matt
Feb. 13, 2023
Players in the US SMS Game / Market
by beckman@angryox.com
Hey Calvin --
Left you a VM today in hopes you would know more than I about this!
I applied / appealed to TCR for a P2P use case exception for our consumer
traffic. I implemented many/most of the CTIA Best Practices for P2P traffic
in code to automatically prevent a customer from signing up and using our
service to spam a few thousand people.
TCR approved our appeal finally in July 2021, though it took a few months.
But the thing that sucks is that there isn't really anything to it -- I
have an email from the CEO of TCR saying that our use case meets their P2P
requirements, and to "show the email" to our carriers as proof.
Very weird.
But it works.
We have P2P binds with Bandwidth, and Inteliquent required us to pay $750
for our own dedicated P2P NetNumber ID, but now we have it and all SMS is
routed through it, at least for IQ DIDs.
We have not talked to Bandwidth about routing ALL of our SMS through our
P2P NNID, but we might, as currently we are sharing the Bandwidth P2P NNID
with who knows how many other customers, and if they get blocked, we get
blocked.
P2P is NOT treated as "high priority" by either carrier; we had a recent
issue where Outbound BW DIDs could not reach VZW. I'm still investigating
what entity broke it and why and how and hoping they fix it. I'll be adding
some monitoring around it soon so I know when it breaks before our
customers.
Hope that helps.
Beckman
+1 571 527 2972 if you wanna chat about it
On Wed, 8 Feb 2023, Calvin E. via VoiceOps wrote:
> 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.
>
> On Wed, Feb 8, 2023 at 3:25 PM Peter Beckman via VoiceOps <
> voiceops at voiceops.org> wrote:
>
>> I built and ran operations for a Ringtone company back in 2004-2005, so I
>> have some experience with SMSCs, DLRs, and how SMS generally works.
>>
>> However, over the years, there seems to be a lot of different players in
>> the game, some aggregators, some called something else, and honestly I
>> cannot seem to find any good, well-written, recent information on how and
>> where SMS messages flow in the US.
>>
>> The players I am talking about are NOT the Tier 0 carriers (e.g. Verizon
>> Wireless, T-Mobile, AT&T, US Mobile), and not the CLECs/ILECs we all might
>> work
>> with (Level3, Bandwidth, Inteliquent/Sinch).
>>
>> I'm looking for what companies/vendors might touch SMS messaging that runs
>> between the 3 major US Wireless networks (I believe THEY are all
>> interconnected directly, but maybe not) and all the other SMS-enabled DIDs
>> and Short Codes that are outside of those wireless networks.
>>
>> Here are players I know about, but I do not know what they do
>> and what other carriers use these players and why:
>>
>> - NetNumber
>> - Syniverse
>> - Neustar
>> - SAP
>> - Sybase
>> - TNS
>>
>> Then we have the confusing SMS routing side: ESPID, AltSPID, VSPID,
>> NetNumberID.
>>
>> Back in 2015 a post to VoiceOps stated:
>>
>> "Syniverse and SAP are working with NeuStar to make use of the
>> AltSPID field
>> in NPAC for SMS routing as an alternative to NetNumber. This is
>> expected by
>> the end of the year. If you have wireline number block assignments
>> which
>> are SMS enabled, you may be facing a monthly per-number fee from
>> NetNumber
>> come January 1st. I suggest anyone in this position contact their
>> SMS
>> peering hub and the NPAC Helpdesk for more information."
>>
>> https://puck.nether.net/pipermail/voiceops/2015-November/006074.html
>>
>> I run a few SMSCs and pass messages through them directly to my carriers.
>> With one carrier I use a shared NNID, and with another I have a
>> dedicated/hosted NNID.
>>
>> Here are my questions:
>>
>> - How would one find out through which Vendors an SMS passes, in order
>> to troubleshoot deliverability or receivability issues?
>> - Does anyone what vendor/aggregator that Verizon Wireless uses?
>> - Are the major US wireless carriers interconnected directly, or
>> through yet another vendor?
>> - Has NetNumberID won out over AltSPID?
>> - Why would long code SMS messages NOT generate DLRs from the
>> receiving
>> carrier through these SMS aggregators/vendors?
>>
>> I acknowledge my limited understanding of all the SMS players and the
>> technical functionality here. Any new knowledge is appreciated.
>>
>> Beckman
>> ---------------------------------------------------------------------------
>> Peter Beckman Internet Guy
>> beckman at angryox.com
>> https://www.angryox.com/
>> ---------------------------------------------------------------------------
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman at angryox.com https://www.angryox.com/
---------------------------------------------------------------------------
Feb. 9, 2023
Percentage of US Wireless Calls that fail to reach/ring phone?
by beckman@angryox.com
Is there any published studies on the number of incoming calls that are
placed to a US Wireless mobile number that fail to actually reach or ring
the phone?
Any studies that go through the most common reasons why that occurs?
I am curious about network prioritization, cell tower capacity
rules/management, and why, if a cellular device has a "good enough"
connection to a tower might the signal to the device that there is an
incoming call NOT be sent?
I have a lot of customers who get frustrated when there is a call we are
forwarding or making to them, and we reach their mobile carrier, but their
mobile device does not ring. They say "I'm looking right at it, and you say
you're calling it, but it isn't ringing!" As if the wireless network is
somehow under our control.
There's a lot of marketing about "network quality" and "network coverage"
but very little about dropped calls, or calls that fail to start and go
straight to Voicemail.
Beckman
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman at angryox.com https://www.angryox.com/
---------------------------------------------------------------------------
Feb. 9, 2023
Players in the US SMS Game / Market
by calvine@gmail.com
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.
On Wed, Feb 8, 2023 at 3:25 PM Peter Beckman via VoiceOps <
voiceops at voiceops.org> wrote:
> I built and ran operations for a Ringtone company back in 2004-2005, so I
> have some experience with SMSCs, DLRs, and how SMS generally works.
>
> However, over the years, there seems to be a lot of different players in
> the game, some aggregators, some called something else, and honestly I
> cannot seem to find any good, well-written, recent information on how and
> where SMS messages flow in the US.
>
> The players I am talking about are NOT the Tier 0 carriers (e.g. Verizon
> Wireless, T-Mobile, AT&T, US Mobile), and not the CLECs/ILECs we all might
> work
> with (Level3, Bandwidth, Inteliquent/Sinch).
>
> I'm looking for what companies/vendors might touch SMS messaging that runs
> between the 3 major US Wireless networks (I believe THEY are all
> interconnected directly, but maybe not) and all the other SMS-enabled DIDs
> and Short Codes that are outside of those wireless networks.
>
> Here are players I know about, but I do not know what they do
> and what other carriers use these players and why:
>
> - NetNumber
> - Syniverse
> - Neustar
> - SAP
> - Sybase
> - TNS
>
> Then we have the confusing SMS routing side: ESPID, AltSPID, VSPID,
> NetNumberID.
>
> Back in 2015 a post to VoiceOps stated:
>
> "Syniverse and SAP are working with NeuStar to make use of the
> AltSPID field
> in NPAC for SMS routing as an alternative to NetNumber. This is
> expected by
> the end of the year. If you have wireline number block assignments
> which
> are SMS enabled, you may be facing a monthly per-number fee from
> NetNumber
> come January 1st. I suggest anyone in this position contact their
> SMS
> peering hub and the NPAC Helpdesk for more information."
>
> https://puck.nether.net/pipermail/voiceops/2015-November/006074.html
>
> I run a few SMSCs and pass messages through them directly to my carriers.
> With one carrier I use a shared NNID, and with another I have a
> dedicated/hosted NNID.
>
> Here are my questions:
>
> - How would one find out through which Vendors an SMS passes, in order
> to troubleshoot deliverability or receivability issues?
> - Does anyone what vendor/aggregator that Verizon Wireless uses?
> - Are the major US wireless carriers interconnected directly, or
> through yet another vendor?
> - Has NetNumberID won out over AltSPID?
> - Why would long code SMS messages NOT generate DLRs from the
> receiving
> carrier through these SMS aggregators/vendors?
>
> I acknowledge my limited understanding of all the SMS players and the
> technical functionality here. Any new knowledge is appreciated.
>
> Beckman
> ---------------------------------------------------------------------------
> Peter Beckman Internet Guy
> beckman at angryox.com
> https://www.angryox.com/
> ---------------------------------------------------------------------------
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
Feb. 9, 2023
Players in the US SMS Game / Market
by beckman@angryox.com
I built and ran operations for a Ringtone company back in 2004-2005, so I
have some experience with SMSCs, DLRs, and how SMS generally works.
However, over the years, there seems to be a lot of different players in
the game, some aggregators, some called something else, and honestly I
cannot seem to find any good, well-written, recent information on how and
where SMS messages flow in the US.
The players I am talking about are NOT the Tier 0 carriers (e.g. Verizon
Wireless, T-Mobile, AT&T, US Mobile), and not the CLECs/ILECs we all might work
with (Level3, Bandwidth, Inteliquent/Sinch).
I'm looking for what companies/vendors might touch SMS messaging that runs
between the 3 major US Wireless networks (I believe THEY are all
interconnected directly, but maybe not) and all the other SMS-enabled DIDs
and Short Codes that are outside of those wireless networks.
Here are players I know about, but I do not know what they do
and what other carriers use these players and why:
- NetNumber
- Syniverse
- Neustar
- SAP
- Sybase
- TNS
Then we have the confusing SMS routing side: ESPID, AltSPID, VSPID, NetNumberID.
Back in 2015 a post to VoiceOps stated:
"Syniverse and SAP are working with NeuStar to make use of the AltSPID field
in NPAC for SMS routing as an alternative to NetNumber. This is expected by
the end of the year. If you have wireline number block assignments which
are SMS enabled, you may be facing a monthly per-number fee from NetNumber
come January 1st. I suggest anyone in this position contact their SMS
peering hub and the NPAC Helpdesk for more information."
https://puck.nether.net/pipermail/voiceops/2015-November/006074.html
I run a few SMSCs and pass messages through them directly to my carriers.
With one carrier I use a shared NNID, and with another I have a
dedicated/hosted NNID.
Here are my questions:
- How would one find out through which Vendors an SMS passes, in order
to troubleshoot deliverability or receivability issues?
- Does anyone what vendor/aggregator that Verizon Wireless uses?
- Are the major US wireless carriers interconnected directly, or
through yet another vendor?
- Has NetNumberID won out over AltSPID?
- Why would long code SMS messages NOT generate DLRs from the receiving
carrier through these SMS aggregators/vendors?
I acknowledge my limited understanding of all the SMS players and the
technical functionality here. Any new knowledge is appreciated.
Beckman
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman at angryox.com https://www.angryox.com/
---------------------------------------------------------------------------
Feb. 8, 2023