I figured out a way to set it up the way I need it to work. So like I said, I wanted to route all MOs originating from all SMSCs to a single script to handle all of them. In my SMSc configuration I am using reroute-smsc-id to re-route all incoming MOs to a single HTTP SMSc that will invoke my script. The thing that kept me back is the preferred-smsc-id setting, because if it is used in conjunction with reroute-smsc-id then reroute-smsc-id is completely ignored without any mention of it in kannel logs.
On Wed, Apr 19, 2023 at 7:12 PM Tolga Ulas <tolga.u...@tolgaulas.com> wrote: > Not sure on top of my head whether it can be smsc independent, check with > the documentation in the related section of thart smsc-id part and > smsbox-route functioning in general. > Tolga Ulas > > > > On Wed, Apr 19, 2023 at 5:51 PM akamat sarat <akamat.sa...@gmail.com> > wrote: > >> Thank for coming back, you mean something like: >> >> group=smsbox-route >> smsbox-id=mysmsbox >> smsc-id=SMSC1; SMSC2; SMSC3... >> >> If so, this means that every time a new SMSC is added, I will need to add >> it to the smsc-id's list in the above configuration. >> After that I will need to restart kannel which I do not want to do. >> If thats not what you mean can you write an example? >> >> Thank you. >> >> >> On Wed, Apr 19, 2023 at 5:39 PM Tolga Ulas <tolga.u...@tolgaulas.com> >> wrote: >> >>> Put a single route to a single smsbox which has a single service and >>> define all your smscs in the route as origin. >>> >>> Tolga Ulas >>> >>> >>> On Wed, Apr 19, 2023 at 5:22 PM akamat sarat <akamat.sa...@gmail.com> >>> wrote: >>> >>>> To all kannelers, >>>> >>>> I am trying to find a way to configure kannel so that all incoming >>>> messages (MOs) from all SMSCs to go to the same script. >>>> The problem is that i could not find a working solution that does not >>>> rely on smsbox-routes >>>> and it is not possible to add smsbox-routes on the fly. >>>> >>>> Any help would be appreciated >>>> >>>
