Again you dont paste the complete conf file :) Core group includes the log-file parameter in order to log what happen with bearerbox. Your defined URL in sms-service will leave traces after bearerbox receives the MO SMS, whether its accessible or not (you may see "could not fetch..........." error type). Be sure to set log-level = 0
log-file filename A file in which to write a log. This in addition to stdout and any log file defined in command line. Log-file in 'core' group is only used by the bearerbox. log-file filename A file in which to write a log. This in addition to stdout and any log file defined in command line. Log-file in 'core' group is only used by the bearerbox. log-file filename A file in which to write a log. This in addition to stdout and any log file defined in command line. Log-file in 'core' group is only used by the bearerbox. On Wed, Jan 26, 2011 at 1:39 PM, Bob O'Souna <[email protected]> wrote: > I am receiving SMS's (from CustomerABC into my 'inflow' SMSC). The task is > to > receive these SMS's (via inflow) and forward them (via outflow) after > changing > the parameters of the SMS (i.e. append some commercial text etc) > > At the moment, I receive the SMS from CustomerABC and retransmit (i.e > inflow -> > outflow) without a problem. I now need to capture the SMS and change the > relevant parameters and then relay the SMS. > > sendctrlsms.php (My script) sends the SMS in the format I require (when run > from > the command line). I now need Kannel to run that script instead of sending > out > the SMS via the default Kannel sendsms > > This is my sms-service > > group=sms-service > keyword=default > name=mytrap > catch-all=true > omit-empty=true > max-messages=0 > concatenation=true > get-url="http://localhost/myscripts/sendctrlsms.php"; > > My SMSCs are as below > > group=smsc > smsc=smpp > system-type=default > transceiver-mode=1 > smsc-username=user1 > smsc-password=pass1 > smsc-id=outflow > denied-smsc-id=inflow > host=xx.xx.xx.xx > port=2978 > source-addr-ton=5 > source-addr-npi=0 > dest-addr-ton=1 > dest-addr-npi=1 > interface-version=34 > log-file=/var/log/kannel/smsc.log > log-level=0 > > group=smsc > smsc=smpp > system-type=default > transceiver-mode=1 > smsc-username=user2 > smsc-password=user2 > smsc-id=inflow > denied-smsc-id=outflow > reroute-smsc-id=outflow > host=xx.xx.xx.xx > port=5392 > source-addr-ton=5 > source-addr-npi=0 > dest-addr-ton=1 > dest-addr-npi=1 > interface-version=34 > log-file=/var/log/kannel/smsc.log > log-level=0 > > > When CustomerABC sends me an SMS, there is no trace of anything in the > Kannel > log files at all. log_level is 0 throughout. The only proof that I have to > indicate that the SMS came through is my kannel.access file ie > > 2011-01-26 08:26:34 Receive SMS [SMSC:inflow] [SVC:] [ACT:user2] [BINF:] > [FID:] > [META:?smpp?] [from:+1234567890] [to:+1987654321] [flags:-1:0:-1:0:-1] > [msg:17:Hello] [udh:0:] > 2011-01-26 08:26:35 Sent SMS [SMSC:outflow] [SVC:] [ACT:user2] [BINF:] > [FID:] > [META:?smpp?] [from:+1234567890] [to:+1987654321] [flags:-1:0:-1:0:-1] > [msg:17:Hello] [udh:0:] > > Can you help so that sms-service's get-url traps the incoming message so > that I > can preprocess, before sending it out? > > >
