Skip to main content
June 22, 2006
Answered

ColdFusion SMS Unicode

  • June 22, 2006
  • 2 replies
  • 2462 views
Hi All,

Has anyone trying sending SMS using CF SMS Gateway in unicode?
Basically I did all the documentation said about setting the dataCoding to 8
and sending the actual text to the server (Clickatell SMPP Gateway).
If I send it to Australia it's easily working.

But for some destination such as china and korea, Clickatell doesn't support for setting up the sender id field. (which is a bit stupid i think, because i'm only using normal mobile phone number and they don't support it). That means the company will set up the sender id for me. (and that's only for some provider)

This is however brings me another problem such as, I don't know which provider my clients are belong to. The weird thing is when I asked for the delivery receipt from the server it gives me delivery back with the dataCoding 0 and err = 1 (message length is invalid). This is also happens even though I send only about 6 or 7 characters long (unicode).

Any help will be greatly appreciated.



This topic has been closed for replies.
Correct answer
Thanks for the reply Paul.

The two messages that i was talking about was actually a mistake. I was on the phone with a really bad connection and I found out that Clickatell tech support guy was talking about the submit_sm_response and deliver_sm, which from what I heard at that time like "Our SMPP gateway send two messages to your end, and maybe you mistakenly understand them".

About "stat:REJECTD err:1" is truly that Clickatell's gateway rejected our SMS. But basically they said they cannot give me a specific error code because of various reason might cause the rejection and err = 1 means it is an error. They also said that at their end, they probably can supply more meaningful error code but not all error code can be identified.

Well, at least I can start the integration test with my app.

Thanks for your help Paul.

2 replies

Participant
July 24, 2023

Hello,

I understand the challenges you are facing while trying to send SMS using CF SMS Gateway with Unicode characters. It seems that Clickatell's SMPP Gateway has some limitations, especially for certain destinations like China and Korea where they don't support setting up the sender ID field for normal mobile phone numbers.

Regarding the delivery receipt with dataCoding 0 and err = 1 (message length is invalid) that you received, this indicates that there might be an issue with the encoding of the message or the message length.

Here are a few suggestions that might help you troubleshoot and resolve the problem:

  1. Message Length: Ensure that your message length, especially in Unicode, is within the allowable limit for the destination country. Different languages and characters in Unicode might have varying byte lengths, so double-check that your messages comply with the limitations.

  2. Encoding: Verify that you are correctly encoding your messages in Unicode (UTF-8). Unicode characters require more bytes than standard ASCII characters, so it's crucial to use the appropriate encoding to avoid message truncation.

  3. Delivery Receipts: If the delivery receipts are not providing enough information, try reaching out to Clickatell's support team for more detailed logs and insights into the message delivery process. They might be able to help you pinpoint the exact issue.

  4. Alternative Providers: If Clickatell's limitations persist and you require reliable Unicode support for China and Korea, consider exploring other SMS gateway providers that specifically cater to those regions. Some providers might offer better support for sender ID and Unicode characters.

  5. Client Information: To know which provider your clients belong to, you could consider requesting that information from them directly. Alternatively, you might be able to identify the provider based on the destination phone number's prefix, as different carriers often have specific number ranges.

Remember to communicate with Clickatell's support team and seek their assistance in resolving the issues you are facing. They should have a better understanding of their platform's capabilities and any specific considerations for different destinations.

I hope these suggestions are helpful, and I wish you success in resolving the SMS delivery issues! If you have any more questions, feel free to ask. Good luck! 🍀

Inspiring
June 23, 2006
otnateos wrote:
> = 1 (message length is invalid). This is also happens even though I send only
> about 6 or 7 characters long (unicode).

are the unicode SMS getting thru? have you updated your cf server, there's one
hot fix that specifically addresses unicode SMS. finally make sure you're not
one one of clickatell's GSM servers, you'd have to use the GSM charset.
June 27, 2006
quote:

are the unicode SMS getting thru? have you updated your cf server, there's one

Are you referring to ColdFusion 7.0.1 Updater Paul?

Yes I did install the updater. I just found out that my problem is not unicode problem at all. Basically every return receipt that I received from the SMPP Gateway has err:1 in the message. All I did is log every CFEvent that I received from the SMPP server if error occurs. The example is:

STRUCT ->
CFCPATH -> ....
GATEWAYID -> My Gateway
ORIGINATORID -> 86???????????
CFCMETHOD -> onIncomingMessage
DATA ->
esmClass -> 4
sourceAddress -> 86???????????
priority -> 0
registeredDelivery -> 0
messageLength -> 135
protocol -> 0
destAddress -> *my number*
MESSAGE -> id:*some hex message id* sub:001 dlvrd:0 submit date:0606270957 done date:0606270957 stat:REJECTD err:1 text:esting routing,
dataCoding -> 0
GATEWAYTYPE -> SMS

and everytime I got an error, I only receive that message. However after I called the SMPP support team just now, they said that on their end they actually send out two messages to my server and in my end, my logger only log one message for every SMS sent.

The thing really bugging me is, does coldfusion hiding some of the messages they received from the server, or does it have some kind of funny thing going on. Well, frankly I don't know much about Coldfusion, I just been using it for about 6 months.