Hi If you use sqlbox, I think you should populate box-id field in order to finetune the routing.
Regards Alvaro On 3/13/13, [email protected] <[email protected]> wrote: > Hi, > > I have configured SMSC connections to do outgoing routing based on > allowed-prefix-regex. It's working fine, except for the fact that my > application code is inserting outgoing SMS data in SQLBOX without any > SMSC-ID, because of which the messages are being discarded now. > > I was kind of hoping that the MT traffic inserted in SQLBOX without any > SMSC-ID should automatically take the SMSC route for which it is allowed > (by traversing through all SMSC-IDs). But it is not the case currently, > whereby the bbox immediately drops the SMS for not having the SMSC-ID > field. An alternate handling to this is to change application programming > to analyze all destination numbers first and then enter SMSC-ID alongwith > submit to SQLBOX. This means a lot of programming overhead on the > application part. > > Is there any optimization parameter in kannel which can handle this thing, > without me having to change application coding? > > Regards, > Hamza > > > On Wed, Mar 13, 2013 at 12:28 AM, Alvaro Cornejo > <[email protected]>wrote: > >> Hi >> >> You should use allowed/denied-smsc and send the sms with >> ...&smsc-id=DestinationSmsc... >> >> Regards >> >> Alvaro >> >> On 3/12/13, [email protected] <[email protected]> wrote: >> > Hi, >> > >> > I am 'trying' to channelize outgoing traffic from kannel based on the >> > username/password combination in sendsms-user groups. My config is >> > following: >> > >> > group = smsbox-route >> > smsbox-id = smsbox >> > smsc-id = SMSC-1;SMSC-2 >> > group = sendsms-user >> > username = ABC >> > password = ABC >> > default-smsc = SMSC-1 >> > max-messages = 5 >> > concatenation = true >> > group = sendsms-user >> > username = XYZ >> > password = XYZ >> > default-smsc = SMSC-2 >> > max-messages = 5 >> > concatenation = true >> > When trying to send SMS via username ABC, ideally it should only go out >> via >> > SMSC-1. However, the SMS is going out randomly from both SMSC-1 and >> SMSC-2. >> > >> > Additional info: I am using SQLBOX in between SMSBOX and BBOX as well. >> > Also, there is only single SMSBOX carrying all ESME connections. >> > >> > How can I force the SMS to follow the defined path, related to the >> > username/password used in sending? >> > >> > Regards, >> > Hamza >> > >> >> >> -- >> >> |-----------------------------------------------------------------------------------------------------------------| >> 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 >> > -- |-----------------------------------------------------------------------------------------------------------------| 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
