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

Charge every TLV a held segment carries against the reassembly cap
Test / lint (pull_request) Successful in 24s
Details
Test / test (18) (pull_request) Successful in 38s
Details
Test / test (20) (pull_request) Successful in 32s
Details
Test / test (22) (pull_request) Successful in 32s
Details
Test / test (24) (pull_request) Successful in 32s
Details
Test / test (26) (pull_request) Successful in 32s
Details
Mirror / push (push) Successful in 6s
Details

Browse Source
This commit is contained in:
Lilleman auf Larv
2026-09-25 18:57:10 +02:00
parent 01210e734a
commit 92456b6f6e
4 changed files with 23 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+3
View File
@@ -35,6 +35,9 @@
- An `alert_notification` or an `outbind` from the peer is logged and left unanswered, as SMPP 3.4
gives neither a response. Each one used to emit `sessionError`, `"alert_notification" has no
response command`.
- `maxOctets` charges every TLV a held segment carries for the memory it keeps, empty ones
included. A peer could hold megabytes per segment beyond the cap by sending thousands of empty
TLVs, which it counted as nothing.
- `server()` refuses a `maxOctets` below 1 or not a whole number, `Infinity` included, like its
other limits. `server({ maxOctets: 0 })` used to start and then refuse every multipart message.
- `callback_num`, `callback_num_atag`, `callback_num_pres_ind`, `broadcast_area_identifier` and