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

Error while connecting to server PDU_STATUS 15

Open
#239 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
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, node.js
Domain
networking

Research direction

Start with the shown Node.js entry point, especially session.on('connect') and the bind_transceiver call. Compare the reported bind_transceiver_resp command_status 15 with the SMPP protocol and the library's bind handling. Done means identifying whether the library or connection parameters cause the failure and documenting a reproducible resolution.

Written by the indexing model from the issue text.

Description

hello i am trying to connect to smpp and i got this error

PDU {
command_length: 16,
command_id: 2147483657,
command_status: 15,
sequence_number: 1,
command: 'bind_transceiver_resp'
}
the same parameters work on another app which is developed with java netbeans

i try to develop app with new tech nodejs and probleming is not solvinf may be i should ad system_type="SMPP"
but still not work

const smpp = require('smpp');
const session = new smpp.Session({host: '********', port: ***});
let isConnected = false
session.on('connect', () => {
isConnected = true;
console.log('is connected')
session.bind_transceiver({
system_id: '',
password: '
',

}, (pdu) => {
if (pdu.command_status == 0) {
console.log('Successfully bound')
}
else {
console.log(pdu)
}

})
})

session.on('error', error => {
console.log('smpp error', error)
isConnected = false;
});

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.