Won't it cause severe log issues in various files, since smsc-id is the only field differentiating different connections? All the incoming keywords and routing would also get messed up if all connections are names as same smsc-id...?
On Mon, Sep 13, 2010 at 9:23 PM, Rene Kluwen <[email protected]> wrote: > You can use forced-smsc = A but give your two SMSC connections the same > smsc id (e.g. smsc-id = A in group = smsc). > > > > == Rene > > > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *[email protected] > *Sent:* Monday, 13 September, 2010 17:49 > *To:* kannel users > *Subject:* Load-balancing for outgoing SMS > > > > Hi, > > > > I have 2 SMSC connections with an operator, A and B. I need to use both of > these connections to send outgoing SMS-MT. My sendsms-user configuration is > following: > > > > group = sendsms-user > > username = 710user > > password = 710pass > > forced-smsc = A > > #default-smsc = A;B > > max-messages = 5 > > concatenation = true > > > > If I try to put any of the parameters (forced-smsc or default-smsc) to > value A;B (Example: default-smsc=A;B), bearerbox does not like it, giving me > error: > > 2010-09-13 20:22:00 DISCARDED SMS [SMSC:A;B] [SVC:710user] [ACT:] [BINF:] > [FID:] [from:710] [to:xxxxxxxxxxx] [flags:-1:0:-1:-1:-1] [msg:11:Hello > world] [udh:0:] > > > > I have tried various combinations but its not working. Need help! > > > > Hamza > > >
