Hi, there is a possibility to achieve what you need to use dead-start directive for SMSC-R and get url:
http://localhost:13001/start-smsc?smsc=SMSC-R&password=pass when disconnection happens. To stop it again you need to use stop-smsc command as well. I recommend using monit (http://mmonit.com) for monitoring and issuing command I've mentioned. About allowed-smsc-ids - well if you want to use multiple smsc you need to use single virtual prefix, you need to do it this way: smsc-id = SMSC-M allowed-smsc-id = virtual-smsc;SMSC-M preferred-smsc-id = virtual-smsc;SMSC-M smsc-id = SMSC-Z allowed-smsc-id = virtual-smsc;SMSC-Z preferred-smsc-id = virtual-smsc;SMSC-Z allowed, preferred, denied only used in congestion when you have multiple smsc connections and want to load-balance between them or connect them into 1 group or don't want to send specific traffic through them. allowed-prefix should work with allowed-smsc-id as well. BUGS: The disadvantage I've found is: kannel is not re-sending already queued messages in the store on errorneous smscs to the new available online smsc (SMSC-R). (need to restart kannel to do that). Also removing smsc with remove-smsc command will lead to queued messages on this smsc removed. (the only thing is to restart kannel to reload queue). 2012/12/1 Ali Kashif <[email protected]> > Dear Friends, > > I am unable to solve the internal bearerbox routing, and seems like I am > stuck. > > I kannel 1.5 with SQLBOX, openSMPP, I am connected to 6 different SMSCs, > Say they are > > > > 1) SMSC-M > > 2) SMSC-U > > 3) SMSC-Z > > 4) SMSC-W > > 5) SMSC-T > > These are 5 providers in my country and they only send SMS to their own > network (special conditions) > > > > 6) SMSC-R (special SMSC, from 3rd party which can send SMS to all > Networks in my country) > > > > My Target was to send SMS through specific SMSC, which I have done using > prefixing > > > > *allowed-prefix="+xx30;00xx30;xx30"* > > *preferred-prefix="+xx30;00xx30;xx30"* > > *denied-prefix="+xx31;00xx31;xx31;+xx32;00xx32;xx32;+xx33;00xx33;xx33;+xx34;00xx34;xx34;+xx35;00xx35;xx35" > (denied all prefixes for other SMSC, so only xx30 will be sent from this > SMSC)* > > > > Every SMSC I am connected to have above allowed-prefix directive but with > prefixes which matches to that SMSC. > > > > And I am Done. My SMS are perfectly routed. Only relevant SMSC is sending > the SMS. Like I get xx30xxxxxxx, it is only and only sent by SMSC-Z > > > > Yesterday I faced one issue. MY SMSC-Z disconnected due to some issue at > their end. Now I never knew that. and ALL SMS failed. Not even queued at > Kannel. This is what I get in kannel > > > > *2012-11-30 13:26:18 send-SMS request added - sender:username:commoc > 127.0.0.1 target:xx3xxxxxxxxx request: 'Dear All,..* > > > Now What I actually I want is. When an SMSC is not available, message > should go through the SMSC-R, (again only if some SMSC-Z is not available) > > > I have tried to use following in conjunction of allowed-prefix, > preferred-prefix > > > *allowed-prefix="+xx30;00xx30;xx30"* > > *preferred-prefix="+xx30;00xx30;xx30"* > > *denied-prefix="+......"* > > *allowed-smsc-id= SMSC-M; SMSC-R* > > *preferred-smsc-id= SMSC-M* > > > > > but as soon as I add these routing stops and kannel is unable to find the > proper route. > > > > Can anyone advise what should I read. > > > > Thanks > > Ali > > >
