Long Message !!

Long Message !! SearchSearch
NowSMS Support Forums ⬆
NowSMS Support - SMS Issues ⬆
Archive through April 12, 2010 ⬆
 ◄    ►
Author Message
Xserver
New member
Username: Xserver

Post Number: 1
Registered: 01-2010
Posted on Sunday, January 24, 2010 - 04:52 pm:   
I am using Now SMS gateway with uplink SMPP Connection to my Service Provider along with SMPP Server.

My problem is :

When i send 320 char message through Now SMS web interface, it is sent perfectly.

But when i send the same message through a Java Based SMPP Client, i get Invalid PDU Error.

I tried setting various options like

MESSAGE_SEGMENT_LENGTH

MESSAGE_MAX_LENGTH_HANDLE_BY_SERVER

But nothing works.

I would appreciate any kind of help in sorting my problem out.
Xserver
New member
Username: Xserver

Post Number: 2
Registered: 01-2010
Posted on Sunday, January 24, 2010 - 04:56 pm:   
To Add More :

if (message_length > MESSAGE_MAX_LENGTH_HANDLE_BY_SERVER) smpp client will split message into segment of length =MESSAGE_SEGMENT_LENGTH and send them with SAR

When i define MESSAGE_SEGMENT_LENGTH = 140 and

MESSAGE_MAX_LENGTH_HANDLE_BY_SERVER = 280

Long Message works , but long messages of 281 chars are splited into 3 messages instead of two.

When i increase the MESSAGE_MAX_LENGTH_HANDLE_BY_SERVER to 320 and MSG_SEGMENT to 160, i get invalid PDU from Now SMS Server.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1707
Registered: 08-2008
Posted on Sunday, January 24, 2010 - 06:10 pm:   
Hi,

Without looking at the raw SMPP data, I don't really know what the client is doing.

But my guess is that you want to set the message segment length to 153 for maximum effectiveness. In a multipart text message, the most text you can fit in a single physical segment is 153.

But I don't know what the difference is between the two parameters that you reference.

--
Des
NowSMS Support
Xserver
New member
Username: Xserver

Post Number: 3
Registered: 01-2010
Posted on Sunday, January 24, 2010 - 06:59 pm:   
MESSAGE_MAX_LENGTH_HANDLE_BY_SERVER is the max message length NowSMS can handle.

MESSAGE_SEGMENT_LENGTH is the max message length the SMPP client will send to NowSMS.

Now what i do is simply do :

if actial_msg_mength > MESSAGE_MAX_LENGTH_HANDLE_BY_SERVER then split the message as per MESSAGE_SEGMENT_LENGTH

For Ex.

If Long Message Length = 300 Char.

The SMPP Client will split the message into 140 + 140 + 20 .

So you can see, the 300 char message is sent in 3 parts instead of two.

But when i split the message in 160 char, i see NowSMS returning INVALID PDU.

Maybe, due to the message length is 160 char and message header makes it more long.

What i want to know is that how NowSMS handles long messages.

If i need to send a long message how much i character should be the segmented message and what encoding should i pack if i want to send 320 char message in 2 segments
Xserver
New member
Username: Xserver

Post Number: 4
Registered: 01-2010
Posted on Sunday, January 24, 2010 - 07:02 pm:   
But my guess is that you want to set the message segment length to 153 for maximum effectiveness. In a multipart text message, the most text you can fit in a single physical segment is 153.


As per above quote, if long message is sent then the segment size is 153 + header info.

But when i send a 320 char long message from http, how is the message sent in 2 parts ?

If the max segment size is 153, then a 320 char message should be sent in 153 + 153 + 8

Am i missing something here ?
Xserver
New member
Username: Xserver

Post Number: 5
Registered: 01-2010
Posted on Sunday, January 24, 2010 - 07:20 pm:   
> > > > I will post the SMPPDEBUG.LOG as well as SMSDEBUG.LOG in a short while fo= r > your reference. > > >
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1708
Registered: 08-2008
Posted on Sunday, January 24, 2010 - 07:20 pm:   
320 characters requires 3 messages.

153 + 153 + 14

> [Delete this line and type your message here]
Xserver
New member
Username: Xserver

Post Number: 6
Registered: 01-2010
Posted on Sunday, January 24, 2010 - 07:23 pm:   
2010-01-25 00:47:07,testing,SMSSubmit,+19999999999,127.0.0.1,SAR-+19999999999-b3-2-1.req,Bi nary,Sender=DEMO;Binary=1;UDH=050003B30201;Data=D3B29B9C769F4132180C344487E5A066 793E0F9FCBECF59CAC36CFD76C35D9CC5ECFC96A337B3D27ABCDECF99AAC36B3E76BB2DACC9EAFC9 6A337B4E5EABCDECF99AAC36B3D773B2DACC5ECFC96A337B3D5793CDECF59CAC36B3E76BB2DACC9E 93D76A337BBE26ABCDECF59CAC36B3D773B2DACC5ECFC96A337BBE26ABCDECF59CAC36B3D773
2010-01-25 00:47:07,testing,SMSSubmit,+19999999999,127.0.0.1,SAR-+19999999999-b3-2-2.req,Bi nary,Sender=DEMO;Binary=1;UDH=050003B30202;Data=B2DACC5ECFC9
2010-01-25 00:47:07,testing,SMSSubmit,+19999999999,127.0.0.1,SAR-+19999999999-37-2-2.req,Bi nary,Sender=DEMO;Binary=1;UDH=060804BB370202;Data=6A337B3D279BD5ECF59CAC36B3D773 B2DACC5ECFC96A337B3D279BD56CECBC2CB797E5


This is the SMSDEBUG for a 300 char message. I see something not right .

Can you decipher and let me know where the problem is ?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1709
Registered: 08-2008
Posted on Sunday, January 24, 2010 - 07:30 pm:   
You should also be able to just set the message limits high...submit as a single message and NowSMS will segment it for you.

Where you run into trouble is if you segment but segment too large.
Xserver
New member
Username: Xserver

Post Number: 7
Registered: 01-2010
Posted on Sunday, January 24, 2010 - 07:33 pm:   
Ok.. I can send un-encoded message to NowSMS through my SMPP Client

But

Do i need to enable "Encode Message with 7-bit Encoding" or "Encode Long Message with 7-Bit Encoding" in NowSMS if i am submitting an un-encoded message ?
Xserver
New member
Username: Xserver

Post Number: 8
Registered: 01-2010
Posted on Sunday, January 24, 2010 - 08:20 pm:   
> > > > At last i can send Long message through my SMPP Client. But i am stuck wi= th > 8-bit encoding which segments the message in 140 characters. I tried usin= g > US-ASCII encoding, but messages are shown up as garbage on mobile. > Any light on this issue will save my sleepless nights

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

Post Number: 1710
Registered: 08-2008
Posted on Sunday, January 24, 2010 - 08:50 pm:   
quote:

Do i need to enable "Encode Message with 7-bit Encoding" or "Encode Long Message with 7-Bit Encoding" in NowSMS if i am submitting an un-encoded message ?



This setting pertains to output, not input.

quote:

At last i can send Long message through my SMPP Client. But i am stuck wi= th > 8-bit encoding which segments the message in 140 characters. I tried usin= g > US-ASCII encoding, but messages are shown up as garbage on mobile. > Any light on this issue will save my sleepless nights



The easy answer would be NOT to segment in your client, and let NowSMS segment it.

If you are segmenting it in your client ... then it can make a difference what version of NowSMS you are using. If you are trying to use an old version of NowSMS (v5.51 or earlier), then older versions did expect SMPP clients to use 7-bit packed encoding whenever UDH was present.

Newer versions expect 8-bit encoding after the UDH (but will detect 7-bit packed encoding).

The bottom line is that I don't know what your SMPP client is actually submitting ... the log file above shows the message after some processing ... the SMPPDEBUG.LOG would show the raw SMPP submission.

My advice would be to use the easy way out ... don't segment it, let NowSMS do it.
Xserver
New member
Username: Xserver

Post Number: 9
Registered: 01-2010
Posted on Sunday, January 24, 2010 - 09:30 pm:   
> > Now, i have removed the segmentation from SMPP Client and sending the ful= l > message to NowSMS. Below is the SMPPDEBUG.LOG of the same period >

02:45:08:424 (00000114) 127.0.0.1 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging 02:45:16:734 (00000114) 127.0.0.1 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging 02:45:22:184 (00000114) 127.0.0.1 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging 02:45:25:044 (00000114) 127.0.0.1 --: WaitForResponseSMPP: SMPP Debug: ioctlsocket failed, no data 02:46:31:044 (00000114) 127.0.0.1 --: WaitForResponseSMPP: SMPP Debug: received bind request 02:46:31:044 (00000114) 127.0.0.1 : 28 byte packet 02:46:31:044 (00000114) 127.0.0.1 ->: 00 00 00 1C 80 00 00 09 00 00 00 0= 0 00 00 00 01 02:46:31:044 (00000114) 127.0.0.1 ->: 4E 6F 77 53 4D 53 00 02 10 00 01 34 NowSMS 4 02:46:36:074 (00000114) 127.0.0.1 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging 02:46:41:084 (00000114) 127.0.0.1 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging 02:46:46:094 (00000114) 127.0.0.1 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging 02:46:51:104 (00000114) 127.0.0.1 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging 02:46:56:134 (00000114) 127.0.0.1 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging 02:47:01:144 (00000114) 127.0.0.1 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging 02:47:06:164 (00000114) 127.0.0.1 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging 02:47:11:344 (00000114) 127.0.0.1 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging 02:47:16:494 (00000114) 127.0.0.1 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging 02:47:21:704 (00000114) 127.0.0.1 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging

My SMPP Client Log :

WARNING: Invalid PDU parameter Jan 25, 2010 2:46:57 AM com.baolocvn.SMPPSender sendShortMessage WARNING: Invalid PDU parameter Jan 25, 2010 2:46:57 AM com.baolocvn.SMPPSender sendShortMessage WARNING: Invalid PDU parameter Jan 25, 2010 2:46:57 AM com.baolocvn.SMPPSender sendShortMessage WARNING: Invalid PDU parameter Jan 25, 2010 2:46:57 AM com.baolocvn.SMPPSender sendShortMessage WARNING: Invalid PDU parameter Jan 25, 2010 2:46:57 AM com.baolocvn.SMPPSender sendShortMessage WARNING: Invalid PDU parameter Jan 25, 2010 2:46:57 AM com.baolocvn.SMPPSender sendShortMessage WARNING: Invalid PDU parameter Jan 25, 2010 2:46:57 AM com.baolocvn.SMPPSender sendShortMessage WARNING: Invalid PDU parameter Jan 25, 2010 2:46:57 AM com.baolocvn.SMPPSender sendShortMessage WARNING: Invalid PDU parameter Jan 25, 2010 2:46:57 AM com.baolocvn.SMPPSender sendShortMessage WARNING: Invalid PDU parameter Jan 25, 2010 2:46:57 AM com.baolocvn.SMPPSender sendShortMessage WARNING: Invalid PDU parameter Jan 25, 2010 2:46:57 AM com.baolocvn.SMPPSender sendShortMessage WARNING: Invalid PDU parameter Jan 25, 2010 2:46:58 AM com.baolocvn.SMPPSender sendShortMessage

And Continues !!!!!!!!!

No SMS Received from the user at the particular time as per SMSDEBUG.LOG .....

>
Xserver
New member
Username: Xserver

Post Number: 10
Registered: 01-2010
Posted on Sunday, January 24, 2010 - 09:40 pm:   
>> > When i use segmentation with utf-8 in my SMPP Client, I get the below log= . >

02:53:03:174 (00000114) 127.0.0.1 --: WaitForResponseSMPP: SMPP Debug: received a submit message 02:53:03:174 (00000114) 127.0.0.1 : 41 byte packet 02:53:03:224 (00000114) 127.0.0.1 ->: 00 00 00 29 80 00 00 04 00 00 00 0= 0 00 00 00 02 ) 02:53:03:224 (00000114) 127.0.0.1 ->: 53 41 52 2D 2B 39 31 39 30 30 30 3= 6 36 30 39 39 SAR-+111111111111 02:53:03:224 (00000114) 127.0.0.1 ->: 38 2D 65 37 2D 33 2D 31 00 8-e7-3-1 02:53:03:224 (00000114) 127.0.0.1 --: WaitForResponseSMPP: SMPP Debug: received a submit message 02:53:03:224 (00000114) 127.0.0.1 : 41 byte packet 02:53:03:224 (00000114) 127.0.0.1 ->: 00 00 00 29 80 00 00 04 00 00 00 0= 0 00 00 00 03 ) 02:53:03:224 (00000114) 127.0.0.1 ->: 53 41 52 2D 2B 39 31 39 30 30 30 3= 6 36 30 39 39 SAR-+111111111111 02:53:03:224 (00000114) 127.0.0.1 ->: 38 2D 65 37 2D 33 2D 32 00 8-e7-3-2 02:53:03:234 (00000114) 127.0.0.1 --: WaitForResponseSMPP: SMPP Debug: received a submit message 02:53:03:234 (00000114) 127.0.0.1 : 41 byte packet 02:53:03:234 (00000114) 127.0.0.1 ->: 00 00 00 29 80 00 00 04 00 00 00 0= 0 00 00 00 04 ) 02:53:03:234 (00000114) 127.0.0.1 ->: 53 41 52 2D 2B 39 31 39 30 30 30 3= 6 36 30 39 39 SAR-+111111111111 02:53:03:234 (00000114) 127.0.0.1 ->: 38 2D 65 37 2D 33 2D 33 00 8-e7-3-3 02:53:08:244 (00000114) 127.0.0.1 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging 02:53:12:324 (00000114) 127.0.0.1 ->: 225 byte packet 02:53:12:324 (00000114) 127.0.0.1 ->: 00 00 00 E1 00 00 00 05 00 00 00 0= 0 00 00 10 4E N 02:53:12:324 (00000114) 127.0.0.1 ->: 57 4D 54 00 01 01 39 31 39 30 30 3= 0 36 36 30 39 WMT 1111111111 02:53:12:324 (00000114) 127.0.0.1 ->: 39 38 00 00 01 54 4D 2D 44 45 4D 4= F 00 04 00 00 11 DEMO 02:53:12:324 (00000114) 127.0.0.1 ->: 00 00 00 00 00 00 88 69 64 3A 53 4= 1 52 2D 2B 39 id:SAR-+1 02:53:12:324 (00000114) 127.0.0.1 ->: 31 39 30 30 30 36 36 30 39 39 38 2= D 65 37 2D 33 11111111111-e7-3 02:53:12:324 (00000114) 127.0.0.1 ->: 2D 32 20 73 75 62 3A 30 30 31 20 6= 4 6C 76 72 64 -2 sub:001 dlvrd 02:53:12:324 (00000114) 127.0.0.1 ->: 3A 30 30 31 20 73 75 62 6D 69 74 2= 0 64 61 74 65 :001 submit date 02:53:12:324 (00000114) 127.0.0.1 ->: 3A 31 30 30 31 32 35 30 32 34 39 2= 0 64 6F 6E 65 :1001250249 done 02:53:12:324 (00000114) 127.0.0.1 ->: 20 64 61 74 65 3A 31 30 30 31 32 3= 5 30 32 34 39 date:1001250249 02:53:12:324 (00000114) 127.0.0.1 ->: 20 73 74 61 74 3A 44 45 4C 49 56 5= 2 44 20 65 72 stat:DELIVRD er 02:53:12:324 (00000114) 127.0.0.1 ->: 72 3A 30 30 30 20 74 65 78 74 3A 6= C 6B 73 64 6A r:000 text:lksdj 02:53:12:324 (00000114) 127.0.0.1 ->: 66 6C 6B 73 64 6A 66 6C 6B 73 64 6= A 66 6C 6B 04 flksdjflksdjflk 02:53:12:324 (00000114) 127.0.0.1 ->: 27 00 01 02 00 1E 00 19 53 41 52 2= D 2B 39 31 39 ' SAR-+111 02:53:12:324 (00000114) 127.0.0.1 ->: 30 30 30 36 36 30 39 39 38 2D 65 3= 7 2D 33 2D 32 111111111-e7-3-2 02:53:12:324 (00000114) 127.0.0.1 ->: 00 02:53:13:734 (00000114) 127.0.0.1 --: SMPPServerSubmitMessage: Got an SMP= P response 02:53:13:734 (00000114) 127.0.0.1
Xserver
New member
Username: Xserver

Post Number: 11
Registered: 01-2010
Posted on Sunday, January 24, 2010 - 10:00 pm:   
> > > > When i use encoding as US-ASCII I get the below logs >

03:16:38:314 (00000114) 127.0.0.1 --: WaitForResponseSMPP: SMPP Debug: received a submit message 03:16:38:314 (00000114) 127.0.0.1 : 41 byte packet 03:16:38:314 (00000114) 127.0.0.1 ->: 00 00 00 29 80 00 00 04 00 00 00 0= 0 00 00 00 02 ) 03:16:38:314 (00000114) 127.0.0.1 ->: 53 41 52 2D 2B 39 31 39 30 30 30 3= 6 36 30 39 39 SAR-+11111111111 03:16:38:314 (00000114) 127.0.0.1 ->: 38 2D 62 36 2D 31 2D 31 00 1-b6-1-1 03:16:38:324 (00000114) 127.0.0.1 --: WaitForResponseSMPP: SMPP Debug: received a submit message 03:16:38:324 (00000114) 127.0.0.1 : 41 byte packet 03:16:38:324 (00000114) 127.0.0.1 ->: 00 00 00 29 80 00 00 04 00 00 00 0= 0 00 00 00 03 ) 03:16:38:324 (00000114) 127.0.0.1 ->: 53 41 52 2D 2B 39 31 39 30 30 30 3= 6 36 30 39 39 SAR-+11111111111 03:16:38:324 (00000114) 127.0.0.1 ->: 38 2D 62 37 2D 31 2D 31 00 1-b7-1-1 03:16:38:324 (00000114) 127.0.0.1 --: WaitForResponseSMPP: SMPP Debug: received a submit message 03:16:38:324 (00000114) 127.0.0.1 : 41 byte packet 03:16:38:334 (00000114) 127.0.0.1 ->: 00 00 00 29 80 00 00 04 00 00 00 0= 0 00 00 00 04 ) 03:16:38:334 (00000114) 127.0.0.1 ->: 53 41 52 2D 2B 39 31 39 30 30 30 3= 6 36 30 39 39 SAR-+11111111111 03:16:38:334 (00000114) 127.0.0.1 ->: 38 2D 38 38 2D 33 2D 33 00 1-88-3-3 03:16:43:344 (00000114) 127.0.0.1 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging 03:16:46:404 (00000114) 127.0.0.1 ->: 225 byte packet 03:16:46:404 (00000114) 127.0.0.1 ->: 00 00 00 E1 00 00 00 05 00 00 00 0= 0 00 00 10 83 03:16:46:404 (00000114) 127.0.0.1 ->: 57 4D 54 00 01 01 39 31 39 30 30 3= 0 36 36 30 39 WMT 9190006609 03:16:46:404 (00000114) 127.0.0.1 ->: 39 38 00 00 01 54 4D 2D 44 45 4D 4= F 00 04 00 00 98 DEMO 03:16:46:404 (00000114) 127.0.0.1 ->: 00 00 00 00 00 00 88 69 64 3A 53 4= 1 52 2D 2B 39 id:SAR-+1 03:16:46:404 (00000114) 127.0.0.1 ->: 31 39 30 30 30 36 36 30 39 39 38 2= D 62 37 2D 31 11111111111-b7-1 03:16:46:404 (00000114) 127.0.0.1 ->: 2D 31 20 73 75 62 3A 30 30 31 20 6= 4 6C 76 72 64 -1 sub:001 dlvrd 03:16:46:404 (00000114) 127.0.0.1 ->: 3A 30 30 31 20 73 75 62 6D 69 74 2= 0 64 61 74 65 :001 submit date 03:16:46:404 (00000114) 127.0.0.1 ->: 3A 31 30 30 31 32 35 30 33 31 33 2= 0 64 6F 6E 65 :1001250313 done 03:16:46:404 (00000114) 127.0.0.1 ->: 20 64 61 74 65 3A 31 30 30 31 32 3= 5 30 33 31 33 date:1001250313 03:16:46:404 (00000114) 127.0.0.1 ->: 20 73 74 61 74 3A 44 45 4C 49 56 5= 2 44 20 65 72 stat:DELIVRD er 03:16:46:404 (00000114) 127.0.0.1 ->: 72 3A 30 30 30 20 74 65 78 74 3A 3= 9 32 37 33 75 r:000 text:9273u 03:16:46:404 (00000114) 127.0.0.1 ->: 75 39 32 37 33 75 75 39 32 37 73 3= 5 75 39 32 04 u9273uu927s5u92 03:16:46:404 (00000114) 127.0.0.1 ->: 27 00 01 02 00 1E 00 19 53 41 52 2= D 2B 39 31 39 ' SAR-+111 03:16:46:404 (00000114) 127.0.0.1 ->: 30 30 30 36 36 30 39 39 38 2D 62 3= 7 2D 31 2D 31 111111111-b7-1-1 03:16:46:404 (00000114) 127.0.0.1 ->: 00 03:16:47:764 (00000114) 127.0.0.1 --: SMPPServerSubmitMessage: Got an SMP= P response 03:16:47:764 (00000114) 127.0.0.1 : 221 byte packet 03:16:52:434 (00000114) 127.0.0.1 ->: 00 00 00 DD 00 00 00 05 00 00 00 0= 0 00 00 10 84 03:16:52:434 (00000114) 127.0.0.1 ->: 57 4D 54 00 01 01 39 31 39 30 30 3= 0 36 36 30 39 WMT 1111111111 03:16:52:434 (00000114) 127.0.0.1 ->: 39 38 00 00 01 54 4D 2D 44 45 4D 4= F 00 04 00 00 11 DEMO 03:16:52:434 (00000114) 127.0.0.1 ->: 00 00 00 00 00 00 84 69 64 3A 53 4= 1 52 2D 2B 39 id:SAR-+1 03:16:52:434 (00000114) 127.0.0.1 ->: 31 39 30 30 30 36 36 30 39 39 38 2= D 38 38 2D 33 11111111111-88-3 03:16:52:434 (00000114) 127.0.0.1 ->: 2D 33 20 73 75 62 3A 30 30 31 20 6= 4 6C 76 72 64 -3 sub:001 dlvrd 03:16:52:434 (00000114) 127.0.0.1 ->: 3A 30 30 31 20 73 75 62 6D 69 74 2= 0 64 61 74 65 :001 submit date 03:16:52:434 (00000114) 127.0.0.1 ->: 3A 31 30 30 31 32 35 30 33 31 33 2= 0 64 6F 6E 65 :1001250313 done 03:16:52:434 (00000114) 127.0.0.1 ->: 20 64 61 74 65 3A 31 30 30 31 32 3= 5 30 33 31 33 date:1001250313 03:16:52:434 (00000114) 127.0.0.1 ->: 20 73 74 61 74 3A 44 45 4C 49 56 5= 2 44 20 65 72 stat:DELIVRD er 03:16:52:434 (00000114) 127.0.0.1 ->: 72 3A 30 30 30 20 74 65 78 74 3A 6= B 6A 73 64 6E r:000 text:kjsdn 03:16:52:434 (00000114) 127.0.0.1 ->: 64 6A 73 58 73 65 72 76 65 72 20 0= 4 27 00 01 02 djsXserver ' 03:16:52:434 (00000114) 127.0.0.1 ->: 00 1E 00 19 53 41 52 2D 2B 39 31 3= 9 30 30 30 36 SAR-+1111111 03:16:52:434 (00000114) 127.0.0.1 ->: 36 30 39 39 38 2D 38 38 2D 33 2D 3= 3 00 11111-88-3-3 03:16:53:764 (00000114) 127.0.0.1 --: SMPPServerSubmitMessage: Got an SMP= P response 03:16:53:764 (00000114) 127.0.0.1 : 225 byte packet 03:16:56:824 (00000114) 127.0.0.1 ->: 00 00 00 E1 00 00 00 05 00 00 00 0= 0 00 00 10 85 03:16:56:824 (00000114) 127.0.0.1 ->: 57 4D 54 00 01 01 39 31 39 30 30 3= 0 36 36 30 39 WMT 1111111111 03:16:56:824 (00000114) 127.0.0.1 ->: 39 38 00 00 01 54 4D 2D 44 45 4D 4= F 00 04 00 00 11 DEMO 03:16:56:824 (00000114) 127.0.0.1 ->: 00 00 00 00 00 00 88 69 64 3A 53 4= 1 52 2D 2B 39 id:SAR-+1 03:16:56:824 (00000114) 127.0.0.1 ->: 31 39 30 30 30 36 36 30 39 39 38 2= D 62 36 2D 31 11111111111-b6-1 03:16:56:824 (00000114) 127.0.0.1 ->: 2D 31 20 73 75 62 3A 30 30 31 20 6= 4 6C 76 72 64 -1 sub:001 dlvrd 03:16:56:824 (00000114) 127.0.0.1 ->: 3A 30 30 31 20 73 75 62 6D 69 74 2= 0 64 61 74 65 :001 submit date 03:16:56:824 (00000114) 127.0.0.1 ->: 3A 31 30 30 31 32 35 30 33 31 33 2= 0 64 6F 6E 65 :1001250313 done 03:16:56:824 (00000114) 127.0.0.1 ->: 20 64 61 74 65 3A 31 30 30 31 32 3= 5 30 33 31 33 date:1001250313 03:16:56:824 (00000114) 127.0.0.1 ->: 20 73 74 61 74 3A 44 45 4C 49 56 5= 2 44 20 65 72 stat:DELIVRD er 03:16:56:824 (00000114) 127.0.0.1 ->: 72 3A 30 30 30 20 74 65 78 74 3A 6= 9 32 37 72 34 r:000 text:i27r4 03:16:56:824 (00000114) 127.0.0.1 ->: 77 33 50 19 59 18 50 31 74 30 79 7= 0 31 7A 32 04 w3P Y P1t0yp1z2 03:16:56:824 (00000114) 127.0.0.1 ->: 27 00 01 02 00 1E 00 19 53 41 52 2= D 2B 39 31 39 ' SAR-+111 03:16:56:824 (00000114) 127.0.0.1 ->: 30 30 30 36 36 30 39 39 38 2D 62 3= 6 2D 31 2D 31 111111111-b6-1-1 03:16:56:824 (00000114) 127.0.0.1 ->: 00 03:16:58:164 (00000114) 127.0.0.1 --: SMPPServerSubmitMessage: Got an SMP= P response 03:16:58:164 (00000114) 127.0.0.1 I receive 3 Message on my mobile , The first 2 part are garbage. The last > message shows remaining valid text of 15 chars. > >
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1712
Registered: 08-2008
Posted on Monday, January 25, 2010 - 03:33 pm:   
I'm sorry, it does not work well when you post logs via e-mail.

All I can extract out of this mess is submit responses that NowSMS is sending back to your client.

It doesn't show me what you're submitting to NowSMS, so I have no way of knowing what that data is ... or how it is formatted. So I can't tell you why it is not being sent out the way you expect it to be.

I would reiterate my previous suggestion ... set the size limits high so that you are not segmenting the data, and just let NowSMS segment it.

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

Post Number: 1713
Registered: 08-2008
Posted on Monday, January 25, 2010 - 03:41 pm:   
I'm sorry, it does not work well when you post logs via e-mail.

All I can extract out of this mess is submit responses that NowSMS is sending back to your client.

It doesn't show me what you're submitting to NowSMS, so I have no way of knowing what that data is ... or how it is formatted. So I can't tell you why it is not being sent out the way you expect it to be.

I would reiterate my previous suggestion ... set the size limits high so that you are not segmenting the data, and just let NowSMS segment it.

--
Des
NowSMS Support
Xserver
New member
Username: Xserver

Post Number: 12
Registered: 01-2010
Posted on Monday, January 25, 2010 - 05:00 pm:   
> > > > I have attached the Logs. > > >
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1716
Registered: 08-2008
Posted on Monday, January 25, 2010 - 07:40 pm:   
As I stated ... it doesn't work when you post the logs via e-mail.

You need to go to the forum link to attach them.
Xserver
New member
Username: Xserver

Post Number: 13
Registered: 01-2010
Posted on Tuesday, January 26, 2010 - 06:09 am:   
text/plain
NowSMS.txt (24.5 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1719
Registered: 08-2008
Posted on Tuesday, January 26, 2010 - 04:23 pm:   
I'm sorry that this is taking so long to resolve.

Maybe I'm not asking the right questions, because I don't think I understand what the problem is.

I don't understand the overall logic flow.

Before I ask some questions to try to fix my understanding ...

Here's what I see in your logs:

quote:

WARNING: Invalid PDU parameter
Jan 25, 2010 2:46:57 AM com.baolocvn.SMPPSender sendShortMessage



That's an issue with the client. I don't know how the client software that you are using works, but if the short_message field is longer than 254 characters, you need to use the message_payload TLV parameter instead. Some implementations do that automatically. I see your client uses TLV for segmentation parameters, so it probably has an option to support message_payload.

quote:

When i use segmentation with utf-8 in my SMPP Client...



DO NOT use UTF-8 in an SMPP client. UTF-8 is not a character set supported by SMPP. Use UCS2 (16-bit Unicode) with data_coding = 8, or iso-8859-1 with data_coding = 3, or the GSM character set with data_coding = 1. (It is also very common to use data_coding = 0 for the SMSC default. The default for NowSMS is the GSM character set in this scenario.)

That said, it looks like you're using all ASCII text with data_coding=0, so you should be fine. The only issue is that it is segmented at 140.

quote:

When i use encoding as US-ASCII I get the below logs



Ah ... now I see your problem.

You're using 16-bit value for sar_msg_ref_num. In this case, your text size limit is 152.

Use a sar_msg_ref_num value of 0xFF (255) or less, and you'll be ok with the maximum 153 byte limit.

That said, we did make some changes recently for scenarios like this ... where if an SMPP message is segmented wrong, we go ahead and try to forward it anyway ... and also where a 16-bit segment reference number is downgraded to an 8-bit reference number.

The latest interim version of NowSMS is at http://www.nowsms.com/download/nowsms20100119.zip, if you want to try it.

But the maximum compatibility solution would be to either use an 8-bit value for the segment reference number, or use a segment size of 152. Using a segment size of 153 requires a segment reference number that can fit into a single byte.

If this doesn't resolve your issues, then I'd like to see debug logs that show both input into NowSMS and output from it. I think that's the part that I'm missing ... I don't know the outbound SMSC configuration.

--
Des
NowSMS Support
Search Search Search Last 30 Days Login / Register Logout

NowSMS Technical Bulletins
Read more