Re: [RIP] Remembering René Kluwen
Repose en paix. tu vivras dans chacun de nous qui avons connu cet outil Le samedi 12 juin 2021 à 09:44:20 UTC+1, Alejandro Guerrieri a écrit : I had the honor to collaborate with him a couple times many years ago, over sqlbox code. A great person and excellent professional. My deepest condolences, he will certainly be missed. On Fri, Jun 11, 2021 at 9:01 AM Stipe Tolj wrote: Dear all, With deep regret and sorrow we let you know that René Kluwen, one of Kannel core developers has passed away this week. René has been a wonderful character and person, a father and a long year active supporter of the Kannel project. His work contributed to the main gateway module, the sqlbox and opensmppbox sub-modules, along with most valued discussions in our mailing list groups. Some of us have been friends with René and we’re heavily shaken by the news. We will miss him, and we would like to express our sincerely condolences to his family. Like in the hearts and minds of his family, his persona will keep on living in his work he contributed with passion to our project. Honoring his contributions is our privilege and determination. Rest in peace René Kluwen (* 10-05-1970, ✝ 06-06-2021) https://kannel.org/images/rouwkaart_rene.png -- Best Regards, Stipe Tolj --- Düsseldorf, NRW, Germany Kannel Foundation tolj.org system architecture http://www.kannel.org/ http://www.tolj.org/ st...@kannel.org s...@tolj.org ---
Re: Minimum Requirement for getting 1000 message per second
Hi Ammar! I suggest you check the load in the SQLBox, BearerBox, MySQL and SMSBox. Our experience is that Mysql tends to slow things down a lot. Another enhancement we've had success with has been having 3-6 SMSBox instances running and connected to the bearerbox, and HAProxy on top distributing messages among them. SMSBoxes are very scalable, and can even be set on separate machines. Ideally, something like: Application+SMSBOX Bearerbox+Backends(ex:Mysql) SMSC Yet, you must check where is the actual bottleneck. On our experience it was MySQL. Finally, and again on our experience, Bearerbox will load CPU as it gets overworked, but RAM will be consumed only as long as messages are in queue (in RAM), Ex: pending DLR without DDBB backend (managed in memory) Hope this helps Cheers, David Szanto El 16/01/15 a las 13:24, Ammar Ali escribió: Hello Everyone, I had started kannel sms gateway before past 2 days. When I was started kannel then tested my application, it shows me 500-800 messages second speed but now I'm getting 200-300 Max messages/second. And the main problem is that it is not increased above 300. Can you suggest me that what is the main bottleneck in whole system setup. Because currently I'm connecting Fake SMSC connections. Thanks in advance *Ammar Ali* *Framp Technology* *Pune (Maharashtra)* On Fri, Jan 16, 2015 at 5:29 PM, Christopher Burke christopher.bu...@simulity.com mailto:christopher.bu...@simulity.com wrote: Hey, If you’re attempting to optimise the solution, you’ll probably want to look at a testbed. Check out https://github.com/twitter/cloudhopper-smpp which is a Java SMPP implementation. I use this and on my 2012 Macbook Pro (2.6ghz i7/8GB RAM/512GB SSD) I get 4.8k submit/sec over 10 sessons when I use Netty 6. Perhaps you can setup another box using the ch-smpp impl for listening (they’ve got performance code/configuration examples in the test/../demo dirs, and have your Kannel submit to it. On the configuration you currently have, you should expect 200-300 msg/sec using Kannel, I’ve never seen it submit much faster than that but admittedly I find understanding Java code a bit easier so I work with ch-smpp more now. Cheers, *Christopher Burke *http://simulity.com http://simulity.com/ Office: +44 (0) 1248 679 281 Fax: +44 (0) 1248 660 323 Skype:krslynx *UK *Unit 8, Ash Court, Parc Menai, Bangor, Gwynedd, LL57 4DF, Wales, UK *Malaysia *Level 30, The Gardens North Tower, Mid Valley City, Lingkaran Syed Putra, 59200, Kuala Lumpur, Malaysia NOTICE: This message contains privileged confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message, you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error, please notify Simulity Labs immediately. Any views expressed in this message are those of the individual sender except where the sender specifically states them to be the view of Simulity Labs On 16 January 2015 at 11:13:34, Mohammed Saleem (mohammedsl...@gmail.com mailto:mohammedsl...@gmail.com) wrote: Hi Then specs you have is more than enough to send even 10k SMS / second with correct configurations. But the bottleneck is the network speed and the allowed TPS from the operator. On Jan 16, 2015 1:40 PM, Ammar Ali ammarali3...@gmail.com mailto:ammarali3...@gmail.com wrote: Hello Currently, I have 4 GB RAM, Intel 24 Core Processor and 120 GB HDD but I'm not getting this TPS (300-500) in a second. Kannel bearerbox version `1.4.4'. Build `Dec 31 2014 18:29:22', compiler `4.4.7 20120313 (Red Hat 4.4.7-11)'. System Linux, release 2.6.32-042stab094.7, version #1 SMP Wed Oct 22 12:43:21 MSK 2014, machine x86_64. Hostname localhost, IP 192.168.1.1. Libxml version 2.7.6. Using OpenSSL 1.0.1e-fips 11 Feb 2013. Compiled with MySQL 5.5.40, using MySQL 5.6.22. Using native malloc. One more thing sometimes I'm getting this TPS but next time It has been decreased and reached at 100-200 TPS in a second. Can you suggest me where the problem in my whole system. This is my whole setup: [Bearerbox]-[SQLBox]-[SMSBox][Fake SMSC (Multiple)] *Configurations:* *Kannel.conf* * * # Single Group CORE group = core admin-port = 13000 admin-port-ssl=no admin-password = *** status-password = *** admin-deny-ip=*.*.*.* admin-allow-ip=*.*.*.* smsbox-interface =127.0.0.1 smsbox-port = 13001 smsbox-port-ssl=no log-file = kannel.log
Concatenated Message and DLR behaviour
Hi all, I have a question about SMPP specifications and Kannel behavior for concatenated SMS messages and DLRs. My understanding is that according to the SMPP specifications the SMSC should send Kannel one DLR for the complete message, not one DLR for each submit_sm. Is this correct and is Kannel implemented accordingly? What is your experience with different SMSCs? Do they send one DLR per complete message or one DLR for each submit_sm? Also, I would like to get information about possible commercial support for Kannel. Does anybody know who I should contact to get this information? Thanks in advance, David Szanto
Routing from Kannel SMPP connection to a connected OpenSMPPbox client
Hi Ive been strugling with this for a week or so now, and could do with a pointer on how to achieve what I need: Using Kannel Bearerbox/SMSbox I have a working SMPP link to our carrier and can receive message to/from (carrier) I am also running OpenSMPPbox to accept a connection from a remote company (client) I need to be able to route inbound messages from the Carrier - Client but cant quite work out where I need to set up the routing. Im not trying to do anything more advanced than this , just a simple passthrough of all traffic from the carrier to the client via SMPP. Can anyone shed any light on how this would be achieved please? Regards David
Unsubscribe
Unsubscribe -Original Message- From: Alvaro Cornejo cornejo.alv...@gmail.com Sent: 7/24/2013 7:25 PM To: Christopher Ward c.j.ward26...@gmail.com; users users@kannel.org Subject: Re: Translate SMPP requests to different SMS api Hi Always cc kannel user list. This way you have more chances to get answers. I never worked with smppbox but if I'm not wrong, you need to use routing options in kannel. Try a search on smppbox + routing on kannel list. Regards Alvaro |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.NET www.smsglobal.com.mx y www.pravcom.com On Wed, Jul 24, 2013 at 6:59 PM, Christopher Ward c.j.ward26...@gmail.com wrote: Thanks for the reply. I do have smppbox, but I'm more after how to approach the configuration to allow me to HTTP POST to the api on the lamp server. As in at which point in the Kannel service can I achieve this? i.e Smppbox -- loop back smsc -- bearer box -- sms box --- HTTP PHP api What and where do I need to configure in order to HTTP POST? Thanks, Chris You need smppbox for that. Is included in kannel sources. Regards Alvaro On 7/23/13, Christopher Ward c.j.ward26...@gmail.com wrote: Currently doing some work on a server that provides SMS services, and utilises their own PHP apis to do so. However a user wishes to use SMPP in order to send and receive their batches of SMS. Ideally what I am required to do is configure an SMPP Server to receive incoming requests from the client to send messages, but then instead translate the requests to an API on the server to handle it instead. Essentially I just need to make it appear to the user that SMPP is being used to handle their SMS batches whilst instead we use our usual SMS send API like normal. I know Kannel utilises HTTP requests, so I imagine it would be as simple as configuring the gateway as an SMPP server to HTTP POST requests with necessary information (i.e. sender, destination, message, time etc) to a url on our Apache server, but I am a bit lost at which point in the configuration I can achieve such without setting up any of the SMS sending\receiving features of the software itself. Running on: CentOS 5 virtual server LAMP stack gateway-1.4.3 source installed libxml2 and libxml2-dev Any pointers would be greatly appreciated. -- |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.NET www.smsglobal.com.mx y www.pravcom.com
Unsubscribe
Unsubscribe From: spameden spame...@gmail.com To: Porter, Kelvin kelvin.por...@h3net.com Cc: de...@kannel.org de...@kannel.org; users@kannel.org users@kannel.org Sent: Tuesday, July 23, 2013 12:31 PM Subject: Re: Proposal for Real-time Routing in opensmppbox and bearerbox Hi! 2013/7/23 Porter, Kelvin kelvin.por...@h3net.com Hi, Responses below. Regards, Kelvin R. Porter From:spameden [mailto:spame...@gmail.com] Sent: Monday, July 22, 2013 6:23 PM To: Porter, Kelvin Cc: de...@kannel.org; users@kannel.org Subject: Re: Proposal for Real-time Routing in opensmppbox and bearerbox 2013/7/23 Porter, Kelvin kelvin.por...@h3net.com Hi, In the straightforward implementation, the load on the database would be 1 query per message sent (MT) and 1 query per message received (MO) (excluding situations where loopback occurred). A caching component could be added separately afterwards. The trade-offs would involve added code complexity, and the increasing latency in having database changes affect message routing. Different applications (e.g., A2P vs. P2P) might or might not see much benefit depending on how long the caching interval is, the rate of back-and-forth conversation, and the size of the cache. I am not familiar with all aspects of the code base, is there a caching mechanism that can be reused? I think there is no caching mechanism at all and grace reload is not implemented yet. Stipe was posting a patch earlier giving kannel the ability to gracefully reload it's configuration, but I think it's still bugy and needs to be cleaned up before accepted in the codebase. [KRP] That would be great. Is it for both opensmppbox and bearerbox? How would you trigger the reload on opensmppbox? Bearerbox only. Here is a patch - http://pastebin.com/v4rSRHrJ (I hope Stipe wouldnt mind posting it). The problem getting configuration from SQL is 1 more query per MT, if you have busy site with huge traffic (100-200 MT /sec) it could affect on your database, so caching definitely needed somehow. Alternatively you can look into storing configuration into memcached. [KRP] 100 – 200 T/sec does not seem that like that many transactions for one of our servers. Well, in this case you get 100-200 additional queries, it was just an example and rly depends on your database workload. [KRP] I can definitely look into a caching component as a subsequent enhancement. The route mechanism you're wanting can be implemented without database as well using add-smsc / remove-smsc commands for example. I'm using myself this 2 hooks for failsafe configuration (when 1 of the smsc goes down, I change with sed 'allowed-smsc-id' directive and re-add via remove-smsc, add-smsc commands specific smsc - everything done automatically via monit with additional scripts). [KRP] Unfortunately, that will not address my needs. I need to be able to add and remove numbers dynamically and affect their routing accordingly. I even heard someone implemented whole kannel configuration in the database, if you could make it - it would be awesome, because it would be MUCH easier to code web interface for kannel to configure it more easily. [KRP] Well, you could not implement the entire configuration in a database, because the process needs configuration information to find the database. True, ofc, you need to provide connection settings as in everywhere. Also, currently, the configuration is read in once at start up time. The code would need to be changed to consult the database or keep in sync with it dynamically. I am proposing an enhancement that would dynamically consult the database (when configured to do so). Migrating the code to dynamic configuration would be useful, I believe; however, moving some or all of the code in this direction would be a significant undertaking. I'm not against your proposal, just thinking about potential problems you might get .. The best plan is to make different engines, i.e. MySQL / PostgreSQL / Oracle / etc. Only dynamic variables like smsbox-route and various smsc settings should be kept into the database to operate them on the fly I think.. Other data like DLR / bearerbox core settings can be static in the configuration I think. Anyways, I'm waiting for your version of the patched opensmppbox / bearerbox to test out! :) I think that if caching is added that it should be configurable as to size and duration. Regards, Kelvin R. Porter From:spameden [mailto:spame...@gmail.com] Sent: Monday, July 22, 2013 3:55 PM To: Porter, Kelvin Cc: de...@kannel.org; users@kannel.org Subject: Re: Proposal for Real-time Routing in opensmppbox and bearerbox Interesting idea, but what about load on the database? Will it be cached or it's gonna get results from the database everytime SMS arrives? 2013/7/23 Porter, Kelvin kelvin.por...@h3net.com Hi, I have included a proposed enhancement for routing message based
Bearerbox Configuration core parameters not being read?
:09:25 [63821] [9] INFO: Logging thread `9' to logfile `/var/log/kannel/smsc-sim2.log' with level `4'. 2013-07-05 08:09:25 [63821] [0] INFO: DLR rerouting for smsc id sim-21 disabled. 2013-07-05 08:09:25 [63821] [0] INFO: Added logfile `/var/log/kannel/smsc-sim2.log' with level `4'. 2013-07-05 08:09:25 [63821] [0] DEBUG: Started thread 10 (gw/smsc/smsc_smpp.c:io_thread) 2013-07-05 08:09:25 [63821] [0] DEBUG: Started thread 11 (gw/smsc/smsc_smpp.c:io_thread) 2013-07-05 08:09:25 [63821] [10] DEBUG: Thread 10 (gw/smsc/smsc_smpp.c:io_thread) maps to pid 63821. 2013-07-05 08:09:25 [63821] [11] DEBUG: Thread 11 (gw/smsc/smsc_smpp.c:io_thread) maps to pid 63821. 2013-07-05 08:09:25 [63821] [10] INFO: Logging thread `10' to logfile `/var/log/kannel/smsc-sim2.log' with level `4'. 2013-07-05 08:09:25 [63821] [11] INFO: Logging thread `11' to logfile `/var/log/kannel/smsc-sim2.log' with level `4'. 2013-07-05 08:09:25 [63821] [0] INFO: DLR rerouting for smsc id sim-21 disabled. 2013-07-05 08:09:25 [63821] [0] INFO: Added logfile `/var/log/kannel/smsc-sim2.log' with level `4'. 2013-07-05 08:09:25 [63821] [0] DEBUG: Started thread 12 (gw/smsc/smsc_smpp.c:io_thread) 2013-07-05 08:09:25 [63821] [0] DEBUG: Started thread 13 (gw/smsc/smsc_smpp.c:io_thread) 2013-07-05 08:09:25 [63821] [12] DEBUG: Thread 12 (gw/smsc/smsc_smpp.c:io_thread) maps to pid 63821. 2013-07-05 08:09:25 [63821] [13] DEBUG: Thread 13 (gw/smsc/smsc_smpp.c:io_thread) maps to pid 63821. 2013-07-05 08:09:25 [63821] [12] INFO: Logging thread `12' to logfile `/var/log/kannel/smsc-sim2.log' with level `4'. 2013-07-05 08:09:25 [63821] [13] INFO: Logging thread `13' to logfile `/var/log/kannel/smsc-sim2.log' with level `4'. 2013-07-05 08:09:25 [63821] [0] DEBUG: Started thread 14 (gw/bb_smscconn.c:sms_router) 2013-07-05 08:09:25 [63821] [0] INFO: 2013-07-05 08:09:25 [63821] [0] INFO: Kannel bearerbox II version 1.4.3 starting 2013-07-05 08:09:25 [63821] [0] INFO: MAIN: Start-up done, entering mainloop Thanks !!! David Szanto
USSD session attached to a particular sms-service/get-url
Hi People, I have configured kannel to connecto to 2 different ussd gateway, I also have configured kannel to have 2 sms-service with 2 different urls. I want to know if it's possible to make kannel aware of the concept of ussd sessions so that when a new ussd session is established (when kannel receives one pdu with a particular ussd_service_op), then it will deliver subsequent pdus asociated with that same ussd session to the same sms-service get-url. Is that possible ? How you guys work when you need to have load balancing your ussd applications ? Kind regards and thanks for the support. -- David Hofmann ADVERTENCIA LEGAL Le informamos, como destinatario de este mensaje, que el contenido del correo electr?nico enviado desde esta cuenta no representa necesariamente la opini?n de las empresas conformantes del Grupo Millicom en Paraguay, ni del Grupo Millicom mismo, por lo que ninguna de ?stas asumen responsabilidad alguna por el mismo, ni en cuanto a su contenido, ni en cuanto a su veracidad, ni en cuanto a su integridad, ni por la circunstancia de que la misma vulnere o sea susceptible de vulnerar la confidencialidad de la informaci?n transmitida. Si no consintiese en la utilizaci?n del correo electr?nico o de las comunicaciones v?a internet, le rogamos nos lo comunique y ponga en nuestro conocimiento de manera inmediata. Este mensaje va dirigido de manera exclusiva a su destinatario, y contiene informaci?n confidencial cuya divulgaci?n no est? permitida por la ley. En caso de haber recibido este mensaje por error, le rogamos que de forma inmediata nos lo comunique mediante correo electr?nico remitido a nuestra atenci?n o a trav?s del tel?fono (+ 595 21) 618 9000, y proceda a su eliminaci?n, as? como a a la eliminaci?n de cualquier documento adjunto al mismo. Asimismo, le comunicamos que la distribuci?n, copia o utilizaci?n de este mensaje o de cualquier documento adjunto al mismo, cualquiera que fuera su finalidad, constituyen conductas prohibidas por la ley
Unsubscribe
Stop -Original Message- From: Alexander Malysh amal...@kannel.org Sent: 5/3/2013 8:12 AM To: Ashish Agarwal ashisha...@gmail.com Cc: users users@kannel.org Subject: Re: MO Concatenation using SAR Hi, SMPP Spec say: For GSM networks, the concatenation related TLVs (sar_msg_ref_num, sar_total_segments, sar_segment_seqnum) or port addressing related TLVs (source_port, dest_port) cannot be used in conjunction with encoded User Data Header in the short_message (user data) field. This means that the above listed TLVs cannot be used if the User Data Header Indicator flag is set. If you see such error then your SMPP-Server is buggy and send both UDHI and sar_. Check with your operator... Alex Am 03.05.2013 um 14:25 schrieb Ashish Agarwal ashisha...@gmail.com: Hello, The SMSC is sending MO on smpp, but kannel is not able to understand the long message, I get the following error 2013-05-03 17:44:33 [29875] [7] ERROR: SMPP[SMSC1]: sar_msg_ref_num, sar_segment_seqnum, sar_total_segments in conjuction with UDHI used, rejected. Can anybody help me with configuring TLV values using SAR for proper concatenation reassembling and forward to url? -- Regards, Ashish
NOT REALLY SOLVED Multiple SMSC connections to the same SMSC Instace DLR inconsistency
Hi everyone! We have just updated kannel to the las svn in trunk version (since in our current version throughput was not working properly), and although now Throughput is working as it should, we're back with the DLR problem on multiple SMSCs. We've made it so that the SMSC Simulators wait at least 1 second before sending DLR information back, but we still get this message: 2013-02-14 20:51:05 [10705] [101] DEBUG: SMPP[sim-1212] handle_pdu, got DLR 2013-02-14 20:51:05 [10705] [101] DEBUG: DLR[internal]: Looking for DLR smsc=sim-1212, ts=2125, dst=9869421485, type=4 2013-02-14 20:51:05 [10705] [101] WARNING: DLR[internal]: DLR from SMSCsim-1212 for DST9869421485 not found. 2013-02-14 20:51:05 [10705] [101] ERROR: SMPP[sim-1212]: got DLR but could not find message or was not interested in it id2125 dst9869421485, type4 With the older version (version 1.4.3, tar.gz downloaded from the site), DLRs work perfectly, but throughput doesn't. And now, after updating to the last svn trunk, kannel can't match DLR messages to it's original MT message. Any clues anyone? Thanks David Szanto El 12/02/13 20:17, Rene Kluwen escribió: This this is a Kannel bug. *From:*users-boun...@kannel.org [mailto:users-boun...@kannel.org] *On Behalf Of *David Szanto *Sent:* vrijdag 8 februari 2013 8:22 *To:* users@kannel.org *Subject:* Re: AW: SOLVED Multiple SMSC connections to the same SMSC Instace DLR inconsistency Hi everyone! First off, thanks for all the helpful comments regarding this issue. In the end, the problem was the SMSC. We where using an SMSC Simulator to carry out the functional and load test. Que delay time for the transition of each message state was set to 0. Due to this, Bearerbox would get final state messages (like DELIVRD) before even creating the ACCEPTED notification. So, it would actually not have a message registered for the DLR it was getting from the SMSC. After setting the Delay time to anything 0, DLR worked like a charm! Still, we learned a lot about how kannel sets IDs for messages and matches them to the corresponding DLRs thanks to all your comments! Thanks a lot people!! David Szanto 05/02/13 10:02, David Szanto escribió: Hi spameden! Thanks for the info! that is VERY helpfull. We've been testing a lot using the same smsc-id but we're still getting the error message at least 900 times for every 10 DLR recieved. The only difference now is that the message mentions type=2 instead of 1. 2013-02-04 11:92:35 [33491] [11] ERROR: SMPP[A]: got DLR but could not find message or was not interested in it id27299 dst20034628200743, type2 We'll be testing what Alvaro suggested regarding the msg-id-type parameter in conjuntion to having the same smsc-id, which is clearly something we should be doing. Also, we're not very sure if some routing would help or not in this case. Thanks for all your input!! David El 04/02/13 09:55, spameden escribió: Kannel matches specific DLR via SMSC-id (defined in the config) and Unique ID given by your SMSC operator. Are you using MySQL as a backend for DLRs? As everyone stated before if you're using multiple logins to the same SMSC operator just use same SMSC-ID. 2013/2/4 David Szanto dsza...@genasys.com mailto:dsza...@genasys.com Hi Thomas!! Thanks for the tips!! We did try setting the same name for all smsc-id's, but had no luck. We still got the error message for certain DLR that got unmatch with their original MT message. The problem was that since they all had the same ids, we could tell what connection was used to send back the DLR. Yet, it didn't help much. We'll try doing what Alvaro suggested (testing the DLR id in Hex vs Decimal, etc... ) plus setting all smsc-id's the same. Correct me if I'm wrong, but kannel sets the ID for the message using the message ID + the SMSC-ID, right? Are there any more parameters used in the equation? Thanks you all for the help!!! El 01/02/13 14:51, Thomas Göttgens escribió: Use the same name for the SMSC ID's. So not A,B,C and D but just A. This way no matter what link the DLR is delivered on, it will match the original message. We've had the same setup in production with 6 binds (via EMI/UCP) for years. -Ursprüngliche Nachricht- Von:users-boun...@kannel.org mailto:users-boun...@kannel.org [mailto:users-boun...@kannel.org] Im Auftrag von David Szanto Gesendet: Freitag, 1. Februar 2013 14:10 An:users@kannel.org mailto:users@kannel.org Betreff: Multiple SMSC connections to the same SMSC Instace DLR inconsistency Hi everyone
Re: NOT REALLY SOLVED Multiple SMSC connections to the same SMSC Instace DLR inconsistency
Hi spameden, We thought so, but we've delayed the DLR 1 second and the error still shows up. We are not using sqlbox. DLRs are handled in memory. group = core admin-port = 13000 admin-password = XXX smsbox-port = 13001 log-file = /var/log/kannel/kannel.log log-level = 4 access-log = /var/log/kannel/access.log We've been checking the source code, and we see that for SMPP, the destination number is NOT used ever when looking for matching DLR messages. dlrmsg = dlr_find(smpp-conn-id, tmp, /* smsc message id */ destination_addr, /* destination */ dlrstat, 0); at smsc/smsc_smpp.c line 1471. The last parameter (0) means that destination number is not used for matching DLRs. Is this correct? In the previous version, destination numbers ARE used to find the corresponding message. Any other clues?? (Thanks for the help guys!!) David Szanto El 14/02/13 11:48, spameden escribió: It might be the same problem when DLR comes before MT is registered. Do you use sqlbox? 2013/2/14 David Szanto dsza...@genasys.com: Hi everyone! We have just updated kannel to the las svn in trunk version (since in our current version throughput was not working properly), and although now Throughput is working as it should, we're back with the DLR problem on multiple SMSCs. We've made it so that the SMSC Simulators wait at least 1 second before sending DLR information back, but we still get this message: 2013-02-14 20:51:05 [10705] [101] DEBUG: SMPP[sim-1212] handle_pdu, got DLR 2013-02-14 20:51:05 [10705] [101] DEBUG: DLR[internal]: Looking for DLR smsc=sim-1212, ts=2125, dst=9869421485, type=4 2013-02-14 20:51:05 [10705] [101] WARNING: DLR[internal]: DLR from SMSCsim-1212 for DST9869421485 not found. 2013-02-14 20:51:05 [10705] [101] ERROR: SMPP[sim-1212]: got DLR but could not find message or was not interested in it id2125 dst9869421485, type4 With the older version (version 1.4.3, tar.gz downloaded from the site), DLRs work perfectly, but throughput doesn't. And now, after updating to the last svn trunk, kannel can't match DLR messages to it's original MT message. Any clues anyone? Thanks David Szanto El 12/02/13 20:17, Rene Kluwen escribió: This this is a Kannel bug. From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of David Szanto Sent: vrijdag 8 februari 2013 8:22 To: users@kannel.org Subject: Re: AW: SOLVED Multiple SMSC connections to the same SMSC Instace DLR inconsistency Hi everyone! First off, thanks for all the helpful comments regarding this issue. In the end, the problem was the SMSC. We where using an SMSC Simulator to carry out the functional and load test. Que delay time for the transition of each message state was set to 0. Due to this, Bearerbox would get final state messages (like DELIVRD) before even creating the ACCEPTED notification. So, it would actually not have a message registered for the DLR it was getting from the SMSC. After setting the Delay time to anything 0, DLR worked like a charm! Still, we learned a lot about how kannel sets IDs for messages and matches them to the corresponding DLRs thanks to all your comments! Thanks a lot people!! David Szanto 05/02/13 10:02, David Szanto escribió: Hi spameden! Thanks for the info! that is VERY helpfull. We've been testing a lot using the same smsc-id but we're still getting the error message at least 900 times for every 10 DLR recieved. The only difference now is that the message mentions type=2 instead of 1. 2013-02-04 11:92:35 [33491] [11] ERROR: SMPP[A]: got DLR but could not find message or was not interested in it id27299 dst20034628200743, type2 We'll be testing what Alvaro suggested regarding the msg-id-type parameter in conjuntion to having the same smsc-id, which is clearly something we should be doing. Also, we're not very sure if some routing would help or not in this case. Thanks for all your input!! David El 04/02/13 09:55, spameden escribió: Kannel matches specific DLR via SMSC-id (defined in the config) and Unique ID given by your SMSC operator. Are you using MySQL as a backend for DLRs? As everyone stated before if you're using multiple logins to the same SMSC operator just use same SMSC-ID. 2013/2/4 David Szanto dsza...@genasys.com Hi Thomas!! Thanks for the tips!! We did try setting the same name for all smsc-id's, but had no luck. We still got the error message for certain DLR that got unmatch with their original MT message. The problem was that since they all had the same ids, we could tell what connection was used to send back the DLR. Yet, it didn't help much. We'll try doing what Alvaro suggested (testing the DLR id in Hex vs Decimal, etc... ) plus setting all smsc-id's the same. Correct me if I'm wrong, but kannel sets the ID for the message using the message ID + the SMSC-ID, right? Are there any more parameters used in the equation? Thanks you all for the help!!! El 01/02/13 14:51, Thomas
Re: NOT REALLY SOLVED Multiple SMSC connections to the same SMSC Instace DLR inconsistency
Hi again!! We've also come to realize that the trunk version is Development, so we're not using it... In which case, we have the throttling problem. We've seen there are patches that fix this problems, but don't know wether we should simply apply them in the 1.4.3 stable version directly, or if we should check out some specific branch. Specifically, could we simply apply the following file in the originally downloaded 1.4.3 stable version for it to work? https://redmine.kannel.org/projects/kannel/repository/revisions/4772/entry/trunk/gw/smsc/smsc_smpp.c Cheers!! David Szanto El 14/02/13 12:14, David Szanto escribió: Hi spameden, We thought so, but we've delayed the DLR 1 second and the error still shows up. We are not using sqlbox. DLRs are handled in memory. group = core admin-port = 13000 admin-password = XXX smsbox-port = 13001 log-file = /var/log/kannel/kannel.log log-level = 4 access-log = /var/log/kannel/access.log We've been checking the source code, and we see that for SMPP, the destination number is NOT used ever when looking for matching DLR messages. dlrmsg = dlr_find(smpp-conn-id, tmp, /* smsc message id */ destination_addr, /* destination */ dlrstat, 0); at smsc/smsc_smpp.c line 1471. The last parameter (0) means that destination number is not used for matching DLRs. Is this correct? In the previous version, destination numbers ARE used to find the corresponding message. Any other clues?? (Thanks for the help guys!!) David Szanto El 14/02/13 11:48, spameden escribió: It might be the same problem when DLR comes before MT is registered. Do you use sqlbox? 2013/2/14 David Szanto dsza...@genasys.com: Hi everyone! We have just updated kannel to the las svn in trunk version (since in our current version throughput was not working properly), and although now Throughput is working as it should, we're back with the DLR problem on multiple SMSCs. We've made it so that the SMSC Simulators wait at least 1 second before sending DLR information back, but we still get this message: 2013-02-14 20:51:05 [10705] [101] DEBUG: SMPP[sim-1212] handle_pdu, got DLR 2013-02-14 20:51:05 [10705] [101] DEBUG: DLR[internal]: Looking for DLR smsc=sim-1212, ts=2125, dst=9869421485, type=4 2013-02-14 20:51:05 [10705] [101] WARNING: DLR[internal]: DLR from SMSCsim-1212 for DST9869421485 not found. 2013-02-14 20:51:05 [10705] [101] ERROR: SMPP[sim-1212]: got DLR but could not find message or was not interested in it id2125 dst9869421485, type4 With the older version (version 1.4.3, tar.gz downloaded from the site), DLRs work perfectly, but throughput doesn't. And now, after updating to the last svn trunk, kannel can't match DLR messages to it's original MT message. Any clues anyone? Thanks David Szanto El 12/02/13 20:17, Rene Kluwen escribió: This this is a Kannel bug. From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of David Szanto Sent: vrijdag 8 februari 2013 8:22 To: users@kannel.org Subject: Re: AW: SOLVED Multiple SMSC connections to the same SMSC Instace DLR inconsistency Hi everyone! First off, thanks for all the helpful comments regarding this issue. In the end, the problem was the SMSC. We where using an SMSC Simulator to carry out the functional and load test. Que delay time for the transition of each message state was set to 0. Due to this, Bearerbox would get final state messages (like DELIVRD) before even creating the ACCEPTED notification. So, it would actually not have a message registered for the DLR it was getting from the SMSC. After setting the Delay time to anything 0, DLR worked like a charm! Still, we learned a lot about how kannel sets IDs for messages and matches them to the corresponding DLRs thanks to all your comments! Thanks a lot people!! David Szanto 05/02/13 10:02, David Szanto escribió: Hi spameden! Thanks for the info! that is VERY helpfull. We've been testing a lot using the same smsc-id but we're still getting the error message at least 900 times for every 10 DLR recieved. The only difference now is that the message mentions type=2 instead of 1. 2013-02-04 11:92:35 [33491] [11] ERROR: SMPP[A]: got DLR but could not find message or was not interested in it id27299 dst20034628200743, type2 We'll be testing what Alvaro suggested regarding the msg-id-type parameter in conjuntion to having the same smsc-id, which is clearly something we should be doing. Also, we're not very sure if some routing would help or not in this case. Thanks for all your input!! David El 04/02/13 09:55, spameden escribió: Kannel matches specific DLR via SMSC-id (defined in the config) and Unique ID given by your SMSC operator. Are you using MySQL as a backend for DLRs? As everyone stated before if you're using multiple logins to the same SMSC operator just use same SMSC-ID. 2013/2/4 David Szanto dsza...@genasys.com Hi Thomas
Re: NOT REALLY SOLVED Multiple SMSC connections to the same SMSC Instace DLR inconsistency
Hi spameden. And thanks again for the quick response!!! We did make sure our messages have at most 160 characters. And we're not using DB, so not much to see there. Do you know of any patch we could apply to the original 1.4.3 in order to make throttle control work? Thanks again! David Szanto El 14/02/13 12:55, spameden escribió: Trunk version is pretty much stable, I've been using for a while svn revision 5001, last uptime was 90days, had to reboot kannel due box upgrade. The only issues with DLR matching I've encountered (possible scenarios): 1) kannel requests only 1st part DLR of the message, so if your SMSC sends DLRs for other parts of concatenated messages they won't be matched (message should be 160 english symbols in case of coding=0 or 70 in case of coding=2). 2) if DB goes down in case of sqlbox DLR also won't be matched 3) if there is constant load and you're restarting kannel some of the DLRs might be missing, because bearerbox is very slow at shutdown and still receiving DLRs whilst sqlbox is already down (which handles DLRs) I use MySQL as a backend for storing DLRs, I'll check later what you're experiencing on my test environment and report back, but I'm quite sure that problem lies somewhere else. 2013/2/14 David Szanto dsza...@genasys.com: Hi again!! We've also come to realize that the trunk version is Development, so we're not using it... In which case, we have the throttling problem. We've seen there are patches that fix this problems, but don't know wether we should simply apply them in the 1.4.3 stable version directly, or if we should check out some specific branch. Specifically, could we simply apply the following file in the originally downloaded 1.4.3 stable version for it to work? https://redmine.kannel.org/projects/kannel/repository/revisions/4772/entry/trunk/gw/smsc/smsc_smpp.c Cheers!! David Szanto El 14/02/13 12:14, David Szanto escribió: Hi spameden, We thought so, but we've delayed the DLR 1 second and the error still shows up. We are not using sqlbox. DLRs are handled in memory. group = core admin-port = 13000 admin-password = XXX smsbox-port = 13001 log-file = /var/log/kannel/kannel.log log-level = 4 access-log = /var/log/kannel/access.log We've been checking the source code, and we see that for SMPP, the destination number is NOT used ever when looking for matching DLR messages. dlrmsg = dlr_find(smpp-conn-id, tmp, /* smsc message id */ destination_addr, /* destination */ dlrstat, 0); at smsc/smsc_smpp.c line 1471. The last parameter (0) means that destination number is not used for matching DLRs. Is this correct? In the previous version, destination numbers ARE used to find the corresponding message. Any other clues?? (Thanks for the help guys!!) David Szanto El 14/02/13 11:48, spameden escribió: It might be the same problem when DLR comes before MT is registered. Do you use sqlbox? 2013/2/14 David Szanto dsza...@genasys.com: Hi everyone! We have just updated kannel to the las svn in trunk version (since in our current version throughput was not working properly), and although now Throughput is working as it should, we're back with the DLR problem on multiple SMSCs. We've made it so that the SMSC Simulators wait at least 1 second before sending DLR information back, but we still get this message: 2013-02-14 20:51:05 [10705] [101] DEBUG: SMPP[sim-1212] handle_pdu, got DLR 2013-02-14 20:51:05 [10705] [101] DEBUG: DLR[internal]: Looking for DLR smsc=sim-1212, ts=2125, dst=9869421485, type=4 2013-02-14 20:51:05 [10705] [101] WARNING: DLR[internal]: DLR from SMSCsim-1212 for DST9869421485 not found. 2013-02-14 20:51:05 [10705] [101] ERROR: SMPP[sim-1212]: got DLR but could not find message or was not interested in it id2125 dst9869421485, type4 With the older version (version 1.4.3, tar.gz downloaded from the site), DLRs work perfectly, but throughput doesn't. And now, after updating to the last svn trunk, kannel can't match DLR messages to it's original MT message. Any clues anyone? Thanks David Szanto El 12/02/13 20:17, Rene Kluwen escribió: This this is a Kannel bug. From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of David Szanto Sent: vrijdag 8 februari 2013 8:22 To: users@kannel.org Subject: Re: AW: SOLVED Multiple SMSC connections to the same SMSC Instace DLR inconsistency Hi everyone! First off, thanks for all the helpful comments regarding this issue. In the end, the problem was the SMSC. We where using an SMSC Simulator to carry out the functional and load test. Que delay time for the transition of each message state was set to 0. Due to this, Bearerbox would get final state messages (like DELIVRD) before even creating the ACCEPTED notification. So, it would actually not have a message registered for the DLR it was getting from the SMSC. After setting the Delay time to anything 0, DLR worked like a charm! Still, we learned
Re: NOT REALLY SOLVED Multiple SMSC connections to the same SMSC Instace DLR inconsistency
Thanks for all the comments! Rinor, the simulator we are using is a java implementation using SMPP protocol called SMPPSim (or SMPP Simulator). We increased the DLR delay from 0.05 to 1 second and got the same result. We do restart all simulators (12 with 4 binds each) before every test. All binds have a recieve-port and transmit port (although the same port is used, but it's not in transceiver mode). This last is a requirement. Yet we're VERY thankful for all the tip!! Anyway, since version 1.5.0 is still development, we've decided to go back to 1.4.3. Nevertheless, Throttling problem persists. We've come to realize the problem relies on gwthread_sleep, which is not really sleeping at all... ;) I've been looking around for some patch to fix this but couldn't find one. We even tried using usleep instead on smsc_smpp.c, but weird things happen when we do this. If anyone has a 1.4.3 revision with this problem solved, We'd very much appreciate it if someone could point us on the right direction. Thanks, David Szanto El 14/02/13 17:13, Rinor Hoxha escribió: Out of curiosity, 1)What is the simulator? (some when in high load, duplicate the id even in the same session) 2)Can you increase the DLR delay = 3 secs on simulator and retry 3)Probably you already know this, however restarting the simulator the foreign ID are restarted from beginning 4)Can you set 3 connections transmitter only and the fourth one receiver only and test We are using it in production and dlr matching is working fine. The removal of destinations in matching has a point. Sometimes some providers,based on scenarios, for example require you put + in front of MSISDN but return the MSISDN without + in DLR (or the reverse)(there are many other scenarios related to this). However the code is there in the dev branch and is just commented so if you need it you can use it. Br, Rinor On Thu, Feb 14, 2013 at 1:02 PM, David Szanto dsza...@genasys.com mailto:dsza...@genasys.com wrote: Hi spameden. And thanks again for the quick response!!! We did make sure our messages have at most 160 characters. And we're not using DB, so not much to see there. Do you know of any patch we could apply to the original 1.4.3 in order to make throttle control work? Thanks again! David Szanto El 14/02/13 12:55, spameden escribió: Trunk version is pretty much stable, I've been using for a while svn revision 5001, last uptime was 90days, had to reboot kannel due box upgrade. The only issues with DLR matching I've encountered (possible scenarios): 1) kannel requests only 1st part DLR of the message, so if your SMSC sends DLRs for other parts of concatenated messages they won't be matched (message should be 160 english symbols in case of coding=0 or 70 in case of coding=2). 2) if DB goes down in case of sqlbox DLR also won't be matched 3) if there is constant load and you're restarting kannel some of the DLRs might be missing, because bearerbox is very slow at shutdown and still receiving DLRs whilst sqlbox is already down (which handles DLRs) I use MySQL as a backend for storing DLRs, I'll check later what you're experiencing on my test environment and report back, but I'm quite sure that problem lies somewhere else. 2013/2/14 David Szanto dsza...@genasys.com mailto:dsza...@genasys.com: Hi again!! We've also come to realize that the trunk version is Development, so we're not using it... In which case, we have the throttling problem. We've seen there are patches that fix this problems, but don't know wether we should simply apply them in the 1.4.3 stable version directly, or if we should check out some specific branch. Specifically, could we simply apply the following file in the originally downloaded 1.4.3 stable version for it to work? https://redmine.kannel.org/projects/kannel/repository/revisions/4772/entry/trunk/gw/smsc/smsc_smpp.c Cheers!! David Szanto El 14/02/13 12:14, David Szanto escribió: Hi spameden, We thought so, but we've delayed the DLR 1 second and the error still shows up. We are not using sqlbox. DLRs are handled in memory. group = core admin-port = 13000 admin-password = XXX smsbox-port = 13001 log-file = /var/log/kannel/kannel.log log-level = 4 access-log = /var/log/kannel/access.log We've been checking the source code, and we see
Re: AW: SOLVED Multiple SMSC connections to the same SMSC Instace DLR inconsistency
Hi everyone! First off, thanks for all the helpful comments regarding this issue. In the end, the problem was the SMSC. We where using an SMSC Simulator to carry out the functional and load test. Que delay time for the transition of each message state was set to 0. Due to this, Bearerbox would get final state messages (like DELIVRD) before even creating the ACCEPTED notification. So, it would actually not have a message registered for the DLR it was getting from the SMSC. After setting the Delay time to anything 0, DLR worked like a charm! Still, we learned a lot about how kannel sets IDs for messages and matches them to the corresponding DLRs thanks to all your comments! Thanks a lot people!! David Szanto 05/02/13 10:02, David Szanto escribió: Hi spameden! Thanks for the info! that is VERY helpfull. We've been testing a lot using the same smsc-id but we're still getting the error message at least 900 times for every 10 DLR recieved. The only difference now is that the message mentions type=2 instead of 1. 2013-02-04 11:92:35 [33491] [11] ERROR: SMPP[A]: got DLR but could not find message or was not interested in it id27299 dst20034628200743, type2 We'll be testing what Alvaro suggested regarding the msg-id-type parameter in conjuntion to having the same smsc-id, which is clearly something we should be doing. Also, we're not very sure if some routing would help or not in this case. Thanks for all your input!! David El 04/02/13 09:55, spameden escribió: Kannel matches specific DLR via SMSC-id (defined in the config) and Unique ID given by your SMSC operator. Are you using MySQL as a backend for DLRs? As everyone stated before if you're using multiple logins to the same SMSC operator just use same SMSC-ID. 2013/2/4 David Szanto dsza...@genasys.com mailto:dsza...@genasys.com Hi Thomas!! Thanks for the tips!! We did try setting the same name for all smsc-id's, but had no luck. We still got the error message for certain DLR that got unmatch with their original MT message. The problem was that since they all had the same ids, we could tell what connection was used to send back the DLR. Yet, it didn't help much. We'll try doing what Alvaro suggested (testing the DLR id in Hex vs Decimal, etc... ) plus setting all smsc-id's the same. Correct me if I'm wrong, but kannel sets the ID for the message using the message ID + the SMSC-ID, right? Are there any more parameters used in the equation? Thanks you all for the help!!! El 01/02/13 14:51, Thomas Göttgens escribió: Use the same name for the SMSC ID's. So not A,B,C and D but just A. This way no matter what link the DLR is delivered on, it will match the original message. We've had the same setup in production with 6 binds (via EMI/UCP) for years. -Ursprüngliche Nachricht- Von:users-boun...@kannel.org mailto:users-boun...@kannel.org [mailto:users-boun...@kannel.org] Im Auftrag von David Szanto Gesendet: Freitag, 1. Februar 2013 14:10 An:users@kannel.org mailto:users@kannel.org Betreff: Multiple SMSC connections to the same SMSC Instace DLR inconsistency Hi everyone! We have a scenario with a single SMSC (using SMPP) for which we have created 4 binds. So basically we have 4 SMSC groups in kannel for a single SMSC (and single account). We'll call Binds A,B,C and D. So, message 328515 is sent using bind A, but DLR for this message is delivered from the SMSC using bind B, which results in the following log error: smsc-sim4.log:2013-01-29 12:55:57 [16831] [35] ERROR: SMPP[B]: got DLR but could not find message or was not interested in it id328515 dst20034628200743, type1 Except for the smsc-id parameter, all other SMSC configuration parameters in kannel are identical: group = smsc smsc = smpp smsc-id = A host = smschost port = 2771 receive-port = 2771 smsc-username = smppclient1 smsc-password = password system-type = VMA log-file = /var/log/kannel/smsc-sim1.log log-level = 0 group = smsc smsc = smpp smsc-id = B host = smschost port=2771 receive-port = 2771 smsc-username = smppclient1 smsc-password = password system-type = VMA log-file = /var/log/kannel/smsc-sim1.log log-level = 2 group = smsc smsc = smpp smsc-id = C host = smschost port=2771 receive-port = 2771 smsc-username = smppclient1 smsc-password = password system-type = VMA log-file = /var/log/kannel/smsc-sim1.log log-level = 2 group = smsc smsc = smpp smsc-id = D host = smschost port=2771 receive-port = 2771 smsc-username = smppclient1 smsc-password = password system-type = VMA log-file = /var/log/kannel/smsc-sim1.log log-level = 2 We believe that because the DLR messages are incomming using
Re: AW: Multiple SMSC connections to the same SMSC Instace DLR inconsistency
Hi spameden! Thanks for the info! that is VERY helpfull. We've been testing a lot using the same smsc-id but we're still getting the error message at least 900 times for every 10 DLR recieved. The only difference now is that the message mentions type=2 instead of 1. 2013-02-04 11:92:35 [33491] [11] ERROR: SMPP[A]: got DLR but could not find message or was not interested in it id27299 dst20034628200743, type2 We'll be testing what Alvaro suggested regarding the msg-id-type parameter in conjuntion to having the same smsc-id, which is clearly something we should be doing. Also, we're not very sure if some routing would help or not in this case. Thanks for all your input!! David El 04/02/13 09:55, spameden escribi: Kannel matches specific DLR via SMSC-id (defined in the config) and Unique ID given by your SMSC operator. Are you using MySQL as a backend for DLRs? As everyone stated before if you're using multiple logins to the same SMSC operator just use same SMSC-ID. 2013/2/4 David Szanto dsza...@genasys.com Hi Thomas!! Thanks for the tips!! We did try setting the same name for all smsc-id's, but had no luck. We still got the error message for certain DLR that got unmatch with their original MT message. The problem was that since they all had the same ids, we could tell what connection was used to send back the DLR. Yet, it didn't help much. We'll try doing what Alvaro suggested (testing the DLR id in Hex vs Decimal, etc... ) plus setting all smsc-id's the same. Correct me if I'm wrong, but kannel sets the ID for the message using the message ID + the SMSC-ID, right? Are there any more parameters used in the equation? Thanks you all for the help!!! El 01/02/13 14:51, Thomas Gttgens escribi: Use the same name for the SMSC ID's. So not A,B,C and D but just A. This way no matter what link the DLR is delivered on, it will match the original message. We've had the same setup in production with 6 binds (via EMI/UCP) for years. -Ursprngliche Nachricht- Von: users-boun...@kannel.org [mailto:users-boun...@kannel.org] Im Auftrag von David Szanto Gesendet: Freitag, 1. Februar 2013 14:10 An: users@kannel.org Betreff: Multiple SMSC connections to the same SMSC Instace DLR inconsistency Hi everyone! We have a scenario with a single SMSC (using SMPP) for which we have created 4 binds. So basically we have 4 SMSC groups in kannel for a single SMSC (and single account). We'll call Binds A,B,C and D. So, message 328515 is sent using bind A, but DLR for this message is delivered from the SMSC using bind B, which results in the following log error: smsc-sim4.log:2013-01-29 12:55:57 [16831] [35] ERROR: SMPP[B]: got DLR but could not find message or was not interested in it id328515 dst20034628200743, type1 Except for the smsc-id parameter, all other SMSC configuration parameters in kannel are identical: group = smsc smsc = smpp smsc-id = A host = smschost port = 2771 receive-port = 2771 smsc-username = smppclient1 smsc-password = password system-type = VMA log-file = /var/log/kannel/smsc-sim1.log log-level = 0 group = smsc smsc = smpp smsc-id = B host = smschost port=2771 receive-port = 2771 smsc-username = smppclient1 smsc-password = password system-type = VMA log-file = /var/log/kannel/smsc-sim1.log log-level = 2 group = smsc smsc = smpp smsc-id = C host = smschost port=2771 receive-port = 2771 smsc-username = smppclient1 smsc-password = password system-type = VMA log-file = /var/log/kannel/smsc-sim1.log log-level = 2 group = smsc smsc = smpp smsc-id = D host = smschost port=2771 receive-port = 2771 smsc-username = smppclient1 smsc-password = password system-type = VMA log-file = /var/log/kannel/smsc-sim1.log log-level = 2 We believe that because the DLR messages are incomming using a different smsc connection, the internal record for that message (328515) doesn't match up, thus leaving kannel not knowing what message the DLR recieved is for. So here is our question: If this is the problem: How can we avoid this? How can we assure kannel is able to match up DLR messages with their corresponding MT records? Any help will be greatly appreciated!! Thanks! David Szanto -- David Szanto Sistemas
Re: AW: Multiple SMSC connections to the same SMSC Instace DLR inconsistency
Hi Thomas!! Thanks for the tips!! We did try setting the same name for all smsc-id's, but had no luck. We still got the error message for certain DLR that got unmatch with their original MT message. The problem was that since they all had the same ids, we could tell what connection was used to send back the DLR. Yet, it didn't help much. We'll try doing what Alvaro suggested (testing the DLR id in Hex vs Decimal, etc... ) plus setting all smsc-id's the same. Correct me if I'm wrong, but kannel sets the ID for the message using the message ID + the SMSC-ID, right? Are there any more parameters used in the equation? Thanks you all for the help!!! El 01/02/13 14:51, Thomas Göttgens escribió: Use the same name for the SMSC ID's. So not A,B,C and D but just A. This way no matter what link the DLR is delivered on, it will match the original message. We've had the same setup in production with 6 binds (via EMI/UCP) for years. -Ursprüngliche Nachricht- Von: users-boun...@kannel.org [mailto:users-boun...@kannel.org] Im Auftrag von David Szanto Gesendet: Freitag, 1. Februar 2013 14:10 An: users@kannel.org Betreff: Multiple SMSC connections to the same SMSC Instace DLR inconsistency Hi everyone! We have a scenario with a single SMSC (using SMPP) for which we have created 4 binds. So basically we have 4 SMSC groups in kannel for a single SMSC (and single account). We'll call Binds A,B,C and D. So, message 328515 is sent using bind A, but DLR for this message is delivered from the SMSC using bind B, which results in the following log error: smsc-sim4.log:2013-01-29 12:55:57 [16831] [35] ERROR: SMPP[B]: got DLR but could not find message or was not interested in it id328515 dst20034628200743, type1 Except for the smsc-id parameter, all other SMSC configuration parameters in kannel are identical: group = smsc smsc = smpp smsc-id = A host = smschost port = 2771 receive-port = 2771 smsc-username = smppclient1 smsc-password = password system-type = VMA log-file = /var/log/kannel/smsc-sim1.log log-level = 0 group = smsc smsc = smpp smsc-id = B host = smschost port=2771 receive-port = 2771 smsc-username = smppclient1 smsc-password = password system-type = VMA log-file = /var/log/kannel/smsc-sim1.log log-level = 2 group = smsc smsc = smpp smsc-id = C host = smschost port=2771 receive-port = 2771 smsc-username = smppclient1 smsc-password = password system-type = VMA log-file = /var/log/kannel/smsc-sim1.log log-level = 2 group = smsc smsc = smpp smsc-id = D host = smschost port=2771 receive-port = 2771 smsc-username = smppclient1 smsc-password = password system-type = VMA log-file = /var/log/kannel/smsc-sim1.log log-level = 2 We believe that because the DLR messages are incomming using a different smsc connection, the internal record for that message (328515) doesn't match up, thus leaving kannel not knowing what message the DLR recieved is for. So here is our question: If this is the problem: How can we avoid this? How can we assure kannel is able to match up DLR messages with their corresponding MT records? Any help will be greatly appreciated!! Thanks! David Szanto -- David Szanto Sistemas (+34) 91 364 91 00 - ext. 116 dsza...@genasys.com Genasys II Spain, S.A.U. Pza. Sta. María Soledad Torres Acosta, 2, 4ºA 28004 Madrid www.genasys.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.
Multiple SMSC connections to the same SMSC Instace DLR inconsistency
Hi everyone! We have a scenario with a single SMSC (using SMPP) for which we have created 4 binds. So basically we have 4 SMSC groups in kannel for a single SMSC (and single account). We'll call Binds A,B,C and D. So, message 328515 is sent using bind A, but DLR for this message is delivered from the SMSC using bind B, which results in the following log error: smsc-sim4.log:2013-01-29 12:55:57 [16831] [35] ERROR: SMPP[B]: got DLR but could not find message or was not interested in it id328515 dst20034628200743, type1 Except for the smsc-id parameter, all other SMSC configuration parameters in kannel are identical: group = smsc smsc = smpp smsc-id = A host = smschost port = 2771 receive-port = 2771 smsc-username = smppclient1 smsc-password = password system-type = VMA log-file = /var/log/kannel/smsc-sim1.log log-level = 0 group = smsc smsc = smpp smsc-id = B host = smschost port=2771 receive-port = 2771 smsc-username = smppclient1 smsc-password = password system-type = VMA log-file = /var/log/kannel/smsc-sim1.log log-level = 2 group = smsc smsc = smpp smsc-id = C host = smschost port=2771 receive-port = 2771 smsc-username = smppclient1 smsc-password = password system-type = VMA log-file = /var/log/kannel/smsc-sim1.log log-level = 2 group = smsc smsc = smpp smsc-id = D host = smschost port=2771 receive-port = 2771 smsc-username = smppclient1 smsc-password = password system-type = VMA log-file = /var/log/kannel/smsc-sim1.log log-level = 2 We believe that because the DLR messages are incomming using a different smsc connection, the internal record for that message (328515) doesn't match up, thus leaving kannel not knowing what message the DLR recieved is for. So here is our question: If this is the problem: How can we avoid this? How can we assure kannel is able to match up DLR messages with their corresponding MT records? Any help will be greatly appreciated!! Thanks! David Szanto
Re: Multiple SMSC connections to the same SMSC Instace DLR inconsistency
Thanks for the prompt response!! I'll get the logs an publish them ASAP. I'll check for the parameter you mention as well. Thanks! David El 01/02/13 14:32, Alvaro Cornejo escribió: Can you post a log of transaction ? The issue probaly is on the id (328515). Some smsc use hex and some use Dec for the same id. There is a parameter dlr-id-type (or somenthing like that) that tells kannel in which format are the in/out ids. Regards Alvaro On 2/1/13, David Szanto dsza...@genasys.com wrote: Hi everyone! We have a scenario with a single SMSC (using SMPP) for which we have created 4 binds. So basically we have 4 SMSC groups in kannel for a single SMSC (and single account). We'll call Binds A,B,C and D. So, message 328515 is sent using bind A, but DLR for this message is delivered from the SMSC using bind B, which results in the following log error: smsc-sim4.log:2013-01-29 12:55:57 [16831] [35] ERROR: SMPP[B]: got DLR but could not find message or was not interested in it id328515 dst20034628200743, type1 Except for the smsc-id parameter, all other SMSC configuration parameters in kannel are identical: group = smsc smsc = smpp smsc-id = A host = smschost port = 2771 receive-port = 2771 smsc-username = smppclient1 smsc-password = password system-type = VMA log-file = /var/log/kannel/smsc-sim1.log log-level = 0 group = smsc smsc = smpp smsc-id = B host = smschost port=2771 receive-port = 2771 smsc-username = smppclient1 smsc-password = password system-type = VMA log-file = /var/log/kannel/smsc-sim1.log log-level = 2 group = smsc smsc = smpp smsc-id = C host = smschost port=2771 receive-port = 2771 smsc-username = smppclient1 smsc-password = password system-type = VMA log-file = /var/log/kannel/smsc-sim1.log log-level = 2 group = smsc smsc = smpp smsc-id = D host = smschost port=2771 receive-port = 2771 smsc-username = smppclient1 smsc-password = password system-type = VMA log-file = /var/log/kannel/smsc-sim1.log log-level = 2 We believe that because the DLR messages are incomming using a different smsc connection, the internal record for that message (328515) doesn't match up, thus leaving kannel not knowing what message the DLR recieved is for. So here is our question: If this is the problem: How can we avoid this? How can we assure kannel is able to match up DLR messages with their corresponding MT records? Any help will be greatly appreciated!! Thanks! David Szanto
Does bearerbox pass messages one on one to the SMSC?
Hi everyone! We've been trying to determine (with my colleagues at work) if when connected to an SMSC using SMPP the bearerbox passes MT messages through the bind in a batch, or one on one. The specific case involves load balancing with 2 or more binds to multiple SMSCs. So, do messages get passed to the SMSCs in groups of 10, 20 or whatever? or does it pass messages one on one? Any comment will be greatly appreciated! Thanks!!! David Szanto
how to set up kannel on boot start
Hi, I have some problems to set up KANNEL on system boot; could someone help us. Thanks Dzifa David NUGLOZE IT,ENGINEER Microsoft Certified Professional Tel: (+241) 07541952 Mail:d.nugl...@ymail.com BP: 11209 Libreville Gabon -Message d'origine- De : users-boun...@kannel.org [mailto:users-boun...@kannel.org] De la part de Maxime Loizeau Envoyé : lundi 6 août 2012 19:06 À : users@kannel.org Objet : Re: Using domain names to allow/deny connections Nobody has a clue ? Le 02/08/2012 09:37, Maxime Loizeau a écrit : Hello, I was wondering if I could use domain names to allow hosts to connect to the box. I tried and it didn't worked but i may have misconfigured my system (juste added the right DNS IP into resolv.conf). Thank you Maxime
RE: how to set up kannel on boot start
The truth is, I dont know how to do it, I dont have any idea for that ; kannel userguide dont say more about it. I use ubuntu 10.4. Thanks Dzifa David NUGLOZE IT,ENGINEER Microsoft Certified Professional Tel: (+241) 07541952 Mail:d.nugl...@ymail.com BP: 11209 Libreville Gabon De : spameden [mailto:spame...@gmail.com] Envoyé : mardi 7 août 2012 11:49 À : Dzifa David NUGLOZE Cc : users@kannel.org Objet : Re: how to set up kannel on boot start What kind of problems you've got? Try googling for init.d script for kannel. 2012/8/7 Dzifa David NUGLOZE d.nugl...@ymail.com Hi, I have some problems to set up KANNEL on system boot; could someone help us. Thanks Dzifa David NUGLOZE IT,ENGINEER Microsoft Certified Professional Tel: (+241) 07541952 Mail:d.nugl...@ymail.com mailto:mail%3ad.nugl...@ymail.com BP: 11209 Libreville Gabon -Message d'origine- De : users-boun...@kannel.org [mailto:users-boun...@kannel.org] De la part de Maxime Loizeau Envoyé : lundi 6 août 2012 19:06 À : users@kannel.org Objet : Re: Using domain names to allow/deny connections Nobody has a clue ? Le 02/08/2012 09:37, Maxime Loizeau a écrit : Hello, I was wondering if I could use domain names to allow hosts to connect to the box. I tried and it didn't worked but i may have misconfigured my system (juste added the right DNS IP into resolv.conf). Thank you Maxime
Re: Kannel not calling the dlr-url
Are you giving each message a unique ID? Check bearerlog for something like got DLR but could not find message or was not interested in it id On 7 June 2012 10:07, SAMSUDDOZA SK skdoza...@live.com wrote: Ok, thanks for your responds . Please tell me how could I solve this issue. I am facing this problem from the beginning, Still I am not solve this problem. So Please give me the instructions to solve it. From: rene.klu...@chimit.nl To: skdoza...@live.com; users@kannel.org; spame...@gmail.com Subject: RE: Kannel not calling the dlr-url Date: Thu, 7 Jun 2012 10:47:39 +0200 Dlr-url’s are properties of smsbox. Sqlbox doesn’t call dlr-url’s. == Rene From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of SAMSUDDOZA SK Sent: Thursday, 07 June, 2012 10:21 To: users@kannel.org; spame...@gmail.com Subject: Kannel not calling the dlr-url Hi All, I'm using Kannel with sqlbox. Kannel does not call dlr-url. I am submitting every sms with dlr-mask to 31 and dlr_url` send_sms table. I got the delivery report in kannel sent_sms table. But kannel is not call the dlr_url for updating report. My url working properly. Please help me, how can i solve this problem. Is there require any extra parameters or activity. I have a question What are the reasons behind kannel not calling the url ? anybody please explain. Thanks in advance Regards sk.Doza
Prevent bearerbox from sending the same message multiple times to the same receipient
Hi Users, I have been experiencing an unpleasant issue with kannel. I have smppbox and bearerbox installed on a centOS Server. The esme clients connect to the smppbox and bearerbox connects to the smscs. Now the issue i am experiencing with kannel is that it appears in bearerbox access log that it sent the same message multiple times (twice or thrice) to the same subscriber. Is their something i can do to prevent this issue mentioned above. Thanks. -- Best Regards. Ige David O.
Can Opensmppbox request for DLR and log
Hi Users, (1) Can OpenSMPPBox request for DLR from bearerbox? (2) Is there any facility or feature in OpenSMPPBox for reporting purpose, like logging in a Database inbound traffic and keeping track of their DLR's? -- Best Regards. Ige David O. Support and Maintenance Address: 50B Ladipo Bateye Street, G.R.A Ikeja. Lagos Email: da...@cellulant.com.ng Official Line: 08059800116
Re: SMPP ACK/NACK Method
Thanks Nikos!!! I'll check it out! David Szanto EL día Martes, 1 de Marzo de 2011 a las 11:35:07, Nikos Balkanas escribió: Hi, You can see them in debug SMSc (bb?) logs. For MT traffic this is in the submit_sm_resp PDU (from SMSc) and deliver_sm_resp (from BB, for a dlr). For MO's it is in deliver_sm_resp (from bb upon MO reception) and submit_sm_resp (from SMSc, upon receiving reply). These are implemented in handle_pdu() in gw/smsc/smsc_smpp.c (? - I think). BR, Nikos - Original Message - From: David Szanto dsza...@genasys.com To: users@kannel.org Sent: Monday, February 28, 2011 2:01 PM Subject: SMPP ACK/NACK Method Hi everyone, I've been following up the list for a couple of years, and it has been MOST helpful. So first I'd like to thank everyone for their participation. Now, to the point. There's a client with whom we'll be setting up a high traffic SMS GW with kannel, and communicating to their SMSC using SMPP. We estimate this platform we'll have peaks of around 500 messages/sec. The client is wondering what method does Kannel use for ACK/NACK over SMPP. The truth is I don't even know where to start looking for this answer. Could anyone please help me out? Thanks!! David Szanto
Re: Concatenated MT delaying
Hi thanks Nikos! yes, it could be a way... (although the protocol is not SMPP... a propietary vodafone protocol 'redbox' that I added modifiying the .c sources). But, could it be possible to make Kannel 'save' in somewhere an internal field received by the smsbox (conextID, the 'sessionId', shared by the the MO and the two MT) and then let the driver 'know' if a MT with a the same sessionID has been sent previously and make a delay (enqueuing it for example...)? Regards David Tubía El 28/02/11 05:34, Nikos Balkanas escribió: Hi, Please read UG about dlrs. You could specify a suitable dlr-url that could send in the 2nd MT if the 1st one is succesfull. Make sure that you set your dlr-mask to at least 8. That corresponds to accepted by SMSc or in SMPP terms SMSc ACK. BR, Nikos - Original Message - From: David Tubia dtu...@wpr.es To: users@kannel.org Sent: Sunday, February 27, 2011 2:35 PM Subject: Concatenated MT delaying Hi all! I have a problem with a SMSC (with a custom protocol, 'redbox'). The issue is about they need 2 MT for each MO in order to bill them. One MT is the premium content and the second is the legal text message. The problem is about they don't recognize them if I send the 2 MT consecutively. the 2 MT have a session ID (the same) and I would need to wait an 'ACK' from the first MT and then send the second MT. But I cannot do it with kannel (could it be possible???) The application that is sending the MT answers for the MO received send the two MT at the same time. A workaround consists on sending the first MT, wait for a while (1 second) and then send the second MT. I tried it modifiying the .c sources but I couldn't see the way to delay one MT from specifically another, and delaying all MTs is a BIG problem when sending huge number of MT (several hundreds) I asked for devs to make a short delay between both MTs but they refused (several apps to touch, they said) and asked me to make the work with kannel. I would like to know if there is any way to implement this with kannel, and I don't know where to see at this moment... can anyone help me? Thanks in advance David Tubνa
SMPP ACK/NACK Method
Hi everyone, I've been following up the list for a couple of years, and it has been MOST helpful. So first I'd like to thank everyone for their participation. Now, to the point. There's a client with whom we'll be setting up a high traffic SMS GW with kannel, and communicating to their SMSC using SMPP. We estimate this platform we'll have peaks of around 500 messages/sec. The client is wondering what method does Kannel use for ACK/NACK over SMPP. The truth is I don't even know where to start looking for this answer. Could anyone please help me out? Thanks!! David Szanto
Concatenated MT delaying
Hi all! I have a problem with a SMSC (with a custom protocol, 'redbox'). The issue is about they need 2 MT for each MO in order to bill them. One MT is the premium content and the second is the legal text message. The problem is about they don't recognize them if I send the 2 MT consecutively. the 2 MT have a session ID (the same) and I would need to wait an 'ACK' from the first MT and then send the second MT. But I cannot do it with kannel (could it be possible???) The application that is sending the MT answers for the MO received send the two MT at the same time. A workaround consists on sending the first MT, wait for a while (1 second) and then send the second MT. I tried it modifiying the .c sources but I couldn't see the way to delay one MT from specifically another, and delaying all MTs is a BIG problem when sending huge number of MT (several hundreds) I asked for devs to make a short delay between both MTs but they refused (several apps to touch, they said) and asked me to make the work with kannel. I would like to know if there is any way to implement this with kannel, and I don't know where to see at this moment... can anyone help me? Thanks in advance David Tubía
SMPP State values
Hi Fellow users, Please does anybody know the meaning of the state values in Kannel: +-+ | ACKNOWLEDGED_BY_BEARERBOX | | RECEIVED_FROM_CLIENT| | REFUSED_PERMANENTLY_BY_SMSC | | SMSC_STAT_ACK_MASK_8| | SMSC_STAT_DELIVRD_ERR_000 | | SMSC_STAT_UNDELIV_ERR_000 | +-+ -- Best Regards. Ige David O. Support and Maintenance Address: 50B Ladipo Bateye Street, G.R.A Ikeja. Lagos Email: da...@cellulant.com.ng Official Line: 08059800116
Meaning of Status
Hi All, Please what does this mean in kannel: SMSC_STAT_ACK_MASK_8 and can u please provide me with the possible status values and meanings. -- Best Regards. Ige David O. Support and Maintenance Address: 50B Ladipo Bateye Street, G.R.A Ikeja. Lagos Email: da...@cellulant.com.ng Official Line: 08059800116
DLR not logging messages in DB
Hi all, I have installed smppbox and kannel on a server. Currently the DLR is not logging messages in the database. So i want messages to be logged in the database. How do i go about this. Is there a way to do realtime report of sent, unsent, failed messages in kannel. Thanks for ur response. Ige David O.
Delivery Report to log messages
Hi all, I have installed smppbox and kannel on a server but we need the delivery report to also log messages in the dlr table. How do we go about it. Or if there another alternative to view sent, undelivered messages at real time when using kannel for realtime reporting purposes.
ESME Client not connecting to OpenSmppbox
Hello everyone, I have installed opensmppbox on a centOS server and have configured it with a client, but the client is not able to connect. When the client tries to connect it gives SMSC rejected login to transmit, code 0x000d (Bind Failed). Couldn't connect to SMS center (retrying in 10 seconds). On the server side, it gives this error, Invalid SMPP PDU received. Server Bearerbox log 2011-01-15 13:07:37 [26155] [5] INFO: Client connected from 127.0.0.1 2011-01-15 13:07:37 [26155] [5] DEBUG: Started thread 45 (gw/bb_boxc.c:function) 2011-01-15 13:07:37 [26155] [45] DEBUG: Thread 45 (gw/bb_boxc.c:function) maps to pid 26155. 2011-01-15 13:07:37 [26155] [45] DEBUG: Started thread 46 (gw/bb_boxc.c:boxc_sender) 2011-01-15 13:07:37 [26155] [46] DEBUG: Thread 46 (gw/bb_boxc.c:boxc_sender) maps to pid 26155. 2011-01-15 13:07:40 [26155] [45] INFO: Connection closed by the box 127.0.0.1 2011-01-15 13:07:40 [26155] [46] DEBUG: send_msg: sending msg to box: 127.0.0.1 2011-01-15 13:07:40 [26155] [46] DEBUG: Thread 46 (gw/bb_boxc.c:boxc_sender) terminates. 2011-01-15 13:07:40 [26155] [45] DEBUG: Thread 45 (gw/bb_boxc.c:function) terminates. 2011-01-15 13:07:48 [26155] [5] INFO: Client connected from 127.0.0.1 2011-01-15 13:07:48 [26155] [5] DEBUG: Started thread 47 (gw/bb_boxc.c:function) 2011-01-15 13:07:48 [26155] [47] DEBUG: Thread 47 (gw/bb_boxc.c:function) maps to pid 26155. 2011-01-15 13:07:48 [26155] [47] DEBUG: Started thread 48 (gw/bb_boxc.c:boxc_sender) 2011-01-15 13:07:48 [26155] [48] DEBUG: Thread 48 (gw/bb_boxc.c:boxc_sender) maps to pid 26155. 2011-01-15 13:07:51 [26155] [47] INFO: Connection closed by the box 127.0.0.1 2011-01-15 13:07:51 [26155] [48] DEBUG: send_msg: sending msg to box: 127.0.0.1 2011-01-15 13:07:51 [26155] [48] DEBUG: Thread 48 (gw/bb_boxc.c:boxc_sender) terminates. 2011-01-15 13:07:51 [26155] [47] DEBUG: Thread 47 (gw/bb_boxc.c:function) terminates. 2011-01-15 13:07:59 [26155] [5] INFO: Client connected from 127.0.0.1 2011-01-15 13:07:59 [26155] [5] DEBUG: Started thread 49 (gw/bb_boxc.c:function) 2011-01-15 13:07:59 [26155] [49] DEBUG: Thread 49 (gw/bb_boxc.c:function) maps to pid 26155. 2011-01-15 13:07:59 [26155] [49] DEBUG: Started thread 50 (gw/bb_boxc.c:boxc_sender) 2011-01-15 13:07:59 [26155] [50] DEBUG: Thread 50 (gw/bb_boxc.c:boxc_sender) maps to pid 26155. 2011-01-15 13:08:02 [26155] [49] INFO: Connection closed by the box 127.0.0.1 2011-01-15 13:08:02 [26155] [50] DEBUG: send_msg: sending msg to box: 127.0.0.1 2011-01-15 13:08:02 [26155] [50] DEBUG: Thread 50 (gw/bb_boxc.c:boxc_sender) terminates. 2011-01-15 13:08:02 [26155] [49] DEBUG: Thread 49 (gw/bb_boxc.c:function) terminates. Server Opensmppbox log 2011-01-15 13:06:40 [28249] [25] INFO: Client connected from 40.100.0.000 2011-01-15 13:06:40 [28249] [25] DEBUG: Connecting to 127.0.0.1 2011-01-15 13:06:40 [28249] [25] INFO: Connected to bearerbox at localhost port 13001. 2011-01-15 13:06:40 [28249] [25] DEBUG: Started thread 26 (opensmppbox.c:smpp_to_bearerbox) 2011-01-15 13:06:40 [28249] [26] DEBUG: Thread 26 (opensmppbox.c:smpp_to_bearerbox) maps to pid 28249. 2011-01-15 13:06:41 [28249] [26] DEBUG: SMPP[opensmppbox]: Got PDU: 2011-01-15 13:06:41 [28249] [26] DEBUG: SMPP PDU 0x4ea0170 dump: 2011-01-15 13:06:41 [28249] [26] DEBUG: type_name: bind_transceiver 2011-01-15 13:06:41 [28249] [26] DEBUG: command_id: 9 = 0x0009 2011-01-15 13:06:41 [28249] [26] DEBUG: command_status: 0 = 0x 2011-01-15 13:06:41 [28249] [26] DEBUG: sequence_number: 13 = 0x000d 2011-01-15 13:06:41 [28249] [26] DEBUG: system_id: 12345 2011-01-15 13:06:41 [28249] [26] DEBUG: password: 12345 2011-01-15 13:06:41 [28249] [26] DEBUG: system_type: vma 2011-01-15 13:06:41 [28249] [26] DEBUG: interface_version: 52 = 0x0034 2011-01-15 13:06:41 [28249] [26] DEBUG: addr_ton: 0 = 0x 2011-01-15 13:06:41 [28249] [26] DEBUG: addr_npi: 1 = 0x0001 2011-01-15 13:06:41 [28249] [26] DEBUG: address_range: NULL 2011-01-15 13:06:41 [28249] [26] DEBUG: SMPP PDU dump ends. 2011-01-15 13:06:41 [28249] [26] DEBUG: SMPP[opensmppbox]: Sending PDU: 2011-01-15 13:06:41 [28249] [26] DEBUG: SMPP PDU 0x4ea38a0 dump: 2011-01-15 13:06:41 [28249] [26] DEBUG: type_name: bind_transceiver_resp 2011-01-15 13:06:41 [28249] [26] DEBUG: command_id: 2147483657 = 0x8009 2011-01-15 13:06:41 [28249] [26] DEBUG: command_status: 13 = 0x000d 2011-01-15 13:06:41 [28249] [26] DEBUG: sequence_number: 13 = 0x000d 2011-01-15 13:06:41 [28249] [26] DEBUG: system_id: NULL 2011-01-15 13:06:41 [28249] [26] DEBUG: SMPP PDU dump ends. 2011-01-15 13:06:42 [28249] [26] ERROR: Invalid SMPP PDU received. 2011-01-15 13:06:42 [28249] [26] DEBUG: Thread 26 (opensmppbox.c:smpp_to_bearerbox) terminates. 2011-01-15 13:06:43 [28249] [25] DEBUG: Thread 25 (opensmppbox.c:function) terminates. Client bearerbox log 2011-01-14 14:19:13 [20507] [6] DEBUG: SMPP[ukserver]: Sending PDU: 2011-01-14 14:19:13 [20507] [6] DEBUG: SMPP PDU
SMS not routed
Hello users, I have setup smppbox on a centOS server and i have created an esme-user in the config which i use to connect to the server from another system. Each time i send a message from this system using the sendsms url, it displays Accepted for delivery' but when it gets to the server it does not route the sms. The Error in the log file is below; 2010-12-25 11:16:09 [4857] [16] DEBUG: Routing failed, re-queued. 2010-12-25 11:16:09 [4857] [16] DEBUG: sms_router: time to sleep 30.00 secs. 2010-12-25 11:16:09 [4857] [16] DEBUG: sms_router: gwlist_len = 1 2010-12-25 11:16:09 [4857] [16] DEBUG: sms_router: handling message (0x95394f0 vs 0x95394f0) 2010-12-25 11:16:09 [4857] [16] DEBUG: Routing failed, re-queued. 2010-12-25 11:16:09 [4857] [16] DEBUG: sms_router: handling message (0x95394f0 vs 0x95394f0) 2010-12-25 11:16:09 [4857] [16] DEBUG: Routing failed, re-queued. 2010-12-25 11:16:09 [4857] [16] DEBUG: sms_router: time to sleep 30.00 secs. 2010-12-25 11:16:10 [4857] [7] DEBUG: Running status update 2010-12-25 11:16:10 [4857] [7] DEBUG: No rows returned for status query 2010-12-25 11:16:17 [4857] [15] DEBUG: HTTP[tyn]: Re-sending request 2010-12-25 11:16:17 [4857] [15] DEBUG: HTTP[tyn]: Start request 2010-12-25 11:16:17 [4857] [3] DEBUG: Queue contains 0 pending requests. 2010-12-25 11:16:17 [4857] [3] DEBUG: Parsing URL ` http://localhost:23013/cgi-bin/sendsms?username=password=xxto=%2B2348056290217text=testingfrom=cellulantcoding=0charset=UTF-8account=david:NULLsmsc=tyndlr-url=57394386-8536-4367-99d6-0b979ea55917 ': 2010-12-25 11:16:17 [4857] [3] DEBUG: Scheme: http:// 2010-12-25 11:16:17 [4857] [3] DEBUG: Host: localhost 2010-12-25 11:16:17 [4857] [3] DEBUG: Port: 23013 2010-12-25 11:16:17 [4857] [3] DEBUG: Username: (null) 2010-12-25 11:16:17 [4857] [3] DEBUG: Password: (null) 2010-12-25 11:16:17 [4857] [3] DEBUG: Path: /cgi-bin/sendsms 2010-12-25 11:16:17 [4857] [3] DEBUG: Query: username=xxxpassword=xxxto=%2B2348056290217text=testingfrom=cellulantcoding=0charset=UTF-8account=david:NULLsmsc=tyndlr-url=57394386-8536-4367-99d6-0b979ea55917 2010-12-25 11:16:17 [4857] [3] DEBUG: Fragment: (null) 2010-12-25 11:16:17 [4857] [3] DEBUG: Connecting nonblocking to 127.0.0.1 2010-12-25 11:16:17 [4857] [3] DEBUG: HTTP: Opening connection to `localhost:23013' (fd=59). 2010-12-25 11:16:17 [4857] [3] DEBUG: Socket connecting 2010-12-25 11:16:17 [4857] [2] DEBUG: Get info about connecting socket 2010-12-25 11:16:17 [4857] [2] DEBUG: Socket not connected 2010-12-25 11:16:17 [4857] [2] ERROR: Couldn't fetch http://localhost:23013/cgi-bin/sendsms?username=xxpassword=xto=%2B2348056290217text=testingfrom=cellulantcoding=0charset=UTF-8account=david:NULLsmsc=tyndlr-url=57394386-8536-4367-99d6-0b979ea55917 2010-12-25 11:16:17 [4857] [15] ERROR: HTTP[tyn]: Couldn't connect to SMS center (retrying in 10 seconds). 2010-12-25 11:16:20 [4857] [7] DEBUG: Running status update 2010-12-25 11:16:20 [4857] [7] DEBUG: No rows returned for status query can someone please tell me what the problem is. Thanks.
Elite not connected to kannel
Hello users, i have installed Elite SMS Gateway on a centOS Server. When i try to get the status of kannel and smpp box it displays: Kannel Control Error communicating with Kannel! and SMPPBox Control Error communicating with SMPPBox! Can anybody tell me why i am getting this error. I have started kannel and Smppbox sucessfully but i just cannot see there status from Elite.
SMS not routed
Hello users, I have setup smppbox on a centOS server and i have created an esme-user in the config which i use to connect to the server from another system. Each time i send a message from this system using the sendsms url, it displays Accepted for delivery' but when it gets to the server it does not route the sms. The Error in the log file is below; 2010-12-25 11:16:09 [4857] [16] DEBUG: Routing failed, re-queued. 2010-12-25 11:16:09 [4857] [16] DEBUG: sms_router: time to sleep 30.00 secs. 2010-12-25 11:16:09 [4857] [16] DEBUG: sms_router: gwlist_len = 1 2010-12-25 11:16:09 [4857] [16] DEBUG: sms_router: handling message (0x95394f0 vs 0x95394f0) 2010-12-25 11:16:09 [4857] [16] DEBUG: Routing failed, re-queued. 2010-12-25 11:16:09 [4857] [16] DEBUG: sms_router: handling message (0x95394f0 vs 0x95394f0) 2010-12-25 11:16:09 [4857] [16] DEBUG: Routing failed, re-queued. 2010-12-25 11:16:09 [4857] [16] DEBUG: sms_router: time to sleep 30.00 secs. 2010-12-25 11:16:10 [4857] [7] DEBUG: Running status update 2010-12-25 11:16:10 [4857] [7] DEBUG: No rows returned for status query 2010-12-25 11:16:17 [4857] [15] DEBUG: HTTP[tyn]: Re-sending request 2010-12-25 11:16:17 [4857] [15] DEBUG: HTTP[tyn]: Start request 2010-12-25 11:16:17 [4857] [3] DEBUG: Queue contains 0 pending requests. 2010-12-25 11:16:17 [4857] [3] DEBUG: Parsing URL ` http://localhost:23013/cgi-bin/sendsms?username=password=xxto=%2B2348056290217text=testingfrom=cellulantcoding=0charset=UTF-8account=david:NULLsmsc=tyndlr-url=57394386-8536-4367-99d6-0b979ea55917 ': 2010-12-25 11:16:17 [4857] [3] DEBUG: Scheme: http:// 2010-12-25 11:16:17 [4857] [3] DEBUG: Host: localhost 2010-12-25 11:16:17 [4857] [3] DEBUG: Port: 23013 2010-12-25 11:16:17 [4857] [3] DEBUG: Username: (null) 2010-12-25 11:16:17 [4857] [3] DEBUG: Password: (null) 2010-12-25 11:16:17 [4857] [3] DEBUG: Path: /cgi-bin/sendsms 2010-12-25 11:16:17 [4857] [3] DEBUG: Query: username=xxxpassword=xxxto=%2B2348056290217text=testingfrom=cellulantcoding=0charset=UTF-8account=david:NULLsmsc=tyndlr-url=57394386-8536-4367-99d6-0b979ea55917 2010-12-25 11:16:17 [4857] [3] DEBUG: Fragment: (null) 2010-12-25 11:16:17 [4857] [3] DEBUG: Connecting nonblocking to 127.0.0.1 2010-12-25 11:16:17 [4857] [3] DEBUG: HTTP: Opening connection to `localhost:23013' (fd=59). 2010-12-25 11:16:17 [4857] [3] DEBUG: Socket connecting 2010-12-25 11:16:17 [4857] [2] DEBUG: Get info about connecting socket 2010-12-25 11:16:17 [4857] [2] DEBUG: Socket not connected 2010-12-25 11:16:17 [4857] [2] ERROR: Couldn't fetch http://localhost:23013/cgi-bin/sendsms?username=xxpassword=xto=%2B2348056290217text=testingfrom=cellulantcoding=0charset=UTF-8account=david:NULLsmsc=tyndlr-url=57394386-8536-4367-99d6-0b979ea55917 2010-12-25 11:16:17 [4857] [15] ERROR: HTTP[tyn]: Couldn't connect to SMS center (retrying in 10 seconds). 2010-12-25 11:16:20 [4857] [7] DEBUG: Running status update 2010-12-25 11:16:20 [4857] [7] DEBUG: No rows returned for status query Here is my kannel configuration: --- bearerbox.conf --- include=/opt/vsmsc/etc/kannel_include.conf group=vsmsc-config path=/opt/vsmsc/etc/vsmsc_bbox.conf group=rr-list id=rr-db table=users key-field=username value-field=throughput group=mysql-connection id=rr-db host=localhost username=xx password=xx database=xx max-connections=1 kannel_include.conf group = core admin-port = 13000 smsbox-port = 13001 admin-password = foobar box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 box-allow-ip = *.*.*.* log-file=/opt/vsmsc/logs/bearerbox.log log-level=0 admin-deny-ip = *.*.*.* admin-allow-ip = 127.0.0.1 #admin-allow-ip = *.*.*.* group = mysql-connection id = kannel_dlr host = localhost username = xx password = xx database = xx max-connections = 5 group = dlr-db id = kannel_dlr table = kannel_dlr field-smsc = smsc field-timestamp = ts field-destination = destination field-source = source field-service = service field-url = url field-mask = mask field-status = status field-boxc-id = boxc #- # SMSC CONNECTIONS #- include=/opt/vsmsc/etc/smsc.d/ #include=/opt/vsmsc/etc/smsc.d/mo_relay.conf #- # SMSBOX SETUP #- group = smsbox smsbox-id=VSMSC_HTTP bearerbox-host = 127.0.0.1 sendsms-port = 13013 log-file=/opt/vsmsc/logs/smsbox.log log-level=0 access-log = /tmp/access.log #- # SEND-SMS USERS #- #- # SERVICES #- group =
Kannel Config Help
Hello, I have installed an Elite SMS Gateway software which also installed Kannel along with it on a centOS server. Each time i try to send SMS using the sendsms url it gives Authorization failed for sendsms. Below is my config, bearerbox.conf --- include=/opt/vsmsc/etc/kannel_include.conf group=vsmsc-config path=/opt/vsmsc/etc/vsmsc_bbox.conf group=rr-list id=rr-db table=users key-field=username value-field=throughput group=mysql-connection id=rr-db host=localhost username=xx password=x database=x max-connections=1 -- kannel_include.conf --- group = core admin-port = 13000 smsbox-port = 13001 admin-password = foobar #box-deny-ip = *.*.*.* #box-allow-ip = 127.0.0.1 box-allow-ip = *.*.*.* log-file=/opt/vsmsc/logs/bearerbox.log log-level=0 admin-deny-ip = *.*.*.* admin-allow-ip = 127.0.0.1 group = mysql-connection id = kannel_dlr host = localhost username = xx password = xx database = xx max-connections = 5 group = dlr-db id = kannel_dlr table = kannel_dlr field-smsc = smsc field-timestamp = ts field-destination = destination field-source = source field-service = service field-url = url field-mask = mask field-status = status field-boxc-id = boxc #- # SMSC CONNECTIONS #- include=/opt/vsmsc/etc/smsc.d/ #include=/etc/kannel/smsc.d/mo_relay.conf #- # SMSBOX SETUP #- group = smsbox smsbox-id=VSMSC_HTTP bearerbox-host = 127.0.0.1 sendsms-port = 13013 log-file=/opt/vsmsc/logs/smsbox.log log-level=0 access-log = /tmp/access.log #- # SEND-SMS USERS #- #- # SERVICES #- group = sms-service keyword = default catch-all=yes exec=/opt/vsmsc/sbin/mo_processor.php /opt/vsmsc/logs/mo_debug.log %p %P %C %b %F omit-empty=yes send-sender=yes --- smsbox.conf --- include=/opt/vsmsc/etc/kannel_include.conf group=vsmsc-config path=/opt/vsmsc/etc/vsmsc_sbox.conf # SEND-SMS USERS group = sendsms-user username = tester password = foobar #user-deny-ip = #user-allow-ip = - vsmsc_bbox.conf --- group=vsmsc id=vsmsc-primary smsc-db=vsmsc smsc-table=smscs user-db=vsmsc user-table=users http-port=16000 mode=1 bearerbox-status-url=http://localhost:13000/status.xml?password=foobar; num-tables=10 server-id=1 transactions-db=vsmsc transactions-table=user_transactions messages-db=vsmsc messages-table=user_messages status-db=vsmsc status-table=status_queue numbers-db=vsmsc numbers-table=numbers keywords-db=vsmsc keywords-table=number_keywords smpp-smsbox-id=VSMSC_SMPP http-smsbox-id=VSMSC_HTTP mo-db=vsmsc mo-table=mo_messages profile-db=vsmsc profile-table=routing_profiles batch-db=vsmsc batch-table=user_batches batch-tracking-db=vsmsc batch-tracking-table=user_batch_tracking_codes opt-out-words=stop block-db=vsmsc block-table=blocked_numbers vsmsc_sbox.conf --- group=mysql-connection id=vsmsc-primary host=localhost username=xx password=xx database=xx max-connections=5 group=vsmsc id=vsmsc-primary smsc-db=vsmsc smsc-table=smscs user-db=vsmsc user-table=users http-port=17000 mode=2 bearerbox-status-url=http://localhost:13000/status.xml?password=foobar; num-tables=10 server-id=1 transactions-db=vsmsc transactions-table=user_transactions messages-db=vsmsc messages-table=user_messages status-db=vsmsc status-table=status_queue numbers-db=vsmsc numbers-table=numbers keywords-db=vsmsc keywords-table=number_keywords smpp-smsbox-id=VSMSC_SMPP http-smsbox-id=VSMSC_HTTP smsbox-override-auth=xx mo-db=vsmsc mo-table=mo_messages profile-db=vsmsc profile-table=routing_profiles
Using kannel
Hi All, I have tried setting up kannel on ubuntu 10.04.1 for testing, although I was able to successfully installed and set it up, however, there is no much use cases documentation out there, could anyone point me to any use cases documentation available on this tool? David On Mon, Aug 30, 2010 at 12:08 PM, users-requ...@kannel.org wrote: Send users mailing list submissions to users@kannel.org To subscribe or unsubscribe via the World Wide Web, visit http://www.kannel.org/mailman/listinfo/users or, via email, send a message with subject or body 'help' to users-requ...@kannel.org You can reach the person managing the list at users-ow...@kannel.org When replying, please edit your Subject line so it is more specific than Re: Contents of users digest... Today's Topics: 1. Re: Nokia N73 (Zak) 2. Re: Nokia N73 (Emmanuel CHANSON) -- Message: 1 Date: Mon, 30 Aug 2010 06:47:41 -0400 From: Zak xi...@netscape.net To: emmanuelchan...@gmail.com Cc: users@kannel.org Subject: Re: Nokia N73 Message-ID: 8cd1647e7c183d4-4bc4-2f...@webmail-m116.sysops.aol.com Content-Type: text/plain; charset=us-ascii Hi Emmanuel, Mine gives Error when I do AT+CNMI. Is your Nokia 6230 working fine for both sending/receiving SMS? -Original Message- From: Emmanuel CHANSON emmanuelchan...@gmail.com To: Zak xi...@netscape.net Cc: gjergji.g...@facilization.com; users@kannel.org Sent: Mon, Aug 30, 2010 11:19 am Subject: Re: Nokia N73 Hello Zak, What's report 'AT+CNMI' command when using your mobile with minicom ? My Nokia gives the following output (Nokia 6230) AT+CNMI=? +CNMI: (0-2),(0-3),(0,2,3),(0-2),(0,1) OK If your gives ERROR then I think you won't be able to use it with Kannel BR, Emmanuel 2010/8/30 Zak xi...@netscape.net Hi All, Anyone at all who used a Nokia N93 or N95 or N97 that can share their config with me? If the phones work on minicom and vwdial, am I correct to assume they should work with kannel as well? but need the correct init string? thanks, Zak -Original Message- From: Gjergji Guri gjergji.g...@facilization.com To: Zak xi...@netscape.net Cc: nbalka...@gmail.com; users@kannel.org Sent: Sun, Aug 29, 2010 10:24 am Subject: Re: Nokia N73 Hi Zak, Have you checked the init string? you can use wvdialconf from the command prompt to find out the inits string of your modem. Are you able to send SMS using the AT commands. You can use minicom program. Cheers, Gjergji On Sun, Aug 29, 2010 at 10:32 AM, Zak xi...@netscape.net wrote: Here's more log from kannel: 2010-08-28 21:28:41 [4145] [0] INFO: Debug_lvl = 1, log_file = none, log_lvl = 0 2010-08-28 21:28:41 [4145] [0] WARNING: DLR: using default 'internal' for storage type. 2010-08-28 21:28:41 [4145] [0] INFO: DLR using storage type: internal 2010-08-28 21:28:41 [4145] [0] INFO: Added logfile `/usr/local/kannel/logs/kannel.log' with level `0'. 2010-08-28 21:28:41 [4145] [0] INFO: Started access logfile `/usr/local/kannel/logs/core_access.log'. 2010-08-28 21:28:41 [4145] [0] INFO: HTTP: Opening server at port 13000. 2010-08-28 21:28:41 [4145] [0] INFO: BOXC: 'smsbox-max-pending' not set, using default (100). 2010-08-28 21:28:41 [4145] [0] INFO: Set SMS resend frequency to 60 seconds. 2010-08-28 21:28:41 [4145] [0] INFO: SMS resend retry set to unlimited. 2010-08-28 21:28:41 [4145] [0] INFO: DLR rerouting for smsc id modem disabled. 2010-08-28 21:28:41 [4145] [0] INFO: Added logfile `/usr/local/kannel/logs/modem.log' with level `1'. 2010-08-28 21:28:41 [4145] [0] INFO: AT2[modem]: configuration shows modemtype Nokia 2010-08-28 21:28:41 [4145] [0] INFO: AT2[modem]: read modem definition for Nokia 2010-08-28 21:28:41 [4145] [0] INFO: 2010-08-28 21:28:41 [4145] [0] INFO: Kannel bearerbox II version 1.4.3 starting 2010-08-28 21:28:41 [4145] [0] INFO: MAIN: Start-up done, entering mainloop 2010-08-28 21:28:41 [4145] [6] INFO: Logging thread `6' to logfile `/usr/local/kannel/logs/modem.log' with level `1'. 2010-08-28 21:28:51 [4145] [0] WARNING: Killing signal or HTTP admin command received, shutting down... 2010-08-28 21:28:54 [4145] [0] INFO: All flow threads have died, killing core 2010-08-28 21:28:54 [4145] [0] INFO: Total WDP messages: received 0, sent 0 2010-08-28 21:28:54 [4145] [0] INFO: Total SMS messages: received 0, sent 0 -Original Message- From: Nikos Balkanas nbalka...@gmail.com To: users@kannel.org; Zak xi...@netscape.net Sent: Sun, Aug 29, 2010 1:24 am Subject: Re: Nokia N73 Please repost same logs at maximum detail. BR, Nikos - Original Message - From: Zak To: users@kannel.org Sent: Saturday, August 28, 2010 11:43 PM Subject: Nokia N73 Hi All, I have a Nokia N73 that I could use to send SMS with minicom
Re: Help on Kannel configuration
Nikos/All, I thought i did reply to all in my last email. I still would want someone to answer my questions. David On Thu, Aug 26, 2010 at 10:23 AM, david ally dade.a...@gmail.com wrote: Yes, I have read the user guide and i also have the kannel.conf file that come with the 1.4.3 stable examples, my understanding is that I can just uncomment some applicable to my requirements entries in this file and then overwrite the /etc/kannel/kannel.conf file in my installation. But in the example file, I couldn't locate the section that deals with http interface and how to access to it on my system further configuration and administration purposes. Also can I continue further configuration and administration of kannel gateway from the http interface when i get it done? Thank you for your help. David 2010/8/25 Nikos Balkanas nbalka...@gmail.com Sure, start with kannel.conf under doc/examples. To understand it check UG. BR, Nikos - Original Message - From: ayokunle odusanya To: Nikos Balkanas Cc: david ally ; users@kannel.org Sent: Wednesday, August 25, 2010 5:14 PM Subject: Re: Help on Kannel configuration Hi, I understand how daunting the configurations parameters can be for a new user, but I'm sure you can have a sample configuration file to work with right away (in the most needed parameters) in the source files of kannel. 2010/8/25 Nikos Balkanas nbalka...@gmail.com Hi, You should start from User's guide at www.kannel.org. It has plenty of configuration examples. BR, Nikos - Original Message - From: david ally To: users@kannel.org Sent: Wednesday, August 25, 2010 3:11 PM Subject: Help on Kannel configuration Hi All, I'm new user of kannel, and this is my use case; I want to use kannel server to receive sms (bulk data students' weekly performance data ) from schools in a particular locality to the Local Government education resource centre, and also from the LG resource centre to the state education resource centre. The data from each school to LG resource center is the only one that need be via sms other data transport from LG to State etc can be via wap or HTTP,because supporting infrastructure could be available at this locations. Thank you! David -- Ayokunle Odusanya
Help on Kannel configuration
Hi All, I'm new user of kannel, and this is my use case; I want to use kannel server to receive sms (bulk data students' weekly performance data ) from schools in a particular locality to the Local Government education resource centre, and also from the LG resource centre to the state education resource centre. The data from each school to LG resource center is the only one that need be via sms other data transport from LG to State etc can be via wap or HTTP,because supporting infrastructure could be available at this locations. Thank you! David
Re: Inbound MO routing with SQL Box
That fixed it! Thank you. i just added: group = smsbox-route smsbox-id = smsbox1 smsc-id = smsc1;smsc2... and that fixed it. Thanks Cezary! From: Cezary Siwek cza...@thebestisp.co.uk To: users@kannel.org Sent: Mon, March 8, 2010 9:20:42 AM Subject: RE: Inbound MO routing with SQL Box Oh, sorry. You’ve got the smsbox configured already. Focus on the smsbox-route then… c. From:users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of David Sent: 08 March 2010 14:59 To: users@kannel.org Subject: Inbound MO routing with SQL Box Hello, I am having a hard time getting SQL box working. I need inbound MOs to be handled by the standard exec command I have specified in the kannel.conf file, not via SQLBox. I want to use SQLbox for outbound messages (ie, insert messages into the SQLBox table to send them). It seems that all MOs are currently being handled by the SQLbox, and the exec command i specify in kannel.conf is not running. Here is my kannel.conf: #Kannel.conf group = core admin-port = 13000 smsbox-port = 13001 admin-password = bar admin-allow-ip = *.*.*.* log-file = /var/log/kannel/kannel.log log-level = 0 box-allow-ip = *.*.*.* dlr-storage = mysql group = smsbox smsbox-id = smsbox1 bearerbox-host = localhost sendsms-port = 13013 bearerbox-port = 13003 sendsms-chars = 0123456789 +- log-file = /var/log/kannel/smsbox.log log-level = 0 # SERVICE: Just one: its all handled by exec.php group = sms-service keyword = default exec = /var/www/html/exec.php msg=%a phone=%p shortcode=%P operatorid=%o metadata=%D /dev/null 21 max-messages = 0 accept-x-kannel-headers = true Here's the sqlbox.conf: #SQLBOX.conf group = sqlbox id = sqlbox-db smsbox-id = sqlbox #global-sender = bearerbox-host = localhost bearerbox-port = 13001 smsbox-port = 13003 smsbox-port-ssl = false sql-log-table = sent_sms sql-insert-table = send_sms log-file = /var/log/kannel/kannel-sqlbox.log log-level = 100 Any help you could lend would be great. Thank you.
Inbound MO routing with SQL Box
Hello, I am having a hard time getting SQL box working. I need inbound MOs to be handled by the standard exec command I have specified in the kannel.conf file, not via SQLBox. I want to use SQLbox for outbound messages (ie, insert messages into the SQLBox table to send them). It seems that all MOs are currently being handled by the SQLbox, and the exec command i specify in kannel.conf is not running. Here is my kannel.conf: #Kannel.conf group = core admin-port = 13000 smsbox-port = 13001 admin-password = bar admin-allow-ip = *.*.*.* log-file = /var/log/kannel/kannel.log log-level = 0 box-allow-ip = *.*.*.* dlr-storage = mysql group = smsbox smsbox-id = smsbox1 bearerbox-host = localhost sendsms-port = 13013 bearerbox-port = 13003 sendsms-chars = 0123456789 +- log-file = /var/log/kannel/smsbox.log log-level = 0 # SERVICE: Just one: its all handled by exec.php group = sms-service keyword = default exec = /var/www/html/exec.php msg=%a phone=%p shortcode=%P operatorid=%o metadata=%D /dev/null 21 max-messages = 0 accept-x-kannel-headers = true Here's the sqlbox.conf: #SQLBOX.conf group = sqlbox id = sqlbox-db smsbox-id = sqlbox #global-sender = bearerbox-host = localhost bearerbox-port = 13001 smsbox-port = 13003 smsbox-port-ssl = false sql-log-table = sent_sms sql-insert-table = send_sms log-file = /var/log/kannel/kannel-sqlbox.log log-level = 100 Any help you could lend would be great. Thank you.
Kannel timeouts / connectivity issues
Anybody know what Kannel's expected behavior when HTTP connections timeout or fail? We have a situation with 120+ sms-service services defined, but have noticed a few of them behave in a peculiar manner where, very occasionally, HTTP requests don't occur until 16 minutes after being received by Kannel. This will happen out of the blue without any errors logged in smsbox.log or kannel.log. This occurs in a transient fashion - there doesn't appear to be any rhyme or reason to when this occurs. This only appears to happen with a particular subset of SMS services which happen to be hosted outside of our immediate hosting environment, suggesting there's some sort of network disruption causing this problem. Potentially this is some of retry based on a 1-minute timeout, followed by a retry 15 minutes later; however this would be out of character since in my experience with Kannel most timeouts / 404s / 500s usually generate everyone's favourite Couldn't fetch content, sorry-type messages. I also can't find any reference to timeouts of these values in the user's guide or the configuration files. Until recently the get-urls for these services had the SMSC included in the URLs (i.e. smsc=%i) but, as these were the only services using this, I've removed this in case there's some sort of problem caused by this. Has anybody else had a similar situation where these sorts of delays have happened? David
Re: Two Basic Questions, Please?
Thank you, Nikos, for the advice. Best regards, David --- On Sat, 28/11/09, Nikos Balkanas nbalka...@gmail.com wrote: From: Nikos Balkanas nbalka...@gmail.com Subject: Re: Two Basic Questions, Please? To: David Halliday tetrah...@yahoo.co.uk, Kannel Users users@kannel.org, Cezary Siwek cza...@thebestisp.co.uk Date: Saturday, 28 November, 2009, 6:54 Hi, And just what are bulk SMS firms are using? Maybe kannel? If you just want to send your own SMS, use a bulk SMS progvider's web interface. Kannel is for bulk SMS providers. A few large corporations are using it also for in-house SMS provision. BR, Nikos - Original Message - From: David Halliday To: Kannel Users ; Nikos Balkanas ; Cezary Siwek Sent: Saturday, November 28, 2009 7:32 AM Subject: Re: Two Basic Questions, Please? Thank you , Cezary and Nikos, for your responses. The option: Application - Kannel - GSM modem is now clear to me. One last point, please, and I will not bother the list with my elementary enquiry anymore. Consider the second option: Application - Kannel - SMSc link Say there is a firm that provides 2 separate services: Service a: Bulk SMS messages to network X Service b: SMSC connectivity with network X (SMPP link) In theory, applying the second option mentioned above, if we went for service b, would it not be cheaper than service a? If the answer is no, then what on earth is the use of the gateway? Most bulk sms firms provide you with a website script/interface to send sms messages from the website anyway, and that is usually included in the price. Best regards, David --- On Sat, 28/11/09, Nikos Balkanas nbalka...@gmail.com wrote: From: Nikos Balkanas nbalka...@gmail.com Subject: Re: Two Basic Questions, Please? To: Cezary Siwek cza...@thebestisp.co.uk, David Halliday tetrah...@yahoo.co.uk, Kannel Users users@kannel.org Date: Saturday, 28 November, 2009, 2:47 ο»Ώ Hi, To make it clearer. A GSM modem is a mobile phone as far as the operator is concerned. Both are using a SIM card and are charged by it. Kannel doesn't care. The differences between a GSM modem and a mobile phone (with modem functionality) are: 1) You can use your mobile for other things as well (calling friends, etc.) 2) A dedicated GSM modem is more reliable, in terms of DLRs, status and SMS handling. BR, Nikos - Original Message - From: Cezary Siwek To: David Halliday ; Kannel Users Sent: Saturday, November 28, 2009 3:08 AM Subject: Re: Two Basic Questions, Please? David, Unfortunately you won't save any money this wayYou will pay the same price by sending an SMS from a mobile phone or using Kannel-gms modem. Well, you save money because you can use Kannel instead of other commercial products. Kannel only helps you in enabling SMS on your website/application. Cezary - Original Message - From: David Halliday To: Kannel Users ; Cezary Siwek Sent: 28 November 2009 00:24 Subject: Re: Two Basic Questions, Please? Hi Cezary, Thank you ever so much for the useful info. The basic point that I still can really understand is 'how' Kannel - or any free gateway - could reduce the cost of sending sms. I just need to get the answer before going through installing linux, buyinga GSM modem, etc. Despite googling a lot for the last 10 days, I am still 'confused' really. The aim is to set it up for someone abroad. The sim card provider do not allow sending free messages from a mobile phone. So, if we went for the option: Application - Free Gateway (e.g. Kannel) - GSM modem ( + simcard) How could that be cheaper than to send them directly from a mobile phone? On Kannel's website, one of the answers for this question 1.2 Why should I use Kannel instead of a commercial WAP gateway? is: The price is right :-) Do you really want to pay thousands of dollars of a WAP gateway? May be in this particular case, one should go for the other option, to bypass the sim card provider altogether, i.e.:- Application - Free Gateway (e.g. Kannel) - SMSc agent/provider In any case, thank you once again for your reply. Best regards, David --- On Fri, 27/11/09, Cezary Siwek cza...@thebestisp.co.uk wrote: From: Cezary Siwek cza...@thebestisp.co.uk Subject: Re: Two Basic Questions, Please? To: Kannel Users users@kannel.org Date: Friday, 27 November, 2009, 23:06 I think 1000sms/day is too much for gsm modem/sim card. I'm assuming you are UK based. Most of UK networks don't allow to send more than 3k sms/month (even if you are on 'unlimited text' plan). If you exceed that volume you may be disconnected or charged as per normal text 10-15p. Please check T and C (especially the fair usage policy) of your SIM provider before you decide to go this way. If you get an SMPP connection from SMS carrier you will pay 3-5p/sms. AFAIK: H3G UK - allows to send 3k SMS. After that you will be charged 10p t-mibile UK - If you send more than 3000
Re: Two Basic Questions, Please?
Thank you very much, Nikos, for your reply. I have learned more from your responses. If anyone on the list could point me to a resource or a basic tutorial on the installation of Kannel and the various options and requirements to achieve sms messaging, I would appreciate that very much. In the meantime, I will keep digging .. Best regards, David --- On Fri, 27/11/09, Nikos Balkanas n...@amdtelecom.net wrote: From: Nikos Balkanas n...@amdtelecom.net Subject: Re: Two Basic Questions, Please? To: David Halliday tetrah...@yahoo.co.uk, Kannel Users users@kannel.org Date: Friday, 27 November, 2009, 2:32 Hi, Yes, a GSM modem (or a bank of those) are fully supported by kannel. I have no clue what is the volume restriction, it depends solely on your operator. I just use dedicated SMSc links, but some other guys in the list have more experience with it. Bear in mind that in both cases the final step is an SMSc. The only difference is that with a GSM modem, the SMSc is your provider's responsibility. BR, Nikos - Original Message - From: David Halliday To: Kannel Users Sent: Friday, November 27, 2009 3:18 AM Subject: Re: Two Basic Questions, Please? Hi Nikos, Many thanks for your repsonse. It is really useful. Before actually sending my enquiry to this list, I had done some searchig for a while on google, and I understood that the only way to send sms message to recepints is by going through an SMS Centre for the dsetination network. In your reply, you mentioned as an option: Application - Kannel - GSM modem Can it really be done that way - *bypassing* the SMS centre? And if yes, what is considered as low volume? Would 1000 messages per day be 'OK' with a sim card provider? And of course, it all depends on the destination network. Real SS7 connections may not be an option. I would appreciate your advice. Best regards David --- On Thu, 26/11/09, Nikos Balkanas n...@amdtelecom.net wrote: From: Nikos Balkanas n...@amdtelecom.net Subject: Re: Two Basic Questions, Please? To: David Halliday tetrah...@yahoo.co.uk, Kannel Users users@kannel.org Date: Thursday, 26 November, 2009, 1:27 Hi, 1) To push SMS you will need: Application - Kannel - GSM modem -or- Application - Kannel - SMSc link Application is some kind of web interface to facilitate and schedule pushes. Optionally you can substitute one of kannel's components, smsbox, with SQLbox for sending bulk. GSM modem provides for a low volume, cheaper usually interface using a SIM card. But volume is restricted else SIM maybe disabled. SMSc provides for a more reliable interface, however, throughput is restricted according to your contract. Volume is unlimited (of course you are charged for each SMS). You can also shop around to get the lowest price globally, whereas with a SIM you are restricted by what your operator gives you. 2) Cost depends on your volume and destination. If Clickatell is an aggeragator, ie routes SMS to other SMScs, you can do better than them. If, however, they have real SS7 connections, given their volume, it is unlikely. BR, Nikos - Original Message - From: David Halliday To: Kannel Users Sent: Wednesday, November 25, 2009 9:54 PM Subject: Two Basic Questions, Please? Hello, I have windows xp on my pc, and am very interested in Kannel. Before installing Linux and going through the whole process, I would like to know, if possible, please:- 1. To send sms messages, what else would one need apart from:- Kannel + GSM modem + SMSC connectivity (for recepients' network) Anything else apart from the above 3 'components'? 2. Would that arrangement be actually cheaper than to go through some bulk SMS suppliers like Clickatell, for example? I think it should, but I am not sure. I would greatly appreciate an answer. Best regards, David
Re: Two Basic Questions, Please?
Hi Cezary, Thank you ever so much for the useful info. The basic point that I still can really understand is 'how' Kannel - or any free gateway - could reduce the cost of sending sms. I just need to get the answer before going through installing linux, buyinga GSM modem, etc. Despite googling a lot for the last 10 days, I am still 'confused' really. The aim is to set it up for someone abroad. The sim card provider do not allow sending free messages from a mobile phone. So, if we went for the option: Application - Free Gateway (e.g. Kannel) - GSM modem ( + simcard) How could that be cheaper than to send them directly from a mobile phone? On Kannel's website, one of the answers for this question 1.2 Why should I use Kannel instead of a commercial WAP gateway? is: The price is right :-) Do you really want to pay thousands of dollars of a WAP gateway? May be in this particular case, one should go for the other option, to bypass the sim card provider altogether, i.e.:- Application - Free Gateway (e.g. Kannel) - SMSc agent/provider In any case, thank you once again for your reply. Best regards, David --- On Fri, 27/11/09, Cezary Siwek cza...@thebestisp.co.uk wrote: From: Cezary Siwek cza...@thebestisp.co.uk Subject: Re: Two Basic Questions, Please? To: Kannel Users users@kannel.org Date: Friday, 27 November, 2009, 23:06 I think 1000sms/day is too much for gsm modem/sim card. I'm assuming you are UK based. Most of UK networks don't allow to send more than 3k sms/month (even if you are on 'unlimited text' plan). If you exceed that volume you may be disconnected or charged as per normal text 10-15p. Please check T and C (especially the fair usage policy) of your SIM provider before you decide to go this way. If you get an SMPP connection from SMS carrier you will pay 3-5p/sms. AFAIK: H3G UK - allows to send 3k SMS. After that you will be charged 10p t-mibile UK - If you send more than 3000 texts a month or text more than 200 different numbers in 5 days, you may be breaking your terms and conditions, which say that you can’t use your phone for anything unlawful or to send nuisance O2 UK- All usage must be for your private, personal and non-commercial purposes. You may not use your SIM Card: a. in, or connected to, any other device including modems; Best Regards, Cezary - Original Message - From: David Halliday To: Kannel Users Sent: 27 November 2009 01:18 Subject: Re: Two Basic Questions, Please? Hi Nikos, Many thanks for your repsonse. It is really useful. Before actually sending my enquiry to this list, I had done some searchig for a while on google, and I understood that the only way to send sms message to recepints is by going through an SMS Centre for the dsetination network. In your reply, you mentioned as an option: Application - Kannel - GSM modem Can it really be done that way - *bypassing* the SMS centre? And if yes, what is considered as low volume? Would 1000 messages per day be 'OK' with a sim card provider? And of course, it all depends on the destination network. Real SS7 connections may not be an option. I would appreciate your advice. Best regards David --- On Thu, 26/11/09, Nikos Balkanas n...@amdtelecom.net wrote: From: Nikos Balkanas n...@amdtelecom.net Subject: Re: Two Basic Questions, Please? To: David Halliday tetrah...@yahoo.co.uk, Kannel Users users@kannel.org Date: Thursday, 26 November, 2009, 1:27 Hi, 1) To push SMS you will need: Application - Kannel - GSM modem -or- Application - Kannel - SMSc link Application is some kind of web interface to facilitate and schedule pushes. Optionally you can substitute one of kannel's components, smsbox, with SQLbox for sending bulk. GSM modem provides for a low volume, cheaper usually interface using a SIM card. But volume is restricted else SIM maybe disabled. SMSc provides for a more reliable interface, however, throughput is restricted according to your contract. Volume is unlimited (of course you are charged for each SMS). You can also shop around to get the lowest price globally, whereas with a SIM you are restricted by what your operator gives you. 2) Cost depends on your volume and destination. If Clickatell is an aggeragator, ie routes SMS to other SMScs, you can do better than them. If, however, they have real SS7 connections, given their volume, it is unlikely. BR, Nikos - Original Message - From: David Halliday To: Kannel Users Sent: Wednesday, November 25, 2009 9:54 PM Subject: Two Basic Questions, Please? Hello, I have windows xp on my pc, and am very interested in Kannel. Before installing Linux and going through the whole process, I would like to know, if possible, please:- 1. To send sms messages, what else would one need apart from:- Kannel + GSM modem + SMSC connectivity (for recepients' network) Anything else apart from the above 3 'components'? 2. Would
Re: Two Basic Questions, Please?
Thank you , Cezary and Nikos, for your responses. The option: Application - Kannel - GSM modem is now clear to me. One last point, please, and I will not bother the list with my elementary enquiry anymore. Consider the second option: Application - Kannel - SMSc link Say there is a firm that provides 2 separate services: Service a: Bulk SMS messages to network X Service b: SMSC connectivity with network X (SMPP link) In theory, applying the second option mentioned above, if we went for service b, would it not be cheaper than service a? If the answer is no, then what on earth is the use of the gateway? Most bulk sms firms provide you with a website script/interface to send sms messages from the website anyway, and that is usually included in the price. Best regards, David --- On Sat, 28/11/09, Nikos Balkanas nbalka...@gmail.com wrote: From: Nikos Balkanas nbalka...@gmail.com Subject: Re: Two Basic Questions, Please? To: Cezary Siwek cza...@thebestisp.co.uk, David Halliday tetrah...@yahoo.co.uk, Kannel Users users@kannel.org Date: Saturday, 28 November, 2009, 2:47  Hi, To make it clearer. A GSM modem is a mobile phone as far as the operator is concerned. Both are using a SIM card and are charged by it. Kannel doesn't care. The differences between a GSM modem and a mobile phone (with modem functionality) are: 1) You can use your mobile for other things as well (calling friends, etc.) 2) A dedicated GSM modem is more reliable, in terms of DLRs, status and SMS handling. BR, Nikos - Original Message - From: Cezary Siwek To: David Halliday ; Kannel Users Sent: Saturday, November 28, 2009 3:08 AM Subject: Re: Two Basic Questions, Please? David, Unfortunately you won't save any money this wayYou will pay the same price by sending an SMS from a mobile phone or using Kannel-gms modem. Well, you save money because you can use Kannel instead of other commercial products. Kannel only helps you in enabling SMS on your website/application. Cezary - Original Message - From: David Halliday To: Kannel Users ; Cezary Siwek Sent: 28 November 2009 00:24 Subject: Re: Two Basic Questions, Please? Hi Cezary, Thank you ever so much for the useful info. The basic point that I still can really understand is 'how' Kannel - or any free gateway - could reduce the cost of sending sms. I just need to get the answer before going through installing linux, buyinga GSM modem, etc. Despite googling a lot for the last 10 days, I am still 'confused' really. The aim is to set it up for someone abroad. The sim card provider do not allow sending free messages from a mobile phone. So, if we went for the option: Application - Free Gateway (e.g. Kannel) - GSM modem ( + simcard) How could that be cheaper than to send them directly from a mobile phone? On Kannel's website, one of the answers for this question 1.2 Why should I use Kannel instead of a commercial WAP gateway? is: The price is right :-) Do you really want to pay thousands of dollars of a WAP gateway? May be in this particular case, one should go for the other option, to bypass the sim card provider altogether, i.e.:- Application - Free Gateway (e.g. Kannel) - SMSc agent/provider In any case, thank you once again for your reply. Best regards, David --- On Fri, 27/11/09, Cezary Siwek cza...@thebestisp.co.uk wrote: From: Cezary Siwek cza...@thebestisp.co.uk Subject: Re: Two Basic Questions, Please? To: Kannel Users users@kannel.org Date: Friday, 27 November, 2009, 23:06 I think 1000sms/day is too much for gsm modem/sim card. I'm assuming you are UK based. Most of UK networks don't allow to send more than 3k sms/month (even if you are on 'unlimited text' plan). If you exceed that volume you may be disconnected or charged as per normal text 10-15p. Please check T and C (especially the fair usage policy) of your SIM provider before you decide to go this way. If you get an SMPP connection from SMS carrier you will pay 3-5p/sms. AFAIK: H3G UK - allows to send 3k SMS. After that you will be charged 10p t-mibile UK - If you send more than 3000 texts a month or text more than 200 different numbers in 5 days, you may be breaking your terms and conditions, which say that you can’t use your phone for anything unlawful or to send nuisance O2 UK- All usage must be for your private, personal and non-commercial purposes. You may not use your SIM Card: a. in, or connected to, any other device including modems; Best Regards, Cezary - Original Message - From: David Halliday To: Kannel Users Sent: 27 November 2009 01:18 Subject: Re: Two Basic Questions, Please? Hi Nikos, Many thanks for your repsonse. It is really useful. Before actually sending my enquiry to this list, I had done some searchig for a while on google, and I understood that the only way to send sms message to recepints is by going through an SMS Centre
Re: Two Basic Questions, Please?
Hi Nikos, Many thanks for your repsonse. It is really useful. Before actually sending my enquiry to this list, I had done some searchig for a while on google, and I understood that the only way to send sms message to recepints is by going through an SMS Centre for the dsetination network. In your reply, you mentioned as an option: Application - Kannel - GSM modem Can it really be done that way - *bypassing* the SMS centre? And if yes, what is considered as low volume? Would 1000 messages per day be 'OK' with a sim card provider? And of course, it all depends on the destination network. Real SS7 connections may not be an option. I would appreciate your advice. Best regards David --- On Thu, 26/11/09, Nikos Balkanas n...@amdtelecom.net wrote: From: Nikos Balkanas n...@amdtelecom.net Subject: Re: Two Basic Questions, Please? To: David Halliday tetrah...@yahoo.co.uk, Kannel Users users@kannel.org Date: Thursday, 26 November, 2009, 1:27 Hi, 1) To push SMS you will need: Application - Kannel - GSM modem -or- Application - Kannel - SMSc link Application is some kind of web interface to facilitate and schedule pushes. Optionally you can substitute one of kannel's components, smsbox, with SQLbox for sending bulk. GSM modem provides for a low volume, cheaper usually interface using a SIM card. But volume is restricted else SIM maybe disabled. SMSc provides for a more reliable interface, however, throughput is restricted according to your contract. Volume is unlimited (of course you are charged for each SMS). You can also shop around to get the lowest price globally, whereas with a SIM you are restricted by what your operator gives you. 2) Cost depends on your volume and destination. If Clickatell is an aggeragator, ie routes SMS to other SMScs, you can do better than them. If, however, they have real SS7 connections, given their volume, it is unlikely. BR, Nikos - Original Message - From: David Halliday To: Kannel Users Sent: Wednesday, November 25, 2009 9:54 PM Subject: Two Basic Questions, Please? Hello, I have windows xp on my pc, and am very interested in Kannel. Before installing Linux and going through the whole process, I would like to know, if possible, please:- 1. To send sms messages, what else would one need apart from:- Kannel + GSM modem + SMSC connectivity (for recepients' network) Anything else apart from the above 3 'components'? 2. Would that arrangement be actually cheaper than to go through some bulk SMS suppliers like Clickatell, for example? I think it should, but I am not sure. I would greatly appreciate an answer. Best regards, David
Two Basic Questions, Please?
Hello, I have windows xp on my pc, and am very interested in Kannel. Before installing Linux and going through the whole process, I would like to know, if possible, please:- 1. To send sms messages, what else would one need apart from:- Kannel + GSM modem + SMSC connectivity (for recepients' network) Anything else apart from the above 3 'components'? 2. Would that arrangement be actually cheaper than to go through some bulk SMS suppliers like Clickatell, for example? I think it should, but I am not sure. I would greatly appreciate an answer. Best regards, David
WEB ADMINISTATOR
I need to see the website Kannel administration, but will not let me see, I'm getting blank screen. I checked the browser settings and no problems with restrictions, also check that the port was 13,000 not using one. I tried from another browser on another PC and the problem persists ... can help sort out the solution.? -- El universitario de estos tiempos está llamado a convertir su espacio en un espacio productivo
Re: WEB ADMINISTATOR
thanks the problems are fix - Alejandro Guerrieri alejandro.guerri...@gmail.com escribió: | Please post more information: | 1. Url being used 2. Configuration (only the core group actually) 3. What do you get when you try to access it, if anything? | Regards, | Alejandro | | | On Mon, Nov 16, 2009 at 4:37 PM, David G. Navarro Ferrer dgnava...@estudiantes.uci.cu wrote: | | | I need to see the website Kannel administration, but will not let me see, I'm getting blank screen. I checked the browser settings and no problems with restrictions, also check that the port was 13,000 not using one. I tried from another browser on another PC and the problem persists ... can help sort out the solution.? | | -- | | El universitario de estos tiempos está llamado a convertir su espacio en un espacio productivo | | -- El universitario de estos tiempos está llamado a convertir su espacio en un espacio productivo
Cygwin + Kannel
Hi: I'm riding Kannel on Windows using Cygwin tools to emulate. When I run it tells me missing the libraries to compile C. Someone could tell me what is the specific library needs?, For I have installed all coming at the Cygwin site and did not work with any. Greetings. David Gerard
Re: kannel + DNS
Disculpenme, pero parece que no me entienden por el idioma. MIren, yo tengo un temrinal que hace una peticion a un servidor web donde tengo alojado una pagina WAP. Esa petición pasa por la pasarela con una direccion (http://192.168.10.23/PortalWap), se conecta al servidor web y este le meustra la pagina. Yo necesito que en vez de poner la direccion http://192.168.10.23/PortalWap la dirección que ponga sea http://miaplicacion.ebussinescel.uci.cu, por ejemplo. Para ello necesito montar un servidor DNS. Mis dudas son las siguienes: 1.) Cómo hago que en mi temrinal ponga la direccion http://miaplicacion.ebussinescel.uci.cu, esta peticion pase por el kannel, luego por el servidor DNS, el mismo la convierta a http://192.168.10.23/PortalWap (Direccion Fisica donde esta alojado mi portal WAP) y entonces muestre el portal wap que tengo hecho. Disculpen, pero es que hablo en español.. Saludos... David G. - Nikos Balkanas nbalka...@gmail.com escribió: | Hi, I will try to explain better, so that there are no missunderstandings, and hopefully end all this mail. 1) You do not put applications to DNS. You put servers into DNS, or even better you assign IP addresses to DNS. Thereferore, you can never hope to put Kannel into DNS. However, all applications within a server that has DNS, can be accessed by name, instead of by IP. 2) You do not bind applications to DNS. You assign DNS resolution to OS. If a server has DNS access, all of its applications can share this access transparently. This way you can feed applications with named URLs. You can never bind one single application to DNS, or exclude DNS for a single application, while the rest of the applications do the opposite. I would appreciate if you stopped asking these questions here. Hope this helps, Nikos | - Original Message - | From: David G. Navarro Ferrer | To: Alejandro Guerrieri | Cc: users | Sent: Wednesday, October 28, 2009 6:14 PM | Subject: Re: kannel + DNS | | | you're right. My question is not whether I can put Kannel within the DNS. My question is how to bind the Kannel with DNS. | - Alejandro Guerrieri alejandro.guerri...@gmail.com escribiΓ³: | | David, | | Nobody said it wasn't important. It's just not the right document to learn how to use Kannel. | | You evidently ignore how does the DNS protocol works, otherwise you wouldn't be asking the nonsense questions you're asking... | | If you read a little about DNS you'll soon find out that there's nothing to configure on Kannel to get DNS resolution working on your server nor to point a domain to your IP. | | Hint: Search for dns on the user guide. This is completely unrelated to Kannel. | | Regards, | | Alejandro | | | | On Wed, Oct 28, 2009 at 4:55 PM, David G. Navarro Ferrer dgnava...@estudiantes.uci.cu wrote: | | | | | | sorry but if de architecture document of Kannel isn't an important document why it's in your site? | | I think you has to make the homework of DNS, I strongly recommend the website http://es.wikipedia.org/wiki/DNS . What I need is that once my request to pass through the Kannel before reaching a Web server passes the DNS to convert my IP address to a URL under a domain. Does anyone know how? I recommend, so that really does know how Kannel in all its magnitude, the document architecture. | | | | - Alejandro Guerrieri alejandro.guerri...@gmail.com escribiΓ³: | | | | | No it's not related to kannel at all and there's nothing to do in kannel to point a domain to an IP. | | | If you're asking this, you need to do your homework about DNS resolution... | | | Besides, the architecture document, apart from being out of date, it's not the user guide, which you should be using to learn about Kannel's operation/administration. | | | Regards, | | | Alejandro | | | | | | | | | | | On Wed, Oct 28, 2009 at 4:25 PM, David G. Navarro Ferrer dgnava...@estudiantes.uci.cu wrote: | | | | | | | | sorry but in the document architecture Kannel said that you can bind a DNS with Kannel for greater efficiency in HTTP requests. I have an own web server with host page and I want instead of putting http://192.168.10.65:8081/aplicacion can put http://aplicacion.bussines.com.For that we need a DNS. This is relevant for Kannel because in the architecture document is recommended for http connections. | | | | | | - Nikos Balkanas n...@amdtelecom.net escribiΓ³: | | | | | | | Hi, This is not relevant to kannel. Please address OS user groups. If using linux try /etc/resolv.conf. Please do not post here questions unrelated to kannel. BR, Nikos | | | | | | - Original Message - | | | | From: David G. Navarro Ferrer | | | | | | To: users | | | | Sent: Wednesday, October 28, 2009 4:37 PM | | | | Subject: kannel + DNS | | | | | | | | | | | | i need to link Kannel with DNS server but i dont know and in the userguide dont have
kannel + DNS
i need to link Kannel with DNS server but i dont know and in the userguide dont have examples about this theme... Please, i need your help. -- El universitario de estos tiempos está llamado a convertir su espacio en un espacio productivo
Re: kannel + DNS
you're right. My question is not whether I can put Kannel within the DNS. My question is how to bind the Kannel with DNS. - Alejandro Guerrieri alejandro.guerri...@gmail.com escribió: | David, | Nobody said it wasn't important. It's just not the right document to learn how to use Kannel. | You evidently ignore how does the DNS protocol works, otherwise you wouldn't be asking the nonsense questions you're asking... | If you read a little about DNS you'll soon find out that there's nothing to configure on Kannel to get DNS resolution working on your server nor to point a domain to your IP. | Hint: Search for dns on the user guide. This is completely unrelated to Kannel. | Regards, | Alejandro | | On Wed, Oct 28, 2009 at 4:55 PM, David G. Navarro Ferrer dgnava...@estudiantes.uci.cu wrote: | | | sorry but if de architecture document of Kannel isn't an important document why it's in your site? | I think you has to make the homework of DNS, I strongly recommend the website http://es.wikipedia.org/wiki/DNS . What I need is that once my request to pass through the Kannel before reaching a Web server passes the DNS to convert my IP address to a URL under a domain. Does anyone know how? I recommend, so that really does know how Kannel in all its magnitude, the document architecture. | | - Alejandro Guerrieri alejandro.guerri...@gmail.com escribió: | | | No it's not related to kannel at all and there's nothing to do in kannel to point a domain to an IP. | | If you're asking this, you need to do your homework about DNS resolution... | | Besides, the architecture document, apart from being out of date, it's not the user guide, which you should be using to learn about Kannel's operation/administration. | | Regards, | | Alejandro | | | | | | | On Wed, Oct 28, 2009 at 4:25 PM, David G. Navarro Ferrer dgnava...@estudiantes.uci.cu wrote: | | | | | sorry but in the document architecture Kannel said that you can bind a DNS with Kannel for greater efficiency in HTTP requests. I have an own web server with host page and I want instead of putting http://192.168.10.65:8081/aplicacion can put http://aplicacion.bussines.com.For that we need a DNS. This is relevant for Kannel because in the architecture document is recommended for http connections. | | | | - Nikos Balkanas n...@amdtelecom.net escribió: | | | | | Hi, This is not relevant to kannel. Please address OS user groups. If using linux try /etc/resolv.conf. Please do not post here questions unrelated to kannel. BR, Nikos | | | | - Original Message - | | | From: David G. Navarro Ferrer | | | | To: users | | | Sent: Wednesday, October 28, 2009 4:37 PM | | | Subject: kannel + DNS | | | | | | | | | i need to link Kannel with DNS server but i dont know and in the userguide dont have examples about this theme... Please, i need your help. | | | | | | -- | | | | | | El universitario de estos tiempos estΓ΅ llamado a convertir su espacio en un espacio productivo | | | | | | | -- | | | | | El universitario de estos tiempos está llamado | a convertir su espacio en un espacio productivo | | | | | | -- | | | El universitario de estos tiempos está llamado a convertir su espacio en un espacio productivo | | -- El universitario de estos tiempos está llamado a convertir su espacio en un espacio productivo
protocols of kannel
I need to know how can I monitor the protocols that are increasingly using some information that passes through Kannel. Are there any tools for it? --
Re: protocols of kannel
Excuse the language but I speak Spanish. It turns out that I need to know how I know that protocols are being used when communicating by Kannel. The problem is I have a terminal that communicates via WAP 1.1 and WAP 2.0 and then I make a request to a web server through Kannel, then this answer me as I am able to accept me the temrinal WAP 2.0, then I returned the Kannel HTTP response and I need to answer me in WML, as if for WAP 1.1. How I can do this and to know which protocols are being used through Kannel. - Nikos Balkanas n...@amdtelecom.net escribió: | Hi, Cannot understand you. What do you mean by increasingly using some information? BR, Nikos | - Original Message - | From: David G. Navarro Ferrer | To: users | Sent: Tuesday, October 27, 2009 4:25 PM | Subject: protocols of kannel | | I need to know how can I monitor the protocols that are increasingly using some information that passes through Kannel. Are there any tools for it? | | -- | | | -- El universitario de estos tiempos está llamado a convertir su espacio en un espacio productivo
Re: Help me about Kannel + HTTP connection
Sorry, but I think you have not understood my previous email. The intention was never to attack anyone, but I do send me a thousand questions and reading the user guide, a document that I have read several times and still can not find the answers. If I thought that the Guide or the community will not be productive, not write to it, on the contrary, only need my software to work and therefore ask the questions because I dont find the answers in the User Guide. I hope he had not hurt anyone's feelings, but if I expect more to help new developers. - Nikos Balkanas nbalka...@gmail.com escribió: | Hi, I have rewritten the whole wap code for another (commercial) project. However, let's pretend, as you say, that I don't know how to answer. Since you know the User's Guide by heart, please enlighten me: 1) What are the required modules to run wap? 2) What variables in the core group are needed to enable wap? 3) What groups do you need to configure aforementioned modules? 4) In what page in the guide is an example wap... configuration, and in what a PPG? PS. A lot of good people have contributed extra effort to maintain this guide. I trust that this is enough, and that you respect them for what they did, by not asking them to read it to you as well. BR, Nikos | - Original Message - | From: David Gerardo | To: Nikos Balkanas | Cc: users | Sent: Thursday, October 15, 2009 10:09 PM | Subject: Re: Help me about Kannel + HTTP connection | | excuse me Kannel community but every time I ask a question send me to see the user guide, I am a programmer and software developer and well that is the user guide. If I make a question is precisely because they find the answer in the materials provided by the community, so if you do not know the answers, understand, but no more to send me the user guide that I almost know it by heart. Sorry for the message but it is certainly unpleasant to all the questions I am doing so visit rebuts materials. | | - Nikos Balkanas n...@amdtelecom.net escribiΓ³: | | Hi, There is an excellent how-to and examples in the User's Guide. You can download it from the site. If you have specific questions about what you read we will be glad to help you. BR, Nikos | | - Original Message - | | From: David Gerardo | | To: users | | Sent: Thursday, October 15, 2009 8:16 PM | | Subject: Help me about Kannel + HTTP connection | | | | Gentlemen, please help urgently. I have a WAP terminal (it is a trunki) that connects to Kannel to review a website that is hosted on another computer. The Kannel creates bridges between the terminal and host the site. I need to know the file kannel.conf, What do I have to configure? The IP address of the computer that is hosting the Kannel is 10.31.18.4 and the IP address where is the site that I want to show in the terminal is on 10.31.18.5. Can you tell me the settings I put in the kannel.conf? | | Thank you for your support. | | | | -- | | | | | | -- | | El universitario de estos tiempos estΓ΅ llamado a convertir su espacio en un espacio productivo | -- El universitario de estos tiempos está llamado a convertir su espacio en un espacio productivo
question about kannel's service
I have a question ... Kannel the only thing you do is set the configuration variables for communication between mobile devices and services for these devices? At the end you have to configure mobile devices to communicate through the Kannel gateway.?
Help me about Kannel + HTTP connection
Gentlemen, please help urgently. I have a WAP terminal (it is a trunki) that connects to Kannel to review a website that is hosted on another computer. The Kannel creates bridges between the terminal and host the site. I need to know the file kannel.conf, What do I have to configure? The IP address of the computer that is hosting the Kannel is 10.31.18.4 and the IP address where is the site that I want to show in the terminal is on 10.31.18.5. Can you tell me the settings I put in the kannel.conf? Thank you for your support. --
Re: Help me about Kannel + HTTP connection
Excuse me but my question is precisely because I have read the user guide several times and still not give me the answer I need. - Nikos Balkanas n...@amdtelecom.net escribió: | Hi, There is an excellent how-to and examples in the User's Guide. You can download it from the site. If you have specific questions about what you read we will be glad to help you. BR, Nikos | - Original Message - | From: David Gerardo | To: users | Sent: Thursday, October 15, 2009 8:16 PM | Subject: Help me about Kannel + HTTP connection | | Gentlemen, please help urgently. I have a WAP terminal (it is a trunki) that connects to Kannel to review a website that is hosted on another computer. The Kannel creates bridges between the terminal and host the site. I need to know the file kannel.conf, What do I have to configure? The IP address of the computer that is hosting the Kannel is 10.31.18.4 and the IP address where is the site that I want to show in the terminal is on 10.31.18.5. Can you tell me the settings I put in the kannel.conf? | Thank you for your support. | | -- | | -- El universitario de estos tiempos está llamado a convertir su espacio en un espacio productivo
Re: Help me about Kannel + HTTP connection
excuse me Kannel community but every time I ask a question send me to see the user guide, I am a programmer and software developer and well that is the user guide. If I make a question is precisely because they find the answer in the materials provided by the community, so if you do not know the answers, understand, but no more to send me the user guide that I almost know it by heart. Sorry for the message but it is certainly unpleasant to all the questions I am doing so visit rebuts materials. - Nikos Balkanas n...@amdtelecom.net escribió: | Hi, There is an excellent how-to and examples in the User's Guide. You can download it from the site. If you have specific questions about what you read we will be glad to help you. BR, Nikos | - Original Message - | From: David Gerardo | To: users | Sent: Thursday, October 15, 2009 8:16 PM | Subject: Help me about Kannel + HTTP connection | | Gentlemen, please help urgently. I have a WAP terminal (it is a trunki) that connects to Kannel to review a website that is hosted on another computer. The Kannel creates bridges between the terminal and host the site. I need to know the file kannel.conf, What do I have to configure? The IP address of the computer that is hosting the Kannel is 10.31.18.4 and the IP address where is the site that I want to show in the terminal is on 10.31.18.5. Can you tell me the settings I put in the kannel.conf? | Thank you for your support. | | -- | | -- El universitario de estos tiempos está llamado a convertir su espacio en un espacio productivo
documentation
Have you any documentation in spanish about kannel?? -- El universitario de estos tiempos está llamado a convertir su espacio en un espacio productivo
Kannel + WAP
Does the value of the variable http-interface-name, whose parameter is an IP address, which is configured on a WAP terminal to connect to Kannel?
How do I configure Kannel to WAP terminal can communicate to an application?
How do I configure Kannel to WAP terminal can communicate to an application?
Where is hosted on Debian files Kannel source code?
Where is hosted on Debian files Kannel source code? --
HELP! Patent claim! Can we use an alternate protocol?
Hello, Us users of SMS Shortcodes are getting hit in the US for violating a patent by TCS Inc. The patent claims to cover: A gateway, comprising: a first communication path to accept a short message from a mobile device; a translation module to insert said short message into an Hypertext Transfer Protocol (HTTP) message; a second communication path to push said HTTP message to at least one Universal Resource Locator (URL); and a return communication path to receive a return message relating to said HTTP message. The patent goes on to mention a whole bunch of stuff, ie, using HTTP POST to send the http message, etc. I just got out of a meeting with my lawyer. He says, the only way to get around this is to NOT use HTTP. Over the weekend, I tried to use the sms-service using EXEC instead of GET-URL, which worked fine... and then the server crashed... i'm guessing too many spawned processes? My question to you all is: how can we NOT use HTTP but have the same end result? ideally, it would use a command-line exec, but push it into a waiting server, instead of spawning a new thread. Does anybody have any ideas on how to do this? Thank you very much, David
Re: HELP! Patent claim! Can we use an alternate protocol?
my php script is this really, really long php script that controls all logic in our company. my concern is that having 10+ running copies of the php script (vs being handled by apache which probably does a better job of managing overhead) caused the server to crash (or kannel to be unresponsive. the command i had is: exec = /var/www/vhosts/.../httpdocs/exec.php msg=%a phone=%p shortcod e=%P operatorid=%o metadata=%D /dev/null 21 now looking at it, if I add a to the end, would that fix it as it detaches the process? ie: exec = /var/www/vhosts/.../httpdocs/exec.php msg=%a phone=%p shortcode=%P operatorid=%o metadata=%D /dev/null 21 --- On Thu, 2/12/09, Nikos Balkanas nbalka...@gmail.com wrote: From: Nikos Balkanas nbalka...@gmail.com Subject: Re: HELP! Patent claim! Can we use an alternate protocol? To: dbw1...@yahoo.com, users@kannel.org Date: Thursday, February 12, 2009, 1:39 PM Hi, You probably have a problem in your exec code. Since it is a different process it doesn't affect kannel and only the server or its target. Mind posting it? BR, Nikos - Original Message - From: David To: users@kannel.org Sent: Thursday, February 12, 2009 9:00 PM Subject: HELP! Patent claim! Can we use an alternate protocol? Hello, Us users of SMS Shortcodes are getting hit in the US for violating a patent by TCS Inc. The patent claims to cover: A gateway, comprising: a first communication path to accept a short message from a mobile device; a translation module to insert said short message into an Hypertext Transfer Protocol (HTTP) message; a second communication path to push said HTTP message to at least one Universal Resource Locator (URL); and a return communication path to receive a return message relating to said HTTP message. The patent goes on to mention a whole bunch of stuff, ie, using HTTP POST to send the http message, etc. I just got out of a meeting with my lawyer. He says, the only way to get around this is to NOT use HTTP. Over the weekend, I tried to use the sms-service using EXEC instead of GET-URL, which worked fine... and then the server crashed... i'm guessing too many spawned processes? My question to you all is: how can we NOT use HTTP but have the same end result? ideally, it would use a command-line exec, but push it into a waiting server, instead of spawning a new thread. Does anybody have any ideas on how to do this? Thank you very much, David
Receiving Long SMS Through Modem
Hi all, when I recieve a long/concatenated message through my wavecom fastrack modem the get-url in the sms-service is also called twice or more. Is it possible to force the modem to first assemble the message and execute the get-url once? If not, how do others handle this case in order to forward the message in just one request? Thanks, David
Connecting a GSM Phone to Linux
Hi, I have a very lame question, I want to use a Sony Ericsson P990i as a modem SMSC via Kannel, but I don't know how to connect it to Linux? Can someone help me? My system is as follows: Desktop: Ubuntu 8.04 (2.6.24-22-generic) Kannel: 1.4.1-2ubuntu1 (installed via package manager). I don't have bluetooth enabled on my desktop, I do have a USB cable for the P990i. Sorry if this is a lame request, but I am reasonable new to Linux and very new to Kannel, if someone could send me in the right direction, I would appreciate it. thanks David
Re: Cell phone companes - will they shut me down?
A company I consulted for once opened a few unlimited text plans Cingular for testing an M2M system. At the end of the first month they got a 5,460-page bill. The bill was only $30, but Cingular turned off the accounts after that. You mileage may vary. On Dec 15, 2008, at 1:27 PM, Scott wrote: First I want to preface I’m in the USA. If I were to use a GSM modem and have an unlimited text plan, would I be shutdown for a high volume of SMS’s? Or at what point would I be shut down? Is there anything else to worry about? Thanks Scott David A. Burgess Kestrel Signal Processing, Inc.
kannel installation help
Hi, I've been using SMS providers that have http api's for years. But now I need to go directly to an SMSC via SMPP. I found some online tutorials and tried installing kannel myself. It compiled, but still no success. I only need it for the basic function of send messages from my applications to the SMSC. I'm not dealing with modems or incoming messages. I would appreciate any assistance in installing it and sending from a PHP script. Is other sofware required. How do I start the service? This was the output when I first ran smsbox: It starts out ok, but then there's a connection failed error. thank you, Bruno 2008-02-17 04:32:11 [9980] [0] PANIC: ./smsbox [0x805151d] 2008-02-17 04:32:38 [15441] [0] INFO: Debug_lvl = -1, log_file = none, log_lvl= 0 2008-02-17 04:32:38 [15441] [0] DEBUG: Kannel smsbox version `1.4.1'. Build `Feb 17 2008 03:49:14', compiler `3.4.5 20051201 (Red Hat 3.4.5-2)'. System Linux, release 2.6.9-023stab043.1-smp, version #1 SMP Mon Mar 5 16:35:19MSK 2007, machine i686. Libxml version 2.6.16. Using native malloc. 2008-02-17 04:32:38 [15441] [0] INFO: Service global sender set as '13013' 2008-02-17 04:32:38 [15441] [0] INFO: HTTP: Opening server at port 13013. 2008-02-17 04:32:38 [15441] [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller) 2008-02-17 04:32:38 [15441] [0] DEBUG: Started thread 2 (gwlib/http.c:server_thr ead) 2008-02-17 04:32:38 [15441] [0] INFO: Set up send sms service at port 13013 2008-02-17 04:32:38 [15441] [0] DEBUG: Started thread 3 (gw/smsbox.c:sendsms_thr ead) 2008-02-17 04:32:38 [15441] [0] DEBUG: - - 2008-02-17 04:32:38 [15441] [0] DEBUG: Kannel smsbox version 1.4.1 starting 2008-02-17 04:32:38 [15441] [0] DEBUG: Started thread 4 (gw/smsbox.c:obey_reques t_thread) 2008-02-17 04:32:38 [15441] [0] DEBUG: Started thread 5 (gw/smsbox.c:url_result_ thread) 2008-02-17 04:32:38 [15441] [3] DEBUG: Thread 3 (gw/smsbox.c:sendsms_thread) map s to pid 15441. 2008-02-17 04:32:38 [15441] [0] DEBUG: Started thread 6 (gw/smsbox.c:http_queue_ thread) 2008-02-17 04:32:38 [15441] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) map s to pid 15441. 2008-02-17 04:32:38 [15441] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) maps to p id 15441. 2008-02-17 04:32:38 [15441] [0] ERROR: connect failed 2008-02-17 04:32:38 [15441] [0] ERROR: System error 111: Connection refused 2008-02-17 04:32:38 [15441] [4] DEBUG: Thread 4 (gw/smsbox.c:obey_request_thread ) maps to pid 15441. 2008-02-17 04:32:38 [15441] [0] ERROR: error connecting to server `127.0.0.1' atport `13001' 2008-02-17 04:32:38 [15441] [0] PANIC: Couldn't connect to the bearerbox. 2008-02-17 04:32:38 [15441] [5] DEBUG: Thread 5 (gw/smsbox.c:url_result_thread)maps to pid 15441. 2008-02-17 04:32:38 [15441] [0] PANIC: ./smsbox(gw_panic+0xa3) [0x807cf3f] 2008-02-17 04:32:38 [15441] [0] PANIC: ./smsbox(main+0xc1f) [0x8056537] 2008-02-17 04:32:38 [15441] [0] PANIC: /lib/tls/libc.so.6(__libc_start_main+0xd3 ) [0xb7d53e23]
Message Queue Full causes sms to be sent to smsc repeatedly many times a second
Hi, I'm having a problem very similar to http://bugs.kannel.org/view.php?id=352 The problem that I'm having is: 1. I send an sms to a specific number like this: /cgi-bin/sendsms?user=myuserpassword=mypasswordto=%2BSomeMobileNumber text=HereIsALongTextcoding=2charset=utf-8from=647463 2. As a result Kannel resends an sms repeatedly many times a second to that phone number overwhelming the smsc I see in kannel logs for each sms that is being sent for this user the following message: ERROR: SMPP[xx]: SMSC returned error code 0x0014 (Message Queue Full) in response to submit_sm. The problem happens only when I send sms to this specific number, with other phone numbers its ok; the smsc guys want to disconnect me because they say I'm sending too many sms to the smsc a second - too many sms sent to smsc. Note that previously the system have sent sms with long text so they were split, to that number (the system converts email to sms to it sent many emails as sms to that phone number). I suspect that maybe that mobile phone is turned off (I don't know for sure whether that's true since I don't have control over this mobile phone its not in my control) so the SMSC queue is probably as message says full of messages that might have not been received by mobile phone. I have tried using: sms-resend-freq = 120 sms-resend-retry = 5 However these parameters didn't affect anything, the sms was still resent many times a second (and many times, was not limited to 5) and I had to restart the kannel to overcome this. Is there a solution to this problem? Is there a workaround to this problem? (My system is in production) If this is a bug, when is it planned to be fixed? Thanks Tomer
RE: Message Queue Full causes sms to be sent to smsc repeatedly manytimes a second
I forgot to mention that I use kannel version 1.4.1 Thanks Tomer From: Tomer Ben David [mailto:[EMAIL PROTECTED] Sent: Monday, January 14, 2008 11:24 AM To: users@kannel.org Subject: Message Queue Full causes sms to be sent to smsc repeatedly manytimes a second Hi, I'm having a problem very similar to http://bugs.kannel.org/view.php?id=352 The problem that I'm having is: 1. I send an sms to a specific number like this: /cgi-bin/sendsms?user=myuserpassword=mypasswordto=%2BSomeMobileNumber text=HereIsALongTextcoding=2charset=utf-8from=647463 2. As a result Kannel resends an sms repeatedly many times a second to that phone number overwhelming the smsc I see in kannel logs for each sms that is being sent for this user the following message: ERROR: SMPP[xx]: SMSC returned error code 0x0014 (Message Queue Full) in response to submit_sm. The problem happens only when I send sms to this specific number, with other phone numbers its ok; the smsc guys want to disconnect me because they say I'm sending too many sms to the smsc a second - too many sms sent to smsc. Note that previously the system have sent sms with long text so they were split, to that number (the system converts email to sms to it sent many emails as sms to that phone number). I suspect that maybe that mobile phone is turned off (I don't know for sure whether that's true since I don't have control over this mobile phone its not in my control) so the SMSC queue is probably as message says full of messages that might have not been received by mobile phone. I have tried using: sms-resend-freq = 120 sms-resend-retry = 5 However these parameters didn't affect anything, the sms was still resent many times a second (and many times, was not limited to 5) and I had to restart the kannel to overcome this. Is there a solution to this problem? Is there a workaround to this problem? (My system is in production) If this is a bug, when is it planned to be fixed? Thanks Tomer This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals computer viruses.
No more sendsms.cgi response Message splits:...
Hello list, I am currently upgrading from 1.3.1 to 1.4.1 and to my deception had to find out there is no longer a message displayed when message concatenation occurs. That was actually pretty handy. I noticed it is still printed in the sms.kannel.log file. Does anyone have an idea on how to reactivate it? David
configure: WARNING: mysql/mysql.h: accepted by the compiler, rejected by the preprocessor!
Hi list, I built kannel 1.4.1 on a Freebsd 6.2-STABLE with MySQL 5.0.45 from the ports (included the use-mysql option in the Makefile). During configure I noticed these warnings: checking mysql/mysql.h usability... yes checking mysql/mysql.h presence... no configure: WARNING: mysql/mysql.h: accepted by the compiler, rejected by the preprocessor! configure: WARNING: mysql/mysql.h: proceeding with the compiler's result checking for mysql/mysql.h... yes checking mysql/mysql_version.h usability... yes checking mysql/mysql_version.h presence... no configure: WARNING: mysql/mysql_version.h: accepted by the compiler, rejected by the preprocessor! configure: WARNING: mysql/mysql_version.h: proceeding with the compiler's result checking for mysql/mysql_version.h... yes Kannel builds and runs (test-wise) without problems. Anyway, I am still a bit concerned about the warnings. Can anyone explain them me and is there a potential danger from them? Thanks, David
Problem Sending SMS with Kannel using Modem Sony Ericsson GT48
Hello ! I'm having problem sending a SMS with Kannel, it always says a -1 response an i don't understand. let me paste the logs and the config. Any idea ? == CONFIG === # Core Config group = core admin-port = 13000 admin-password = XXX status-password = XXX admin-deny-ip = *.*.*.* admin-allow-ip = 127.0.0.1;10.10.0.* smsbox-port = 13002 wdp-interface-name = * log-file = /var/log/kannel/bearerbox.log box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1;10.10.0.* store-file = /var/log/kannel/kannel.store access-log = /var/log/kannel/access.log # Modem ;) group = smsc smsc = at smsc-id = SMSC modemtype = sonygt48 device = /dev/ttyUSB0 speed = 9600 group = modems id = sonygt48 name = Sony Ericsson detect-string = GR48 init-string = AT+CNMI=3,2,0,0 reset-string = ATZ broken = true # SMS User group = sendsms-user username = sms password = sms123 # SMS Box group = smsbox bearerbox-host = localhost sendsms-port = 13003 global-sender = 301002233 log-file = /var/log/kannel/smsbox.log access-log = /var/log/kannel/smsaccess.log === LOGS (ACCESS LOG) = 2007-07-09 14:44:15 Log begins 2007-07-09 14:45:12 FAILED Send SMS [SMSC:SMSC] [SVC:sms] [ACT:] [BINF:] [from:301002233] [to:3014215586] [flags:-1:0:-1:-1:-1] [msg:20:Mensaje desde Kannel] [udh:0:] === LOGS (BEARER LOG) === 2007-07-09 14:44:31 [11692] [6] INFO: AT2[SMSC]: init device 2007-07-09 14:44:31 [11692] [6] INFO: AT2[SMSC]: speed set to 9600 2007-07-09 14:44:32 [11692] [6] DEBUG: AT2[SMSC]: -- ATZ^M 2007-07-09 14:44:32 [11692] [6] DEBUG: AT2[SMSC]: -- OK 2007-07-09 14:44:32 [11692] [6] DEBUG: AT2[SMSC]: -- AT^M 2007-07-09 14:44:33 [11692] [6] DEBUG: AT2[SMSC]: -- OK 2007-07-09 14:44:33 [11692] [6] DEBUG: AT2[SMSC]: -- ATF^M 2007-07-09 14:44:33 [11692] [6] DEBUG: AT2[SMSC]: -- ATF 2007-07-09 14:44:33 [11692] [6] DEBUG: AT2[SMSC]: -- OK 2007-07-09 14:44:33 [11692] [6] DEBUG: AT2[SMSC]: -- ATE0^M 2007-07-09 14:44:33 [11692] [6] DEBUG: AT2[SMSC]: -- ATE0 2007-07-09 14:44:33 [11692] [6] DEBUG: AT2[SMSC]: -- OK 2007-07-09 14:44:33 [11692] [6] DEBUG: AT2[SMSC]: -- AT+IFC=2,2^M 2007-07-09 14:44:33 [11692] [6] DEBUG: AT2[SMSC]: -- OK 2007-07-09 14:44:33 [11692] [6] DEBUG: AT2[SMSC]: -- AT+CPIN?^M 2007-07-09 14:44:33 [11692] [6] DEBUG: AT2[SMSC]: -- +CPIN: READY 2007-07-09 14:44:34 [11692] [6] DEBUG: AT2[SMSC]: -- OK 2007-07-09 14:44:34 [11692] [6] DEBUG: AT2[SMSC]: -- AT+CMGF=0^M 2007-07-09 14:44:34 [11692] [6] DEBUG: AT2[SMSC]: -- OK 2007-07-09 14:44:34 [11692] [6] DEBUG: AT2[SMSC]: -- AT+CSMS=?^M 2007-07-09 14:44:34 [11692] [6] DEBUG: AT2[SMSC]: -- +CSMS: (0) 2007-07-09 14:44:34 [11692] [6] DEBUG: AT2[SMSC]: -- OK 2007-07-09 14:44:34 [11692] [6] DEBUG: AT2[SMSC]: -- AT+CNMI=3,2,0,0^M 2007-07-09 14:44:34 [11692] [6] DEBUG: AT2[SMSC]: -- OK 2007-07-09 14:44:34 [11692] [6] INFO: AT2[SMSC]: AT SMSC successfully opened. 2007-07-09 14:44:53 [11692] [14] DEBUG: boxc_receiver: sms received 2007-07-09 14:44:53 [11692] [14] DEBUG: send_msg: sending msg to box: 127.0.0.1 2007-07-09 14:44:54 [11692] [6] DEBUG: AT2[SMSC]: TP-Validity-Period: 24.0hours 2007-07-09 14:44:54 [11692] [6] DEBUG: AT2[SMSC]: -- AT+CMGS=31^M 2007-07-09 14:45:00 [11692] [6] DEBUG: AT2[SMSC]: send command status: -1 -- David Duque
Re: Routing SMSes
Well I figured out a solution that I believe is full proof for 1 receiver and 1 transmitter. If you set transceiver to false on both of them and then set receiver-port = (not zero) and port = (zero) for the the reciever and then set the receiver-port = (zero) and port = (not zero) for the transmitter then kannel will connect with a bind_transmitter and bind_receiver for the appropriate smsc connection. note that the port directive acts like a transmitter-port although it is not labeled that. -Jon Jon David Koon wrote: I have a problem where I need to exclusively receive on one smsc and send on another. For sending I have tried to set the default-smsc and forced-smsc directives in the sendsms-user group. I am baffled concerning routing on the receiving side. I have tried putting 0 for the recieve-port for the one that only sends and this seems to work, but it is hard to confirm. I have included a truncated log as well as the kannel configuration. Kannel bearerbox version `1.4.1-mblox'. Build `Jun 6 2007 17:29:30', compiler `3.4.6 20060404 (Red Hat 3.4.6-8)'. System Linux, release 2.6.9-55.ELsmp, version #1 SMP Wed May 2 14:28:44 EDT 2007, machine i686. Hostname localhost, IP 127.0.0.1. Libxml version 2.6.16. Using OpenSSL 0.9.7a Feb 19 2003. Compiled with MySQL 4.1.20, using MySQL 4.1.20. Using native malloc. SMSC: MBlox (PSMS for receiving MT for sending) *Please do not explain the 42a error (Fixing this will fix that) Thanks in advance, Jon group = core admin-port = 13000 admin-password = f00bar smsbox-port = 13003 log-file = kannel-mblox.log access-log = kannel-mblox.access log-level = 0 #unified-prefix = 1,0 dlr-storage = mysql #dlr-storage = internal group = mysql-connection id = mydlr host = ** username = ** password = database = max-connections = 1 group = dlr-db id = mydlr table = DLR_Reports field-smsc = smsc field-timestamp = timestamp field-destination = destination field-source = source field-service = service field-url = url field-mask = mask field-status = status field-boxc-id = boxcid group = smsc smsc = smpp log-level = 0 #used for reference within kannel smsc-id = psms host = *** port = ** smsc-username = ** smsc-password = system-type = ** service-type = transceiver-mode = true #0x01 means: deliver_sm decimal, submit_sm_resp hex msg-id-type = 0x01 source-addr-ton = 3 group = smsc smsc = smpp log-level = 0 #used for reference within kannel smsc-id = mt host = ** port = smsc-username = *** smsc-password = * system-type = ** service-type = ** transceiver-mode = true receive-port = 0 #0x01 means: deliver_sm decimal, submit_sm_resp hex msg-id-type = 0x01 source-addr-ton = 3 group = smsbox bearerbox-host = 127.0.0.1 sendsms-port = 13013 #global-sender should be the short code global-sender = ** log-level = 0 group = sendsms-user username = * password = forced-smsc = mt default-smsc = mt group = sms-service keyword = keyword-regex = .* catch-all = yes max-messages = 0 get-url = http://*/inbound.php?timestamp=%tsender=%precipient=%Pbody=%a 2007-06-19 17:53:13 [21887] [0] INFO: Added logfile `kannel-mblox.log' with level `0'. 2007-06-19 17:53:13 [21887] [0] INFO: Started access logfile `kannel-mblox.access'. 2007-06-19 17:53:13 [21887] [0] INFO: HTTP: Opening server at port 13000. 2007-06-19 17:53:13 [21887] [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller) 2007-06-19 17:53:13 [21887] [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread) 2007-06-19 17:53:13 [21887] [0] DEBUG: Started thread 3 (gw/bb_http.c:httpadmin_run) 2007-06-19 17:53:13 [21887] [0] DEBUG: starting smsbox connection module 2007-06-19 17:53:13 [21887] [0] INFO: BOXC: 'smsbox-max-pending' not set, using default (100). 2007-06-19 17:53:13 [21887] [0] DEBUG: Started thread 4 (gw/bb_boxc.c:sms_to_smsboxes) 2007-06-19 17:53:13 [21887] [0] DEBUG: Started thread 5 (gw/bb_boxc.c:smsboxc_run) 2007-06-19 17:53:13 [21887] [0] INFO: Set SMS resend frequency to 60 seconds. 2007-06-19 17:53:13 [21887] [0] INFO: SMS resend retry set to unlimited. 2007-06-19 17:53:13 [21887] [0] INFO: DLR rerouting for smsc id psms disabled. 2007-06-19 17:53:13 [21887] [0] DEBUG: Started thread 6 (gw/smsc/smsc_smpp.c:io_thread) 2007-06-19 17:53:13 [21887] [0] INFO: DLR rerouting for smsc id mt disabled. 2007-06-19 17:53:13 [21887] [0] DEBUG: Started thread 7 (gw/smsc/smsc_smpp.c:io_thread) 2007-06-19 17:53:13 [21887] [0] DEBUG: Started thread 8 (gw/bb_smscconn.c:sms_router) 2007-06-19 17:53:13 [21887] [0] INFO: 2007-06
Routing SMSes
I have a problem where I need to exclusively receive on one smsc and send on another. For sending I have tried to set the default-smsc and forced-smsc directives in the sendsms-user group. I am baffled concerning routing on the receiving side. I have tried putting 0 for the recieve-port for the one that only sends and this seems to work, but it is hard to confirm. I have included a truncated log as well as the kannel configuration. Kannel bearerbox version `1.4.1-mblox'. Build `Jun 6 2007 17:29:30', compiler `3.4.6 20060404 (Red Hat 3.4.6-8)'. System Linux, release 2.6.9-55.ELsmp, version #1 SMP Wed May 2 14:28:44 EDT 2007, machine i686. Hostname localhost, IP 127.0.0.1. Libxml version 2.6.16. Using OpenSSL 0.9.7a Feb 19 2003. Compiled with MySQL 4.1.20, using MySQL 4.1.20. Using native malloc. SMSC: MBlox (PSMS for receiving MT for sending) *Please do not explain the 42a error (Fixing this will fix that) Thanks in advance, Jon group = core admin-port = 13000 admin-password = f00bar smsbox-port = 13003 log-file = kannel-mblox.log access-log = kannel-mblox.access log-level = 0 #unified-prefix = 1,0 dlr-storage = mysql #dlr-storage = internal group = mysql-connection id = mydlr host = ** username = ** password = database = max-connections = 1 group = dlr-db id = mydlr table = DLR_Reports field-smsc = smsc field-timestamp = timestamp field-destination = destination field-source = source field-service = service field-url = url field-mask = mask field-status = status field-boxc-id = boxcid group = smsc smsc = smpp log-level = 0 #used for reference within kannel smsc-id = psms host = *** port = ** smsc-username = ** smsc-password = system-type = ** service-type = transceiver-mode = true #0x01 means: deliver_sm decimal, submit_sm_resp hex msg-id-type = 0x01 source-addr-ton = 3 group = smsc smsc = smpp log-level = 0 #used for reference within kannel smsc-id = mt host = ** port = smsc-username = *** smsc-password = * system-type = ** service-type = ** transceiver-mode = true receive-port = 0 #0x01 means: deliver_sm decimal, submit_sm_resp hex msg-id-type = 0x01 source-addr-ton = 3 group = smsbox bearerbox-host = 127.0.0.1 sendsms-port = 13013 #global-sender should be the short code global-sender = ** log-level = 0 group = sendsms-user username = * password = forced-smsc = mt default-smsc = mt group = sms-service keyword = keyword-regex = .* catch-all = yes max-messages = 0 get-url = http://*/inbound.php?timestamp=%tsender=%precipient=%Pbody=%a 2007-06-19 17:53:13 [21887] [0] INFO: Added logfile `kannel-mblox.log' with level `0'. 2007-06-19 17:53:13 [21887] [0] INFO: Started access logfile `kannel-mblox.access'. 2007-06-19 17:53:13 [21887] [0] INFO: HTTP: Opening server at port 13000. 2007-06-19 17:53:13 [21887] [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller) 2007-06-19 17:53:13 [21887] [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread) 2007-06-19 17:53:13 [21887] [0] DEBUG: Started thread 3 (gw/bb_http.c:httpadmin_run) 2007-06-19 17:53:13 [21887] [0] DEBUG: starting smsbox connection module 2007-06-19 17:53:13 [21887] [0] INFO: BOXC: 'smsbox-max-pending' not set, using default (100). 2007-06-19 17:53:13 [21887] [0] DEBUG: Started thread 4 (gw/bb_boxc.c:sms_to_smsboxes) 2007-06-19 17:53:13 [21887] [0] DEBUG: Started thread 5 (gw/bb_boxc.c:smsboxc_run) 2007-06-19 17:53:13 [21887] [0] INFO: Set SMS resend frequency to 60 seconds. 2007-06-19 17:53:13 [21887] [0] INFO: SMS resend retry set to unlimited. 2007-06-19 17:53:13 [21887] [0] INFO: DLR rerouting for smsc id psms disabled. 2007-06-19 17:53:13 [21887] [0] DEBUG: Started thread 6 (gw/smsc/smsc_smpp.c:io_thread) 2007-06-19 17:53:13 [21887] [0] INFO: DLR rerouting for smsc id mt disabled. 2007-06-19 17:53:13 [21887] [0] DEBUG: Started thread 7 (gw/smsc/smsc_smpp.c:io_thread) 2007-06-19 17:53:13 [21887] [0] DEBUG: Started thread 8 (gw/bb_smscconn.c:sms_router) 2007-06-19 17:53:13 [21887] [0] INFO: 2007-06-19 17:53:13 [21887] [0] INFO: Kannel bearerbox II version 1.4.1-mblox starting 2007-06-19 17:53:13 [21887] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) maps to pid 21887. 2007-06-19 17:53:13 [21887] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) maps to pid 21887. 2007-06-19 17:53:13 [21887] [3] DEBUG: Thread 3 (gw/bb_http.c:httpadmin_run) maps to pid 21887. 2007-06-19 17:53:13 [21887] [4] DEBUG: Thread 4 (gw/bb_boxc.c:sms_to_smsboxes) maps to pid 21887. 2007-06-19 17:53:13 [21887] [5] DEBUG: Thread 5 (gw/bb_boxc.c:smsboxc_run) maps to pid 21887. 2007-06-19 17:53:13 [21887] [6] DEBUG: Thread 6 (gw/smsc/smsc_smpp.c:io_thread) maps to pid 21887. 2007-06-19 17:53:13 [21887] [0] INFO: MAIN: Start-up done, entering mainloop 2007-06-19 17:53:13 [21887] [7] DEBUG: Thread 7 (gw/smsc/smsc_smpp.c:io_thread) maps to
RE: Forcing SMSC doesn't work
Hello all I seem to have cracked this problem by making sure all the other SMSCs are listed under denied-smsc-id. For example, under SMSC-T1.A should be the following configuration parameters: group = smsc smsc = smpp smsc-id = SMSC-T1.A allowed-prefix = 027;6427;+6427;021;6421;+6421; preferred-prefix = 027;6427;+6427 denied-smsc-id = SMSC-T1.B;SMSC-T1.C;SMSC-T2.A -- had to include the SMSC(s) for the other telco here preferred-smsc-id = SMSC-T1.A Messages have been pushed out on the requested SMSC 100% of the time now. David -Original Message- From: David Ritchie [mailto:[EMAIL PROTECTED] Sent: Tuesday, 3 April 2007 1:48 p.m. To: users@kannel.org Subject: Forcing SMSC doesn't work Hi -- when doing an MT push, I want to force the SMSC I want messages to go out on, regardless of what the handset's prefix happens to be. However, it doesn't seem to work -- messages just go out on a random SMSC, even when I include a smsc= value in the MT push URL. We're recently suffering the overhead of the telcos rolling out number portability, and want to achieve the following: -- force a message to be pushed to a specific SMSC, provided the SMSC is specified in the push URL -- set a default SMSC (or group of SMSCs) for a prefix, in case the SMSC *isn't* specified -- and have confidence it'll all work. I am currently connected to 4 SMSCs, 3 providing connectivity to telco T1 (call these SMSC-T1.A through SMSC-T1.C), and one connected to telco T2 (SMSC-T2.A). Previously if I pushed out to a handset prefixed with 6427, it went out (randomly) through one of the 3 SMSCs connected to telco T1. The three smsc groups looked like this: group = smsc smsc = smpp smsc-id = SMSC-T1.A [ this changed between SMSCs ] allowed-prefix = 027;6427;+6427 denied-smsc-id = SMS-T1.B;SMS-T1.C [ obviously this was different between SMSCs ] preferred-smsc-id = smsc-t1a And the fourth SMSC (to the other telco) was along these lines: group = smsc smsc = smpp smsc-id = SMSC-T2.A allowed-prefix = 021;6421;+6421 (Judging from these prefixes, you can probably guess what country I am in.) With number portability, messages sent to handsets beginning with 6427 could potentially be forced to be sent out through telco T2; likewise handsets prefixed with 6421 might have to have messages pushed out through one of the SMSCs associated with telco T1. So I tried a test -- knowing a handset number which happened to have been ported from T1 to T2, but still keeping the 6427 prefix, I made some changes to the Kannel configuration, namely changing the allowed prefixes for all the SMSCs to allow all prefixes: allowed-prefix = 027;6427;+6427;021;6421;+6421; I also added a preferred-prefix value in case we tried to push out messages without specifying the SMSC preferred-prefix = 021;6421;+6421 The URL I requested included a value for smsc set to SMSC-T2.A (url-encoded), and assumed this would forced the message to go out through SMSC-T2.A; instead the message goes to *any* of the four SMSCs (since they've all got 6427 as a valid prefix). It appears to be a random choice between the four. Your advice is appreciated. David
Forcing SMSC doesn't work
Hi -- when doing an MT push, I want to force the SMSC I want messages to go out on, regardless of what the handset's prefix happens to be. However, it doesn't seem to work -- messages just go out on a random SMSC, even when I include a smsc= value in the MT push URL. We're recently suffering the overhead of the telcos rolling out number portability, and want to achieve the following: -- force a message to be pushed to a specific SMSC, provided the SMSC is specified in the push URL -- set a default SMSC (or group of SMSCs) for a prefix, in case the SMSC *isn't* specified -- and have confidence it'll all work. I am currently connected to 4 SMSCs, 3 providing connectivity to telco T1 (call these SMSC-T1.A through SMSC-T1.C), and one connected to telco T2 (SMSC-T2.A). Previously if I pushed out to a handset prefixed with 6427, it went out (randomly) through one of the 3 SMSCs connected to telco T1. The three smsc groups looked like this: group = smsc smsc = smpp smsc-id = SMSC-T1.A [ this changed between SMSCs ] allowed-prefix = 027;6427;+6427 denied-smsc-id = SMS-T1.B;SMS-T1.C [ obviously this was different between SMSCs ] preferred-smsc-id = smsc-t1a And the fourth SMSC (to the other telco) was along these lines: group = smsc smsc = smpp smsc-id = SMSC-T2.A allowed-prefix = 021;6421;+6421 (Judging from these prefixes, you can probably guess what country I am in.) With number portability, messages sent to handsets beginning with 6427 could potentially be forced to be sent out through telco T2; likewise handsets prefixed with 6421 might have to have messages pushed out through one of the SMSCs associated with telco T1. So I tried a test -- knowing a handset number which happened to have been ported from T1 to T2, but still keeping the 6427 prefix, I made some changes to the Kannel configuration, namely changing the allowed prefixes for all the SMSCs to allow all prefixes: allowed-prefix = 027;6427;+6427;021;6421;+6421; I also added a preferred-prefix value in case we tried to push out messages without specifying the SMSC preferred-prefix = 021;6421;+6421 The URL I requested included a value for smsc set to SMSC-T2.A (url-encoded), and assumed this would forced the message to go out through SMSC-T2.A; instead the message goes to *any* of the four SMSCs (since they've all got 6427 as a valid prefix). It appears to be a random choice between the four. Your advice is appreciated. David
Re: sms-resend-retry ignored
Hi, We have also been experiencing the same problem making us restart kannel multiple times a day, as the messages start getting delayed and generates extra traffic towards SMSC. It appears that the bug has already been detected but not fixed yet: http://bugs.kannel.org/view.php?id=352 Someone from the developers might be able to tell when is this problem expected to be fixed? Will really make life much more peaceful ;-) Thanks David - Original Message From: Alejandro Guerrieri [EMAIL PROTECTED] To: users@kannel.org users@kannel.org Sent: Sunday, February 4, 2007 1:13:36 AM Subject: Re: sms-resend-retry ignored Adam, As a rule of thumb, if having problems with older versions of Kannel, first step it's to upgrade to latest CVS, since many errors are already corrected on CVS. If after upgrading the problem persists, then inform the list since it may be a previously unseen or undetected bug. Regards, Alejandro On 2/3/07, Adam Trueman [EMAIL PROTECTED] wrote: Hi, We have been having problems with the Message Queue Full error with Kannel 1.4.0. Kannel used to send a lot of retry requests (about 10/sec) putting unwanted load on SMSC and causing delays in the handling of other messages. With the introduction of sms-resend-retry and sms-resend-freq in Kannel 1.4.1 the problem was expected to have been solved. So we have upgraded to Kannel 1.4.1 stable release. These parameters do control the problem for some time, but the problem appears a few hours after starting kannel. It appears that whenever Message Queue Full error occurs for a concatenated message split in parts, sms-resend-retry and sms-resend-freq dont apply, putting kannel again in the same state, generating a lot of retry requests badly affecting the performance. Is there a solution to the problem? Any help is greatly appreciated. Thanks Adam Be a PS3 game guru. Get your game face on with the latest PS3 news and previews at Yahoo! Games. -- Alejandro Guerrieri Magicom http://www.magicom-bcn.net/ LinkedIn: http://www.linkedin.com/in/aguerrieri Get your own web address. Have a HUGE year through Yahoo! Small Business. http://smallbusiness.yahoo.com/domains/?p=BESTDEAL
Masking originating addresses
Hello all -- has anybody had any success with using TPOA (or similar) to mask the originating address for MT SMS messages? Regards David
RE: Masking originating addresses
Yes, that's right -- setting the sender number. -Original Message- From: Iain Dooley [mailto:[EMAIL PROTECTED] Sent: Tuesday, 30 January 2007 10:32 a.m. To: David Ritchie Cc: users@kannel.org Subject: Re: Masking originating addresses hi david, On Tue, 30 Jan 2007, David Ritchie wrote: Hello all -- has anybody had any success with using TPOA (or similar) to mask the originating address for MT SMS messages? do you just mean setting the sender number? cheers iain
Fwd: Re: Mail2SMS with Kannel
Hi everyone, You could try using Exim as an SMTP. Its configuration files are almost like a simple scripting language and it can allow you to do tricky things like getting a mail who's recipient is a regular expression and send its content to a URL or external script or basicly anything you want, at SMTP time (or later :-D ) This would be a more direct and simple way of aproching the problem with out falling into mail boxes. (IMAP or POP). Hope it helps... Cheers, David El Martes, 7 de Noviembre de 2006 05:57, Alvaro Cornejo escribió: I´ve also been trying to dicover a way to have the system send an alert to an app in order to wakeup a process that will go get the message instead of having my e-mail client periodically look at the inbox for new messages. Still unable to doit Does anybody knows if this is possible? ideas? Regards Alvaro --- David Szanto Cori Genasys II Spain, S.A.U. Ventura de la Vega, 5 28014 - Madrid, SPAIN Phone + 34 91 364 91 00 Fax + 34 91 364 91 19 Email [EMAIL PROTECTED] www.genasys.com Este mensaje se dirige exclusivamente a su destinatario y puede contener información privilegiada o confidencial. Si no es Vd. el destinatario indicado, queda notificado de que la utilización, divulgación y/o copia sin autorización está prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. This message is intended exclusively for its addressee and may contain information that is confidential and protected by professional privilege. If you are not the intended recipient you are hereby notified that any dissemination, copy or disclosure of this communication is strictly prohibited by law. If this message has been received in error, please inmediately notify us via e-mail and delete it. --- -- --- David Szanto Cori Genasys II Spain, S.A.U. Ventura de la Vega, 5 28014 - Madrid, SPAIN Phone + 34 91 364 91 00 Fax + 34 91 364 91 19 Email [EMAIL PROTECTED] www.genasys.com Este mensaje se dirige exclusivamente a su destinatario y puede contener información privilegiada o confidencial. Si no es Vd. el destinatario indicado, queda notificado de que la utilización, divulgación y/o copia sin autorización está prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. This message is intended exclusively for its addressee and may contain information that is confidential and protected by professional privilege. If you are not the intended recipient you are hereby notified that any dissemination, copy or disclosure of this communication is strictly prohibited by law. If this message has been received in error, please inmediately notify us via e-mail and delete it.
SMSC returns Throttling error a bit too often
Hi everyone, I've got kannel v 1.4.0 installed on a debian (Sarge) platform comunicating with a SMSC through SMPP v3.4. Now, I've been getting the following error 7 times every 30 seconds or so: --- 2006-10-30 07:23:08 [5408] [7] WARNING: SMPP: PDU NULL terminated string has no NULL. 2006-10-30 07:23:08 [5408] [7] ERROR: SMPP[SMPP:smsc:9802/9802:PLAT_GPP:GENASYS]: SMSC returned error code 0x0058 (Throttling error) in response to submit_sm. --- I've got kannel configured with: thoughput=10 in order not to stampeed over the SMSC. But I don't really understand what the SMSC means by this error. On the othe hand I'm also getting: 2006-10-30 07:31:13 [5408] [7] ERROR: SMPP: Unknown TLV(0x000e,0x0001,01) for PDU type (deliver_sm) received! For what I've read, it could be solved by changing interface-version to 33. But the SMSC kannel is talking to works with SMPP3.4, so I'm a bit lost in that respect also. If anyone can help me solve this issues or at least help me understand what they mean, I'd appreciate it very much. Thanks, --- David Szanto Cori Genasys II Spain, S.A.U. Ventura de la Vega, 5 28014 - Madrid, SPAIN Phone + 34 91 364 91 00 Fax + 34 91 364 91 19 Email [EMAIL PROTECTED] www.genasys.com Este mensaje se dirige exclusivamente a su destinatario y puede contener información privilegiada o confidencial. Si no es Vd. el destinatario indicado, queda notificado de que la utilización, divulgación y/o copia sin autorización está prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. This message is intended exclusively for its addressee and may contain information that is confidential and protected by professional privilege. If you are not the intended recipient you are hereby notified that any dissemination, copy or disclosure of this communication is strictly prohibited by law. If this message has been received in error, please inmediately notify us via e-mail and delete it.
Re: SMSC returns Throttling error a bit too often
Hi Ben, Thanks for your prompt response!! According to my operator they used to have a limit of 10 SMSs/second, but they changed it to unlimited days ago. Actually that's why I set the throughput to 10. I'm quite lost with this. Besides I'm quite new to kannel. :-D Any other ideas? Thanks again!! David El Lunes, 30 de Octubre de 2006 14:48, escribió: David, It sounds to me like you are sending more messages per second that your operator is allowing. Ask them how many messages per second you are allowed to send, and then set the throughput accordingly. Regards Ben
Multiple Sessions to same SMSC - like Swisscom
Hi list, I've been sending through Swisscom's SMSC for quite a while now with one connection. To get more throughput they allow opening multiple sessions to the SMSC. In order to get this configured is it actually that simple as just copying the existing SMSC-connection settings in kannel.conf a couple of times? group = smsc smsc = emi2 smsc-id = swisscom host = ip port = port alt-host = ip alt-port = port smsc-username = xxx smsc-password = xxx flow-control = 1 throughput = 2 Will kannel then do load balancing between the open connections and still use the throughput setting for each connection? I know there are a few Swisscom users out there. How do you configure this? Thanx for help. David
Re: Multiple Sessions to same SMSC - like Swisscom
David E. Meier wrote: Hi list, I've been sending through Swisscom's SMSC for quite a while now with one connection. To get more throughput they allow opening multiple sessions to the SMSC. In order to get this configured is it actually that simple as just copying the existing SMSC-connection settings in kannel.conf a couple of times? group = smsc smsc = emi2 smsc-id = swisscom host = ip port = port alt-host = ip alt-port = port smsc-username = xxx smsc-password = xxx flow-control = 1 throughput = 2 Will kannel then do load balancing between the open connections and still use the throughput setting for each connection? yep. Stipe That was easy enough. Thanks Stipe.
DLR storage in MySQL
We're storing DLRs in MySQL successfully but the DLRs aren't being deleted which seems at odds with other people's experience (i.e. http://www.kannel.org/pipermail/users/2006-August/000294.html) but makes sense, since often we include a dlr-mask value (e.g. 12) which result in multiple DLRs being returned. Can anybody outline any successful DLR archiving or deletion strategies they've implemented, or perhaps outline how we can delete DLRs after a certain expiry date? Is there a danger (other than disk space issues) in letting the DLR table grow? Thanks! David R
Re: Bearebox Panic
That's worked! Thanks a lot --- David Sedeño El vie, 21-07-2006 a las 12:57 +0530, shehan escribió: Stop Kannel Delete your sms store files .After that start Kannel - Original Message - From: David Sedeño [EMAIL PROTECTED] To: users@kannel.org Sent: Friday, July 21, 2006 12:47 PM Subject: Bearebox Panic Hi, We have a system with kannel installed and it was working ok for a long time. After a hard reboot of the machine, kannel was sending some messages duplicates and some messages didn't send at all (we use Kannel with nagios). In the kannel.log file we see: 2006-07-21 08:21:49 [14915] [7] DEBUG: AT2[/dev/ttyS0]: send command status: 0 2006-07-21 08:21:49 [14915] [7] PANIC: gwlib/octstr.c:1423: octstr_append_char: Assertion `ch = UCHAR_MAX' failed. 2006-07-21 08:21:49 [14915] [7] PANIC: /usr/local/gw/sbin/bearerbox(gw_panic+0x175) [0x80ca1c6] 2006-07-21 08:21:49 [14915] [7] PANIC: /usr/local/gw/sbin/bearerbox(octstr_append_char+0x64) [0x80ce294] 2006-07-21 08:21:49 [14915] [7] PANIC: /usr/local/gw/sbin/bearerbox [0x8069d9a] 2006-07-21 08:21:49 [14915] [7] PANIC: /usr/local/gw/sbin/bearerbox [0x80682ef] 2006-07-21 08:21:49 [14915] [7] PANIC: /usr/local/gw/sbin/bearerbox [0x8067ecc] 2006-07-21 08:21:49 [14915] [7] PANIC: /usr/local/gw/sbin/bearerbox [0x8067dfc] 2006-07-21 08:21:49 [14915] [7] PANIC: /usr/local/gw/sbin/bearerbox [0x8065cd8] 2006-07-21 08:21:49 [14915] [7] PANIC: /usr/local/gw/sbin/bearerbox [0x80c095c] 2006-07-21 08:21:49 [14915] [7] PANIC: /lib/tls/libpthread.so.0 [0x400ac7f3] 2006-07-21 08:21:49 [14915] [7] PANIC: /lib/tls/libc.so.6(__clone+0x5a) [0x4037a62a] So bearebox now panic with some strange message... any idea? Thanks in advance -- David Sedeño Fernández Administración de Sistemas Spansurf S.L. [EMAIL PROTECTED] -- David Sedeño Fernández Administración de Sistemas Spansurf S.L. [EMAIL PROTECTED]
Multiple smsboxes (was RE: Prioritising MO/MT messages)
Thanks Stipe -- having multiple smsboxes sounds like it could be worth
following up on. Can anyone provide me with an example of how to configure
Kannel to use multiple smsboxes? I've tried doing this and, although Kannel
starts up successfully, I'm not entirely sure I've configured it correctly:
--8-
# SMSBOX SETUP
#
group = smsbox
smsbox-id = smsbox01
bearerbox-host = localhost
sendsms-port = 13013
log-file = /etc/kannel/logs/smsbox.log
log-level = 0
group = smsbox
smsbox-id = smsbox02
bearerbox-host = localhost
sendsms-port = 13013
log-file = /etc/kannel/logs/smsbox.log
log-level = 0
--8-
Note that if I change the log file names (e.g. smsbox01.log and
smsbox02.log), only smsbox02.log gets written to. This makes me think only
the second config is being read in and obeyed. Likewise, if the sendsms-port
values are different, only the second one is actually listened to. If I leave
off the second group configuration, then it doesn't start up at all.
Thanks
David R
-Original Message-
From: Stipe Tolj [mailto:[EMAIL PROTECTED]
Sent: Sunday, 16 July 2006 11:52 p.m.
To: David Ritchie
Cc: users@kannel.org
Subject: Re: Prioritising MO/MT messages
David Ritchie wrote:
Hello all. A scenario I'm experiencing at the moment involves a large
(several thousand) number of MT messages being pushed through Kannel,
during which it looks like MO messages (and the routing of them to the
appropriate URLs) gets relegated to a back seat; that is, a delay of
several minutes can take place between Kannel receiving the MO message,
and it getting around to pushing it to the correct URL:
smsbox.log:2006-07-15 12:52:13 [8487] [4] INFO: Starting to service
Test from HANDSET to SHORTCODE
smsbox.log:2006-07-15 12:53:08 [8487] [4] INFO: Starting to service
Test from HANDSET to SHORTCODE
smsbox.log:2006-07-15 12:55:10 [8487] [9] DEBUG: Parsing URL
`http://URL/?source=HANDSETdestination=SHORTCODEmessage=Test':
smsbox.log:2006-07-15 12:55:10 [8487] [9] DEBUG: Query:
source=HANDSETdestination=SHORTCODEmessage=Test
smsbox.log:2006-07-15 13:01:22 [8487] [9] DEBUG: Parsing URL
`http://URL/?source=HANDSETdestination=SHORTCODEmessage=Test':
smsbox.log:2006-07-15 13:01:22 [8487] [9] DEBUG: Query:
source=HANDSETdestination=SHORTCODEmessage=Test
As the log above displays, I sent in two messages (both saying Test)
to the shortcode, 1 minute apart. I was some minutes (between 3 and 8)
minutes before either of those messages were routed to the URL for that
shortcode. During this time we were successfully sending 100s of MT
messages (pushed using the HTTP interface) to handsets to the same SMSC
as I would have sent the above message from (i.e there's only one for
that carrier), but on a different shortcode and from a different server
(i.e. an entirely different service!).
ok, this seems to be the issue when you load the MT side heavily, and the HTTP
calling thread inside smsbox is set to pending, since resources (cpu time)
have to be shared.
I agree that a heavy loading of one side (MT) should not block fully the
other
side (MO).
We currently don't handle this extreme situation.
One solution is to use several smsbox'es connected to the same bearerbox. This
can balance out the load on the single smsbox.
It appears that restarting Kannel wipes the queue of messages, as any
sent between restarts are happily accepted but never routed. I have
started using the store file to see whether that makes a difference.
correct, smsbox's internal HTTP calling queue is _NOT_ persistant. Which means
if you restart the box while in heavy load, the waiting messages to be called
will get lost.
We need to addapt store file mechanism to smsbo too. Some guys have such
versions in private branches (namely Alex and me). But this needs to get merged
into the official tree.
It's also worth noting that the service with the MT messages also
requests DLRs (down to deliver to handset), so for every MT message
there are 1 - 2 MO messages with DLR information. These also apparently
get queued, in favour of the outgoing MT messages.
yep, MO and/or DLR HTTP calls are the same for smsbox.
Is there a way of prioritising MT messages to be a lower priority to MO
messages? Or even prioritising services one over another? Or perhaps
this is a file descriptor problem -- would increasing the number of FDs
allow more messages to be sent during a given time? Have you any other
ideas / experience?
no, there is no current way in setting priority policy. You'll need to use more
smsboxs connected to the bearerbox and let the system balance over them.
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Prioritising MO/MT messages
Hello all. A scenario I'm experiencing at the moment involves a large (several thousand) number of MT messages being pushed through Kannel, during which it looks like MO messages (and the routing of them to the appropriate URLs) gets relegated to a back seat; that is, a delay of several minutes can take place between Kannel receiving the MO message, and it getting around to pushing it to the correct URL: smsbox.log:2006-07-15 12:52:13 [8487] [4] INFO: Starting to service Test from HANDSET to SHORTCODE smsbox.log:2006-07-15 12:53:08 [8487] [4] INFO: Starting to service Test from HANDSET to SHORTCODE smsbox.log:2006-07-15 12:55:10 [8487] [9] DEBUG: Parsing URL `http://URL/?source=HANDSETdestination=SHORTCODEmessage=Test': smsbox.log:2006-07-15 12:55:10 [8487] [9] DEBUG: Query: source=HANDSETdestination=SHORTCODEmessage=Test smsbox.log:2006-07-15 13:01:22 [8487] [9] DEBUG: Parsing URL `http://URL/?source=HANDSETdestination=SHORTCODEmessage=Test': smsbox.log:2006-07-15 13:01:22 [8487] [9] DEBUG: Query: source=HANDSETdestination=SHORTCODEmessage=Test As the log above displays, I sent in two messages (both saying Test) to the shortcode, 1 minute apart. I was some minutes (between 3 and 8) minutes before either of those messages were routed to the URL for that shortcode. During this time we were successfully sending 100s of MT messages (pushed using the HTTP interface) to handsets to the same SMSC as I would have sent the above message from (i.e there's only one for that carrier), but on a different shortcode and from a different server (i.e. an entirely different service!). It appears that restarting Kannel wipes the queue of messages, as any sent between restarts are happily accepted but never routed. I have started using the store file to see whether that makes a difference. It's also worth noting that the service with the MT messages also requests DLRs (down to deliver to handset), so for every MT message there are 1 - 2 MO messages with DLR information. These also apparently get queued, in favour of the outgoing MT messages. Is there a way of prioritising MT messages to be a lower priority to MO messages? Or even prioritising services one over another? Or perhaps this is a file descriptor problem -- would increasing the number of FDs allow more messages to be sent during a given time? Have you any other ideas / experience? Regards David Ritchie
Using PHP scripts
I'm resigned using the SQLBox patch since I do not have a way to know the problem. Basically, what I need to do is Task#1: Mobile Terminated (MT) messages be automatically inserted in MySQL database. Task#2: Mobile Originated (MO) messages be automatically inserted in MySQL database. I've heard someone who used PHP to do insertion to database. What I plan to do is this (as from my understanding of kannel): Use PHP script to act as an intermediary between Kannel and MySQL. Question#1:In ~/gateway-1.4.0/contribs/php-admin folder, there is a script named sendsms.php. Is it the script that runs http interface sendsms interface? Assumption#1: ~/gateway-1.4.0/contribs/php-admin/sendsms.php is the script that the gateway runs when using the http interface in sending sms (Mobile Terminated, MT). Question#2:If Assumption#1 holds, I have an idea of inserting codes in it that connects to a MySQL database and would automatically insert MT messages. Is it feasible? Is my idea alright? Question#3But this will only solve Task#1. How about Task#2? How will I use PHP to "track" incoming messages? What part of Kannel can PHP communicate so as to "sense" Mobile Originated (MO) messages? Assumption#2:~/gateway-1.4.0/contribs/php-admin/sendsms.php is NOT the script or program that the gateway executes when using the http interface in sending SMS. It some other programs or gatewat mechanism which I am do not know. Question#4:If Assumption#2 holds, how will I use PHP to track outgoing (MT) messages? Question#3 is also repeated. How will I use PHP to "sense" incoming (MO) messages. Question#5:As from my understanding of Kannel, it is the bearerbox that sends and receives messages. Is there some way that PHP can communicate with the bearerbox? Question#6:Since I would be using PHP as an intermediary between Kannel and MySQL, will it be necessary to use "./configure --with-mysql" in compiling the gateway? Question#7:Will I still need to configure DLR group in conf? What role will DLR play in my setup, assuming it is correct? (I can hardly understand DLR until now, because I cannot compile well). Pardon for silly questions. Thanks for those who can bear with them and answer them. "Suffer the little children..." Mark 10:13 Julius New Yahoo! Messenger with Voice. Call regular phones from your PC and save big.
Re: Using PHP scripts
Why? Which Problem do you have with sqlbox? You can do it. But why? This is exactly what sqlbox does! I mailed the users lists two weeks ago. Actually, this problem is about two months already. I really want to use sqlbox, but since i've stuck with this problem, I opt to find some other way. http://www.mail-archive.com/users@kannel.org/msg07403.html http://www.mail-archive.com/users@kannel.org/msg07404.html Commonly MO messages are routed to some script (which are defined for you). If you decide to go without sqlbox then that script must to log the traffic. The question "how" means "can i have some sample code snippets that i can analyze and play with?" or "some pseudo-code if you don't have any code?". So, what variables will I use, how will I manipulate the script, how can I log to the traffic, etc, using PHP. In connecting MySQL to PHP, I use this script $connection = mysql_connect($dbhost, $dbuser, $dbpasswd); If I am to log into the traffic as you say, what particular functions will I need to use. Thanks if you have any idea. Yes, If you want to do it by a php script add some code in sensdms.php for insert into mysql databases and use it. In sending messages, we used cURL in our application in "packaging" the URL for http interface (http://localhost:port/cgi-bin/sendsms...), how will I invoke sendsms if we would use the sendsms.php? In which folder will I put sendsms.php after I edit it? Delivery Reports contains status of certain transactions. Such as submit_sm. These delivery reports comes from the SMSC and is routed by bearerbox to dlr-url. I may add DLR for insertion into the database aside from messages themselves. Julius Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates starting at 1/min.
Re: SQLBox part 1: make patch
By the way I use MYSQL 5.0.Julius David Bacolod [EMAIL PROTECTED] wrote: I think the problem is with the sqlbox patch. Or I'd rather say that the problem is with my dependencies (or system settings, I do not know what really it is) that do not fit with the patch and the patched executables. Please tell me the problem. cvs -d :pserver:[EMAIL PROTECTED]:/home/cvs co sqlbox #sqlbox from cvs cd sqlbox make patch #patching patching file Makefile.in patching file configure Hunk #1 succeeded at 81 (offset -4 lines). Hunk #2 FAILED at 4656. Hunk #3 FAILED at 4703. Hunk #4 succeeded at 5466 (offset -309 lines). 2 out of 4 hunks FAILED -- saving rejects to file configure.rej patching file configure.in Hunk #1 FAILED at 913. Hunk #2 succeeded at 1081 (offset -89 lines). 1 out of 2 hunks FAILED -- saving rejects to file configure.in.rej patching file gw/smsbox.c Hunk #1 succeeded at 3165 with fuzz 2 (offset -137 lines). Hunk #2 succeeded at 3346 (offset -2 lines). patching file gwlib/cfg.def Hunk #1 succeeded at 238 (offset -5 lines). Hunk #2 succeeded at 550 (offset -5 lines). make: *** [patch] Error 1 sqlbox.patch patches 5 files: Makefile.in, configure, configure.in, gw/smsbox.c, gwlib/cfg.def. Three were succesfully patched. I tried to inspect the two who got error, configure and configure.in, with the hope that I can see what could be the problem. But since I'm a baby in bash scripting, I was only able to understand few things using instinctive pattern matching. configure hunk 2: 4656 hunk 3: 4703 `$MYSQL_CONFIG --libs_r | sed -e "s/'//g"` was not able to replace `$MYSQL_CONFIG --libs_r` question number 1: Why do we need to replace ' with a null character? configure.in hunk 1: 913 `$MYSQL_CONFIG --libs_r | sed -e "s/\x27//g"` was not able to replace `$MYSQL_CONFIG --libs_r` `$MYSQL_CONFIG --libs | sed -e "s/\x27//g"` was not able to replace `$MYSQL_CONFIG --libs` question number 2: What character \x27 represent? question number 3: Can I know what values $MYSQL_CONFIG, $MYSQL_LIBS represent? I'm kind of confused and it's still not clear to me how it works. I do not have much time understanding all of these. I just want to know what am I lacking in my configurations, dependencies, libraries, system variables, compilations, database, etc, (whatever you may call it) ... if there is any. Please help (especially to Mr. Rene Kluwen). Thanks in advance. Get amazing travel prices for air and hotel in one click on Yahoo! FareChase
Re: SQLBox part 2: configure
By the way I use MYSQL 5.0Julius David Bacolod [EMAIL PROTECTED] wrote: I have installed MySQL. It seems that it has nothing to do with the database but with the patched configure. - Configuring for Kannel gateway version 1.4.0 ... Running system checks ... checking host system type... i686-pc-linux-gnu checking for gcc... (cached) gcc checking whether the C compiler (gcc -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -rdynamic) works... yes checking whether the C compiler (gcc -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -rdynamic) is a cross-compiler... no checking whether we are using GNU C... (cached) yes checking whether gcc accepts -g... (cached) yes checking for a BSD compatible install... (cached) /usr/bin/install -c checking for ranlib... (cached) ranlib checking for bison... (cached) bison -y checking for flex... (cached) flex checking for yywrap in -lfl... (cached) yes checking for convert... (cached) /usr/bin/convert checking for perl... (cached) /usr/bin/perl checking size of short... (cached) 2 checking size of int... (cached) 4 checking size of long... (cached) 4 checking size of long long... (cached) 8 checking for log in -lm... (cached) yes checking for accept in -lsocket... (cached) no checking for inet_ntoa in -lnsl... (cached) yes checking for inet_ntop in -lresolv... (cached) yes checking for inet_ntop in -lbind... (cached) yes checking for pthread_exit in -lpthread... (cached) yes checking for libiconv in -liconv... (cached) no checking how to run the C preprocessor... (cached) gcc -E checking for ANSI C header files... (cached) yes checking for sys/ioctl.h... (cached) yes checking for sys/time.h... (cached) yes checking for sys/types.h... (cached) yes checking for unistd.h... (cached) yes checking for sys/poll.h... (cached) yes checking for pthread.h... (cached) yes checking for getopt.h... (cached) yes checking for syslog.h... (cached) yes checking for iconv.h... (cached) yes checking for zlib.h... (cached) yes checking for execinfo.h... (cached) yes checking for stdlib.h... (cached) yes checking for sys/socket.h... (cached) yes checking for sys/sockio.h... (cached) no checking for net/if.h... (cached) yes checking for netinet/in.h... (cached) yes checking for gettimeofday... (cached) yes checking for select... (cached) yes checking for socket... (cached) yes checking for strdup... (cached) yes checking for getopt_long... (cached) yes checking for localtime_r... (cached) yes checking for gmtime_r... (cached) yes checking for backtrace... (cached) yes checking for srandom... (cached) yes checking for getopt... (cached) yes checking for gethostbyname_r... (cached) yes checking for which type of gethostbyname_r... (cached) 6 checking for socklen_t in sys/socket.h... (cached) yes checking for getopt in stdio.h... (cached) no checking for getopt in unistd.h... (cached) yes checking for regex.h... (cached) yes checking for regcomp... (cached) yes Checking for POSIX threads support ... checking for working pthreads... yes checking for pthread_spinlock support... yes checking for pthread_rwlock support... yes checking for sem_init in -lrt... (cached) yes checking for semaphore support... yes Checking for libxml2 support ... checking for xml2-config... (cached) /usr/bin/xml2-config checking libxml version... 2.6.19 Configuring for PCRE support ... checking whether to compile with PCRE support... disabled Configuring DocBook support ... checking for jade... (cached) jade checking for jadetex... (cached) jadetex checking for pdfjadetex... (cached) pdfjadetex checking for dvips... (cached) dvips checking for fig2dev... (cached) no checking for convert... (cached) /usr/bin/convert checking for /usr/lib/sgml/stylesheet/dsssl/docbook/nwalsh/html/docbook.dsl... (cached) no checking for /usr/lib/sgml/stylesheets/nwalsh-modular/html/docbook.dsl... (cached) no checking for /usr/share/sgml/docbook/dsssl-stylesheets-1.59/html/docbook.dsl... (cached) no checking for /usr/share/sgml/docbook/dsssl-stylesheets-1.77/html/docbook.dsl... (cached) no checking for /usr/share/sgml/docbook/dsssl-stylesheets/html/docbook.dsl... (cached) yes checking for /usr/lib/sgml/stylesheet/dsssl/docbook/nwalsh/print/docbook.dsl... (cached) no checking for /usr/lib/sgml/stylesheets/nwalsh-modular/print/docbook.dsl... (cached) no checking for /usr/share/sgml/docbook/dsssl-stylesheets-1.59/print/docbook.dsl... (cached) no checking for /usr/share/sgml/docbook/dsssl-stylesheets-1.77/print/docbook.dsl... (cached) no checking for /usr/share/sgml/docbook/dsssl-stylesheets/print/docbook.dsl... (cached) yes Not building documentation. Configuring parameters ... checking which malloc to use... native malloc enabling local time enabling cookies Configuring OpenSSL support ... checking whether to compile with SSL support... trying /usr/lib /usr/include/openssl checking for openssl... (cached) /usr/bin/openssl checking
SQLBox part 1: make patch
I think the problem is with the sqlbox patch. Or I'd rather say that the problem is with my dependencies (or system settings, I do not know what really it is) that do not fit with the patch and the patched executables. Please tell me the problem. cvs -d :pserver:[EMAIL PROTECTED]:/home/cvs co sqlbox #sqlbox from cvs cd sqlbox make patch #patching patching file Makefile.in patching file configure Hunk #1 succeeded at 81 (offset -4 lines). Hunk #2 FAILED at 4656. Hunk #3 FAILED at 4703. Hunk #4 succeeded at 5466 (offset -309 lines). 2 out of 4 hunks FAILED -- saving rejects to file configure.rej patching file configure.in Hunk #1 FAILED at 913. Hunk #2 succeeded at 1081 (offset -89 lines). 1 out of 2 hunks FAILED -- saving rejects to file configure.in.rej patching file gw/smsbox.c Hunk #1 succeeded at 3165 with fuzz 2 (offset -137 lines). Hunk #2 succeeded at 3346 (offset -2 lines). patching file gwlib/cfg.def Hunk #1 succeeded at 238 (offset -5 lines). Hunk #2 succeeded at 550 (offset -5 lines). make: *** [patch] Error 1 sqlbox.patch patches 5 files: Makefile.in, configure, configure.in, gw/smsbox.c, gwlib/cfg.def. Three were succesfully patched. I tried to inspect the two who got error, configure and configure.in, with the hope that I can see what could be the problem. But since I'm a baby in bash scripting, I was only able to understand few things using instinctive pattern matching. configure hunk 2: 4656 hunk 3: 4703 `$MYSQL_CONFIG --libs_r | sed -e "s/'//g"` was not able to replace `$MYSQL_CONFIG --libs_r` question number 1: Why do we need to replace ' with a null character? configure.in hunk 1: 913 `$MYSQL_CONFIG --libs_r | sed -e "s/\x27//g"` was not able to replace `$MYSQL_CONFIG --libs_r` `$MYSQL_CONFIG --libs | sed -e "s/\x27//g"` was not able to replace `$MYSQL_CONFIG --libs` question number 2: What character \x27 represent? question number 3: Can I know what values $MYSQL_CONFIG, $MYSQL_LIBS represent? I'm kind of confused and it's still not clear to me how it works. I do not have much time understanding all of these. I just want to know what am I lacking in my configurations, dependencies, libraries, system variables, compilations, database, etc, (whatever you may call it) ... if there is any. Please help (especially to Mr. Rene Kluwen). Thanks in advance. Love cheap thrills? Enjoy PC-to-Phone calls to 30+ countries for just 2¢/min with Yahoo! Messenger with Voice.
SQLBox part 2: configure
I have installed MySQL. It seems that it has nothing to do with the database but with the patched configure. - Configuring for Kannel gateway version 1.4.0 ... Running system checks ... checking host system type... i686-pc-linux-gnu checking for gcc... (cached) gcc checking whether the C compiler (gcc -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -rdynamic) works... yes checking whether the C compiler (gcc -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -rdynamic) is a cross-compiler... no checking whether we are using GNU C... (cached) yes checking whether gcc accepts -g... (cached) yes checking for a BSD compatible install... (cached) /usr/bin/install -c checking for ranlib... (cached) ranlib checking for bison... (cached) bison -y checking for flex... (cached) flex checking for yywrap in -lfl... (cached) yes checking for convert... (cached) /usr/bin/convert checking for perl... (cached) /usr/bin/perl checking size of short... (cached) 2 checking size of int... (cached) 4 checking size of long... (cached) 4 checking size of long long... (cached) 8 checking for log in -lm... (cached) yes checking for accept in -lsocket... (cached) no checking for inet_ntoa in -lnsl... (cached) yes checking for inet_ntop in -lresolv... (cached) yes checking for inet_ntop in -lbind... (cached) yes checking for pthread_exit in -lpthread... (cached) yes checking for libiconv in -liconv... (cached) no checking how to run the C preprocessor... (cached) gcc -E checking for ANSI C header files... (cached) yes checking for sys/ioctl.h... (cached) yes checking for sys/time.h... (cached) yes checking for sys/types.h... (cached) yes checking for unistd.h... (cached) yes checking for sys/poll.h... (cached) yes checking for pthread.h... (cached) yes checking for getopt.h... (cached) yes checking for syslog.h... (cached) yes checking for iconv.h... (cached) yes checking for zlib.h... (cached) yes checking for execinfo.h... (cached) yes checking for stdlib.h... (cached) yes checking for sys/socket.h... (cached) yes checking for sys/sockio.h... (cached) no checking for net/if.h... (cached) yes checking for netinet/in.h... (cached) yes checking for gettimeofday... (cached) yes checking for select... (cached) yes checking for socket... (cached) yes checking for strdup... (cached) yes checking for getopt_long... (cached) yes checking for localtime_r... (cached) yes checking for gmtime_r... (cached) yes checking for backtrace... (cached) yes checking for srandom... (cached) yes checking for getopt... (cached) yes checking for gethostbyname_r... (cached) yes checking for which type of gethostbyname_r... (cached) 6 checking for socklen_t in sys/socket.h... (cached) yes checking for getopt in stdio.h... (cached) no checking for getopt in unistd.h... (cached) yes checking for regex.h... (cached) yes checking for regcomp... (cached) yes Checking for POSIX threads support ... checking for working pthreads... yes checking for pthread_spinlock support... yes checking for pthread_rwlock support... yes checking for sem_init in -lrt... (cached) yes checking for semaphore support... yes Checking for libxml2 support ... checking for xml2-config... (cached) /usr/bin/xml2-config checking libxml version... 2.6.19 Configuring for PCRE support ... checking whether to compile with PCRE support... disabled Configuring DocBook support ... checking for jade... (cached) jade checking for jadetex... (cached) jadetex checking for pdfjadetex... (cached) pdfjadetex checking for dvips... (cached) dvips checking for fig2dev... (cached) no checking for convert... (cached) /usr/bin/convert checking for /usr/lib/sgml/stylesheet/dsssl/docbook/nwalsh/html/docbook.dsl... (cached) no checking for /usr/lib/sgml/stylesheets/nwalsh-modular/html/docbook.dsl... (cached) no checking for /usr/share/sgml/docbook/dsssl-stylesheets-1.59/html/docbook.dsl... (cached) no checking for /usr/share/sgml/docbook/dsssl-stylesheets-1.77/html/docbook.dsl... (cached) no checking for /usr/share/sgml/docbook/dsssl-stylesheets/html/docbook.dsl... (cached) yes checking for /usr/lib/sgml/stylesheet/dsssl/docbook/nwalsh/print/docbook.dsl... (cached) no checking for /usr/lib/sgml/stylesheets/nwalsh-modular/print/docbook.dsl... (cached) no checking for /usr/share/sgml/docbook/dsssl-stylesheets-1.59/print/docbook.dsl... (cached) no checking for /usr/share/sgml/docbook/dsssl-stylesheets-1.77/print/docbook.dsl... (cached) no checking for /usr/share/sgml/docbook/dsssl-stylesheets/print/docbook.dsl... (cached) yes Not building documentation. Configuring parameters ... checking which malloc to use... native malloc enabling local time enabling cookies Configuring OpenSSL support ... checking whether to compile with SSL support... trying /usr/lib /usr/include/openssl checking for openssl... (cached) /usr/bin/openssl checking for CRYPTO_lock in -lcrypto... (cached) yes checking for SSL_library_init in -lssl...
