opentelecoms-org / jsmpp

SMPP implemented in Java
Apache License 2.0
232 stars 164 forks source link

No request for sequence_number 2 found #166

Open itshoney27 opened 2 years ago

itshoney27 commented 2 years ago

Hi Everyone! My application is able to connect to smpp server However getting below warning and the message is not been delivered.

INFO 253141 --- [ main] i.s.SMSAPPdemo.MultipleSubmitExample : Broadcasting sms INFO 253141 --- [ main] org.jsmpp.session.SMPPSession : Connected from port 39488 to /41.57.87.231:5002 INFO 253141 --- [Worker-29884f84] org.jsmpp.session.SMPPSession : Starting PDUReaderWorker INFO 253141 --- [ main] org.jsmpp.session.SMPPSession : Other side reports SMPP interface version 34 INFO 253141 --- [ main] i.s.SMSAPPdemo.MultipleSubmitExample : Connected with SMPP with system id ITTECH INFO 253141 --- [ main] i.s.SMSAPPdemo.MultipleSubmitExample : Messages submitted, result is org.jsmpp.session.SubmitMultiResult@8de3d1c6 WARN 253141 --- [pool-1-thread-1] o.j.session.state.SMPPSessionBoundTX : No request for sequence_number 2 found WARN 253141 --- [pool-1-thread-1] o.j.session.state.SMPPSessionBoundTX : No request for sequence_number 2 found WARN 253141 --- [pool-1-thread-3] o.j.session.state.SMPPSessionBoundTX : No request for sequence_number 2 found

pmoerenhout commented 2 years ago

The warning occurs if a response is received, whereby the corresponding request is not found. When your submit_multi request is send, a incrementing sequence number is added and stored. Also your EMSE (SMSC) send the response multiple times with the same sequence number. As the there is no answer possible on the submit_multi_resp, the SMSC should consider the response as send and processed.