Re: [Couldnot parse DLR string sscanf way, fallback to old way. Please report!] -- problem with message id

[Milan P. Stanic]

size: 4
> > 2016-08-22 16:14:53 [18226] [6] DEBUG:  immutable: 0
> > 2016-08-22 16:14:53 [18226] [6] DEBUG:  data: 03 00 00  
> > ...
> > 2016-08-22 16:14:53 [18226] [6] DEBUG:Octet string dump ends.
> > 2016-08-22 16:14:53 [18226] [6] DEBUG:   message_state: 2 = 0x0002
> > 2016-08-22 16:14:53 [18226] [6] DEBUG:   receipted_message_id: "13F19886"
> > 2016-08-22 16:14:53 [18226] [6] DEBUG: SMPP PDU dump ends.
> > 2016-08-22 16:14:53 [18226] [6] DEBUG: SMPP[SMSC] handle_pdu, got DLR
> > 2016-08-22 16:14:53 [18226] [6] DEBUG: SMPP[SMSC]: Could not parse DLR 
> > string sscanf way, fallback to old way. Please report!
> > 2016-08-22 16:14:53 [18226] [6] ERROR: SMPP[SMSC]: got DLR but could not 
> > find message or was not interested in it id<> dst<79028710256>, type<2>
> > 
> > 
> > 
> > 
> > 22.08.2016 12:58, amal...@kannel.org <mailto:amal...@kannel.org> пишет:
> >> Hi,
> >> 
> >> please try SVN version. Looks like 1.4.4 has issue with TLVs…
> >> 
> >> Alex
> >> 
> >> 
> >>> Am 15.08.2016 um 06:43 schrieb Черепанов Алексей Владиславович 
> >>> mailto:sw_cherepa...@motivtelecom.ru>>:
> >>> 
> >>> Here's the dump of packets.
> >>> 
> >>> 
> >>> Short Message Peer to Peer, Command: Submit_sm - resp, Status: "Ok", Seq: 
> >>> 684, Len: 25
> >>> Length: 25
> >>> Operation: Submit_sm - resp (0x8004)
> >>> Result: Ok (0x)
> >>> Sequence #: 684
> >>> Message id.: 2D8B40B4
> >>> 
> >>> Short Message Peer to Peer, Command: Deliver_sm, Seq: 674395051, Len: 95
> >>> Length: 95
> >>> Operation: Deliver_sm (0x0005)
> >>> Sequence #: 674395051
> >>> Service type: (Default)
> >>> Type of number (originator): International (0x01)
> >>> Numbering plan indicator (originator): ISDN (E163/E164) (0x01)
> >>> Originator address: 79028710256
> >>> Type of number (recipient): International (0x01)
> >>> Numbering plan indicator (recipient): ISDN (E163/E164) (0x01)
> >>> Recipient address: 343269
> >>>  ..00 = Messaging mode: Default SMSC mode (0x00)
> >>> ..00 01.. = Message type: Short message contains SMSC Delivery 
> >>> Receipt (0x01)
> >>> 00..  = GSM features: No specific features selected (0x00)
> >>> Protocol id.: 0x7f
> >>> Priority level: GSM: None  ANSI-136: Bulk IS-95: Normal 
> >>> (0x00)
> >>> Scheduled delivery time: Immediate delivery
> >>> Validity period: SMSC default validity period
> >>>  ..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)
> >>>  ...0 = Replace: Don't replace (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)
> >>> Predefined message: 0
> >>> Message length: 0
> >>> Optional parameters
> >>> Optional parameter: message_state (0x0427)
> >>> Tag: 0x0427
> >>> Length: 1
> >>> Message state: DELIVERED (2)
> >>> Optional parameter: network_error_code (0x0423)
> >>> Tag: 0x0423
> >>> Length: 3
> >>> Error type: GSM (3)
> >>> Error code: 0x
> &

Re: [Couldnot parse DLR string sscanf way,fallback to old way. Please report!] -- problem with message id

[Milan P. Stanic]

On Fri, 2016-08-12 at 15:27, Черепанов Алексей Владиславович wrote:
> Hi, there. Having a problem with handling deliver_sm.
> Kannel couldn't parse message id:
> 
> 2016-08-12 14:45:59 [2952] [6] DEBUG: SMPP[SMSC]: Couldnot parse DLR string
> sscanf way,fallback to old way. Please report!
> 2016-08-12 14:45:59 [2952] [6] ERROR: SMPP[SMSC]: got DLR but could not find
> message or was not interested in it id<> dst<79028710256>, type<2>
> 2016-08-12 14:45:59 [2952] [6] DEBUG: message_id: NULL

Look like your provider (upstream SMPP server) does not send 'standard'
DLR message.
Actually there is no standard format for DLR message but most providers
format it following sample in SMPP specification document.

Could you check with your provider in what format their server send
message to your kannel. Or, you can extract it with some network capture
tools (tcpdump, tshark/wireshark) and see in what format messages are.

Re: Error in kannel-monitor

[Milan P. Stanic]

Dear Vladimir,

Please post your questions to us...@kannel.org mailing list where you
have better chances to get answer. devel@kannel.org list is for
developers discussions.

On Tue, 2016-03-01 at 10:47, Беляев Владимир Николаевич wrote:
> $url = $config["base_url"]."/status.xml";
> $xml_data = "";
> /* open the file description to the URL */
> if (($fp = fopen($url, "r"))) {
> $bgcolor = 'green';
> /* read the XML input */
> while (!feof($fp)) {
> $xml_data .= fread($fp, 20);
> }
> fclose($fp);
> 
> Through the browser opens the URL

It is not clear (at least to me) what you are trying to do with this php
script and how do invoke it. Please try to describe what you are trying
to achieve and how do you do that. Also describe your working
environment i.e. your OS and how did you installed Kannel and
accompanying software.

> > When you open a kannel-monitor I get an error
> > 
> > [Tue Feb 09 09:50:14.899177 2016] [:error] [pid 45752] [client 
> > 172.19.1.35:56951] PHP Warning:
> > fopen(http://localhost:13000/status.xml?password=): failed to open stream:
> > Permission denied in /var/www/html/kannel-monitor/index.php on line 91
> > 
> > What can be wrong&
> 
> Message tells that the index.php cannot open something (file, socket or 
> something else).
> Look at line 91 in index.php script and see what file it is trying to open 
> and check the permissions of that file and who is the owner of it.
> 
> Or, post your index.php script (just few lines around line 91) so someone 
> could give you a hint.
> 
> 
> 

Re: Not work "priority" in settings SMSC

[Milan P. Stanic]

On Wed, 2016-02-10 at 14:41, Беляев Владимир Николаевич wrote:
> Option does not work "priority" in settings SMSC.
> 
> I set up the SMSC1 priority=0, SMSC2 priority=3, but SMS is distributed
> evenly.
> 
> Why can this be?

devel@kannel.org mailing list is mostly for development questions.
It would be better to post your question to us...@kannel.org mailing
list where are a lot of kannel users reads posts and some of them ready
to help. Probably there are bigger chances to get answers about
configuration (and other usage) problems. 

Re: Error in kannel-monitor

[Milan P. Stanic]

On Tue, 2016-02-09 at 10:04, Беляев Владимир Николаевич wrote:
> Добрый день!
Здравствуйте!

> When you open a kannel-monitor I get an error
> 
> [Tue Feb 09 09:50:14.899177 2016] [:error] [pid 45752] [client
> 172.19.1.35:56951] PHP Warning:
> fopen(http://localhost:13000/status.xml?password=): failed to open stream:
> Permission denied in /var/www/html/kannel-monitor/index.php on line 91
> 
> What can be wrong&

Message tells that the index.php cannot open something (file, socket or
something else).
Look at line 91 in index.php script and see what file it is trying to
open and check the permissions of that file and who is the owner of it.

Or, post your index.php script (just few lines around line 91) so
someone could give you a hint.

Re: Error INSERT INTO sent_sms

[Milan P. Stanic]

On Fri, 2016-02-05 at 13:57, Беляев Владимир Николаевич wrote:
> Добрый день!

Добар дан! :)
 
> An error occurred while sending sms:
> 
> DEBUG: sql: INSERT INTO sent_sms ( sql_id, momt, sender, receiver, udhdata,
> msgdata, time, smsc_id, service, account, sms_type, mclass, mwi, coding,
> compress, validity, deferred, dlr_mask, dlr_url, pid, alt_dcs, rpi, charset,
> boxc_id, binfo, meta_data ) VALUES ( NULL, 'DLR', 'SNGB', '+79682012971',
> NULL, 'id:33303613023 sub:001 dlvrd:001 submit date:1602051127 done
> date:1602051127 stat:DELIVRD err:0 text:
> 
> ERROR: MYSQL: You have an error in your SQL syntax; check the manual that
> corresponds to your MariaDB server version for the right syntax to use near
> ''id:33303613023 sub:001 dlvrd:001 submit date:1602051127 done
> date:1602051127 st' at line 1

I didn't worked with MariaDB and don't know if it's syntax differs from
Mysql. Anyway, look s like there is missing ending single quote
character (') around value for meta_data column.
Are you sure you DEBUG text (look above) is properly posted here?

> 2016-02-05 13:32:57 [57147] [4] DEBUG: smsbox_to_bearerbox: sms received
> 
> SMPP dump:
> 2016-02-05 13:33:01 [57268] [6] DEBUG: Optional parameter length read as 12
> 2016-02-05 13:33:01 [57268] [6] DEBUG: SMPP[smstraffic_test]: Got PDU:
> 2016-02-05 13:33:01 [57268] [6] DEBUG: SMPP PDU 0x7f259c000a30 dump:
> 2016-02-05 13:33:01 [57268] [6] DEBUG: type_name: deliver_sm
> 2016-02-05 13:33:01 [57268] [6] DEBUG: command_id: 5 = 0x0005
> 2016-02-05 13:33:01 [57268] [6] DEBUG: command_status: 0 = 0x
> 2016-02-05 13:33:01 [57268] [6] DEBUG: sequence_number: 404759 = 0x00062d17
> 2016-02-05 13:33:01 [57268] [6] DEBUG: service_type: NULL
> 2016-02-05 13:33:01 [57268] [6] DEBUG: source_addr_ton: 0 = 0x
> 2016-02-05 13:33:01 [57268] [6] DEBUG: source_addr_npi: 0 = 0x
> 2016-02-05 13:33:01 [57268] [6] DEBUG: source_addr: "79682012971"
> 2016-02-05 13:33:01 [57268] [6] DEBUG: dest_addr_ton: 0 = 0x
> 2016-02-05 13:33:01 [57268] [6] DEBUG: dest_addr_npi: 0 = 0x
> 2016-02-05 13:33:01 [57268] [6] DEBUG: destination_addr: "SNGB"
> 2016-02-05 13:33:01 [57268] [6] DEBUG: esm_class: 4 = 0x0004
> 2016-02-05 13:33:01 [57268] [6] DEBUG: protocol_id: 0 = 0x
> 2016-02-05 13:33:01 [57268] [6] DEBUG: priority_flag: 0 = 0x
> 2016-02-05 13:33:01 [57268] [6] DEBUG: schedule_delivery_time: NULL
> 2016-02-05 13:33:01 [57268] [6] DEBUG: validity_period: NULL
> 2016-02-05 13:33:01 [57268] [6] DEBUG: registered_delivery: 0 = 0x
> 2016-02-05 13:33:01 [57268] [6] DEBUG: replace_if_present_flag: 0 =
> 0x
> 2016-02-05 13:33:01 [57268] [6] DEBUG: data_coding: 0 = 0x
> 2016-02-05 13:33:01 [57268] [6] DEBUG: sm_default_msg_id: 0 = 0x
> 2016-02-05 13:33:01 [57268] [6] DEBUG: sm_length: 116 = 0x0074
> 2016-02-05 13:33:01 [57268] [6] DEBUG: short_message:
> 2016-02-05 13:33:01 [57268] [6] DEBUG: Octet string at 0x7f259c000d60:
> 2016-02-05 13:33:01 [57268] [6] DEBUG: len: 116
> 2016-02-05 13:33:01 [57268] [6] DEBUG: size: 117
> 2016-02-05 13:33:01 [57268] [6] DEBUG: immutable: 0
> 2016-02-05 13:33:01 [57268] [6] DEBUG: data: 69 64 3a 33 33 33 30 33 37 37
> 32 35 31 35 20 73 id:33303772515 s
> 2016-02-05 13:33:01 [57268] [6] DEBUG: data: 75 62 3a 30 30 31 20 64 6c 76
> 72 64 3a 30 30 31 ub:001 dlvrd:001
> 2016-02-05 13:33:01 [57268] [6] DEBUG: data: 20 73 75 62 6d 69 74 20 64 61
> 74 65 3a 31 36 30 submit date:160
> 2016-02-05 13:33:01 [57268] [6] DEBUG: data: 32 30 35 31 31 33 32 20 64 6f
> 6e 65 20 64 61 74 2051132 done dat
> 2016-02-05 13:33:01 [57268] [6] DEBUG: data: 65 3a 31 36 30 32 30 35 31 31
> 33 33 20 73 74 61 e:1602051133 sta
> 2016-02-05 13:33:01 [57268] [6] DEBUG: data: 74 3a 44 45 4c 49 56 52 44 20
> 65 72 72 3a 30 20 t:DELIVRD err:0
> 2016-02-05 13:33:01 [57268] [6] DEBUG: data: 74 65 78 74 3a 54 65 73 74 20
> 44 4c 52 20 53 4d text:Test DLR SM
> 2016-02-05 13:33:01 [57268] [6] DEBUG: data: 50 50 20 33 PP 3
> 2016-02-05 13:33:01 [57268] [6] DEBUG: Octet string dump ends.
> 2016-02-05 13:33:01 [57268] [6] DEBUG: message_state: 2 = 0x0002
> 2016-02-05 13:33:01 [57268] [6] DEBUG: receipted_message_id: "33303772515"
> 2016-02-05 13:33:01 [57268] [6] DEBUG: SMPP PDU dump ends.
> 
> Send code:
> 
> my $resp = $smpp->submit_sm( source_addr => 'SNGB',
> source_addr_ton => 0x05,
> source_addr_npi => 0x01,
> destination_addr => $phone,
> dest_addr_ton => 0x01,
> dest_addr_npi => 0x01,
> data_coding => 0x08,
> message_payload => $msg_ucs2,
> esm_class => 0x00,
> registered_delivery => 1);

Is this some ready made function or something you developed in house?

Re: Fwd: Need Help Regarding Encrypting Passwords

[Milan P. Stanic]

On Wed, 2015-07-08 at 10:31, Stipe Tolj wrote:
> Am 15.05.2015 07:55, schrieb Pandey Nitin:
> >Can you please help me regarding the encryption of the passwords that we
> >use in kannel configuration files.
> >
> >For example - I want to use the encrypted passwords in KANNEL.CONF file
> >for -
> >1. SMSC connection
> >2. ADMIN passwords.
> I'd like to assist here. Can you please describe the scenario for the
> required encrypted counterparts of of passwords in the config?
> 
> For the admin password it's pretty clear, and can be facilitated via sha1
> hash values, since the user needs to provide the password interactively when
> performing and HTTP admin URI command.
> 
> But how about SMSC connection passwords? Bearerbox needs to send them to the
> SMSC in plain-text. So, the daemon needs to be able to recover them from any
> crypt-ed version.
> 
> An idea would be to use AES to encrypt them with the admin keyword. Then at
> daemon start time the calling user would need to supply the admin password
> on the command line to let bearerbox "unlock" the crypt-ed string in the
> config to gain the plain-text for communication with the SMSC.

Is it wise to give any password on the command line, especially for long
running processes, because it could be seen with the simple 'ps' command
except when the system is security hardened.

> In addition you would need to "shadow" the password strings in the log
> files.
> 
> Is there no chance to use file permissions for this, if it's "only" a matter
> of grouping the maintenance staff to see/no-see of passwords in the config?

-- 
Kind regards

Re: USSD connection problem

[Milan P. Stanic]

On Tue, 2015-02-10 at 19:14, mohammad hossein shafinia wrote:
> We have installed Kannel 1.5.0 to resolve connecting with USSD via TLV.
> 
> With this version SMSbox and bearbox didn't stopped and we connected to
> USSD gateway.
> 
> But unfortunately we can't receive any USSD request.

I don't know if USSD can be over SMPP in Kannel. It can be sent over
modem, IIRC.

> Would you please help us and share with us a sample config file.

As I told in my previous mail, I don't use Kannel anymore so I cannot
help you with your problem.

> Please find our config file in the attachment.
> On Sat, Feb 7, 2015 at 4:34 PM, Milan P. Stanic  wrote:
> 
> > On Sat, 2015-02-07 at 16:06, mohammad hossein shafinia wrote:
> > > Thank you so much for your helpful comment.
> > >
> > > Also would you please let us know if the config file is OK?
> >
> > I don't use (unfortunately) Kannel for more than two years so I cannot
> > tell much about your config.
> > Upgrade Kannel to one of the newer version and test it. If it does not
> > work then post your log and config, so someone else could help you, I
> > hope.
> >
> > > On Sat, Feb 7, 2015 at 3:42 PM, Milan P. Stanic  wrote:
> > > > On Sat, 2015-02-07 at 12:47, mohammad hossein shafinia wrote:
> > > > [...]
> > > > > However, I want to develop an application to connect to USSD. But I
> > don't
> > > > > know how do I configure (kannel.conf) to connect to USSD. First we
> > > > changed
> > > > > the configuration of kannel.conf similar to what we done for SMS,
> > then
> > > > > restarted Kannel and we was connected to USSD server, but we couldn't
> > > > send
> > > > > or receive any USSD transaction. After that we searched more and
> > find a
> > > > > parameter named TLV and changed the parameter based on that, but
> > after
> > > > > restarting the Kannel, SMSbox and bearbox just stopped.
> > > > >
> > > > > Can you give me a sample of kannel.conf for connection to USSD ?
> > > > >
> > > > > Also please find the current config file that we are using now in the
> > > > > attachment. Please let me know how we have to change that config
> > file.
> > > > >
> > > > > Version: Kannel bearerbox version `1.4.1'.
> > > >
> > > > Kannel version 1.4.1 does not support TLVs, IIRC.
> > > >
> > > > You should use 1.4.4 or 1.5.0 (or even SVN) version not just because of
> > > > TLVs but because 1.4.1 is really old and lots of bugs are fixed in
> > newer
> > > > versions.

-- 
Kind regards,  Milan
--
Arvanta,http://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: USSD connection problem

[Milan P. Stanic]

On Sat, 2015-02-07 at 16:06, mohammad hossein shafinia wrote:
> Thank you so much for your helpful comment.
> 
> Also would you please let us know if the config file is OK?

I don't use (unfortunately) Kannel for more than two years so I cannot
tell much about your config.
Upgrade Kannel to one of the newer version and test it. If it does not
work then post your log and config, so someone else could help you, I
hope.

> On Sat, Feb 7, 2015 at 3:42 PM, Milan P. Stanic  wrote:
> > On Sat, 2015-02-07 at 12:47, mohammad hossein shafinia wrote:
> > [...]
> > > However, I want to develop an application to connect to USSD. But I don't
> > > know how do I configure (kannel.conf) to connect to USSD. First we
> > changed
> > > the configuration of kannel.conf similar to what we done for SMS, then
> > > restarted Kannel and we was connected to USSD server, but we couldn't
> > send
> > > or receive any USSD transaction. After that we searched more and find a
> > > parameter named TLV and changed the parameter based on that, but after
> > > restarting the Kannel, SMSbox and bearbox just stopped.
> > >
> > > Can you give me a sample of kannel.conf for connection to USSD ?
> > >
> > > Also please find the current config file that we are using now in the
> > > attachment. Please let me know how we have to change that config file.
> > >
> > > Version: Kannel bearerbox version `1.4.1'.
> >
> > Kannel version 1.4.1 does not support TLVs, IIRC.
> >
> > You should use 1.4.4 or 1.5.0 (or even SVN) version not just because of
> > TLVs but because 1.4.1 is really old and lots of bugs are fixed in newer
> > versions.

-- 
Kind regards,  Milan
--
Arvanta,http://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: USSD connection problem

[Milan P. Stanic]

On Sat, 2015-02-07 at 12:47, mohammad hossein shafinia wrote:
[...]
> However, I want to develop an application to connect to USSD. But I don't
> know how do I configure (kannel.conf) to connect to USSD. First we changed
> the configuration of kannel.conf similar to what we done for SMS, then
> restarted Kannel and we was connected to USSD server, but we couldn't send
> or receive any USSD transaction. After that we searched more and find a
> parameter named TLV and changed the parameter based on that, but after
> restarting the Kannel, SMSbox and bearbox just stopped.
> 
> Can you give me a sample of kannel.conf for connection to USSD ?
> 
> Also please find the current config file that we are using now in the
> attachment. Please let me know how we have to change that config file.
> 
> Version: Kannel bearerbox version `1.4.1'.

Kannel version 1.4.1 does not support TLVs, IIRC.

You should use 1.4.4 or 1.5.0 (or even SVN) version not just because of
TLVs but because 1.4.1 is really old and lots of bugs are fixed in newer
versions.

-- 
Kind regards,  Milan
--
Arvanta,http://www.arvanta.net
Please do not send me e-mail containing HTML code or documents in
proprietary format (word, excel, pps and so on)

Opensmppbox naming for debian package

[Milan P. Stanic]

Hi,

I've built kannel and opensmppbox for debian stable (wheezy) and I want
to put the packages to apt repository to easing installation for users
of the debian and debian derived distributions.

I have doubt about name of the opensmppbox (and sqlbox, maybe). I named
it kannel-opensmppbox for now (and thought to do same for sqlbox, i.e.
kannel-sqlbox) but I'm not sure if that is right.

So, please help me to resolve my dilemma and give me constructive
suggestions about naming scheme.

Especially I want to hear original authors of the opensmppbox (Rene) and
sqlbox (Alejandro, IIRC) and their opinion.

-- 
Kind regards
--
Arvanta,http://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: mysql support for kannel 1.5.0 from DEB packages

[Milan P. Stanic]

On Sat, 2013-01-05 at 07:26, cgchen wrote:
> Hi,
> 
> Can someone please confirm that kannel 1.5.0 from deb package comes with 
> mysql support. The reason I asked is because as soon as I changed dlr-storage 
> to mysql with mysql connection settings from the user guide, I'm not able to 
> start kannel back up

My bad. Despite the fact I put in description file that the deb package
is compiled with 'sqlite3, MySQL, Postgresql' support, it is compiled
with sqlite3 support only.

This weekend I'll try to build it according to the description file.

-- 
Kind regards,  Milan
--
Arvanta,http://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: debian wheezy kannel 1.5.0 with kannel-sqlbox 0.7.2.-3

[Milan P. Stanic]

On Sat, 2013-01-05 at 05:57, cgchen wrote:
> Hi
> 
> I've been trying to integrate sqlbox with kannel. Kannel 1.5.0 is installed 
> through the downloaded deb package as per installation guide and 
> kannel-sqlbox 0.7.2-3 is installed through apt-get install on Debian Wheezy.
 
Kannel 1.5.0 is not in official Debian repository, AFAIK.
Where from you downloaded deb packages?

If you downloaded deb packages from Kannel site
(https://redmine.kannel.org/projects/kannel/files) then you cannot use
kannel-sqlbox from Debian repository because it is not compatible with
Kannel 1.5.0 version from the Kannel site.

I built kannel-sqlbox-1.5.0 (for amd64 arch only) which is compatible
with above mentioned Kannel but I didn't uploaded it because I didn't
tested it (I don't use sqlbox so I couldn't test it).

If you installed Kannel deb packages from Kannel site send me i private
mail and I will post sqlbox deb package to you if you are brave to test
it.

> My problem is that when smsbox is connected directly to the bearerbox, 
> everything works fine but when I added sqlbox in the middle of the 2, all the 
> processes starts up fine as usual but as soon as I send a msg, both the 
> smsbox and sqlbox processes crashes instantly. Please see below for sqlbox 
> logs:
> 
>  2013-01-05 22:38:18 [8658] [0] INFO: Added logfile 
> `/var/log/kannel/kannel-sqlbox.log' with level `0'.
> 2013-01-05 22:38:18 [8658] [0] INFO: MYSQL: Connected to server at localhost.
> 2013-01-05 22:38:18 [8658] [0] INFO: MYSQL: server version 5.1.66-0+squeeze1, 
> client version 5.1.66.
> 2013-01-05 22:38:18 [8658] [0] DEBUG: Started thread 1 
> (sqlbox.c:sql_to_bearerbox)
> 2013-01-05 22:38:18 [8658] [1] DEBUG: Thread 1 (sqlbox.c:sql_to_bearerbox) 
> maps to pid 8658.
> 2013-01-05 22:38:18 [8658] [1] INFO: Connected to bearerbox at 127.0.0.1 port 
> 13001.
> 2013-01-05 22:38:18 [8658] [1] DEBUG: Started thread 2 
> (sqlbox.c:bearerbox_to_sql)
> 2013-01-05 22:38:18 [8658] [2] DEBUG: Thread 2 (sqlbox.c:bearerbox_to_sql) 
> maps to pid 8658.
> 2013-01-05 22:38:19 [8658] [0] DEBUG: Started thread 3 (sqlbox.c:function)
> 2013-01-05 22:38:19 [8658] [3] DEBUG: Thread 3 (sqlbox.c:function) maps to 
> pid 8658.
> 2013-01-05 22:38:19 [8658] [3] INFO: Client connected from <127.0.0.1>
> 2013-01-05 22:38:19 [8658] [3] INFO: Connected to bearerbox at 127.0.0.1 port 
> 13001.
> 2013-01-05 22:38:19 [8658] [3] DEBUG: Started thread 4 
> (sqlbox.c:bearerbox_to_smsbox)
> 2013-01-05 22:38:19 [8658] [3] DEBUG: smsbox_to_bearerbox: got boxc_id 
>  from <127.0.0.1>
> 2013-01-05 22:38:19 [8658] [4] DEBUG: Thread 4 (sqlbox.c:bearerbox_to_smsbox) 
> maps to pid 8658.
> 2013-01-05 22:38:53 [8658] [3] DEBUG: smsbox_to_bearerbox: sms received
> 2013-01-05 22:38:53 [8658] [4] INFO: Connection closed by the box <127.0.0.1>
> 2013-01-05 22:38:53 [8658] [4] DEBUG: bearerbox_to_smsbox: connection to 
> bearerbox died.
> 2013-01-05 22:38:53 [8658] [4] DEBUG: Thread 4 (sqlbox.c:bearerbox_to_smsbox) 
> terminates.
> 2013-01-05 22:38:53 [8658] [3] DEBUG: Thread 3 (sqlbox.c:function) terminates.
> 2013-01-05 22:38:53 [8658] [1] DEBUG: Thread 1 (sqlbox.c:sql_to_bearerbox) 
> terminates.
> 2013-01-05 22:39:03 [8658] [0] DEBUG: Thread 2 (sqlbox.c:bearerbox_to_sql) 
> still running
> 2013-01-05 22:39:03 [8658] [0] DEBUG: Immutable octet strings: 62.
> 
> 
> Does anybody know why this is happening or had any success with such setup 
> and could provide any assistance is much appreciated.
> 
> Thanks in advance.
> 
> Here is my complete setup:
> 
> group = core
> dlr-storage = internal
> admin-port = 13000
> admin-password = abcabc
> status-password = abcabc
> admin-deny-ip = "*.*.*.*"
> admin-allow-ip = "127.0.0.1;192.168.1.*"
> smsbox-port = 13001
> log-level = 0
> log-file = "/var/log/kannel/bearerbox.log"
> box-deny-ip = "*.*.*.*"
> box-allow-ip = "127.0.0.1;192.168.1.*"
> 
> group = smsbox
> smsbox-id = smsbox1
> bearerbox-host = 127.0.0.1
> bearerbox-port = 13003
> sendsms-port = 13013
> log-file = "/var/log/kannel/smsbox.log"
> log-level = 0
> access-log = "/var/log/kannel/access.log"
> 
> group = sendsms-user
> username = abcabc
> password = abcabc
> 
> group = smsc
> smsc = smpp
> smsc-id = SMSC1
> host = 1
> port = 1
> smsc-username = abcabc
> smsc-password = abcabc
> address-range = ""
> system-type = ""
> transceiver-mode = true
> 
> group = sms-service
> keyword = default
> accept-x-kannel-headers = true
> max-messages = 100
> assume-plain-text = true
> catch-all = true
> 
> ##sqlbox
> group = sqlbox
> id = sqlbox-db
> smsbox-id = smsbox1
> #smsbox-id = sqlbox
> #global-sender = ""
> bearerbox-host = 127.0.0.1
> bearerbox-port = 13001
> smsbox-port = 13003
> smsbox-port-ssl = false
> sql-log-table = sent_sms
> sql-insert-table = send_sms
> log-file = "/var/log/kannel/kannel-sqlbox.log"
> log-level = 0
> #ssl-client-certkey-file = ""
> #ssl-server-cert-file = ""
> #ssl-server-key-file = ""
> #ssl-trusted-ca-file = ""
> 
> # Database connection examples. Please uncomment a

Re: sim-buffering

[Milan P. Stanic]

Mailing list devel@kannel.org is to discus development of the Kannel.
You shouldn't post questions about Kannel usage to this list.

User question should be posted to us...@kannel.org.

On Mon, 2012-12-03 at 15:01, Navdeep Bagga wrote:
> I find huawei modem
> 
> Huawei E220 3G USB Modem 7.2Mbps
> http://www.ebay.in/sch/i.html?_trksid=p3907.m570.l1313&_nkw=huawei+e220&_sacat=0&_from=R40
> 
> Is this modem compatible with kannel?

Yes, it is.

> if not please refer me which modem I should buy
> Thanking You.
> On Mon, Dec 3, 2012 at 11:21 AM, Andreas Fink  wrote:
> > the phone most probably doesn't support this mode. its a limit of the 
> > hardware you are using.
> > To receive lots of sms you should use reliable gsm modems or get incoming 
> > messages directly from an operator's smsc or from a incoming proxy provider.

-- 
Kind regards,  Milan
--
Arvanta,http://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: OpenSNMPP and SQLBox package building ?

[Milan P. Stanic]

On Sun, 2012-09-30 at 08:27, Sebastien Cramatte wrote:
> Hi,
> 
> I've finally create  package for SQLBox and OpenSMPP and rebuild Kannel 1.5  
> with mysql, sqlite3 and postgre support.
> SQLBox and OpenSNMPP packages still requires clean up, fix dependencies and  
> include docs  and examples.
> Moreover I need description for both package.
> 
> But I would be happy to contribute to SVN :)

Debian devs doesn't like debian dirs in upstream source but they
tolerate that. And I tend to agree with them because IMHO it is not a
good idea to have every distribution and OS's packaging files in
upstream source. This can lead to messy scripts and put more burden to
upstream developer and maintainer.

Best way is to use Debian diffs against upstream package and use
dpkg-source to create build environment.

These days I'm waiting for next stable Debian release and I'm preparing
Kannel 1.5.0 for it. I already prepared sqlbox and opensmppbox packages.

And I hope we will have next stable Kannel release real soon now. ;-)
Yes, I know that the 1.5.0 is quite stable but I see that a lot of
people (actually managers) doesn't like to use any software with a
development tag attached.

Last year I've built 1.5.0 and it can be found on the:
https://redmine.kannel.org/projects/kannel/files

I've also built sqlbox and opensmppbox deb packages but didn't uploaded
(actually Alex put files there) because these two were/are just
included in the Kannel addons section and at that time I was not sure
how they were stable for users with faint of heart.

In short, I'm against the idea of including distro or OS packaging mess
into upstream. Leave that job to the packagers.

> Best regards
> 
> De: spameden mailto:spame...@gmail.com>>
> Fecha: Sun, 30 Sep 2012 02:11:48 +0400
> Para: - - mailto:scrama...@nixus.es>>
> CC: "devel@kannel.org" 
> mailto:devel@kannel.org>>
> Asunto: Re: OpenSNMPP and SQLBox package building ?
> 
> You mean build it as a debian package (.deb)?
> 
> Yeah, you would need to add manually folder with a rules or use checkinstall.
> 
> 2012/9/30 Sebastien Cramatte mailto:scrama...@nixus.es>>
> Hi,
> 
> I've just rebuild Kannel 1.5  package for my Debian squeeze.
> 
> I would like to build SQLBox and OpenSNMPP.
> Does it exists somewhere base  debian folder  to achieve this  as 
> unfortunately  in SVN doesn't exists ?
> 
> Best regards
> 

-- 
Kind regards,  Milan
--
Arvanta,http://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: devel Digest, Vol 68, Issue 13

[Milan P. Stanic]

On Fri, 2012-04-20 at 16:41, Alexander Malysh wrote:
> there was indeed BUG. I have fixed it in SVN.

Ah, yes. I see diff. Tnx for clarification.

When I wrote that my svn version works it was from a little outdated
revision.
 
> Am 20.04.2012 um 14:41 schrieb Tanja Kipreska:
> > Hello Milan, 
> > I haven't changed anything in the code.
> > I've just downloaded the newest kannel_snapshot, compiled it and tried 
> > again. 
> > 
> > The scenario i'm performing is following:
> > 1. Start bearerbox (testgw:/vas/bin/kannel_1.5.0_20.04.2012/sbin # 
> > ./bearerbox -v 1 /vas/config/kannel/kannel_tanja.conf)
> > 2. Start smsbox (testgw:/vas/bin/kannel_1.5.0_20.04.2012/sbin # ./smsbox -v 
> > 1 /vas/config/kannel/kannel_tanja.conf)
> > 3. Send SIGINT to smsbox process (smsbox process is terminated and 
> > restarted after 10 seconds with new PID)
> > testgw:/vas/bin/kannel_1.5.0_20.04.2012/sbin # ./smsbox -v 1 
> > /vas/config/kannel/kannel_tanja.conf (see bellow)
> > 2012-04-20 14:25:36 [9535] [0] INFO: Debug_lvl = 1, log_file = , 
> > log_lvl = 0
> > 2012-04-20 14:25:36 [9535] [0] INFO: Logging accesses to 
> > '/vas/logs/kannel/smsboxaccess.log'.
> > 2012-04-20 14:25:36 [9535] [0] INFO: Started access logfile 
> > `/vas/logs/kannel/smsboxaccess.log'.
> > 2012-04-20 14:25:36 [9535] [0] INFO: HTTP: Opening server at port 4004.
> > 2012-04-20 14:25:36 [9535] [0] INFO: Set up send sms service at port 4004
> > 2012-04-20 14:25:36 [9535] [0] INFO: Using HTTP request queueing with 10 
> > retries, 60s delay.
> > 2012-04-20 14:25:36 [9535] [0] INFO: Connected to bearerbox at localhost 
> > port 4001.
> > ^C2012-04-20 14:25:41 [9535] [0] ERROR: SIGINT received, aborting program...
> > 2012-04-20 14:25:41 [9535] [0] ERROR: Bearerbox is gone, restarting
> > 2012-04-20 14:25:41 [9535] [0] INFO: Received (and handled?) 0 requests in 
> > 5 seconds (0.00 per second)
> > 2012-04-20 14:25:41 [9535] [0] INFO: Kannel smsbox terminating.
> > testgw:/vas/bin/kannel_1.5.0_20.04.2012/sbin # 2012-04-20 14:25:52 [9545] 
> > [0] INFO: Debug_lvl = 1, log_file = , log_lvl = 0
> > 2012-04-20 14:25:52 [9545] [0] INFO: Logging accesses to 
> > '/vas/logs/kannel/smsboxaccess.log'.
> > 2012-04-20 14:25:52 [9545] [0] INFO: Started access logfile 
> > `/vas/logs/kannel/smsboxaccess.log'.
> > 2012-04-20 14:25:52 [9545] [0] INFO: HTTP: Opening server at port 4004.
> > 2012-04-20 14:25:52 [9545] [0] INFO: Set up send sms service at port 4004
> > 2012-04-20 14:25:52 [9545] [0] INFO: Using HTTP request queueing with 10 
> > retries, 60s delay.
> > 2012-04-20 14:25:52 [9545] [0] INFO: Connected to bearerbox at localhost 
> > port 4001.
> > 
> > I was analyzing the smsbox.c and according to output that i get i 
> > understand that first signal_handler is called
> > 
> > switch (signum) {
> > case SIGINT:
> > 
> >if (program_status != shutting_down) {
> > error(0, "SIGINT received, aborting program...");
> > program_status = shutting_down;
> > }
> > break;
> > 
> > which is OK, than (according to the output messages) 
> > read_messages_from_bearerbox() is executed. More precisely 
> > 
> > while (program_status != shutting_down) {
> > /* block infinite for reading messages */
> > ret = read_from_bearerbox(&msg, INFINITE_TIME);
> > if (ret == -1) {
> > error(0, "Bearerbox is gone, restarting");
> > program_status = shutting_down;
> > restart = 1;
> > break;
> > } else if (ret == 1) /* timeout */
> >     continue;
> > else if (msg == NULL) /* just to be sure, may not happens */
> > break;
> > 
> > and this is odd because program_status was previously set to shutting_down 
> > (by the signal_handler function).
> > 
> > Please note that I'm compiling and running kannel on 64bit OS. Can this be 
> > the reason for this behavior?
> > 
> > Thanks in advance,
> > Tanja
> > 
> > 
> > 
> > Message: 2
> > Date: Fri, 20 Apr 2012 13:55:16 +0200
> > From: "Milan P. Stanic" 
> > To: devel@kannel.org
> > Subject: Re: After SIGINT received SMSBOX restarts (bug or a feature)
> > Message-ID: <20120420115515.ga17...@arvanta.net>
> > Content-Type: text/plain; charset=us-ascii
> > 
> > On Fri, 2012-04-20 at 09:19, Tanja Kipreska wrote:
> > 

Re: After SIGINT received SMSBOX restarts (bug or a feature)

[Milan P. Stanic]

On Fri, 2012-04-20 at 09:19, Tanja Kipreska wrote:
> Hello,
> 
> I've been testing kannel 1.5.0 for some time and I've noticed that when I
> start smsbox from command line - ./smsbox -v 0
> /vas/config/kannel_tanja.conf (not as daemon) , and than try to shut it
> down by generating SIGINT signal (CTRL+C), but smsbox process restarts with
> new PID. Please see output given bellow. My question is: Is this bug in
> smsbox process or a feature (expected behavior)?

I tried to start bearbox and smsbox (svn version) from command line and
stop it with CTRL-C (SIGINT). Both works as expected.

I can't see any bug in mentioned behavior, and smsbox (nor bearbox)
doesn't have that feature.

Did you changed source?

> testgw:/vas/bin/kannel_1.5.0_
> modified/sbin # ./smsbox -v 0 /vas/config/kannel_tanja.conf
> 2012-04-19 12:01:46 [984] [0] INFO: Debug_lvl = 0, log_file = ,
> log_lvl = 0
> 2012-04-19 12:01:46 [984] [0] DEBUG: Loading include file
> `/vas/config/kannel/kannel_services.conf' (on line 148 of file
> 
> /vas/config/kannel_tanja.conf).
> 2012-04-19 12:01:46 [984] [0] DEBUG: Kannel smsbox version `svn-r'.
> Build `Apr 10 2012 10:37:05', compiler `4.3.4 [gcc-4_3-branch revision
> 152973]'.
> System Linux, release 3.0.13-0.27-default, version #1 SMP Wed Feb 15
> 13:33:49 UTC 2012 (d73692b), machine
> 
> x86_64.
> Hostname testgw.one.net.mk, IP 127.0.0.2.
> Libxml version 2.7.6.
> Compiled with MySQL 5.5.21, using MySQL 5.5.21.
> Using native malloc.
> 
> 2012-04-19 12:01:46 [984] [0] INFO: Logging accesses to
> '/vas/logs/kannel/smsboxaccess.log'.
> 2012-04-19 12:01:46 [984] [0] INFO: Started access logfile
> `/vas/logs/kannel/smsboxaccess.log'.
> 2012-04-19 12:01:46 [984] [0] INFO: HTTP: Opening server at port 4004.
> 2012-04-19 12:01:46 [984] [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller)
> 2012-04-19 12:01:46 [984] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) maps
> to pid 984.
> 2012-04-19 12:01:46 [984] [0] DEBUG: Started thread 2
> (gwlib/http.c:server_thread)
> 2012-04-19 12:01:46 [984] [0] INFO: Set up send sms service at port 4004
> 2012-04-19 12:01:46 [984] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread)
> maps to pid 984.
> 2012-04-19 12:01:46 [984] [0] DEBUG: Started thread 3
> (gw/smsbox.c:sendsms_thread)
> 2012-04-19 12:01:46 [984] [3] DEBUG: Thread 3 (gw/smsbox.c:sendsms_thread)
> maps to pid 984.
> 2012-04-19 12:01:46 [984] [2] DEBUG: HTTP: Including port 4004, fd 9 for
> polling in server thread
> 2012-04-19 12:01:46 [984] [0] INFO: Using HTTP request queueing with 10
> retries, 60s delay.
> 2012-04-19 12:01:46 [984] [0] DEBUG:
> --
> 2012-04-19 12:01:46 [984] [0] DEBUG: Kannel smsbox version svn-r starting
> 2012-04-19 12:01:46 [984] [0] DEBUG:   dumping group (sendsms-user):
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = <*.*.*.*>
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = 
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = <4>
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = 
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = 
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = <1>
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = <#!>
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = 
> 2012-04-19 12:01:46 [984] [0] DEBUG:   dumping group (sendsms-user):
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = 
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = 
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = <4>
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = 
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = 
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = <1>
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = <#!>
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = 
> 2012-04-19 12:01:46 [984] [0] DEBUG:   dumping group (sendsms-user):
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = <*.*.*.*>
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = 
> 2012-04-19 12:01:46 [984] [0] DEBUG:  =
> 
> 
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = <4>
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = 
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = 
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = <1>
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = <#!>
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = 
> 2012-04-19 12:01:46 [984] [0] DEBUG:   dumping group (sendsms-user):
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = 
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = 
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = <4>
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = 
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = 
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = <1>
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = <#!>
> 2012-04-19 12:01:46 [984] [0] DEBUG:  = 
> 2012-04-19 12:01:46 [984] [4] DEBUG: Thread 4
> (gw/smsbox.c:obey_request_thread) maps to pid 984.
> 2012-04-19 12:01:46 [984] [0] DEBUG: Started thread 4
> (gw/smsbox.c:obey_request_thread)
> 2012-04-19 12:01:46 [984] [0] DEBUG: Started thread 5
> (gw/smsbox.c:url_result_thread)
> 2012-04-19 12:01:46 [984] [5] DEBUG: T

Re: upgrading kannel

[Milan P. Stanic]

On Wed, 2011-11-30 at 00:05, Daniel Boira wrote:
> I have kannel 1.4.3 on my ubuntu 10.04
> What need I do to upgrade to kannel 1.5, also with sqlbox?

You can download Debian/Ubuntu packages from
https://redmine.kannel.org/projects/kannel/files

There are only packages for i386 and amd64 architectures because I don't
have time to make it for seldom used arc's.


For sqlbox I built package for amd64 only but I didn't posted it to Alex
because I don't use sqlbox so I didn't tried to install it and I don't
know if it works. It is untested.

If you are brave enough and if you willing to try sqlbox I can put it
somewhere on the net for you.

I don't know if it works, so I if you install it and it destroys your
data, hardware or whole world don't blame me.

-- 
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: Making SMPP esm_class configurable?

[Milan P. Stanic]

On Fri, 2011-09-09 at 08:40, Alan McNatty wrote:
> Thanks Alejandro,
> 
> OK can we please hear from anyone who would be unhappy if the patch was
> restricted to values 0 _to_ 3? This sounds good to me.

"0 _to_ 3" means 0, 1, 2 and 3 as possible values. Right?

> If no takers (I'll give it a week or so) I will keep integer but put
> back some constraints (and adjust the documentation) and re-submit.
> Appreciate everyone's patience it's good to get this flexible enough to
> work for everyone whilst still including some sensible limits. 
> 
> Cheers,
> Alan
> 
> On Thu, 2011-09-08 at 14:26 +0200, Alejandro Guerrieri wrote:
> > Ops, missed the point, sorry.
> > 
> > IMHO restricted to 0 and 3 should cover most cases. You could take it 
> > further and allowing 0 _to_ 3 to make it slightly more flexible as well.
> > 
> > Default should be 3 to keep it backwards-compatible.
> > 
> > Regards,
> > --
> > Alejandro Guerrieri
> > aguerri...@kannel.org
> > 
> > 
> > 
> > On Sep 8, 2011, at 2:17 PM, Alexander Malysh wrote:
> > 
> > > Hi Alex,
> > > 
> > > this is not the question whether commit or not. The question is, how 
> > > patch should looks like?
> > > a) commit as boolean
> > > b) commit as integer with restrictions -> need recompile when not 
> > > supported values (0 or 3) should be used
> > > c) commit as integer without restrictions
> > > 
> > > Thanks,
> > > Alexander Malysh
> > > 
> > > Am 08.09.2011 um 13:37 schrieb Alejandro Guerrieri:
> > > 
> > >> Having to patch and recompile Kannel a few times in the past to change 
> > >> that parameters to make it work in South America, I can only say +1 to 
> > >> it :)
> > >> 
> > >> Regards,
> > >> --
> > >> Alejandro Guerrieri
> > >> aguerri...@kannel.org
> > >> 
> > >> 
> > >> 
> > >> On Sep 8, 2011, at 12:29 PM, Alexander Malysh wrote:
> > >> 
> > >>> Hi Alan,
> > >>> 
> > >>> thanks for the patch but I'm waiting for more comments in this topic.
> > >>> If no comments coming, I will commit your patch next week.
> > >>> 
> > >>> Thanks,
> > >>> Alexander Malysh
> > >>> 
> > >>> Am 07.09.2011 um 02:14 schrieb Alan McNatty:
> > >>> 
> >  Hi Alex,
> >  
> >  Based on option a) please find the attached patch. I understand reasons
> >  for locking it down but it is clear to me that users want more control
> >  over this setting (beyond what we may think is sensible). Userguide
> >  patch hopefully spells out a sufficient warning.
> >  
> >  Cheers,
> >  Alan
> >  
> >  On Thu, 2011-08-18 at 18:57 +0200, Alexander Malysh wrote:
> > > Hi,
> > > 
> > > 
> > > I don't see this as issue. The user ether let it default or try to
> > > change in agreement with SMSC operator. If user will try some random
> > > values
> > > then operator will just shutdown his account. If you ask me, I don't
> > > see any need to allow changing default esm-class. But if we see buggy
> > > SMSCs
> > > that don't accept STORE & FORWARD mode then I don't know what to
> > > expect here. Maybe some drunk developer implement SMS as datagram
> > > mode,
> > > who knows :-)
> > > 
> > > 
> > > We have 2 options:
> > > a) allow user to set any values and write in the docs that this may be
> > > dangerous
> > > b) we restrict user to only have two options 0 (default mode) and 3
> > > (store & forward), then boolean value should be enough
> > > 
> > > 
> > > Alex
> > > 
> > > 
> > > Am 18.08.2011 um 12:33 schrieb Nikos Balkanas:
> > > 
> > >> Hi Alex,
> > >> 
> > >> 
> > >> 
> > >> I don't agree that this should be left open to the user. A few may
> > >> know what to do with the spec. However, a lot will play around with
> > >> the values until they get them working. Consider that a user sets
> > >> this to DATAGRAM, and kannel generates a store and forward pdu with
> > >> DATAGRAM esm_class. It doesn't hurt kannel, but what about the SMSc
> > >> that receives it? It could possibly generate a core dump if the
> > >> implementation is widely different, resulting in loss of service. Do
> > >> you really want to leave that open?
> > >> 
> > >> 
> > >> BR,
> > >> Nikos
> > >> 
> > >> On Thu, Aug 18, 2011 at 11:31 AM, Alexander Malysh
> > >>  wrote:
> > >> Hi Alan,
> > >> 
> > >> sorry to write my response late (I was on vacation), but I
> > >> don't think we need some restriction on configured
> > >> esm-class.
> > >> If we allow to change esm-class in the config, IMHO there is
> > >> no need to restrict it's value, because
> > >> the user know what he does.
> > >> 
> > >> For cannel it's equal, which value to set as esm-class
> > >> because kannel doesn't interpreting it.
> > >> 
> > >> Thanks,
> > >> Alex
> > >> 
> > >> Am 15.08.2011 um 09:35 schrieb Alan McNatty:
> > >> 
> > >>> Thanks Nikos,
> > >>

Re: Kannel 1.5.0 Debian packages

[Milan P. Stanic]

Hi,

On Wed, 2011-03-23 at 18:23, adolfo maltez wrote:
> The official mantainer for kannel package in debian are:
> 
> Paul Dwerryhouse  -> p...@dwerryhouse.com.au

I know. Last year I tried to contact him by mail two times to convince
him to put new (1.5.0) version in the Debian but he didn't answer to me.

> Jonas Smedegaard  -> d...@jones.dk

Yes, I know. I talked with him on debian-devel mailing list.

You can see my post here:

http://lists.debian.org/debian-devel/2010/01/msg00329.html

and full thread is here:

http://www.linux-archive.org/debian-development/310690-paul-dwerryhouse-mia.html
 
> http://packages.debian.org/wheezy/kannel

It is old 1.4.3 version, as you can see there.

> 2011/3/21 Milan P. Stanic 
> > I have noticed on us...@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.

Re: Kannel 1.5.0 Debian packages

[Milan P. Stanic]

Hi,

[ Sorry for X-post ]

On Thu, 2011-03-24 at 10:26, Alan McNatty wrote:
> Hi Alex,
> 
> Thanks for rolling us a new deb.
> 
> Thanks also for building with Postgres support - that will save me
> rolling my own :)
> 
> Just a couple of questions:
> 
> 1) I notice we have the usual binaries ... but I thought there was talk
> of run_kannel_box being deprecated since we have --parachute --daemonize
> capability. What are people doing these days by default - see attached
> init.d script for example. 

I built it to be as close as possible to official Debian package because
I don't want to 'surprise' users/admins during upgrade from stable.

> 2) (this is likely a longer term / roadmap question) Any chance sqlbox
> (and possibly others, e.g smppbox) could be included as a binary as
> well? 

sqlbox (0.7.2 version) is shipped with Debian stable. I have made sqlbox
deb from SVN package just for test but didn't posted it because I don't
know how it works because I never tried to use or play with it.

> It is sounded like more and more folk are using these as standard and it
> would be advantageous to the project to have them included in standard
> deb. 

I built Opensmppbox deb packages few months age for me to play with it
but didn't posted it to Alex because I'm not sure how SVN version is
good to put on Kannel site for download.

> I realise they are not in the standard build so possibly this is a
> question more around when the source / build trees might be merged (i.e
> --enable-sqlbox, etc)? So likely some work involved here - and best of
> all likely involves autoconf, etc compiler magic that troubles many of
> us.
> 
> Cheers,
> Alan
> 
> p.s sorry for the cross-post .. just reply-all'ing
> 
> On Wed, 2011-03-23 at 12:20 +0100, Alexander Malysh wrote:
> > 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=

Re: Kannel 1.5.0 Debian packages

[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 us...@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: Kannel 1.5.0 Debian packages

[Milan P. Stanic]

Hi Alex and Nikos,

On Tue, 2011-03-22 at 15:21, Alexander Malysh wrote:
> Hi Nikos,
> 
> as far as I know, you only need to install client libraries and not the whole 
> database and I don't see this as a big issue.
> I hope we will switch later to dlopen...

You are right. Only client libraries (not the database) must be
installed to satisfy dependencies.
 
> Thanks,
> Alexander Malysh
> 
> Am 22.03.2011 um 15:14 schrieb Nikos Balkanas:
> 
> > Hi,
> > 
> > There is an issue with the current db compilation:
> > 
> > - Sqlite3, Postgresql and MySQL
> > 
> > That means for the binary to run, you need to install all 3 dbs. 
> > Additionaly, since SQLbox tries to be cute about it, it creates its own 
> > databases and tables and picks automatically the first one enabled, ie 
> > Sqlite3, if i am not mistaken, or the first that it checks for, i.e. Mysql.
> > Granted this is an issue to be fixed in sqlbox, but regardless i would 
> > strongly encourage different builds, each one with a single, at most, DB.
> > 
> > Already uploaded Debian packages may not be any better, but it would be 
> > nice these to be better built.
> > 
> > BR,
> > Nikos
> > - Original Message - From: "Alexander Malysh" 
> > To: "Milan P. Stanic" 
> > Cc: 
> > Sent: Tuesday, March 22, 2011 3:37 PM
> > Subject: Re: Kannel 1.5.0 Debian packages
> > 
> > 
> > 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.
> > 
> > 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.
> >&g

Re: Kannel 1.5.0 Debian packages

[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 us...@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.

Kannel 1.5.0 Debian packages

[Milan P. Stanic]

Hi all,

I have noticed on us...@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.

Re: Submitting a patch to Kannel: best practices?

[Milan P. Stanic]

On Tue, 2010-12-21 at 12:28, Alexander Malysh wrote:
> Hi,
> 
> I agree with Alejandro on this.

+1, if it counts.
 
> 
> Am 18.12.2010 um 15:02 schrieb Alejandro Guerrieri:
> 
> > An approach similar to the one we use with the smsc-admin-id would work 
> > perfectly.
> > 
> > smsbox-id, for routing.
> > smsbox-admin-id for sending commands.
> > 
> >> A distributed management is always better than a centralized one as 
> >> complexity scales up, and doesn't limit you to anything in simpler 
> >> scenarios.
> > 
> > I disagree with that, as most of the industry does. Clusters are managed 
> > from a central place, not from each box alone (and I have my share of 
> > experience with clusters to back my point). Might work for 2-3 boxes, but 
> > try to manage 10 instances by hitting 10 different urls on 10 different 
> > servers. Scale that to 100, 1000, 1...
> > 
> > Regards,
> > --
> > Alejandro Guerrieri
> > aguerri...@kannel.org
> > 
> > 
> > 
> > On 18/12/2010, at 14:48, Nikos Balkanas wrote:
> > 
> >> I don't think that wholistic centralized management is an acceptable 
> >> option. Even with centralized management smsbox-id will be required. There 
> >> are several features that are only applicable to the particular instance 
> >> you need them. For example, live reconfiguration of services or sendsms 
> >> accounts to a particular smsbox. It is not available yet, but there is no 
> >> benefit in excluding it from a future version. As far as the other smsbox 
> >> types go (sqlbox, smppbox), they should be allowed to have their own sets 
> >> of live parameters, completely different than standard smsbox, according 
> >> to their needs without trapping them to an "smsbox format". These "extra 
> >> features" or lack thereof cannot be distinguished by smsbox-id alone.
> >> 
> >> A distributed management is always better than a centralized one as 
> >> complexity scales up, and doesn't limit you to anything in simpler 
> >> scenarios.
> >> 
> >> BR,
> >> Nikos
> >> 
> >> On Fri, Dec 17, 2010 at 8:50 PM, Alejandro Guerrieri 
> >>  wrote:
> >> Well, it's a tradeoff, as usual.
> >> 
> >> If you get a complex cluster of services, usually you either manage them 
> >> altogether (and lose granularity), or manage them individually (and each 
> >> time you need to change something on all of them you need to do it X 
> >> times).
> >> 
> >> Now, a good compromise would be to be able to optionally target a specific 
> >> instance by passing the smsbox-id. If you don't pass it, the command is 
> >> delivered to all the connected smsboxes, but if you pass it the command is 
> >> only passed to that specific smsbox instance.
> >> 
> >> Regards,
> >> --
> >> Alejandro Guerrieri
> >> aguerri...@kannel.org
> >> 
> >> On 17/12/2010, at 19:44, Nikos Balkanas wrote:
> >> 
> >> > Maybe, but it doesn't scale well. Consider that you may have 2-3 
> >> > smsboxes, an sqlbox and an smppbox (all connected as smsboxes to bb). 
> >> > Next you might want to be able to change dynamically log levels to each 
> >> > one, or dynamically manage sendsms accounts. You will end up with a bb 
> >> > admin page a mile long. Besides, sqlbox has different admin requirements 
> >> > than smppbox or smsbox and bb cannot tell them apart.
> >> >
> >> > BR,
> >> > Nikos
> >> > - Original Message - From: Alexander Malysh
> >> > To: Nikos Balkanas
> >> > Cc: David McCann ; devel@kannel.org
> >> > Sent: Friday, December 17, 2010 5:04 PM
> >> > Subject: Re: Submitting a patch to Kannel: best practices?
> >> >
> >> >
> >> > Hi,
> >> >
> >> >
> >> > it would be better to let bearerbox tell smsbox to reload lists. admin 
> >> > message already exists for communication
> >> > between bearerbox and smsbox (see restart command as example).
> >> >
> >> >
> >> > Then you don't need extra admin interface for smsbox.
> >> >
> >> >
> >> > Thanks,
> >> > Alexander Malysh
> >> >
> >> >
> >> > Am 17.12.2010 um 14:49 schrieb Nikos Balkanas:
> >> >
> >> >
> >> > Hi David,
> >> >
> >> >
> >> >
> >> > Yes. bb has its own black/white lists for incoming MO traffic, similar 
> >> > to smsbox's MT. These can be reloaded on the fly through its http admin 
> >> > interface. Another very useful feature is that it allows you to change 
> >> > log-levels on the fly. Very useful for debugging.
> >> >
> >> >
> >> > Check gw/bb_http.c: httpd_commands for sources.
> >> >
> >> >
> >> > I am not talking about bearerbox telling smsbox to reload its lists. I 
> >> > am talking for a separate http admin for smsbox, like the one in bb. 
> >> > Otherwise you would have major restructuring to get it through the admin 
> >> > *Msg, and it is not worth it.
> >> >
> >> >
> >> > BR,
> >> > Nikos
> >> >
> >> >
> >> > On Fri, Dec 17, 2010 at 1:07 PM, David McCann  
> >> > wrote:
> >> >
> >> > Hi Nikos--
> >> >
> >> >
> >> > Thank you for the promt reply!  I completely agree that this makes more 
> >> > sense as a bearerbox, admin command.  I initially added it as such, but 
> >> > the

Re: Patch: gw/smsc/smsc_smpp.c (Re: syncronize kannel with smsc)

[Milan P. Stanic]

[ how this tread lost mailing list headers? ]

On Tue, 2010-12-14 at 12:27, Alexander Malysh wrote:
> Hi,
> 
> it's a condition for every time based parameter that server synchronized to 
> NTP.
> If this not a case it's not our bad.
> 
> I don't know reason for switching to absolute time anymore.
> 
> As to the bug: just imagine, you send message with validity of 1min, kannel 
> try to deliver to SMSC but SMSC is not reachable for 2 min.
> Then SMSC is reachable again and kannel submits message to SMSC with validity 
> of 1min BUT validity is already expired because we
> waited for 2 mins for SMSC.

I agree. As I wrote in one of previous post, absolute time is default
for SMPP. We don't know do all SMSC software implementations accept
relative times but for now we know that almost all accept absolute.
To find what is the status with this issue for all SMPP servers could
be tedious and error prone task.
 
> Thanks,
> Alexander Malysh
> 
> Am 13.12.2010 um 22:19 schrieb Nikos Balkanas:
> 
> > Hi,
> > 
> > I was not aware that you were in relative time before.
> > 
> > The only reason for switching is that it offers greater accuracy than 
> > absolute time. There is no guarantee that SMScs are correctly synchronized 
> > to NTP. Some users seem to objection to this. (or the UG entry). You 
> > obviously had your reasons for switching to absolute time. Could you list 
> > them or send me an email reference?
> > 
> > In kannel, in SMPP, the validity is correctly converted to calendar date 
> > before sending out. There is no bug, and the resolution in configuration is 
> > perefectly acceptable (seconds are an overkill).
> > 
> > BR,
> > Nikos
> > 
> > - Original Message - From: "Alexander Malysh" 
> > To: "Nikos Balkanas" 
> > Cc: "Milan P. Stanic" ; "ishagh ouldbah" 
> > ; 
> > Sent: Monday, December 13, 2010 7:29 PM
> > Subject: Re: Patch: gw/smsc/smsc_smpp.c (Re: syncronize kannel with smsc)
> > 
> > 
> > Hi,
> > 
> > I don't see why we have to switch to relative time again. Only bug in 
> > kannel is, that validity is in minutes and not
> > absolute time. The same bug apply to deferred.
> > 
> > Thanks,
> > Alexander Malysh
> > 
> > Am 27.11.2010 um 09:09 schrieb Nikos Balkanas:
> > 
> >> I stand corrected. bb sends in, at least in SMPP, absolute time as GMT + 
> >> validity * 60 for validity and scheduled delivery time. Not very safe or 
> >> good. Needs the server to be synchronized with SMSc, which would probably 
> >> mean both have to be ntp synchronized.
> >> 
> >> This is a defect of the SMPP spec. It defines the format of relative time 
> >> in absolute terms, instead of seconds, making it difficult to calculate 
> >> and reconstruct.
> >> 
> >> The proposed patch makes smpp work with relative time. Please test, I do 
> >> not have access to an SMSc. Let me know how it goes. I hope that all SMScs 
> >> support it. It is more accurate than absolute time, since it doesn't 
> >> require synchronization between smsc and bearerbox.
> >> 
> >> Please vote.
> >> 
> >> BR,
> >> Nikos
> >> - Original Message - From: "Milan P. Stanic" 
> >> To: 
> >> Sent: Monday, November 22, 2010 4:25 PM
> >> Subject: Re: syncronize kannel with smsc
> >> 
> >> 
> >>> On Mon, 2010-11-22 at 05:31, ishagh ouldbah wrote:
> >>>> are you sure?
> >>> 
> >>> According to SMPP version 3.4 time can be absolute or relative. Absolute
> >>> time is default.
> >>> How it is implemented in particular software is another question. I
> >>> think that the kannel uses absolute time, at least for SMPP.
> >>> 
> >>> Here is comment from gw/smsc/smsc_smpp.c
> >>> -
> >>> /*
> >>>   * check for validity and defered settings
> >>>   * were message value has higher priiority then smsc config group
> >>>   * value
> >>>   * Note: we always send in UTC and just define "Time Difference" as
> >>>   * 00 and
> >>>   *   direction '+'.
> >>>   */
> >>> 
> >>> --
> >>> 
> >>>> 
> >>>> From: Nikos Balkanas 
> >>>> To

Re: [PATCH] Logging to syslog

[Milan P. Stanic]

On Tue, 2010-11-30 at 14:58, Stipe Tolj wrote:
> Am 30.11.2010 14:45, schrieb Alejandro Guerrieri:
> > That's extremely unflexible imho. If you want to get kannel to log alone 
> > without being cluttered with other daemon's logs, you're out of luck.
> > 
> > In our case, we'd like to use it for remote logging, so we'd use one of the 
> > "user" facilities to get kannel and _only_ kannel on it, directed to 
> > kannel-only log files.
> > 
> > I don't see the problem on allowing the extra flexibility. It's definitely 
> > useful for our scenario at least.
> 
> yep, agree... we keep the default as Alexander suggest as 'LOG_DAEMON' 
> facility,
> but provide the capabilities to extend what we want. Right?

Right, IMHO.

Most modern syslog servers have options to match program name (even
regex) and dispatch log messages according to admin defined rules.

-- 
Kind regards,  Milan
--
Arvanta, IT Securityhttp://www.arvanta.net
Please do not send me e-mail containing HTML code.

Re: SMPP BOX

[Milan P. Stanic]

On Wed, 2010-09-22 at 15:43, Nikos Balkanas wrote:
> (not x-posting)

[ Sorry, I also don't like X-posts but just wanted to move thread to
  devel ]

> Just a note. I suspect that Debian 1.4.3 may be no good. At least
> sqlbox was compiled with 3 DB libraries, so users had to install all
> DB libraries for the rpm - impractical. Also since sqlbox is a bit
> intelligent about its DB and building its own tables, it was picking
> the first one defined, therefore it would always pick mysql no
> matter what.

Yes. Kannel in Debian testing/unstable is linked with sqlite0, sqlite3,
postgresql and mysql. So is the kannel-sqlbox package.

Dependency hell, IMHO.

Well, I just offered to upload newer version for kannel users who wants
to use SVN version (and next stable 'real soon now') but don't like/know
how to build it from sources.
And it would be really nice to update kannel's site with current data
and links.

> Maybe kannel has the same fate. But i was not referring to Debian
> for submission. I was referring to the kannel site, where available
> rpms are ~10 yrs old.

Yes, Debian packages on the kannel site is really outdated.
http://www.litux.org in unreachable.

> BR,
> Nikos
> - Original Message - From: "Milan P. Stanic"
> 
> To: 
> Cc: 
> Sent: Wednesday, September 22, 2010 2:04 PM
> Subject: Re: SMPP BOX
> 
> 
> [ Cc-ing to devel so Alex can read ]
> 
> On Wed, 2010-09-22 at 13:11, Nikos Balkanas wrote:
> >You need to be an administrator to upload content. The way I would
> >do it, is to mark it as "Contribution: ..." in Subject and submit to
> >Alex M, cc the list. He will upload it for you. If it is too large
> >for email, talk to Alex first.
> 
> OK. Tnx. I will do that.
> 
> >PS: Usually rpms are built out of stable realeases (ie 1.4.3) not
> >svn. Since a lot of additions have hapenned since, you might want to
> >wait a bit for next release, 1.4.4, I believe it is very close due.
> 
> Stable release (1.4.3) is already in Debian testing/unstable (and
> Ubuntu, I think).
> Debian is reluctant to accept development versions of software so I
> usually build Kannel (and other important packages) from source.
> 
> And because current Debian testing in "frozen" state I think that the
> new stable release (as Alex announced on devel list) have a little
> chance to go to next Debian stable. I know that is not best situation
> because I know that the development version of Kannel is stable and
> deserves to be in the stable distro's (be it Debian or other).
> 
> Long story short, I would like to help people who do not have experience
> to build Kannel (and opensmppbox) from sources, to have development (and
> real soon now, stable) version "out of the box", because I did it
> already for my own use.
> 
> >BR,
> >Nikos
> >- Original Message - From: "Milan P. Stanic"
> >
> >To: 
> >Sent: Wednesday, September 22, 2010 12:15 PM
> >Subject: Re: SMPP BOX
> >
> >
> >On Wed, 2010-09-22 at 12:08, Nikos Balkanas wrote:
> >>There is a special area in the downloads section of the site that
> >>includes rpms. Why don't you contribute it there?
> >
> >Nice idea. I can build postgresql and mysql versions to.
> >
> >Though I don't know how to upload it there. Must I have account or
> >anonymous upload is allowed?
> >
> >>BR,
> >>Nikos
> >>- Original Message - From: "Milan P. Stanic"
> >>
> >>To: 
> >>Sent: Wednesday, September 22, 2010 11:49 AM
> >>Subject: Re: SMPP BOX
> >>
> >>
> >>On Wed, 2010-09-22 at 00:44, dafodil wrote:
> >>>I guess i need these steps to install smpp box
> >>>
> >>>create a directory gateway under path /usr/local then run command
> >>>svn co https://svn.kannel.org/gateway/trunk
> >>>
> >>>Create a directory smppbox  under path /usr/local/gateway then
> >>run >command
> >>>svn co https://svn.kannel.org/smppbox/trunk
> >>>
> >>>then go to directory /usr/local/gateway/trunk and run these commands
> >>> ./configure
> >>>  make
> >>>  make install
> >>>
> >>>Same command run under /usr/local/gateway/smppbox/trunk
> >>> ./configure
> >>>  make
> >>>  make install
> >>>
> >>>But i have got kannel installed(stable vesion 1.4.3).so what
> >should i >>do?
> >>>remove existing and install new ones.(if i need to remove than how?)
> >>>or just re

Re: SMPP BOX

[Milan P. Stanic]

[ Cc-ing to devel so Alex can read ]

On Wed, 2010-09-22 at 13:11, Nikos Balkanas wrote:
> You need to be an administrator to upload content. The way I would
> do it, is to mark it as "Contribution: ..." in Subject and submit to
> Alex M, cc the list. He will upload it for you. If it is too large
> for email, talk to Alex first.
 
OK. Tnx. I will do that.

> PS: Usually rpms are built out of stable realeases (ie 1.4.3) not
> svn. Since a lot of additions have hapenned since, you might want to
> wait a bit for next release, 1.4.4, I believe it is very close due.

Stable release (1.4.3) is already in Debian testing/unstable (and
Ubuntu, I think).
Debian is reluctant to accept development versions of software so I
usually build Kannel (and other important packages) from source.

And because current Debian testing in "frozen" state I think that the
new stable release (as Alex announced on devel list) have a little
chance to go to next Debian stable. I know that is not best situation
because I know that the development version of Kannel is stable and
deserves to be in the stable distro's (be it Debian or other).

Long story short, I would like to help people who do not have experience
to build Kannel (and opensmppbox) from sources, to have development (and
real soon now, stable) version "out of the box", because I did it
already for my own use.

> BR,
> Nikos
> - Original Message - From: "Milan P. Stanic"
> 
> To: 
> Sent: Wednesday, September 22, 2010 12:15 PM
> Subject: Re: SMPP BOX
> 
> 
> On Wed, 2010-09-22 at 12:08, Nikos Balkanas wrote:
> >There is a special area in the downloads section of the site that
> >includes rpms. Why don't you contribute it there?
> 
> Nice idea. I can build postgresql and mysql versions to.
> 
> Though I don't know how to upload it there. Must I have account or
> anonymous upload is allowed?
> 
> >BR,
> >Nikos
> >- Original Message - From: "Milan P. Stanic"
> >
> >To: 
> >Sent: Wednesday, September 22, 2010 11:49 AM
> >Subject: Re: SMPP BOX
> >
> >
> >On Wed, 2010-09-22 at 00:44, dafodil wrote:
> >>I guess i need these steps to install smpp box
> >>
> >>create a directory gateway under path /usr/local then run command
> >>svn co https://svn.kannel.org/gateway/trunk
> >>
> >>Create a directory smppbox  under path /usr/local/gateway then
> >run >command
> >>svn co https://svn.kannel.org/smppbox/trunk
> >>
> >>then go to directory /usr/local/gateway/trunk and run these commands
> >> ./configure
> >>  make
> >>  make install
> >>
> >>Same command run under /usr/local/gateway/smppbox/trunk
> >> ./configure
> >>  make
> >>  make install
> >>
> >>But i have got kannel installed(stable vesion 1.4.3).so what should i do?
> >>remove existing and install new ones.(if i need to remove than how?)
> >>or just reinstalling the svn source should go fine.(in that case
> >do i >need
> >>any additional steps apart from what mentioned above)
> >
> >I built Kannel SVN version a week ago for Debian testing/unstable (with
> >sqlite3 support only) for i386 and amd64 architectures. If someone wants
> >to host them somewhere for users who do not have enough experience with
> >building software from sources I can upload all the packages (binary,
> >development, extra and documentation).
> >
> >It works in production on the squeeze (testing) Debian distribution
> >without any problem. I presume it should work on current stable
> >and testing Ubuntu.
> >
> >I also debianized opensmmpbox and built it for amd64 architecture (but
> >I could build i386 version because I have development chroots all
> >around) so it could be useful for people with less experience.
> >
> >If someone have resources (and good will) to host these packages drop
> >me a note, please.
> >
> >>Kiran Reddy-3 wrote:
> >>>
> >>>   Hi,
> >>>
> >>> https://svn.kannel.org/gateway/trunk
> >>>
> >>>
> >>> On 9/22/2010 12:54, dafodil wrote:
> >>>> Hi List,
> >>>> > From the document i get following:
> >>>> -
> >>>> Latest Kannel must be installed (>1.4.3 svn version), including
> >>>> development
> >>>> headers and libraries.
> >>>> Kannel’s gwlib is needed for compilation. Additionally
> >a >>> working
> >>>> (running)
> >>>> Bearerbox is needed to 

Re: [PATCH] fix bug #529 (sms-resend-* ignored for concatenated messages)

[Milan P. Stanic]

On Wed, 2010-09-15 at 10:52, Alejandro Guerrieri wrote:
> Send it compressed, Kannel's mail server sends text attachments as part of 
> the body.

Maybe your mail client does not interpret it properly because I have got
patch as attachment.

-- 
Kind regards,  Milan
--
Arvanta, IT Securityhttp://www.arvanta.net
Please do not send me e-mail containing HTML code.

Re: wtls branch merged

[Milan P. Stanic]

On Mon, 2010-09-13 at 07:44, Nikos Balkanas wrote:
> Actually nothing changes from the day before. wtls is not enabled by
> default. This submission just fixes a broken feature, doesn't
> provide a new one. The same way that providers built packages before
> (without wtls) the same way they will continue to do. They simply
> have one more option: wtls that works. More options never hurt
> anyone.

Yes. You are right. This issue is old one as can be verified on the
mail-archive from year 2002:
http://www.mail-archive.com/de...@kannel.3glab.org/msg05446.html 

> Lastly I stand by my original assessment. We are fully covered by
> openssl's license. RC5 is not implemented in wtls code, but is part
> of the openssl source. There used to be strict export restrictions,
> till the Reagan years, but they have been relaxed since then (1990).
> wtls is not restricted. Users may be restricted to download openssl
> alltogether, but this is not our concern, and in that case they can
> always configure kannel without encryption (SSL or wtls).

Here is quote from the file /usr/share/doc/openssl/README.Debian (Debian
distro, of course) regarding issue:

PATENT ISSUES
-

Some algorithms used in the library are covered by patents.  As
a result, the following algorithms in libcrypto have been disabled:
- RC5
- MDC2
- IDEA

Also see the patents section in the README file.


README which comes with openssl says something similar.

PATENTS
 ---

 Various companies hold various patents for various algorithms in various
 locations around the world. _YOU_ are responsible for ensuring that your use
 of any algorithms is legal by checking if there are any patents in your
 country.  The file contains some of the patents that we know about or are
 rumored to exist. This is not a definitive list.

 RSA Security holds software patents on the RC5 algorithm.  If you
 intend to use this cipher, you must contact RSA Security for
 licensing conditions. Their web page is http://www.rsasecurity.com/.

 RC4 is a trademark of RSA Security, so use of this label should perhaps
 only be used with RSA Security's permission.

 The IDEA algorithm is patented by Ascom in Austria, France, Germany, Italy,
 Japan, the Netherlands, Spain, Sweden, Switzerland, UK and the USA. They
 should be contacted if that algorithm is to be used; their web page is
 http://www.ascom.ch/.

 NTT and Mitsubishi have patents and pending patents on the Camellia
 algorithm, but allow use at no charge without requiring an explicit
 licensing agreement: http://info.isl.ntt.co.jp/crypt/eng/info/chiteki.html


So, I believe that the legal teams of various free operating system
distributors have considered all issues about that and decided that is
not safe to enable patented algorithms despite the fact that the
implementation in openssl is licensed for free.

After all, Kannel as it is now, is safe because distributors will not
enable WTLS (I presume) and users who need WTLS have to compile openssl
and kannel from the source, what is good practice anyway (but we can
expect a lot of questions from novices in the lists).

Maybe something about that should go in the FAQ.

I don't want to tell that the Kannel should be changed. It is perfectly
fine in the current state in regard with RC5 and WTLS, IMHO.

> Quoting from netsnmp
> (http://www.net-snmp.org/wiki/index.php/Crypto_Export_Restrictions):
> 
> "Our cryptography software portions (AES and DES) actually come from
> OpenSSL and are not implemented internally. Additionally, back when
> export restrictions were relaxed for open source software, all that
> is required for an open source package thats provides releases on a
> web site is to send proper notification to the US export office
> (which we did), but the export office does not respond to such
> queries (they only log it).
> 
> It's up to manufactures of devices and software that intend to sell
> their devices over-seas to go through proper paperwork for the
> device that includes open source software. IE, nothing we could give
> you would satisfy your own requirements. We strongly suggest you
> consult with an export control lawyer as this community is not a
> legal service that you can count on."
> 
> This apparently is not specific to rc5, but includes all linking to
> openssl libraries, including kannel's https implementation.

Not realy. In https RC5 is not "prefered" encryption algorithm like in
WTLS. 

> Hope this clears up things,
> Nikos
> 
> - Original Message - From: "Milan P. Stanic"

Re: wtls branch merged

[Milan P. Stanic]

To reply myself:

On Sun, 2010-09-12 at 19:36, Milan P. Stanic wrote:
> On Sun, 2010-09-12 at 20:13, Nikos Balkanas wrote:
> > I don't believe so. The openssl RC5 is licensed under the openssl
> > license (similar to kannel's).
> > 
> > http://www.openssl.org/source/license.html
> 
> Licence is for software implementation and it is free but the RC5
> algorithm is patented, AFAIK. I'm not a lawyer and I don't all details
> but I think that the RC5 cannot be used in USA (and possible other
> countries) without licence from the patent holder (in that case RSA
> Data Security).
> 
> A quick look at WTLS specification shows that the RC5 isn't mandatory
> but optional.

Just found this "Press Release"

http://www.rsa.com/press_release.aspx?id=172

which states that RC5

algorithm that is specified as "should be supported by all WTLS clients
and servers" by the WAP Forum for WTLS environments.


So, I was wrong. But the issue remains. I suspect that any distributor
will have Kannel package with WTLS enabled in their repositories.
 
> > Yes it is necessary, as mentioned in a previous mail. Incorrectly I
> > said that it is used in key generation. Actually it is one of the 3
> > cipher algorithms used for content according to the wtls spec:
> > 
> > enum bulk_algorithms {
> >NULL_bulk,
> >RC5_CBC_40,
> >RC5_CBC_56,
> >RC5_CBC,
> >DES_CBC_40,
> >DES_CBC,
> >TRIPLE_DES_CBC_EDE,
> >IDEA_CBC_40,
> >IDEA_CBC_56,
> >IDEA_CBC
> > };
> > 
> > This implementation supports the RC5 and DES algorithms. Not the IDEA.
> > 
> > Kannel already has wtls with RC5 for all these years, except that it
> > doesn't work.
> > 
> > BR,
> > Nikos
> > 
> > - Original Message - From: "Milan P. Stanic"
> > 
> > To: 
> > Sent: Sunday, September 12, 2010 7:42 PM
> > Subject: Re: wtls branch merged
> > 
> > 
> > >On Sun, 2010-09-12 at 17:35, Nikos Balkanas wrote:
> > >>But you don't need an rpm if you build from sources. You have all
> > >>the includes and sources that you need.
> > >>If you are referring about the binary kannel rpms, these are
> > >>seriously outdated. Besides rpms are for the masses, and wtls is for
> > >>the few...You should disable wtls when building for the masses.
> > >
> > >It could be problem for distributors (RH, Debian, Suse, xxxBSD and
> > >others) if they cannot distribute Kannel with WTLS enabled because RC5
> > >is patented and distributors don't want to go court.
> > >
> > >Is the RC5 mandatory for WTLS?
> > >
> > >>Nikos
> > >>.
> > >>- Original Message - From: "Rene Kluwen"
> > >>
> > >>To: "'Nikos Balkanas'" ; "'Alexander Malysh'"
> > >>
> > >>Cc: "'Kannel Devel'" 
> > >>Sent: Sunday, September 12, 2010 5:29 PM
> > >>Subject: RE: wtls branch merged
> > >>
> > >>
> > >>>Okay... suppose you can build it in one step.
> > >>>
> > >>>That still won't solve the rpm dependency.
> > >>>
> > >>>== Rene
> > >>>
> > >>>-Original Message-
> > >>>From: Nikos Balkanas [mailto:nbalka...@gmail.com]
> > >>>Sent: Sunday, 12 September, 2010 16:23
> > >>>To: Rene Kluwen; 'Alexander Malysh'
> > >>>Cc: 'Kannel Devel'
> > >>>Subject: Re: wtls branch merged
> > >>>
> > >>>Actually it is not that bad. Openssl compiles from sources in one step:
> > >>>
> > >>>config threads no-krb5 shared enable-rc5 --prefix=/usr/local/64
> > >>>
> > >>>Clean, nothing to it.
> > >>>
> > >>>BR,
> > >>>Nikos
> > >>>- Original Message - From: "Rene Kluwen"
> > >>>
> > >>>To: "'Nikos Balkanas'" ; "'Alexander Malysh'"
> > >>>
> > >>>Cc: "'Kannel Devel'" 
> > >>>Sent: Sunday, September 12, 2010 5:12 PM
> > >>>Subject: RE: wtls branch merged
> > >>>
> > >>>
> > >>>>Hmmm... too much of a bother. I wonder if anybody still uses wap
> > >>>>nowada

Re: wtls branch merged

[Milan P. Stanic]

On Sun, 2010-09-12 at 20:13, Nikos Balkanas wrote:
> I don't believe so. The openssl RC5 is licensed under the openssl
> license (similar to kannel's).
> 
> http://www.openssl.org/source/license.html

Licence is for software implementation and it is free but the RC5
algorithm is patented, AFAIK. I'm not a lawyer and I don't all details
but I think that the RC5 cannot be used in USA (and possible other
countries) without licence from the patent holder (in that case RSA
Data Security).

A quick look at WTLS specification shows that the RC5 isn't mandatory
but optional.

> Yes it is necessary, as mentioned in a previous mail. Incorrectly I
> said that it is used in key generation. Actually it is one of the 3
> cipher algorithms used for content according to the wtls spec:
> 
> enum bulk_algorithms {
>NULL_bulk,
>RC5_CBC_40,
>RC5_CBC_56,
>RC5_CBC,
>DES_CBC_40,
>DES_CBC,
>TRIPLE_DES_CBC_EDE,
>IDEA_CBC_40,
>IDEA_CBC_56,
>IDEA_CBC
> };
> 
> This implementation supports the RC5 and DES algorithms. Not the IDEA.
> 
> Kannel already has wtls with RC5 for all these years, except that it
> doesn't work.
> 
> BR,
> Nikos
> 
> - Original Message - From: "Milan P. Stanic"
> 
> To: 
> Sent: Sunday, September 12, 2010 7:42 PM
> Subject: Re: wtls branch merged
> 
> 
> >On Sun, 2010-09-12 at 17:35, Nikos Balkanas wrote:
> >>But you don't need an rpm if you build from sources. You have all
> >>the includes and sources that you need.
> >>If you are referring about the binary kannel rpms, these are
> >>seriously outdated. Besides rpms are for the masses, and wtls is for
> >>the few...You should disable wtls when building for the masses.
> >
> >It could be problem for distributors (RH, Debian, Suse, xxxBSD and
> >others) if they cannot distribute Kannel with WTLS enabled because RC5
> >is patented and distributors don't want to go court.
> >
> >Is the RC5 mandatory for WTLS?
> >
> >>Nikos
> >>.
> >>- Original Message - From: "Rene Kluwen"
> >>
> >>To: "'Nikos Balkanas'" ; "'Alexander Malysh'"
> >>
> >>Cc: "'Kannel Devel'" 
> >>Sent: Sunday, September 12, 2010 5:29 PM
> >>Subject: RE: wtls branch merged
> >>
> >>
> >>>Okay... suppose you can build it in one step.
> >>>
> >>>That still won't solve the rpm dependency.
> >>>
> >>>== Rene
> >>>
> >>>-Original Message-
> >>>From: Nikos Balkanas [mailto:nbalka...@gmail.com]
> >>>Sent: Sunday, 12 September, 2010 16:23
> >>>To: Rene Kluwen; 'Alexander Malysh'
> >>>Cc: 'Kannel Devel'
> >>>Subject: Re: wtls branch merged
> >>>
> >>>Actually it is not that bad. Openssl compiles from sources in one step:
> >>>
> >>>config threads no-krb5 shared enable-rc5 --prefix=/usr/local/64
> >>>
> >>>Clean, nothing to it.
> >>>
> >>>BR,
> >>>Nikos
> >>>- Original Message - From: "Rene Kluwen"
> >>>
> >>>To: "'Nikos Balkanas'" ; "'Alexander Malysh'"
> >>>
> >>>Cc: "'Kannel Devel'" 
> >>>Sent: Sunday, September 12, 2010 5:12 PM
> >>>Subject: RE: wtls branch merged
> >>>
> >>>
> >>>>Hmmm... too much of a bother. I wonder if anybody still uses wap
> >>>>nowadays.
> >>>>
> >>>>Maybe in combination with mbuni, wap might be convenient. But
> >>even >>then,
> >>>>people won't use wtls.
> >>>>
> >>>>@Alexander: What dependencies does the pre-compiled package need when
> >>>>using
> >>>>this 'feature'? Because otherwise nobody (at least I won't) be able to
> >>>>install it from rpm, because the CentOS packages include
> >>openssl >>without
> >>>>RC5
> >>>>support. Not sure about other distributions.
> >>>>
> >>>>== Rene
> >>>>
> >>>>-Original Message-
> >>>>From: Nikos Balkanas [mailto:nbalka...@gmail.com]
> >>>>Sent: Sunday, 12 September, 2010 15:58
> >>>>To: Rene Kluwen; 'Alexander Malysh'
&

Re: wtls branch merged

[Milan P. Stanic]

On Sun, 2010-09-12 at 17:35, Nikos Balkanas wrote:
> But you don't need an rpm if you build from sources. You have all
> the includes and sources that you need.
> If you are referring about the binary kannel rpms, these are
> seriously outdated. Besides rpms are for the masses, and wtls is for
> the few...You should disable wtls when building for the masses.

It could be problem for distributors (RH, Debian, Suse, xxxBSD and
others) if they cannot distribute Kannel with WTLS enabled because RC5
is patented and distributors don't want to go court.

Is the RC5 mandatory for WTLS?

> Nikos
> .
> - Original Message - From: "Rene Kluwen"
> 
> To: "'Nikos Balkanas'" ; "'Alexander Malysh'"
> 
> Cc: "'Kannel Devel'" 
> Sent: Sunday, September 12, 2010 5:29 PM
> Subject: RE: wtls branch merged
> 
> 
> >Okay... suppose you can build it in one step.
> >
> >That still won't solve the rpm dependency.
> >
> >== Rene
> >
> >-Original Message-
> >From: Nikos Balkanas [mailto:nbalka...@gmail.com]
> >Sent: Sunday, 12 September, 2010 16:23
> >To: Rene Kluwen; 'Alexander Malysh'
> >Cc: 'Kannel Devel'
> >Subject: Re: wtls branch merged
> >
> >Actually it is not that bad. Openssl compiles from sources in one step:
> >
> >config threads no-krb5 shared enable-rc5 --prefix=/usr/local/64
> >
> >Clean, nothing to it.
> >
> >BR,
> >Nikos
> >- Original Message - From: "Rene Kluwen"
> >
> >To: "'Nikos Balkanas'" ; "'Alexander Malysh'"
> >
> >Cc: "'Kannel Devel'" 
> >Sent: Sunday, September 12, 2010 5:12 PM
> >Subject: RE: wtls branch merged
> >
> >
> >>Hmmm... too much of a bother. I wonder if anybody still uses wap
> >>nowadays.
> >>
> >>Maybe in combination with mbuni, wap might be convenient. But even then,
> >>people won't use wtls.
> >>
> >>@Alexander: What dependencies does the pre-compiled package need when
> >>using
> >>this 'feature'? Because otherwise nobody (at least I won't) be able to
> >>install it from rpm, because the CentOS packages include openssl without
> >>RC5
> >>support. Not sure about other distributions.
> >>
> >>== Rene
> >>
> >>-Original Message-
> >>From: Nikos Balkanas [mailto:nbalka...@gmail.com]
> >>Sent: Sunday, 12 September, 2010 15:58
> >>To: Rene Kluwen; 'Alexander Malysh'
> >>Cc: 'Kannel Devel'
> >>Subject: Re: wtls branch merged
> >>
> >>Actually you get these errors because you didn't solve your rc5 issue and
> >>proceeded nevertheless.
> >>
> >>rc5 is needed for cryptography of wtls. Otherwise you won't be able to
> >>produce the keys. Either install openssl with rc5 enabled or build from
> >>sources with --enable-rc5. When you get these, your gw-config.h will set
> >>the
> >>
> >>correct directives and compile cleanly.
> >>
> >>After compilation, you will have to configure wtls group in your
> >>kannel.conf
> >>
> >>and produce a pair of self-signed RSA keys for that.
> >>
> >>BR,
> >>Nikos
> >>
> >>- Original Message - From: "Nikos Balkanas"
> >>
> >>To: "Rene Kluwen" ; "'Alexander Malysh'"
> >>
> >>Cc: "'Kannel Devel'" 
> >>Sent: Sunday, September 12, 2010 4:45 PM
> >>Subject: Re: wtls branch merged
> >>
> >>
> >>>OK. I think you solved the RC5 issue. You need headers (openssl-devel)
> >>>with rc5 enabled.
> >>>
> >>>About the rest:
> >>>
> >>>After configure --with-wtls=openssl you should end up with gw-config.h:
> >>>
> >>>/* Defined if we're using OpenSSL WTLS */
> >>>211: #define HAVE_WTLS_OPENSSL 1
> >>>
> >>>If not, enable it manually and rebuild.
> >>>
> >>>BR,
> >>>Nikos
> >>>- Original Message - From: "Rene Kluwen"
> >>>
> >>>To: "'Rene Kluwen'" ; "'Nikos Balkanas'"
> >>>; "'Alexander Malysh'" 
> >>>Cc: "'Kannel Devel'" 
> >>>Sent: Sunday, September 12, 2010 3:38 PM
> >>>Subject: RE: wtls branch merged
> >>>
> >>>
> Clearly I am missing something. After ./configure
> --with-wtls=openssl, I
> get:
> (openssl-devel is installed).
> 
> /home/system/adm_rene/svn/pam/trunk/gw/wapbox.c:235:
> undefined reference
> to
> `private_key'
> /home/system/adm_rene/svn/pam/trunk/gw/wapbox.c:236:
> undefined reference
> to
> `private_key'
> /home/system/adm_rene/svn/pam/trunk/gw/wapbox.c:219:
> undefined reference
> to
> `x509_cert'
> /home/system/adm_rene/svn/pam/trunk/gw/wapbox.c:220:
> undefined reference
> to
> `x509_cert'
> libwap.a(wtls.o): In function `clientHello':
> /home/system/adm_rene/svn/pam/trunk/wap/wtls.c:453: undefined reference
> to
> `wtls_choose_ciphersuite'
> /home/system/adm_rene/svn/pam/trunk/wap/wtls.c:472: undefined reference
> to
> `wtls_choose_clientkeyid'
> /home/system/adm_rene/svn/pam/trunk/wap/wtls.c:484: undefined reference
> to
> `wtls_choose_snmode'
> libwap.a(wtls.o): In function `wtls_event_handle':
> /home/system/adm_rene/svn/pam/trunk/wap/wtls_state-decl.h:302:
> undefined
> reference to `packet_contains_changecipherspec'
> /home/system/adm_rene/svn/pam/trunk/wap/wtls_state-d

Re: Patch: gw/urltrans.c

[Milan P. Stanic]

On Mon, 2010-08-30 at 18:36, Alejandro Guerrieri wrote:
> Afaik, Kannel uses pcre for regexps.
> 
> Not sure if it's possible to pass parameters as it is now, but seems like a 
> possible course of action.

It is configure script option and is disabled by default.
And it is not mentioned in userguide.
 
> On 30/08/2010, at 18:33, Milan P. Stanic wrote:
> 
> > On Mon, 2010-08-30 at 17:33, Rene Kluwen wrote:
> >> I agree here. Regexps are by default not case sensitive, unless the 
> >> i-modifier is set.
> >> 
> >> Isn't internal option setting an option? Like they do here: 
> >> http://nl2.php.net/manual/en/regexp.reference.internal-options.php
> >> 
> >> Example: (?i:foo)
> > 
> > This example is PCRE, I think. Kannel regex is POSIX compatible.
> > 
> > -- 
> > 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: Patch: gw/urltrans.c

[Milan P. Stanic]

On Mon, 2010-08-30 at 17:33, Rene Kluwen wrote:
> I agree here. Regexps are by default not case sensitive, unless the 
> i-modifier is set.
> 
> Isn't internal option setting an option? Like they do here: 
> http://nl2.php.net/manual/en/regexp.reference.internal-options.php
> 
> Example: (?i:foo)

This example is PCRE, I think. Kannel regex is POSIX compatible.

-- 
Kind regards,  Milan
--
Arvanta, IT Securityhttp://www.arvanta.net
Please do not send me e-mail containing HTML code.

Re: Patch: gw/urltrans.c

[Milan P. Stanic]

On Mon, 2010-08-30 at 17:06, Nikos Balkanas wrote:
> Please see comments inlined.
> Nikos
> - Original Message - From: "Alexander Malysh"
> 
> To: "Nikos Balkanas" 
> Cc: 
> Sent: Monday, August 30, 2010 12:08 PM
> Subject: Re: Patch: gw/urltrans.c
> 
> 
> >>Hi,
> 
> >>why do you change explicit configuration to something implicit?
> 
> I don't understand. Please explain what is explicit and what is implicit.
> 
> >>user have to decide whether to use keyword or keyword-regex and
> >>if both given
> >>it's error and was indicated so.
> 
> Just trying to align source with documentation, by popular demand.
> 
> >>About the case sensitivity, I would like to give a user
> >>possibility to decide.
> >>The policy should be:
> >>- if keyword given make it case insensitive (just backwards
> >>compatibility)
> >>- if keyword-regex given it's case sensitive
> 
> That's confusing for anyone. How do you know what users want? It
> could blow the list off. I think everything should be treated
> equally. keyword-regex is just an extention of keyword. Rules
> applying to the first should apply to the second as well.
> 
> Any votes from the list?

keyword-regex _should_ be case sensitive without any doubt, IMHO.

If it (by chance) becomes case insensitive that will be great
confusion.
 
-- 
Kind regards,  Milan
--
Arvanta, IT Securityhttp://www.arvanta.net
Please do not send me e-mail containing HTML code.

Re: Discussion: Prepaid counting

[Milan P. Stanic]

On Sun, 2010-08-08 at 12:06, Alejandro Guerrieri wrote:
> I concur 100%, I've seen so many different approaches to billing that I think 
> it's virtually impossible to build a one-size-fits-all solution to deal with 
> it.
> 
> Even if you do, it would probably be very complex to configure and heavy on 
> resources, and anyway soon a carrier would probably come up with a new, 
> "innovative" approach that it wouldn't be able to be dealt with.
> 
> That's why I think that a plugin approach would be the way to go. That way, 
> plugins to deal with different scenarios could be developed to suit the 
> particular needs at hand.

I agree with with your opinion, if it counts :)
 
> Regards,
> --
> Alejandro Guerrieri
> aguerri...@kannel.org
> 
> 
> 
> On 08/08/2010, at 08:23, Konstantin Vayner wrote:
> 
> > There are a lot of issues that arise when dealing with prepaid
> > 
> > First of all, in many cases the balance is supposed to be per message type 
> > (eg short text sms cost X, concatenated cost Y per message, wappush cost Z 
> > per message).
> > Second, billing models often differ - in some cases we charge all messages 
> > regardless (the customer "touches" our service - pays), in other cases - we 
> > bill upon submission to target network (regardless if message was accepted 
> > for delivery or rejected), in some - only if it was accepted , and in some 
> > cases we even charge the customer when the message was successfully 
> > delivered to handset (upon dlr reception).
> > Also, in some cases a whole concatenated message is billed asif it was a 
> > single message (possibly by a different rate, possible at same).
> > 
> > And all these might vary from customer to customer (its up to marketing to 
> > decide how they charge the customers).
> > 
> > I am not sure bb needs that much extra functionality/flexibility that can 
> > be built in external application anyway
> > 
> > Regards,
> >   Konstantin
> > 
> > On Sat, Aug 7, 2010 at 11:16 PM, Juan Nin  wrote:
> > I agree with Alejandro, this is specific for your needs, and may fit
> > other people's needs too, but it's not generic enough.
> > 
> > For example, binfo may be used with some carriers, but not with
> > others. In my own experience I have never connected to a carrier where
> > I could use binfo for this purposes.
> > 
> > As Alejandro says, a plugin approach would be better, so that you can
> > use whatever you want without adding specific cases logic into kannel.
> > 
> > You could even implement it on your application side, with no need of
> > doing it directly on Kannel (of course may have it's benefits to do it
> > on Kannel side on certain cases though).
> > 
> > 
> > On Sun, Aug 1, 2010 at 3:28 PM, Alejandro Guerrieri
> >  wrote:
> > > This patch will definitely have its place for many people's requirement, 
> > > but it's not generic enough for general usage imho.
> > >
> > > Personally speaking, I don't like the idea of clogging any boxes' code 
> > > with non-generic stuff. The billing approach would work for some people, 
> > > but surely won't be flexible enough for others.
> > >
> > > I like Stipe's "plugin approach" on his (commercial) smppbox: messages 
> > > can be routed thru plugins, where you can implement all kind of stuff and 
> > > add/remove them from your message pipeline. Using that approach, all kind 
> > > of billing mechanisms could be implemented (along with many other stuff 
> > > of course).
> > >
> > > Regards,
> > > --
> > > Alejandro Guerrieri
> > > aguerri...@kannel.org
> > >
> > >
> > >
> > > On 01/08/2010, at 03:08, Rene Kluwen wrote:
> > >
> > >> Suppose I add 2 tables to sqlbox:
> > >>
> > >> mysql> describe sms_users;
> > >> +-+--+--+-+-+---+
> > >> | Field   | Type | Null | Key | Default | Extra |
> > >> +-+--+--+-+-+---+
> > >> | binfo   | varchar(100) | NO   | PRI | NULL|   |
> > >> | balance | float(10,0)  | NO   | | 0   |   |
> > >> +-+--+--+-+-+---+
> > >> 2 rows in set (0.00 sec)
> > >>
> > >> And:
> > >>
> > >> mysql> describe sms_rates;
> > >> +-+--+--+-+-+---+
> > >> | Field   | Type | Null | Key | Default | Extra |
> > >> +-+--+--+-+-+---+
> > >> | prefix  | varchar(100) | NO   | PRI | |   |
> > >> | smsc| varchar(100) | NO   | PRI | |   |
> > >> | rate| float(10,4)  | NO   | | 0.  |   |
> > >> | country | varchar(255) | YES  | | |   |
> > >> +-+--+--+-+-+---+
> > >> 4 rows in set (0.00 sec)
> > >>
> > >> And suppose I match prefix/smsc against sms_rates and draw the variable
> > >> "rate" from it.
> > >>
> > >> Next, I check the sms_users table with the binfo field (not sure if this 
> > >> is
> > >> a good idea or not) and I withdraw "rate" from "balance" if "ba

Re: Patch: test/drive_smpp.c

[Milan P. Stanic]

[ This is totally of-topic to the list. I will resist after that post
  and sorry for this one ]

On Mon, 2010-07-05 at 01:54, Konstantin Vayner wrote:
> @Milan,
> 
> Actually, this is quite normal to reply *to* specific person and cc to list.
> This is nothing new, and in fact this is default behavior of most email
> clients unless specifically forced to do otherwise (which i see your email
> client - mutt - does - but also probably forced to do so by configuration).

No, mutt (as most mail clients) have this _feature_ from the beginning.

> I *do* expect someone that addresses me in reply to put my address in the To
> field.
> I've resisted replying the previous time you brought up this point, but
> since you're on it, i thought my 2 cents might add value as well ;)

I don't agree. Any decent mailing list software and mail client can
handle mailing list posts without problem in the "right way" (tm).

-- 
Kind regards,  Milan

Re: Patch: test/drive_smpp.c

[Milan P. Stanic]

On Mon, 2010-07-05 at 00:56, Nikos Balkanas wrote:
> [You should reply to me, Cc the list, so that it is obvious from the
> headers, to whom it is addressed]

Looks like you want to change the rules for mailing list too, not only
coding style. ;)
 
> Then I gather, from your own words that style is a collective
> decision. But if you notice from the rest of kannel's code style has
> changed several times since the beginning. Maybe the time has come
> for another such change, if it benefits the community.

Changing style could be done if the maintainers agree on that.
But, even if the maintainer want to change style s/he should ask other
developers if they agree on that. Maintainers of the free/open source
software are not (usually) dictators (even if they sometimes called
"benevolent dictators").

If the developers or the community persuades maintainer to change rules
it can be done, but I suspect that one developer could do that.

> Of course noone can commit whatever he wants to the list, it is up
> to the maintainer whether to accept it or not. And it is up to the
> contributor, based on those rules, whether he will submit it or not.

> BR,
> Nikos
> - Original Message - From: "Milan P. Stanic"
> 
> To: 
> Sent: Sunday, July 04, 2010 10:47 PM
> Subject: Re: Patch: test/drive_smpp.c
> 
> 
> >[ You shouldn't post replies to me. I'm subscribed to list ]
> >
> >On Sun, 2010-07-04 at 13:22, Nikos Balkanas wrote:
> >>If styling rules are one man's decision, better be acceptable and to
> >>a degree flexible, or they will deter contributors from submitting
> >>work. Which contradicts open source philosophy.
> >
> >Styling rules are seldom one man's decision in free/open source. It is
> >usually a consensus established during initial phase of the project and
> >often copied from other successful projects.
> >If everyone is allowed to add/insert personal style/preferences that
> >leads to big mess and such code is hard to follow.
> >
> >Newcomers are expected to adopt to the established rules and style.
> >
> >I would like to see kannel in git repository and during discussion
> >about switching to new VCS I had temptation to propose that but because
> >I don't contribute code to kannel I resisted. I remember last Alex's
> >message about matter and even started to write reply but after little
> >thinking I ceased because I didn't like to disturb him with one useless
> >mail.
> >
> >>Granted  kannel is in better shape than most other software, but
> >>there is always room for improvement.
> >
> >Yes. I agree with you.
> >And, I really appreciate your contribution to kannel.
> >
> >>BR,
> >>Nikos
> >>- Original Message - From: "Milan P. Stanic"
> >>
> >>To: 
> >>Sent: Sunday, July 04, 2010 12:52 PM
> >>Subject: Re: Patch: test/drive_smpp.c
> >>
> >>
> >>>On Sun, 2010-07-04 at 00:58, Nikos Balkanas wrote:
> >>>>I am very sorry. My apologies for the missunderstanding. My
> >>>>impression is that identation means replacing tabs with spaces and
> >>>>aligning left text according to level. I see here that you are
> >>>>actually asking about source code reformatting and even for a code
> >>>>change. Some of the styling options that you ask, especially that
> >>>>"if" statement, are unreadable by several people, including me.
> >>>>Well, not exactly unreadable, but very difficult to read. And that
> >>>>is a problem in the case of the author who is called to support it.
> >>>>Who decided on this style anyway?
> >>>
> >>>In the free/open source software usually maintainers are those who set
> >>>the rules and style.
> >>>
> >>>[ And usually (as is the case in kannel) these rules and style are far
> >>> better than in commercial software ]

-- 
Kind regards,  Milan

Re: Patch: test/drive_smpp.c

[Milan P. Stanic]

[ You shouldn't post replies to me. I'm subscribed to list ]

On Sun, 2010-07-04 at 13:22, Nikos Balkanas wrote:
> If styling rules are one man's decision, better be acceptable and to
> a degree flexible, or they will deter contributors from submitting
> work. Which contradicts open source philosophy.

Styling rules are seldom one man's decision in free/open source. It is
usually a consensus established during initial phase of the project and
often copied from other successful projects.
If everyone is allowed to add/insert personal style/preferences that
leads to big mess and such code is hard to follow.

Newcomers are expected to adopt to the established rules and style.

I would like to see kannel in git repository and during discussion
about switching to new VCS I had temptation to propose that but because
I don't contribute code to kannel I resisted. I remember last Alex's
message about matter and even started to write reply but after little
thinking I ceased because I didn't like to disturb him with one useless
mail.

> Granted  kannel is in better shape than most other software, but
> there is always room for improvement.

Yes. I agree with you.
And, I really appreciate your contribution to kannel.

> BR,
> Nikos
> - Original Message - From: "Milan P. Stanic"
> 
> To: 
> Sent: Sunday, July 04, 2010 12:52 PM
> Subject: Re: Patch: test/drive_smpp.c
> 
> 
> >On Sun, 2010-07-04 at 00:58, Nikos Balkanas wrote:
> >>I am very sorry. My apologies for the missunderstanding. My
> >>impression is that identation means replacing tabs with spaces and
> >>aligning left text according to level. I see here that you are
> >>actually asking about source code reformatting and even for a code
> >>change. Some of the styling options that you ask, especially that
> >>"if" statement, are unreadable by several people, including me.
> >>Well, not exactly unreadable, but very difficult to read. And that
> >>is a problem in the case of the author who is called to support it.
> >>Who decided on this style anyway?
> >
> >In the free/open source software usually maintainers are those who set
> >the rules and style.
> >
> >[ And usually (as is the case in kannel) these rules and style are far
> > better than in commercial software ]

-- 
Kind regards,  Milan

Re: Patch: test/drive_smpp.c

[Milan P. Stanic]

On Sun, 2010-07-04 at 00:58, Nikos Balkanas wrote:
> I am very sorry. My apologies for the missunderstanding. My
> impression is that identation means replacing tabs with spaces and
> aligning left text according to level. I see here that you are
> actually asking about source code reformatting and even for a code
> change. Some of the styling options that you ask, especially that
> "if" statement, are unreadable by several people, including me.
> Well, not exactly unreadable, but very difficult to read. And that
> is a problem in the case of the author who is called to support it.
> Who decided on this style anyway?

In the free/open source software usually maintainers are those who set
the rules and style.

[ And usually (as is the case in kannel) these rules and style are far
  better than in commercial software ]

-- 
Kind regards,  Milan
--
Arvanta, http://www.arvanta.net
Please do not send me e-mail containing HTML code.

Re: Patch: smsc_smpp.c

[Milan P. Stanic]

On Fri, 2009-10-23 at 12:04, Alexander Malysh wrote:
> This is true that SMPP spec don't define DLR format but give only
> recommendation but this recommendation was adapted
> by 99% SMSC maker and is quasi standard. If someone think that he
> can ignore such fact we will ignore this SMSC maker
> and user who connecting such SMSC have to ask SMSC operator/maker
> why they ignore quasi standard.
> The more people ask the more SMSC operator/maker will think about to
> fix this issue.

I don't know how there are commercial SMPP gateways in use nowadays (I
don't know for anyone) but if there are some/many then the users are on
the mercy of SMSC makers and their software implementation.

I also think that the operators are on the mercy of the SMSC software
makers (SMSC software is closed source, I think) and because of that I
don't expect they will implement SMPP spec recommendation.

P.S.
Current implementation is not problem for me personally because I work
with one operator which adds null on the end of the string/text but I've
found simple workaround in my applications.

> Am 23.10.2009 um 11:43 schrieb Nikos Balkanas:
> 
> >Unfortunately mail archives list only first few mails. Many
> >experienced contributors, like Alejandro, Milan and Seikath, hold
> >the opinnion that this recommendation is an example, not an SMPP
> >spec, and therefore more flexible. I myself consider it more
> >strictly, as a spec.
> >
> >However, no matter how you look at it, it is an ommision in the
> >code, if the old parser considers only spaces and neglects string
> >endings. I am not talking about free text parsing here. I still
> >consider formal tags mandatory. Besides the change in code is
> >trivial and minimal.
> >
> >From the discussion, both Stanic and Seikath have branched off
> >with their own versions. This is unfortunate.
> >
> >I am attaching the last mail, which includes most previous ones.
> >Please take the time to read some of it.
> >
> >BR,
> >Nikos
> >- Original Message -
> >From: Alexander Malysh
> >To: Nikos Balkanas
> >Cc: devel@kannel.org Devel
> >Sent: Friday, October 23, 2009 12:03 PM
> >Subject: Re: Patch: smsc_smpp.c
> >
> >Hi Nikos,
> >
> >ok got it...
> >
> >We have such discussions many times already and we always got to
> >decision that kannel can't and should't
> >support things that are not standard except it easy to integrate
> >and has no impact on the code readability,
> >security etc.
> >
> >I don't think we have to patch DLR parsing in SMPP due to this
> >clear SMSC bug. This is some homegrown SMSC
> >just don't accept quasi standard. This SMSC should be fixed and
> >not kannel...
> >
> >Thanks,
> >Alexander Malysh
> >
> >PS: I think we should have this configurable and regex group
> >matching should do it...
> >
> >Am 22.10.2009 um 19:24 schrieb Nikos Balkanas:
> >
> >>Sure.
> >>
> >>http://www.mail-archive.com/us...@kannel.org/msg17659.html
> >>- Original Message -
> >>From: Alexander Malysh
> >>To: Nikos Balkanas
> >>Cc: devel@kannel.org Devel
> >>Sent: Thursday, October 22, 2009 5:58 PM
> >>Subject: Re: Patch: smsc_smpp.c
> >>
> >>can you please give me link to this discussion?
> >>
> >>Thanks,
> >>Alexander Malysh
> >>
> >>Am 22.10.2009 um 13:17 schrieb Nikos Balkanas:
> >>
> >>>Hi,
> >>>
> >>>Oh boy. You missed all the fun :-)
> >>>
> >>>Original email by Latitude Test on 13/10/2009, where DELIVERD
> >>>DLRs are misreported by kannel as failures (type 2). There was
> >>>quite a discussion about whether it was a kannel bug, or an
> >>>out of spec DLR. In the end it was a consensus that kannel
> >>>needed a patch.
> >>>
> >>>Bottom of the line: Spec is very loose at this point about DLR
> >>>fields. Kannel expects either an exact format (sscanf) or it
> >>>reverts to a more flexible old style search. Problem is that
> >>>in the search it assumes that the value of each field is
> >>>followed by space, and that is not necessarily true (if field
> >>>is last in DLR).
> >>>
> >>>Seikath also said that he has a couple of cases like that.
> >>>
> >>>BTW, I have asked Latitude to test it, because I cannot, but
> >>>he seems to get disappeared after creating all this stir :-(
> >>>
> >>>BR
> >>>Nikos
> >>>- Original Message -
> >>>From: Alexander Malysh
> >>>To: Nikos Balkanas
> >>>Cc: devel@kannel.org Devel
> >>>Sent: Thursday, October 22, 2009 11:08 AM
> >>>Subject: Re: Patch: smsc_smpp.c
> >>>
> >>>Hi Nikos,
> >>>
> >>>could you please explain why we need this patch?
> >>>
> >>>Thanks,
> >>>Alexander Malysh
> >>>
> >>>Am 19.10.2009 um 18:30 schrieb Nikos Balkanas:
> >>>
> Hi,
> 
> A trivial patch, that should be able to handle all DLRs as
> long as they keep formal tags.
> 
> Please test.
> 
> BR,
> Nikos
> >>>
> >>>
> >>
> >>
> >
> >
> 

-- 
Kind regards,  Milan
--
Arvanta, IT Securityhttp://www.arvanta.net
Please do not send me e-mail containing HTML code.

Re: Patch: SMSbox crash

[Milan P. Stanic]

On Thu, 2009-08-27 at 00:34, Donald Jackson wrote:
> Your patch looks fine but, the problem is that we have received an empty MO,
> and this will now not allow the sms-service to process it (maybe some sort
> of default process).
> 
> I'm not sure this is the behavior users would expect, I think most users
> would expect that if they received an empty SMS they would still receive it.
> 
> Obviously this is limited to some carriers who have this behavior in their
> data_sm PDU's. I think we should simply fix it in smsbox by converting a
> NULL msgdata into a octstr_create("") and that should suffice without
> causing any unnecessary issues with the lower layers.
> 
> Thoughts? Alot of writing for such a simple issue :D

If you allow me to express my opinion:
I'm not kannel developer, but from users perspective I agree with you. I
expect from kannel to deliver message to applications even if the
message is empty.
 
> 2009/8/27 Nikos Balkanas 
> 
> >  Dear Alex,
> >
> > This is a trivial patch. However, I would like to suggest something to
> > improve it:
> >
> > In thread sms_to_smsboxes it checks and if msg = NULL it drops it. I
> > added a check if msgdata is NULL to drop it as well.
> >
> > This would avoid further processing (less overhead) of the sms and simplify
> > further logic present and future, in that they wouldn't have to be concerned
> > with it. I assume that empty MO sms don't need any sms-service or further
> > processing.
> >
> > What do you think?
> >
> > PS. Compilation is clean. I don't have, though, any smsc connections to
> > test it. @Hemant: Can you please test?
> >
> > BR,
> > Nikos
> >
> > - Original Message -
> > *From:* Alexander Malysh 
> > *To:* Development mailing list 
> > *Cc:* Donald Jackson  ; Hemant 
> > Gmail; Nikos
> > Balkanas 
> > *Sent:* Wednesday, August 26, 2009 10:59 AM
> > *Subject:* Re: Patch: SMSbox crash
> >
> > Hi all,
> > ok, seems too many parts of kannel rely on the msgdata not to be NULL.
> >
> > @Donald: never use octstr_imm of you pass this to further processing.
> > octstr_imm doesn't support all functions and you don't know what the user of
> > such field will do with it.
> >
> > If this really the case that too much kannel parts rely on msgdata to be
> > not NULL then your patch is not enough. Please try attached patch
> > that will fix this issue for all available SMSC module.
> >
> > Thanks,
> > Alexander Malysh
> >
> > --
> >
> >
> >  Am 25.08.2009 um 20:24 schrieb Nikos Balkanas:
> >
> >  Hi Donald,
> >
> > I guess intercepting it upstream was my intention, too, however I think you
> > got it too far back. I was thinking more likely at the SMS router function
> > to check if payload is NULL to quietly discard the SMS and pick the next one
> > from Q, this way minimizing overhead. Plus at this stage it would apply to
> > all MO SMS, not only SMPP.
> >
> > I changed subject to patch, so that Alex picks up on it and speaks his
> > mind.
> >
> > BR,
> > Nikos
> >
> > - Original Message -
> > *From:* Donald Jackson 
> > *To:* Nikos Balkanas 
> > *Cc:* Hemant Gmail  ; de...@vm1.kannel.org
> > *Sent:* Tuesday, August 25, 2009 8:33 PM
> > *Subject:* Re: SMSbox crashed
> >
> > Hi Nikos,
> > Apologies I wasn't actually following the thread he emailed me privately :)
> >
> > The problem occurs in smsbox when it tries to find a translation for the
> > message. The different thing about these messages, is they are NULL. This is
> > because this operator is not sending the (TLV) message_payload parameter
> > with the data_sm PDU if no text is specified.
> >
> > Smsbox/find_translation does no NULL checking on msgdata before trying the
> > octstr_covert_range, which is why it fails the assertion. My patch simply
> > sets the parameter to an empty Octstr inside the data_sm code, to prevent
> > smsbox from falling over, and then still passing the upstream applications
> > an empty string, instead of '(null)'.
> >
> > Let me know your thoughts,
> >
> > Thanks,
> > Donald
> >
> > 2009/8/25 Nikos Balkanas 
> >
> >>  Thanks, Donald.
> >>
> >> I was personally holding out for Herman to try out patching, but yours is
> >> more than welcome.
> >>
> >> I have also not forgotten your store isuue. I have not been able to
> >> reproduce it with fakesmsc, so it seems to be exclusive to the at driver. I
> >> will have to add code to simulate the modem calls (don't have modem or 
> >> other
> >> smsc links - I am a wap guy) and i wouldn't like to spend a lot of money to
> >> try it out on a real connection.
> >>
> >> Meanwhile could you provide us with some relevant bb logs from the
> >> problem? I believe you can increase in real time the log detail from the
> >> http administration.
> >>
> >> BR,
> >> Nikos
> >>
> >> - Original Message -
> >> *From:* Donald Jackson 
> >> *To:* Development mailing list 
> >> *Cc:* Hemant Gmail  ; de...@vm1.kannel.org
> >> *Sent:* Tuesday, August 25, 2009 4:40 PM
> >> *Subject:* Re: SMSbox cr

Re: Kannel not load balancing after restart and messages get stuck inqueue

[Milan P. Stanic]

On Wed, 2009-06-10 at 14:32, Nikos Balkanas wrote:
> I happen to agree also. But the fact is, that this is how kannel 
> currently works. And i have to abide by that. Anyway, read my response to 
> Alvaro, it may be just a configuration issue.

I'm not sure if we are talking about same behavior of bearerbox but as
I see it, bearerbox in 1.4.3 version (and some previous) starts and
stays even if no one smsc (smsbox can't connect to SMSC) is running or in
online status.

If you talk about some specific configuration (smsc routing or load
balancing) then you might be right. I didn't tested such use cases.

Or, I misunderstood your post totally.

> - Original Message - From: "Alan McNatty" 
> To: 
> Cc: 
> Sent: Wednesday, June 10, 2009 2:23 PM
> Subject: Re: Kannel not load balancing after restart and messages get 
> stuck inqueue
>
>
>> Milan P. Stanic wrote:
>>> On Wed, 2009-06-10 at 10:02, Nikos Balkanas wrote:
>>>> I must be the one thanking you for the discussion. You see I am a wap
>>>> guy, and don't know of many of the issues that sms people face.
>>>>
>>>> The only concern is at startup. After it has bbox has started
>>>> succesfully, and therefore sms_router, started as well, it doesn't
>>>> matter. You can take all the smscs you want offline to service them.
>>>> sms_router will work with the rest of them.
>>>>
>>>> The only issue is for startup. I cannot test the scenario you describe,
>>>> because i don't have real smsc connections. However, if both connections
>>>> are active the minute kannel starts (1st case0, there should be no
>>>> problem. In the second case, the unavailable smsc should be 
>>>> commented out
>>>> the configuration.
>>>>
>>>> I guess the only question is: Under what circumstances bbox will start,
>>>> if the 2nd smsc is not responding?
>>>
>>> Bearerbox should always start. Even if there is no one smsc active.
>>> Smsc can become active later for miscellaneous reasons.
>>>
>> I agree 100% with Milan here. SMSC's are not in our control - there
>> could be many points of failure between kannel and SMSC. Firewalls,
>> VPN's etc may be unhappy and we lose connectivity .. we need kannel to
>> be stable (in operation and restart, etc) and manage the reconnect and
>> message distribution (SMPP is pretty good here).
>>
>> As Alvaro was suggesting earlier in the thread some sort of dynamic
>> redistribution of queued message (maybe like keepalived or sim.) could
>> be ideal .. but obviously some work ..
>>
>> Nikos I appreciate you have been busy doing some development. I can help
>> test some of the SMSC 'stuff' (from SMPP) perspective - it's obviously
>> in my interest here ;). As of now I haven't used a-lot of the routing
>> features so this is a bit new to me (I will try and get back into it and
>> hopefully make some suggestions).

-- 
Kind regards,  Milan

Re: Kannel not load balancing after restart and messages get stuck inqueue

[Milan P. Stanic]

On Wed, 2009-06-10 at 10:02, Nikos Balkanas wrote:
> I must be the one thanking you for the discussion. You see I am a wap 
> guy, and don't know of many of the issues that sms people face.
>
> The only concern is at startup. After it has bbox has started 
> succesfully, and therefore sms_router, started as well, it doesn't 
> matter. You can take all the smscs you want offline to service them. 
> sms_router will work with the rest of them.
>
> The only issue is for startup. I cannot test the scenario you describe,  
> because i don't have real smsc connections. However, if both connections 
> are active the minute kannel starts (1st case0, there should be no 
> problem. In the second case, the unavailable smsc should be commented out 
> the configuration.
>
> I guess the only question is: Under what circumstances bbox will start, 
> if the 2nd smsc is not responding?

Bearerbox should always start. Even if there is no one smsc active.
Smsc can become active later for miscellaneous reasons.

-- 
Kind regards,  Milan

Re: Claro http communication

[Milan P. Stanic]

On Mon, 2009-05-25 at 17:28, Juan Nin wrote:
> There are already several HTTP SMSC specific implementations on
> Kannel, the ones that Hervé mentioned are some of them.

Kannel supports SMPP, EMI, UCP, AT, several HTTP and the others
protocols. I hope that the kannel will not become to bloated if we
tried to push every variant of HTTP specific implementation into it.

> Of course you can do it directly without Kannel, but it's a good
> approach to do it via Kannel, so that you always use it as your
> gateway and not one method for some carriers and another one for
> others, It's also nice to do it via Kannel cause it already implements
> stuff like it's internal queue, etc

-- 
Kind regards,  Milan

Re: Claro http communication

[Milan P. Stanic]

On Mon, 2009-05-25 at 18:14, Hervé Nicol wrote:
> We have to send / receive SMS and DLRs over Claro (brazilian telco). We
> will communicate with them by HTTP.
   ^ 
> If we write a patch for kannel for operator-specific HTML communication
> (just like for Clickatell, Brunet, 3united.com...), is there any chance
> that it may be included in Kannel CVS?

You have to communicate with kannel over HTTP. Kannel have to
communicate with provider over HTTP. Why you could not communicate with
provider over HTTP without kannel.
What should be role of the kannel in your case?

I don't like to say that you do not have good reason for that. I'm just
curious.

> Do you have some special hints / advices on how to proceed?
> It won't be too hard for us to write this code considering the existing
> operator-specific code, but it costs nothing to ask for some advice
> before starting to work on it ;)

-- 
Kind regards,  Milan

Re: singlethreaded or multithreaded

[Milan P. Stanic]

On Wed, 2009-05-06 at 17:52, Beatrice Tamburrino wrote:
> The webserver should be part of a big software engine which my company 
> develops. we also use the apache server but for incoming traffic, we need a 
> custom build one for overviewing the requests.
> 
> anyway, its not a big deal to write a webserver, but I'm really interested on 
> how the output-requests are done?
> 
> maybe you have an idea?

I wrote custom server/application in Perl. I'm thinking to rewrite it in
C, but don't have time to do that. It's cheaper to by CPU/memory.

And, yes, kannel send requests over http interface (GET method) in
parallel, not sequentially.

-- 
Kind regards,  Milan
--
Arvanta, IT Securityhttp://www.arvanta.net
Please do not send me e-mail containing HTML code.

Re: SMS over SS7

[Milan P. Stanic]

On Fri, 2009-03-27 at 11:51, Andreas Fink wrote:
> On 26.03.2009, at 07:50, jyoti wrote:
>> If we use sms for push over ss7 E1 link.i.e directly connected to MSC,
>> instead of SMSC(SMPP),Does we will get an advantage?
>> if yes can we devlop kannel to support the above?
[...]
> This is what we have been doing since 2001. It is major work.
>
> To give you an idea: if you talk directly SS7, you are an SMSC. The  
> store and forward part of an SMSC is no magic. Its just plugging in a  
> database and some SMPP filling it. But then to send out the data, you  
> need to query the HLR and process the response to then forward the SMS  
> to the MSC or retry later if the subscriber is offline.
[...]
> So if anyone has such an access, talk to me.

If you want something to be done just forbid (your) children to do that.

-- 
Kind regards,  Milan

Re: Memory problem with kannel sms outgoing delivery report

[Milan P. Stanic]

On Wed, Nov 07, 2007 at 09:41:41AM -0200, Allison Almeida wrote:
> With my experience, i strongly suggest physical servers for kannel
> production environments.

Under UML kannel works just fine.

Best regards

Re: [STATUS] Kannel 1.4.1 stable release

[Milan P. Stanic]

On Fri, Sep 29, 2006 at 12:06:03AM +0200, Stipe Tolj wrote:
> Milan P. Stanic wrote:
> >I made packages for Debian stable (Sarge) with smpp-throttle.patch.
> 
> which patch exactly please?
> 
> Can you reference this via mail subject, date and sender?

Patch is posted to devel list by [EMAIL PROTECTED]
01 Aug 2006.

http://www.mail-archive.com/devel@kannel.org/msg06082.html

Best regards

Re: [STATUS] Kannel 1.4.1 stable release

[Milan P. Stanic]

On Mon, Sep 25, 2006 at 06:26:27PM +0200, Stipe Tolj wrote:
> The Kannel Group is pleased to announce the availability of Kannel 1.4.1 
> stable release via it's web site at URL

Good work! I wish to thank to all developers.

I made packages for Debian stable (Sarge) with smpp-throttle.patch.
They are at (if anyone need it):
http://www.rns-nis.co.yu/~mps/kannel/

No apt repository, sorry.

Best regards