Maybe you've set "bearerbox-host" in the sms-group and it was pointing to the old machine.
On Fri, Jun 12, 2009 at 9:09 AM, <[email protected]>wrote: > The computer was on the network. It is just that the SMSC blocks the > port in question to users who aren't of pre-approved IPs. As for smsbox > being somehow started, I am the only one using that computer, and I haven't > started it (smsbox) in at least two weeks. Also, I never definately never > configured any routing options. And also, according to bearerbox logs > nothing was sent. All I see is it confirming its connection about every 5 > minutes. This doesn't at all account for the messages which were being sent > every few seconds, according to SMSC. (I'm not entirely convinced that > there isn't some exaggeration on their part) > > > > Thanks for your reply > > > > J > > > > *From:* Nikos Balkanas [mailto:[email protected]] > *Sent:* Friday, June 12, 2009 8:45 AM > *To:* von Gunten-Hinke Jessica, SCS-NIT-NIO-SE-ISC; [email protected] > *Subject:* Re: smsc bombardment without smsbox running > > > > Hi, > > > > The only thing that I can think of, is that an *smsbox* (or SQLbox) got > active somehow. I mean, you were sure that no network access was to the > SMSc, and yet there was. How difficult would be to start smsbox? Propably > someone needed to use it and enabled the network and smsbox. > > The only configuration without smsbox that can enable that (provifed that > network exists) are the reroute & reroute-smsc-id options in the smsc group. > > > > These problems can best be diagnosed while still active, i.e. without > rebooting/restarting application or server. To find out you need to look at > the bearerbox logs (access +application) and see where bearerbox got SMS > from. > > > > > > BR, > > Nikos > > ----- Original Message ----- > > *From:* [email protected] > > *To:* [email protected] > > *Sent:* Friday, June 12, 2009 9:16 AM > > *Subject:* smsc bombardment without smsbox running > > > > Hi All, > > > > I have a strange situation. > > > > I set up kannel. It was a functional setup but it was on a computer whose > IP didn't have access to my SMSC's port. > > > > Later I made the "real" setup on another computer and more or less > abandoned the other. > > > > Bearerbox remained set to start at boot on the original computer, but not > smsbox. The computer had been rebooted a number of times, so there is no > reason to think smsbox was still running,since there was no one to turn > start it. Regardless the SMSC has called and said they are being bombarded > with SMSs, which they are rejecting, which are originating from the original > computer's IP. I really don't understand how this could be, since smsbox > wasn't started, and no one has tried to send SMSs from it. > > > > Does anyone know of a scenario which could explain this, due to > configurations otherwise? > > > > TIA > > > > J > > > >
