Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Client receiving empty message due to encoding conflict.

Open
#252 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
javascript, node.js
Domain
api, backend

Research direction

The report does not identify a source file, test, reproducible message, or specific expected behavior. Start by reproducing the accepted message under the reported GSM7 and encoding conditions, then trace the client/server encoding path and add a regression test once the failure and correct delivery behavior are confirmed.

Written by the indexing model from the issue text.

Description

i am using this library...even i am not doing anything much PDU..instead of grabbing information...no encoding nothing...and library is default to GSM7...why client is complaining about no message on his side..leaving every message in ACCEPT...sometimes message have wierd characters.

Dominant language
JavaScript
Stars
434
Forks
194
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from farhadi/node-smpp

All issues in farhadi/node-smpp

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.