Phone as modem throughput
Hello Kannel users, I'm wondering if this can be tweaked somehow, or it really depends on the phone I'm using as modem for kannel? For all of you using a phone/modem, please let me know if you get a better throughput than this (which I think is very very slow). SMS: received 0 (0 queued), sent 24 (0 queued), store size 0 SMS: inbound (0.00,0.00,0.00) msg/sec, outbound (0.12,0.13,0.13) msg/sec Thanks, Alejandro
Re: Selecting which smsc to use from HTTP interface
It works now :) Gracias Alvaro! On 12/07/2011 09:42 p.m., Alvaro Cornejo wrote: You need to add allowed-smsc denied-smsc parameters in your smsc config |-| 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 Tue, Jul 12, 2011 at 9:03 PM, Alejandro Mejia Evertszame...@gua.net wrote: Hello guys, I'm a little confused with the smsc parameter when sending a message from HTTP, as I have 2 smsc configured (oper1 and oper2). Both serve same country prefix, so I thought I was able to route the message to a specific smsc-id using http://x.x.x.x/cgi-bin/sendsms.bla+bla+bla...smsc=oper2 Messages allways get routed through oper1 I was reading this under UG: If you want to use SMS push services, requesters should then set the smsc request parameter, or 'sendsms-user' groups should be defined like this: group = sendsms-user username = operator_A password = foo forced-smsc = A group = sendsms-user username = operator_B password = bar forced-smsc = B Is it possible to select which smsc to use as I'm trying to do with HTTP's param smsc? or do I have to route using the method described on UG? Thanks in advance for your help, Alejandro
Re: HUAWEI E 1550 Modem getting disconnected
Does sim buffering cause messages to be stored on sim before being sent? If this is the case, you should disable it, so messages are sent using AT+CMGS straight, instead of using AT+CMGW and then send it. Just using my logic, as I'm not an expert. Someone else correct me if I'm wrong hehehe. On 13/07/2011 08:37 a.m., Jalal Uddin wrote: Hello Thank you for reply. I am trying lot of things to get out of this issue. interesting thing is i don't see this issue reported that much, just feels like i am not only one. my current throughput is 5, and tomorrow i am going to set it even lower, something like 0.1 to see if my USB stick modem is too weak for sending 1000 or not. i am using memory storage = SM i tried ME as well, but both causes the issue. DLR is stored in MySql. i am not sure what you mean by using same memorey for MT and MO, i found that in Kannel, only drl storage and message-storage is the two options. is there any other storage choices? Sim buffering is set to true, but i tried with false as well i think, but i am not sure about this. What do you think is the right option for such USB stick GSM modem? Modem connectivity is OK, because we have passed that stage already, our SMS sending, delivery report receving is working cool just when we try to send above 500 SMS at a single shot then it fails. can you give me some idea how can i avoid too many stored message problem. because i am not sure whether i have any option to avoid such thing. Thank you On Wed, Jul 13, 2011 at 7:42 PM, Alvaro Cornejo cornejo.alv...@gmail.com mailto:cornejo.alv...@gmail.com wrote: Hi hard to say what the problem is but _) Verify that your modem is not storing messages in its internal buffer _) Your modem migh freeze because of too many stored messages _) If you decrease the throughput thoughput=10, still having the same problem? _) Check with minicom or other terminal sw of you can connect to the modem and verify memory status. _) Some modems use the same memory allocations for MT MO... might you have MO stored in your modem? _) Set logs to debug to see if you get more info Hope helps |-| 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 http://www.perusms.NET www.smsglobal.com.mx http://www.smsglobal.com.mx y www.pravcom.com http://www.pravcom.com On Wed, Jul 13, 2011 at 7:39 AM, Jalal Uddin jalal@gmail.com mailto:jalal@gmail.com wrote: Hello everyone, I need some urgent help. I am using HUAWEI E 1550 Modem for SMS sending. When i am sending (200-250) SMS then it is working just fine, but when i am sending over 500 SMS, an error comes in, CMS ERROR: Unknown error. - maybe Sim storage is full? I'll have a look at it. (500) after that kannel tries to again initialize the modem and fails to connect it. some more errors like - Coundn't connect or Wrong or no answer to ATZ comes in. from the actions it feels like kannel bearerbox tries to rebind the modem again, but it can't. Then i shutdown the bearerbox and try to restart it, still it can't open the the modem in the same USB port now. i disconnected the modem and unplugged it and plugged it in the same port, and still the bearerbox can't connect to the device. I see that AT commands are not going through anymore, just like when i try to bind the modem in wrong USB port. may be plugging the modem in another USB port works, but what i need to know is what can be the possible reason for kannel lossing connection with the modems when more than 500 SMS is sent with throughput = 5 (in case that is important) btw , i am using either Ubuntu server 10 or Ubuntu 10.10. Does anyone faced such problem, can anyone suggest me a solution to this problem? Please help me on this, because i am wasting lot of money trying to test 1000 SMS deliver and i am suffering from this problem for more than 3 months now. Please help. Thank you
Selecting which smsc to use from HTTP interface
Hello guys, I'm a little confused with the smsc parameter when sending a message from HTTP, as I have 2 smsc configured (oper1 and oper2). Both serve same country prefix, so I thought I was able to route the message to a specific smsc-id using http://x.x.x.x/cgi-bin/sendsms.bla+bla+bla...smsc=oper2 Messages allways get routed through oper1 I was reading this under UG: /If you want to use SMS push services, requesters should then set the smsc request parameter, or 'sendsms-user' groups should be defined like this:/ /group = sendsms-user username = operator_A password = foo forced-smsc = A group = sendsms-user username = operator_B password = bar forced-smsc = B/ Is it possible to select which smsc to use as I'm trying to do with HTTP's param smsc? or do I have to route using the method described on UG? Thanks in advance for your help, Alejandro
DLR using a phone
Hello everyone. Excuse me for this dumb question, but I got lost on the UG regarding this. I'm using an LG phone and I have MT and MO working fine. When sending a message via HTTP I'm setting dlr-mask=31 I'm getting DLR correctly but only with status = 8 (delivered to smsc). When I get the sms on my mobile phone, there's nothing being received by kannel, so my guessing is that I'm setting dlr-mask with a value that doesn't ask my mobile operator to get a DLR for the sent message. Or am I wrong? Can someone explain which are valid values for dlr-mask if I want to request for full DLR to the operator? (I'm sure my operator supports DLR, because when sending from the phone with this option enabled, I get a DLR when it gets delivered on the destination's mobile) Thanks in advance for your time. Regards, Alejandro
Re: DLR using a phone
Thanks for your reply Nikos. I guess that if I call my mobile operator's customer service, they won't even know what I'm talking about hehehe. The phone I'm using is an Android, so I'll make some more tests using the phone directly to find out if it gets the delivered report. Cheers! Alejandro On 11/07/2011 04:30 p.m., Nikos Balkanas wrote: Hi, You are doing the right thing. It seems to be your smsc problem. Talk to them. dlr-mask = 31 covers all possible reports. BR, Nikos - Original Message - From: Alejandro Mejia Evertsz ame...@gua.net To: users@kannel.org Sent: Tuesday, July 12, 2011 1:17 AM Subject: DLR using a phone Hello everyone. Excuse me for this dumb question, but I got lost on the UG regarding this. I'm using an LG phone and I have MT and MO working fine. When sending a message via HTTP I'm setting dlr-mask=31 I'm getting DLR correctly but only with status = 8 (delivered to smsc). When I get the sms on my mobile phone, there's nothing being received by kannel, so my guessing is that I'm setting dlr-mask with a value that doesn't ask my mobile operator to get a DLR for the sent message. Or am I wrong? Can someone explain which are valid values for dlr-mask if I want to request for full DLR to the operator? (I'm sure my operator supports DLR, because when sending from the phone with this option enabled, I get a DLR when it gets delivered on the destination's mobile) Thanks in advance for your time. Regards, Alejandro
Re: DLR using a phone
Hi Michael, I had this already figured out by reading the UG and experimenting a little. (maybe more than a little hehehe) I'm getting the first dlr from the smsc and it's calling my dlr-url correctly (I made a perl .cgi that get's the parameters and store the new dlr status on mysql). So far, I guess we both got to the same place ;) My doubt was about the dlr-mask I was using (because I thought I wasn't requesting smsc the right thing for it to give me full dlrs). Nikos confirmed that I'm using the right mask, so now I have to strugle with my operator's smsc. I guess I'll try the other 2 operators smsc with other sims on the same phone to check if any of them provide with full dlrs. Thanks a lot for the time you took to explain me how dlr-url works. Cheers! Alejandro On 11/07/2011 05:01 p.m., Michael van der Poel wrote: Hi Alejandro, I wish, I could give you the full answer to your question, but I am struggling now for some weeks to recover the full DLR and store it in a MySQL database. I have learned some things in those weeks and I hope, I will finally accomplish it soon. What I have figured out so far, is: - you receive a first DLR (the submit_sm_resp ) that serves as an acknowledgement from your provider (e.g., 8). This just means, that the provider has received your request to send the SMS; - it is the second DLR (the deliver_sm that you are looking for where the provider confirms whether the message was actually delivered (or whether the attempts to deliver the message failed, the mobile number was incorrect, ect.). This second message is delivered over HTTP and you will have to set up a Call Back URL (something like: http://yourserver.com/dlr.php?smscID=%idlr=%danswer=%Ato=%pfrom=%Pts=%T smsID=07fceb25372fcc4cb847c7099008500echarset=%Ckannel_id=%I) This is called the dlr-url which you will have to define in your kannel configuration, and on your server you will need a php script, that your provider can call and submit the values of the delivery report to. These will come in the form of parameters such as '%p' and '%u' (see pggs. 94-95 of the UG). The php script captures these values and stores them in your database. This is the bit where I am stuck :-( There is plenty of material in the UG and in the various forums. What beginning Kannel users like you and I miss, is a good description of how it all comes together. I am sure that once we have see everything working, we will say Ah, of course!. Anyhow, I hope, the above will help to get you started and maybe the experts can correct me where I am wrong. Regards, Michael On 11/7/11 23:17, Alejandro Mejia Evertszame...@gua.net wrote: Hello everyone. Excuse me for this dumb question, but I got lost on the UG regarding this. I'm using an LG phone and I have MT and MO working fine. When sending a message via HTTP I'm setting dlr-mask=31 I'm getting DLR correctly but only with status = 8 (delivered to smsc). When I get the sms on my mobile phone, there's nothing being received by kannel, so my guessing is that I'm setting dlr-mask with a value that doesn't ask my mobile operator to get a DLR for the sent message. Or am I wrong? Can someone explain which are valid values for dlr-mask if I want to request for full DLR to the operator? (I'm sure my operator supports DLR, because when sending from the phone with this option enabled, I get a DLR when it gets delivered on the destination's mobile) Thanks in advance for your time. Regards, Alejandro
Re: DLR using a phone
Hola Michael, Are you sending through smsbox or mysqlbox? I'm using smsbox, and the URL I'm calling to send the message looks like this: http://x.x.x.x:8080/cgi-bin/sendsms?username=mysuernamepassword=mypasswordto=mymobiletext=Hello+worlddlr-mask=31dlr-url=http://y.y.y.y/dlr.cgi?id=mysmsID%26status=%d Please note the last (ampersand) is url-encoded, so the script from which I'm calling this URL doesn't think this is another parameter, and not part of dlr-url. (let me know if I'm not being clear hehehe) This way the dlr will call: http://y.y.y.y/dlr.cgi?id=mysmsIDstatus=%d Are you using Apache to run your dlr.cgi script on y.y.y.y ? If so, you could check your apache logs to see wether you're getting the request from kannel or not. Another thing I use to debug is running bearerbox and smsbox directly from the shell so I'm able to see what kannel is doing, because first of all, you should check if the smsc is posting the dlr to kannel or not. (maybe I should have started by saying this hehehe) Let me know if I can be of any help. Buena suerte! Alejandro On 11/07/2011 10:49 p.m., Michael van der Poel wrote: Hi Alejandro, Sorry, I hadn't seen Nikos's reply. I can see the deliver_sm with all the information (the full dlr) in the logs but so far I can't manage to capture it into my MySQL table. Tan cerca pero tan lejos! Soon I will crack it, though. Best of luck with your endeavours! Michael On 12/7/11 04:26, Alejandro Mejia Evertszame...@gua.net wrote: Hi Michael, I had this already figured out by reading the UG and experimenting a little. (maybe more than a little hehehe) I'm getting the first dlr from the smsc and it's calling my dlr-url correctly (I made a perl .cgi that get's the parameters and store the new dlr status on mysql). So far, I guess we both got to the same place ;) My doubt was about the dlr-mask I was using (because I thought I wasn't requesting smsc the right thing for it to give me full dlrs). Nikos confirmed that I'm using the right mask, so now I have to strugle with my operator's smsc. I guess I'll try the other 2 operators smsc with other sims on the same phone to check if any of them provide with full dlrs. Thanks a lot for the time you took to explain me how dlr-url works. Cheers! Alejandro On 11/07/2011 05:01 p.m., Michael van der Poel wrote: Hi Alejandro, I wish, I could give you the full answer to your question, but I am struggling now for some weeks to recover the full DLR and store it in a MySQL database. I have learned some things in those weeks and I hope, I will finally accomplish it soon. What I have figured out so far, is: - you receive a first DLR (the submit_sm_resp ) that serves as an acknowledgement from your provider (e.g., 8). This just means, that the provider has received your request to send the SMS; - it is the second DLR (the deliver_sm that you are looking for where the provider confirms whether the message was actually delivered (or whether the attempts to deliver the message failed, the mobile number was incorrect, ect.). This second message is delivered over HTTP and you will have to set up a Call Back URL (something like: http://yourserver.com/dlr.php?smscID=%idlr=%danswer=%Ato=%pfrom=%Pts=%T smsID=07fceb25372fcc4cb847c7099008500echarset=%Ckannel_id=%I) This is called the dlr-url which you will have to define in your kannel configuration, and on your server you will need a php script, that your provider can call and submit the values of the delivery report to. These will come in the form of parameters such as '%p' and '%u' (see pggs. 94-95 of the UG). The php script captures these values and stores them in your database. This is the bit where I am stuck :-( There is plenty of material in the UG and in the various forums. What beginning Kannel users like you and I miss, is a good description of how it all comes together. I am sure that once we have see everything working, we will say Ah, of course!. Anyhow, I hope, the above will help to get you started and maybe the experts can correct me where I am wrong. Regards, Michael On 11/7/11 23:17, Alejandro Mejia Evertszame...@gua.net wrote: Hello everyone. Excuse me for this dumb question, but I got lost on the UG regarding this. I'm using an LG phone and I have MT and MO working fine. When sending a message via HTTP I'm setting dlr-mask=31 I'm getting DLR correctly but only with status = 8 (delivered to smsc). When I get the sms on my mobile phone, there's nothing being received by kannel, so my guessing is that I'm setting dlr-mask with a value that doesn't ask my mobile operator to get a DLR for the sent message. Or am I wrong? Can someone explain which are valid values for dlr-mask if I want to request for full DLR to the operator? (I'm sure my operator supports DLR, because when sending from the phone with this option enabled, I get a DLR when it gets delivered on the destination's mobile) Thanks in advance for your time. Regards, Alejandro
Re: Charset encofing problem using sqlbox
Try sending the already encoded URL to smsbox HTTP API: test%20l'e%20%C3%A9%20%C3%A7%20%C3%A0%20%40%20%C3%AA If you need to encode some more sample text you can use this tool: http://meyerweb.com/eric/tools/dencoder/ On 05/06/2011 10:09 a.m., Rene Kluwen wrote: Issue the correct charset when sending through the http interface. Kannel should be able to convert it. *From:*Emmanuel CHANSON [mailto:emmanuelchan...@gmail.com] *Sent:* Sunday, 05 June, 2011 14:03 *To:* Rene Kluwen *Cc:* users *Subject:* Re: Charset encofing problem using sqlbox ç replaced by *Ç* and ê replaced by ? is smsc-related. You will notice that if you do not have sqlbox in between then you will get the same results. *== So how can I send and receive these corrects characters ? I tried unicode but same result. When you said smsc-related you you mean GSM modem in my case ? I am using GSM modem to send SMS.* About the different tables: Try to change the msg_data field from text to blob. *== I changed send_sms/sent_sms sqlbox table msgdata field from text to blob but same result.* Thanks Emmanuel 2011/6/5 Rene Kluwen rene.klu...@chimit.nl mailto:rene.klu...@chimit.nl ç replaced by *Ç* and ê replaced by ? is smsc-related. You will notice that if you do not have sqlbox in between then you will get the same results. About the different tables: Try to change the msg_data field from text to blob. == Rene *From:*users-boun...@kannel.org mailto:users-boun...@kannel.org [mailto:users-boun...@kannel.org mailto:users-boun...@kannel.org] *On Behalf Of *Emmanuel CHANSON *Sent:* Sunday, 05 June, 2011 13:39 *To:* users *Subject:* Charset encofing problem using sqlbox Hello, I may ask a question that has maybe already been resolved but I did not find the solution. My architecture: PHP/Mysql - smsbox HTTP api - smsbox - sqlbox - bearerbox - GSM modem Using smsbox HTTP api I am sending the following message using PHP: *test l'e é ç à @ ê* in PHP/Mysql table Outgoing SMS I have: *test l'e é ç à @ ê* in sqlbox sent_sms table I can see: *test l'e é Ç à @ ?* And I receive on my mobile: *test l'e é Ç à @ ?* So ç replaced by *Ç* and ê replaced by ? Any ideas to this problem? BR Emmanuel
