| WAP Push over SMPP with NowSMS |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through May 12, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Raulos Favor Unregistered guest |
I am evaluating the NowSMS product to see if it meets are needs and am having issues sending WAP Push messages. We have connected NowSMS to our SMPP and can successfully send SMS messages via the web interface. When we use it to send a wap push, the push message arrives on the phone but as a Text Message. All the message shows is some foreign characters (literally representation of the hex) and our link for the SI. Could this be an Issue with NowSMS? Is it an issue with our SMPP provider? We tried to send wap push via a GPRS modem with similar results on Now SMS. Thanks- Raulos | |||
| Raulos Favor Unregistered guest |
So NowSMS does not support Wap Push over external SMPP? We are still trying to get this to work via the web admin page and still have no success. Our purchasing decision is going to be based on the ability to rely on this functionality. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2092 Registered: 10-2002 |
Raulos,
That statement is not true. If the message is appearing on your phone as a text message, it certainly sounds like a potential problem with your SMPP provider ... or the receiving phone does not support WAP push. What model phone are you sending the push to? You say that you have also tried this via a GPRS modem ... did it also appear as a text message? What country are you located in? We have had instances in North America where it was necessary to make a configuration change in NowSMS with some networks. Manually edit the SMSGW.INI file, and under the [SMSGW] section header, add a setting BinaryDCS=4. Then restart the NowSMS service. -bn | |||
| Raulos Favor Unregistered guest |
Bryce- The phone we are using does support Wap Push. We are sending it to the Motorola V300 running on TMobile. We are located in the US and having issues. When we connect NowSMS to our SMPP it appears as a garbabled Text Message. GPRS modem from on network appears to work. GPRS modem from another network to TMobile shows up as text. Do you know what is with the inconsistencies? What kind of setup could cause these issues with our SMPP or our GPRS modem if it is not an NowSMS issue. -Raulos | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2104 Registered: 10-2002 |
Hi Raulos, The information that you have provided is VERY helpful.
Most likely your SMPP provider does not understand User Data Header (UDH) for binary messages. (In the SMPP environment, this is expressed as esm_class = 0x40.) The fact that you see the URL of your push in the garbage text tells me that the SMSC is indeed sending out the message with the proper binary flags, but it is likely not transmitting the UDHI (User Data Header Indicator) flag. Without the UDHI flag set in the message, the receiving handset will not be able to identify the message as a WAP push message. Unfortunately, because of the mix of CDMA and GSM/TDMA in the US, many SMS providers do not understand binary SMS messages. You should contact your SMPP provider and explain the information that I have provided you with here, explaining that you need to send out binary SMS messages that include User Data Header (UDH). Hopefully they can assist you if they know this.
Yes, this is one of the headaches in the US. SMS interoperability links between the major US carriers only understand text messages. If you try to send a binary message across carriers, the intercarrier connection either loses the message, or loses important attributes of the message (such as the UDHI flag that I mentioned above). At present, in the US, when sending binary message types like WAP push over a GSM/GPRS modem, they can generally only be sent to recipients subscribed to the same carrier. Unfortunately, all of this is beyond our control from a NowSMS perspective. We need integretity of the binary SMS message attributes to be maintained enroute to the recipient. The BinaryDCS=4 setting under [SMSGW] in SMSGW.INI can be useful for some SMSCs, but there is no alternate way to specify that a message contains User Data Header (UDH). -bn | |||
| Raulos Favor Unregistered guest |
Bryce- Well I tried some more connecting to SMPP and this is the dump that is received at the SMPP: command_length => 88 command_id => 4 command_status => 0 sequence_number => 2 service_type => source_addr_ton => 0 source_addr_npi => 0 source_addr => 007 dest_addr_ton => 0 dest_addr_npi => 0 destination_addr => 14152006095 esm_class => 64 protocol_id => 0 priority_flag => 0 scheduled_delivery_time => validity_period => registered_delivery => 16 replace_if_present_flag => 0 data_coding => 245 sm_default_msg_id => 0 sm_length => 41 short_message => ^F^E^D^K~D#p\^F^A.^B^Ej^@EF^L^Cwapforum.com^@^A^CLink^@^A^A Does that look like correct output that would come from the NowSMS gateway? I am trying to contact our smpp and see what happens when they pass it to their provider. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2131 Registered: 10-2002 |
Yes. I'm not used to seeing many of those values in decimal format ... I'm used to seeing them in hex ... so it took me a minute. Basically, the key is that we are sending out an "esm_class" value of 0x40 (64) which indicates that the short_message includes "user data header". When the SMSC sees this flag, it needs to set the UDHI (user data header indicator) in the SMS message that is generated for delivery over the air. The data_coding value is another issue. Our default value is 0xF5 (245). This value is somewhat unusual in North America, so you may want to use the configuration setting that I mentioned above (SMSGW.INI / [SMSGW] section / BinaryDCS=4), which will change this value to 4. -bn | |||
| Raulos Favor Unregistered guest |
Bryce- Yes I figured it out before I saw this post (doh!). The issue was indeed the data coding. Once we set that to 4 we had no issues. Is there any info on this board site/ for generating wap push for CDMA? Are there any differences? -Raulos | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2141 Registered: 10-2002 |
Raulos, Glad to hear that the DCS change made a difference. So far I haven't seen any clear information about generating WAP Push over CDMA. This is something that we would like to support, but it has been something of a challenge for us to get a test environment that allowed us to test sending binary SMS into a CDMA network. -bn | |||
