| AT&T OMA OTA Config |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through August 22, 2012 ⬆ |
◄ ► |
| Author | Message | |||
| Jeffrey Dunn New member Username: Jeff2d2 Post Number: 2 Registered: 02-2012 |
I believe I have tested with all that I could using NowSMS and I really hope we can get it working for our needs: sending custom config settings OTA. First of all, we use an AT&T MVNO (Red Pocket Mobile). All of our phones use prepaid SIM cards from them. We use the LG CU720 and LG GD710. Both of these phones support OMA (according to their specs). So why am I having such trouble sending an OTA config to them? Let me explain: After much tinkering, I can tether one of the phones to my PC and send SMS, MMS, and EMS messages all day. But I cannot get it to send any kind of WAP push. My understanding is that this is because AT&T blocks this ability. Great. We have an SMS aggregator that can send WAP push messages for us, but have been unsuccessful with sending OMA OTA configs. My question is this: I have the XML in text document file that needs to go to the phone. I understand this needs to be converted to WBXML first. I think I can do that no problem, but them how do I get it to the phone? Can it be SMS'd? If so, how? Can it be sent via bluetooth? How? Someone once mentioned creating a Java app that is installed to the phone, which upon opening it deploys the correct settings. Not sure about this. This can't be that hard, but appears impossible with AT&T. There has to be a way. Thank you. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3868 Registered: 08-2008 |
Hi Jeffrey, If its a <wap-provisioningdoc> format XML, then the easiest way to send it is from the "Send XML Settings" menu in NowSMS. That is the way that these documents would normally be sent over SMS. (The XML gets converted into a WBXML format and packaged in a WAP Push over SMS.) I've never heard of installing a Java app to do this. I have heard of a company creating an Android app to receive and apply these settings messages because stock Android does not support them. I don't think you could do that in Java because Java won't let an application listen and intercept on the WAP Push port. -- Des NowSMS Support | |||
| Jeffrey Dunn New member Username: Jeff2d2 Post Number: 3 Registered: 02-2012 |
Thank you, Des. Yes, I have tried to use Send XML Settings, but the whole problem is I am sending from an AT&T device to an AT&T device. Evidently AT&T blocks WAP push messages in this fashion. Using the other OTA tools in NowSMS seem to fail as well. The service queue just shows a CMS +500 error whenever trying to send WAP anything. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3869 Registered: 08-2008 |
Hi Jeffrey, I assumed that you were now using an SMS aggregator that supported WAP Push messages, and that NowSMS was interfacing with them sending binary SMS. But I guess that aggregator is building the push messages themselves, and you do not have control over the binary format of the SMS? -- Des NowSMS Support | |||
| Jeffrey Dunn New member Username: Jeff2d2 Post Number: 4 Registered: 02-2012 |
We haven't really explored how much we can use the SMS aggregator for in this purpose. We use them to send web links (WAPSI) to our customers right now, but that's it. What we'd like to do is send the Internet settings via OTA, and if that means getting them involved, then that's a possibility. Ideally however, we'd like to see if we can do it on our own and avoid the per SMS charge we get from them. That's when I found NowSMS. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3872 Registered: 08-2008 |
Understood. Unfortunately, for the last couple of years, AT&T does seem to be blocking mobile originated WAP Push messages from being sent. The WBXML content for the OTA is the payload for a WAP Push message, just like WAP Push SI is also WBXML ... just different push content types. -- Des NowSMS Support | |||
| Jeffrey Dunn New member Username: Jeff2d2 Post Number: 5 Registered: 02-2012 |
Hi Des, Our SMS aggregator has now updated their api to allow sending of binary content to AT&T phones. I have been able to send a couple very simple binary messages, so taking the next steps to composing an OMA provisioning message is right around the corner. I have the XML ready to go. How do I go about converting this XML into a binary data string? Does it have to be done manually (character by character), or could NowSMS assist with this? My trial period expired unfortunately so it will not let me play anymore :( | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3909 Registered: 08-2008 |
Hi Jeffrey, The OMA Provisioning Content and WBXML (Wireless Binary XML) specifications from the Open Mobile Alliance document the binary format, if you are so inclined. References: http://www.openmobilealliance.org/Technical/current_releases.aspx http://www.openmobilealliance.org/Technical/wapindex.aspx NowSMS can perform this conversion automatically via the "Send XML Settings" interface (http://www.nowsms.com/doc/web-menu-interface/send-xml-settings). If you want to give it another trial, try it on a different PC. -- Des NowSMS Support | |||
| Jeffrey Dunn New member Username: Jeff2d2 Post Number: 6 Registered: 02-2012 |
Hi Des, I have opened a new trial on another PC, but I am still having trouble getting out of it what I need. The SMS aggregator opened an API call via HTTP. The API is something like: http://smsaggregator.com/<binary-string-goes-here>. I need to get the OMA message down to one, long, concatenated binary string. I don't see how the Send XML Settings interface does this. It appears to only be able to submit through the SMSC setup setup in NowSMS, of which we have none. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3917 Registered: 08-2008 |
Hi Jeffrey, I was just figuring on you using the HTTP SMSC interface. And I was going to give you the templates for smsaggregator.com ... but re-reading your message, I see that is just an example. As long as HTTP GET is supported, defining an HTTP SMSC template (http://www.nowsms.com/doc/configuring-smsc-connections/http-smsc) is fairly straight-forward. By default, NowSMS is going to segment the message. If the provider needs it unsegmented, check “Send long messages without segmentation” in the definition. -- Des NowSMS Support | |||
