Works like a charm, a curl request to http://localhost:14000/cgi-bin/sendsms?... creates a sms mo which gets forwarded to client. E.G we send a SMS with coding=0 and content "€" thats what we receive: data: 1b 65 ("€" in gsm7).
But if we do send "€" with coding=2 we receive UTF-8 encoded content: data: e2 82 ac
Same happens for concatenated gsm7 SMS.
We have also tried to write sms mo entries directly to smpp_store table with similar results. I think we tried every combination of coding, charset etc.
Hi there,
we have a little issue that clients do receive sms mo UTF-8 encoded.
We have created a dummy SMSC just for sms mo:
Then we re-route all sms mo to ksmppd:
KSMPPD then calls route.php to get the client who should receive the sms mo:
Works like a charm, a curl request to http://localhost:14000/cgi-bin/sendsms?... creates a sms mo which gets forwarded to client. E.G we send a SMS with coding=0 and content "€" thats what we receive:
data: 1b 65
("€" in gsm7).But if we do send "€" with coding=2 we receive UTF-8 encoded content:
data: e2 82 ac
Same happens for concatenated gsm7 SMS.We have also tried to write sms mo entries directly to smpp_store table with similar results. I think we tried every combination of coding, charset etc.
We're stuck now. Thanks in advance for any help!
BR
CL