jbubik / kalkun Goto Github PK

Using Compose window, the user can add recipients one by one. Develop a possibility to select a contact group and then add all contacts from that group to be among the recipients. Contacts that already are recipients would NOT be doubled. Could be repeated for different groups to compose SMS for people in more than one contact group.

After sending SMS there is always a yellow-boxed message:

Your message has been move to Outbox and ready for delivery.

That is sometimes not true - there might already be sending errors. This should be reflected by a red-boxed message:

Cannot send message. Your message has been saved to Outbox with a problem description.

When i delete SMS from outbox, then Kalkun displays a message:

A Database Error Occurred
Error Number: 1062
Duplicate entry '85' for key 'PRIMARY'
INSERT INTO `user_sentitems` (`id_user`, `id_sentitems`) VALUES ('2', '85')

That makes Kalkun unusable. In database, I see that SMS with ID 85 is deleted from "outbox". There is still entry in "user_outbox" with ID 85. After deleting this line from "user_outbox", it is OK.

Private groups are unusable for others.
Public groups are visible for all others.
Develop Shared Groups! Kalkun user could tell, which users he is sharing the group with. Shared Group could be marked as shared only for use / shared for editing.

As of November 2014 Czech T-Mobile has changes their SMS gateway. They added CAPTCHA after sending 10 messages. The gateway script needs to be modified.

many texts missing
improve terminology
use consistent naming

There is a working script written in javascript - part of the esmska project:
https://github.com/kparal/esmska/blob/master/gateways/%5BCZ%5Dt-zones.gateway

The same can be done in PHP with curl library.
Would be nice to use a diffrent t-zones account for every kalkun user.

originally based on Kalkun 0.6, changes need to be ported to current master.

The new-gateway (or direct gateway) subsystem is currently in a Proof-of-Concept stage. It can send SMS via gammu and one of these providers: kannel, clickatell, ozeking, nowsms, way2sms. These new providers are lacking proper database support. Known shortcomings:

• After sending-out an SMS, it is not saved in sentitems.
• Sending at a later time is not supported.
• Failures in SMS delivery are not reported to the user.
• Does not play well with the Multi Modem configuration (Multi Modem is gammu-only)

Tip: create a Class to sit between all the NewGateway_model and gammu_model. This class could implement the necessary handling for all new gateway providers.