Newbie question - Fake smsc test not working during installation

358 views
Skip to first unread message

Adam Uhuru

unread,
Apr 20, 2016, 9:14:59 AM4/20/16
to rapidsms
Hi,

I'm sorry for asking this question that may seem obvious, but I wasn't able to find an answer on the forum posts. I've followe instructions on how to configure RapidSMS with Kannel Backend from this page: http://rapidsms.readthedocs.org/en/latest/topics/backends/kannel.html, after having created a new project following instructions from this other page: http://rapidsms.readthedocs.org/en/develop/tutorial/tutorial01.html#tutorial01

Kannel is working. Test was successful. RapidSMS page is working. Http Message tests were successful.

I then tried to configure the fake smsc backend. I added a backend for the fake SMSC to RapidSMS settings.py file, as specified. But noted that the urls.py description differs completely from what I am having on my installation. On the documentation, this file looks like this

from django.conf.urls.defaults import *
from rapidsms.backends.kannel.views import KannelBackendView

urlpatterns = patterns('',
    # ...
    url(r"^backend/kannel-fake-smsc/$",
        KannelBackendView.as_view(backend_name="kannel-fake-smsc")),
)

On my installation, however, this file looks like on this screenshot


When I run the fake smsc test


/usr/lib/kannel/test/fakesmsc -m 1 "123 789 text echo hi"


I get no answer. I'm just having this message from the prompt:


INFO: fakesmsc starting


From /var/log/kannel/bearerbox.log, I'm getting this line


INFO: Fakesmsc client connected from 127.0.0.1


I made some search about this topic but didn't find anything that could help me to figure out what is going wrong with my configuration. 


Can I have your help please ?


Thanking you very much in advance.


Best regards

Adam




mhah

unread,
Apr 29, 2016, 12:45:16 PM4/29/16
to rapidsms
I have same problème no one help us..

Victor Miclovich

unread,
Apr 29, 2016, 2:13:54 PM4/29/16
to rapi...@googlegroups.com
Folks are no longer very active given the rise of RapidPro

Sent from my iPhone
--
You received this message because you are subscribed to the Google Groups "rapidsms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rapidsms+u...@googlegroups.com.
To post to this group, send email to rapi...@googlegroups.com.
Visit this group at https://groups.google.com/group/rapidsms.
For more options, visit https://groups.google.com/d/optout.

Lengani Kaunda

unread,
Apr 29, 2016, 5:18:10 PM4/29/16
to rapi...@googlegroups.com
Hello,

Could you share your current Kannel configuration?

Best regards,

Lengani

mhah

unread,
Apr 30, 2016, 6:10:35 AM4/30/16
to rapidsms
My kannel configuration is :



# 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 (http://www.kannel.org) 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. You need these to actually receive and send
# messages to handset, but can use GSM modems as virtual SMSCs

# Here is a sample SMSC for use with the /usr/lib/kannel/test/fakesmsc command

group = smsc
smsc = fake
smsc-id = FAKE
port = 10000
connect-allow-ip = 127.0.0.1

#---------------------------------------------
# SMSBOX SETUP
#
# Smsbox(es) do higher-level SMS handling after they have been received from
# SMS centers by bearerbox, or before they are given to bearerbox for delivery

group = smsbox
bearerbox-host = 127.0.0.1
sendsms-port = 13013
sendsms-chars = "0123456789 +-"
log-file = "/var/log/kannel/smsbox.log"
log-level = 0
access-log = "/var/log/kannel/smsbox-access.log"
reply-couldnotfetch = "Your message could not be processed at this time.  Please try again later. (err=couldnotfetch)"
reply-requestfailed = "Your message could not be processed at this time.  Please try again later. (err=requestfailed)"
reply-couldnotrepresent = "Your message could not be processed at this time.  Please try again later. (err=couldnotrepresent)"
http-request-retry = 3
http-queue-delay = 10

# SEND-SMS USERS
#
# These users are used when Kannel smsbox sendsms interface is used to
# send PUSH sms messages, i.e. calling URL like
# http://kannel.machine:13013/cgi-bin/sendsms?username=tester&password=foobar...

# This is the username and password that RapidSMS uses to deliver SMSes to
# Kannel.  It must also set the 'smsc' variable in the query string, so that
# Kannel knows which SMSC to use to route the message.

group = sendsms-user
username = rapidsms
password = CHANGE-ME
user-deny-ip = "*.*.*.*"
user-allow-ip = "127.0.0.1;"

#---------------------------------------------
# SERVICES
#
# These are 'responses' to sms PULL messages, i.e. messages arriving from
# handsets. The response is based on message content. Only one sms-service is
# applied, using the first one to match.

# The 'ping-kannel' service let's you check to see if Kannel is running,
# even if RapidSMS is offline for some reason.

group = sms-service
keyword = ping-kannel
text = "Kannel is online and responding to messages."

# There should be always a 'default' service. This service is used when no
# other 'sms-service' is applied.  These relay incoming messages from any
# configured SMSCs to the appropriate HTTP backend URLs in RapidSMS.
# By setting 'accepted-smsc', we are assured that messages are routed to
# the appropriate backend in RapidSMS.

group = sms-service
keyword = default
catch-all = yes
accepted-smsc = FAKE
# don't send a reply here (it'll come through sendsms):
max-messages = 0
get-url = http://127.0.0.1:8000/backend/kannel-fake-smsc/?id=%p&text=%a&charset=%C&coding=%c


best regards..


Le mercredi 20 avril 2016 14:14:59 UTC+1, Adam Uhuru a écrit :
Reply all
Reply to author
Forward
0 new messages