DCS Value

DCS Value SearchSearch
Author Message
KB commodity
New member
Username: Kbcomex

Post Number: 6
Registered: 12-2007
Posted on Friday, May 16, 2008 - 03:35 pm:   

Hello Everyone!

I am using NOWSMS 2006.

I am connected to SMSC through SMPP & my clients are submitting SMS through SMPP & Http.

Now the problem is, SMSC required DCS value to be 8 but my client are submitting SMS with the dcs value 0.

How can I change this DCS Value to 8.

Regards
KB Commex
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7577
Registered: 10-2002
Posted on Tuesday, June 10, 2008 - 09:50 pm:   

NowSMS only uses DCS=8 if the message text contains Unicode characters that are outside of the standard GSM character set. Otherwise, it uses DCS=0.

Are you saying that your provider requires all text messages (even ones with simple text like "abc") to be sent in Unicode format?

-bn
Pratik Chauhan
New member
Username: Pratikchauhan

Post Number: 5
Registered: 06-2008
Posted on Thursday, August 14, 2008 - 07:48 pm:   

Hi,

I have created SMPP connection with my SMSC which uses DCS=2 (Octet 8-Bit Binary). I can also see on Ethereal/wireshark protocol analyzer that when I send message from my smsc to NowSMS software DCS value is 2. But when I see SMSIN logs in NowSMS it shows that DCS=4. Also I am using transparent routing to send any messages received through my SMSC to re-route to International SMS carriers over second SMPP connection. Since NowSMS changes to DCS=4, International carriers also see message with DCS=4 and then many GSM destinations can receive messages but they can not view message.

which causes this DCS change when sms reach to NowSMS gateway? Also, is there any way in tranparent routing case, to change to DCS=0 when sending message to Outbound SMPP connection irrespective of the DCS value of message received over Inbound SMPP link.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4
Registered: 08-2008
Posted on Tuesday, August 19, 2008 - 05:28 pm:   

Hi,

NowSMS uses an SMPP data_coding value of 4 for most binary messages, because that code value matches the value that is defined in for the SMS Data Coding Scheme (DCS, a.k.a., TP-Data-Coding-Scheme) in ETSI GSM 03.38 for the actual over the air SMS.

In the actual over the air SMS, a DCS value of 4 is the normal value that is used for a binary message (unless message class information is present in the message). A DCS value of 2 is undefined for an actual SMS message being sent over the air.

In the SMPP world, data_coding values of 2 and 4 both indicate binary messages. Because NowSMS can talk to different types of SMSCs, if it receives an SMPP message with a data_coding value of 2, it changes it to 4, so that it will be compatible with other systems.

Are you sure that this is causing a problem?

I can discuss this further with our engineers ... a configuration setting on a per SMSC basis to use data_coding = 2 instead of 4 does not sound like it would be difficult considering all of the other unusual parameters that NowSMS supports. But we'd want you to confirm that this is really a problem before we spent much time on it.

There is no way to change DCS value to 0 when sending to outbound SMPP connection. That would be a sure way to corrupt messages. The only idea that I have is that maybe it would be helpful to have an option in NowSMS to remove any message class settings from outbound messages for a particular SMSC. I have seen that some SMSCs definitely do not like DCS values that include message class encoding ... of course, that can cause some problems for messages that require message class encoding (but if the SMSC would otherwise hopelessly corrupt the message, that's a small price to pay).

I'd suggest you try to do some tests to determine where the problem lies, and if one or both of the above settings might do the trick, then I'll try to work it through the engineering queue.

--
Des
NowSMS Support