Diafaan SMS Server uses standards as much as possible and since percent encoding is the standard encoding for URIs, Diafaan SMS Server uses that for all HTTP queries.
The actual encoding of the message depends on the gateway that is used to send the message. Depending on the characters in the message, the settings of the gateway and the value of the message-type parameter, the message will be encoded in the default SMS character set or in UCS16 encoding. Some SMPP servers require another encoding like the ISO 8859 character set and the SMPP Gateway in Diafaan SMS Server can use that too if it is specified in the settings. The specific encoding that is used when the message is sent has very little impact on the send speed of the gateways.
The number of message parts for a long message and the actual message-type that is used to send the message(s) is only available after Diafaan SMS Server has sent the message because it depends on the actual gateway that sent the message. This information is passed on in the 'message_log' HTTP callback.
But most of the smpp gateway they support the utf16 , and our front end and main system built to use the utf16,what i can understand from your answer that we have to convert each message to URI encoding , which i think it will slow down more the smpp speed.
Other thing if we did not use the message-type , then how the http callback will calculate the message parts ?
You can use the Unicode characters directly in the URI or (preferably) use the standard URI percent encoding for the Unicode characters. 063906310628064A is not a correct URI encoding for a Unicode text in a URI, this string can be encoded as %D8%B9%D8%B1%D8%98%D9%8A.
There is no need to set the message-type to sms.unicode. Diafaan SMS Server will automatically use the correct encoding when it sends the message with a GSM Modem Gateway or SMPP Gateway. The message-type should only be set if you want to enforce a specific encoding, even if that means that the message will not be sent correctly or not as efficient as possible.
Hello again henk,
When we are tryo to send unicode message example : 063906310628064A , we are receiving the message on the handset phone also as 063906310628064A not to their original characters .
we have set the message-type=sms.unicode , and we have tried to force the smpp gateway by using MessageType to unicode type in the Advanced settings but still same.
note that our smpp gateway supporting the unicode ucs 16, as we are currently using them.
please advise what is the issue
Most Users Ever Online: 494
Currently Browsing this Page:
Guest Posters: 597
Newest Members:, Henk Helmantel
Administrators: Henk Helmantel: 1263