I've noticed that the folks at Clickatell are direct linking an old piece of code for py-clickatell.
Quite amusing when you realise that I've written interfaces for their API interface in PHP, python, and ruby (once I figure out where I put that code I wrote last year for something I was prototyping when first looking at ruby over a year ago).
Continue reading "Clickatell love direct linking to source" »
I've started opening up Pandora's Box by releasing more code under liberal Open Source licenses.
More code to be released in due course.
UPDATE:
Quick update py-clickatell was mentioned before when an earlier revision was made available.
Per a comment posted on non-related post regarding my python code to connect to send SMS messages via Clickatell.
The pycurl wrapper is available from http://pycurl.sourceforge.net/ which provides the python wrapper around the cURL library.
The folks at Clickatell also now have Clickatell Wholesale. Interesting stuff. I'm planning on forking SMS_Clickatell to SMS_Clickatell_Wholesale for using that gateway.
This is a bit of a work in progress while the documentation is still not finished, I'm basically putting some examples of how to use SMS_Clickatell.
Querying your balance (of available SMS Credits) which you have with Clickatell:
<?php
require_once 'SMS/Clickatell.php';
$sms = new SMS_Clickatell;
$res = $sms->init (
array (
'user' => 'username',
'pass' => 'password',
'api_id' => '12345'
)
);
$res = $sms->auth();
echo 'Credits remaining: ' . $sms->getbalance() . '\n';
?>
Initially when the SMS_Clickatell code was being written I had a company called Ataris Technologies which used SMS messaging for various projects. The "sample code" provide by Clickatell does not provide an easy way for integrating into their gateway without modifying the provided code and adding error checking, etc. etc.
Using the curl extension (in PHP) one can securely connect using HTTPS to Clickatell's API server. The PEAR component enables easier integration into Clickatell's API server as the bulk of the code has been written (the interfacing with Clickatell's API Server), one has more control of how your application interfaces with SMS_Clickatell.
Errors are returned as PEAR_Errors. Which makes it easier for you to display error messages in your application rather than having error messages displayed randomly on the screen.
An example of code for sending a SMS message to a single recipient:
<?php
require_once 'SMS/Clickatell.php';
$sms = new SMS_Clickatell;
$res = $sms->init (
array (
'user' => 'username',
'pass' => 'password',
'api_id' => '12345'
)
);
$res = $sms->auth();
if (PEAR::isError($res)) {
die ($res->getMessage());
}
$sent = $sms->sendmsg (
array(
'from' => 'YourName',
'to' => $_POST['recipient'],
'text' => stripslashes($_POST['msg']),
'msg_type' => $_POST['msg_type'],
'climsgid' => $climsgid
)
);
if (PEAR::isError($sent)) {
die ($sent->getMessage());
}
echo 'Your message ID to the gateway is ' . trim($sent['1']) . '\n';
?>
I've released a version of the SMS_Clickatell PEAR module (reusable PHP component) today which implements spending vouchers which are generated on the Clickatell website.
Documentation is being written and will be made available shortly.
I'm quite impressed! Pieter's company Clickatell is linking to my PEAR projects page with the following text:
Clickatell SMS PEAR Module (Reusable PHP component)
This PEAR package provides SMS functionality and access to the Clickatell SMS Gateway.
http://www.powertrip.co.za/PEAR/
I think it should be updated to say something like:
"The SMS_Clickatell PEAR package provides SMS functionality and access to the Clickatell SMS Gateway."
Also the link should be pointed to http://www.powertrip.co.za/PEAR/SMS_Clickatell/ considering I started moving content for each PEAR package to a seperate page.
I will at some stage place some decent documentation online for the package. I was wondering how long it would take them to link to my website as their "code example" is not really reusable.
There is also a python version of the script which I'm working which should be finished sometime into the new year.
Bretton posted an email earlier refering to the following Dodgy SMS services feel WASPA's sting article on ITWeb.
[Johannesburg, 11 October 2004] - A watchdog body has been set up to
guard the mobile industry against unscrupulous SMS services that rip off consumers.
The Wireless Application Service Providers Association (WASPA) has been established by industry players, with seed money from the three cellular operators, and is an organisation aimed at providing protection to service providers.
According to WASPA's deputy chairman, Pieter de Villiers of Clickatell, it is impossible to monitor all the third-party traffic that is pushed over a network, so the association has been formed to protect service providers from being held liable for defamatory or illegal third-party content.
I've finally had a couple of minutes to setup phpdoc to generate API documentation for the SMS::Clickatell PEAR class I wrote. The documentation is available over here.
I will be improving the documentation when time permits.
Continue reading "SMS::Clickatell 0.4 API Documentation online" »
Reading through Celerity's documentation, I'm finding it quite useless compared to the better quality documentation from Clickatell.
Maybe it's just me but I like being able to download the pdf from Clickatell's website and print it and work from decent documentation which always makes a developers life easier.
Started work on SMS_Celerity which works with Celerity Systems system (vsms.net / bulksms2.way.co.za etc.). I'm going to need to stress test it prior to releasing the code under the PHP license.
Bumped into the guys at the Futurex conference which was held at the Cape Town International Convention Centre in Cape Town, South Africa.
I've just rolled out another release of SMS_Clickatell which is my implementation into the Clickatell Bulk SMS Gateway. One can find the tarball on my PEAR project page.
Here is a little bit of sample code for the SMS::Clickatell PEAR Class I wrote.
