Am 14.02.22, 18:01, schrieb akamat sarat:
Dear Users,

We are unable to debug an issue with SMSC having to do with delivery
reports missing from SMSC over smpp bind.
The  connection to SMSC is   working properly according to kannel logs.
No obvious errors are visible in the logs.
But we are missing delivery reports that SMSC is saying were delivered
and ACKd by kannel.
Specifically they are saying that they have 'CDRs state "Delivered
Direct"' and that kannel ACKd the delivery report.
We however cannot see it in kannel access logs or SMSC logs or in any logs.
Having run tcpdumps we cannot locate it either.

Any way to debug this issue that we are missing?
Thanks,
Akamat

Hi Akamat,

what COULD be the case here is that Kannel bearerbox does ACK the deliver_sm PDUs from the SMSC with a corresponding deliver_sm_resp PDU, (so from the SMSCs perspective they are acknowledged), but your DLR message ID setup (or smsc-id patch setup) is configured wrong in Kannel, and the DLR is formally not resolved in bearerbox to the temporary data that is store in the DLR storage. Hence the DLR is "not found", and then not logged to the access-log (in older releases).

Suggesting you run the bearerbox.log (log-file) in DEBUG level (log-level = 0), and then check that you DO see the deliver_sm PDUs from the SMSC.

Additional things to check:

- Make sure you are AWARE of the message ID notation. Some SMSCs use hex in submit_sm_resp PDU, but decimal in the deliver_sm payload (see msg-id-type directive)

- If you splitted the SMPP binds in receiver and transmitter, make sure they have the same 'smsc-id' identifier, otherwise you would receive a DLR on the receive bind that would not resolve correctly from the DLR storage, since the transmitter side used a difference smsc-id tag.

--
Best Regards,
Stipe Tolj

-------------------------------------------------------------------
Düsseldorf, NRW, Germany

Kannel Foundation                 tolj.org system architecture
http://www.kannel.org/            http://www.tolj.org/

st...@kannel.org                  s...@tolj.org
-------------------------------------------------------------------

Reply via email to