Setting up RapidSMS with Kannel is a free and open source SMS gateway that can be configured for use with RapidSMS. While in-depth Kannel configuration is outside the scope of this documentation, it’s possible to configure Kannel to connect directly to USB or serial GSM modems as well as third party HTTP or SMPP gateways. For more information about the connections Kannel supports (what Kannel calls an “SMS Center” or “SMSC”), see the in-depth and refer to “Chapter 6. Setting up a SMS Gateway”. The following guide will help you setup Kannel on Ubuntu to talk to a single GSM modem and RapidSMS installation. # CONFIGURATION FOR USING SMS KANNEL WITH RAPIDSMS # # For any modifications to this file, see Kannel User Guide # If that does not help, see Kannel web page (and # various online help and mailing list archives # # Notes on those who base their configuration on this: # 1) check security issues! (allowed IPs, passwords and ports) # 2) groups cannot have empty rows inside them!
# 3) read the user guide include = '/etc/kannel/modems.conf' #--------------------------------------------- # CORE # # There is only one core group and it sets all basic settings # of the bearerbox (and system). You should take extra notes on # configuration variables like 'store-file' (or 'store-dir'), # 'admin-allow-ip' and 'access.log' group = core admin-port = 13000 smsbox-port = 13001 admin-password = CHANGE-ME status-password = CHANGE-ME admin-deny-ip = '*.*.*.*' admin-allow-ip = '127.0.0.1' box-deny-ip = '*.*.*.*' box-allow-ip = '127.0.0.1' log-file = '/var/log/kannel/bearerbox.log' log-level = 0 #--------------------------------------------- # SMSC CONNECTIONS # # SMSC connections are created in bearerbox and they handle SMSC specific # protocol and message relying. Ss 0:00 /usr/sbin/run_kannel_box --pidfile /var/run/kannel/kannel_bearerbox.pid --no-extra-args /usr/sbin/bearerbox -v 4 -- /etc/kannel/kannel.conf 3232? Sl 0:00 /usr/sbin/bearerbox -v 4 -- /etc/kannel/kannel.conf 3243? Ss 0:00 /usr/sbin/run_kannel_box --pidfile /var/run/kannel/kannel_smsbox.pid --no-extra-args /usr/sbin/smsbox -v 4 -- /etc/kannel/kannel.conf 3245?
Sl 0:00 /usr/sbin/smsbox -v 4 -- /etc/kannel/kannel.conf You can further test that Kannel is running by using the fake SMSC (used only for testing) to use the “ping-kannel” service that we included in the Kannel configuration above.
By default, Kannel will route the message in a round-robin way between all connected SMSCs. There are three SMSC parameters which control the routing to a specific SMSC: • denied-smsc-id SMS messages with SMSC ID equal to any of the IDs in this list are never routed to this SMSC.
Apr 10, 2012 Kannel – connection to the SMSC. Kannel supports SMPP protocol versions 3.3 and 3.4. There could be a lot of things set up.
Multiple entries are separated with semicolons (';') • allowed-smsc-id This list is opposite to previous: only SMS messages with SMSC ID in this list are ever routed to this SMSC. Multiple entries are separated with semicolons (';') • preferred-smsc-id SMS messages with SMSC ID from this list are sent to this SMSC instead than to SMSC without that ID as preferred. Multiple entries are separated with semicolons (';') Juggling with these variables allows you to create from very simple to very complex routing scenarios. Here is a very basic example: Suppose we have 2 SMSC, smsc1 and smsc2 and we want to route sms messages to one of those 2 SMSC. In our kannel config file we add the following lines: group = smsc smsc-id = smsc1 allowed-smsc-id = smsc1 group = smsc smsc-id = smsc2 allowed-smsc-id = smsc2 Now, we can specify what smsc to send through in the request to kannel sendsms interface: GET /kannel/sendsms? Adobe Cs5 Crack Torrent. smsc=SMSC_ID&to=TO&text=TEXT where SMSC_ID can be one of smsc1 or smsc2. In this example, if we don't specify any smsc in the GET request, the sms will not match any of the rules for smsc1 or smsc2 and will not be sent. Weapons Of War there. We can avoid this by setting a default SMSC to be used by all outgoing message with the following sendsms-user group variable: • default-smsc string If no SMSC ID is given with the HTTP request, use this one as default route for all push messages. Barbie As The Island Princess Pc.
Group = sendsms-user default-smsc = smsc1 Another option would be to use the denied-smsc-id variable: group = smsc smsc-id = smsc1 denied-smsc-id = smsc2 group = smsc smsc-id = smsc2 denied-smsc-id = smsc1 With this configuration, when we specify the smsc in the HTTP request the sms will be routed to the smsc with that id, but when we don't, Kannel will fall back to a round-robin between smsc1 and smsc2. For more advanced uses: For a more in-depth understanding of Kannel's routing and more complex scenarios you can also check out this thread.