Client receiving empty message due to encoding conflict.

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.

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.