view mod_sms_clickatell/README.md @ 6319:04c3273cb81f

mod_auth_cyrus: Add empty 'profile' table to SASL handler objects This is for compatibility with Prosody's built-in util.sasl objects. A SASL profile table usually includes methods supported by the backend, which can be used by SASL mechanism handlers to perform operations (such as testing the password). It also optionally contains a 'cb' field with channel binding method handlers. The Cyrus backend doesn't support channel binding, and doesn't have the same concept of auth backend methods (it handles all that internally, and Prosody has no insight or control over it). Thus, we create an empty profile which informs Prosody that the SASL handler does not support any of the auth or channel binding methods. Some features will not work, but they didn't work anyway. This just makes it explicit. This fixes a traceback in mod_sasl2_fast, which expected SASL handlers to always contain a 'profile' field.
author Matthew Wild <mwild1@gmail.com>
date Thu, 04 Sep 2025 10:14:46 +0100
parents fe081789f7b5
children
line wrap: on
line source

---
labels:
- 'Stage-Alpha'
summary: XMPP to SMS gateway using the Clickatell API
...

Introduction
============

This module provides and SMS gateway component which uses the Clickatell
HTTP API to deliver text messages. See clickatell.com for details on
their services. Note that at present, this is entirely one way: replies
will either go nowhere or as sms to the source number you specify.

Configuration
=============

In prosody.cfg.lua:

    Component "sms.example.com" "sms_clickatell"
        sms_message_prefix = "some text"

The sms\_message\_prefix is a piece of text you want prefixing to all
messages sent through the gateway. For example, I use the prefix
"`[Via XMPP]` " to indicate to recipients that I've sent the message via
the internet rather than the mobile network. Since my primary use case
for this component is to be able to send messages to people only
reachable via mobile when I myself only have internet access and no
mobile reception, this option allows me to give a hint to my recipients
that any reply they send may not reach me in a timely manner.

Usage
=====

Once you've installed and configured, you should be able to use service
discovery in your XMPP client to find the component service. Once found,
you need to register with the service, supplying your Clickatell
username, password, API ID, and a source number for your text messages.

The source number is the mobile number you want messages to 'originate'
from i.e. where your recipients see messages coming from. The number
should be in international format without leading plus sign, or you can
use some other format if clickatell supports it.

To send text messages to a target number, you need to add a contact in
the form of `[number]@sms.example.com`, where `[number]` is the mobile
number of the recipient, in international format without leading plus
sign, and sms.example.com is the name for the component you configured
above. For example:

447999000001@sms.yourdomain.com

You should then be able to send messages to this contact which get sent
as text messages to the number by the component.

Compatibility
=============

  ----- -------
  0.7   Works
  ----- -------

Todo
====

-   Refactor to create a framework for multiple sms gateway back ends,
    and split Clickatell specific code in to its own back end