Hi I didn't see allow/deny smsc parameters in your smsc config. You need to add them to each smsc in order to tell kannel where to route/don't route messages. Also when sending the message you need to add the directive ...&smsc=R01... OR ...&smsc=R02... OR ...&smsc=R03... to your http call to tell kannel wich route to use. You can even use a "virtual route" to route to more than one smsc:
group = smsc smsc = "smpp" smsc-id = R01 system-type = smpp ... allow-smsc=R01;V01 group = smsc smsc = "smpp" smsc-id = R02 system-type = smpp ... allow-smsc=R02;V01 group = smsc smsc = "smpp" smsc-id = R03 system-type = smpp ... allow-smsc=R03 In the example above smsc 1 and 2 will allow sms directly to them but also to route V01; where V01 is virtual since there is no "definition" for it. To route sms for it just add ...&smsc=V01... to your http call. Hope this helps Regards Alvaro |-----------------------------------------------------------------------------------------------------------------| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.NET www.smsglobal.com.mx y www.pravcom.com On Wed, Nov 2, 2011 at 10:32 PM, Big Crunch <[email protected]> wrote: > Hi Alvaro, > > I have attached the config files we have, and yes allowed and denied > smsc-ids tags are there, but has the implementation changed recently for > this, because as from what I know of earlier the default was we need not > include the denied smsc-ids (or the allowed smsc-ids) tags and the messages > were routed to to that smsc, so by default it worked like deny all other > smsc-ids. Correct me if I am wrong here. > > Thanks, > BC. > >> Date: Wed, 2 Nov 2011 10:24:12 -0500 >> Subject: Re: Incorrect Routing by Bearerbox >> From: [email protected] >> To: [email protected] >> CC: [email protected] >> >> What about config files? >> >> You might need to add allow-smsc/denied-smsc to your smsc directives. >> Check userguide for details. >> >> Regards >> >> Alvaro >> >> >> |-----------------------------------------------------------------------------------------------------------------| >> Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier >> celular y Nextel >> en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via >> SMS y GPRS online >> Visitenos en www.perusms.NET www.smsglobal.com.mx y >> www.pravcom.com >> >> >> >> On Wed, Nov 2, 2011 at 3:52 AM, Big Crunch <[email protected]> >> wrote: >> > Hi, >> > >> > In the past couple of weeks I have seen some erratic behaviour from >> > bearerbox. It does not route an sms onto the route that it has been >> > asked >> > to, instead it seems to choose any of the live routes and send the >> > message >> > onto them. >> > >> > We are using smppbox to send messages across to bearerbox and we use a >> > custom routing and billing program through the use of smppbox_http >> > plugin. >> > The plugin sends back the routing information to the smppbox and it in >> > turn >> > sends it to bearerbox but the bearerbox does not use it and instead >> > routes >> > the message onto a randomly (apparently) chosen route. >> > >> > I have attached the bearerbox and smppbox log file dumps to help throw >> > some >> > light onto this. >> > >> > Two sets of files are attached >> > 1. bearerbox_server.log & smppbox.log >> > 2. bearerbox_server_2011-10-13.log & smppbox_2011-10-13.log >> > >> > PS : I have masked certain sensitive bit of information with Xs, but the >> > PDUs are all fine. >> > >> > Please advice, thanks. >> > >> > Regards, >> > BC. >> > >
