Support

Use the right channel so the community and maintainers can help quickly.

Questions And Setup Help

Use GitHub Discussions for:

• Quick start help.
• Routing configuration questions.
• SMPP bind and provider setup questions.
• Usage patterns and integration ideas.
• General community discussion.

Bugs

Use GitHub Issues for reproducible bugs.

Include:

• Sendium version or Docker tag.
• Steps to reproduce.
• Expected behavior.
• Actual behavior.
• Sanitized credentials.yml, smsg.properties, or routingTable.conf snippets when relevant.
• Relevant log lines from smsg.log, smppclient.log, smppserver.log, or httpapi.log.

Default httpapi.log entries omit request query strings. If your deployment uses a custom HTTP access-log pattern, sanitize any /sendsms query parameters before sharing logs.

SMPP PDU, byte, message, response, and MO diagnostic logs are opt-in because they can contain credentials, phone numbers, and message bodies. Sanitize log.pdus, log.bytes, print.msgs, print.resps, and print.mos output before sharing it.

For message-path investigations, prefer message.* lifecycle trace lines. message.trace.mode = necessary is the default and keeps only message.accepted, message.submitted, message.dlr, and message.deliver.sent; use message.trace.mode = all when route/enqueue/response detail is needed. These logs include IDs, message type, account/system context, and delivery state without including phone numbers or message bodies.

Feature Requests

Use GitHub Discussions for early ideas. Open an issue when the behavior and use case are clear enough to track.

Security Issues

Do not post security vulnerabilities publicly. Email info@sendium.org and read Security Policy.

Before Posting Publicly

Remove:

• Passwords, API keys, and credentials.
• Real system IDs and account IDs.
• Real phone numbers and message bodies.
• Sensitive IP addresses and provider details.