Steve Rapaport wrote: > > >* bearerbox MUST be able to start with some (up to all) smsc connections > >failing and startup and should constantly retry to connect. that should > >probably resolved not on smsc level, but higher, to be global and > >systematic. emi2 and smpp seems to be ok, but cimd2 fails to start if cannot > >connect to smsc. why, you might ask? well .. I have a setup now where I have > >currently 11 smsc connections over internet and You can imagine that some > >network problems are often to occur, but a failing smsc must not prevent > >whole system from starting. > > Totally agreed, and this has been discussed before, but I don't know > what decisions resulted. Anyone?
start of bearerbox without termination on initial error should be supported, agreed. BTW, we have 32 SMSC links on one system. So you may be aware that we know about such issues. > >* as I have connections to smsc's in different countries, the number > >normalization does not work. I propose to rewrite unified-prefix and number > >normalization so that it would be based on smsc, assuming that a message in > >smsc2_rout() have it's smsc_id field filled. maybe a new config group - > >country - should be introduced, which will hold the number prefix > >normalization and all smsc's have a config param 'country' pointing to the > >country group. > > Very good idea. Again I'm surprised it hasn't been done already. smsc specific normalization has been suggested, we should put this up to the TODO file anyway now. > >* adding and reconfiguring smsc connections should be possible without > >restarting whole system. > > +1 on that! At the very least, a HUP signal should force a re-read of > the config file. hmmm, yep, HUP'ing bearerbox should be initiating a re-read of the config file. But hence we have to shutdown all connections previously and bring all connections up again. ?? Maybe this is not what certain users want? We got smsc specific shutdown and restart available now via the admin HTTP commmands. > >* another idea, not very clear, however .. I have several connections to > >every smsc - because there are different numbers available for clients - and > >I have several operators - for example in estonia 3 operators and 3 > >numbers - maybe a new parameter for smsc needs to be introduced - let's call > >it service-group for now, which will bind together (ie have same value) for > >all smsc connetions with similar service number. and then it should be > >easily possible to add option to enable routing only within the service > >groups. hmm, you want to group single connections logically to one, right?! Ok, let's assume you have smsc-id = A,B,C all from one logical operator, then you can use within the sendsms HTTP call a GET variable smsc=operator and define within earch of the 3 smsc groups a allowed-smsc-id = "operator". Hence you can "address" smsc-ids which are actually not defined within the config file. This way you can group smsc connections to one logically. 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
