Its not anything specific - I just started with the implementation of standard messages in order to see how it goes and how many people are using it.
Check the Clickatell source file (in the http package). You should identify the binary message and make the appropriate call to Clickatell (for example, convert the message to HEX bytes, set the appropriate flags - whatever is necessary from Clickatell to identify a binary message). On Sep 24, 10:19 am, Alam Sher <[email protected]> wrote: > By the way? Why SMSLib doesn't support sending binary SMS using clickatell? > Does that also mean that I can't send SMSLib's Encrypted SMS implementation? > If I want to implement it myself, what would you suggest would be the > starting point for this? > > Thanks, > Alam Sher > > > > > > On Thu, Sep 24, 2009 at 12:41 PM, Alam Sher <[email protected]> wrote: > > > Ok, now what if I convert the encrypted byte array to String and send > > a text message instead of a binary message. On the client side I'll > > have to convert String to byte array and then decrypt the bytes and > > present the result. > > > Should it work? Any special encoding scheme I should follow? Any > > suggestion? > > > Thanks, > > Alam Sher > > > On Sep 24, 12:34 pm, Thanasis <[email protected]> wrote: > > > Hello, > > > > SMSLib does not support binary messages via the Clickatell handler. > > > > As for the first issue, I'll check whether something has breaked the > > > functionality of the Clickatell handler (see this: > >http://code.google.com/p/smslib/issues/detail?id=267) > > > > On Sep 23, 10:59 pm, Alam Sher <[email protected]> wrote: > > > > > Gateway Id: clickatell.http.1 > > > > Encoding: 8-bit > > > > Date: Wed Sep 23 14:57:54 ACT 2009 > > > > SMSC Ref No: e6f03fc9de31da147703d765d6bd7dd4 > > > > Recipient:+923235330994 > > > > Dispatch Date: Wed Sep 23 14:57:55 ACT 2009 > > > > Message Status: SENT > > > > Validity Period (Hours): -1 > > > > Status Report: false > > > > Source / Destination Ports: 50000 / 50001 > > > > Flash SMS: false > > > > Binary: > > > 0C918F29DCE864392F5AF4C8F27DCE742BBB2107A1B5A5B54C118A3AEDC9D3D12EB3A5A694C > > 35FEEE83592978F38AB33A1C3 > > > > > This is the message output just before its sent. > > > > > Regards, > > > > Alam Sher > > > > > On Sep 24, 1:55 am, Alam Sher <[email protected]> wrote: > > > > > > Dear Experts! > > > > > > I am facing some strange problems using SMSLib > > > > > > 1. When i use the latest build of SMSLib I can even create a service > > > > > using ClickAtell Gateway. It just throws Null Pointer Exception. > > > > > > 2. However when I use some previous build (smslib-3.4.0) same code > > > > > works fine and I can send Text messages (On specific Port for J2ME > > > > > client) using my clickatell account. But the issue arises when I try > > > > > to send a binary message (Basically I am trying to encrypt a message > > > > > myself and not using SMSLib default support for encryption) my binary > > > > > messages are delivered but contains no data at all. They have empty > > > > > bodies. > > > > > > Please guide me how to overcome this problem? You need some debugging > > > > > info or this is some kind of known issue? > > > > > > So as a summary here are my requirements: > > > > > > Binary SMS with specific source and destinaiton port info to be sent > > > > > using clickatell gateway. > > > > > > Anticipating a quick and positive response from your side. > > > > > > Regards, > > > > > Alam Sher > > -- > Regards, > ________________ > Alam Sher Khan > +92 323 533 0994 > +92 331 505 5549 > +92 31a lam sher --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SMSLib for Java User Group" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/smslib?hl=en -~----------~----~----~----~------~----~------~--~---
