Spell out the hand-wired ESME's bind, and where a getter-only assignment throws
Mirror / push (push) Has been cancelled
Test / test (18) (pull_request) Successful in 32s
Test / test (20) (pull_request) Successful in 31s
Test / lint (pull_request) Successful in 28s
Test / test (22) (pull_request) Successful in 32s
Test / test (24) (pull_request) Successful in 37s
Test / test (26) (pull_request) Successful in 31s

This commit is contained in:
2026-09-28 04:08:53 +02:00
parent 4bdb1e64b0
commit 2142c2e3bb
3 changed files with 8 additions and 4 deletions
+4 -2
View File
@@ -429,8 +429,10 @@ const { err, pduObj } = await session.send({
end accepted it, on every link it binds. `bindType` is `receiver`, `transceiver` or `transmitter`;
`declaredVersion` is 0-255, or `undefined` where the peer declared none. Anything else returns `err`
and records nothing.
- An ESME records the bind from its `bind_resp`, in `reconnect.onConnected` on every rebind:
`session.bound('transmitter', pduObj.tlvs.sc_interface_version?.tagValue)`.
- An ESME wired by hand sends its own `bind_<bindType>` through `session.send()`, after it is
constructed and again in `reconnect.onConnected`, and records each accepted one with
`session.bound(bindType, pduObj.tlvs.sc_interface_version?.tagValue)`, where `bindType` is the one
it sent and `pduObj` the `bind_resp` that `send()` resolved with.
## Receiving in depth