Angel Fradejas wrote: > > Stipe Tolj wrote: > > >* at least sync behaviour of smsc modules for re-connect behaviour and > >pull corresponding config directive flags to upper smscconn layer. > > I have already sent a patch to make reconnection configuration and behaviour > for EMI2 the same as SMPP. You have to vote on it still. > > If I get positive votes about the way it's done, I can take the handling of > directives up to smsconn.c > > I also would like to reconvert CIMD2 driver to SMSCConn* api before new > release. So I'll take Kalle's work on this issue and update it to current > CVS, and make its config/behaviour consistent with SMPP/EMI2.
yep, I'll check your patch and vote. > >* enable smsbox to use the new 'strict'ness option, so that it waits > >for the ACK/NACK of bearerbox and replies correspondigly in it's HTTP > >reply for the sendsms interface. > > I suggest here 3 behaviours: > > 1) Default: if nothing is stated, make this the same as they are now, for > compatibility reasons. > 2) Config: introduce a smsbox config directive "strict=yes/no". "No" is the > current behaviour, "Yes" would be take into account the ack/nack from > bearerbox to return a significative http status. > 3) sendsms: whatever the default or config beahaviour is, allow to change it > on every MT by adding an "&strict=" url parameter. If not given, fallback to > config/default behaviour. > > That would make things compatible with existing kannel.conf files. yep, +1, as discusted while having some great fajitas ;)) 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
