Page 1 of 1
return ESME_RINVMSGLEN while sending a message
Posted: Thu Jun 03, 2010 9:27 am
by aallvvii
Hello can some one help me and let me know why i am receiving this message when i send an sms. some time i receive this message and some time i dont. waiting for reply
Thanks
Posted: Sun Jul 04, 2010 8:30 pm
by alt
In order to tell you the reason why you got ESME_RINVMSGLEN I need to see what smpp client has sent.
Please use code from SmppClientDemo
client.evSendData +=new ALT.SMS.SmppClient.SendDataEventHandler(client_evSendData);
...
private void client_evSendData(object sender, byte[] data)
{
AddToLog("Sending Data: "+ByteArrayToHexString(data));
}
and send me log data.
Posted: Mon Jul 05, 2010 2:06 pm
by aallvvii
Dear Alt
thanks for the reply i am sending you the log as you mentioned waitinf for your reply
Regards
aallvvii
5:02:05 PM: Sending Data: 0000001180000005000000000012fc3800
5:02:05 PM: Sending Data: 0000001180000005000000000012fc3800
5:02:36 PM: Sending Data: 000000cc00000004000000000bd8f4ae00050039323737300001013937343335323438373300400000003130303730373035303233363030302b00000008008c050003a9020100480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065
5:02:36 PM: Sending Data: 000000cc00000004000000000bd8f4ae00050039323737300001013937343335323438373300400000003130303730373035303233363030302b00000008008c050003a9020100480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065
5:02:36 PM: Received Data: 00000011800000040000000b0bd8f4ae00
5:02:36 PM: SubmitSmResp received. Status: ESME_RINVDSTADR, Message Id: , Sequence: 198767790
Posted: Mon Jul 05, 2010 2:52 pm
by aallvvii
Sorry i Just Pasted th wrong log i will paste the log you are looking for sorry.
Posted: Mon Jul 05, 2010 4:03 pm
by aallvvii
Dear Alt
Sorry for the incorrect log which i have posted before here is the log which you are looking for. One more thing some times i dont receive this msg but mostly i receive this msg. Thanks for your time. Waiting for your reply and solution.
Regards
aallvvii
7:00:58 PM: Sending Data: 000000cc00000004000000000df1ae7200050039323737300000003937343335323438373300400000003130303730373037303035383030302b00000008008c050003ad030100480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065
7:00:58 PM: Sending Data: 000000cc00000004000000000df1ae7200050039323737300000003937343335323438373300400000003130303730373037303035383030302b00000008008c050003ad030100480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065
7:00:58 PM: Received Data: 0000001180000004000000010df1ae7200
7:00:58 PM: SubmitSmResp received. Status: ESME_RINVMSGLEN, Message Id: , Sequence: 233942642
7:01:04 PM: Sending Data: 000000cc00000004000000000df1ae7500050039323737300000003937343335323438373300400000003130303730373037303130343030302b00000008008c050003ae030100480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065
7:01:04 PM: Sending Data: 000000cc00000004000000000df1ae7500050039323737300000003937343335323438373300400000003130303730373037303130343030302b00000008008c050003ae030100480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065006c006c006f00480065
7:01:04 PM: Received Data: 0000001180000004000000010df1ae7500
7:01:04 PM: SubmitSmResp received. Status: ESME_RINVMSGLEN, Message Id: , Sequence: 233942645
Posted: Tue Jul 06, 2010 2:02 pm
by alt
Your submit_sm messages are ok.
Do you get ESME_RINVMSGLEN when you send short text?
Please try to find out if SMSC supports concatenated messages?
And try SubmitMode.Payload mode.
Posted: Wed Jul 07, 2010 6:40 am
by aallvvii
Dear alt thanks for the quick reply. i did not receive this message when i send short code and yes my smsc support concatenated messages. when i use payload mode i didnt receive and msg on my cell phone. Some time i dont receive this msg (ESME_RINVMSGLEN) while sending concatenated msg but mostly i received this. waiting for your solution thanks
Regards
Waseem
Posted: Wed Jul 07, 2010 7:46 am
by alt
I think you need to ask SMSC side why they return this status for correct messages.
Sometimes, because of network buffer size, SubmitSm packet can be received from network using two read operations. Possible SMSC does not wait when they receive second part of SubmitSm packet and it returns ESME_RINVMSGLEN.
Posted: Wed Jul 07, 2010 10:18 am
by aallvvii
Thanks for you reply. I have figure out one more thing when i select data coding to default the concatenated message is send without error but when i select data coding to UCS2 it give me this error ESME_RINVMSGLEN. Any idea why is this happening with UCS2 data coding?. Waiting for your suggestions.
Regards
aallvvii
Posted: Sun Jul 11, 2010 6:53 pm
by alt
Does SMSC always send this error code when you send message in UCS2 encoding?
Posted: Sun Jul 11, 2010 9:45 pm
by aallvvii
No it does not send this error every time but mostly it send this error.
Posted: Thu Jul 15, 2010 10:56 am
by aallvvii
Any solution to my problem or any suggestions....................
Posted: Thu Jul 15, 2010 5:14 pm
by alt
I don't see any errors in the library.
Try to send wrong packets log to SMSC technician.
Possible they can analyze it and tell you the reason.