Member Avatar for static

Hi,
i'm now making a project of sending ,receiving ..with SMS.I think only sending, receivng,includeing error handlin doesn't make my project complete. What do i need to improve my proj.

plz ignore my mistakes. :cheesy:

Thank You

  • 3 Contributors
  • 2 Replies
  • 89 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by veerareddy

Dani AI

Generated

For : sending and receiving plus basic error handling are a solid start. To make the project look complete and useful as a portfolio or coursework piece, treat it like a small production-grade messaging system: define requirements, pick the right transport, and implement message lifecycle, reliability, monitoring, and compliance.

Suggested checklist (each item is a concrete addition to implement):

  • Scope and requirements: expected throughput, one-way vs two-way, international support, latency and delivery guarantees.
  • Transport options and tradeoffs: GSM modem with AT commands (simple, low scale), SMPP to an SMSC (scalable, telecom-grade), or cloud REST gateways (fast to prototype). Pick the one that matches the expected scale.
  • Message handling: support GSM 7-bit and UCS-2/Unicode, implement concatenated SMS reassembly and UDH handling, and normalize character-encoding errors.
  • Delivery lifecycle and persistence: store messages in a DB table with statuses (queued, sent, delivered, failed), external provider IDs, timestamps and retry_count; implement idempotence and exponential backoff retries.
  • Delivery reports and error mapping: consume DLRs, map provider error codes to human-friendly statuses, surface actionable errors.
  • Management UI and features: admin console for queues, templates, scheduling, opt-in/opt-out lists, and rate limits.
  • Testing and monitoring: use provider sandboxes or emulators, add logging, metrics and alerts, and perform load tests.
  • Security and compliance: encrypt PII at rest, use TLS and tokens for APIs, implement consent/opt-in workflows and retention policies.

For : sharing a minimal, sanitized example of the Java stack (Java SE vs Java ME, chosen transport, DB schema) will let others give targeted fixes; remove keys and phone numbers first. For : clarifying the target platform and scale will narrow the best choices above.

Cautions: SMS costs and local regulations matter. If international and Unicode messaging are needed, test actual carrier behavior end-to-end.

Recommended Answers

All 2 Replies

Member Avatar for leelee

Pardon?

Member Avatar for veerareddy

Hi,
now we are also on similar project like this
so first send project code code and description
we will try and rectify ur code
then it is useful both of u
ok
Thank u

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.