Re: Outgoing SMS routing configuration
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, ha...@aeon.pk 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 > wrote: > >> Hi >> >> You should use allowed/denied-smsc and send the sms with >> ...&smsc-id=DestinationSmsc... >> >> Regards >> >> Alvaro >> >> On 3/12/13, ha...@aeon.pk 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
Re: Outgoing SMS routing configuration
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 wrote: > Hi > > You should use allowed/denied-smsc and send the sms with > ...&smsc-id=DestinationSmsc... > > Regards > > Alvaro > > On 3/12/13, ha...@aeon.pk 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 >
Re: Outgoing SMS routing configuration
Hi You should use allowed/denied-smsc and send the sms with ...&smsc-id=DestinationSmsc... Regards Alvaro On 3/12/13, ha...@aeon.pk 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
Outgoing SMS routing configuration
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
RE: Outgoing SMS routing via different SMSC by destination number prefix
group = smsc smsc = fake smsc-id = smsc-0 port = 1 connect-allow-ip = 127.0.0.1 denied-prefix = 007;008 -Original Message- From: users-boun...@vm1.kannel.org [mailto:users-boun...@vm1.kannel.org] On Behalf Of Eugene Prokopiev Sent: Thursday, 13 September, 2012 07:08 To: us...@vm1.kannel.org Subject: Outgoing SMS routing via different SMSC by destination number prefix Hi, What is the right way to route outgoing SMS routing via different SMSC by destination number prefix + default route for any unknown prefixes? I tried to do it by this configuration: group = core admin-port = 13000 admin-password = admin smsbox-port = 13001 dlr-storage = internal group = smsbox bearerbox-host = localhost smsbox-id = smsbox-0 sendsms-port = 13013 group = smsc smsc = fake smsc-id = smsc-7 port = 10007 connect-allow-ip = 127.0.0.1 allowed-prefix = 007 group = smsc smsc = fake smsc-id = smsc-8 port = 10008 connect-allow-ip = 127.0.0.1 allowed-prefix = 008 group = smsc smsc = fake smsc-id = smsc-0 port = 1 connect-allow-ip = 127.0.0.1 group = sendsms-user username = "" password = " Messages with prefox 007 are routed via smsc-7 but sometimes are routed via smsc-0. Why can it be? What is the best configuration for my use case? -- Regards, Eugene Prokopiev
Outgoing SMS routing via different SMSC by destination number prefix
Hi, What is the right way to route outgoing SMS routing via different SMSC by destination number prefix + default route for any unknown prefixes? I tried to do it by this configuration: group = core admin-port = 13000 admin-password = admin smsbox-port = 13001 dlr-storage = internal group = smsbox bearerbox-host = localhost smsbox-id = smsbox-0 sendsms-port = 13013 group = smsc smsc = fake smsc-id = smsc-7 port = 10007 connect-allow-ip = 127.0.0.1 allowed-prefix = 007 group = smsc smsc = fake smsc-id = smsc-8 port = 10008 connect-allow-ip = 127.0.0.1 allowed-prefix = 008 group = smsc smsc = fake smsc-id = smsc-0 port = 1 connect-allow-ip = 127.0.0.1 group = sendsms-user username = "" password = " Messages with prefox 007 are routed via smsc-7 but sometimes are routed via smsc-0. Why can it be? What is the best configuration for my use case? -- Regards, Eugene Prokopiev
Re: SMS routing
Thanks Mike :) On Mon, Jan 5, 2009 at 4:18 PM, Mike Nwaogu wrote: > Sorry had supposed you were using the cgi via http to send. > If that's the case you'll need to specify which smsc you wish to use, it's > done programatically at the application level. > Your URL will look like this ... > > > http://localhost:13003/cgi-bin/sendsms?username=&password=&to=$to&from=$frm&; > default_smsc=smsc1&text=$msg > > Regards, > Mike Nwaogu > Tel: 234_802_325_6437 > > > -- > *From:* hafez ahmad > *To:* Mike Nwaogu > *Cc:* "users@kannel.org" > *Sent:* Monday, January 5, 2009 1:34:39 PM > *Subject:* Re: SMS routing > > Dear Mike, > > thanks for reply, but can you please explain more? > > Regards, > Hafez > > On Mon, Jan 5, 2009 at 11:20 AM, Mike Nwaogu wrote: > >> default-smsc=[smsc_id_name] >> >> Regards, >> Mike Nwaogu >> Tel: 234_802_325_6437 >> >> >> -- >> *From:* hafez ahmad >> *To:* "users@kannel.org" >> *Sent:* Monday, January 5, 2009 9:13:55 AM >> *Subject:* SMS routing >> >> Dears, >> >> I have 2 TX SMPP connection for the same operator, I need to send SMSs >> using the first connection, but if the 1st connection have load , the SMSs >> served using the 2nd connection. >> >> can I do that using kannel or it is Application level? , and if yes it is >> using the *allowed-smsc-id? >> >> * >> Thanks for help, >> Hafez >> >> > > > -- > Hafez A.Ahmad > Amman-Jordan > mobile:962-785259011 > 962-795708728 > http://blog.hafezadnan.com > > -- Hafez A.Ahmad Amman-Jordan mobile:962-785259011 962-795708728 http://blog.hafezadnan.com
Re: SMS routing
Sorry had supposed you were using the cgi via http to send. If that's the case you'll need to specify which smsc you wish to use, it's done programatically at the application level. Your URL will look like this ... http://localhost:13003/cgi-bin/sendsms?username=&password=&to=$to&from=$frm&default_smsc=smsc1&text=$msg Regards, Mike Nwaogu Tel: 234_802_325_6437 From: hafez ahmad To: Mike Nwaogu Cc: "users@kannel.org" Sent: Monday, January 5, 2009 1:34:39 PM Subject: Re: SMS routing Dear Mike, thanks for reply, but can you please explain more? Regards, Hafez On Mon, Jan 5, 2009 at 11:20 AM, Mike Nwaogu wrote: default-smsc=[smsc_id_name] Regards, Mike Nwaogu Tel: 234_802_325_6437 From: hafez ahmad To: "users@kannel.org" Sent: Monday, January 5, 2009 9:13:55 AM Subject: SMS routing Dears, I have 2 TX SMPP connection for the same operator, I need to send SMSs using the first connection, but if the 1st connection have load , the SMSs served using the 2nd connection. can I do that using kannel or it is Application level? , and if yes it is using the allowed-smsc-id? Thanks for help, Hafez -- Hafez A.Ahmad Amman-Jordan mobile:962-785259011 962-795708728 http://blog.hafezadnan.com
Re: SMS routing
Dear Mike, thanks for reply, but can you please explain more? Regards, Hafez On Mon, Jan 5, 2009 at 11:20 AM, Mike Nwaogu wrote: > default-smsc=[smsc_id_name] > > Regards, > Mike Nwaogu > Tel: 234_802_325_6437 > > > -- > *From:* hafez ahmad > *To:* "users@kannel.org" > *Sent:* Monday, January 5, 2009 9:13:55 AM > *Subject:* SMS routing > > Dears, > > I have 2 TX SMPP connection for the same operator, I need to send SMSs > using the first connection, but if the 1st connection have load , the SMSs > served using the 2nd connection. > > can I do that using kannel or it is Application level? , and if yes it is > using the *allowed-smsc-id? > > * > Thanks for help, > Hafez > > -- Hafez A.Ahmad Amman-Jordan mobile:962-785259011 962-795708728 http://blog.hafezadnan.com
Re: SMS routing
default-smsc=[smsc_id_name] Regards, Mike Nwaogu Tel: 234_802_325_6437 From: hafez ahmad To: "users@kannel.org" Sent: Monday, January 5, 2009 9:13:55 AM Subject: SMS routing Dears, I have 2 TX SMPP connection for the same operator, I need to send SMSs using the first connection, but if the 1st connection have load , the SMSs served using the 2nd connection. can I do that using kannel or it is Application level? , and if yes it is using the allowed-smsc-id? Thanks for help, Hafez
SMS routing
Dears, I have 2 TX SMPP connection for the same operator, I need to send SMSs using the first connection, but if the 1st connection have load , the SMSs served using the 2nd connection. can I do that using kannel or it is Application level? , and if yes it is using the *allowed-smsc-id? * Thanks for help, Hafez
incoming SMS routing
I've setup Kannel 1.4 with "fakeSMSC" configuration. I'm able to SEND SMS from a PC via http-get, where the "from" and "to" number can be specified. So any PC user (depending on white/black list) is able to SEND SMS to the (fake) SMSC. My question is about the other direction: how to simulate RECEIVE SMS from the fakeSMSC to a specific PC user. Maybe the first question here is the following: Is it possible for internet users to being (temporarily) "subcribed" to receive SMS via http (by using for example a kannel GW connected to SMSC) in stead of receiving SMS via their regular mobile device, but still based on their regular mobile number (so that the SMS sender does not need to be aware of the internet subscription of the receiver)? Next question is how to configure kannel to map the mobile numbers of the users to their PC domain-name for proper incoming SMS routing. Do I need the push proxy gateway for this purpose? Anyhow, I could not figure out how to map and route based on the regular mobile numbers of these "internet users". apreciate any hints -- View this message in context: http://www.nabble.com/incoming-SMS-routing-tp16935576p16935576.html Sent from the Kannel - User mailing list archive at Nabble.com.
Re: sms routing
I think you should explain your routing purpose . for example I'm routing messages to 6 application 2 set of 3 instances which separated by prefix On 8/23/07, Rodrigo Cremaschi <[EMAIL PROTECTED]> wrote: > > No. > But you can make an application that invokes two (or as many as you > wish) applications. > > On 8/23/07, Paweł Buńko <[EMAIL PROTECTED]> wrote: > > Hello, > > is it possible to make kannel to route sms to more than one application? > > > > -- > > Paweł Buńko > > Dział Rozwoju Produktów > > AutoGuard & Insurance sp. z o.o. > > e-mail: [EMAIL PROTECTED] > > tel +48 22 611 68 82 > > mobile +48 502 477 791 > > > > Tlen.pl: pawlin_b > > GG: #1692409 > > Skype: pawlin > > > > > > > -- --Vahid Ghafarpour. http://vahid.ghafarpour.ir/ vahid at ghafarpour dot ir ghafarpour at gmail dot com
Re: sms routing
No. But you can make an application that invokes two (or as many as you wish) applications. On 8/23/07, Paweł Buńko <[EMAIL PROTECTED]> wrote: > Hello, > is it possible to make kannel to route sms to more than one application? > > -- > Paweł Buńko > Dział Rozwoju Produktów > AutoGuard & Insurance sp. z o.o. > e-mail: [EMAIL PROTECTED] > tel +48 22 611 68 82 > mobile +48 502 477 791 > > Tlen.pl: pawlin_b > GG: #1692409 > Skype: pawlin > > >
sms routing
Hello, is it possible to make kannel to route sms to more than one application? -- Paweł Buńko Dział Rozwoju Produktów AutoGuard & Insurance sp. z o.o. e-mail: [EMAIL PROTECTED] tel +48 22 611 68 82 mobile +48 502 477 791 Tlen.pl: pawlin_b GG: #1692409 Skype: pawlin
Re: sms routing while some smsc doesn't work
anybody? I really need help Paweł Buńko napisał(a): Hello, I have 3 smsc oisd type of 3 different gsm operator and I have 3 gsm modem of 3 different operator and I'm trying to configure kannel to send sms throught modems while some of those oisd smsc doesn't work or some of gsm modem doesn't work my kannel konfiguration is: kannel.conf # # Sample configuration file for Kannel bearerbox on Debian. # See the documentation for explanations of fields. # # HTTP administration is disabled by default. Make sure you set the # password if you enable it. group = core admin-port = 13000 admin-password = bar admin-allow-ip = "*.*.*.*" smsbox-port = 13003 log-file = "/var/log/kannel/bearerbox.log" log-level = 0 access-log = "/var/log/kannel/access.log" store-file = "/var/log/kannel/storefile" store-dump-freq = 60 sms-resend-retry = 5 sms-resend-freq = 30 box-deny-ip = "*.*.*.*" box-allow-ip = "127.0.0.1" include = "/etc/kannel/smsbox.conf" smsbox.conf # SMSC CONNECTIONS group = smsc smsc = oisd smsc-id = SMSCERA host = 213.158.194.29 port = 12101 keepalive = 25 my-number = 3553 validityperiod = 30 log-file = "/var/log/kannel/SMSCERA.log" log-level = 0 allowed-smsc-id = SMSCERA group = smsc smsc = oisd smsc-id = SMSCIDEA host = 213.158.194.29 port = 12102 keepalive = 25 my-number = 3553 validityperiod = 30 log-file = "/var/log/kannel/SMSCIDEA.log" log-level = 0 allowed-smsc-id = SMSCIDEA group = smsc smsc = oisd smsc-id = SMSCPLUS host = 213.158.194.29 port = 12103 keepalive = 25 my-number = 3553 validityperiod = 30 log-file = "/var/log/kannel/SMSCPLUS.log" log-level = 0 allowed-smsc-id = SMSCPLUS group = smsc smsc = at smsc-id = GM47ERA modemtype = sonyericsson_gr47 device = /dev/ttyS2 speed = 9600 pin = 4834 keepalive = 5 max-error-count = 5 log-file = "/var/log/kannel/GM47ERA.log" log-level = 0 sim-buffering = true my-number = +400 allowed-smsc-id = GM47ERA;SMSCERA;SMSCIDEA;SMSCPLUS;GM47IDEA;GM47PLUS group = smsc smsc = at smsc-id = GM47IDEA modemtype = sonyericsson_gr47 device = /dev/ttyS1 speed = 9600 pin = 4834 keepalive = 5 max-error-count = 5 log-file = "/var/log/kannel/GM47IDEA.log" log-level = 0 sim-buffering = true my-number = +4850200 allowed-smsc-id = GM47IDEA;SMSCERA;SMSCIDEA;SMSCPLUS;GM47ERA;GM47PLUS group = smsc smsc = at smsc-id = GM47PLUS modemtype = sonyericsson_gr47 device = /dev/ttyS3 speed = 9600 pin = 4834 keepalive = 5 max-error-count = 5 log-file = "/var/log/kannel/GM47PLUS.log" log-level = 0 sim-buffering = true my-number = +486 allowed-smsc-id = GM47PLUS;SMSCERA;SMSCIDEA;SMSCPLUS;GM47IDEA;GM47ERA # SMSBOX SETUP group = smsbox bearerbox-host = 127.0.0.1 sendsms-port = 13013 global-sender = 3553 log-file = "/var/log/kannel/smsbox.log" log-level = 0 access-log = "/var/log/kannel/smsboxaccess.log" reply-couldnotfetch = "" reply-couldnotrepresent = "" reply-requestfailed = "" http-request-retry = 5000 http-queue-delay = 30 max-pending-requests = 1 # SEND-SMS USERS group = sendsms-user username = SMSCERA password = SMSCERA #forced-smsc = SMSCERA group = sendsms-user username = SMSCIDEA password = SMSCIDEA #forced-smsc = SMSCIDEA group = sendsms-user username = SMSCPLUS password = SMSCPLUS #forced-smsc = SMSCPLUS group = sendsms-user username = GM47ERA password = GM47ERA #forced-smsc = GM47ERA group = sendsms-user username = GM47IDEA password = GM47IDEA #forced-smsc = GM47IDEA group = sendsms-user username = GM47PLUS password = GM47PLUS #forced-smsc = GM47PLUS # SERVICES # there should be default always group = sms-service keyword = default get-url = "http://172.16.8.86:14000/?msg=%b&dateTime=%t&unixTime=%T&from=%q&smscId=%i&coding=%c"; catch-all = true max-messages = 0 # MODEMS group = modems id = sonyericsson_gr47 name = "Sony Ericsson GR47" detect-string = "GR47" message-storage = "ME" init-string = "AT+CNMI=3,2,0,0" reset-string = "ATZ" keepalive-cmd = "AT+CSQ" need-sleep = true sendline-sleep = 2000 when I'm trying to send sms through some of this smsc e.g. http://172.16.8.86:13013/cgi-bin/sendsms?username=SMSCERA&password=SMSCERA&from=3553&to=502477791&text=hello&smsc-id=SMSERA&dlr-mask=31&coding=0&dlr-url=http%3A%2F%2F172.16.8.86%3A14001%2F%3FsmscId%3D%25i%26status%3D%25d%26answer%3D%25A%26to%3D%25Q%26from%3D%25q%26dateTime%3D%25t%26unixTime%3D%25T%26messageId%3D47&validity=30 I receive 'Not routable. Do not try again.' from kannel. what is wrong? to achieve sending sms through proper smsc I was using forced-smsc but when that smsc-id is not working kannel trying to send through it withou rerouting to another allowed-smsc-id could anyone help me? -- Paweł Buńko Dział Rozwoju Produktów AutoGuard & Insurance sp. z o.o. e-mail: [EMAIL PROTECTED] tel +48 22 611 68 82 mobile +48 502 477 791 Tlen.pl: pawlin_b GG: #1692409 Skype: pawlin
Re: sms routing while some smsc doesn't work
Paweł Buńko napisał(a): Hello, I have 3 smsc oisd type of 3 different gsm operator and I have 3 gsm modem of 3 different operator and I'm trying to configure kannel to send sms throught modems while some of those oisd smsc doesn't work or some of gsm modem doesn't work my kannel konfiguration is: kannel.conf # # Sample configuration file for Kannel bearerbox on Debian. # See the documentation for explanations of fields. # # HTTP administration is disabled by default. Make sure you set the # password if you enable it. group = core admin-port = 13000 admin-password = bar admin-allow-ip = "*.*.*.*" smsbox-port = 13003 log-file = "/var/log/kannel/bearerbox.log" log-level = 0 access-log = "/var/log/kannel/access.log" store-file = "/var/log/kannel/storefile" store-dump-freq = 60 sms-resend-retry = 5 sms-resend-freq = 30 box-deny-ip = "*.*.*.*" box-allow-ip = "127.0.0.1" include = "/etc/kannel/smsbox.conf" smsbox.conf # SMSC CONNECTIONS group = smsc smsc = oisd smsc-id = SMSCERA host = 213.158.194.29 port = 12101 keepalive = 25 my-number = 3553 validityperiod = 30 log-file = "/var/log/kannel/SMSCERA.log" log-level = 0 allowed-smsc-id = SMSCERA group = smsc smsc = oisd smsc-id = SMSCIDEA host = 213.158.194.29 port = 12102 keepalive = 25 my-number = 3553 validityperiod = 30 log-file = "/var/log/kannel/SMSCIDEA.log" log-level = 0 allowed-smsc-id = SMSCIDEA group = smsc smsc = oisd smsc-id = SMSCPLUS host = 213.158.194.29 port = 12103 keepalive = 25 my-number = 3553 validityperiod = 30 log-file = "/var/log/kannel/SMSCPLUS.log" log-level = 0 allowed-smsc-id = SMSCPLUS group = smsc smsc = at smsc-id = GM47ERA modemtype = sonyericsson_gr47 device = /dev/ttyS2 speed = 9600 pin = 4834 keepalive = 5 max-error-count = 5 log-file = "/var/log/kannel/GM47ERA.log" log-level = 0 sim-buffering = true my-number = +400 allowed-smsc-id = GM47ERA;SMSCERA;SMSCIDEA;SMSCPLUS;GM47IDEA;GM47PLUS group = smsc smsc = at smsc-id = GM47IDEA modemtype = sonyericsson_gr47 device = /dev/ttyS1 speed = 9600 pin = 4834 keepalive = 5 max-error-count = 5 log-file = "/var/log/kannel/GM47IDEA.log" log-level = 0 sim-buffering = true my-number = +4850200 allowed-smsc-id = GM47IDEA;SMSCERA;SMSCIDEA;SMSCPLUS;GM47ERA;GM47PLUS group = smsc smsc = at smsc-id = GM47PLUS modemtype = sonyericsson_gr47 device = /dev/ttyS3 speed = 9600 pin = 4834 keepalive = 5 max-error-count = 5 log-file = "/var/log/kannel/GM47PLUS.log" log-level = 0 sim-buffering = true my-number = +486 allowed-smsc-id = GM47PLUS;SMSCERA;SMSCIDEA;SMSCPLUS;GM47IDEA;GM47ERA # SMSBOX SETUP group = smsbox bearerbox-host = 127.0.0.1 sendsms-port = 13013 global-sender = 3553 log-file = "/var/log/kannel/smsbox.log" log-level = 0 access-log = "/var/log/kannel/smsboxaccess.log" reply-couldnotfetch = "" reply-couldnotrepresent = "" reply-requestfailed = "" http-request-retry = 5000 http-queue-delay = 30 max-pending-requests = 1 # SEND-SMS USERS group = sendsms-user username = SMSCERA password = SMSCERA #forced-smsc = SMSCERA group = sendsms-user username = SMSCIDEA password = SMSCIDEA #forced-smsc = SMSCIDEA group = sendsms-user username = SMSCPLUS password = SMSCPLUS #forced-smsc = SMSCPLUS group = sendsms-user username = GM47ERA password = GM47ERA #forced-smsc = GM47ERA group = sendsms-user username = GM47IDEA password = GM47IDEA #forced-smsc = GM47IDEA group = sendsms-user username = GM47PLUS password = GM47PLUS #forced-smsc = GM47PLUS # SERVICES # there should be default always group = sms-service keyword = default get-url = "http://172.16.8.86:14000/?msg=%b&dateTime=%t&unixTime=%T&from=%q&smscId=%i&coding=%c"; catch-all = true max-messages = 0 # MODEMS group = modems id = sonyericsson_gr47 name = "Sony Ericsson GR47" detect-string = "GR47" message-storage = "ME" init-string = "AT+CNMI=3,2,0,0" reset-string = "ATZ" keepalive-cmd = "AT+CSQ" need-sleep = true sendline-sleep = 2000 when I'm trying to send sms through some of this smsc e.g. http://172.16.8.86:13013/cgi-bin/sendsms?username=SMSCERA&password=SMSCERA&from=3553&to=502477791&text=hello&smsc-id=SMSERA&dlr-mask=31&coding=0&dlr-url=http%3A%2F%2F172.16.8.86%3A14001%2F%3FsmscId%3D%25i%26status%3D%25d%26answer%3D%25A%26to%3D%25Q%26from%3D%25q%26dateTime%3D%25t%26unixTime%3D%25T%26messageId%3D47&validity=30 I receive 'Not routable. Do not try again.' from kannel. what is wrong? to achieve sending sms through proper smsc I was using forced-smsc but when that smsc-id is not working kannel trying to send through it withou rerouting to another allowed-smsc-id could anyone help me? Setting up multi-operator Kannel Sometimes there is a need for Kannel to listen to two (or more) distinct SMS centers, and messages must be routed to services according to where they came from, and replies likewise must return to same SMSC. This is done via smsc-id magic. Here is a shortened sample configuration, which handles to distinct SMS servers and services: group = smsc smsc-id = A deni
sms routing while some smsc doesn't work
Hello, I have 3 smsc oisd type of 3 different gsm operator and I have 3 gsm modem of 3 different operator and I'm trying to configure kannel to send sms throught modems while some of those oisd smsc doesn't work or some of gsm modem doesn't work my kannel konfiguration is: kannel.conf # # Sample configuration file for Kannel bearerbox on Debian. # See the documentation for explanations of fields. # # HTTP administration is disabled by default. Make sure you set the # password if you enable it. group = core admin-port = 13000 admin-password = bar admin-allow-ip = "*.*.*.*" smsbox-port = 13003 log-file = "/var/log/kannel/bearerbox.log" log-level = 0 access-log = "/var/log/kannel/access.log" store-file = "/var/log/kannel/storefile" store-dump-freq = 60 sms-resend-retry = 5 sms-resend-freq = 30 box-deny-ip = "*.*.*.*" box-allow-ip = "127.0.0.1" include = "/etc/kannel/smsbox.conf" smsbox.conf # SMSC CONNECTIONS group = smsc smsc = oisd smsc-id = SMSCERA host = 213.158.194.29 port = 12101 keepalive = 25 my-number = 3553 validityperiod = 30 log-file = "/var/log/kannel/SMSCERA.log" log-level = 0 allowed-smsc-id = SMSCERA group = smsc smsc = oisd smsc-id = SMSCIDEA host = 213.158.194.29 port = 12102 keepalive = 25 my-number = 3553 validityperiod = 30 log-file = "/var/log/kannel/SMSCIDEA.log" log-level = 0 allowed-smsc-id = SMSCIDEA group = smsc smsc = oisd smsc-id = SMSCPLUS host = 213.158.194.29 port = 12103 keepalive = 25 my-number = 3553 validityperiod = 30 log-file = "/var/log/kannel/SMSCPLUS.log" log-level = 0 allowed-smsc-id = SMSCPLUS group = smsc smsc = at smsc-id = GM47ERA modemtype = sonyericsson_gr47 device = /dev/ttyS2 speed = 9600 pin = 4834 keepalive = 5 max-error-count = 5 log-file = "/var/log/kannel/GM47ERA.log" log-level = 0 sim-buffering = true my-number = +400 allowed-smsc-id = GM47ERA;SMSCERA;SMSCIDEA;SMSCPLUS;GM47IDEA;GM47PLUS group = smsc smsc = at smsc-id = GM47IDEA modemtype = sonyericsson_gr47 device = /dev/ttyS1 speed = 9600 pin = 4834 keepalive = 5 max-error-count = 5 log-file = "/var/log/kannel/GM47IDEA.log" log-level = 0 sim-buffering = true my-number = +4850200 allowed-smsc-id = GM47IDEA;SMSCERA;SMSCIDEA;SMSCPLUS;GM47ERA;GM47PLUS group = smsc smsc = at smsc-id = GM47PLUS modemtype = sonyericsson_gr47 device = /dev/ttyS3 speed = 9600 pin = 4834 keepalive = 5 max-error-count = 5 log-file = "/var/log/kannel/GM47PLUS.log" log-level = 0 sim-buffering = true my-number = +486 allowed-smsc-id = GM47PLUS;SMSCERA;SMSCIDEA;SMSCPLUS;GM47IDEA;GM47ERA # SMSBOX SETUP group = smsbox bearerbox-host = 127.0.0.1 sendsms-port = 13013 global-sender = 3553 log-file = "/var/log/kannel/smsbox.log" log-level = 0 access-log = "/var/log/kannel/smsboxaccess.log" reply-couldnotfetch = "" reply-couldnotrepresent = "" reply-requestfailed = "" http-request-retry = 5000 http-queue-delay = 30 max-pending-requests = 1 # SEND-SMS USERS group = sendsms-user username = SMSCERA password = SMSCERA #forced-smsc = SMSCERA group = sendsms-user username = SMSCIDEA password = SMSCIDEA #forced-smsc = SMSCIDEA group = sendsms-user username = SMSCPLUS password = SMSCPLUS #forced-smsc = SMSCPLUS group = sendsms-user username = GM47ERA password = GM47ERA #forced-smsc = GM47ERA group = sendsms-user username = GM47IDEA password = GM47IDEA #forced-smsc = GM47IDEA group = sendsms-user username = GM47PLUS password = GM47PLUS #forced-smsc = GM47PLUS # SERVICES # there should be default always group = sms-service keyword = default get-url = "http://172.16.8.86:14000/?msg=%b&dateTime=%t&unixTime=%T&from=%q&smscId=%i&coding=%c"; catch-all = true max-messages = 0 # MODEMS group = modems id = sonyericsson_gr47 name = "Sony Ericsson GR47" detect-string = "GR47" message-storage = "ME" init-string = "AT+CNMI=3,2,0,0" reset-string = "ATZ" keepalive-cmd = "AT+CSQ" need-sleep = true sendline-sleep = 2000 when I'm trying to send sms through some of this smsc e.g. http://172.16.8.86:13013/cgi-bin/sendsms?username=SMSCERA&password=SMSCERA&from=3553&to=502477791&text=hello&smsc-id=SMSERA&dlr-mask=31&coding=0&dlr-url=http%3A%2F%2F172.16.8.86%3A14001%2F%3FsmscId%3D%25i%26status%3D%25d%26answer%3D%25A%26to%3D%25Q%26from%3D%25q%26dateTime%3D%25t%26unixTime%3D%25T%26messageId%3D47&validity=30 I receive 'Not routable. Do not try again.' from kannel. what is wrong? to achieve sending sms through proper smsc I was using forced-smsc but when that smsc-id is not working kannel trying to send through it withou rerouting to another allowed-smsc-id could anyone help me? -- Paweł Buńko Dział Rozwoju Produktów AutoGuard & Insurance sp. z o.o. e-mail: [EMAIL PROTECTED] tel +48 22 611 68 82 mobile +48 502 477 791 Tlen.pl: pawlin_b GG: #1692409 Skype: pawlin
Re: Question about sms routing
Read about "allowed-receiver-prefix" and "denied-receiver-prefix" on the user guide, you should be able to do it that way. Hope it helps On 1/27/06, Konstantinos Liadakis <[EMAIL PROTECTED]> wrote: > > > Hello, I am new to kannel and think it is a great software, > > > > I have installed it, setup 3 smpp smsc and 1 UCP/EMI and all seem to work > fine. I can send and receive sms and I am quite happy with it. > > > > I would like to do the following though. > > > > I would like to be able to set for each of my users, routing depending on > destination, for example > > > > If we have 3 SMSC's A,B,C and 2 users user1 and user2 I would like to be > able to say that for user 1 destinations with prefix 30697 to be routed > through smsc A and for prefix 30693 to be routed through SMSC B. > > > > In the same manner I would like for user2 to route destinations with prefix > 30697 through C and destinations with [refix 30693 to be routed through SMSC > B > > > > Is this kind of thing possible with Kannel > > > > Thank you very much in advance for your help > > > > Kind regards > > > > Kosntantinos Liadakis -- Alejandro Guerrieri Magicom http://www.magicom-bcn.net/
Re: Question about sms routing
Hi Konstantinos... Well, I think it cannot be done using kannel solely, however a very very SIMPLE script (perl, php.. bash..) can read this numbers of yours and post to the http send url with the correct SMSC-ID intented for each prefix. This is at least how i go about this issue! greetings, Alejandro Konstantinos Liadakis wrote: Hello, I am new to kannel and think it is a great software, I have installed it, setup 3 smpp smsc and 1 UCP/EMI and all seem to work fine. I can send and receive sms and I am quite happy with it. I would like to do the following though. I would like to be able to set for each of my users, routing depending on destination, for example If we have 3 SMSC’s A,B,C and 2 users user1 and user2 I would like to be able to say that for user 1 destinations with prefix 30697 to be routed through smsc A and for prefix 30693 to be routed through SMSC B. In the same manner I would like for user2 to route destinations with prefix 30697 through C and destinations with [refix 30693 to be routed through SMSC B Is this kind of thing possible with Kannel Thank you very much in advance for your help Kind regards Kosntantinos Liadakis
Question about sms routing
Hello, I am new to kannel and think it is a great software, I have installed it, setup 3 smpp smsc and 1 UCP/EMI and all seem to work fine. I can send and receive sms and I am quite happy with it. I would like to do the following though. I would like to be able to set for each of my users, routing depending on destination, for example If we have 3 SMSC’s A,B,C and 2 users user1 and user2 I would like to be able to say that for user 1 destinations with prefix 30697 to be routed through smsc A and for prefix 30693 to be routed through SMSC B. In the same manner I would like for user2 to route destinations with prefix 30697 through C and destinations with [refix 30693 to be routed through SMSC B Is this kind of thing possible with Kannel Thank you very much in advance for your help Kind regards Kosntantinos Liadakis
Re: sms routing?
Kyriacos, Look into the allowed-smsc-id and denied-smsc-id settings for the SMSC group. http://kannel.org/download/1.4.0/userguide-1.4.0/userguide.html#AEN1085 Andrew On Wednesday 18 January 2006 06:03 am, Kyriacos Sakkas wrote: > hi all, > I have connections to multiple smsc, and want some messages which I > submit via http to kannel to be send out via a specific smsc when > multiple of my smscs support that number range. > > I have tried to do it by specifying the smsc in my get request and by > using forced-smsc in my sendsms-user group > which have failed although it would seem that that's what those settings > are for. > > The user manual details using smsbox routing but in what I find slightly > confusing manner. I have to assume that whet it says incoming messages > it is referring to what for me are outgoing (MT). > Before going in and messing a working setup I would appreciate any > thoughts on this matter and maybe a possible easier way of doing it. > For me it looks easier to prepend a digit (e.g 9) before the number and > then only put this in the allowed prefix of the smsc I want this > messages to be send from. > > I will not Include my conf in this post, but if anybody wants to be > specific please let me know, and I will clean and post it. > > thanks in advance, > Kyriacos Sakkas
sms routing?
hi all, I have connections to multiple smsc, and want some messages which I submit via http to kannel to be send out via a specific smsc when multiple of my smscs support that number range. I have tried to do it by specifying the smsc in my get request and by using forced-smsc in my sendsms-user group which have failed although it would seem that that's what those settings are for. The user manual details using smsbox routing but in what I find slightly confusing manner. I have to assume that whet it says incoming messages it is referring to what for me are outgoing (MT). Before going in and messing a working setup I would appreciate any thoughts on this matter and maybe a possible easier way of doing it. For me it looks easier to prepend a digit (e.g 9) before the number and then only put this in the allowed prefix of the smsc I want this messages to be send from. I will not Include my conf in this post, but if anybody wants to be specific please let me know, and I will clean and post it. thanks in advance, Kyriacos Sakkas -- Kyriacos Sakkas Development Team Netsmart Tel: + 357 22 452565 Fax: + 357 22 452566 Email: [EMAIL PROTECTED] http://www.netsmart.com.cy Taking Business to a New Level! ** Confidentiality Notice: The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution, or copying of this email message is strictly prohibited. If you think that you have received this email message in error, please email the sender at [EMAIL PROTECTED] **
SMS routing based on smsc-id does not work properly.
Dear, Sirs! Sorry for I have two different SMSC(one is SMPP-based, another one is HTTP-based ) in configuration file and have some problems with routing. I want to route reply to the same SMSC, which receive request. I make configuration as in documentation http://www.kannel.org/download/kannel-userguide-snapshot/userguide.html#AEN4033 but it does not work properly. CONFIG: group = core admin-port = smsbox-port = log-file = "kannel.log" log-level = 0 box-deny-ip = "*.*.*.*" box-allow-ip = "127.0.0.1" access-log = "access.log" store-file = "kannel.store" # SMSC CONNECTIONS group = smsc smsc = smpp smsc-id = SMSC1 denied-smsc-id = SMSC2 transceiver-mode = 1 host = SMPP SMSC IP Addr port = smsc-username = "user" smsc-password = "pass" system-type = "VMA" group = smsc smsc = http smsc-id = SMSC2 denied-smsc-id = SMSC1 system-type = kannel smsc-username = "user" smsc-password = "pass" port = send-url = "http://XXX.XXX.XX/sms"; connect-allow-ip = "HTTP SMSC IP" # SMSBOX SETUP group = smsbox bearerbox-host = localhost sendsms-chars = "0123456789 +-" log-file = "smsbox.log" log-level = 0 access-log = "access.log" group = sms-service keyword = default name = "test1" max-messages = 10 concatenation = false allowed-receiver-prefix = accepted-smsc = SMSC1 split-chars = " " omit-empty = true text = "TEST1" group = sms-service keyword = default name = "test2" max-messages = 10 concatenation = false allowed-receiver-prefix = accepted-smsc = SMSC2 split-chars = " " omit-empty = true text = "TEST2" If I send sms request from SMSC1, kannel send reply back via SMSC2, but if i send sms request from SMSC2, kannel sends reply back via SMSC2 too. Then i set config block of SMSC2 above SMSC1. And if I send sms request from SMSC1, kannel sends reply back via SMSC1, but if i send sms request from SMSC2 kannel send reply back via SMSC1 too. Only if i set routing based on "allowed-prefix" in my config, then all work fine. But kannel users guide shows than i can do routing based on "smsc-id, denied-smsc-id, accepted-smsc" params. What i do wrong? Thank you beforehand. -- Best regards, Roman.
[Spam] Re: SMS routing between two SMSC
hi Pomah, On Thu, 2004-11-25 at 15:03, Роман wrote: > Dear, Sirs! > > I have two different SMSC(one SMPP based, another one based upon HTTP) in > configuration file and have some problems with > routing. I want to route reply to the same SMSC, which receive > request. I make configuration as in documentation > http://www.kannel.org/download/kannel-userguide-snapshot/userguide.html#AEN4033 > but it does not work for unknown reasons. > > CONFIG: > > group = core > admin-port = > smsbox-port = > log-file = "kannel.log" > log-level = 0 > box-deny-ip = "*.*.*.*" > box-allow-ip = "127.0.0.1" > access-log = "access.log" > store-file = "kannel.store" > > > # SMSC CONNECTIONS > > group = smsc > smsc = smpp > smsc-id = SMSC1 > denied-smsc-id = SMSC2 > transceiver-mode = 1 > host = SMPP SMSC IP Addr > port = > smsc-username = "user" > smsc-password = "pass" > system-type = "VMA" > > > group = smsc > smsc = http > smsc-id = SMSC2 > denied-smsc-id = SMSC1 > system-type = kannel > smsc-username = "user" > smsc-password = "pass" > port = > send-url = "http://XXX.XXX.XX/sms"; > connect-allow-ip = "HTTP SMSC IP" > > > # SMSBOX SETUP > > group = smsbox > bearerbox-host = localhost > sendsms-chars = "0123456789 +-" > log-file = "smsbox.log" > log-level = 0 > access-log = "access.log" > > group = sms-service > keyword = default > name = "test1" > max-messages = 10 > concatenation = false > allowed-receiver-prefix = > accepted-smsc = SMSC1 > split-chars = " " > omit-empty = true > text = "TEST1" > > group = sms-service > keyword = default > name = "test2" > max-messages = 10 > concatenation = false > allowed-receiver-prefix = > accepted-smsc = SMSC2 > split-chars = " " > omit-empty = true > text = "TEST2" > > If I send sms request from SMSC1, kannel send reply back via SMSC2, but if i > send > sms request from SMSC2 kannel send reply back via SMSC2 too. > Then i set config block of SMSC2 above SMSC1. And if I send sms > request from SMSC1, kannel send reply back via SMSC1, but if i send > sms request from SMSC2 kannel send reply back via SMSC1 too. > > Only if i set in my config routing based on "allowed-prefix", then all > work fine. But documentation say than i can do routing based upon > "smsc-id, denied-smsc-id, accepted-smsc". > > What i do wrong? > May be that u used keyword Default for both, and the Default is the keyword which will be placed at the last, and kannel will take the values of the Default from the sms services at the last. > Thank you beforehand. > * This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. *
