HTTP SMSC , Binary URL and Unicode Submission

HTTP SMSC , Binary URL and Unicode Submission SearchSearch
Author Message
Extreme Solution
New member
Username: Extremesolution

Post Number: 1
Registered: 10-2010
Posted on Monday, October 11, 2010 - 09:26 am:   

Hi ,

We have been trying to integrate with a few SMSC's such as Kannel Via an HTTP SMSC connection.

While text URL is pretty straight forward , Unicode and binary becomes very tricky as it is stated that a UDH value must be passed in the Binary URL Template , while a unicode SMS doesn't contain a UDH paramatere nor value , which results submitting a NULL value to Kannel and no message delivery.

Any idea how to get around identifying Binary and Unicode URL templates in HTTP SMSC.

Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2562
Registered: 08-2008
Posted on Tuesday, October 12, 2010 - 08:11 pm:   

Hi Sherif,

Are you sure that the blank UDH is the problem?

If I recall correctly, Kannel requires binary data to be encoded as URL escaped characters instead of ASCII hex.

There is a @@DataBin@@ parameter (and @@UDHBin@@) parameter that can be used instead of @@Data@@ (and @@UDH@@), which encodes the binary data in this way.

There is also a hidden configuration option to submit Unicode messages using the text template with UTF-8 character encoding. I'm not sure if that option would work with Kannel.

As a starting point, I'd suggest determining whether or not the null UDH parameter is causing a problem. To determine this, I'd suggest sending two Unicode test messages. The first one should have less than 70 Unicode characters, and the second should have more. (The one with more than 70 characters would be sent as a multipart message and include UDH.)

NowSMS Support