Not correctly messages break

Smpp v3.4 client

Moderator: alt

Locked
Goraciy
Posts: 7
Joined: Wed Aug 26, 2009 1:32 pm
Location: Russia

Not correctly messages break

Post by Goraciy » Fri Aug 28, 2009 11:49 am

Hello.
The unpleasant error is found.
If the length of the message is equal 140 byte SmppClient divides such messages on 2, though value of parametre client. ShortMessageMaxBytes it is exposed by default (140).
So, if the message of 140 byte we pay as for 2 that is not so pleasant.
Thanks.
adrianaitken
Posts: 16
Joined: Fri May 08, 2009 1:07 pm
Location: Jersey, UK

Post by adrianaitken » Tue Sep 01, 2009 1:43 pm

I've just had an earful from my marketing department - this is happening to a few thousand messages we've just sent. And their test phones are recieved garbled messages ie it's not linking them up properly after being sent. The strange thing is, 5 test messages were sent and all were OK, then they sent the same message to thousands and it broke :shock:

I'm running the component dated 27 Aug., I might revert back to the previous one to see if it fixes it.
Regards
Adrian

I no longer work so do not use this any more and therefore can not help you with any answers. Bye bye and good luck.
alt
Site Admin
Posts: 985
Joined: Tue Apr 25, 2006 9:45 am

Re: Not correctly messages break

Post by alt » Tue Sep 01, 2009 4:20 pm

Goraciy wrote:If the length of the message is equal 140 byte SmppClient divides such messages on 2
Thank you for your report. Fixed.
Please try last version.
alt
Site Admin
Posts: 985
Joined: Tue Apr 25, 2006 9:45 am

Post by alt » Tue Sep 01, 2009 4:24 pm

adrianaitken wrote:And their test phones are recieved garbled messages ie it's not linking them up properly after being sent.
Can you give an example how it was recieved on the phones?
adrianaitken
Posts: 16
Joined: Fri May 08, 2009 1:07 pm
Location: Jersey, UK

Post by adrianaitken » Wed Sep 02, 2009 8:03 am

alt wrote:
adrianaitken wrote:And their test phones are recieved garbled messages ie it's not linking them up properly after being sent.
Can you give an example how it was recieved on the phones?
Sorry, they're in another bulding to me and have deleted everything.
Regards
Adrian

I no longer work so do not use this any more and therefore can not help you with any answers. Bye bye and good luck.
mukul
Posts: 7
Joined: Tue Oct 06, 2009 8:34 pm

Post by mukul » Wed Oct 07, 2009 8:57 pm

ya the same problem with me also

when the message length is 140 or more its is submitting 2 messages to my smsc. and the message type is binary.

if the length is less then 140 it is okay and type is text


and on the mobile phones the the messages are delivering as 2 binary (8 bit) messages.

i think this problem is with sms data encodings it is always submitting with 8 bit data codings
alt
Site Admin
Posts: 985
Joined: Tue Apr 25, 2006 9:45 am

Post by alt » Wed Oct 14, 2009 8:49 am

mukul,

Can you post here log with sent byte when you submit message 140 bytes lenght?
mukul
Posts: 7
Joined: Tue Oct 06, 2009 8:34 pm

Post by mukul » Mon Nov 02, 2009 12:23 pm

i have pushed a mesaage of 160 char is shoud encode in 140byts but is is exceeeding 140 byts

if i submit 140 char sms it ecodes in 140 byts

i think problem is with data encoding please check

160chars should ne encode in 140 byts

the log is bellow


5:45:11 PM: SmppClient connected
5:45:11 PM: Binding SmppClient for SystemId: mukul
5:45:11 PM: SmppClient bound
5:45:11 PM: Bind result : system is NowSMS with status ESME_ROK
5:45:11 PM: Sending Data: 0000002100000009000000003c25a2d56d756b756c006d756b756c000034000000
5:45:11 PM: Received Data: 0000001c80000009000000003c25a2d54e6f77534d53000210000134
5:45:17 PM: QuerySm for message SAR-++919831856890-73-2-1
5:45:18 PM: QuerySmResp for message SAR-++919831856890-73-2-1 with status SMPPCLIENT_GENERIC_NACK, message state None
5:45:18 PM: Sending Data: 000000cc00000004000000003c25a2d60000006d6b0001012b39313938333138353638393000400000003039313130343035343531363030302b00000000008c050003730201746869732069732061207465787420736d73206f6e6c7920746578742074657374696e672074686973206d65737361676520697320686176696e6720313630206368617261637465727320736f2069742073686f756420626520313430206279747320616e64206f6e6520736d7320627574206973206973206578656564696e672031343020
5:45:18 PM: Received Data: 0000002a80000004000000003c25a2d65341522d2b2b3931393833313835363839302d37332d322d3100
5:45:18 PM: Sending Data: 0000006000000004000000003c25a2d70000006d6b0001012b39313938333138353638393000400000003039313130343035343531363030302b000000000020050003730202627974732e20706c6561736520636865636b206f6b6179206b6b
5:45:18 PM: Received Data: 0000002a80000004000000003c25a2d75341522d2b2b3931393833313835363839302d37332d322d3200
5:45:18 PM: GenericNack received with status ESME_RINVCMDID
5:45:18 PM: Sending Data: 0000002f00000003000000003c25a2d85341522d2b2b3931393833313835363839302d37332d322d310000006d6b00
mukul
Posts: 7
Joined: Tue Oct 06, 2009 8:34 pm

Post by mukul » Mon Nov 09, 2009 6:50 am

please reply
alt
Site Admin
Posts: 985
Joined: Tue Apr 25, 2006 9:45 am

Post by alt » Mon Nov 09, 2009 9:12 am

can you post your code how you create and send these messages.
TANK
Posts: 4
Joined: Tue Apr 06, 2010 12:48 pm

SMPPCLIENT_GENERIC_NACK

Post by TANK » Tue Apr 06, 2010 1:08 pm

Good day

Can someone please tell me what does the message below mean?

SMPPCLIENT_GENERIC_NACK

Your assistance would be appreciated.

Regards.[/quote]
alt
Site Admin
Posts: 985
Joined: Tue Apr 25, 2006 9:45 am

Post by alt » Wed Nov 03, 2010 11:42 am

SMPPCLIENT_GENERIC_NACK means that command is not supported by SMSC. In case above it is QuerySm.
Locked