Kannel configuration
Hi, I have for the last two weeks been trying to configure kannel to send and receive sms using a normal mobile phone. First I tried using Nokia N70 but it did not work and later I tried using LG B2000 which also didn't work. The message am getting is that the message has been queued. Could it be that Kannnel doesn't support these two phones? Please help because I really need to have it working as soon as possible. Regards. - Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
smsc parameter been ignored?
Dear all,
I'm having some problems while trying to send a message explicitly
specifying smsc, either via http request, like this one:
http://localhost:13013/cgi-bin/sendsms?username=testerpassword=foobarfrom=[removed]to=[removed]text=sisismsc=smsc_2dlr-mask=28account=user_1
or directly inserting in send_sms, with:
insert into send_sms(momt,sender,receiver,smsc_id,msgdata)
values('MT','[removed]','[removed]','smsc_2','desde sqlbox')
I can not see why both attempts are been sent with another smsc
(smsc_1). But if include smsc=smsc_1 the message is delivered with
smsc_3 !!
Well at list its enrouted to that smsc, there are couple issues with
clickatell support: ain't no way to specify system_id (api_id) and I
think no unicode is allowed, it would be nice to allow raw parameters
to pass from cgi-bin/sendsms to custom http smsc to give flexibility for
eventual api changes. But that is not the main subject of this call for
help :)
here I reproduce the smsc definitions from my kannel.conf file (exact
same order of apperance):
# GSM smsc setup (1)
group = smsc
smsc = at
smsc-id = smsc_1
modemtype = Motorola
device = /dev/ttyACM0
speed = 115200
keepalive = 7200
my-number = [removed]
sms-center = [removed]
sim-buffering = false
# GSM smsc setup (2)
group = smsc
smsc = at
smsc-id = smsc_2
modemtype = Nokia
device = /dev/ttyACM1
speed = 115200
keepalive = 7200
my-number = [removed]
sms-center = [removed]
sim-buffering = false
group = smsc
smsc = http
smsc-id = smsc_3
system-type = clickatell
send-url = http://api.clickatell.com/http
port = 13004
smsc-username = root
smsc-password = youwish
I hope anyone can spot my error or what I'm missing. I really need to be
able to specify smsc.
best regards,
Gerardo
Re: smsc parameter been ignored?
Hi Gerardo,
Have you tried adding allowed-smsc-id = smsc_1 to your configuration file?
Kind regards,
Roland.
Gerardo Segura wrote:
Dear all,
I'm having some problems while trying to send a message explicitly
specifying smsc, either via http request, like this one:
http://localhost:13013/cgi-bin/sendsms?username=testerpassword=foobarfrom=[removed]to=[removed]text=sisismsc=smsc_2dlr-mask=28account=user_1
or directly inserting in send_sms, with:
insert into send_sms(momt,sender,receiver,smsc_id,msgdata)
values('MT','[removed]','[removed]','smsc_2','desde sqlbox')
I can not see why both attempts are been sent with another smsc
(smsc_1). But if include smsc=smsc_1 the message is delivered with
smsc_3 !!
Well at list its enrouted to that smsc, there are couple issues with
clickatell support: ain't no way to specify system_id (api_id) and I
think no unicode is allowed, it would be nice to allow raw parameters
to pass from cgi-bin/sendsms to custom http smsc to give flexibility
for eventual api changes. But that is not the main subject of this
call for help :)
here I reproduce the smsc definitions from my kannel.conf file (exact
same order of apperance):
# GSM smsc setup (1)
group = smsc
smsc = at
smsc-id = smsc_1
modemtype = Motorola
device = /dev/ttyACM0
speed = 115200
keepalive = 7200
my-number = [removed]
sms-center = [removed]
sim-buffering = false
# GSM smsc setup (2)
group = smsc
smsc = at
smsc-id = smsc_2
modemtype = Nokia
device = /dev/ttyACM1
speed = 115200
keepalive = 7200
my-number = [removed]
sms-center = [removed]
sim-buffering = false
group = smsc
smsc = http
smsc-id = smsc_3
system-type = clickatell
send-url = http://api.clickatell.com/http
port = 13004
smsc-username = root
smsc-password = youwish
I hope anyone can spot my error or what I'm missing. I really need to
be able to specify smsc.
best regards,
Gerardo
CDMA phone
Hello, Does anyone got some experience on CDMA and Kannel ? What about the CDMA samsung phone such as the U410 ? Is it working with kannl ? Regards _ Antivirus avast! http://www.avast.com : message Sortant sain. Base de donnees virale (VPS) : 080421-1, 21/04/2008 Analyse le : 22/04/2008 00:55:54 avast! - copyright (c) 1988-2008 ALWIL Software.
Re: smsc parameter been ignored?
Hi there,
Actually I have had the same problem. You can get over this by setting the
allowed-smsc-id to the same ID of the current SMSC
e.g.
# GSM smsc setup (1)
group = smsc
smsc = at
smsc-id = smsc_1
modemtype = Motorola
device = /dev/ttyACM0
speed = 115200
keepalive = 7200
my-number = [removed]
sms-center = [removed]
sim-buffering = false
allowed-smsc-id = smsc_1
# GSM smsc setup (2)
group = smsc
smsc = at
smsc-id = smsc_2
modemtype = Nokia
device = /dev/ttyACM1
speed = 115200
keepalive = 7200
my-number = [removed]
sms-center = [removed]
sim-buffering = false
allowed-smsc-id = smsc_2
group = smsc
smsc = http
smsc-id = smsc_3
system-type = clickatell
send-url = http://api.clickatell.com/http
port = 13004
smsc-username = root
smsc-password = youwish
allowed-smsc-id = smsc_1
Regards,
Remon
--
From: Rolandow [EMAIL PROTECTED]
Sent: Tuesday, April 22, 2008 9:39 AM
To: users@kannel.org
Subject: Re: smsc parameter been ignored?
Hi Gerardo,
Have you tried adding allowed-smsc-id = smsc_1 to your configuration
file?
Kind regards,
Roland.
Gerardo Segura wrote:
Dear all,
I'm having some problems while trying to send a message explicitly
specifying smsc, either via http request, like this one:
http://localhost:13013/cgi-bin/sendsms?username=testerpassword=foobarfrom=[removed]to=[removed]text=sisismsc=smsc_2dlr-mask=28account=user_1
or directly inserting in send_sms, with:
insert into send_sms(momt,sender,receiver,smsc_id,msgdata)
values('MT','[removed]','[removed]','smsc_2','desde sqlbox')
I can not see why both attempts are been sent with another smsc
(smsc_1). But if include smsc=smsc_1 the message is delivered with smsc_3
!!
Well at list its enrouted to that smsc, there are couple issues with
clickatell support: ain't no way to specify system_id (api_id) and I
think no unicode is allowed, it would be nice to allow raw parameters to
pass from cgi-bin/sendsms to custom http smsc to give flexibility for
eventual api changes. But that is not the main subject of this call for
help :)
here I reproduce the smsc definitions from my kannel.conf file (exact
same order of apperance):
# GSM smsc setup (1)
group = smsc
smsc = at
smsc-id = smsc_1
modemtype = Motorola
device = /dev/ttyACM0
speed = 115200
keepalive = 7200
my-number = [removed]
sms-center = [removed]
sim-buffering = false
# GSM smsc setup (2)
group = smsc
smsc = at
smsc-id = smsc_2
modemtype = Nokia
device = /dev/ttyACM1
speed = 115200
keepalive = 7200
my-number = [removed]
sms-center = [removed]
sim-buffering = false
group = smsc
smsc = http
smsc-id = smsc_3
system-type = clickatell
send-url = http://api.clickatell.com/http
port = 13004
smsc-username = root
smsc-password = youwish
I hope anyone can spot my error or what I'm missing. I really need to be
able to specify smsc.
best regards,
Gerardo
Re: smsc parameter been ignored?
Thanks, as you wise guys have suggested it was a matter of declaring:
allowed-smsc-id = smsc_x
inside each smsc group with that very same id
Thank you all again!
Gerardo
Otandeka Simon Peter wrote:
Hello Gerardo,
Try out the following:-
Specify the preferred-smsc-id and denied-smsc-id in the group=smsc
configuration
and also try to use forced-smsc parameter in the sendsms-user group.
It might not be complete solution but might help.
Keep me posted on the results.
Kind regards,
Peter
Rolandow wrote:
Hi Gerardo,
Have you tried adding allowed-smsc-id = smsc_1 to your configuration
file?
Kind regards,
Roland.
Gerardo Segura wrote:
Dear all,
I'm having some problems while trying to send a message explicitly
specifying smsc, either via http request, like this one:
http://localhost:13013/cgi-bin/sendsms?username=testerpassword=foobarfrom=[removed]to=[removed]text=sisismsc=smsc_2dlr-mask=28account=user_1
or directly inserting in send_sms, with:
insert into send_sms(momt,sender,receiver,smsc_id,msgdata)
values('MT','[removed]','[removed]','smsc_2','desde sqlbox')
I can not see why both attempts are been sent with another smsc
(smsc_1). But if include smsc=smsc_1 the message is delivered with
smsc_3 !!
Well at list its enrouted to that smsc, there are couple issues with
clickatell support: ain't no way to specify system_id (api_id) and I
think no unicode is allowed, it would be nice to allow raw
parameters to pass from cgi-bin/sendsms to custom http smsc to give
flexibility for eventual api changes. But that is not the main
subject of this call for help :)
here I reproduce the smsc definitions from my kannel.conf file (exact
same order of apperance):
# GSM smsc setup (1)
group = smsc
smsc = at
smsc-id = smsc_1
modemtype = Motorola
device = /dev/ttyACM0
speed = 115200
keepalive = 7200
my-number = [removed]
sms-center = [removed]
sim-buffering = false
# GSM smsc setup (2)
group = smsc
smsc = at
smsc-id = smsc_2
modemtype = Nokia
device = /dev/ttyACM1
speed = 115200
keepalive = 7200
my-number = [removed]
sms-center = [removed]
sim-buffering = false
group = smsc
smsc = http
smsc-id = smsc_3
system-type = clickatell
send-url = http://api.clickatell.com/http
port = 13004
smsc-username = root
smsc-password = youwish
I hope anyone can spot my error or what I'm missing. I really need to
be able to specify smsc.
best regards,
Gerardo
Re: Kannel configuration
Please elaborate a bit. I dont understand what you mean when you say modem configuration file or block. Thanks. Praveen .K.R [EMAIL PROTECTED] wrote: i think u need to check ur modem configuration file or block On 4/22/08, Benmute wrote: Hi, I have for the last two weeks been trying to configure kannel to send and receive sms using a normal mobile phone. First I tried using Nokia N70 but it did not work and later I tried using LG B2000 which also didn't work. The message am getting is that the message has been queued. Could it be that Kannnel doesn't support these two phones? Please help because I really need to have it working as soon as possible. Regards. Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. - Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
Re: Siemens TC35i Terminal
Hi Ricardo, Ricardo Jorge schrieb: [...] I have a question. The SIM card that we place on the TC35i is a regular SIM card? Like the one on my mobile phone. yes its an normal SIM card. Dont forget to disable sim-buffering and use ME instead. Please *dont* hotplug the SIM card, unplug the power before you remove the card. Otherwise the SIM is dead. Does anyone have any suggestions or another equipment recommendation? We use some moxa nport serial-device Device Server. So you can handle 16 Modems via network based driver. -- MfG Karsten Horsmann Key-ID 0xA78BD551 signature.asc Description: OpenPGP digital signature
[OT] Network architecture/topology for large-scale Kannel deployment
Hi All, This is somewhat off-topic, but I'm interested in hearing about how people are using Kannel in large-scale deployments. Particularly, if you are using Kannel with multiple operators for large amounts of your own traffic or as a gateway for others' traffic. By large amounts, I mean at least a few million to tens of millions of messages per day. Specifically: - What does your network topology look like? - How many and what type of machines do you dedicate to each operator connection? - How do you handle failover? What software do you use for failover? What are the pros/cons? - Do you use an external HTTP server to throttle/offset load on the sendsms interface to the smsbox? Why did you chose to do that? What are the pros/cons? - Are your operator connections always secured via VPN? What VPN software are you using? What are the pros/cons? - Are there problems you have experienced using Kannel under very high load? - What support software have you created to help you manage your deployment of Kannel? - Is the in-memory or mysql external delivery report storage mechanism sufficient, or have you implemented a more performant/robust solution? - How much NOC and engineering staff are dedicated to maintaining Kannel? Basically, I'm hoping this would be a good forum for some of the high-volume users of Kannel to share their knowledge (war stories) with the rest of us. Thanks! Garth
