-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
handset messages not saved in table and not pushed to dashboard #3
Comments
Sounds as if Kannel may not be wired correctly to the HTTP endpoint of On Thu, Jun 7, 2012 at 9:52 AM, sosewe <
|
this is my kannel.conf CONFIGURATION FOR USING SMS KANNEL WITH RAPIDSMS IN MALAWIFor any modifications to this file, see Kannel User GuideIf that does not help, see Kannel web page (http://www.kannel.org) andvarious online help and mailing list archivesNotes 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 guideKalle Marjola for Kannel project 2001, 2004include = "/etc/kannel/modems.conf" #--------------------------------------------- COREThere is only one core group and it sets all basic settingsof the bearerbox (and system). You should take extra notes onconfiguration variables like 'store-file' (or 'store-dir'),'admin-allow-ip' and 'access.log'group = core SMSC CONNECTIONSSMSC connections are created in bearerbox and they handle SMSC specificprotocol and message relying. You need these to actually receive and sendmessages to handset, but can use GSM modems as virtual SMSCsThis is a fake smsc connection, only used to test the system andservices. It really cannot relay messages to actual handsets!#group = smsc #group = smsc does not seem to be used; included for consistency#interface-version = 34 By denying all other SMSCes, we are assured this one is used only todeliver messages from the TNM backend in RapidSMS.#denied-smsc-id = zain-modem #mysql connection #group =dlr-db group = smsc By denying all other SMSCes, we are assured this one is used only todeliver messages from the Zain backend in RapidSMS.#denied-smsc-id = tnm-smpp #--------------------------------------------- SMSBOX SETUPSmsbox(es) do higher-level SMS handling after they have been received fromSMS centers by bearerbox, or before they are given to bearerbox fordelivery group = smsbox SEND-SMS USERSThese users are used when Kannel smsbox sendsms interface is used tosend PUSH sms messages, i.e. calling URL likehttp://kannel.machine:13013/cgi-bin/sendsms?username=tester&password=foobar. This is the username and password that RapidSMS uses to deliver SMSes toKannel. It must also set the 'smsc' variable in the query string, so thatKannel knows which SMSC to use to route the message.group = sendsms-user #--------------------------------------------- SERVICESThese are 'responses' to sms PULL messages, i.e. messages arriving fromhandsets. The response is based on message content. Only one sms-serviceis 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 There should be always a 'default' service. This service is used when noother 'sms-service' is applied. These relay incoming messages from Zainand TNM, respectively, to the appropriate HTTP backend URLs in RapidSMS.By setting 'accepted-smsc', we are assured that messages are routed tothe appropriate backend in RapidSMS.group = sms-service don't send a reply here (it'll come through sendsms):max-messages = 0 #group = sms-service don't send a reply here (it'll come through sendsms):#max-messages = 3 On Thu, Jun 7, 2012 at 4:58 PM, David McCann <
stephen osewe |
Yup. problem is with this line: get-url = http://127.0.0.1:8081/?id=%p&text=%a&charset=%C&coding=%c change that to : get-url = That assumes that you're not using a custom urls.py to point to the receive On Thu, Jun 7, 2012 at 10:07 AM, sosewe <
|
am still not getting my way withi this even after implementing the changes,any other idea ? |
What do your main urls.py and settings.py look like? Possible it's some On Fri, Jun 8, 2012 at 2:25 AM, sosewe <
|
Let me send you a copy of my settings.py settings.py#!/usr/bin/env python vim: ai ts=4 sts=4 et sw=4encoding=utf-8--------------------------------------------------------------------MAIN CONFIGURATION--------------------------------------------------------------------you should configure your database here before doing any real work.see: http://docs.djangoproject.com/en/dev/ref/settings/#databasesDATABASES = { the rapidsms backend configuration is designed to resemble django'sdatabase configuration, as a nested dict of (name, configuration).the ENGINE option specifies the module of the backend; the most commonbackend types (for a GSM modem or an SMPP server) are bundled withrapidsms, but you may choose to write your own.all other options are passed to the Backend when it is instantiated,to configure it. see the documentation in those modules for a list ofthe valid options for each.INSTALLED_BACKENDS = {
} to help you get started quickly, many django/rapidsms apps are enabledby default. you may wish to remove some and/or add your own.INSTALLED_APPS = [
] this rapidsms-specific setting defines which views are linked by thetabbed navigation. when adding an app to INSTALLED_APPS, you may wishto add it here, also, to expose it in the rapidsms ui.RAPIDSMS_TABS = [ --------------------------------------------------------------------BORING CONFIGURATION--------------------------------------------------------------------#Time Zone Settings debug mode is turned on as default, since rapidsms is under heavydevelopment at the moment, and full stack traces are very usefulwhen reporting bugs. don't forget to turn this off in production.DEBUG = TEMPLATE_DEBUG = True after login (which is handled by django.contrib.auth), redirect to thedashboard rather than 'accounts/profile' (the default).LOGIN_REDIRECT_URL = "/" #set our login url to match RapidSMS; url patterns use django-nose to run tests. rapidsms contains lots of packages andmodules which django does not find automatically, and importing themall manually is tiresome and error-prone.TEST_RUNNER = "django_nose.NoseTestSuiteRunner" for some reason this setting is blank in django's global_settings.py,but it is needed for static assets to be linkable.MEDIA_URL = "/static/" #If you are going to use XForms with ODK collect or another XForms this is required for the django.contrib.sites tests to run, but alsonot included in global_settings.py, and is almost always
|
Everything here seems okay...it's difficult to diagnose further for me from http://:/router/receive/?backend=safaricom-modem&sender=8675309&message=test And see what the response is from the server, and what shows up in the On Mon, Jun 11, 2012 at 1:48 AM, sosewe <
|
How can you make python listen to port 8081 ? On Mon, Jun 18, 2012 at 5:31 PM, David McCann <
stephen osewe |
HI David, Check out this feedback I got; {"status": "Message handled.", "message": {"status": "H", "direction": "I", Its a JSON response On Tue, Jun 19, 2012 at 10:55 AM, stephen osewe stephenosewe@gmail.comwrote:
stephen osewe |
So at this point, everything is running properly from rapidsms_httprouter's perspective, provided this message also appears in the message log. From here I can only say that kannel isn't hitting your /router/receive url properly, so verifying that it is pointing to: http://:/router/receive/?backend=safaricom-modem&sender=8675309&message=test Would be the first test, followed by a more in-depth analysis of the logs, etc. I would also read through the django and kannel documentation, as there are lots of useful things there for getting a server set up and configured (including port numbers, etc). At this point, however, I am closing this issue, as it no longer seems to concern rapidsms_httprouter. |
Yeah,You can say that,What I have done is use the same port the server is 2012-06-19 15:42:19 [7995] [8] DEBUG: Octet string dump ends. On Tue, Jun 19, 2012 at 3:45 PM, David McCann <
stephen osewe |
When sending messages via the message tester,the messages are saved into the messages table and they also appear on the message log web interface(dashboard),but for messages sent via a handset,no message is logged into a table and the dashboard shows nothing too.
when i send 'ping-kannel' I get the approriate response 'kannel is online and responding to messages' but still this message is not saved in a table and neither does it appear on the dashboard,but on sending 'ping' i get no response at all.
The text was updated successfully, but these errors were encountered: