Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client receiving empty message due to encoding conflict. #252

Open
dotsinspace opened this issue Mar 28, 2024 · 2 comments
Open

Client receiving empty message due to encoding conflict. #252

dotsinspace opened this issue Mar 28, 2024 · 2 comments

Comments

@dotsinspace
Copy link

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.

@guicuton
Copy link

guicuton commented 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
Copy link
Author

Yes found out that date of sm got too old and library starts ab normal behaviour like this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants