smsbox
How many of you really use the feature of independent smsbox in different machine than the bearerbox? (or several smsboxes). Just thinking about the old 'thread smsbox' which was in old Kannel... -- &kalle marjola product concept manager NETikos finland (http://www.netikos.fi)
[BUG] smsbox
hi all, we are using Kannel 1.1.5 (no patches) and SMPP protocol and Red Hat Linux 7.1. in last 8 days, smsbox process disappear several times (not bearerbox). we check smsbox.log and found some panic message: 2001-10-01 01:08:35 [3] PANIC: mutex_unlock: Mutex failure!2001-10-08 01:51:21 [3] PANIC: mutex_unlock: Mutex failure!2001-10-08 02:28:58 [8] PANIC: mutex_unlock: Mutex failure!2001-10-08 17:57:50 [8] PANIC: mutex_unlock: Mutex failure! what can we do?any help would be appreciated. thanks & best regards ml
SMSBox PANIC
Hi! Ouch... 2001-12-12 06:58:19 [4] PANIC: gwlib/list.c:213: list_get: Assertion `pos < list->len' failed. ..I know I read how to fix this somewhere but I can´t seem to find it, I know this occurs when a empty SMS is recieved. I use the CVS version av kannel and the at module with a Siemens M20 GSM modem. If anyone out there has a quick fix for this I would be in debt! Best regards, Andreas Wallén _ Send and receive Hotmail on your mobile device: http://mobile.msn.com
smsbox bug
Hi, I found a bug in smsbox, related to empty text SMS handling (or a sms contaning only spaces). The problem arises when you send a space only text for example, and in the default sms-service get-url you use the %k token, for example group = sms-service keyword = default get-url = http://localhost/default.php?keyword=%k smsbox exits with a failed assertion 2002-01-10 16:56:13 [4] PANIC: gwlib/list.c:213: list_get: Assertion `pos < list->len' failed. I fixed the bug with some additional checking in the urltrans_get_pattern function. Could someone commit this patch to the cvs? Angel Fradejas. patch_urltrans.diff Description: Binary data
smsbox error
Hi. I got this error once every 2 days using one week ago cvs. bearer log does not show anything, smsbox sometimes cannot read from an fd so it closese connection. I use it under window 2000 as a service so it restarts, but what I would like to know is: 1) smsbox is trying to read someting from bearer because it received an sms or it periodically verifies connection? This because I'm afraid to loose some message, as when it restarts I can't see any sms received at that time. 2) If someone knows why it happens I'll be very glad, but I think it's very difficult to say. Thanks very much Here is smsbox log: 2002-04-06 22:04:05 [0] ERROR: Error reading from fd 18:2002-04-06 22:04:05 [0] ERROR: System error 104: Connection reset by peer2002-04-06 22:04:05 [0] ERROR: Error reading from fd 18:2002-04-06 22:04:05 [0] ERROR: System error 104: Connection reset by peer2002-04-06 22:04:05 [0] INFO: Error reading from bearerbox, disconnecting2002-04-06 22:04:05 [0] INFO: Received (and handled?) 124 requests in 142631 seconds (0.00 per second)2002-04-06 22:04:05 [0] INFO: Kannel smsbox terminating.2002-04-06 22:04:05 [6] DEBUG: Thread 6 (gw/heartbeat.c:heartbeat_thread) terminates.2002-04-06 22:04:05 [0] DEBUG: Waiting for 2 (gwlib/http.c:server_thread) to terminate2002-04-06 22:04:05 [3] DEBUG: HTTP: No clients with requests, quitting.2002-04-06 22:04:05 [3] DEBUG: Thread 3 (gw/smsbox.c:sendsms_thread) terminates.2002-04-06 22:04:05 [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) terminates.2002-04-06 22:04:05 [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) terminates.2002-04-06 22:04:05 [0] DEBUG: Waiting for 4 (gw/smsbox.c:obey_request_thread) to terminate2002-04-06 22:04:05 [4] DEBUG: Thread 4 (gw/smsbox.c:obey_request_thread) terminates.2002-04-06 22:04:05 [0] DEBUG: Waiting for 5 (gw/smsbox.c:url_result_thread) to terminate2002-04-06 22:04:05 [5] DEBUG: Thread 5 (gw/smsbox.c:url_result_thread) terminates.2002-04-06 22:04:05 [0] DEBUG: Waiting for 8 (gwlib/http.c:write_request_thread) to terminate2002-04-06 22:04:05 [8] DEBUG: Thread 8 (gwlib/http.c:write_request_thread) terminates.2002-04-06 22:04:05 [7] DEBUG: Thread 7 (gwlib/fdset.c:poller) terminates.2002-04-06 22:04:05 [0] DEBUG: Immutable octet strings: 218.2002-04-06 22:04:05 [0] DEBUG: Current allocations: 2 areas, 28 bytes2002-04-06 22:04:05 [0] DEBUG: Highest number of allocations: 1393 areas2002-04-06 22:04:05 [0] DEBUG: Highest memory usage: 73971 bytes2002-04-06 22:04:05 [0] DEBUG: Area 0xa016130, size 16, max_size 162002-04-06 22:04:05 [0] DEBUG: Allocated by octstr_create_from_data_real at gwlib/octstr.c:1712002-04-06 22:04:05 [0] DEBUG: Claimed by init_smsbox at gw/smsbox.c:20662002-04-06 22:04:05 [0] DEBUG: Contents of area (first 16 bytes):2002-04-06 22:04:05 [0] DEBUG: 68 61 01 0a 0b 00 00 00 0c 00 00 00 00 00 00 00 2002-04-06 22:04:05 [0] DEBUG: Area 0xa016168, size 12, max_size 122002-04-06 22:04:05 [0] DEBUG: Allocated by octstr_create_from_data_real at gwlib/octstr.c:1792002-04-06 22:04:05 [0] DEBUG: Contents of area (first 16 bytes):2002-04-06 22:04:05 [0] DEBUG: 30 31 32 33 34 35 36 37 38 39 20 00 2002-04-06 22:04:11 [0] INFO: Added logfile `smsbox.log' with level `0'. here it restarts.. P.S. (it uses even sim-buffering, don't know if this helps).
smsbox crashed
Hi All, smsbox crashed with the followong last entry in smsbox log file. I am using Kannel develepment release on Redhat 6.2 2002-06-04 16:30:27 [1] PANIC: gwlib/http.c:1535: port_put_request: Assertion `p!= NULL' failed. what should i DO. Also i want to purchase new hardware for machine. How much RAM would enough. I have decided to buy P3 & Intel server board (Scsi built-in) regards CIPHER _ Chat with friends online, try MSN Messenger: http://messenger.msn.com
smsbox terminating
Operating System Redhat: 7.3 Kannel Development Release Following is the smsbox last log 2002-06-25 15:16:13 [0] INFO: Connection closed by the bearerbox 2002-06-25 15:16:13 [0] INFO: Received (and handled?) 0 requests in 928709 secon ds (0.00 per second) 2002-06-25 15:16:13 [0] INFO: Kannel smsbox terminating. 2002-06-25 15:16:13 [1] WARNING: Destroying fdset with 996 active entries. CIPHER _ Send and receive Hotmail on your mobile device: http://mobile.msn.com
Re: smsbox
Kalle Marjola wrote: > > How many of you really use the feature of independent smsbox in different > machine than the bearerbox? (or several smsboxes). Just thinking about the > old 'thread smsbox' which was in old Kannel... we do, at least in some extend. Are you planing to incorporate smsbox as bearerbox thread?! If yes, we dislike this because of several reasons, one of them is the abilitiy to make config changes 'on-the-fly' to smsbox related groups, while bearerbox is still running. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: smsbox
On Fri, 9 Aug 2002, Stipe Tolj wrote: > > How many of you really use the feature of independent smsbox in different > > machine than the bearerbox? (or several smsboxes). Just thinking about the > > old 'thread smsbox' which was in old Kannel... > > we do, at least in some extend. Are you planing to incorporate smsbox > as bearerbox thread?! Well, several threads... (and this is just speculation. Last time the idea was torpedoed down because of load distribution reasons, after I have done some tests etc.) > If yes, we dislike this because of several reasons, one of them is the > abilitiy to make config changes 'on-the-fly' to smsbox related groups, > while bearerbox is still running. Do you have some nifty way to take smsbox down for that use, so that no messages are lost while they are being transfered between bearerbox and smsbox? (or open http connections) Dynamic configuration loading is doable (been there...), so what are those other reasons? (it is amazing how much it simplifies things to have smsbox in same process. And makes Kannel much faster) (for distribution, the possibility to run distinct smsbox could be left, too, alhought I do not see much use for that...) -- &kalle marjola product concept manager NETikos finland (http://www.netikos.fi)
Re: smsbox
--On Friday, August 9, 2002 2:06 PM +0300 Kalle Marjola <[EMAIL PROTECTED]> wrote: > On Fri, 9 Aug 2002, Stipe Tolj wrote: > >> > How many of you really use the feature of independent smsbox in >> > different machine than the bearerbox? (or several smsboxes). Just >> > thinking about the old 'thread smsbox' which was in old Kannel... >> >> we do, at least in some extend. Are you planing to incorporate smsbox >> as bearerbox thread?! > > Well, several threads... (and this is just speculation. Last time the > idea was torpedoed down because of load distribution reasons, after I > have done some tests etc.) > >> If yes, we dislike this because of several reasons, one of them is the >> abilitiy to make config changes 'on-the-fly' to smsbox related groups, >> while bearerbox is still running. > > Do you have some nifty way to take smsbox down for that use, so that no > messages are lost while they are being transfered between bearerbox and > smsbox? (or open http connections) (pure speculating here) A way could be to have the smsbox doing some gracefull restart by reading the configuration while the connections (sockets) stay connected. Then messages would get queue up. Unless the restart takes very long you would no loose messages. Not sure how the timing/speed is for this. > > Dynamic configuration loading is doable (been there...), so what > are those other reasons? > (it is amazing how much it simplifies things to have smsbox in same > process. And makes Kannel much faster) Just curious, but what about the wapbox?? Would that go faster too?? Yes, dynamic configuration is possible via various ways, SNMP, HTTP or even just some kind of gracefull restart that reads the configuration and setups the new environment. > > (for distribution, the possibility to run distinct smsbox could be left, > too, alhought I do not see much use for that...) Only when the load can go so sky high that a singl machine cannot keep up Harrie Internet Management Consulting mailto:[EMAIL PROTECTED]http ://www.mod-snmp.com/ --- Author of MOD-SNMP, enabling SNMP management to the Apache server.
Re: smsbox
On Fri, 9 Aug 2002, Harrie Hazewinkel wrote: > > Do you have some nifty way to take smsbox down for that use, so that no > > messages are lost while they are being transfered between bearerbox and > > smsbox? (or open http connections) > > (pure speculating here) A way could be to have the smsbox doing some > gracefull restart by reading the configuration while the connections > (sockets) stay connected. Then messages would get queue up. Unless > the restart takes very long you would no loose messages. Not sure how > the timing/speed is for this. Well my question was not about how it can be done but how they do do it right now :] > > (it is amazing how much it simplifies things to have smsbox in same > > process. And makes Kannel much faster) > > Just curious, but what about the wapbox?? Would that go faster too?? Possibly, but with wap, you do not need to say 'ack' to each message like with smsc > Yes, dynamic configuration is possible via various ways, SNMP, HTTP > or even just some kind of gracefull restart that reads the configuration > and setups the new environment. What I meant here is that dynamic configuration loading inside Kannel without stopping the smsc connections can be done (quite easily), thus effectually same thing as never stopping bearerbox but restarting smsbox > > (for distribution, the possibility to run distinct smsbox could be left, > > too, alhought I do not see much use for that...) > > Only when the load can go so sky high that a singl machine cannot keep up Naturally. But show me the single SMSC connection that can do that. And if you have several SMS center connections, you can have several bearerboxes, too (yes, I know that if you need to reoute things between them, this can still cause problems. That is just what I'm asking here, does anyone really USE that or is it just speculation that it CAN be done and used? Is it worth all the pain of message/ack/dlr transfer between smsbox and bearerbox?) Usually the speed of applications (oh, the java servlets) and SMSC connections is the only factor of the speed. The core Kannel can handle like 1000-2000 msg/s of fixed answers in normal modern tabletop, like 500-1000 HTTP based services (if the server is fast enough) SMS centers usually do something between 10-50/s, java servlets less. Correct me if I'm horribly wrong -- &kalle marjola product concept manager NETikos finland (http://www.netikos.fi)
Re: smsbox
> Do you have some nifty way to take smsbox down for that use, so that no > messages are lost while they are being transfered between bearerbox and > smsbox? (or open http connections) Hmm, doesn't smsbox go gracefully down, which means it waits until all transfered open SMS to bearerbox and HTTP requests are handled? This should be done I guess. > Dynamic configuration loading is doable (been there...), so what > are those other reasons? > (it is amazing how much it simplifies things to have smsbox in same > process. And makes Kannel much faster) reload of configuration on the fly?! Hmm, that's new to me, what signal are you using and for what box? Do you have any accurate benchmarks comparing the two processes? Maybe we can keep the code that clean that we can have a configure switch to incorporate the smsbox into bearerbox as thread?! I think this would be perfect for all of us. > (for distribution, the possibility to run distinct smsbox could be left, > too, alhought I do not see much use for that...) BTW, I didn't got the point how bearerbox knows to which smsbox it has to route inbound messages? Or is it passing a copy to all connected smsboxes?` Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: smsbox
On Fri, 9 Aug 2002, Stipe Tolj wrote: > reload of configuration on the fly?! Hmm, that's new to me, what > signal are you using and for what box? I mean that can be done, I have done some tests, and it used admin command. > Do you have any accurate benchmarks comparing the two processes? Guess... ;] But I could arrange.. > Maybe we can keep the code that clean that we can have a configure > switch to incorporate the smsbox into bearerbox as thread?! I think > this would be perfect for all of us. But that wouldn't help for intra-Kannel logistics, sould it? :] > BTW, I didn't got the point how bearerbox knows to which smsbox it has > to route inbound messages? Or is it passing a copy to all connected > smsboxes?` All smsboxes are equal, and thus bearerbox sends the message to random one, or the one with lowest load (cannot recall the exact algorithm, use the source...) -- &kalle marjola product concept manager NETikos finland (http://www.netikos.fi)
Re: smsbox
> Well my question was not about how it can be done but how they do do it > right now :] we do terminate and restart smsbox to re-read the updated configuration. > What I meant here is that dynamic configuration loading inside Kannel > without stopping the smsc connections can be done (quite easily), thus > effectually same thing as never stopping bearerbox but restarting smsbox which is what we do. But you still have to stop and restart bearerbox if you change smsc groups (adding or modifying) and hence those who are not affected have to go down and up too. > Naturally. But show me the single SMSC connection that can do that. And > if you have several SMS center connections, you can have several > bearerboxes, too (yes, I know that if you need to reoute things between > them, this can still cause problems. That is just what I'm asking here, > does anyone really USE that or is it just speculation that it CAN be done > and used? Is it worth all the pain of message/ack/dlr transfer between > smsbox and bearerbox?) we had a maximum of 50 outbound msg/sec. as limit to an SMPP link. None was faster yet. And bearerbox smiles about those on our machine. I'm also thinking of problems arrising from the planed modularization. As far as I see we will have modularization (which is already there) for SMSC modules and SMS services (i.e. sendsms, sendota, sendringtone, sendlogo etc). which means if someone links in a SMS service module (into smsbox scope) and smsbox is implemented as threads inside bearerbox and the new code dumps core, the whole systems blows up. Which is not the way we would like to see it. > Usually the speed of applications (oh, the java servlets) and SMSC > connections is the only factor of the speed. The core Kannel can handle > like 1000-2000 msg/s of fixed answers in normal modern tabletop, > like 500-1000 HTTP based services (if the server is fast enough) > SMS centers usually do something between 10-50/s, java servlets less. Yeah, some sms-services on our side have a bottleneck of 20 msg/sec. on a servlet side, which is really depressing. At least PHP does 60 msg/sec. for the same application, so we are pushing for performance here. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: smsbox
On Fri, 9 Aug 2002, Stipe Tolj wrote: > > Well my question was not about how it can be done but how they do do it > > right now :] > > we do terminate and restart smsbox to re-read the updated > configuration. Okay, just curious about possible open HTTP connections etc. so they do not cause problems? (like lost replies later on requeed with store system) > > What I meant here is that dynamic configuration loading inside Kannel > > without stopping the smsc connections can be done (quite easily), thus > > effectually same thing as never stopping bearerbox but restarting smsbox > > which is what we do. > > But you still have to stop and restart bearerbox if you change smsc > groups (adding or modifying) and hence those who are not affected have > to go down and up too. Yes, the same way it goes with the integrated one. > I'm also thinking of problems arrising from the planed modularization. > As far as I see we will have modularization (which is already there) > for SMSC modules and SMS services (i.e. sendsms, sendota, > sendringtone, sendlogo etc). which means if someone links in a SMS > service module (into smsbox scope) and smsbox is implemented as > threads inside bearerbox and the new code dumps core, the whole > systems blows up. Which is not the way we would like to see it. That is a valid point. If I start to speak ideally, I would get rid of all such services and instead implement just one simple http sender/receiver and all those services would be done by external filter/proxy/whatever. No idea to make basic _gateway_ an application server. But that is of course 'if I was the king of the world and would do redo everything' -talk. Things that aleady exist are hard to move away (like those prefix-suffix things in sms-service groups.. one in 200 uses them and thus they cannot be removed and left to be application problem..) -- &kalle marjola product concept manager NETikos finland (http://www.netikos.fi)
Re: smsbox
> > reload of configuration on the fly?! Hmm, that's new to me, what > > signal are you using and for what box? > > I mean that can be done, I have done some tests, and it used > admin command. AFAIK, you can not re-read the config file on the fly?!?! > > Do you have any accurate benchmarks comparing the two processes? > > Guess... ;] But I could arrange.. that would help, yes. > > Maybe we can keep the code that clean that we can have a configure > > switch to incorporate the smsbox into bearerbox as thread?! I think > > this would be perfect for all of us. > > But that wouldn't help for intra-Kannel logistics, sould it? :] if we astract the logical bearerbox <-> smsbox communication so the configure switch does select then the accurate implementation (function or tcp calling) this would work. Think of MySQL-4's new way to link the whole mysqld engine to your client executable, I think they use the same approach. > > BTW, I didn't got the point how bearerbox knows to which smsbox it has > > to route inbound messages? Or is it passing a copy to all connected > > smsboxes?` > > All smsboxes are equal, and thus bearerbox sends the message to random > one, or the one with lowest load (cannot recall the exact algorithm, > use the source...) Hmm, that's bad in some sence. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: smsbox
On Fri, 9 Aug 2002, Stipe Tolj wrote: > > > reload of configuration on the fly?! Hmm, that's new to me, what > > > signal are you using and for what box? > > > > I mean that can be done, I have done some tests, and it used > > admin command. > > AFAIK, you can not re-read the config file on the fly?!?! Not with CVS Kannel. With patched, yes. (but do not ask for it, at least yer, it is quite a mess and has all these toher thigns I'm talking about here, so it is not compatible) > if we astract the logical bearerbox <-> smsbox communication so the > configure switch does select then the accurate implementation > (function or tcp calling) this would work. Think of MySQL-4's new way > to link the whole mysqld engine to your client executable, I think > they use the same approach. Hm, that could work.. > > All smsboxes are equal, and thus bearerbox sends the message to random > > one, or the one with lowest load (cannot recall the exact algorithm, > > use the source...) > > Hmm, that's bad in some sence. Well, it has been like this for all these 3 or so years and no one has ever complained... (but I doubt that anyone has used more than one smsbox except for testing purposes :) PS: Now that I at last remember: please do not send me double copies each time you reply to my emails. I'm on devel list, too, no need to send personal reply (hm, am I starting to sound like Lars?) -- &kalle marjola product concept manager NETikos finland (http://www.netikos.fi)
Re: smsbox
> Okay, just curious about possible open HTTP connections etc. so they do > not cause problems? (like lost replies later on requeed with store system) don't know. > That is a valid point. If I start to speak ideally, I would get rid of all > such services and instead implement just one simple http sender/receiver > and all those services would be done by external filter/proxy/whatever. > No idea to make basic _gateway_ an application server. Hmmm, yes and no. Don't know to which side I tend :| Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
smsbox port problem
Hi, Quite strangely my Kannel (version 1.0.3) is not able to open the server socket at smsbox-port. No matter what port i'm mentioning there, the bearerbox simply isn't able to open the listening socket. When i check by "netstat" then it doesn't show that port in the existing listening sockets either. Could anyone give me any cue on this. This is quite urgent for me as our server is in the production environment. Regards, Venu -- Venugopal Panchamukhi Mobile# +358-(0)9-4110 1675 E-Mail: [EMAIL PROTECTED] [EMAIL PROTECTED]
bearerbox <-> smsbox communication ???
hello! does anybody have description of bearerbox and smsbox communication protocol. i want to write my own smsbox for a specific application, but i could'nt find the description. please help me if you can.. yours, Veljo
RE: [BUG] smsbox
> we are using Kannel 1.1.5 (no patches) and SMPP protocol and Red Hat Linux 7.1. > in last 8 days, smsbox process disappear several times (not bearerbox). > we check smsbox.log and found some panic message: > 2001-10-01 01:08:35 [3] PANIC: mutex_unlock: Mutex failure! > 2001-10-08 01:51:21 [3] PANIC: mutex_unlock: Mutex failure! > 2001-10-08 02:28:58 [8] PANIC: mutex_unlock: Mutex failure! > 2001-10-08 17:57:50 [8] PANIC: mutex_unlock: Mutex failure! > what can we do? Unfortunately, there's probably not much you can say about what happened without the log in debug mode. Is there anything particular you were trying to do around each time that the process stopped? (btw, it's better for everyone if you keep your postings in plain text rather than HTML) Ian
Re: [BUG] smsbox
hi Ian, thanks for your reply. i do log in debug mode. 2001-10-08 17:57:50 [8] DEBUG: HTTP: Sending request: 2001-10-08 17:57:50 [8] DEBUG: Octet string at 0x808eb18: 2001-10-08 17:57:50 [8] DEBUG: len: 76 2001-10-08 17:57:50 [8] DEBUG: size: 77 2001-10-08 17:57:50 [8] DEBUG: immutable: 0 2001-10-08 17:57:50 [8] DEBUG: data: 47 45 54 20 2f 3f 26 6d GET /?&m 2001-10-08 17:57:50 [8] DEBUG: data: 73 67 3d 64 26 66 72 6f sg=d&fro 2001-10-08 17:57:50 [8] DEBUG: data: 6d 3d 38 36 31 33 39 32 m=861392 2001-10-08 17:57:50 [8] DEBUG: data: 38 39 32 30 37 32 30 20 8920720 2001-10-08 17:57:50 [8] DEBUG: data: 20 48 54 54 50 2f 31 2eHTTP/1. 2001-10-08 17:57:50 [8] DEBUG: data: 31 0d 0a 48 6f 73 74 3a 1..Host: 2001-10-08 17:57:50 [8] DEBUG: data: 20 6c 6f 63 61 6c 68 6flocalho 2001-10-08 17:57:50 [8] DEBUG: data: 73 74 3a 33 36 30 30 30 st:26000 2001-10-08 17:57:50 [8] DEBUG: data: 0d 0a 0d 0a 2001-10-08 17:57:50 [8] DEBUG: Octet string dump ends. 2001-10-08 17:57:50 [8] PANIC: mutex_unlock: Mutex failure! 2001-10-08 17:57:50 [8] PANIC: System error 22: Invalid argument > > we are using Kannel 1.1.5 (no patches) and SMPP protocol and Red Hat Linux > 7.1. > > in last 8 days, smsbox process disappear several times (not bearerbox). > > we check smsbox.log and found some panic message: > > 2001-10-01 01:08:35 [3] PANIC: mutex_unlock: Mutex failure! > > 2001-10-08 01:51:21 [3] PANIC: mutex_unlock: Mutex failure! > > 2001-10-08 02:28:58 [8] PANIC: mutex_unlock: Mutex failure! > > 2001-10-08 17:57:50 [8] PANIC: mutex_unlock: Mutex failure! > > what can we do? > > Unfortunately, there's probably not much you can say about what happened > without the log in debug mode. Is there anything particular you were trying > to do around each time that the process stopped? > > (btw, it's better for everyone if you keep your postings in plain text > rather than HTML) > > Ian > >
RE: [BUG] smsbox
> 2001-10-08 17:57:50 [8] DEBUG: HTTP: Sending request: > 2001-10-08 17:57:50 [8] DEBUG: Octet string at 0x808eb18: > 2001-10-08 17:57:50 [8] DEBUG: len: 76 > 2001-10-08 17:57:50 [8] DEBUG: size: 77 > 2001-10-08 17:57:50 [8] DEBUG: immutable: 0 > 2001-10-08 17:57:50 [8] DEBUG: data: 47 45 54 20 2f 3f 26 6d GET /?&m > 2001-10-08 17:57:50 [8] DEBUG: data: 73 67 3d 64 26 66 72 6f sg=d&fro > 2001-10-08 17:57:50 [8] DEBUG: data: 6d 3d 38 36 31 33 39 32 m=861392 > 2001-10-08 17:57:50 [8] DEBUG: data: 38 39 32 30 37 32 30 20 8920720 > 2001-10-08 17:57:50 [8] DEBUG: data: 20 48 54 54 50 2f 31 2eHTTP/1. > 2001-10-08 17:57:50 [8] DEBUG: data: 31 0d 0a 48 6f 73 74 3a 1..Host: > 2001-10-08 17:57:50 [8] DEBUG: data: 20 6c 6f 63 61 6c 68 6flocalho > 2001-10-08 17:57:50 [8] DEBUG: data: 73 74 3a 33 36 30 30 30 st:26000 > 2001-10-08 17:57:50 [8] DEBUG: data: 0d 0a 0d 0a > 2001-10-08 17:57:50 [8] DEBUG: Octet string dump ends. > 2001-10-08 17:57:50 [8] PANIC: mutex_unlock: Mutex failure! > 2001-10-08 17:57:50 [8] PANIC: System error 22: Invalid argument I see the GET as /?&msg=d&from=8613928920720. For some reason the document name is missing, and there's an extra '&' (before msg). I'd expect something like /foo.php?msg=d&from=8613928920720. Does your sms-service 'url' or get-url' parameter match this? What happens if you point a browser at the page you're trying to reach? You could try telnet to localhost at port 26000 and issue the raw HTTP request yourself, and see what you get back.
Re: [BUG] smsbox
hi, Ian, does smsbox quit when she get error? we have got 100,000 msg in last 8 days and met the error only several times.so we think the url is correct.we think the key was :> > 2001-10-08 17:57:50 [8] PANIC: mutex_unlock: Mutex failure!> > 2001-10-08 17:57:50 [8] PANIC: System error 22: Invalid argument- Original Message - From: "Ian Daly" <[EMAIL PROTECTED]>To: <[EMAIL PROTECTED]>Sent: Monday, October 08, 2001 11:36 PMSubject: RE: [BUG] smsbox> > 2001-10-08 17:57:50 [8] DEBUG: HTTP: Sending request:> > 2001-10-08 17:57:50 [8] DEBUG: Octet string at 0x808eb18:> > 2001-10-08 17:57:50 [8] DEBUG: len: 76> > 2001-10-08 17:57:50 [8] DEBUG: size: 77> > 2001-10-08 17:57:50 [8] DEBUG: immutable: 0> > 2001-10-08 17:57:50 [8] DEBUG: data: 47 45 54 20 2f 3f 26 6d GET /?&m> > 2001-10-08 17:57:50 [8] DEBUG: data: 73 67 3d 64 26 66 72 6f sg=d&fro> > 2001-10-08 17:57:50 [8] DEBUG: data: 6d 3d 38 36 31 33 39 32 m=861392> > 2001-10-08 17:57:50 [8] DEBUG: data: 38 39 32 30 37 32 30 20 8920720> > 2001-10-08 17:57:50 [8] DEBUG: data: 20 48 54 54 50 2f 31 2e HTTP/1.> > 2001-10-08 17:57:50 [8] DEBUG: data: 31 0d 0a 48 6f 73 74 3a 1..Host:> > 2001-10-08 17:57:50 [8] DEBUG: data: 20 6c 6f 63 61 6c 68 6f localho> > 2001-10-08 17:57:50 [8] DEBUG: data: 73 74 3a 33 36 30 30 30 st:26000> > 2001-10-08 17:57:50 [8] DEBUG: data: 0d 0a 0d 0a > > 2001-10-08 17:57:50 [8] DEBUG: Octet string dump ends.> > 2001-10-08 17:57:50 [8] PANIC: mutex_unlock: Mutex failure!> > 2001-10-08 17:57:50 [8] PANIC: System error 22: Invalid argument> > I see the GET as /?&msg=d&from=8613928920720. For some reason the document> name is missing, and there's an extra '&' (before msg). I'd expect something> like /foo.php?msg=d&from=8613928920720. Does your sms-service 'url' or> get-url' parameter match this? What happens if you point a browser at the> page you're trying to reach? You could try telnet to localhost at port 26000> and issue the raw HTTP request yourself, and see what you get back.> >
RE: [BUG] smsbox
> does smsbox quit when she get error? Yes, all of the Kannel processes will quit after a PANIC level message. > we have got 100,000 msg in last 8 days and met the error only > several times. > so we think the url is correct. Okay, but the GET that the log shows still looks malformed to me, it looks suspicious. > > we think the key was : > > > > 2001-10-08 17:57:50 [8] PANIC: mutex_unlock: Mutex failure! > > > 2001-10-08 17:57:50 [8] PANIC: System error 22: Invalid argument In that case I appeal to the wisdom of the list :) Anyone got any ideas?
Re: [BUG] smsbox
hi, Ian, we found that compile kannel with default config , smsbox is stable. and compile kannel with config like this, smsbox is unstable. ./configure --with-defaults=speed --disable-docs --disable-assertions thanks & best regards ml > - Original Message - > From: "Ian Daly" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, October 09, 2001 5:09 PM > Subject: RE: [BUG] smsbox > > > > > does smsbox quit when she get error? > > > > Yes, all of the Kannel processes will quit after a PANIC level message. > > > > > we have got 100,000 msg in last 8 days and met the error only > > > several times. > > > so we think the url is correct. > > > > Okay, but the GET that the log shows still looks malformed to me, it looks > > suspicious. > > > > > > > > we think the key was : > > > > > > > > 2001-10-08 17:57:50 [8] PANIC: mutex_unlock: Mutex failure! > > > > > 2001-10-08 17:57:50 [8] PANIC: System error 22: Invalid argument > > > > In that case I appeal to the wisdom of the list :) Anyone got any ideas? > > > > >
smsbox eating CPU ?
I just noticed, the smsbox on my machine is eating up 'as much cpu as it can get'. Even though no requests are coming in (it still serves messages when it has to, though). Anyone have any hints on typical causes of this ? "my other kannels" don't do this... The machine in question serves both a gsm modem and an SMSC.
Re: SMSBox PANIC
> 2001-12-12 06:58:19 [4] PANIC: gwlib/list.c:213: list_get: Assertion `pos < > list->len' failed. > > ..I know I read how to fix this somewhere but I can´t seem to find it, > I know this occurs when a empty SMS is recieved. > > I use the CVS version av kannel and the at module with a Siemens M20 GSM > modem. If anyone out there has a quick fix for this I would be in debt! A look in the mailing list archive reveals that the problems seems _not_ to be fixed?! Anyone of the developers who did work on it? It does not seem to be a lacking default sms-service, is it? Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: SMSBox PANIC
No, I have default SMS-service. Does anyone know if switching to the at2 module helps? >From: Stipe Tolj <[EMAIL PROTECTED]> >To: Andreas Wall?n <[EMAIL PROTECTED]> >CC: [EMAIL PROTECTED] >Subject: Re: SMSBox PANIC >Date: Wed, 12 Dec 2001 15:55:25 +0100 > > > 2001-12-12 06:58:19 [4] PANIC: gwlib/list.c:213: list_get: Assertion >`pos < > > list->len' failed. > > > > ..I know I read how to fix this somewhere but I can´t seem to find it, > > I know this occurs when a empty SMS is recieved. > > > > I use the CVS version av kannel and the at module with a Siemens M20 GSM > > modem. If anyone out there has a quick fix for this I would be in debt! > >A look in the mailing list archive reveals that the problems seems >_not_ to be fixed?! Anyone of the developers who did work on it? > >It does not seem to be a lacking default sms-service, is it? > >Stipe > >[EMAIL PROTECTED] >--- >Wapme Systems AG > >Münsterstr. 248 >40470 Düsseldorf > >Tel: +49-211-74845-0 >Fax: +49-211-74845-299 > >E-Mail: [EMAIL PROTECTED] >Internet: http://www.wapme-systems.de >--- >wapme.net - wherever you are > _ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com
RE: SMSBox PANIC
There were reports that receiving an empty SMS could trigger such a bug. And no, if it's smsbox that is crashing than at2 won't help. Regards Jörg -Original Message- From: Andreas Wallén To: [EMAIL PROTECTED] Sent: 12/12/01 3:57 PM Subject: Re: SMSBox PANIC No, I have default SMS-service. Does anyone know if switching to the at2 module helps? >From: Stipe Tolj <[EMAIL PROTECTED]> >To: Andreas Wall?n <[EMAIL PROTECTED]> >CC: [EMAIL PROTECTED] >Subject: Re: SMSBox PANIC >Date: Wed, 12 Dec 2001 15:55:25 +0100 > > > 2001-12-12 06:58:19 [4] PANIC: gwlib/list.c:213: list_get: Assertion >`pos < > > list->len' failed. > > > > ..I know I read how to fix this somewhere but I can´t seem to find it, > > I know this occurs when a empty SMS is recieved. > > > > I use the CVS version av kannel and the at module with a Siemens M20 GSM > > modem. If anyone out there has a quick fix for this I would be in debt! > >A look in the mailing list archive reveals that the problems seems >_not_ to be fixed?! Anyone of the developers who did work on it? > >It does not seem to be a lacking default sms-service, is it? > >Stipe > >[EMAIL PROTECTED] >--- >Wapme Systems AG > >Münsterstr. 248 >40470 Düsseldorf > >Tel: +49-211-74845-0 >Fax: +49-211-74845-299 > >E-Mail: [EMAIL PROTECTED] >Internet: http://www.wapme-systems.de >--- >wapme.net - wherever you are > _ Join the world's largest e-mail service with MSN Hotmail. http://www.hotmail.com
RE: SMSBox PANIC
If receiving an empty message is really the cause, changing the configuration reply-emptymessage in smsbox group or omit-empty in the sms-service group might help. -steve ] -Original Message- ] From: [EMAIL PROTECTED] ] [mailto:[EMAIL PROTECTED]]On Behalf Of Jörg Pommnitz ] Sent: Wednesday, December 12, 2001 4:07 PM ] To: '[EMAIL PROTECTED] ' ] Subject: RE: SMSBox PANIC ] ] ] There were reports that receiving an empty SMS could trigger such a bug. ] And no, if it's smsbox that is crashing than at2 won't help. ] ] Regards ] Jörg ] ] -Original Message- ] From: Andreas Wallén ] To: [EMAIL PROTECTED] ] Sent: 12/12/01 3:57 PM ] Subject: Re: SMSBox PANIC ] ] ] No, I have default SMS-service. Does anyone know if switching to the at2 ] ] module helps? ] ] >From: Stipe Tolj <[EMAIL PROTECTED]> ] >To: Andreas Wall?n <[EMAIL PROTECTED]> ] >CC: [EMAIL PROTECTED] ] >Subject: Re: SMSBox PANIC ] >Date: Wed, 12 Dec 2001 15:55:25 +0100 ] > ] > > 2001-12-12 06:58:19 [4] PANIC: gwlib/list.c:213: list_get: Assertion ] ] >`pos < ] > > list->len' failed. ] > > ] > > ..I know I read how to fix this somewhere but I can´t seem to find ] it, ] > > I know this occurs when a empty SMS is recieved. ] > > ] > > I use the CVS version av kannel and the at module with a Siemens M20 ] GSM ] > > modem. If anyone out there has a quick fix for this I would be in ] debt! ] > ] >A look in the mailing list archive reveals that the problems seems ] >_not_ to be fixed?! Anyone of the developers who did work on it? ] > ] >It does not seem to be a lacking default sms-service, is it? ] > ] >Stipe ] > ] >[EMAIL PROTECTED] ] >--- ] >Wapme Systems AG ] > ] >Münsterstr. 248 ] >40470 Düsseldorf ] > ] >Tel: +49-211-74845-0 ] >Fax: +49-211-74845-299 ] > ] >E-Mail: [EMAIL PROTECTED] ] >Internet: http://www.wapme-systems.de ] >--- ] >wapme.net - wherever you are ] > ] ] ] ] ] _ ] Join the world's largest e-mail service with MSN Hotmail. ] http://www.hotmail.com ] ]
RE: SMSBox PANIC
omit-empty = true on the default sms-service seems to do the trick!! Many thanks!!! Best regards, Andreas Wallén >From: "Steve Rapaport" <[EMAIL PROTECTED]> >Reply-To: <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Subject: RE: SMSBox PANIC >Date: Wed, 12 Dec 2001 17:28:58 +0100 > >If receiving an empty message is really the cause, >changing the configuration >reply-emptymessage in smsbox group > >or >omit-empty in the sms-service group > >might help. > >-steve > >] -Original Message- >] From: [EMAIL PROTECTED] >] [mailto:[EMAIL PROTECTED]]On Behalf Of Jörg Pommnitz >] Sent: Wednesday, December 12, 2001 4:07 PM >] To: '[EMAIL PROTECTED] ' >] Subject: RE: SMSBox PANIC >] >] >] There were reports that receiving an empty SMS could trigger such a bug. >] And no, if it's smsbox that is crashing than at2 won't help. >] >] Regards >] Jörg >] >] -Original Message- >] From: Andreas Wallén >] To: [EMAIL PROTECTED] >] Sent: 12/12/01 3:57 PM >] Subject: Re: SMSBox PANIC >] >] >] No, I have default SMS-service. Does anyone know if switching to the at2 >] >] module helps? >] >] >From: Stipe Tolj <[EMAIL PROTECTED]> >] >To: Andreas Wall?n <[EMAIL PROTECTED]> >] >CC: [EMAIL PROTECTED] >] >Subject: Re: SMSBox PANIC >] >Date: Wed, 12 Dec 2001 15:55:25 +0100 >] > >] > > 2001-12-12 06:58:19 [4] PANIC: gwlib/list.c:213: list_get: Assertion >] >] >`pos < >] > > list->len' failed. >] > > >] > > ..I know I read how to fix this somewhere but I can´t seem to find >] it, >] > > I know this occurs when a empty SMS is recieved. >] > > >] > > I use the CVS version av kannel and the at module with a Siemens M20 >] GSM >] > > modem. If anyone out there has a quick fix for this I would be in >] debt! >] > >] >A look in the mailing list archive reveals that the problems seems >] >_not_ to be fixed?! Anyone of the developers who did work on it? >] > >] >It does not seem to be a lacking default sms-service, is it? >] > >] >Stipe >] > >] >[EMAIL PROTECTED] >] >--- >] >Wapme Systems AG >] > >] >Münsterstr. 248 >] >40470 Düsseldorf >] > >] >Tel: +49-211-74845-0 >] >Fax: +49-211-74845-299 >] > >] >E-Mail: [EMAIL PROTECTED] >] >Internet: http://www.wapme-systems.de >] >--- >] >wapme.net - wherever you are >] > >] >] >] >] >] _ >] Join the world's largest e-mail service with MSN Hotmail. >] http://www.hotmail.com >] >] > > _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx
Re: SMSBox PANIC
Oh no. There's still a bug in smsbox.c with msgdata == NULL ? g.. I'll take a look at it. - Original Message - From: "Andreas Wallén" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, December 12, 2001 6:45 PM Subject: RE: SMSBox PANIC > > > omit-empty = true on the default sms-service seems to do the trick!! Many > thanks!!! > > Best regards, > Andreas Wallén > > >From: "Steve Rapaport" <[EMAIL PROTECTED]> > >Reply-To: <[EMAIL PROTECTED]> > >To: <[EMAIL PROTECTED]> > >Subject: RE: SMSBox PANIC > >Date: Wed, 12 Dec 2001 17:28:58 +0100 > > > >If receiving an empty message is really the cause, > >changing the configuration > >reply-emptymessage in smsbox group > > > >or > >omit-empty in the sms-service group > > > >might help. > > > >-steve > > > >] -Original Message----- > >] From: [EMAIL PROTECTED] > >] [mailto:[EMAIL PROTECTED]]On Behalf Of Jörg Pommnitz > >] Sent: Wednesday, December 12, 2001 4:07 PM > >] To: '[EMAIL PROTECTED] ' > >] Subject: RE: SMSBox PANIC > >] > >] > >] There were reports that receiving an empty SMS could trigger such a bug. > >] And no, if it's smsbox that is crashing than at2 won't help. > >] > >] Regards > >] Jörg > >] > >] -Original Message- > >] From: Andreas Wallén > >] To: [EMAIL PROTECTED] > >] Sent: 12/12/01 3:57 PM > >] Subject: Re: SMSBox PANIC > >] > >] > >] No, I have default SMS-service. Does anyone know if switching to the at2 > >] > >] module helps? > >] > >] >From: Stipe Tolj <[EMAIL PROTECTED]> > >] >To: Andreas Wall?n <[EMAIL PROTECTED]> > >] >CC: [EMAIL PROTECTED] > >] >Subject: Re: SMSBox PANIC > >] >Date: Wed, 12 Dec 2001 15:55:25 +0100 > >] > > >] > > 2001-12-12 06:58:19 [4] PANIC: gwlib/list.c:213: list_get: Assertion > >] > >] >`pos < > >] > > list->len' failed. > >] > > > >] > > ..I know I read how to fix this somewhere but I can´t seem to find > >] it, > >] > > I know this occurs when a empty SMS is recieved. > >] > > > >] > > I use the CVS version av kannel and the at module with a Siemens M20 > >] GSM > >] > > modem. If anyone out there has a quick fix for this I would be in > >] debt! > >] > > >] >A look in the mailing list archive reveals that the problems seems > >] >_not_ to be fixed?! Anyone of the developers who did work on it? > >] > > >] >It does not seem to be a lacking default sms-service, is it? > >] > > >] >Stipe > >] > > >] >[EMAIL PROTECTED] > >] >--- > >] >Wapme Systems AG > >] > > >] >Münsterstr. 248 > >] >40470 Düsseldorf > >] > > >] >Tel: +49-211-74845-0 > >] >Fax: +49-211-74845-299 > >] > > >] >E-Mail: [EMAIL PROTECTED] > >] >Internet: http://www.wapme-systems.de > >] >--- > >] >wapme.net - wherever you are > >] > > >] > >] > >] > >] > >] _ > >] Join the world's largest e-mail service with MSN Hotmail. > >] http://www.hotmail.com > >] > >] > > > > > > > > > _ > MSN Photos is the easiest way to share and print your photos: > http://photos.msn.com/support/worldwide.aspx > > >
Re: SMSBox PANIC
> Oh no. There's still a bug in smsbox.c with msgdata == NULL ? > > g.. I'll take a look at it. Great, thanks Bruno! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: smsbox bug
Angel Fradejas wrote: > > Hi, > > I found a bug in smsbox, related to empty text SMS handling (or a sms > contaning only spaces). The problem arises when you send a space only text > for example, and in the default sms-service get-url you use the %k token, > for example > >group = sms-service >keyword = default >get-url = http://localhost/default.php?keyword=%k > > smsbox exits with a failed assertion > >2002-01-10 16:56:13 [4] PANIC: gwlib/list.c:213: list_get: Assertion `pos > < list->len' failed. > > I fixed the bug with some additional checking in the urltrans_get_pattern > function. > > Could someone commit this patch to the cvs? The patch has been just applied to cvs. Thanks a lot for the submission. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: smsbox error
Hi Oded,
I'm using your patch (sim-buffering), and I really
think that's part of the problem.
Suddendly Dr. Watson raises an error on
bearerbox,
even if in the log you can's see anything, then
smsbox write that log.
I would really like to know If I louse some
sms.
By the way I can tell you that before sim-buffering
I never had Dr. Watson,
but I can't tell you if that was the cause or
not.
Cheers
Andrea
P.S. I got it under windows 2000 advanced
server
- Original Message -
From:
Oded Arbel
To: Andrea Viscovich
Sent: Monday, April 08, 2002 7:09
PM
Subject: RE: smsbox error
It
is very wierd - my bet is that this is a windows problem. I have encountered
sporadicly closing sockets in the past, but only on NT4.
OTOH
- I'm a linux freak, so you need to take everything I say about windows with a
grain of salt ;-)
--Oded Arbelm-Wise Inc.[EMAIL PROTECTED]
"I
am afraid that as death becomes less certain, taxes will get
worse." -- Mary Smith
-Original Message-From: Andrea Viscovich
[mailto:[EMAIL PROTECTED]]Sent: Monday, April 08, 2002 12:22
PMTo: [EMAIL PROTECTED]Subject: smsbox
error
Hi.
I got this error once every 2 days using one week ago
cvs.
bearer log does not show anything,
smsbox sometimes cannot read from an fd so it closese
connection.
I use it under window 2000 as a service so it restarts,
but
what I would like to know is:
1) smsbox is trying to read someting from bearer because
it received an sms
or it periodically verifies connection? This
because I'm afraid to loose some
message, as when it restarts I can't see any
sms received at that time.
2) If someone knows why it happens I'll be very glad, but
I think it's very difficult to say.
Thanks very
much
Here is
smsbox log:
2002-04-06 22:04:05 [0] ERROR: Error reading from fd
18:2002-04-06 22:04:05 [0] ERROR: System error 104: Connection reset by
peer2002-04-06 22:04:05 [0] ERROR: Error reading from fd
18:2002-04-06 22:04:05 [0] ERROR: System error 104: Connection reset by
peer2002-04-06 22:04:05 [0] INFO: Error reading from bearerbox,
disconnecting2002-04-06 22:04:05 [0] INFO: Received (and handled?) 124
requests in 142631 seconds (0.00 per second)2002-04-06 22:04:05 [0]
INFO: Kannel smsbox terminating.2002-04-06 22:04:05 [6] DEBUG: Thread 6
(gw/heartbeat.c:heartbeat_thread) terminates.2002-04-06 22:04:05 [0]
DEBUG: Waiting for 2 (gwlib/http.c:server_thread) to terminate2002-04-06
22:04:05 [3] DEBUG: HTTP: No clients with requests, quitting.2002-04-06
22:04:05 [3] DEBUG: Thread 3 (gw/smsbox.c:sendsms_thread)
terminates.2002-04-06 22:04:05 [2] DEBUG: Thread 2
(gwlib/http.c:server_thread) terminates.2002-04-06 22:04:05 [1] DEBUG:
Thread 1 (gwlib/fdset.c:poller) terminates.2002-04-06 22:04:05 [0]
DEBUG: Waiting for 4 (gw/smsbox.c:obey_request_thread) to
terminate2002-04-06 22:04:05 [4] DEBUG: Thread 4
(gw/smsbox.c:obey_request_thread) terminates.2002-04-06 22:04:05 [0]
DEBUG: Waiting for 5 (gw/smsbox.c:url_result_thread) to
terminate2002-04-06 22:04:05 [5] DEBUG: Thread 5
(gw/smsbox.c:url_result_thread) terminates.2002-04-06 22:04:05 [0]
DEBUG: Waiting for 8 (gwlib/http.c:write_request_thread) to
terminate2002-04-06 22:04:05 [8] DEBUG: Thread 8
(gwlib/http.c:write_request_thread) terminates.2002-04-06 22:04:05 [7]
DEBUG: Thread 7 (gwlib/fdset.c:poller) terminates.2002-04-06 22:04:05
[0] DEBUG: Immutable octet strings: 218.2002-04-06 22:04:05 [0] DEBUG:
Current allocations: 2 areas, 28 bytes2002-04-06 22:04:05 [0] DEBUG:
Highest number of allocations: 1393 areas2002-04-06 22:04:05 [0] DEBUG:
Highest memory usage: 73971 bytes2002-04-06 22:04:05 [0] DEBUG: Area
0xa016130, size 16, max_size 162002-04-06 22:04:05 [0] DEBUG: Allocated
by octstr_create_from_data_real at gwlib/octstr.c:1712002-04-06 22:04:05
[0] DEBUG: Claimed by init_smsbox at gw/smsbox.c:20662002-04-06 22:04:05
[0] DEBUG: Contents of area (first 16 bytes):2002-04-06 22:04:05 [0]
DEBUG: 68 61 01 0a 0b 00 00 00 0c 00 00 00 00 00 00 00
2002-04-06 22:04:05 [0] DEBUG: Area 0xa016168, size 12, max_size
122002-04-06 22:04:05 [0] DEBUG: Allocated by
octstr_create_from_data_real at gwlib/octstr.c:1792002-04-06 22:04:05
[0] DEBUG: Contents of area (first 16 bytes):2002-04-06 22:04:05 [0]
DEBUG: 30 31 32 33 34 35 36 37 38 39 20 00 2002-04-06
22:04:11 [0] INFO: Added logfile `smsbox.log' with level `0'.
here it
restarts..
P.S. (it uses even sim-buffering, don't know
if this helps).
Re: smsbox crashed
Cipher Strength kirjoittaa tiistaina, 4. kesäkuuta 2002, kello 10:31: > > smsbox crashed with the followong last entry in smsbox log file. I am > using Kannel develepment release on Redhat 6.2 > > 2002-06-04 16:30:27 [1] PANIC: gwlib/http.c:1535: port_put_request: > Assertion `p!= NULL' failed. > > what should i DO. Sending smsbox and bearerbox logs is useful ;) In addition, more data about the message causing the crash (there are unhandled NULL pointer here, and one must know first, is the assertion itself necessary) > Also i want to purchase new hardware for machine. How much RAM would > enough. I have decided to buy P3 & Intel server board (Scsi built-in) 400 - 500 M would certainly be enough. Kannel should not let long queues happen in the first place. Aarno
Re: smsbox terminating
HI, Which version of Kannel is this?? 1.1.6, 1.2.0rc1 or CVS?? --On Wednesday, July 3, 2002 8:33 PM +0500 Cipher Strength <[EMAIL PROTECTED]> wrote: > > > Operating System Redhat: 7.3 > Kannel Development Release > > Following is the smsbox last log > > 2002-06-25 15:16:13 [0] INFO: Connection closed by the bearerbox > 2002-06-25 15:16:13 [0] INFO: Received (and handled?) 0 requests in > 928709 secon ds (0.00 per second) > 2002-06-25 15:16:13 [0] INFO: Kannel smsbox terminating. > 2002-06-25 15:16:13 [1] WARNING: Destroying fdset with 996 active entries. > > > CIPHER > > > _ > Send and receive Hotmail on your mobile device: http://mobile.msn.com > > > Harrie Internet Management Consulting mailto:[EMAIL PROTECTED]http ://www.mod-snmp.com/
Re: smsbox terminating
> Following is the smsbox last log > > 2002-06-25 15:16:13 [0] INFO: Connection closed by the bearerbox > 2002-06-25 15:16:13 [0] INFO: Received (and handled?) 0 requests in 928709 > secon > ds (0.00 per second) > 2002-06-25 15:16:13 [0] INFO: Kannel smsbox terminating. > 2002-06-25 15:16:13 [1] WARNING: Destroying fdset with 996 active entries. what's wrong with that? Some process has to be send a SIGTERM signal to smsbox to make this happen. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: smsbox terminating
--On Wednesday, July 3, 2002 6:30 PM +0200 Stipe Tolj <[EMAIL PROTECTED]> wrote: >> Following is the smsbox last log >> >> 2002-06-25 15:16:13 [0] INFO: Connection closed by the bearerbox >> 2002-06-25 15:16:13 [0] INFO: Received (and handled?) 0 requests in >> 928709 secon >> ds (0.00 per second) >> 2002-06-25 15:16:13 [0] INFO: Kannel smsbox terminating. >> 2002-06-25 15:16:13 [1] WARNING: Destroying fdset with 996 active >> entries. > > what's wrong with that? > > Some process has to be send a SIGTERM signal to smsbox to make this > happen. Are you sure?? If I sent the process a SIGTERM (kill -TERM) the smsbox process just gives back 'terminated' no additional info of shutting down. If I give it a SIGINT it nicely says it recieved it and terminates with info what it is closing all. Harrie Internet Management Consulting mailto:[EMAIL PROTECTED]http ://www.mod-snmp.com/
Re: smsbox terminating
> If I sent the process a SIGTERM (kill -TERM) the smsbox process just > gives back 'terminated' no additional info of shutting down. > > If I give it a SIGINT it nicely says it recieved it and > terminates with info what it is closing all. Harrie, you're right of course. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: smsbox terminating
--On Wednesday, July 3, 2002 8:05 PM +0200 Stipe Tolj <[EMAIL PROTECTED]> wrote: >> If I sent the process a SIGTERM (kill -TERM) the smsbox process just >> gives back 'terminated' no additional info of shutting down. >> >> If I give it a SIGINT it nicely says it recieved it and >> terminates with info what it is closing all. > > Harrie, you're right of course. Of course?? Would this mean I am perfect and thus nobody?? ;-)) Serious, for the problem on Linux I am not much of a help. I don't have such a system, but just noticed it while playing yesterday on FreeBSD. Harrie Internet Management Consulting mailto:[EMAIL PROTECTED]http ://www.mod-snmp.com/
Re: smsbox terminating
Harrie Hazewinkel kirjoittaa torstaina, 4. heinäkuuta 2002, kello 01:45: I would be nice to see bearerbox log. After all, there was a message "bearerbox closing the connection". Certainly wapbox goes down in this case. > > --On Wednesday, July 3, 2002 8:05 PM +0200 Stipe Tolj > <[EMAIL PROTECTED]> wrote: > >>> If I sent the process a SIGTERM (kill -TERM) the smsbox process just >>> gives back 'terminated' no additional info of shutting down. >>> >>> If I give it a SIGINT it nicely says it recieved it and >>> terminates with info what it is closing all. >> >> Harrie, you're right of course. > > Of course?? Would this mean I am perfect and thus nobody?? ;-)) > > Serious, for the problem on Linux I am not much of a help. > I don't have such a system, but just noticed it while > playing yesterday on FreeBSD. > > > > Harrie > > Internet Management Consulting > mailto:[EMAIL PROTECTED]http ://www.mod-snmp.com/ >
Re: smsbox terminating
Harrie Hazewinkel wrote: > > --On Wednesday, July 3, 2002 8:05 PM +0200 Stipe Tolj > <[EMAIL PROTECTED]> wrote: > > >> If I sent the process a SIGTERM (kill -TERM) the smsbox process just > >> gives back 'terminated' no additional info of shutting down. > >> > >> If I give it a SIGINT it nicely says it recieved it and > >> terminates with info what it is closing all. > > > > Harrie, you're right of course. > > Of course?? Would this mean I am perfect and thus nobody?? ;-)) > > Serious, for the problem on Linux I am not much of a help. > I don't have such a system, but just noticed it while > playing yesterday on FreeBSD. :))) No, but I confused the answer with the different signals, so in *this case* you are perfectly right :)) Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: smsbox terminating
Hi All, Sorry for the message sent on mailing list. Actually i was in hurry at that time and send without checking much but the smsbox crashed and there was no logging for smsbox from long ago. Thanks all of YOU >Harrie Hazewinkel wrote: > > > > --On Wednesday, July 3, 2002 8:05 PM +0200 Stipe Tolj > > <[EMAIL PROTECTED]> wrote: > > > > >> If I sent the process a SIGTERM (kill -TERM) the smsbox process just > > >> gives back 'terminated' no additional info of shutting down. > > >> > > >> If I give it a SIGINT it nicely says it recieved it and > > >> terminates with info what it is closing all. > > > > > > Harrie, you're right of course. > > > > Of course?? Would this mean I am perfect and thus nobody?? ;-)) > > > > Serious, for the problem on Linux I am not much of a help. > > I don't have such a system, but just noticed it while > > playing yesterday on FreeBSD. > >:))) > >No, but I confused the answer with the different signals, so in *this >case* you are perfectly right :)) > >Stipe > >[EMAIL PROTECTED] >--- >Wapme Systems AG > >Vogelsanger Weg 80 >40470 Düsseldorf > >Tel: +49-211-74845-0 >Fax: +49-211-74845-299 > >E-Mail: [EMAIL PROTECTED] >Internet: http://www.wapme-systems.de >--- >wapme.net - wherever you are CIPHER _ Send and receive Hotmail on your mobile device: http://mobile.msn.com
Re: smsbox terminating
Harrie Hazewinkel wrote: > > > --On Wednesday, July 3, 2002 8:05 PM +0200 Stipe Tolj > <[EMAIL PROTECTED]> wrote: > >>> If I sent the process a SIGTERM (kill -TERM) the smsbox process just >>> gives back 'terminated' no additional info of shutting down. >>> >>> If I give it a SIGINT it nicely says it recieved it and >>> terminates with info what it is closing all. >> >> >> Harrie, you're right of course. > > > Of course?? Would this mean I am perfect and thus nobody?? ;-)) > > Serious, for the problem on Linux I am not much of a help. > I don't have such a system, but just noticed it while > playing yesterday on FreeBSD. > > > > Harrie > > Internet Management Consulting > mailto:[EMAIL PROTECTED]http ://www.mod-snmp.com/ > > It looks to me as if bearerbox closed the connection to the smsbox, after which smsbox immidietly terminates (as it should - this is a feature). you have to ask yourself, why did the bearerbox close the connection to the smsbox ? most likely it is because the bearerbox was closing down for some reason - check the bearerbox logs. -- Oded Arbel m-Wise mobile solutions
[BUG] smsbox memleak
Hi All There is a new memory leak in the cvs, in smsbox. For each dlr ack.. and probabally sms-service 2002-11-18 15:59:11 [0] DEBUG: Allocated by octstr_create_from_data_real at gwlib/octstr.c:185 2002-11-18 15:59:11 [0] DEBUG: Claimed by parse_url at gwlib/http.c:1156 2002-11-18 15:59:11 [0] DEBUG: Contents of area (first 16 bytes): 2002-11-18 15:59:11 [0] DEBUG: 48 5a 0c 09 16 00 00 00 17 00 00 00 00 00 00 00 2002-11-18 15:59:11 [0] DEBUG: Area 0x90c2960, size 16, max_size 16 2002-11-18 15:59:11 [0] DEBUG: Allocated by octstr_create_from_data_real at gwlib/octstr.c:185 2002-11-18 15:59:11 [0] DEBUG: Claimed by parse_url at gwlib/http.c:1156 2002-11-18 15:59:11 [0] DEBUG: Contents of area (first 16 bytes): Nisan
[RFC]: strip_blanks in smsbox
When sending an sms, kannel do a strip_blanks to remove any cr,lf,space et all from the beginning and the end of the message. I'm trying to send some cards (messages that scroll with jokes, ascii images and others) that requires to have some spaces in the first line, and kannel "eats" them. May I change the strip_blanks to a strip_newlines, so kannel only remove the newlines (cr or lf) and leave the spaces at the beginning (I can remove the spaces at the end too). BTW: did you notice that Siemens process CR and LF as a new line and nokia ignores CR ? And that nokia 6210 eats all the spaces at the beginning of the lines, for example, 1%0A%20%202, 6210 ignores the two %20 (spaces). Grrr
Re: smsbox port problem
> Hi, >Quite strangely my Kannel (version 1.0.3) is not able to open the > server socket at smsbox-port. No matter what port i'm mentioning > there, the bearerbox simply isn't able to open the listening socket. > When i check by "netstat" then it doesn't show that port in the > existing listening sockets either. >Could anyone give me any cue on this. This is quite urgent for me > as our server is in the production environment. any permission items not granting rights? Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
RE: smsbox port problem
>Quite strangely my Kannel (version 1.0.3) is not able to > open the server socket at smsbox-port. No matter what port > i'm mentioning there, the bearerbox simply isn't able to open > the listening socket. When i check by "netstat" then it > doesn't show that port in the existing listening sockets either. The bearerbox doesn't open smsbox-port unless you have an SMSC configured. Try setting up a fakesmsc to test with.
AW: bearerbox <-> smsbox communication ???
This should get you started: http://liw.iki.fi/liw/texts/cpp-trick.html Regards Jörg > -Ursprüngliche Nachricht- > Von: Veljo Otsason [mailto:[EMAIL PROTECTED]] > Gesendet am: Montag, 26. November 2001 13:12 > An: [EMAIL PROTECTED] > Betreff: bearerbox <-> smsbox communication ??? > > hello! > > does anybody have description of bearerbox and smsbox communication > protocol. i want to write my own smsbox for a specific > application, but i > could'nt find the description. please help me if you can.. > yours, > Veljo > >
Re: smsbox eating CPU ?
On Fri, 2001-11-30 at 14:40, [EMAIL PROTECTED] wrote: > I just noticed, the smsbox on my machine is eating up > 'as much cpu as it can get'. Even though no requests are coming in > (it still serves messages when it has to, though). >Anyone have any hints on typical causes of this ? > > "my other kannels" don't do this... > The machine in question serves both a gsm modem and an SMSC. > I've seen the same behaviour on our kannel running 1.1.5, and as you say, incoming and outgoing sms's seems to work as they should. br Robin
RE: smsbox eating CPU ?
I think this has to do with the way some of the SMSC's have been implemented. The basic pattern is that the smsc code fires up a thread or two, both of which rotate around an infinite loop. Depending on how polling of incoming data is done, these loops may well consume a lot processing power. This is what I noticed while implementing the smsc_cgw code (or, I did precisely the same thing). I solved it by making the threads sleep some small amount of time (with pollfd) while waiting for data. - Anders -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Robin Ericsson Sent: 30. marraskuuta 2001 15:44 To: [EMAIL PROTECTED] Subject: Re: smsbox eating CPU ? On Fri, 2001-11-30 at 14:40, [EMAIL PROTECTED] wrote: > I just noticed, the smsbox on my machine is eating up > 'as much cpu as it can get'. Even though no requests are coming in > (it still serves messages when it has to, though). >Anyone have any hints on typical causes of this ? > > "my other kannels" don't do this... > The machine in question serves both a gsm modem and an SMSC. > I've seen the same behaviour on our kannel running 1.1.5, and as you say, incoming and outgoing sms's seems to work as they should. br Robin
RE: smsbox eating CPU ?
On Fri, 2001-11-30 at 15:27, Anders Lindh wrote: > > I think this has to do with the way some of the SMSC's have been > implemented. The basic pattern is that the smsc code fires up a thread > or two, both of which rotate around an infinite loop. Depending on how > polling of incoming data is done, these loops may well consume a lot > processing power. This is what I noticed while implementing the smsc_cgw > code (or, I did precisely the same thing). I solved it by making the > threads sleep some small amount of time (with pollfd) while waiting for > data. > In my case this is smsbox eating cpu, not bearerbox. br R.
SV: smsbox eating CPU ?
See below (sent in July): --- On a different note I believe to have located the source of CPU-hungry boxes. The problem lies in Kannel's handling of HTTP 1.1 requests. Try using the send-sms interface or the Kannel-admin module from a HTTP 1.1 compliant browser, leave the browser window open and watch the bearerbox or smsbox go powerhungry ~1 minute after the request. It happens every time!! My temporary workaround has been to treat all HTTP-requests as HTTP 1.0 (in http.c), but this is only a short-term solution as there are important benefits from using HTTP 1.1. --- This problem has existed for a long time and has never been fixed. Unfortunately, while my workaround has severely helped, two simultaneous HTTP-request to Kannel can sometimes have the same effect. cheers, Frederik Ammitzbøll Unwire Vestergade 12A, 3. 1456 København K Tlf.: +45 33 33 08 70 Mobil: +45 27 11 99 99 Fax : +45 33 33 09 70 Web: www.unwire.dk > > I think this has to do with the way some of the SMSC's have been > > implemented. The basic pattern is that the smsc code fires up a thread > > or two, both of which rotate around an infinite loop. Depending on how > > polling of incoming data is done, these loops may well consume a lot > > processing power. This is what I noticed while implementing the smsc_cgw > > code (or, I did precisely the same thing). I solved it by making the > > threads sleep some small amount of time (with pollfd) while waiting for > > data. > > > > In my case this is smsbox eating cpu, not bearerbox. > > > > br > R. > > > >
Re: smsbox eating CPU ?
On Fri, 30 Nov 2001 14:40:23 +0100, you wrote: >I just noticed, the smsbox on my machine is eating up >'as much cpu as it can get'. Even though no requests are coming in >(it still serves messages when it has to, though). > Anyone have any hints on typical causes of this ? > >"my other kannels" don't do this... >The machine in question serves both a gsm modem and an SMSC. I have had the same problem with bearerbox and wapbox in a dual CPU machine for a year now. Only solution available is this script run by cron... #!/bin/sh strtest=`top c n 1 b|grep bearer|grep 99.9` if [ ! -z "$strtest" ] then logger "Restarting kannel..." /etc/rc.d/init.d/kannel stop > /dev/null 2>&1 sleep 5 /etc/rc.d/init.d/kannel start > /dev/null 2>&1 sleep 10 fi strtest=`top c n 1 b|grep wapbox|grep 99.9` if [ ! -z "$strtest" ] then logger "Restarting kannel..." /etc/rc.d/init.d/kannel stop > /dev/null 2>&1 sleep 5 /etc/rc.d/init.d/kannel start > /dev/null 2>&1 fi Cheers, Kari
Stable smsbox / AT drivers
Hi there, I've been using the smsbox and AT drivers from release 1.1.5 for some time now. I use it with WaveCom WM02 devices for incoming messages only. The problem that I have is that sometimes, the box will just stop receiving messages, although there is no reported error in the logs. Once the box is restarted messages are received again. Also, EVERYTIME a blank sms message is received (no text) the box falls over complaining thus; INFO: Starting to service <> from <+447971325173> to <1234> PANIC: gwlib/list.c:213: list_get: Assertion `pos < list->len' failed. Please can somebody tell me how I can avoid these problems? Is there are newer version available? If so, from where? Kind regards, Andy
Re: smsbox eating CPU ?
Dear list: As my traffic has increased lately I have occasionally noticed my emi2 smsbox going "power-hungry" as well. It goes from an insignificant CPU load to 96-99%, and stays there. There's no significant impact on the performance but that's probably because I'm nowhere near using the machine's capacity right now. I'm handling only 10-50 SMS per minute right now, on a dedicated line to the operator. I'm manually restarting the boxes when I notice it, but if anyone finds a better fix, please announce to the list. (Yes, I saw the clever little script that checks for high CPU and restarts automatically, I'm hoping for a better one than that.) I was following the discussion but didn't see much resolution, it seems real to me. I hope the issue is followed up... Steve Rapaport Frederik Ammitzbøll wrote: >>>On a different note I believe to have located the source of CPU-hungry >>>boxes. The problem lies in Kannel's handling of HTTP 1.1 >>> >>requests. Try using >> >>>the send-sms interface or the Kannel-admin module from a HTTP >>> >>1.1 compliant >> >>>browser, leave the browser window open and watch the bearerbox >>> >>or smsbox go >> >>>powerhungry ~1 minute after the request. It happens every time!! >>> >>>My temporary workaround has been to treat all HTTP-requests as >>> >>HTTP 1.0 (in >> >>>http.c), but this is only a short-term solution as there are important >>>benefits from using HTTP 1.1. >>>--- >>> >>>This problem has existed for a long time and has never been fixed. >>>Unfortunately, while my workaround has severely helped, two simultaneous >>>HTTP-request to Kannel can sometimes have the same effect. >>> >>I tried to reconstruct the HTTP/1.1 based effect you describe using >>the admin interface, but could not see any bearerbox's cpu demand >>which would lead me to such an assumption?! >> > >Strange...I'm not making this up you know. It happens every single time I >try it, and before I applied my little workaround, Kannel would get >CPU-hungry several times per day - now it only happens once a week and we >have approx. 1000 times the traffic we had back then? Could it be a platform >dependant problem (sounds rather unlikely but...)? > >cheers, > >Frederik Ammitzbøll >Unwire >Vestergade 12A, 3. >1456 København K > >Tlf.: +45 33 33 08 70 >Mobil: +45 27 11 99 99 >Fax : +45 33 33 09 70 >Web: www.unwire.dk > > > > > -- Steve Rapaport World Citizen
Re: smsbox eating CPU ?
Hi all, some off-topic question. I have a cisco router for X.25-TCP/IP translation. Every time it connects to the SMSC, in telnet session router says Trying 2...Open How do I disable these ? Thanks.
smsbox closed connection (at2)
Something very very bad happens sometimes with smsbox. This isn't the first time it happens Don't really know why, but it closes connection. Maybe it's because it receives an empty sms, but I have omit-empty = true in sms-service group. I give you here all the details, and I really hope I can solve this bug that keeps craching smsbox. (this is cvs (about one month ago) with at2 (on win2000). Andreas please help :-) Thanks in advance Andrea --begin bearebox .log 2002-02-12 23:53:40 [10] DEBUG: boxc_receiver: got ack 2002-02-12 23:53:40 [10] INFO: Connection closed by the box <127.0.0.1> 2002-02-12 23:53:40 [6] DEBUG: AT2[/dev/com9]: <-- OK 2002-02-13 05:45:10 [6] DEBUG: AT2[/dev/com9]: <-- +CMT: ,23 2002-02-13 05:45:10 [6] DEBUG: AT2[/dev/com9]: <-- 0791934329004080040C9193437810237020203160641104046176790D 2002-02-13 05:45:10 [6] DEBUG: AT2[/dev/com9]: --> AT+CNMA^M 2002-02-13 05:45:10 [11] DEBUG: Thread 11 (gw/bb_boxc.c:boxc_sender) terminates. 2002-02-13 05:45:10 [10] DEBUG: Thread 10 (gw/bb_boxc.c:function) terminates. begin .access 2002-02-12 23:51:13 Receive SMS [SMSC:A] [SVC:] [from:393393297830] [to:1234] [flags:0:1:0:0] [msg:6:MATRIX] [udh:0:] 2002-02-12 23:51:24 SMS HTTP-request sender:393393297830 request: 'Vampir.it>LaComunitàDellaNotte-SABATO 26 RickyLeRoy,MickyV,Zicky e spettacolo live techno Eva Vugaris.IMPERDIBILE,info e liste 3474116027 NON MANCARE!!!' url: 'http://www.futureland.it/sms/insert_received.asp?testo=MATRIX&sender=393393 297830&receiver=A' reply: 200 '<< successful >>' 2002-02-13 00:53:40 Receive SMS [SMSC:B] [SVC:] [from:393487013207] [to:1234] [flags:0:1:0:0] [msg:0:] [udh:0:] ---begin smsbox.log 2002-02-12 21:22:28 [4] INFO: Starting to service from <+393408341452> to <2234> 2002-02-12 21:22:28 [8] DEBUG: HTTP: Sending request: 2002-02-12 21:22:28 [8] DEBUG: Octet string at 0x1003bfc8: 2002-02-12 21:22:28 [8] DEBUG: len: 135 2002-02-12 21:22:28 [8] DEBUG: size: 136 2002-02-12 21:22:28 [8] DEBUG: immutable: 0 2002-02-12 21:22:28 [8] DEBUG: data: 47 45 54 20 2f 73 6d 73 GET /sms 2002-02-12 21:22:28 [8] DEBUG: data: 2f 69 6e 73 65 72 74 5f /insert_ 2002-02-12 21:22:28 [8] DEBUG: data: 72 65 63 65 69 76 65 64 received 2002-02-12 21:22:28 [8] DEBUG: data: 2e 61 73 70 3f 74 65 73 .asp?tes 2002-02-12 21:22:28 [8] DEBUG: data: 74 6f 3d 52 49 4e 47 26 to=RING& 2002-02-12 21:22:28 [8] DEBUG: data: 73 65 6e 64 65 72 3d 25 sender=% 2002-02-12 21:22:28 [8] DEBUG: data: 32 42 33 39 33 34 30 38 2B393408 2002-02-12 21:22:28 [8] DEBUG: data: 33 34 31 34 35 32 26 72 341452&r 2002-02-12 21:22:28 [8] DEBUG: data: 65 63 65 69 76 65 72 3d eceiver= 2002-02-12 21:22:28 [8] DEBUG: data: 41 20 48 54 54 50 2f 31 A HTTP/1 2002-02-12 21:22:28 [8] DEBUG: data: 2e 31 0d 0a 48 6f 73 74 .1..Host 2002-02-12 21:22:28 [8] DEBUG: data: 3a 20 77 77 77 2e 66 75 : www.fu 2002-02-12 21:22:28 [8] DEBUG: data: 74 75 72 65 6c 61 6e 64 tureland 2002-02-12 21:22:28 [8] DEBUG: data: 2e 69 74 0d 0a 55 73 65 .it..Use 2002-02-12 21:22:28 [8] DEBUG: data: 72 2d 41 67 65 6e 74 3a r-Agent: 2002-02-12 21:22:28 [8] DEBUG: data: 20 4b 61 6e 6e 65 6c 20Kannel 2002-02-12 21:22:28 [8] DEBUG: data: 63 76 73 0d 0a 0d 0a cvs 2002-02-12 21:22:28 [8] DEBUG: Octet string dump ends. 2002-02-12 21:22:34 [7] DEBUG: HTTP: Status line: 2002-02-12 21:22:34 [5] INFO: No reply sent, denied. 2002-02-12 21:50:16 [4] INFO: Starting to service from <+393299070245> to <2234> 2002-02-12 21:50:16 [8] ERROR: Error reading from fd 25: 2002-02-12 21:50:16 [8] ERROR: System error 104: Connection reset by peer 2002-02-12 21:50:16 [8] DEBUG: HTTP: Opening connection to `www.futureland.it:80'. 2002-02-12 21:50:16 [8] DEBUG: HTTP: Sending request: 2002-02-12 21:50:16 [8] DEBUG: Octet string at 0x10044c88: 2002-02-12 21:50:16 [8] DEBUG: len: 135 2002-02-12 21:50:16 [8] DEBUG: size: 136 2002-02-12 21:50:16 [8] DEBUG: immutable: 0 2002-02-12 21:50:16 [8] DEBUG: data: 47 45 54 20 2f 73 6d 73 GET /sms 2002-02-12 21:50:16 [8] DEBUG: data: 2f 69 6e 73 65 72 74 5f /insert_ 2002-02-12 21:50:16 [8] DEBUG: data: 72 65 63 65 69 76 65 64 received 2002-02-12 21:50:16 [8] DEBUG: data: 2e 61 73 70 3f 74 65 73 .asp?tes 2002-02-12 21:50:16 [8] DEBUG: data: 74 6f 3d 52 49 4e 47 26 to=RING& 2002-02-12 21:50:16 [8] DEBUG: data: 73 65 6e 64 65 72 3d 25 sender=% 2002-02-12 21:50:16 [8] DEBUG: data: 32 42 33 39 33 32 39 39 2B393299 2002-02-12 21:50:16 [8] DEBUG: data: 30 37 30 32 34 35 26 72 070245&r 2002-02-12 21:50:16 [8] DEBUG: data: 65 63 65 69 76 65 72 3d eceiver= 2002-02-12 21:50:16 [8] DEBUG: data: 43 20 48 54 54 50 2f 31 C HTTP/1 2002-02-12 21:50:16 [8] DEBUG: data: 2e 31 0d 0a 48 6f 73 74 .1..Host 2002-02-12 21:50:16 [8] DEBUG: data: 3a 20 77 77 77 2e 66 75 : www.fu 2002-02-12 21:50:16 [8] DEBUG:
Re: [BUG] smsbox memleak
> There is a new memory leak in the cvs, in smsbox. > > For each dlr ack.. and probabally sms-service > > 2002-11-18 15:59:11 [0] DEBUG: Allocated by octstr_create_from_data_real at > gwlib/octstr.c:185 > 2002-11-18 15:59:11 [0] DEBUG: Claimed by parse_url at gwlib/http.c:1156 > 2002-11-18 15:59:11 [0] DEBUG: Contents of area (first 16 bytes): > 2002-11-18 15:59:11 [0] DEBUG: 48 5a 0c 09 16 00 00 00 17 00 00 00 00 00 00 00 > 2002-11-18 15:59:11 [0] DEBUG: Area 0x90c2960, size 16, max_size 16 > 2002-11-18 15:59:11 [0] DEBUG: Allocated by octstr_create_from_data_real at > gwlib/octstr.c:185 > 2002-11-18 15:59:11 [0] DEBUG: Claimed by parse_url at gwlib/http.c:1156 > 2002-11-18 15:59:11 [0] DEBUG: Contents of area (first 16 bytes): can you provide a patch for this, please?! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Mutex cygwin smsbox problem
Hi! Kannel version 1.2.0 On Windows 2000 Advanced Server, using cygwin (donwloaded from cygwin.com one and a half months ago) smsbox dies and the following message appears in smsbox's log: 2002-12-06 09:46:17 [8] ERROR: System error 104: Connection reset by peer 2002-12-06 09:46:18 [7] PANIC: gwlib/thread.c:79: mutex_lock_real: Mutex failure! (Called from gwlib/list.c:427:lock.) Do you have any idea or workaround to aviod this problem? Maybe this is a problem with cygwin pthread, isn't it? Thank, Andras -- _ Fogarasi, András informatikus mérnök, közgazdász szakmérnök/ information technology engineer, engineer of economics http://www.fogarasi.com/ Mobile: +36 30 2378124 PGP key: http://www.fogarasi.com/gpg/fog-pub.html _ Unix/Linux system administration, system programming, web development, system integration, consultancy _
AW: [RFC]: strip_blanks in smsbox
ASCII-art won't work with a proportional font. I do not see how you can get any consistent results. Regards Jörg -Ursprüngliche Nachricht- Von: Bruno David Rodrigues [mailto:[EMAIL PROTECTED]] Gesendet am: Donnerstag, 15. November 2001 15:02 An: [EMAIL PROTECTED] Betreff: [RFC]: strip_blanks in smsbox When sending an sms, kannel do a strip_blanks to remove any cr,lf,space et all from the beginning and the end of the message. I'm trying to send some cards (messages that scroll with jokes, ascii images and others) that requires to have some spaces in the first line, and kannel "eats" them. May I change the strip_blanks to a strip_newlines, so kannel only remove the newlines (cr or lf) and leave the spaces at the beginning (I can remove the spaces at the end too). BTW: did you notice that Siemens process CR and LF as a new line and nokia ignores CR ? And that nokia 6210 eats all the spaces at the beginning of the lines, for example, 1%0A%20%202, 6210 ignores the two %20 (spaces). Grrr
Re: SV: smsbox eating CPU ?
Frederik Ammitzbøll schrieb: > > See below (sent in July): > > --- > On a different note I believe to have located the source of CPU-hungry > boxes. The problem lies in Kannel's handling of HTTP 1.1 requests. Try using > the send-sms interface or the Kannel-admin module from a HTTP 1.1 compliant > browser, leave the browser window open and watch the bearerbox or smsbox go > powerhungry ~1 minute after the request. It happens every time!! > > My temporary workaround has been to treat all HTTP-requests as HTTP 1.0 (in > http.c), but this is only a short-term solution as there are important > benefits from using HTTP 1.1. > --- > > This problem has existed for a long time and has never been fixed. > Unfortunately, while my workaround has severely helped, two simultaneous > HTTP-request to Kannel can sometimes have the same effect. I tried to reconstruct the HTTP/1.1 based effect you describe using the admin interface, but could not see any bearerbox's cpu demand which would lead me to such an assumption?! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
SV: SV: smsbox eating CPU ?
> > On a different note I believe to have located the source of CPU-hungry > > boxes. The problem lies in Kannel's handling of HTTP 1.1 > requests. Try using > > the send-sms interface or the Kannel-admin module from a HTTP > 1.1 compliant > > browser, leave the browser window open and watch the bearerbox > or smsbox go > > powerhungry ~1 minute after the request. It happens every time!! > > > > My temporary workaround has been to treat all HTTP-requests as > HTTP 1.0 (in > > http.c), but this is only a short-term solution as there are important > > benefits from using HTTP 1.1. > > --- > > > > This problem has existed for a long time and has never been fixed. > > Unfortunately, while my workaround has severely helped, two simultaneous > > HTTP-request to Kannel can sometimes have the same effect. > > I tried to reconstruct the HTTP/1.1 based effect you describe using > the admin interface, but could not see any bearerbox's cpu demand > which would lead me to such an assumption?! Strange...I'm not making this up you know. It happens every single time I try it, and before I applied my little workaround, Kannel would get CPU-hungry several times per day - now it only happens once a week and we have approx. 1000 times the traffic we had back then? Could it be a platform dependant problem (sounds rather unlikely but...)? cheers, Frederik Ammitzbøll Unwire Vestergade 12A, 3. 1456 København K Tlf.: +45 33 33 08 70 Mobil: +45 27 11 99 99 Fax : +45 33 33 09 70 Web: www.unwire.dk
Re: smsbox closed connection (at2)
Andrea Viscovich wrote: > > Something very very bad happens sometimes with smsbox. > This isn't the first time it happens > Don't really know why, but it closes connection. > Maybe it's because it receives an empty sms, but > I have omit-empty = true in sms-service group. > I give you here all the details, and I really hope I can solve this bug > that keeps craching smsbox. > (this is cvs (about one month ago) with at2 (on win2000). > 2002-02-12 23:53:40 [7] DEBUG: HTTP: Status line: Server Error> > 2002-02-12 23:53:40 [5] ERROR: Start marker was damaged for area 0x10024cf8 > 2002-02-12 23:53:40 [5] ERROR: Could not find area information. > 2002-02-12 23:53:40 [5] PANIC: gwlib/octstr.c:2034: seems_valid_real: > Assertion `gw_check_is_allocated(ostr)' failed. (Called from > gw/smsbox.c:698:url_result_thread.) so we have a failing assertion checking which is panicing here in smsbox and causing it to stop. Unfortunatly our cvs checkout is not up to date so I don't see what is happening on *your* line 698 of smsbox.c. The current cvs is out of scope for url_result_thread() for this line number. Could you please copy a short passage around that number, or the url_result_thread() function, so we can see what operations causes the assertion problem. Usually you will do something nasty with a orctstr* when you get this. BTW, if this is happening from time to time and crashing your bearerbox you may either consider to run smsbox as NT service and define a restart with Win200 internal mechanisms for the service or use a shell wrapper script around calling smsbox which loops infinitly around calling smsbox. (But this should be considered a kludge, of course). Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
smsbox and mutex detailed analysis
I'm not as familiar with the Kannel code as various others so I hope this can help track down the mutex problem in smsbox. To reproduce the mutex failure, you simply need to make rapid HTTP requests to smsbox. Sometimes smsbox will kark it quickly, or sometimes it will take longer. You can point bearerbox to a bad IP SMSC... so that the messages don't actually get sent out. This is where the mutex is failing... 2002-02-18 05:15:28 [3] PANIC: gwlib/conn.c:174: unlock_out_real: Mutex unlock failed. (Called from gwlib/conn.c:793:conn_register.) My line numbers aren't in sync with CVS so I've attached a patch to insert the debugging messages that I've coded. It looks like the HTTP server thread [2] is doing something bad with the 'conn' mutex because smsbox seems to die when the HTTP server thread [2] calls conn_register before sendsms thread [3] calls conn_register. Phew... I hope someone can manage to kill this bug with the info provided... 'cause my brain is highly overloaded with pthread-i-ness... ;-) Good luck, Cheerios, Ben 2002-02-18 05:34:05 [0] INFO: Starting to log to file /home/ben/smsbox.log level 3 2002-02-18 05:34:05 [0] INFO: Added logfile `/home/ben/smsbox.log' with level `3'. 2002-02-18 05:34:05 [0] INFO: Service global sender set as '123' 2002-02-18 05:34:05 [0] DEBUG: HTTP: Opening server at port 13013. 2002-02-18 05:34:05 [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller) 2002-02-18 05:34:05 [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread) 2002-02-18 05:34:05 [0] INFO: Set up send sms service at port 13013 2002-02-18 05:34:05 [0] DEBUG: Started thread 3 (gw/smsbox.c:sendsms_thread) 2002-02-18 05:34:05 [0] DEBUG: ------ 2002-02-18 05:34:05 [0] DEBUG: Kannel smsbox version cvs starting 2002-02-18 05:34:05 [0] DEBUG: Started thread 4 (gw/smsbox.c:obey_request_thread) 2002-02-18 05:34:05 [0] DEBUG: Started thread 5 (gw/smsbox.c:url_result_thread) 2002-02-18 05:34:05 [0] INFO: Connected to bearerbox at localhost port 13001. 2002-02-18 05:34:05 [0] DEBUG: Started thread 6 (gw/heartbeat.c:heartbeat_thread) 2002-02-18 05:37:12 [3] INFO: smsbox: Got HTTP request from <192.168.1.149> 2002-02-18 05:37:12 [3] INFO: sendsms used by 2002-02-18 05:37:12 [3] INFO: sendsms sender: (192.168.1.149) to:<61413122959> msg: 2002-02-18 05:37:12 [3] DEBUG: message length 160, sending 1 messages 2002-02-18 05:37:12 [3] ERROR: ben unlock_out_real: conn_write_withlen: gwlib/conn.c:1012 2002-02-18 05:37:12 [3] DEBUG: Status: 202 Answer: 2002-02-18 05:37:12 [3] ERROR: ben unlock_out_real: conn_write: gwlib/conn.c:985 2002-02-18 05:37:12 [3] DEBUG: HTTP: Resetting HTTPClient for `192.168.1.149'. 2002-02-18 05:37:12 [3] DEBUG: ben ret == 0 client_reset(client): http_send_reply 2002-02-18 05:37:12 [3] ERROR: ben unlock_in_real: conn_register: gwlib/conn.c:793 2002-02-18 05:37:12 [3] ERROR: ben unlock_out_real: conn_register: gwlib/conn.c:794 2002-02-18 05:37:12 [1] ERROR: ben unlock_in_real: poll_callback: gwlib/conn.c:746 2002-02-18 05:37:12 [1] ERROR: ben unlock_in_real: conn_read_line: gwlib/conn.c:1072 2002-02-18 05:37:12 [1] ERROR: ben unlock_in_real: conn_eof: gwlib/conn.c:688 2002-02-18 05:37:12 [1] DEBUG: HTTP: Destroying HTTPClient area 0x809b628. 2002-02-18 05:37:12 [1] DEBUG: HTTP: Destroying HTTPClient for `192.168.1.149'. 2002-02-18 05:37:12 [2] DEBUG: HTTP: Creating HTTPClient for `192.168.1.149'. 2002-02-18 05:37:12 [2] ERROR: ben unlock_in_real: conn_register: gwlib/conn.c:793 2002-02-18 05:37:12 [2] ERROR: ben unlock_out_real: conn_register: gwlib/conn.c:794 2002-02-18 05:37:12 [1] ERROR: ben unlock_in_real: poll_callback: gwlib/conn.c:746 2002-02-18 05:37:12 [1] ERROR: ben unlock_in_real: conn_read_line: gwlib/conn.c:1089 2002-02-18 05:37:12 [1] ERROR: ben unlock_in_real: conn_read_line: gwlib/conn.c:1089 2002-02-18 05:37:12 [1] ERROR: ben unlock_in_real: conn_unregister: gwlib/conn.c:827 2002-02-18 05:37:12 [1] ERROR: ben unlock_out_real: conn_unregister: gwlib/conn.c:828 2002-02-18 05:37:12 [3] INFO: smsbox: Got HTTP request from <192.168.1.149> 2002-02-18 05:37:12 [3] INFO: sendsms used by 2002-02-18 05:37:12 [3] INFO: sendsms sender: (192.168.1.149) to:<61408493783> msg: 2002-02-18 05:37:12 [3] DEBUG: message length 160, sending 1 messages 2002-02-18 05:37:12 [3] ERROR: ben unlock_out_real: conn_write_withlen: gwlib/conn.c:1012 2002-02-18 05:37:12 [3] DEBUG: Status: 202 Answer: 2002-02-18 05:37:12 [3] ERROR: ben unlock_out_real: conn_write: gwlib/conn.c:985 2002-02-18 05:37:12 [3] DEBUG: HTTP: Resetting HTTPClient for `192.168.1.149'. 2002-02-18 05:37:12 [3] DEBUG: ben ret == 0 client_reset(client): http_send_reply 2002-02-18 05:37:12 [3] ERROR: ben unlock_in_real: conn_register: gwlib/conn.c:793 2002-02-18 05:37:12 [3] ERROR: ben unlock_out_real: conn_register: gwlib/conn.c:794 2002-02-18 05:37:12 [1] ERROR: ben unlock_in
SMPP causing smsbox to crash?
Hey guys, I've set up SMPPSim, and ive created the proper entries in my kannel.conf to use it as an smsc to connect to, and all is well. it connects and the whole 9 yards. When i send a message to it, it accepts it, and loops it back to kannel. So far we're okay. When kannel GETS this message looped back to itself, it freaks out and crashes. I sent the original message (to the smsc) with From=12345 To=16047289785 Text=haha Here is the log output from smsbox from the point of getting the message back, and dying. (I am using cvs from 2 days ago) 2002-02-22 11:54:07 [4] WARNING: No translation found for from <12345> to <16047289785> 2002-02-22 11:54:07 [4] ERROR: request failed 2002-02-22 11:54:07 [4] DEBUG: message length 14, sending 1 messages 2002-02-22 11:54:08 [4] WARNING: No translation found for from <16047289785> to <12345> 2002-02-22 11:54:08 [4] ERROR: request failed 2002-02-22 11:54:08 [4] ERROR: Start marker was damaged for area 0x81bcd60 2002-02-22 11:54:08 [4] ERROR: Could not find area information. 2002-02-22 11:54:08 [4] PANIC: gwlib/octstr.c:2056: seems_valid_real: Assertion `gw_check_is_allocated(ostr)' failed. (Called from gwlib/octstr.c:252:octstr_len Any help?
wait_for_connections fails and kills smsbox
Interesting problem using latest cvs (with CMTI patch) is that occassionally the wait_for_connections process fails and takes the smsbox with it. Looks like the process fails to read from the serial port (either due to the phone or some other random process on my machine) and this takes the smsbox down (which I don't think it should do). Anyone fixed this? Alex 2002-05-01 09:53:05 [5] DEBUG: AT2[Motorola1]: <-- OK 2002-05-01 13:50:17 [4] ERROR: wait_for_connections failed 2002-05-01 13:50:17 [5] ERROR: AT2[Motorola1]: error on select 2002-05-01 13:50:17 [5] ERROR: System error 13: Permission denied 2002-05-01 13:50:17 [4] ERROR: System error 13: Permission denied 2002-05-01 13:50:17 [5] WARNING: gwthread_sleep: error in poll ... 2002-05-01 13:50:18 [5] WARNING: gwthread_sleep: error in poll 2002-05-01 13:50:18 [5] WARNING: System error 13: Permission denied 2002-05-01 13:50:18 [5] ERROR: AT2[Motorola1]: error on select 2002-05-01 13:50:18 [5] ERROR: System error 13: Permission denied 2002-05-01 13:50:22 [0] ERROR: Error reading from fd 18: 2002-05-01 13:50:22 [0] ERROR: System error 104: Connection reset by peer 2002-05-01 13:50:22 [0] ERROR: Error reading from fd 18: 2002-05-01 13:50:22 [0] ERROR: System error 104: Connection reset by peer 2002-05-01 13:50:22 [0] INFO: Error reading from bearerbox, disconnecting 2002-05-01 13:50:22 [0] INFO: Received (and handled?) 2 requests in 72512 seconds (0.00 per second) 2002-05-01 13:50:22 [0] INFO: Kannel smsbox terminating. 2002-05-01 13:50:22 [6] DEBUG: Thread 6 (gw/heartbeat.c:heartbeat_thread) terminates. 2002-05-01 13:50:23 [0] DEBUG: Waiting for 2 (gwlib/http.c:server_thread) to terminate 2002-05-01 13:50:23 [2] WARNING: gwthread_sleep: error in poll 2002-05-01 13:50:23 [2] WARNING: System error 13: Permission denied -- Alex Judd http://www.skywire.co.uk
DLRmask 1, smsbox crashesh (CIMD2)
Hi, I'm using kannel 1.1.6 on RH7.1. We have developed small CIMD2 server using CIMD Java API. When I connect kannel to server, they exchange packets properly. Even submit_message goes smoothly. But when I put dlrmask = 1 in HTTP sendsms, as soon as kannel receives delivery report packet from server, smsbox crashesh. (See log). The packet dump from server is 04-06-1999 17:02:08: Server is Listening at port :6789 04-06-1999 17:02:15: Client :01:001 010:foo 011:bar 59 04-06-1999 17:02:16: Server :51:001 3C 04-06-1999 17:04:13: Client :03:003 021:999 056:0 041:0 045:0 033:Welcome to SMS Gateway 88 04-06-1999 17:04:13: Submit Message 04-06-1999 17:04:13: Server :53:003 021:999 060:020504050413 FA 04-06-1999 17:13:56: Client :03:035 021:5678 056:12 045:0 033:dlr test 38 04-06-1999 17:13:56: Submit Message 04-06-1999 17:13:56: Server :53:035 021:5678 060:020504051356 32 04-06-1999 17:13:56: Server :23:004 021:5678 046:0 060:020504051356 063:020504051356 061:4 062:0 91 04-06-1999 17:13:57: Client :73:004 43 http://kannelhost:13013/cgi-bin/sendsms?user=shridhar&pass=vqindia&to=5678&f rom=1234&text=dlr%20test&dlrmask=1 Kannel.conf: group = core admin-port = 13000 smsbox-port = 13001 admin-password = vqindia log-file = "bearerbox.log" log-level = 0 box-deny-ip = "*.*.*.*" box-allow-ip = "127.0.0.1" access-log = "access.log" group = smsc smsc = cimd2 smsc-id = ussd host = 192.168.1.97 port = 6789 smsc-username = "foo" smsc-password = "bar" keepalive = 1 group = smsbox bearerbox-host = localhost sendsms-port = 13013 global-sender = 1234 log-file = "smsbox.log" log-level = 0 sms-length = 200 group = sms-service keyword = default text = "Welcome to VQI Gateway" group = sendsms-user username = shridhar password = vqindia dlr-url = "http://localhost/dlr.html"; Bearerbox log: 2002-06-04 17:15:21 [4] DEBUG: Started thread 14 (gw/bb_boxc.c:function) 2002-06-04 17:15:21 [14] INFO: Client connected from <127.0.0.1> 2002-06-04 17:15:21 [14] DEBUG: Started thread 15 (gw/bb_boxc.c:boxc_sender) 2002-06-04 17:15:44 [14] DEBUG: boxc_receiver: sms received 2002-06-04 17:15:44 [6] DEBUG: smscconn_sender (CIMD2:192.168.1.97:6789:foo): sending message 2002-06-04 17:15:44 [6] DEBUG: CIMD2 sending message. Text: 2002-06-04 17:15:44 [6] DEBUG: Octet string at 0x820b178: 2002-06-04 17:15:44 [6] DEBUG: len: 8 2002-06-04 17:15:44 [6] DEBUG: size: 9 2002-06-04 17:15:44 [6] DEBUG: immutable: 0 2002-06-04 17:15:44 [6] DEBUG: data: 64 6c 72 20 74 65 73 74 dlr test 2002-06-04 17:15:44 [6] DEBUG: Octet string dump ends. 2002-06-04 17:15:44 [6] DEBUG: After CIMD2 encoding: 2002-06-04 17:15:44 [6] DEBUG: Octet string at 0x820b178: 2002-06-04 17:15:44 [6] DEBUG: len: 8 2002-06-04 17:15:44 [6] DEBUG: size: 9 2002-06-04 17:15:44 [6] DEBUG: immutable: 0 2002-06-04 17:15:44 [6] DEBUG: data: 64 6c 72 20 74 65 73 74 dlr test 2002-06-04 17:15:44 [6] DEBUG: Octet string dump ends. 2002-06-04 17:15:46 [5] DEBUG: Looking for DLR smsc=CIMD2:192.168.1.97:6789:foo, ts=050405135625, dst=5678, type=1 2002-06-04 17:15:46 [5] DEBUG: created DLR message: 2002-06-04 17:15:46 [5] DEBUG: smscconn (CIMD2:192.168.1.97:6789:foo): new message received 2002-06-04 17:15:46 [13] DEBUG: Thread 13 (gw/bb_boxc.c:boxc_sender) terminates. 2002-06-04 17:15:46 [12] DEBUG: Thread 12 (gw/bb_boxc.c:function) terminates. 2002-06-04 17:15:46 [14] INFO: Connection closed by the box <127.0.0.1> 2002-06-04 17:15:46 [15] DEBUG: boxc_sender: sent message to <127.0.0.1> 2002-06-04 17:15:46 [15] DEBUG: Thread 15 (gw/bb_boxc.c:boxc_sender) terminates. 2002-06-04 17:15:46 [14] DEBUG: Thread 14 (gw/bb_boxc.c:function) terminates. SMSbox log: 2002-06-04 17:15:21 [0] INFO: Added logfile `smsbox.log' with level `0'. 2002-06-04 17:15:21 [0] INFO: Service global sender set as '123' 2002-06-04 17:15:21 [0] DEBUG: HTTP: Opening server at port 13013. 2002-06-04 17:15:21 [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller) 2002-06-04 17:15:21 [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread) 2002-06-04 17:15:21 [0] INFO: Set up send sms service at port 13013 2002-06-04 17:15:21 [0] DEBUG: Started thread 3 (gw/smsbox.c:sendsms_thread) 2002-06-04 17:15:21 [0] DEBUG: -- 2002-06-04 17:15:21 [0] DEBUG: Kannel smsbox version 1.1.6 starting 2002-06-04 17:15:21 [0] DEBUG: Started thread 4 (gw/smsbox.c:obey_request_thread) 2002-06-04 17:15:21 [0] DEBUG: Started thread 5 (gw/smsbox.c:url_result_thread) 2002-06-04 17:15:21 [0] INFO: Connected to bearerbox at localhost port 13001. 2002-06-04 17:15:21 [0] DEBUG: Started thread 6 (gw/heartbeat.c:heartbeat_thread) 2002-06-04 17:15:44 [2] DEBUG: HTTP: Creating HTTPClient for `192.168.1.97'. 2002-06-04 17:15:44 [3] INFO: smsbox: Got HTTP request from <192.168.1.97> 2002-06-04 17:15:44 [3] INFO: sendsms used by
Re: smsbox crashed (stable 1.2.0)
Hello Cipher,
Maybe you could provide a bit more information such as config (to show
sendsms-user setup - are you using 'white/black' lists etc). Are you
trying to send multiple messages, does it fail always/somtimes, etc ...
Also it is a good idea to supply logs with debug level 0. NB: adding a
few debug() calls of your own to narrow the problem down to a code line
or block is useful.
>From a quick look at the code in smsbox.c the first pointer to a problem
is the Illegal character log which is printed in smsbox_req_handle. The
receiv number should be added to a 'denied' list and the message (later)
ignored (with logging). When I send a single message via kannel's http
interface with a a bogus 'to' field I receive the following which fits
the above description. Can you replicate this? If you provide a bit more
information I/we can try and replicate your problem.
[3] INFO: smsbox: Got HTTP request from <127.0.0.1>
[3] INFO: sendsms used by
[3] INFO: Illegal characters in 'to' string ('123456a') vs '0123456789
+-'
[3] INFO: sendsms sender: (127.0.0.1) to:<123456a> msg:
[3] DEBUG: Status: 400 Answer:
Cheers,
Alan
ps. I have created a similar panic by switching ostr pointers (ie:
without a duplicate or create). If you have modified the code in any way
you might like to check this.
On Sat, 2002-07-20 at 20:46, Cipher Strength wrote:
> NO body yet replied to this.
>
>
> >
> >Hi ALL,
> >
> >kannel stable release 1.2.0
> >RedHat 7.3
> >EMI2
> >
> >smsbox crashed with the following last entries in smsbox log file
> >
> >2002-07-16 22:37:48 [3] INFO: smsbox: Got HTTP request
> >from <
> >10.156.11.7>
> >2002-07-16 22:37:48 [3] INFO: sendsms used by
> >2002-07-16 22:37:48 [3] INFO: Illegal characters in 'to' string ('721275j')
> >vs '
> >0123456789 +-'
> >2002-07-16 22:37:48 [3] INFO: sendsms sender: (10.156.11.7)
> >to:< 721275j> msg:<*WEBSMS* hjkkjkhj>
> >2002-07-16 22:37:48 [3] PANIC: gwlib/octstr.c:2112: seems_valid_real:
> >Assertion
> >`ostr->len + 1 <= ostr->size' failed. (Called from
> >gw/smsbox.c:1813:smsbox_req_h
> >andle.)
> >
> >
> >CIPHER
RE: smsbox crashed (stable 1.2.0)
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Cipher Strength
> Sent: Saturday, July 20, 2002 11:46 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: smsbox crashed (stable 1.2.0)
>
>
> NO body yet replied to this.
the following should fix the problem .. however, there may be more memory
leaks, so could somebody (who wrote it?) please take a look at that.
will somebody care to take time to commit this and my previous bugfix-patch
into cvs?
kaido
diff -ur gateway-1.2.0/gw/smsbox.c gateway-patched/gw/smsbox.c
--- gateway-1.2.0/gw/smsbox.c Wed Jun 12 00:35:45 2002
+++ gateway-patched/gw/smsbox.c Mon Jul 22 11:57:00 2002
@@ -1786,7 +1786,7 @@
}
}
msg_destroy(msg);
-list_destroy(receiver, octstr_destroy_item);
+list_destroy(receiver, NULL);
list_destroy(allowed, octstr_destroy_item);
/* have all receivers been denied by list rules?! */
@@ -1811,6 +1811,7 @@
octstr_format_append(returnerror, " Denied receivers are:");
while ((receiv = list_extract_first(denied)) != NULL) {
octstr_format_append(returnerror, " %s",
octstr_get_cstr(receiv));
+ octstr_destroy (receiv);
}
}
list_destroy(denied, octstr_destroy_item);
[PATCH] internal bearerbox <-> smsbox routing
Hi all,
attached is a patch that I developed today for internal smsbox routing
inside bearerbox. The patch is quite big, so I'll try to explain what
the intention is and what it does.
Basically currently any sms that arrives at bearerbox via a specific
thread of a specific smsc module is produced to a global queue
(incoming_sms). All connected smsbox'es do grap a msg from that queue
all process it. This mechanism is basically used to load-balance msg
traffic to various smsbox'es.
However, sometimes it may be desireable for various reasons to be able
to "route" the sms msg to a specific smsbox. This has to be done
inside bearerbox, between the smsc module layer and the communication
to the smsbox'es.
First, bearerbox needs to know about smsboxes in a way that is
semantically more relevant. We know the IP of the smsbox and even a
local file descriptor, but that's not enough. Imagine a smsbox sending
a DLR-requesting msg. Not smsbox(1) sends msg to bearerbox, bearerbox
holds the dlr queue, receives the report from the smsc module and now
does not know if it should route to smsbox(1) or smsbox(2). Now
basically in this easy scenario it does not matter, because each
smsbox instance does "only" a URL lookup. But think of a SMPP proxying
box that has own state tables and reports have to be re-routed exactly
to that instance to update status tables.
Ok, here is how the thing works:
* gw/smsbox.c: graps a 'smsbox-id' from it's config group and sends
an admin msg identifying itself with a id to bearerbox
* gw/bb_boxc.c: when an admin msg is received by an identicying
smsbox, the incoming queue is switched to a private list, so that no
other smsbox shares the same list with the new identified smsbox
* gw/msg.h: adding a boxc_id Octstr to type sms to hold the
smsbox-id while transporting msg from smsbox'es to bearerbox
* gw/dlr.c: adding a boxc_id parameter to the dlr_add() abstraction
layers and to the relecant smsc_foobar.c modules
* the message went out of the smsc module door
* the delivery report comes in
* gw/dlr.c: dlr_find() inserts the remembered boxc_id to the msg
structure and passes it through the smsc module to gw/bb_smscconn.c
* gw/bb_smscconn.c: gets all incoming sms from the smsc modules and
calls the new gw/bb_boxc.c:route_incoming_sms() routine to descride to
while list this msg is produced and hence to which smsbox the msg is
routed
The smsbox routing is defined in the configuration file via the
multi-grou "smsbox-route", like this
group = smsbox-route
smsbox-id = smsbox_1
smsc_ids = "fake_1;fake_2;fake_3"
shortcuts = "83444;83555"
which means route any message coming from the smsc-id's or
msg.receiver number to this smsbox instance.
To store the mapping and routing information, 3 hash dictionaries are
used. One that holds all connection pointers from the smsbox'es and 2
seperate dictionaries for the smsc-id and receiver number mapping.
I'd like to apply the patch. Mainly it does not change any current
behaviour, but it's still a cerious change in the bearerbox internals,
so I'd like to ask for comments or objections before going to commit
this. I have tested a lot of this, but no garantee, as always :))
Stipe
[EMAIL PROTECTED]
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf
Tel: +49-211-74845-0
Fax: +49-211-74845-299
E-Mail: [EMAIL PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are
diff -ru gateway/gw/bb_boxc.c gateway-smpp/gw/bb_boxc.c
--- gateway/gw/bb_boxc.c2002-09-06 14:03:16.0 +0200
+++ gateway-smpp/gw/bb_boxc.c 2002-09-06 21:21:16.0 +0200
@@ -40,6 +40,9 @@
static volatile sig_atomic_t wapbox_running;
static List*wapbox_list = NULL;
static List*smsbox_list = NULL;
+static Dict *smsbox_by_id = NULL;
+static Dict *smsbox_by_smsc = NULL;
+static Dict *smsbox_by_receiver = NULL;
static longsmsbox_port;
static int smsbox_port_ssl = 0;
@@ -65,6 +68,7 @@
List *retry; /* If sending fails */
List *outgoing;
volatile sig_atomic_t alive;
+Octstr *boxc_id;
} Boxc;
@@ -173,6 +177,26 @@
store_save(msg);
debug("bb.boxc", 0, "boxc_receiver: got ack");
}
+else if (msg_type(msg) == admin && msg->admin.command == cmd_identify) {
+ List *newlist;
+
+ /* and add the boxc_ud into conn for boxc_status() output */
+ if (conn->boxc_id == NULL)
+ conn->boxc_id = octstr_duplicate(msg->admin.boxc_id);
+ /*
+ * re-link the incoming queue for this connection to an independent
+ */
Re: merging smsbox and bearerbox
This is going to be a bit long mail. Background: As I have now and then announced, I (long time ago) merged smsbox and bearerbox together, to make Kannel faster, easier to program (DLR's, store-files, dynamic configurations etc.). As a part of this project, we made list of reliability improvements. The main aims of this project were: - to make Kannel as fast as possible, so that the speed _always_ depends on external things (SMSC, HTT server) speed - to make system as reliable as possible (reliable store-file, steady memory use etc.) As a result, there is extend modifications to some parts (sms services) while some are as they were (newer smsc connections, wap parts). Now the politics here at NETikos have changed (well, not the only thing that have changed) so we look forward to integrate various features to Kannel CVS tree and partake more in the project. Of course there is that problem that most of these 'improvements' are tied to that new architecture (merged smsbox) and doing them otherwise might not be possible or not worth it. So, is the merging worth it? Well I finally found time to run some benchmarks, here is results briefly (see the attachment for more results): The benchmarking was not easy thing, and it is NOT a very good one either, as the problem is how to benchmark just one thing. As the merged Kannel (our version) has in addition to that merge, a better store-file and throttle system for fakesmsc, it resulted in level results regardless what I threw to it - it did not eat the resources of the system nor slowed down. With Vanilla Kannel (fresh CVS) I have to put store-file away etc. So this benchmark not only tested the speed difference of merged smsbox and bearerbox versus separate boxes, but other parts, too. I tried to minimize the effect of other parts and thus ran several tests with various settings. Well, the full results are in the attachment. Short conclusion: It is clearly faster to use merged system. However, as a sidenote, the inter-box speed etc. are not the main issue here, unless building up a very, very special system (where there is more than 1000-2000 msg/s of incoming traffic). However, the merged system made it far more easier to implement throttle system (for incoming messages and HTTP) and improved store-file, which resulted that this merged version could handle any loads without slowing down or eating all the resources. Vanilla Kannel was killed by OS after swap ran out or it got bogged down by the store-file. But that is another store does that happen in real world or just in benchmarks :] As last words, yes we have various little bits and in upcoming weeks, we investigate how we can merge them into CVS tree and then provide patches. Hopefully as many as possible, but some might become difficult because of the above differences and limited time to do bigger modifications to make them work.. -- &kalle marjola product concept manager NETikos finland (http://www.netikos.fi) Setup: Vanilla Kannel (fresh CVS) vs. modified Kannel (merged bearer- and smsbox, throttle system to fakesmsc driver, improved HTTP) System: Linux on tabletop Linux. No store-file. Merged Kannel has better store-system. Vanilla Kannel got completely frozen if store-file was used with high incoming message traffic. --- 1. fakesmsc and bearerbox/smsbox all in same machine, sending 'nop' messages at interval of 0.0001 (1/s) (note: fakesmsc binary of own distribution. But I guess they are the same) Vanilla Kannel: (1) 2002-09-17 09:17:42 [0] INFO: fakesmsc: from first to last sent message 1.4 s, 7308.5 msgs/s 2002-09-17 09:17:42 [0] INFO: fakesmsc: from first to last received message 4.7 s, 2120.6 msgs/s (10) 2002-09-17 09:04:29 [0] INFO: fakesmsc: from first to last sent message 13.4 s, 7441.1 msgs/s 2002-09-17 09:04:29 [0] INFO: fakesmsc: from first to last received message 50.0 s, 1999.2 msgs/s NOTE: memory growth (to 25 megabytes) (100) Couldn't handle, too much memory growth. Killed by operating system. Same happened even with interval = 0.0004 (2500 msg/s) Merged Kannel: (1) 2002-09-17 07:02:09 [0] INFO: fakesmsc: from first to last sent message 1.0 s, 9864.4 msgs/s 2002-09-17 07:02:09 [0] INFO: fakesmsc: from first to last received message 2.7 s, 3711.5 msgs/s NOTE: with store-file, ~2800 msg/s (10) 2002-09-17 07:03:12 [0] INFO: fakesmsc: from first to last sent message 17.7 s, 5650.2 msgs/s 2002-09-17 07:03:12 [0] INFO: fakesmsc: from first to last received message 27.6 s, 3623.6 msgs/s NOTE: with store-file, ~2830 msg/s (100) 2002-09-17 07:08:24 [0] INFO: fakesmsc: from first to last sent message 252.8 s, 3955.7 msgs/s 2002-09-17 07:08:24 [0] INFO: fakesmsc: from first to last received message 262.7 s, 3807.2 msgs/s
Re: merging smsbox and bearerbox
Kalle Marjola wrote: > > As a result, there is extend modifications to some parts (sms services) > while some are as they were (newer smsc connections, wap parts). Now > the politics here at NETikos have changed (well, not the only thing that > have changed) so we look forward to integrate various features to > Kannel CVS tree and partake more in the project. first of all we're happy to have you back again as active contributor :) > As last words, yes we have various little bits and in upcoming weeks, we > investigate how we can merge them into CVS tree and then provide patches. > Hopefully as many as possible, but some might become difficult because > of the above differences and limited time to do bigger modifications to > make them work.. please make the patches as readable as possible, which means keep the diff files semantically together, so that every patch does change one semantical issue. I guess we should first observce the patches and then descide in the group how to handle them concerning inclusion to the official tree. BTW, we have implemented an SMPP server on Kannel's gwlib base that does connect to bearerbox as a 'smsbox'. So I'm a bit critical conerning having one big bearerbox+smsbox. But I guess the same that applied for incorporating smsbox to bearerbox may be done to our smppbox too. It's currently in experimental production state and we have been planning to make this public too in some time. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: merging smsbox and bearerbox
Hi Kalle.. wow.. ;-).. i have been wanting to either merge smsbox and bearerbox or mere smsbox with our apps... This sounds great!.. It would be great to have a list of the major differences, especially (well for me) with respect to the smsc modules and control thereof. How different are the implementations? Has Netikos kept up with the current CVS in anyway? looking forward to this nisan
Re: merging smsbox and bearerbox
> > please make the patches as readable as possible, which means keep the > diff files semantically together, so that every patch does change one > semantical issue. The main problem here is the entirely updated inner structure. This means that we talk hundreds of lines of code here, which cannot be separated that easily - for example, we cannot use improved store-file without changing message queue system. Earlier when we talked about this bearerbox/smsbox issue, one reason to have separate smsbox was to keep unstable special message things (OTA etc.) out of bearerbox, so that if they fail, bearerbox is not affected. This arises again the very question 'what should Kannel (gateway) do?' In my opinion, the gateway should: - be as reliable as possible (no memory leak, no crashing, no panics, no lost messages) - act as fast tunnel between user agents and applications - provide minimal features (API) to make it usable In this sense, gateway could have following things: - SMSC connection handling (this is the main thing wanted from it) - simple message routing to SMSCes - virtual SMSC handling (for HTTP based content gateways, external SMSC connection systems etc.) - simple message routing to external HTTP servers - simple message concatenation (or support to force used SMSC) - OPTIONAL: fixed answers for time-critical things Following things should not be there: - complicated message handling (logos, icons, ringtones, OTA,..) -> these messages should be created by other process which then uses the simple interface of the gateway - message modifications (headers, footers, etc.) - unstable drivers etc. - wap stack (seperate wapbox is good) Thus, I would move basic SMS handling to bearerbox and then leave more complicated (push etc.) things to smsbox. Like make smsbox completely stand-alone, so that it is not needed but can be used if additional features are needed. In practise, to make things work 'like they were', bearerbox would be configured to send all SMS'es to this new smsbox (maybe over HTTP?) which would then do routing/modifications, and push any replies (or return as reply to bearerbox HTTP) to bearerbox as any external application. Bearerbox would not see difference between that stand-alone smsbox and any other application, making it simpler. But this stand-alone smsbox could be provided with Kannel, to make easier to develop applications. -- &kalle marjola product concept manager NETikos finland (http://www.netikos.fi)
[FYI] smsbox routing patch commited
Hi list, I commited now Wapme's smsbox routing patch to Kannel's cvs HEAD tree. The basic idea behind the smsbox routing is that we can now route inbound messages to specific smsbox instances. bearerbox may be connected to several smsboxes, mainly for load-balancing purposes. Now as smsboxes do send MT messages everything is pretty easy and Kannel has been desgined mainly for this direction. If you write own boxes that use Kannels internal message representation and communication layer between bearerbox and smsbox, like EMI/UCP and SMPP proxys that simulare the behaviour of a real smsbox you will get into heavy problem for MO messages. bearerbox gets an message and passes it by default to a random (non identified/registered smsbox connection). Via smsbox-route groups you can tell bearerbox where you want certain messages to be routed to. I.e. you have an smppbox that is an SMPP server. It handles all the SMPP specific communication to your clients. Now you assign your clients some shortcuts numbers in certain networks, like 1 for 4 different netwoks. Now bearerbox gets the MO messages and you need to implement a switch in bearerbox that makes bearerbox know that messages with receiver number 1 should be passed to the smppbox instead of it's standard smsbox in order that smppbox may transcode the message to an deliver_sm PDU. I thing that this smsbox routing concept is very powerfull, espacially if you want to use Kannel as SMS proxying system, where you write your own protocoll boxes and use bearerbox as smsc handling aggregator. We use this at Wapme to provide customers SMPP v3.4 and EMI/UCP 4.0 server connections via our smppbox. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Mutex cygwin smsbox problem
Fogarasi Andras wrote: > > Kannel version 1.2.0 On Windows 2000 Advanced Server, using cygwin > (donwloaded from cygwin.com one and a half months ago) smsbox dies and > the following message appears in smsbox's log: > > 2002-12-06 09:46:17 [8] ERROR: System error 104: Connection reset by > peer > 2002-12-06 09:46:18 [7] PANIC: gwlib/thread.c:79: mutex_lock_real: Mutex > failure! (Called from gwlib/list.c:427:lock.) > > Do you have any idea or workaround to aviod this problem? Maybe this is > a problem with cygwin pthread, isn't it? yes, it seems to be pthread cygwin related. Unfortunatly I have no clue why this is happening. But consider pthread support on cygwin not as stable as other unix flavors. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Bug - memory leak in smsbox
The function http_queue_thread() leaks memory because the structures allocated by a call to get_receiver() are not subsequently freed. Add msg_destroy (msg); octstr_destroy (req_url); http_destroy_headers (req_headers); octstr_destroy (req_body); inside the while() loop to resolve. Paul Keogh ANAM Wireless Internet Solutions http://www.anam.com +353 1 284 7555 (wired) +353 86 234 6047 (wireless) Castle Yard, Saint Patrick's Road, Dalkey, County Dublin, Ireland
Re: AW: [RFC]: strip_blanks in smsbox
On Thu, 2001-11-15 at 14:31, Jörg Pommnitz wrote: ASCII-art won't work with a proportional font. I do not see how you can get any consistent results. :))) Not my problem. I'm just the responsable for transporting the messages. Some other guys create the messages. But the messages usually work and are nice (well, some jokes sucks like hell, but again, not my problem) Regards Jörg -Ursprüngliche Nachricht- Von: Bruno David Rodrigues [mailto:[EMAIL PROTECTED]] Gesendet am: Donnerstag, 15. November 2001 15:02 An: [EMAIL PROTECTED] Betreff: [RFC]: strip_blanks in smsbox When sending an sms, kannel do a strip_blanks to remove any cr,lf,space et all from the beginning and the end of the message. I'm trying to send some cards (messages that scroll with jokes, ascii images and others) that requires to have some spaces in the first line, and kannel "eats" them. May I change the strip_blanks to a strip_newlines, so kannel only remove the newlines (cr or lf) and leave the spaces at the beginning (I can remove the spaces at the end too). BTW: did you notice that Siemens process CR and LF as a new line and nokia ignores CR ? And that nokia 6210 eats all the spaces at the beginning of the lines, for example, 1%0A%20%202, 6210 ignores the two %20 (spaces). Grrr
Re: smsbox and mutex detailed analysis
Benjamin Lee wrote:
> 2002-02-18 05:15:28 [3] PANIC: gwlib/conn.c:174: unlock_out_real: Mutex unlock
>failed. (Called from gwlib/conn.c:793:conn_register.)
This is probably the bug I mentioned a couple of weeks ago. As I said
before, it can be fixed by changing the order of the unlock statements
at the end of conn_register, or (a cleaner way) by adding a
lock_out/unlock_out pair at the start of conn_destroy.
Btw, someone who has had problems with CPU use from HTTP requests could
try whether changing the "if (revents & POLLIN) {" line to
"if (revents & (POLLIN | POLLERR)) {" in conn.c/poll_callback affects
that. The latter is what it says in my improved version of conn.c and
I've never seen the CPU use problem, but I don't think I saw it with the
old version either, so it would be nice to know whether that fixes it.
Re: smsbox and mutex detailed analysis
Uoti Urpala wrote: > > Benjamin Lee wrote: > > > 2002-02-18 05:15:28 [3] PANIC: gwlib/conn.c:174: unlock_out_real: Mutex unlock >failed. (Called from gwlib/conn.c:793:conn_register.) > > This is probably the bug I mentioned a couple of weeks ago. As I said > before, it can be fixed by changing the order of the unlock statements > at the end of conn_register, or (a cleaner way) by adding a > lock_out/unlock_out pair at the start of conn_destroy. Ben can you try this out in your testbed and report if this fixes the problem? Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: smsbox and mutex detailed analysis
Hi List, Stipe Tolj wrote: > > Uoti Urpala wrote: > > > > Benjamin Lee wrote: > > > > > 2002-02-18 05:15:28 [3] PANIC: gwlib/conn.c:174: unlock_out_real: Mutex unlock >failed. (Called from gwlib/conn.c:793:conn_register.) > > > > This is probably the bug I mentioned a couple of weeks ago. As I said > > before, it can be fixed by changing the order of the unlock statements > > at the end of conn_register, or (a cleaner way) by adding a > > lock_out/unlock_out pair at the start of conn_destroy. > > Ben can you try this out in your testbed and report if this fixes the > problem? I had same problem when I tried to run a SMS service simulation. Uoti's patch seems to fix it. Thanks ! Aarno
Re: smsbox and mutex detailed analysis
Uoti Urpala wrote:
>
> Btw, someone who has had problems with CPU use from HTTP requests could
> try whether changing the "if (revents & POLLIN) {" line to
> "if (revents & (POLLIN | POLLERR)) {" in conn.c/poll_callback affects
> that. The latter is what it says in my improved version of conn.c and
> I've never seen the CPU use problem, but I don't think I saw it with the
> old version either, so it would be nice to know whether that fixes it.
I have tested this on our testing linux system and it seems to fix the
CPU cycling problem we had detected when accessing to bearerbox's
admin page using IE and HTTP/1.1.
Thanks Uoti for the suggestion!
I'll add the fix to current cvs.
Stipe
[EMAIL PROTECTED]
---
Wapme Systems AG
Münsterstr. 248
40470 Düsseldorf
Tel: +49-211-74845-0
Fax: +49-211-74845-299
E-Mail: [EMAIL PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are
Re: SMPP causing smsbox to crash?
What is it exactly that you are trying to do so far ? :) I have used the Kannel with SMPPSim, and it was working quite fine for me .. - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, February 22, 2002 3:00 PM Subject: SMPP causing smsbox to crash? > Hey guys, I've set up SMPPSim, and ive created the proper entries in my > kannel.conf to use it as an smsc to connect to, and all is well. it connects > and the whole 9 yards. When i send a message to it, it accepts it, and loops it > back to kannel. > > So far we're okay. > > When kannel GETS this message looped back to itself, it freaks out and crashes. > > I sent the original message (to the smsc) with > From=12345 > To=16047289785 > Text=haha > > Here is the log output from smsbox from the point of getting the message back, > and dying. (I am using cvs from 2 days ago) > > > 2002-02-22 11:54:07 [4] WARNING: No translation found for from <12345> > to <16047289785> > 2002-02-22 11:54:07 [4] ERROR: request failed > 2002-02-22 11:54:07 [4] DEBUG: message length 14, sending 1 messages > 2002-02-22 11:54:08 [4] WARNING: No translation found for from > <16047289785> to <12345> > 2002-02-22 11:54:08 [4] ERROR: request failed > 2002-02-22 11:54:08 [4] ERROR: Start marker was damaged for area 0x81bcd60 > 2002-02-22 11:54:08 [4] ERROR: Could not find area information. > 2002-02-22 11:54:08 [4] PANIC: gwlib/octstr.c:2056: seems_valid_real: Assertion > `gw_check_is_allocated(ostr)' failed. (Called from gwlib/octstr.c:252:octstr_len > > > Any help? > >
Re: SMPP causing smsbox to crash?
I set up smppsim, and im just trying to test that kannel works with SMPP. I grabbed SMPPSim and I just want to verify that sending to smppsim works, and having smppsim send back works. (smppsim is also not storing the messages it recieved in its log file either) What configuration were you using w/ smppsim and what were you trying to accomplish? >What is it exactly that you are trying to do so far ? :) >I have used the Kannel with SMPPSim, and it was working quite fine for me .. > >- Original Message - >From: <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Friday, February 22, 2002 3:00 PM >Subject: SMPP causing smsbox to crash? > > >> Hey guys, I've set up SMPPSim, and ive created the proper entries in my >> kannel.conf to use it as an smsc to connect to, and all is well. it >connects >> and the whole 9 yards. When i send a message to it, it accepts it, and >loops it >> back to kannel. >> >> So far we're okay. >> >> When kannel GETS this message looped back to itself, it freaks out and >crashes. >> >> I sent the original message (to the smsc) with >> From=12345 >> To=16047289785 >> Text=haha >> >> Here is the log output from smsbox from the point of getting the message >back, >> and dying. (I am using cvs from 2 days ago) >> >> >> 2002-02-22 11:54:07 [4] WARNING: No translation found for from ><12345> >> to <16047289785> >> 2002-02-22 11:54:07 [4] ERROR: request failed >> 2002-02-22 11:54:07 [4] DEBUG: message length 14, sending 1 messages >> 2002-02-22 11:54:08 [4] WARNING: No translation found for >from >> <16047289785> to <12345> >> 2002-02-22 11:54:08 [4] ERROR: request failed >> 2002-02-22 11:54:08 [4] ERROR: Start marker was damaged for area 0x81bcd60 >> 2002-02-22 11:54:08 [4] ERROR: Could not find area information. >> 2002-02-22 11:54:08 [4] PANIC: gwlib/octstr.c:2056: seems_valid_real: >Assertion >> `gw_check_is_allocated(ostr)' failed. (Called from >gwlib/octstr.c:252:octstr_len >> >> >> Any help? >> >>
Re: SMPP causing smsbox to crash?
Well, I was just analizing the SMPP protocol and checking the speed. Trust me, Kannel supports SMPP v 3.3 very well, I guess better than Sim runs the emulations even :) Afaik The SMPPSim does save the messages in some log file, and u can parse it if you need those .. I was running Kannel as SMPP Entity for around a year in production environment, and it was pretty stable, and very fast. - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, February 22, 2002 3:59 PM Subject: Re: SMPP causing smsbox to crash? > I set up smppsim, and im just trying to test that kannel works with SMPP. I > grabbed SMPPSim and I just want to verify that sending to smppsim works, and > having smppsim send back works. (smppsim is also not storing the messages it > recieved in its log file either) > > What configuration were you using w/ smppsim and what were you trying to > accomplish? > > > >What is it exactly that you are trying to do so far ? :) > >I have used the Kannel with SMPPSim, and it was working quite fine for me .. > > > >- Original Message - > >From: <[EMAIL PROTECTED]> > >To: <[EMAIL PROTECTED]> > >Sent: Friday, February 22, 2002 3:00 PM > >Subject: SMPP causing smsbox to crash? > > > > > >> Hey guys, I've set up SMPPSim, and ive created the proper entries in my > >> kannel.conf to use it as an smsc to connect to, and all is well. it > >connects > >> and the whole 9 yards. When i send a message to it, it accepts it, and > >loops it > >> back to kannel. > >> > >> So far we're okay. > >> > >> When kannel GETS this message looped back to itself, it freaks out and > >crashes. > >> > >> I sent the original message (to the smsc) with > >> From=12345 > >> To=16047289785 > >> Text=haha > >> > >> Here is the log output from smsbox from the point of getting the message > >back, > >> and dying. (I am using cvs from 2 days ago) > >> > >> > >> 2002-02-22 11:54:07 [4] WARNING: No translation found for from > ><12345> > >> to <16047289785> > >> 2002-02-22 11:54:07 [4] ERROR: request failed > >> 2002-02-22 11:54:07 [4] DEBUG: message length 14, sending 1 messages > >> 2002-02-22 11:54:08 [4] WARNING: No translation found for > >from > >> <16047289785> to <12345> > >> 2002-02-22 11:54:08 [4] ERROR: request failed > >> 2002-02-22 11:54:08 [4] ERROR: Start marker was damaged for area 0x81bcd60 > >> 2002-02-22 11:54:08 [4] ERROR: Could not find area information. > >> 2002-02-22 11:54:08 [4] PANIC: gwlib/octstr.c:2056: seems_valid_real: > >Assertion > >> `gw_check_is_allocated(ostr)' failed. (Called from > >gwlib/octstr.c:252:octstr_len > >> > >> > >> Any help? > >> > >> > > > > > >
Re: SMPP causing smsbox to crash?
- Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, February 22, 2002 11:00 PM Subject: SMPP causing smsbox to crash? > When kannel GETS this message looped back to itself, it freaks out and crashes. > > I sent the original message (to the smsc) with > From=12345 > To=16047289785 > Text=haha > > Here is the log output from smsbox from the point of getting the message back, > and dying. (I am using cvs from 2 days ago) > > > 2002-02-22 11:54:07 [4] WARNING: No translation found for from <12345> > to <16047289785> > 2002-02-22 11:54:07 [4] ERROR: request failed > 2002-02-22 11:54:07 [4] DEBUG: message length 14, sending 1 messages > 2002-02-22 11:54:08 [4] WARNING: No translation found for from > <16047289785> to <12345> > 2002-02-22 11:54:08 [4] ERROR: request failed > 2002-02-22 11:54:08 [4] ERROR: Start marker was damaged for area 0x81bcd60 > 2002-02-22 11:54:08 [4] ERROR: Could not find area information. > 2002-02-22 11:54:08 [4] PANIC: gwlib/octstr.c:2056: seems_valid_real: Assertion > `gw_check_is_allocated(ostr)' failed. (Called from gwlib/octstr.c:252:octstr_len The PANIC is a bug in request_failed message and I've corrected it now in CVS. The "No translation" is another problem
AW: AW: Kannel and M20 smsbox
Hi Daniele, I'm not sure but, I mean your problem was discussed earlier in the list, see http://www.mail-archive.com/cgi-bin/htsearch?method=and&format=short&config= users_kannel_3glab_org&restrict=&exclude=&words=siemens+m20 All I kwow is that the Siemens M20 have some bugs. BTW. It would be nice, if you can send a copy to [EMAIL PROTECTED] or [EMAIL PROTECTED], so that we can discuss the problem in the list. More eyes more answers ! Bjoern kind regards Vodafone TeleCommerce GmbH Architecture & Engineering Bjoern Buettner Daniel Goldbach Str. 17-19 40880 Ratingen Tel. +49 (0) 21 02 / 97 20 13 Fax +49 (0) 21 02 / 97 15 14 mailto:[EMAIL PROTECTED] www.vodafone.com www.vodafone-telecommerce.de > -Ursprüngliche Nachricht- > Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Gesendet: Dienstag, 26. Februar 2002 17:49 > An: [EMAIL PROTECTED] > Betreff: Re: AW: Kannel and M20 smsbox > > > Hi! > I was trying to send a message with text 'Hi Steve' to my telephone, > and this is all the infos I can get. > That comes from the access.log file: > > 2002-02-26 15:22:22 FAILED Send SMS [SMSC:siemens] > [from:123] [to:3287597573] [msg:Hi Steve] > > This from the smsbox shell: > > 2002-02-26 14:22:19 [3] INFO: smsbox: Got HTTP request > from <127.0.0.1> > 2002-02-26 14:22:19 [3] INFO: /cgi-bin/sendsms > sender: (127.0.0.1) to:<3287597573> > msg: > 2002-02-26 14:22:19 [3] DEBUG: Answer: > 2002-02-26 14:22:19 [3] DEBUG: HTTP: Destroying > HTTPClient area 0x81a6f10. > > This last from the bearerbox: > > 2002-02-26 14:22:19 [9] DEBUG: boxc_receiver: sms > received > 2002-02-26 14:22:19 [7] DEBUG: smscconn_sender (AT: > /dev/ttyS0): sending message > 2002-02-26 14:22:19 [7] DEBUG: TP-Validity-Period: > 24.0 hours > 2002-02-26 14:22:19 [7] DEBUG: AT: Command: AT+CMGS=20 > > 2002-02-26 14:22:19 [7] DEBUG: AT: Command: > 0011000A8123789557371FF1A708C834684A2FDBCB > > 2002-02-26 14:22:22 [7] DEBUG: send command status: -1 > 2002-02-26 14:22:22 [7] DEBUG: smsc_wrapper /dev/ttyS0>: reconnect started > 2002-02-26 14:42:12 [6] ERROR: read device file > 2002-02-26 14:42:12 [6] ERROR: System error 11: > Resource temporarily unavailable > 2002-02-26 14:22:19 [3] DEBUG: HTTP: Destroying > HTTPClient for `127.0.0.1'. > > Thanks > > Daniele > > > Have you any debug msg. ? > > > > Bjoern > > > > kind regards > > > > Vodafone TeleCommerce GmbH > > Architecture & Engineering > > Bjoern Buettner > > Daniel Goldbach Str. 17-19 > > 40880 Ratingen > > > > Tel. +49 (0) 21 02 / 97 20 13 > > Fax +49 (0) 21 02 / 97 15 14 > > > > mailto:[EMAIL PROTECTED] > > www.vodafone.com > > www.vodafone-telecommerce.de > > > > > > > - > This Mail has been checked for Viruses > Attention: Encrypted mails can NOT be checked! > > ** > > Diese Mail wurde auf Viren geprueft > Hinweis: Verschluesselte mails koennen NICHT auf Viren geprueft werden! > - >
[BUG] Smsbox crash with empty messages
I just love CVSWEB and checking-malloc;) smsbox panics on smsbox line 1180 because of a empty text field (NULL): http://www.kannel.3glab.org/cgi-bin/viewcvs.cgi/gateway/gw/smsbox.c? annotate=1.174#1180 In patch 1.164 at 2002/01/25: udh == NULL ? ( text == NULL ? "" : octstr_get_cstr(text) ) : "<< UDH >>"); udh == NULL ? ( text == NULL ? "" : octstr_get_cstr(text) ) : octstr_get_cstr(text)); Why ?! I'm reverting this line -- Davi
Re: wait_for_connections fails and kills smsbox
On Wed, 2002-05-01 at 17:07, Alex Judd wrote: > Interesting problem using latest cvs (with CMTI patch) is that > occassionally the wait_for_connections process fails and takes the smsbox > with it. > > Looks like the process fails to read from the serial port (either due to > the phone or some other random process on my machine) and this takes the > smsbox down (which I don't think it should do). Anyone fixed this? > If bearerbox goes down, wapbox and smsbox goes too. If bearerbox cannot reach a smsc, it goes down too, UNLESS: set "retry = true" on at2 smsc group (and I'd advise you to use it in every smsc group) to force kannel to reopen at2 connection. If you want to "ping" the modem and keep the connection alive, set "keepalive = 60" (seconds) too and if you have motorola manual (or try yourself and tell us if it works), set keepalive-cmd = "AT+CBC;+CSQ" on modems.conf, near your groups=modems, id=motorola (uhm, I don't see any motorola, which at group are you using) keepalive in smsc group tells for how many seconds will kannel send the keepalive-cmd, and that keepalive command tells: +CBC: 1,100 +CSQ: 15,0 1=on power (0 for batery, I think) 100 = batery level 15 = signal level (see 3gpp 27005 or 27007) 0 is signal quality, but I haven't yet seen anything else than 0 > Alex > > 2002-05-01 09:53:05 [5] DEBUG: AT2[Motorola1]: <-- OK > 2002-05-01 13:50:17 [4] ERROR: wait_for_connections failed > 2002-05-01 13:50:17 [5] ERROR: AT2[Motorola1]: error on select > 2002-05-01 13:50:17 [5] ERROR: System error 13: Permission denied > 2002-05-01 13:50:17 [4] ERROR: System error 13: Permission denied > 2002-05-01 13:50:17 [5] WARNING: gwthread_sleep: error in poll > ... > 2002-05-01 13:50:18 [5] WARNING: gwthread_sleep: error in poll > 2002-05-01 13:50:18 [5] WARNING: System error 13: Permission denied > 2002-05-01 13:50:18 [5] ERROR: AT2[Motorola1]: error on select > 2002-05-01 13:50:18 [5] ERROR: System error 13: Permission denied > 2002-05-01 13:50:22 [0] ERROR: Error reading from fd 18: > 2002-05-01 13:50:22 [0] ERROR: System error 104: Connection reset by peer > 2002-05-01 13:50:22 [0] ERROR: Error reading from fd 18: > 2002-05-01 13:50:22 [0] ERROR: System error 104: Connection reset by peer > 2002-05-01 13:50:22 [0] INFO: Error reading from bearerbox, disconnecting > 2002-05-01 13:50:22 [0] INFO: Received (and handled?) 2 requests in 72512 seconds >(0.00 per second) > 2002-05-01 13:50:22 [0] INFO: Kannel smsbox terminating. > 2002-05-01 13:50:22 [6] DEBUG: Thread 6 (gw/heartbeat.c:heartbeat_thread) terminates. > 2002-05-01 13:50:23 [0] DEBUG: Waiting for 2 (gwlib/http.c:server_thread) to >terminate > 2002-05-01 13:50:23 [2] WARNING: gwthread_sleep: error in poll > 2002-05-01 13:50:23 [2] WARNING: System error 13: Permission denied > -- > Alex Judd > http://www.skywire.co.uk > >
Re: wait_for_connections fails and kills smsbox
Thanks Bruno - good to see your full name is now on your emails :) > set "retry = true" on at2 smsc group (and I'd advise you to use it in > every smsc group) to force kannel to reopen at2 connection. > > If you want to "ping" the modem and keep the connection alive, > set "keepalive = 60" (seconds) too and if you have motorola manual > (or try yourself and tell us if it works), set > keepalive-cmd = "AT+CBC;+CSQ" > on modems.conf, near your groups=modems, id=motorola (uhm, I don't see > any motorola, which at group are you using) See my patch earlier (+CMTI support) which includes the new group for the Motorola P7389i and support for it to be added to CVS (unless someone has done already???). I guess here we could use something really simple like an ATI4 or similar as a 'do something' comand however your battery level one is quite nice. Alex -- Alex Judd http://www.skywire.co.uk
Re: wait_for_connections fails and kills smsbox
On Fri, 2002-05-03 at 10:58, Alex Judd wrote: > Thanks Bruno - good to see your full name is now on your emails :) > > > set "retry = true" on at2 smsc group (and I'd advise you to use it in > > every smsc group) to force kannel to reopen at2 connection. > > > > If you want to "ping" the modem and keep the connection alive, > > set "keepalive = 60" (seconds) too and if you have motorola manual > > (or try yourself and tell us if it works), set > > keepalive-cmd = "AT+CBC;+CSQ" > > on modems.conf, near your groups=modems, id=motorola (uhm, I don't see > > any motorola, which at group are you using) > > See my patch earlier (+CMTI support) which includes the new group for the > Motorola P7389i and support for it to be added to CVS (unless someone has > done already???). > > I guess here we could use something really simple like an ATI4 or similar > as a 'do something' comand however your battery level one is quite nice. If keepalive is set, kannel would just send 'AT', because it's the default "keepalive command" but you can change it on modems.conf. I'm using those commands because sometimes my modem got out of network and I needed to reset it. I was thinking in using those values to do a automatic reset patch, but the modem no longers gets out of network and I forgot about the patch... > > Alex > > -- > Alex Judd > http://www.skywire.co.uk > >
Re: DLRmask 1, smsbox crashesh (CIMD2)
> 2002-06-04 17:15:46 [4] INFO: Starting delivery report from > <5678> > 2002-06-04 17:15:46 [4] PANIC: gwlib/octstr.c:275: octstr_copy_real: > Assertion `len >= 0' failed. there seems to be an assertion checking failing while an octstr_duplicate() call is called with a NULL argument, IMO. Please try to track this down. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [PATCH] internal bearerbox <-> smsbox routing
Hi Stipe. Wow..this sounds really usefull.. I can already use it, but I think we should have it as a separate patch for now, the CVS is relatively stable, and this is quite a big internal change. I would be happy to try it on our dev servers. nisan At 09:58 PM 9/6/02 +0200, Stipe Tolj wrote: >Hi all, > >attached is a patch that I developed today for internal smsbox routing >inside bearerbox. The patch is quite big, so I'll try to explain what >the intention is and what it does. > >Basically currently any sms that arrives at bearerbox via a specific >thread of a specific smsc module is produced to a global queue >(incoming_sms). All connected smsbox'es do grap a msg from that queue >all process it. This mechanism is basically used to load-balance msg >traffic to various smsbox'es. > >However, sometimes it may be desireable for various reasons to be able >to "route" the sms msg to a specific smsbox. This has to be done >inside bearerbox, between the smsc module layer and the communication >to the smsbox'es. > >First, bearerbox needs to know about smsboxes in a way that is >semantically more relevant. We know the IP of the smsbox and even a >local file descriptor, but that's not enough. Imagine a smsbox sending >a DLR-requesting msg. Not smsbox(1) sends msg to bearerbox, bearerbox >holds the dlr queue, receives the report from the smsc module and now >does not know if it should route to smsbox(1) or smsbox(2). Now >basically in this easy scenario it does not matter, because each >smsbox instance does "only" a URL lookup. But think of a SMPP proxying >box that has own state tables and reports have to be re-routed exactly >to that instance to update status tables. > >Ok, here is how the thing works: > > * gw/smsbox.c: graps a 'smsbox-id' from it's config group and sends >an admin msg identifying itself with a id to bearerbox > * gw/bb_boxc.c: when an admin msg is received by an identicying >smsbox, the incoming queue is switched to a private list, so that no >other smsbox shares the same list with the new identified smsbox > * gw/msg.h: adding a boxc_id Octstr to type sms to hold the >smsbox-id while transporting msg from smsbox'es to bearerbox > * gw/dlr.c: adding a boxc_id parameter to the dlr_add() abstraction >layers and to the relecant smsc_foobar.c modules > * the message went out of the smsc module door > * the delivery report comes in > * gw/dlr.c: dlr_find() inserts the remembered boxc_id to the msg >structure and passes it through the smsc module to gw/bb_smscconn.c > * gw/bb_smscconn.c: gets all incoming sms from the smsc modules and >calls the new gw/bb_boxc.c:route_incoming_sms() routine to descride to >while list this msg is produced and hence to which smsbox the msg is >routed > >The smsbox routing is defined in the configuration file via the >multi-grou "smsbox-route", like this > > group = smsbox-route > smsbox-id = smsbox_1 > smsc_ids = "fake_1;fake_2;fake_3" > shortcuts = "83444;83555" > >which means route any message coming from the smsc-id's or >msg.receiver number to this smsbox instance. > >To store the mapping and routing information, 3 hash dictionaries are >used. One that holds all connection pointers from the smsbox'es and 2 >seperate dictionaries for the smsc-id and receiver number mapping. > >I'd like to apply the patch. Mainly it does not change any current >behaviour, but it's still a cerious change in the bearerbox internals, >so I'd like to ask for comments or objections before going to commit >this. I have tested a lot of this, but no garantee, as always :)) > >Stipe > >[EMAIL PROTECTED] >--- >Wapme Systems AG > >Vogelsanger Weg 80 >40470 Düsseldorf > >Tel: +49-211-74845-0 >Fax: +49-211-74845-299 > >E-Mail: [EMAIL PROTECTED] >Internet: http://www.wapme-systems.de >--- >wapme.net - wherever you arediff -ru gateway/gw/bb_boxc.c >gateway-smpp/gw/bb_boxc.c >--- gateway/gw/bb_boxc.c2002-09-06 14:03:16.0 +0200 >+++ gateway-smpp/gw/bb_boxc.c 2002-09-06 21:21:16.0 +0200 >@@ -40,6 +40,9 @@ > static volatile sig_atomic_t wapbox_running; > static List*wapbox_list = NULL; > static List*smsbox_list = NULL; >+static Dict *smsbox_by_id = NULL; >+static Dict *smsbox_by_smsc = NULL; >+static Dict *smsbox_by_receiver = NULL; > > static longsmsbox_port; > static int smsbox_port_ssl = 0; >@@ -65,6 +68,7 @@ > List *retry; /* If sending fails */ > List
Re: [PATCH] internal bearerbox <-> smsbox routing
Nisan Bloch wrote: > > Hi Stipe. > > Wow..this sounds really usefull.. I can already use it, but I think we > should have it as a separate patch for now, the CVS is relatively stable, > and this is quite a big internal change. I would be happy to try it on our > dev servers. ok, how about checking if recent new features and bug fixes from 1.2.0 stable to now are ok. They seem to be, since no one complains :)) and then release 1.2.1 stable before doing this smsbox routing patch to cvs?! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [FYI] smsbox routing patch commited
forgot to say: of course the smsbox routing is an added feature, which means the standard default behaviour has *not* changed. If your smsbox does not identify itself via the 'smsbox-id' directive to bearerbox and there are no 'smsbox-route' group in your configuration everything stays the same. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [FYI] smsbox routing patch commited
That's very cool Stipe. I've been working here with creating an SMPP listener in order to allow peering and the routing changes work nicely with that. Has anyone commited an SMPP listener to the group yet? Alex - Original Message - From: "Stipe Tolj" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, November 14, 2002 2:43 AM Subject: Re: [FYI] smsbox routing patch commited > forgot to say: > > of course the smsbox routing is an added feature, which means the > standard default behaviour has *not* changed. > > If your smsbox does not identify itself via the 'smsbox-id' directive > to bearerbox and there are no 'smsbox-route' group in your > configuration everything stays the same. > > Stipe > > [EMAIL PROTECTED] > --- > Wapme Systems AG > > Vogelsanger Weg 80 > 40470 Düsseldorf > > Tel: +49-211-74845-0 > Fax: +49-211-74845-299 > > E-Mail: [EMAIL PROTECTED] > Internet: http://www.wapme-systems.de > --- > wapme.net - wherever you are
Re: [FYI] smsbox routing patch commited
> I've been working here with creating an SMPP listener in order to allow > peering and the routing changes work nicely with that. Has anyone commited > an SMPP listener to the group yet? we have a full fleadged SMPP v3.4 and EMI/UCP 4.0 server here using Kannel's sources (libgwlib and libgw) as code base. It will be commited to Kannel as soon as we have negotiated some things. But *please* don't send me requests for it. It's currently property of Wapme and hence I won't send someone the sources or even binaries. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
