rapidsms-tropo
Basic Tropo backend for RapidSMS, version 0.14.0 or later.
Requirements
Usage
Create an application at tropo.com. Its type should be “Web API”.
Add rtropo to your Python path and set up the Tropo backend in your Django settings file.
The required settings for your Tropo backend in INSTALLED_BACKENDS are:
- ENGINE
“rtropo.outgoing.TropoBackend”
- config
A dictionary with the rest of your settings for this backend. Required settings inside config are:
- messaging_token
Your messaging token from Tropo (a long hex string)
- number
The phone number your Tropo app is using. Must start with “+” and the country code.
For example:
INSTALLED_BACKENDS = {
"my-tropo-backend": {
"ENGINE": "rtropo.outgoing.TropoBackend",
'config': {
# Your Tropo application's outbound token for messaging (required)
'messaging_token': 'YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY',
# Your Tropo application's voice/messaging phone number, starting
# with "+" and the country code (required)
'number': '+1-###-###-####',
},
},
}
At this point you should be able to send outgoing messages, but more setup is needed to receiving incoming messages.
Set up your URLconf to send incoming http requests from tropo to rtropo.views.message_received, passing the backend_name parameter, whose value must be the same as the backend name you used in INSTALLED_BACKENDS.
For example:
from django.conf.urls.defaults import *
from rtropo import views
urlpatterns = patterns('',
url(r"^tropo/$",
views.message_received,
kwargs={'backend_name': 'my-tropo-backend'},
name='tropo'),
)
You can use any URL. If you want to add some (slight) protection against someone other than Tropo passing you messages pretending to be Tropo, you might make your URL long and random, e.g.:
from django.conf.urls.defaults import *
from rtropo import views
urlpatterns = patterns('',
url(r"^534bd769-3e2e-42bd-8337-2099d9f38858/$",
views.message_received,
kwargs={'backend_name': 'my-tropo-backend'},
name='tropo'),
)
Configure your Tropo application at tropo.com so its SMS/Messaging URL will invoke the Django URL that you just configured. E.g.:
https://yourserver.example.com/534bd769-3e2e-42bd-8337-2099d9f38858/
Background
Development by Caktus Consulting Group.
Changelog
v0.2.0 (Released 2013-05-20)
Updates for RapidSMS 0.14 and later.
Support for bulk messaging - with RapidSMS 0.14.0 or later, many messages can be sent without requiring separate round trip requests to Tropo for each.
Add tests
Add tox test runner
Drop Tropo python library, which was hardly being used anyway.
Security improvements.
v0.1.2 (Released 2013-05-17)
Add validation of some incoming requests from Tropo.
Probably last version to support threadless-router, rapidsms<0.10.0
v0.1.1 (Released 2012-07-02)
Updated MANIFEST to include distribute_setup.py
v0.1.0 (Released 2012-06-28)
Initial stable release
Metadata
Release files for rapidsms-tropo 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rapidsms-tropo-0.2.0.tar.gz | 13.9 kB | Without provenance | Details for rapidsms-tropo-0.2.0.tar.gz |
Release files / rapidsms-tropo-0.2.0.tar.gz
| Download URL | rapidsms-tropo-0.2.0.tar.gz |
|---|---|
| Size | 13.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e93c6c3eb1904c4ca8660b837e0032d7efc6b67add286734f90af61bfdcdeda7
|
|
BLAKE2b-256 checksum How to use checksums |
944c5690c46f36833f0aa1bc80b04e2b3c6bf051e7a1c105a06fa7a690af0406
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for rapidsms-tropo 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.