InetLab

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.

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

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

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.

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?

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.

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

mukul,

Can you post here log with sent byte when you submit message 140 bytes lenght?

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

please reply

can you post your code how you create and send these messages.

Good day

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

SMPPCLIENT_GENERIC_NACK

Your assistance would be appreciated.

Regards.[/quote]

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