Skip to main content
A server is a listener your customers bind in to. Keys below are set as outSms.instance.<name>.<key>, with outSms.default.<key> as the fallback tier — see Property tiers. Every worker also has the base settings.

Ports and connections

A listener that cannot take its port does not stop the gateway. It logs and the rest keeps running, which is right for a multi-listener deployment and surprising the first time — check /ops/health rather than assuming a clean start means every listener is up.

TLS

Proxy protocol

Per-account defaults

Applied to every account binding here unless the credential overrides them.
conf.maxRate.default and the REST ceiling smsg.restapi.maxRate.default do not track each other. Set both when the limit is meant to be gateway-wide — see Limits.

Inbound messages (MO)

Empty mo.owner.default means nowhere. The listener logs message.mo.unmapped and consumes the message rather than guessing an owner. That is deliberate — delivering a stranger’s inbound message to the wrong customer is worse than dropping it — but it means unmapped MO traffic disappears quietly unless you watch for that log line.

Receipts, addressing and encoding

TLVs, whitelisting and products

See Whitelisting and Limits.

Threads

Diagnostics

message.trace.mode appears in the per-instance table but is global only — an outSms.instance.<name>.message.trace.mode is never read. Set it unprefixed. See Logging.