- VoiceOps - lists.voiceops.org

IPAWS/FEMA National Test - VoWIFI
by nathana＠fsr.com Oct. 6, 2023

Oct. 6, 2023

...huh. https://cacm.acm.org/magazines/2021/10/255719-securing-the-wireless-emergen… Guess it is delivered over a separate interface to the MME than SMS would be. Kinda boggles the mind that "WEA over IMS" isn't a thing. Perhaps it's an issue of scalability? WEA messages over NAS presumably doesn't require that much overhead: MME sends the message out to all eNBs, who in turn I'd guess would just indiscriminately transmit it to all attached UEs. More broadcast-y than unicast-y. Whereas I guess an IMS-based solution would require the CSCF to enumerate all active registrations and then transmit a SIP message individually to each subscriber, one-by-one. Still, the lack of at least some IP-based way of accomplishing this seems like a huge oversight, especially in an age where it seems like more people (especially in more rural areas) are more reliant on VoWiFi than ever before in order to have any use whatsoever of their mobile voice service while at home. -- Nathan -----Original Message----- From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Nathan Anderson via VoiceOps Sent: Wednesday, October 4, 2023 3:53 PM To: voiceops at voiceops.org Subject: Re: [VoiceOps] IPAWS/FEMA National Test - VoWIFI Darn...it actually had occurred to me to test this very thing by forcing airplane mode and then enabling WiFi, but then spaced it and didn't manage to do that before the broadcast went out! Assuming I'd actually managed to run the test, I was actually fully prepared to be surprised if I had NOT gotten the test broadcast while exclusively on WiFi Calling. It seems bizarre to me to learn that WEAs are dependent on the same NAS CP messages that non-IP-based SMS over LTE is also dependent on...can this really be true?? This is strange because it would require that all mobile carriers continue to run and maintain a 2G core, since (as far as I know) SMS can only be encapsulated within LTE NAS by way of the SGs interface. (Perhaps there is some separate interface over which WEA payloads specifically are sent to the MME?) Some months ago -- but well after the 3G UMTS shutdown had taken place -- I found that my ability to use SMS on the AT&T network had suddenly broken in a weird way, and ONLY worked over WiFi. Which was naturally a *wee* bit inconvenient. After digging into it over a few days, I figured out that the SMS over IP (IMS) setting in my (non-5G) handset's baseband was disabled. And apparently this setting is ignored when you are on VoWiFi, since IMS is literally the only way to deliver SMS over ePDG. I enabled it & that fixed my problem with SMS over LTE. I did some back-and-forth testing and every time I re-disabled that baseband setting, SMS over LTE broke again. I took this all as a sign that AT&T was probably looking to retire their entire 2G/3G core, though admittedly I haven't tried forcing the same handset back to SMS-over-SGs since then in order to see if maybe this was just a temporary (yet prolonged) glitch on their side. -- Nathan -----Original Message----- From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Jay R. Ashworth via VoiceOps Sent: Wednesday, October 4, 2023 2:08 PM To: jra Cc: VoiceOps Subject: Re: [VoiceOps] IPAWS/FEMA National Test - VoWIFI I now have a counter report that the Cellular Control Channel necessary to get these alerts to a cellphone *is not proxied by carrier WIFI-connect*, by design. I'm familiar with his credentials, and I'll assume he knows what he's talking about, cause *I* know what he's talking about, and he sounds like he's talking sense. :-) Thanks to everyone who responded. If you *did* get an alert, *and you know you were not in range of ANY cell network*, only WIFI proxy, that wasn't supposed to be possible and I would still like to hear about that. Cheers, -- jr 'just zis guy, you know?' a ----- Original Message ----- > From: "Jay R. Ashworth via VoiceOps" <voiceops at voiceops.org> > To: "VoiceOps" <voiceops at voiceops.org> > Sent: Wednesday, October 4, 2023 3:25:04 PM > Subject: [VoiceOps] IPAWS/FEMA National Test - VoWIFI > I have a report from a usually reliable source that he did not receive today's > IPAWS/CMAS/WEA test message, and he surmises this might be because his phone > handset is forced to VoWIFI. I have a number of other reports, mostly though > not all, from the broadcast engineering community; nobody reported expecting > a CMAS and not getting it, so that's not data here. > > Is anyone on the list involved with the FEMA/IPAWS/CMAS link, or knows someone > who is, and has a channel to clear this query up through? > > I could be unsurprised to find that the carrier VoWIFI proxies missed out on > proxying SMS Cell Broadcast, which I gather provides the underlying PHY for > CMAS. > > Cheers, > -- jra > > -- > Jay R. Ashworth Baylink jra at baylink.com > Designer The Things I Think RFC 2100 > Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII > St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274 > _______________________________________________ > VoiceOps mailing list > VoiceOps at voiceops.org > https://puck.nether.net/mailman/listinfo/voiceops -- Jay R. Ashworth Baylink jra at baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274 _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

2 1

IPAWS/FEMA National Test - VoWIFI
by nathana＠fsr.com Oct. 4, 2023

Oct. 4, 2023

Darn...it actually had occurred to me to test this very thing by forcing airplane mode and then enabling WiFi, but then spaced it and didn't manage to do that before the broadcast went out! Assuming I'd actually managed to run the test, I was actually fully prepared to be surprised if I had NOT gotten the test broadcast while exclusively on WiFi Calling. It seems bizarre to me to learn that WEAs are dependent on the same NAS CP messages that non-IP-based SMS over LTE is also dependent on...can this really be true?? This is strange because it would require that all mobile carriers continue to run and maintain a 2G core, since (as far as I know) SMS can only be encapsulated within LTE NAS by way of the SGs interface. (Perhaps there is some separate interface over which WEA payloads specifically are sent to the MME?) Some months ago -- but well after the 3G UMTS shutdown had taken place -- I found that my ability to use SMS on the AT&T network had suddenly broken in a weird way, and ONLY worked over WiFi. Which was naturally a *wee* bit inconvenient. After digging into it over a few days, I figured out that the SMS over IP (IMS) setting in my (non-5G) handset's baseband was disabled. And apparently this setting is ignored when you are on VoWiFi, since IMS is literally the only way to deliver SMS over ePDG. I enabled it & that fixed my problem with SMS over LTE. I did some back-and-forth testing and every time I re-disabled that baseband setting, SMS over LTE broke again. I took this all as a sign that AT&T was probably looking to retire their entire 2G/3G core, though admittedly I haven't tried forcing the same handset back to SMS-over-SGs since then in order to see if maybe this was just a temporary (yet prolonged) glitch on their side. -- Nathan -----Original Message----- From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Jay R. Ashworth via VoiceOps Sent: Wednesday, October 4, 2023 2:08 PM To: jra Cc: VoiceOps Subject: Re: [VoiceOps] IPAWS/FEMA National Test - VoWIFI I now have a counter report that the Cellular Control Channel necessary to get these alerts to a cellphone *is not proxied by carrier WIFI-connect*, by design. I'm familiar with his credentials, and I'll assume he knows what he's talking about, cause *I* know what he's talking about, and he sounds like he's talking sense. :-) Thanks to everyone who responded. If you *did* get an alert, *and you know you were not in range of ANY cell network*, only WIFI proxy, that wasn't supposed to be possible and I would still like to hear about that. Cheers, -- jr 'just zis guy, you know?' a ----- Original Message ----- > From: "Jay R. Ashworth via VoiceOps" <voiceops at voiceops.org> > To: "VoiceOps" <voiceops at voiceops.org> > Sent: Wednesday, October 4, 2023 3:25:04 PM > Subject: [VoiceOps] IPAWS/FEMA National Test - VoWIFI > I have a report from a usually reliable source that he did not receive today's > IPAWS/CMAS/WEA test message, and he surmises this might be because his phone > handset is forced to VoWIFI. I have a number of other reports, mostly though > not all, from the broadcast engineering community; nobody reported expecting > a CMAS and not getting it, so that's not data here. > > Is anyone on the list involved with the FEMA/IPAWS/CMAS link, or knows someone > who is, and has a channel to clear this query up through? > > I could be unsurprised to find that the carrier VoWIFI proxies missed out on > proxying SMS Cell Broadcast, which I gather provides the underlying PHY for > CMAS. > > Cheers, > -- jra > > -- > Jay R. Ashworth Baylink jra at baylink.com > Designer The Things I Think RFC 2100 > Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII > St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274 > _______________________________________________ > VoiceOps mailing list > VoiceOps at voiceops.org > https://puck.nether.net/mailman/listinfo/voiceops -- Jay R. Ashworth Baylink jra at baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274 _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

1 0

IPAWS/FEMA National Test - VoWIFI
by jra＠baylink.com Oct. 4, 2023

Oct. 4, 2023

I have a report from a usually reliable source that he did not receive today's IPAWS/CMAS/WEA test message, and he surmises this might be because his phone handset is forced to VoWIFI. I have a number of other reports, mostly though not all, from the broadcast engineering community; nobody reported expecting a CMAS and not getting it, so that's not data here. Is anyone on the list involved with the FEMA/IPAWS/CMAS link, or knows someone who is, and has a channel to clear this query up through? I could be unsurprised to find that the carrier VoWIFI proxies missed out on proxying SMS Cell Broadcast, which I gather provides the underlying PHY for CMAS. Cheers, -- jra -- Jay R. Ashworth Baylink jra at baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274

1 1

Any ideas on..
by jawaid＠bazyar.net Oct. 3, 2023

Oct. 3, 2023

where I could get my hands on a Metaswitch lab setup with the following: MetaSphere CFS MetaView Server Perimeta SAS (Service Assurance Server) and particular need: MetaView Web Services API Network-Wide Web Services API The purpose is to to write some software against it, for automated provisioning. I know this is a weird request, but there you have it :-) Cheers, Jawaid

1 0

Intrado Contact
by securityconcern2023＠proton.me Sept. 28, 2023

Sept. 28, 2023

Hi, Anyone from Intrado on this list? Does anyone have a contact for Intrado security? TIA.

1 0

Request to block number?
by ctaloi＠gmail.com Sept. 26, 2023

Sept. 26, 2023

Hey All, I have a new one. We (hosted phone provider) have received three calls today from an individual asking us to block him from calling our company. I can't figure out his end game. He's tried multiple times and didn't explain why when questioned. He said multiple times he wanted his number to be blocked from calling our company. Thoughts? Could it be a social engineering attempt? What for? Chris

14 34

Scam Caller - course of action for service provider?
by ctaloi＠gmail.com Sept. 26, 2023

Sept. 26, 2023

Hey All, We have a customer who came on board and used our hosted phone service. They made it through our "know your customer process" by misrepresenting themselves. They were actually referred by another customer. 24 hours into their service with us one of our carriers flagged their calls. I started digging into their traffic and learned they are running a scam to convince elderly folks to give up their credit card information. It makes me sick to think this was on my network. I have obviously terminated their service. I would like to take this to the authorities. I have call recordings and KYC information. Thoughts on where to start? Chris

3 2

CLID weirdness
by dave＠brockmans.com Sept. 21, 2023

Sept. 21, 2023

Hello, First, please forgive me, I am a network engineer by trade, I am not extremely well-versed in telephony. Please forgive me if I use the wrong terminology or otherwise misstate something. It is not intended and does not come from malicious intent. I have a customer with a SIP trunk from $LocalTeleco. We send our own CLID out from our (3CX) PBX. For one specific DID (which also happens to be the office main number /sigh) everywhere I can see it calling, shows up as "Restricted, Anonymous, or Private". However, I can call MCI at 800.444.4444 and they tell me the correct CLID digits. I have several hundred other DIDs that I can present, and appear correctly at the same receiving carriers that show restricted/anonymous/private on the main DID, and MCI will read back the expected digits. Would anyone more versed in this side of things be willing to let me make a couple of test calls, and you tell me if you see anything strange that I can take back to $LocalTeleco? This has been working as expected for about 3 years, somewhere in the past couple of months, something has changed (and not on our end). $LocalTeleco says everything looks fine to them, but I think they are not super well versed in their Phone switch (mostly by listening to them confer with colleagues and looking up documentation while I'm on the phone with them). With Gratitude, Dave Brockman Senior Network Engineer Gig City Cloud, LLC

3 5

Request to block number?
by nathana＠fsr.com Sept. 21, 2023

Sept. 21, 2023

For those who have gotten this call, I am curious if the voice sounded *EXACTLY* like the one in the recording posted earlier to this list, or different? -- Nathan From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Jason Gaddis via VoiceOps Sent: Thursday, September 21, 2023 1:20 PM To: VoiceOps Subject: Re: [VoiceOps] Request to block number? +1. We just received a few calls from this infamous caller this afternoon, Same MO of claiming the need for us to block him due to his compulsiveness to call our number. Aside from his name, no other information was shared. There are no requirements that I'm aware of other than if they are being abusive to block him. Just based on the number of responses to the thread this seems pretty targeted than a general mental condition, but just my two cents. Same telephone number as posted. I'm suggesting to our folks to stay vigilant. On Thu, Sep 21, 2023 at 3:22?PM Carlos Alvarez via VoiceOps < voiceops at voiceops.org> wrote: When called via Bandwidth, it gives a 503. When called via thinQ (and whatever carrier they chose to use), it was answered, and then played an ?all circuits are busy? message. The number shows it?s active with Verizon Wireless. Interesting. Obviously, I used a fake CLID for the call. On Sep 21, 2023 at 12:12:44?PM, David Breakey via VoiceOps < voiceops at voiceops.org> wrote: No, and I'm not inclined to do so. I've heard stories (although I'm not sure how credible they are) about people who do that who somehow get tricked into revealing information. While I'm not particularly concerned about that (I'm deeply paranoid by default when it comes to unsolicited calls), I really don't care to deal with a potential headache ? However, the number that came up for me was: 484-579-1377, which Google IDs as a debt collector. On 9/21/23 13:04, Carlos Alvarez via VoiceOps wrote: Now I really look forward to my turn to get this call. Have either of you tried calling that number back? _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

1 0

A2P-aaS
by abalashov＠evaristesys.com Sept. 20, 2023

Sept. 20, 2023

I have a purely internal portal application that is used to send SMS notifications about customer monitoring incidents and emergencies about... twice a month. Maybe 5-10 messages per month total, across several associates combined. It's all done through Twilio's SMS API. There is not enough Prozac, pot, liquor, etc. in the world that's going to make me log into Twilio's portal and do their campaign enrollment. For these negligible volumes of purely internal notification traffic, a pure cost centre, not customer-facing anything, etc., I just don't care, and you won't make me care. However, these notifications are fairly essential because they allow me to pierce the iOS "Do Not Disturb" wall on our phones and get them even at 3 AM. There's no decent over-the-top alternative I can see; I have to enable notifications for an over-the-top messaging application as a whole, the last thing I want to do. So, there's a business opportunity here for an SMS provider who 1) offers a relatively straightforward REST API to send SMS and 2) will take care of the A2P campaign garbage aspect. I'd love if someone took that up. -- Alex -- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com Tel: +1-706-510-6800

9 10