Data Coding Deliver_SM

Data Coding Deliver_SM SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through May 19, 2016 » Data Coding Deliver_SM « Previous || Next »
Author Message
Ralph Leyrer
New member
Username: Rleyrer

Post Number: 1
Registered: 05-2016
Posted on Thursday, May 12, 2016 - 07:07 pm:   

I open a ticket on this subject, but could not attach supporting screen snippets.
Also, I wanted to provide more detailed information.

We have a system that can only accept SMS messages with 7-bit GSM and language =0.
This system cant be changed as we don’t have the source code for the SMS driver.

A recent NowSMS server is generating values of 1=English, 4=Spanish, but we can not get NowSMS to generate language=0.

We have tried numerous changes as define din the forum on the client side and on the carrier side, but nothing
Generates the header that we need.

We have tried
BInaryDCSOveride…
TextDCS=0,4
SMSCCharSet=iso-8859-1
Also tried IA5.

What needs to be done to get the DCS CBS Message Language set to ‘0x00’?

Attached Wireshark packet snippets included.

Ralph Leyrer
404-205-2921
application/vnd.openxmlformats-officedocument.wordprocessingml.documentData Coiding Language Issues - Snippets
NowSMSDataCodingLanguageIssue.docx (280.8 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5641
Registered: 08-2008
Posted on Thursday, May 12, 2016 - 08:07 pm:   

Hi Ralph,

NowSMS uses SMS DCS values, not CBS (cell broadcast) DCS values.

Where are these messages coming from? I can't see a reason why NowSMS would generate any DCS values, it would just be relaying the values.

In SMPP, data_coding = 0 means default alphabet. 1 means GSM character set. 4 means binary content.

If NowSMS is generating a value of 1 when you expect 0, set the SMPP character set to Default. (Default uses the GSM character set and DCS 0. If you change this setting to GSM, NowSMS forces DCS 1.)

Are these messages actually cell broadcast messages?

--
Des
NowSMS Support
Ralph Leyrer
New member
Username: Rleyrer

Post Number: 2
Registered: 05-2016
Posted on Friday, May 13, 2016 - 09:43 am:   

I only indicated CBS as that is what Wireshark showed I the packet capture snippet.

The device sending this SMS message is a car telematics device.

The issue we are having it seems is that the DCS language is a value of 1-English or 4-Spanish and our end-system needs 0-German or 2-??. Our end-system receiving the SMS message can not be changed as we do not have the source code for it.

So regardless of what the SMS message contains when NowSMS receives the SMS message from the carrier, we need to override it if needed so the DCS is 7-bit-gsm and language 0-german.

The two snippets show this. Header for "PRODUCTION" which works fine for us versus header for "ITEST" environment which does not work.

We have a NowSMS server in Production environment running NowSMS version v2011.07.05 and it works ok and provides 7-bit GSM + language 0-German.

We have a NowSMS server in an "ITEST" (pre-prod integration test) environment
running version NowSMS version v2015.06.25 which we have not been able to configure to provide the same 7-bit GSM, language 0-German. We have change config parameters and all we have been getting is 1-English or 4-Spanish.

Some of the config parameters we have changed to try to get it to work in ITEST (v2015.06.05) are:
factory default setting
textDCS
BinaryDCSOveride
SMSCCharset
CharsetDefault

We cant rollback the ITEST version to V2011.07.05 as we do not have that software build and are unable to download it.

Any help would be appreciated.

THanks
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5642
Registered: 08-2008
Posted on Friday, May 13, 2016 - 12:54 pm:   

Hi Ralph,

These data_coding values do NOT specify language. So, they are not indicating German, English or Spanish.

They indicate character set:

0 - default
1 - GSM/IA5
2 - 8-bit binary (generally considered obsolete)
3 - iso-8859-1
4 - 8-bit binary
8 - unicode UCS-16

By default, NowSMS is going to use 0. It would only use 1 if the configuration explicitly is set to use the GSM character set.

You refer to deliver_sm, so I assume this is an SMPP client connecting to NowSMS as its SMPP server. In that case the character set is configured under Web/SMPP Options.



Remove any of the other settings that you manually tried. By default, NowSMS is going to use data_coding 0 for standard text messages. If you are still seeing data_coding 1, there is a setting somewhere that is causing it. Start with the above and I will follow-up with more shortly.

--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5643
Registered: 08-2008
Posted on Friday, May 13, 2016 - 01:19 pm:   

Regarding 2 vs. 4 ... both of those values are valid in SMPP. But 2 is considered antiquated. In GSM, 2 is an invalid value, while 4 is valid for 8-bit binary content.

Because many modern SMPP applications do not understand data_coding=2, NowSMS will change 2 to 4.

If you have an older SMPP application that requires 2 for binary, manual settings can be applied in SMSGW.INI.

When NowSMS is the client:

[SMPP - server:port]
BinaryDCS=2

When NowSMS is the server:

[SMPP]
BinaryDCS=2

NowSMS 2011.07.05 would have worked the same way with these values as I found this thread from 2010 which explains this same issue: http://support.nowsms.com/discus/messages/1/59836.html

--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5644
Registered: 08-2008
Posted on Friday, May 13, 2016 - 01:26 pm:   

Ralph,

One more thought...if the above does not guide you to a solution...

Email SMSGW.INI, SMSIN-20160513.LOG and SMSOUT-20160513.LOG (and maybe the in/out from yesterday) to nowsms@nowsms.com with Attention: Des in the subject line of the message. That should give me a better picture of what's going on.

And if necessary, I'll locate the old release in our archives if there is not an obvious solution.

--
Des
NowSMS Support
Ralph Leyrer
New member
Username: Rleyrer

Post Number: 3
Registered: 05-2016
Posted on Friday, May 13, 2016 - 01:43 pm:   

Hi Des

We are getting ready to test in a few minutes based on your input.

Thanks for responding quickly.

We will let you know results.

Thanks again.

Ralph
Ralph Leyrer
New member
Username: Rleyrer

Post Number: 4
Registered: 05-2016
Posted on Friday, May 13, 2016 - 01:59 pm:   

Des
We set everything to default and we got 8-bit binary DCS coding of 0x04.

We need to get 7-bit GSM DCS coding of 0.
Ralph Leyrer
New member
Username: Rleyrer

Post Number: 5
Registered: 05-2016
Posted on Friday, May 13, 2016 - 02:05 pm:   

DES

To clarify, we are not sure about the value of 4 that we are getting. To match our current NowSMS Production server, we want to 0x00 to be sent as the DCS coding.


I will send you the log files shortly.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5645
Registered: 08-2008
Posted on Friday, May 13, 2016 - 02:10 pm:   

Ralph,

I need to understand the input. What data_coding is it using? How is it arriving into NowSMS...I assume also SMPP?

Do you have a trace of that?

--
Des
NowSMS Support
Lee Eidson
New member
Username: Leidson

Post Number: 12
Registered: 04-2014
Posted on Friday, May 13, 2016 - 02:21 pm:   

Hi Des

You're correct - all SMPP. We just sent a collection of files to you via email, with packet captures at startup and during a test, the in/out log files and the ini file.
Ralph Leyrer
New member
Username: Rleyrer

Post Number: 6
Registered: 05-2016
Posted on Friday, May 13, 2016 - 02:22 pm:   

We can do a WebEx if you so desire.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5646
Registered: 08-2008
Posted on Friday, May 13, 2016 - 03:01 pm:   

Hi Ralph,

I've been looking through the logs and traces, and some of the messages are arriving into NowSMS with data_coding=4, with content that is definitely not text-based.

I used a Wireshark filter of smpp.data_coding != 0 to quickly find them.

NowSMS seems to delivering the message in the same format in which the message was received. Same data_coding, same message content.

You mentioned earlier that this old system only understands data_coding values of 0 and 2. Maybe you need to configure NowSMS to convert data_coding from 4 to 2 for this system. BinaryDCS=2 under the [SMPP] header in SMSGW.INI would do this.

--
Des
NowSMS Support
Lee Eidson
New member
Username: Leidson

Post Number: 13
Registered: 04-2014
Posted on Friday, May 13, 2016 - 03:33 pm:   

Hi Des

We'll give it a try and let you know. You pointed us in this direction earlier and we missed it. The link you provided leads to an even older post (http://support.nowsms.com/discus/messages/1/24851.html) where you gave the same response to Clint Perry....who worked with us in the past and configured the original server that we're replacing. Small world, eh?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5647
Registered: 08-2008
Posted on Friday, May 13, 2016 - 04:06 pm:   

Hi Lee,

I suspected there might be a connection! We rarely have a requirement for BinaryDCS=2.

--
Des
NowSMS Support

Login Login / Register Logout Logout Search Last 30 Days Topics Topics