Well I had hoped that my carrier would let me slide on this, but it's not an option. It seems to me that this should be a bug... if the system-type is wrong, then kannel should fail the same way it does a bad password. As it is now the example Rene outlined below is not what it does. It retries...
I created Bug #559 to track this. If you disagree or think this should not be the case please let me know. Thanks, Roy From: Rene Kluwen [mailto:[email protected]] Sent: Monday, August 23, 2010 11:04 AM To: Roy Walker; 'Alejandro Guerrieri' Cc: [email protected] Subject: RE: System-Type retrying on failure I think it depends on what the smsc returns as an error code. If system-type is wrong and smsc returns 0x0d (13) then it is considered "wrong credentials" and afaik, Kannel doesn't retry. == Rene From: [email protected] [mailto:[email protected]] On Behalf Of Roy Walker Sent: Monday, 23 August, 2010 17:45 To: Alejandro Guerrieri Cc: [email protected] Subject: RE: System-Type retrying on failure Should this be opened as a feature request or bug report...? Seems like a decision one way or the other... change it or make it configurable. From: Alejandro Guerrieri [mailto:[email protected]] Sent: Friday, August 20, 2010 4:30 PM To: Roy Walker Cc: [email protected] Subject: Re: System-Type retrying on failure That depends on which carrier do you ask, but yes I agree, many of them require system-type to be treated as a "fatal" error and not retried. Imho should be a configurable option or a compile switch at least. Regards, Alex On Fri, Aug 20, 2010 at 10:27 PM, Roy Walker <[email protected]<mailto:[email protected]>> wrote: Found what some might consider a bug, but when an invalid system-type is passed on an SMPP bind, it will retry based on the reconnect-delay setting. This should be a stop failure and should work the same as an invalid smsc-username/system-id or smsc-password. Where it does not retry... right? Roy
