| How to Send WAP Push Advanced |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through June 03, 2020 ⬆ |
◄ ► |
| Author | Message | |||
| nobuhiro kaneko New member Username: Kaneko Post Number: 2 Registered: 04-2020 |
I want to send WAP Push to lwm2m client via SMS. The data format is Table:L in OMA-TS-LightweightM2M_Core-V1_1-20180612-C.pdf. Please let me know how to set the parameters of web interface. I tried to set the following. But the lwm2m client device could not received the SMS. Thank you.  | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8342 Registered: 10-2002 |
Hi, I've never worked with this format before, but it seems relatively straight-forward ... and I can clear up some confusion. First, as a reference to others (and for me to refer to) here's that Table L:  Considering that you are working from an example that provides the SMS UDH and WSP headers. It may be easier (and less confusing) to generate the binary SMS directly. Your UDH would be 0605040b84c02 The message data would be 0106034402b60b2161fb63b13101300138 (WSP headers + content) Use DCS=F5 for WAP Push  The URL format for submitting a binary message programmatically is described here: https://www.nowsms.com/doc/submitting-sms-messages/sending-binary-messages Leave out the PID value referenced in that document, as it is not relevant for WAP Push. -bn Bryce Norwood Now SMS/MMS Support | |||
| nobuhiro kaneko New member Username: Kaneko Post Number: 3 Registered: 04-2020 |
Hi, I tried the above but the lwm2m client device could not received the SMS. I am using Nexus5X. I checked Outbound SMS Queue of NowSMS Modem app. The cause is "HTTPSMSC: Connection failed,HTTP status code = 503". Nexus5X is rooted and is set "AT+CMGF=0". I can send if SMS text message. Are there any advice? Thank you. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 6126 Registered: 08-2008 |
Hi, Binary messages cannot be sent through the Android modem app interface. They can be sent via a GSM modem connected via serial or USB. You mention AT+CMGF=0 ... that is the type of command that NowSMS would send over this serial/USB interface. If the device can expose that type of interface to the PC, then it should work if you configure NowSMS two connect serial/USB instead of via the app. HOWEVER, our experience is that a dedicated USB stick type of modem is more reliable than trying to use a phone as a serial/USB modem. -- Des NowSMS Support | |||
| nobuhiro kaneko New member Username: Kaneko Post Number: 4 Registered: 04-2020 |
Hi, I do not try the USB stick type yet but... I confirmed CarrierCapability.java of android. https://cs.android.com/android/platform/superproject/+/master:cts/tests/tests/te lephony/current/src/android/telephony/cts/CarrierCapability.java There was a following comment. // List of network operators that doesn't support Data(binary) SMS message public static final List<String> UNSUPPORT_DATA_SMS_MESSAGES = Arrays.asList( "44010", // NTT DOCOMO "44020", // SBM "44051", // KDDI So, I think we can't send binary by using Japanese carrier's SIM. Do you have the experience of binary SMS send test in Japan ? Thank you. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8343 Registered: 10-2002 |
Hi, That is an interesting observation. If I recall correctly, the original 2G/3G networks in Japan were not based on GSM. but CDMA. Their evolution followed 3GPP2 instead of 3GPP. Annoyingly, the WAP Push over SMS formats are different in these environments. (To be more correct, it is WDP that gets encoded differently between these environments. WAP push is implemented using connectionless WSP over WDP.) For example, UDH (user data header) is specific to GSM/3GPP SMS. UDH is used for encoding segmentation and port number addressing (which was used by protocols like Nokia Smart Messaging and even some primitive Java apps pre-WAP). Similar concepts were not part of CDMA/3GPP2, so they were defined by the WAP/WDP protocol. Here's an excerpt from the spec where this was defined:   That seems simple enough, but it's not. Let's go back to the previously discussed example message. The UDH was 0605040b84c002, which is the WDP layer encoding of the GSM SMS. The message data would be 0106034402b60b2161fb63b13101300138, which is the WSP headers + content. For CDMA SMS, we would preface the SMS user data with: 00 (MSG_TYPE) 01 (TOTAL_SEGMENTS) 00 (SEGMENT_NUMBER) c002 (SOURCE_PORT) 0b84 (DESTINATION_PORT) The complete binary SMS in this case would be: 000100c0020b84 0106034402b60b2161fb63b13101300138 If this message was too long to fit in a single SMS, life would be more complicated. Segmentation and reassembly for GSM SMS uses a user defined message reference number. In CDMA SMS, segmentation is dependent on a MESSAGE_ID field that can only be set by an SMSC. So, how does this type of binary SMS actually get sent? In our experience, we've only found 2 methods. For both methods, it should be noted that NowSMS natively uses the GSM UDH encoding. NowSMS then converts this encoding when sending it. 1.) SMPP using WDP Adaptation. Segmentation and port numbers are encoded as SMPP TLV parameters, with service type set to WAP. The SMSC is expected to encode the message to the format used by the destination network. 2.) NowSMS is frequently used in lab/testing environments where it uses HTTP to submit messages to network simulators. These template formats can be adapted to encode WAP Push in this CDMA format. For more info see https://www.nowsms.com/doc/mmsc-messaging-server/mmsc-in-cdma-or-cdma2000-environments and https://support.nowsms.com/discus/messages/485/50776.html One final note...if you need to use this format, the GSM modem is a dead end. Any modems that we have seen for those networks supported only text formats. -bn Bryce Norwood Now SMS/MMS Support | |||
