Thanks. It worked. However, I am facing more issues. I have 6 LAs, and am supposed to enable 3 sessions per LA each (total 18). As advised, I replicated 3 similar configurations of 'group=smsc' part. LA connectivity is established as soon as I switch on bearerbox. But SMSC does not seem to like too much connection triggering at one time against one LA. It randomly establishes any one, two or sometimes all three instances of same LA for successful connectivity. The non-connected LA remain in the 're-connecting' state forever, throwing following error:
2010-07-27 21:59:26 [19881] [8] WARNING: SMPP: PDU NULL terminated string (system_id) has no NULL. 2010-07-27 21:59:26 [19881] [8] ERROR: SMPP[polling616]: SMSC rejected login to transmit, code 0x0000000d (Bind Failed). 2010-07-27 21:59:26 [19881] [8] ERROR: SMPP[polling616]: I/O error or other error. Re-connecting. 2010-07-27 21:59:26 [19881] [8] ERROR: SMPP[polling616]: Couldn't connect to SMS center (retrying in 60 seconds). This error keeps coming at every retry attempt for the reconnecting sessions. I did some hit and trial for bearerbox restarting and discovered that the behaviour is totally random. I have clear confirmation from the operator that multiple sessions are allowed on SMSC, and there are times when by luck, bbox restart logs in all sessions for one LA successfully, so the problem might not be on SMSC end. I am not sure how to handle this. Is this issue because of concurrent login attempts by all 3 sessions of same LA with same credentials? Can I introduce some time-delay in the first attempt of LA binding? Currently they all get connected as soon as I start bbox. Thanks, Hamza On Tue, Jul 27, 2010 at 12:20 PM, Konstantin Vayner <[email protected]>wrote: > Set up multiple group = smsc groups with same credentials. > > Note that you should have them all defined with same smsc-id to avoid DLR > issues (because kannel uses smsc-id as part of the key for dlr lookup, and > since you're using same account, the remote smsc may send the DLRs over any > of the active connections). > > If you're running SVN, then you have a separate configuration option > "smsc-admin-id" , which you can use to tell the connections apart (this is > used in administration interface to check status and/or start/stop certain > smscs). > If you're running a stable version (1.4.3), then you dont have this > separate option and will only be able to control them altogether. > > Regards, > Konstantin > > > On Tue, Jul 27, 2010 at 10:08 AM, [email protected] <[email protected]> wrote: > >> Hi, >> >> How can I establish multiple sessions with same LA in kannel config, given >> the operator SMSC is configured for this? Far-end is Acision SMSC over SMPP >> 3.4. >> >> Thanks, >> >> Hamza >> > >
