Say what a peer did with each receipt segment, and leave no drop unlogged

2026-09-01 17:59:37 +02:00
parent 67c0402def
commit 61985fb914
7 changed files with 113 additions and 36 deletions
@@ -351,7 +351,8 @@ const { err, pduObj } = await session.send({
 A send issued while the link is down waits for the reconnect instead of failing, and goes out once
 the new link is bound — up to `responseTimeout`, after which it gives up having sent nothing. A
 request already on the wire is the other case: the SMSC may have taken it and lost only the response,
-so it fails, and `sendSms()` counts it in `unanswered`, whether the link dropped under it, the peer
+so it fails, and `sendSms()` and `sms.sendDlr()` count it in `unanswered`, whether the link dropped
+under it, the peer
 never answered in time, or you aborted it after it went out. Neither applies with `reconnect: false`,
 where a drop ends the session and every send after it is refused.