larvit/smpp-js
3
0
Fork 0
Code Issues Pull Requests Actions Activity

Name the retry status by direction, and correct what the held-message decision claims
Test / lint (pull_request) Successful in 28s
Details
Test / test (18) (pull_request) Successful in 31s
Details
Test / test (20) (pull_request) Successful in 30s
Details
Test / test (22) (pull_request) Successful in 31s
Details
Test / test (24) (pull_request) Successful in 30s
Details
Test / test (26) (pull_request) Successful in 37s
Details
Mirror / push (push) Successful in 4s
Details

Browse Source
This commit was merged in pull request #29.
This commit is contained in:
Lilleman auf Larv
2026-09-26 14:53:09 +02:00
parent f2977638f2
commit 42b1239f3d
5 changed files with 28 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+1 -1
View File
@@ -42,7 +42,7 @@
the cap is lost, since its segments were already answered.
- A message arriving while the application holds 1000 unanswered, or 64 MiB of them counted the way
`maxOctets` counts segments, is refused with `ESME_RTHROTTLED` (`ESME_RX_T_APPN` on a
`deliver_sm`), so the peer keeps it and retries. **Call `sendResp()` on every `sms`, multipart
delivery), so the peer keeps it and retries. **Call `sendResp()` on every `sms`, multipart
included**: 1000 left unanswered now stop inbound traffic for up to five minutes, where the oldest
used to be dropped with a warning.
- A `submit_sm` segment the reassembly buffer has no room for is refused with `ESME_RTHROTTLED`,