yep, thats what i use...
for example: group = smsc smsc = smpp smsc-id = smsc1 ... allowed-smsc-id = smsc1 group = smsc smsc = smpp smsc-id = smsc2 ... allowed-smsc-id = smsc2 and then when passing message to sendsms add &smsc=smsc1 or &smsc=smsc2 works fine for me On Wed, Jun 23, 2010 at 12:44 PM, Latitude Berlin <latitude.de@ googlemail.com> wrote: > Hi Konstantin, > > And you use ..&smsc=<CONN_NAME>? > I tired this too but didn't work for me. > > Cheers. > > > On Wed, Jun 23, 2010 at 11:36 AM, Konstantin Vayner <[email protected]>wrote: > >> I actually prefer using "allowed-smsc-id" (set to self - or name you give >> to group of smscs that should be balanced between...) in such cases, >> especially when there are a lot of links defined >> >> Regards, >> Konstantin >> >> >> On Wed, Jun 23, 2010 at 12:32 PM, Latitude Berlin <latitude.de@ >> googlemail.com> wrote: >> >>> Hi, >>> >>> I have configured kannel to send SMS via SMPP with 2 groups defined. As I >>> understand, Kannel does load balancing itself and choses one of the >>> configured to send out SMS. >>> >>> I am sending bulk of messages and want to use only connection1. I did this >>> the following way: >>> >>> >>> kannel.conf >>> --------------------------- >>> # SMSC SMPP >>> group = smsc >>> smsc = smpp >>> smsc-id = conn1 >>> ... >>> denied-smsc-id = conn2 >>> >>> # SMSC SMPP >>> group = smsc >>> smsc = smpp >>> smsc-id = conn2 >>> >>> >>> >>> >>> >>> ... >>> denied-smsc-id = conn1 >>> >>> >>> HTTP send req: >>> -------------------- >>> ...&smsc=conn1 >>> >>> My question is that whether denied-smsc-id … is really required? If I >>> don't add this, I see kannel ignoring my ...&smsc=conn1request and >>> crossing the SMSC group itself. >>> Regards. >>> >>> >> >
