RE: Problem with SM routing ?

ok - more info : I added lots of debug() calls to smsc2_rout, and I
found that it does not send the messages to the SMSC modules because it
doesn't think they are active ! and apparently they are not. for some
reason gwthread_create() succeeds, but the threads it create never get
woken up. I went and changed my start() callback to call gwthread_wake()
on the module's main thread, before exiting and now it sorta works, but
the fake smsc still doesn't. 
It only "sorta" works because I added a debug() call in my wait/busy
loop and I don't get as much junk in the logs as ought to be. I think
that gwthread_sleep() does not return unless someone calls
gwthread_wakeup() on it (which is what the add_msg() call back does).
very weird...

I still don't know why it happens - on other computers it works A-OK. 
all the computers in question are Mandrake Linux 7.1 (kernel
2.4.something).

Oded Arbel
m-Wise Inc.
[email protected]

--
Hlade's Law:
If you have a difficult task, give it to a lazy person - they will find
an easier way to do it.


> -----Original Message-----
> From: Oded Arbel 
> Sent: Tuesday, February 26, 2002 6:14 PM
> To: Kannel-devel (E-mail)
> Subject: Problem with SM routing ?
> 
> 
> Hi list.
> 
> when testing a module I'm writing, I sometime get this weird 
> behaviour :
> when I send messages, I see this in the logs :
> 
> 2002-02-26 15:54:44 [7] DEBUG: boxc_receiver: sms received
> 2002-02-26 15:54:44 [6] DEBUG: sms_router: time to sleep
> 2002-02-26 16:03:37 [7] DEBUG: boxc_receiver: sms received
> 2002-02-26 16:03:45 [7] DEBUG: boxc_receiver: sms received
> (these are three messages sent. sometimes I get "time to sleep" after
> each message sent)
> 
> but no message reaches the module. I couldn't manage to reproduce this
> behaviour under a debugger, and on the machine that I'm debugging it
> happens from time to time, but not a lot. now I started to test on a
> remote computer, and there it always happens - I can't make is send
> messages. unfortunatly, I don't have a debugger on the remote machine.
> why doesn't it send the messages to the module ?
> 
> here is my config file
> 
> group = core
> admin-port = 14500
> smsbox-port = 14501
> admin-password = bar
> box-deny-ip = "*.*.*.*"
> box-allow-ip = "127.0.0.1"
> log-file = "/gw/logs/kannel.log"
> access-log = "/gw/logs/kannel-access.log"
> log-level = 0
> 
> ########TRANSMITTERS########
> 
> group = smsc
> smsc = fake
> smsc-id = cd
> port = 25100
> 
> group = smsc
> smsc = soap
> smsc-id = ab
> <some module specific configuration snipped>
> 
> #########SMSBOX-CONFIG########
> 
> group = smsbox
> bearerbox-host = localhost
> sendsms-port = 14503
> log-level = 0
> log-file = "/gw/logs/smsbox.log"
> access-log = "/gw/logs/smsbox-access.log"
> global-sender = 1
> 
> ###########SERVICES##########
> 
> group = sms-service
> keyword = default
> url="http://localhost/interface/mo.php?text=%a&from=%p&to=%P&time=%t"
> max-messages=0
> 
> #####SEND-SMS USERS##########
> 
> group = sendsms-user
> username = tester
> password = foobar
> default-smsc = ab
> 
> I'd appreciate any pointers guys :-)
> 
> Oded Arbel
> m-Wise Inc.
> [email protected]
> 
> --
> "A doctor can bury his mistakes but an architect can only advise his
> clients to plant vines."
> 	-- Frank Lloyd Wright
> 
>