7 Ways Ozeki Message Server Improves Enterprise SMS Workflows

Troubleshooting Ozeki Message Server: Common Issues and Fixes

Below are common problems with Ozeki Message Server (OMS), likely causes, and step-by-step fixes. Assume OMS version is recent; if you need commands or UI steps for a specific version, say which one.

1. SMS not sending

• Likely causes: incorrect SMS gateway/SMPP configuration, network/firewall blocking, invalid credentials, insufficient account credits.
• Fix steps:
  1. Check gateway settings — in OMS Web GUI, open the relevant SMS gateway connection and verify host, port, system id, password and encoding.
  2. Test connectivity — from the OMS server run telnet gateway_host gateway_port (or nc -vz) to verify TCP connectivity.
  3. Confirm credentials — contact the gateway provider or check the provider portal for correct credentials and account status.
  4. Inspect logs — in OMS check the message log and gateway log for error codes (e.g., SMPP bind failure); match codes to provider docs.
  5. Check firewall/NAT — ensure outbound port is allowed and NAT preserves source IP if provider requires it.
  6. Retry and monitor — restart the gateway connection in OMS and send a test SMS.

2. Messages stuck in queue

• Likely causes: gateway unavailable, throttling, message format issues, database lock.
• Fix steps:
  1. Open OMS Queues — identify messages stuck and note timestamps and error fields.
  2. Verify gateway status — if the gateway is offline, start/rebind it.
  3. Look for throttling — providers return rate-limit responses; reduce send rate or request higher throughput.
  4. Validate message content — remove unsupported characters or long concatenated payloads and retry.
  5. Check OMS database and service health — ensure the database isn’t full and the OMS service has resources; restart service if necessary.
  6. Requeue or resend — use OMS admin actions to requeue or delete problematic messages.

3. Delivery reports missing or delayed

• Likely causes: DR not enabled, provider not sending DRs, incorrect DR route mapping, time sync issues.
• Fix steps:
  1. Enable DRs — confirm delivery report (DLR) settings are enabled for the gateway and message routes.
  2. Confirm provider support — check with provider whether they supply DLRs and which SMPP TLVs are used.
  3. Map DLRs correctly — ensure OMS route is configured to accept and map incoming DLRs to the original message IDs.
  4. Check timestamps and NTP — ensure server clock is accurate; large clock drift can cause confusion in logs.
  5. Inspect logs — search for incoming DLR PDUs and any reject codes.

4. Authentication or bind failures (SMPP)

• Likely causes: wrong credentials, wrong system type, IP blocking, unsupported protocol version.
• Fix steps:
  1. Verify credentials and system type — double-check system id, password, and system type fields.
  2. Confirm allowed IPs — ensure provider has your server IP whitelisted if required.
  3. Protocol compatibility — check if provider requires SMPP v3.4 vs v3.3 or specific TLVs; adjust OMS settings.
  4. Check simultaneous binds limit — providers often limit binds per account; close extra binds.
  5. Review provider error codes — check OMS logs for SMPP bind_resp status and act accordingly.

5. Unicode or character encoding problems

• Likely causes: wrong data encoding, using GSM 03.38 characters outside set, incorrect UCS2 handling.
• Fix steps:
  1. Set correct encoding — for non-Latin scripts set message data coding to UCS2 in OMS.
  2. Test with sample text — send a short test containing the problematic characters.
  3. Check segmentation — long UCS2 messages split differently; verify concatenation headers are supported by the provider.
  4. Adjust message length handling — configure OMS to calculate and segment messages correctly for selected encoding.

6. Web GUI inaccessible or slow

• Likely causes: server resource exhaustion, Java issues, browser caching, outdated Java runtime.
• Fix steps:
  1. Restart OMS service — simple restart often resolves transient UI hangs.
  2. Check server resources — monitor CPU, memory, disk I/O; increase resources or clear logs if full.
  3. Update Java — ensure compatible Java runtime is installed per OMS requirements.
  4. Clear browser cache — test in incognito or different browser.
  5. Review OMS logs — look for webserver or application errors.

7. Database connection errors

• Likely causes: DB server down, credentials changed, network, schema mismatch after upgrade.
• Fix steps:
  1. Verify DB service — ensure DB is running and reachable from OMS server.
  2. Test connection — use DB client with OMS credentials to connect.
  3. Check credentials and JDBC string — confirm connection string, port, username, password.
  4. Review schema/version — after upgrades ensure DB schema migration completed.
  5. Restore backups if corrupted — follow DB restore best practices.

8. SSL/TLS connection failures

• Likely causes: expired certs, mismatched hostnames, unsupported cipher suites.
• Fix steps:
  1. Verify certificates — check expiry and validity chain; renew if needed.
  2. Confirm hostname — ensure gateway’s certificate matches the host you connect to.
  3. Enable compatible ciphers — update Java crypto settings if needed.
  4. Test with openssl — openssl s_client -connect host:port -showcerts to inspect.

Useful diagnostic checklist

• Logs: review OMS message, gateway, and system logs first.
• Connectivity: test TCP connectivity to gateways and DB.
• Credentials: verify provider accounts and credentials.
• Provider status: confirm provider service status and any maintenance.
• Resources: check server CPU, memory, disk.
• Time: ensure NTP is running and time is correct.

If you want, I can generate exact command examples, sample log searches, or a troubleshooting checklist tailored to your OMS version and OS — tell me the OS and OMS version.