RE: RE : Can't send more than 9 sms ! Help !!!
Title: RE: RE : Can't send more than 9 sms ! Help !!! Hi, I've also faced such a problem, but as far as I know, the problem is not within DLR response since I face this when I have received all DLR status of sent messages. Interested in any possible resons/solution. Sincerely, Amin -Original Message- From: [EMAIL PROTECTED] on behalf of JML Sent: Mon 2/21/2005 12:52 PM To: users@kannel.org Subject: RE : Can't send more than 9 sms ! Help !!! Hi, Thanks for your comments... 1/ I saw that there is somewhere a possibility to set some priority for sending, and after the queue is empty the receiveing process start... But not able to find it again ? Was i dreamming ? About deferred time option, we can't use it as in our configuration, it is another server that decides which server / when / how... 2/ We try with the exact copy of the whole conf on a faster server (u160 SCSI one, with huge RAM). We get no trouble...any suggest except to change the others ..? In fact here is the whole technical conf : Distant DB server, on which we put the DB with DLR table and pending SMS table. Local servers with one modem each (for security reason ) One local server for asking the distant DB server if there's some SMS to send. If yes, takes these SMS and dispatch them locally. (we are trying to optimize all that by asking to each kannel servers the queue state but get an error/or empty queue -this is wrong!- when doing this dispatch). Can the fact that the DLR DB server is distant (and the network is 5mb from it, 128K to it) be a problem ? After reading your message, we do not understand why it's working on one server and not on the other ?? We can't desactivate the DLR so the only ways would be : 1/ trying with a replicate locate DB 2/ Setting the bearerbox to first send all the SMS, and only after to be in receive mode. Will try the 1/ but have you any idea for the 2/ ? Thanks a lot. Marco. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] De la part de Davy Chan Envoyé : lundi 21 février 2005 04:40 À : users@kannel.org Objet : Re: Can't send more than 9 sms ! Help !!! **From: JML [EMAIL PROTECTED] **To: users@kannel.org **Subject: Can't send more than 9 sms ! Help !!! **Date: Sun, 20 Feb 2005 14:51:37 +0100 ** **Hi ! **Using kannel 1.4.0, with wavecom modems, on mandrake 10.1. **We use a http interface for sending sms. **Everything is ok with a one by one SMS( sending, receiving, Mysql DLR's, **etc.) ** **But as soon as we try more ( as few as 30!) we get errors : Here is the **debug : **[...] [ ... lines deleted ... ] **What's going wrong ??? **Please heellp !! Think about what is going on in the modem. You are not only asking the modem to send the SMS, but also to receive any DLRs coming from the Operator at the same time. What is most likely happening is that the bearerbox's sending out of SMS is being interrupted by the unsolicited notifications caused by reception of the DLR from the operator. Here is how the bearerbox sends an SMS through the GSM modem: - When the bearerbox tries to send out an SMS, it issues an AT+CMGS command to the modem. - The bearerbox expects an '' symbol to indicate the modem is ready to receive the hexadecimal representation of PDU. - The bearerbox sends the hexadecimal representation of the PDU and then a ^Z (ASCII character 0x1A) to indicate it is done with the PDU. - The bearerbox expects the GSM modem to respond back with: +CMGS: ## where ## is a number representing the current outgoing SMS count. At any time the above sequence is interrupted (for example by a reception of a DLR), then the bearerbox assumes the sending of the SMS failed and will retry to submit the scenario specified about again (up to 2 addition attempts). When the DLR is sent by the Operator, the GSM modem will receive it and interrupt anything currently happening and issue an unsolicited notification (in this case a +CMT or +CMTI) to indicate it received something from the operator. This DLR can and does interfer with the bearerbox's expected send/response sequence. The only thing to do would be to: - Not request the DLR - Not send SMS until you received the DLR from the previous sent SMS - Send out the SMS but set the deferred delivery option so that you can send out all the SMS first and then get the DLR afterwards. - Re-write the AT driver to have a more robust state machine. See ya... d.c.
RE: NACK/MALFORM in DLR status
Title: RE: NACK/MALFORM in DLR status What kind of mailing list this one is? I've asked a question several days ago, and repeated it twice, but no one seems to care. -Original Message- From: Amin abbaspour Sent: Wed 1/19/2005 10:40 AM To: Amin abbaspour; users@kannel.org Subject: RE: NACK/MALFORM in DLR status Hi all, I searched a bit, and noticed that NACK/MALFORMET is generated in gw/smsc/smsc_at.c. It seems that after sending AT+CMGS whether '' does not appear or after sending message modem does not return OK msg. Has anyone encountered such a problem? Maybe I should insert a delay before reading '' and 'OK'? Sincerely, Amin -Original Message- From: [EMAIL PROTECTED] on behalf of Amin abbaspour Sent: Mon 2005/01/17 07:58 ?.? To: users@kannel.org Subject: NACK/MALFORM in DLR status Hi all, Would you please let me know what is NACK/MALFORM in DLR status, when it happens and what is to be done to resolve it. I'm using AT interface for sending SMS. Sincerely, Amin
RE: NACK/MALFORM in DLR status
Title: RE: NACK/MALFORM in DLR status Hi all, I searched a bit, and noticed that NACK/MALFORMET is generated in gw/smsc/smsc_at.c. It seems that after sending AT+CMGS whether '' does not appear or after sending message modem does not return OK msg. Has anyone encountered such a problem? Maybe I should insert a delay before reading '' and 'OK'? Sincerely, Amin -Original Message- From: [EMAIL PROTECTED] on behalf of Amin abbaspour Sent: Mon 2005/01/17 07:58 . To: users@kannel.org Subject: NACK/MALFORM in DLR status Hi all, Would you please let me know what is NACK/MALFORM in DLR status, when it happens and what is to be done to resolve it. I'm using AT interface for sending SMS. Sincerely, Amin
NACK/MALFORM in DLR status
Title: NACK/MALFORM in DLR status Hi all, Would you please let me know what is NACK/MALFORM in DLR status, when it happens and what is to be done to resolve it. I'm using AT interface for sending SMS. Sincerely, Amin
Traffic scheduling between several modems
Title: Traffic scheduling between several modems Hi, I have several modems attached to kannel machine. How can I force Kannel to send SMS using all of these modems e.g. with round robin policy. Using the same smsc-id does not solve it since the traffic always come out from the first modem in the config file. I can change smsc-id variable in each submit, but before doing that I wanted to know if the kannel itself has such an ability or not. Sincerely, Amin
RE: Wavecom and Kannel !
Title: RE: Wavecom and Kannel ! Hi, I managed to work with Mavecom Fastrack M1206 with 'speed=115200' and init-string=AT+CMGF=0 in AT2 mode. Sincerely, Amin -Original Message- From: [EMAIL PROTECTED] on behalf of James Coleman Sent: Wed 9/8/2004 12:55 PM To: Mostafa Hadian Cc: [EMAIL PROTECTED] Subject: Re: Wavecom and Kannel ! This seems familiar. Looks like kannel can't talk to port so it can't talk to modem either yet. (no responses from modem) Search list archives and you may find some useful help? http://www.mail-archive.com/[EMAIL PROTECTED]/msg02480.html Check permissions of /dev/ttyS0 and also settings (using setserial and stty) speed of port in particular I think could be it. You can set speed of port in kannel config file. http://www.mail-archive.com/[EMAIL PROTECTED]/msg02135.html do the simple things first change the speed test maybe use minicom to test what settings you can talk to the modem at. http://www.mail-archive.com/cgi-bin/htsearch?method=and=short=users_kannel_org===minicom good luck! James. On Wed, Sep 08, 2004 at 12:36:17PM +0330, Mostafa Hadian wrote: Hi Thanks for quick reply, ===Config 1 group = smsc smsc-id = modem smsc = at modemtype = wavecom device = /dev/ttyS0 allowed-smsc-id=modem Result 1=== 2004-09-08 12:22:53 [0] DEBUG: Read from modem: '' 2004-09-08 12:22:53 [0] DEBUG: AT: Command: ATF 2004-09-08 12:23:03 [0] DEBUG: Read from modem: '' 2004-09-08 12:23:03 [0] DEBUG: AT: Command: AT 2004-09-08 12:23:13 [0] DEBUG: Read from modem: '' 2004-09-08 12:23:13 [0] DEBUG: AT: Command: ATE0 2004-09-08 12:23:23 [0] DEBUG: Read from modem: '' 2004-09-08 12:23:23 [0] ERROR: Failed to create Smsc wrapper 2004-09-08 12:23:23 [0] PANIC: Cannot start with SMSC connection failing 2004-09-08 12:23:23 [0] ERROR: Error reading from fd 20: 2004-09-08 12:23:23 [0] ERROR: System error 104: Connection reset by peer 2004-09-08 12:23:23 [0] ERROR: Connection to bearerbox broke. 2004-09-08 12:23:23 [0] INFO: Received (and handled?) 0 requests in 30 seconds (0.00 per second) 2004-09-08 12:23:23 [0] INFO: Kannel smsbox terminating. 2004-09-08 12:23:23 [7] DEBUG: Thread 7 (gw/heartbeat.c:heartbeat_thread) terminates. 2004-09-08 12:23:23 [0] DEBUG: Waiting for 2 (gwlib/http.c:server_thread) to terminate 2004-09-08 12:23:23 [3] DEBUG: HTTP: No clients with requests, quitting. 2004-09-08 12:23:23 [3] DEBUG: Thread 3 (gw/smsbox.c:sendsms_thread) terminates. 2004-09-08 12:23:23 [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) terminates. 2004-09-08 12:23:23 [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) terminates. 2004-09-08 12:23:23 [0] DEBUG: Waiting for 4 (gw/smsbox.c:obey_request_thread) to terminate 2004-09-08 12:23:23 [4] DEBUG: Thread 4 (gw/smsbox.c:obey_request_thread) terminates. 2004-09-08 12:23:23 [6] DEBUG: Thread 6 (gw/smsbox.c:http_queue_thread) terminates. 2004-09-08 12:23:23 [0] DEBUG: Waiting for 5 (gw/smsbox.c:url_result_thread) to terminate 2004-09-08 12:23:23 [5] DEBUG: Thread 5 (gw/smsbox.c:url_result_thread) terminates. ** ** ===config 2== group = smsc smsc-id = modem smsc = at2 modemtype = wavecom device = /dev/ttyS0 allowed-smsc-id=modem ===Results== 2004-09-08 12:28:25 [4] DEBUG: Started thread 8 (gw/bb_boxc.c:function) 2004-09-08 12:28:25 [8] INFO: Client connected from 127.0.0.1 2004-09-08 12:28:25 [8] DEBUG: Started thread 9 (gw/bb_boxc.c:boxc_sender) 2004-09-08 12:28:25 [0] INFO: Connected to bearerbox at localhost port 13001. 2004-09-08 12:28:25 [0] DEBUG: Started thread 7 (gw/heartbeat.c:heartbeat_thread) 2004-09-08 12:28:25 [8] DEBUG: boxc_receiver: unlocking sender 2004-09-08 12:28:25 [9] DEBUG: boxc_sender: sender unlocked 2004-09-08 12:28:29 [6] INFO: AT2[modem]: closing device 2004-09-08 12:28:29 [6] INFO: AT2[modem]: opening device 2004-09-08 12:28:29 [6] DEBUG: AT2[modem]: device opened 2004-09-08 12:28:29 [6] INFO: AT2[modem]: speed set to 38400 2004-09-08 12:28:29 [6] DEBUG: AT2[modem]: -- ^M 2004-09-08 12:28:31 [6] DEBUG: AT2[modem]: -- AT^M // here is a line which response from modem contains special characters that cannt view correctly 2004-09-08 12:28:31 [6] DEBUG: AT2[modem]: -- !q! end of this line has special char // 2004-09-08 12:28:31 [6] DEBUG: AT2[modem]: -- !q!? 2004-09-08 12:28:35 [6] DEBUG: AT2[modem]: -- AT^M 2004-09-08 12:28:35 [6] DEBUG: AT2[modem]: -- , 2004-09-08 12:28:39 [6] DEBUG: AT2[modem]: -- AT^M 2004-09-08 12:28:39 [6] DEBUG: AT2[modem]: -- , 2004-09-08 12:28:43 [6] INFO: AT2[modem]: closing device 2004-09-08 12:28:43 [6] INFO: AT2[modem]: opening device 2004-09-08 12:28:43 [6] DEBUG: AT2[modem]: device opened 2004-09-08 12:28:43 [6] INFO: AT2[modem]: speed set to 19200 2004-09-08 12:28:43 [6] DEBUG: AT2[modem]: -- ^M 2004-09-08 12:28:45 [6] DEBUG: AT2[modem]: -- AT^M
RE: Fetch received SMS from phone
Hi, The following worked well with my SL45i: init-string = AT+CNMI=1,2,0,2,1 Amin Here's an init string that should work with the SL45: init-string = AT+CNMI=1,2,0,1,1 otherwise turning sim buffering on will help as well. Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Amin Abbaspour Sent: woensdag 7 juli 2004 8:33 To: [EMAIL PROTECTED] Subject: Fetch received SMS from phone Hi, I used Siemens SL45 and Nokia 6210 with Kannel. Connection is perfect and I can send SMS, but when SMS comes to phone, it does not pass it to kannel box. Has anyone encountered this? Is it some thing with CNMI init string? Thanks Amin
Re: Kannel as SMPP receiver(again)
Hi, I set the below config, but kannel complaines that not 'host' is specified. When I set 'host=my-ip', kannel tries to bind to it(and not to LISTEN on that port!) Do you have the kannel LISTEN on receive-port with below config? Thanks I have smsc accounts with tx/rx access but i use kannel only for rx and use a self developed smpp gateway for tx. I set port=0 and receive-port=port given by smsc admin Here is a sample portion from a smskannel.conf: group = smsc smsc = smpp smsc-id = ThisSMSC port = 0 receive-port = 1234 smsc-username = userid smsc-password = password Regards, Ambar Roy One97 Communications (P) Ltd. 701-702, Arunachal Building, 19 Barakhamba Road, New Delhi - 110 001 98100-94479 [EMAIL PROTECTED] - Original Message - From: Amin Abbaspour [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, July 10, 2004 6:21 PM Subject: Kannel as SMPP receiver(again) Hi all, This question seems to be asked several times, and as I searched the list, the answer is 'yes', but no where I can find a clear answer. My Question is: If I wanna receive SMS from another SMSC(they do not support 'tr') with SMPP protocol, where should I define my port number and user/password(In my machine). I looked at the user guide's SMPP part, and noticed that port/receiver-port are both about the other side SMPP, not my machine. for example when I set my receive-port, kannel tries to bind to remote host in that port. If this can be done, would you please exactly mention the place where port and username/password of my kannel box for SMPP can be set. are they the same as smsbox user/pass? Thanks in advance Amin
Kannel as SMPP receiver(again)
Hi all, This question seems to be asked several times, and as I searched the list, the answer is 'yes', but no where I can find a clear answer. My Question is: If I wanna receive SMS from another SMSC(they do not support 'tr') with SMPP protocol, where should I define my port number and user/password(In my machine). I looked at the user guide's SMPP part, and noticed that port/receiver-port are both about the other side SMPP, not my machine. for example when I set my receive-port, kannel tries to bind to remote host in that port. If this can be done, would you please exactly mention the place where port and username/password of my kannel box for SMPP can be set. are they the same as smsbox user/pass? Thanks in advance Amin
Fetch received SMS from phone
Hi, I used Siemens SL45 and Nokia 6210 with Kannel. Connection is perfect and I can send SMS, but when SMS comes to phone, it does not pass it to kannel box. Has anyone encountered this? Is it some thing with CNMI init string? Thanks Amin
Routing SMS From one SMSC to the other
Hi, I am new to kannel, sorry if the answer is vivid. I wanna route SMS coming from one SMSC to the other in kannel 1.2.1. For this purpose I use sms-service and I post the originating message with ...sms=other-smsc again to route it. This method works, but i guess there should be a better way to route messages. Tanx in advance
