# RV50 not sending text **URL:** \ **Category:** General Discussion\ **Created:** [June 22, 2018, 5:33pm UTC](https://forum.inductiveautomation.com/t/rv50-not-sending-text/18582 "2018-06-22T17:33:54Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![abishur](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/abishur/32/9096_2.png) [@abishur](https://forum.inductiveautomation.com/u/abishur)\ **Post date:** [June 22, 2018, 5:33pm UTC](https://forum.inductiveautomation.com/t/rv50-not-sending-text/18582/1 "2018-06-22T17:33:54Z")
I have posted this question on the Sierra Wireless forums also, but I suspect this will be the place I get an answer from. I have an RV50X, NA & EMEA. I updated the firmware of the device and the radio firmware. I have an AT&T SIM card and I am completely unable to send or receive SMS messages. At first the card did not have SMS on the plan, however I have had the service added and despite power cycling or rebooting the device it remains completely unable to send or receive text messages! My network, power, and signal lights are all solid green. I have the white sense wire and the red power wire both connected to +24v DC and the black ground connected to ground and the green GPIO not connected to anything. My APN is set to “broadband” I’ve left the default values for SMS address type, SMS Address Numbering Plant, and AT+CGSMS When I send a text using the UDP test tool, here’s the results in the log: > ALEOS\_SERVICES\_SMSPROC: readEth2SMSSocket: Received a message from the host > Jun 22 17:17:27 debug ALEOS\_SERVICES\_SMSPROC: Sending SMS msg Test message to ########## > Jun 22 17:17:27 info ALEOS\_SERVICES\_SMSPROC: sendMsgToQCON: Logging message Test message of size 12 to QCON > Jun 22 17:17:27 info ALEOS\_SERVICES\_SMSPROC: sendMsgToQCON: Response is Test message destination ########## sms size 12 > Jun 22 17:17:27 debug ALEOS\_SERVICES\_SMSPROC: sendMsgToQCON: nextBufIndex 6 > Jun 22 17:17:27 debug ALEOS\_SERVICES\_SMSPROC: sendMsgToQCON: Logging Message at 6 > Jun 22 17:17:27 info ALEOS\_SERVICES\_SMSPROC: sendMsgToQCON: Sending message to QCON > Jun 22 17:17:27 info ALEOS\_SERVICES\_SMSPROC: sendMsgToQCON: Sent buffer index 6 > Jun 22 17:17:27 debug ALEOS\_SERVICES\_SMSPROC: SMS Message Sent Successfully > Jun 22 17:17:27 debug ALEOS\_SERVICES\_SMSPROC: readEth2SMSSocket:Status of the eth2sms 0 > Jun 22 17:17:27 debug Any ideas why it’s not working? ---
**Author:** ![abishur](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/abishur/32/9096_2.png) [@abishur](https://forum.inductiveautomation.com/u/abishur)\ **Post date:** [June 22, 2018, 5:39pm UTC](https://forum.inductiveautomation.com/t/rv50-not-sending-text/18582/2 "2018-06-22T17:39:58Z")
Also, for reference when I use the UDP test tool, I do not get a response back in the tool. Also, also, here is the log after a reboot: [https://pastebin.com/bvhcHnEn](https://pastebin.com/bvhcHnEn) ---
**Author:** ![abishur](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/abishur/32/9096_2.png) [@abishur](https://forum.inductiveautomation.com/u/abishur)\ **Post date:** [June 25, 2018, 8:02pm UTC](https://forum.inductiveautomation.com/t/rv50-not-sending-text/18582/3 "2018-06-25T20:02:07Z")
For those interested, the end problem was two fold and from what I can tell is specific to the ATT network. 1st, ATT put the text plan on the wrong SIM card. 2nd, the SIM card has been configured as the wrong type of device! It had been configured as a tablet (i.e. not a phone), as a result the APN it connected to was “broadband”. Turns out that any device using the “broadband” APN can receive texts from the ATT service group, but cannot send or receive texts to anyone or anything else. Which was exactly the behavior I was seeing at the end. If you go to the WAN/Cellular tab and look at the “SIM Slot 1 Configuration” under the “Cellular” entry you need to see the following. ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/b/b2d878ae666daa9cc5642282e05396b6108cefe4.png) It’s not going to work to just change the APN name. If you just change it then you won’t be able to connect to the network at all. In the end we had to use an IMEI number from a random ATT iPhone so we could select the correct plan type. Using the IMEI of the RV50 would ONLY give us the option of using a plan that would use the “broadband” APN.