Repository navigation
Client receiving empty message due to encoding conflict. #252
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.
Activity
guicuton commentedon Apr 4, 2024
Have to check with your SMSC vendor why the handset is not receiving and what kind of encode their bind runs on.
dotsinspace commentedon Apr 5, 2024
Yes found out that date of sm got too old and library starts ab normal behaviour like this one.
@
fdciabdul commentedon Jun 29, 2026
Likely the DCS-decoding bug (#66): the low-nibble mask mis-detects encoding for several data_coding values, producing empty/garbled text. node-smpp-next parses the full DCS byte. Worth a try.
Fork: https://github.com/fdciabdul/node-smpp-next