PDU/Network error: EOF on receive ESME_RTHROTTLED in submit sm resp

linxGnu / gosmpp

Smpp (3.4) Client Library for Go

Apache License 2.0

155 stars 62 forks source link

PDU/Network error: EOF on receive ESME_RTHROTTLED in submit sm resp #118

Closed parsibox closed 1 year ago

parsibox commented 1 year ago

hi when i send an sms and receive error like ESME_RTHROTTLED client disconnect and say PDU/Network error: EOF

laduchesneau commented 1 year ago

When the libraries decodes the PDU, the submit_sm_resp, the Parse func generate the EOF error and is caught by the check in receivables.go. This will restart the bind.

Looking at your pcap, why is the sequence set to 0 ? Shouldn't your SMSC return the sequence # from the submit_sm pdu ?

laduchesneau commented 1 year ago

Ive copied you submit_sm_resp into PDU_test.go and it fails. I initially thought it was the sequence number being 0, but it looks like its more to do with the command_status.

parsibox commented 1 year ago

i manually set sequence to 0 on submit sm but why pdu test failed?

linxGnu commented 1 year ago

@parsibox It looks to me that above error is throttling from SMSC.

How many messages are you trying to send to SMSC within 1 minute / 1 second?
How does your SMSC's rate limit look like?

parsibox commented 1 year ago

@parsibox It looks to me that above error is throttling from SMSC.

How many messages are you trying to send to SMSC within 1 minute / 1 second?

How does your SMSC's rate limit look like?

yes i know it is throttling error but my question is why this lib can not pars it? it goes unbind and and reconnect when this pdu receive this is a standard pdu for rate limit on submit sm we should get this error and like this error code on submit sm resp without undind and we want to get that error code

laduchesneau commented 1 year ago

Your issue with the bind closing after receiving a response to a failed submit_sm, should be resolved in #119. The PR was included in the latest release, v0.1.9.