A problem is that the Verizon SIM I have for the BR1 mini I chose to easily fit the BR1 mini. Unfortunately it is the larger size and won’t fit in my jetpack or other device that uses a micro size SIM. So I can’t put the BR1 SIM in an alternate device I have in order to get the verizon text message.
Verizon has the only option when I try and login to my account there to send a 1 time auth code to the SMS number of the hotspot plan to “Confirm that it’s me”. So without being able to read the SMS on the BR1, I’m not able to login to verizon or manage my verizon account which I only have the BR1 device on.
Similar issue. ATT SIM receives Text just fine in Pepwave Transit Duo, latest firmware. Verizon will only work in a VZ hotspot.
Did you discover anything else about this?
No, I had left my verizon hotspot at another location, so I actually had to purchase another verizon hotspot on ebay, put the verizon sim in it, got the text message so I could access my verizion account, and then I put the sim back in the BR1. I keep the verizon hotspot around in case I need to get a text message to that verizon sim for now.
I only use the local interface on the Transit Duo. No messages from VZ in the past 8 months. Yet I put the sim in the Hotspot and it get txts right away.
I’ve recently been trying to figure this out as well. I’ve got about 20 Max BR1 (varying models) with Verizon sim cards in them. Was hoping to use the API to send a message if a server was down. When I go to the Sim Toolkit, I either get “Bad Gateway” or “No SMS”. Would be great if these worked on Verizon 100%.
@Russ_McGinley, may I know all the BR1 (20 units) failed to read the SMS? May I know the all BR1 are running 8.0.2? Have you tested the SIM card with your phone whether the SMS can be read?
When I go to Advanced, SIM Toolkit, then select SMS for the Tool, I get the following:
MAX-BR1-LTE-US running 8.0.2 build 3612 says “No SMS”
MAX-BR1-ENT-LTE-US running 8.0.2 build 4407 says “No SIM Status” when clicking on SIM Toolkit
MAX-BR1-MK2-LTEA-W running 8.0.2 build 1480 says “No SMS”
MAX-BR1-LTEA-W running 8.0.2 build 3612 says “No SMS”
All have Verizon SIM cards in them. SMS is not blocked on these lines.
@Russ_McGinley, please help to open ticket and attention it to me. Please put in the working SIM card into the BR1 and turn on Remote Assistance for me to take a closer look.
@Russ_McGinley, sorry for the confusion here but we do not support the reading of SMS text messages.
The SIM Toolkit is more or less designed for pre-paid SIM cards on International carriers. Verizon will not even activate a pre-paid SIM card on our devices or any commercial router for that matter.
First, I’ll say the Pepwave devices have worked great for me, best cellular devices I’ve had by far.
However, as a customer I do feel a bit confused by the fact that the product data sheets say “Compatible with Verizon, ATT, Sprint, T-mobile” and have those logos.
The SMS toolkit isn’t a critical feature, so I can live with it not working, but I wanted to respond because the Pepwave hardware is great and it would be awful for me if pepwave stops working with major US carriers. Is there anything we can do as peplink customers to help get expanded rather than reduced carrier support for pepwave hardware?
Is this API from Verizon or from Peplink and where is it? My use case for getting the SMS was because Verizon won’t let me log into the billing section until after I setup my security on the account for a prepaid account. I need access to the SMS to get a code to login with. Now I have to get the sim card out of the peplink, put it into a phone and see if it can get code. If it’s possible to get access to the SMS messages from my peplink transit, it would have helped me at least this once. It sounds like there is no way for me to get it now without using a phone, but having access to SMS (if technically possible) would be desired for this case and maybe future billing issues. And of course there are the issues around the different size for sims in peplinks vs the phones. This is unpleasant, but not complicated.
Update - what a hassle. So I took the peplink off the wall, removed the cover from the sim slots, had to take out both since I couldn’t remember which one was which and it was turned off, got the correct sim, removed the small and middle sim pieces from the bigger outer sim piece, put that into a lenovo, booted it up, found it was not comptable with verizon and shut it down and removed the verizon sim from that phone and put it back the way it was. Then I took a samsung and removed it’s sim, removed the verizon middle size off of the small sim size and put that in the samsung. Booted the samsung and it said it had to restart because of the new sim. After rebooting and logging in, I had to tell verizon to resend the code and it came through. I was able to setup my billing account with verizon and then had to shutdown the samsung, remove the sim, replace the old sim and boot it back up. Now I still have to add the small sim piece to the medium and large sim pieces so I can put it back in the peplink. All of this because peplinks aren’t able to access SMS messages from verizon. I state again that because of the process I just went through, you should provide access to the SMS in the peplink web interface.
Your carrier is the issue here and looking through the forum they are the most problematic carrier in the world, best to take it up with your carrier and the local government authorities that regualate the carrier, the issue is not the Pepwave hardware.
Happy to Help,
Marcus
It’s hard as a small customer to make this case since the SMS doesn’t reach the pepwave device when it works fine to other devices, for example multiple Novatel/Inseego devices.
I hate when I get sidetracked from a project. Anywho… My use case for this is to send out alerts from our monitoring platform when the VPN connection is down. When I try it with the Pepwave Max series, I get 404 errors. We now have a Balance 30 LTE, and I just tested with that. It works as intended. I am not able to retrieve texts, but that’s not what I’m after.
