Ozeki SMS Gateway Health Check

For On-Premises Installation on Windows Server

The comprehensive health check is performed by Ozeki Engineers in the frames of Ozeki Technical Suppoort quarterly or on user request. If you would like your system checked, please open a technical support ticket with the title "Ozeki SMS Gateway Health Check Request" at myozeki.com

1. System & OS Health

  • 2.1. Windows Server OS version and build are supported and up-to-date.
  • 2.2. All critical Windows security updates and patches installed.
  • 2.3. .NET Framework / .NET 8.0 is installed and updated.
  • 2.4. CPU usage (average & peak) within acceptable limits.
  • 2.5. RAM usage and free memory sufficient for current load.
  • 2.6. Disk space on system drive > 20% free.
  • 2.7. Ozeki installation and data directories have ample free space (≥ 100 GB recommended for logs/DB).
  • 2.8. Disk health (chkdsk / SMART status) is healthy.
  • 2.9. Server uptime reviewed
  • 2.10. Windows Event Logs (System, Application) free of critical errors related to Ozeki.
  • 2.11. Network adapters status and IP configuration correct.
  • 2.12. Server power settings set to High Performance.
  • 2.13. Pagefile configuration appropriate for high memory usage.
  • 2.14. Windows Firewall service is running.
  • 2.15. No unexpected services or processes consuming resources.
  • 2.16. Time synchronization (NTP) active and accurate.

2. Ozeki Service & Process Status

  • 2.1. Ozeki SMS Gateway Windows service is running and set to Automatic.
  • 2.2. Ozeki web GUI accessible via HTTPS (default port 9515).
  • 2.3. Ozeki process memory and CPU consumption normal.
  • 2.4. GUI login successful with admin account.
  • 2.5. No multiple instances of Ozeki processes running.
  • 2.6. All required network ports are assigned to the ozeki process PID (netstat -nao).
  • 2.7. Service recovery options configured (restart on failure).
  • 2.8. Ozeki service account has necessary permissions (Local System or dedicated account).
  • 2.9. Latest Ozeki version installed.
  • 2.10. Data folder backed up for recovery.
  • 2.11. System is Activated. No license expiration warnings.

2. Ozeki Internals

  • 3.1. Submit reference list size (View/submit references).
  • 3.2. Scheduled job list size (View/scheduled jobs).
  • 3.3. Ozeki internal system events (View/Events).
  • 3.4. Reporting database enabled.
  • 3.5. Reporting database size.
  • 3.6. All installed connections are enabled and healthy.
  • 3.7. Message queue size bellow 1000 for each user.
  • 3.8. All created user accounts are enabled and healthy.
  • 3.9. Are there any unused user accounts that could be disabled/deleted.
  • 3.10. Are there any unused connections that could be disabled/deleted.
  • 3.11. Web server component (GUI) responding without delays.
  • 3.12. Folder sizes and file counts in Ozeki Data folder are normal.
  • 3.13. Ozeki internal logs rotated and not filling disk.
  • 3.14. Secure logging enabled (masking sensitive data, such as passwords).

3. Hardware Connections (Modems / GSM / LTE)

The following tests should be performed if Modems, GSM gateways, LTE equipment is connected to Ozeki SMS Gateawy.

  • 4.1. All GSM/LTE modems detected in Ozeki.
  • 4.2. Connection with Android mobile phones are up and healthy
    (separate health check should be performed for each connected Android device).
  • 4.3. Modem connection status = Connected / Polling started.
  • 4.4. SIM card signal strength adequate (≥ 15-20 dB).
  • 4.5. SIM cards registered to network.
  • 4.6. SIM balance / credit checked where applicable.
  • 4.7. Modem firmware up-to-date.
  • 4.8. USB/RS232 port stability verified (no disconnects).
  • 4.9. AT communication is going on flawlessly.
  • 4.10. SMS center (SMSC) numbers correctly configured.
  • 4.11. Encoding (GSM 7-bit / UCS2) settings verified.
  • 4.12. Throughput limits per modem configured properly.
  • 4.13. Concatenated / long SMS handling tested.
  • 4.14. Modem-specific logs reviewed for errors.
  • 4.15. Modem auto-connect configured.
  • 4.16. Redundant modems / failover paths available and tested.
  • 4.17. Physical inspection: Antenna connections secure and properly placed.
  • 4.18. Physical inspection: Data cable is securely connected to both the modem and the compter.
  • 4.19. Physical inspection: Modem power cable securely connected to the modem.
  • 4.20. Physical inspection: Modem power supply temperature check.
  • 4.21. Physical inspection: Modem temperature check.
  • 4.22. Physical inspection: Modem led indicators.

4. IP / SMPP / External Connections

The following tests should be performed for all SMPP, CIMD2, UCP, HTTP connections.

  • 5.1. Link: SMPP connections status = Connected.
  • 5.2. Link: SMPP low level logging shows errors.
  • 5.3. Link: Connection keep-alive and heartbeat settings optimal.
  • 5.4. Link: No connection flapping or frequent reconnects.
  • 5.5. SMPP connection is working for: message submission.
  • 5.6. SMPP connection is working for: message receiving.
  • 5.7. SMPP connection is working for: delivery report receiving.
  • 5.8. Delivery report (DLR) matching working correctly.
  • 5.9. Message throughput (MPS) windows size is configured properly.
  • 5.10. Message throughput (MPS) speed limits are configured properly.
  • 5.11. Message throughput (MPS) per connection is sufficient.
  • 5.12. Message throughput (MPS) Burst test with 20 sms to test throttling behavioiur.
  • 5.13. TLS/SSL certificates for secure connections valid.
  • 5.14. Routing: Connection-specific routing rules active.
  • 5.15. Routing: Failover routes cover the connection and configured and functional.

5. SMS Routing

  • 6.1. Verify the routing table has a default route for outgoing messages.
  • 6.2. Verify the routing table has a default route for incoming messages.
  • 6.3. Verify the routing table has rules to reach all outgoing connections.
  • 6.4. Check each rules filter conditions to make sure they are valid.
  • 6.5. Ensure rule sequence matches priorities (specific prefixes before generic rules).
  • 6.6. Verify if case‑insensitive keyword matching is used (e.g., "INFO" vs. "Info").
  • 6.7. Validate time‑of‑day or day‑of‑week conditions.
  • 6.8. Check inbound source connections match active users or apps.
  • 6.9. Verify every target connection (SMPP, GSM modem, email) exists and is healthy.
  • 6.10. Confirm a backup SMS route exists for primary IP connection failure.
  • 6.11. Open backup rule Advanced menu and verify Backup Condition is enabled.
  • 6.12. Check load balancing routes (connection groups) with mini stress tests (20 sms to see if all routes are utilized).
  • 6.13. Simulate primary connection failure and verify automatic switch to backup.
  • 6.14. Inspect routing log entries for users.
  • 6.15. If required, verify routing restriction (e.g., block international SMS except for authorised users).
  • 6.16. Test message modifications if configured (phone number manipulation, messages text manipulation).
  • 6.17. Check regex rules to make sure they are properly formatted.
  • 6.18. If randomized phone numbers are configured, ensure gateway can pick or randomise Sender ID to avoid blacklisting.
  • 6.19. If HLR is configured: Verify gateway is connected to an active HLR Lookup account.
  • 6.20. If HLR is configured: Test HLR information (on/off, ported, roaming) is used as routing condition.
  • 6.21. Check sample message delivery history and Event log to verify routing steps and errors are recorded.
  • 6.22. Blacklist / whitelist filtering operational.

6. Network, Firewall & Ports

  • 7.1. Required ports open (9515 HTTPS, 9516 websocket, 9508-9509 API, 9550 SMPP, etc.).
  • 7.2. Windows Firewall rules allow Ozeki traffic.
  • 7.3. No port conflicts detected.
  • 7.4. Network bandwidth sufficient for current volume (speed test, okula or google).
  • 7.5. DNS resolution working for any hostname-based connections.
  • 7.6. No unexpected inbound connection attempts in logs.
  • 7.7. VPN / secure tunnel health (if used).
  • 7.8. Rate limiting and QoS policies (if any) reviewed.
  • 7.9. Packet loss and error counters on NICs near zero.

7. Performance & Messaging

  • 8.1. Current messages-per-second (MPS) within system capacity.
  • 8.2. Outbound and inbound message queues empty or low.
  • 8.3. Delivery success rate > 95% for recent traffic.
  • 8.4. Average delivery time within SLA.
  • 8.5. Routing engine performance normal.
  • 8.6. SQL reporting database queries performing well.
  • 8.7. Service restart: Bootup time.
  • 8.8. Service restart: Message persistence and recovery during service restart.
  • 8.9. Message encoding: Long message (concatenated) handling verified.
  • 8.10. Message encoding: Character encoding / special characters processed correctly.
  • 8.11. Performance counters logged and trending reviewed.

8. Database & Logging

The following tests should be performed only if database reporting is configured.

  • 9.1. Reporting database connection healthy.
  • 9.2. No lost messages during temporary DB outage. (If possible to do db shutdown/restart)
  • 9.3. Database tables (ozekimessagein/ozekimessageout) optimized and indexed.
  • 9.4. Database tables number of items is within optimal range.
  • 9.5. Archiving of old messages performed.
  • 9.6. SQL logfile size and growth monitored.
  • 9.7. Database user permissions least-privilege compliant.

9. Security, Backups & Compliance

  • 10.1. Admin and user passwords strength.
  • 10.2. GUI access restricted to trusted IPs in firewall.
  • 10.3. HTTPS certificate valid and not expired.
  • 10.4. No known vulnerabilities in current Ozeki version.
  • 10.5. Configuration and message database backed up recently.
  • 10.6. Backup restore test performed in last quarter.
  • 10.7. Disaster recovery plan documented and tested.
  • 10.8. No unauthorized configuration changes detected.
  • 10.9. SMS content filtering / compliance rules active.

10. Monitoring, Alerts & Maintenance

  • 11.1. Is Ozeki Alarm Installed to notifcy about downtime and system events.
  • 11.2. SNMP / email / SMS alerts configured and tested.
  • 11.3. Integration with external monitoring (Zabbix, SCOM, etc.) healthy.
  • 11.4. Next health check scheduled date.

More information