Hi list, this is informative and also a COMPATIBILITY BREAKER!
We have moved the smsc group config directive 'reconnect-delay' which was used mainly for SMPP and SM/ASI to the higher abstraction SMSCConn layer, so all SMSC modules can benefit from this. Which means within AT2 and EMI2 there is *no longer* a 'retry' smsc group directive and there is *no longer* an exponential back-off behaviour for reconnecting to the SMSC links. They are now using also the 'reconnect-delay' that you give within the smsc group. Which also means they will *alway* try to reconnect, unless you don't set the link to 'dead' state or choose a very high 'reconnect-delay'. Can anyone please try the current cvs tree on their SMSC links and check if the reconnecting behaviour acts as expected. It should. 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
