Flash SMS via HTTP

Flash SMS via HTTP SearchSearch
Author Message
Hareeharan Kandavel
New member
Username: Haree

Post Number: 27
Registered: 12-2012
Posted on Monday, December 09, 2013 - 05:37 pm:   

Hi Team,

We would like to send flash SMSvia HTTP.

For direct URL submissions, I believe the DCS value should be set to 10. However, when submitting the messages from SMSC connection, could you please tell me where should the configuration changes be applied? I believe the changes could be applied in .INI file. If so, could you please let me know the parameters and the value?


Thanks,

Haree
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4768
Registered: 08-2008
Posted on Monday, December 09, 2013 - 09:50 pm:   

Hi Haree,


There is no INI file option to force a DCS value. You would need to specify that DCS value (or data_coding in SMPP) when submitting the message.

Maybe if you explain more of the details of your configuration ... including an overview of what protocols are used at what stage of the message path ... then maybe I might have a suggestion.

If you wanted all messages to be sent using flash, and your outbound SMSC connection is SMPP, then I think there might be a setting that could be used to override the DCS value for that connection.

However, with SMPP there are other options. DCS value 10 is technically not legal in SMPP. NowSMS remaps it to F0, which is legal and is interpreted equivalently by receiving devices.

However, that applies only to straight text messages. If unicode encoding is used, the only valid DCS flash value is 18 ... which is marked as a reserved value that is not to be used in SMPP. Because of this, NowSMS remaps 18 to 8 (non-flash Unicode) when routing over SMPP. To block this remapping (if your SMPP provider will support data_coding values 10 and 18), add RemapMessageClassDCS=No under the [SMPP - server:port] section of SMSGW.INI.

--
Des
NowSMS Support


Note: all DCS/data_coding values referenced above are hex
Hareeharan Kandavel
New member
Username: Haree

Post Number: 28
Registered: 12-2012
Posted on Tuesday, December 10, 2013 - 09:34 am:   

Hi Des,

Thank you for your response.

We do HTTP submissions to our SMPP Providers by creating SMPP connections in the Outbound SMSC tab.

We would like to set up a dedicated SMPP bind connection just for Flash messages so that all the messages are sent using Flash.

Could you please let us know the appropriate DCS settings to be applied to the SMPP connection for both text and Unicode Flash messages so that all the messages can be submitted using Flash?


Thanks,

Haree
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4770
Registered: 08-2008
Posted on Tuesday, December 10, 2013 - 04:12 pm:   

Hi Haree,

As I stated above, I cannot guarantee that an SMPP provider will support flash Unicode messages. The DCS value for flash Unicode is 18, which is reserved value that the SMPP specification says should not be used.

That said, here are settings that can be added to the [SMPP - server:port] section of SMSGW.INI to force all messages to flash format:

TextDCS=F0

This will set the data_coding/DCS value for all text messages sent over this connection to F0. I recommend this value instead of 10 as it is more compatible with different transports.

To also include Unicode, add:

UnicodeDCS=18
RemapMessageClassDCS=No

Note that 18 is not a valid data_coding value in the SMPP spec, so there's a good chance your provider will not properly understand this setting.

Also note that RemapMessageClassDCS=No currently does not work when async mode is enabled on an SMPP connection, so async mode should be disabled.

--
Des
NowSMS Support
Hareeharan Kandavel
New member
Username: Haree

Post Number: 29
Registered: 12-2012
Posted on Wednesday, December 11, 2013 - 01:55 pm:   

Hi Des,

Thank you for the explanation.

That settings for the normal Flash messages now works.

However, our SMPP provider has requested us to submit messages with a DCS value of 24 for Unicode flash messages. Do, I still need to follow the below settings:

UnicodeDCS=18
RemapMessageClassDCS=No

Also, just out of curiosity, could you please tell me how the RemapMessageClassDCS=No is related to async mode as I don't see any obvious relation between them?


Thanks,

Haree
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4771
Registered: 08-2008
Posted on Thursday, December 12, 2013 - 01:06 am:   

Hi Haree,

I suspect that they mean 24 decimal, which is 18 hex ... so you should be OK with the settings I recommended.


quote:

Also, just out of curiosity, could you please tell me how the RemapMessageClassDCS=No is related to async mode as I don't see any obvious relation between them?




Before I recommend any settings, especially in frequently used ones, I try them first to verify.

In this case, things were not working like I expected. I disabled async mode, and they worked. So I ran more tests. I don't see the connection either.

That said, my problems were with RemapMessageClassDCS=No. I was manually submitting messages with DCS=18, and NowSMS was changing to DCS=8. I added this setting but it was being ignored in async mode.

If you force the DCS for flash with UnicodeDCS=18, it will work whether or not async mode is enabled.

--
Des
NowSMS Support