Re: USSD with Kannel
Hi Arif, I believe your issue is related to Telco provider. 1 - To send an USSD request, you have to send a submit_sm packet with this TLV with value "2", which its sent accordingly by you. When you receive a deliver_sm packet with this TLV in response, the value will be "18", instead telco sends you 12 which is a reserved code and might interrupt the session (im not sure what does 12 code causes). 2 - Also submit_sm_resp from Telco is not including message id, producing an error. These two issues need to be addressed by them. On Thu, Apr 14, 2016 at 3:22 AM, Arif Noor <md.a...@forest-interactive.com> wrote: > Hi Elton, > > > > Kindly find the attachment for the logs. Note that this was done manually > since the application are not functioning yet since I need to get the MO > through first. > > > > Thank you, > > Arif Noor. > > > > *From:* Elton Hoxha [mailto:elt...@gmail.com] > *Sent:* Wednesday, April 13, 2016 8:30 PM > *To:* Arif Noor > *Cc:* Stipe Tolj; users@kannel.org > *Subject:* Re: USSD with Kannel > > > > Also please debug logs of submit SM after you are receiving initial PSSR. > > > > >
Re: USSD with Kannel
gt; > 2016-04-13 15:51:26 [12361] [9] DEBUG: Octet string dump ends. > > 2016-04-13 15:51:26 [12361] [9] DEBUG: HTTP: Status line: > > 2016-04-13 15:51:26 [12361] [9] DEBUG: HTTP: Received response: > > 2016-04-13 15:51:26 [12361] [9] DEBUG: Octet string at 0x7f3184001190: > > 2016-04-13 15:51:26 [12361] [9] DEBUG: len: 204 > > 2016-04-13 15:51:26 [12361] [9] DEBUG: size: 1024 > > 2016-04-13 15:51:26 [12361] [9] DEBUG: immutable: 0 > > 2016-04-13 15:51:26 [12361] [9] DEBUG: data: 43 61 63 68 65 2d 43 6f 6e > 74 72 6f 6c 3a 20 70 Cache-Control: p > > 2016-04-13 15:51:26 [12361] [9] DEBUG: data: 72 69 76 61 74 65 0d 0a 43 > 6f 6e 74 65 6e 74 2d rivate..Content- > > 2016-04-13 15:51:26 [12361] [9] DEBUG: data: 54 79 70 65 3a 20 74 65 78 > 74 2f 68 74 6d 6c 3b Type: text/html; > > 2016-04-13 15:51:26 [12361] [9] DEBUG: data: 20 63 68 61 72 73 65 74 3d > 75 74 66 2d 38 0d 0acharset=utf-8.. > > 2016-04-13 15:51:26 [12361] [9] DEBUG: data: 53 65 72 76 65 72 3a 20 4d > 69 63 72 6f 73 6f 66 Server: Microsof > > 2016-04-13 15:51:26 [12361] [9] DEBUG: data: 74 2d 49 49 53 2f 38 2e 35 > 0d 0a 58 2d 41 73 70 t-IIS/8.5..X-Asp > > 2016-04-13 15:51:26 [12361] [9] DEBUG: data: 4e 65 74 2d 56 65 72 73 69 > 6f 6e 3a 20 34 2e 30 Net-Version: 4.0 > > 2016-04-13 15:51:26 [12361] [9] DEBUG: data: 2e 33 30 33 31 39 0d 0a 58 > 2d 50 6f 77 65 72 65 .30319..X-Powere > > 2016-04-13 15:51:26 [12361] [9] DEBUG: data: 64 2d 42 79 3a 20 41 53 50 > 2e 4e 45 54 0d 0a 44 d-By: ASP.NET..D > > 2016-04-13 15:51:26 [12361] [9] DEBUG: data: 61 74 65 3a 20 57 65 64 2c > 20 31 33 20 41 70 72 ate: Wed, 13 Apr > > 2016-04-13 15:51:26 [12361] [9] DEBUG: data: 20 32 30 31 36 20 30 37 3a > 35 30 3a 32 34 20 472016 07:50:24 G > > 2016-04-13 15:51:26 [12361] [9] DEBUG: data: 4d 54 0d 0a 43 6f 6e 74 65 > 6e 74 2d 4c 65 6e 67 MT..Content-Leng > > 2016-04-13 15:51:26 [12361] [9] DEBUG: data: 74 68 3a 20 33 0d 0a 0d 0a > 32 30 30 th: 3200 > > 2016-04-13 15:51:26 [12361] [9] DEBUG: Octet string dump ends. > > > > The previous log provided was also from smsbox but it doesn’t seem to call > the get-url and giving the no sender/receiver error. Please do let me > know if you need any further details. > > > > Thanks, > > Arif Noor. > > > > > > *From:* Elton Hoxha [mailto:elt...@gmail.com] > *Sent:* Wednesday, April 13, 2016 3:05 PM > *To:* Arif Noor > *Cc:* Stipe Tolj; users@kannel.org > *Subject:* Re: USSD with Kannel > > > > could you paste your debug logs while you call "get-url" of your app? > > > > >
Re: USSD with Kannel
could you paste your debug logs while you call "get-url" of your app? On Wed, Apr 13, 2016 at 5:35 AM, Arif Noorwrote: > Hi All, > > Update : After I patched the kannel the error message are no longer > present however MO are still not being delivered to the application but I > received new error in SMSBOX log as per below. > > 2016-04-13 10:38:58 [12246] [5] ERROR: smsbox_req_thread: no > sender/receiver, dump follows: > 2016-04-13 10:38:58 [12246] [5] DEBUG: Msg object at 0x1378640: > 2016-04-13 10:38:58 [12246] [5] DEBUG: type: sms > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.sender: > 2016-04-13 10:38:58 [12246] [5] DEBUG: Octet string at 0x1378800: > 2016-04-13 10:38:58 [12246] [5] DEBUG:len: 12 > 2016-04-13 10:38:58 [12246] [5] DEBUG:size: 13 > 2016-04-13 10:38:58 [12246] [5] DEBUG:immutable: 0 > 2016-04-13 10:38:58 [12246] [5] DEBUG:data: 2b 36 30 31 30 33 30 36 34 > 38 3x 3x +601030648xx > 2016-04-13 10:38:58 [12246] [5] DEBUG: Octet string dump ends. > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.receiver: > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.udhdata: > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.msgdata: > 2016-04-13 10:38:58 [12246] [5] DEBUG: Octet string at 0x1378500: > 2016-04-13 10:38:58 [12246] [5] DEBUG:len: 1 > 2016-04-13 10:38:58 [12246] [5] DEBUG:size: 2 > 2016-04-13 10:38:58 [12246] [5] DEBUG:immutable: 0 > 2016-04-13 10:38:58 [12246] [5] DEBUG:data: 31 > 1 > 2016-04-13 10:38:58 [12246] [5] DEBUG: Octet string dump ends. > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.time: 1460515138 > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.smsc_id: > 2016-04-13 10:38:58 [12246] [5] DEBUG: Octet string at 0x13784b0: > 2016-04-13 10:38:58 [12246] [5] DEBUG:len: 8 > 2016-04-13 10:38:58 [12246] [5] DEBUG:size: 9 > 2016-04-13 10:38:58 [12246] [5] DEBUG:immutable: 0 > 2016-04-13 10:38:58 [12246] [5] DEBUG:data: 73 6d 70 70 55 53 53 44 >smppUSSD > 2016-04-13 10:38:58 [12246] [5] DEBUG: Octet string dump ends. > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.smsc_number: > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.foreign_id: > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.service: > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.account: > 2016-04-13 10:38:58 [12246] [5] DEBUG: Octet string at 0x1378460: > 2016-04-13 10:38:58 [12246] [5] DEBUG:len: 6 > 2016-04-13 10:38:58 [12246] [5] DEBUG:size: 7 > 2016-04-13 10:38:58 [12246] [5] DEBUG:immutable: 0 > 2016-04-13 10:38:58 [12246] [5] DEBUG:data: 7x 6x 7x 3x 3x 3x >xxx126 > 2016-04-13 10:38:58 [12246] [5] DEBUG: Octet string dump ends. > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.id: > 852d8fa4-25f3-44fb-856b-39a2fa9d8131 > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.sms_type: 0 > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.mclass: -1 > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.mwi: -1 > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.coding: 3 > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.compress: 0 > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.validity: -1 > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.deferred: -1 > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.dlr_mask: -1 > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.dlr_url: > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.pid: 0 > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.alt_dcs: 0 > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.rpi: -1 > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.charset: > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.boxc_id: > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.binfo: > 2016-04-13 10:38:58 [12246] [5] DEBUG: Octet string at 0x1378860: > 2016-04-13 10:38:58 [12246] [5] DEBUG:len: 4 > 2016-04-13 10:38:58 [12246] [5] DEBUG:size: 5 > 2016-04-13 10:38:58 [12246] [5] DEBUG:immutable: 0 > 2016-04-13 10:38:58 [12246] [5] DEBUG:data: 55 53 53 44 >USSD > 2016-04-13 10:38:58 [12246] [5] DEBUG: Octet string dump ends. > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.msg_left: -1 > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.split_parts: (nil) > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.priority: 0 > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.resend_try: -1 > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.resend_time: -1 > 2016-04-13 10:38:58 [12246] [5] DEBUG: sms.meta_data: > 2016-04-13 10:38:58 [12246] [5] DEBUG: Octet string at 0x1378890: > 2016-04-13 10:38:58 [12246] [5] DEBUG:len: 65 > 2016-04-13 10:38:58 [12246] [5] DEBUG:size: 66 > 2016-04-13 10:38:58 [12246] [5] DEBUG:immutable: 0 > 2016-04-13 10:38:58 [12246] [5] DEBUG:data: 3f 73 6d 70 70 3f 75 73 73 > 64 5f 68 6c 72 3d 36 ?smpp?ussd_hlr=6 > 2016-04-13 10:38:58 [12246] [5] DEBUG:data: 30 26 75 73 73 64 5f 6f 70 > 74 69 6f 6e 61 6c 3d 0_optional= > 2016-04-13 10:38:58 [12246] [5] DEBUG:data: 30 30 31 30 30 34 33 34 35 > 37 30 44 42 30 46 46 00100434570DB0FF
Re: USSD with Kannel
At least for me, Session = MsgID + MSISDN combination kept at application side. This part belongs to you and your skills how to keep track of them at application side and has not to do with Kannel. Kannel did its job passing the message through. While communicating with Telecom provider, refer to these parameters which are global standard; 0 = PSSD Indication 1 = PSSR Indication 2 = USSR Request 3 = USSN Request 4 to 15 = Reserved 16 = PSSD Response 17 = PSSR Response 18 = USSR Confirm 19 = USSN Confirm On Thu, Apr 7, 2016 at 10:50 AM, Arif Noor <md.a...@forest-interactive.com> wrote: > Hi Elton, > > > > Yes after the first MO, the app submit with 126 as originator. Also could > you tell me how the app supposed to differentiate the session. Is it by > using msgID or something? As for the USSR confirm, I guess I should ask the > USSDC since they passed the value 12 instead of 18. > > > > Thank you for your input so far J > > > > *From:* Elton Hoxha [mailto:elt...@gmail.com] > *Sent:* Thursday, April 07, 2016 4:38 PM > > *To:* Arif Noor > *Cc:* Donald Jackson; users@kannel.org > *Subject:* Re: USSD with Kannel > > > > After you receive the first MO do you submit the SM having 126 as > originator? If yes, maybe something wrong with the sessions you are keeping > on application side. > > > > Furthermore, at this stage of session `ussd_srv_op' should have the value > of 18 = USSR Confirm. Yours look like 12. > > > > Here is my deliver SM > > > > 2016-04-07 05:07:19 [5368] [6] DEBUG: Optional parameter tag (0x0501) > > 2016-04-07 05:07:19 [5368] [6] DEBUG: Optional parameter length read as 1 > > 2016-04-07 05:07:19 [5368] [6] DEBUG: Found configured optional parameter > `mydata' > > 2016-04-07 05:07:19 [5368] [6] DEBUG: SMPP[ussdmenu]: Got PDU: > > 2016-04-07 05:07:19 [5368] [6] DEBUG: SMPP PDU 0x9b13ba8 dump: > > 2016-04-07 05:07:19 [5368] [6] DEBUG: type_name: deliver_sm > > 2016-04-07 05:07:19 [5368] [6] DEBUG: command_id: 5 = 0x0005 > > 2016-04-07 05:07:19 [5368] [6] DEBUG: command_status: 0 = 0x > > 2016-04-07 05:07:19 [5368] [6] DEBUG: sequence_number: 12653547 = > 0x00c113eb > > 2016-04-07 05:07:19 [5368] [6] DEBUG: service_type: "USSD" > > 2016-04-07 05:07:19 [5368] [6] DEBUG: source_addr_ton: 1 = 0x0001 > > 2016-04-07 05:07:19 [5368] [6] DEBUG: source_addr_npi: 1 = 0x0001 > > 2016-04-07 05:07:19 [5368] [6] DEBUG: source_addr: "xxx" > > 2016-04-07 05:07:19 [5368] [6] DEBUG: dest_addr_ton: 1 = 0x0001 > > 2016-04-07 05:07:19 [5368] [6] DEBUG: dest_addr_npi: 1 = 0x0001 > > 2016-04-07 05:07:19 [5368] [6] DEBUG: destination_addr: "100" > > 2016-04-07 05:07:19 [5368] [6] DEBUG: esm_class: 0 = 0x > > 2016-04-07 05:07:19 [5368] [6] DEBUG: protocol_id: 0 = 0x > > 2016-04-07 05:07:19 [5368] [6] DEBUG: priority_flag: 0 = 0x > > 2016-04-07 05:07:19 [5368] [6] DEBUG: schedule_delivery_time: NULL > > 2016-04-07 05:07:19 [5368] [6] DEBUG: validity_period: NULL > > 2016-04-07 05:07:19 [5368] [6] DEBUG: registered_delivery: 0 = 0x > > 2016-04-07 05:07:19 [5368] [6] DEBUG: replace_if_present_flag: 0 = > 0x > > 2016-04-07 05:07:19 [5368] [6] DEBUG: data_coding: 0 = 0x > > 2016-04-07 05:07:19 [5368] [6] DEBUG: sm_default_msg_id: 0 = 0x > > 2016-04-07 05:07:19 [5368] [6] DEBUG: sm_length: 1 = 0x0001 > > 2016-04-07 05:07:19 [5368] [6] DEBUG: short_message: "1" > > 2016-04-07 05:07:19 [5368] [6] DEBUG: mydata: "18" > > > > > > On Thu, Apr 7, 2016 at 10:21 AM, Arif Noor <md.a...@forest-interactive.com> > wrote: > > Hi Elton, > > > > Please find below for the logs. > > > > 1435309:2016-04-01 17:20:51 [2353] [6] DEBUG: Optional parameter tag > (0x0501) > > 1435310:2016-04-01 17:20:51 [2353] [6] DEBUG: Optional parameter length > read as 1 > > 1435311:2016-04-01 17:20:51 [2353] [6] DEBUG: Found configured optional > parameter `ussd_srv_op' > > 1435312:2016-04-01 17:20:51 [2353] [6] DEBUG: Optional parameter tag > (0x4006) > > 1435313:2016-04-01 17:20:51 [2353] [6] DEBUG: Optional parameter length > read as 2 > > 1435314:2016-04-01 17:20:51 [2353] [6] DEBUG: Found configured optional > parameter `ussd_hlr' > > 1435315:2016-04-01 17:20:51 [2353] [6] DEBUG: Optional parameter tag > (0x400c) > > 1435316:2016-04-01 17:20:51 [2353] [6] DEBUG: Optional parameter length > read as 16 > > 1435317:2016-04-01 17:20:51 [2353] [6] DEBUG: Found configured optional > parameter `ussd_optional' > > 1435318:2016-04-01 17:20:5
Re: USSD with Kannel
[6] DEBUG: registered_delivery: 0 = > 0x > > 1435337:2016-04-01 17:20:51 [2353] [6] DEBUG: replace_if_present_flag: 0 > = 0x > > 1435338:2016-04-01 17:20:51 [2353] [6] DEBUG: data_coding: 15 = > 0x000f > > 1435339:2016-04-01 17:20:51 [2353] [6] DEBUG: sm_default_msg_id: 0 = > 0x > > 1435340:2016-04-01 17:20:51 [2353] [6] DEBUG: sm_length: 1 = 0x0001 > > 1435341:2016-04-01 17:20:51 [2353] [6] DEBUG: short_message: "1" > > 1435342:2016-04-01 17:20:51 [2353] [6] DEBUG: ussd_service_op: > > 1435343:2016-04-01 17:20:51 [2353] [6] DEBUG:Octet string at > 0x7f41bc01d010: > > 1435344:2016-04-01 17:20:51 [2353] [6] DEBUG: len: 1 > > 1435345:2016-04-01 17:20:51 [2353] [6] DEBUG: size: 2 > > 1435346:2016-04-01 17:20:51 [2353] [6] DEBUG: immutable: 0 > > 1435347:2016-04-01 17:20:51 [2353] [6] DEBUG: data: > 12. > > 1435348:2016-04-01 17:20:51 [2353] [6] DEBUG:Octet string dump ends. > > 1435349:2016-04-01 17:20:51 [2353] [6] DEBUG: ussd_hlr: "60" > > 1435350:2016-04-01 17:20:51 [2353] [6] DEBUG: ussd_optional: > "0010015156FE3D42" > > 1435351:2016-04-01 17:20:51 [2353] [6] DEBUG: ussd_srv_op: > > 1435352:2016-04-01 17:20:51 [2353] [6] DEBUG:Octet string at > 0x7f41bc00d440: > > 1435353:2016-04-01 17:20:51 [2353] [6] DEBUG: len: 1 > > 1435354:2016-04-01 17:20:51 [2353] [6] DEBUG: size: 2 > > 1435355:2016-04-01 17:20:51 [2353] [6] DEBUG: immutable: 0 > > 1435356:2016-04-01 17:20:51 [2353] [6] DEBUG: data: > 12. > > 1435357:2016-04-01 17:20:51 [2353] [6] DEBUG:Octet string dump ends. > > 1435358:2016-04-01 17:20:51 [2353] [6] DEBUG: SMPP PDU dump ends. > > 1435359:2016-04-01 17:20:51 [2353] [6] ERROR: SMPP[smppUSSD]: Malformed > destination_addr `(null)', may not be empty. Discarding MO message. > > > > Thank you and Regards, > > Arif Noor > > > > *From:* Elton Hoxha [mailto:elt...@gmail.com] > *Sent:* Thursday, April 07, 2016 4:15 PM > *To:* Arif Noor > *Cc:* Donald Jackson; users@kannel.org > *Subject:* Re: USSD with Kannel > > > > Hello Arif, > > > > Please paste here the pdu of deliver SM while pressing Accept or Decline. > > > > On Thu, Apr 7, 2016 at 9:54 AM, Arif Noor <md.a...@forest-interactive.com> > wrote: > > Hi Donald, > > > > Thank you for your reply, we have set up kannel to receive the TLV, just > need to know how can I differentiate the sessions. > > Also as per previous mail, I was wondering why I was getting below error. > > > > 2016-03-25 11:05:49 [2353] [6] ERROR: SMPP[smppUSSD]: Malformed > destination_addr `(null)', may not be empty. Discarding MO message. > > > > It doesn’t have any issue when I start the USSD session which it have > destination address (in this case 126) but when replying the menu let’s say > (1. Accept, 2. Decline) and I entered 1 and press send , it gave me above > error on smpp thus the application server can’t proceed since it doesn’t > receive any reply / MO. > > > > Any input in this are highly appreciated J. > > > > Thank you, > > Arif Noor. > > > > > > *From:* Donald Jackson [mailto:donaldjs...@gmail.com] > *Sent:* Tuesday, April 05, 2016 12:45 PM > *To:* Arif Noor > *Subject:* RE: USSD with Kannel > > > > Hi Arif, > > > > You will not be able to do this out the box with Kannel, you will need to > make code changes to handle your use case. > > > > Thanks, > > -- > Donald Jackson > > >
Re: USSD with Kannel
Hello Arif, Please paste here the pdu of deliver SM while pressing Accept or Decline. On Thu, Apr 7, 2016 at 9:54 AM, Arif Noorwrote: > Hi Donald, > > > > Thank you for your reply, we have set up kannel to receive the TLV, just > need to know how can I differentiate the sessions. > > Also as per previous mail, I was wondering why I was getting below error. > > > > 2016-03-25 11:05:49 [2353] [6] ERROR: SMPP[smppUSSD]: Malformed > destination_addr `(null)', may not be empty. Discarding MO message. > > > > It doesn’t have any issue when I start the USSD session which it have > destination address (in this case 126) but when replying the menu let’s say > (1. Accept, 2. Decline) and I entered 1 and press send , it gave me above > error on smpp thus the application server can’t proceed since it doesn’t > receive any reply / MO. > > > > Any input in this are highly appreciated J. > > > > Thank you, > > Arif Noor. > > > > > > *From:* Donald Jackson [mailto:donaldjs...@gmail.com] > *Sent:* Tuesday, April 05, 2016 12:45 PM > *To:* Arif Noor > *Subject:* RE: USSD with Kannel > > > > Hi Arif, > > > > You will not be able to do this out the box with Kannel, you will need to > make code changes to handle your use case. > > > > Thanks, > > -- > Donald Jackson >
Re: USSD Configuration for Kannel
It handles. Just needs to be associated with smpp-tlv group. group = smpp-tlv name = mydata tag = 0x0501 type = integer length = 1 smsc-id = ussd On Thu, Aug 14, 2014 at 7:39 PM, ha...@aeon.pk ha...@aeon.pk wrote: Kannel does not handle USSD. On Fri, Aug 8, 2014 at 8:11 PM, michael osakede ire...@yahoo.com wrote: Hello, Can anyone send me instructions on how to bind to a USSDC? I have the IP / username/password and port number. I tried connecting to using : group = smsc smsc-id = ussdpre smsc = smpp host = XX.XX.XX.XX port = XXX smsc-username = XX smsc-password = XX system-type = keepalive = 50 allowed-smsc-id = ussdpre transceiver-mode = true msg-id-type = 0x00 throughput = 30 max-pending-submits = 10 wait-ack = 600 I get this error: 2014-08-08 16:01:58 [15951] [6] ERROR: Error reading from fd 52: 2014-08-08 16:01:58 [15951] [6] ERROR: System error 104: Connection reset by peer 2014-08-08 16:01:58 [15951] [6] ERROR: SMPP[ussdpre]: Couldn't connect to SMS center (retrying in 10 seconds). 2014-08-08 16:02:08 [15951] [6] DEBUG: Connecting to XX.XX.XX.XX Is it possible to handle USSD using kannel? Michael
Re: USSD Interactive Session using metadata.
You can search on the mailing list the older posts and you will find information how to configure SMPP connection with Metadata and TLV. On Thu, Sep 26, 2013 at 9:23 AM, प्रवीण कुमार त्रिपाठी trpthp...@gmail.comwrote: Hi, I m using kannel latest svn trunk and want to use kannel for ussd interactive sessions. Can anybody tell me how to proceed for the same. Thanks in advance Regards Prabin Tipathi
Re: Detecting Numbers that are off
I`m re-reading the userguide for you; Chapter 10. SMS Delivery Reports This chapter explains how to set up Kannel to deliver delivery reports. Delivery reports are a method to tell your system if the message has arrived on the destination phone. There are different things which can happen to a message on the way to the phone which are: - Message gets rejected by the SMSC (unknown subscriber, invalid destination number etc). - Message gets accepted by the SMSC but the phone rejects the message. - Message gets accepted by the SMSC but the phone is off or out of reach. The message gets buffered. - Message gets successfully delivered. *Note: *If you want to use delivery reports, you must define a smsc-id for each smsc group. When you deliver SMS to Kannel you have to indicate what kind of delivery report messages you would like to receive back from the system. The delivery report types currently implemented are: - 1: delivery success - 2: delivery failure - 4: message buffered - 8: smsc submit - 16: smsc reject - 32: smsc intermediate notifications Regards On Wed, Sep 7, 2011 at 11:50 PM, Isaac Kamya isa...@laditelecom.com wrote: Hi all Am using the Kannel as an sms gateway. I normally send out bulk messages to many Numbers. Is it possible to detect a phone number that is off? Best Regards Isaac Kamya www.laditelecom.com
Re: Kannel SMS Parking Application
Using SMS as mobile payment channel is getting wider, but I dont see Kannel as major factor here. All application logic is beyond kannel, by processing the relevant keywords, i.e start parking; stop parking. Including billing integrations as well, which consists at definition of charging model. Either chargeable by defining a specific shortcode with the static price, or calling directly Operator Billing API to check balance and charge dynamically based on spent hours. 2011/6/21 Nikos Balkanas nbalka...@gmail.com Hi, For the benefit of the list could someone explain what is an SMS parking aplication? Maybe we have an idea about what to do. BR, Nikos - Original Message - From: Joseph Koech kipponthe...@gmail.com To: users@kannel.org Sent: Tuesday, June 21, 2011 9:47 AM Subject: Re: Kannel SMS Parking Application Hi Milan P, That really sounds great. i am mostly interested on the send/stop sms parking and the response after one stops the SMS parking. I won't mind if you omitted the payment part and shared the rest. Looking forward. Thanks. KR, Joseph. On Tue, Jun 21, 2011 at 9:26 AM, Milan P. Stanic m...@arvanta.net wrote: On Tue, 2011-06-21 at 08:16, Joseph Koech wrote: I am trying to build a simple SMS parking application. I am relatively well off with kannel but I wanted to know if anyone has tried this before and maybe point out some other tools / s/w that are required. I will also appreciate if someone will be willing to hold my hand through the development process. I did that even three times. I even intended to release one of the SMS parking application for free use but I cannot because of some NDA with payment providers. -- Kind regards, Milan --** Arvanta, IT Security http://www.arvanta.net Please do not send me e-mail containing HTML code.
Re: Network initiated USSD
Most of operators provide SMPP interface to their USSD GW. All you need to do is to contact them and provide smpp account. Also some of them can provide even web service. Meanwhile you can google about other alternatives. There are some providers which can give you API to send international USSD messages. On Tue, Jun 14, 2011 at 5:38 PM, Cezary Siwek cza...@thebestisp.co.ukwrote: Hi, some operators use SMPP as a transport for USSD messages but it's operator-specific Regards On 14/06/2011 16:27, Hammad wrote: Hi, USSD is a service that uses MAP protocol since its with HLR. You need connectiviity with HLR to recieve USSD messages. I dont think Kannel has anything relevant for USSD. Regards, Hammad Flexilogix Inc On Mon, Jun 13, 2011 at 10:43 PM, Jinson Abraham jin...@mobme.inmailto: jin...@mobme.in wrote: Can somebody help me with this? ** On Mon, Jun 13, 2011 at 12:08 PM, Jinson Abraham jin...@mobme.in mailto:jin...@mobme.in wrote: Hello All, Is it possible to send Network Initiated USSD messages from Kannel? I'm trying to develop a USSD app which sends NI USSD messages and get the user response and respond accordingly. /Thanks Regards/** *Jinson * ** -- Disclaimer: This transmission (including any attachments) may contain confidential information, privileged material or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system.
Re: Variable Definition
Hi, - variable “port” under the “group = smsc” Is the port Kannel uses to connect to the Operator/Provider - sendsms-port” under the “group = smsbox Is the port of URL that your application hits to send the sms. On Mon, May 9, 2011 at 1:47 PM, Deborah Pisani deborah.pis...@go.com.mtwrote: Hello, May someone explain what is the difference between the variable “port” under the “group = smsc” and the variable “sendsms-port” under the “group = smsbox”? Thank you. Best Regards, Deborah and Andrew
Re: storage type 'mysql' is not supported - obvious reasons already cheked
Try to install package like libmysql-devel Then... ./configure --with-malloc=native --with-mysql-dir=/usr/include/mysql --with-mysql --prefix=/usr/local/kannel 2011/4/29 Πετσούκα Τάνια ta...@tessera.gr Hello, i've read all support-mails for the storage type 'mysql' is not supported error, and i've tried all the described solutions. But error still exists. I would greatly appreciate it if you could help me on this. I run CentOS 5.6 and i've complied gateway 1.4.3 from source. ./configure --prefix=/usr/local/kannel --with-mysql Configure results for mysq as follows: - Configuring DB support ... checking whether to compile with MySQL support... searching checking for mysql_config... /usr/bin/mysql_config checking mysql version... 5.1.56 checking mysql reentrant libs... -rdynamic -L/usr/lib/mysql -lmysqlclient_r -lz -lpthread -lcrypt -lnsl -lm -lpthread -lmygcc checking for mysql_init in -lmysqlclient_r... yes checking mysql includes... -I/usr/include/mysql checking mysql/mysql.h usability... yes checking mysql/mysql.h presence... yes checking for mysql/mysql.h... yes checking mysql/mysql_version.h usability... yes checking mysql/mysql_version.h presence... yes checking for mysql/mysql_version.h... yes checking whether to compile with MySQL support... yes checking whether to compile with LibSDB support... disabled checking whether to compile with SQLite2 support... disabled checking whether to compile with SQLite3 support... disabled checking whether to compile with Oracle support... disabled checking whether to compile with PostgresSQL support... disabled --- Βearerbox respond: - 2011-04-29 11:37:53 [7954] [0] INFO: Debug_lvl = -1, log_file = none, log_lvl = 0 2011-04-29 11:37:53 [7954] [0] PANIC: DLR: storage type 'mysql' is not supported! 2011-04-29 11:37:53 [7954] [0] PANIC: bearerbox(gw_panic+0xc2) [0x80cc0b2] 2011-04-29 11:37:53 [7954] [0] PANIC: bearerbox(dlr_init+0x22c) [0x805fa9c] 2011-04-29 11:37:53 [7954] [0] PANIC: bearerbox(main+0x10a) [0x805304a] 2011-04-29 11:37:53 [7954] [0] PANIC: /lib/libc.so.6(__libc_start_main+0xdc) [0x45be9c] 2011-04-29 11:37:53 [7954] [0] PANIC: bearerbox [0x8052211] - - Petsouka Tania Web Developer Tessera Multimedia S.A Vas.Georgiou 24 Thessaloniki 54640 Tel. +302310889155 Fax: +302310889156 -
Re: Ussd development with kannel
Its better to upgrade your kannel with latest version. After it, add to your conf file following lines, so you can talk to your USSDC. group = smpp-tlv name = mydata tag = 0x0501 type = integer length = 1 smsc-id = YourID After successfull binding, the following line within sms-service section, is an example of receiving MO USSD requests, sending all needed parameters to your application. get-url = http://IP:PORT /UssdServices.asmx/GetUssdRequest?metadata=%Doriginator=%pchoice=%areceiver=%PussdId=%I You can read the user guide about explanation of these parameters. 2011/3/15 gautam sasikumar gautam...@gmail.com h, I have an operator who is forwarding the request from his USSD to my server in smpp protocol. I was wondering about how am i to catch that request in kannel and forward it to my application. Will i be able to get the parameters like the mmi that the user sent, Any input that the user gives( Like 1 for sports, 2 for News etc), the session id of that particular session in the TLV parameters of the kannel or will i get all these parameters in the text of the message. 2011/3/14 Marcin Bockowski boc...@gmail.com 2011/3/14 gautam sasikumar gautam...@gmail.com: Hiii, I am developing USSD application which is at a basic stage. I was looking for a patch for USSD in kannel version 1.4.3. I have searched the whole web but in vain. I have three basic questions. 1 Does Kannel require a patch for implementing ussd?? 2 If Kannel does require a patch, then where can i find a patch? 3 What parameters do i have set in kannel to avail ussd facilities. Hey, it all depends on your USSDC provider and supported protocols... Kannel may be used as HTTP to SMPP gateway in some case. Kind Regards, -- Marcin Boćkowski tel. +48 79 69 0 69 79
Re: Ussd development with kannel
Download and install recent version, no patch is needed. 2011/3/15 gautam sasikumar gautam...@gmail.com H, Does this mean that kannel doesn't need a patch for USSD.??? 2011/3/15 Elton Hoxha elt...@gmail.com Its better to upgrade your kannel with latest version. After it, add to your conf file following lines, so you can talk to your USSDC. group = smpp-tlv name = mydata tag = 0x0501 type = integer length = 1 smsc-id = YourID After successfull binding, the following line within sms-service section, is an example of receiving MO USSD requests, sending all needed parameters to your application. get-url = http://IP:PORT /UssdServices.asmx/GetUssdRequest?metadata=%Doriginator=%pchoice=%areceiver=%PussdId=%I You can read the user guide about explanation of these parameters. 2011/3/15 gautam sasikumar gautam...@gmail.com h, I have an operator who is forwarding the request from his USSD to my server in smpp protocol. I was wondering about how am i to catch that request in kannel and forward it to my application. Will i be able to get the parameters like the mmi that the user sent, Any input that the user gives( Like 1 for sports, 2 for News etc), the session id of that particular session in the TLV parameters of the kannel or will i get all these parameters in the text of the message. 2011/3/14 Marcin Bockowski boc...@gmail.com 2011/3/14 gautam sasikumar gautam...@gmail.com: Hiii, I am developing USSD application which is at a basic stage. I was looking for a patch for USSD in kannel version 1.4.3. I have searched the whole web but in vain. I have three basic questions. 1 Does Kannel require a patch for implementing ussd?? 2 If Kannel does require a patch, then where can i find a patch? 3 What parameters do i have set in kannel to avail ussd facilities. Hey, it all depends on your USSDC provider and supported protocols... Kannel may be used as HTTP to SMPP gateway in some case. Kind Regards, -- Marcin Boćkowski tel. %2B48%2079%2069%200%2069%2079+48 79 69 0 69 79
Re: Kannel smpp-tlv
you don`t need to patch. Download the latest svn version where TLV is supported. Include following lines in configuration file, then start your tests. group = smpp-tlv name = mydata tag = 0x0501 type = integer length = 1 smsc-id = local On Tue, Mar 8, 2011 at 3:12 PM, Imran Aghayev imran.agha...@hotmail.co.ukwrote: How to patch Kannel in order to send USSD requests over SMPP and receive responses ?
Re: Dynamic change of message i
Again you dont paste the complete conf file :) Core group includes the log-file parameter in order to log what happen with bearerbox. Your defined URL in sms-service will leave traces after bearerbox receives the MO SMS, whether its accessible or not (you may see could not fetch... error type). Be sure to set log-level = 0 log-file filename A file in which to write a log. This in addition to stdout and any log file defined in command line. Log-file in 'core' group is only used by the bearerbox. log-file filename A file in which to write a log. This in addition to stdout and any log file defined in command line. Log-file in 'core' group is only used by the bearerbox. log-file filename A file in which to write a log. This in addition to stdout and any log file defined in command line. Log-file in 'core' group is only used by the bearerbox. On Wed, Jan 26, 2011 at 1:39 PM, Bob O'Souna bobo...@yahoo.co.uk wrote: I am receiving SMS's (from CustomerABC into my 'inflow' SMSC). The task is to receive these SMS's (via inflow) and forward them (via outflow) after changing the parameters of the SMS (i.e. append some commercial text etc) At the moment, I receive the SMS from CustomerABC and retransmit (i.e inflow - outflow) without a problem. I now need to capture the SMS and change the relevant parameters and then relay the SMS. sendctrlsms.php (My script) sends the SMS in the format I require (when run from the command line). I now need Kannel to run that script instead of sending out the SMS via the default Kannel sendsms This is my sms-service group=sms-service keyword=default name=mytrap catch-all=true omit-empty=true max-messages=0 concatenation=true get-url=http://localhost/myscripts/sendctrlsms.php; My SMSCs are as below group=smsc smsc=smpp system-type=default transceiver-mode=1 smsc-username=user1 smsc-password=pass1 smsc-id=outflow denied-smsc-id=inflow host=xx.xx.xx.xx port=2978 source-addr-ton=5 source-addr-npi=0 dest-addr-ton=1 dest-addr-npi=1 interface-version=34 log-file=/var/log/kannel/smsc.log log-level=0 group=smsc smsc=smpp system-type=default transceiver-mode=1 smsc-username=user2 smsc-password=user2 smsc-id=inflow denied-smsc-id=outflow reroute-smsc-id=outflow host=xx.xx.xx.xx port=5392 source-addr-ton=5 source-addr-npi=0 dest-addr-ton=1 dest-addr-npi=1 interface-version=34 log-file=/var/log/kannel/smsc.log log-level=0 When CustomerABC sends me an SMS, there is no trace of anything in the Kannel log files at all. log_level is 0 throughout. The only proof that I have to indicate that the SMS came through is my kannel.access file ie 2011-01-26 08:26:34 Receive SMS [SMSC:inflow] [SVC:] [ACT:user2] [BINF:] [FID:] [META:?smpp?] [from:+1234567890] [to:+1987654321] [flags:-1:0:-1:0:-1] [msg:17:Hello] [udh:0:] 2011-01-26 08:26:35 Sent SMS [SMSC:outflow] [SVC:] [ACT:user2] [BINF:] [FID:] [META:?smpp?] [from:+1234567890] [to:+1987654321] [flags:-1:0:-1:0:-1] [msg:17:Hello] [udh:0:] Can you help so that sms-service's get-url traps the incoming message so that I can preprocess, before sending it out?
Re: Credit Limit
Hi, You can do it from application side by hitting send-sms url defined with proper parameters for respective SMSC links. On Thu, Dec 23, 2010 at 10:14 AM, michael osakede ire...@yahoo.com wrote: Hi Users, How can I set an SMSC Config ie: I want this smsc to send 1000 messages only, the idea is I can only send 1000 messages on this SMSC and nothing more, so once the credit is exhusted I want to route to another provider. group = smsc smsc-id=mike smsc = smpp host = xx.xx.xx.xx port = receive-port = smsc-username = smsc-password = system-type = smpp dest-addr-ton = 1 address-range = bind-addr-ton = 0 bind-addr-npi = 1 source-addr-ton = 5 source-addr-npi = 1 dest-addr-ton = 1 dest-addr-npi = 1 Michael
Re: Modified SMPP 3.4 spec
You dont need additional fields of SMPP 3.4. Defining TLV for ussd_service_op would be enough. On Thu, Dec 23, 2010 at 1:13 PM, Kanchan K kathuria.kanc...@gmail.comwrote: Hi, We have an requirement where the SMPP 3.4 is slightly modified. There are 2 new fields added to support USSD. I'd like to know if i can still use Kannel as SMS gateway. Thanks
Re: Get-Url issue
Hi, Remove keyword =, you are already using regex instead. On Wed, Dec 15, 2010 at 9:28 AM, Miguel Duarte migueldu...@gmail.comwrote: Hello, I checked the UG, added a smsbox-route with the same smsbox-id as my smsbox. But still not working! What am I missing? here is my configuration: group = core admin-port = 13000 admin-password = sucker admin-deny-ip = *.*.*.* admin-allow-ip = 192.168.1.1 wapbox-port = 13002 wdp-interface-name = * log-file = /var/log/kannel/bearerbox.log box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 dlr-storage = internal smsbox-port = 13014 group = wapbox bearerbox-host = localhost log-file = /var/log/kannel/wapbox.log group=smsc smsc=smpp smsc-id=internal interface-version=34 host=192.168.1.100 port=5016 system-id=HIDDEN smsc-password=HIDDEN system-type=default transceiver-mode=1 group = sendsms-user username = HIDDEN password = HIDDEN group = smsbox smsbox-id = myID bearerbox-host = 127.0.0.1 sendsms-port = 13013 log-level = 0 global-sender = 88145 group = smsbox-route smsbox-id = myID shortcode = 84135 group = sms-service keyword = keyword-regex = .* catch-all = yes max-messages = 0 get-url = http://localhost/sendsms.php?to=%pmsg=%a; On Wed, Dec 15, 2010 at 9:02 AM, Mohammed Saleem mohammedsl...@gmail.com wrote: you need to add a smsbox-route group, check the UG for more info Best Regards, Mohammed M I Sleem http://www.abusleem.net - Personal blog http://www.freakle.com - The Search Freak http://www.colorle.com/ On Wed, Dec 15, 2010 at 8:20 AM, Miguel Duarte migueldu...@gmail.comwrote: Hello, It seems that kannel is not forwarding the SMS it receives from the SMPP to an external website (php). I only found this that might be interesting in the bearerbox.log - [4] WARNING: smsbox_list empty! I can see in the bearerbox.log that its receiving the message. In the apache logs I can see no communication tentative from kannel. I would appreciate any help. Here is my configuration from kannel.conf: group = core admin-port = 13000 admin-password = sucker admin-deny-ip = *.*.*.* admin-allow-ip = 192.168.1.1 wapbox-port = 13002 wdp-interface-name = * log-file = /var/log/kannel/bearerbox.log box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 dlr-storage = internal smsbox-port = 13014 group = wapbox bearerbox-host = localhost log-file = /var/log/kannel/wapbox.log group=smsc smsc=smpp smsc-id=internal interface-version=34 host=192.168.1.100 port=5016 system-id=HIDDEN smsc-password=HIDDEN system-type=default transceiver-mode=1 group = sendsms-user username = usertest password = passwd1 group = smsbox bearerbox-host = 127.0.0.1 sendsms-port = 13013 log-level = 0 global-sender = 88135 group = sms-service keyword = keyword-regex = .* catch-all = yes max-messages = 0 get-url = http://localhost/sendsms.php?to=%pmsg=%a;
Re: Get-Url issue
smsbox-route is not needed in this case, remove that group and try again. On Wed, Dec 15, 2010 at 9:43 AM, Miguel Duarte migueldu...@gmail.comwrote: Hello Elton, Still pretty the same. I noticed since I introduced the smsbox-route I'm not receiving the delivery confirmation in my mobile to messages sent to my shortcode. On Wed, Dec 15, 2010 at 10:33 AM, Elton Hoxha elt...@gmail.com wrote: Hi, Remove keyword =, you are already using regex instead. On Wed, Dec 15, 2010 at 9:28 AM, Miguel Duarte migueldu...@gmail.comwrote: Hello, I checked the UG, added a smsbox-route with the same smsbox-id as my smsbox. But still not working! What am I missing? here is my configuration: group = core admin-port = 13000 admin-password = sucker admin-deny-ip = *.*.*.* admin-allow-ip = 192.168.1.1 wapbox-port = 13002 wdp-interface-name = * log-file = /var/log/kannel/bearerbox.log box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 dlr-storage = internal smsbox-port = 13014 group = wapbox bearerbox-host = localhost log-file = /var/log/kannel/wapbox.log group=smsc smsc=smpp smsc-id=internal interface-version=34 host=192.168.1.100 port=5016 system-id=HIDDEN smsc-password=HIDDEN system-type=default transceiver-mode=1 group = sendsms-user username = HIDDEN password = HIDDEN group = smsbox smsbox-id = myID bearerbox-host = 127.0.0.1 sendsms-port = 13013 log-level = 0 global-sender = 88145 group = smsbox-route smsbox-id = myID shortcode = 84135 group = sms-service keyword = keyword-regex = .* catch-all = yes max-messages = 0 get-url = http://localhost/sendsms.php?to=%pmsg=%a; On Wed, Dec 15, 2010 at 9:02 AM, Mohammed Saleem mohammedsl...@gmail.com wrote: you need to add a smsbox-route group, check the UG for more info Best Regards, Mohammed M I Sleem http://www.abusleem.net - Personal blog http://www.freakle.com - The Search Freak http://www.colorle.com/ On Wed, Dec 15, 2010 at 8:20 AM, Miguel Duarte migueldu...@gmail.comwrote: Hello, It seems that kannel is not forwarding the SMS it receives from the SMPP to an external website (php). I only found this that might be interesting in the bearerbox.log - [4] WARNING: smsbox_list empty! I can see in the bearerbox.log that its receiving the message. In the apache logs I can see no communication tentative from kannel. I would appreciate any help. Here is my configuration from kannel.conf: group = core admin-port = 13000 admin-password = sucker admin-deny-ip = *.*.*.* admin-allow-ip = 192.168.1.1 wapbox-port = 13002 wdp-interface-name = * log-file = /var/log/kannel/bearerbox.log box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 dlr-storage = internal smsbox-port = 13014 group = wapbox bearerbox-host = localhost log-file = /var/log/kannel/wapbox.log group=smsc smsc=smpp smsc-id=internal interface-version=34 host=192.168.1.100 port=5016 system-id=HIDDEN smsc-password=HIDDEN system-type=default transceiver-mode=1 group = sendsms-user username = usertest password = passwd1 group = smsbox bearerbox-host = 127.0.0.1 sendsms-port = 13013 log-level = 0 global-sender = 88135 group = sms-service keyword = keyword-regex = .* catch-all = yes max-messages = 0 get-url = http://localhost/sendsms.php?to=%pmsg=%a;
Re: Get-Url issue
2010-12-15 11:53:47 [22909] [6] DEBUG: source_addr_npi: 1 = 0x0001 2010-12-15 11:53:47 [22909] [6] DEBUG: source_addr: 258849902931 2010-12-15 11:53:47 [22909] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2010-12-15 11:53:47 [22909] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2010-12-15 11:53:47 [22909] [6] DEBUG: destination_addr: 84134134 2010-12-15 11:53:47 [22909] [6] DEBUG: esm_class: 0 = 0x 2010-12-15 11:53:47 [22909] [6] DEBUG: protocol_id: 0 = 0x 2010-12-15 11:53:47 [22909] [6] DEBUG: priority_flag: 0 = 0x 2010-12-15 11:53:47 [22909] [6] DEBUG: schedule_delivery_time: NULL 2010-12-15 11:53:47 [22909] [6] DEBUG: validity_period: NULL 2010-12-15 11:53:47 [22909] [6] DEBUG: registered_delivery: 0 = 0x 2010-12-15 11:53:47 [22909] [6] DEBUG: replace_if_present_flag: 0 = 0x 2010-12-15 11:53:47 [22909] [6] DEBUG: data_coding: 0 = 0x 2010-12-15 11:53:47 [22909] [6] DEBUG: sm_default_msg_id: 0 = 0x 2010-12-15 11:53:47 [22909] [6] DEBUG: sm_length: 4 = 0x0004 2010-12-15 11:53:47 [22909] [6] DEBUG: short_message: This is just a message 2010-12-15 11:53:47 [22909] [6] DEBUG: SMPP PDU dump ends. 2010-12-15 11:53:47 [22909] [6] WARNING: smsbox_list empty! 2010-12-15 11:53:47 [22909] [6] DEBUG: SMPP[internal]: Sending PDU: 2010-12-15 11:53:47 [22909] [6] WARNING: smsbox_list empty! 2010-12-15 11:53:47 [22909] [6] DEBUG: SMPP[internal]: Sending PDU: 2010-12-15 11:53:47 [22909] [6] DEBUG: SMPP PDU 0x2473f60 dump: 2010-12-15 11:53:47 [22909] [6] DEBUG: type_name: deliver_sm_resp 2010-12-15 11:53:47 [22909] [6] DEBUG: command_id: 2147483653 = 0x8005 2010-12-15 11:53:47 [22909] [6] DEBUG: command_status: 0 = 0x 2010-12-15 11:53:47 [22909] [6] DEBUG: sequence_number: 5 = 0x0005 2010-12-15 11:53:47 [22909] [6] DEBUG: message_id: NULL 2010-12-15 11:53:47 [22909] [6] DEBUG: SMPP PDU dump ends. 2010-12-15 11:53:47 [22909] [6] DEBUG: SMPP[internal]: throughput (0.00,0.00) 2010-12-15 11:53:47 [22909] [4] WARNING: smsbox_list empty! 2010-12-15 11:53:52 [22909] [6] DEBUG: SMPP[internal]: throughput (0.00,0.00) 2010-12-15 11:53:52 [22909] [6] DEBUG: SMPP[internal]: Got PDU: 2010-12-15 11:53:52 [22909] [6] DEBUG: SMPP PDU 0x246f380 dump: 2010-12-15 11:53:52 [22909] [6] DEBUG: type_name: enquire_link 2010-12-15 11:53:52 [22909] [6] DEBUG: command_id: 21 = 0x0015 2010-12-15 11:53:52 [22909] [6] DEBUG: command_status: 0 = 0x 2010-12-15 11:53:52 [22909] [6] DEBUG: sequence_number: 6 = 0x0006 2010-12-15 11:53:52 [22909] [6] DEBUG: SMPP PDU dump ends. 2010-12-15 11:53:52 [22909] [6] DEBUG: SMPP[internal]: Sending PDU: 2010-12-15 11:53:52 [22909] [6] DEBUG: SMPP PDU 0x2473f60 dump: 2010-12-15 11:53:52 [22909] [6] DEBUG: type_name: enquire_link_resp 2010-12-15 11:53:52 [22909] [6] DEBUG: command_id: 2147483669 = 0x8015 2010-12-15 11:53:52 [22909] [6] DEBUG: command_status: 0 = 0x 2010-12-15 11:53:52 [22909] [6] DEBUG: sequence_number: 6 = 0x0006 2010-12-15 11:53:52 [22909] [6] DEBUG: SMPP PDU dump ends. 2010-12-15 11:53:52 [22909] [6] DEBUG: SMPP[internal]: throughput (0.00,0.00) On Wed, Dec 15, 2010 at 11:15 AM, Mohammed Saleem mohammedsl...@gmail.com wrote: WARNING: smsbox_list empty! is thrown when there is no smsbox connecting to the bearerbox or there is no route to any connected smsbox, so yes it is needed please post the log for bearerbox and smsbox log files Best Regards, Mohammed M I Sleem http://www.abusleem.net - Personal blog http://www.freakle.com - The Search Freak http://www.colorle.com/ On Wed, Dec 15, 2010 at 10:56 AM, Elton Hoxha elt...@gmail.com wrote: smsbox-route is not needed in this case, remove that group and try again. On Wed, Dec 15, 2010 at 9:43 AM, Miguel Duarte migueldu...@gmail.comwrote: Hello Elton, Still pretty the same. I noticed since I introduced the smsbox-route I'm not receiving the delivery confirmation in my mobile to messages sent to my shortcode. On Wed, Dec 15, 2010 at 10:33 AM, Elton Hoxha elt...@gmail.com wrote: Hi, Remove keyword =, you are already using regex instead. On Wed, Dec 15, 2010 at 9:28 AM, Miguel Duarte migueldu...@gmail.comwrote: Hello, I checked the UG, added a smsbox-route with the same smsbox-id as my smsbox. But still not working! What am I missing? here is my configuration: group = core admin-port = 13000 admin-password = sucker admin-deny-ip = *.*.*.* admin-allow-ip = 192.168.1.1 wapbox-port = 13002 wdp-interface-name = * log-file = /var/log/kannel/bearerbox.log box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 dlr-storage = internal smsbox-port = 13014 group = wapbox bearerbox-host = localhost log-file = /var/log/kannel/wapbox.log group=smsc smsc=smpp smsc-id=internal interface-version=34 host=192.168.1.100 port=5016 system-id=HIDDEN smsc-password=HIDDEN system-type
Re: Get-Url issue
Are you running a single instance of smsbox? If not, why do you need smsbox-route? Try to remove that group and see if the incoming sms will hit your application. On Wed, Dec 15, 2010 at 11:05 AM, Miguel Duarte migueldu...@gmail.comwrote: Its a smsbox-id, which is the name in the smsbox and smsbox-route. And the other is my shortcode. On Wed, Dec 15, 2010 at 12:03 PM, Elton Hoxha elt...@gmail.com wrote: What is this ID? 2010-12-15 11:50:32 [22909] [0] DEBUG: Adding smsbox routing to id vodacom for receiver no 84134134 On Wed, Dec 15, 2010 at 10:55 AM, Miguel Duarte migueldu...@gmail.comwrote: Hello, Thanks for helping me. Here is the bearerbox.log: 2010-12-15 11:50:32 [22909] [0] INFO: Added logfile `/var/log/kannel/bearerbox.log' with level `0'. 2010-12-15 11:50:32 [22909] [0] INFO: SSL not supported, no SSL initialization done. 2010-12-15 11:50:32 [22909] [0] INFO: HTTP: Opening server at port 13000. 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller) 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread) 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 3 (gw/bb_http.c:httpadmin_run) 2010-12-15 11:50:32 [22909] [0] DEBUG: starting smsbox connection module 2010-12-15 11:50:32 [22909] [0] INFO: BOXC: 'smsbox-max-pending' not set, using default (100). 2010-12-15 11:50:32 [22909] [0] DEBUG: Adding smsbox routing to id vodacom for receiver no 84134134 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 4 (gw/bb_boxc.c:sms_to_smsboxes) 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 5 (gw/bb_boxc.c:smsboxc_run) 2010-12-15 11:50:32 [22909] [0] INFO: Set SMS resend frequency to 60 seconds. 2010-12-15 11:50:32 [22909] [0] INFO: SMS resend retry set to unlimited. 2010-12-15 11:50:32 [22909] [0] DEBUG: MO concatenated message handling enabled 2010-12-15 11:50:32 [22909] [0] INFO: DLR rerouting for smsc id internal disabled. 2010-12-15 11:50:32 [22909] [0] WARNING: SMPP: obsolete system-id variable is set, use smsc-username instead. 2010-12-15 11:50:32 [22909] [0] WARNING: SMPP: smsc-username not set, using system-id instead 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 6 (gw/smsc/smsc_smpp.c:io_thread) 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 7 (gw/bb_smscconn.c:sms_router) 2010-12-15 11:50:32 [22909] [0] DEBUG: starting UDP sender/receiver module 2010-12-15 11:50:32 [22909] [0] INFO: Adding interface * 2010-12-15 11:50:32 [22909] [0] DEBUG: udpc_create: Bound to UDP 0.0.0.0:9200 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 8 (gw/bb_udp.c:udp_receiver) 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 9 (gw/bb_udp.c:udp_sender) 2010-12-15 11:50:32 [22909] [0] DEBUG: udpc_create: Bound to UDP 0.0.0.0:9201 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 10 (gw/bb_udp.c:udp_receiver) 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 11 (gw/bb_udp.c:udp_sender) 2010-12-15 11:50:32 [22909] [0] DEBUG: starting wapbox connection module 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 12 (gw/bb_boxc.c:wdp_to_wapboxes) 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 13 (gw/bb_boxc.c:wapboxc_run) 2010-12-15 11:50:32 [22909] [0] DEBUG: starting WDP router 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 14 (gw/bearerbox.c:wdp_router) 2010-12-15 11:50:32 [22909] [0] INFO: 2010-12-15 11:50:32 [22909] [0] INFO: Kannel bearerbox II version 1.5.0 starting 2010-12-15 11:50:32 [22909] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) maps to pid 22909. 2010-12-15 11:50:32 [22909] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) maps to pid 22909. 2010-12-15 11:50:32 [22909] [2] DEBUG: HTTP: Including port 13000, fd 7 for polling in server thread 2010-12-15 11:50:32 [22909] [3] DEBUG: Thread 3 (gw/bb_http.c:httpadmin_run) maps to pid 22909. 2010-12-15 11:50:32 [22909] [4] DEBUG: Thread 4 (gw/bb_boxc.c:sms_to_smsboxes) maps to pid 22909. 2010-12-15 11:50:32 [22909] [5] DEBUG: Thread 5 (gw/bb_boxc.c:smsboxc_run) maps to pid 22909. 2010-12-15 11:50:32 [22909] [0] INFO: MAIN: Start-up done, entering mainloop 2010-12-15 11:50:32 [22909] [6] DEBUG: Thread 6 (gw/smsc/smsc_smpp.c:io_thread) maps to pid 22909. 2010-12-15 11:50:32 [22909] [6] DEBUG: Connecting to 192.168.1.100 2010-12-15 11:50:32 [22909] [7] DEBUG: Thread 7 (gw/bb_smscconn.c:sms_router) maps to pid 22909. 2010-12-15 11:50:32 [22909] [8] DEBUG: Thread 8 (gw/bb_udp.c:udp_receiver) maps to pid 22909. 2010-12-15 11:50:32 [22909] [9] DEBUG: Thread 9 (gw/bb_udp.c:udp_sender) maps to pid 22909. 2010-12-15 11:50:32 [22909] [10] DEBUG: Thread 10 (gw/bb_udp.c:udp_receiver) maps to pid 22909. 2010-12-15 11:50:32 [22909] [11] DEBUG: Thread 11 (gw/bb_udp.c:udp_sender) maps to pid 22909. 2010-12-15 11:50:32 [22909] [12] DEBUG: Thread 12 (gw/bb_boxc.c:wdp_to_wapboxes) maps to pid 22909. 2010-12-15 11:50:32
Re: Get-Url issue
Sorry, correction; If YES, why do you need smsbox-route? On Wed, Dec 15, 2010 at 11:12 AM, Elton Hoxha elt...@gmail.com wrote: Are you running a single instance of smsbox? If not, why do you need smsbox-route? Try to remove that group and see if the incoming sms will hit your application. On Wed, Dec 15, 2010 at 11:05 AM, Miguel Duarte migueldu...@gmail.comwrote: Its a smsbox-id, which is the name in the smsbox and smsbox-route. And the other is my shortcode. On Wed, Dec 15, 2010 at 12:03 PM, Elton Hoxha elt...@gmail.com wrote: What is this ID? 2010-12-15 11:50:32 [22909] [0] DEBUG: Adding smsbox routing to id vodacom for receiver no 84134134 On Wed, Dec 15, 2010 at 10:55 AM, Miguel Duarte migueldu...@gmail.com wrote: Hello, Thanks for helping me. Here is the bearerbox.log: 2010-12-15 11:50:32 [22909] [0] INFO: Added logfile `/var/log/kannel/bearerbox.log' with level `0'. 2010-12-15 11:50:32 [22909] [0] INFO: SSL not supported, no SSL initialization done. 2010-12-15 11:50:32 [22909] [0] INFO: HTTP: Opening server at port 13000. 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller) 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread) 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 3 (gw/bb_http.c:httpadmin_run) 2010-12-15 11:50:32 [22909] [0] DEBUG: starting smsbox connection module 2010-12-15 11:50:32 [22909] [0] INFO: BOXC: 'smsbox-max-pending' not set, using default (100). 2010-12-15 11:50:32 [22909] [0] DEBUG: Adding smsbox routing to id vodacom for receiver no 84134134 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 4 (gw/bb_boxc.c:sms_to_smsboxes) 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 5 (gw/bb_boxc.c:smsboxc_run) 2010-12-15 11:50:32 [22909] [0] INFO: Set SMS resend frequency to 60 seconds. 2010-12-15 11:50:32 [22909] [0] INFO: SMS resend retry set to unlimited. 2010-12-15 11:50:32 [22909] [0] DEBUG: MO concatenated message handling enabled 2010-12-15 11:50:32 [22909] [0] INFO: DLR rerouting for smsc id internal disabled. 2010-12-15 11:50:32 [22909] [0] WARNING: SMPP: obsolete system-id variable is set, use smsc-username instead. 2010-12-15 11:50:32 [22909] [0] WARNING: SMPP: smsc-username not set, using system-id instead 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 6 (gw/smsc/smsc_smpp.c:io_thread) 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 7 (gw/bb_smscconn.c:sms_router) 2010-12-15 11:50:32 [22909] [0] DEBUG: starting UDP sender/receiver module 2010-12-15 11:50:32 [22909] [0] INFO: Adding interface * 2010-12-15 11:50:32 [22909] [0] DEBUG: udpc_create: Bound to UDP 0.0.0.0:9200 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 8 (gw/bb_udp.c:udp_receiver) 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 9 (gw/bb_udp.c:udp_sender) 2010-12-15 11:50:32 [22909] [0] DEBUG: udpc_create: Bound to UDP 0.0.0.0:9201 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 10 (gw/bb_udp.c:udp_receiver) 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 11 (gw/bb_udp.c:udp_sender) 2010-12-15 11:50:32 [22909] [0] DEBUG: starting wapbox connection module 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 12 (gw/bb_boxc.c:wdp_to_wapboxes) 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 13 (gw/bb_boxc.c:wapboxc_run) 2010-12-15 11:50:32 [22909] [0] DEBUG: starting WDP router 2010-12-15 11:50:32 [22909] [0] DEBUG: Started thread 14 (gw/bearerbox.c:wdp_router) 2010-12-15 11:50:32 [22909] [0] INFO: 2010-12-15 11:50:32 [22909] [0] INFO: Kannel bearerbox II version 1.5.0 starting 2010-12-15 11:50:32 [22909] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) maps to pid 22909. 2010-12-15 11:50:32 [22909] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) maps to pid 22909. 2010-12-15 11:50:32 [22909] [2] DEBUG: HTTP: Including port 13000, fd 7 for polling in server thread 2010-12-15 11:50:32 [22909] [3] DEBUG: Thread 3 (gw/bb_http.c:httpadmin_run) maps to pid 22909. 2010-12-15 11:50:32 [22909] [4] DEBUG: Thread 4 (gw/bb_boxc.c:sms_to_smsboxes) maps to pid 22909. 2010-12-15 11:50:32 [22909] [5] DEBUG: Thread 5 (gw/bb_boxc.c:smsboxc_run) maps to pid 22909. 2010-12-15 11:50:32 [22909] [0] INFO: MAIN: Start-up done, entering mainloop 2010-12-15 11:50:32 [22909] [6] DEBUG: Thread 6 (gw/smsc/smsc_smpp.c:io_thread) maps to pid 22909. 2010-12-15 11:50:32 [22909] [6] DEBUG: Connecting to 192.168.1.100 2010-12-15 11:50:32 [22909] [7] DEBUG: Thread 7 (gw/bb_smscconn.c:sms_router) maps to pid 22909. 2010-12-15 11:50:32 [22909] [8] DEBUG: Thread 8 (gw/bb_udp.c:udp_receiver) maps to pid 22909. 2010-12-15 11:50:32 [22909] [9] DEBUG: Thread 9 (gw/bb_udp.c:udp_sender) maps to pid 22909. 2010-12-15 11:50:32 [22909] [10] DEBUG: Thread 10 (gw/bb_udp.c:udp_receiver) maps to pid 22909. 2010-12-15 11:50:32 [22909] [11] DEBUG: Thread 11 (gw/bb_udp.c:udp_sender) maps
Re: Configuration of smskannel.conf ..!
hi, If you are able to broadcast sms from gsm modem then there is no extra job needed. Manually means, open browser and hit the send sms url (cgi-bin/sendsms?...) On 12/4/10, msc pune mscp...@gmail.com wrote: I am using GSM Modem for broadcasting SMS's .I have installed the modem it is working I am able to send sms through GSM Modem. I would like to send sms manually using Kannel Gateway. What changes I am suppose to do in the smskannel.conf file. And what is the procedure to send sms after configuration. Regards MSC Pune
Re: Kannel was reset connection when receive and send large message in second
Hi, When I have encountered this error, I had a problem with the my DB, processed by application. First check the if any table lock happened and perform a debug of Process.aspx with your DB. On Fri, Nov 12, 2010 at 10:07 AM, Willy Mularto sangpr...@gmail.com wrote: It's about the webserver and or the aspx script needs to be tuned up. sangprabv sangpr...@gmail.com http://www.petitiononline.com/froyo/ On Nov 12, 2010, at 3:58 PM, Nguyen Van Minh wrote: Please help me :( On Thu, Nov 11, 2010 at 8:26 PM, Nguyen Van Minh min...@fscvietnam.comwrote: Dear Kannel users, I have BIG problem, when my Kannel receive and send about 80~100SMS/s I got some errors (see log), and Kannel server hangs some time. I need reset Kannel :(. I think, the problem is content server can't process 100 request (my content server used ASP.NET http://asp.net/) then Kannel was reset connection OR SMSCs may reset my connection? My SMSC tell me that allow 20 SMS/s (I set throughput=10). Please tell my how to resolve problem. Need I upgrade to fast content server? Thanks, 2010-11-12 02:46:32 [22457] [3] ERROR: Error reading from fd 87: 2010-11-12 02:46:32 [22457] [3] ERROR: System error 104: Connection reset by peer 2010-11-12 02:46:32 [22457] [0] ERROR: Error writing 196 octets to fd 84: 2010-11-12 02:46:32 [22457] [0] ERROR: System error 32: Broken pipe 2010-11-12 02:46:32 [22457] [8] ERROR: Error reading from fd 59: 2010-11-12 02:46:32 [22457] [8] ERROR: System error 104: Connection reset by peer 2010-11-12 02:46:32 [22457] [8] ERROR: Couldn't fetch http://*.*.*.*/zzz/Process.aspx?msgdata=Xsmbreceivetime=1289504791sender=%2B8497822394$ 2010-11-12 02:46:32 [22457] [8] ERROR: Error reading from fd 33: 2010-11-12 02:46:32 [22457] [8] ERROR: System error 104: Connection reset by peer 2010-11-12 02:46:32 [22457] [8] ERROR: Couldn't fetch http://*.*.*.*/zzz/Process.aspx?msgdata=XSAGreceivetime=1289504790sender=%2B8497479641$ 2010-11-12 02:46:32 [22457] [8] ERROR: Error reading from fd 62: 2010-11-12 02:46:32 [22457] [8] ERROR: System error 104: Connection reset by peer 2010-11-12 02:46:32 [22457] [8] ERROR: Couldn't fetch http://*.*.*.*/zzz/Process.aspx?msgdata=Xstnreceivetime=1289504786sender=%2B8497918692$ 2010-11-12 02:46:32 [22457] [8] ERROR: Error reading from fd 74: 2010-11-12 02:46:32 [22457] [8] ERROR: System error 104: Connection reset by peer 2010-11-12 02:46:32 [22457] [8] ERROR: Couldn't fetch http://*.*.*.*/zzz/Process.aspx?msgdata=Xsreceivetime=1289504785sender=%2B84979228318$ 2010-11-12 02:46:32 [22457] [8] ERROR: Error reading from fd 51: 2010-11-12 02:46:32 [22457] [8] ERROR: System error 104: Connection reset by peer 2010-11-12 02:46:32 [22457] [8] ERROR: Couldn't fetch http://*.*.*.*/zzz/dlr.aspx?auto=1smscID=telcosmsID=fe92877912a14b52bffdc852ff67c0e5$ 2010-11-12 02:46:32 [22457] [8] ERROR: Error reading from fd 54: 2010-11-12 02:46:32 [22457] [8] ERROR: System error 104: Connection reset by peer 2010-11-12 02:46:32 [22457] [8] ERROR: Couldn't fetch http://*.*.*.*/zzz/Process.aspx?msgdata=XSMBreceivetime=1289504787sender=%2B8416480153$ 2010-11-12 02:46:32 [22457] [8] ERROR: Error reading from fd 57: 2010-11-12 02:46:32 [22457] [8] ERROR: System error 104: Connection reset by peer 2010-11-12 02:46:32 [22457] [8] ERROR: Couldn't fetch http://*.*.*.*/zzz/Process.aspx?msgdata=%00X%00s%00m%00b%00+%260+0%02X%020%020+%26recei$ 2010-11-12 02:46:32 [22457] [8] ERROR: Error reading from fd 38: 2010-11-12 02:46:32 [22457] [8] ERROR: System error 104: Connection reset by peer 2010-11-12 02:46:32 [22457] [8] ERROR: Couldn't fetch http://*.*.*.*/zzz/Process.aspx?msgdata=Kreceivetime=1289504791sender=%2B841699749553$ 2010-11-12 02:46:32 [22457] [8] ERROR: Error reading from fd 31: 2010-11-12 02:46:32 [22457] [8] ERROR: System error 104: Connection reset by peer 2010-11-12 02:46:32 [22457] [8] ERROR: Couldn't fetch http://*.*.*.*/zzz/Process.aspx?msgdata=XSMBreceivetime=1289504791sender=%2B8498277693$ 2010-11-12 02:46:32 [22457] [8] ERROR: Error reading from fd 40: 2010-11-12 02:46:32 [22457] [8] ERROR: System error 104: Connection reset by peer 2010-11-12 02:46:32 [22457] [8] ERROR: Couldn't fetch http://*.*.*.*/zzz/Process.aspx?msgdata=Caumbreceivetime=1289504789sender=%2B841696253$ 2010-11-12 02:46:32 [22457] [8] ERROR: Error reading from fd 64: 2010-11-12 02:46:32 [22457] [8] ERROR: System error 104: Connection reset by peer 2010-11-12 02:46:32 [22457] [8] ERROR: Couldn't fetch http://*.*.*.*/zzz/Process.aspx?msgdata=Kreceivetime=1289504786sender=%2B841679333666$ 2010-11-12 02:46:32 [22457] [8] ERROR: Error reading from fd 41: 2010-11-12 02:46:32 [22457] [8] ERROR: System error 104: Connection reset by peer 2010-11-12 02:46:32 [22457] [8] ERROR: Couldn't fetch http://*.*.*.*/zzz/Process.aspx?msgdata=Sxmbreceivetime=1289504789sender=%2B8497332476$ 2010-11-12 02:46:32 [22457] [8] ERROR: Error reading from fd 58: --
Re: Kannel on wmware
I have test it in VM for more than 1 year, no problem occured. Just be sure for enough space, zipping logs (if u use maximum level of debug). 2010/10/25 Luís Tiago Rico lti...@present-technologies.com Hi, I want also to install kannel at several VM's, with diferent configurations for testing enviornment. I dont see any trouble there, but didn't do that yet. Give it a try and tell us how it went! :) Cheers 2010/10/25 Alex nomu...@gmail.com Hi Not worked wiith Vmware but if your challenge is to use kannel on widows you could use two options 1.Download compiled binarries by jackson and change the configuration file to your needs 2. Compile kannel on windows through cygwin http://lamdaica.com/modules/ajax/getArticleDetail.aspx?id=2lang I hope this helps On 25 October 2010 14:12, Nguyen Van Minh min...@fscvietnam.com wrote: Hi Kannel users, I want to install kannel on Wmware on Windows host server for production environment. Is kannel working stable on wmware (ubuntu)? Thanks, Minh -- FSC INFORMATICS ELECTRONICS JOINT STOCK COMPANY Add: 1st floor, 3B building, No45 Phuong Liet Str., Thanh Xuan Dist., Ha Noi, Vietnam Tel: +84-4-38688809 +84-4-38688832 Fax: +84-4-38688810 Website: http://www.fscvietnam.com ; http://www.fsc.vn Email: i...@fscvietnam.com Direct: min...@fscvietnam.com , Mobile: +84-4-904101100 -- Best regards, Alex -- Luís Tiago Rico *Present Technologies* Rua D. João de Castro, Lote 12 Urbanização Quinta da Fonte 3030-384 Coimbra Portugal
Re: USSD and shortCode programming
It is needed to agree with mobile operators to assign a smpp account for you in order to connect to their USSDC. After that you can start developing Menu and services. I`m not aware if there are global USSD providers that provide HTTP API, for example like Clickatell who does the same for SMS channel. On Tue, Oct 12, 2010 at 7:57 AM, dafodil neo.tu...@yahoo.com wrote: Hi elthox, thanks for ur time. what i need to have for ussd or short code exchage apart from kannel. can u pls give me some pointer on that. Br daf elthox wrote: I think you dont have the needed infrastructure for developing USSD application. Kannel needs to connect to USSDC through SMPP. In your case you are using modem which is not relevant in this case. On Mon, Oct 11, 2010 at 11:06 AM, dafodil neo.tu...@yahoo.com wrote: Thanks for the detail.MSISDN helps for correlation. Let me know if i m not misleading u. I am on my pc connected to modem and kannel is up and running. i wan to to initiate USSD. can it be over GSM(using my gsm modem and not GPRS/internet) or it can be only over HTTP/GPRS. can u pls give a sample configuration and url how this can be done. Thanks a lot. Br Daf elthox wrote: You stated yourself in the first post. USSD is based on sessions. So these sessions should be managed by application until network (time out, usually 3 or 5 minutes) or user releases it (when he/she interrupts the dialog). For every initial incoming/outgoing request, originated by subscriber (or vice versa), you assign a session id coorelated with MSISDN (compound key). Then u can use this key to identify the respective session until subscriber finalizes the dialog. Elton On Mon, Oct 11, 2010 at 9:53 AM, dafodil neo.tu...@yahoo.com wrote: Thanks for the reply. can u explain on this All that should be done in application side, differentiating the sessions while users access the ussd application in paralel. thanks once agian for ur time. Br daf elthox wrote: Hi, No need to to submit any patch for USSD. Configuring ussd_service_op is just enough. Then you should take care of the sessions, for which kannel is not responsible. All that should be done in application side, differentiating the sessions while users access the ussd application in paralel. You can check older posts related to configuration and how to send USSR/USSN. Regards elton On Mon, Oct 11, 2010 at 9:11 AM, dafodil neo.tu...@yahoo.com wrote: Hi List, I understand that sms is through store/foreward where as ussd is session based.is it possible to send ussd and sms to short code through kannel.i have browsed many archives where people have submitted patches so that kannel can send ussd.so far my understaning is concerned. To send USSD data we have to use a TLV parameter ussd_service_op. is it possible to do that.any pointer on shortcode programming(sending sms to shortcode) would help me to learn. Thanks. Br daf -- View this message in context: http://old.nabble.com/USSD-and-shortCode-programming-tp29931635p29931635.html Sent from the Kannel - User mailing list archive at Nabble.com. -- View this message in context: http://old.nabble.com/USSD-and-shortCode-programming-tp29931635p29931817.html Sent from the Kannel - User mailing list archive at Nabble.com. -- View this message in context: http://old.nabble.com/USSD-and-shortCode-programming-tp29931635p29932255.html Sent from the Kannel - User mailing list archive at Nabble.com. -- View this message in context: http://old.nabble.com/USSD-and-shortCode-programming-tp29931635p29940428.html Sent from the Kannel - User mailing list archive at Nabble.com.
Re: USSD and shortCode programming
Hi, No need to to submit any patch for USSD. Configuring ussd_service_op is just enough. Then you should take care of the sessions, for which kannel is not responsible. All that should be done in application side, differentiating the sessions while users access the ussd application in paralel. You can check older posts related to configuration and how to send USSR/USSN. Regards elton On Mon, Oct 11, 2010 at 9:11 AM, dafodil neo.tu...@yahoo.com wrote: Hi List, I understand that sms is through store/foreward where as ussd is session based.is it possible to send ussd and sms to short code through kannel.i have browsed many archives where people have submitted patches so that kannel can send ussd.so far my understaning is concerned. To send USSD data we have to use a TLV parameter ussd_service_op. is it possible to do that.any pointer on shortcode programming(sending sms to shortcode) would help me to learn. Thanks. Br daf -- View this message in context: http://old.nabble.com/USSD-and-shortCode-programming-tp29931635p29931635.html Sent from the Kannel - User mailing list archive at Nabble.com.
Re: USSD and shortCode programming
You stated yourself in the first post. USSD is based on sessions. So these sessions should be managed by application until network (time out, usually 3 or 5 minutes) or user releases it (when he/she interrupts the dialog). For every initial incoming/outgoing request, originated by subscriber (or vice versa), you assign a session id coorelated with MSISDN (compound key). Then u can use this key to identify the respective session until subscriber finalizes the dialog. Elton On Mon, Oct 11, 2010 at 9:53 AM, dafodil neo.tu...@yahoo.com wrote: Thanks for the reply. can u explain on this All that should be done in application side, differentiating the sessions while users access the ussd application in paralel. thanks once agian for ur time. Br daf elthox wrote: Hi, No need to to submit any patch for USSD. Configuring ussd_service_op is just enough. Then you should take care of the sessions, for which kannel is not responsible. All that should be done in application side, differentiating the sessions while users access the ussd application in paralel. You can check older posts related to configuration and how to send USSR/USSN. Regards elton On Mon, Oct 11, 2010 at 9:11 AM, dafodil neo.tu...@yahoo.com wrote: Hi List, I understand that sms is through store/foreward where as ussd is session based.is it possible to send ussd and sms to short code through kannel.i have browsed many archives where people have submitted patches so that kannel can send ussd.so far my understaning is concerned. To send USSD data we have to use a TLV parameter ussd_service_op. is it possible to do that.any pointer on shortcode programming(sending sms to shortcode) would help me to learn. Thanks. Br daf -- View this message in context: http://old.nabble.com/USSD-and-shortCode-programming-tp29931635p29931635.html Sent from the Kannel - User mailing list archive at Nabble.com. -- View this message in context: http://old.nabble.com/USSD-and-shortCode-programming-tp29931635p29931817.html Sent from the Kannel - User mailing list archive at Nabble.com.
Re: USSD and shortCode programming
I think you dont have the needed infrastructure for developing USSD application. Kannel needs to connect to USSDC through SMPP. In your case you are using modem which is not relevant in this case. On Mon, Oct 11, 2010 at 11:06 AM, dafodil neo.tu...@yahoo.com wrote: Thanks for the detail.MSISDN helps for correlation. Let me know if i m not misleading u. I am on my pc connected to modem and kannel is up and running. i wan to to initiate USSD. can it be over GSM(using my gsm modem and not GPRS/internet) or it can be only over HTTP/GPRS. can u pls give a sample configuration and url how this can be done. Thanks a lot. Br Daf elthox wrote: You stated yourself in the first post. USSD is based on sessions. So these sessions should be managed by application until network (time out, usually 3 or 5 minutes) or user releases it (when he/she interrupts the dialog). For every initial incoming/outgoing request, originated by subscriber (or vice versa), you assign a session id coorelated with MSISDN (compound key). Then u can use this key to identify the respective session until subscriber finalizes the dialog. Elton On Mon, Oct 11, 2010 at 9:53 AM, dafodil neo.tu...@yahoo.com wrote: Thanks for the reply. can u explain on this All that should be done in application side, differentiating the sessions while users access the ussd application in paralel. thanks once agian for ur time. Br daf elthox wrote: Hi, No need to to submit any patch for USSD. Configuring ussd_service_op is just enough. Then you should take care of the sessions, for which kannel is not responsible. All that should be done in application side, differentiating the sessions while users access the ussd application in paralel. You can check older posts related to configuration and how to send USSR/USSN. Regards elton On Mon, Oct 11, 2010 at 9:11 AM, dafodil neo.tu...@yahoo.com wrote: Hi List, I understand that sms is through store/foreward where as ussd is session based.is it possible to send ussd and sms to short code through kannel.i have browsed many archives where people have submitted patches so that kannel can send ussd.so far my understaning is concerned. To send USSD data we have to use a TLV parameter ussd_service_op. is it possible to do that.any pointer on shortcode programming(sending sms to shortcode) would help me to learn. Thanks. Br daf -- View this message in context: http://old.nabble.com/USSD-and-shortCode-programming-tp29931635p29931635.html Sent from the Kannel - User mailing list archive at Nabble.com. -- View this message in context: http://old.nabble.com/USSD-and-shortCode-programming-tp29931635p29931817.html Sent from the Kannel - User mailing list archive at Nabble.com. -- View this message in context: http://old.nabble.com/USSD-and-shortCode-programming-tp29931635p29932255.html Sent from the Kannel - User mailing list archive at Nabble.com.
Re: Can't receive smpp Mo message
hi, Firstly your smpp connection should be defined as tranciever. If you did so, then check sms-service group to route the MO sms to your application. On 10/10/10, Kidi Kidi kidi...@yahoo.fr wrote: I can't receive smpp Mo message, but i can sent MT message very well. Could you help me? this is my smsc = smpp config file : group = smsc smsc = smpp smsc-id = smscid host = xx.xx.xx.xx port = receive-port = 2775 smsc-username = xxx smsc-password = xxx transceiver-mode = true system-type = 'VMA' interface-version = 34 address-range = ''
Re: Unable to read message, format is not supported
maybe you are using 8-bit format (coding=1) On 10/8/10, Alvaro Cornejo cornejo.alv...@gmail.com wrote: without logs difficult to help, but it can be a charset issue? |-| 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 Fri, Oct 8, 2010 at 12:06 PM, Harbhag Singh Sohal harbhag.so...@gmail.com wrote: Today I tried to send sms to 17 different persons, but in most of the cellphones middle part of the sms was missing while few complained that whenever they tried to open the message they saw the following error Unable to read message, format is not supported. What is the reason for this ? I am sending my kannel.conf and sqlbox.conf as attachment. P.S: I am sending sms via database using sqlbox and not via http.
Re: Unable to read message, format is not supported
it depends on how the message is composed. If you dont have special characters coding=0 7-bit is appropriate. If u include special characters then 16-bit is required, coding=2. Check the user guide for send-sms parameters. On 10/8/10, Harbhag Singh Sohal harbhag.so...@gmail.com wrote: What should I do ? On Fri, Oct 8, 2010 at 11:26 PM, Elton Hoxha elt...@gmail.com wrote: maybe you are using 8-bit format (coding=1) On 10/8/10, Alvaro Cornejo cornejo.alv...@gmail.com wrote: without logs difficult to help, but it can be a charset issue? |-| 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 Fri, Oct 8, 2010 at 12:06 PM, Harbhag Singh Sohal harbhag.so...@gmail.com wrote: Today I tried to send sms to 17 different persons, but in most of the cellphones middle part of the sms was missing while few complained that whenever they tried to open the message they saw the following error Unable to read message, format is not supported. What is the reason for this ? I am sending my kannel.conf and sqlbox.conf as attachment. P.S: I am sending sms via database using sqlbox and not via http. -- Harbhag Singh Sohal Website : http://harbhag.wordpress.com/ Twitter : http://twitter.com/harbhag Facebook : http://facebook.com/harbhag Email : harbhag.so...@gmail.com
Re: Re : SMSC returned error code 0x0000000b (Invalid Destination Address) in response to submit_sm.
Both of you guys are posting from France, probably connected to the same SMSC :) Maybe operator is having any night activity and destination tables of SMSC have been affected. On Fri, Oct 8, 2010 at 1:28 AM, Kidi Kidi kidi...@yahoo.fr wrote: either i use the parameters below or not i get the same result. i have a shortcode 2845 and i want to sent a message to a long phone number. source-addr-ton=1 source-addr-npi=1 dest-addr-ton=1 dest-addr-npi=1 bind-addr-ton=1 bind-addr-npi=1 -- *De :* Emmanuel CHANSON emmanuelchan...@gmail.com *À :* Kidi Kidi kidi...@yahoo.fr *Cc :* users@kannel.org *Envoyé le :* Jeu 7 octobre 2010, 23h 12min 58s *Objet :* Re: SMSC returned error code 0x000b (Invalid Destination Address) in response to submit_sm. I have exactly the same issue at the moment and I try to determine if it is a Kannel or SMSC issue: I try different combination of TON NPI without success. For the moment I would say it is a SMSC configuration issue...but bearerbox.log - 2010-10-07 10:54:34 [16729] [6] DEBUG: SMPP[m]: throughput (0.00,0.00) 2010-10-07 10:54:34 [16729] [6] DEBUG: SMPP[m]: throughput (0.00,0.00) 2010-10-07 10:54:34 [16729] [6] DEBUG: SMPP[m]: Got PDU: 2010-10-07 10:54:34 [16729] [6] DEBUG: SMPP PDU 0xb3802be0 dump: 2010-10-07 10:54:34 [16729] [6] DEBUG: type_name: enquire_link_resp 2010-10-07 10:54:34 [16729] [6] DEBUG: command_id: 2147483669 = 0x8015 2010-10-07 10:54:34 [16729] [6] DEBUG: command_status: 0 = 0x 2010-10-07 10:54:34 [16729] [6] DEBUG: sequence_number: 37 = 0x0025 2010-10-07 10:54:34 [16729] [6] DEBUG: SMPP PDU dump ends. 2010-10-07 10:54:34 [16729] [6] DEBUG: SMPP[m]: throughput (0.00,0.00) 2010-10-07 10:55:00 [16729] [18] DEBUG: boxc_receiver: sms received 2010-10-07 10:55:00 [16729] [6] DEBUG: SMPP[m]: throughput (0.00,0.00) 2010-10-07 10:55:00 [16729] [6] DEBUG: SMPP[m]: Sending PDU: 2010-10-07 10:55:00 [16729] [6] DEBUG: SMPP PDU 0xb3803980 dump: 2010-10-07 10:55:00 [16729] [6] DEBUG: type_name: submit_sm 2010-10-07 10:55:00 [16729] [6] DEBUG: command_id: 4 = 0x0004 2010-10-07 10:55:00 [16729] [6] DEBUG: command_status: 0 = 0x 2010-10-07 10:55:00 [16729] [6] DEBUG: sequence_number: 38 = 0x0026 2010-10-07 10:55:00 [16729] [6] DEBUG: service_type: NULL 2010-10-07 10:55:00 [16729] [6] DEBUG: source_addr_ton: 2 = 0x0002 2010-10-07 10:55:00 [16729] [6] DEBUG: source_addr_npi: 1 = 0x0001 2010-10-07 10:55:00 [16729] [6] DEBUG: source_addr: 5656 2010-10-07 10:55:00 [16729] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2010-10-07 10:55:00 [16729] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2010-10-07 10:55:00 [16729] [6] DEBUG: destination_addr: x 2010-10-07 10:55:00 [16729] [6] DEBUG: esm_class: 3 = 0x0003 2010-10-07 10:55:00 [16729] [6] DEBUG: protocol_id: 0 = 0x 2010-10-07 10:55:00 [16729] [6] DEBUG: priority_flag: 0 = 0x 2010-10-07 10:55:00 [16729] [6] DEBUG: schedule_delivery_time: NULL 2010-10-07 10:55:00 [16729] [6] DEBUG: validity_period: NULL 2010-10-07 10:55:00 [16729] [6] DEBUG: registered_delivery: 0 = 0x 2010-10-07 10:55:00 [16729] [6] DEBUG: replace_if_present_flag: 0 = 0x 2010-10-07 10:55:00 [16729] [6] DEBUG: data_coding: 0 = 0x 2010-10-07 10:55:00 [16729] [6] DEBUG: sm_default_msg_id: 0 = 0x 2010-10-07 10:55:00 [16729] [6] DEBUG: sm_length: 4 = 0x0004 2010-10-07 10:55:00 [16729] [6] DEBUG: short_message: test 2010-10-07 10:55:00 [16729] [6] DEBUG: SMPP PDU dump ends. 2010-10-07 10:55:00 [16729] [6] DEBUG: SMPP[m]: throughput (1.00,0.00) 2010-10-07 10:55:00 [16729] [18] DEBUG: send_msg: sending msg to box: 127.0.0.1 2010-10-07 10:55:00 [16729] [6] DEBUG: SMPP[m]: throughput (1.00,0.00) 2010-10-07 10:55:00 [16729] [6] WARNING: SMPP: PDU NULL terminated string (message_id) has no NULL. 2010-10-07 10:55:00 [16729] [6] DEBUG: SMPP[m]: Got PDU: 2010-10-07 10:55:00 [16729] [6] DEBUG: SMPP PDU 0xb3802f50 dump: 2010-10-07 10:55:00 [16729] [6] DEBUG: type_name: submit_sm_resp 2010-10-07 10:55:00 [16729] [6] DEBUG: command_id: 2147483652 = 0x8004 2010-10-07 10:55:00 [16729] [6] DEBUG: command_status: 11 = 0x000b 2010-10-07 10:55:00 [16729] [6] DEBUG: sequence_number: 38 = 0x0026 2010-10-07 10:55:00 [16729] [6] DEBUG: message_id: NULL 2010-10-07 10:55:00 [16729] [6] DEBUG: SMPP PDU dump ends. 2010-10-07 10:55:00 [16729] [6] ERROR: SMPP[m]: *SMSC returned error code 0x000b (Invalid Destination Address) in response to submit_sm.* 2010-10-07 10:55:00 [16729] [6] DEBUG: SMPP[m]: throughput (1.00,0.00) Regards, Emmanuel 2010/10/8 Kidi Kidi kidi...@yahoo.fr Hi, I use kannel SMPP ESME and i get this error whenever i try to send a MT message : SMSC returned error code 0x000b (Invalid Destination Address) in response to submit_sm.
Re: Send single SMS to multiple recipients
Hi, What is your send-sms URL used in this case? Elton On Mon, Oct 4, 2010 at 1:29 PM, Innocent Muchedzi innoc...@syldah.comwrote: Hie I am using kannel SMPP and is working fine and my problem is to send multiple recipients at once. eg i want to send a happy birthday sms to all subscribers in my database born today and i was separating the recipient number is a space but only the first number in the list is reciving the sms message. my config file is as: # # KANNEL CORE GROUP CONFIGURATION # # group=core admin-port=13000 smsbox-port=13001 wapbox-port=13002 admin-password=linuxmysql box-deny-ip=*.*.*.* box-allow-ip=127.0.0.1 admin-deny-ip=*.*.*.* admin-allow-ip=127.0.0.1 udp-deny-ip=*.*.*.* udp-allow-ip=127.0.0.1 dlr-storage=internal store-type=spool store-location=/tmp/kannel wdp-interface-name=* log-file=/var/log/kannel/bearerbox.log access-log=/var/log/kannel/bearerbox-access.log log-level=1 unified-prefix = +267,00267,0;+,00;+264,00264 # # SMS Center Group# # # Mascom SMPP Connection ### # group=smsc smsc= smpp smsc-id = mascom16933 interface-version=34 host=removed port=removed system-id=syldah smsc-username = removed smsc-password = removed system-type = VMA address-range = '' log-file = /var/log/kannel/mascom.log log-level = 1 transceiver-mode=true throughput = 1000 unified-prefix = +267,00267,0;+,00 #receive-port = 10052 #my-number = 16933 # LeoNamibia SMPP Connection ### # group=smsc smsc= smpp smsc-id = leo16933 interface-version=34 host=removed port=removed system-id=syldah smsc-username = removed smsc-password = removed system-type = VMA address-range = '' log-file = /var/log/kannel/leanamibia.log log-level = 1 transceiver-mode=true throughput = 1000 unified-prefix = +264,00264,0;+,00 #receive-port = 10052 #my-number = 16933 # # SMSBox Group# # group = smsbox bearerbox-host = 127.0.0.1 sendsms-port = 13013 #smsbox-id = smsbox sendsms-chars = 0123456789 +-, log-file = /var/log/kannel/smsbox.log access-log = /var/log/kannel/smsbox-access.log log-level = 1 # # WAPBox Group# # group = wapbox bearerbox-host = 127.0.0.1 # #Smsbox routing Grou# # group = smsbox-route smsbox-id = mascombox smsc-id = mascom16933;leo16933 shortcode = 16933;16499 # # SMS SERVICES # # group = sms-service keyword = default text = Welcome to Mobitec Mobile Services. Your mesage contains an error couldnt be processed. SMS goodnews or classifieds or games or directory to get help info max-messages = 1 omit-empty = true ## INCLUDE FUNCTION ## include = /etc/mobitec.services # # SMS User Group # # group = sendsms-user username = removed password = removed user-deny-ip = *.*.*.* user-allow-ip = 127.0.0.1;192.168.0.10 max-messages = 1 concatenation = true omit-empty = true please advice me on how to compose the sms and if i need to adjust my config Innocent Muchedzi Creative Directory Syldah
Re: Send single SMS to multiple recipients
URL looks OK. Then post the logs generated after you hit the URL. Checking submit_sm and submit_sm resp PDU-s will be helpful. Elton On Mon, Oct 4, 2010 at 1:42 PM, Innocent Muchedzi innoc...@syldah.comwrote: http://127.0.0.1:13013/cgi-bin/sendsms?username=removedpassword=removedfrom=innocentsmsc=mascom16933to=%2B26771806864+%2B26771770994+%2B26774114816text=testing+bulkcoding=0 the text url are urlencodedhttp://127.0.0.1:13013/cgi-bin/sendsms?username=removedpassword=removedfrom=Innocentsmsc=mascom16933to=%2B26773410189text=coding=0 - Original Message - *From:* Elton Hoxha elt...@gmail.com *To:* Innocent Muchedzi innoc...@syldah.com *Cc:* users@kannel.org *Sent:* Monday, October 04, 2010 1:36 PM *Subject:* Re: Send single SMS to multiple recipients Hi, What is your send-sms URL used in this case? Elton On Mon, Oct 4, 2010 at 1:29 PM, Innocent Muchedzi innoc...@syldah.comwrote: Hie I am using kannel SMPP and is working fine and my problem is to send multiple recipients at once. eg i want to send a happy birthday sms to all subscribers in my database born today and i was separating the recipient number is a space but only the first number in the list is reciving the sms message. my config file is as: # # KANNEL CORE GROUP CONFIGURATION # # group=core admin-port=13000 smsbox-port=13001 wapbox-port=13002 admin-password=linuxmysql box-deny-ip=*.*.*.* box-allow-ip=127.0.0.1 admin-deny-ip=*.*.*.* admin-allow-ip=127.0.0.1 udp-deny-ip=*.*.*.* udp-allow-ip=127.0.0.1 dlr-storage=internal store-type=spool store-location=/tmp/kannel wdp-interface-name=* log-file=/var/log/kannel/bearerbox.log access-log=/var/log/kannel/bearerbox-access.log log-level=1 unified-prefix = +267,00267,0;+,00;+264,00264 # # SMS Center Group# # # Mascom SMPP Connection ### # group=smsc smsc= smpp smsc-id = mascom16933 interface-version=34 host=removed port=removed system-id=syldah smsc-username = removed smsc-password = removed system-type = VMA address-range = '' log-file = /var/log/kannel/mascom.log log-level = 1 transceiver-mode=true throughput = 1000 unified-prefix = +267,00267,0;+,00 #receive-port = 10052 #my-number = 16933 # LeoNamibia SMPP Connection ### # group=smsc smsc= smpp smsc-id = leo16933 interface-version=34 host=removed port=removed system-id=syldah smsc-username = removed smsc-password = removed system-type = VMA address-range = '' log-file = /var/log/kannel/leanamibia.log log-level = 1 transceiver-mode=true throughput = 1000 unified-prefix = +264,00264,0;+,00 #receive-port = 10052 #my-number = 16933 # # SMSBox Group# # group = smsbox bearerbox-host = 127.0.0.1 sendsms-port = 13013 #smsbox-id = smsbox sendsms-chars = 0123456789 +-, log-file = /var/log/kannel/smsbox.log access-log = /var/log/kannel/smsbox-access.log log-level = 1 # # WAPBox Group# # group = wapbox bearerbox-host = 127.0.0.1 # #Smsbox routing Grou# # group = smsbox-route smsbox-id = mascombox smsc-id = mascom16933;leo16933 shortcode = 16933;16499 # # SMS SERVICES # # group = sms-service keyword = default text = Welcome to Mobitec Mobile Services. Your mesage contains an error couldnt be processed. SMS goodnews or classifieds
Re: send messages to multiple numbers using sqlbox
Hi, Is this Kannel question or basic programming issue? Load your msisdn list from file or anywhere else to your table like you do for a single record. On Fri, Oct 1, 2010 at 5:59 AM, Harbhag Singh Sohal harbhag.so...@gmail.com wrote: I am using the following query to send sms INSERT INTO send_sms ( momt, sender, receiver, msgdata, sms_type ) VALUES ( 'MT', '1234', '1234567890', 'Hello world', 2 ); I can send message to the single number without any problem but I want to know how can I send message to multiple numbers. From http interface I can achieve this by simply typing multiple numbers with + sign between them.
Re: DLR Problem
Hi, Does this happen when you remove msg-id-type=0X02 from your configuration? On Thu, Sep 30, 2010 at 2:43 PM, hafez ahmad hafezad...@gmail.com wrote: Hi All, I have problem with the DLR that DLR row not found, I use msg-id-type=0X02 , but I still have the problem, please note also that this problem not always happened, sometimes the kannel finds the DLR row in the database. Also I have note the following the TS field in the DLR table mean reference to the Manual field-timestamp = ts field-timestamp (m) string The table field that is used for the timestamp data but as we see in the below log: 2010-09-30 16:12:01 [23945] [15] DEBUG: sql: SELECT mask, service, url, source, destination, boxc FROM dlr WHERE smsc='MYSMPP' AND * ts='1657099323'*; but the ts here is the message id not the Timestamp , do you have any ideas about that ? 2010-09-30 16:12:01 [23945] [15] DEBUG: len: 120 2010-09-30 16:12:01 [23945] [15] DEBUG: size: 121 2010-09-30 16:12:01 [23945] [15] DEBUG: immutable: 0 2010-09-30 16:12:01 [23945] [15] DEBUG: data: 69 64 3a 36 32 43 35 35 34 33 42 20 73 75 62 3a id:62C5543B sub: 2010-09-30 16:12:01 [23945] [15] DEBUG: data: 30 30 31 20 64 6c 76 72 64 3a 30 30 31 20 73 75 001 dlvrd:001 su 2010-09-30 16:12:01 [23945] [15] DEBUG: data: 62 6d 69 74 20 64 61 74 65 3a 31 30 30 39 33 30 bmit date:100930 2010-09-30 16:12:01 [23945] [15] DEBUG: data: 31 36 31 32 20 64 6f 6e 65 20 64 61 74 65 3a 31 1612 done date:1 2010-09-30 16:12:01 [23945] [15] DEBUG: data: 30 30 39 33 30 31 36 31 32 20 73 74 61 74 3a 52 009301612 stat:R 2010-09-30 16:12:01 [23945] [15] DEBUG: data: 45 4a 45 43 54 44 20 65 72 72 3a 30 30 30 20 74 EJECTD err:000 t 2010-09-30 16:12:01 [23945] [15] DEBUG: data: 65 78 74 3a 20 20 20 20 20 20 20 20 20 20 20 20 ext: 2010-09-30 16:12:01 [23945] [15] DEBUG: data: 20 20 20 20 20 20 20 20 2010-09-30 16:12:01 [23945] [15] DEBUG:Octet string dump ends. 2010-09-30 16:12:01 [23945] [15] DEBUG: SMPP PDU dump ends. 2010-09-30 16:12:01 [23945] [15] DEBUG: SMPP[MYSMPP] handle_pdu, got DLR 2010-09-30 16:12:01 [23945] [15] DEBUG: DLR[mysql]: Looking for DLR smsc=MYSMPP, ts=1657099323, dst=9XX, type=2 2010-09-30 16:12:01 [23945] [15] DEBUG: sql: SELECT mask, service, url, source, destination, boxc FROM dlr WHERE smsc='MYSMPP' AND ts='1657099323'; 2010-09-30 16:12:01 [23945] [15] DEBUG: no rows found 2010-09-30 16:12:01 [23945] [15] WARNING: DLR[mysql]: DLR from SMSCMYSMPP for DST9XX not found. Regards and very thanks Hafez
Re: how to store messages and dlr in mysql
Hi, You configured mysql below is about storing pending deliveries and not messages. If the message is delivered, the respective record in dlr table is deleted, thats why you dont see those. In order to play with texts and contacts, do it in application side. I assume you have some db there storing incoming or outgoing SMS. On Mon, Sep 27, 2010 at 4:43 PM, mac...@fastermail.com wrote: I have successfully managed to start kannel gateway with mysql connected as you can see from the log file provided below but the challenge is when i send and receive the messages the delivery reports are not stored in the mysql even when i have provided the required configuration as you can see from my configuration file below. Moving forward according to what the user guide says you can store the received messages and the phone numbers of the senders in mysql but am a bit stack on how i can do that.Please provide me with the details that are needed to straight away post the received messages and the numbers into the database.If possible tell me the steps that i must undertake. The project that am undertaking requires messages and phone numbers to be stored in mysql database so that i can dynamically play around with the contact details but to do that i need a way of sending both the messages and phone numbers into the mysql database. bearerbox log file 2010-09-27 01:57:36 [3146] [0] INFO: Debug_lvl = 1, log_file = none, log_lvl = 0 2010-09-27 01:57:36 [3146] [0] INFO: Mutex gwlib/list.c:135: 196 locks, 0 collisions. 2010-09-27 01:57:36 [3146] [0] INFO: Mutex gwlib/list.c:135: 27 locks, 0 collisions. 2010-09-27 01:57:36 [3146] [0] INFO: Mutex gwlib/list.c:135: 13 locks, 0 collisions. 2010-09-27 01:57:36 [3146] [0] INFO: Mutex gwlib/list.c:135: 15 locks, 0 collisions. 2010-09-27 01:57:36 [3146] [0] INFO: Mutex gwlib/list.c:135: 9 locks, 0 collisions. 2010-09-27 01:57:36 [3146] [0] INFO: Mutex gwlib/list.c:135: 11 locks, 0 collisions. 2010-09-27 01:57:36 [3146] [0] INFO: Mutex gwlib/list.c:135: 7 locks, 0 collisions. 2010-09-27 01:57:36 [3146] [0] INFO: Mutex gwlib/list.c:135: 7 locks, 0 collisions. 2010-09-27 01:57:36 [3146] [0] INFO: Mutex gwlib/list.c:135: 13 locks, 0 collisions. 2010-09-27 01:57:36 [3146] [0] INFO: Mutex gwlib/list.c:135: 25 locks, 0 collisions. 2010-09-27 01:57:36 [3146] [0] INFO: Mutex gwlib/list.c:135: 197 locks, 0 collisions. 2010-09-27 01:57:36 [3146] [0] INFO: Mutex gwlib/list.c:135: 3 locks, 0 collisions. 2010-09-27 01:57:36 [3146] [0] INFO: Mutex gwlib/list.c:135: 2 locks, 0 collisions. 2010-09-27 01:57:36 [3146] [0] INFO: MYSQL: Connected to server at localhost. 2010-09-27 01:57:36 [3146] [0] INFO: MYSQL: server version 5.1.45, client version 5.1.45. 2010-09-27 01:57:36 [3146] [0] INFO: DLR using storage type: mysql 2010-09-27 01:57:36 [3146] [0] INFO: Added logfile `/tmp/kannel.log' with level `0'. 2010-09-27 01:57:36 [3146] [0] INFO: Started access logfile `/tmp/access.log'. 2010-09-27 01:57:36 [3146] [0] INFO: HTTP: Opening server at port 13000. 2010-09-27 01:57:36 [3146] [0] INFO: Mutex gwlib/list.c:135: 1 locks, 0 collisions. 2010-09-27 01:57:36 [3146] [0] INFO: BOXC: 'smsbox-max-pending' not set, using default (100). 2010-09-27 01:57:36 [3146] [0] INFO: Set SMS resend frequency to 60 seconds. 2010-09-27 01:57:36 [3146] [0] INFO: SMS resend retry set to unlimited. 2010-09-27 01:57:36 [3146] [0] INFO: DLR rerouting for smsc id (null) disabled. 2010-09-27 01:57:36 [3146] [0] INFO: AT2[/dev/ttyUSB0]: configuration doesn't show modemtype. will autodetect 2010-09-27 01:57:36 [3146] [6] INFO: AT2[/dev/ttyUSB0]: opening device 2010-09-27 01:57:36 [3146] [0] INFO: 2010-09-27 01:57:36 [3146] [0] INFO: Kannel bearerbox II version svn-r4838 starting 2010-09-27 01:57:36 [3146] [0] INFO: MAIN: Start-up done, entering mainloop 2010-09-27 01:57:37 [3146] [6] INFO: AT2[/dev/ttyUSB0]: speed set to 115200 2010-09-27 01:57:39 [3146] [6] INFO: AT2[/dev/ttyUSB0]: Closing device 2010-09-27 01:57:39 [3146] [6] INFO: AT2[/dev/ttyUSB0]: detect speed is 115200 2010-09-27 01:57:39 [3146] [6] INFO: AT2[/dev/ttyUSB0]: opening device 2010-09-27 01:57:40 [3146] [6] INFO: AT2[/dev/ttyUSB0]: speed set to 115200 2010-09-27 01:57:43 [3146] [6] INFO: Mutex gwlib/list.c:135: 196 locks, 0 collisions. 2010-09-27 01:57:43 [3146] [6] INFO: Mutex gwlib/list.c:135: 27 locks, 0 collisions. 2010-09-27 01:57:43 [3146] [6] INFO: Mutex gwlib/list.c:135: 13 locks, 0 collisions. 2010-09-27 01:57:43 [3146] [6] INFO: Mutex gwlib/list.c:135: 15 locks, 0 collisions. 2010-09-27 01:57:43 [3146] [6] INFO: Mutex gwlib/list.c:135: 9 locks, 0 collisions. 2010-09-27 01:57:43 [3146] [6] INFO: Mutex gwlib/list.c:135: 11 locks, 0 collisions. 2010-09-27 01:57:43 [3146] [6] INFO: Mutex gwlib/list.c:135: 7 locks, 0 collisions. 2010-09-27 01:57:43 [3146] [6] INFO: Mutex gwlib/list.c:135: 7 locks, 0 collisions.
Re: Delayed reply - wait for bearerbox
Hi, Just for clarifying the above problem. In the configuration pasted at first mail I noticed; group = smsbox bearerbox-host = localhost bearerbox-port = 13000 sendsms-port = 13131 global-sender = 42443162 log-file = /var/log/kannel/smsbox.log access-log = /var/log/kannel/access.log immediate-sendsms-reply = false Could the definition of that port be the problem of smsbox connection? On Tue, Sep 28, 2010 at 11:38 AM, Peter Mohr p...@mobilityarchitects.comwrote: Running with this test config works perfect. I've modified it just a little bit and it still works. Thanks for all your help! \Peter _ Peter Mohr Partner Mobile: +45 3162 1290 Mobility Architects www.mobilityarchitects.com Mobility Architects hjælper nogle af Danmarks største organisationer og virksomheder med at udnytte potentialet i mobil teknologi. Vi har en kreativ, visionær og forretningsfokuseret tilgang til at løse vores kunders problemer. Resultatet er driftsikre, skalerbare og brugervenlige løsninger. Vi har Danmarks førende Afaria-kompetencer og tilbyder desuden: Mobil strategi og forretningsrådgivning, design af mobil infrastruktur og sikkerhed, rådgivning om udvikling af mobile løsninger, implementering af device management løsninger samt support og uddannelse.
Re: Multle SMSC
Hi, Work with these two parameter in smsc group denied-smsc-id preferred-smsc-id On Fri, Sep 24, 2010 at 12:22 AM, Iskren Stoyanov isk...@bulware.bg wrote: Hello, I'm using Kannel 1.4.3 for MT. My Kannel is connected to two SMPP servers. From what I have understood from the documentation bearbox chooses random a SMSC and thats what always happens. I tried to to set SMSC in the request URL - didn't worked. SMSC is chosen randomly. Tried to add different users with forced-smsc and again SMSC is chosen randomly. When send through user with forced-smsc and set smsc in the url I get in the log file: INFO: send-sms request smsc id ignored, as smsc id forced to testsmsc But testsmsc is not used to send the message. How can I force the SMSC to be used? Here is my config: group = core admin-port = 13000 admin-password = admin-deny-ip = *.*.*.* admin-allow-ip = 127.0.0.1 smsbox-port = 13001 log-file = /var/log/kannel/bearerbox.log log-level = 3 box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 dlr-storage = mysql #--- mysql connection group = mysql-connection id = mydlr host = localhost username = kannel password = PASS database = kannel max-connections = 1 # DLR table structure group = dlr-db id = mydlr table = dlr field-smsc = smsc field-timestamp = timestamp field-destination = destination field-source = source field-service = service field-url = url field-mask = mask field-status = status field-boxc-id = boxc_id group = smsc smsc = smpp smsc-id = testsmsc host = 127.0.0.1 port = receive-port = smsc-username = bulsmst smsc-password = testC system-type = null service-type = sms interface-version = 34 group = smsc smsc = smpp smsc-id = routesms host = host.com port = receive-port = smsc-username = user smsc-password = PASS system-type = null max-pending-submits = 20 enquire-link-interval = 60 denied-prefix = 35989 group = smsbox bearerbox-host = 127.0.0.1 sendsms-port = 7048 global-sender = bulsms #log-level = 3 log-file = /var/log/kannel/smsbox.log group = sendsms-user username = bulware password = PASS forced-smsc = testsmsc max-messages = 3 concatenation = true group = sendsms-user username = routesms password = PASS forced-smsc = routesms max-messages = 3 concatenation = true -- Regards, Iskren Stoyanov Bulware Technologies Ltd.
Re: Broadcast SMS with Kannel.... help please.
As far as I understand, Aldo wants to implement Bulk SMS application using Kannel, It has not to do with Cell Broadcast. So SS7 and other Core Network related protocols are irelevant. The script can be created in your application side, retrieving subscriber list from DB, then calling HTTP interface that Kannel provides. About TPS limitation, you can control it in your script. Regards Elton On Tue, Sep 21, 2010 at 5:26 PM, Rene Kluwen rene.klu...@chimit.nl wrote: If you are a cellular carrier: Why don't you use SS7 to send broadcast messages? If they is an smpp proxy in between: Check your provider about a possible TLV that allows you to send broadcast messages. == Rene -Original Message- From: Aldo Zavala [mailto:a...@cleartalk.net] Sent: Tuesday, 21 September, 2010 16:35 To: Rene Kluwen; users@kannel.org Subject: RE: Broadcast SMS with Kannel help please. It is SMPP, I was thinking on pull a Subscribers list from our Provisioning Middleware, then create a script that submit like 25-30 SMS per second in order to not overkill the SMC. Thanks, Aldo Zavala 24/7 (760).890.4221 Mobile (760).556.5050 Office (760).234.0015 - Original Message - From: Rene Kluwen [mailto:rene.klu...@chimit.nl] To: 'Aldo Zavala' [mailto:a...@cleartalk.net], users@kannel.org Sent: Tue, 21 Sep 2010 04:23:08 -0700 Subject: RE: Broadcast SMS with Kannel help please. So what is your downstream smsc protocol? SMPP? AT2? SS7? -Original Message- From: Aldo Zavala [mailto:a...@cleartalk.net] Sent: Monday, 20 September, 2010 23:48 To: Rene Kluwen; users@kannel.org Subject: RE: Broadcast SMS with Kannel help please. We are a CDMA Cellular Carrier and sometimes need to send a broadcast SMS to our subscribers... Thanks, Aldo Zavala - Original Message - From: Rene Kluwen [mailto:rene.klu...@chimit.nl] To: 'Aldo Zavala' [mailto:a...@cleartalk.net], users@kannel.org Sent: Mon, 20 Sep 2010 14:45:26 -0700 Subject: RE: Broadcast SMS with Kannel help please. Not so sure what you mean... but.. if you mean cell broadcast messages, then it depends on your provider if they support it. It should be a network-provider. I don't think they allow aggregators to do cell broadcasts. == Rene -Original Message- From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Aldo Zavala Sent: Monday, 20 September, 2010 20:10 To: users@kannel.org Subject: Broadcast SMS with Kannel help please. Hi, Is there some script already done or a built in function that allows Kannel to send a broadcast SMS? I am not sure if my previous email was blocked so I am sending it again. Sorry if you received this twice... Aldo
Re: Broadcast SMS with Kannel.... help please.
yes you can, separating each entry (destination) with space (' ', '+' url-encoded). For more check the user guide. On Tue, Sep 21, 2010 at 6:38 PM, Aldo Zavala a...@cleartalk.net wrote: Thanks a lot for ths clarification I have started to get a little bit confused... =) Yes, I have access to DB and to Application side. I will design and implement a script that first gather the desired SMS Users group and then submits SMS's to that list using the Kannel HTTP Interface in chunks of 25-30 TPS... Thanks a lot for the explanations guys!! One last thing, is there a given kannel HTTP built in method to send to multiple numbers? Or should I invoke the method one by one? Thanks, Aldo Zavala - Original Message - From: Elton Hoxha [mailto:elt...@gmail.com] To: Rene Kluwen [mailto:rene.klu...@chimit.nl] Cc: Aldo Zavala [mailto:a...@cleartalk.net], users@kannel.org Sent: Tue, 21 Sep 2010 09:26:03 -0700 Subject: Re: Broadcast SMS with Kannel help please. As far as I understand, Aldo wants to implement Bulk SMS application using Kannel, It has not to do with Cell Broadcast. So SS7 and other Core Network related protocols are irelevant. The script can be created in your application side, retrieving subscriber list from DB, then calling HTTP interface that Kannel provides. About TPS limitation, you can control it in your script. Regards Elton On Tue, Sep 21, 2010 at 5:26 PM, Rene Kluwen rene.klu...@chimit.nl wrote: If you are a cellular carrier: Why don't you use SS7 to send broadcast messages? If they is an smpp proxy in between: Check your provider about a possible TLV that allows you to send broadcast messages. == Rene -Original Message- From: Aldo Zavala [mailto:a...@cleartalk.net] Sent: Tuesday, 21 September, 2010 16:35 To: Rene Kluwen; users@kannel.org Subject: RE: Broadcast SMS with Kannel help please. It is SMPP, I was thinking on pull a Subscribers list from our Provisioning Middleware, then create a script that submit like 25-30 SMS per second in order to not overkill the SMC. Thanks, Aldo Zavala 24/7 (760).890.4221 Mobile (760).556.5050 Office (760).234.0015 - Original Message - From: Rene Kluwen [mailto:rene.klu...@chimit.nl] To: 'Aldo Zavala' [mailto:a...@cleartalk.net], users@kannel.org Sent: Tue, 21 Sep 2010 04:23:08 -0700 Subject: RE: Broadcast SMS with Kannel help please. So what is your downstream smsc protocol? SMPP? AT2? SS7? -Original Message- From: Aldo Zavala [mailto:a...@cleartalk.net] Sent: Monday, 20 September, 2010 23:48 To: Rene Kluwen; users@kannel.org Subject: RE: Broadcast SMS with Kannel help please. We are a CDMA Cellular Carrier and sometimes need to send a broadcast SMS to our subscribers... Thanks, Aldo Zavala - Original Message - From: Rene Kluwen [mailto:rene.klu...@chimit.nl] To: 'Aldo Zavala' [mailto:a...@cleartalk.net], users@kannel.org Sent: Mon, 20 Sep 2010 14:45:26 -0700 Subject: RE: Broadcast SMS with Kannel help please. Not so sure what you mean... but.. if you mean cell broadcast messages, then it depends on your provider if they support it. It should be a network-provider. I don't think they allow aggregators to do cell broadcasts. == Rene -Original Message- From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Aldo Zavala Sent: Monday, 20 September, 2010 20:10 To: users@kannel.org Subject: Broadcast SMS with Kannel help please. Hi, Is there some script already done or a built in function that allows Kannel to send a broadcast SMS? I am not sure if my previous email was blocked so I am sending it again. Sorry if you received this twice... Aldo
Re: Kannel Mysql connectivity
If message is sent (delivered as well), you will not find that record in dlr table. That is the logic of that table. Being populated with undelivered SMS-s. After each delivery the row is deleted. Thi is the main goal of DLR table. On Thu, Sep 16, 2010 at 7:34 AM, Harbhag Singh Sohal harbhag.so...@gmail.com wrote: On Mon, Sep 13, 2010 at 5:09 PM, Harbhag Singh Sohal harbhag.so...@gmail.com wrote: On Mon, Sep 13, 2010 at 4:53 PM, Rene Kluwen rene.klu...@chimit.nl wrote: See userguide about directive access-log in group = core. I did as you said and now in access-log I can see the messages sent. But I dont anything getting stored in the MySQL database. I have configured the kannel to user external dlr and I have defined all the necessary fields in dlr table and when I start the bearerbox it shows that it is successfully connected to the MySQL database but nothing is getting stored in the database. The table dlr is empty. What wrong I am doing here.
Re: SMPP delivery port
Both techniques are possible. Either GSM UDH parameters, or the use of the dest_port optional TLV parameter. On Thu, Sep 16, 2010 at 3:36 PM, Juan Nin jua...@gmail.com wrote: That's not done with TLVs, to specify the destination port you need to use UDH. Try using udh=0605041234 where 1234 is the destination port On Thu, Sep 16, 2010 at 9:55 AM, Elton Hoxha elt...@gmail.com wrote: Hi, You need to configure TLV section in your conf file associated with the latest Kannel releases. AFAIK 1.4.3 stable version doesnt support meta-data. TLV Parameter Tag: 0x020B TLV Parameter Type: 2BYTE On Thu, Sep 16, 2010 at 2:21 PM, Anderson Schmidt alsn...@yahoo.com.br wrote: Hi all, I was searching information about how to deliver SMSs through Kannel, in a specific port on devices. More precisely, the SMPP destination port parameter. On devices, I'm going to have a java application using WMA, that listen to that specific port to wake up and process the SMS accordingly. I already have kannel working fine, for short and long simple text SMSs, but I couldn't find specific explanations about this delivery port param on the user guide. Any idea of how this can be implemented? Thanks in advance, Anderson
Re: Using Kannel to send Flash SMS
Are you talking about OTA settings? On Fri, Sep 10, 2010 at 5:05 PM, Mads N. Vestergaard – CoolSMS A/S m...@coolsms.com wrote: Hi Alex, In most cases the phone doesn't give you the option to save it, but some phones allows a user to save the message. Den 10/09/2010 kl. 16.53 skrev Alex: Hi Kannel team, I am sending flash sms' using the mclass parameter. However i want to send the sms such that when the user receives it it has a prompt for them to reply. In short I want them to reply the sms and not save it. currently the prompt is to save it or discard. Is this possible -- Best regards, Alex
Re: Using Kannel to send Flash SMS
Yes you can send an OTA message which user can be able to either save it or discard it. I suppose you have an OTA application and the binary form of the message. You have to pass the UDH to the kannel in send-sms url. Hope it helps. On Fri, Sep 10, 2010 at 5:12 PM, Alex nomu...@gmail.com wrote: Yes Elton Can I send an OTA with the message to prompt a reply? I do not want to save the msg, I want to prompt a reply such that the user presses a button on his phone and immediately types the reply the way USSD works. On 10 September 2010 18:10, Elton Hoxha elt...@gmail.com wrote: Are you talking about OTA settings? On Fri, Sep 10, 2010 at 5:05 PM, Mads N. Vestergaard – CoolSMS A/S m...@coolsms.com wrote: Hi Alex, In most cases the phone doesn't give you the option to save it, but some phones allows a user to save the message. Den 10/09/2010 kl. 16.53 skrev Alex: Hi Kannel team, I am sending flash sms' using the mclass parameter. However i want to send the sms such that when the user receives it it has a prompt for them to reply. In short I want them to reply the sms and not save it. currently the prompt is to save it or discard. Is this possible -- Best regards, Alex -- Best regards, Alex
Re: Deliver_sm
You will see deliver_sm PDU-s whenever you send back from your mobile toward application. On Mon, Aug 30, 2010 at 1:14 PM, dafodil neo.tu...@yahoo.com wrote: Hi List, i habe bit confusion in my case.I see submit_sm and submit_sm_resp in the log but not deliver_sm. Can it be a problem with my configuration or carrier has not enabled it.How ever my message is successfully delivered to the destination mobile.i m using HTTP post to send message and dlr type default(internal) Br daf -- View this message in context: http://old.nabble.com/Deliver_sm-tp29571489p29571489.html Sent from the Kannel - User mailing list archive at Nabble.com.
Re: Deliver_sm
Check and read about dlr-mask option. On Mon, Aug 30, 2010 at 1:14 PM, dafodil neo.tu...@yahoo.com wrote: Hi List, i habe bit confusion in my case.I see submit_sm and submit_sm_resp in the log but not deliver_sm. Can it be a problem with my configuration or carrier has not enabled it.How ever my message is successfully delivered to the destination mobile.i m using HTTP post to send message and dlr type default(internal) Br daf -- View this message in context: http://old.nabble.com/Deliver_sm-tp29571489p29571489.html Sent from the Kannel - User mailing list archive at Nabble.com.
Re: service works with SMPPsim and not with real smsc
Whose IP is 172.22.130.223? On Fri, Aug 27, 2010 at 10:40 AM, gasmen xma...@live.com wrote: how???but there is the smsc group defnined group=smsc smsc=smpp smsc-id=SMPPSim interface-version=34 host=172.22.130.223 port=4000 system-id= smsc-password= system-type=default #alt-charset = UTF-8 transceiver-mode=1 there is another group to define for the real smsc?? Rene Kluwen wrote: Also: There is no section in your config that defines your real smsc? == Rene -Original Message- From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Alvaro Cornejo Sent: Thursday, 26 August, 2010 16:03 To: gasmen Cc: users@kannel.org Subject: Re: service works with SMPPsim and not with real smsc set log-level to 0 and post logs |--- --| 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 Thu, Aug 26, 2010 at 4:22 AM, gasmen xma...@live.com wrote: this is my configuration it calls my servlet uploaded on web server when i use SMPPsim but when i use the real smsc it didnt call the service. group = core admin-port = 13000 smsbox-port = 13001 admin-password = bar log-file = /home/aymen/gateway-1.4.3/gw/config/logs/kannel.log log-level = 0 access-log = /home/aymen/gateway-1.4.3/gw/config/logs/access.log #box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 #--- # SMSC CONNECTIONS #-- #smsc connexion(SMPP protocol) #-- group=smsc smsc=smpp smsc-id=SMPPSim interface-version=34 host=172.22.130.223 port=4000 system-id= smsc-password= system-type=default #alt-charset = UTF-8 transceiver-mode=1 #--- #smsc connexion(SMPP protocol) # # SMSBOX SETUP #- # Smsbox(es) do higher-level SMS handling after they have been received from # SMS centers by bearerbox, or before they are given to bearerbox for delivery group = smsbox bearerbox-host = 127.0.0.1 sendsms-port = 13013 #sendsms-chars = 0123456789 +- log-file = /home/aymen/gateway-1.4.3/gw/config/logs/smsbox.log log-level = 1 access-log = /home/aymen/gateway-1.4.3/gw/config/logs/access.log group = sendsms-user username = tester password = foobar user-deny-ip = *.*.*.* user-allow-ip = 127.0.0.1 #get-url=http://localhost:13013/cgi-bin/sendsms?username=testerpassword=fo obarfrom=%pto=%Ptext=%r # # SERVICES #- #- #Store service and Multimedia download #- catch-all = true group = sms-service #the first word in the sms keyword = default get-url = http://aymen-laptop:8080/salem/servlet/kannel?text=%r; Rene Kluwen wrote: Could you post your current configuration files? == Rene From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of gasmen Sent: Wednesday, 25 August, 2010 14:39 To: users@kannel.org Subject: service works with SMPPsim and not with real smsc HI all i am using kannel 1.4.3 and i am excuting servlet with group sms-service it works good and it call the servlet when i use the SMMPsim but just i change the configuration of smsc group to work with real smsc message come to the mobile phone but it didnt call the servlet ... so i am looking for your help maybe i will add some configuration the groups to start the service with the real smsc!!! thanks a lot _ View this message in context: service http://old.nabble.com/service-works-with-SMPPsim-and-not-with-real-smsc-tp2 9531805p29531805.html works with SMPPsim and not with real smsc Sent from the Kannel http://old.nabble.com/Kannel---User-f14436.html - User mailing list archive at Nabble.com. -- View this message in context: http://old.nabble.com/my-service-works-with-SMPPsim-but-not-with-real-smsc-t p29531805p29540423.html Sent from the Kannel - User mailing list archive at Nabble.com. -- View this message in context: http://old.nabble.com/my-service-works-with-SMPPsim-but-not-with-real-smsc-tp29531805p29550588.html Sent from the Kannel - User mailing list archive at Nabble.com.
Re: configuration help required
Maybe you need to define two sms-service groups to call each of your services in background. To match your given digits; 1 - keyword-regex = ^[0-9]+$ 2 - keyword-regex = ^[0-9]+ [1-4]+ [0-1]+$ On Thu, Aug 26, 2010 at 9:22 AM, sangprabv sangpr...@gmail.com wrote: It should be about sms-service sangprabv sangpr...@gmail.com http://www.petitiononline.com/froyo/ On Aug 26, 2010, at 2:10 PM, Irfan Malik wrote: Hi All, I am looking for help to configure kannel sms-service based on number of words in request. Requirement is to append different URL's to the request based on number of words in keyword. it should work for any keyword Request 1) 92123456789 Request 2) 92123456789 1234 10 For number 1, want to append a URL e.g. http://www.myweb.com/blank For number 2, want to append a URL e.g. http://www.myweb1.com/pinrequest From definition of keyword, I could see it is possible but don't know how to configure it, keyword (m) word Services are identified by the first word in the SMS. Each `%s' in the URL corresponds to one word in the SMS message. Words are separated with spaces. A keyword is matched only if the number of words in the SMS message is the same as the number of `%s' fields in the URL. This allows you to configure the gateway to use different URLs for the same keyword depending on the number of words the SMS message contains. The keyword matches in non-case sensitive manner, which means you don't have to use aliases to handle different cased versions of your keyword. Any help would be very much appreciated. Best Regards, Irfan Malik
Re: Re : Stop sms coming with what is displaying in web explorer
Try max-messages = 0 at sms-service group On Thu, Jul 15, 2010 at 10:34 AM, Marc ANDREAS rowai2...@yahoo.fr wrote: I don't want to receive this by sms. De : seikath seik...@gmail.com À : users@kannel.org Envoyé le : Jeu 15 juillet 2010, 9h 28min 04s Objet : Re: Stop sms coming with what is displaying in web explorer easy close the damn web explorer. On 07/15/2010 11:11 AM, Marc ANDREAS wrote: Hi group, Can you help me to stop sms from Kannel ? In fact when I send an http request to Kannel I don't want to receive what is displayed in the web explorer. Regards, Marc
Re: Network Initiated USSR
Hi, The send-sms URL looks OK, when meta data variable is set to 2 you should receive the USSR request in your mobile. Try to change the length = 2 in your conf to length = 1. Hope it helps On Mon, Feb 15, 2010 at 8:55 AM, GSM Revolution gsm@gmail.com wrote: Hi, I want to start an USSR with session initiated from network end(not from handset). I am sending Network Initiated USSR to smpp server with ussd_service_op and its_session_info but getting as an USSN in my handset. parameters set for metadata are - *ussd_service_op=2 (for USSR) and its_session_info=* Here is the URL post - http://localhost:8080/cgi-bin/sendsms?user=ABCpassword=XYZfrom=Testto=123456789012text=WelCome%20To%20World%0A1%2ETime%0A2%2EDate%0Ametadata=%3Fsmpp%3Fservice%5Fop%3D2%26session%5Finfo%3D Do i need any other parameter configuration in kannel config file ?? Fragment of my config file is - *group = smpp-tlv name = service_op tag = 0x0501 type = integer length = 2 group = smpp-tlv name = session_info tag = 0x1383 type = octetstring length = 4 *
Re: Network Initiated USSR
Hi, I`m just wondering why you are using session info TLV. The session can be handled easily in application side, no need to use kannel for it. At least this is the way I`m developing the ussd menu. It is just an assumption, maybe doesnt affect at all, but try not to include the session info inside meta-data, leave it purely for service_op. Regards On Mon, Feb 15, 2010 at 10:19 AM, ricky123 gsm@gmail.com wrote: Hi, Thank you for your reply. I changed length to '1' and found no difference. still i am getting as an USSN messgae not an USSR. elthox wrote: Hi, The send-sms URL looks OK, when meta data variable is set to 2 you should receive the USSR request in your mobile. Try to change the length = 2 in your conf to length = 1. Hope it helps On Mon, Feb 15, 2010 at 8:55 AM, GSM Revolution gsm@gmail.com wrote: Hi, I want to start an USSR with session initiated from network end(not from handset). I am sending Network Initiated USSR to smpp server with ussd_service_op and its_session_info but getting as an USSN in my handset. parameters set for metadata are - *ussd_service_op=2 (for USSR) and its_session_info=* Here is the URL post - http://localhost:8080/cgi-bin/sendsms?user=ABCpassword=XYZfrom=Testto=123456789012text=WelCome%20To%20World%0A1%2ETime%0A2%2EDate%0Ametadata=%3Fsmpp%3Fservice%5Fop%3D2%26session%5Finfo%3D Do i need any other parameter configuration in kannel config file ?? Fragment of my config file is - *group = smpp-tlv name = service_op tag = 0x0501 type = integer length = 2 group = smpp-tlv name = session_info tag = 0x1383 type = octetstring length = 4 * -- View this message in context: http://old.nabble.com/Network-Initiated-USSR-tp27590456p27591144.html Sent from the Kannel - User mailing list archive at Nabble.com.
Re: Network Initiated USSR
There must be also other parameters like (but I dont think are relevant in your case): - At Kannel Side, in smpp group service-type = USSD - At USSD Center side, your client`s service type (among CMT, VMN, VMA etc) should be configured as USSD. I guess you have arranged also the pdu type to be deliver or submit_sm, because data_sm is not available. By the way which vendor is providing your USSDC? On Mon, Feb 15, 2010 at 12:35 PM, ricky123 gsm@gmail.com wrote: Hi, I removed session info from metadata for Network Initiated USSR but getting same an USSN. do you think any configuration required at smpp server side? elthox wrote: Hi, I`m just wondering why you are using session info TLV. The session can be handled easily in application side, no need to use kannel for it. At least this is the way I`m developing the ussd menu. It is just an assumption, maybe doesnt affect at all, but try not to include the session info inside meta-data, leave it purely for service_op. Regards On Mon, Feb 15, 2010 at 10:19 AM, ricky123 gsm@gmail.com wrote: Hi, Thank you for your reply. I changed length to '1' and found no difference. still i am getting as an USSN messgae not an USSR. elthox wrote: Hi, The send-sms URL looks OK, when meta data variable is set to 2 you should receive the USSR request in your mobile. Try to change the length = 2 in your conf to length = 1. Hope it helps On Mon, Feb 15, 2010 at 8:55 AM, GSM Revolution gsm@gmail.com wrote: Hi, I want to start an USSR with session initiated from network end(not from handset). I am sending Network Initiated USSR to smpp server with ussd_service_op and its_session_info but getting as an USSN in my handset. parameters set for metadata are - *ussd_service_op=2 (for USSR) and its_session_info=* Here is the URL post - http://localhost:8080/cgi-bin/sendsms?user=ABCpassword=XYZfrom=Testto=123456789012text=WelCome%20To%20World%0A1%2ETime%0A2%2EDate%0Ametadata=%3Fsmpp%3Fservice%5Fop%3D2%26session%5Finfo%3D Do i need any other parameter configuration in kannel config file ?? Fragment of my config file is - *group = smpp-tlv name = service_op tag = 0x0501 type = integer length = 2 group = smpp-tlv name = session_info tag = 0x1383 type = octetstring length = 4 * -- View this message in context: http://old.nabble.com/Network-Initiated-USSR-tp27590456p27591144.html Sent from the Kannel - User mailing list archive at Nabble.com. -- View this message in context: http://old.nabble.com/Network-Initiated-USSR-tp27590456p27592263.html Sent from the Kannel - User mailing list archive at Nabble.com.
Re: Network Initiated USSR
YEs I mentioned From parameter, put some 3 digit number. On Mon, Feb 15, 2010 at 1:07 PM, GSM Revolution gsm@gmail.com wrote: Hi, I have changed the destination parameter *to* in url. nothing else was changed. Do i require to change sender address?? On 2/15/10, Elton Hoxha elt...@gmail.com wrote: I had a look again on your URL http://localhost:8080/cgi-bin/sendsms?user=ABCpassword=XYZfrom=Testto=123456789012text=WelCome%20To%20World%0A1%2ETime%0A2%2EDate%0Ametadata=%3Fsmpp%3Fservice%5Fop%3D2%26session%5Finfo%3D From parameter is modified by you as aphanumeric or is it really like that? In my case Kannel would receive back an error if I would use aphanumeric, I dont think your USSD is suporting it either. On Mon, Feb 15, 2010 at 12:45 PM, Elton Hoxha elt...@gmail.com wrote: There must be also other parameters like (but I dont think are relevant in your case): - At Kannel Side, in smpp group service-type = USSD - At USSD Center side, your client`s service type (among CMT, VMN, VMA etc) should be configured as USSD. I guess you have arranged also the pdu type to be deliver or submit_sm, because data_sm is not available. By the way which vendor is providing your USSDC? On Mon, Feb 15, 2010 at 12:35 PM, ricky123 gsm@gmail.com wrote: Hi, I removed session info from metadata for Network Initiated USSR but getting same an USSN. do you think any configuration required at smpp server side? elthox wrote: Hi, I`m just wondering why you are using session info TLV. The session can be handled easily in application side, no need to use kannel for it. At least this is the way I`m developing the ussd menu. It is just an assumption, maybe doesnt affect at all, but try not to include the session info inside meta-data, leave it purely for service_op. Regards On Mon, Feb 15, 2010 at 10:19 AM, ricky123 gsm@gmail.com wrote: Hi, Thank you for your reply. I changed length to '1' and found no difference. still i am getting as an USSN messgae not an USSR. elthox wrote: Hi, The send-sms URL looks OK, when meta data variable is set to 2 you should receive the USSR request in your mobile. Try to change the length = 2 in your conf to length = 1. Hope it helps On Mon, Feb 15, 2010 at 8:55 AM, GSM Revolution gsm@gmail.com wrote: Hi, I want to start an USSR with session initiated from network end(not from handset). I am sending Network Initiated USSR to smpp server with ussd_service_op and its_session_info but getting as an USSN in my handset. parameters set for metadata are - *ussd_service_op=2 (for USSR) and its_session_info=* Here is the URL post - http://localhost:8080/cgi-bin/sendsms?user=ABCpassword=XYZfrom=Testto=123456789012text=WelCome%20To%20World%0A1%2ETime%0A2%2EDate%0Ametadata=%3Fsmpp%3Fservice%5Fop%3D2%26session%5Finfo%3D Do i need any other parameter configuration in kannel config file ?? Fragment of my config file is - *group = smpp-tlv name = service_op tag = 0x0501 type = integer length = 2 group = smpp-tlv name = session_info tag = 0x1383 type = octetstring length = 4 * -- View this message in context: http://old.nabble.com/Network-Initiated-USSR-tp27590456p27591144.html Sent from the Kannel - User mailing list archive at Nabble.com. -- View this message in context: http://old.nabble.com/Network-Initiated-USSR-tp27590456p27592263.html Sent from the Kannel - User mailing list archive at Nabble.com.
Re: Network Initiated USSR
I had a look again on your URL http://localhost:8080/cgi-bin/sendsms?user=ABCpassword=XYZfrom=Testto=123456789012text=WelCome%20To%20World%0A1%2ETime%0A2%2EDate%0Ametadata=%3Fsmpp%3Fservice%5Fop%3D2%26session%5Finfo%3D From parameter is modified by you as aphanumeric or is it really like that? In my case Kannel would receive back an error if I would use aphanumeric, I dont think your USSD is suporting it either. On Mon, Feb 15, 2010 at 12:45 PM, Elton Hoxha elt...@gmail.com wrote: There must be also other parameters like (but I dont think are relevant in your case): - At Kannel Side, in smpp group service-type = USSD - At USSD Center side, your client`s service type (among CMT, VMN, VMA etc) should be configured as USSD. I guess you have arranged also the pdu type to be deliver or submit_sm, because data_sm is not available. By the way which vendor is providing your USSDC? On Mon, Feb 15, 2010 at 12:35 PM, ricky123 gsm@gmail.com wrote: Hi, I removed session info from metadata for Network Initiated USSR but getting same an USSN. do you think any configuration required at smpp server side? elthox wrote: Hi, I`m just wondering why you are using session info TLV. The session can be handled easily in application side, no need to use kannel for it. At least this is the way I`m developing the ussd menu. It is just an assumption, maybe doesnt affect at all, but try not to include the session info inside meta-data, leave it purely for service_op. Regards On Mon, Feb 15, 2010 at 10:19 AM, ricky123 gsm@gmail.com wrote: Hi, Thank you for your reply. I changed length to '1' and found no difference. still i am getting as an USSN messgae not an USSR. elthox wrote: Hi, The send-sms URL looks OK, when meta data variable is set to 2 you should receive the USSR request in your mobile. Try to change the length = 2 in your conf to length = 1. Hope it helps On Mon, Feb 15, 2010 at 8:55 AM, GSM Revolution gsm@gmail.com wrote: Hi, I want to start an USSR with session initiated from network end(not from handset). I am sending Network Initiated USSR to smpp server with ussd_service_op and its_session_info but getting as an USSN in my handset. parameters set for metadata are - *ussd_service_op=2 (for USSR) and its_session_info=* Here is the URL post - http://localhost:8080/cgi-bin/sendsms?user=ABCpassword=XYZfrom=Testto=123456789012text=WelCome%20To%20World%0A1%2ETime%0A2%2EDate%0Ametadata=%3Fsmpp%3Fservice%5Fop%3D2%26session%5Finfo%3D Do i need any other parameter configuration in kannel config file ?? Fragment of my config file is - *group = smpp-tlv name = service_op tag = 0x0501 type = integer length = 2 group = smpp-tlv name = session_info tag = 0x1383 type = octetstring length = 4 * -- View this message in context: http://old.nabble.com/Network-Initiated-USSR-tp27590456p27591144.html Sent from the Kannel - User mailing list archive at Nabble.com. -- View this message in context: http://old.nabble.com/Network-Initiated-USSR-tp27590456p27592263.html Sent from the Kannel - User mailing list archive at Nabble.com.
Re: Network Initiated USSR
Strange, if you can post some logs showing submit pdu-s and responses. If you can take any smpp dump, it would be better . On Mon, Feb 15, 2010 at 2:05 PM, GSM Revolution gsm@gmail.com wrote: still i am getting as USSN after every modification!! On 2/15/10, Elton Hoxha elt...@gmail.com wrote: It is enough to put some digits there instead of alphanumeric, ther is no need for definition at USSDC. On Mon, Feb 15, 2010 at 1:13 PM, GSM Revolution gsm@gmail.comwrote: Is this number provided by the USSD centre or i can put any 3 digit number?? On 2/15/10, Elton Hoxha elt...@gmail.com wrote: YEs I mentioned From parameter, put some 3 digit number. On Mon, Feb 15, 2010 at 1:07 PM, GSM Revolution gsm@gmail.comwrote: Hi, I have changed the destination parameter *to* in url. nothing else was changed. Do i require to change sender address?? On 2/15/10, Elton Hoxha elt...@gmail.com wrote: I had a look again on your URL http://localhost:8080/cgi-bin/sendsms?user=ABCpassword=XYZfrom=Testto=123456789012text=WelCome%20To%20World%0A1%2ETime%0A2%2EDate%0Ametadata=%3Fsmpp%3Fservice%5Fop%3D2%26session%5Finfo%3D From parameter is modified by you as aphanumeric or is it really like that? In my case Kannel would receive back an error if I would use aphanumeric, I dont think your USSD is suporting it either. On Mon, Feb 15, 2010 at 12:45 PM, Elton Hoxha elt...@gmail.comwrote: There must be also other parameters like (but I dont think are relevant in your case): - At Kannel Side, in smpp group service-type = USSD - At USSD Center side, your client`s service type (among CMT, VMN, VMA etc) should be configured as USSD. I guess you have arranged also the pdu type to be deliver or submit_sm, because data_sm is not available. By the way which vendor is providing your USSDC? On Mon, Feb 15, 2010 at 12:35 PM, ricky123 gsm@gmail.comwrote: Hi, I removed session info from metadata for Network Initiated USSR but getting same an USSN. do you think any configuration required at smpp server side? elthox wrote: Hi, I`m just wondering why you are using session info TLV. The session can be handled easily in application side, no need to use kannel for it. At least this is the way I`m developing the ussd menu. It is just an assumption, maybe doesnt affect at all, but try not to include the session info inside meta-data, leave it purely for service_op. Regards On Mon, Feb 15, 2010 at 10:19 AM, ricky123 gsm@gmail.com wrote: Hi, Thank you for your reply. I changed length to '1' and found no difference. still i am getting as an USSN messgae not an USSR. elthox wrote: Hi, The send-sms URL looks OK, when meta data variable is set to 2 you should receive the USSR request in your mobile. Try to change the length = 2 in your conf to length = 1. Hope it helps On Mon, Feb 15, 2010 at 8:55 AM, GSM Revolution gsm@gmail.com wrote: Hi, I want to start an USSR with session initiated from network end(not from handset). I am sending Network Initiated USSR to smpp server with ussd_service_op and its_session_info but getting as an USSN in my handset. parameters set for metadata are - *ussd_service_op=2 (for USSR) and its_session_info=* Here is the URL post - http://localhost:8080/cgi-bin/sendsms?user=ABCpassword=XYZfrom=Testto=123456789012text=WelCome%20To%20World%0A1%2ETime%0A2%2EDate%0Ametadata=%3Fsmpp%3Fservice%5Fop%3D2%26session%5Finfo%3D Do i need any other parameter configuration in kannel config file ?? Fragment of my config file is - *group = smpp-tlv name = service_op tag = 0x0501 type = integer length = 2 group = smpp-tlv name = session_info tag = 0x1383 type = octetstring length = 4 * -- View this message in context: http://old.nabble.com/Network-Initiated-USSR-tp27590456p27591144.html Sent from the Kannel - User mailing list archive at Nabble.com. -- View this message in context: http://old.nabble.com/Network-Initiated-USSR-tp27590456p27592263.html Sent from the Kannel - User mailing list archive at Nabble.com.
Re: How to send TLV for USSD Push
Hi, I have succeded sending all USSD commands in a simpler way, I mean configuration and parameters point of view. In conf file: group = smpp-tlv name = mydata tag = 0x0501 type = integer length = 1 smsc-id = ussdmenu and send-sms url looks like: http://10.1.5.30:x/cgi-bin/sendsms?username=kotpassword=kotfrom=187to=xxtext=hellometa-data=%3Fsmpp%3Fmydata%3D3 Hope it helps On Wed, Feb 3, 2010 at 1:33 PM, GSM Revolution gsm@gmail.com wrote: Hi, I want to push USSN through kannel but unable to send. Configuration for TLV for USSD is - *group = smpp-tlv name = service_type tag = 0x0501 type = octetstring length = 2 smsc-id = Unicel1 group = smpp-tlv name = message_payload tag = 0x0424 type = octetstring length = 20 smsc-id = Unicel1 group = smpp-tlv name = dest_bearer_type tag = 0x0007 type = integer length = 2 smsc-id = Unicel1* I am passing request through http request - before encoding of metadata is -*?smpp?service_type=3dest_bearer_type=4message_payload=0203040506 * After url encode * http://localhost:8080/cgi-bin/sendsms?user=XYZpassword=ABCfrom=testto=011234554321metadata=%3Fsmpp%3Fservice%5Ftype%3D3%26dest%5Fbearer%5Ftype%3D4%26message%5Fpayload%3D0203040506 * In bearerbox I do not see any TLV parameters. Do i require any patch for this?? Please help me out of this issue Thanks in advance Regards Ricky
Re: Error Code in DLR Status
With Dlr-mask Request for delivery reports with the state of the sent message. The value is a bit mask composed of: 1: Delivered to phone, 2: Non-Delivered to Phone, 4: Queued on SMSC, 8: Delivered to SMSC, 16: Non-Delivered to SMSC. Must set dlr-url on sendsms-user group or use the dlr-url CGI variable. You can check it in the user guide On Mon, Dec 21, 2009 at 10:15 AM, Jinson jin...@mobme.in wrote: Hello Users, How do I get the error code value in my dlr url when I get dlr status as rejected? 2009-12-21 07:05:15 [17394] [10] ERROR: SMPP[SMPP11]: SMSC returned error code *0x0045* (Submit failed) in response to submit_sm. My DLR URL parameters will look like this type=%dkannel_id=%Fmsisdn=%pdlrvalue=%Amessage_id=my internal message id Thanks Jinson Abraham
Re: how to implement multiple short codes
Assuming that you have smpp connection, you can create separate conf files for each shortcode (if you have 2 smpp accounts from the operator). You can start two bearerboxes with the respective conf file having their own smsc group. Or you can include both smsc groups in one conf file, starting just one instance of berarerbox, and having separated send-sms and sms-service in the configuration distinguished by accepted-smsc and forced-smsc for routing purpose. You can check the guide for these parameters. On Mon, Dec 21, 2009 at 11:45 AM, Innocent Muchedzi innoc...@syldah.co.bwwrote: Hie I have 2 short codes and a single kannel box server, and i want to implement the two short codes, how should i do it thank you -- This message has been scanned for viruses and dangerous content by the BBI SMTP filter, and is believed to be clean.
Re: Error Code in DLR Status
if you get type=16 why *0x0045* is important for you? What would be its purpose? On Mon, Dec 21, 2009 at 11:11 AM, Jinson jin...@mobme.in wrote: I have set the dlr-mask=31 and im getting type =16 for the above mentioned message. But is there any way to get the error code on my dlr url ERROR: SMPP[SMPP11]: SMSC returned error code *0x0045* (Submit failed) in response to submit_sm. Thanks MobME storms into Emerging 50 Companies in India by Nasscom On Mon, Dec 21, 2009 at 3:17 PM, Elton Hoxha elt...@gmail.com wrote: With Dlr-mask Request for delivery reports with the state of the sent message. The value is a bit mask composed of: 1: Delivered to phone, 2: Non-Delivered to Phone, 4: Queued on SMSC, 8: Delivered to SMSC, 16: Non-Delivered to SMSC. Must set dlr-url on sendsms-user group or use the dlr-url CGI variable. You can check it in the user guide On Mon, Dec 21, 2009 at 10:15 AM, Jinson jin...@mobme.in wrote: Hello Users, How do I get the error code value in my dlr url when I get dlr status as rejected? 2009-12-21 07:05:15 [17394] [10] ERROR: SMPP[SMPP11]: SMSC returned error code *0x0045* (Submit failed) in response to submit_sm. My DLR URL parameters will look like this type=%dkannel_id=%Fmsisdn=%pdlrvalue=%Amessage_id=my internal message id Thanks Jinson Abraham
multiple submit_sm
Hi guys, I`m facing some problem when I submit using TLV parameter for ussd operation. I`m using cvs-20091124 I`m sending an MO request and then sms is submitted using sendsms interface with meta-data parameter included. After the first successful submit, another submit is generated automatically. Anyone can help? Thanks 2009-12-03 17:08:31 [13584] [6] DEBUG: SMPP PDU 0x8718f20 dump: 2009-12-03 17:08:31 [13584] [6] DEBUG: type_name: enquire_link 2009-12-03 17:08:31 [13584] [6] DEBUG: command_id: 21 = 0x0015 2009-12-03 17:08:31 [13584] [6] DEBUG: command_status: 0 = 0x 2009-12-03 17:08:31 [13584] [6] DEBUG: sequence_number: 2 = 0x0002 2009-12-03 17:08:31 [13584] [6] DEBUG: SMPP PDU dump ends. 2009-12-03 17:08:31 [13584] [6] DEBUG: SMPP[test]: throughput (0.00,0.00) 2009-12-03 17:08:31 [13584] [6] DEBUG: SMPP[test]: throughput (0.00,0.00) 2009-12-03 17:08:31 [13584] [6] DEBUG: SMPP[test]: Got PDU: 2009-12-03 17:08:31 [13584] [6] DEBUG: SMPP PDU 0x8718f38 dump: 2009-12-03 17:08:31 [13584] [6] DEBUG: type_name: enquire_link_resp 2009-12-03 17:08:31 [13584] [6] DEBUG: command_id: 2147483669 = 0x8015 2009-12-03 17:08:31 [13584] [6] DEBUG: command_status: 0 = 0x 2009-12-03 17:08:31 [13584] [6] DEBUG: sequence_number: 2 = 0x0002 2009-12-03 17:08:31 [13584] [6] DEBUG: SMPP PDU dump ends. 2009-12-03 17:08:31 [13584] [6] DEBUG: SMPP[test]: throughput (0.00,0.00) 2009-12-03 17:08:41 [13584] [6] DEBUG: SMPP[test]: throughput (0.00,0.00) 2009-12-03 17:08:41 [13584] [6] DEBUG: Optional parameter tag (0x0501) 2009-12-03 17:08:41 [13584] [6] DEBUG: Optional parameter length read as 1 2009-12-03 17:08:41 [13584] [6] DEBUG: Found configured optional parameter `mydata' 2009-12-03 17:08:41 [13584] [6] DEBUG: SMPP[test]: Got PDU: 2009-12-03 17:08:41 [13584] [6] DEBUG: SMPP PDU 0x8718f78 dump: 2009-12-03 17:08:41 [13584] [6] DEBUG: type_name: deliver_sm 2009-12-03 17:08:41 [13584] [6] DEBUG: command_id: 5 = 0x0005 2009-12-03 17:08:41 [13584] [6] DEBUG: command_status: 0 = 0x 2009-12-03 17:08:41 [13584] [6] DEBUG: sequence_number: 10 = 0x000a 2009-12-03 17:08:41 [13584] [6] DEBUG: service_type: USSD 2009-12-03 17:08:41 [13584] [6] DEBUG: source_addr_ton: 1 = 0x0001 2009-12-03 17:08:41 [13584] [6] DEBUG: source_addr_npi: 1 = 0x0001 2009-12-03 17:08:41 [13584] [6] DEBUG: source_addr: 355672118168 2009-12-03 17:08:41 [13584] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2009-12-03 17:08:41 [13584] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2009-12-03 17:08:41 [13584] [6] DEBUG: destination_addr: 200 2009-12-03 17:08:41 [13584] [6] DEBUG: esm_class: 0 = 0x 2009-12-03 17:08:41 [13584] [6] DEBUG: protocol_id: 0 = 0x 2009-12-03 17:08:41 [13584] [6] DEBUG: priority_flag: 0 = 0x 2009-12-03 17:08:41 [13584] [6] DEBUG: schedule_delivery_time: NULL 2009-12-03 17:08:41 [13584] [6] DEBUG: validity_period: NULL 2009-12-03 17:08:41 [13584] [6] DEBUG: registered_delivery: 0 = 0x 2009-12-03 17:08:41 [13584] [6] DEBUG: replace_if_present_flag: 0 = 0x 2009-12-03 17:08:41 [13584] [6] DEBUG: data_coding: 0 = 0x 2009-12-03 17:08:41 [13584] [6] DEBUG: sm_default_msg_id: 0 = 0x 2009-12-03 17:08:41 [13584] [6] DEBUG: sm_length: 5 = 0x0005 2009-12-03 17:08:41 [13584] [6] DEBUG: short_message: *200# 2009-12-03 17:08:41 [13584] [6] DEBUG: mydata: 1 2009-12-03 17:08:41 [13584] [6] DEBUG: SMPP PDU dump ends. 2009-12-03 17:08:41 [13584] [6] WARNING: SMPP[test]: Mallformed addr `200', generally expected at least 7 digits. 2009-12-03 17:08:41 [13584] [6] DEBUG: SMPP[test]: Sending PDU: 2009-12-03 17:08:41 [13584] [6] DEBUG: SMPP PDU 0x871a0c0 dump: 2009-12-03 17:08:41 [13584] [6] DEBUG: type_name: deliver_sm_resp 2009-12-03 17:08:41 [13584] [6] DEBUG: command_id: 2147483653 = 0x8005 2009-12-03 17:08:41 [13584] [6] DEBUG: command_status: 0 = 0x 2009-12-03 17:08:41 [13584] [6] DEBUG: sequence_number: 10 = 0x000a 2009-12-03 17:08:41 [13584] [6] DEBUG: message_id: NULL 2009-12-03 17:08:41 [13584] [6] DEBUG: SMPP PDU dump ends. 2009-12-03 17:08:41 [13584] [6] DEBUG: SMPP[test]: throughput (0.00,0.00) 2009-12-03 17:08:41 [13584] [10] DEBUG: send_msg: sending msg to box: 10.1.21.187 2009-12-03 17:08:41 [13584] [10] DEBUG: boxc_sender: sent message to 10.1.21.187 2009-12-03 17:08:41 [13584] [9] DEBUG: boxc_receiver: got ack 2009-12-03 17:08:41 [13584] [9] DEBUG: boxc_receiver: sms received 2009-12-03 17:08:41 [13584] [9] DEBUG: send_msg: sending msg to box: 10.1.21.187 2009-12-03 17:08:41 [13584] [6] DEBUG: SMPP[test]: throughput (0.00,0.00) 2009-12-03 17:08:41 [13584] [6] DEBUG: new group created `smpp' 2009-12-03 17:08:41 [13584] [6] DEBUG: group=`smpp' key=`mydata' value=`2' 2009-12-03 17:08:41 [13584] [6] DEBUG: SMPP[test]: Sending PDU: 2009-12-03 17:08:41 [13584] [6] DEBUG: SMPP PDU 0x8716898 dump: 2009-12-03 17:08:41 [13584] [6] DEBUG: type_name: submit_sm
Re: multiple submit_sm
Hi guys, For those who have this kind of problem the simple soultion is omit-empty = true On Tue, Dec 8, 2009 at 2:32 PM, Elton Hoxha elt...@gmail.com wrote: Hi guys, I`m facing some problem when I submit using TLV parameter for ussd operation. I`m using cvs-20091124 I`m sending an MO request and then sms is submitted using sendsms interface with meta-data parameter included. After the first successful submit, another submit is generated automatically. Anyone can help? Thanks 2009-12-03 17:08:31 [13584] [6] DEBUG: SMPP PDU 0x8718f20 dump: 2009-12-03 17:08:31 [13584] [6] DEBUG: type_name: enquire_link 2009-12-03 17:08:31 [13584] [6] DEBUG: command_id: 21 = 0x0015 2009-12-03 17:08:31 [13584] [6] DEBUG: command_status: 0 = 0x 2009-12-03 17:08:31 [13584] [6] DEBUG: sequence_number: 2 = 0x0002 2009-12-03 17:08:31 [13584] [6] DEBUG: SMPP PDU dump ends. 2009-12-03 17:08:31 [13584] [6] DEBUG: SMPP[test]: throughput (0.00,0.00) 2009-12-03 17:08:31 [13584] [6] DEBUG: SMPP[test]: throughput (0.00,0.00) 2009-12-03 17:08:31 [13584] [6] DEBUG: SMPP[test]: Got PDU: 2009-12-03 17:08:31 [13584] [6] DEBUG: SMPP PDU 0x8718f38 dump: 2009-12-03 17:08:31 [13584] [6] DEBUG: type_name: enquire_link_resp 2009-12-03 17:08:31 [13584] [6] DEBUG: command_id: 2147483669 = 0x8015 2009-12-03 17:08:31 [13584] [6] DEBUG: command_status: 0 = 0x 2009-12-03 17:08:31 [13584] [6] DEBUG: sequence_number: 2 = 0x0002 2009-12-03 17:08:31 [13584] [6] DEBUG: SMPP PDU dump ends. 2009-12-03 17:08:31 [13584] [6] DEBUG: SMPP[test]: throughput (0.00,0.00) 2009-12-03 17:08:41 [13584] [6] DEBUG: SMPP[test]: throughput (0.00,0.00) 2009-12-03 17:08:41 [13584] [6] DEBUG: Optional parameter tag (0x0501) 2009-12-03 17:08:41 [13584] [6] DEBUG: Optional parameter length read as 1 2009-12-03 17:08:41 [13584] [6] DEBUG: Found configured optional parameter `mydata' 2009-12-03 17:08:41 [13584] [6] DEBUG: SMPP[test]: Got PDU: 2009-12-03 17:08:41 [13584] [6] DEBUG: SMPP PDU 0x8718f78 dump: 2009-12-03 17:08:41 [13584] [6] DEBUG: type_name: deliver_sm 2009-12-03 17:08:41 [13584] [6] DEBUG: command_id: 5 = 0x0005 2009-12-03 17:08:41 [13584] [6] DEBUG: command_status: 0 = 0x 2009-12-03 17:08:41 [13584] [6] DEBUG: sequence_number: 10 = 0x000a 2009-12-03 17:08:41 [13584] [6] DEBUG: service_type: USSD 2009-12-03 17:08:41 [13584] [6] DEBUG: source_addr_ton: 1 = 0x0001 2009-12-03 17:08:41 [13584] [6] DEBUG: source_addr_npi: 1 = 0x0001 2009-12-03 17:08:41 [13584] [6] DEBUG: source_addr: 355672118168 2009-12-03 17:08:41 [13584] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2009-12-03 17:08:41 [13584] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2009-12-03 17:08:41 [13584] [6] DEBUG: destination_addr: 200 2009-12-03 17:08:41 [13584] [6] DEBUG: esm_class: 0 = 0x 2009-12-03 17:08:41 [13584] [6] DEBUG: protocol_id: 0 = 0x 2009-12-03 17:08:41 [13584] [6] DEBUG: priority_flag: 0 = 0x 2009-12-03 17:08:41 [13584] [6] DEBUG: schedule_delivery_time: NULL 2009-12-03 17:08:41 [13584] [6] DEBUG: validity_period: NULL 2009-12-03 17:08:41 [13584] [6] DEBUG: registered_delivery: 0 = 0x 2009-12-03 17:08:41 [13584] [6] DEBUG: replace_if_present_flag: 0 = 0x 2009-12-03 17:08:41 [13584] [6] DEBUG: data_coding: 0 = 0x 2009-12-03 17:08:41 [13584] [6] DEBUG: sm_default_msg_id: 0 = 0x 2009-12-03 17:08:41 [13584] [6] DEBUG: sm_length: 5 = 0x0005 2009-12-03 17:08:41 [13584] [6] DEBUG: short_message: *200# 2009-12-03 17:08:41 [13584] [6] DEBUG: mydata: 1 2009-12-03 17:08:41 [13584] [6] DEBUG: SMPP PDU dump ends. 2009-12-03 17:08:41 [13584] [6] WARNING: SMPP[test]: Mallformed addr `200', generally expected at least 7 digits. 2009-12-03 17:08:41 [13584] [6] DEBUG: SMPP[test]: Sending PDU: 2009-12-03 17:08:41 [13584] [6] DEBUG: SMPP PDU 0x871a0c0 dump: 2009-12-03 17:08:41 [13584] [6] DEBUG: type_name: deliver_sm_resp 2009-12-03 17:08:41 [13584] [6] DEBUG: command_id: 2147483653 = 0x8005 2009-12-03 17:08:41 [13584] [6] DEBUG: command_status: 0 = 0x 2009-12-03 17:08:41 [13584] [6] DEBUG: sequence_number: 10 = 0x000a 2009-12-03 17:08:41 [13584] [6] DEBUG: message_id: NULL 2009-12-03 17:08:41 [13584] [6] DEBUG: SMPP PDU dump ends. 2009-12-03 17:08:41 [13584] [6] DEBUG: SMPP[test]: throughput (0.00,0.00) 2009-12-03 17:08:41 [13584] [10] DEBUG: send_msg: sending msg to box: 10.1.21.187 2009-12-03 17:08:41 [13584] [10] DEBUG: boxc_sender: sent message to 10.1.21.187 2009-12-03 17:08:41 [13584] [9] DEBUG: boxc_receiver: got ack 2009-12-03 17:08:41 [13584] [9] DEBUG: boxc_receiver: sms received 2009-12-03 17:08:41 [13584] [9] DEBUG: send_msg: sending msg to box: 10.1.21.187 2009-12-03 17:08:41 [13584] [6] DEBUG: SMPP[test]: throughput (0.00,0.00) 2009-12-03 17:08:41 [13584] [6] DEBUG: new group created `smpp' 2009-12-03 17:08:41
Re: Re: meta-data TLV for USSD
Hi Alex and others, where is the difference in submitting the sms with meta-data variable together with short message text and submitting only meta-data without no text??? 2009-12-03 10:49:37 [12458] [6] DEBUG: group=`smpp' key=`my-custom-var' value=`Hello World' 2009-12-03 10:49:37 [12458] [6] DEBUG: SMPP[test]: Sending PDU: 2009-12-03 10:49:37 [12458] [6] DEBUG: SMPP PDU 0x9313308 dump: 2009-12-03 10:49:37 [12458] [6] DEBUG: type_name: submit_sm 2009-12-03 10:49:37 [12458] [6] DEBUG: command_id: 4 = 0x0004 2009-12-03 10:49:37 [12458] [6] DEBUG: command_status: 0 = 0x 2009-12-03 10:49:37 [12458] [6] DEBUG: sequence_number: 2 = 0x0002 2009-12-03 10:49:37 [12458] [6] DEBUG: service_type: NULL 2009-12-03 10:49:37 [12458] [6] DEBUG: source_addr_ton: 2 = 0x0002 2009-12-03 10:49:37 [12458] [6] DEBUG: source_addr_npi: 1 = 0x0001 2009-12-03 10:49:37 [12458] [6] DEBUG: source_addr: 200 2009-12-03 10:49:37 [12458] [6] DEBUG: dest_addr_ton: 2 = 0x0002 2009-12-03 10:49:37 [12458] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2009-12-03 10:49:37 [12458] [6] DEBUG: destination_addr: 35x 2009-12-03 10:49:37 [12458] [6] DEBUG: esm_class: 3 = 0x0003 2009-12-03 10:49:37 [12458] [6] DEBUG: protocol_id: 0 = 0x 2009-12-03 10:49:37 [12458] [6] DEBUG: priority_flag: 0 = 0x 2009-12-03 10:49:37 [12458] [6] DEBUG: schedule_delivery_time: NULL 2009-12-03 10:49:37 [12458] [6] DEBUG: validity_period: NULL 2009-12-03 10:49:37 [12458] [6] DEBUG: registered_delivery: 0 = 0x 2009-12-03 10:49:37 [12458] [6] DEBUG: replace_if_present_flag: 0 = 0x 2009-12-03 10:49:37 [12458] [6] DEBUG: data_coding: 0 = 0x 2009-12-03 10:49:37 [12458] [6] DEBUG: sm_default_msg_id: 0 = 0x 2009-12-03 10:49:37 [12458] [6] DEBUG: sm_length: 5 = 0x0005 2009-12-03 10:49:37 [12458] [6] DEBUG: short_message: hello 2009-12-03 10:49:37 [12458] [6] DEBUG: my-custom-var: Hello World So hello world in my-custom-var has higher priority or? What happens in these cases with both short message and meta-data? Thanks in advance... Elton On Fri, Dec 4, 2009 at 10:43 AM, Sandesh K sandyk...@rediffmail.com wrote: hi marcin, could please share this valuable information; it would be really delight. What type of provisions we have to do in SMSC; what we need on SMSC side to be enabled. Regards, Sandesh K On Thu, 03 Dec 2009 17:04:41 +0530 wrote 2009/12/3 Elton Hoxha Hello, ... I have partially succeded to connect to USSD, sending MO requests, but then I`m stuck, sessions remains open until it is droped by Core Network. Anyway if you have any conf sample would be a lot of help. Hey all, we are using kannel as gateway for USSD services with success. Generally if you want to use just USSD strings conf may look like this: group = smsc smsc-id = MVNO-USSD-STRING smsc = smpp host = 10.10.10.10 port = 5014 smsc-username = foo smsc-password = bar system-type = VMA service-type = EA log-file= /var/log/kannel-ussd/ussd_strings.log log-level= 0 wait-ack-expire = 1 If you need menu based services just change: service-type = CR It works pretty with Hu*wei USSDC. Soon I'll be ready to release HTTP backend which can be used in sms-service (nifty GUI, menus, games, polls, etc.). If you are interested in such solution just let me know - i'll try to speed things up ;-) Regards, -- Marcin Boćkowski tel. +48 79 69 0 69 79
Re: Automatically split messages
Hi, As far as I know this is performed by SMSC, then mobile phone assembled it and shows as long sms. On Mon, Dec 7, 2009 at 8:27 AM, Hemant Gmail hbaan...@gmail.com wrote: Hi, Can someone please help me with automatic splitting of message? This is what I want to do, suppose a message has 250 characters .. it should automatically get split in two message and add message numbering to it like (1 of 2) and (2 of 2). Please let me know if this is possible in Kannel configuration. Regards, Hemant
Re: meta-data TLV for USSD
Hello, Yes Michael using data SM is more appropriate, but as far as I know many commercial SMPP gateways are also trying to adapt submit and deliver SM by using TLV to communicate with USSD. So I dont guess Kannel is inferior to these other products. I have partially succeded to connect to USSD, sending MO requests, but then I`m stuck, sessions remains open until it is droped by Core Network. Anyway if you have any conf sample would be a lot of help. Thanks Elton On Thu, Dec 3, 2009 at 12:46 AM, Michael Bochkaryov mi...@rattler.kiev.uawrote: Hello, I've tried to connect Kannel with USSD server. In my case it was enough to use ussd_service_op TLV (see SMPP 3.4 spec. p.5.3.2.44). Anyway Kannel is not good solution to implement USSD services because of: a) mostly USSD centers require data_sm instead of submit_sm/deliver_sm PDUs; b) Kannel includes some SMS-related logic (mostly exceptions processing) that doesn't suite for USSD I'll try to find configuration if nobody removed this yet. But I've personally switched to own small Net::SMPP based application. -- Regards, Michael Bochkaryov www.rattler.kiev.ua 2009/12/2 Elton Hoxha elt...@gmail.com Thanks Alex, Does anyone else has experience with USSD applications? Regards Elton On Wed, Dec 2, 2009 at 11:55 AM, Alejandro Guerrieri alejandro.guerri...@gmail.com wrote: Elton, I don't have much experience with USSD honestly, I don't know how is the session started/ended. Kannel's not really designed to work as an USSD gateway, so I'm not sure if you're stumbling with something needing a patch or not. Regarding tags, SMPP Spec 3.4 has a list of the standard values. However, there's a user defined segment (starting 0x1400) where vendors can implement their proprietary tags. There's a copy of the spec here: http://www.nowsms.com/discus/messages/1/SMPP_v3_4_Issue1_2-24857.pdf Hope it helps, Alex On Wed, Dec 2, 2009 at 11:45 AM, Elton Hoxha elt...@gmail.com wrote: Thanks Alex, Actually, for MT cases, Im calling the HTTP using the example in the guide; meta-data=%3Fsmpp%3Fmy-data%3DHello%2BWorld but I receive some SMSC returned errors like invalid destinations, which of course has not to do with kannel. I have two ambigous cases in my head; -How can I terminate the session initialized by MO request? When I throw a request, lets say by dialing *200#, I`m able to call my application sending there %D values, but it lasts many seconds until HLR terminates it by itself. Also If multiple requests in paralel are initialised, how Kannel can keep records of each session, so when I will reply back from cgi-bin, kannel will understand the respective session and drop it? - How can I find the related specifications for Tag parameter? I see many combinations in hexadecimal but withput understanding their meaning. Is there any explanations for each hexa code? Thank You, Elton On Wed, Dec 2, 2009 at 11:23 AM, Alejandro Guerrieri alejandro.guerri...@gmail.com wrote: You need to pass the value on the meta-data field. For example: meta-data=?smpp?my-custom-var=1 (urlencoded of course) Regards, Alex On Wed, Dec 2, 2009 at 9:01 AM, Elton Hoxha elt...@gmail.com wrote: Hi guys, I`m trying to use kannel for sending ussd request and receiving back using SMPP. my conf for TLV is: group = smpp-tlv name = my-custom-var tag = 0x0501 type = integer length = 2 smsc-id = test Using this I`m able to call my application by dialing ussd shortcodes, but I`m not able to terminate the session immediately. Also the values of ussd parameters take place under the VALUE parameter of TLV itself which is not present in the above conf. How can I manipulate this parameter if its not configurable in kannel? P.S this is an example I found googling around; Field Size Octets Type Description Parameter Tag 2 Integer 0x0501 Length 2 Integer Length of value part in octets Value 1 Integer This value can be one of the following values: 0 = PSSD Indication 1 = PSSR Indication 2 = USSR Request 3 = USSN Request 4 to 15 = Reserved 16 = PSSD Response 17 = PSSR Response 18 = USSR Confirm 19 = USSN Confirm 20 to 31 = Reserved 32 to 255 = Vendor specific operations
meta-data TLV for USSD
Hi guys, I`m trying to use kannel for sending ussd request and receiving back using SMPP. my conf for TLV is: group = smpp-tlv name = my-custom-var tag = 0x0501 type = integer length = 2 smsc-id = test Using this I`m able to call my application by dialing ussd shortcodes, but I`m not able to terminate the session immediately. Also the values of ussd parameters take place under the VALUE parameter of TLV itself which is not present in the above conf. How can I manipulate this parameter if its not configurable in kannel? P.S this is an example I found googling around; Field Size Octets Type Description Parameter Tag 2 Integer 0x0501 Length 2 Integer Length of value part in octets Value 1 Integer This value can be one of the following values: 0 = PSSD Indication 1 = PSSR Indication 2 = USSR Request 3 = USSN Request 4 to 15 = Reserved 16 = PSSD Response 17 = PSSR Response 18 = USSR Confirm 19 = USSN Confirm 20 to 31 = Reserved 32 to 255 = Vendor specific operations
Re: meta-data TLV for USSD
Thanks Alex, Actually, for MT cases, Im calling the HTTP using the example in the guide; meta-data=%3Fsmpp%3Fmy-data%3DHello%2BWorld but I receive some SMSC returned errors like invalid destinations, which of course has not to do with kannel. I have two ambigous cases in my head; -How can I terminate the session initialized by MO request? When I throw a request, lets say by dialing *200#, I`m able to call my application sending there %D values, but it lasts many seconds until HLR terminates it by itself. Also If multiple requests in paralel are initialised, how Kannel can keep records of each session, so when I will reply back from cgi-bin, kannel will understand the respective session and drop it? - How can I find the related specifications for Tag parameter? I see many combinations in hexadecimal but withput understanding their meaning. Is there any explanations for each hexa code? Thank You, Elton On Wed, Dec 2, 2009 at 11:23 AM, Alejandro Guerrieri alejandro.guerri...@gmail.com wrote: You need to pass the value on the meta-data field. For example: meta-data=?smpp?my-custom-var=1 (urlencoded of course) Regards, Alex On Wed, Dec 2, 2009 at 9:01 AM, Elton Hoxha elt...@gmail.com wrote: Hi guys, I`m trying to use kannel for sending ussd request and receiving back using SMPP. my conf for TLV is: group = smpp-tlv name = my-custom-var tag = 0x0501 type = integer length = 2 smsc-id = test Using this I`m able to call my application by dialing ussd shortcodes, but I`m not able to terminate the session immediately. Also the values of ussd parameters take place under the VALUE parameter of TLV itself which is not present in the above conf. How can I manipulate this parameter if its not configurable in kannel? P.S this is an example I found googling around; Field Size Octets Type Description Parameter Tag 2 Integer 0x0501 Length 2 Integer Length of value part in octets Value 1 Integer This value can be one of the following values: 0 = PSSD Indication 1 = PSSR Indication 2 = USSR Request 3 = USSN Request 4 to 15 = Reserved 16 = PSSD Response 17 = PSSR Response 18 = USSR Confirm 19 = USSN Confirm 20 to 31 = Reserved 32 to 255 = Vendor specific operations
Re: meta-data TLV for USSD
Thanks Alex, Does anyone else has experience with USSD applications? Regards Elton On Wed, Dec 2, 2009 at 11:55 AM, Alejandro Guerrieri alejandro.guerri...@gmail.com wrote: Elton, I don't have much experience with USSD honestly, I don't know how is the session started/ended. Kannel's not really designed to work as an USSD gateway, so I'm not sure if you're stumbling with something needing a patch or not. Regarding tags, SMPP Spec 3.4 has a list of the standard values. However, there's a user defined segment (starting 0x1400) where vendors can implement their proprietary tags. There's a copy of the spec here: http://www.nowsms.com/discus/messages/1/SMPP_v3_4_Issue1_2-24857.pdf Hope it helps, Alex On Wed, Dec 2, 2009 at 11:45 AM, Elton Hoxha elt...@gmail.com wrote: Thanks Alex, Actually, for MT cases, Im calling the HTTP using the example in the guide; meta-data=%3Fsmpp%3Fmy-data%3DHello%2BWorld but I receive some SMSC returned errors like invalid destinations, which of course has not to do with kannel. I have two ambigous cases in my head; -How can I terminate the session initialized by MO request? When I throw a request, lets say by dialing *200#, I`m able to call my application sending there %D values, but it lasts many seconds until HLR terminates it by itself. Also If multiple requests in paralel are initialised, how Kannel can keep records of each session, so when I will reply back from cgi-bin, kannel will understand the respective session and drop it? - How can I find the related specifications for Tag parameter? I see many combinations in hexadecimal but withput understanding their meaning. Is there any explanations for each hexa code? Thank You, Elton On Wed, Dec 2, 2009 at 11:23 AM, Alejandro Guerrieri alejandro.guerri...@gmail.com wrote: You need to pass the value on the meta-data field. For example: meta-data=?smpp?my-custom-var=1 (urlencoded of course) Regards, Alex On Wed, Dec 2, 2009 at 9:01 AM, Elton Hoxha elt...@gmail.com wrote: Hi guys, I`m trying to use kannel for sending ussd request and receiving back using SMPP. my conf for TLV is: group = smpp-tlv name = my-custom-var tag = 0x0501 type = integer length = 2 smsc-id = test Using this I`m able to call my application by dialing ussd shortcodes, but I`m not able to terminate the session immediately. Also the values of ussd parameters take place under the VALUE parameter of TLV itself which is not present in the above conf. How can I manipulate this parameter if its not configurable in kannel? P.S this is an example I found googling around; Field Size Octets Type Description Parameter Tag 2 Integer 0x0501 Length 2 Integer Length of value part in octets Value 1 Integer This value can be one of the following values: 0 = PSSD Indication 1 = PSSR Indication 2 = USSR Request 3 = USSN Request 4 to 15 = Reserved 16 = PSSD Response 17 = PSSR Response 18 = USSR Confirm 19 = USSN Confirm 20 to 31 = Reserved 32 to 255 = Vendor specific operations
Re: How to Make URL based Carrier Server using Kannel like jatayu
I have implemented what you are asking. Third parties, or users having respective usernames and password connects to my proxy via HTTP (XML), inserting their sms to my db. After, I pick them up from db and push through kannel http interface. THis is applied for both MO and MT. For sure you need to develop some extra interface. On Wed, Nov 18, 2009 at 2:08 PM, Henri Hovi henri.h...@patidure.com wrote: Or use the sqlbox to inject the messages instead of the HTTP connection from script to Kannel... On Wed, Nov 18, 2009 at 3:06 PM, Henri Hovi henri.h...@patidure.com wrote: Hi, now Your question has some sense... If You must use database, the easiest way would be to do some front-end script which receives the messages, authenticates the users and manages the statistics, then one common account to Kannel where the messages are forwarded. Anyhow, this ight be too much overhead if You have a lot of traffic. Another option requires You to change Kannel to use database to store and collect such information and that can be pretty big job. -- Henri On Wed, Nov 18, 2009 at 2:58 PM, Amritesh Rachelwar amriteshs...@gmail.com wrote: Dear, Actually we are interested to make one URL, using which any one can send SMS having a specific username and password using internet. We need to maintain database for them all that how many SMS they have sent and time, destination no etc. So i need to configure the kannel for a no of username and password and need to maintain database separately according to username. Thanks and Regards Amritesh Deepak Rachelwar 2009/11/18 Nikos Balkanas n...@amdtelecom.net Hi, I presume you are talking about push SMS (MT) messages. Sendsms users are not kept in a database, but in the configuration guide. Please read about group sendsms-user in the User Guide. BR, Nikos - Original Message - From: Amritesh Rachelwar To: users Sent: Wednesday, November 18, 2009 1:51 PM Subject: How to Make URL based Carrier Server using Kannel like jatayu Dear, We want to make a URL (HTTP) based Server using kannel gateway. We have one SMPP connectivity with SMSC and a Static IP. How can we create different username and passwords for all users and how to manage there data bases accordingly. Thanks and Regards Amritesh Deepak Rachelwar -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com
Re: problem connecting to SMSC using SMPP 3.4
Maybe it has to do with system type parameter. You have it empty here, meanwhile it maybe configured at the smsc side. Ask from them what is system type name. On Thu, Nov 19, 2009 at 5:33 PM, Stéphane Bruno mysubscription...@gmail.com wrote: Hello all, I am trying to connect to an SMSC using SMPP 3.4. I am receiving the following error: [7] ERROR: connect failed 2009-11-19 11:30:28 [2889] [7] ERROR: System error 22: Invalid argument 2009-11-19 11:30:28 [2889] [7] ERROR: error connecting to server `IP_ADDRESS' at port `3717' 2009-11-19 11:30:28 [2889] [7] ERROR: SMPP[voila]: Couldn't connect to server. 2009-11-19 11:30:28 [2889] [7] ERROR: SMPP[voila]: Couldn't connect to SMS center (retrying in 10 seconds). Here is my config for the SMSC: group = smsc smsc = smpp host = IP_ADDRESS smsc-id = AN_ID allowed-smsc-id = AN_ID port = 3717 #receive-port = our-host = MY_HOST_NAME smsc-username = USERNAME smsc-password = PASSWORD system-type = transceiver-mode = true #service-type = interface-version = 34 #address-range = my-number = 7464 source-addr-ton = 1 dest-addr-ton = 1 #bind-addr-ton = 1 source-addr-npi = 1 dest-addr-npi = 1 #bind-addr-npi = 1 source-addr-autodetect = false #alt-charset = log-file = /var/log/kannel/voila.log log-level = 1 Please help! Stéphane
concat for MO
Hi guys, what is the purpose of concatenation parameter in sms-service group? group = sms-service #keyword = default keyword-regex = .* catch-all = true #disables the sending of SMS max-messages = 0 concatenation = true accepted-smsc = x get-url = http:/xxx/KannelGetSms.asmx/GetSms?originator=%pdestination=%Ptext=%asmsctype=%i I mean, as a name is meaningful, the explanation in the guide as well, but when it is set to true the end side( which is kannel) receives the parts of longs sms and doesnt assemble them. Any help appreaciated. Elton
SMSC name conflict???
Hi guys, Is there any possibility to have conflict between two bearerbox processes running in paralel, having separate smpp connection but same SMSC name?? example: gprs-bill 2009-11-04 16:50:44 [5057] [6] DEBUG: SMPP[gprs-bill]: Sending enquire link: 2009-11-04 16:50:44 [5057] [6] DEBUG: SMPP PDU 0x9743758 dump: 2009-11-04 16:50:44 [5057] [6] DEBUG: type_name: enquire_link 2009-11-04 16:50:44 [5057] [6] DEBUG: command_id: 21 = 0x0015 2009-11-04 16:50:44 [5057] [6] DEBUG: command_status: 0 = 0x 2009-11-04 16:50:44 [5057] [6] DEBUG: sequence_number: 28 = 0x001c 2009-11-04 16:50:44 [5057] [6] DEBUG: SMPP PDU dump ends. I`m just doubting because I had some connection reset errors. Thanks
Fwd: SMSC name conflict???
More details: - a.conf group=smsc smsc=smpp smsc-id=gprs-bill interface-version=34 host=10.1.7.21 port=1600 system-id=a smsc-password=a system-type=a transceiver-mode=true - b.conf group=smsc smsc=smpp smsc-id=gprs-bill interface-version=34 host=10.1.7.21 port=1600 system-id=b smsc-password=b system-type=b transceiver-mode=true So, starting to bearerboxes (normally with different ports) may cause any problem if both conf files have same smsc-id? Thanks On Wed, Nov 4, 2009 at 5:43 PM, vijay shanker vijay.s...@gmail.com wrote: Can not be conformed. How many connection your SMMP service provider supports? Two bearer box may be running but on different ports. Try to find out or give more relevant details. Like what is your configuration? or what is the problem you have encountered. Regards, Vijay Shanker Dubey On Wed, Nov 4, 2009 at 9:22 PM, Elton Hoxha elt...@gmail.com wrote: Hi guys, Is there any possibility to have conflict between two bearerbox processes running in paralel, having separate smpp connection but same SMSC name?? example: gprs-bill 2009-11-04 16:50:44 [5057] [6] DEBUG: SMPP[gprs-bill]: Sending enquire link: 2009-11-04 16:50:44 [5057] [6] DEBUG: SMPP PDU 0x9743758 dump: 2009-11-04 16:50:44 [5057] [6] DEBUG: type_name: enquire_link 2009-11-04 16:50:44 [5057] [6] DEBUG: command_id: 21 = 0x0015 2009-11-04 16:50:44 [5057] [6] DEBUG: command_status: 0 = 0x 2009-11-04 16:50:44 [5057] [6] DEBUG: sequence_number: 28 = 0x001c 2009-11-04 16:50:44 [5057] [6] DEBUG: SMPP PDU dump ends. I`m just doubting because I had some connection reset errors. Thanks
Re: SMSC name conflict???
Thanks Alvaro but its a misundesrtanding. ITs not a matter of SMSC provider. Im just thinking from kannel point of view, considering the example I gave above. Actually both conenctions are live and running, but sometimes having interruption, connection reset by peer. When sending the enquiry link, kannel prints smsc name 2009-11-04 18:28:44 [5057] [6] DEBUG: SMPP[gprs-bill]: Sending enquire link: 2009-11-04 18:28:44 [5057] [6] DEBUG: SMPP PDU 0x973d3a8 dump: 2009-11-04 18:28:44 [5057] [6] DEBUG: type_name: enquire_link 2009-11-04 18:28:44 [5057] [6] DEBUG: command_id: 21 = 0x0015 2009-11-04 18:28:44 [5057] [6] DEBUG: command_status: 0 = 0x 2009-11-04 18:28:44 [5057] [6] DEBUG: sequence_number: 224 = 0x00e0 2009-11-04 18:28:44 [5057] [6] DEBUG: SMPP PDU dump ends. So by havving two processes by sending enqiry links or whatever with the same name gprs-bill, may be any problem? THanks On Wed, Nov 4, 2009 at 6:20 PM, Alvaro Cornejo cornejo.alv...@gmail.comwrote: Elton I think it is more a problem from your SMSC provider. If they do allow you to have 2 -or more- connections to the same port or not. The connection resets can happen for multiple reasons including problems on any of the peers, the network (Lan/Wan) , etc. 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 www.smsglobal.com.mx y www.pravcom.com On Wed, Nov 4, 2009 at 11:56 AM, Elton Hoxha elt...@gmail.com wrote: More details: - a.conf group=smsc smsc=smpp smsc-id=gprs-bill interface-version=34 host=10.1.7.21 port=1600 system-id=a smsc-password=a system-type=a transceiver-mode=true - b.conf group=smsc smsc=smpp smsc-id=gprs-bill interface-version=34 host=10.1.7.21 port=1600 system-id=b smsc-password=b system-type=b transceiver-mode=true So, starting to bearerboxes (normally with different ports) may cause any problem if both conf files have same smsc-id? Thanks On Wed, Nov 4, 2009 at 5:43 PM, vijay shanker vijay.s...@gmail.com wrote: Can not be conformed. How many connection your SMMP service provider supports? Two bearer box may be running but on different ports. Try to find out or give more relevant details. Like what is your configuration? or what is the problem you have encountered. Regards, Vijay Shanker Dubey On Wed, Nov 4, 2009 at 9:22 PM, Elton Hoxha elt...@gmail.com wrote: Hi guys, Is there any possibility to have conflict between two bearerbox processes running in paralel, having separate smpp connection but same SMSC name?? example: gprs-bill 2009-11-04 16:50:44 [5057] [6] DEBUG: SMPP[gprs-bill]: Sending enquire link: 2009-11-04 16:50:44 [5057] [6] DEBUG: SMPP PDU 0x9743758 dump: 2009-11-04 16:50:44 [5057] [6] DEBUG: type_name: enquire_link 2009-11-04 16:50:44 [5057] [6] DEBUG: command_id: 21 = 0x0015 2009-11-04 16:50:44 [5057] [6] DEBUG: command_status: 0 = 0x 2009-11-04 16:50:44 [5057] [6] DEBUG: sequence_number: 28 = 0x001c 2009-11-04 16:50:44 [5057] [6] DEBUG: SMPP PDU dump ends. I`m just doubting because I had some connection reset errors. Thanks
Re: Replace if present parameter in kannel
Hasnt anyone dealed before with this issue? I have to develop some application which its depended on sms replacement...please guys give me some ideas how I can handle it. Thanks Elton On Tue, Oct 13, 2009 at 10:31 AM, Elton Hoxha elt...@gmail.com wrote: Hi, As the mentioned issue is one of basic functionalities of SMPP, I think it should be an workaround, even if its not possible through explicit defined parameters. I read this article in the blog http://tiliman.wordpress.com/2008/12/20/replacing-sms-on-a-phone-using-kannel-sms-gateway/ Sending a self destruct or replaceable message is pretty easy with Kannel as long as your SMSC supports it. Send first SMS with pid=65 http://SERVER:PORT /cgi-bin/sendsms?from=55512345username=mepassword=mypass to=5551233text=original+msgpid=65 Send second SMS with pid=65 http://SERVER:PORT /cgi-bin/sendsms?from=55512345username=mepassword=mypass to=5551233text=msg+replacedpid=65 Can I have your comments on this method? (As far as I read pid values are limited) Thanks Elton 2009/10/12 Nikos Balkanas nbalka...@gmail.com Hi, There is no such a parameter in configuration variables. For an up2date list of all configureation variables see gwlib/cfg.def. I guess if it doesn't exist, you cannot set it. BR, Nikos - Original Message - *From:* Elton Hoxha elt...@gmail.com *To:* Nikos Balkanas nbalka...@gmail.com *Cc:* kannel users users@kannel.org *Sent:* Monday, October 12, 2009 4:49 PM *Subject:* Re: Replace if present parameter in kannel Hi, I guess it is configuration issue same like other optional parameters; validity, source npi, address range etc. How can I set this parameter for replacing old submits in the queue? Thanks 2009/10/12 Nikos Balkanas nbalka...@gmail.com Hi, ???. What are u referring to? Configuration? Source code? Nikos - Original Message - *From:* Elton Hoxha elt...@gmail.com *To:* kannel users users@kannel.org *Sent:* Monday, October 12, 2009 3:56 PM *Subject:* Replace if present parameter in kannel Hi guys, Can anybody tell me how can I set the if present parameter to 0 or 1 depending on my needs? In the guide, at smpp section I couldnt find anything. Thanks Elton
Re: Replace if present parameter in kannel
Hi, As the mentioned issue is one of basic functionalities of SMPP, I think it should be an workaround, even if its not possible through explicit defined parameters. I read this article in the blog http://tiliman.wordpress.com/2008/12/20/replacing-sms-on-a-phone-using-kannel-sms-gateway/ Sending a self destruct or replaceable message is pretty easy with Kannel as long as your SMSC supports it. Send first SMS with pid=65 http://SERVER:PORT /cgi-bin/sendsms?from=55512345username=mepassword=mypass to=5551233text=original+msgpid=65 Send second SMS with pid=65 http://SERVER:PORT /cgi-bin/sendsms?from=55512345username=mepassword=mypass to=5551233text=msg+replacedpid=65 Can I have your comments on this method? (As far as I read pid values are limited) Thanks Elton 2009/10/12 Nikos Balkanas nbalka...@gmail.com Hi, There is no such a parameter in configuration variables. For an up2date list of all configureation variables see gwlib/cfg.def. I guess if it doesn't exist, you cannot set it. BR, Nikos - Original Message - *From:* Elton Hoxha elt...@gmail.com *To:* Nikos Balkanas nbalka...@gmail.com *Cc:* kannel users users@kannel.org *Sent:* Monday, October 12, 2009 4:49 PM *Subject:* Re: Replace if present parameter in kannel Hi, I guess it is configuration issue same like other optional parameters; validity, source npi, address range etc. How can I set this parameter for replacing old submits in the queue? Thanks 2009/10/12 Nikos Balkanas nbalka...@gmail.com Hi, ???. What are u referring to? Configuration? Source code? Nikos - Original Message - *From:* Elton Hoxha elt...@gmail.com *To:* kannel users users@kannel.org *Sent:* Monday, October 12, 2009 3:56 PM *Subject:* Replace if present parameter in kannel Hi guys, Can anybody tell me how can I set the if present parameter to 0 or 1 depending on my needs? In the guide, at smpp section I couldnt find anything. Thanks Elton
Replace if present parameter in kannel
Hi guys, Can anybody tell me how can I set the if present parameter to 0 or 1 depending on my needs? In the guide, at smpp section I couldnt find anything. Thanks Elton
Re: Replace if present parameter in kannel
Hi, I guess it is configuration issue same like other optional parameters; validity, source npi, address range etc. How can I set this parameter for replacing old submits in the queue? Thanks 2009/10/12 Nikos Balkanas nbalka...@gmail.com Hi, ???. What are u referring to? Configuration? Source code? Nikos - Original Message - *From:* Elton Hoxha elt...@gmail.com *To:* kannel users users@kannel.org *Sent:* Monday, October 12, 2009 3:56 PM *Subject:* Replace if present parameter in kannel Hi guys, Can anybody tell me how can I set the if present parameter to 0 or 1 depending on my needs? In the guide, at smpp section I couldnt find anything. Thanks Elton
smsbox http administration
Hi guys, I would like to know if there is any chance to stop/start the smsboxes via HTTP like we do with beareboxes. In the manual there is the following; restart Re-start whole bearerbox, hence all SMSC links. Password required. Beware that you loose the smsbox connections in such a case. So, after bringing up the bearerboxes how can we be able to manage the smsboxes as well (excluding the option of starting via shell) Thanks Elton
Re: validity period of sms messages
In minutes On Fri, Jun 26, 2009 at 10:00 AM, Latitude Berlin latitude.de@ googlemail.com wrote: Hi, Valitidy period of SMS message in the HTTP send request (...validity=) should be specified as milli sec or sec? For example: For validity period of 10 minutes, I will try ...validity=10*60*1000 Thanks.
Re: SMPP Disconnection
Hi, Refering to this thread: http://www.kannel.org/pipermail/devel/2006-December/000688.html In earlier version this problem was present, according to Stipe, it was solved after the new releases. Is there a relationship with the intervals of enquiry links or high load sms traffic? Regards Elton On Mon, Jun 22, 2009 at 10:28 AM, Falko Ziemann fal...@gmail.com wrote: Hi, maybe a problem with the enquire link interval? So that the enquire_link comes, when the smsc already run into a timeout? Regards Falko Am 22.06.2009 um 08:55 schrieb Elton Hoxha: Hi guys, From the application (the application that listens and sends through kannel) I noticed some queued for later delivery logs. I checked the kannel logs for the respective time that happened. The connection is re-established but do you have any idea what is the reason of System Error 104? Thanks 2009-06-21 18:14:09 [5781] [6] DEBUG: SMPP[credit-141]: Sending enquire link: 2009-06-21 18:14:09 [5781] [6] DEBUG: SMPP PDU 0xb2200708 dump: 2009-06-21 18:14:09 [5781] [6] DEBUG: type_name: enquire_link 2009-06-21 18:14:09 [5781] [6] DEBUG: command_id: 21 = 0x0015 2009-06-21 18:14:09 [5781] [6] DEBUG: command_status: 0 = 0x 2009-06-21 18:14:09 [5781] [6] DEBUG: sequence_number: 18694 = 0x4906 2009-06-21 18:14:09 [5781] [6] DEBUG: SMPP PDU dump ends. 2009-06-21 18:14:09 [5781] [6] ERROR: Error reading from fd 25: 2009-06-21 18:14:09 [5781] [6] ERROR: System error 104: Connection reset by peer 2009-06-21 18:14:09 [5781] [6] ERROR: SMPP[credit-141]: Couldn't connect to SMS center (retrying in 10 seconds). 2009-06-21 18:14:12 [5781] [8] DEBUG: boxc_receiver: sms received 2009-06-21 18:14:12 [5781] [8] DEBUG: send_msg: sending msg to box: 10.1.2.202 2009-06-21 18:14:12 [5781] [7] DEBUG: clear_old_concat_parts called 2009-06-21 18:14:12 [5781] [7] DEBUG: sms_router: handling message (0x98610f8 vs 0x98610f8) 2009-06-21 18:14:12 [5781] [7] DEBUG: Routing failed, re-queued. 2009-06-21 18:14:12 [5781] [7] DEBUG: sms_router: handling message (0x98610f8 vs 0x98610f8) 2009-06-21 18:14:12 [5781] [7] DEBUG: Routing failed, re-queued. 2009-06-21 18:14:12 [5781] [7] DEBUG: sms_router: time to sleep 30.00 secs. 2009-06-21 18:14:12 [5781] [7] DEBUG: sms_router: gwlist_len = 1 2009-06-21 18:14:12 [5781] [7] DEBUG: sms_router: handling message (0x98610f8 vs 0x98610f8) 2009-06-21 18:14:12 [5781] [7] DEBUG: Routing failed, re-queued. 2009-06-21 18:14:12 [5781] [7] DEBUG: sms_router: handling message (0x98610f8 vs 0x98610f8) 2009-06-21 18:14:12 [5781] [7] DEBUG: Routing failed, re-queued. 2009-06-21 18:14:12 [5781] [7] DEBUG: sms_router: time to sleep 30.00 secs. 2009-06-21 18:14:15 [5781] [8] DEBUG: boxc_receiver: sms received 2009-06-21 18:14:15 [5781] [8] DEBUG: send_msg: sending msg to box: 10.1.2.202 2009-06-21 18:14:19 [5781] [8] DEBUG: boxc_receiver: sms received 2009-06-21 18:14:19 [5781] [8] DEBUG: send_msg: sending msg to box: 10.1.2.202 2009-06-21 18:14:19 [5781] [6] DEBUG: SMPP[credit-141]: Sending PDU: 2009-06-21 18:14:19 [5781] [6] DEBUG: SMPP PDU 0xb2200590 dump: 2009-06-21 18:14:19 [5781] [6] DEBUG: type_name: bind_transceiver 2009-06-21 18:14:19 [5781] [6] DEBUG: command_id: 9 = 0x0009 2009-06-21 18:14:19 [5781] [6] DEBUG: command_status: 0 = 0x 2009-06-21 18:14:19 [5781] [6] DEBUG: sequence_number: 18695 = 0x4907 2009-06-21 18:14:19 [5781] [6] DEBUG: system_id: xxx 2009-06-21 18:14:19 [5781] [6] DEBUG: password: xxx 2009-06-21 18:14:19 [5781] [6] DEBUG: system_type: xxx 2009-06-21 18:14:19 [5781] [6] DEBUG: interface_version: 52 = 0x0034 2009-06-21 18:14:19 [5781] [6] DEBUG: addr_ton: 0 = 0x 2009-06-21 18:14:19 [5781] [6] DEBUG: addr_npi: 0 = 0x 2009-06-21 18:14:19 [5781] [6] DEBUG: address_range: 141 2009-06-21 18:14:19 [5781] [6] DEBUG: SMPP PDU dump ends. 2009-06-21 18:14:19 [5781] [6] DEBUG: Optional parameter tag (0x0210) 2009-06-21 18:14:19 [5781] [6] DEBUG: Optional parameter length read as 1 2009-06-21 18:14:19 [5781] [6] DEBUG: SMPP[credit-141]: Got PDU: 2009-06-21 18:14:19 [5781] [6] DEBUG: SMPP PDU 0xb2200590 dump: 2009-06-21 18:14:19 [5781] [6] DEBUG: type_name: bind_transceiver_resp 2009-06-21 18:14:19 [5781] [6] DEBUG: command_id: 2147483657 = 0x8009 2009-06-21 18:14:19 [5781] [6] DEBUG: command_status: 0 = 0x 2009-06-21 18:14:19 [5781] [6] DEBUG: sequence_number: 18695 = 0x4907 2009-06-21 18:14:19 [5781] [6] DEBUG: system_id: NULL 2009-06-21 18:14:19 [5781] [6] DEBUG: sc_interface_version: 52 = 0x0034 2009-06-21 18:14:19 [5781] [6] DEBUG: SMPP PDU dump ends. 2009-06-21 18:14:19 [5781] [7] DEBUG: sms_router: gwlist_len = 3 2009-06-21 18:14:19 [5781] [7] DEBUG: sms_router: handling message (0x98610f8 vs 0x98610f8) 2009-06-21 18:14:19 [5781] [7] DEBUG: Message routed successfully. 2009-06-21 18:14:19 [5781] [7] DEBUG: sms_router: handling
SMPP Disconnection
Hi guys, From the application (the application that listens and sends through kannel) I noticed some queued for later delivery logs. I checked the kannel logs for the respective time that happened. The connection is re-established but do you have any idea what is the reason of System Error 104? Thanks 2009-06-21 18:14:09 [5781] [6] DEBUG: SMPP[credit-141]: Sending enquire link: 2009-06-21 18:14:09 [5781] [6] DEBUG: SMPP PDU 0xb2200708 dump: 2009-06-21 18:14:09 [5781] [6] DEBUG: type_name: enquire_link 2009-06-21 18:14:09 [5781] [6] DEBUG: command_id: 21 = 0x0015 2009-06-21 18:14:09 [5781] [6] DEBUG: command_status: 0 = 0x 2009-06-21 18:14:09 [5781] [6] DEBUG: sequence_number: 18694 = 0x4906 2009-06-21 18:14:09 [5781] [6] DEBUG: SMPP PDU dump ends. 2009-06-21 18:14:09 [5781] [6] ERROR: Error reading from fd 25: 2009-06-21 18:14:09 [5781] [6] ERROR: System error 104: Connection reset by peer 2009-06-21 18:14:09 [5781] [6] ERROR: SMPP[credit-141]: Couldn't connect to SMS center (retrying in 10 seconds). 2009-06-21 18:14:12 [5781] [8] DEBUG: boxc_receiver: sms received 2009-06-21 18:14:12 [5781] [8] DEBUG: send_msg: sending msg to box: 10.1.2.202 2009-06-21 18:14:12 [5781] [7] DEBUG: clear_old_concat_parts called 2009-06-21 18:14:12 [5781] [7] DEBUG: sms_router: handling message (0x98610f8 vs 0x98610f8) 2009-06-21 18:14:12 [5781] [7] DEBUG: Routing failed, re-queued. 2009-06-21 18:14:12 [5781] [7] DEBUG: sms_router: handling message (0x98610f8 vs 0x98610f8) 2009-06-21 18:14:12 [5781] [7] DEBUG: Routing failed, re-queued. 2009-06-21 18:14:12 [5781] [7] DEBUG: sms_router: time to sleep 30.00 secs. 2009-06-21 18:14:12 [5781] [7] DEBUG: sms_router: gwlist_len = 1 2009-06-21 18:14:12 [5781] [7] DEBUG: sms_router: handling message (0x98610f8 vs 0x98610f8) 2009-06-21 18:14:12 [5781] [7] DEBUG: Routing failed, re-queued. 2009-06-21 18:14:12 [5781] [7] DEBUG: sms_router: handling message (0x98610f8 vs 0x98610f8) 2009-06-21 18:14:12 [5781] [7] DEBUG: Routing failed, re-queued. 2009-06-21 18:14:12 [5781] [7] DEBUG: sms_router: time to sleep 30.00 secs. 2009-06-21 18:14:15 [5781] [8] DEBUG: boxc_receiver: sms received 2009-06-21 18:14:15 [5781] [8] DEBUG: send_msg: sending msg to box: 10.1.2.202 2009-06-21 18:14:19 [5781] [8] DEBUG: boxc_receiver: sms received 2009-06-21 18:14:19 [5781] [8] DEBUG: send_msg: sending msg to box: 10.1.2.202 2009-06-21 18:14:19 [5781] [6] DEBUG: SMPP[credit-141]: Sending PDU: 2009-06-21 18:14:19 [5781] [6] DEBUG: SMPP PDU 0xb2200590 dump: 2009-06-21 18:14:19 [5781] [6] DEBUG: type_name: bind_transceiver 2009-06-21 18:14:19 [5781] [6] DEBUG: command_id: 9 = 0x0009 2009-06-21 18:14:19 [5781] [6] DEBUG: command_status: 0 = 0x 2009-06-21 18:14:19 [5781] [6] DEBUG: sequence_number: 18695 = 0x4907 2009-06-21 18:14:19 [5781] [6] DEBUG: system_id: xxx 2009-06-21 18:14:19 [5781] [6] DEBUG: password: xxx 2009-06-21 18:14:19 [5781] [6] DEBUG: system_type: xxx 2009-06-21 18:14:19 [5781] [6] DEBUG: interface_version: 52 = 0x0034 2009-06-21 18:14:19 [5781] [6] DEBUG: addr_ton: 0 = 0x 2009-06-21 18:14:19 [5781] [6] DEBUG: addr_npi: 0 = 0x 2009-06-21 18:14:19 [5781] [6] DEBUG: address_range: 141 2009-06-21 18:14:19 [5781] [6] DEBUG: SMPP PDU dump ends. 2009-06-21 18:14:19 [5781] [6] DEBUG: Optional parameter tag (0x0210) 2009-06-21 18:14:19 [5781] [6] DEBUG: Optional parameter length read as 1 2009-06-21 18:14:19 [5781] [6] DEBUG: SMPP[credit-141]: Got PDU: 2009-06-21 18:14:19 [5781] [6] DEBUG: SMPP PDU 0xb2200590 dump: 2009-06-21 18:14:19 [5781] [6] DEBUG: type_name: bind_transceiver_resp 2009-06-21 18:14:19 [5781] [6] DEBUG: command_id: 2147483657 = 0x8009 2009-06-21 18:14:19 [5781] [6] DEBUG: command_status: 0 = 0x 2009-06-21 18:14:19 [5781] [6] DEBUG: sequence_number: 18695 = 0x4907 2009-06-21 18:14:19 [5781] [6] DEBUG: system_id: NULL 2009-06-21 18:14:19 [5781] [6] DEBUG: sc_interface_version: 52 = 0x0034 2009-06-21 18:14:19 [5781] [6] DEBUG: SMPP PDU dump ends. 2009-06-21 18:14:19 [5781] [7] DEBUG: sms_router: gwlist_len = 3 2009-06-21 18:14:19 [5781] [7] DEBUG: sms_router: handling message (0x98610f8 vs 0x98610f8) 2009-06-21 18:14:19 [5781] [7] DEBUG: Message routed successfully. 2009-06-21 18:14:19 [5781] [7] DEBUG: sms_router: handling message (0x9860918 vs 0x9860918)
Re: SMS with GSM character set
Thanks Jyoti, I will give it a try. Falko, If I use UTF-8 in URL, it should be used with coding = 1, which cause that the content will be delivered in unreadable format for the mobile. Otherwise, If I use ISO-8859-1, i should add coding=2 which encodes it in 16-bit (the characters are normally delivered) but I reduce the bytes having only 70 characters. Regards elton On Fri, May 8, 2009 at 7:35 AM, Falko Ziemann fal...@gmail.com wrote: Elton, please read my last mail again. You must not encode the text in the sendsms URL in gsm! You must send the text to kannel in the encoding the http-client tells kannel which characterset it uses, so mostly UTF-8 or Iso-Latin Regards Falko Am 07.05.2009 um 16:18 schrieb Elton Hoxha: SMPP configuration is simple, I think everybody has it like this group=smsc smsc=smpp smsc-id=internal1 interface-version=34 host=10.x.x.x port=1600 system-id=test smsc-password=test system-type=test transceiver-mode=false address-range=7070 Can anyone please who is able to send these kind of characters (for example @), paste me the smpp configuration or the send-sms url that is used with the required parameters? Regards Elton On Thu, May 7, 2009 at 1:48 PM, Jovan Kostovski chomb...@gmail.comwrote: On Thu, May 7, 2009 at 1:26 PM, Elton Hoxha elt...@gmail.com wrote: I checked many many times, kannel is sending empty message when i type these special characters. I traced by ethereal the smpp block and there is no text forwarded by kannel to SMSC. Also there is no ascii configuration in SMSC just GSM alphabet. Strange anyway here is the debug Can you send your configuration and the way you are sending the message so someone which has SMPP connection with a SMSC can reproduce this situation? BR, Jovan
Re: SMS with GSM character set
LEts forget about HTTP Client. When I call send-sms from .NET service, what is the procedure of encoding that suits for kannel? Regards Elton On Fri, May 8, 2009 at 8:19 AM, Elton Hoxha elt...@gmail.com wrote: Thanks Jyoti, I will give it a try. Falko, If I use UTF-8 in URL, it should be used with coding = 1, which cause that the content will be delivered in unreadable format for the mobile. Otherwise, If I use ISO-8859-1, i should add coding=2 which encodes it in 16-bit (the characters are normally delivered) but I reduce the bytes having only 70 characters. Regards elton On Fri, May 8, 2009 at 7:35 AM, Falko Ziemann fal...@gmail.com wrote: Elton, please read my last mail again. You must not encode the text in the sendsms URL in gsm! You must send the text to kannel in the encoding the http-client tells kannel which characterset it uses, so mostly UTF-8 or Iso-Latin Regards Falko Am 07.05.2009 um 16:18 schrieb Elton Hoxha: SMPP configuration is simple, I think everybody has it like this group=smsc smsc=smpp smsc-id=internal1 interface-version=34 host=10.x.x.x port=1600 system-id=test smsc-password=test system-type=test transceiver-mode=false address-range=7070 Can anyone please who is able to send these kind of characters (for example @), paste me the smpp configuration or the send-sms url that is used with the required parameters? Regards Elton On Thu, May 7, 2009 at 1:48 PM, Jovan Kostovski chomb...@gmail.comwrote: On Thu, May 7, 2009 at 1:26 PM, Elton Hoxha elt...@gmail.com wrote: I checked many many times, kannel is sending empty message when i type these special characters. I traced by ethereal the smpp block and there is no text forwarded by kannel to SMSC. Also there is no ascii configuration in SMSC just GSM alphabet. Strange anyway here is the debug Can you send your configuration and the way you are sending the message so someone which has SMPP connection with a SMSC can reproduce this situation? BR, Jovan
Re: SMS with GSM character set
Hi Falko,, Thanks for your comments, I tried what you said and I get 2009-05-08 02:09:50 [5317] [3] ERROR: Failed to convert string from UTF-8 to UTF-8, errno was 84 2009-05-08 02:09:50 [5317] [3] DEBUG: Found an invalid multibyte sequence at position 0 2009-05-08 02:09:50 [5317] [3] DEBUG: Status: 400 Answer: Charset or body misformed, rejected My URL: http://localhost:13014/cgi-bin/sendsms?username=test3password=test3from=ELTONto=355672509006text= £coding=0charset=UTF-8 But when I send: http://localhost:13014/cgi-bin/sendsms?username=test3password=test3from=ELTONto=355672509006text=$coding=0charset=UTF-8 The message is delivered properly. I think both £(pound) and $(dollar) are in the alphabet Any clue? Regards Elton On Fri, May 8, 2009 at 9:22 AM, Falko Ziemann fal...@gmail.com wrote: Unimportant...Your http-client (if you write some script in .NET it is also a http-client, just a very personal one) states the encoding while connecting and that is the one you must use. That has nothing to do with coding! See: you send UTF-8 string to kannel with coding=0. Than kannel takes the UTF-8 string an makes it GSM. But if you already send a GSM string, and your http-function tells kannel it is UTF-8 and kannel tries to make GSM out of it everything gets messed up. You do too much of the work that kannel wants to do. Just take the normal string and do an url_encode function (don't know how it is called in .NET) on it and pass it to kannel. Kannel and the compiler will do the job for you. Regards Falko Am 08.05.2009 um 08:58 schrieb Elton Hoxha: LEts forget about HTTP Client. When I call send-sms from .NET service, what is the procedure of encoding that suits for kannel? Regards Elton On Fri, May 8, 2009 at 8:19 AM, Elton Hoxha elt...@gmail.com wrote: Thanks Jyoti, I will give it a try. Falko, If I use UTF-8 in URL, it should be used with coding = 1, which cause that the content will be delivered in unreadable format for the mobile. Otherwise, If I use ISO-8859-1, i should add coding=2 which encodes it in 16-bit (the characters are normally delivered) but I reduce the bytes having only 70 characters. Regards elton On Fri, May 8, 2009 at 7:35 AM, Falko Ziemann fal...@gmail.com wrote: Elton, please read my last mail again. You must not encode the text in the sendsms URL in gsm! You must send the text to kannel in the encoding the http-client tells kannel which characterset it uses, so mostly UTF-8 or Iso-Latin Regards Falko Am 07.05.2009 um 16:18 schrieb Elton Hoxha: SMPP configuration is simple, I think everybody has it like this group=smsc smsc=smpp smsc-id=internal1 interface-version=34 host=10.x.x.x port=1600 system-id=test smsc-password=test system-type=test transceiver-mode=false address-range=7070 Can anyone please who is able to send these kind of characters (for example @), paste me the smpp configuration or the send-sms url that is used with the required parameters? Regards Elton On Thu, May 7, 2009 at 1:48 PM, Jovan Kostovski chomb...@gmail.comwrote: On Thu, May 7, 2009 at 1:26 PM, Elton Hoxha elt...@gmail.com wrote: I checked many many times, kannel is sending empty message when i type these special characters. I traced by ethereal the smpp block and there is no text forwarded by kannel to SMSC. Also there is no ascii configuration in SMSC just GSM alphabet. Strange anyway here is the debug Can you send your configuration and the way you are sending the message so someone which has SMPP connection with a SMSC can reproduce this situation? BR, Jovan
Re: SMS with GSM character set
I got this error 2009-05-08 02:49:48 [5641] [3] INFO: sendsms sender:test3:ELTON (10.1.21.146) to:355672509006 msg:é 2009-05-08 02:49:48 [5641] [3] DEBUG: Stored UUID 73f6686e-e184-4e3d-986b-32fb88d30878 2009-05-08 02:49:48 [5641] [3] WARNING: Incomplete UTF-8 char discovered, skipped. 2 2009-05-08 02:49:48 [5641] [3] WARNING: Incomplete UTF-8 char discovered, skipped. 2 2009-05-08 02:49:48 [5641] [3] WARNING: Incomplete UTF-8 char discovered, skipped. 2 Then the character comes empty instead of %E9 (in send-sms url) which is é On Fri, May 8, 2009 at 10:00 AM, Falko Ziemann fal...@gmail.com wrote: Don't set the charset!!!You there define the output charset, not the input charset and charset UTF-8 with coding 0 is ... well ... The UTF-8 is NOT defined in the URL, your http-client/scipt/whatever defines it for itself in the HTTP-header. Put all that stuff away, just send this: http://localhost:13014/cgi-bin/sendsms?username=test3password=test3from=ELTONto=355672509006text= http://localhost:13014/cgi-bin/sendsms?username=test3password=test3from=ELTONto=355672509006text= %24%40coding=0 That should bring you a sms containing a $ (dollar) and a @ (at) Regards Falko Am 08.05.2009 um 09:43 schrieb Elton Hoxha: Hi Falko,, Thanks for your comments, I tried what you said and I get 2009-05-08 02:09:50 [5317] [3] ERROR: Failed to convert string from UTF-8 to UTF-8, errno was 84 2009-05-08 02:09:50 [5317] [3] DEBUG: Found an invalid multibyte sequence at position 0 2009-05-08 02:09:50 [5317] [3] DEBUG: Status: 400 Answer: Charset or body misformed, rejected My URL: http://localhost:13014/cgi-bin/sendsms?username=test3password=test3from=ELTONto=355672509006text= £coding=0charset=UTF-8 But when I send: http://localhost:13014/cgi-bin/sendsms?username=test3password=test3from=ELTONto=355672509006text=$coding=0charset=UTF-8 The message is delivered properly. I think both £(pound) and $(dollar) are in the alphabet Any clue? Regards Elton On Fri, May 8, 2009 at 9:22 AM, Falko Ziemann fal...@gmail.com wrote: Unimportant...Your http-client (if you write some script in .NET it is also a http-client, just a very personal one) states the encoding while connecting and that is the one you must use. That has nothing to do with coding! See: you send UTF-8 string to kannel with coding=0. Than kannel takes the UTF-8 string an makes it GSM. But if you already send a GSM string, and your http-function tells kannel it is UTF-8 and kannel tries to make GSM out of it everything gets messed up. You do too much of the work that kannel wants to do. Just take the normal string and do an url_encode function (don't know how it is called in .NET) on it and pass it to kannel. Kannel and the compiler will do the job for you. Regards Falko Am 08.05.2009 um 08:58 schrieb Elton Hoxha: LEts forget about HTTP Client. When I call send-sms from .NET service, what is the procedure of encoding that suits for kannel? Regards Elton On Fri, May 8, 2009 at 8:19 AM, Elton Hoxha elt...@gmail.com wrote: Thanks Jyoti, I will give it a try. Falko, If I use UTF-8 in URL, it should be used with coding = 1, which cause that the content will be delivered in unreadable format for the mobile. Otherwise, If I use ISO-8859-1, i should add coding=2 which encodes it in 16-bit (the characters are normally delivered) but I reduce the bytes having only 70 characters. Regards elton On Fri, May 8, 2009 at 7:35 AM, Falko Ziemann fal...@gmail.com wrote: Elton, please read my last mail again. You must not encode the text in the sendsms URL in gsm! You must send the text to kannel in the encoding the http-client tells kannel which characterset it uses, so mostly UTF-8 or Iso-Latin Regards Falko Am 07.05.2009 um 16:18 schrieb Elton Hoxha: SMPP configuration is simple, I think everybody has it like this group=smsc smsc=smpp smsc-id=internal1 interface-version=34 host=10.x.x.x port=1600 system-id=test smsc-password=test system-type=test transceiver-mode=false address-range=7070 Can anyone please who is able to send these kind of characters (for example @), paste me the smpp configuration or the send-sms url that is used with the required parameters? Regards Elton On Thu, May 7, 2009 at 1:48 PM, Jovan Kostovski chomb...@gmail.comwrote: On Thu, May 7, 2009 at 1:26 PM, Elton Hoxha elt...@gmail.com wrote: I checked many many times, kannel is sending empty message when i type these special characters. I traced by ethereal the smpp block and there is no text forwarded by kannel to SMSC. Also there is no ascii configuration in SMSC just GSM alphabet. Strange anyway here is the debug Can you send your configuration and the way you are sending the message so someone which has SMPP connection with a SMSC can reproduce this situation? BR, Jovan
Re: SMS with GSM character set
I tried this: http://10.1.21.137:13014/cgi-bin/sendsms?username=test3password=test3from=ELTONto=355672509006text=%C3%A9coding=0 character is transformed again in kannel Debug logs: 2009-05-08 03:50:23 [5641] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms from 10.1.21.146 2009-05-08 03:50:23 [5641] [3] INFO: sendsms used by test3 2009-05-08 03:50:23 [5641] [3] INFO: sendsms sender:test3:ELTON (10.1.21.146) to:355672509006 msg:é 2009-05-08 03:50:23 [5641] [3] DEBUG: Stored UUID 531b8b7e-526b-4605-b0bf-79f8faf91854 2009-05-08 03:50:23 [5641] [3] DEBUG: message length 2, sending 1 messages 2009-05-08 03:50:23 [5641] [3] DEBUG: Status: 202 Answer: Sent. 2009-05-08 03:50:23 [5641] [3] DEBUG: Delayed reply - wait for bearerbox 2009-05-08 03:50:23 [5632] [9] DEBUG: boxc_receiver: sms received 2009-05-08 03:50:23 [5632] [9] DEBUG: send_msg: sending msg to box: 10.1.21.137 2009-05-08 03:50:23 [5641] [0] DEBUG: Got ACK (0) of 531b8b7e-526b-4605-b0bf-79f8faf91854 2009-05-08 03:50:23 [5641] [0] DEBUG: HTTP: Resetting HTTPClient for `10.1.21.146'. 2009-05-08 03:50:23 [5632] [6] DEBUG: SMPP[internal2]: Sending PDU: 2009-05-08 03:50:23 [5632] [6] DEBUG: SMPP PDU 0x99d2650 dump: 2009-05-08 03:50:23 [5632] [6] DEBUG: type_name: submit_sm 2009-05-08 03:50:23 [5632] [6] DEBUG: command_id: 4 = 0x0004 2009-05-08 03:50:23 [5632] [6] DEBUG: command_status: 0 = 0x 2009-05-08 03:50:23 [5632] [6] DEBUG: sequence_number: 127 = 0x007f 2009-05-08 03:50:23 [5632] [6] DEBUG: service_type: NULL 2009-05-08 03:50:23 [5632] [6] DEBUG: source_addr_ton: 5 = 0x0005 2009-05-08 03:50:23 [5632] [6] DEBUG: source_addr_npi: 0 = 0x 2009-05-08 03:50:23 [5632] [6] DEBUG: source_addr: ELTON 2009-05-08 03:50:23 [5632] [6] DEBUG: dest_addr_ton: 2 = 0x0002 2009-05-08 03:50:23 [5632] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2009-05-08 03:50:23 [5632] [6] DEBUG: destination_addr: 355672509006 2009-05-08 03:50:23 [5632] [6] DEBUG: esm_class: 3 = 0x0003 2009-05-08 03:50:23 [5632] [6] DEBUG: protocol_id: 0 = 0x 2009-05-08 03:50:23 [5632] [6] DEBUG: priority_flag: 0 = 0x 2009-05-08 03:50:23 [5632] [6] DEBUG: schedule_delivery_time: NULL 2009-05-08 03:50:23 [5632] [6] DEBUG: validity_period: NULL 2009-05-08 03:50:23 [5632] [6] DEBUG: registered_delivery: 0 = 0x 2009-05-08 03:50:23 [5632] [6] DEBUG: replace_if_present_flag: 0 = 0x 2009-05-08 03:50:23 [5632] [6] DEBUG: data_coding: 0 = 0x 2009-05-08 03:50:23 [5632] [6] DEBUG: sm_default_msg_id: 0 = 0x 2009-05-08 03:50:23 [5632] [6] DEBUG: sm_length: 1 = 0x0001 2009-05-08 03:50:23 [5632] [6] DEBUG: short_message: 2009-05-08 03:50:23 [5632] [6] DEBUG:Octet string at 0x99d2fd0: 2009-05-08 03:50:23 [5632] [6] DEBUG: len: 1 2009-05-08 03:50:23 [5632] [6] DEBUG: size: 3 2009-05-08 03:50:23 [5632] [6] DEBUG: immutable: 0 2009-05-08 03:50:23 [5632] [6] DEBUG: data: 05. 2009-05-08 03:50:23 [5632] [6] DEBUG:Octet string dump ends. On Fri, May 8, 2009 at 11:17 AM, Falko Ziemann fal...@gmail.com wrote: No?! é is %C3%A9 in UTF-8. é is %E9 in RAW encoding. http://kellyjones.netfirms.com/webtools/ascii_utf8_table.shtml Regards Falko Am 08.05.2009 um 10:49 schrieb Elton Hoxha: I got this error 2009-05-08 02:49:48 [5641] [3] INFO: sendsms sender:test3:ELTON (10.1.21.146) to:355672509006 msg:é 2009-05-08 02:49:48 [5641] [3] DEBUG: Stored UUID 73f6686e-e184-4e3d-986b-32fb88d30878 2009-05-08 02:49:48 [5641] [3] WARNING: Incomplete UTF-8 char discovered, skipped. 2 2009-05-08 02:49:48 [5641] [3] WARNING: Incomplete UTF-8 char discovered, skipped. 2 2009-05-08 02:49:48 [5641] [3] WARNING: Incomplete UTF-8 char discovered, skipped. 2 Then the character comes empty instead of %E9 (in send-sms url) which is é On Fri, May 8, 2009 at 10:00 AM, Falko Ziemann fal...@gmail.com wrote: Don't set the charset!!!You there define the output charset, not the input charset and charset UTF-8 with coding 0 is ... well ... The UTF-8 is NOT defined in the URL, your http-client/scipt/whatever defines it for itself in the HTTP-header. Put all that stuff away, just send this: http://localhost:13014/cgi-bin/sendsms?username=test3password=test3from=ELTONto=355672509006text= http://localhost:13014/cgi-bin/sendsms?username=test3password=test3from=ELTONto=355672509006text= %24%40coding=0 That should bring you a sms containing a $ (dollar) and a @ (at) Regards Falko Am 08.05.2009 um 09:43 schrieb Elton Hoxha: Hi Falko,, Thanks for your comments, I tried what you said and I get 2009-05-08 02:09:50 [5317] [3] ERROR: Failed to convert string from UTF-8 to UTF-8, errno was 84 2009-05-08 02:09:50 [5317] [3] DEBUG: Found an invalid multibyte sequence at position 0 2009-05-08 02:09:50 [5317] [3] DEBUG: Status: 400 Answer: Charset or body misformed, rejected My URL: http://localhost:13014/cgi
Re: SMS with GSM character set
Hi Jovan, All my tests included GSM 7-bit characters like é or è, I`m not interested in ISO-8859-1. Unfortunately all my efforts are failing...despite your help.. Elton On Fri, May 8, 2009 at 1:14 PM, Jovan Kostovski chomb...@gmail.com wrote: On Fri, May 8, 2009 at 1:12 PM, Jovan Kostovski chomb...@gmail.com wrote: On Fri, May 8, 2009 at 12:32 PM, Elton Hoxha elt...@gmail.com wrote: I tried this: http://10.1.21.137:13014/cgi-bin/sendsms?username=test3password=test3from=ELTONto=355672509006text=%C3%A9coding=0 character is transformed again in kannel The characters you are trying to send are not defined in GSM 03.38 7bit alphabet. The characters that you are sending are from ISO 8859-1 which means you have to use 8 bit coding coding=1. That's why you don't get the original message on your ME. Try sending message with some characters from the GSM 7 alphabet i.e message text =@è€ http://10.1.21.137:13014/cgi-bin/sendsms?username=test3password=test3from=ELTONto=355672509006text=%00%040%1B%65coding=0 I made a mistake in the url for, here is the right one. Sorry http://10.1.21.137:13014/cgi-bin/sendsms?username=test3password=test3from=ELTONto=355672509006text=%00%04%1B%65coding=0 BR, Jovan
Re: SMS with GSM character set
Hi Falko, We are SMSC provider at the same time :) And we use GSM charset. As I mentioned in another thread, sending these type of characters using 7-bit works from other smpp gateways, but from Kannel fails. Elton On Thu, May 7, 2009 at 9:52 AM, Falko Ziemann fal...@gmail.com wrote: The deutschland effect.Many operator don't use the original GSM charset, but the so called Mannesmann charset (first used by Mannesmann D2). Due to this most operator ignore the DCS. Ask your provider, if they can activate the original GSM charset for you. Regards Falko Am 06.05.2009 um 18:27 schrieb Latitude Berlin: Both dint work for me also:( ... coding=0alt-dcs=1 ... coding=0alt-dcs=0 - Latitude On Wed, May 6, 2009 at 6:20 PM, Elton Hoxha elt...@gmail.com wrote: in send-sms url as a parameter On Wed, May 6, 2009 at 6:18 PM, Latitude Berlin latitude.de@ googlemail.com wrote: Under which group alt-dcs is to be defined? - Latitude On Wed, May 6, 2009 at 6:17 PM, Elton Hoxha elt...@gmail.com wrote: Hi, I face the same problem: - With alt-dcs = 0 I get the following 2009-05-05 22:22:33 [5168] [3] INFO: sendsms sender:test2:1517 (10.1.21.146) to:35567200 msg: 2009-05-05 22:22:33 [5157] [7] DEBUG: short_message: The content is %00, but kannel converts it to empty space. - With alt-dcs=1; 2009-05-05 22:23:48 [5168] [3] INFO: sendsms sender:test2:1517 (10.1.21.146) to:35567200 msg: 2009-05-05 22:23:48 [5157] [7] DEBUG: short_message: ? Regards Elton On Wed, May 6, 2009 at 5:49 PM, Jovan Kostovski chomb...@gmail.comwrote: On Wed, May 6, 2009 at 5:32 PM, Latitude Berlin latitude...@googlemail.com wrote: Hi, I am sending some text with some german characters like: test chars ÄÖÜ äöü and I dont get the original content on my device. If I use UTF-8, then it works fine. But I wanna use GSM charset for this since Ä, ä, Ö, ö, Ü, ü are are of GMS charset. Kindly advise. Try the following test: set alt-dcs=0 send %00 as message text. Yyou should get the @ character if GSM 7 bit encoding is used If you don't get that character set alt-dcs=1 and repeat the test. If you get the @ character, by sendind %00 as message test, then try the umlauts, you should get them on your ME. HTH, Jovan
Re: SMS with GSM character set
That`s true, But actually Im not saying that in the kannel logs message characters appears different and in the mobile screen in different way. What appears in the logs (like or ?, instead of é ) appears in the mobile as well. Elton On Thu, May 7, 2009 at 10:52 AM, Falko Ziemann fal...@gmail.com wrote: OK, sorry, I have to admit that I didn't read the whole messages. I just saw that someone from germany has a problem with DCS, which nearly everyone in germany has faced at least once... A hint, that I can give to you, is that some ssh clients can also change the output of the logfile. When I look at the kannel-log with special characters with a putty from a windows the log shows other characters than when I look at it with OpenSSH from my MacOS. It can even change with the same client when you look at it with less or vim. So better only trust what you read in the sms, not in the logfile. Regards Falko Am 07.05.2009 um 10:41 schrieb Elton Hoxha: Hi Falko, We are SMSC provider at the same time :) And we use GSM charset. As I mentioned in another thread, sending these type of characters using 7-bit works from other smpp gateways, but from Kannel fails. Elton On Thu, May 7, 2009 at 9:52 AM, Falko Ziemann fal...@gmail.com wrote: The deutschland effect.Many operator don't use the original GSM charset, but the so called Mannesmann charset (first used by Mannesmann D2). Due to this most operator ignore the DCS. Ask your provider, if they can activate the original GSM charset for you. Regards Falko Am 06.05.2009 um 18:27 schrieb Latitude Berlin: Both dint work for me also:( ... coding=0alt-dcs=1 ... coding=0alt-dcs=0 - Latitude On Wed, May 6, 2009 at 6:20 PM, Elton Hoxha elt...@gmail.com wrote: in send-sms url as a parameter On Wed, May 6, 2009 at 6:18 PM, Latitude Berlin latitude.de@ googlemail.com wrote: Under which group alt-dcs is to be defined? - Latitude On Wed, May 6, 2009 at 6:17 PM, Elton Hoxha elt...@gmail.com wrote: Hi, I face the same problem: - With alt-dcs = 0 I get the following 2009-05-05 22:22:33 [5168] [3] INFO: sendsms sender:test2:1517 (10.1.21.146) to:35567200 msg: 2009-05-05 22:22:33 [5157] [7] DEBUG: short_message: The content is %00, but kannel converts it to empty space. - With alt-dcs=1; 2009-05-05 22:23:48 [5168] [3] INFO: sendsms sender:test2:1517 (10.1.21.146) to:35567200 msg: 2009-05-05 22:23:48 [5157] [7] DEBUG: short_message: ? Regards Elton On Wed, May 6, 2009 at 5:49 PM, Jovan Kostovski chomb...@gmail.comwrote: On Wed, May 6, 2009 at 5:32 PM, Latitude Berlin latitude...@googlemail.com wrote: Hi, I am sending some text with some german characters like: test chars ÄÖÜ äöü and I dont get the original content on my device. If I use UTF-8, then it works fine. But I wanna use GSM charset for this since Ä, ä, Ö, ö, Ü, ü are are of GMS charset. Kindly advise. Try the following test: set alt-dcs=0 send %00 as message text. Yyou should get the @ character if GSM 7 bit encoding is used If you don't get that character set alt-dcs=1 and repeat the test. If you get the @ character, by sendind %00 as message test, then try the umlauts, you should get them on your ME. HTH, Jovan
Re: SMS with GSM character set
Is mclass related with GSM alphabet? I think it is used for flash SMS or other options. I didnt use it in fact. Should I? On Thu, May 7, 2009 at 10:59 AM, Falko Ziemann fal...@gmail.com wrote: I don't think so... uh, by the way, I forgot to ask for another classic fault: did you set the mclass switch in the sendsms url as parameter? Regards Falko Am 07.05.2009 um 10:51 schrieb Latitude Berlin: Are we saying that this is a Kannel bug? - Latitude On Thu, May 7, 2009 at 10:41 AM, Elton Hoxha elt...@gmail.com wrote: Hi Falko, We are SMSC provider at the same time :) And we use GSM charset. As I mentioned in another thread, sending these type of characters using 7-bit works from other smpp gateways, but from Kannel fails. Elton On Thu, May 7, 2009 at 9:52 AM, Falko Ziemann fal...@gmail.com wrote: The deutschland effect.Many operator don't use the original GSM charset, but the so called Mannesmann charset (first used by Mannesmann D2). Due to this most operator ignore the DCS. Ask your provider, if they can activate the original GSM charset for you. Regards Falko Am 06.05.2009 um 18:27 schrieb Latitude Berlin: Both dint work for me also:( ... coding=0alt-dcs=1 ... coding=0alt-dcs=0 - Latitude On Wed, May 6, 2009 at 6:20 PM, Elton Hoxha elt...@gmail.com wrote: in send-sms url as a parameter On Wed, May 6, 2009 at 6:18 PM, Latitude Berlin latitude.de@ googlemail.com wrote: Under which group alt-dcs is to be defined? - Latitude On Wed, May 6, 2009 at 6:17 PM, Elton Hoxha elt...@gmail.com wrote: Hi, I face the same problem: - With alt-dcs = 0 I get the following 2009-05-05 22:22:33 [5168] [3] INFO: sendsms sender:test2:1517 (10.1.21.146) to:35567200 msg: 2009-05-05 22:22:33 [5157] [7] DEBUG: short_message: The content is %00, but kannel converts it to empty space. - With alt-dcs=1; 2009-05-05 22:23:48 [5168] [3] INFO: sendsms sender:test2:1517 (10.1.21.146) to:35567200 msg: 2009-05-05 22:23:48 [5157] [7] DEBUG: short_message: ? Regards Elton On Wed, May 6, 2009 at 5:49 PM, Jovan Kostovski chomb...@gmail.comwrote: On Wed, May 6, 2009 at 5:32 PM, Latitude Berlin latitude...@googlemail.com wrote: Hi, I am sending some text with some german characters like: test chars ÄÖÜ äöü and I dont get the original content on my device. If I use UTF-8, then it works fine. But I wanna use GSM charset for this since Ä, ä, Ö, ö, Ü, ü are are of GMS charset. Kindly advise. Try the following test: set alt-dcs=0 send %00 as message text. Yyou should get the @ character if GSM 7 bit encoding is used If you don't get that character set alt-dcs=1 and repeat the test. If you get the @ character, by sendind %00 as message test, then try the umlauts, you should get them on your ME. HTH, Jovan
Re: SMS with GSM character set
Can you tell me the parameters you are using in send-sms url as you are succeding in sending these characters? Are also other parameters that should be configured in SMSC group? Attached are the debuf for two submit SM. First one using alt-dcs=1, and second one alt-dcs = 0 Thanks Elton On Thu, May 7, 2009 at 11:31 AM, Falko Ziemann fal...@gmail.com wrote: Still don't think so. As I run some services in german, I have a lot of ÄÖÜäöüß's passing my kannel without any problem in GSM charset without any problem. So I really think it has something to do with the configuration. Maybe you can post a full debug of the smpp package, kannel is sending. Regards Falko Am 07.05.2009 um 11:24 schrieb Elton Hoxha: So, its a bug? :) On Thu, May 7, 2009 at 11:17 AM, Falko Ziemann fal...@gmail.com wrote: No, but mclass forces special DCS values. So when the mclass switch is set, the alt-dcs parameter is ignored. So, no help for you problem, sorry. Regards Falko Am 07.05.2009 um 11:01 schrieb Elton Hoxha: Is mclass related with GSM alphabet? I think it is used for flash SMS or other options. I didnt use it in fact. Should I? On Thu, May 7, 2009 at 10:59 AM, Falko Ziemann fal...@gmail.com wrote: I don't think so... uh, by the way, I forgot to ask for another classic fault: did you set the mclass switch in the sendsms url as parameter? Regards Falko Am 07.05.2009 um 10:51 schrieb Latitude Berlin: Are we saying that this is a Kannel bug? - Latitude On Thu, May 7, 2009 at 10:41 AM, Elton Hoxha elt...@gmail.com wrote: Hi Falko, We are SMSC provider at the same time :) And we use GSM charset. As I mentioned in another thread, sending these type of characters using 7-bit works from other smpp gateways, but from Kannel fails. Elton On Thu, May 7, 2009 at 9:52 AM, Falko Ziemann fal...@gmail.com wrote: The deutschland effect.Many operator don't use the original GSM charset, but the so called Mannesmann charset (first used by Mannesmann D2). Due to this most operator ignore the DCS. Ask your provider, if they can activate the original GSM charset for you. Regards Falko Am 06.05.2009 um 18:27 schrieb Latitude Berlin: Both dint work for me also:( ... coding=0alt-dcs=1 ... coding=0alt-dcs=0 - Latitude On Wed, May 6, 2009 at 6:20 PM, Elton Hoxha elt...@gmail.com wrote: in send-sms url as a parameter On Wed, May 6, 2009 at 6:18 PM, Latitude Berlin latitude.de@ googlemail.com wrote: Under which group alt-dcs is to be defined? - Latitude On Wed, May 6, 2009 at 6:17 PM, Elton Hoxha elt...@gmail.comwrote: Hi, I face the same problem: - With alt-dcs = 0 I get the following 2009-05-05 22:22:33 [5168] [3] INFO: sendsms sender:test2:1517 (10.1.21.146) to:35567200 msg: 2009-05-05 22:22:33 [5157] [7] DEBUG: short_message: The content is %00, but kannel converts it to empty space. - With alt-dcs=1; 2009-05-05 22:23:48 [5168] [3] INFO: sendsms sender:test2:1517 (10.1.21.146) to:35567200 msg: 2009-05-05 22:23:48 [5157] [7] DEBUG: short_message: ? Regards Elton On Wed, May 6, 2009 at 5:49 PM, Jovan Kostovski chomb...@gmail.com wrote: On Wed, May 6, 2009 at 5:32 PM, Latitude Berlin latitude...@googlemail.com wrote: Hi, I am sending some text with some german characters like: test chars ÄÖÜ äöü and I dont get the original content on my device. If I use UTF-8, then it works fine. But I wanna use GSM charset for this since Ä, ä, Ö, ö, Ü, ü are are of GMS charset. Kindly advise. Try the following test: set alt-dcs=0 send %00 as message text. Yyou should get the @ character if GSM 7 bit encoding is used If you don't get that character set alt-dcs=1 and repeat the test. If you get the @ character, by sendind %00 as message test, then try the umlauts, you should get them on your ME. HTH, Jovan 2009-05-06 08:27:22 [5168] [2] DEBUG: HTTP: Creating HTTPClient for `10.1.21.146'. 2009-05-06 08:27:22 [5168] [2] DEBUG: HTTP: Created HTTPClient area 0x8d3ed50. 2009-05-06 08:27:22 [5168] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms from 10.1.21.146 2009-05-06 08:27:22 [5168] [3] INFO: sendsms used by test2 2009-05-06 08:27:22 [5168] [3] INFO: sendsms sender:test2:1517 (10.1.21.146) to:35567240 msg:é 2009-05-06 08:27:22 [5168] [3] DEBUG: Stored UUID 9078ca53-4f2c-4833-8870-e6160f8cb36e 2009-05-06 08:27:22 [5168] [3] WARNING: Incomplete UTF-8 char discovered, skipped. 2 2009-05-06 08:27:22 [5168] [3] WARNING: Incomplete UTF-8 char discovered, skipped. 2 2009-05-06 08:27:22 [5168] [3] WARNING: Incomplete UTF-8 char discovered, skipped. 2 2009-05-06 08:27:22 [5168] [3] DEBUG: message length 1, sending 1 messages 2009-05-06 08:27:22 [5168] [3] DEBUG: Status: 202 Answer: Sent. 2009-05-06 08:27:22 [5168] [3] DEBUG: Delayed reply - wait for bearerbox 2009-05-06 08:27:22 [5157] [10] DEBUG: boxc_receiver: sms received 2009-05-06 08:27:22 [5157] [10] DEBUG: send_msg: sending msg to box
Re: SMS with GSM character set
Sorry, in my previous debug I encoded the é character using %E9. Now the encoded value is %05. As you can see in the attached logs, kannel gets empty sms. Regards Elton On Thu, May 7, 2009 at 11:40 AM, Elton Hoxha elt...@gmail.com wrote: Can you tell me the parameters you are using in send-sms url as you are succeding in sending these characters? Are also other parameters that should be configured in SMSC group? Attached are the debuf for two submit SM. First one using alt-dcs=1, and second one alt-dcs = 0 Thanks Elton On Thu, May 7, 2009 at 11:31 AM, Falko Ziemann fal...@gmail.com wrote: Still don't think so. As I run some services in german, I have a lot of ÄÖÜäöüß's passing my kannel without any problem in GSM charset without any problem. So I really think it has something to do with the configuration. Maybe you can post a full debug of the smpp package, kannel is sending. Regards Falko Am 07.05.2009 um 11:24 schrieb Elton Hoxha: So, its a bug? :) On Thu, May 7, 2009 at 11:17 AM, Falko Ziemann fal...@gmail.com wrote: No, but mclass forces special DCS values. So when the mclass switch is set, the alt-dcs parameter is ignored. So, no help for you problem, sorry. Regards Falko Am 07.05.2009 um 11:01 schrieb Elton Hoxha: Is mclass related with GSM alphabet? I think it is used for flash SMS or other options. I didnt use it in fact. Should I? On Thu, May 7, 2009 at 10:59 AM, Falko Ziemann fal...@gmail.com wrote: I don't think so... uh, by the way, I forgot to ask for another classic fault: did you set the mclass switch in the sendsms url as parameter? Regards Falko Am 07.05.2009 um 10:51 schrieb Latitude Berlin: Are we saying that this is a Kannel bug? - Latitude On Thu, May 7, 2009 at 10:41 AM, Elton Hoxha elt...@gmail.com wrote: Hi Falko, We are SMSC provider at the same time :) And we use GSM charset. As I mentioned in another thread, sending these type of characters using 7-bit works from other smpp gateways, but from Kannel fails. Elton On Thu, May 7, 2009 at 9:52 AM, Falko Ziemann fal...@gmail.comwrote: The deutschland effect.Many operator don't use the original GSM charset, but the so called Mannesmann charset (first used by Mannesmann D2). Due to this most operator ignore the DCS. Ask your provider, if they can activate the original GSM charset for you. Regards Falko Am 06.05.2009 um 18:27 schrieb Latitude Berlin: Both dint work for me also:( ... coding=0alt-dcs=1 ... coding=0alt-dcs=0 - Latitude On Wed, May 6, 2009 at 6:20 PM, Elton Hoxha elt...@gmail.com wrote: in send-sms url as a parameter On Wed, May 6, 2009 at 6:18 PM, Latitude Berlin latitude.de@ googlemail.com wrote: Under which group alt-dcs is to be defined? - Latitude On Wed, May 6, 2009 at 6:17 PM, Elton Hoxha elt...@gmail.comwrote: Hi, I face the same problem: - With alt-dcs = 0 I get the following 2009-05-05 22:22:33 [5168] [3] INFO: sendsms sender:test2:1517 (10.1.21.146) to:35567200 msg: 2009-05-05 22:22:33 [5157] [7] DEBUG: short_message: The content is %00, but kannel converts it to empty space. - With alt-dcs=1; 2009-05-05 22:23:48 [5168] [3] INFO: sendsms sender:test2:1517 (10.1.21.146) to:35567200 msg: 2009-05-05 22:23:48 [5157] [7] DEBUG: short_message: ? Regards Elton On Wed, May 6, 2009 at 5:49 PM, Jovan Kostovski chomb...@gmail.com wrote: On Wed, May 6, 2009 at 5:32 PM, Latitude Berlin latitude...@googlemail.com wrote: Hi, I am sending some text with some german characters like: test chars ÄÖÜ äöü and I dont get the original content on my device. If I use UTF-8, then it works fine. But I wanna use GSM charset for this since Ä, ä, Ö, ö, Ü, ü are are of GMS charset. Kindly advise. Try the following test: set alt-dcs=0 send %00 as message text. Yyou should get the @ character if GSM 7 bit encoding is used If you don't get that character set alt-dcs=1 and repeat the test. If you get the @ character, by sendind %00 as message test, then try the umlauts, you should get them on your ME. HTH, Jovan 2009-05-06 08:40:38 [5168] [2] DEBUG: HTTP: Creating HTTPClient for `10.1.21.146'. 2009-05-06 08:40:38 [5168] [2] DEBUG: HTTP: Created HTTPClient area 0x8d3a3b8. 2009-05-06 08:40:38 [5168] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms from 10.1.21.146 2009-05-06 08:40:38 [5168] [3] INFO: sendsms used by test2 2009-05-06 08:40:38 [5168] [3] INFO: sendsms sender:test2:1517 (10.1.21.146) to:35567240 msg: 2009-05-06 08:40:38 [5168] [3] DEBUG: Stored UUID 40d9bbcd-ee55-46c4-b005-bc0568738211 2009-05-06 08:40:38 [5168] [3] DEBUG: message length 1, sending 1 messages 2009-05-06 08:40:38 [5168] [3] DEBUG: Status: 202 Answer: Sent. 2009-05-06 08:40:38 [5168] [3] DEBUG: Delayed reply - wait for bearerbox 2009-05-06 08:40:38 [5157] [10] DEBUG: boxc_receiver: sms received 2009-05-06 08:40:38 [5157] [10] DEBUG: send_msg: sending msg to box: 10.1.21.137
Re: SMS with GSM character set
SMPP configuration is simple, I think everybody has it like this group=smsc smsc=smpp smsc-id=internal1 interface-version=34 host=10.x.x.x port=1600 system-id=test smsc-password=test system-type=test transceiver-mode=false address-range=7070 Can anyone please who is able to send these kind of characters (for example @), paste me the smpp configuration or the send-sms url that is used with the required parameters? Regards Elton On Thu, May 7, 2009 at 1:48 PM, Jovan Kostovski chomb...@gmail.com wrote: On Thu, May 7, 2009 at 1:26 PM, Elton Hoxha elt...@gmail.com wrote: I checked many many times, kannel is sending empty message when i type these special characters. I traced by ethereal the smpp block and there is no text forwarded by kannel to SMSC. Also there is no ascii configuration in SMSC just GSM alphabet. Strange anyway here is the debug Can you send your configuration and the way you are sending the message so someone which has SMPP connection with a SMSC can reproduce this situation? BR, Jovan
Re: kannel and greek characters
Another related issue; How is possible that while connecting to the same SMSC via SMPP from another SMPP gateway (test purpose) I`m able to send 7-bit alphabet characters according to the specification here http://www.cardboardfish.com/support/bin/view/Main/GSMEncoding I dont set any coding schema and the accents characters are sent properly. Is it Kannel issue then to involve 8-bit in order to support this? Regards Elton 2009/5/5 Nikos Balkanas nbalka...@gmail.com Hi Elton, If you consult any ASCII table, you can verify for yourself that any such characters are above '~', which is 126. The only way to transmit such characters within 7 bits, is to throw away some other character and take its place. I presume that the aforementioned mobiles, agree on some special non-ASCII encoding and can use that. I would imagine that: 1) You need to have same regional settings in each mobile, and possible same brand? 2) You need to have the same extended encoding activated. Which means you are missing on regular characters. I wish I could be more specific, but I don't have a mobile. Maybe a few other guys from the list can help out. BR, Nikos - Original Message - From: elthox elt...@gmail.com To: users@kannel.org Sent: Tuesday, May 05, 2009 9:46 AM Subject: Re: kannel and greek characters Hi Nikos, You mentioned that umlauts and accents are extended characters that are out of the range of 7-bit alphabet. How come, when sending mobile to mobile SMS, with a reduced character set (7-bit) the message is delivered properly writing Γ©, Γ± etc. But while trying it from SMPP channel doesnt work, for example giving the encoded hexa value %05 for Γ©, it will translate it as ?. Do you have anyidea? Regards Elton Nikos Balkanas wrote: Hi Nick, Almost, not quite. GSM encoding is not doing any recoding at the character level, just at the byte level. I.e. all ASCII characters below 128 can be represented as 7 bits and these include all the major Latin-1 or ISO-8859-1. There are some extended characters in ISO-8859-1 (umlauts, accents etc) that if you include even a single one it will fall back to 8bit. So sending capitalized english chars as Greek to save SMS space, might work as long as you stick to Greeklish. BR, Nikos - Original Message - From: Nick nic...@gmx.net To: users@kannel.org Sent: Friday, March 27, 2009 2:38 PM Subject: Re: kannel and greek characters Thanks Nikos When i set the coding to 1 or to 2 , i cant send 160 char messages anymore There must be a way to encode the message to GSM encoding , and send 160 char messages with capital greek characters From this URL http://www.cardboardfish.com/support/bin/view/Main/GSMEncoding According to GSM specification, a standard SMS message can contain up to 140 bytes of data (payload). Standard latin (ISO-8859-1) character encoding represents a single character using 1 byte, which is 8 bits. Therefore, the maximum number of latin 1 characters that could be included in an sms is 140. GSM encoding represents characters using 7 bits instead of 8. This therefore provides a maximum of 160 characters per SMS. (140 * 8 bits) / 7 bits = 160 This effectively halves the number of characters that the GSM character set can support, compared to ISO-8859-1. In order to include common characters that are usually represented using the 8th bit, these characters as well as other symbol characters must be re-mapped to a combination of lower bits. These re-mapped characters are often referred to as special characters. This re-mapping, in combination with packing 7-bit characters into 8-bit bytes is called GSM Encoding. Hi Nick, SMS can hold 160 B of 7bit chars or 140 B of 8bit chars (+/- some UDF headers). Half of that for Unicode. ASCII characters are 7bit, Greek are 8bit. If you choose to send them as Unicode it is 70 B. In your URL coding=0 corresponds to 7bit coding. Wrong one for Greek. Try with coding 2 (Unicode) or coding 1 (8bit). BR, Nikos - Original Message - From: Nick nic...@gmx.net To: users@kannel.org Sent: Thursday, March 26, 2009 9:14 PM Subject: kannel and greek characters Hello all I try to send greek sms 160 characters long with kannel with no luck I can send 70 characters Unicode messages successfully, but cant send 160 char long messages I have installed kannel on 2 linux servers, one with centos 4.6 and one with centos 5.1 I have installed the latest version 1.4.3 and the latest cvs version I have compiled both version with and without the greek patch bellow http://www.kannel.org/pipermail/users/2006-July/40.html I have read and followed all post with keyword greek in both users and developers mailing list No luck According the posts in the mailling list, when i send http://192.168.0.1:13131/cgi-bin/sendsms?user=pass=to=30697700coding=0text=KA%14HMEPA (%14 = greek letter Ξ›) it suppose to
Re: SMS with GSM character set
Hi, I face the same problem: - With alt-dcs = 0 I get the following 2009-05-05 22:22:33 [5168] [3] INFO: sendsms sender:test2:1517 (10.1.21.146) to:35567200 msg: 2009-05-05 22:22:33 [5157] [7] DEBUG: short_message: The content is %00, but kannel converts it to empty space. - With alt-dcs=1; 2009-05-05 22:23:48 [5168] [3] INFO: sendsms sender:test2:1517 (10.1.21.146) to:35567200 msg: 2009-05-05 22:23:48 [5157] [7] DEBUG: short_message: ? Regards Elton On Wed, May 6, 2009 at 5:49 PM, Jovan Kostovski chomb...@gmail.com wrote: On Wed, May 6, 2009 at 5:32 PM, Latitude Berlin latitude...@googlemail.com wrote: Hi, I am sending some text with some german characters like: test chars ÄÖÜ äöü and I dont get the original content on my device. If I use UTF-8, then it works fine. But I wanna use GSM charset for this since Ä, ä, Ö, ö, Ü, ü are are of GMS charset. Kindly advise. Try the following test: set alt-dcs=0 send %00 as message text. Yyou should get the @ character if GSM 7 bit encoding is used If you don't get that character set alt-dcs=1 and repeat the test. If you get the @ character, by sendind %00 as message test, then try the umlauts, you should get them on your ME. HTH, Jovan
Re: SMS with GSM character set
in send-sms url as a parameter On Wed, May 6, 2009 at 6:18 PM, Latitude Berlin latitude...@googlemail.comwrote: Under which group alt-dcs is to be defined? - Latitude On Wed, May 6, 2009 at 6:17 PM, Elton Hoxha elt...@gmail.com wrote: Hi, I face the same problem: - With alt-dcs = 0 I get the following 2009-05-05 22:22:33 [5168] [3] INFO: sendsms sender:test2:1517 (10.1.21.146) to:35567200 msg: 2009-05-05 22:22:33 [5157] [7] DEBUG: short_message: The content is %00, but kannel converts it to empty space. - With alt-dcs=1; 2009-05-05 22:23:48 [5168] [3] INFO: sendsms sender:test2:1517 (10.1.21.146) to:35567200 msg: 2009-05-05 22:23:48 [5157] [7] DEBUG: short_message: ? Regards Elton On Wed, May 6, 2009 at 5:49 PM, Jovan Kostovski chomb...@gmail.comwrote: On Wed, May 6, 2009 at 5:32 PM, Latitude Berlin latitude...@googlemail.com wrote: Hi, I am sending some text with some german characters like: test chars ÄÖÜ äöü and I dont get the original content on my device. If I use UTF-8, then it works fine. But I wanna use GSM charset for this since Ä, ä, Ö, ö, Ü, ü are are of GMS charset. Kindly advise. Try the following test: set alt-dcs=0 send %00 as message text. Yyou should get the @ character if GSM 7 bit encoding is used If you don't get that character set alt-dcs=1 and repeat the test. If you get the @ character, by sendind %00 as message test, then try the umlauts, you should get them on your ME. HTH, Jovan