jasmin
jasmin copied to clipboard
Value (test) size 4 does not match expected 15
Hello,
we are getting this exception when trying pass the message sent to jasmin to upstream SMSC:
2020-03-04 12:04:00 CRITICAL 805 Rejecting SubmitSmPDU[247c20b2-e05f-4914-a498-3187f3e7aede] through [cid:<some cid>] for an unknown error (<type 'exceptions.ValueError'>): Value (test) size 4 does not match expected 15
I traced it to bundled smpp.pdu package, but since it have many jasmin-specific modifications I think it's better to ask here. It looks like jasmin is not capable to resend PDU's where message text is set in message_payload optional parameter or something like that. Please clarify what's wrong here. Message dump is attached.
@farirat any idea?
It's a binary pdu decoding issue, something is not encoded correctly and jasmin cant read it.
You need to have the hex representation of the pdu in the log, share it and i'll take a look
It's a binary pdu decoding issue, something is not encoded correctly and jasmin cant read it.
You need to have the hex representation of the pdu in the log, share it and i'll take a look
I grepped all the logs the only thing is found in default-smpps_01.log.2020-03-04:
:2020-03-04 12:04:00 INFO 805 SMS-MT [uid:username] [cid:connector] [msgid:247c20b2-e05f-4914-a498-3187f3e7aede] [prio:1] [from:7999333XXXX] [to:7999699XXXX] [content:]
content field (where hex representation should go) is empty.
Still the message is here as you can see from the dump. It is put not into message_bytes, but into optional parameter message_payload
instead.
ping?
I have the same problem. According to observations, in 4 cases out of 5, such an exception flies. 1 time out of 4, the message goes through normally. One and the same text can pass, it can not pass. And in the exception, the expected size is always 9. Regardless of the size of the message
Some update: Determined when the failure occurs. If the message is long and ends with a space, an exception is raised.
Stale issue detected, remove stale label or comment or this will be closed soon.
This issue was closed because it has been stalled more than a year with no activity.