Re: is there a parameter (escape code) in dlr-url to return smsc-admin-id?

[Alexander Malysh]

Hi,

as far as I see, no.

Regards,
Alexander Malysh
Am 10. Okt. 2023, 18:33 +0200 schrieb lbrezs...@gmx.co.uk :
> In kannel.conf config when defining dlr-url is there a parameter (escape 
> code) to return smsc-admin-id?
> Documented %i will return the smsc-id of the connection that received the 
> message. But if there are multiple binds per smsc defined by smsc-admin-id 
> for the same conncetion, is there a way to get more granular info?

Re: dlr_err

[Alexander Malysh]

Hi,

this is raw error code from SMPP TLV.

Regards,
Alexander Malysh
Am 1. Feb. 2023, 10:15 +0100 schrieb arunbm123 :
> hi
>
> I am getting [ META:meta] dlr_err=%30%00%00
> in access.log
>
> can any one enlighten whats this error
>
>
>
> - Thanks
>   Arun
>
>

Re: Mismatch between received message coding and smsbox forwarded message coding

[Alexander Malysh]

Hi,

access-log-format controls access log format and if it’s changed you may see in 
access log different flag positions which results in different values für 
message coding in URL.

Regards,
Alexander Malysh
Am 20. Okt. 2022, 08:58 +0200 schrieb Giulio Giovannini 
:
> Hello Alexander.
>
> Not sure what you mean. What config parameter controls the access log format 
> you are referring to? How do you think it is set and how should I set it?
> How would the log format have an impact on placeholder substitution?
>
> Best regards,
> Giulio
>
> > On Wed, 19 Oct 2022 at 17:18, Alexander Malysh  wrote:
> > > Hi,
> > >
> > > did you maybe changed access log format and mixed %c / %C there ?
> > >
> > > Regards,
> > > Alexander Malysh
> > > Am 3. Okt. 2022, 11:46 +0200 schrieb Giulio Giovannini 
> > > :
> > > > Hi all,
> > > >
> > > > I receive on kannel (svn-r5188M) an MO message with the below flags:
> > > >
> > > > 2022-10-03 08:14:15 Receive SMS [SMSC:] [SVC:] [ACT:] [BINF:] 
> > > > [FID:] [META:?smpp?] [from:] [to:xxx] [flags:-1:2:-1:0:-1] 
> > > > [msg:278:] [udh:0:]
> > > >
> > > > As you can see the second flag, the message coding %c, is set to 2 and 
> > > > the body of the MO is UCS2 encoded.
> > > >
> > > > I forward this message out using smsbox HTTP client capabilities 
> > > > configuring the below get-url:
> > > >
> > > > group = sms-service
> > > > keyword-regex = ".*"
> > > > name= 
> > > > catch-all = true
> > > > get-url = 
> > > > "http://.com/dispatcher?messageCoding=%c=%P=%p=%b=1;
> > > > accept-x-kannel-headers = true
> > > > max-messages = 0
> > > >
> > > > As you can see I am asking kannel to fill parameter messageCoding with 
> > > > content of placeholder %c
> > > >
> > > > If I check the smsbox access log I see that the messageCoding has been 
> > > > set to 0 when the message is forwarded to the HTTP endpoint defined in 
> > > > the get-url.
> > > >
> > > > 2022-10-03 08:14:15 SMS HTTP-request sender: request: 'xxx!' url: 
> > > > 'http:///.com/dispatcher?messageCoding=0==='
> > > >  reply: 200 '<< successful >>'
> > > >
> > > > Is this a known bug? Have I misconfigured anything?
> > > >
> > > > Using %C placeholder instead of %c would solve the issue I think. The 
> > > > 4th flag in the log trace above printed when the message is received is 
> > > > the %C placeholder and it is already at 0 (flags:-1:2:-1:0:-1).
> > > >
> > > > Thanks for your help,
> > > >
> > > > Giulio
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >

Re: Mismatch between received message coding and smsbox forwarded message coding

[Alexander Malysh]

Hi,

did you maybe changed access log format and mixed %c / %C there ?

Regards,
Alexander Malysh
Am 3. Okt. 2022, 11:46 +0200 schrieb Giulio Giovannini :
> Hi all,
>
> I receive on kannel (svn-r5188M) an MO message with the below flags:
>
> 2022-10-03 08:14:15 Receive SMS [SMSC:] [SVC:] [ACT:] [BINF:] 
> [FID:] [META:?smpp?] [from:] [to:xxx] [flags:-1:2:-1:0:-1] 
> [msg:278:] [udh:0:]
>
> As you can see the second flag, the message coding %c, is set to 2 and the 
> body of the MO is UCS2 encoded.
>
> I forward this message out using smsbox HTTP client capabilities configuring 
> the below get-url:
>
> group = sms-service
> keyword-regex = ".*"
> name= 
> catch-all = true
> get-url = 
> "http://.com/dispatcher?messageCoding=%c=%P=%p=%b=1;
> accept-x-kannel-headers = true
> max-messages = 0
>
> As you can see I am asking kannel to fill parameter messageCoding with 
> content of placeholder %c
>
> If I check the smsbox access log I see that the messageCoding has been set to 
> 0 when the message is forwarded to the HTTP endpoint defined in the get-url.
>
> 2022-10-03 08:14:15 SMS HTTP-request sender: request: 'xxx!' url: 
> 'http:///.com/dispatcher?messageCoding=0===' 
> reply: 200 '<< successful >>'
>
> Is this a known bug? Have I misconfigured anything?
>
> Using %C placeholder instead of %c would solve the issue I think. The 4th 
> flag in the log trace above printed when the message is received is the %C 
> placeholder and it is already at 0 (flags:-1:2:-1:0:-1).
>
> Thanks for your help,
>
> Giulio
>
>
>
>
>
>

Re: change modems / bearerbox no longer connects

[Alexander Malysh]

Hi,

you have to enable debug and see what’s going wrong. sometimes you need a init 
string in kennel config to get modem working.

Regards,
Alexander Malysh
Am 10. Juni 2022, 01:09 +0200 schrieb Stuart Kendrick 
:
> I have just replaced my old 3G modem (MultiTech) with a new 4G one (also 
> MultiTech) … and now bearerbox fails to negotiate speed … • What is this 
> telling me? […]2022-06-09T15:53:50.161623-07:00 vishnu bearerbox[5519]: 
> 2022-06-09 15:53:50 [5519] [0] INFO: AT2[/dev/modem]: configuration doesn't 
> show modemtype. will autodetect2022-06-09T15:53:50.161746-07:00 vishnu 
> bearerbox[5519]: 2022-06-09 15:53:50 [5519] [6] INFO: AT2[/dev/modem]: 
> opening device2022-06-09T15:53:50.161842-07:00 vishnu bearerbox[5519]: 
> 2022-06-09 15:53:50 [5519] [0] INFO: Adding interface 
> *2022-06-09T15:53:50.162154-07:00 vishnu bearerbox[5519]: 2022-06-09 15:53:50 
> [5519] [0] INFO: 
> 2022-06-09T15:53:50.162202-07:00 
> vishnu bearerbox[5519]: 2022-06-09 15:53:50 [5519] [0] INFO: Kannel bearerbox 
> II version 1.4.5 starting2022-06-09T15:53:50.162259-07:00 vishnu 
> bearerbox[5519]: 2022-06-09 15:53:50 [5519] [0] INFO: MAIN: Start-up done, 
> entering mainloop2022-06-09T15:53:50.162311-07:00 vishnu bearerbox[5519]: 
> 2022-06-09 15:53:50 [5519] [5] INFO: Client connected from 
> <127.0.0.1>2022-06-09T15:53:51.164367-07:00 vishnu bearerbox[5519]: 
> 2022-06-09 15:53:51 [5519] [6] INFO: AT2[/dev/modem]: speed set to 
> 1152002022-06-09T15:54:11.485394-07:00 vishnu bearerbox[5519]: 2022-06-09 
> 15:54:11 [5519] [6] INFO: AT2[/dev/modem]: Closing 
> device2022-06-09T15:54:11.485648-07:00 vishnu bearerbox[5519]: 2022-06-09 
> 15:54:11 [5519] [6] INFO: AT2[/dev/modem]: opening 
> device2022-06-09T15:54:12.487582-07:00 vishnu bearerbox[5519]: 2022-06-09 
> 15:54:12 [5519] [6] INFO: AT2[/dev/modem]: speed set to 
> 576002022-06-09T15:54:32.908334-07:00 vishnu bearerbox[5519]: 2022-06-09 
> 15:54:32 [5519] [6] INFO: AT2[/dev/modem]: Closing 
> device2022-06-09T15:54:32.909724-07:00 vishnu bearerbox[5519]: 2022-06-09 
> 15:54:32 [5519] [6] INFO: AT2[/dev/modem]: opening 
> device2022-06-09T15:54:33.910791-07:00 vishnu bearerbox[5519]: 2022-06-09 
> 15:54:33 [5519] [6] INFO: AT2[/dev/modem]: speed set to 
> 384002022-06-09T15:54:54.333076-07:00 vishnu bearerbox[5519]: 2022-06-09 
> 15:54:54 [5519] [6] INFO: AT2[/dev/modem]: Closing 
> device2022-06-09T15:54:54.348974-07:00 vishnu bearerbox[5519]: 2022-06-09 
> 15:54:54 [5519] [6] INFO: AT2[/dev/modem]: opening 
> device2022-06-09T15:54:55.335600-07:00 vishnu bearerbox[5519]: 2022-06-09 
> 15:54:55 [5519] [6] INFO: AT2[/dev/modem]: speed set to 
> 192002022-06-09T15:55:15.750830-07:00 vishnu bearerbox[5519]: 2022-06-09 
> 15:55:15 [5519] [6] INFO: AT2[/dev/modem]: Closing 
> device2022-06-09T15:55:15.751195-07:00 vishnu bearerbox[5519]: 2022-06-09 
> 15:55:15 [5519] [6] INFO: AT2[/dev/modem]: opening 
> device2022-06-09T15:55:16.753260-07:00 vishnu bearerbox[5519]: 2022-06-09 
> 15:55:16 [5519] [6] INFO: AT2[/dev/modem]: speed set to 
> 96002022-06-09T15:55:37.172905-07:00 vishnu bearerbox[5519]: 2022-06-09 
> 15:55:37 [5519] [6] INFO: AT2[/dev/modem]: Closing 
> device2022-06-09T15:55:37.174270-07:00 vishnu bearerbox[5519]: 2022-06-09 
> 15:55:37 [5519] [6] INFO: AT2[/dev/modem]: cannot detect 
> speed2022-06-09T15:55:37.174399-07:00 vishnu bearerbox[5519]: 2022-06-09 
> 15:55:37 [5519] [6] ERROR: AT2[/dev/modem]: Couldn't connect (retrying in 10 
> seconds). I can use minicom to query the modem and report information about 
> local service AT+GMI                                                          
>                 Telit                                                         
>                  OK                                                           
>                     AT+GMM                                                    
>                      ME910C1-NA AT+CSQ+CSQ:  29.6 AT#SERVINFO                 
>                                                    #SERVINFO: 
> 5035,-50,"AT","310260",1BE,2C34,256,0,-79 This suggests to me that 
> Linux can talk to the modem via /dev/modem, and that the modem is talking to 
> the service provider linux# ll /dev/modemlrwxrwxrwx 1 root root 7 Jun  9 
> 15:21 /dev/modem -> ttyUSB1linux# ll /dev/ttyUSB1crw-rw-rw- 1 root dialout 
> 188, 1 Jun  9 15:55 /dev/ttyUSB1linux# cat 
> /etc/udev/rules.d/10-modem.rulesKERNEL=="ttyUSB1", SYMLINK+="modem", 
> MODE="0666"linux# From /etc/kannel/kannel.conf# SMSC GSMgroup = smscsmsc = 
> atmodemtype = autodevice = /dev/modemvalidityperiod = 24max-error-count = 20 
> From /etc/kannel/modems.conf# If modemtype=auto, try everyone and defaults to 
> this onegroup = modemsid = genericname = "Generic Modem" Do I perhaps need to 
> define something other than ‘generic’ for a 4G Multitech? --sk Stuart 
> KendrickAllen Institute

Re: Is it possible to enforce service_type on SMPP connection?

[Alexander Malysh]

Hi,

Kannel uses binfo from message as service_type in submit_sm or configured 
service_type from SMSC group.
Therefore you just have to not set binfo filed in message and kannel will use 
configured service_type.

Regards,
Alexander Malysh
Am 1. Nov. 2021, 13:44 +0100 schrieb ale...@pavlyuts.ru:
> Dear friends,
>
> I need and advice from a Kannel guru and thanks in advance for any help:
>
> The problem: I was happy using Kannel too bridge two SMSC by SMPP 3.4, 
> running Kannel as ESME for both. Everything was fine before I need to connect 
> third one, and I got an issue:
>
>
> 1. One of my old connected SMSC set service_type to “CMT” and it is 
> hardcoded, mean I can’t change this behavior.
> 2. The new SMSC only accepts when service_type is set to default “” (empty 
> string) or hardcoded non-standard value “sms”. Any other value made it fail 
> to accept the message and not even answer to submit_sm.
>
>
> Therefore, I got one-way SMS path: it delivers from new to old, looks like 
> old don’t care about service type at all. But it fails from old to new as the 
> new sends service_type=”CMT”, which can’t be accepted by new one.
>
> Then, I found “service-type” configuration variable which seems to set exact 
> service type for SMPP connection. However, after some tests, I found it works 
> as below:
>
> 1. If routed message has service_type=”” (default) it be set per 
> “service-type” variable value. No matter is it comes from SMSbox or routed 
> from other SMPP.
> 2. If incoming service_type has any non-empty value, it will be left intact 
> and forwarded whatever I place to service-type variable. It neither set it to 
> default nor any other value, just left intact.
>
>
> So, my question is: is it possible to configure Kannel to enforce 
> service_type field on an outgoing SMTP message, overriding any other value?
>
> For my experience it looks like the answer is “no”, but may behavior also 
> controlled by some other options and I do not know how to set it right way.
>
> Also, it looks like I can use one more “leg” to forward it by http/kanel 
> connection (two kannel instances?). Then service_type be taken from variable 
> and it might work. But I prefer configure one instance if possible.
>
> Extra info: Kannel 1.4.5 on Centos 7, very trivial config with 3 SMSC and 
> only regex mask for each. Think, no use to attach it here.
>
> Thank you in advance for your attention and help!
>
> Sincerely,
>
> Alex

Re: RapidPro integration with Kannel

[Alexander Malysh]

Hello,

can you please explain a little bit more about this ?

Regards,
Alexander Malysh
Am 3. Sept. 2021, 01:45 +0200 schrieb Nedal Swehli :
> Hello All,
> Any one has experience integrating RapidPro with Kannel and is available to 
> support our project?
> Thanks!

Re: Submit Failed and DLRs Mask

[Alexander Malysh]

Hi,

please read user guide , there all the infos you need:

https://kannel.org/download/kannel-userguide-snapshot/userguide.html#delivery-reports


You need dlr mask 8 and 16 set -> 24

Regards,
Alexander Malysh
Am 25. Aug. 2021, 03:32 +0200 schrieb Gabriel Augusto Diaz Zapata 
:
> Hello People
>
> I'm having an issue with submt_sm_response failed and DLRS
>
> If I set DLR =0 sending and MT, and the submit_sm is rejected by SMSC, I 
> don't receive the NACK in kannel Table. I checked the logs and the error was 
> logged and detected, but I don't have the NACK (like an DLR) on the send_sms 
> table.
>
> 2021-08-24 12:22:29 [11550] [19] DEBUG: SMPP PDU 0x7fb1f0001a30 dump:
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   type_name: submit_sm
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   command_id: 4 = 0x0004
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   command_status: 0 = 0x
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   sequence_number: 21 = 0x0015
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   service_type: NULL
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   source_addr_ton: 1 = 0x0001
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   source_addr_npi: 1 = 0x0001
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   source_addr: "85080"
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   dest_addr_ton: 2 = 0x0002
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   dest_addr_npi: 2 = 0x0002
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   destination_addr: "XXX"
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   esm_class: 3 = 0x0003
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   protocol_id: 0 = 0x
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   priority_flag: 3 = 0x0003
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   schedule_delivery_time: NULL
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   validity_period: NULL
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   registered_delivery: 0 = 0x
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   replace_if_present_flag: 0 = 
> 0x
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   data_coding: 0 = 0x
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   sm_default_msg_id: 0 = 0x
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   sm_length: 29 = 0x001d
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   short_message:
> 2021-08-24 12:22:29 [11550] [19] DEBUG:    Octet string at 0x7fb1e00135b0:
> 2021-08-24 12:22:29 [11550] [19] DEBUG:      len:  29
> 2021-08-24 12:22:29 [11550] [19] DEBUG:      size: 30
> 2021-08-24 12:22:29 [11550] [19] DEBUG:      immutable: 0
> 2021-08-24 12:22:29 [11550] [19] DEBUG:      data: 54 45 54 53 20 54 45 53 54 
> 20 54 45 53 54 20 43   TETS TEST TEST C
> 2021-08-24 12:22:29 [11550] [19] DEBUG:      data: 4f 4e 20 35 37 20 53 49 4e 
> 20 44 4c 52            ON 57 SIN DLR
> 2021-08-24 12:22:29 [11550] [19] DEBUG:    Octet string dump ends.
> 2021-08-24 12:22:29 [11550] [19] DEBUG: SMPP PDU dump ends.
> 2021-08-24 12:22:29 [11550] [19] DEBUG: SMPP[]: throughput (1.00,30.00)
> 2021-08-24 12:22:29 [11550] [19] DEBUG: SMPP[: throughput (1.00,30.00)
> 2021-08-24 12:22:29 [11550] [19] DEBUG: SMPP[: Got PDU:
> 2021-08-24 12:22:29 [11550] [19] DEBUG: SMPP PDU 0x7fb1f0001a30 dump:
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   type_name: submit_sm_resp
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   command_id: 2147483652 = 0x8004
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   command_status: 80 = 0x0050
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   sequence_number: 21 = 0x0015
> 2021-08-24 12:22:29 [11550] [19] DEBUG:   message_id: "17b792f50c5020d24d"
> 2021-08-24 12:22:29 [11550] [19] DEBUG: SMPP PDU dump ends.
> 2021-08-24 12:22:29 [11550] [19] ERROR: SMPP[]: SMSC returned error code 
> 0x0050 (Invalid Destination address TON) in response to submit_sm.
>
>
>
>
> But If i set DLR =31 or 16, or 24, the DLR is sent back to kannel and HTTP 
> URL configured, and a new SQL record is inserted like an DLR (MOMT field)
>
> Is there a way to always have the responses from the submit_sm in the tables, 
> regardless of the DLR type  sent?
>
> We have problems because DLRs are considered messages and are charged by the 
> operator, so we cant activate DLRs
>
> any suggestions?
>
> Best regards,
> Gabriel
>

Re: Whatsapp Bot and Whatsapp Marketing

[Alexander Malysh]

Dear Textnator Team,

this is a first and last warning, no commercials on users/devel list please. 
For commercials we have commerc...@kannel.org ML.

Regards,
Alexander Malysh
Am 14. Aug. 2021, 15:40 +0200 schrieb Textnator Support :
> Dear Users,
> If anyone interested in doing whatsapp marketing.We are providing 
> resellership panel for whatsapp chat bot and whatsapp marketing(limitted to 
> 500 nos daily from one whatsapp number to avoid blocking).You can add as many 
> whatsapp number.For free demo please reply or send a message to 
> supp...@textnator.com
>
> Regards,
> Textnator Team

Re: Submit_sm resp after deliver_sm

[Alexander Malysh]

Hi,

this is clearly vendor BUG because submit_sm_resp has to arrive _before_ 
deliver_sm with DLR included.
submit_sm_resp includes message ID that is arrive afterwards in deliver_sm. If 
deliver_sm arrive before submit_sm_resp how kannel should know, that this DLR 
with some message ID belongs to submit_sm where kannel still waiting for 
submit_sm_resp?

Regards,
Alexander Malysh
Am 6. Aug. 2021, 04:59 +0200 schrieb Arif Noor :
> Hi All,
>
> Greetings, I constantly observing these message in the log file and get 
> informed that dlr is missing :
>
> Sample log :
>
> 2021-08-05 11:21:24 [6842] [8] ERROR: SMPP[6Series]: got DLR but could not 
> find message or was not interested in it id<1C1B9970> dst<601139873013>, 
> type<2>
>
> From pcap trace I found that the deliver_sm received before submit_sm.
>
>
> Does Kannel write the dlr-url to the db after receiving the submit_sm : resp?
> Is there any way to handle this issue as the vendor mentioned that it was 
> normal, kindly advise.
>
> Best Regards
> Arif Noor
>

Re: How to get TLV data from kannel by using meta-data

[Alexander Malysh]

Hi,

version 1.5.0 is too old, please use 1.4.5 or better SVN version. As far as I 
see from your description, it should work.

Thanks,
Alex


> Am 14.08.2020 um 10:20 schrieb Diwakar Bhatt :
> 
> Hi All,
> 
> I am using kannel 1.5.0, and i am really confused regarding the meta-data 
> capture, I have tried everything but couldn't come with correct solution.
> 
> Can you guys please help me with the problem I am facing, the detailed 
> explanation of question is in below link.
> 
> https://stackoverflow.com/questions/63331949/how-to-get-tlv-data-from-kannel-by-using-meta-data
>  
> 
> 
> 
> Regards,
> Diwakar Bhatt | Lead Developer - Engineering
> 
>   
> ACL Mobile Limited
> T: +91.120. 6139000 x 354| M: +91 8939277935
> W: www.aclmobile.com 
> "This electronic mail message sent from ACL Mobile Limited may contain 
> Confidential/Restricted/Internal information and should only be viewed by the 
> intended recipients. Under no circumstances may any such information be 
> disclosed, copied, used or distributed to any unauthorized persons or 
> entities without the written consent of ACL Mobile Limited. If you are not 
> the intended recipient, any review, retransmission, dissemination or reliance 
> on the content of these materials is strictly prohibited and may be the 
> subject of legal action. If you received this email in error please notify 
> the sender and delete the message"

Re: Kannel Support - memory leak

[Alexander Malysh]

Hi,

if it’s a Stipe’s software (means not a official kannel.org 
) then we are unable to help you, because it’s closed 
source.

Thanks,
Alex


> Am 11.08.2020 um 05:54 schrieb ploep...@fibernetics.ca:
> 
> We have .conf files to define the routes, but all the TNs are stored in a 
> database in which Kannel read from.
>  
> We where working with Stipe initially to get the cluster setup, but he is 
> appearing a little elusive at the moment.  So we figure to reach out to the 
> community. 
>  
>  
> Peter Loeppky | Voice Network System Specialist | Fibernetics
> +1-519-489-6700 x675 | www.fibernetics.ca 
>  
> From: users  On Behalf Of Rene Kluwen
> Sent: August 10, 2020 2:44 PM
> To: 'Davor Spasoski' ; ploep...@corp.fibernetics.ca
> Cc: users@kannel.org
> Subject: RE: Kannel Support - memory leak
>  
> How is the routing database sustained? In .conf files?
>  
> == Rene
>  
> Van: users mailto:users-boun...@kannel.org>> 
> Namens Davor Spasoski
> Verzonden: maandag 10 augustus 2020 20:15
> Aan: ploep...@corp.fibernetics.ca 
> CC: users@kannel.org 
> Onderwerp: Re: Kannel Support - memory leak
>  
> Despite being an open source supporter through and through, I’d have to say 
> if you have 3.5M routes, maybe you are a good candidate for a professional 
> support. 
> And no, I’m not affiliated to any of the companies offering that kind of 
> kannel support.
>  
> Good luck  
>  
>  
> 
>> On Aug 10, 2020, at 19:33, "ploep...@fibernetics.ca 
>> " > > wrote:
>> 
>>  
>> We have a 4 node Kannel cluster, which after bearerbox consumes all the ram 
>> on the box, usually about once a day, crashes and we have separate 
>> monitoring scripts to shutdown the remaining processes and start them back 
>> up.
>>  
>> Every time we reload the number route database, bearerbox uses an extra 
>> 1.8GB of ram. Our number routing database containg 3.5M records.
>>  
>> We are looking to get this resolved.
>>  
>>  
>> 
>> Peter Loeppky | Voice Network System Specialist | Fibernetics
>> +1-519-489-6700 x675 | www.fibernetics.ca 
>>  
>  
> 
> Disclaimer: A1 Makedonija DOOEL Skopje
> This e-mail (including any attachments) is confidential and may be protected 
> by legal privilege. If you are not the intended recipient, you should not 
> copy it, re-transmit it, use it or disclose its contents, but should return 
> it to the sender immediately and delete your copy from your system. Any 
> unauthorized use or dissemination of this message in whole or in part is 
> strictly prohibited. Please note that e-mails are susceptible to change. A1 
> Makedonija DOOEL Skopje shall not be liable for the improper or incomplete 
> transmission of the information contained in this communication nor for any 
> delay in its receipt or damage to your system.
> Please, do not print this e-mail unless it is necessary! Think about saving 
> the environment!
> 
> Напомена: А1 Македонија ДООЕЛ Скопје
> Оваа електронска порака (вклучувајќи ги и прилозите) е доверлива и може да 
> биде заштитена со правни привилегии. Доколку не сте лицето на кое таа му е 
> наменета пораката, не треба да ја копирате, дистрибуирате или да ја откривате 
> нејзината содржина, туку веднаш да ја препратите до испраќачот и да ја 
> избришете оригиналната порака и сите нејзини копии од Вашиот компјутерски 
> систем. Секое неовластено користење на оваа порака во целост или делови од 
> истата е строго забрането. Ве молиме да забележите дека електронските пораки 
> се подложни на промени. А1 Македонија ДООЕЛ Скопје не презема одговорност за 
> несоодветно или нецелосно пренесување на информациите содржани во оваа 
> комуникација, ниту пак за било какво задоцнување на приемот или оштетувања на 
> вашиот систем.
> Ве молиме не ја печатете оваа порака освен ако не е неопходно! Зачувајте ја 
> природата!

Re: IPv6 fail

[Alexander Malysh]

For MySql connection Kannel libs are not used. Kannel uses MySQL client library 
and therefore
there is something different wrong because MySQL client libs supports IPV6.

Alex

> Am 20.07.2020 um 10:28 schrieb Antony Stone 
> :
> 
> On Monday 20 July 2020 at 08:48:39, Alexander Malysh wrote:
> 
>> Hi,
>> 
>> Kannel always take the first IP from DNS response. Therefore you have to
>> make sure IPV4 address is the first address,
> 
> Er, you can't do that with DNS.  Records are returned from the resolver in a 
> random order on each request, in a deliberate effort to spread out the load 
> on 
> servers.
> 
> On Monday 20 July 2020 at 09:07:15, Alexander Malysh wrote:
> 
>> Hmm, looking into the code Kannel should connect just fine even DNS
>> resolves to IPV4 and IPV6.
>> 
>> Please check in your logs in debug mode for:
>> 
>> Connecting to <%s>
>> 
>> AND
>> 
>> connect to <%s> failed
> 
> I see no "Connecting to" messages for the hostname in question.
> 
> I do see:
> 
> 2020-07-20 09:18:19 [6053] [0] ERROR: MYSQL: Can't connect to MySQL server on 
> 'server.example.com' (111 "Connection refused")
> 
> 2020-07-20 09:18:19 [6053] [0] PANIC: SQLBOX: MySQL: database pool has no 
> connections!
> 
> 2020-07-20 09:18:19 [6143] [0] ERROR: MYSQL: can not connect to database!
> 
> Now, the "connection refused" part puzzled me - it looked like kannel was 
> connecting to MySQL but MySQL was saying "go away", so I set up tshark to 
> capture packets to/from port 3306, and what I see is that an *IPv6* 
> connection 
> *is being made* between the two servers, there's a login request, an 'OK' 
> response and then the connection gets closed.
> 
> I'm going to investigate this a bit more to see exactly what query and 
> response are being exchanged, once I can spend a bt of time with a broken 
> system again.
> 
> 
> Thanks for the assistance,
> 
> 
> Antony.
> 
> -- 
> A few words to be cautious of between American and English:
> - momentarily
> - suspenders
> - chips
> - pants
> - jelly
> - pavement
> - vest
> - pint (and gallon)
> - pissed
> 
> 
>   Please reply to the list;
> please *don't* CC me.
> 

Re: IPv6 fail

[Alexander Malysh]

Hmm, looking into the code Kannel should connect just fine even DNS resolves to 
IPV4 and IPV6.

Please check in your logs in debug mode for:

Connecting to <%s>

AND

connect to <%s> failed

Thanks,
Alex

> Am 20.07.2020 um 08:48 schrieb Alexander Malysh :
> 
> Hi,
> 
> Kannel always take the first IP from DNS response. Therefore you have to make 
> sure IPV4
> address is the first address,
> 
> Alex
> 
> 
>> Am 19.07.2020 um 15:43 schrieb Antony Stone 
>> > <mailto:antony.st...@kannel.open.source.it>>:
>> 
>> On Sunday 19 July 2020 at 15:04:45, Alexander Malysh wrote:
>> 
>>> Hi,
>>> 
>>> kannel doesn’t support IPV6 yet.
>> 
>> Hm, it appears to be even worse than I thought...
>> 
>> I was switching from a config file which contained the hostname of a server 
>> which only had an IPv4 address, to a hostname which only resolves to an IPv6 
>> address.
>> 
>> Since kannel doesn't do IPv6 yet, that didn't work.
>> 
>> However today I seem to have found that if you give kannel a hostname which 
>> resolves to both IPv4 and IPv6 addresses, it still can't connect to the IPv4 
>> address!
>> 
>> Just the existence of an IPv6 address in the hostname lookup is enough to 
>> prevent kannel from being able to connect to the IPv4 address alongside it.
>> 
>> 
>> Can anyone else confirm this finding, or is it just me and my networking 
>> setup 
>> (which works fine for other services connecting to both IPv4 and IPv6 
>> addresses 
>> for the same hostname)?
>> 
>> 
>> Thanks,
>> 
>> 
>> Antony.
>> 
>> -- 
>> "When you talk about Linux versus Windows, you're talking about which 
>> operating system is the best value for money and fit for purpose. That's a 
>> very 
>> basic decision customers can make if they have the information available to 
>> them. Quite frankly if we lose to Linux because our customers say it's 
>> better 
>> value for money, tough luck for us."
>> 
>> - Steve Vamos, MD of Microsoft Australia
>> 
>>   Please reply to the list;
>> please *don't* CC me.
>> 
>> 
> 

Re: IPv6 fail

[Alexander Malysh]

Hi,

Kannel always take the first IP from DNS response. Therefore you have to make 
sure IPV4
address is the first address,

Alex


> Am 19.07.2020 um 15:43 schrieb Antony Stone 
> :
> 
> On Sunday 19 July 2020 at 15:04:45, Alexander Malysh wrote:
> 
>> Hi,
>> 
>> kannel doesn’t support IPV6 yet.
> 
> Hm, it appears to be even worse than I thought...
> 
> I was switching from a config file which contained the hostname of a server 
> which only had an IPv4 address, to a hostname which only resolves to an IPv6 
> address.
> 
> Since kannel doesn't do IPv6 yet, that didn't work.
> 
> However today I seem to have found that if you give kannel a hostname which 
> resolves to both IPv4 and IPv6 addresses, it still can't connect to the IPv4 
> address!
> 
> Just the existence of an IPv6 address in the hostname lookup is enough to 
> prevent kannel from being able to connect to the IPv4 address alongside it.
> 
> 
> Can anyone else confirm this finding, or is it just me and my networking 
> setup 
> (which works fine for other services connecting to both IPv4 and IPv6 
> addresses 
> for the same hostname)?
> 
> 
> Thanks,
> 
> 
> Antony.
> 
> -- 
> "When you talk about Linux versus Windows, you're talking about which 
> operating system is the best value for money and fit for purpose. That's a 
> very 
> basic decision customers can make if they have the information available to 
> them. Quite frankly if we lose to Linux because our customers say it's better 
> value for money, tough luck for us."
> 
> - Steve Vamos, MD of Microsoft Australia
> 
>   Please reply to the list;
> please *don't* CC me.
> 

Re: IPv6 fail

[Alexander Malysh]

Hi,

kannel doesn’t support IPV6 yet. 

Thanks,
Alex

P.S. Patch that you found is not enough and is not complete.

> Am 19.07.2020 um 11:04 schrieb Antony Stone 
> :
> 
> Hi.
> 
> I'm using kannel 1.4.5 with MySQL for DLR storage, and yesterday I changed 
> the 
> "host" parameter in my kannel.conf and sqlbox.conf sections:
> 
> # MySQL Connection 
> group = mysql-connection 
> id = dlr-db 
> host = server.example.com 
> username = kannelsql
> password = strongpassword
> database = kanneldlr
> 
> Previously server.example.com  was IPv4 
> resolvable but I now need to talk to a 
> new server over IPv6, and kannel simply refused to start.
> 
> I get messages in sqlbox.log such as:
> 
> 2020-07-18 22:51:37 [11895] [0] ERROR: MYSQL: Unknown MySQL server host 
> 'server.example.com ' (-8)
> 
> If I simply switch it back to the IPv4 resolvable name of the old server, it 
> starts as usual.
> 
> So, I'm suspecting that kannel has no clue about IPv6... :(
> 
> 
> A Google search for "kannel IPv6" points me at things such as:
> 
> http://kannel.6189.n7.nabble.com/PATCH-IPV6-Socket-support-td29095.html 
> 
> 
> however this gives me no information about which version of kannel the patch 
> has been applied to, and whether it applies to DLR storage as well as 
> kannel's 
> own HTTP communications.
> 
> 
> So, my question is:
> 
> can I get kannel to connect to a MySQL server for DLR storage over IPv6, and 
> which version of kannel (and / or sqlbox) do I need to be using for this?
> 
> 
> Thanks,
> 
> 
> Antony.
> 
> -- 
> Having been asked for a reference for this man,
> I can confirm that you will be very lucky indeed
> if you can get him to work for you.
> 
>   Please reply to the list;
> please *don't* CC me.
> 

Re: Empty Incoming SMS

[Alexander Malysh]

Hi,

please share your kannel config.

Thanks,
Alex


> Am 29.06.2020 um 11:21 schrieb nashwan Al-Mawri  >:
> 
> Dear Antony 
> 
> please see my answers below 
> 1. If you send someone a text message through your Kannel system, they 
> receive 
> it, and then reply back to it *quoting your original message* as well as 
> anything else they want to say, do you get the text of the original message 
> back? 
> when i test it with my phone i receive it and when i reply with OK i got it 
> back on Kannel system ,
> 
> 2. For a message sent by someone else (from a standard phone), do you receive 
> the text of what they send accurately?
> i have MT service and the customer should send OK to subscriber to my service 
> , when we send bulk SMS  most of the incoming SMS are empty , some with other 
> text ,and few send the right Keyword Ok .
> 
> when i check the log for the numbers that send blank SMS 
> DEBUG: Parsing URL 
> `http://localhost/vms/getsms.php?sender=%2B26399456789=8061==-1=2020-06-10+18:28:00=%2B26399456789==sourceline1=f6f42e80-2f5f-476b-8b89-4c45aacb0b43
>  
> ':
> 2020-06-10 18:28:00 [2221] [10] DEBUG:   Query: 
> sender=%2B26399456789=8061==-1=2020-06-10+18:28:00=%2B26399456789 
> ==sourceline1=f6f42e80-2f5f-476b-8b89-4c45aacb0b43
> 
> best regards
> Nashwan
> 
> On Wed, Jun 24, 2020 at 4:10 PM Antony Stone 
>  > wrote:
> On Wednesday 24 June 2020 at 14:40:58, nashwan Al-Mawri wrote:
> 
> > I checked the kannel log , and i found out ,the  blank sms text on the log
> > is ? as you can see on the log below , please note that the
> > outgoing SMS  is unicode characters and it works fine , any suggestions ,
> > do i have to do any formatting  for the incoming sms ,,
> 
> Sorry, I don't understand.  What you have posted is a perfectly plain ASCII 
> message, which reads "id:11200301200624091626130061 submit 
> date:2006241204 
> done date:2006241204 stat:DELIVRD err:000 text:? "
> 
> As far as I can tell, that is precisely what the sender is sending you.  It's 
> some sort of delivery comfirmation for a message sent at (20)20-06-24 12:04 
> with ID 11200301200624091626130061, and I would expect the text at the 
> end 
> has been replaced with "? " for security reasons.
> 
> I'm still of the opinion that you have to get the sender to tell you 
> precisely 
> what they think they have sent (in a similar level of detail to these log 
> files) in order to be sure whether there is anything wrong with your setup.
> 
> 
> Let me ask a couple of other questions:
> 
> 1. If you send someone a text message through your Kannel system, they 
> receive 
> it, and then reply back to it *quoting your original message* as well as 
> anything else they want to say, do you get the text of the original message 
> back?
> 
> 2. For a message sent by someone else (from a standard phone), do you receive 
> the text of what they send accurately?
> 
> 
> I'm just trying to distinguish what I would call "normal messages" from the 
> delivery report you've given as an example.
> 
> 
> Antony.
> 
> -- 
> Roses are red,
> Bacon is too,
> Poetry's hard,
> Bacon.
> with thanks to Claire Davison
> 
>Please reply to the list;
>  please *don't* CC me.
> 

Re: Unable to deliver DLRs: "Couldn't fetch..."

[Alexander Malysh]

Hi,

you are welcome!

for smsbox as well as for http SMSC in bearerbox we have following option to 
configure this behaviour:

max-pending-requestsnumber of messages  Maximum number of pending MO or 
DLR messages that are handled in parallel. (Default: 512)

Thanks,
Alex



> Am 22.05.2020 um 20:46 schrieb Paulo Correia :
> 
> Hi Alexander,
> 
> Thank you for the tip!
> 
> I've found the following errors:
> 
> 2020-05-20 23:28:50 [52975] [10] ERROR: Couldn't create new socket.
> 2020-05-20 23:28:50 [52975] [10] ERROR: System error 24: Too many open files
> 2020-05-20 23:28:50 [52975] [10] ERROR: error connecting to server 
> `dlrreceiver_ip' at port `dlrreceiver_port'
> 2020-05-20 23:28:50 [52975] [10] ERROR: Couldn't send request to 
> <http://dlrreceiver_ip:dlrreceiver_port/receive-dlr?type=8=X=ACK%2F==XXX==XXX=aUsername
>  
> <http://dlrreceiver_ip:dlrreceiver_port/receive-dlr?type=8=X=ACK%2F==XXX==XXX=aUsername>>
> 
> 
> I'll check what's needed to increase the limit of open files.
> 
> Kind regards,
> Paulo Correia
> Head of Development
> 
> telephone:+351210337760 fax: +351210337761 
> email: paulo.corr...@go4mobility.com <mailto:paulo.corr...@go4mobility.com> 
> skype: pcorreia.g4m 
> 
>  <https://go4mobility.com/en>
>  <https://www.linkedin.com/company/go4mobility/>
> _
> CONFIDENTIALITY
> This message, as well as existing attached files, may be confidential and 
> privileged. Use or disclosure by anyone other than an intended recipient is 
> not authorised.
> If you have received this message by error, you are kindly requested to 
> delete it and notify the sender. Thank you for your cooperation.
> 
> From: Alexander Malysh  on behalf of Alexander Malysh 
> 
> Sent: 22 May 2020 15:38
> To: Paulo Correia 
> Cc: users@kannel.org 
> Subject: Re: Unable to deliver DLRs: "Couldn't fetch..."
>  
> Hi,
> 
> do you have any errors except couldn’t fetch? mostly it’s because either 
> kannel ran out of filedexfriptors or
> because receiving server is unable to accept that much connections from 
> kannel (or both).
> 
> Check you kannel log file for other errors.
> 
> Thanks,
> Alex
> 
> 
>> Am 21.05.2020 um 14:35 schrieb Paulo Correia > <mailto:paulo.corr...@go4mobility.com>>:
>> 
>> Hi fellow kannel users,
>> 
>> We've been using kannel for quite some years and on the latest months we've 
>> seen an issue when processing DLRs on high traffic.
>> 
>> We send the messages to kannel using HTTP with the /cgi-bin/sendsms adding 
>> the dlr-url and dlr-mask values as always have been sending.
>> When kannel receives a DLR, it'll then send us an HTTP notification using 
>> the previously defined dlr-url for that message, assuming the dlr-mask 
>> matches the status.
>> 
>> When the traffic is high, we normally get the following on our smsbox logs:
>> 2020-05-21 00:02:58 [47847] [9] ERROR: Couldn't fetch 
>> <http://dlrreceiver_ip:dlrreceiver_port/receive-dlr?type=8=X=ACK%2F==XXX==XXX=aUsername
>>  
>> <http://dlrreceiver_ip:dlrreceiver_port/receive-dlr?type=8=X=ACK%2F==XXX==XXX=aUsername>>
>> 
>> We then have to parse the logs to obtain these "lost" DLRs and reprocess 
>> them.
>> 
>> My questions:
>> Has anyone seen this behaviour? 
>> Any hints how to solve it?
>> What can cause this issue?
>> Failure of processing on the dlrreceiver_ip:dlrreceiver_port ?
>> Timeout on dlrreceiver_ip:dlrreceiver_port ?
>> Could there be another way to send the DLRs instead of HTTP? 
>> Could they be stored in SQL?
>> We even created a HAProxy to receive the requests and route them to the 
>> server, and in case of an issue, reroute them to an application that stores 
>> the "missed dlr" into the DB, but still doesn't cut it.
>> 
>> Thanks in advance!
>> 
>> Kind regards,
>> Paulo Correia
>> Head of Development
>> 
>> telephone:+351210337760 fax: +351210337761 
>> email: paulo.corr...@go4mobility.com <mailto:paulo.corr...@go4mobility.com> 
>> skype: pcorreia.g4m 
>> 
>>  <https://go4mobility.com/en>
>>  <https://www.linkedin.com/company/go4mobility/>
>> _
>> CONFIDENTIALITY
>> This message, as well as existing attached files, may be confidential and 
>> privileged. Use or disclosure by anyone other than an intended recipient is 
>> not authorised.
>> If you have received this message by error, you are kindly requested to 
>> delete it and notify the sender. Thank you for your cooperation.
>> 
>> 
> 
> 

Re: Unable to deliver DLRs: "Couldn't fetch..."

[Alexander Malysh]

Hi,

do you have any errors except couldn’t fetch? mostly it’s because either kannel 
ran out of filedexfriptors or
because receiving server is unable to accept that much connections from kannel 
(or both).

Check you kannel log file for other errors.

Thanks,
Alex


> Am 21.05.2020 um 14:35 schrieb Paulo Correia :
> 
> Hi fellow kannel users,
> 
> We've been using kannel for quite some years and on the latest months we've 
> seen an issue when processing DLRs on high traffic.
> 
> We send the messages to kannel using HTTP with the /cgi-bin/sendsms adding 
> the dlr-url and dlr-mask values as always have been sending.
> When kannel receives a DLR, it'll then send us an HTTP notification using the 
> previously defined dlr-url for that message, assuming the dlr-mask matches 
> the status.
> 
> When the traffic is high, we normally get the following on our smsbox logs:
> 2020-05-21 00:02:58 [47847] [9] ERROR: Couldn't fetch 
>   
> >
> 
> We then have to parse the logs to obtain these "lost" DLRs and reprocess them.
> 
> My questions:
> Has anyone seen this behaviour? 
> Any hints how to solve it?
> What can cause this issue?
> Failure of processing on the dlrreceiver_ip:dlrreceiver_port ?
> Timeout on dlrreceiver_ip:dlrreceiver_port ?
> Could there be another way to send the DLRs instead of HTTP? 
> Could they be stored in SQL?
> We even created a HAProxy to receive the requests and route them to the 
> server, and in case of an issue, reroute them to an application that stores 
> the "missed dlr" into the DB, but still doesn't cut it.
> 
> Thanks in advance!
> 
> Kind regards,
> Paulo Correia
> Head of Development
> 
> telephone:+351210337760 fax: +351210337761 
> email: paulo.corr...@go4mobility.com  
> skype: pcorreia.g4m 
> 
>  
>  
> _
> CONFIDENTIALITY
> This message, as well as existing attached files, may be confidential and 
> privileged. Use or disclosure by anyone other than an intended recipient is 
> not authorised.
> If you have received this message by error, you are kindly requested to 
> delete it and notify the sender. Thank you for your cooperation.
> 
> 

Re: Questions towards using Kannel 1.5.0

[Alexander Malysh]

Hi,

see inline…

> Am 30.04.2020 um 16:35 schrieb Akis Stamatiou 
> :
> 
> Hello Kannel team,
> 
> 1. We are investigating the possibility to use kannel with the opensmpp 
> plugin to be part of our infrastructure.
> We have run a PoC using kannel 1.5.0 on Ubuntu 16.04 and 18.04, and it went 
> really well.
> Since version 1.5.0 is an older version, we would like to know if there is 
> any level of support for it and its opensmpp plugin?

the latest Kannel release is 1.4.5 and not 1.5.0. Please use it or SVN 
checkout, it should be stable enough.
Yes, we can provide commercial support for Kannel, please ping me if you like 
to know details.

> 
> 2. Can Kannel be used in a High availability concept?

Yes and no, it depends on your needs.

> 
> 3. Also we required to make a minor change to opensmppbox to cover our needs.
> -we added a boolean flag in the configuration to disable multipart message 
> concatenation in opensmppbox-
> When we make a merge request, and if the request is approved, will the 
> changes be added for version 1.5.0, or only for the latest version?

Please post your patch to de...@kannel.org  and we 
will vote/commit it to SVN.

> 
> Looking forward to hearing from you.
> 
> Thank you,  
> 
> -- 
> 
>  
>   
> Akis Stamatiou
> 
> Technical Product Manager
> 
> 
> 
>    
>   
>  
>   
>   
>   
>  
>   
> T +302106618500 (ext.279) 
> M +306986973922 
> Skype: live:stamprok_1 <>
>  
> 
> PRIVILEGED AND CONFIDENTIAL COMMUNICATION
> 
> This e-mail transmission, and any documents, files or previous e-mail 
> messages attached to it, may contain confidential information that is legally 
> privileged. If you are not the intended recipient or a person responsible for 
> delivering it to the intended recipient, you are hereby notified that any 
> disclosure, copying, distribution or use of any of the information contained 
> in or attached to this transmission is STRICTLY PROHIBITED. If you have 
> received this transmission in error, please: (1) immediately notify me by 
> reply e-mail, or by collect telephone call; and (2) destroy the original 
> transmission and its attachments without reading or saving in any manner.

Re: Temporary message store for multi-part SMSs

[Alexander Malysh]

Hi,

unfortunately you mixed two things together.

1. Store support.
It’s a snapshot of messages that Kannel has in his memory (RAM) stored 
either on disk (spool, file) or in Redis.
This store is used for a case if Kannel crashes, then messages are not 
lost.
This is _NOT_ shared between Kannel instances, but different instance 
can read store if first instance gone for long time.

2. DLR support.
It’s temp. DLR storage to storing messages where Kannel still waiting 
for a DLR to arrive.
DLR storage can be shared (like same MySQL DB and table) and if one 
instance receive DLR for the message
sent via second instance, DLR will be mapped and processed (please set 
same SMSC-IDs for both instances/binds).

DBPool is just internal Kannel Database Pool that supports multiple databases 
and is used for all database accesses in kannel.

I hope it’s a little bit clearer now.

Regards,
Alex


> Am 28.03.2020 um 15:23 schrieb Antony Stone 
> :
> 
> Hi.
> 
> I'm using kannel talking SMPP to an upstream SMSC provider.
> 
> We can send and receive SMS fine, and DLR is working well too.  We use MySQL 
> for the DLR store.
> 
> However, we have a High-Availability setup, which means that we have two 
> machines running kannel, each with a connection to the upstream provider, and 
> inbound SMSs can arrive on either connection.
> 
> In the case of multi-part SMSs, different parts can arrive on each link, 
> resulting in one of our kannel instances having, say, parts 1 and 3, and the 
> other instance having part 2 of the same message.  There's no way either of 
> them can know what the other has seen, so the end result is that the user 
> receives three independent message parts (not necessarily even in the right 
> order).
> 
> Since we use a MySQL cluster for the DLR store, I wanted to use that also for 
> the temporary message store for multi-part SMSs, and indeed I notice in the 
> section "Compiling the Gateway" of 
> https://kannel.org/download/1.4.5/userguide-1.4.5/userguide.html 
>  that there 
> are two options (amongst others):
> 
>   --with-mysqlEnable using MySQL libraries for DBPool and DLR support.
> 
>   --with-redisEnable using Redis for DBPool and DLR support. Requires 
> the hiredis library.
> 
> I'm assuming that "DBPool" refers to the temporary message store during 
> processing of multi-part SMSs.  I don't see the term "DBPool" defined or 
> indeed 
> even used anywhere in the documentation other than in the description of 
> these 
> options (and the related MSSQL etc options).
> 
> 
> However, under "Core configuration", the option "store-type" says "This 
> variable defines a type of backend used for store subsystem. Now two types 
> are 
> supported: a) file: writes store into one single file b) spool: writes store 
> into spool directory (one file for each message) c) redis: writes store into 
> a 
> redis key storage."
> 
> I'm assuming that "two" in the above description is simply a hang-over from a 
> previous version of the documentation, when the "redis" type was not 
> available, but my main question is "how do we select MySQL for the DBPool 
> storage?"
> 
> 
> Thanks for any pointers...
> 
> 
> Antony.
> 
> -- 
> There's no such thing as bad weather - only the wrong clothes.
> 
> - Billy Connolly
> 
>   Please reply to the list;
> please *don't* CC me.
> 

Re: WARNING: smsbox_list empty!

[Alexander Malysh]

Hi,

this warning can popup in the startup phase of bearerbox when 
smsbox/opensmppbpx is still not connected to bearerbox and messages have to be 
routed already.
if it works afterwards and no such warnings are popping up after startup then 
nothing to worry about.

Thanks,
Alex


> Am 18.12.2019 um 01:59 schrieb Александр Недзельский :
> 
> Hi,
> 
> I've searched through similar topics, checked 
> https://www.kannel.org/download/1.4.4/gateway-1.4.4/gw/bb_boxc.c 
> , but still 
> cannot find a solution:
> 
> Upon start and after I see in bearerbox.log multiple messages at moment, 
> repeating periodically:
> 
> 2019-12-18 03:09:40 [26216] [4] WARNING: smsbox_list empty!
> 2019-12-18 03:09:40 [26216] [4] WARNING: smsbox_list empty!
> 2019-12-18 03:09:40 [26216] [4] WARNING: smsbox_list empty!
> 2019-12-18 03:09:40 [26216] [4] WARNING: smsbox_list empty!
> 2019-12-18 03:09:40 [26216] [4] WARNING: smsbox_list empty!
> 2019-12-18 03:09:40 [26216] [4] WARNING: smsbox_list empty!
> 2019-12-18 03:09:40 [26216] [4] WARNING: smsbox_list empty!
> 2019-12-18 03:09:40 [26216] [4] WARNING: smsbox_list empty!
> 
> At the same time all messages are sending and everything is workin fine.
> 
> I've tried changing config in smsbox-route and smsbox part but no success.
> 
> My kannel.conf:
> 
> group = core
> admin-port = 13000
> admin-password = [deleted]
> status-password = [deleted]
> log-file = "/var/log/kannel/bearerbox.log"
> log-level = 0
> store-type = spool
> store-location = "/var/spool/kannel"
> box-deny-ip = "*.*.*.*"
> box-allow-ip = "[deleted]"
> smsbox-port = 13001
>  
> group = smsbox
> smsbox-id = smsbox
> bearerbox-host = localhost
> bearerbox-port = 13001
> sendsms-port = 13007
> sendsms-url = /mt.cgi
> log-file = "/var/log/kannel/smsbox.log"
> access-log = "/var/log/kannel/smsbox.access.log"
> mo-recode = true
> log-level = 0
>  
> group = smsbox-route
> smsbox-id = smsbox 
>  
> group = sendsms-user
> username = [deleted]
> password = [deleted]
> concatenation = true
> max-messages = 10 
>  
> group = smsc
> smsc = fake
> smsc-id = fake
> allowed-smsc-id = fake
> port = 1
> connect-allow-ip = 127.0.0.1 
>  
> group = smsc
> smsc = smpp
> smsc-id = [deleted]
> allowed-smsc-id = [deleted]
> log-file = "/var/log/kannel/[deleted].log"
> smsc-username = "[deleted]"
> smsc-password = "[deleted]"
> host = [deleted]
> port = 4442
> transceiver-mode = true
> system-type= ""
> service-type = ""
> address-range = ""
> source-addr-ton = 0
> source-addr-npi = 1
> dest-addr-ton = 1
> dest-addr-npi= 1
> log-level = 0
> alt-charset=ucs-2be
> connection-timeout = 300
> 
> Thank you for your help!
> 
> 
> С уважением,
> Недзельский Александр

Re: TLV Parameters

[Alexander Malysh]

Hi,

please start read userguide ;-)

https://kannel.org/download/kannel-userguide-snapshot/userguide.html#AEN6481 


Alex


> Am 21.11.2019 um 11:07 schrieb Robin C :
> 
> 
> Hi all,
> 
> How to add and where to add TLV parameters in Kannel ? 
> -- 
>  Thanks & Regards,
>   
>   Robin C
> 
> 
> 
> 
> 
> 
> 
> Disclaimer:  This message contains confidential information and is intended 
> only for the individual named.  If you are not the named addressee you should 
> not disseminate, distribute or copy this e-mail.  Please notify the sender 
> immediately by e-mail if you have received this e-mail by mistake and delete 
> this e-mail from your system.  E-mail transmission cannot be guaranteed to be 
> secure or error-free as information could be intercepted, corrupted, lost, 
> destroyed, arrive late or incomplete, or contain viruses.  The sender 
> therefore does not accept liability for any errors or omissions in the 
> contents of this message, which arise as a result of e-mail transmission.  If 
> verification is required please request a hard-copy version.
> 
> 7 Switch off as you go |q Recycle always | P Print only if absolutely 
> necessary
> 

Re: Three out of four

[Alexander Malysh]

Hi,

define dlr-url in your request to smsbox and you are done.

Thanks,
Alex

> Am 16.08.2019 um 11:59 schrieb Antony Stone 
> :
> 
> Hi.
> 
> I've recently installed kannel 1.4.4 on a Debian Stretch machine (from the 
> standard Debian repository package).
> 
> I have an account with an SMSC provider and I'm talking to them using SMPP 3.4
> 
> So far I've got kannel set up and configured to:
> 
> 1. Send SMS to mobiles - works.
> 
> 2. Receive delivery notifications for sent messages - works.
> 
> 3. Receive SMS from mobiles - works.
> 
> The bit I'm missing is that I can't work out how to send a delivery 
> notification for messages I receive.
> 
> For the inbound delivery notifications, I'm getting a status code 8 from the 
> SMSC when they've received my message and are processing it, then I get a 
> status code 1 when the message is delivered to the mobile.
> 
> Can I configure kannel to automatically send status code 8 when it gets an 
> inbound message, and passes it on to my delivery URL?
> 
> And then, how do I send the appropriate request to kannel to say "message has 
> been delivered to user" to get it to send out status code 1?
> 
> 
> Thanks,
> 
> 
> Antony.
> 
> -- 
> +++ Divide By Cucumber Error.  Please Reinstall Universe And Reboot +++
> 
>   Please reply to the list;
> please *don't* CC me.
> 

Re: SMS/SMPP/VOICE all in one Frontend Web Application

[Alexander Malysh]

Hi,

please stop advertising on users mailing list! we have commercial mailing list 
for this purpose.

Thanks,
Alex


> Am 23.07.2019 um 10:40 schrieb vinayak mv :
> 
> Dear Users,
> 
> Dedicated Bulk SMS, VOICE, SMPP frontend and backend appllication for monthly 
> rental.
> Unlimited usage at Rs 15k/month please reply for demo 
> 
> Panel Features
> 
> 1.Bulk SMS,VOICE and SMPP on a single panel
> 2. Users/Resellers Feature
> 3. Different View templates for resellers
> 4. Virtual Credit and Fake Delivery System
> 5.Fake Report generation for SMS,VOICE,SMPP
> 6.Template, SenderId, Spam filtering
> 7. Complete MIS Features
> 8. Manage Users and Resellers
> 9. Configure Operator Connectivity through frontend
> 10. SMS Routing option
> 11. Unique error code mapping for SMS, VOICE and SMPP
> 12. Intelligent Routing
> 
> -- 
> Thanks & Regards,
> 

Re: Kannel throughput affected by DLR

[Alexander Malysh]

Hi,

only for sending.

Alex


> Am 12.06.2019 um 11:22 schrieb Valentin Militaru 
> :
> 
> Hi,
>  
> Can you please tell me if the smsc param “throughput” refers only to sent 
> messages, or does it include DLRs also?
>  
> Thanks!

Re: Error while starting bearerbox

[Alexander Malysh]

Hi,

thanks for the output, as I already told, your store file is corrupted. Please 
delete store file and backup and start again.

P.S. Please update to the new stable version.

Thanks,
Alex 

> Am 07.05.2019 um 16:22 schrieb SDB  <mailto:sant...@thinkwalnut.com>>:
> 
> Hello Alex,
> 
> Please find below the output :
> 
> [root@SMSC_Kannel ~]# addr2line -e /usr/local/kannel_svn/sbin/bearerbox 
> 0x491dfe 0x491f6f 0x495cbc 0x444687 0x40f014 0x7fd026f05af5 0x40f755
> /usr/local/src/gateway-1.4.4/gwlib/log.c:572
> /usr/local/src/gateway-1.4.4/gwlib/log.c:608
> /usr/local/src/gateway-1.4.4/gwlib/octstr.c:357 (discriminator 1)
> /usr/local/src/gateway-1.4.4/gw/bb_store_file.c:134
> /usr/local/src/gateway-1.4.4/gw/bearerbox.c:726
> ??:0
> ??:?
> [root@SMSC_Kannel ~]# 
> 
> 
> 
> Regards
> Santosh Bhabal |  Sr. System Administrator | TSG | 9137253070 / 8767466290
> On 07/05/19 7:49 PM, Alexander Malysh wrote:
>> Hi,
>> 
>> looks like your store file is corrupted.
>> 
>> can you please post backtrace?
>> 
>> addr2line -e PATH_TO_BEARERBOX_BIN 0x491dfe 0x491f6f 0x495cbc 0x444687 
>> 0x40f014 0x7fd026f05af5 0x40f755
>> 
>> Thanks,
>> Alex
>> 
>>> Am 07.05.2019 um 06:50 schrieb SDB >> <mailto:sant...@thinkwalnut.com>>:
>>> 
>>> Hello Rene,
>>> 
>>> But why it is killing the bearerbox process ?
>>> 
>>> Bearerbox should start with the error right ?
>>> 
>>> On 06/05/19 2:03 PM, Rene Kluwen wrote:
>>>> Looks like a boo-boo in your group = smsc config for the “transaction” 
>>>> smsc.
>>>> Maybe you have a wrong port number. It looks like it’s connecting to a 
>>>> non-smpp port.
>>>>  
>>>> == Rene
>>>>  
>>>> Van: users  <mailto:users-boun...@kannel.org> 
>>>> Namens SDB
>>>> Verzonden: maandag 6 mei 2019 07:27
>>>> Aan: users@kannel.org <mailto:users@kannel.org>
>>>> Onderwerp: Error while starting bearerbox
>>>>  
>>>> Hello Experts,
>>>> 
>>>> I am getting below error while starting the bearerbox :
>>>> 
>>>> 2019-05-03 19:44:42 [2981] [6] ERROR: Error reading from fd 22:
>>>> 2019-05-03 19:44:42 [2981] [6] ERROR: System error 104: Connection reset 
>>>> by peer
>>>> 2019-05-03 19:44:42 [2981] [6] ERROR: SMPP[transaction]: Couldn't connect 
>>>> to SMS center (retrying in 10 seconds).
>>>> 2019-05-03 19:44:42 [2981] [0] INFO: Loading store file 
>>>> `/var/log/kannel/transaction/store.log'
>>>> 2019-05-03 19:44:42 [2981] [0] INFO: Store-file size 16613376, starting to 
>>>> unpack (may take awhile)
>>>> 2019-05-03 19:44:42 [2981] [0] ERROR: Packet too short while unpacking Msg.
>>>> 2019-05-03 19:44:42 [2981] [0] ERROR: Msg packet was invalid.
>>>> 2019-05-03 19:44:42 [2981] [0] ERROR: Garbage at store-file, skipped.
>>>> 2019-05-03 19:44:42 [2981] [0] PANIC: gwlib/octstr.c:357: 
>>>> octstr_copy_real: Assertion `len >= 0' failed.
>>>> 2019-05-03 19:44:42 [2981] [0] PANIC: 
>>>> /usr/local/kannel_svn/sbin/bearerbox(gw_backtrace+0xae) [0x491dfe]
>>>> 2019-05-03 19:44:42 [2981] [0] PANIC: 
>>>> /usr/local/kannel_svn/sbin/bearerbox(gw_panic+0x15f) [0x491f6f]
>>>> 2019-05-03 19:44:42 [2981] [0] PANIC: 
>>>> /usr/local/kannel_svn/sbin/bearerbox(octstr_copy_real+0xfc) [0x495cbc]
>>>> 2019-05-03 19:44:42 [2981] [0] PANIC: 
>>>> /usr/local/kannel_svn/sbin/bearerbox() [0x444687]
>>>> 2019-05-03 19:44:42 [2981] [0] PANIC: 
>>>> /usr/local/kannel_svn/sbin/bearerbox(main+0xab4) [0x40f014]
>>>> 2019-05-03 19:44:42 [2981] [0] PANIC: 
>>>> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fd026f05af5]
>>>> 2019-05-03 19:44:42 [2981] [0] PANIC: 
>>>> /usr/local/kannel_svn/sbin/bearerbox() [0x40f755]
>>>> 
>>>> I am using Kannel bearerbox II version 1.4.4
>>>> 
>>>> Please help.
>>>> 
>> 
> 

Re: Error while starting bearerbox

[Alexander Malysh]

Hi,

looks like your store file is corrupted.

can you please post backtrace?

addr2line -e PATH_TO_BEARERBOX_BIN 0x491dfe 0x491f6f 0x495cbc 0x444687 0x40f014 
0x7fd026f05af5 0x40f755

Thanks,
Alex

> Am 07.05.2019 um 06:50 schrieb SDB :
> 
> Hello Rene,
> 
> But why it is killing the bearerbox process ?
> 
> Bearerbox should start with the error right ?
> 
> On 06/05/19 2:03 PM, Rene Kluwen wrote:
>> Looks like a boo-boo in your group = smsc config for the “transaction” smsc.
>> Maybe you have a wrong port number. It looks like it’s connecting to a 
>> non-smpp port.
>>  
>> == Rene
>>  
>> Van: users   
>> Namens SDB
>> Verzonden: maandag 6 mei 2019 07:27
>> Aan: users@kannel.org 
>> Onderwerp: Error while starting bearerbox
>>  
>> Hello Experts,
>> 
>> I am getting below error while starting the bearerbox :
>> 
>> 2019-05-03 19:44:42 [2981] [6] ERROR: Error reading from fd 22:
>> 2019-05-03 19:44:42 [2981] [6] ERROR: System error 104: Connection reset by 
>> peer
>> 2019-05-03 19:44:42 [2981] [6] ERROR: SMPP[transaction]: Couldn't connect to 
>> SMS center (retrying in 10 seconds).
>> 2019-05-03 19:44:42 [2981] [0] INFO: Loading store file 
>> `/var/log/kannel/transaction/store.log'
>> 2019-05-03 19:44:42 [2981] [0] INFO: Store-file size 16613376, starting to 
>> unpack (may take awhile)
>> 2019-05-03 19:44:42 [2981] [0] ERROR: Packet too short while unpacking Msg.
>> 2019-05-03 19:44:42 [2981] [0] ERROR: Msg packet was invalid.
>> 2019-05-03 19:44:42 [2981] [0] ERROR: Garbage at store-file, skipped.
>> 2019-05-03 19:44:42 [2981] [0] PANIC: gwlib/octstr.c:357: octstr_copy_real: 
>> Assertion `len >= 0' failed.
>> 2019-05-03 19:44:42 [2981] [0] PANIC: 
>> /usr/local/kannel_svn/sbin/bearerbox(gw_backtrace+0xae) [0x491dfe]
>> 2019-05-03 19:44:42 [2981] [0] PANIC: 
>> /usr/local/kannel_svn/sbin/bearerbox(gw_panic+0x15f) [0x491f6f]
>> 2019-05-03 19:44:42 [2981] [0] PANIC: 
>> /usr/local/kannel_svn/sbin/bearerbox(octstr_copy_real+0xfc) [0x495cbc]
>> 2019-05-03 19:44:42 [2981] [0] PANIC: /usr/local/kannel_svn/sbin/bearerbox() 
>> [0x444687]
>> 2019-05-03 19:44:42 [2981] [0] PANIC: 
>> /usr/local/kannel_svn/sbin/bearerbox(main+0xab4) [0x40f014]
>> 2019-05-03 19:44:42 [2981] [0] PANIC: 
>> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fd026f05af5]
>> 2019-05-03 19:44:42 [2981] [0] PANIC: /usr/local/kannel_svn/sbin/bearerbox() 
>> [0x40f755]
>> 
>> I am using Kannel bearerbox II version 1.4.4
>> 
>> Please help.
>> 

Re: DLR issue on Kannel 1.4.4

[Alexander Malysh]

Hi,

there is not enough infos to understand what’s going wrong.

Please post submit_sm to this failing DLR then we at least will see what 
happened.

Thanks,
Alex

 Am 15.08.2015 um 18:57 schrieb Moazzam moz...@gmail.com:
 
 No not using multi part  MT  my all messages are carrying 
 [flags:-1:0:-1:-1:31]  within 140 char length limit.
 
 On 8/15/2015 9:42 PM, spameden wrote:
 
 
 2015-08-15 18:03 GMT+03:00 Moazzam moz...@gmail.com 
 mailto:moz...@gmail.com:
 
Thanks Alvaro, however, I do not think this is related to the dlr
type. Most of the time its working fine only couple of time we see
this. For example   there were 146 such occurrence out of 28580
where we got this error which is about 5% of the total SMS sent on
that day.
 
[kannel]# cat gateway.log |grep 2015-08-14|grep -c got DLR but
could not find message
146
 
[kannel]# cat access.log|grep 2015-08-14|grep -c Sent
28580
 
Perhaps the final DLR is not reach in due time and causing this.
Is there anyway to fine tune this with a configuration change?
 
 
 Hi. Do you send multipart MT? Kannel only asks for DLR for the first part of 
 the MT, but many SMSC operators sending for all parts DLR reports that's why 
 you might be getting such errors in your error log.
 
 You can check by sending multipart message (for coding=0 it would be more 
 than 140 symbols or for coding=2 70).
 
 
 
 
On 8/14/2015 7:39 PM, Alvaro Cornejo wrote:
 
Hi
 
Check the format of dlr-id some smsc use hex and some dec.
Adjust kannel config accordingly
 
I think the parameter to adjust is dlr-type
 
Regards
 

 |-|
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.com
http://www.perusms.com http://www.perusms.com
 
 
On Fri, Aug 14, 2015 at 8:48 AM, Moazzam moz...@gmail.com
mailto:moz...@gmail.com mailto:moz...@gmail.com
mailto:moz...@gmail.com wrote:
 
Hi,
 
I have a production kannel v1.4.4 instance running with
sqlbox and
opensmppbox  along with mysql as DLR storage. So far so
good but
I am facing an issue with the DLR where DLR are being
queued  and
strange error related to the message id  destination is
appearing
the the gateway log as below. Please advise how to get rid
of this
problem.
 
2015-06-23 01:33:00 [32056] [6] DEBUG: SMPP[crs]: Got PDU:
2015-06-23 01:33:00 [32056] [6] DEBUG: SMPP PDU
0x7fceba10 dump:
2015-06-23 01:33:00 [32056] [6] DEBUG:  type_name: deliver_sm
2015-06-23 01:33:00 [32056] [6] DEBUG:  command_id: 5 =
0x0005
2015-06-23 01:33:00 [32056] [6] DEBUG:  command_status: 0 =
0x
2015-06-23 01:33:00 [32056] [6] DEBUG:  sequence_number: 2 =
0x0002
2015-06-23 01:33:00 [32056] [6] DEBUG:  service_type: NULL
2015-06-23 01:33:00 [32056] [6] DEBUG:  source_addr_ton: 1 =
0x0001
2015-06-23 01:33:00 [32056] [6] DEBUG:  source_addr_npi: 1 =
0x0001
2015-06-23 01:33:00 [32056] [6] DEBUG:  source_addr:
2xxx
2015-06-23 01:33:00 [32056] [6] DEBUG:  dest_addr_ton: 5 =
0x0005
2015-06-23 01:33:00 [32056] [6] DEBUG:  dest_addr_npi: 0 =
0x
2015-06-23 01:33:00 [32056] [6] DEBUG:  destination_addr:
Zx
2015-06-23 01:33:00 [32056] [6] DEBUG:  esm_class: 4 =
0x0004
2015-06-23 01:33:00 [32056] [6] DEBUG:  protocol_id: 0 =
0x
2015-06-23 01:33:00 [32056] [6] DEBUG:  priority_flag: 0 =
0x
2015-06-23 01:33:00 [32056] [6] DEBUG:
schedule_delivery_time: NULL
2015-06-23 01:33:00 [32056] [6] DEBUG:  validity_period: NULL
2015-06-23 01:33:00 [32056] [6] DEBUG:
registered_delivery: 0 =
0x
2015-06-23 01:33:00 [32056] [6] DEBUG:
replace_if_present_flag: 0
= 0x
2015-06-23 01:33:00 [32056] [6] DEBUG:  data_coding: 0 =
0x
2015-06-23 01:33:00 [32056] [6] DEBUG:  sm_default_msg_id: 0 =
0x
2015-06-23 01:33:00 [32056] [6] DEBUG:  sm_length: 112 =
0x0070
2015-06-23 01:33:00 [32056] [6] DEBUG:  short_message:
2015-06-23 01:33:00 [32056] [6] DEBUG:Octet string at
0x7fceb0001110:
2015-06-23 01:33:00 [32056] [6] DEBUG: 

Re: ESME - Opensmppbox - Kannel - SMSC Encoding problem

[Alexander Malysh]

Hi Yegor,

as far as I understood your issue, you have just to use data_coding=0x08 on 
ESME side and encode msg body to UCS2.

Alex

 Am 21.05.2015 um 12:06 schrieb Yegor Ivaschenko 
 yegor_ivasche...@exigenebit.com:
 
 Dear, Aurel.
 Thank you for your quick reply.
 I don't really sure want I should do next. Answer to you directly or maybe 
 only to users@kannel or both.
 Teach me the procedure.
 
 Anyway, I did a lot of testing of my ESME behaviour.
 It has web interface, message input box and status bar which indicates how 
 many characters entered and upper limit for current message. (i.e.  5 / 140 
 )
 As I know,
 
 UTF-16 (16-bit Unicode Transformation Format) is a character encoding capable 
 of encoding all 1,112,064 possible characters in Unicode. The encoding is 
 variable-length, as code points are encoded with one or two 16-bit code units.
 UTF-16 developed from an earlier fixed-width 16-bit encoding known as UCS-2 
 (for 2-byte Universal Character Set) once it became clear that a fixed-width 
 2-byte encoding could not encode enough characters to be truly universal. 
 (http://en.wikipedia.org/wiki/UTF-16).
 
 So UCS-2 is always fixed 16-bit encoding.
 Also UCS-2 is always BE. This is what wiki says:
 
 UCS-2 encoding is defined to be big-endian only. In practice most software 
 defaults to little-endian,[citation needed 
 http://en.wikipedia.org/wiki/Wikipedia:Citation_needed] and handles a 
 leading BOM to define the byte order just as in UTF-16. Although the similar 
 designations UCS-2BE and UCS-2LE imitate the UTF-16 labels, they do not 
 represent official encoding schemes. (http://en.wikipedia.org/wiki/UTF-16)
 
 Well, when I enter in my ESME something like this: asdfÆäæë  (which are 
 actually characters from ISO8859-1 chars table) it shows in status bar 
 (9/140). When I send it to opensmppbox, with wireshark analysis I can see, 
 that it uses 1 byte per character encoding.
 So It can't be UCS-2 or UTF-16. It's definitely latin-1 (or some other of 
 ISO-8859 family).
 
 When I add some non-latin-1 character (like russian ф or japanese テ (te)) 
 asdfÆäæë фテstatus bar of ESME's message input box changes upper limit to 
 70. In wireshark dump I can see, that message send to opensmppbox has leading 
 FF FE character which leads to LE encoding. Each character encoded with 2 
 bytes. 
 So again, it's not UCS-2 (which, according to standard have to be Big Endian 
 w/o BOM). It's either UTF-16 LE or non official UCS-2.
 
 So my ESME actually uses two encoding schemes depending on message itself. If 
 needed I can provide dumps and logs.
 
 So one more time, SMSC need only pure UCS-2 (or UTF-16 BE w/o BOM). My ESME 
 sends messages using ISO-8859-(1) and UTF-16 LE.
 My question is : Is there any way to cast all messages going from ESME to 
 UTF-16 BE encoding by means of Kannel or some additional software in pair 
 with Kannel?
 
 
 By the way, can you tell me were is that ticket considering this problem.
 Maybe I can help by providing further information like wireshark dump, kannel 
 logs and configs etc.
 
 
 Best regards,
 Ivashchenko Yegor
 差出人: Aurel Branzeanu branzeanu.au...@gmail.com
 送信日時: 2015年5月21日 0:54
 宛先: Yegor Ivaschenko
 CC: users@kannel.org
 件名: Re: ESME - Opensmppbox - Kannel - SMSC Encoding problem
  
 Hello, Yegor!
 
 On Wed, May 20, 2015 at 4:30 PM, Yegor Ivaschenko 
 yegor_ivasche...@exigenebit.com mailto:yegor_ivasche...@exigenebit.com 
 wrote:
 My ESME, based on characters used in message use 2 encoding type.
 
 I think it does not use 2 encodings, but just UCS-2, whose latin part matches 
 ISO8859-1
 
 There is, however, a very nasty bug when receiving messages to opensmppbox in 
 UCS-2 (data_coding = 8) and using two alphabets, say, english and russian - I 
 will submit a bug-report right now.
 
 --
 Sincerely yours,
 
 Aurel Branzeanu,
 
 mailto: branzeanu.au...@gmail.com mailto:branzeanu.au...@gmail.com
 Skype: tvorogov
 GSM Orange:  +373 6 940-7700
 GSM Moldcell: +373 7 940-7700
 

Re: Mutli DB support for DLR entries in failover mode

[Alexander Malysh]

Hi,

for this purpose usually used shared virtual IP for DBs with a heartbeat or you 
can try to use haproxy in tcp mode.

Alex

Am 30.09.2014 um 08:18 schrieb Husnain Taseer husnain.tas...@gmail.com:

 Dear Kannel Users,
 
 I want to connect multiple databases with single Kannel instance to record 
 DLR data in failover mode. if one database is down then kannel should start 
 inserting data in 2nd database. Is there any patch available to achieve this 
 functionality please also advise if any other method can be used to do this.
 
 
 
 Regards,
 Husnain Taseer
  

Re: Dynamic submit_sm.service_type

[Alexander Malysh]

Hi,

yes, you can. Look in user guide for binfo parameter.

Alex

Am 12.09.2014 um 12:21 schrieb Niel Smith daniel.alfred.sm...@gmail.com:

 Hi all,
 
 Is it possible to, on the fly, specify the value for the service type using 
 /cgi-bin/sendsms? I've been searching around without any luck.
 
 According to the kannel documentation, it's possible to configure a static 
 service type inside a smsc group.
 
 service-typestring Optional; if specified, sets the service type for 
 the SMSC. If unset, the default service type is used. This may be used to 
 influence SMS routing (for example). The SMSC operator may also refer to this 
 as the profile ID. The maximum length of the service type is 6, according 
 to the SMPP specification v3.4. Defined values are: CMT (cellular 
 messaging), CPT (cellular paging), VMN (voice mail notification), VMA 
 (voice mail alerting), WAP (wireless application protocol), USSD 
 (unstructured supplementary services data), CBS (cell broadcast service) 
 and GUTS (generic UDP transport service). Other values may be defined 
 mutually between the SMSC and the ESME application. 
 
 Thanks!
 

Re: Kannel Multiple DB connection

[Alexander Malysh]

Hi,

you can try to configure CNAME in DNS and put two IPs in round robin manner.
Then configure mysql connection with at least 2 connections and you should have
2 connections to different nodes.

Alex


Am 03.06.2014 um 11:23 schrieb Abdul Basit basit.e...@gmail.com:

 Hi, smii
 
 Thank you for prompt reply. 
 
 This is one way. right!
 
 But my architecture is using two Mysql master nodes in parallel so i don't 
 have one virtual IP or floating IP.
 Instead i have two DB IPs. 
 
 Is there any way to open two DB connections on different IPs?
 
 
 --
 regards,
 
 abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445
 
 
 On Tue, Jun 3, 2014 at 4:02 PM, smii saber saber.s...@gmail.com wrote:
 Hi Abdul basit
 Normally in the mysql-connection group you have to configure the  host ip 
 adresse of your mysql db, so:
 1- you install you db cluser system 
 2- configure the virtual ip on the  host ip adresse of your mysql in kannel 
 configuration file
 
 group = mysql-connection
 id = mydlr
 host = virtual ip adress of your db nodes
 username = foo
 password = bar
 database = dlr
 max-connections = 1
 
 
 2014-06-03 9:37 GMT+01:00 Abdul Basit basit.e...@gmail.com:
 
 Dear Team,
 
 I am using kannel for SMPP connectivity and storing DLR in mysql DB.
 
 Now working on a scalable solution using Mysql multi-master setup. 
 Currently Kannel connect to only 1 DB server for DLR storage.
 
 Is there any way that i can configure kannel for multiple master DB servers 
 (either in load balance mode or in failover manner)?
 
 Looking forward for suggestions.
 
 --
 regards,
 
 abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445
 
 

Re: Redis delivery report DLR backend

[Alexander Malysh]

Hi,

Lorenzo your account on redmine activated now and email configuration error in 
redmine fixed.

Alex

Am 13.03.2014 um 17:15 schrieb spameden spame...@gmail.com:

 Forwarding to devel-list, hopefully someone would check and copying Alexander.
 
 
 2014-03-13 17:10 GMT+04:00 Lorenzo Bagni ba...@networkweb.net:
 Hi,
 I've found the problem under redis backend crash.
 My dlr-url ( 
 http://my.fqdn.name/DlrManager.aspx31oa=%pda=%Psmsc=%idlrtype=%ddetail=%atempo=%Tid=%idelr=%Auser=%nforeign=%Fidgen=0|1|2|3|4|5|6
  ) contais many parameters with values as %[char], some of this broke 
 /usr/bin/bearerbox, some not but store on Redis backend different values:
 %p %P %T %n = PANIC
 %a is soted as 0x0.07f1160003b48p-1022
 %A is soted as 0x0.07f1160003b48p-1022
 %F is soted as 0.00
 %i is soted as 378
 %d is soted as 378
 
 The dlr-url is passed is urlencoded, so I guess the issue is when the bearer 
 decode and evaluate per params sent to http://kannel-ip:13013/cgi-bin/sendsms.
 
 Last thing, I've tried to register under Kannel Redmine, but after 
 successully registration I cannot login because I've nevere recevied the 
 confirmation mail.
 For admins: could you kinldy check my account and unlock my account?
 
 Thanks in advance
 Bagni
 
 
 2014-03-12 16:06 GMT+01:00 Lorenzo Bagni ba...@networkweb.net:
 
 Hi,
 I've activated the REDIS_DEBUG but the HMSET command works on redis-cli, but 
 not with Kannel:
 bearerbox.log:
 2014-03-12 15:54:14 [30938] [8] DEBUG: DLR[redis]: Adding DLR 
 smsc=kannelfake, ts=8f3d43b4-f93c-4d8f-b681-35b658f74d90, src=51303, 
 dst=39328000, mask=31, boxc=
 2014-03-12 15:54:14 [30938] [8] DEBUG: Adding DLR into keystore
 2014-03-12 15:54:14 [30938] [8] DEBUG: redis cmd: HMSET 
 dlr:kannelfake:8f3d43b4-f93c-4d8f-b681-35b658f74d90:4677782 smsc kannelfake 
 ts 8f3d43b4-f93c-4d8f-b681-35b658f74d90 source 51303 destination 
 39328 service user_mobyt_fake url 
 http://my.fqdn.name/DlrManager.aspx31oa=%pda=%Psmsc=%idlrtype=%ddetail=%atempo=%Tid=%idelr=%Auser=%nforeign=%Fidgen=0|1|2|3|4|5|6
  mask _NULL_ boxc ? status 0
 2014-03-12 15:54:14 [30938] [8] PANIC: /usr/sbin/bearerbox() [0x4a810c]
 2014-03-12 15:54:14 [30938] [8] PANIC: /lib64/libpthread.so.0(+0xf710) 
 [0x7f3d26ec0710]
 2014-03-12 15:54:14 [30938] [8] PANIC: /usr/sbin/bearerbox() [0x48d431]
 2014-03-12 15:54:14 [30938] [8] PANIC: /usr/sbin/bearerbox() [0x41fa63]
 2014-03-12 15:54:14 [30938] [8] PANIC: 
 /usr/sbin/bearerbox(dlr_add_real+0x3a3) [0x41cf63]
 2014-03-12 15:54:14 [30938] [8] PANIC: /usr/sbin/bearerbox() [0x457b7f]
 2014-03-12 15:54:14 [30938] [8] PANIC: 
 /usr/sbin/bearerbox(smscconn_send+0x5f) [0x42406f]
 2014-03-12 15:54:14 [30938] [8] PANIC: /usr/sbin/bearerbox(smsc2_rout+0x428) 
 [0x417f68]
 2014-03-12 15:54:14 [30938] [8] PANIC: /usr/sbin/bearerbox() [0x418e1d]
 2014-03-12 15:54:14 [30938] [8] PANIC: /usr/sbin/bearerbox() [0x491da9]
 2014-03-12 15:54:14 [30938] [8] PANIC: /lib64/libpthread.so.0(+0x79d1) 
 [0x7f3d26eb89d1]
 2014-03-12 15:54:14 [30938] [8] PANIC: /lib64/libc.so.6(clone+0x6d) 
 [0x7f3d25c50b6d]
 
 Any clue for this?
 Thanks in advance
 Bagni
 
 
 2014-03-06 12:37 GMT+01:00 Lorenzo Bagni ba...@networkweb.net:
 
 Hi all,
 I'm facing a blocking problem on redis backend for delivery report.
 I'm sendig correctly (and receive on my MT) but the bearerbox hangs when try 
 to write on redis:
 
 smsc log:
 2014-03-06 11:44:54 [25724] [7] DEBUG: SMPP[mobytusaprod]: Got PDU:
 2014-03-06 11:44:54 [25724] [7] DEBUG: SMPP PDU 0x7f6c08000a10 dump:
 2014-03-06 11:44:54 [25724] [7] DEBUG:   type_name: submit_sm_resp
 2014-03-06 11:44:54 [25724] [7] DEBUG:   command_id: 2147483652 = 0x8004
 2014-03-06 11:44:54 [25724] [7] DEBUG:   command_status: 0 = 0x
 2014-03-06 11:44:54 [25724] [7] DEBUG:   sequence_number: 2 = 0x0002
 2014-03-06 11:44:54 [25724] [7] DEBUG:   message_id:
 2014-03-06 11:44:54 [25724] [7] DEBUG:Octet string at 0x7f6c080011a0:
 2014-03-06 11:44:54 [25724] [7] DEBUG:  len:  36
 2014-03-06 11:44:54 [25724] [7] DEBUG:  size: 37
 2014-03-06 11:44:54 [25724] [7] DEBUG:  immutable: 0
 2014-03-06 11:44:54 [25724] [7] DEBUG:  data: 37 35 33 31 62 34 32 61 2d 
 66 34 34 66 2d 34 33   7531b42a-f44f-43
 2014-03-06 11:44:54 [25724] [7] DEBUG:  data: 38 31 2d 39 63 35 61 2d 36 
 31 37 65 32 32 33 31   81-9c5a-617e2231
 2014-03-06 11:44:54 [25724] [7] DEBUG:  data: 36 30 35 63 
   605c
 2014-03-06 11:44:54 [25724] [7] DEBUG:Octet string dump ends.
 2014-03-06 11:44:54 [25724] [7] DEBUG: SMPP PDU dump ends.
 2014-03-06 11:44:54 [25724] [7] DEBUG: new group created `smpp'
 2014-03-06 11:44:54 [25724] [7] DEBUG: group=`smpp' key=`mobyt_campaignid' 
 value=`1245'
 2014-03-06 11:44:54 [25724] [7] DEBUG: DLR[redis]: Adding DLR 
 smsc=mobytusaprod, ts=7531b42a-f44f-4381-9c5a-617e2231605c, src=51303, 
 dst=393284677782, mask=31, boxc=
 2014-03-06 11:44:54 [25724] [7] DEBUG: Adding DLR into keystore
 
 bearerbox log:
 

Re: Which version for production usage?

[Alexander Malysh]

Hi Samuel,

I would suggest to use SVN trunk, we consider it as stable.

Alex

Am 24.01.2014 um 11:39 schrieb Samuel Fornes samuel_is_k...@hotmail.com:

 Hi!
  
 We are looking into Kannel for a project we are launching. As we investigated 
 Kannel we noticed that the frontpage of the website hasn’t been updated in a 
 while, but there seems to have been quite a bit of activity in the repos.
  
 Hence, we’d like to ask, which version of Kannel should we choose for running 
 stable production servers?
  
 The one announced on the website
 Some version from the repos
 Latest commit from the repos
  
 I’d like to also extend a thanks to the core devs for making Kannel available 
 to everyone. Great job!
  
 Kind regards,
  
 Samuel F.

Re: Setting Throughput On fly

[Alexander Malysh]

Hi,

this is not possible.

Alex

Am 08.12.2013 um 11:17 schrieb Sayed Hadi Rastgou Haghi 
hadi.rast...@gmail.com:

 Dear all,
 
 Is it possible to set throughput for a smsc connection on fly ?
 
 -- 
 Sincerely,
 
 Sayed Hadi Rastgou Haghi

Re: Kannel Blacklist Feature

[Alexander Malysh]

Hi,

this is not really true. Kannel has Blacklist feature and you don't have to 
adjust kannel config any time.
Kannel make HTTP call to get blacklist and you can reload the list on the fly 
via HTTP call (see reload lists http admin command).

Alex

Am 07.12.2013 um 19:01 schrieb spameden spame...@gmail.com:

 Yes, kannel have such feature.
 
 But it's not really convinient to use it, because you have to adjust config 
 files each time and reload kannel completely.
 
 Better handle this on your application (e.g. your script) and also add 
 captcha to make sure it's not bots sending messages.
 
 
 2013/12/7 Faizan Mirza efuz...@gmail.com
 Hello,
 
 I am allowing users to send Free SMS to local country numbers but some people 
 as you know abuse and send bad messages to others so before they complain we 
 monitor and blacklist recipient number so he/she wont receive any message so 
 how to apply blacklist numbers for outgoing messages please help...
 
 

Re: Priority parameter on sendsms, is it used?

[Alexander Malysh]

Hi,

Kannel SVN is production ready even more as 1.4.3 

Alex

Am 26.11.2013 um 09:42 schrieb Paulo Correia paulo.corr...@pdmfc.com:

 Hi Alex,
 
 Thank you for the reply.
 
 Is kannel 1.5.X or SVN versions production ready? We are processing around 
 10M SMS/month and we cannot change unless the new version is production ready.
 
 Best regards,
 Paulo Correia
 
 Em 25-11-2013 11:00, Alexander Malysh escreveu:
 Hi,
 
 use kannel SVN or at least 1.5.X where priority queue implemented.
 
 Alex
 
 Am 21.11.2013 um 11:46 schrieb Paulo Correia paulo.corr...@pdmfc.com:
 
 Hi all!
 
 Again I have the same situation:
 More than 20K messages pending:
 curl -s 'http://kannel-host:kannel-port/store-status?password=*' | 
 wc -l
 29291
 Most of the pending messages were submitted with priority=0
 One of the messages sent to kannel with priority=2 and is still pending 
 after 45minutes ... it should have been sent before the others
 Is there a way to resolve this?
 I'm using kannel-1.4.3: bearerbox and smsbox (no sqlbox) with spool storage.
 
 Any help is appreciated!
 
 Best regards,
 Paulo Correia
 
 On 18-11-2013 09:39, Paulo Correia wrote:
 Hi again! 
 
 Has anyone ever experienced strange behaviour with priorities on kannel 
 1.4.3 for large amount of messages? 
 In this case we are just using smsbox and bearerbox and for large amounts 
 of messages (over 100/second and over 20K messages) we tend to get most in 
 the spool and the priorities seem to be changed. 
 
 Best regards, 
 Paulo Correia 
 
 Em 06-11-2013 12:14, Paulo Correia escreveu: 
 Hi! 
 
 I'm having some trouble with the priority parameter of the sendsms not 
 being respected on kannel 1.4.3. 
 
 If I send a large ammount of messages to kannel with sendsms, let's say 
 around 2, most of them with priorities 0 or 1, and in the middle of 
 them I send some other messages with priorities 2 or 3, I tippically get 
 some of the messages with higher priority being held back, waiting for 
 some lower priority messages to be sent to the SMSC. 
 
 The SMSC used is EMI/UCP. 
 
 Is this the normal behaviour? Is there a way to make the messages with 
 higher priority to be sent before the others? 
 
 Thanks in advance. 
 
 Best regards, 
 Paulo Correia 
 
 
 
 
 
 
 

Re: Priority parameter on sendsms, is it used?

[Alexander Malysh]

Hi,

use kannel SVN or at least 1.5.X where priority queue implemented.

Alex

Am 21.11.2013 um 11:46 schrieb Paulo Correia paulo.corr...@pdmfc.com:

 Hi all!
 
 Again I have the same situation:
 More than 20K messages pending:
 curl -s 'http://kannel-host:kannel-port/store-status?password=*' | wc 
 -l
 29291
 Most of the pending messages were submitted with priority=0
 One of the messages sent to kannel with priority=2 and is still pending after 
 45minutes ... it should have been sent before the others
 Is there a way to resolve this?
 I'm using kannel-1.4.3: bearerbox and smsbox (no sqlbox) with spool storage.
 
 Any help is appreciated!
 
 Best regards,
 Paulo Correia
 
 On 18-11-2013 09:39, Paulo Correia wrote:
 Hi again! 
 
 Has anyone ever experienced strange behaviour with priorities on kannel 
 1.4.3 for large amount of messages? 
 In this case we are just using smsbox and bearerbox and for large amounts of 
 messages (over 100/second and over 20K messages) we tend to get most in the 
 spool and the priorities seem to be changed. 
 
 Best regards, 
 Paulo Correia 
 
 Em 06-11-2013 12:14, Paulo Correia escreveu: 
 Hi! 
 
 I'm having some trouble with the priority parameter of the sendsms not 
 being respected on kannel 1.4.3. 
 
 If I send a large ammount of messages to kannel with sendsms, let's say 
 around 2, most of them with priorities 0 or 1, and in the middle of 
 them I send some other messages with priorities 2 or 3, I tippically get 
 some of the messages with higher priority being held back, waiting for some 
 lower priority messages to be sent to the SMSC. 
 
 The SMSC used is EMI/UCP. 
 
 Is this the normal behaviour? Is there a way to make the messages with 
 higher priority to be sent before the others? 
 
 Thanks in advance. 
 
 Best regards, 
 Paulo Correia 
 
 
 
 
 

Re: Allowed-prefix vs Denied-prefix

[Alexander Malysh]

Hi,

please use users@kannel.org, forwarding...

Alex

Am 06.09.2013 um 13:01 schrieb Anshul Jain anshul.j...@mahindracomviva.com:

 Hi Kannel Team,
  
 Thanks in Advance for your help.
  
 I want to block my kannel to push SMS to a particular series..  I am using 
 2.5.1 version of bearerbox. I tried to use below configurations but still my 
 kannel is pushing sms on denied series. Request your help to catch my mistake 
 to correct my configuration
  
 Core-Bearer bearerbox version `2.5.1'.
 System Linux, release 2.6.18-238.el5, version #1 SMP Sun Dec 19 14:22:44 EST 
 2010, machine x86_64.
  
 group = core
 admin-port = 15214
 smsbox-port = 15215
 admin-password = bar
 log-level = 0
 log-file = /mmoneyvar/mmoney_smsclogs/gateway_event.log
 access-log = /mmoneyvar/mmoney_smsclogs/gateway_access.log
  
 ##start newbulk##
 group = smsc
 smsc = smpp
 smsc-id = smsc
 host = 10.100.60.123
 port = 31110
 receive-port = 0
 system-type = mcom
 smsc-username = mcom
 smsc-password = mcom
 address-range = 
 transceiver-mode =  false
 interface-version = 34
 keepalive = 2
 #max-pending-submits = 5
 source-addr-autodetect = true
 #source-addr-ton = 4
 #source-addr-npi = 1
 dest-addr-ton = 3
 dest-addr-npi = 9
 msg-id-type = 0x01
 reconnect-delay=1
 allowed-prefix = +23480;23480;0023480
 denied-prefix = +23470;0023470
 ##end newbulk##
  
 Here i want to block SMS to series starting from (234)70, 234 here is country 
 code. Humble request if you can help me troubleshooting it.
  
 Thanks and Regards
  
 Anshul Jain| Global Projects Delivery | India: + 91 98-999-81631(SMS) | 
 Nigeria :- +234-7011955229
 A-26, Info City | Sector 34, Gurgaon 122001 | Haryana, India | T: +91 124 481 
 9000 | F: +91 124 481 9777 | www.mahindracomviva.com
 image001.jpg
 We are now Mahindra Comviva
  
 This e-mail and all material transmitted with it are for the use of the 
 intended recipient(s) ONLY and contains confidential and/or privileged 
 information. If you are not the intended recipient, please contact the sender 
 by reply e-mail and destroy all copies and the original message. Any 
 unauthorized review, use, disclosure, dissemination, forwarding, printing or 
 copying of this email or any action taken pursuant to the contents of the 
 present e-mail is strictly prohibited and is unlawful. The recipient 
 acknowledges that Comviva Technologies Limited or its management or 
 directors, are unable to exercise control or ensure the integrity over /of 
 the contents of the information contained in e-mail. Any views expressed 
 herein are those of the individual sender only and no binding nature of the 
 contents shall be implied or assumed unless the sender does so expressly with 
 due authority of Comviva Technologies Limited. E-mail and any contents 
 transmitted with it are prone to viruses and related defects despite all 
 efforts to avoid such by Comviva Technologies Limited.
 This e-mail and all material transmitted with it are for the use of the 
 intended recipient(s) ONLY and contains confidential and/or privileged 
 information. If you are not the intended recipient, please contact the sender 
 by reply e-mail and destroy all copies and the original message. Any 
 unauthorized review, use, disclosure, dissemination, forwarding, printing or 
 copying of this email or any action taken pursuant to the contents of the 
 present e-mail is strictly prohibited and is unlawful. The recipient 
 acknowledges that Comviva Technologies Limited or its management or 
 directors, are unable to exercise control or ensure the integrity over /of 
 the contents of the information contained in e-mail. Any views expressed 
 herein are those of the individual sender only and no binding nature of the 
 contents shall be implied or assumed unless the sender does so expressly with 
 due authority of Comviva Technologies Limited. E-mail and any contents 
 transmitted with it are prone to viruses and related defects despite all 
 efforts to avoid such by Comviva Technologies Limited.

Re: SMPP Asynchronous mode

[Alexander Malysh]

Hi,

kannel can handle this but you should not set max-pending-submits to high 
because it can finish in double delivery
if connection interrupt in the middle.

Alex

Am 05.08.2013 um 11:32 schrieb [Digital^Dude] ® millennium@gmail.com:

 Hi,
 
 look at max-pending-submits.
 
 Assuming the operator delivers sms without problems with delay of 
 submit_sm_resp, I was just wondering how kannel would behave if 
 max-pending-submits is more than 200...
 Alex
 
 Am 01.08.2013 um 20:02 schrieb [Digital^Dude] ® millennium@gmail.com:
 
 Hello,
 
 I happened to take a tcpdump of my kannel smpp connection with a telco. 
 Every submit_sm was followed by a submit_sm_resp. It seemed like kannel 
 operating in synchronous mode I fear that the outbound throughput is 
 adversely affected by the submit_sm waiting for a submit_sm_resp and not 
 immediately sending a burst of submit_sm at once.
 
 Any hints how I can forcefully make it go async?
 
 --
 Thanks.
 
 

Re: SMPP Asynchronous mode

[Alexander Malysh]

Hi,

look at max-pending-submits.

Alex

Am 01.08.2013 um 20:02 schrieb [Digital^Dude] ® millennium@gmail.com:

 Hello,
 
 I happened to take a tcpdump of my kannel smpp connection with a telco. Every 
 submit_sm was followed by a submit_sm_resp. It seemed like kannel operating 
 in synchronous mode I fear that the outbound throughput is adversely 
 affected by the submit_sm waiting for a submit_sm_resp and not immediately 
 sending a burst of submit_sm at once.
 
 Any hints how I can forcefully make it go async?
 
 --
 Thanks.

Re: SMS with question mark ?

[Alexander Malysh]

 Hi,
 
 ok here is your error because you didn't encode metadata value:
 
 ?smpp?message_payload=[QAR4]SONAR To unsub send STOP 00 to 
 0###http://XXX.XXX.com:8080/sms/qadl.php?id=1976568
 
 should be:
 
 ?URLENCODE(smpp)?URLENCODE(message_payload)=URLENCODE([QAR4]SONAR To unsub 
 send STOP 00 to 0###http://XXX.XXX.com:8080/sms/qadl.php?id=1976568)
 
 -- result
 ?smpp?message_payload=%5BQAR4%5DSONAR+To+unsub+send+STOP+00+to+0%23%23%23http%3A%2F%2FXXX.XXX.com%3A8080%2Fsms%2Fqadl.php%3Fid%3D1976568
 
 Am 18.07.2013 um 10:46 schrieb Mohammad Ali Alfarra 
 mohammad.alfa...@info2cell.com:
 
 Hi All,
 
 Thanks all for your answers.
 
 Alexander, my Kannel version is 1.5.
 
 Rene, I'll try to urlencoding twice today.
 
 Mohammed, URL hited as XML POST, please find one example below:
 
 2013-07-16 09:31:25 [3873] [3] INFO: smsbox: Got HTTP request 
 /cgi-bin/sendsms from 127.0.0.1
 2013-07-16 09:31:25 [3873] [3] DEBUG: XMLParsing: XML: ?xml 
 version=1.0?messagesubmit
 danumberX/number/daoanumberX/number/oa   
  dcscoding0/coding/dcsfrom
 usernameX/usernamepasswordX/password
 binfo/binfo/from
 meta-data?smpp?message_payload=[QAR4]SONAR To unsub send STOP 00 to 
 0###http://XXX.XXX.com:8080/sms/qadl.php?id=1976568/meta-data
 statusrequestdlr-mask31/dlr-mask
 dlr-urlhttp://127.0.0.1/cgi-bin/kannel/kannel_dlr/dlr_handler.php?smsc_id=%iamp;msg_id=179775714amp;to=Xamp;state=%damp;response=%Aamp;sender=X/dlr-url
 /statusrequest/submit/message
 2013-07-16 09:31:25 [3873] [3] INFO: sendsms used by kannel
 2013-07-16 09:31:25 [3873] [3] INFO: sendsms sender:kannel:X 
 (127.0.0.1) to:multi-cast msg:
 2013-07-16 09:31:25 [3873] [3] DEBUG: Stored UUID 
 e8649745-0af2-47d6-a470-5de5fe61ee9a
 2013-07-16 09:31:25 [3873] [3] DEBUG: message length 0, sending 1 messages
 2013-07-16 09:31:25 [3873] [3] DEBUG: Status: 202 Answer: Sent.
 
 Emeric, I use ASCII if you notice the config.
 
 Sincerely
 --
 Mohammad Ali Alfarra 
 System Administrator (RHCSS, RHCE, LPI-2, LPI-1, MCITP, MCSE)
 Support Mob: +962797062851
 Email: mohammad.alfa...@info2cell.com
 
 
 On Thu, Jul 18, 2013 at 4:12 AM, emeric kamleu kaml...@yahoo.fr wrote:
 Just encode your app files to ANSI or UTF-8. You can use Notepad++ and 
 convert them directly in ANSI or UTF-8.
 
 
 De : Rene Kluwen rene.klu...@chimit.nl
 À : 'Mohammad Ali Alfarra' mohammad.alfa...@info2cell.com; 'spameden' 
 spame...@gmail.com 
 Cc : users@kannel.org 
 Envoyé le : Mercredi 17 juillet 2013 19h34
 Objet : RE: SMS with question mark ?
 
 Try urlencoding it twice. So a question mark will look like %253F.
  
 From: users [mailto:users-boun...@kannel.org] On Behalf Of Mohammad Ali 
 Alfarra
 Sent: woensdag 17 juli 2013 15:47
 To: spameden
 Cc: users@kannel.org
 Subject: Re: SMS with question mark ?
  
 yes I'm sure we use urlencode the ? also we use another special characters 
 in the same message but it's complain about ? and =
 We got this error on smsc logs.
 
 2013-07-16 09:29:25 [21294] [41] DEBUG: new group created `smpp'
 2013-07-16 09:29:25 [21294] [41] DEBUG: group=`smpp' key=`message_payload' 
 value=`[QAR4]SONAR To unsub send STOP 00 to 
 0###http://XXX.XXX.com:8080/sms/qadl.php'
 2013-07-16 09:29:25 [21294] [41] ERROR: MDATA: Found '=' but not expected it 
 end=-1 start=113 type=0.
 I changed some data on the above log to 0 or X.
 
 Sincerely
 --
 Mohammad Ali Alfarra 
 System Administrator (RHCSS, RHCE, LPI-2, LPI-1, MCITP, MCSE)
 Support Mob: +962797062851
 Email: mohammad.alfa...@info2cell.com
  
 On Wed, Jul 17, 2013 at 4:18 PM, spameden spame...@gmail.com wrote:
 are you sure you did urlencode '?' ?
 
 it should look like this (single ? sign):
 
 %3F
  
 2013/7/17 Mohammad Ali Alfarra mohammad.alfa...@info2cell.com
 Dears,
 Problem is:
 We're trying to send URL over SMS but the problem is that we use question 
 mark ? on the URL, so whenever we send an MT we got an ERROR on SMSC logs 
 and the message will delivered to the client empty.
 Config:
 
 SMSC
 group = smsc
 smsc = smpp
 interface-version = 34
 smsc-id = testoperator
 connect-allow-ip = 127.0.0.1
 allowed-smsc-id = testoperator
 log-file = /var/log/kannel1.5/smsc/testoperator_smsc.log
 log-level = 0
 host = X.X.X.X
 port = 1
 transceiver-mode = true
 smsc-username = User
 smsc-password = Pass
 system-type = NULL
 enquire-link-interval = 60
 source-addr-ton = 5
 source-addr-npi = 0
 dest-addr-ton = 1
 dest-addr-npi = 1
 validityperiod = 1440
 alt-charset = ASCII
 
 We have TLV for this SMSC connection:
 group = smpp-tlv
 name = message_payload
 #AS PER SMPP SPEC:
 tag = 0x0424
 #AS PER SMPP SPEC:
 type = octetstring
 length = 65536
 smsc-id = testoperator
 Logs:
  
 SMSC:
 
 2013-07-11 10:06:16 [21294] [41] DEBUG: SMPP[qtelcgw]: Sending PDU:
 2013-07-11 10:21:07 [21294] [41] DEBUG: SMPP PDU 0x6bef4c40 dump:
 2013-07-11 

Re: SMS with question mark ?

[Alexander Malysh]

Hi,

which Kannel version are you using?

Alex

Am 17.07.2013 um 15:46 schrieb Mohammad Ali Alfarra 
mohammad.alfa...@info2cell.com:

 yes I'm sure we use urlencode the ? also we use another special characters in 
 the same message but it's complain about ? and =
 
 We got this error on smsc logs.
 
 2013-07-16 09:29:25 [21294] [41] DEBUG: new group created `smpp'
 2013-07-16 09:29:25 [21294] [41] DEBUG: group=`smpp' key=`message_payload' 
 value=`[QAR4]SONAR To unsub send STOP 00 to 
 0###http://XXX.XXX.com:8080/sms/qadl.php'
 2013-07-16 09:29:25 [21294] [41] ERROR: MDATA: Found '=' but not expected it 
 end=-1 start=113 type=0.
 
 I changed some data on the above log to 0 or X.
 
 Sincerely
 --
 Mohammad Ali Alfarra 
 System Administrator (RHCSS, RHCE, LPI-2, LPI-1, MCITP, MCSE)
 Support Mob: +962797062851
 Email: mohammad.alfa...@info2cell.com
 
 
 On Wed, Jul 17, 2013 at 4:18 PM, spameden spame...@gmail.com wrote:
 are you sure you did urlencode '?' ?
 
 it should look like this (single ? sign):
 
 %3F
 
 
 2013/7/17 Mohammad Ali Alfarra mohammad.alfa...@info2cell.com
 Dears,
 
 Problem is:
 We're trying to send URL over SMS but the problem is that we use question 
 mark ? on the URL, so whenever we send an MT we got an ERROR on SMSC logs 
 and the message will delivered to the client empty.
 
 Config:
 
 SMSC
 group = smsc
 smsc = smpp
 interface-version = 34
 smsc-id = testoperator
 connect-allow-ip = 127.0.0.1
 allowed-smsc-id = testoperator
 log-file = /var/log/kannel1.5/smsc/testoperator_smsc.log
 log-level = 0
 host = X.X.X.X
 port = 1
 transceiver-mode = true
 smsc-username = User
 smsc-password = Pass
 system-type = NULL
 enquire-link-interval = 60
 source-addr-ton = 5
 source-addr-npi = 0
 dest-addr-ton = 1
 dest-addr-npi = 1
 validityperiod = 1440
 alt-charset = ASCII
 
 We have TLV for this SMSC connection:
 group = smpp-tlv
 name = message_payload
 #AS PER SMPP SPEC:
 tag = 0x0424
 #AS PER SMPP SPEC:
 type = octetstring
 length = 65536
 smsc-id = testoperator
 
 Logs:
 
 SMSC:
 
 2013-07-11 10:06:16 [21294] [41] DEBUG: SMPP[qtelcgw]: Sending PDU:
 2013-07-11 10:21:07 [21294] [41] DEBUG: SMPP PDU 0x6bef4c40 dump:
 2013-07-11 10:21:07 [21294] [41] DEBUG:   type_name: submit_sm
 2013-07-11 10:21:07 [21294] [41] DEBUG:   command_id: 4 = 0x0004
 2013-07-11 10:21:07 [21294] [41] DEBUG:   command_status: 0 = 0x
 2013-07-11 10:21:07 [21294] [41] DEBUG:   sequence_number: 121883 = 0x0001dc1b
 2013-07-11 10:21:07 [21294] [41] DEBUG:   service_type: X
 2013-07-11 10:21:07 [21294] [41] DEBUG:   source_addr_ton: 5 = 0x0005
 2013-07-11 10:21:07 [21294] [41] DEBUG:   source_addr_npi: 0 = 0x
 2013-07-11 10:21:07 [21294] [41] DEBUG:   source_addr: X
 2013-07-11 10:21:07 [21294] [41] DEBUG:   dest_addr_ton: 1 = 0x0001
 2013-07-11 10:21:07 [21294] [41] DEBUG:   dest_addr_npi: 1 = 0x0001
 2013-07-11 10:21:07 [21294] [41] DEBUG:   destination_addr: XXX
 2013-07-11 10:21:07 [21294] [41] DEBUG:   esm_class: 3 = 0x0003
 2013-07-11 10:21:07 [21294] [41] DEBUG:   protocol_id: 0 = 0x
 2013-07-11 10:21:07 [21294] [41] DEBUG:   priority_flag: 0 = 0x
 2013-07-11 10:21:07 [21294] [41] DEBUG:   schedule_delivery_time: NULL
 2013-07-11 10:21:07 [21294] [41] DEBUG:   validity_period: 130712102107000+
 2013-07-11 10:21:07 [21294] [41] DEBUG:   registered_delivery: 1 = 0x0001
 2013-07-11 10:21:07 [21294] [41] DEBUG:   replace_if_present_flag: 0 = 
 0x
 2013-07-11 10:21:07 [21294] [41] DEBUG:   data_coding: 0 = 0x
 2013-07-11 10:21:07 [21294] [41] DEBUG:   sm_default_msg_id: 0 = 0x
 2013-07-11 10:21:07 [21294] [41] DEBUG:   sm_length: 0 = 0x
 2013-07-11 10:21:07 [21294] [41] DEBUG:   short_message: 
 2013-07-11 10:21:07 [21294] [41] DEBUG: SMPP PDU dump ends.
 
 Thanks in advance.
 
 Sincerely
 --
 Mohammad Ali Alfarra 
 System Administrator (RHCSS, RHCE, LPI-2, LPI-1, MCITP, MCSE)
 Support Mob: +962797062851
 Email: mohammad.alfa...@info2cell.com
 
 

Re: Kannel + OpenSMPP box

[Alexander Malysh]

Am 23.05.2013 um 19:21 schrieb spameden spame...@gmail.com:

 Unfortunately there is no solution.
 
 You can modify yourself source code to achieve it.
 
 Or you can look at the commercial SMPPBox, msg st...@tolj.org for details.

or msg to me :-)

 
 
 2013/5/23 Saju John s_j...@thuraya.com
 So, what is the solution ? Is there any queue or store can be 
 implemented/configured.
 
 Saju
  
 From: spameden [mailto:spame...@gmail.com] 
 Sent: Thursday, May 23, 2013 09:02 PM
 To: Saju John 
 Cc: Вадим Бажов mas...@remort.net; users@kannel.org users@kannel.org 
 Subject: Re: Kannel + OpenSMPP box 
  
 That's exactly what I've said to Vadim.
 
 
 2013/5/23 Saju John s_j...@thuraya.com
 Hello Spameden,
 
 it is not the opensmppbox is disconnected. But the client connection to the 
 opensmmpbox sometimes get connected. Possibly because of client connection 
 failure or the server maintenance at client site or internet disconnection.
 
 Saju
 
 From: spameden [spame...@gmail.com]
 Sent: Thursday, May 23, 2013 8:19 PM
 To: Вадим Бажов
 Cc: Saju John; users@kannel.org
 Subject: Re: Kannel + OpenSMPP box
 
 2013/5/23 Вадим Бажов mas...@remort.net
 why opensmppbox is disconnected? it should be always bounded with kannel. 
 you'll better start all the service using bearerbox masterservice. it'll run 
 kannel+all modules mentioned in kannel.conf such as opensmppbox, sqlbox if 
 present.
 
 It has nothing to do with opensmppbox disconnecting, you didnt understand 
 correctly what John said. 
 
 Client connected through OpenSMPPBox got disconnected, thats why MO was not 
 correctly routed.
 
 It's clearly a bug in OpenSMPPBox and should be fixed. (i.e. store 
 temporarily message in the kannel.store until client connects again).
 
 
 
 if your trouble is in ability to send more than one sms at the same moment, 
 because kannel is still working for the first sent sms by that time - 
 increase number of threads (it's 1 thread by default. i increased it up to 10 
 threads)
 
 23.05.2013 15:37, Saju John пишет:
 Hello All,
 
  
 I am using the kannel + opensmppbox for sending and receiving the message. 
 Kannel has multiple smpp connection to SMSC. The users connect to the 
 opensmppbox and submit and receive SMSs. When a new message is received at 
 the SMSC from the mobile , it is transferred to the kannel and the kennel 
 transfer it to the opensmppbox. If the opensmppbox is disconnected at that 
 point, the message is lost and “Request failed” message is sent to the 
 mobile.
 
  
 Kannel Access log shows the message “Request Failed”
 
  
 
 Kannel bearerbox give the warning “WARNING: Could not route message to 
 smsbox id name, smsbox is gone!
 
  
 
 Kannel smsbox give the warning “WARNING: No translation found for message  
 from NumberA to NumberBERROR: request failed
 
  
  
 I am looking for a way to put the message in a queue, if the client 
 connection to opensmppbox got terminated. When the client connect again, it 
 should transfer the pending mesaage.
 
  
  
 Regards,
 
  
 
 Saju John
 
  
  
 DISCLAIMER: The content of this email and any attachments (“email”) is 
 confidential, subject to copyright and may be read, copied and used only by 
 the intended recipient. If you are not the intended recipient please notify 
 us and erase all copies and do not disclose the email to any person. Nothing 
 in this email shall bind Thuraya in any contract or obligation. Thuraya 
 reserves the right to monitor all email communications through its networks. 
 We believe, but do not warrant, that this email is virus free.
 
 
 
  
 DISCLAIMER: The content of this email and any attachments (“email”) is 
 confidential, subject to copyright and may be read, copied and used only by 
 the intended recipient. If you are not the intended recipient please notify 
 us and erase all copies and do not disclose the email to any person. Nothing 
 in this email shall bind Thuraya in any contract or obligation. Thuraya 
 reserves the right to monitor all email communications through its networks. 
 We believe, but do not warrant, that this email is virus free.
 
 
  
 DISCLAIMER: The content of this email and any attachments (�email�) is 
 confidential, subject to copyright and may be read, copied and used only by 
 the intended recipient. If you are not the intended recipient please notify 
 us and erase all copies and do not disclose the email to any person. Nothing 
 in this email shall bind Thuraya in any contract or obligation. Thuraya 
 reserves the right to monitor all email communications through its networks. 
 We believe, but do not warrant, that this email is virus free.
 
 

Re: MO Concatenation using SAR

[Alexander Malysh]

Hi,

SMPP Spec say:

For GSM networks, the concatenation related TLVs 
(sar_msg_ref_num, sar_total_segments, sar_segment_seqnum)
or port addressing related TLVs
(source_port, dest_port) cannot be used in conjunction with 
encoded User Data Header in the short_message
(user data) field. This means that the above listed TLVs cannot 
be used if the User Data Header Indicator flag is set.

If you see such error then your SMPP-Server is buggy and send both UDHI and 
sar_. Check with your operator...

Alex

Am 03.05.2013 um 14:25 schrieb Ashish Agarwal ashisha...@gmail.com:

 Hello,
 
 The SMSC is sending MO on smpp, but kannel is not able to understand the long 
 message, I get the following error
 
 2013-05-03 17:44:33 [29875] [7] ERROR: SMPP[SMSC1]: sar_msg_ref_num, 
 sar_segment_seqnum, sar_total_segments in conjuction with UDHI used, rejected.
 
 Can anybody help me with configuring TLV values using SAR for proper 
 concatenation reassembling and forward to url?
 
 -- 
 Regards,
 
 Ashish

Re: Kannel crash not in log files

[Alexander Malysh]

Hi,

it should be logged in the syslog.

Alex

Am 07.03.2013 um 19:05 schrieb Brian McCavour bmccav...@yahoo.com:

 
 Hi,
 
 When I run an instance directly from the promp (/smsbox myconfig.conf) if it 
 fails to launch, or crashes, then I will see the error right away, for 
 instance this smsbox startup:
 2013-03-07 17:43:11 [31163] [0] ERROR: Group 'sendsms-user' may not contain 
 field 'global-sender'.
 2013-03-07 17:43:11 [31163] [0] ERROR: Error found on line 46 of file 
 `../etc/smsbox_ns.conf'.
 2013-03-07 17:43:11 [31163] [0] PANIC: Couldn't read configuration from 
 `../etc/smsbox_ns.conf'.
 2013-03-07 17:43:11 [31163] [0] PANIC: ./smsbox(gw_panic+0x15b) [0x43abdb]
 2013-03-07 17:43:11 [31163] [0] PANIC: ./smsbox(main+0xf78) [0x40d7d8]
 2013-03-07 17:43:11 [31163] [0] PANIC: 
 /lib64/libc.so.6(__libc_start_main+0xf4) [0x351ec1d994]
 2013-03-07 17:43:11 [31163] [0] PANIC: ./smsbox [0x40c1a9]
 
 but if instead I run it as --daemonize, and I specify in the config:
 log-file = /var/log/XYZ/kannel/smsbox_ns.log
 access-log = /var/log/XYZ/kannel/smsbox_ns.log
 log-level = 0
 
 Then I don't see anything in the logs.
 Is there some way to get this logged while in daemon mode ?
 
 
 Thanks,
 Brian

Re: No submit_sm_resp

[Alexander Malysh]

Rene,

deliver_sm_resp is always without message_id.

Alex

Am 06.03.2013 um 19:22 schrieb Rene Kluwen rene.klu...@chimit.nl:

 So you do send a deliver_sm_resp. Just with an empty message id.
 Let me look at this closer.
 
 -Original Message-
 From: Jam Hitz [mailto:is.mu...@gmail.com] 
 Sent: woensdag 6 maart 2013 18:40
 To: Rene Kluwen
 Cc: Alexander Malysh; users@kannel.org
 Subject: Re: No submit_sm_resp
 
 Here is the Bearerbox Log (Please NOTE: Upon the recommendations of the
 telco, I have created 10 instances of saf_receiver_b SMSC as defined in the
 config). I shared my settings with the telco and they are also insisting
 that I raise window setting to 500 even though the documentation says
 maximum is 10).  Inspite of all that, I still get like only 5 SMS/min (when
 I'm lucky)
 
 Another observation: in my bearerbox log, I am getting some interesting
 errors especially when restarting the daemon:
 
 2013-03-06 20:20:41 [26334] [3] ERROR: System error 98: Address already in
 use [26385] [0] INFO: DLR rerouting for smsc id saf_receiver_b disabled.
 
  and lots of these:
 2013-03-06 20:24:43 [26488] [17] DEBUG: sms_router: handling message
 (0x20bbc10 vs 0x12a4460)
 2013-03-06 20:24:43 [26488] [17] DEBUG: Routing failed, re-queued.
 
 ...and lots of these (saf_7711 is the transmitter SMSC bind)
 WARNING: SMPP[saf_7711]: Not ACKED message found, will retransmit.
 SENT66sec. ago, SEQ84, DST12345398700
 
 
 Here is my bearerbox log:
 
 2013-03-06 20:32:05 [26488] [9] DEBUG: SMPP[saf_receiver_b]: Sending enquire
 link:
 2013-03-06 20:32:05 [26488] [9] DEBUG: SMPP PDU 0x7f36dc000a30 dump:
 2013-03-06 20:32:05 [26488] [9] DEBUG:   type_name: enquire_link
 2013-03-06 20:32:05 [26488] [9] DEBUG:   command_id: 21 = 0x0015
 2013-03-06 20:32:05 [26488] [9] DEBUG:   command_status: 0 = 0x
 2013-03-06 20:32:05 [26488] [9] DEBUG:   sequence_number: 14 = 0x000e
 2013-03-06 20:32:05 [26488] [9] DEBUG: SMPP PDU dump ends.
 2013-03-06 20:32:06 [26488] [8] DEBUG: SMPP[saf_receiver_b]: Sending enquire
 link:
 2013-03-06 20:32:06 [26488] [8] DEBUG: SMPP PDU 0x7f36e4000e40 dump:
 2013-03-06 20:32:06 [26488] [8] DEBUG:   type_name: enquire_link
 2013-03-06 20:32:06 [26488] [8] DEBUG:   command_id: 21 = 0x0015
 2013-03-06 20:32:06 [26488] [8] DEBUG:   command_status: 0 = 0x
 2013-03-06 20:32:06 [26488] [8] DEBUG:   sequence_number: 88 = 0x0058
 2013-03-06 20:32:06 [26488] [8] DEBUG: SMPP PDU dump ends.
 2013-03-06 20:32:07 [26488] [15] DEBUG: SMPP[saf_receiver_b]: Sending
 enquire link:
 2013-03-06 20:32:07 [26488] [15] DEBUG: SMPP PDU 0x7f36ce90 dump:
 2013-03-06 20:32:07 [26488] [15] DEBUG:   type_name: enquire_link
 2013-03-06 20:32:07 [26488] [15] DEBUG:   command_id: 21 = 0x0015
 2013-03-06 20:32:07 [26488] [15] DEBUG:   command_status: 0 = 0x
 2013-03-06 20:32:07 [26488] [15] DEBUG:   sequence_number: 13 = 0x000d
 2013-03-06 20:32:07 [26488] [15] DEBUG: SMPP PDU dump ends.
 2013-03-06 20:32:08 [26488] [11] DEBUG: SMPP[saf_receiver_b]: Sending
 enquire link:
 2013-03-06 20:32:08 [26488] [11] DEBUG: SMPP PDU 0x7f36de40 dump:
 2013-03-06 20:32:08 [26488] [11] DEBUG:   type_name: enquire_link
 2013-03-06 20:32:08 [26488] [11] DEBUG:   command_id: 21 = 0x0015
 2013-03-06 20:32:08 [26488] [11] DEBUG:   command_status: 0 = 0x
 2013-03-06 20:32:08 [26488] [11] DEBUG:   sequence_number: 14 = 0x000e
 2013-03-06 20:32:08 [26488] [11] DEBUG: SMPP PDU dump ends.
 2013-03-06 20:32:09 [26488] [11] DEBUG: Optional parameter tag (0x0606)
 2013-03-06 20:32:09 [26488] [11] DEBUG: Optional parameter length read as 1
 2013-03-06 20:32:09 [26488] [11] WARNING: SMPP: Unknown
 TLV(0x0606,0x0001,00) for PDU type (deliver_sm) received!
 2013-03-06 20:32:09 [26488] [11] DEBUG: Optional parameter tag (0x1501)
 2013-03-06 20:32:09 [26488] [11] DEBUG: Optional parameter length read as 13
 2013-03-06 20:32:09 [26488] [11] WARNING: SMPP: Unknown
 TLV(0x1501,0x000d,32353437323235303036313200) for PDU type
 (deliver_sm) received!
 2013-03-06 20:32:09 [26488] [11] DEBUG: SMPP[saf_receiver_b]: Got PDU:
 2013-03-06 20:32:09 [26488] [11] DEBUG: SMPP PDU 0x7f36d0001500 dump:
 2013-03-06 20:32:09 [26488] [11] DEBUG:   type_name: deliver_sm
 2013-03-06 20:32:09 [26488] [11] DEBUG:   command_id: 5 = 0x0005
 2013-03-06 20:32:09 [26488] [11] DEBUG:   command_status: 0 = 0x
 2013-03-06 20:32:09 [26488] [11] DEBUG:   sequence_number: 2 = 0x0002
 2013-03-06 20:32:09 [26488] [11] DEBUG:   service_type: INSRV
 2013-03-06 20:32:09 [26488] [11] DEBUG:   source_addr_ton: 1 = 0x0001
 2013-03-06 20:32:09 [26488] [11] DEBUG:   source_addr_npi: 1 = 0x0001
 2013-03-06 20:32:09 [26488] [11] DEBUG:   source_addr: 254703842263
 2013-03-06 20:32:09 [26488] [11] DEBUG:   dest_addr_ton: 0 = 0x
 2013-03-06 20:32:09 [26488] [11] DEBUG:   dest_addr_npi: 1 = 0x0001
 2013-03-06 20:32:09 [26488] [11] DEBUG:   destination_addr: 7711
 2013-03-06 20:32:09 [26488] [11

Re: dlr-mask ignored status 4

[Alexander Malysh]

Hi,

this is not a issue with registered_delivery_flag it's just wrong dlr_mask = 19 
that you use. You have to put dlr_mask = 4 into
requested dlr_mask ( for example dlr_mask = 23).

Alex

Am 06.03.2013 um 12:42 schrieb Rene Kluwen rene.klu...@chimit.nl:

 What is the value of registered_delivery flag of the original smpp message?
  
 == Rene
  
 From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of 
 Jose Figueroa
 Sent: woensdag 6 maart 2013 4:20
 To: users@kannel.org
 Subject: dlr-mask ignored status 4
  
 Hello guys
  
 Today I started a sandbox to setup some route.
  
 I have this form my scenario:
  
 Opensmppbox - Sqlbox - Bearerbox
  
 But when I tried to send I got the following backtrace. Maybe if something 
 happened to you and you can help me. As fair as I know the supplier is using 
 OZEKI NG as their platform.
  
 What would be the problem?
  
 Thanks in advance,
  
 -- Log 
  
 2013-03-06 00:07:45 [8479] [412] DEBUG: SMPP[SMSCMX]: throughput (1.00,50.00)
 2013-03-06 00:07:45 [8479] [412] DEBUG: SMPP[SMSCMX]: throughput (1.00,50.00)
 2013-03-06 00:07:45 [8479] [412] DEBUG: SMPP[SMSCMX]: Got PDU:
 2013-03-06 00:07:45 [8479] [412] DEBUG: SMPP PDU 0x7f559495e7a0 dump:
 2013-03-06 00:07:45 [8479] [412] DEBUG:   type_name: submit_sm_resp
 2013-03-06 00:07:45 [8479] [412] DEBUG:   command_id: 2147483652 = 0x8004
 2013-03-06 00:07:45 [8479] [412] DEBUG:   command_status: 0 = 0x
 2013-03-06 00:07:45 [8479] [412] DEBUG:   sequence_number: 26 = 0x001a
 2013-03-06 00:07:45 [8479] [412] DEBUG:   message_id: 16191027
 2013-03-06 00:07:45 [8479] [412] DEBUG: SMPP PDU dump ends.
 2013-03-06 00:07:45 [8479] [412] DEBUG: DLR[internal]: Adding DLR 
 smsc=SMSCMX, ts=16191027, src=+52551231234567, dst=+525518206397, mask=19, 
 boxc=sandbox
 2013-03-06 00:07:45 [8479] [412] DEBUG: SMPP[SMSCMX]: throughput (1.00,50.00)
 2013-03-06 00:07:45 [8479] [412] DEBUG: SMPP[SMSCMX]: throughput (1.00,50.00)
 2013-03-06 00:07:45 [8479] [412] DEBUG: SMPP[SMSCMX]: Got PDU:
 2013-03-06 00:07:45 [8479] [412] DEBUG: SMPP PDU 0x7f559488ea20 dump:
 2013-03-06 00:07:45 [8479] [412] DEBUG:   type_name: deliver_sm
 2013-03-06 00:07:45 [8479] [412] DEBUG:   command_id: 5 = 0x0005
 2013-03-06 00:07:45 [8479] [412] DEBUG:   command_status: 0 = 0x
 2013-03-06 00:07:45 [8479] [412] DEBUG:   sequence_number: 1 = 0x0001
 2013-03-06 00:07:45 [8479] [412] DEBUG:   service_type: NULL
 2013-03-06 00:07:45 [8479] [412] DEBUG:   source_addr_ton: 1 = 0x0001
 2013-03-06 00:07:45 [8479] [412] DEBUG:   source_addr_npi: 1 = 0x0001
 2013-03-06 00:07:45 [8479] [412] DEBUG:   source_addr: 525518206397
 2013-03-06 00:07:45 [8479] [412] DEBUG:   dest_addr_ton: 2 = 0x0002
 2013-03-06 00:07:45 [8479] [412] DEBUG:   dest_addr_npi: 1 = 0x0001
 2013-03-06 00:07:45 [8479] [412] DEBUG:   destination_addr: sandbox
 2013-03-06 00:07:45 [8479] [412] DEBUG:   esm_class: 4 = 0x0004
 2013-03-06 00:07:45 [8479] [412] DEBUG:   protocol_id: 0 = 0x
 2013-03-06 00:07:45 [8479] [412] DEBUG:   priority_flag: 0 = 0x
 2013-03-06 00:07:45 [8479] [412] DEBUG:   schedule_delivery_time: NULL
 2013-03-06 00:07:45 [8479] [412] DEBUG:   validity_period: NULL
 2013-03-06 00:07:45 [8479] [412] DEBUG:   registered_delivery: 0 = 0x
 2013-03-06 00:07:45 [8479] [412] DEBUG:   replace_if_present_flag: 0 = 
 0x
 2013-03-06 00:07:45 [8479] [412] DEBUG:   data_coding: 0 = 0x
 2013-03-06 00:07:45 [8479] [412] DEBUG:   sm_default_msg_id: 0 = 0x
 2013-03-06 00:07:45 [8479] [412] DEBUG:   sm_length: 108 = 0x006c
 2013-03-06 00:07:45 [8479] [412] DEBUG:   short_message:
 2013-03-06 00:07:45 [8479] [412] DEBUG:Octet string at 0x7f559458cd30:
 2013-03-06 00:07:45 [8479] [412] DEBUG:  len:  108
 2013-03-06 00:07:45 [8479] [412] DEBUG:  size: 109
 2013-03-06 00:07:45 [8479] [412] DEBUG:  immutable: 0
 2013-03-06 00:07:45 [8479] [412] DEBUG:  data: 69 64 3a 31 36 31 39 31 30 
 32 37 20 73 75 62 3a   id:16191027 sub:
 2013-03-06 00:07:45 [8479] [412] DEBUG:  data: 30 30 30 20 64 6c 76 72 64 
 3a 30 30 31 20 73 75   000 dlvrd:001 su
 2013-03-06 00:07:45 [8479] [412] DEBUG:  data: 62 6d 69 74 20 64 61 74 65 
 3a 31 33 30 33 30 35   bmit date:130305
 2013-03-06 00:07:45 [8479] [412] DEBUG:  data: 30 37 30 36 20 64 6f 6e 65 
 20 64 61 74 65 3a 31   0706 done date:1
 2013-03-06 00:07:45 [8479] [412] DEBUG:  data: 33 30 33 30 35 30 37 30 36 
 20 73 74 61 74 3a 41   303050706 stat:A
 2013-03-06 00:07:45 [8479] [412] DEBUG:  data: 43 43 45 50 54 44 20 65 72 
 72 3a 30 30 30 20 74   CCEPTD err:000 t
 2013-03-06 00:07:45 [8479] [412] DEBUG:  data: 65 78 74 3a 31 36 31 39 31 
 30 32 37   ext:16191027
 2013-03-06 00:07:45 [8479] [412] DEBUG:Octet string dump ends.
 2013-03-06 00:07:45 [8479] [412] DEBUG: SMPP PDU dump ends.
 2013-03-06 00:07:45 [8479] [412] DEBUG: SMPP[SMSCMX] handle_pdu, got DLR
 2013-03-06 00:07:45 

Re: No submit_sm_resp

[Alexander Malysh]

And Kannel send generick NACK for unknown/wrong commands.

Alex

Am 05.03.2013 um 16:01 schrieb Jason Mule jason.m...@gmail.com:

 Jam,
 
 The SMSC should send messages to you using either deliver_sm or data_sm PDUs.
 
 On 5 March 2013 09:24, Jam Hitz is.mu...@gmail.com wrote:
 Hello.
 
 I have a very long queue of messages at the SMSC that Kannel is
 picking up very, very slowly. We did a tcpdump and they concluded that
 Kannel was not sending a submit_sm_resp after getting a submit_sm
 causing the SMSC to re-transmit the submit_sm over and over, hence the
 delay.
 
 Please help. My settings are as follows:
 
 #  CORE =
 group = core
 admin-port = 13000
 smsbox-port = 13001
 admin-password = password
 log-level = 0
 store-type = file
 store-location = /var/log/kannel/store_file
 store-dump-freq = 1
 log-file = /var/log/kannel/bearerbox.log
 access-log = /var/log/kannel/bearerbox_access.log
 box-deny-ip = *.*.*.*
 box-allow-ip = 127.0.0.1
 dlr-storage = mysql
 sms-resend-retry = 50
 
 #  SMS DAEMON 
 group = smsbox
 bearerbox-host = 127.0.0.1
 sendsms-port = 13013
 log-file = /var/log/kannel/smsbox.log
 log-level = 0
 access-log = /var/log/kannel/smsbox_access.log
 http-request-retry = 10
 #sendsms-url=/send
 mo-recode=true
 
 #-- MYSQL DLR 
 group = mysql-connection
 id = mysql_dlr
 host = localhost
 username = dlr
 password = dlr
 database = dlr
 max-connections = 1
 
 group = dlr-db
 id = mysql_dlr
 table = dlr
 field-smsc = smsc
 field-timestamp = ts
 field-destination = destination
 field-source = source
 field-service = service
 field-url = url
 field-mask = mask
 field-status = status
 field-boxc-id = boxc
 
 #=== SERVICES  ===
 include = /etc/kannel/default_service.conf
 
 
 #=== SMSC CONNECTIONS ===
 
 group=smsc
 smsc=smpp
 smsc-id=saf_receiver_b
 interface-version=34
 host=192.168.9.93
 receive-port=6695
 system-type=
 smsc-username=username
 smsc-password=password
 log-level=0
 source-addr-ton = 2
 source-addr-npi = 1
 dest-addr-ton = 2
 dest-addr-npi = 1
 msg-id-type = 0x01
 alt-charset = ASCII
 alt-addr-charset = GSM
 enquire-link-interval = 5
 max-pending-submits = 20
 flow-control = 0
 window = 50
 wait-ack=120
 wait-ack-expire=0x02
 
 
 
 
 -- 
 Kind regards
 Jason Mule
 

Re: Kannel r5024 for sar_ mo concatenation

[Alexander Malysh]

Hi,

yes, you can.

Alex

Am 27.02.2013 um 12:58 schrieb [Digital^Dude] ® millennium@gmail.com:

 Hi,
 
 this was a typo in my patch. Fixed in SVN.
 
 Can I use sar_ MO concatenation without defining smsbox-id and smsbox-route? 
 Thanks, it works now. 
 Alex
 
 Am 25.02.2013 um 17:21 schrieb Alexander Malysh amal...@kannel.org:
 
 Hmm very strange UDH, I will look into this.
 
 Alex
 
 Am 25.02.2013 um 10:41 schrieb [Digital^Dude] ® millennium@gmail.com:
 
 Yes, I use SMPP SMSC.
 bearerbox log:
 2013-02-25 14:04:51 [3768] [6] DEBUG: SMPP[x]: throughput (0.00,1.00)
 2013-02-25 14:04:51 [3768] [6] DEBUG: Optional parameter tag (0x000e)
 2013-02-25 14:04:51 [3768] [6] DEBUG: Optional parameter length read as 1
 2013-02-25 14:04:51 [3768] [6] WARNING: SMPP: Unknown TLV(0x000e,0x0001,01) 
 for PDU type (deliver_sm) received!
 2013-02-25 14:04:51 [3768] [6] DEBUG: Optional parameter tag (0x0006)
 2013-02-25 14:04:51 [3768] [6] DEBUG: Optional parameter length read as 1
 2013-02-25 14:04:51 [3768] [6] WARNING: SMPP: Unknown TLV(0x0006,0x0001,01) 
 for PDU type (deliver_sm) received!
 2013-02-25 14:04:51 [3768] [6] DEBUG: Optional parameter tag (0x020c)
 2013-02-25 14:04:51 [3768] [6] DEBUG: Optional parameter length read as 2
 2013-02-25 14:04:51 [3768] [6] DEBUG: Optional parameter tag (0x020e)
 2013-02-25 14:04:51 [3768] [6] DEBUG: Optional parameter length read as 1
 2013-02-25 14:04:51 [3768] [6] DEBUG: Optional parameter tag (0x020f)
 2013-02-25 14:04:51 [3768] [6] DEBUG: Optional parameter length read as 1
 2013-02-25 14:04:51 [3768] [6] DEBUG: Optional parameter tag (0x0424)
 2013-02-25 14:04:51 [3768] [6] DEBUG: Optional parameter length read as 27
 2013-02-25 14:04:51 [3768] [6] DEBUG: SMPP[x]: Got PDU:
 2013-02-25 14:04:51 [3768] [6] DEBUG: SMPP PDU 0x8dc3190 dump:
 2013-02-25 14:04:51 [3768] [6] DEBUG:   type_name: deliver_sm
 2013-02-25 14:04:51 [3768] [6] DEBUG:   command_id: 5 = 0x0005
 2013-02-25 14:04:51 [3768] [6] DEBUG:   command_status: 0 = 0x
 2013-02-25 14:04:51 [3768] [6] DEBUG:   sequence_number: 3 = 0x0003
 2013-02-25 14:04:51 [3768] [6] DEBUG:   service_type: NULL
 2013-02-25 14:04:51 [3768] [6] DEBUG:   source_addr_ton: 1 = 0x0001
 2013-02-25 14:04:51 [3768] [6] DEBUG:   source_addr_npi: 1 = 0x0001
 2013-02-25 14:04:51 [3768] [6] DEBUG:   source_addr: 923029422885
 2013-02-25 14:04:51 [3768] [6] DEBUG:   dest_addr_ton: 4 = 0x0004
 2013-02-25 14:04:51 [3768] [6] DEBUG:   dest_addr_npi: 1 = 0x0001
 2013-02-25 14:04:51 [3768] [6] DEBUG:   destination_addr: 1767
 2013-02-25 14:04:51 [3768] [6] DEBUG:   esm_class: 0 = 0x
 2013-02-25 14:04:51 [3768] [6] DEBUG:   protocol_id: 0 = 0x
 2013-02-25 14:04:51 [3768] [6] DEBUG:   priority_flag: 0 = 0x
 2013-02-25 14:04:51 [3768] [6] DEBUG:   schedule_delivery_time: NULL
 2013-02-25 14:04:51 [3768] [6] DEBUG:   validity_period: NULL
 2013-02-25 14:04:51 [3768] [6] DEBUG:   registered_delivery: 0 = 0x
 2013-02-25 14:04:51 [3768] [6] DEBUG:   replace_if_present_flag: 0 = 
 0x
 2013-02-25 14:04:51 [3768] [6] DEBUG:   data_coding: 0 = 0x
 2013-02-25 14:04:51 [3768] [6] DEBUG:   sm_default_msg_id: 0 = 0x
 2013-02-25 14:04:51 [3768] [6] DEBUG:   sm_length: 0 = 0x
 2013-02-25 14:04:51 [3768] [6] DEBUG:   short_message: 
 2013-02-25 14:04:51 [3768] [6] DEBUG:   sar_msg_ref_num: 87 = 0x0057
 2013-02-25 14:04:51 [3768] [6] DEBUG:   sar_total_segments: 2 = 0x0002
 2013-02-25 14:04:51 [3768] [6] DEBUG:   sar_segment_seqnum: 2 = 0x0002
 2013-02-25 14:04:51 [3768] [6] DEBUG:   message_payload:
 2013-02-25 14:04:51 [3768] [6] DEBUG:Octet string at 0x8dc4478:
 2013-02-25 14:04:51 [3768] [6] DEBUG:  len:  27
 2013-02-25 14:04:51 [3768] [6] DEBUG:  size: 28
 2013-02-25 14:04:51 [3768] [6] DEBUG:  immutable: 0
 2013-02-25 14:04:51 [3768] [6] DEBUG:  data: 78 20 6a 75 6d 70 73 20 6f 
 76 65 72 20 74 68 65   x jumps over the
 2013-02-25 14:04:51 [3768] [6] DEBUG:  data: 20 6c 61 7a 79 20 64 6f 67 
 2e 20   lazy dog.
 2013-02-25 14:04:51 [3768] [6] DEBUG:Octet string dump ends.
 2013-02-25 14:04:51 [3768] [6] DEBUG: SMPP PDU dump ends.
 2013-02-25 14:04:51 [3768] [6] ERROR: Failed to convert string from gsm 
 to UTF-8 - probably broken type names.
 2013-02-25 14:04:51 [3768] [6] ERROR: Failed to convert msgdata from 
 charset gsm to UTF-8, will leave as is.
 2013-02-25 14:04:51 [3768] [6] DEBUG: Got part 255 [ref 2, total parts 255] 
 of message from x. Dump follows:
 2013-02-25 14:04:51 [3768] [6] DEBUG: Msg object at 0x8dcf538:
 2013-02-25 14:04:51 [3768] [6] DEBUG:  type: sms
 2013-02-25 14:04:51 [3768] [6] DEBUG:  sms.sender:
 2013-02-25 14:04:51 [3768] [6] DEBUG:  Octet string at 0x8dcf608:
 2013-02-25 14:04:51 [3768] [6] DEBUG:len:  13
 2013-02-25 14:04:51 [3768] [6] DEBUG:size: 14
 2013-02-25 14:04:51 [3768] [6] DEBUG:immutable: 0
 2013-02-25 14:04:51 [3768] [6] DEBUG:data: x

Re: Kannel r5024 for sar_ mo concatenation

[Alexander Malysh]

Hi,

do you use SMPP SMSC? Could you please provide bearerbox  smsbox debug log?

Alex

Am 25.02.2013 um 07:51 schrieb [Digital^Dude] ® millennium@gmail.com:

 Hello,
 
 Since I have upgraded from r5014, I am unable to receive any hit for inbound 
 sms in my bearerbox. Kannel status does show the correct number of sms 
 received, but I cannot see the message details in any log. And hence, I am 
 unable to send an automated reply on incoming messages. Debug mode logging of 
 sms also does not facilitate.
 
 OS:
 Ubuntu 11.04 natty
 Kannel:
 URL: https://svn.kannel.org/gateway/trunk
 Repository Root: https://svn.kannel.org/gateway
 Repository UUID: a7d65f57-29cd-40c9-b71e-ebca51ad1b1d
 Revision: 5024
 Node Kind: directory
 Schedule: normal
 Last Changed Author: amalysh
 Last Changed Rev: 5024
 Last Changed Date: 2013-02-21 22:01:03 +0500 (Thu, 21 Feb 2013)
 gw/smskannel.conf:
 group = sms-service
 keyword = default
 text = No service specified
 alt-charset=gsm
 forced-smsc=X
 concatenation=true
 catch-all=true
 
 I also have the following in my core:
 sms-combine-concatenated-mo = true
 sms-combine-concatenated-mo-timeout = 1800
 
 
 I have to use the latest version (r5024+) in order to use MO concatenation 
 feature comitted by amalysh:
 2013-02-21 Alexander Malysh amalysh at kannel.org
 * gw/smsc/smsc_smpp.c: added support for sar_ multipart TLVs.
 
 Please help me get to the issue so that it can be resolved.
 Thanks

Re: Kannel r5024 for sar_ mo concatenation

[Alexander Malysh]

Hi,

this was a typo in my patch. Fixed in SVN.

Alex

Am 25.02.2013 um 17:21 schrieb Alexander Malysh amal...@kannel.org:

 Hmm very strange UDH, I will look into this.
 
 Alex
 
 Am 25.02.2013 um 10:41 schrieb [Digital^Dude] ® millennium@gmail.com:
 
 Yes, I use SMPP SMSC.
 bearerbox log:
 2013-02-25 14:04:51 [3768] [6] DEBUG: SMPP[x]: throughput (0.00,1.00)
 2013-02-25 14:04:51 [3768] [6] DEBUG: Optional parameter tag (0x000e)
 2013-02-25 14:04:51 [3768] [6] DEBUG: Optional parameter length read as 1
 2013-02-25 14:04:51 [3768] [6] WARNING: SMPP: Unknown TLV(0x000e,0x0001,01) 
 for PDU type (deliver_sm) received!
 2013-02-25 14:04:51 [3768] [6] DEBUG: Optional parameter tag (0x0006)
 2013-02-25 14:04:51 [3768] [6] DEBUG: Optional parameter length read as 1
 2013-02-25 14:04:51 [3768] [6] WARNING: SMPP: Unknown TLV(0x0006,0x0001,01) 
 for PDU type (deliver_sm) received!
 2013-02-25 14:04:51 [3768] [6] DEBUG: Optional parameter tag (0x020c)
 2013-02-25 14:04:51 [3768] [6] DEBUG: Optional parameter length read as 2
 2013-02-25 14:04:51 [3768] [6] DEBUG: Optional parameter tag (0x020e)
 2013-02-25 14:04:51 [3768] [6] DEBUG: Optional parameter length read as 1
 2013-02-25 14:04:51 [3768] [6] DEBUG: Optional parameter tag (0x020f)
 2013-02-25 14:04:51 [3768] [6] DEBUG: Optional parameter length read as 1
 2013-02-25 14:04:51 [3768] [6] DEBUG: Optional parameter tag (0x0424)
 2013-02-25 14:04:51 [3768] [6] DEBUG: Optional parameter length read as 27
 2013-02-25 14:04:51 [3768] [6] DEBUG: SMPP[x]: Got PDU:
 2013-02-25 14:04:51 [3768] [6] DEBUG: SMPP PDU 0x8dc3190 dump:
 2013-02-25 14:04:51 [3768] [6] DEBUG:   type_name: deliver_sm
 2013-02-25 14:04:51 [3768] [6] DEBUG:   command_id: 5 = 0x0005
 2013-02-25 14:04:51 [3768] [6] DEBUG:   command_status: 0 = 0x
 2013-02-25 14:04:51 [3768] [6] DEBUG:   sequence_number: 3 = 0x0003
 2013-02-25 14:04:51 [3768] [6] DEBUG:   service_type: NULL
 2013-02-25 14:04:51 [3768] [6] DEBUG:   source_addr_ton: 1 = 0x0001
 2013-02-25 14:04:51 [3768] [6] DEBUG:   source_addr_npi: 1 = 0x0001
 2013-02-25 14:04:51 [3768] [6] DEBUG:   source_addr: 923029422885
 2013-02-25 14:04:51 [3768] [6] DEBUG:   dest_addr_ton: 4 = 0x0004
 2013-02-25 14:04:51 [3768] [6] DEBUG:   dest_addr_npi: 1 = 0x0001
 2013-02-25 14:04:51 [3768] [6] DEBUG:   destination_addr: 1767
 2013-02-25 14:04:51 [3768] [6] DEBUG:   esm_class: 0 = 0x
 2013-02-25 14:04:51 [3768] [6] DEBUG:   protocol_id: 0 = 0x
 2013-02-25 14:04:51 [3768] [6] DEBUG:   priority_flag: 0 = 0x
 2013-02-25 14:04:51 [3768] [6] DEBUG:   schedule_delivery_time: NULL
 2013-02-25 14:04:51 [3768] [6] DEBUG:   validity_period: NULL
 2013-02-25 14:04:51 [3768] [6] DEBUG:   registered_delivery: 0 = 0x
 2013-02-25 14:04:51 [3768] [6] DEBUG:   replace_if_present_flag: 0 = 
 0x
 2013-02-25 14:04:51 [3768] [6] DEBUG:   data_coding: 0 = 0x
 2013-02-25 14:04:51 [3768] [6] DEBUG:   sm_default_msg_id: 0 = 0x
 2013-02-25 14:04:51 [3768] [6] DEBUG:   sm_length: 0 = 0x
 2013-02-25 14:04:51 [3768] [6] DEBUG:   short_message: 
 2013-02-25 14:04:51 [3768] [6] DEBUG:   sar_msg_ref_num: 87 = 0x0057
 2013-02-25 14:04:51 [3768] [6] DEBUG:   sar_total_segments: 2 = 0x0002
 2013-02-25 14:04:51 [3768] [6] DEBUG:   sar_segment_seqnum: 2 = 0x0002
 2013-02-25 14:04:51 [3768] [6] DEBUG:   message_payload:
 2013-02-25 14:04:51 [3768] [6] DEBUG:Octet string at 0x8dc4478:
 2013-02-25 14:04:51 [3768] [6] DEBUG:  len:  27
 2013-02-25 14:04:51 [3768] [6] DEBUG:  size: 28
 2013-02-25 14:04:51 [3768] [6] DEBUG:  immutable: 0
 2013-02-25 14:04:51 [3768] [6] DEBUG:  data: 78 20 6a 75 6d 70 73 20 6f 
 76 65 72 20 74 68 65   x jumps over the
 2013-02-25 14:04:51 [3768] [6] DEBUG:  data: 20 6c 61 7a 79 20 64 6f 67 
 2e 20   lazy dog.
 2013-02-25 14:04:51 [3768] [6] DEBUG:Octet string dump ends.
 2013-02-25 14:04:51 [3768] [6] DEBUG: SMPP PDU dump ends.
 2013-02-25 14:04:51 [3768] [6] ERROR: Failed to convert string from gsm to 
 UTF-8 - probably broken type names.
 2013-02-25 14:04:51 [3768] [6] ERROR: Failed to convert msgdata from charset 
 gsm to UTF-8, will leave as is.
 2013-02-25 14:04:51 [3768] [6] DEBUG: Got part 255 [ref 2, total parts 255] 
 of message from x. Dump follows:
 2013-02-25 14:04:51 [3768] [6] DEBUG: Msg object at 0x8dcf538:
 2013-02-25 14:04:51 [3768] [6] DEBUG:  type: sms
 2013-02-25 14:04:51 [3768] [6] DEBUG:  sms.sender:
 2013-02-25 14:04:51 [3768] [6] DEBUG:  Octet string at 0x8dcf608:
 2013-02-25 14:04:51 [3768] [6] DEBUG:len:  13
 2013-02-25 14:04:51 [3768] [6] DEBUG:size: 14
 2013-02-25 14:04:51 [3768] [6] DEBUG:immutable: 0
 2013-02-25 14:04:51 [3768] [6] DEBUG:data: xx
 2013-02-25 14:04:51 [3768] [6] DEBUG:  Octet string dump ends.
 2013-02-25 14:04:51 [3768] [6] DEBUG:  sms.receiver:
 2013-02-25 14:04:51 [3768] [6] DEBUG:  Octet string at 0x8dcf638:
 2013-02-25

Re: Long Messages using httpsmsc

[Alexander Malysh]

Rene,

I can't reproduce it. I can supply any validity  deferred values via smsbox 
and it works as expected.

Alex

Am 23.02.2013 um 14:21 schrieb Rene Kluwen rene.klu...@chimit.nl:

 Please, Alexander.
 Fix this bug. Because I’ve got other clients with the same issue.
 I haven’t had time myself to look into it.
  
 == Rene
  
 From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf 
 Of[Digital^Dude] ®
 Sent: vrijdag 22 februari 2013 10:03
 To: Alexander Malysh
 Cc: users@kannel.org
 Subject: Re: Long Messages using httpsmsc
  
 Hi,
  
 sar support has been commited yesterday, enjoy :-)
 I tried my best to enjoy but the latest svn revision throws up:
 SMSC returned error code 0x0062 (Invalid message validity period) in 
 response to submit_sm
  
 Alex
  
 Am 22.02.2013 um 08:48 schrieb [Digital^Dude] ® millennium@gmail.com:
 
 
 Hi,
  
 sar_ within HTTP SMSC???
  
 Obviously its not in the http smsc! ! !
 So can I assume that when kannel tells me that MO concatenated message 
 handling is enabled, I should only think of the UDH mode? If yes, is there a 
 patch for kannel that makes the 'sar' method available?
 I found a patch that was committed by Stipe at: 
 http://www.mail-archive.com/devel@kannel.org/msg11322.html
 however, I am unable to get the patch applied on any of the 50xx svn 
 revisions.
 Thanks for the help!
 And to the sar_ question: kannel doesn't support it but support UDH mode.
  
 Alex
  
 Am 21.02.2013 um 13:06 schrieb [Digital^Dude] ® millennium@gmail.com:
 
 
 On Fri, Feb 8, 2013 at 3:36 PM, Ali Kashif syedalikas...@gmail.com wrote:
  
 try adding following in CORE section.
  
 sms-combine-concatenated-mo = true
 sms-combine-concatenated-mo-timeout = 1800
  
  
  
 and in your httpSMSC 
  
 max-sms-octets= 1260
  
 
 I guess the only way to do this is via 
 sar_segment_seqnum
 and
 sar_total_segments
 
 Any implementation for that already done?
  
  
  
  

Re: Long Messages using httpsmsc

[Alexander Malysh]

#define HAVE_GMTIME_R 1

don't understand what difference it should make? can you exmplain?

Alex

Am 24.02.2013 um 20:32 schrieb Rene Kluwen rene.klu...@chimit.nl:

 What is your value of HAVE_GMTIME_R in gw-config.h?
  
 == Rene
  
 From: Alexander Malysh [mailto:malys...@gmail.com] On Behalf Of Alexander 
 Malysh
 Sent: zondag 24 februari 2013 12:44
 To: Rene Kluwen
 Cc: '[Digital^Dude] R'; users@kannel.org
 Subject: Re: Long Messages using httpsmsc
  
 Rene,
  
 I can't reproduce it. I can supply any validity  deferred values via smsbox 
 and it works as expected.
  
 Alex
  
 Am 23.02.2013 um 14:21 schrieb Rene Kluwen rene.klu...@chimit.nl:
 
 
 Please, Alexander.
 Fix this bug. Because I’ve got other clients with the same issue.
 I haven’t had time myself to look into it.
  
 == Rene
  
 From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf 
 Of[Digital^Dude] ®
 Sent: vrijdag 22 februari 2013 10:03
 To: Alexander Malysh
 Cc: users@kannel.org
 Subject: Re: Long Messages using httpsmsc
  
 Hi,
  
 sar support has been commited yesterday, enjoy :-)
 I tried my best to enjoy but the latest svn revision throws up:
 SMSC returned error code 0x0062 (Invalid message validity period) in 
 response to submit_sm
  
 Alex
  
 Am 22.02.2013 um 08:48 schrieb [Digital^Dude] ® millennium@gmail.com:
 
 
 
 Hi,
  
 sar_ within HTTP SMSC???
  
 Obviously its not in the http smsc! ! !
 So can I assume that when kannel tells me that MO concatenated message 
 handling is enabled, I should only think of the UDH mode? If yes, is there a 
 patch for kannel that makes the 'sar' method available?
 I found a patch that was committed by Stipe at: 
 http://www.mail-archive.com/devel@kannel.org/msg11322.html
 however, I am unable to get the patch applied on any of the 50xx svn 
 revisions.
 Thanks for the help!
 And to the sar_ question: kannel doesn't support it but support UDH mode.
  
 Alex
  
 Am 21.02.2013 um 13:06 schrieb [Digital^Dude] ® millennium@gmail.com:
 
 
 
 On Fri, Feb 8, 2013 at 3:36 PM, Ali Kashif syedalikas...@gmail.com wrote:
  
 try adding following in CORE section.
  
 sms-combine-concatenated-mo = true
 sms-combine-concatenated-mo-timeout = 1800
  
  
  
 and in your httpSMSC 
  
 max-sms-octets= 1260
  
 
 I guess the only way to do this is via 
 sar_segment_seqnum
 and
 sar_total_segments
 
 Any implementation for that already done?
  
  
  
  

Re: Long Messages using httpsmsc

[Alexander Malysh]

Hi,

sar support has been commited yesterday, enjoy :-)

Alex

Am 22.02.2013 um 08:48 schrieb [Digital^Dude] ® millennium@gmail.com:

 Hi,
 
 sar_ within HTTP SMSC???
 
 Obviously its not in the http smsc! ! !
 So can I assume that when kannel tells me that MO concatenated message 
 handling is enabled, I should only think of the UDH mode? If yes, is there a 
 patch for kannel that makes the 'sar' method available?
 I found a patch that was committed by Stipe at: 
 http://www.mail-archive.com/devel@kannel.org/msg11322.html
 however, I am unable to get the patch applied on any of the 50xx svn 
 revisions.
 Thanks for the help!
 And to the sar_ question: kannel doesn't support it but support UDH mode.
 
 Alex
 
 Am 21.02.2013 um 13:06 schrieb [Digital^Dude] ® millennium@gmail.com:
 
 On Fri, Feb 8, 2013 at 3:36 PM, Ali Kashif syedalikas...@gmail.com wrote:
 
 try adding following in CORE section.
 
 sms-combine-concatenated-mo = true
 sms-combine-concatenated-mo-timeout = 1800
 
 
 
 and in your httpSMSC 
 
 max-sms-octets= 1260
 
 
 I guess the only way to do this is via 
 sar_segment_seqnum
 and
 sar_total_segments
 
 Any implementation for that already done?
 
 
 

Re: Long Messages using httpsmsc

[Alexander Malysh]

Hi,

sar_ within HTTP SMSC???

And to the sar_ question: kannel doesn't support it but support UDH mode.

Alex

Am 21.02.2013 um 13:06 schrieb [Digital^Dude] ® millennium@gmail.com:

 On Fri, Feb 8, 2013 at 3:36 PM, Ali Kashif syedalikas...@gmail.com wrote:
 
 try adding following in CORE section.
 
 sms-combine-concatenated-mo = true
 sms-combine-concatenated-mo-timeout = 1800
 
 
 
 and in your httpSMSC 
 
 max-sms-octets= 1260
 
 
 I guess the only way to do this is via 
 sar_segment_seqnum
 and
 sar_total_segments
 
 Any implementation for that already done?
 

Re: SQLBOX ERROR(Segmentation fault (core dumped)):

[Alexander Malysh]

Hi,

please start with version you are using, debug logs, backtrace...

Thanks,
Alex

Am 19.02.2013 um 11:06 schrieb Himanshu Matta himan...@hostnsoft.com:

 Hello,
 
 When I connect sqlbox with bearerbox then it shows 
 Segmentation fault (core dumped)
 
 What is it ? 
 why it is coming ? 
 How to avoid it ?
 
 -- 
 Thanks and regards,
 Himanshu Matta.
 

Re: start-stop-daemon with --background flag or -d flag for bearebox

[Alexander Malysh]

Hi,

you don't need start-stop-daemon and it's not supported/maintained anymore.

Start bearerbox with a -d option BUT use full path, e.g.:

/path/bearerbox -d /path/config.conf

Alex

Am 29.01.2013 um 18:54 schrieb Brian McCavour bmccav...@yahoo.com:

 Hi,
 
 Starting from the 1.4.3 source I configured/compiled:
 sh configure --enable-start-stop-daemon
 make
 
 Now when I run from utils/
 ./start-stop-daemon --start --exec ../gw/bearerbox -- 
 ../kannel.config/kannel.conf
 It works fine but executes in the shell.
 
 When I run with --backgorund it returns to the prompt and nothing happens.
 ./start-stop-daemon --start --background --exec ../gw/bearerbox -- 
 ../kannel.config/kannel.conf
 (Verified with lsof -i -n, as well as http admin interface fails to connect, 
 unlike the non --background attempt))
 
 Doing web search for a solution, I see many similar examples, though some use 
 run_kannel_box instead of directly calling the bearebox.
 On further investigation I noticed that it's actualy the same result when I 
 simply run from gw/:
 ./bearerbox ../kannel.config/kannel.conf (works fine)
 and
 ./bearerbox -d ../kannel.config/kannel.conf (nothing happens)
 
 
 Does anyone know what I'm missing?
 
 Thanks,
 Brian
 
 
 
 
 
 

Re: Does bearerbox pass messages one on one to the SMSC?

[Alexander Malysh]

Hi,

Kannel uses windowing. See max-pending-requests in the user guide.

Alex

Am 25.01.2013 um 11:12 schrieb David Szanto dsza...@genasys.com:

 Hi everyone!
 
 We've been trying to determine (with my colleagues at work) if when connected 
 to an SMSC using SMPP the bearerbox passes MT messages through the bind in a 
 batch, or one on one.
 The specific case involves load balancing with 2 or more binds to multiple 
 SMSCs.
 
 So, do messages get passed to the SMSCs in groups of 10, 20 or whatever? or 
 does it pass messages one on one?
 
 Any comment will be greatly appreciated!
 
 Thanks!!!
 
 David Szanto
 

Re: *** MERRY CHRISTMAS and a HAPPY NEW YEAR! *** from the Kannel Group!

[Alexander Malysh]

I would like to join the Stipe wishes!

Happy New Year to all supporters of Kannel Group!

Alexander Maöysh

Am 24.12.2012 um 15:19 schrieb Stipe Tolj st...@kannel.org:

 Dear developers,
 Dear users,
 
 in the name of the whole Kannel Group, and to all the great individual 
 supporters and contributor that have shown again tremendous participation and 
 encouragement in this year we wish you:
 
  *** Merry Christmas, Happy Holidays and a Happy New Year! ***
 
 Enjoy the holiday season and make yourself a great time, either with family, 
 friends or both. :)
 
 Stipe
 
 -- 
 ---
 Kölner Landstrasse 419
 40589 Düsseldorf, NRW, Germany
 
 tolj.org system architecture  Kannel Software Foundation (KSF)
 http://www.tolj.org/  http://www.kannel.org/
 
 mailto:st_{at}_tolj.org   mailto:stolj_{at}_kannel.org
 ---
 

Re: problem : opensmppbox seem to split my concatened SMS

[Alexander Malysh]

Hi,

try to set max-sms-octets for http smsc.

Alex

Am 19.11.2012 um 07:45 schrieb Bertrand Dupont bertrand.dupon...@yahoo.fr:

 Hi all,
 
 I've a kannel with the following configuration :
 
 OpenSMPPbox -- Bearerbox -- Http SMSC --- php Script
 
 We are using this configuration to accept SMPP connection from customers and 
 inject SMS in our system to process billing etc... before sending them.
 My problem is that concatened messages are splits in x sms of 153 char and 
 I can't figure out why kannel are splitting those SMS.
 
 In the bearerbox access log file I can see that my sms is still in one 
 piece not splitted
 
 2012-11-19 06:26:33 Sent SMS [SMSC:OUTPUT] [SVC:2650] [ACT:] [BINF:] 
 [FID:ka_f233789e97f2fbef206de8bd925ea4ec] [META:?smpp?] [from:SMS] 
 [to:3362894] [flags:-1:0:-1:0:19] [msg:341:2 sms long sms long sms 
 long essai sms long sms long sms long sms long essai sms long sms long sms 
 long sms long essai sms long sms long sms long sms long essai sms long sms 
 long sms long sms long essai sms long sms long sms long sms long essai sms 
 long sms long sms long sms long essai sms long sms long sms long sms long 
 essai sms long] [udh:0:]
 
 In my kannel.conf I've the concatenation = true config as follow :
 
 # SEND-SMS USERS
 
 group = sendsms-user
 username = INPUT
 password = eknootmotdepasse
 concatenation = true
 forced-smsc = OUTPUT
 max-messages = 3
 
 As I can see my full message in the access-bearerbox log file, does that 
 means that my problem is between bearerbox and the http_smsc ?
 Or the problem can also be in the opensmppbox ? does someone already face 
 this issue ? maybe it's just a config problem but I can't face it !
 
 Thanks for your help.
 
 Regards,
 Bertrand

Re: Kannel PANICS octstr_convert_range

[Alexander Malysh]

Hi Rob,

you are looking in the wrong direction. As far as I see from your crash it's so 
that bearerbox send message to smsbox
and not another way around. Therefore you have to check, what you still have in 
the store file (if you delete it then also delete .bak files)
and see in the access log of bearerbox which message cause crash.

Alex

P.S. I would suggest to upgrade to SVN version, it's more stable and maintained 
as 1.4.3. 1.4.3 is very very old.

On 27.09.2012, at 10:06, Rob GB rob_gar_...@hotmail.com wrote:

 
 Hi Alex, 
 
 I'm using Kannel 1.4.3, sorry for not mentioning this before.
 
 Do you know by chance the context of where the error appeared in smsbox? I 
 would like to understand the possible ways we can trigger the “assert != 
 null” to fail.
 
 Back-tracking from the error I find the following places the error could have 
 come from:
 
 ~/tmp/kannel$ find . -name *.c -exec grep -iH octstr_convert_range {} \;
 
 ./gateway-1.4.3/gw/xml_shared.c:octstr_convert_range(charset, 0, 
 octstr_len(charset), toupper);
 ./gateway-1.4.3/gw/urltrans.c:octstr_convert_range(tmp, 0, 
 octstr_len(tmp), tolower);
 ./gateway-1.4.3/gw/urltrans.c:  octstr_convert_range(os, 0, 
 octstr_len(os), tolower);
 ./gateway-1.4.3/gw/urltrans.c:octstr_convert_range(data, 0, 
 octstr_len(data), tolower);
 ./gateway-1.4.3/gw/wap_push_pap_compiler.c:octstr_convert_range(nameos, 
 0, octstr_len(nameos), tolower);
 ./gateway-1.4.3/gw/wap_push_pap_compiler.c:octstr_convert_range(*address, 
 0, octstr_len(*address), tolower);
 ./gateway-1.4.3/gw/wml_compiler.c:  octstr_convert_range(escape, 0, 
 octstr_len(escape), tolower);
 ./gateway-1.4.3/gwlib/octstr.c:void octstr_convert_range(Octstr *ostr, long 
 pos, long len,
 ./gateway-1.4.3/gwlib/octstr.c:octstr_convert_range(ostr, 0, ostr-len, 
 make_printable); 
 
 To me they all seem to point to an URL being bad or similar in a PAP request. 
 However I have not changed anything in my config and underlaying APP for 
 months.
 
 I also wonder about the spool directory.  Why does Kannel continue to crash 
 unless we clean the spool directory?
  
 Why are some messages left in the spool directory? The normal behaviour for 
 in-/out-bound messages is for them to be stored in the spool directory and 
 then deleted once they have been acknowledged to be received. So the question 
 then becomes; What’s so “special” with the messages that remains in the spool 
 directory?
 
 Looking at the logs from today I find that we end keeping the message with ID 
 d4e378df-8fa7-4d7b-83a3-bc28dfc44b12 in the spool directory and not the 
 message with ID a45dd024-55dc-46f8-aefa-15d0bb321a73.
 I cannot see any difference in the log file on why the first one is stored 
 and the second isn’t.
 
 2012-09-27 08:14:49 [28185] [3] INFO: smsbox: Got HTTP request 
 /cgi-bin/sendsms from 10.223.205.193
 2012-09-27 08:14:49 [28185] [3] INFO: sendsms used by smsc1
 2012-09-27 08:14:49 [28185] [3] INFO: sendsms sender:smsc1:LabelSMS 
 (10.223.205.193) to:55257465 msg:
 2012-09-27 08:14:49 [28185] [3] DEBUG: Stored UUID 
 d4e378df-8fa7-4d7b-83a3-bc28dfc44b12
 2012-09-27 08:14:49 [28185] [3] DEBUG: message length 0, sending 1 messages
 2012-09-27 08:14:49 [28185] [3] DEBUG: Status: 202 Answer: Sent.
 2012-09-27 08:14:49 [28185] [3] DEBUG: Delayed reply - wait for bearerbox
 2012-09-27 08:14:49 [28185] [0] DEBUG: Got ACK (0) of 
 d4e378df-8fa7-4d7b-83a3-bc28dfc44b12
 2012-09-27 08:14:49 [28185] [0] DEBUG: HTTP: Resetting HTTPClient for 
 `10.223.205.193'.
 
 (...)
 
 2012-09-27 08:14:49 [28185] [3] INFO: smsbox: Got HTTP request 
 /cgi-bin/sendsms from 10.223.205.193
 2012-09-27 08:14:49 [28185] [3] INFO: sendsms used by smsc2
 2012-09-27 08:14:49 [28185] [3] INFO: sendsms sender:smsc2:LabelSMS 
 (10.223.205.193) to:524423191572 msg:
 2012-09-27 08:14:49 [28185] [3] DEBUG: Stored UUID 
 a45dd024-55dc-46f8-aefa-15d0bb321a73
 2012-09-27 08:14:49 [28185] [3] DEBUG: message length 0, sending 1 messages
 2012-09-27 08:14:49 [28185] [3] DEBUG: Status: 202 Answer: Sent.
 2012-09-27 08:14:49 [28185] [3] DEBUG: Delayed reply - wait for bearerbox
 2012-09-27 08:14:49 [28185] [0] DEBUG: Got ACK (0) of 
 a45dd024-55dc-46f8-aefa-15d0bb321a73
 2012-09-27 08:14:49 [28185] [0] DEBUG: HTTP: Resetting HTTPClient for 
 `10.223.205.193'.
 
  
 Thanks a lot.
 
 ///RGB
 
 
 
 
 
 
 
 
 Subject: Re: Kannel PANICS octstr_convert_range
 From: amal...@kannel.org
 Date: Wed, 26 Sep 2012 18:58:32 +0200
 CC: users@kannel.org
 To: rob_gar_...@hotmail.com
 
 Hi,
 
 seems some queued message within bearerbox cause this panic. Try ether to 
 upgrade to the latest SVN version
 or delete bearerbox.store file.
 
 Alex
 
 On 26.09.2012, at 17:28, Rob GB rob_gar_...@hotmail.com wrote:
 
 
 Hi Kannel people,
 
 I have been using Kannel for almost 2 year, but today it has crashed and 
 cannot make it work:
 
 
 2012-09-26 17:15:23 [28324] [0] INFO: Added logfile 
 

Re: Kannel PANICS octstr_convert_range

[Alexander Malysh]

http://www.kannel.org/pipermail/devel/attachments/20090826/42b1df45/attachment-0001.obj

On 27.09.2012, at 13:37, Rob GB rob_gar_...@hotmail.com wrote:

 
 Hi,
 
 I think the fix was commited in this bug, but cannot find in the repo:
 
 http://www.kannel.org/pipermail/devel/2009-August/002872.html
 
 Could you guide me where the fix is?
 
 Thanks.
 
 
 From: rob_gar_...@hotmail.com
 To: amal...@kannel.org
 CC: users@kannel.org
 Subject: RE: Kannel PANICS octstr_convert_range
 Date: Thu, 27 Sep 2012 05:19:31 -0500
 
 
 Hi Alex,
 
 We would like to fix the v1.4.3 since v1.5.0 is not officially released.
 
 I think we detected what type of MO is causing the problems, it is one with 
 no data in the Data_sm message:
 
 
 Flags: 0x18 (PSH, ACK)
 0...  = Congestion Window Reduced (CWR): Not set
 .0..  = ECN-Echo: Not set
 ..0.  = Urgent: Not set
 ...1  = Acknowledgement: Set
  1... = Push: Set
  .0.. = Reset: Not set
  ..0. = Syn: Not set
  ...0 = Fin: Not set
 
 Window size: 32768
 
 
 Short Message Peer to Peer, Command: Data_sm, Seq: 175, Len: 59
 Length : 59
 Operation : Data_sm (0x0103)
 Sequence #: 175
 Service type: (Default)
 Type of number (originator): International (0x01)
 Numbering plan indicator (originator): ISDN (E163/E164) (0x01)
 Originator address: 525534097529
 Type of number (recipient): International (0x01)
 Numbering plan indicator (recipient): ISDN (E163/E164) (0x01)
 Recipient address: 522030203000
  ..00 = Messaging mode: Default SMSC mode (0x00)
 ..00 00.. = Message type : Default message type (0x00)
 00..  = GSM features : No specific features selected (0x00)
  ..00 = Delivery receipt : No SMSC delivery receipt requested (0x00)
  00.. = Message type : No recipient SME acknowledgement requested (0x00)
 ...0  = Intermediate notif: No intermediate notification requested (0x00)
 
 
 Data coding: 0x00
 SMPP Data Coding Scheme: SMSC default alphabet (0x00)
 GSM SMS Data Coding
   = DCS Coding Group for SMS: SMS DCS: General Data Coding 
 indication - Uncompressed text, no message class (0x00)
 ..0.  = DCS Text compression: Uncompressed text
 ...0  = DCS Class present: No message class
  00.. = DCS Character set: GSM 7-bit default alphabet (0x00)
 GSM CBS Data Coding
   = DCS Coding Group for CBS: CBS DCS: Language using the GSM 7-bit 
 default alphabet (0x00)
 ..00  = DCS CBS Message language: German (0x00)
 
 Optional parameters
 Optional parameter: source_network_type (0x000e)
 Tag: 0x000e
 Length: 1
 Originator network: GSM (0x01)
 
 
 We think Kannel hits the assert != null error when it tries to parse the URL 
 used for pushing the message to our server.
 
 Do you know what patch we could apply to fix this problem?
 
 Thanks indeed.
 
 ///RGB
 
 
 Subject: Re: Kannel PANICS octstr_convert_range
 From: amal...@kannel.org
 Date: Thu, 27 Sep 2012 10:30:25 +0200
 CC: users@kannel.org
 To: rob_gar_...@hotmail.com
 
 Hi Rob,
 
 you are looking in the wrong direction. As far as I see from your crash 
 it's so that bearerbox send message to smsbox
 and not another way around. Therefore you have to check, what you still 
 have in the store file (if you delete it then also delete .bak files)
 and see in the access log of bearerbox which message cause crash.
 
 Alex
 
 P.S. I would suggest to upgrade to SVN version, it's more stable and 
 maintained as 1.4.3. 1.4.3 is very very old.
 
 On 27.09.2012, at 10:06, Rob GB rob_gar_...@hotmail.com wrote:
 
 
 Hi Alex,
 
 I'm using Kannel 1.4.3, sorry for not mentioning this before.
 
 Do you know by chance the context of where the error appeared in smsbox? I 
 would like to understand the possible ways we can trigger the “assert != 
 null” to fail.
 
 Back-tracking from the error I find the following places the error could 
 have come from:
 
 ~/tmp/kannel$ find . -name *.c -exec grep -iH octstr_convert_range {} \;
 
 ./gateway-1.4.3/gw/xml_shared.c: octstr_convert_range(charset, 0, 
 octstr_len(charset), toupper);
 ./gateway-1.4.3/gw/urltrans.c: octstr_convert_range(tmp, 0, 
 octstr_len(tmp), tolower);
 ./gateway-1.4.3/gw/urltrans.c: octstr_convert_range(os, 0, octstr_len(os), 
 tolower);
 ./gateway-1.4.3/gw/urltrans.c: octstr_convert_range(data, 0, 
 octstr_len(data), tolower);
 ./gateway-1.4.3/gw/wap_push_pap_compiler.c: octstr_convert_range(nameos, 
 0, octstr_len(nameos), tolower);
 ./gateway-1.4.3/gw/wap_push_pap_compiler.c: octstr_convert_range(*address, 
 0, octstr_len(*address), tolower);
 ./gateway-1.4.3/gw/wml_compiler.c: octstr_convert_range(escape, 0, 
 octstr_len(escape), tolower);
 ./gateway-1.4.3/gwlib/octstr.c:void octstr_convert_range(Octstr *ostr, 
 long pos, long len,
 ./gateway-1.4.3/gwlib/octstr.c: octstr_convert_range(ostr, 0, ostr-len, 
 make_printable);
 
 To me they all seem to point to an URL being bad or similar in a PAP 
 request. However I have not 

Re: Kannel PANICS octstr_convert_range

[Alexander Malysh]

Hi,

seems some queued message within bearerbox cause this panic. Try ether to 
upgrade to the latest SVN version
or delete bearerbox.store file.

Alex

On 26.09.2012, at 17:28, Rob GB rob_gar_...@hotmail.com wrote:

 
 Hi Kannel people,
 
 I have been using Kannel for almost 2 year, but today it has crashed and 
 cannot make it work:
 
 
 2012-09-26 17:15:23 [28324] [0] INFO: Added logfile 
 `/opt/kannel/log/smsbox.log' with level `1'.
 2012-09-26 17:15:23 [28324] [0] INFO: Logging accesses to 
 '/opt/kannel/log/access.log'.
 2012-09-26 17:15:23 [28324] [0] INFO: Started access logfile 
 `/opt/kannel/log/access.log'.
 2012-09-26 17:15:23 [28324] [0] INFO: HTTP: Opening server at port 13013.
 2012-09-26 17:15:23 [28324] [0] INFO: Set up send sms service at port 13013
 2012-09-26 17:15:23 [28324] [0] INFO: Connected to bearerbox at localhost 
 port 13001.
 2012-09-26 14:59:38 [754] [4] PANIC: gwlib/octstr.c:2481: seems_valid_real: 
 Assertion `ostr != NULL' failed. (Called from 
 gwlib/octstr.c:836:octstr_convert_range.)
 2012-09-26 14:59:38 [754] [4] PANIC: /opt/kannel/sbin/smsbox(gw_panic+0x15b) 
 [0x43c74b]
 2012-09-26 14:59:38 [754] [4] PANIC: /opt/kannel/sbin/smsbox [0x43cfc9]
 2012-09-26 14:59:38 [754] [4] PANIC: 
 /opt/kannel/sbin/smsbox(octstr_convert_range+0x3d) [0x43d49d]
 2012-09-26 14:59:38 [754] [4] PANIC: 
 /opt/kannel/sbin/smsbox(urltrans_find+0x55) [0x41cf75]
 2012-09-26 14:59:38 [754] [4] PANIC: /opt/kannel/sbin/smsbox [0x4156e0]
 2012-09-26 14:59:38 [754] [4] PANIC: /opt/kannel/sbin/smsbox [0x4337d5]
 2012-09-26 14:59:38 [754] [4] PANIC: /lib64/libpthread.so.0 [0x372c20673d]
 2012-09-26 14:59:38 [754] [4] PANIC: /lib64/libc.so.6(clone+0x6d) 
 [0x372b6d3d1d]
 
 Neither Kannel nor our app nor the operating system have changed, Kannel just 
 entered in PANIC and stopped working.
 
 Kindly assist. Thanks.
 
 ///RGB
 
 

Re: Smsbox sometimes doesn't servicing request

[Alexander Malysh]

Hi,

do I read this correct, the way smsbox talk to sqlbox? or do you mean bearerbox 
talk to sqlbox?

Alex

On 21.09.2012, at 03:34, Willy Mularto sangpr...@gmail.com wrote:

 Hi Alex,
 I did some researches on this matter and can confirm that this issue started 
 right after meta-data was implemented (r4682). And It is more the way SMSBox 
 talk to SQLBox and vice versa. Today I am going to compile current SQLBox SVN 
 against r4681 and let's see the result.
 
 
 
 On Sep 20, 2012, at 11:23 PM, Alexander Malysh wrote:
 
 Hi,
 
 is this only sqlbox bug or smsbox as well?
 
 Thanks,
 Alex
 
 On 20.09.2012, at 04:42, Willy Mularto sangpr...@gmail.com wrote:
 
 Yes, all use the latest SVN. I can confirm this is a bug and an old bug 
 actually (since meta-data implemented). Already posted to redmine and 
 contacted developers. Hope they can found the solution.
 
 
 
 On Sep 19, 2012, at 10:47 PM, spameden wrote:
 
 Hey Willy!
 
 Did you use latest version from SVN?
 
 2012/9/19 Rene Kluwen rene.klu...@chimit.nl
 You seem to have crossed an old sqlbox bug.
 I remember, under high load, sqlbox misses some MO messages.
 
 As of now, for all I know, this hasn't been solved yet.
 
 == Rene
 
 -Original Message-
 From: users-boun...@vm1.kannel.org [mailto:users-boun...@vm1.kannel.org] On
 Behalf Of Willy Mularto
 Sent: Wednesday, 19 September, 2012 12:35
 To: kannel users@kannel.org
 Subject: Smsbox sometimes doesn't servicing request
 
 Guys,
 I have a weird situation. smsbox sometimes doesn't servicing request (not
 forward MO to get-url). Here is my configuration:
 
 group = core
 admin-port = 7960
 smsbox-port = 7961
 admin-password = kannel
 status-password = kannel
 box-allow-ip = 127.0.0.1;192.168.8.
 store-type = spool
 store-location = /home/kannel/var/queue
 sms-incoming-queue-limit = -1
 sms-outgoing-queue-limit = -1
 store-dump-freq = 5
 dlr-storage = mysql
 sms-resend-freq = 60
 sms-resend-retry = -1
 smsbox-max-pending = 100
 log-file = /home/kannel/var/log/bearerbox.log
 access-log = /home/kannel/var/log/bearerbox-access.log
 log-level = 0
 
 group = mysql-connection
 id = mydlr
 host = 192.168.8.3
 username = kannel
 password = password
 database = traffics
 
 group = dlr-db
 id = mydlr
 table = partner_dlr
 field-smsc = smsc
 field-timestamp = ts
 field-destination = destination
 field-source = source
 field-service = service
 field-url = url
 field-mask = mask
 field-status = status
 field-boxc-id = boxc
 
 group = smsc
 smsc = http
 system-type = kannel
 smsc-id = kannel
 smsc-username = kanneluser
 smsc-password = kannelpass
 port = 7278
 send-url = http://192.168.8.2/test.php;
 connect-allow-ip = 127.0.0.1;192.168.8.2
 allowed-smsc-id = kannel
 log-file = /home/kannel/var/log/partner.log
 log-level = 0
 
 group = smsbox-route
 smsbox-id = smsbox
 smsc-id = kannel
 
 group = sendsms-user
 username = kannel
 password = kannel
 max-messages = 10
 concatenation = true
 
 group = sms-service
 keyword = default
 get-url =
 http://handler.kannel.gw:4684/?sender=%preceiver=%Psms=%atelco=%imsgid=
 %Ifid=%F
 catch-all = true
 omit-empty = true
 max-messages = 0
 
 group = smsbox
 smsbox-id = smsbox
 sendsms-port = 7962
 bearerbox-port = 7963
 http-request-retry = 100
 http-queue-delay = 10
 max-pending-requests = 8192
 mo-recode = 1
 log-file = /home/kannel/var/log/smsbox_1.log
 access-log = /home/kannel/var/log/smsbox-access_1.log
 log-level = 1
 
 group = mysql-connection
 id = smsgw-db
 host = 192.168.8.3
 port = 3306
 username = kannel
 password = password
 database = traffics
 max-connections = 10
 
 group = sqlbox
 id = smsgw-db
 bearerbox-port = 7961
 smsbox-id = smsbox
 smsbox-port = 7963
 sql-log-table = partner_sent
 sql-insert-table = partner_queue
 log-file = /home/kannel/var/log/sqlbox_1_pull.log
 log-level = 0
 
 Willy Mularto
 F300HD+MR18DE (NLC1725)
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 Willy Mularto
 F300HD+MR18DE (NLC1725)
 
 
 
 
 
 
 
 
 
 
 
 Willy Mularto
 F300HD+MR18DE (NLC1725)
 
 
 
 
 
 
 
 
 

Re: Smsbox sometimes doesn't servicing request

[Alexander Malysh]

Hi,

is this only sqlbox bug or smsbox as well?

Thanks,
Alex

On 20.09.2012, at 04:42, Willy Mularto sangpr...@gmail.com wrote:

 Yes, all use the latest SVN. I can confirm this is a bug and an old bug 
 actually (since meta-data implemented). Already posted to redmine and 
 contacted developers. Hope they can found the solution.
 
 
 
 On Sep 19, 2012, at 10:47 PM, spameden wrote:
 
 Hey Willy!
 
 Did you use latest version from SVN?
 
 2012/9/19 Rene Kluwen rene.klu...@chimit.nl
 You seem to have crossed an old sqlbox bug.
 I remember, under high load, sqlbox misses some MO messages.
 
 As of now, for all I know, this hasn't been solved yet.
 
 == Rene
 
 -Original Message-
 From: users-boun...@vm1.kannel.org [mailto:users-boun...@vm1.kannel.org] On
 Behalf Of Willy Mularto
 Sent: Wednesday, 19 September, 2012 12:35
 To: kannel users@kannel.org
 Subject: Smsbox sometimes doesn't servicing request
 
 Guys,
 I have a weird situation. smsbox sometimes doesn't servicing request (not
 forward MO to get-url). Here is my configuration:
 
 group = core
 admin-port = 7960
 smsbox-port = 7961
 admin-password = kannel
 status-password = kannel
 box-allow-ip = 127.0.0.1;192.168.8.
 store-type = spool
 store-location = /home/kannel/var/queue
 sms-incoming-queue-limit = -1
 sms-outgoing-queue-limit = -1
 store-dump-freq = 5
 dlr-storage = mysql
 sms-resend-freq = 60
 sms-resend-retry = -1
 smsbox-max-pending = 100
 log-file = /home/kannel/var/log/bearerbox.log
 access-log = /home/kannel/var/log/bearerbox-access.log
 log-level = 0
 
 group = mysql-connection
 id = mydlr
 host = 192.168.8.3
 username = kannel
 password = password
 database = traffics
 
 group = dlr-db
 id = mydlr
 table = partner_dlr
 field-smsc = smsc
 field-timestamp = ts
 field-destination = destination
 field-source = source
 field-service = service
 field-url = url
 field-mask = mask
 field-status = status
 field-boxc-id = boxc
 
 group = smsc
 smsc = http
 system-type = kannel
 smsc-id = kannel
 smsc-username = kanneluser
 smsc-password = kannelpass
 port = 7278
 send-url = http://192.168.8.2/test.php;
 connect-allow-ip = 127.0.0.1;192.168.8.2
 allowed-smsc-id = kannel
 log-file = /home/kannel/var/log/partner.log
 log-level = 0
 
 group = smsbox-route
 smsbox-id = smsbox
 smsc-id = kannel
 
 group = sendsms-user
 username = kannel
 password = kannel
 max-messages = 10
 concatenation = true
 
 group = sms-service
 keyword = default
 get-url =
 http://handler.kannel.gw:4684/?sender=%preceiver=%Psms=%atelco=%imsgid=
 %Ifid=%F
 catch-all = true
 omit-empty = true
 max-messages = 0
 
 group = smsbox
 smsbox-id = smsbox
 sendsms-port = 7962
 bearerbox-port = 7963
 http-request-retry = 100
 http-queue-delay = 10
 max-pending-requests = 8192
 mo-recode = 1
 log-file = /home/kannel/var/log/smsbox_1.log
 access-log = /home/kannel/var/log/smsbox-access_1.log
 log-level = 1
 
 group = mysql-connection
 id = smsgw-db
 host = 192.168.8.3
 port = 3306
 username = kannel
 password = password
 database = traffics
 max-connections = 10
 
 group = sqlbox
 id = smsgw-db
 bearerbox-port = 7961
 smsbox-id = smsbox
 smsbox-port = 7963
 sql-log-table = partner_sent
 sql-insert-table = partner_queue
 log-file = /home/kannel/var/log/sqlbox_1_pull.log
 log-level = 0
 
 Willy Mularto
 F300HD+MR18DE (NLC1725)
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 Willy Mularto
 F300HD+MR18DE (NLC1725)
 
 
 
 
 
 
 
 
 

Re: Facing an issue starting up Kannel

[Alexander Malysh]

Hi,

this is not true. I use Mac each day and test/develop Kannel on Mac and never 
saw such issue.
Could you please test the latest SVN version and let us know which OSX version 
are you using?

Alex

Am 04.09.2012 um 11:05 schrieb Manoj M N m4n0...@gmail.com:

 Thanks Rene. So I suppose kannel was never tried on a mac. My production 
 setup will be linux, but that will take a while. So I thought I will test out 
 on my dev laptop.
 
 Regards,
 
 On Fri, Aug 31, 2012 at 11:01 AM, Rene Kluwen rene.klu...@chimit.nl wrote:
 Please always copy the users list when asking for support.
 
  
 
 This is interesting. Unfortunately I don’t have access to a Mac. To debug 
 this further.
 
 But maybe one of the other developers has.
 
 The bug is pretty straight forward. But can be one of as many as 11 
 parameters that probably has a NULL or uninitialized value.
 
  
 
 == Rene
 
  
 
 From: Manoj M N [mailto:m4n0...@gmail.com] 
 Sent: Friday, 31 August, 2012 03:20
 To: Rene Kluwen
 Subject: Re: Facing an issue starting up Kannel
 
  
 
 Thanks for the help Rene, Please see attached the requested info. If you need 
 more info, please let me know.
 
 Thanks,
 
 On Fri, Aug 31, 2012 at 2:23 AM, Rene Kluwen rene.klu...@chimit.nl wrote:
 
 Is it possible for you to start bearerbox with gdb and do a backtrace on it?
 
  
 
 == Rene
 
  
 
 From: users-boun...@vm1.kannel.org [mailto:users-boun...@vm1.kannel.org] On 
 Behalf Of Manoj M N
 Sent: Thursday, 30 August, 2012 18:26
 To: us...@vm1.kannel.org
 Subject: Facing an issue starting up Kannel
 
  
 
 Hello, 
 
 I am very new to WAP/SMS gateways and my requirement goes as far as to get 
 SMS messages sent out using my 3G data card with a SIM card in it for now. So 
 as you can see my requirement is pretty basic.
 
 I use a MAC and I downloaded the source code and compiled/installed kannel. I 
 have put a sample config file as per the documentation 
 group = core
 admin-port = 13000
 admin-password = f00bar
 
 # Default service.
 group = sms-service
 keyword = default
 text = No services defined
 
 When I try to start 
 007/-- sudo /usr/local/sbin/bearerbox -v 1 
 Password:
 2012-08-30 21:57:44 [599] [0] INFO: Debug_lvl = 1, log_file = none, log_lvl 
 = 0
 2012-08-30 21:57:44 [599] [0] WARNING: DLR: using default 'internal' for 
 storage type.
 2012-08-30 21:57:44 [599] [0] INFO: DLR using storage type: internal
 Segmentation fault
 
 I am getting this error and it is not coming up at all. 
 
 I am possibly doing something stupid, can you please help me understand?
 
 Regards,
 
  
 
 

Re: Kannel HTTP SMSC Segmentation Fault

[Alexander Malysh]

Hi,

fixed in SVN.

Alex

Am 31.08.2012 um 08:08 schrieb Willy Mularto sangpr...@gmail.com:

 This is HTTP SMSC not sendsms CGI.
 
 
 
 On Aug 31, 2012, at 1:01 PM, Otandeka Simon Peter wrote:
 
 
 Please attach your config file so that we can see what you missed out.
 
 Try lynx -dump 
 'http://localhost:13015/cgi-bin/sendsms?from=0987654321to12345username=norkpassword=z0rksmsc=your
  smsc id'
 
 On Fri, Aug 31, 2012 at 5:55 AM, Willy Mularto sangpr...@gmail.com wrote:
 Just compiled the latest svn execute the bearerbox:
 2012-08-31 09:54:35 [28393] [0] INFO: HTTP[kannel]: Initiated and ready
 2012-08-31 09:54:35 [28393] [8] DEBUG: Thread 8 
 (gw/smsc/smsc_http.c:httpsmsc_send_cb) maps to pid 28393.
 2012-08-31 09:54:35 [28393] [0] DEBUG: Started thread 10 
 (gw/bb_smscconn.c:sms_router)
 
 Try to hit it:
 sprabv@smsgw1:~/gw/test$ lynx -dump 
 'http://localhost:13015/?from=0987654321to12345username=norkpassword=z0rksmsc-id=your
  smsc id'
 
 Looking up localhost:13015
 Making HTTP connection to localhost:13015
 Sending HTTP request.
 HTTP request sent; waiting for response.
 Alert!: Unexpected network read error; connection aborted.
 Can't Access 
 `http://localhost:13015/?from=0987654321to12345username=norkpassword=z0rk'
 Alert!: Unable to access document.
 
 lynx: Can't access startfile
 
 
 The log said:
 2012-08-31 09:54:43 [28393] [7] DEBUG: HTTP[kannel]: Got request 
 `/?from=0987654321to12345=username=norkpassword=z0rk'
 2012-08-31 09:54:43 [28393] [7] PANIC: sbin/bearerbox() [0x49257c]
 2012-08-31 09:54:43 [28393] [7] PANIC: /lib/libpthread.so.0(+0xf8f0) 
 [0x7f0b2c5a18f0]
 2012-08-31 09:54:43 [28393] [7] PANIC: sbin/bearerbox() [0x44e1f8]
 2012-08-31 09:54:43 [28393] [7] PANIC: sbin/bearerbox() [0x47e5be]
 2012-08-31 09:54:43 [28393] [7] PANIC: /lib/libpthread.so.0(+0x69ca) 
 [0x7f0b2c5989ca]
 2012-08-31 09:54:43 [28393] [7] PANIC: /lib/libc.so.6(clone+0x6d) 
 [0x7f0b2bfa5cdd]
 
 The weird is bearerbox can't identify the smsc-id name. It is said null
 
 
 
 
 Willy Mularto
 F300HD+MR18DE (NLC1725)
 
 
 
 
 
 
 
 
 
 
 
 
 Willy Mularto
 F300HD+MR18DE (NLC1725)
 
 
 
 
 
 
 
 
 

Re: Kannel and SMPP

[Alexander Malysh]

Hi,

please use us...@kanel.org mailing list.

Thanks,
Alexander Malysh

Am 21.08.2012 um 12:00 schrieb Gideon Karuga gideonkar...@yahoo.com:

 
 Hi Amalysh, 
 
 Sorry to trouble you, was wondering if you could please assist me in Kannel 
 setup for smpp connection. 
 
 I have done everything according to the book, I do not know where I might be 
 going wrong. 
 
 I am setting up kannel with smpp, your assistance is greatly appreciated. 
 
 Thanks and Best Regards, 
 
 Gideon Karuga,
 
 

test, pls ignore

[Alexander Malysh]

Re: SMPP and system_error

[Alexander Malysh]

Hi,

as far as I know higate require some TLVs to be defined and sent. Please check 
their API and configure SMPP
appropriate.

Thanks,
Alex

Am 07.07.2012 um 01:00 schrieb Emmanuel CHANSON:

 Thanks for your reply
 
 Yes I can see the line:
 DEBUG:   message_id: NULL but in submit_sm_resp
 so I thought the warning is about the missing message_id = NULL presence in 
 submit_sm ?
 
 BTW what mean and for what is used this ? stg to make the submit_response 
 come back with an id or not ?
 I guess this is required for DLR ?
 How to make it return an id ?
 
 And how to force it to NULL in submit_sm ?
 
 I would like to remove this warning so that provider wont take this warning 
 as THE problem and we focus on the system_error problem
 
 Regards,
 
 Emmanuel
 
 2012/7/7 Rene Kluwen rene.klu...@chimit.nl
 Weird… according to your logs, message_id HAS a null.
 
 Nonetheless the system error (8) is a different issue.
 
  
 
 From: Emmanuel CHANSON [mailto:emmanuelchan...@gmail.com] 
 Sent: Saturday, 07 July, 2012 00:36
 To: Rene Kluwen
 Cc: users
 Subject: Re: SMPP and system_error
 
  
 
 Hello,
 
 Do you have any clue on how to resolve this warning ?
 WARNING: SMPP: PDU NULL terminated string (message_id) has no NULL.
 
 Regards
 
 2012/7/6 Emmanuel CHANSON emmanuelchan...@gmail.com
 
 Thanks Rene for your help,
 
 Higate support reply me this about this error:
 
 
 WARNING: SMPP: PDU NULL terminated string (message_id) has no NULL.
 
 Please note that this is not a warning but an error, it is not an higate 
 error but the SMPP protocol error, if you do not null terminate the tlv's 
 within SMPP the higate system might kick it.
 
 What does it mean ?
 
 Regards,
 
 Emmanuel
 
  
 
 2012/7/4 Rene Kluwen rene.klu...@chimit.nl
 
 The best you can do is ask your provider what it means.
 
 They are giving this error.
 
  
 
 From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of 
 Emmanuel CHANSON
 Sent: Tuesday, 03 July, 2012 22:39
 To: users
 Subject: SMPP and system_error
 
  
 
 Hello,
 
 Trying to connect to a Mobile Aggregator through SMPP I got this error:
 
 SMSC returned error code 0x0008 (System Error) in response to submit_sm.
 
 Also this:
 WARNING: SMPP: PDU NULL terminated string (message_id) has no NULL. 
 but I guess this is not the real problem but how to handle this also ?
 
 Kannel.conf:#SMSC SMPP
 group=smsc
 smsc=smpp
 smsc-id=higate
 interface-version=34
 host=**
 port=2775
 system-id = 
 smsc-username = 
 smsc-password=
 system-type
 transceiver-mode=1
 #source-addr-autodetect = false
 #address-range = 
 source-addr-ton = 1
 source-addr-npi = 1
 dest-addr-ton = 1
 dest-addr-npi = 1
 bind-addr-ton = 1
 bind-addr-npi = 1
 #msg-id-type = 0x01
 log-file = /var/log/kannel/smsc-smpp.log
 log-level = 0
 
 
 == /var/log/kannel/smsc-smpp.log ==
 2012-07-04 08:02:20 [26432] [7] DEBUG: SMPP[higate]: throughput (0.00,0.00)
 2012-07-04 08:02:20 [26432] [7] DEBUG: SMPP[higate]: Manually forced source 
 addr ton = 1, source add npi = 1
 2012-07-04 08:02:20 [26432] [7] DEBUG: SMPP[higate]: Manually forced dest 
 addr ton = 1, dest add npi = 1
 2012-07-04 08:02:20 [26432] [7] DEBUG: SMPP[higate]: Sending PDU:
 2012-07-04 08:02:20 [26432] [7] DEBUG: SMPP PDU 0x7fb69c000a10 dump:
 2012-07-04 08:02:20 [26432] [7] DEBUG:   type_name: submit_sm
 2012-07-04 08:02:20 [26432] [7] DEBUG:   command_id: 4 = 0x0004
 2012-07-04 08:02:20 [26432] [7] DEBUG:   command_status: 0 = 0x
 2012-07-04 08:02:20 [26432] [7] DEBUG:   sequence_number: 2 = 0x0002
 2012-07-04 08:02:20 [26432] [7] DEBUG:   service_type: NULL
 2012-07-04 08:02:20 [26432] [7] DEBUG:   source_addr_ton: 1 = 0x0001
 2012-07-04 08:02:20 [26432] [7] DEBUG:   source_addr_npi: 1 = 0x0001
 2012-07-04 08:02:20 [26432] [7] DEBUG:   source_addr: 2034
 2012-07-04 08:02:20 [26432] [7] DEBUG:   dest_addr_ton: 1 = 0x0001
 2012-07-04 08:02:20 [26432] [7] DEBUG:   dest_addr_npi: 1 = 0x0001
 2012-07-04 08:02:20 [26432] [7] DEBUG:   destination_addr: 254724886107
 2012-07-04 08:02:20 [26432] [7] DEBUG:   esm_class: 3 = 0x0003
 2012-07-04 08:02:20 [26432] [7] DEBUG:   protocol_id: 0 = 0x
 2012-07-04 08:02:20 [26432] [7] DEBUG:   priority_flag: 0 = 0x
 2012-07-04 08:02:20 [26432] [7] DEBUG:   schedule_delivery_time: NULL
 2012-07-04 08:02:20 [26432] [7] DEBUG:   validity_period: NULL
 2012-07-04 08:02:20 [26432] [7] DEBUG:   registered_delivery: 0 = 0x
 2012-07-04 08:02:20 [26432] [7] DEBUG:   replace_if_present_flag: 0 = 
 0x
 2012-07-04 08:02:20 [26432] [7] DEBUG:   data_coding: 0 = 0x
 2012-07-04 08:02:20 [26432] [7] DEBUG:   sm_default_msg_id: 0 = 0x
 2012-07-04 08:02:20 [26432] [7] DEBUG:   sm_length: 6 = 0x0006
 2012-07-04 08:02:20 [26432] [7] DEBUG:   short_message:
 2012-07-04 08:02:20 [26432] [7] DEBUG:Octet string at 0x7fb69c000c20:
 2012-07-04 08:02:20 [26432] [7] DEBUG:  len:  6
 2012-07-04 08:02:20 [26432] [7] DEBUG: 

Re: Meta data parameters in kannel snapshot version (31/08/2010)

[Alexander Malysh]

Hi,

meta-data is not supported in smsc group. Userguide was wrong, I just fixed it.

Thanks,
Alex

Am 31.05.2012 um 08:52 schrieb Sam:

 Hi Alwaro,
 
 I am using one of the most recent snapshots as you can see from the log 
 below. This is i believe is 1.5.
 
 2012-05-16 23:48:14 [10478] [0] DEBUG: Kannel bearerbox version `svn-r4974'.
 Build `May 12 2012 17:14:19', compiler `4.4.4 20100726 (Red Hat 4.4.4-13)'.
 System Linux, release 2.6.32-71.el6.i686, version #1 SMP Wed Dec 15 09:50:18 
 EST 2010, machine i686.
 Hostname kannelgw, IP 192.168.1.34.
 Libxml version 2.7.6.
 Using OpenSSL 1.0.0-fips 29 Mar 2010.
 Using Oracle OCI 11.2.
 Using native malloc.
 
 
 On Wed, May 30, 2012 at 4:45 PM, Alvaro Cornejo cornejo.alv...@gmail.com 
 wrote:
 What kannel version are you using?
 
 1.4.3 does not support it.
 
 Regards
 
 Alvaro
 
 On 5/30/12, Sam nu.e...@gmail.com wrote:
  Hi Group,
 
  When i try to specify  'meta-data' in my config I get the error below.
  However in the userguide,  'meta-data' was specified as an option.
 
  2012-05-30 15:50:47 [30833] [0] ERROR: Group 'smsc' may not contain field
  'meta-data'.
 
  --
  Sam
 
 
 
 --
 |-|
 Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
 celular y Nextel
 en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via
 SMS y GPRS online
  Visitenos en www.perusms.NET www.smsglobal.com.mx y
 www.pravcom.com
 

Re: Meta data parameters in kannel snapshot version (31/08/2010)

[Alexander Malysh]

you can pass meta-data as cgi parameter, header or xml tag via smsbox. Please 
check userguide how to do it.

Thanks,
Alex

Am 31.05.2012 um 09:40 schrieb Sam:

 Humm... Tnx Alex M.
 
 So where do I specify meta-data directly? I need to pass a custom parameter 
 and value to the USSDC for authentication.
 
 N.B. I was also wondering how the initial poster of this thread got away with 
 it in his own config.
 
 On Thu, May 31, 2012 at 8:28 AM, Alexander Malysh amal...@kannel.org wrote:
 Hi,
 
 meta-data is not supported in smsc group. Userguide was wrong, I just fixed 
 it.
 
 Thanks,
 Alex
 
 Am 31.05.2012 um 08:52 schrieb Sam:
 
 Hi Alwaro,
 
 I am using one of the most recent snapshots as you can see from the log 
 below. This is i believe is 1.5.
 
 2012-05-16 23:48:14 [10478] [0] DEBUG: Kannel bearerbox version `svn-r4974'.
 Build `May 12 2012 17:14:19', compiler `4.4.4 20100726 (Red Hat 4.4.4-13)'.
 System Linux, release 2.6.32-71.el6.i686, version #1 SMP Wed Dec 15 09:50:18 
 EST 2010, machine i686.
 Hostname kannelgw, IP 192.168.1.34.
 Libxml version 2.7.6.
 Using OpenSSL 1.0.0-fips 29 Mar 2010.
 Using Oracle OCI 11.2.
 Using native malloc.
 
 
 On Wed, May 30, 2012 at 4:45 PM, Alvaro Cornejo cornejo.alv...@gmail.com 
 wrote:
 What kannel version are you using?
 
 1.4.3 does not support it.
 
 Regards
 
 Alvaro
 
 On 5/30/12, Sam nu.e...@gmail.com wrote:
  Hi Group,
 
  When i try to specify  'meta-data' in my config I get the error below.
  However in the userguide,  'meta-data' was specified as an option.
 
  2012-05-30 15:50:47 [30833] [0] ERROR: Group 'smsc' may not contain field
  'meta-data'.
 
  --
  Sam
 
 
 
 --
 |-|
 Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
 celular y Nextel
 en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via
 SMS y GPRS online
  Visitenos en www.perusms.NET www.smsglobal.com.mx y
 www.pravcom.com
 
 
 

Re: kannel DLR states

[Alexander Malysh]

Hi,

rejected will be generated in the upper layer so no need to patch anything.
As to the status codes: you don't really need status code what you need is the 
error code, check meta data errorcode field.

Alex

Am 10.04.2012 um 23:22 schrieb spameden:

 Hello, list.
 
 Sometimes it's good to know the exact reason why sms was failed.
 
 Is there any way I can get extended information about message delivery status?
 
 i.e. if it was REJECTED / UNDELIVERABLE / DELETED / EXPIRED
 
 According to SMPP v3.4 message states are:
 
 Message State Value Description
 ENROUTE 1 The message is in enroute
 state.
 DELIVERED 2 Message is delivered to
 destination
 EXPIRED 3 Message validity period has
 expired.
 DELETED 4 Message has been deleted.
 UNDELIVERABLE 5 Message is undeliverable
 ACCEPTED 6 Message is in accepted state
 (i.e. has been manually read
 on behalf of the subscriber by
 customer service)
 UNKNOWN 7 Message is in invalid state
 REJECTED 8 Message is in a rejected state
 
 Kannel seems to give status = 1 for delivered messages and status = 2 for all 
 other failed messages (i.e. EXPIRED / REJECTED / UNDELIVERABLE, etc).
 
 Kannel's documentation says there is a 16 status for REJECTED messages, but 
 kannel still gives status 2 instead. SMSC sends correct message state 8.
 
 I checked the source also it seems there is no handling of additional 
 statuses in code (from gw/smsc/smsc_smpp.c):
 
 /* first check for SMPP v3.4 and above */
 1291 if (smpp-version  0x33  receipted_message_id) {
 1292 msgid = octstr_duplicate(receipted_message_id);
 1293 switch(message_state) {
 1294 case 1: /* ENROUTE */
 1295 case 6: /* ACCEPTED */
 1296 dlrstat = DLR_BUFFERED;
 1297 break;
 1298 case 2: /* DELIVERED */
 1299 dlrstat = DLR_SUCCESS;
 1300 break;
 1301 case 3: /* EXPIRED */
 1302 case 4: /* DELETED */
 1303 case 5: /* UNDELIVERABLE */
 1304 case 7: /* UNKNOWN */
 1305 case 8: /* REJECTED */
 1306 dlrstat = DLR_FAIL;
 1307 break;
 1308 case -1: /* message state is not present, partial SMPP v3.4 */
 1309 debug(bb.sms.smpp, 0, SMPP[%s]: Partial SMPP v3.4, 
 receipted_message_id present but not message_state.,
 1310 octstr_get_cstr(smpp-conn-id));
 1311 dlrstat = -1;
 1312 break;
 1313 default:
 1314 warning(0, SMPP[%s]: Got DLR with unknown 'message_state' 
 (%ld).,
 1315 octstr_get_cstr(smpp-conn-id), message_state);
 1316 dlrstat = DLR_FAIL;
 1317 break;
 1318 }
 1319 }
 
 
 What's the right way to get additional information about message state from 
 kannel? 
 
 Should I modify source or I can use somehow msgdata field from DLR somehow 
 with stat code (REJECTD/DELIVRD/etc) ?
 
 Thanks in advance.
 
 
 

Re: kannel DLR states

[Alexander Malysh]

Recent SVN version of Kannel does this for you. No need todo anything, check 
metadata field in your DLR.

Alex

Am 11.04.2012 um 10:46 schrieb spameden:

 How I can get this value without parsing msgdata field of incoming DLR?
 
 (I'm on sqlbox, inserting records to send sms, sqlbox is between berarerbox 
 and smsbox).
 
 
 2012/4/11 Alexander Malysh amal...@kannel.org
 Hi,
 
 rejected will be generated in the upper layer so no need to patch anything.
 As to the status codes: you don't really need status code what you need is 
 the error code, check meta data errorcode field.
 
 Alex
 
 Am 10.04.2012 um 23:22 schrieb spameden:
 
  Hello, list.
 
  Sometimes it's good to know the exact reason why sms was failed.
 
  Is there any way I can get extended information about message delivery 
  status?
 
  i.e. if it was REJECTED / UNDELIVERABLE / DELETED / EXPIRED
 
  According to SMPP v3.4 message states are:
 
  Message State Value Description
  ENROUTE 1 The message is in enroute
  state.
  DELIVERED 2 Message is delivered to
  destination
  EXPIRED 3 Message validity period has
  expired.
  DELETED 4 Message has been deleted.
  UNDELIVERABLE 5 Message is undeliverable
  ACCEPTED 6 Message is in accepted state
  (i.e. has been manually read
  on behalf of the subscriber by
  customer service)
  UNKNOWN 7 Message is in invalid state
  REJECTED 8 Message is in a rejected state
 
  Kannel seems to give status = 1 for delivered messages and status = 2 for 
  all other failed messages (i.e. EXPIRED / REJECTED / UNDELIVERABLE, etc).
 
  Kannel's documentation says there is a 16 status for REJECTED messages, but 
  kannel still gives status 2 instead. SMSC sends correct message state 8.
 
  I checked the source also it seems there is no handling of additional 
  statuses in code (from gw/smsc/smsc_smpp.c):
 
  /* first check for SMPP v3.4 and above */
  1291 if (smpp-version  0x33  receipted_message_id) {
  1292 msgid = octstr_duplicate(receipted_message_id);
  1293 switch(message_state) {
  1294 case 1: /* ENROUTE */
  1295 case 6: /* ACCEPTED */
  1296 dlrstat = DLR_BUFFERED;
  1297 break;
  1298 case 2: /* DELIVERED */
  1299 dlrstat = DLR_SUCCESS;
  1300 break;
  1301 case 3: /* EXPIRED */
  1302 case 4: /* DELETED */
  1303 case 5: /* UNDELIVERABLE */
  1304 case 7: /* UNKNOWN */
  1305 case 8: /* REJECTED */
  1306 dlrstat = DLR_FAIL;
  1307 break;
  1308 case -1: /* message state is not present, partial SMPP v3.4 */
  1309 debug(bb.sms.smpp, 0, SMPP[%s]: Partial SMPP v3.4, 
  receipted_message_id present but not message_state.,
  1310 octstr_get_cstr(smpp-conn-id));
  1311 dlrstat = -1;
  1312 break;
  1313 default:
  1314 warning(0, SMPP[%s]: Got DLR with unknown 'message_state' 
  (%ld).,
  1315 octstr_get_cstr(smpp-conn-id), message_state);
  1316 dlrstat = DLR_FAIL;
  1317 break;
  1318 }
  1319 }
 
 
  What's the right way to get additional information about message state from 
  kannel?
 
  Should I modify source or I can use somehow msgdata field from DLR somehow 
  with stat code (REJECTD/DELIVRD/etc) ?
 
  Thanks in advance.
 
 
 
 
 

Re: spam in issue comments on redmine.kannel.org

[Alexander Malysh]

Hi,

thanks for the tip. Just updated redmine and installed recaptcha plugin.

Alex

Am 03.04.2012 um 23:08 schrieb spameden:

 I noticed there are lots of spam-posts in the issues on redmine.kannel.org
 
 Examples:
 https://redmine.kannel.org/issues/322#note-10
 https://redmine.kannel.org/issues/95#note-13
 
 Would you consider adding a captcha for the self-registration / anonymous 
 users comments posting?
 
 Here is a captcha plugin for redmine:
 
 https://github.com/egroeper/redmine_recaptcha

Re: the tariff code

[Alexander Malysh]

Dear Michael,

I would suggest, you start read userguide:

http://kannel.org/download/kannel-userguide-snapshot/userguide.html#AEN6204

Thanks,
Alex

Am 02.04.2012 um 13:10 schrieb Michael Farouk:

 Dear Alexander,
  
 I have two TLV parameter, the first for “carrier routing code 0x1400” and the 
 second for “tariff code 0x1401” so I add two TLV parameter like that
  
 Carrier routing code
 group = smpp-tlv
 name = TLV-name….
 tag = 0x1400
 type = octetstring
 length = 20
 smsc-id = x
  
  
 Tariff code
 group = smpp-tlv
 name = TLV-name….
 tag = 0x1401
 type = octetstring
 length = 20
 smsc-id = x
  
 So in the metadata parameter I add a carrier name also when I add the 
 binfo=C500 in the MT url to charge 5 $ it was not work, I use wireshark to 
 check the packet I found only the carrier parameter in optional parameters  
  
 Optional parameters
 Optional parameter: 0x1400 (0x1400): 43415f57494e44
 Tag: 0x1400
 Length: 7
 Value: 43415f57494e44
  
 So I need to send additional parameter (for tariff code 0x1401) like that to 
 charge 5 $:
  
  
 Optional parameter: 0x1401 (0x1401): 43353030
 Tag: 0x1401
 Length: 4
 Value: 43353030
  
  
 Best Regards
 Michael Farouk | Network  Platform Coordinator  
 ARPUPLUS – An Orascom Telecom Company
 Algeria | Morocco | Tunisia | Egypt | Sudan | Jordan | Lebanon | Iraq | KSA | 
 UAE | Yemen | 
 Palestine | Pakistan | Bangladesh | Italy | Canada | USA |
 Mob: +20.122.174.9662| Tel: +20.2.3345.8301/2 | Fax: +20.2.3304.3201
 Email: mfar...@arpuplus.com | Web: www.arpuplus.com
 image001.jpg
  
 From: Alexander Malysh [mailto:malys...@googlemail.com] On Behalf Of 
 Alexander Malysh
 Sent: Sunday, April 01, 2012 10:23 PM
 To: Michael Farouk
 Cc: users@kannel.org
 Subject: Re: the tariff code
  
 Hi,
  
 you have to send metadata in your request that include tlv name. Please check 
 metadata section in userguide.
  
 Thanks,
 Alex
  
 Am 01.04.2012 um 12:55 schrieb Michael Farouk:
 
 
 Dears,
  
 I faced problem kannel 1.5.0 in the tariff code; I connect with the USA 
 operator with the SMPP protocol so I have a TLV parameter for the tariff code 
 (0x1401) the following my TLV configuration:
  
 group = smpp-tlv
 name = TLV-name….
 tag = 0x1401
 type = octetstring
 length = 20
 smsc-id = x
  
 Also in the MT ULR to send message I add the parameter binfo=C500 it mean the 
 handset will be charge the 5 dollars, when use the wireshark to check the 
 packet between my kannel server and SMSC I cannot see the optional parameter 
 so this message not charge with 5 dollars.
  
 So I need to help to solve my problem,
  
 Best Regards
 Michael
  

Re: the tariff code

[Alexander Malysh]

Hi,

you have to send metadata in your request that include tlv name. Please check 
metadata section in userguide.

Thanks,
Alex

Am 01.04.2012 um 12:55 schrieb Michael Farouk:

 Dears,
  
 I faced problem kannel 1.5.0 in the tariff code; I connect with the USA 
 operator with the SMPP protocol so I have a TLV parameter for the tariff code 
 (0x1401) the following my TLV configuration:
  
 group = smpp-tlv
 name = TLV-name….
 tag = 0x1401
 type = octetstring
 length = 20
 smsc-id = x
  
 Also in the MT ULR to send message I add the parameter binfo=C500 it mean the 
 handset will be charge the 5 dollars, when use the wireshark to check the 
 packet between my kannel server and SMSC I cannot see the optional parameter 
 so this message not charge with 5 dollars.
  
 So I need to help to solve my problem,
  
 Best Regards
 Michael
  

Re: Inconsistent behavior around encoding and SMPP

[Alexander Malysh]

Hi,

cyrillic can only be send with ucs2 therefore coding=2.

Kannel behavior for coding=2 and 3 is simple: don't touch it it's binary and up 
to user to encode it BUT
if you need that kannel converts some charset to ucs2 for you then just use two 
params:
charset=YOUR_CHARSET
coding=2

Then kannel will do it for you.

Thanks,
Alex

Am 31.03.2012 um 00:45 schrieb chad selph:

 I understand that coding=2 stands for UCS-2 but the problem I'm pointing out 
 is that it doesn't actually re-encode the UTF8 bytes into actual UCS-2 bytes. 
  This is inconsistent because it will convert utf8 to GSM, or to Latin-1 (if 
 the alt-charset is set to Latin1).
 
 As far as the charset parameter: from my understand of the docs, it's 
 actually irrelevant to the SMPP stuff, this is just for you to tell smsbox 
 which percent encoding your text is in (URLs only support ascii).  It 
 defaults to UTF-8 in the newer versions and this is what prefer to use.  But 
 the important thing is that it has no relevance to the data_coding that gets 
 sent over SMPP.
 
 
 On Fri, Mar 30, 2012 at 3:20 PM, spameden spame...@gmail.com wrote:
 utf8 + coding=0 never worked for me for cyrillic text messages.
 
 the only combination is coding=2  charset=utf8, otherwise I'm getting 
 bollocks on mobile screen. 
 
 according to the kannel's documentation, coding is:
 
 coding number
 Optional. Sets the coding
 scheme bits in DCS field.
 Accepts values 0 to 2, for 7bit,
 8bit or UCS-2. If unset, defaults
 to 7 bits unless a udh is defined,
 which sets coding to 8bits.
 
 so coding=2 stands for UCS-2 message.
 
 
 2012/3/31 chad selph chad.se...@gmail.com
 I'm trying to figure out how to send different data encodings from Kannel 
 1.5.0 over SMPP.  The SMPP Spec lists the following options for data_coding 
 field:
 
 0 0 0 0 0 0 0 0 SMSC Default Alphabet
 0 0 0 0 0 0 0 1 IA5(CCITTT.50)/ASCII(ANSIX3.4)
 0 0 0 0 0 0 1 0 Octet unspecified (8-bit binary)
 0 0 0 0 0 0 1 1 Latin1(ISO-8859-1)
 0 0 0 0 0 1 0 0 Octet unspecified (8-bit binary)
 0 0 0 0 0 1 0 1 JIS(X0208-1990)
 0 0 0 0 0 1 1 0 Cyrllic(ISO-8859-5)
 0 0 0 0 0 1 1 1 Latin/Hebrew (ISO-8859-8)
 0 0 0 0 1 0 0 0 UCS2(ISO/IEC-10646)
 ... and some others.
 
 To initiate MT messages, we're using the sendsms http interface on smsbox 
 (the one here: 
 http://www.kannel.org/download/1.5.0/userguide-1.5.0/userguide.html#AEN4623 
 ).  It looks like the only relevant parameter into the sendsms is the 
 coding parameter, which can only be 0, 1, or 2.  0 causes data_coding 0, 
 1 causes 4, and 2 causes 8.  I don't see a way to set data_coding to 3, for 
 example, in order to do Latin-1.
 
 Another thing is that only 0 causes the message text to get encoded from 
 UTF-8 (input encoding from http) into the correct encoding.  For example, 
 sending the UTF-8 data with coding=2 does not re-encode the message into 
 USC-2, but just sends your UTF-8 bytes as if they were UCS-2 but sending utf8 
 data with coding=0 does re-encode them into GSM.
 
 These things seem to me to be incorrect behavior, however given the wide use 
 of kannel I figured I should make sure I'm not missing something obvious 
 before I draft a patch to attempt to fix them.  Am I missing something?
 
 

Re: Inconsistent behavior around encoding and SMPP

[Alexander Malysh]

Then I don't understand what should be the issue here :-) ?

Thanks,
Alex

Am 01.04.2012 um 23:15 schrieb spameden:

 Exactly what I've said :)
 
 If your source text is in utf8 you need to specify charset=utf8 and coding=2.
 
 2012/4/2 Alexander Malysh amal...@kannel.org
 Hi,
 
 cyrillic can only be send with ucs2 therefore coding=2.
 
 Kannel behavior for coding=2 and 3 is simple: don't touch it it's binary and 
 up to user to encode it BUT
 if you need that kannel converts some charset to ucs2 for you then just use 
 two params:
   charset=YOUR_CHARSET
   coding=2
 
 Then kannel will do it for you.
 
 Thanks,
 Alex
 
 Am 31.03.2012 um 00:45 schrieb chad selph:
 
 I understand that coding=2 stands for UCS-2 but the problem I'm pointing out 
 is that it doesn't actually re-encode the UTF8 bytes into actual UCS-2 
 bytes.  This is inconsistent because it will convert utf8 to GSM, or to 
 Latin-1 (if the alt-charset is set to Latin1).
 
 As far as the charset parameter: from my understand of the docs, it's 
 actually irrelevant to the SMPP stuff, this is just for you to tell smsbox 
 which percent encoding your text is in (URLs only support ascii).  It 
 defaults to UTF-8 in the newer versions and this is what prefer to use.  But 
 the important thing is that it has no relevance to the data_coding that gets 
 sent over SMPP.
 
 
 On Fri, Mar 30, 2012 at 3:20 PM, spameden spame...@gmail.com wrote:
 utf8 + coding=0 never worked for me for cyrillic text messages.
 
 the only combination is coding=2  charset=utf8, otherwise I'm getting 
 bollocks on mobile screen. 
 
 according to the kannel's documentation, coding is:
 
 coding number
 Optional. Sets the coding
 scheme bits in DCS field.
 Accepts values 0 to 2, for 7bit,
 8bit or UCS-2. If unset, defaults
 to 7 bits unless a udh is defined,
 which sets coding to 8bits.
 
 so coding=2 stands for UCS-2 message.
 
 
 2012/3/31 chad selph chad.se...@gmail.com
 I'm trying to figure out how to send different data encodings from Kannel 
 1.5.0 over SMPP.  The SMPP Spec lists the following options for data_coding 
 field:
 
 0 0 0 0 0 0 0 0 SMSC Default Alphabet
 0 0 0 0 0 0 0 1 IA5(CCITTT.50)/ASCII(ANSIX3.4)
 0 0 0 0 0 0 1 0 Octet unspecified (8-bit binary)
 0 0 0 0 0 0 1 1 Latin1(ISO-8859-1)
 0 0 0 0 0 1 0 0 Octet unspecified (8-bit binary)
 0 0 0 0 0 1 0 1 JIS(X0208-1990)
 0 0 0 0 0 1 1 0 Cyrllic(ISO-8859-5)
 0 0 0 0 0 1 1 1 Latin/Hebrew (ISO-8859-8)
 0 0 0 0 1 0 0 0 UCS2(ISO/IEC-10646)
 ... and some others.
 
 To initiate MT messages, we're using the sendsms http interface on smsbox 
 (the one here: 
 http://www.kannel.org/download/1.5.0/userguide-1.5.0/userguide.html#AEN4623 
 ).  It looks like the only relevant parameter into the sendsms is the 
 coding parameter, which can only be 0, 1, or 2.  0 causes data_coding 0, 
 1 causes 4, and 2 causes 8.  I don't see a way to set data_coding to 3, for 
 example, in order to do Latin-1.
 
 Another thing is that only 0 causes the message text to get encoded from 
 UTF-8 (input encoding from http) into the correct encoding.  For example, 
 sending the UTF-8 data with coding=2 does not re-encode the message into 
 USC-2, but just sends your UTF-8 bytes as if they were UCS-2 but sending 
 utf8 data with coding=0 does re-encode them into GSM.
 
 These things seem to me to be incorrect behavior, however given the wide use 
 of kannel I figured I should make sure I'm not missing something obvious 
 before I draft a patch to attempt to fix them.  Am I missing something?
 
 
 
 

Re: NACK reporting help

[Alexander Malysh]

Hi,

this is not easy to fix because you send only one but long message and awaiting 
only one DLR.
BUT kannel splits message into peaces for you and receive two DLRs. How would 
you put both reason
codes into one DLR? In you case that would be easy because they both equal but 
what do you do if not?

Thanks,
Alex

Am 06.03.2012 um 12:20 schrieb Ashish Agarwal:

 Hello All,
 
 Any update on the below query.
 
 On Wed, Feb 22, 2012 at 5:59 PM, Ashish Agarwal ashisha...@gmail.com wrote:
 Hello,
 
 I have been using kannel for over 2 years now and I am currently using the 
 latest 1.5 version of kannel. I have come across an issue with NACK reports 
 generated for messages that fails or are rejected by the smsc. 
 
 I have the following problem:-
 
 As per the PDU user receives the command_status: 1153 = 0x0481 from the 
 smsc but the kannel esme does not interpret it correctly. 
 
 e.g. 
 
 2012-02-22 17:24:31 FAILED Send SMS [SMSC:] [SVC:] [ACT:XXX] [BINF:] 
 [FID:] [META:] [from:XXX] [to:XXX] [flags:-1:0:-1:-1:19] 
 [msg:185:1..Create a basic account (Pictorial Representation)..Create a FREE 
 basic account on kareeredge.com and start searching and applying for jobs 
 through your personal dashboard right away.] [udh:0:]
 
 2012-02-22 17:24:31 Receive DLR [SMSC:XXX] [SVC:] [ACT:] [BINF:] [FID:] 
 [META:] [from:] [to:XXX] [flags:-1:-1:-1:-1:16] [msg:5:NACK/] [udh:0:]
 
 
 
 As you see NACK/ should contain NACK/0x0481. I have tried this with 
 multiple cases and have found out that when esme submits more than 160 
 characters of message and the message is rejected by the smppbox we do not 
 receive the NACK report correctly whereas when message text is less than 160 
 characters esme receive the report correctly as below:-
 
 
 2012-02-22 17:23:10 FAILED Send SMS [SMSC:] [SVC:] [ACT:XXX] [BINF:] 
 [FID:] [META:] [from:] [to:] [flags:-1:0:-1:-1:19] [msg:75:Dear This 
 is remind to u that,Please sms to 56767 to get more products Free] [udh:0:]
 2012-02-22 17:23:10 Receive DLR [SMSC:SIP11] [SVC:smssip1] [ACT:] [BINF:] 
 [FID:] [META:] [from:INFINI] [to:91990147] [flags:-1:-1:-1:-1:16] 
 [msg:73:NACK/0x0481/Vendor-specific error, please refer to your SMPP 
 provider] [udh:0:]
 
 Also %A value in dlr-url gives the same output as mentioned above, because of 
 which we are not able to trace the exact reason for the sms failure in case 
 of sms text more than 160 characters.
 
 For supporting also find the pdu dump of the message text of 185 characters:-
 
 2012-02-22 17:24:31 [6329] [15] DEBUG: boxc_receiver: sms received
 2012-02-22 17:24:31 [6329] [15] DEBUG: new split_parts created 0x2aaab4135f70
 2012-02-22 17:24:31 [6329] [15] DEBUG: send_msg: sending msg to boxc: sqlbox
 2012-02-22 17:24:31 [6329] [8] DEBUG: SMPP[]: throughput (0.00,0.00)
 2012-02-22 17:24:31 [6329] [8] DEBUG: SMPP[]: Sending PDU:
 2012-02-22 17:24:31 [6329] [8] DEBUG: SMPP PDU 0x2aaab413ee00 dump:
 2012-02-22 17:24:31 [6329] [8] DEBUG:   type_name: submit_sm
 2012-02-22 17:24:31 [6329] [8] DEBUG:   command_id: 4 = 0x0004
 2012-02-22 17:24:31 [6329] [8] DEBUG:   command_status: 0 = 0x
 2012-02-22 17:24:31 [6329] [8] DEBUG:   sequence_number: 192708 = 0x0002f0c4
 2012-02-22 17:24:31 [6329] [8] DEBUG:   service_type: NULL
 2012-02-22 17:24:31 [6329] [8] DEBUG:   source_addr_ton: 5 = 0x0005
 2012-02-22 17:24:31 [6329] [8] DEBUG:   source_addr_npi: 0 = 0x
 2012-02-22 17:24:31 [6329] [8] DEBUG:   source_addr: XXX
 2012-02-22 17:24:31 [6329] [8] DEBUG:   dest_addr_ton: 2 = 0x0002
 2012-02-22 17:24:31 [6329] [8] DEBUG:   dest_addr_npi: 1 = 0x0001
 2012-02-22 17:24:31 [6329] [8] DEBUG:   destination_addr: XX
 2012-02-22 17:24:31 [6329] [8] DEBUG:   esm_class: 67 = 0x0043
 2012-02-22 17:24:31 [6329] [8] DEBUG:   protocol_id: 0 = 0x
 2012-02-22 17:24:31 [6329] [8] DEBUG:   priority_flag: 0 = 0x
 2012-02-22 17:24:31 [6329] [8] DEBUG:   schedule_delivery_time: NULL
 2012-02-22 17:24:31 [6329] [8] DEBUG:   validity_period: NULL
 2012-02-22 17:24:31 [6329] [8] DEBUG:   registered_delivery: 1 = 0x0001
 2012-02-22 17:24:31 [6329] [8] DEBUG:   replace_if_present_flag: 0 = 
 0x
 2012-02-22 17:24:31 [6329] [8] DEBUG:   data_coding: 0 = 0x
 2012-02-22 17:24:31 [6329] [8] DEBUG:   sm_default_msg_id: 0 = 0x
 2012-02-22 17:24:31 [6329] [8] DEBUG:   sm_length: 159 = 0x009f
 2012-02-22 17:24:31 [6329] [8] DEBUG:   short_message:
 2012-02-22 17:24:31 [6329] [8] DEBUG:Octet string at 0x2aaab4172160:
 2012-02-22 17:24:31 [6329] [8] DEBUG:  len:  159
 2012-02-22 17:24:31 [6329] [8] DEBUG:  size: 1024
 2012-02-22 17:24:31 [6329] [8] DEBUG:  immutable: 0
 2012-02-22 17:24:31 [6329] [8] DEBUG:  data: 05 00 03 90 02 01 31 2e 3f 
 43 72 65 61 74 65 20   ..1.?Create
 2012-02-22 17:24:31 [6329] [8] DEBUG:  data: 61 20 62 61 73 69 63 20 61 
 63 63 6f 75 6e 74 20   a basic account
 2012-02-22 

Re: Sending Unicode Message over 70 characters

[Alexander Malysh]

for MT concatenation works since 1.3 (IIRC). For MO since 1.5

Alex

Am 20.11.2011 um 11:14 schrieb Milan P. Stanic:

 On Sun, 2011-11-20 at 13:31, afshin afzali wrote:
 I just added :
 
 max-messages = 3
 concatenation = true
 
 under sendsms-user group. FYI I use kannel 1.4.2 right now.
 
 I'm curious. Does SMS concatenation works with Kannel 1.4.2 for MO and
 MT?
 
 On Sat, Nov 19, 2011 at 11:42 PM, Milan P. Stanic m...@arvanta.net wrote:
 On Sat, 2011-11-19 at 22:00, afshin afzali wrote:
 Do you mean max-messages under SMS-Service group? It seems has been
 implemented in stable release !
 
 Search the word concatenated and concatenation in the userguide. It is
 explained there.
 
 On Sat, Nov 19, 2011 at 9:15 PM, Milan P. Stanic m...@arvanta.net
 wrote:
 On Sat, 2011-11-19 at 19:52, afshin afzali wrote:
 Ok, Is it possible to configure kannel to segment long message to
 multi-pages message?
 
 Of course. Read the userguide. It is descibred. And use at least 1.5.0
 version.
 
 On Sat, Nov 19, 2011 at 7:05 PM, Milan P. Stanic m...@arvanta.net
 wrote:
 On Sat, 2011-11-19 at 16:45, afshin afzali wrote:
 I'm using GSM Modem to send SMS. To send unicode messages I use
 charset=UTF-8 and coding=2. My problem is that I could not be
 able to
 send
 messages over 70 characters (unicode).
 Appreciate all comments !
 UTF-8 use two bytes (octets) for single character. 70*2=140 i.e.
 near
 maximum characters in one SMS.
 
 -- 
 Kind regards,  Milan
 --
 Arvanta, IT Securityhttp://www.arvanta.net
 Please do not send me e-mail containing HTML code or documents in
 proprietary format (word, excel, pps and so on)
 

Re: Capturing UDH

[Alexander Malysh]

Hi,

you will never get concat UDH (at least if always goes well) because of the 
option:
sms-combine-concatenated-mo = true

Alex

Am 20.11.2011 um 15:31 schrieb Issam Alameh:

 Hello 
 
 
 following is a configuration for sms-service, I am unable to get the udh for
 the long incoming sms message, searched everything every documentation and
 could not find the solution
 
 I am running kannel 1.4.3 
 
 always for %u i get empty string
 
 
 
 
 I hope someone could help here 
 
 group = core
 admin-port = 13000
 admin-password = **
 admin-deny-ip = *.*.*.*
 admin-allow-ip = 127.0.0.1
 smsbox-port = 13003
 log-file = /var/log/kannel/bearerbox.log
 box-deny-ip = *.*.*.*
 box-allow-ip = 127.0.0.1
 access-log=/var/log/kannel/access-core.log
 sms-combine-concatenated-mo = true
 
 group = smsbox
 bearerbox-host = 127.0.0.1
 sendsms-port = 13013
 #sendsms-chars = 
 log-file = /var/log/kannel/bearer
 log-level = 
 access-log = /var/log/kannel/bearer.access
 log-level = 
 mo-recode = 1
 
 group = sms-service
 keyword-regex=.*
 max-messages = 0
 #catch-all = yes
 accept-x-kannel-headers = true 
 get-url =
 http://localhost/t.php?BigI=:%A:%B:%C:%D:%E:%G:%H:%I:%J:%K:%L:%M:%N:%O:%P:%
 Q:%R:%S:%T:%U:%V:%W:%X:%Y:%Z:%a:%b:%c:%d:%e:%g:%h:%i:%j:%k:%l:%m:%n:%o:%p:%q
 :%r:%s:%t:%u:%v:%w:%x:%y:%z
 #post-url= http://localhost/t.php
 #get-url =
 http://localhost/sms/sms2email.php?from=%pmessage=%acode=%ccharset=%Cud
 h=%u
 concatenation = true
 file = /var/log/kannel/smsservice
 
 group = smsc
 smsc = smpp
 smsc-id = smpp-provider
 host =  api.provider
 port = 9911
 receive-port = 9911
 transceiver-mode = false
 throughput = 50
 smsc-username = **
 smsc-password = ***
 system-type = SMPP
 dest-addr-ton = 1
 dest-addr-npi = 1
 source-addr-ton = 5
 source-addr-npi = 0
 log-file = /var/log/kannel/smpp-kannel-provider.log
 log-level = 0
 msg-id-type = 0x01
 alt-charset = LATIN1
 enquire-link-interval = 30
 max-pending-submits=50

Re: Internal timestamp reached a maximum?

[Alexander Malysh]

Hi,

TS in Kannel is String and not a integer so that should be external issue 
because Kannel doesn't generate TS,
it's received from remote SMSC.

Alex

Am 18.11.2011 um 17:59 schrieb Garrett Ahern:

 Hello,
 
 I've noticed in our Kannel logs that the ts is set to 4294967295 (the highest 
 32 bit number possible) for every SMS. We use internal (memory) storage for 
 DLR's, so I think the TS above is internally generated, not taken from MySQL 
 or anything else. The consequence is that I have caught Kannel mismatching 
 the DLR's e.g. POST'ing a DLR for yesterday's SMS to a particular number, 
 instead of today's SMS to the same number, because TS+DEST is no longer 
 unique.
 
 So my question is has anyone else had this issue and how do you get Kannel to 
 start at number 1 again for the TS ?
 
 
 Thanks,
 Garrett

Re: wap 1.x and wtls

[Alexander Malysh]

Hi,

I don't know which informations you mean. Any details or better patch?

Alex

Am 06.07.2011 um 18:27 schrieb Nikos Balkanas:

 Hi,
 
 Look at the openssl site for certificate instructions. It is not kannel's 
 responsibility.
 
 Make sure that certificates are self-signed and without password. Comment out 
 privatekey-password from wtls configuration and retry.
 
 Alex:
 
 There was a section in UG about wtls configuration. It even included 
 certificate generation instructions. Apparently this was removed. Now, that 
 wtls is supported again, it should be put back.
 
 BR,
 Nikos
 - Original Message - From: Armindo Antunes 
 armindo.antu...@gmail.com
 To: users@kannel.org
 Sent: Wednesday, July 06, 2011 1:28 PM
 Subject: wap 1.x and wtls
 
 
 Hi!
 
 I'm trying to use the current development release 1.5.0 as a wap 1.x
 gateway on ubuntu linux.
 Unsecured connections are working fine but when enabling secure
 connections, the wapbox doesn't respond and it crashes on the handshake
 phase.
 
 I've tested with Openwave v7 Simulator, Nokia 7650 and Sony Ericsson
 T68i without success.
 Could it be the way I've generated the certificate?
 openssl req -new -newkey rsa:1024 -keyout server.key -out server.req
 openssl ca -policy policy_anything -notext -in server.req -out
 server.crt
 
 The OpenSSL version is 1.0.0d that I've compiled to include RC5 algorithm.
 Where can I find the proper instrutions to create the needed
 certificates for the WTLS connection?
 
 Please find in attach my kannel configuration (and certificates),
 wireshark capture and complete logs for the request.
 
 
 Any help would be appreciated.
 Thanks in Advance,
 Armindo Antunes
 
 
 
 Complete logs:
 sudo tail -f /var/log/kannel/*.log
 == /var/log/kannel/bearerbox.log ==
 2011-07-06 10:44:44 [925] [10] DEBUG: datagram received
 2011-07-06 10:44:44 [925] [12] DEBUG: Did not find previous routing info
 for WDP, generating new
 2011-07-06 10:44:44 [925] [20] DEBUG: send_msg: sending msg to box:
 127.0.0.1
 2011-07-06 10:44:44 [925] [20] DEBUG: boxc_sender: sent message to
 127.0.0.1
 2011-07-06 10:44:44 [925] [19] INFO: Connection closed by the box
 127.0.0.1
 2011-07-06 10:44:44 [925] [20] DEBUG: send_msg: sending msg to box:
 127.0.0.1
 2011-07-06 10:44:44 [925] [20] DEBUG: Thread 20
 (gw/bb_boxc.c:boxc_sender) terminates.
 2011-07-06 10:44:44 [925] [19] DEBUG: Thread 19 (gw/bb_boxc.c:function)
 terminates.
 2011-07-06 10:44:44 [925] [13] INFO: Client connected from 127.0.0.1
 2011-07-06 10:44:44 [925] [13] DEBUG: Started thread 21
 (gw/bb_boxc.c:function)
 2011-07-06 10:44:44 [925] [21] DEBUG: Thread 21 (gw/bb_boxc.c:function)
 maps to pid 925.
 2011-07-06 10:44:44 [925] [21] DEBUG: setting up systems for new wapbox
 2011-07-06 10:44:44 [925] [21] DEBUG: Started thread 22
 (gw/bb_boxc.c:boxc_sender)
 2011-07-06 10:44:44 [925] [22] DEBUG: Thread 22
 (gw/bb_boxc.c:boxc_sender) maps to pid 925.
 
 == /var/log/kannel/wapbox.log ==
 2011-07-06 10:44:44 [2318] [0] DEBUG: Msg object at 0x8685038:
 2011-07-06 10:44:44 [2318] [0] DEBUG:  type: wdp_datagram
 2011-07-06 10:44:44 [2318] [0] DEBUG:  wdp_datagram.source_address:
 2011-07-06 10:44:44 [2318] [0] DEBUG:  Octet string at 0x8683af0:
 2011-07-06 10:44:44 [2318] [0] DEBUG:len:  12
 2011-07-06 10:44:44 [2318] [0] DEBUG:size: 13
 2011-07-06 10:44:44 [2318] [0] DEBUG:immutable: 0
 2011-07-06 10:44:44 [2318] [0] DEBUG:data: 31 37 32 2e 31 38 2e 30
 2e 32 33 33   172.18.0.233
 2011-07-06 10:44:44 [2318] [0] DEBUG:  Octet string dump ends.
 2011-07-06 10:44:44 [2318] [0] DEBUG:  wdp_datagram.source_port: 8502
 2011-07-06 10:44:44 [2318] [0] DEBUG:  wdp_datagram.destination_address:
 2011-07-06 10:44:44 [2318] [0] DEBUG:  Octet string at 0x8683b98:
 2011-07-06 10:44:44 [2318] [0] DEBUG:len:  7
 2011-07-06 10:44:44 [2318] [0] DEBUG:size: 8
 2011-07-06 10:44:44 [2318] [0] DEBUG:immutable: 0
 2011-07-06 10:44:44 [2318] [0] DEBUG:data: 30 2e 30 2e 30 2e 30
  0.0.0.0
 2011-07-06 10:44:44 [2318] [0] DEBUG:  Octet string dump ends.
 2011-07-06 10:44:44 [2318] [0] DEBUG:  wdp_datagram.destination_port: 9203
 2011-07-06 10:44:44 [2318] [0] DEBUG:  wdp_datagram.user_data:
 2011-07-06 10:44:44 [2318] [0] DEBUG:  Octet string at 0x8683c30:
 2011-07-06 10:44:44 [2318] [0] DEBUG:len:  229
 2011-07-06 10:44:44 [2318] [0] DEBUG:size: 230
 2011-07-06 10:44:44 [2318] [0] DEBUG:immutable: 0
 2011-07-06 10:44:44 [2318] [0] DEBUG:data: c3 00 00 00 e0 01 00 dd
 01 00 05 f8 ee 51 c2 7f   .Q..
 2011-07-06 10:44:44 [2318] [0] DEBUG:data: 27 4c c7 f2 5a 77 f0 1d
 f1 00 00 20 08 00 02 04   'L..Zw. 
 2011-07-06 10:44:44 [2318] [0] DEBUG:data: 00 00 00 00 05 00 02 04
 00 00 00 00 07 00 02 04   
 2011-07-06 10:44:44 [2318] [0] DEBUG:data: 00 00 00 00 06 00 02 04
 00 00 00 00 00 8a 08 00   
 2011-07-06 10:44:44 [2318] [0] DEBUG:data: fe 7d fb 7f c3 4f 6e b9
 6b 

Re: Kannel Issue

[Alexander Malysh]

Hi Sudhakar,

please ask users mailing list (CCed). There are many users that can help you.

Thanks,
Alexander Malysh

Am 31.03.2011 um 17:41 schrieb Sudhakar G:

 Hi Alex,
 I was setting up a kannel sms gateway  have got struck with a issue, was 
 referring net for the solution  found your responses for many issues related 
 to Kannel. So thought of contacting you for help.
 
 I am here with attaching my configuration  the smpp logs. I am getting 
 ERROR: SMPP[smpp]: got DLR but could not find message or was not interested 
 in it id3790456584 dst45524, type2 
 while I am pushing a test message from kannel internal URL 
 http://localhost:13002/cgi-bin/sendsms?username=kannelpassword=rL4yto=9739978823text=TestFromKannel2
  
 
 I tried various combination of configurations to get rid of error but no 
 success.
 
 Let me know where am I doing the mistake in configuration.
 
 Thanks,
 Sudhakar
 
 
 kannel.conf.txtsmpp.log

Re: question about ota-setting

[Alexander Malysh]

Please ask such questions on users ML and don't write to devel-owners...

Thanks,
Alexander Malysh

Am 24.03.2011 um 23:02 schrieb Sijia Zhu:

 Hi,
 
 I have a problem about ota-setting, I tried to send the configuration to my 
 cell phone, I have two kinds of cell phones, Nokia N95 and Nokia E75, both 
 cell phones said can not open, message format not supported, but when I 
 tried to send ota-bookmark, I can receive the message and can open the 
 message. Could you please help me solve this problem?
 
 Below is my kannel configuration:
 
 group = core
 admin-port = 13000
 wapbox-port = 13002
 smsbox-port = 13001
 admin-password = bar
 #status-password = foo
 #admin-deny-ip = 
 #admin-allow-ip = 
 wdp-interface-name = *
 log-file = /tmp/bearerbox.log
 log-level = 0
 box-deny-ip = *.*.*.*
 box-allow-ip = 127.0.0.1
 #access-log = /tmp/access.log
 #store-file = /tmp/kannel.store
 #ssl-server-cert-file = cert.pem
 #ssl-server-key-file = key.pem
 #ssl-certkey-file = mycertandprivkeyfile.pem
 #http-proxy-host = 127.0.0.1
 #http-proxy-port = 8191
 
 group = wap-url-map
 name = map_mmsc
 url = /*
 map-url = http://localhost:8191/*;
 accept-cookies = yes
 
 group = wapbox 
 bearerbox-host = localhost
 log-file = /tmp/wapbox.log
 log-level = 0 #RADIUS Accounting Proxy setup for WAPBOX
 
 group = radius-acct
 our-port = 1813
 secret-nas = s3kr1tP45S
 nas-ports = 64
 
 #SMSC SMPP
 group = smsc
 smsc = smpp
 smsc-id = ginod
 host = 10.0.0.80
 port = 8002
 #receive-port = 7234
 smsc-username = ginod
 smsc-password =
 system-type = WAP
 service-type = WAP
 interface-version =
 address-range =
 
 #SMSBOX SETUP
 group = smsbox
 bearerbox-host = localhost
 global-sender = 13013
 sendsms-port = 13013
 sendsms-url = /cgi-bin/sendsms
 sendota-url = /cgi-bin/sendota
 sendsms-chars = 0123456789 +-
 #global-sender = 12345
 log-file = /tmp/smsbox.loggroup = sms-service
 keyword = www
 post-url = http://%S;
 
 group = ota-setting
 ota-id = wap-link
 location = http://www.yahoo.com
 service = Our company's WAP site
 ipaddress = 10.0.2.1
 phonenumber = 3129698311
 bearer = data
 speed = 9600
 calltype = isdn
 connection = cont
 pppsecurity = off
 authentication = normal
 login = wapuser 
 secret = thepasswd
 
 group = ota-bookmark
 ota-id = wap-config
 url = http://www.yahoo.com
 
 group = sendsms-user
 username = tester
 password = foobar
 user-allow-ip = 10.0.2.1
 max-messages = 5
 concatenation = true
 
 log-level = 0
 
 syslog-level = none
 access-log = /tmp/wapaccess.log
 
 
 
 
 
 BR
 SJ

Re: Kannel 1.5.0 Debian packages

[Alexander Malysh]

Hi All,

just uploaded debs for 1.5.0 to https://redmine.kannel.org/projects/kannel/files
please check and give me/Milan feedback.

Thanks,
Alexander Malysh

Am 22.03.2011 um 16:24 schrieb Milan P. Stanic:

 Hi Alex,
 
 On Tue, 2011-03-22 at 14:37, Alexander Malysh wrote:
 Hi Milan,
 
 as far as I see, configuration should be fine. Could you please upload debs 
 and diff tar to some place
 and we will push it to download section then.
 
 I will upload it later and send the URL to you in private mail.
 
 Thanks,
 Alexander Malysh
 
 Am 22.03.2011 um 14:09 schrieb Milan P. Stanic:
 
 Hi Alex,
 
 On Tue, 2011-03-22 at 09:56, Alexander Malysh wrote:
 Hi Milan,
 
 that would be great to have debian packages for 1.5.0
 
 I forgot to mention in original post that I sent these packages to
 someone in Romania who is tried it on Ubuntu. He told me that the same
 binary packages which I run on Debian also works well on Ubuntu but I
 forget which release he runs.
 
 could you please answer some questions:
 - how these packages compiled
 
 I patched 1.5.0 source with official Debian diff (actually tar file)
 because my intention is that the packages I build shouldn't differ a lot
 from Debian shipped packages. It is because of that if someone upgrade
 it from official Debian release to newly built packages s/he doesn't
 have to change anything in configuration files.
 
 - which DB support is enabled
 
 Sqlite3, Postgresql and MySQL.
 
 - compiler/configure flags used
 
 Here is the relevant section from debian/rules files:
 ./configure \
   --host=$(DEB_HOST_GNU_TYPE) \
   --build=$(DEB_BUILD_GNU_TYPE) \
   --enable-warnings \
   --prefix=/usr \
   --mandir=\$${prefix}/share/man \
   --infodir=\$${prefix}/share/info \
   --enable-docs --enable-pam --enable-pcre \
   --enable-ssl --with-ssl=/usr \
   --with-mysql --with-mysql-dir=/usr \
   --with-sqlite3 \
   --with-pgsql --with-pgsql-dir=/usr
 
 
 And here is relevant section from Makefile:
 
 
 LIBS=-lpq -lmysqlclient_r -lssl -ldl -lpam -lpcreposix -lrt -lresolv
 -lnsl -lm  -lpthread -lxml2 -L/usr/lib -lpcreposix -lpcre -L/usr/lib
 -lcrypto -lssl -rdynamic -L/usr/lib/mysql -lmysqlclient_r
 -L/usr/local/lib -lsqlite3 -L/usr/lib
 
 CFLAGS=-D_REENTRANT=1 -I. -Igw -g -O2 -D_XOPEN_SOURCE=600 -D_BSD_SOURCE
 -D_LARGE_FILES= -I/usr/include/libxml2  -Wall -Wmissing-prototypes
 -Wmissing-declarations -Wnested-externs -Winline -Wformat
 -Wformat-security -Wmissing-format-attribute -I/usr/include
 -I/usr/include/mysql -I/usr/include/postgresql
 
 LDFLAGS= -rdynamic
 
 Do you have some place to upload packages and we will push those then to 
 download section?
 
 Yes, I can upload it but would like to know first if the configuration
 above is correct. If not, I can rebuild it with your (or someone else)
 suggestions.
 
 Thanks,
 Alexander Malysh
 
 Am 21.03.2011 um 23:46 schrieb Milan P. Stanic:
 
 Hi all,
 
 I have noticed on users@kannel.org list that some user have a problem
 how to build Kannel on Debian/Ubuntu systems.
 
 On the Kannel site in download section Debian packages are outdated
 (1.4.1 version for Debian sarge). Current Debian stable release is
 shipped with with Kannel 1.4.3 version which is old as we all know.
 
 I have built Kannel 1.5.0 (development release) for Debian squeeze
 (current stable) and for i386 and amd64 architectures. It works without
 problem for more than three or four months.
 
 IMHO it would be useful for users to update Kannel download section
 and put new Debian packages there. I'm ready to upload them but I don't
 know where or whom to send these packages.
 
 P.S.
 I'm not sure who is the site admin so I write to list.
 
 -- 
 Kind regards,  Milan
 --
 Arvanta, IT Securityhttp://www.arvanta.net
 Please do not send me e-mail containing HTML code.
 
 
 
 -- 
 Kind regards,  Milan
 --
 Arvanta, IT Securityhttp://www.arvanta.net
 Please do not send me e-mail containing HTML code.
 
 
 
 -- 
 Kind regards,  Milan
 --
 Arvanta, IT Securityhttp://www.arvanta.net
 Please do not send me e-mail containing HTML code.
 

Re: [bug] clickatell unicode HTTP code for Kannel

[Alexander Malysh]

Hi,

in order to send message as UCS2 you can try this:

http://localhost:13013/cgi-bin/sendsms?username=password=to=24492
347from=Companytext=Mr.+Joo+Seu+seguro+automvel+MM3A308720+caduca+hoje.+Contacte-nos+227280210%2F220+ou+visite-nos+numa+de+nossas+agncias+para+activar+a+nova+aplice.
coding=2charset=UTF-8smsc=clickatell

Thanks,
Alexander Malysh

Am 18.03.2011 um 17:13 schrieb Hillel:

 Hi,
 
 Our message is: 
 Mr. João Seu seguro automóvel MM3A308720 caduca hoje. Contacte-nos
 227280210/220 ou visite-nos numa de nossas agências para activar a nova
 apólice.  (147 characters)
 
 Our goal is to send it as concatenated Unicode and use UTF-8 as that is what
 Clickatell accepts.
 Questions - do we use padding?
 The only case of (Sent. Message splits: 3) is from Sending to Kannel not
 using padding, leave out charset below.  But it arrives *some text missing*
 2061206E6F7661206170C3B36C963652E and not a Unicode message.  
 Is there a bug in Kannel code for Clickatell or are we doing something
 incorrect?
 
 Result is: 
 4D722E204A6FC3A36F205365752073656775726F206175746F6DC3B376656C204D4D33413330
 383732302063616475636120686F6A652E20436F6E74616374652D6E6F732032323732383032
 31302F323230206F75207669736974652D6E6F73206E756D61206465206E6F73736173206167
 C3AA6E63696173207061726120616374697661722061206E6F7661206170C3B36C6963652E
 
 If we use padding:
 
 004d0072002e0020004a006f00e3006f0020005300650075002000730065006700750072006f
 0020006100750074006f006d00f300760065006c0020004d004d003300410033003000380037
 00320030002000630061006400750063006100200068006f006a0065002e00200043006f006e
 00740061006300740065002d006e006f00730020003200320037003200380030003200310030
 002f0032003200300020006f00750020007600690073006900740065002d006e006f00730020
 006e0075006d00610020006400650020006e006f007300730061007300200061006700ea006e
 0063006900610073002000700061007200610020006100630074006900760061007200200061
 0020006e006f0076006100200061007000f3006c006900630065002e
 
 Sending to Kannel not using padding, leave out charset:
 
 [root@messaging ~]# lynx -dump
 'http://localhost:13013/cgi-bin/sendsms?username=password=to=24492
 347from=Companytext=4D722E204A6FC3A36F205365752073656775726F206175746F
 6DC3B376656C204D4D33413330383732302063616475636120686F6A652E20436F6E74616374
 652D6E6F73203232373238303231302F323230206F75207669736974652D6E6F73206E756D61
 206465206E6F73736173206167C3AA6E63696173207061726120616374697661722061206E6F
 7661206170C3B36C6963652Ecoding=2smsc=clickatell'
 
   Sent. Message splits: 3
 
 Sending to Kannel not using padding, put in charset:
 
 [root@messaging ~]# lynx -dump
 'http://localhost:13013/cgi-bin/sendsms?username=password=to=24492
 347from=Companytext=4D722E204A6FC3A36F205365752073656775726F206175746F
 6DC3B376656C204D4D33413330383732302063616475636120686F6A652E20436F6E74616374
 652D6E6F73203232373238303231302F323230206F75207669736974652D6E6F73206E756D61
 206465206E6F73736173206167C3AA6E63696173207061726120616374697661722061206E6F
 7661206170C3B36C6963652Echarset=utf-8coding=2smsc=clickatell'
 
   Sent. Message splits: 5
 
 Sending to Kannel using padding, leave out charset:
 
 [root@messaging ~]# lynx -dump
 'http://localhost:13013/cgi-bin/sendsms?username=password=to=24492
 347from=Companytext=004d0072002e0020004a006f00e3006f002000530065007500
 2000730065006700750072006f0020006100750074006f006d00f300760065006c0020004d00
 4d00330041003300300038003700320030002000630061006400750063006100200068006f00
 6a0065002e00200043006f006e00740061006300740065002d006e006f007300200032003200
 37003200380030003200310030002f0032003200300020006f00750020007600690073006900
 740065002d006e006f00730020006e0075006d00610020006400650020006e006f0073007300
 61007300200061006700ea006e00630069006100730020007000610072006100200061006300
 740069007600610072002000610020006e006f0076006100200061007000f3006c0069006300
 65002ecoding=2smsc=clickatell'
 
   Sent. Message splits: 5
 
 Sending to Kannel using padding, include charset:
 
 [root@messaging ~]# lynx -dump
 'http://localhost:13013/cgi-bin/sendsms?username=password=to=24492
 347from=Companytext=004d0072002e0020004a006f00e3006f002000530065007500
 2000730065006700750072006f0020006100750074006f006d00f300760065006c0020004d00
 4d00330041003300300038003700320030002000630061006400750063006100200068006f00
 6a0065002e00200043006f006e00740061006300740065002d006e006f007300200032003200
 37003200380030003200310030002f0032003200300020006f00750020007600690073006900
 740065002d006e006f00730020006e0075006d00610020006400650020006e006f0073007300
 61007300200061006700ea006e00630069006100730020007000610072006100200061006300
 740069007600610072002000610020006e006f0076006100200061007000f3006c0069006300
 65002echarset=utf-8coding=2smsc=clickatell'
 
   Sent. Message splits: 9
 
 
 -Original Message-
 From: Alexander Malysh [mailto:malys...@googlemail.com] On Behalf Of
 Alexander Malysh
 Sent: 28 January 2011 11:01 AM
 To: Hillel
 Cc: de

Re: Crash of the smsbox

[Alexander Malysh]

Hi,

could you please try 1.5.0 or better SVN version? 1.4.3 is a little bit 
outdated...

Thanks,
Alexander Malysh

Am 07.03.2011 um 09:24 schrieb Beatrice Tamburrino:

 Hi guys!
 I have a working kannel (1.4.3) with an emi interface to a provider - now, 
 last week there were a big crash on kannel side. I analyzed the log files and 
 saw this:
 
 2011-02-09 20:55:16 [2553] [8] DEBUG: Octet string dump ends.
 2011-02-09 20:55:16 [2553] [8] ERROR: Error writing 246 octets to fd 31:
 2011-02-09 20:55:16 [2553] [8] ERROR: System error 104: Connection reset by 
 peer
 2011-02-09 20:55:16 [2553] [8] ERROR: Error writing 246 octets to fd 31:
 2011-02-09 20:55:16 [2553] [8] ERROR: System error 32: Broken pipe
 2011-02-09 20:55:16 [2553] [8] ERROR: Couldn't send request to 
 http://10.9.X.XX:Y/dlr?rsp=4D52D4DC-146-079XXX,1297281316,1,Message+for+079XXX%2C+with+identification+110209185558+has+been+delivered+on+2011-02-09+at+18%3A55%3A58.
 2011-02-09 20:55:16 [2553] [8] DEBUG: Failed while sending request
 2011-02-09 20:55:16 [2553] [8] PANIC: gwlib/conn.c:852: conn_unregister: 
 Assertion `conn != NULL' failed.
 2011-02-09 20:55:16 [2553] [8] PANIC: /usr/sbin/smsbox(gw_panic+0xcd) 
 [0x808a33d]
 2011-02-09 20:55:16 [2553] [8] PANIC: /usr/sbin/smsbox(conn_unregister+0x174) 
 [0x807c8b4]
 2011-02-09 20:55:16 [2553] [8] PANIC: /usr/sbin/smsbox() [0x8085ef7]
 2011-02-09 20:55:16 [2553] [8] PANIC: /usr/sbin/smsbox() [0x807f565]
 2011-02-09 20:55:16 [2553] [8] PANIC: /usr/sbin/smsbox() [0x808167d]
 2011-02-09 20:55:16 [2553] [8] PANIC: 
 /lib/tls/i686/cmov/libpthread.so.0(+0x596e) [0x8c896e]
 2011-02-09 20:55:16 [2553] [8] PANIC: 
 /lib/tls/i686/cmov/libc.so.6(clone+0x5e) [0x9a9a0e]
 2011-02-09 20:56:12 [2565] [0] INFO: Added logfile 
 `/var/log/kannel/nvkannel_smsbox.log' with level `0'.
 2011-02-09 20:56:12 [2565] [0] INFO: Service global sender set as 'TEST'
 2011-02-09 20:56:12 [2565] [0] INFO: Logging accesses to 
 '/var/log/kannel/nvkannel_access.log'.
 2011-02-09 20:56:12 [2565] [0] INFO: Started access logfile 
 `/var/log/kannel/nvkannel_access.log'.
 2011-02-09 20:56:12 [2565] [0] INFO: HTTP: Opening server at port 13003.
 2011-02-09 20:56:12 [2565] [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller)
 2011-02-09 20:56:12 [2565] [0] DEBUG: Started thread 2 
 (gwlib/http.c:server_thread)
 2011-02-09 20:56:12 [2565] [0] INFO: Set up send sms service at port 13003
 2011-02-09 20:56:12 [2565] [0] DEBUG: Started thread 3 
 (gw/smsbox.c:sendsms_thread)
 2011-02-09 20:56:12 [2565] [0] DEBUG: 
 --
 .
 
 It seems that something brought the smsbox to crash - I don't know why - I 
 hope somebody of you can help me out. How can it be fixed? Is this bug 
 allready known.
 
 I would appreciate any help from you
 
 thanks in advance
 
 cheers
 
 beatrice
 
 -- 
 GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit 
 gratis Handy-Flat! http://portal.gmx.net/de/go/dsl
 

kannel.org planned downtime 28.02.2011 13:00-18:00 CET

[Alexander Malysh]

Thanks for understanding!

Alexander Malysh

[Resolved] Re: kannel.org planned downtime 28.02.2011 13:00-18:00 CET

[Alexander Malysh]

kannel.org up and running again.

Am 28.02.2011 um 12:01 schrieb Alexander Malysh:

 Thanks for understanding!
 
 Alexander Malysh

Re: Patch: wtls provision

[Alexander Malysh]

Hi Nikos,

sorry for delay, patch commited to branch and after testing will be merged to 
trunk.

This branch can be found at: 
https://svn.kannel.org/gateway/branches/wtls_provision

I would like to see more people that can test/review this patch.

Thanks,
Alexander Malysh

Am 26.04.2010 um 01:34 schrieb Nikos Balkanas:

 Hi Alex,
 
 As stressed I never implied any wrongdoing from your part. If anything you 
 are the only person dedicated to this project like a regular job. Rest of us 
 are mostly daydreaming small snippets in our free time. There can be no 
 kannel without you.
 
 The Patch is back. Reformatted according to your specs. Let me know if you 
 need anything more.
 
 Like in the original, it will provide for the following wtls functionality:
 
 A) Supported MACs:
 
   SHA_0,
   SHA_40,
   SHA_80,
   SHA_NOLIMIT,
   MD5_40,
   MD5_80,
   MD5_NOLIMIT
 
 MIA's:
SHA_XOR_40
 
 B) Supported Ciphers:
 
   RC5_CBC_40,
   RC5_CBC_56,
   RC5_CBC,
   DES_CBC,
   DES_CBC_40
 
 MIA's:
   NULL_bulk,
   TRIPLE_DES_CBC_EDE,
   IDEA_CBC_40,
   IDEA_CBC_56,
   IDEA_CBC
 
 C) Supported Keys:
 
   RSA_anon
 
 MIA's:
   RSA_anon_512,
   RSA_anon_768,
   RSA_NOLIMIT,
   RSA_512,
   RSA_768,
   ECDH_anon,
   ECDH_anon_113,
   ECDH_anon_131,
   ECDH_ECDSA_NOLIMIT
 
 Keys might seem a shortcoming, but I have yet to see a mobile that doesn't 
 support RSA_anon. I do expect that a few of the rest of the keys are 
 supported as well (i.e. RSA_anon_512, RSA_anon_768) just didn't have the 
 chance to test them.
 
 D) Spec States
 
 All wtls states are supported except:
 
   1) Suspend/resume wtls session
   2) Cipher change when already connected
 
 I have not come across these states when testing with a variety of mobiles. 
 In practice (2) is implemented through another client hello while already 
 connected to the same client.
 
 BR,
 Nikos
 - Original Message - From: Alexander Malysh
 To: Nikos Balkanas
 Cc: de...@kannel.org
 Sent: Tuesday, April 13, 2010 12:49 AM
 Subject: Re: Patch: wtls provision
 
 
 Hi Nikos,
 
 
 sorry for delay but I hope you saw that WAP is not my part...
 if you still want to contribute this patch then I'm willing to help you with 
 it.
 
 
 What I need from you:
 1) patch with white spaces ignore
 2) description how I can test your patch
 
 
 You can send me these things in private email but please understand that we 
 are all volunteers and don't
 receive salary for our work and make this only in our private time. So for 
 such large patches it may take
 some time to review, test and commit it.
 
 
 Thanks for your understanding and contribution,
 Alexander Malysh 
 kannel.diff.gz

Re: rewrite test

[Alexander Malysh]

Hi Nikos,

we didn't changed mailserver configuration for ages... So it it should be 
something temporarily.

Thanks,
Alexander Malysh

P.S. Let me know if it happens again, I will then look into config.

Am 16.04.2010 um 02:10 schrieb Nikos Balkanas:

 Hi Alex,
 
 Something funny is happenning with the mail. Arno sends his mail cc: 
 users@kannel.org, and I receive it as cc: us...@vm1.kannel.org. When I 
 accidentally replied to his email cc: us...@vm1.kannel.org, my email bounced 
 back with unknown user. When he tried it, it went through fine.
 
 Is everything OK with kannel's mailserver? (of course it could be any 
 intermediate mailserver for that matter).
 
 BR,
 Nikos
 - Original Message - From: arno a...@daika08.ch
 To: us...@vm1.kannel.org
 Sent: Thursday, April 15, 2010 9:35 PM
 Subject: rewrite test
 
 
 has to bounce
 

Re: ***HAPPY NEW YEAR! *** from the Kannel Group!

[Alexander Malysh]

happy new year!!!

Am 31.12.2009 um 15:25 schrieb Stipe Tolj:

 Dear developers,
 Dear users,
 
 in the name of the whole Kannel Group, and to all the great individual
 supporters and contributor that have shown tremendous participation and
 encouragement in this year - making and keeping Kannel the most used SMS 
 gateway
 software in the world! - we wish you:
 
  *** Happy New Year! ***
 
 Enjoy your New Year's Eve and make yourself a great time, either with family,
 friends or both. :)
 
 Stipe
 
 -- 
 ---
 Kölner Landstrasse 419
 40589 Düsseldorf, NRW, Germany
 
 tolj.org system architecture  Kannel Software Foundation (KSF)
 http://www.tolj.org/  http://www.kannel.org/
 
 mailto:st_{at}_tolj.org   mailto:stolj_{at}_kannel.org
 ---
 

Re: Kannel timeouts / connectivity issues

[Alexander Malysh]

Hi Nikos,

the issue is that when you set timeout in configuration it's valid for _all_ 
http client connections.

If you think it this config option would be useful, please provide patch for 
this because I'm too busy now :)
I would suggest to set it in group = core for bearerbox and group = smsbox for 
smsbox.

Thanks,
Alexander Malysh

Am 03.12.2009 um 05:22 schrieb Nikos Balkanas:

 Hi,
  
 According to Changelog, Alexander M. on 6/8/2006 added a function in 
 gwlib/http.c:
  
 void http_set_client_timeout(long timeout)
  
 which sets the timeout for the http outgoing connections. Unfortunately it is 
 ghost and not used anywhere in the code or configuration. As a result the 
 http_client_timeout is hardwired into the code:
  
 static int http_client_timeout = 240;
  
 It's a rather trivial matter to add it in the configuration, but I think that 
 Alex, the original contributor, should do it. If he cannot I could.
  
 What do you say Alex?
  
 Of course 15' timeout seems an overexaggeration. The OS kernel should drop 
 the connection before that.
  
 BR,
 Nikos
 - Original Message -
 From: David Ritchie
 To: users@kannel.org
 Sent: Thursday, December 03, 2009 12:06 AM
 Subject: Kannel timeouts / connectivity issues
 
 Anybody know what Kannel’s expected behavior when HTTP connections timeout or 
 fail?
  
 We have a situation with 120+ “sms-service” services defined, but have 
 noticed a few of them behave in a peculiar manner where, very occasionally, 
 HTTP requests don’t occur until 16 minutes after being received by Kannel. 
 This will happen “out of the blue” without any errors logged in smsbox.log or 
 kannel.log. This occurs in a transient fashion – there doesn’t appear to be 
 any rhyme or reason to when this occurs.
  
 This only appears to happen with a particular subset of SMS services which 
 happen to be hosted outside of our immediate hosting environment, suggesting 
 there’s some sort of network disruption causing this problem. Potentially 
 this is some of retry based on a 1-minute timeout, followed by a retry 15 
 minutes later; however this would be “out of character” since in my 
 experience with Kannel most timeouts / 404s / 500s usually generate 
 everyone’s favourite “Couldn’t fetch content, sorry”-type messages. I also 
 can’t find any reference to timeouts of these values in the user’s guide or 
 the configuration files.
  
 Until recently the get-urls for these services had the SMSC included in the 
 URLs (i.e. “smsc=%i”) but, as these were the only services using this, I’ve 
 removed this in case there’s some sort of problem caused by this.
  
 Has anybody else had a similar situation where these sorts of delays have 
 happened?
  
 David
  
  

Re: Kannel timeouts / connectivity issues

[Alexander Malysh]

I don't know what you mean by configurable globally? each box has it's own 
global config...

Thanks,
Alexander Malysh

Am 03.12.2009 um 12:47 schrieb Nikos Balkanas:

 You are absolutely right. In fact it is easier than i thought. I will get 
 right to it. And let's make default timeout to something easier on the eye, 
 ie 60.
  
 BR,
 Nikos 
 - Original Message -
 From: Alejandro Guerrieri
 To: Nikos Balkanas
 Cc: Alexander Malysh ; users@kannel.org
 Sent: Thursday, December 03, 2009 1:24 PM
 Subject: Re: Kannel timeouts / connectivity issues
 
 http smsc's works from bearerbox I think
 
 2009/12/3 Nikos Balkanas n...@amdtelecom.net
 Hi Alex,
  
 Right now all client connections have a set limit of 240 hardwired in code. 
 It is easy to make this configurable globally, and I think it would be an 
 improvement over the hardcoded one.
  
 Now, from your sayings, this should be done /box (let's not forget wapbox) 
 and this is more of a hussle. Smsbox  wapbox can use the same setting, and i 
 don't know of any bb http client connections. Do you?
  
 Besides I don't have time right now for /box timeout support. But the global 
 one is trivial to do and can do it. Is this OK?
  
 I don't need it, but it seems that David does.
  
 BR,
 Nikos
 - Original Message -
 From: Alexander Malysh
 To: Nikos Balkanas
 Cc: users@kannel.org
 Sent: Thursday, December 03, 2009 11:35 AM
 Subject: Re: Kannel timeouts / connectivity issues
 
 Hi Nikos,
 
 the issue is that when you set timeout in configuration it's valid for _all_ 
 http client connections.
 
 If you think it this config option would be useful, please provide patch for 
 this because I'm too busy now :)
 I would suggest to set it in group = core for bearerbox and group = smsbox 
 for smsbox.
 
 Thanks,
 Alexander Malysh
 
 Am 03.12.2009 um 05:22 schrieb Nikos Balkanas:
 
 Hi,
  
 According to Changelog, Alexander M. on 6/8/2006 added a function in 
 gwlib/http.c:
  
 void http_set_client_timeout(long timeout)
  
 which sets the timeout for the http outgoing connections. Unfortunately it 
 is ghost and not used anywhere in the code or configuration. As a result the 
 http_client_timeout is hardwired into the code:
  
 static int http_client_timeout = 240;
  
 It's a rather trivial matter to add it in the configuration, but I think 
 that Alex, the original contributor, should do it. If he cannot I could.
  
 What do you say Alex?
  
 Of course 15' timeout seems an overexaggeration. The OS kernel should drop 
 the connection before that.
  
 BR,
 Nikos
 - Original Message -
 From: David Ritchie
 To: users@kannel.org
 Sent: Thursday, December 03, 2009 12:06 AM
 Subject: Kannel timeouts / connectivity issues
 
 Anybody know what Kannel’s expected behavior when HTTP connections timeout 
 or fail?
 We have a situation with 120+ “sms-service” services defined, but have 
 noticed a few of them behave in a peculiar manner where, very occasionally, 
 HTTP requests don’t occur until 16 minutes after being received by Kannel. 
 This will happen “out of the blue” without any errors logged in smsbox.log 
 or kannel.log. This occurs in a transient fashion – there doesn’t appear to 
 be any rhyme or reason to when this occurs.
 This only appears to happen with a particular subset of SMS services which 
 happen to be hosted outside of our immediate hosting environment, suggesting 
 there’s some sort of network disruption causing this problem. Potentially 
 this is some of retry based on a 1-minute timeout, followed by a retry 15 
 minutes later; however this would be “out of character” since in my 
 experience with Kannel most timeouts / 404s / 500s usually generate 
 everyone’s favourite “Couldn’t fetch content, sorry”-type messages. I also 
 can’t find any reference to timeouts of these values in the user’s guide or 
 the configuration files.
 Until recently the get-urls for these services had the SMSC included in the 
 URLs (i.e. “smsc=%i”) but, as these were the only services using this, I’ve 
 removed this in case there’s some sort of problem caused by this.
 Has anybody else had a similar situation where these sorts of delays have 
 happened?
 David
 
 
 

Re: [ANN] Kannel.org downtime Tuesday 27.10.2009

[Alexander Malysh]

oops, wrong date 27.10.2009 instead of 23.10.2009

Alexander Malysh schrieb:

Hello all,

please be aware that kannel.org machine will be down on Tuesday 
27.10.2009 from 10:00 CEST till appr. 21:00 CEST due to the move

to new data centre.

Thanks for understanding,
Alexander Malysh

Re: wappush mBlox

[Alexander Malysh]

don't know how important this is for users? we don't use wapbox at all  
because it's easier to create wappush message in application

and send it via sendsms interface.

Thanks,
Alex

Am 15.07.2009 um 16:48 schrieb Nikos Balkanas:

Well, it is not high in my priorities, I have to contribute more  
important stuff first, but is it something that would be of interest  
to wap, or given its current status it's not worth it?


BR,
Nikos
- Original Message -
From: Alexander Malysh
To: Nikos Balkanas
Cc: Alejandro Guerrieri ; users@kannel.org ; Ishtiaq Ahmed
Sent: Wednesday, July 15, 2009 5:26 PM
Subject: Re: wappush mBlox

Hi Nikos,

meta-data is not supported on /wappush interface because it's  
handled in wapbox.
meta-data is supported only in smsbox. But it should be really easy  
task to add meta-data to wapbox (only read port/get vars and store  
it in msg).


Thanks,
Alex

Am 15.07.2009 um 15:50 schrieb Nikos Balkanas:

Sorry, about the confusion Alej. But as you can see from the  
thread, Ishtiaq is already using sendsms to send his wap messages.  
He was asking if it is explicitly supported in wap.


Alex, seems like you did the work on meta-data. I don't believe it  
was ported to wap. I know that wap is no longer supported, but are  
you considering about porting it to wap?


BR,
Nikos
- Original Message -
From: Alejandro Guerrieri
To: Nikos Balkanas
Cc: Ishtiaq Ahmed ; users@kannel.org
Sent: Wednesday, July 15, 2009 4:30 PM
Subject: Re: wappush mBlox

I'm not sure about meta-data supports over wap (I'm an SMS  
guy ;) ), a possible option would be to encode the wap-push  
externally and use the sendsms interface instead (where you could  
use the meta-data parameters for sure).


Se here:

http://www.blogalex.com/archives/12

Regards,

Alejandro

PS: For the record, meta-data support was added by Alex Malyish,  
I've only submitted a few patches afterwards.


2009/7/15 Nikos Balkanas nbalka...@gmail.com
Hi,

Hmmm. That is indeed cleaner. You seem to know what you are doing.  
meta-data support was added by Alex G, last year. I strongly  
suspect that he skipped wap. Alex, would you care to comment?


You should know that wap is no longer supported in kannel for the  
past 2 years or so.



BR,
Nikos
- Original Message - From: Ishtiaq Ahmed ishtiaq.ah...@ooober.com 


To: Nikos Balkanas nbalka...@gmail.com
Cc: users@kannel.org
Sent: Wednesday, July 15, 2009 9:10 AM
Subject: Re: wappush mBlox



Hi Nikos,

Let me make things more clear for you... mBlox is a US based mobile  
operator... and there are specific TLVs that needs to be set using  
meta-data tag in sendsms interface... Here is one example...


http://KANNELBOX:13131/cgi-bin/sendsms?to=%2B14168874XXXtext=grassrootsdlr-url=http%3A%2F%2FSTAGGING%3A7080%2Fsmsprocessor%2Frdr.htm%3Fstatus%3D%25d%26text%3D%25A%26phone%3D%25p%26shortcode%3D%25P%26smscid%3D%25i%26meta-data%3D%25D%26refmsgid%3D17819%26uid%3D1823dlr-mask=31from=510XXpassword=12345username=12345FREE_MESSGAE=Ysmsc=MBlox*meta-data=%3Fsmpp%3FMToperator%3D113%26

Now here we are setting the values for the TLVs like MTOperator  
which has been configured in the kannel.conf like this...


group = smpp-tlv
name = MToperator
tag = 0x2150
type = integer
length = 2

*Now my question is how would we set the TLV values while using  
the /wappush



I hope this may made things clear


Regards,

Ishtiaq Ahmed




Nikos Balkanas wrote:
Hi,

I don't understand your problem:

1) What is mBlox?
2) What is ppg meta-data? Do you mean pap control document?

If your problem is that you cannot use your /wappush interface,  
please post:


1) PAP  SI XML post documents
2) Configuration file(s)
3) Maximum detail wapbox relevant logs

BR,
Nikos
- Original Message - From: Ishtiaq Ahmed ishtiaq.ah...@ooober.com 


To: users@kannel.org
Sent: Tuesday, July 14, 2009 12:39 PM
Subject: wappush mBlox


Hi Fellows,

I am trying to use the /wappush interface for sending out the wap  
push to mblox network. For this I need to set the meta-data for  
mBlox. I am able to send out in UDH format with sendsms interface,  
but dont know exactly how to set the meta-data for ppg (/wappush)  
interface.



Any help in this regard would be very helpful...



Thanks,


Ishtiaq Ahmed