Nabble - Kannel

Re: Two Basic Questions, Please?

2009-11-28T11:21:36Z

Thank you, Nikos, for the advice.

Best regards,

David

--- On Sat, 28/11/09, Nikos Balkanas <nbalkanas@...> wrote:

From: Nikos Balkanas <nbalkanas@...>
Subject: Re: Two Basic Questions, Please?
To: "David Halliday" <tetrahall@...>, "Kannel Users" <users@...>, "Cezary Siwek" <czarek@...>
Date: Saturday, 28 November, 2009, 6:54

Hi,

And just what are bulk SMS firms are using? Maybe kannel?

If you just want to send your own SMS, use a bulk SMS progvider's web interface. Kannel is for bulk SMS providers. A few large corporations are using it also for in-house SMS provision.

BR,

Nikos

----- Original Message -----

From: David Halliday

To: Kannel Users ; Nikos Balkanas ; Cezary Siwek

Sent: Saturday, November 28, 2009 7:32 AM

Subject: Re: Two Basic Questions, Please?

Thank you , Cezary and Nikos, for your responses.

The option:

Application -> Kannel -> GSM modem

is now clear to me.

One last point, please, and I will not bother the list with my elementary enquiry anymore.

Consider the second option:

Application -> Kannel -> SMSc link

Say there is a firm that provides 2 separate services:

Service a: Bulk SMS messages to network X

Service b: SMSC connectivity with network X (SMPP link)

In theory, applying the second option mentioned above, if we went for service b, would it not be cheaper than service a?

If the answer is no, then what on earth is the use of the gateway? Most bulk sms firms provide you with a website script/interface to send sms messages from the website anyway, and that is usually included in the price.

Best regards,

David

--- On Sat, 28/11/09, Nikos Balkanas <nbalkanas@...> wrote:

From: Nikos Balkanas <nbalkanas@...>
Subject: Re: Two Basic Questions, Please?
To: "Cezary Siwek" <czarek@...>, "David Halliday" <tetrahall@...>, "Kannel Users" <users@...>
Date: Saturday, 28 November, 2009, 2:47

ο»Ώ
Hi,

To make it clearer. A GSM modem is a mobile phone as far as the operator is concerned. Both are using a SIM card and are charged by it. Kannel doesn't care. The differences between a GSM modem and a mobile phone (with modem functionality) are:

1) You can use your mobile for other things as well (calling friends, etc.)

2) A dedicated GSM modem is more reliable, in terms of DLRs, status and SMS handling.

BR,

Nikos

----- Original Message -----

From: Cezary Siwek

To: David Halliday ; Kannel Users

Sent: Saturday, November 28, 2009 3:08 AM

Subject: Re: Two Basic Questions, Please?

David,

Unfortunately you won't save any money this way....You will pay the same price by sending an SMS from a mobile phone or using Kannel->gms modem. Well, you save money because you can use Kannel instead of other commercial products. Kannel only helps you in enabling SMS on your website/application.

Cezary

----- Original Message -----

From: David Halliday

To: Kannel Users ; Cezary Siwek

Sent: 28 November 2009 00:24

Subject: Re: Two Basic Questions, Please?

Hi Cezary,

Thank you ever so much for the useful info.

The basic point that I still can really understand is 'how' Kannel - or any free gateway - could reduce the cost of sending sms. I just need to get the answer before going through installing linux, buyinga GSM modem, etc.

Despite googling a lot for the last 10 days, I am still 'confused' really.

The aim is to set it up for someone abroad. The sim card provider do not allow sending free messages from a mobile phone.

So, if we went for the option:

Application -> Free Gateway (e.g. Kannel) -> GSM modem ( + simcard)

How could that be cheaper than to send them directly from a mobile phone?

On Kannel's website, one of the answers for this question
1.2 Why should I use Kannel instead of a commercial WAP gateway?

is: The price is right :-) Do you really want to pay thousands of dollars of a WAP gateway?

May be in this particular case, one should go for the other option, to bypass the sim card provider altogether, i.e.:-

Application -> Free Gateway (e.g. Kannel) -> SMSc agent/provider

In any case, thank you once again for your reply.

Best regards,

David

--- On Fri, 27/11/09, Cezary Siwek <czarek@...> wrote:

From: Cezary Siwek <czarek@...>
Subject: Re: Two Basic Questions, Please?
To: "Kannel Users" <users@...>
Date: Friday, 27 November, 2009, 23:06

I think 1000sms/day is too much for gsm modem/sim card.

I'm assuming you are UK based. Most of UK networks don't allow to send more than 3k sms/month (even if you are on 'unlimited text' plan). If you exceed that volume you may be disconnected or charged as per normal text 10-15p. Please check T and C (especially the "fair usage policy") of your SIM provider before you decide to go this way.

If you get an SMPP connection from SMS carrier you will pay 3-5p/sms.

AFAIK:

H3G UK - allows to send 3k SMS. After that you will be charged 10p

t-mibile UK - "If you send more than 3000 texts a month or text more than 200 different numbers in 5 days, you may be breaking your terms and conditions, which say that you canβ€™t use your phone for anything unlawful or to send nuisance"

O2 UK- "All usage must be for your private, personal and non-commercial purposes. You may not use your SIM Card: a. in, or connected to, any other device including modems;"

Best Regards,

Cezary

----- Original Message -----

From: David Halliday

To: Kannel Users

Sent: 27 November 2009 01:18

Subject: Re: Two Basic Questions, Please?

Hi Nikos,

Many thanks for your repsonse. It is really useful.

Before actually sending my enquiry to this list, I had done some searchig for a while on google, and I understood that the only way to send sms message to recepints is by going through an SMS Centre for the dsetination network.

In your reply, you mentioned as an option:

Application -> Kannel -> GSM modem

Can it really be done that way - *bypassing* the SMS centre?

And if yes, what is considered as "low volume"? Would 1000 messages per day be 'OK' with a sim card provider?

And of course, it all depends on the destination network. Real SS7 connections may not be an option.

I would appreciate your advice.

Best regards

David

--- On Thu, 26/11/09, Nikos Balkanas <nbal@...> wrote:

From: Nikos Balkanas <nbal@...>
Subject: Re: Two Basic Questions, Please?
To: "David Halliday" <tetrahall@...>, "Kannel Users" <users@...>
Date: Thursday, 26 November, 2009, 1:27

Hi,

1) To push SMS you will need:

Application -> Kannel -> GSM modem

-or-

Application -> Kannel -> SMSc link

Application is some kind of web interface to facilitate and schedule pushes. Optionally you can substitute one of kannel's components, smsbox, with SQLbox for sending bulk.

GSM modem provides for a low volume, cheaper usually interface using a SIM card. But volume is restricted else SIM maybe disabled. SMSc provides for a more reliable interface, however, throughput is restricted according to your contract. Volume is unlimited (of course you are charged for each SMS). You can also shop around to get the lowest price globally, whereas with a SIM you are restricted by what your operator gives you.

2) Cost depends on your volume and destination. If Clickatell is an aggeragator, ie routes SMS to other SMScs, you can do better than them. If, however, they have real SS7 connections, given their volume, it is unlikely.

BR,

Nikos

----- Original Message -----

From: David Halliday

To: Kannel Users

Sent: Wednesday, November 25, 2009 9:54 PM

Subject: Two Basic Questions, Please?

Hello,

I have windows xp on my pc, and am very interested in Kannel.

Before installing Linux and going through the whole process, I would like to know, if possible, please:-

1. To send sms messages, what else would one need apart from:-

Kannel + GSM modem + SMSC connectivity (for recepients' network)

Anything else apart from the above 3 'components'?

2. Would that arrangement be actually cheaper than to go through some bulk SMS suppliers like Clickatell, for example? I think it should, but I am not sure.

I would greatly appreciate an answer.

Best regards,

David

From forum: Kannel - User

Kannel confuse me for 10 days, I need your help.

2009-11-28T04:45:33Z

hi friends,wapkannel.conf wapkannel.conf wapserver+screen.JPG Nokia+client+simulator.JPG
I try to configurate a kannel wap gate, But I failed to let the client access the wap gate.
I have done these works in the last 10 days .
firstly, I setup a nokia client simulator(nokia 7210 SDK), the only configuration is gateway IP, I set it to 192.168.11.8, which is the kannel wap server. The port is 9200.
secondly, I setup a kannel wap gate in Cent OS 5(linux), and I run the kannel wap gate after I configurating the wap server.
thirdly, I connet to the website http://gmail.com in nokia client simulator, but the client show me a message No Gateway Reply(see attached file Nokia client simulator.JPG), in the same time, the server show me some message(see attached file wapgate screen.JPG).
Besides, you can read my kannelwap.conf file(see attached file wapkannel.conf), some errors?
Please help me. Thanks in advance.

boocheen
2009.11.28

From forum: Kannel - Dev

Re: Two Basic Questions, Please?

2009-11-27T22:54:45Z

Hi,

And just what are bulk SMS firms are using? Maybe kannel?

If you just want to send your own SMS, use a bulk SMS progvider's web interface. Kannel is for bulk SMS providers. A few large corporations are using it also for in-house SMS provision.

BR,

Nikos

----- Original Message -----

From: tetrahall@...

To: users@... ; nbalkanas@... ; czarek@...

Sent: Saturday, November 28, 2009 7:32 AM

Subject: Re: Two Basic Questions, Please?

Thank you , Cezary and Nikos, for your responses.

The option:

Application -> Kannel -> GSM modem

is now clear to me.

One last point, please, and I will not bother the list with my elementary enquiry anymore.

Consider the second option:

Application -> Kannel -> SMSc link

Say there is a firm that provides 2 separate services:

Service a: Bulk SMS messages to network X

Service b: SMSC connectivity with network X (SMPP link)

In theory, applying the second option mentioned above, if we went for service b, would it not be cheaper than service a?

If the answer is no, then what on earth is the use of the gateway? Most bulk sms firms provide you with a website script/interface to send sms messages from the website anyway, and that is usually included in the price.

Best regards,

David

--- On Sat, 28/11/09, Nikos Balkanas <nbalkanas@...> wrote:

From: Nikos Balkanas <nbalkanas@...>
Subject: Re: Two Basic Questions, Please?
To: "Cezary Siwek" <czarek@...>, "David Halliday" <tetrahall@...>, "Kannel Users" <users@...>
Date: Saturday, 28 November, 2009, 2:47

ΞΏΒ»Ξ�
Hi,

To make it clearer. A GSM modem is a mobile phone as far as the operator is concerned. Both are using a SIM card and are charged by it. Kannel doesn't care. The differences between a GSM modem and a mobile phone (with modem functionality) are:

1) You can use your mobile for other things as well (calling friends, etc.)

2) A dedicated GSM modem is more reliable, in terms of DLRs, status and SMS handling.

BR,

Nikos

----- Original Message -----

From: Cezary Siwek

To: David Halliday ; Kannel Users

Sent: Saturday, November 28, 2009 3:08 AM

Subject: Re: Two Basic Questions, Please?

David,

Unfortunately you won't save any money this way....You will pay the same price by sending an SMS from a mobile phone or using Kannel->gms modem. Well, you save money because you can use Kannel instead of other commercial products. Kannel only helps you in enabling SMS on your website/application.

Cezary

----- Original Message -----

From: David Halliday

To: Kannel Users ; Cezary Siwek

Sent: 28 November 2009 00:24

Subject: Re: Two Basic Questions, Please?

Hi Cezary,

Thank you ever so much for the useful info.

The basic point that I still can really understand is 'how' Kannel - or any free gateway - could reduce the cost of sending sms. I just need to get the answer before going through installing linux, buyinga GSM modem, etc.

Despite googling a lot for the last 10 days, I am still 'confused' really.

The aim is to set it up for someone abroad. The sim card provider do not allow sending free messages from a mobile phone.

So, if we went for the option:

Application -> Free Gateway (e.g. Kannel) -> GSM modem ( + simcard)

How could that be cheaper than to send them directly from a mobile phone?

On Kannel's website, one of the answers for this question
1.2 Why should I use Kannel instead of a commercial WAP gateway?

is: The price is right :-) Do you really want to pay thousands of dollars of a WAP gateway?

May be in this particular case, one should go for the other option, to bypass the sim card provider altogether, i.e.:-

Application -> Free Gateway (e.g. Kannel) -> SMSc agent/provider

In any case, thank you once again for your reply.

Best regards,

David

--- On Fri, 27/11/09, Cezary Siwek <czarek@...> wrote:

From: Cezary Siwek <czarek@...>
Subject: Re: Two Basic Questions, Please?
To: "Kannel Users" <users@...>
Date: Friday, 27 November, 2009, 23:06

I think 1000sms/day is too much for gsm modem/sim card.

I'm assuming you are UK based. Most of UK networks don't allow to send more than 3k sms/month (even if you are on 'unlimited text' plan). If you exceed that volume you may be disconnected or charged as per normal text 10-15p. Please check T and C (especially the "fair usage policy") of your SIM provider before you decide to go this way.

If you get an SMPP connection from SMS carrier you will pay 3-5p/sms.

AFAIK:

H3G UK - allows to send 3k SMS. After that you will be charged 10p

t-mibile UK - "If you send more than 3000 texts a month or text more than 200 different numbers in 5 days, you may be breaking your terms and conditions, which say that you canΞ²β‚¬β„Άt use your phone for anything unlawful or to send nuisance"

O2 UK- "All usage must be for your private, personal and non-commercial purposes. You may not use your SIM Card: a. in, or connected to, any other device including modems;"

Best Regards,

Cezary

----- Original Message -----

From: David Halliday

To: Kannel Users

Sent: 27 November 2009 01:18

Subject: Re: Two Basic Questions, Please?

Hi Nikos,

Many thanks for your repsonse. It is really useful.

Before actually sending my enquiry to this list, I had done some searchig for a while on google, and I understood that the only way to send sms message to recepints is by going through an SMS Centre for the dsetination network.

In your reply, you mentioned as an option:

Application -> Kannel -> GSM modem

Can it really be done that way - *bypassing* the SMS centre?

And if yes, what is considered as "low volume"? Would 1000 messages per day be 'OK' with a sim card provider?

And of course, it all depends on the destination network. Real SS7 connections may not be an option.

I would appreciate your advice.

Best regards

David

--- On Thu, 26/11/09, Nikos Balkanas <nbal@...> wrote:

From: Nikos Balkanas <nbal@...>
Subject: Re: Two Basic Questions, Please?
To: "David Halliday" <tetrahall@...>, "Kannel Users" <users@...>
Date: Thursday, 26 November, 2009, 1:27

Hi,

1) To push SMS you will need:

Application -> Kannel -> GSM modem

-or-

Application -> Kannel -> SMSc link

Application is some kind of web interface to facilitate and schedule pushes. Optionally you can substitute one of kannel's components, smsbox, with SQLbox for sending bulk.

GSM modem provides for a low volume, cheaper usually interface using a SIM card. But volume is restricted else SIM maybe disabled. SMSc provides for a more reliable interface, however, throughput is restricted according to your contract. Volume is unlimited (of course you are charged for each SMS). You can also shop around to get the lowest price globally, whereas with a SIM you are restricted by what your operator gives you.

2) Cost depends on your volume and destination. If Clickatell is an aggeragator, ie routes SMS to other SMScs, you can do better than them. If, however, they have real SS7 connections, given their volume, it is unlikely.

BR,

Nikos

----- Original Message -----

From: David Halliday

To: Kannel Users

Sent: Wednesday, November 25, 2009 9:54 PM

Subject: Two Basic Questions, Please?

Hello,

I have windows xp on my pc, and am very interested in Kannel.

Before installing Linux and going through the whole process, I would like to know, if possible, please:-

1. To send sms messages, what else would one need apart from:-

Kannel + GSM modem + SMSC connectivity (for recepients' network)

Anything else apart from the above 3 'components'?

2. Would that arrangement be actually cheaper than to go through some bulk SMS suppliers like Clickatell, for example? I think it should, but I am not sure.

I would greatly appreciate an answer.

Best regards,

David

From forum: Kannel - User

Re: Two Basic Questions, Please?

2009-11-27T21:32:20Z

Thank you , Cezary and Nikos, for your responses.

The option:

Application -> Kannel -> GSM modem

is now clear to me.

One last point, please, and I will not bother the list with my elementary enquiry anymore.

Consider the second option:

Application -> Kannel -> SMSc link

Say there is a firm that provides 2 separate services:

Service a: Bulk SMS messages to network X

Service b: SMSC connectivity with network X (SMPP link)

In theory, applying the second option mentioned above, if we went for service b, would it not be cheaper than service a?

If the answer is no, then what on earth is the use of the gateway? Most bulk sms firms provide you with a website script/interface to send sms messages from the website anyway, and that is usually included in the price.

Best regards,

David

--- On Sat, 28/11/09, Nikos Balkanas <nbalkanas@...> wrote:

From: Nikos Balkanas <nbalkanas@...>
Subject: Re: Two Basic Questions, Please?
To: "Cezary Siwek" <czarek@...>, "David Halliday" <tetrahall@...>, "Kannel Users" <users@...>
Date: Saturday, 28 November, 2009, 2:47

ο»Ώ
Hi,

To make it clearer. A GSM modem is a mobile phone as far as the operator is concerned. Both are using a SIM card and are charged by it. Kannel doesn't care. The differences between a GSM modem and a mobile phone (with modem functionality) are:

1) You can use your mobile for other things as well (calling friends, etc.)

2) A dedicated GSM modem is more reliable, in terms of DLRs, status and SMS handling.

BR,

Nikos

----- Original Message -----

From: Cezary Siwek

To: David Halliday ; Kannel Users

Sent: Saturday, November 28, 2009 3:08 AM

Subject: Re: Two Basic Questions, Please?

David,

Unfortunately you won't save any money this way....You will pay the same price by sending an SMS from a mobile phone or using Kannel->gms modem. Well, you save money because you can use Kannel instead of other commercial products. Kannel only helps you in enabling SMS on your website/application.

Cezary

----- Original Message -----

From: David Halliday

To: Kannel Users ; Cezary Siwek

Sent: 28 November 2009 00:24

Subject: Re: Two Basic Questions, Please?

Hi Cezary,

Thank you ever so much for the useful info.

The basic point that I still can really understand is 'how' Kannel - or any free gateway - could reduce the cost of sending sms. I just need to get the answer before going through installing linux, buyinga GSM modem, etc.

Despite googling a lot for the last 10 days, I am still 'confused' really.

The aim is to set it up for someone abroad. The sim card provider do not allow sending free messages from a mobile phone.

So, if we went for the option:

Application -> Free Gateway (e.g. Kannel) -> GSM modem ( + simcard)

How could that be cheaper than to send them directly from a mobile phone?

On Kannel's website, one of the answers for this question
1.2 Why should I use Kannel instead of a commercial WAP gateway?

is: The price is right :-) Do you really want to pay thousands of dollars of a WAP gateway?

May be in this particular case, one should go for the other option, to bypass the sim card provider altogether, i.e.:-

Application -> Free Gateway (e.g. Kannel) -> SMSc agent/provider

In any case, thank you once again for your reply.

Best regards,

David

--- On Fri, 27/11/09, Cezary Siwek <czarek@...> wrote:

From: Cezary Siwek <czarek@...>
Subject: Re: Two Basic Questions, Please?
To: "Kannel Users" <users@...>
Date: Friday, 27 November, 2009, 23:06

I think 1000sms/day is too much for gsm modem/sim card.

I'm assuming you are UK based. Most of UK networks don't allow to send more than 3k sms/month (even if you are on 'unlimited text' plan). If you exceed that volume you may be disconnected or charged as per normal text 10-15p. Please check T and C (especially the "fair usage policy") of your SIM provider before you decide to go this way.

If you get an SMPP connection from SMS carrier you will pay 3-5p/sms.

AFAIK:

H3G UK - allows to send 3k SMS. After that you will be charged 10p

t-mibile UK - "If you send more than 3000 texts a month or text more than 200 different numbers in 5 days, you may be breaking your terms and conditions, which say that you canβ€™t use your phone for anything unlawful or to send nuisance"

O2 UK- "All usage must be for your private, personal and non-commercial purposes. You may not use your SIM Card: a. in, or connected to, any other device including modems;"

Best Regards,

Cezary

----- Original Message -----

From: David Halliday

To: Kannel Users

Sent: 27 November 2009 01:18

Subject: Re: Two Basic Questions, Please?

Hi Nikos,

Many thanks for your repsonse. It is really useful.

Before actually sending my enquiry to this list, I had done some searchig for a while on google, and I understood that the only way to send sms message to recepints is by going through an SMS Centre for the dsetination network.

In your reply, you mentioned as an option:

Application -> Kannel -> GSM modem

Can it really be done that way - *bypassing* the SMS centre?

And if yes, what is considered as "low volume"? Would 1000 messages per day be 'OK' with a sim card provider?

And of course, it all depends on the destination network. Real SS7 connections may not be an option.

I would appreciate your advice.

Best regards

David

--- On Thu, 26/11/09, Nikos Balkanas <nbal@...> wrote:

From: Nikos Balkanas <nbal@...>
Subject: Re: Two Basic Questions, Please?
To: "David Halliday" <tetrahall@...>, "Kannel Users" <users@...>
Date: Thursday, 26 November, 2009, 1:27

Hi,

1) To push SMS you will need:

Application -> Kannel -> GSM modem

-or-

Application -> Kannel -> SMSc link

Application is some kind of web interface to facilitate and schedule pushes. Optionally you can substitute one of kannel's components, smsbox, with SQLbox for sending bulk.

GSM modem provides for a low volume, cheaper usually interface using a SIM card. But volume is restricted else SIM maybe disabled. SMSc provides for a more reliable interface, however, throughput is restricted according to your contract. Volume is unlimited (of course you are charged for each SMS). You can also shop around to get the lowest price globally, whereas with a SIM you are restricted by what your operator gives you.

2) Cost depends on your volume and destination. If Clickatell is an aggeragator, ie routes SMS to other SMScs, you can do better than them. If, however, they have real SS7 connections, given their volume, it is unlikely.

BR,

Nikos

----- Original Message -----

From: David Halliday

To: Kannel Users

Sent: Wednesday, November 25, 2009 9:54 PM

Subject: Two Basic Questions, Please?

Hello,

I have windows xp on my pc, and am very interested in Kannel.

Before installing Linux and going through the whole process, I would like to know, if possible, please:-

1. To send sms messages, what else would one need apart from:-

Kannel + GSM modem + SMSC connectivity (for recepients' network)

Anything else apart from the above 3 'components'?

2. Would that arrangement be actually cheaper than to go through some bulk SMS suppliers like Clickatell, for example? I think it should, but I am not sure.

I would greatly appreciate an answer.

Best regards,

David

From forum: Kannel - User

Re: Two Basic Questions, Please?

2009-11-27T18:47:32Z

ο»Ώ

Hi,

To make it clearer. A GSM modem is a mobile phone as far as the operator is concerned. Both are using a SIM card and are charged by it. Kannel doesn't care. The differences between a GSM modem and a mobile phone (with modem functionality) are:

1) You can use your mobile for other things as well (calling friends, etc.)

2) A dedicated GSM modem is more reliable, in terms of DLRs, status and SMS handling.

BR,

Nikos

----- Original Message -----

From: czarek@...

To: tetrahall@... ; users@...

Sent: Saturday, November 28, 2009 3:08 AM

Subject: Re: Two Basic Questions, Please?

David,

Unfortunately you won't save any money this way....You will pay the same price by sending an SMS from a mobile phone or using Kannel->gms modem. Well, you save money because you can use Kannel instead of other commercial products. Kannel only helps you in enabling SMS on your website/application.

Cezary

----- Original Message -----

From: tetrahall@...

To: users@... ; czarek@...

Sent: 28 November 2009 00:24

Subject: Re: Two Basic Questions, Please?

Hi Cezary,

Thank you ever so much for the useful info.

The basic point that I still can really understand is 'how' Kannel - or any free gateway - could reduce the cost of sending sms. I just need to get the answer before going through installing linux, buyinga GSM modem, etc.

Despite googling a lot for the last 10 days, I am still 'confused' really.

The aim is to set it up for someone abroad. The sim card provider do not allow sending free messages from a mobile phone.

So, if we went for the option:

Application -> Free Gateway (e.g. Kannel) -> GSM modem ( + simcard)

How could that be cheaper than to send them directly from a mobile phone?

On Kannel's website, one of the answers for this question
1.2 Why should I use Kannel instead of a commercial WAP gateway?

is: The price is right :-) Do you really want to pay thousands of dollars of a WAP gateway?

May be in this particular case, one should go for the other option, to bypass the sim card provider altogether, i.e.:-

Application -> Free Gateway (e.g. Kannel) -> SMSc agent/provider

In any case, thank you once again for your reply.

Best regards,

David

--- On Fri, 27/11/09, Cezary Siwek <czarek@...> wrote:

From: Cezary Siwek <czarek@...>
Subject: Re: Two Basic Questions, Please?
To: "Kannel Users" <users@...>
Date: Friday, 27 November, 2009, 23:06

I think 1000sms/day is too much for gsm modem/sim card.

I'm assuming you are UK based. Most of UK networks don't allow to send more than 3k sms/month (even if you are on 'unlimited text' plan). If you exceed that volume you may be disconnected or charged as per normal text 10-15p. Please check T and C (especially the "fair usage policy") of your SIM provider before you decide to go this way.

If you get an SMPP connection from SMS carrier you will pay 3-5p/sms.

AFAIK:

H3G UK - allows to send 3k SMS. After that you will be charged 10p

t-mibile UK - "If you send more than 3000 texts a month or text more than 200 different numbers in 5 days, you may be breaking your terms and conditions, which say that you canβ€™t use your phone for anything unlawful or to send nuisance"

O2 UK- "All usage must be for your private, personal and non-commercial purposes. You may not use your SIM Card: a. in, or connected to, any other device including modems;"

Best Regards,

Cezary

----- Original Message -----

From: David Halliday

To: Kannel Users

Sent: 27 November 2009 01:18

Subject: Re: Two Basic Questions, Please?

Hi Nikos,

Many thanks for your repsonse. It is really useful.

Before actually sending my enquiry to this list, I had done some searchig for a while on google, and I understood that the only way to send sms message to recepints is by going through an SMS Centre for the dsetination network.

In your reply, you mentioned as an option:

Application -> Kannel -> GSM modem

Can it really be done that way - *bypassing* the SMS centre?

And if yes, what is considered as "low volume"? Would 1000 messages per day be 'OK' with a sim card provider?

And of course, it all depends on the destination network. Real SS7 connections may not be an option.

I would appreciate your advice.

Best regards

David

--- On Thu, 26/11/09, Nikos Balkanas <nbal@...> wrote:

From: Nikos Balkanas <nbal@...>
Subject: Re: Two Basic Questions, Please?
To: "David Halliday" <tetrahall@...>, "Kannel Users" <users@...>
Date: Thursday, 26 November, 2009, 1:27

Hi,

1) To push SMS you will need:

Application -> Kannel -> GSM modem

-or-

Application -> Kannel -> SMSc link

Application is some kind of web interface to facilitate and schedule pushes. Optionally you can substitute one of kannel's components, smsbox, with SQLbox for sending bulk.

GSM modem provides for a low volume, cheaper usually interface using a SIM card. But volume is restricted else SIM maybe disabled. SMSc provides for a more reliable interface, however, throughput is restricted according to your contract. Volume is unlimited (of course you are charged for each SMS). You can also shop around to get the lowest price globally, whereas with a SIM you are restricted by what your operator gives you.

2) Cost depends on your volume and destination. If Clickatell is an aggeragator, ie routes SMS to other SMScs, you can do better than them. If, however, they have real SS7 connections, given their volume, it is unlikely.

BR,

Nikos

----- Original Message -----

From: David Halliday

To: Kannel Users

Sent: Wednesday, November 25, 2009 9:54 PM

Subject: Two Basic Questions, Please?

Hello,

I have windows xp on my pc, and am very interested in Kannel.

Before installing Linux and going through the whole process, I would like to know, if possible, please:-

1. To send sms messages, what else would one need apart from:-

Kannel + GSM modem + SMSC connectivity (for recepients' network)

Anything else apart from the above 3 'components'?

2. Would that arrangement be actually cheaper than to go through some bulk SMS suppliers like Clickatell, for example? I think it should, but I am not sure.

I would greatly appreciate an answer.

Best regards,

David

From forum: Kannel - User

Re: Two Basic Questions, Please?

2009-11-27T17:08:43Z

David,

Unfortunately you won't save any money this way....You will pay the same price by sending an SMS from a mobile phone or using Kannel->gms modem. Well, you save money because you can use Kannel instead of other commercial products. Kannel only helps you in enabling SMS on your website/application.

Cezary

----- Original Message -----

From: tetrahall@...

To: users@... ; czarek@...

Sent: 28 November 2009 00:24

Subject: Re: Two Basic Questions, Please?

Hi Cezary,

Thank you ever so much for the useful info.

The basic point that I still can really understand is 'how' Kannel - or any free gateway - could reduce the cost of sending sms. I just need to get the answer before going through installing linux, buyinga GSM modem, etc.

Despite googling a lot for the last 10 days, I am still 'confused' really.

The aim is to set it up for someone abroad. The sim card provider do not allow sending free messages from a mobile phone.

So, if we went for the option:

Application -> Free Gateway (e.g. Kannel) -> GSM modem ( + simcard)

How could that be cheaper than to send them directly from a mobile phone?

On Kannel's website, one of the answers for this question
1.2 Why should I use Kannel instead of a commercial WAP gateway?

is: The price is right :-) Do you really want to pay thousands of dollars of a WAP gateway?

May be in this particular case, one should go for the other option, to bypass the sim card provider altogether, i.e.:-

Application -> Free Gateway (e.g. Kannel) -> SMSc agent/provider

In any case, thank you once again for your reply.

Best regards,

David

--- On Fri, 27/11/09, Cezary Siwek <czarek@...> wrote:

From: Cezary Siwek <czarek@...>
Subject: Re: Two Basic Questions, Please?
To: "Kannel Users" <users@...>
Date: Friday, 27 November, 2009, 23:06

I think 1000sms/day is too much for gsm modem/sim card.

I'm assuming you are UK based. Most of UK networks don't allow to send more than 3k sms/month (even if you are on 'unlimited text' plan). If you exceed that volume you may be disconnected or charged as per normal text 10-15p. Please check T and C (especially the "fair usage policy") of your SIM provider before you decide to go this way.

If you get an SMPP connection from SMS carrier you will pay 3-5p/sms.

AFAIK:

H3G UK - allows to send 3k SMS. After that you will be charged 10p

t-mibile UK - "If you send more than 3000 texts a month or text more than 200 different numbers in 5 days, you may be breaking your terms and conditions, which say that you can’t use your phone for anything unlawful or to send nuisance"

O2 UK- "All usage must be for your private, personal and non-commercial purposes. You may not use your SIM Card: a. in, or connected to, any other device including modems;"

Best Regards,

Cezary

----- Original Message -----

From: David Halliday

To: Kannel Users

Sent: 27 November 2009 01:18

Subject: Re: Two Basic Questions, Please?

Hi Nikos,

Many thanks for your repsonse. It is really useful.

Before actually sending my enquiry to this list, I had done some searchig for a while on google, and I understood that the only way to send sms message to recepints is by going through an SMS Centre for the dsetination network.

In your reply, you mentioned as an option:

Application -> Kannel -> GSM modem

Can it really be done that way - *bypassing* the SMS centre?

And if yes, what is considered as "low volume"? Would 1000 messages per day be 'OK' with a sim card provider?

And of course, it all depends on the destination network. Real SS7 connections may not be an option.

I would appreciate your advice.

Best regards

David

--- On Thu, 26/11/09, Nikos Balkanas <nbal@...> wrote:

From: Nikos Balkanas <nbal@...>
Subject: Re: Two Basic Questions, Please?
To: "David Halliday" <tetrahall@...>, "Kannel Users" <users@...>
Date: Thursday, 26 November, 2009, 1:27

Hi,

1) To push SMS you will need:

Application -> Kannel -> GSM modem

-or-

Application -> Kannel -> SMSc link

Application is some kind of web interface to facilitate and schedule pushes. Optionally you can substitute one of kannel's components, smsbox, with SQLbox for sending bulk.

GSM modem provides for a low volume, cheaper usually interface using a SIM card. But volume is restricted else SIM maybe disabled. SMSc provides for a more reliable interface, however, throughput is restricted according to your contract. Volume is unlimited (of course you are charged for each SMS). You can also shop around to get the lowest price globally, whereas with a SIM you are restricted by what your operator gives you.

2) Cost depends on your volume and destination. If Clickatell is an aggeragator, ie routes SMS to other SMScs, you can do better than them. If, however, they have real SS7 connections, given their volume, it is unlikely.

BR,

Nikos

----- Original Message -----

From: David Halliday

To: Kannel Users

Sent: Wednesday, November 25, 2009 9:54 PM

Subject: Two Basic Questions, Please?

Hello,

I have windows xp on my pc, and am very interested in Kannel.

Before installing Linux and going through the whole process, I would like to know, if possible, please:-

1. To send sms messages, what else would one need apart from:-

Kannel + GSM modem + SMSC connectivity (for recepients' network)

Anything else apart from the above 3 'components'?

2. Would that arrangement be actually cheaper than to go through some bulk SMS suppliers like Clickatell, for example? I think it should, but I am not sure.

I would greatly appreciate an answer.

Best regards,

David

From forum: Kannel - User

Re: Two Basic Questions, Please?

2009-11-27T16:24:54Z

Hi Cezary,

Thank you ever so much for the useful info.

The basic point that I still can really understand is 'how' Kannel - or any free gateway - could reduce the cost of sending sms. I just need to get the answer before going through installing linux, buyinga GSM modem, etc.

Despite googling a lot for the last 10 days, I am still 'confused' really.

The aim is to set it up for someone abroad. The sim card provider do not allow sending free messages from a mobile phone.

So, if we went for the option:

Application -> Free Gateway (e.g. Kannel) -> GSM modem ( + simcard)

How could that be cheaper than to send them directly from a mobile phone?

On Kannel's website, one of the answers for this question
1.2 Why should I use Kannel instead of a commercial WAP gateway?

is: The price is right :-) Do you really want to pay thousands of dollars of a WAP gateway?

May be in this particular case, one should go for the other option, to bypass the sim card provider altogether, i.e.:-

Application -> Free Gateway (e.g. Kannel) -> SMSc agent/provider

In any case, thank you once again for your reply.

Best regards,

David

--- On Fri, 27/11/09, Cezary Siwek <czarek@...> wrote:

From: Cezary Siwek <czarek@...>
Subject: Re: Two Basic Questions, Please?
To: "Kannel Users" <users@...>
Date: Friday, 27 November, 2009, 23:06

I think 1000sms/day is too much for gsm modem/sim card.

I'm assuming you are UK based. Most of UK networks don't allow to send more than 3k sms/month (even if you are on 'unlimited text' plan). If you exceed that volume you may be disconnected or charged as per normal text 10-15p. Please check T and C (especially the "fair usage policy") of your SIM provider before you decide to go this way.

If you get an SMPP connection from SMS carrier you will pay 3-5p/sms.

AFAIK:

H3G UK - allows to send 3k SMS. After that you will be charged 10p

t-mibile UK - "If you send more than 3000 texts a month or text more than 200 different numbers in 5 days, you may be breaking your terms and conditions, which say that you can’t use your phone for anything unlawful or to send nuisance"

O2 UK- "All usage must be for your private, personal and non-commercial purposes. You may not use your SIM Card: a. in, or connected to, any other device including modems;"

Best Regards,

Cezary

----- Original Message -----

From: David Halliday

To: Kannel Users

Sent: 27 November 2009 01:18

Subject: Re: Two Basic Questions, Please?

Hi Nikos,

Many thanks for your repsonse. It is really useful.

Before actually sending my enquiry to this list, I had done some searchig for a while on google, and I understood that the only way to send sms message to recepints is by going through an SMS Centre for the dsetination network.

In your reply, you mentioned as an option:

Application -> Kannel -> GSM modem

Can it really be done that way - *bypassing* the SMS centre?

And if yes, what is considered as "low volume"? Would 1000 messages per day be 'OK' with a sim card provider?

And of course, it all depends on the destination network. Real SS7 connections may not be an option.

I would appreciate your advice.

Best regards

David

--- On Thu, 26/11/09, Nikos Balkanas <nbal@...> wrote:

From: Nikos Balkanas <nbal@...>
Subject: Re: Two Basic Questions, Please?
To: "David Halliday" <tetrahall@...>, "Kannel Users" <users@...>
Date: Thursday, 26 November, 2009, 1:27

Hi,

1) To push SMS you will need:

Application -> Kannel -> GSM modem

-or-

Application -> Kannel -> SMSc link

Application is some kind of web interface to facilitate and schedule pushes. Optionally you can substitute one of kannel's components, smsbox, with SQLbox for sending bulk.

GSM modem provides for a low volume, cheaper usually interface using a SIM card. But volume is restricted else SIM maybe disabled. SMSc provides for a more reliable interface, however, throughput is restricted according to your contract. Volume is unlimited (of course you are charged for each SMS). You can also shop around to get the lowest price globally, whereas with a SIM you are restricted by what your operator gives you.

2) Cost depends on your volume and destination. If Clickatell is an aggeragator, ie routes SMS to other SMScs, you can do better than them. If, however, they have real SS7 connections, given their volume, it is unlikely.

BR,

Nikos

----- Original Message -----

From: David Halliday

To: Kannel Users

Sent: Wednesday, November 25, 2009 9:54 PM

Subject: Two Basic Questions, Please?

Hello,

I have windows xp on my pc, and am very interested in Kannel.

Before installing Linux and going through the whole process, I would like to know, if possible, please:-

1. To send sms messages, what else would one need apart from:-

Kannel + GSM modem + SMSC connectivity (for recepients' network)

Anything else apart from the above 3 'components'?

2. Would that arrangement be actually cheaper than to go through some bulk SMS suppliers like Clickatell, for example? I think it should, but I am not sure.

I would greatly appreciate an answer.

Best regards,

David

From forum: Kannel - User

Re: Two Basic Questions, Please?

2009-11-27T15:06:03Z

I think 1000sms/day is too much for gsm modem/sim card.

I'm assuming you are UK based. Most of UK networks don't allow to send more than 3k sms/month (even if you are on 'unlimited text' plan). If you exceed that volume you may be disconnected or charged as per normal text 10-15p. Please check T and C (especially the "fair usage policy") of your SIM provider before you decide to go this way.

If you get an SMPP connection from SMS carrier you will pay 3-5p/sms.

AFAIK:

H3G UK - allows to send 3k SMS. After that you will be charged 10p

t-mibile UK - "If you send more than 3000 texts a month or text more than 200 different numbers in 5 days, you may be breaking your terms and conditions, which say that you cant use your phone for anything unlawful or to send nuisance"

O2 UK- "All usage must be for your private, personal and non-commercial purposes. You may not use your SIM Card: a. in, or connected to, any other device including modems;"

Best Regards,

Cezary

----- Original Message -----

From: tetrahall@...

To: users@...

Sent: 27 November 2009 01:18

Subject: Re: Two Basic Questions, Please?

Hi Nikos,

Many thanks for your repsonse. It is really useful.

Before actually sending my enquiry to this list, I had done some searchig for a while on google, and I understood that the only way to send sms message to recepints is by going through an SMS Centre for the dsetination network.

In your reply, you mentioned as an option:

Application -> Kannel -> GSM modem

Can it really be done that way - *bypassing* the SMS centre?

And if yes, what is considered as "low volume"? Would 1000 messages per day be 'OK' with a sim card provider?

And of course, it all depends on the destination network. Real SS7 connections may not be an option.

I would appreciate your advice.

Best regards

David

--- On Thu, 26/11/09, Nikos Balkanas <nbal@...> wrote:

From: Nikos Balkanas <nbal@...>
Subject: Re: Two Basic Questions, Please?
To: "David Halliday" <tetrahall@...>, "Kannel Users" <users@...>
Date: Thursday, 26 November, 2009, 1:27

Hi,

1) To push SMS you will need:

Application -> Kannel -> GSM modem

-or-

Application -> Kannel -> SMSc link

Application is some kind of web interface to facilitate and schedule pushes. Optionally you can substitute one of kannel's components, smsbox, with SQLbox for sending bulk.

GSM modem provides for a low volume, cheaper usually interface using a SIM card. But volume is restricted else SIM maybe disabled. SMSc provides for a more reliable interface, however, throughput is restricted according to your contract. Volume is unlimited (of course you are charged for each SMS). You can also shop around to get the lowest price globally, whereas with a SIM you are restricted by what your operator gives you.

2) Cost depends on your volume and destination. If Clickatell is an aggeragator, ie routes SMS to other SMScs, you can do better than them. If, however, they have real SS7 connections, given their volume, it is unlikely.

BR,

Nikos

----- Original Message -----

From: David Halliday

To: Kannel Users

Sent: Wednesday, November 25, 2009 9:54 PM

Subject: Two Basic Questions, Please?

Hello,

I have windows xp on my pc, and am very interested in Kannel.

Before installing Linux and going through the whole process, I would like to know, if possible, please:-

1. To send sms messages, what else would one need apart from:-

Kannel + GSM modem + SMSC connectivity (for recepients' network)

Anything else apart from the above 3 'components'?

2. Would that arrangement be actually cheaper than to go through some bulk SMS suppliers like Clickatell, for example? I think it should, but I am not sure.

I would greatly appreciate an answer.

Best regards,

David

From forum: Kannel - User

Re: SQLBox Issues and Limit per cycle SQLBox patch

2009-11-27T11:03:03Z

My guess is that it's the missing meta-data field support on sqlbox, but I still need to do some extra tests to confirm.

I've the patch partially ready (missing some details on a couple of db engines only), will finish testing it and commit next week.

Regards,

Alex

On Fri, Nov 27, 2009 at 7:59 PM, Bruno Aguirre <brunoaguirrerissio@...> wrote:

Ok, is there any way i can help? Perhaps if you have an idea of where is the issue i can help you in the fix

2009/11/27 Alejandro Guerrieri <alejandro.guerrieri@...>

There seems to be an issue with latest CVS'es (with meta-data) and Sqlbox.

I'm working on a fix, but I've been quite busy lately, I hope to be able to finish it next week.

Regards,

Alex

On Fri, Nov 27, 2009 at 7:11 PM, Bruno Aguirre <brunoaguirrerissio@...> wrote:

Hi to all!.
I'm having some sort of issues using sqlbox, in a test enviroment i'm loosing 50% of the mos. In a graphical way:

   SMPPSim <----->      Bearerbox     <---->    Sqlbox       <-----> Smsbox <-------> HTTP
- Inyect 100Mos -       - Receives 100mos -       - Inserts 50mos -    - Sent 50 mts -    - Inyect 50 mts -

I'm using the SQLBox from the cvs, also i've correct the patch from Limit per cycle for this version, at first i thought that was my implementation the mistake then i've switched to the lastest cvs and the bug was already there.

My config:

1 ###############################################################
2 #                                 #
3 #         CORE CONFIG - Extended Config Setup                 #
4 #                                                             #
5 ###############################################################
6
7 group = core
8 admin-port = 13000
9 # Administration Port
10 admin-password = @dM1nMe
11 # Administration Password
12 admin-deny-ip = "*.*.*.*"
13 # Deny all ips for Administrate
14 admin-allow-ip = "127.0.0.1"
15 # Allow only this IPs, semicolon separated
16 smsbox-port = 13010
17 # Smsbox connection Port
18 wapbox-port = 13020
19 # Wapbox connection Port
20 wdp-interface-name = "*"
21 # UDP BroadCast
22 log-level = 0
23 # Verbose level, 0 More debug... 4 Less debug
24 log-file = "/var/log/kannel/bearerbox.log"
25 # Log file path
26 box-deny-ip = "*.*.*.*"
27 # Deny All Ips to connect to Bearerbox
28 box-allow-ip = "127.0.0.1"
29 # Allow only this Ips , semicolon separated
30 dlr-storage = mysql
31 # Where to store temp DLR data, internal default, Mysql recomended
32 store-type = spool
33 # Store type, block file is default, spool is one file per message
34 store-location = "/var/spool/kannel"
35 # Folder location of the spool
36
37 ###############################################################
38 #                                 #
39 #      MYSQL CONFIG - DLR Temp Storage                    #
40 #                                 #
41 ###############################################################
42
43 group = mysql-connection
44 id = mydlr
45 # Identification
46 host = 127.0.0.1
47 # IP of the MYSQL Database
48 port = 3306
49 # Port of the MYSQL Database
50 username = root
51 # Username of the connection
52 password = mysql
53 # Pasword of the connection
54 database = kannel
55 # Database name
56 max-connections = 50
57 # Maximun Concurrent conections

58
59 group = dlr-db
60 id = mydlr
61 # Identification
62 table = dlr
63 # Table Name
64 field-smsc = smsc
65 # Smsc Field Name
66 field-timestamp = ts
67 # Timestamp Field Name
68 field-destination = destination
69 # Destination Field Name
70 field-source = source
71 # Source Field Name
72 field-service = service
73 # Service Field Name
74 field-url = url
75 # Url Field Name
76 field-mask = mask
77 # Dlr Mask Field Name
78 field-status = status
79 # Status Field Name
80 field-boxc-id = box
81 # Box Id Field Name
82
83 group = smpp-tlv
84 name   = MAS_APP_ID
85 smsc-id = "debug"
86 tag    = 0x1401
87 type   = nulterminated
88 length = 4
89
90
91 ###############################################################
92 #                                 #
93 #      SMSBOX CONFIG - Handle SQLBox Instance             #
94 #                                                             #
95 ###############################################################
96
97 group = smsbox
98 #smsbox-id = smsbox
99 # Identification
100 bearerbox-host = localhost
101 #bearerbox-port = 13030
102 # Ip to the Bearerbox
103 sendsms-port = 13013
104 # Available port for SMS inyection
105 log-file = "/var/log/kannel/smsbox.log"
106 # Log file path
107 log-level = 0
108 # Verbose level, 0 More debug... 4 Less debug
109 #http-request-retry = 10
110 # Retry for the http request
111 #http-queue-delay = 30
112 # Delay per Retry
113
114 ###############################################################
115 #                                     #
116 #      WAPBOX CONFIG - Wap Gateway Main config            #
117 #                                     #
118 ###############################################################
119
120 group           = wapbox
121 bearerbox-host = 127.0.0.1
122 # Bearerbox IP
123 log-file        = "/var/log/kannelX1/wapbox.log"
124 # Log file path
125 log-level       = 4
126 # Verbose level, 0 More debug... 4 Less debug
127 syslog-level    = none
128 # Log in syslog
129
130 ###############################################################
131 #                                 #
132 #     PUSH PROXY GATEWAY - WapPush inyection              #
133 #                                 #
134 ###############################################################
135
136 group             = ppg
137 ppg-url           = /wappush
138 # Route in the inyection
139 ppg-port          = 8080
140 # Port for inyection
141 concurrent-pushes = 100
142 # Concurrency
143 users             = 1024
144 # Total users connected
145 ppg-allow-ip      = "127.0.0.1"
146 # Allow only this Ips , semicolon separated
147 trusted-pi        = true
148 # Trust by default
149 service-name      = ppg1
150 # Service name
151
152 group           = wap-push-user
153 wap-push-user   = wappush
154 # User for the inyection
155 ppg-username    = foo
156 # Username for the inyection
157 ppg-password    = bar
158 # Password
159 allow-ip        = "127.0.0.1"
160 # Allow only this Ips , semicolon separated
161
162 ###############################################################
163 #                                 #
164 #       SEND SMS - Send messages configuration            #
165 #                                 #
166 ###############################################################
167
168 group = sendsms-user
169 username = tester
170 # Username for the inyection
171 password = foobar
172 # Password For the inyection
173 user-deny-ip = "*.*.*.*"
174 # Deny All IPs
175 user-allow-ip = "127.0.0.1"
176 # Allow only this Ips , semicolon separated
177
178 ###############################################################
179 #                                 #
180 #       SEND SMS ROUTING - Send Messages routing          #
181 #                                 #
182 ###############################################################
183
184 group           = sms-service
185 keyword         = default
186 catch-all       = true
187 # Catch All
188 omit-empty      = true
189 # Omit Empty response
190 max-messages    = 10
191 #max-messages    = 0
192 # Dont send MTs synchronously
193 get-url         = "http://localhost:8090/mo?smsc_id=%i&short_code=%P&phone=%p&message=%a"
194 #text = "OK"
195 # URL to invoke ( README for constants )
196
197 ###############################################################
198 #                                 #
199 #       SMSCS CONFIG - Carrier Specific Config        #
200 #                                 #
201 ###############################################################
202
203 include = "/etc/kannel/smsc/debug/carriers.conf"

1 ###############################################################
2 #                                 #
3 #       SQLBOX CONFIG - Full status storage and Queueing #
4 #                                 #
5 ###############################################################
6
7 group = sqlbox
8 id = sqlbox
9 # Config Identification
10 #smsbox-id = chunkerbox
11 # Identification
12 bearerbox-host = localhost
13 # Bearerbox IP
14 bearerbox-port = 13010
15 # Bearerbox Port
16 smsbox-port = 13030
17 # Send Sms box ( From kannel core config )
18 #limit-per-cycle = 1
19 # SELECT limit
20 smsbox-port-ssl = false
21 # Usses SSL?
22 sql-log-table = sent_sms
23 # Sent Sms Table name
24 sql-insert-table = send_sms
25 # Queueing Sms Table name
26 log-file = "/var/log/kannel/sqlbox.log"
27 # Log File name
28 log-level = 0
29 # Log Verbosity
30
31 group = mysql-connection
32 id = sqlbox
33 # Identification
34 host = 127.0.0.1
35 # Database IP
36 port = 3306
37 # Database Port
38 username = root
39 # Username ( Grant CREATE )
40 password = mysql
41 # Password
42 database = kannel
43 # Database name
44 max-connections = 10

From forum: Kannel - User

Re: SQLBox Issues and Limit per cycle SQLBox patch

2009-11-27T10:59:59Z

Ok, is there any way i can help? Perhaps if you have an idea of where is the issue i can help you in the fix

2009/11/27 Alejandro Guerrieri <alejandro.guerrieri@...>

There seems to be an issue with latest CVS'es (with meta-data) and Sqlbox.

I'm working on a fix, but I've been quite busy lately, I hope to be able to finish it next week.

Regards,

Alex

On Fri, Nov 27, 2009 at 7:11 PM, Bruno Aguirre <brunoaguirrerissio@...> wrote:

Hi to all!.
I'm having some sort of issues using sqlbox, in a test enviroment i'm loosing 50% of the mos. In a graphical way:

   SMPPSim <----->      Bearerbox     <---->    Sqlbox       <-----> Smsbox <-------> HTTP
- Inyect 100Mos -       - Receives 100mos -       - Inserts 50mos -    - Sent 50 mts -    - Inyect 50 mts -

I'm using the SQLBox from the cvs, also i've correct the patch from Limit per cycle for this version, at first i thought that was my implementation the mistake then i've switched to the lastest cvs and the bug was already there.

My config:

1 ###############################################################
2 #                                 #
3 #         CORE CONFIG - Extended Config Setup                 #
4 #                                                             #
5 ###############################################################
6
7 group = core
8 admin-port = 13000
9 # Administration Port
10 admin-password = @dM1nMe
11 # Administration Password
12 admin-deny-ip = "*.*.*.*"
13 # Deny all ips for Administrate
14 admin-allow-ip = "127.0.0.1"
15 # Allow only this IPs, semicolon separated
16 smsbox-port = 13010
17 # Smsbox connection Port
18 wapbox-port = 13020
19 # Wapbox connection Port
20 wdp-interface-name = "*"
21 # UDP BroadCast
22 log-level = 0
23 # Verbose level, 0 More debug... 4 Less debug
24 log-file = "/var/log/kannel/bearerbox.log"
25 # Log file path
26 box-deny-ip = "*.*.*.*"
27 # Deny All Ips to connect to Bearerbox
28 box-allow-ip = "127.0.0.1"
29 # Allow only this Ips , semicolon separated
30 dlr-storage = mysql
31 # Where to store temp DLR data, internal default, Mysql recomended
32 store-type = spool
33 # Store type, block file is default, spool is one file per message
34 store-location = "/var/spool/kannel"
35 # Folder location of the spool
36
37 ###############################################################
38 #                                 #
39 #      MYSQL CONFIG - DLR Temp Storage                    #
40 #                                 #
41 ###############################################################
42
43 group = mysql-connection
44 id = mydlr
45 # Identification
46 host = 127.0.0.1
47 # IP of the MYSQL Database
48 port = 3306
49 # Port of the MYSQL Database
50 username = root
51 # Username of the connection
52 password = mysql
53 # Pasword of the connection
54 database = kannel
55 # Database name
56 max-connections = 50
57 # Maximun Concurrent conections

58
59 group = dlr-db
60 id = mydlr
61 # Identification
62 table = dlr
63 # Table Name
64 field-smsc = smsc
65 # Smsc Field Name
66 field-timestamp = ts
67 # Timestamp Field Name
68 field-destination = destination
69 # Destination Field Name
70 field-source = source
71 # Source Field Name
72 field-service = service
73 # Service Field Name
74 field-url = url
75 # Url Field Name
76 field-mask = mask
77 # Dlr Mask Field Name
78 field-status = status
79 # Status Field Name
80 field-boxc-id = box
81 # Box Id Field Name
82
83 group = smpp-tlv
84 name   = MAS_APP_ID
85 smsc-id = "debug"
86 tag    = 0x1401
87 type   = nulterminated
88 length = 4
89
90
91 ###############################################################
92 #                                 #
93 #      SMSBOX CONFIG - Handle SQLBox Instance             #
94 #                                                             #
95 ###############################################################
96
97 group = smsbox
98 #smsbox-id = smsbox
99 # Identification
100 bearerbox-host = localhost
101 #bearerbox-port = 13030
102 # Ip to the Bearerbox
103 sendsms-port = 13013
104 # Available port for SMS inyection
105 log-file = "/var/log/kannel/smsbox.log"
106 # Log file path
107 log-level = 0
108 # Verbose level, 0 More debug... 4 Less debug
109 #http-request-retry = 10
110 # Retry for the http request
111 #http-queue-delay = 30
112 # Delay per Retry
113
114 ###############################################################
115 #                                     #
116 #      WAPBOX CONFIG - Wap Gateway Main config            #
117 #                                     #
118 ###############################################################
119
120 group           = wapbox
121 bearerbox-host = 127.0.0.1
122 # Bearerbox IP
123 log-file        = "/var/log/kannelX1/wapbox.log"
124 # Log file path
125 log-level       = 4
126 # Verbose level, 0 More debug... 4 Less debug
127 syslog-level    = none
128 # Log in syslog
129
130 ###############################################################
131 #                                 #
132 #     PUSH PROXY GATEWAY - WapPush inyection              #
133 #                                 #
134 ###############################################################
135
136 group             = ppg
137 ppg-url           = /wappush
138 # Route in the inyection
139 ppg-port          = 8080
140 # Port for inyection
141 concurrent-pushes = 100
142 # Concurrency
143 users             = 1024
144 # Total users connected
145 ppg-allow-ip      = "127.0.0.1"
146 # Allow only this Ips , semicolon separated
147 trusted-pi        = true
148 # Trust by default
149 service-name      = ppg1
150 # Service name
151
152 group           = wap-push-user
153 wap-push-user   = wappush
154 # User for the inyection
155 ppg-username    = foo
156 # Username for the inyection
157 ppg-password    = bar
158 # Password
159 allow-ip        = "127.0.0.1"
160 # Allow only this Ips , semicolon separated
161
162 ###############################################################
163 #                                 #
164 #       SEND SMS - Send messages configuration            #
165 #                                 #
166 ###############################################################
167
168 group = sendsms-user
169 username = tester
170 # Username for the inyection
171 password = foobar
172 # Password For the inyection
173 user-deny-ip = "*.*.*.*"
174 # Deny All IPs
175 user-allow-ip = "127.0.0.1"
176 # Allow only this Ips , semicolon separated
177
178 ###############################################################
179 #                                 #
180 #       SEND SMS ROUTING - Send Messages routing          #
181 #                                 #
182 ###############################################################
183
184 group           = sms-service
185 keyword         = default
186 catch-all       = true
187 # Catch All
188 omit-empty      = true
189 # Omit Empty response
190 max-messages    = 10
191 #max-messages    = 0
192 # Dont send MTs synchronously
193 get-url         = "http://localhost:8090/mo?smsc_id=%i&short_code=%P&phone=%p&message=%a"
194 #text = "OK"
195 # URL to invoke ( README for constants )
196
197 ###############################################################
198 #                                 #
199 #       SMSCS CONFIG - Carrier Specific Config        #
200 #                                 #
201 ###############################################################
202
203 include = "/etc/kannel/smsc/debug/carriers.conf"

1 ###############################################################
2 #                                 #
3 #       SQLBOX CONFIG - Full status storage and Queueing #
4 #                                 #
5 ###############################################################
6
7 group = sqlbox
8 id = sqlbox
9 # Config Identification
10 #smsbox-id = chunkerbox
11 # Identification
12 bearerbox-host = localhost
13 # Bearerbox IP
14 bearerbox-port = 13010
15 # Bearerbox Port
16 smsbox-port = 13030
17 # Send Sms box ( From kannel core config )
18 #limit-per-cycle = 1
19 # SELECT limit
20 smsbox-port-ssl = false
21 # Usses SSL?
22 sql-log-table = sent_sms
23 # Sent Sms Table name
24 sql-insert-table = send_sms
25 # Queueing Sms Table name
26 log-file = "/var/log/kannel/sqlbox.log"
27 # Log File name
28 log-level = 0
29 # Log Verbosity
30
31 group = mysql-connection
32 id = sqlbox
33 # Identification
34 host = 127.0.0.1
35 # Database IP
36 port = 3306
37 # Database Port
38 username = root
39 # Username ( Grant CREATE )
40 password = mysql
41 # Password
42 database = kannel
43 # Database name
44 max-connections = 10

From forum: Kannel - User

Re: SQLBox Issues and Limit per cycle SQLBox patch

2009-11-27T10:44:44Z

There seems to be an issue with latest CVS'es (with meta-data) and Sqlbox.

I'm working on a fix, but I've been quite busy lately, I hope to be able to finish it next week.

Regards,

Alex

On Fri, Nov 27, 2009 at 7:11 PM, Bruno Aguirre <brunoaguirrerissio@...> wrote:

Hi to all!.
I'm having some sort of issues using sqlbox, in a test enviroment i'm loosing 50% of the mos. In a graphical way:

   SMPPSim <----->      Bearerbox     <---->    Sqlbox       <-----> Smsbox <-------> HTTP
- Inyect 100Mos -       - Receives 100mos -       - Inserts 50mos -    - Sent 50 mts -    - Inyect 50 mts -

I'm using the SQLBox from the cvs, also i've correct the patch from Limit per cycle for this version, at first i thought that was my implementation the mistake then i've switched to the lastest cvs and the bug was already there.

My config:

1 ###############################################################
2 #                                 #
3 #         CORE CONFIG - Extended Config Setup                 #
4 #                                                             #
5 ###############################################################
6
7 group = core
8 admin-port = 13000
9 # Administration Port
10 admin-password = @dM1nMe
11 # Administration Password
12 admin-deny-ip = "*.*.*.*"
13 # Deny all ips for Administrate
14 admin-allow-ip = "127.0.0.1"
15 # Allow only this IPs, semicolon separated
16 smsbox-port = 13010
17 # Smsbox connection Port
18 wapbox-port = 13020
19 # Wapbox connection Port
20 wdp-interface-name = "*"
21 # UDP BroadCast
22 log-level = 0
23 # Verbose level, 0 More debug... 4 Less debug
24 log-file = "/var/log/kannel/bearerbox.log"
25 # Log file path
26 box-deny-ip = "*.*.*.*"
27 # Deny All Ips to connect to Bearerbox
28 box-allow-ip = "127.0.0.1"
29 # Allow only this Ips , semicolon separated
30 dlr-storage = mysql
31 # Where to store temp DLR data, internal default, Mysql recomended
32 store-type = spool
33 # Store type, block file is default, spool is one file per message
34 store-location = "/var/spool/kannel"
35 # Folder location of the spool
36
37 ###############################################################
38 #                                 #
39 #      MYSQL CONFIG - DLR Temp Storage                    #
40 #                                 #
41 ###############################################################
42
43 group = mysql-connection
44 id = mydlr
45 # Identification
46 host = 127.0.0.1
47 # IP of the MYSQL Database
48 port = 3306
49 # Port of the MYSQL Database
50 username = root
51 # Username of the connection
52 password = mysql
53 # Pasword of the connection
54 database = kannel
55 # Database name
56 max-connections = 50
57 # Maximun Concurrent conections

58
59 group = dlr-db
60 id = mydlr
61 # Identification
62 table = dlr
63 # Table Name
64 field-smsc = smsc
65 # Smsc Field Name
66 field-timestamp = ts
67 # Timestamp Field Name
68 field-destination = destination
69 # Destination Field Name
70 field-source = source
71 # Source Field Name
72 field-service = service
73 # Service Field Name
74 field-url = url
75 # Url Field Name
76 field-mask = mask
77 # Dlr Mask Field Name
78 field-status = status
79 # Status Field Name
80 field-boxc-id = box
81 # Box Id Field Name
82
83 group = smpp-tlv
84 name   = MAS_APP_ID
85 smsc-id = "debug"
86 tag    = 0x1401
87 type   = nulterminated
88 length = 4
89
90
91 ###############################################################
92 #                                 #
93 #      SMSBOX CONFIG - Handle SQLBox Instance             #
94 #                                                             #
95 ###############################################################
96
97 group = smsbox
98 #smsbox-id = smsbox
99 # Identification
100 bearerbox-host = localhost
101 #bearerbox-port = 13030
102 # Ip to the Bearerbox
103 sendsms-port = 13013
104 # Available port for SMS inyection
105 log-file = "/var/log/kannel/smsbox.log"
106 # Log file path
107 log-level = 0
108 # Verbose level, 0 More debug... 4 Less debug
109 #http-request-retry = 10
110 # Retry for the http request
111 #http-queue-delay = 30
112 # Delay per Retry
113
114 ###############################################################
115 #                                     #
116 #      WAPBOX CONFIG - Wap Gateway Main config            #
117 #                                     #
118 ###############################################################
119
120 group           = wapbox
121 bearerbox-host = 127.0.0.1
122 # Bearerbox IP
123 log-file        = "/var/log/kannelX1/wapbox.log"
124 # Log file path
125 log-level       = 4
126 # Verbose level, 0 More debug... 4 Less debug
127 syslog-level    = none
128 # Log in syslog
129
130 ###############################################################
131 #                                 #
132 #     PUSH PROXY GATEWAY - WapPush inyection              #
133 #                                 #
134 ###############################################################
135
136 group             = ppg
137 ppg-url           = /wappush
138 # Route in the inyection
139 ppg-port          = 8080
140 # Port for inyection
141 concurrent-pushes = 100
142 # Concurrency
143 users             = 1024
144 # Total users connected
145 ppg-allow-ip      = "127.0.0.1"
146 # Allow only this Ips , semicolon separated
147 trusted-pi        = true
148 # Trust by default
149 service-name      = ppg1
150 # Service name
151
152 group           = wap-push-user
153 wap-push-user   = wappush
154 # User for the inyection
155 ppg-username    = foo
156 # Username for the inyection
157 ppg-password    = bar
158 # Password
159 allow-ip        = "127.0.0.1"
160 # Allow only this Ips , semicolon separated
161
162 ###############################################################
163 #                                 #
164 #       SEND SMS - Send messages configuration            #
165 #                                 #
166 ###############################################################
167
168 group = sendsms-user
169 username = tester
170 # Username for the inyection
171 password = foobar
172 # Password For the inyection
173 user-deny-ip = "*.*.*.*"
174 # Deny All IPs
175 user-allow-ip = "127.0.0.1"
176 # Allow only this Ips , semicolon separated
177
178 ###############################################################
179 #                                 #
180 #       SEND SMS ROUTING - Send Messages routing          #
181 #                                 #
182 ###############################################################
183
184 group           = sms-service
185 keyword         = default
186 catch-all       = true
187 # Catch All
188 omit-empty      = true
189 # Omit Empty response
190 max-messages    = 10
191 #max-messages    = 0
192 # Dont send MTs synchronously
193 get-url         = "http://localhost:8090/mo?smsc_id=%i&short_code=%P&phone=%p&message=%a"
194 #text = "OK"
195 # URL to invoke ( README for constants )
196
197 ###############################################################
198 #                                 #
199 #       SMSCS CONFIG - Carrier Specific Config        #
200 #                                 #
201 ###############################################################
202
203 include = "/etc/kannel/smsc/debug/carriers.conf"

1 ###############################################################
2 #                                 #
3 #       SQLBOX CONFIG - Full status storage and Queueing #
4 #                                 #
5 ###############################################################
6
7 group = sqlbox
8 id = sqlbox
9 # Config Identification
10 #smsbox-id = chunkerbox
11 # Identification
12 bearerbox-host = localhost
13 # Bearerbox IP
14 bearerbox-port = 13010
15 # Bearerbox Port
16 smsbox-port = 13030
17 # Send Sms box ( From kannel core config )
18 #limit-per-cycle = 1
19 # SELECT limit
20 smsbox-port-ssl = false
21 # Usses SSL?
22 sql-log-table = sent_sms
23 # Sent Sms Table name
24 sql-insert-table = send_sms
25 # Queueing Sms Table name
26 log-file = "/var/log/kannel/sqlbox.log"
27 # Log File name
28 log-level = 0
29 # Log Verbosity
30
31 group = mysql-connection
32 id = sqlbox
33 # Identification
34 host = 127.0.0.1
35 # Database IP
36 port = 3306
37 # Database Port
38 username = root
39 # Username ( Grant CREATE )
40 password = mysql
41 # Password
42 database = kannel
43 # Database name
44 max-connections = 10

From forum: Kannel - User

SQLBox Issues and Limit per cycle SQLBox patch

2009-11-27T10:11:23Z

Hi to all!.
I'm having some sort of issues using sqlbox, in a test enviroment i'm loosing 50% of the mos. In a graphical way:

   SMPPSim <----->      Bearerbox     <---->    Sqlbox       <-----> Smsbox <-------> HTTP
- Inyect 100Mos -       - Receives 100mos -       - Inserts 50mos -    - Sent 50 mts -    - Inyect 50 mts -

I'm using the SQLBox from the cvs, also i've correct the patch from Limit per cycle for this version, at first i thought that was my implementation the mistake then i've switched to the lastest cvs and the bug was already there.

My config:

1 ###############################################################
2 #                                 #
3 #         CORE CONFIG - Extended Config Setup                 #
4 #                                                             #
5 ###############################################################
6
7 group = core
8 admin-port = 13000
9 # Administration Port
10 admin-password = @dM1nMe
11 # Administration Password
12 admin-deny-ip = "*.*.*.*"
13 # Deny all ips for Administrate
14 admin-allow-ip = "127.0.0.1"
15 # Allow only this IPs, semicolon separated
16 smsbox-port = 13010
17 # Smsbox connection Port
18 wapbox-port = 13020
19 # Wapbox connection Port
20 wdp-interface-name = "*"
21 # UDP BroadCast
22 log-level = 0
23 # Verbose level, 0 More debug... 4 Less debug
24 log-file = "/var/log/kannel/bearerbox.log"
25 # Log file path
26 box-deny-ip = "*.*.*.*"
27 # Deny All Ips to connect to Bearerbox
28 box-allow-ip = "127.0.0.1"
29 # Allow only this Ips , semicolon separated
30 dlr-storage = mysql
31 # Where to store temp DLR data, internal default, Mysql recomended
32 store-type = spool
33 # Store type, block file is default, spool is one file per message
34 store-location = "/var/spool/kannel"
35 # Folder location of the spool
36
37 ###############################################################
38 #                                 #
39 #      MYSQL CONFIG - DLR Temp Storage                    #
40 #                                 #
41 ###############################################################
42
43 group = mysql-connection
44 id = mydlr
45 # Identification
46 host = 127.0.0.1
47 # IP of the MYSQL Database
48 port = 3306
49 # Port of the MYSQL Database
50 username = root
51 # Username of the connection
52 password = mysql
53 # Pasword of the connection
54 database = kannel
55 # Database name
56 max-connections = 50
57 # Maximun Concurrent conections

58
59 group = dlr-db
60 id = mydlr
61 # Identification
62 table = dlr
63 # Table Name
64 field-smsc = smsc
65 # Smsc Field Name
66 field-timestamp = ts
67 # Timestamp Field Name
68 field-destination = destination
69 # Destination Field Name
70 field-source = source
71 # Source Field Name
72 field-service = service
73 # Service Field Name
74 field-url = url
75 # Url Field Name
76 field-mask = mask
77 # Dlr Mask Field Name
78 field-status = status
79 # Status Field Name
80 field-boxc-id = box
81 # Box Id Field Name
82
83 group = smpp-tlv
84 name   = MAS_APP_ID
85 smsc-id = "debug"
86 tag    = 0x1401
87 type   = nulterminated
88 length = 4
89
90
91 ###############################################################
92 #                                 #
93 #      SMSBOX CONFIG - Handle SQLBox Instance             #
94 #                                                             #
95 ###############################################################
96
97 group = smsbox
98 #smsbox-id = smsbox
99 # Identification
100 bearerbox-host = localhost
101 #bearerbox-port = 13030
102 # Ip to the Bearerbox
103 sendsms-port = 13013
104 # Available port for SMS inyection
105 log-file = "/var/log/kannel/smsbox.log"
106 # Log file path
107 log-level = 0
108 # Verbose level, 0 More debug... 4 Less debug
109 #http-request-retry = 10
110 # Retry for the http request
111 #http-queue-delay = 30
112 # Delay per Retry
113
114 ###############################################################
115 #                                     #
116 #      WAPBOX CONFIG - Wap Gateway Main config            #
117 #                                     #
118 ###############################################################
119
120 group           = wapbox
121 bearerbox-host = 127.0.0.1
122 # Bearerbox IP
123 log-file        = "/var/log/kannelX1/wapbox.log"
124 # Log file path
125 log-level       = 4
126 # Verbose level, 0 More debug... 4 Less debug
127 syslog-level    = none
128 # Log in syslog
129
130 ###############################################################
131 #                                 #
132 #     PUSH PROXY GATEWAY - WapPush inyection              #
133 #                                 #
134 ###############################################################
135
136 group             = ppg
137 ppg-url           = /wappush
138 # Route in the inyection
139 ppg-port          = 8080
140 # Port for inyection
141 concurrent-pushes = 100
142 # Concurrency
143 users             = 1024
144 # Total users connected
145 ppg-allow-ip      = "127.0.0.1"
146 # Allow only this Ips , semicolon separated
147 trusted-pi        = true
148 # Trust by default
149 service-name      = ppg1
150 # Service name
151
152 group           = wap-push-user
153 wap-push-user   = wappush
154 # User for the inyection
155 ppg-username    = foo
156 # Username for the inyection
157 ppg-password    = bar
158 # Password
159 allow-ip        = "127.0.0.1"
160 # Allow only this Ips , semicolon separated
161
162 ###############################################################
163 #                                 #
164 #       SEND SMS - Send messages configuration            #
165 #                                 #
166 ###############################################################
167
168 group = sendsms-user
169 username = tester
170 # Username for the inyection
171 password = foobar
172 # Password For the inyection
173 user-deny-ip = "*.*.*.*"
174 # Deny All IPs
175 user-allow-ip = "127.0.0.1"
176 # Allow only this Ips , semicolon separated
177
178 ###############################################################
179 #                                 #
180 #       SEND SMS ROUTING - Send Messages routing          #
181 #                                 #
182 ###############################################################
183
184 group           = sms-service
185 keyword         = default
186 catch-all       = true
187 # Catch All
188 omit-empty      = true
189 # Omit Empty response
190 max-messages    = 10
191 #max-messages    = 0
192 # Dont send MTs synchronously
193 get-url         = "http://localhost:8090/mo?smsc_id=%i&short_code=%P&phone=%p&message=%a"
194 #text = "OK"
195 # URL to invoke ( README for constants )
196
197 ###############################################################
198 #                                 #
199 #       SMSCS CONFIG - Carrier Specific Config        #
200 #                                 #
201 ###############################################################
202
203 include = "/etc/kannel/smsc/debug/carriers.conf"

1 ###############################################################
2 #                                 #
3 #       SQLBOX CONFIG - Full status storage and Queueing #
4 #                                 #
5 ###############################################################
6
7 group = sqlbox
8 id = sqlbox
9 # Config Identification
10 #smsbox-id = chunkerbox
11 # Identification
12 bearerbox-host = localhost
13 # Bearerbox IP
14 bearerbox-port = 13010
15 # Bearerbox Port
16 smsbox-port = 13030
17 # Send Sms box ( From kannel core config )
18 #limit-per-cycle = 1
19 # SELECT limit
20 smsbox-port-ssl = false
21 # Usses SSL?
22 sql-log-table = sent_sms
23 # Sent Sms Table name
24 sql-insert-table = send_sms
25 # Queueing Sms Table name
26 log-file = "/var/log/kannel/sqlbox.log"
27 # Log File name
28 log-level = 0
29 # Log Verbosity
30
31 group = mysql-connection
32 id = sqlbox
33 # Identification
34 host = 127.0.0.1
35 # Database IP
36 port = 3306
37 # Database Port
38 username = root
39 # Username ( Grant CREATE )
40 password = mysql
41 # Password
42 database = kannel
43 # Database name
44 max-connections = 10

From forum: Kannel - User

Re: Two Basic Questions, Please?

2009-11-27T10:06:58Z

Thank you very much, Nikos, for your reply. I have learned more from your responses.

If anyone on the list could point me to a resource or a basic tutorial on the installation of Kannel and the various options and requirements to achieve sms messaging, I would appreciate that very much.

In the meantime, I will keep digging ..

Best regards,

David

--- On Fri, 27/11/09, Nikos Balkanas <nbal@...> wrote:

From: Nikos Balkanas <nbal@...>
Subject: Re: Two Basic Questions, Please?
To: "David Halliday" <tetrahall@...>, "Kannel Users" <users@...>
Date: Friday, 27 November, 2009, 2:32

Hi,

Yes, a GSM modem (or a bank of those) are fully supported by kannel. I have no clue what is the volume restriction, it depends solely on your operator. I just use dedicated SMSc links, but some other guys in the list have more experience with it. Bear in mind that in both cases the final step is an SMSc. The only difference is that with a GSM modem, the SMSc is your provider's responsibility.

BR,

Nikos

----- Original Message -----

From: David Halliday

To: Kannel Users

Sent: Friday, November 27, 2009 3:18 AM

Subject: Re: Two Basic Questions, Please?

Hi Nikos,

Many thanks for your repsonse. It is really useful.

Before actually sending my enquiry to this list, I had done some searchig for a while on google, and I understood that the only way to send sms message to recepints is by going through an SMS Centre for the dsetination network.

In your reply, you mentioned as an option:

Application -> Kannel -> GSM modem

Can it really be done that way - *bypassing* the SMS centre?

And if yes, what is considered as "low volume"? Would 1000 messages per day be 'OK' with a sim card provider?

And of course, it all depends on the destination network. Real SS7 connections may not be an option.

I would appreciate your advice.

Best regards

David

--- On Thu, 26/11/09, Nikos Balkanas <nbal@...> wrote:

From: Nikos Balkanas <nbal@...>
Subject: Re: Two Basic Questions, Please?
To: "David Halliday" <tetrahall@...>, "Kannel Users" <users@...>
Date: Thursday, 26 November, 2009, 1:27

Hi,

1) To push SMS you will need:

Application -> Kannel -> GSM modem

-or-

Application -> Kannel -> SMSc link

Application is some kind of web interface to facilitate and schedule pushes. Optionally you can substitute one of kannel's components, smsbox, with SQLbox for sending bulk.

GSM modem provides for a low volume, cheaper usually interface using a SIM card. But volume is restricted else SIM maybe disabled. SMSc provides for a more reliable interface, however, throughput is restricted according to your contract. Volume is unlimited (of course you are charged for each SMS). You can also shop around to get the lowest price globally, whereas with a SIM you are restricted by what your operator gives you.

2) Cost depends on your volume and destination. If Clickatell is an aggeragator, ie routes SMS to other SMScs, you can do better than them. If, however, they have real SS7 connections, given their volume, it is unlikely.

BR,

Nikos

----- Original Message -----

From: David Halliday

To: Kannel Users

Sent: Wednesday, November 25, 2009 9:54 PM

Subject: Two Basic Questions, Please?

Hello,

I have windows xp on my pc, and am very interested in Kannel.

Before installing Linux and going through the whole process, I would like to know, if possible, please:-

1. To send sms messages, what else would one need apart from:-

Kannel + GSM modem + SMSC connectivity (for recepients' network)

Anything else apart from the above 3 'components'?

2. Would that arrangement be actually cheaper than to go through some bulk SMS suppliers like Clickatell, for example? I think it should, but I am not sure.

I would greatly appreciate an answer.

Best regards,

David

From forum: Kannel - User

Re: SMPP data_sm implementation for MT messages

2009-11-27T07:04:29Z

where do you have message_payload extracted to user?

that is simple:

MT(data_sm) -> sendsms?text=ABC&metadata=?smpp?pdu_type=data_sm... -> data_sm.message_payload=ABC
MT(submit_sm) -> sendsms?text=ABC... -> submit_sm.short_message=ABC

MO(data_sm) -> data_sm.message_payload=ABC -> receivesms?text=ABC&metadata=?smpp?pdu_type=data_sm
MO(submit_sm) -> submit_sm.short_message=ABC -> receivesms?text=ABC

If user set for MT text=ABC&metadata=?smpp?pdu_type=data_sm&message_payload=XXX then it's undefined and
we are free to choose which one to use and I would prefer to use text as message_payload...

Hope that's clear.

Thanks,
Alexander Malysh

Am 27.11.2009 um 15:21 schrieb Michael Zervakis:

>
> Let's assume that we follow Alex's recommendation "meta-data=?smpp?operation=data_sm&..." and if operation is omitted we use submit_sm as default.
>
>
> We should clarify what should happen to "text=xxxx" if set and this should affect both submit_sm and data_sm operations as SMPP specs state that short_message and message_payload cannot coexist in a PDU (sm_length should be zero if message_payload is used). I can think of three cases here:
>
> 1) When "text" has a value and "message_payload" is not set. For submit_sm no need to change anything. For data_sm we append meta-data with message_payload and set the value of "text" to it (example: "text=XXXX&meta-data=?smpp?operation=data_sm").
> 2) When both "text" and "message_payload" have values. For submit_sm operation "text" value is set to null (so "sm_length" is set to 0 and we don't break specs) and we use the provided "message_payload" value. For data_sm operation we simply ignore "text" value.
>
> 3) When "message_payload" has a value and "text" is not set. Normal case doesn't break specs.
>
>
>
>
>
>> -----Original Message-----
>> From: Alexander Malysh [mailto:malysh00@...] On Behalf Of
> Alexander Malysh
>> Sent: Friday, November 27, 2009 3:32 PM
>> To: Michael Zervakis
>> Cc: devel@...; aguerrieri@...
>> Subject: Re: SMPP data_sm implementation for MT messages
>
>
>> Hi,
>
>
>> why not just use metadata=?smpp?operation=data_sm&... ?
>
>> then you can check in smsc_smpp whether submit_sm or data_sm should be used.
>
>
>> Whether you have to use message_payload or short_message is
> implementation details that
>
>> should not be exported to user interface.
>
>
>> Thanks,
>
>> Alexander Malysh
>
>
>> Am 27.11.2009 um 13:00 schrieb Michael Zervakis:
>
>
>> > Data_sm PDU cannot contain a short_message field. Actually data_sm
> contains only TLVs and instead of "short_message" field we should use TLV "message_payload" to send text. As a result text=xxxx is obsolete when sending data_sm PDU. If we use data=xxxx what would be the value of data since all necessary data will be included in "meta-data=?smpp?" ?
>
>> >
>
>> >
>
>> >> -----Original Message-----
>
>> >> From: Alejandro Guerrieri [mailto:aguerrieri@...]
>
>> >> Sent: Friday, November 27, 2009 12:04 PM
>
>> >> To: Michael Zervakis
>
>> >> Cc: devel@...
>
>> >> Subject: Re: SMPP data_sm implementation for MT messages
>
>> >
>
>> >
>
>> > >What about using "data=xxxx" instead of "text=xxxx" ?
>
>> >
>
>> > >--
>
>> >
>
>> > >Alejandro Guerrieri
>
>> >
>
>> > >aguerrieri@...
>
>> >
>
>> > >
>
>> > >
>
>> > >
>
>> > >On 27/11/2009, at 10:00, Michael Zervakis wrote:
>
>> >
>
>> > >
>
>> > >> Data_sm can be used as an alternate of submit_sm when transmitting
>
>> > >> optional parameters (meta-data) and some carriers require the use of
>
>> > >> data_sm for MT charging applications.
>
>> >
>
>> > >> Since Kannel is not implementing this feature it's a good idea to
>
>> > >> start a discussion on how this could be implemented.
>
>> >
>
>> > >>
>
>> > >> First of all it's obvious that "static int send_messages()" at gw
>
>> >
>
>> > >> \smsc\smsc_smpp.c must be able to differentiate msgs that need to be
>
>> > >> sent as data_sm.
>
>> >
>
>> > >> I can think of two ways to achieve this:
>
>> >
>
>> > >> 1) Alter MSG definition to inlcude a new parameter that defines type
>
>> > >> of message Data or normal SMS
>
>> >
>
>> > >> Possible ways to use the new parameter could be the following
>
>> >
>
>> > >> /cgi-bin/sendsms?from=1111&to=2222&<new parameter>=data&meta-data=?
>
>> >
>
>> > >> smpp?key=value
>
>> >
>
>> > >> /cgi-bin/senddata?from=1111&to=2222&meta-data=?smpp?key=value
>
>> >
>
>> > >> 2) Leave MSG definition untouched and use meta-data to mark msg as
>
>> > >> data
>
>> >
>
>> > >> /cgi-bin/sendsms?from=1111&to=2222&meta-data=?smpp?<new
>
>> > >> parameter>=data&key=value
>
>> >
>
>> > >>
>
>> > >> Finally a new function has to be defined at gw\smsc\smsc_smpp.c to
>
>> > >> build data_sm pdu from msg for example "static SMPP_PDU
>
>> > >> *dmsg_to_pdu(SMPP *smpp, Msg *msg)"
>
>> >
>
>> > >> and function "static int handle_pdu()" at gw\smsc\smsc_smpp.c has to
>
>> > >> be modified to include a case for data_sm_resp PDU.
>
>> >
>
>> > >>
>
>> > >> Any comments?
>
>> >
>
>> > >>
>
>> > >>
>
>> >
>
>

From forum: Kannel - Dev

RE: SMPP data_sm implementation for MT messages

2009-11-27T06:21:49Z

Let's assume that we follow Alex's recommendation
"meta-data=?smpp?operation=data_sm&..." and if operation is omitted we
use submit_sm as default.

We should clarify what should happen to "text=xxxx" if set and this
should affect both submit_sm and data_sm operations as SMPP specs state
that short_message and message_payload cannot coexist in a PDU
(sm_length should be zero if message_payload is used). I can think of
three cases here:

1) When "text" has a value and "message_payload" is not set. For
submit_sm no need to change anything. For data_sm we append meta-data
with message_payload and set the value of "text" to it (example:
"text=XXXX&meta-data=?smpp?operation=data_sm").
2) When both "text" and "message_payload" have values. For submit_sm
operation "text" value is set to null (so "sm_length" is set to 0 and we
don't break specs) and we use the provided "message_payload" value. For
data_sm operation we simply ignore "text" value.

3) When "message_payload" has a value and "text" is not set. Normal case
doesn't break specs.

>-----Original Message-----
>From: Alexander Malysh [mailto:malysh00@...] On Behalf Of
Alexander Malysh
>Sent: Friday, November 27, 2009 3:32 PM
>To: Michael Zervakis
>Cc: devel@...; aguerrieri@...
>Subject: Re: SMPP data_sm implementation for MT messages

>

>Hi,

>

>why not just use metadata=?smpp?operation=data_sm&... ?

>then you can check in smsc_smpp whether submit_sm or data_sm should be used.

>

>Whether you have to use message_payload or short_message is
implementation details that

>should not be exported to user interface.

>

>Thanks,

>Alexander Malysh

>

>Am 27.11.2009 um 13:00 schrieb Michael Zervakis:

>

> > Data_sm PDU cannot contain a short_message field. Actually data_sm
contains only TLVs and instead of "short_message" field we should use
TLV "message_payload" to send text. As a result text=xxxx is obsolete
when sending data_sm PDU. If we use data=xxxx what would be the value of
data since all necessary data will be included in "meta-data=?smpp?" ?

> >

> >

> >> -----Original Message-----

> >> From: Alejandro Guerrieri [mailto:aguerrieri@...]

> >> Sent: Friday, November 27, 2009 12:04 PM

> >> To: Michael Zervakis

> >> Cc: devel@...

> >> Subject: Re: SMPP data_sm implementation for MT messages

> >

> >

> > >What about using "data=xxxx" instead of "text=xxxx" ?

> >

> > >--

> >

> > >Alejandro Guerrieri

> >

> > >aguerrieri@...

> >

> > >

> > >

> > >

> > >On 27/11/2009, at 10:00, Michael Zervakis wrote:

> >

> > >

> > >> Data_sm can be used as an alternate of submit_sm when transmitting

> > >> optional parameters (meta-data) and some carriers require the use of

> > >> data_sm for MT charging applications.

> >

> > >> Since Kannel is not implementing this feature it's a good idea to

> > >> start a discussion on how this could be implemented.

> >

> > >>

> > >> First of all it's obvious that "static int send_messages()" at gw

> >

> > >> \smsc\smsc_smpp.c must be able to differentiate msgs that need to be

> > >> sent as data_sm.

> >

> > >> I can think of two ways to achieve this:

> >

> > >> 1) Alter MSG definition to inlcude a new parameter that defines type

> > >> of message Data or normal SMS

> >

> > >> Possible ways to use the new parameter could be the following

> >

> > >> /cgi-bin/sendsms?from=1111&to=2222&<new parameter>=data&meta-data=?

> >

> > >> smpp?key=value

> >

> > >> /cgi-bin/senddata?from=1111&to=2222&meta-data=?smpp?key=value

> >

> > >> 2) Leave MSG definition untouched and use meta-data to mark msg as

> > >> data

> >

> > >> /cgi-bin/sendsms?from=1111&to=2222&meta-data=?smpp?<new

> > >> parameter>=data&key=value

> >

> > >>

> > >> Finally a new function has to be defined at gw\smsc\smsc_smpp.c to

> > >> build data_sm pdu from msg for example "static SMPP_PDU

> > >> *dmsg_to_pdu(SMPP *smpp, Msg *msg)"

> >

> > >> and function "static int handle_pdu()" at gw\smsc\smsc_smpp.c has to

> > >> be modified to include a case for data_sm_resp PDU.

> >

> > >>

> > >> Any comments?

> >

> > >>

> > >>

> >

>

From forum: Kannel - Dev

Re: gsm-7 encoding

2009-11-27T05:33:01Z

Hi,

see gw/smsc/smsc_at.c

Thanks,
Alexander Malysh

Am 27.11.2009 um 05:32 schrieb Paco:

> Hello, according to 3GPP TS 23.038 the gsm-7 characters should be coded as septets and padding bits should be used when the message has an UDH, but I can't find this code on kannel. Could someone please point to me where this packing and unpacking is done? It seems that they are sent as octets.
>
> Thanks

From forum: Kannel - Dev

Re: SMPP data_sm implementation for MT messages

2009-11-27T05:32:09Z

Hi,

why not just use metadata=?smpp?operation=data_sm&... ?
then you can check in smsc_smpp whether submit_sm or data_sm should be used.

Whether you have to use message_payload or short_message is implementation details that
should not be exported to user interface.

Thanks,
Alexander Malysh

Am 27.11.2009 um 13:00 schrieb Michael Zervakis:

> Data_sm PDU cannot contain a short_message field. Actually data_sm contains only TLVs and instead of "short_message" field we should use TLV "message_payload" to send text. As a result text=xxxx is obsolete when sending data_sm PDU. If we use data=xxxx what would be the value of data since all necessary data will be included in "meta-data=?smpp?" ?
>
>
>> -----Original Message-----
>> From: Alejandro Guerrieri [mailto:aguerrieri@...]
>> Sent: Friday, November 27, 2009 12:04 PM
>> To: Michael Zervakis
>> Cc: devel@...
>> Subject: Re: SMPP data_sm implementation for MT messages
>
>
> >What about using "data=xxxx" instead of "text=xxxx" ?
>
> >--
>
> >Alejandro Guerrieri
>
> >aguerrieri@...
>
> >
> >
> >
> >On 27/11/2009, at 10:00, Michael Zervakis wrote:
>
> >
> >> Data_sm can be used as an alternate of submit_sm when transmitting
> >> optional parameters (meta-data) and some carriers require the use of
> >> data_sm for MT charging applications.
>
> >> Since Kannel is not implementing this feature it's a good idea to
> >> start a discussion on how this could be implemented.
>
> >>
> >> First of all it's obvious that "static int send_messages()" at gw
>
> >> \smsc\smsc_smpp.c must be able to differentiate msgs that need to be
> >> sent as data_sm.
>
> >> I can think of two ways to achieve this:
>
> >> 1) Alter MSG definition to inlcude a new parameter that defines type
> >> of message Data or normal SMS
>
> >> Possible ways to use the new parameter could be the following
>
> >> /cgi-bin/sendsms?from=1111&to=2222&<new parameter>=data&meta-data=?
>
> >> smpp?key=value
>
> >> /cgi-bin/senddata?from=1111&to=2222&meta-data=?smpp?key=value
>
> >> 2) Leave MSG definition untouched and use meta-data to mark msg as
> >> data
>
> >> /cgi-bin/sendsms?from=1111&to=2222&meta-data=?smpp?<new
> >> parameter>=data&key=value
>
> >>
> >> Finally a new function has to be defined at gw\smsc\smsc_smpp.c to
> >> build data_sm pdu from msg for example "static SMPP_PDU
> >> *dmsg_to_pdu(SMPP *smpp, Msg *msg)"
>
> >> and function "static int handle_pdu()" at gw\smsc\smsc_smpp.c has to
> >> be modified to include a case for data_sm_resp PDU.
>
> >>
> >> Any comments?
>
> >>
> >>
>

From forum: Kannel - Dev

RE: SMPP data_sm implementation for MT messages

2009-11-27T04:00:45Z

Data_sm PDU cannot contain a short_message field. Actually data_sm
contains only TLVs and instead of "short_message" field we should use
TLV "message_payload" to send text. As a result text=xxxx is obsolete
when sending data_sm PDU. If we use data=xxxx what would be the value of
data since all necessary data will be included in "meta-data=?smpp?" ?

>-----Original Message-----
>From: Alejandro Guerrieri [mailto:aguerrieri@...]
>Sent: Friday, November 27, 2009 12:04 PM
>To: Michael Zervakis
>Cc: devel@...
>Subject: Re: SMPP data_sm implementation for MT messages

>

>What about using "data=xxxx" instead of "text=xxxx" ?

>--

>Alejandro Guerrieri

>aguerrieri@...

>

>

>

>On 27/11/2009, at 10:00, Michael Zervakis wrote:

>

>> Data_sm can be used as an alternate of submit_sm when transmitting

>> optional parameters (meta-data) and some carriers require the use of

>> data_sm for MT charging applications.

>> Since Kannel is not implementing this feature it's a good idea to

>> start a discussion on how this could be implemented.

>>

>> First of all it's obvious that "static int send_messages()" at gw

>> \smsc\smsc_smpp.c must be able to differentiate msgs that need to be

>> sent as data_sm.

>> I can think of two ways to achieve this:

>> 1) Alter MSG definition to inlcude a new parameter that defines type

>> of message Data or normal SMS

>> Possible ways to use the new parameter could be the following

>> /cgi-bin/sendsms?from=1111&to=2222&<new parameter>=data&meta-data=?

>> smpp?key=value

>> /cgi-bin/senddata?from=1111&to=2222&meta-data=?smpp?key=value

>> 2) Leave MSG definition untouched and use meta-data to mark msg as

>> data

>> /cgi-bin/sendsms?from=1111&to=2222&meta-data=?smpp?<new

>> parameter>=data&key=value

>>

>> Finally a new function has to be defined at gw\smsc\smsc_smpp.c to

>> build data_sm pdu from msg for example "static SMPP_PDU

>> *dmsg_to_pdu(SMPP *smpp, Msg *msg)"

>> and function "static int handle_pdu()" at gw\smsc\smsc_smpp.c has to

>> be modified to include a case for data_sm_resp PDU.

>>

>> Any comments?

>>

>>

From forum: Kannel - Dev

Re: SMPP data_sm implementation for MT messages

2009-11-27T02:03:45Z

What about using "data=xxxx" instead of "text=xxxx" ?
--
Alejandro Guerrieri
aguerrieri@...

On 27/11/2009, at 10:00, Michael Zervakis wrote:

> Data_sm can be used as an alternate of submit_sm when transmitting
> optional parameters (meta-data) and some carriers require the use of
> data_sm for MT charging applications.
> Since Kannel is not implementing this feature it's a good idea to
> start a discussion on how this could be implemented.
>
> First of all it's obvious that "static int send_messages()" at gw
> \smsc\smsc_smpp.c must be able to differentiate msgs that need to be
> sent as data_sm.
> I can think of two ways to achieve this:
> 1) Alter MSG definition to inlcude a new parameter that defines type
> of message Data or normal SMS
> Possible ways to use the new parameter could be the following
> /cgi-bin/sendsms?from=1111&to=2222&<new parameter>=data&meta-data=?
> smpp?key=value
> /cgi-bin/senddata?from=1111&to=2222&meta-data=?smpp?key=value
> 2) Leave MSG definition untouched and use meta-data to mark msg as
> data
> /cgi-bin/sendsms?from=1111&to=2222&meta-data=?smpp?<new
> parameter>=data&key=value
>
> Finally a new function has to be defined at gw\smsc\smsc_smpp.c to
> build data_sm pdu from msg for example "static SMPP_PDU
> *dmsg_to_pdu(SMPP *smpp, Msg *msg)"
> and function "static int handle_pdu()" at gw\smsc\smsc_smpp.c has to
> be modified to include a case for data_sm_resp PDU.
>
> Any comments?
>
>

From forum: Kannel - Dev

SMPP data_sm implementation for MT messages

2009-11-27T01:00:13Z

Data_sm can be used as an alternate of submit_sm when transmitting
optional parameters (meta-data) and some carriers require the use of
data_sm for MT charging applications.
Since Kannel is not implementing this feature it's a good idea to start
a discussion on how this could be implemented.

First of all it's obvious that "static int send_messages()" at
gw\smsc\smsc_smpp.c must be able to differentiate msgs that need to be
sent as data_sm.
I can think of two ways to achieve this:
1) Alter MSG definition to inlcude a new parameter that defines type of
message Data or normal SMS
Possible ways to use the new parameter could be the following
/cgi-bin/sendsms?from=1111&to=2222&<new
parameter>=data&meta-data=?smpp?key=value
/cgi-bin/senddata?from=1111&to=2222&meta-data=?smpp?key=value
2) Leave MSG definition untouched and use meta-data to mark msg as data
/cgi-bin/sendsms?from=1111&to=2222&meta-data=?smpp?<new
parameter>=data&key=value

Finally a new function has to be defined at gw\smsc\smsc_smpp.c to build
data_sm pdu from msg for example "static SMPP_PDU *dmsg_to_pdu(SMPP
*smpp, Msg *msg)"
and function "static int handle_pdu()" at gw\smsc\smsc_smpp.c has to be
modified to include a case for data_sm_resp PDU.

Any comments?

From forum: Kannel - Dev

gsm-7 encoding

2009-11-26T20:32:24Z

Hello, according to 3GPP TS 23.038 the gsm-7 characters should be coded as septets and padding bits should be used when the message has an UDH, but I can't find this code on kannel. Could someone please point to me where this packing and unpacking is done? It seems that they are sent as octets.

Thanks

From forum: Kannel - Dev

Re: Two Basic Questions, Please?

2009-11-26T18:32:02Z

Hi,

Yes, a GSM modem (or a bank of those) are fully supported by kannel. I have no clue what is the volume restriction, it depends solely on your operator. I just use dedicated SMSc links, but some other guys in the list have more experience with it. Bear in mind that in both cases the final step is an SMSc. The only difference is that with a GSM modem, the SMSc is your provider's responsibility.

BR,

Nikos

----- Original Message -----

From: tetrahall@...

To: users@...

Sent: Friday, November 27, 2009 3:18 AM

Subject: Re: Two Basic Questions, Please?

Hi Nikos,

Many thanks for your repsonse. It is really useful.

Before actually sending my enquiry to this list, I had done some searchig for a while on google, and I understood that the only way to send sms message to recepints is by going through an SMS Centre for the dsetination network.

In your reply, you mentioned as an option:

Application -> Kannel -> GSM modem

Can it really be done that way - *bypassing* the SMS centre?

And if yes, what is considered as "low volume"? Would 1000 messages per day be 'OK' with a sim card provider?

And of course, it all depends on the destination network. Real SS7 connections may not be an option.

I would appreciate your advice.

Best regards

David

--- On Thu, 26/11/09, Nikos Balkanas <nbal@...> wrote:

From: Nikos Balkanas <nbal@...>
Subject: Re: Two Basic Questions, Please?
To: "David Halliday" <tetrahall@...>, "Kannel Users" <users@...>
Date: Thursday, 26 November, 2009, 1:27

Hi,

1) To push SMS you will need:

Application -> Kannel -> GSM modem

-or-

Application -> Kannel -> SMSc link

Application is some kind of web interface to facilitate and schedule pushes. Optionally you can substitute one of kannel's components, smsbox, with SQLbox for sending bulk.

GSM modem provides for a low volume, cheaper usually interface using a SIM card. But volume is restricted else SIM maybe disabled. SMSc provides for a more reliable interface, however, throughput is restricted according to your contract. Volume is unlimited (of course you are charged for each SMS). You can also shop around to get the lowest price globally, whereas with a SIM you are restricted by what your operator gives you.

2) Cost depends on your volume and destination. If Clickatell is an aggeragator, ie routes SMS to other SMScs, you can do better than them. If, however, they have real SS7 connections, given their volume, it is unlikely.

BR,

Nikos

----- Original Message -----

From: David Halliday

To: Kannel Users

Sent: Wednesday, November 25, 2009 9:54 PM

Subject: Two Basic Questions, Please?

Hello,

I have windows xp on my pc, and am very interested in Kannel.

Before installing Linux and going through the whole process, I would like to know, if possible, please:-

1. To send sms messages, what else would one need apart from:-

Kannel + GSM modem + SMSC connectivity (for recepients' network)

Anything else apart from the above 3 'components'?

2. Would that arrangement be actually cheaper than to go through some bulk SMS suppliers like Clickatell, for example? I think it should, but I am not sure.

I would greatly appreciate an answer.

Best regards,

David

From forum: Kannel - User

Re: Two Basic Questions, Please?

2009-11-26T17:18:26Z

Hi Nikos,

Many thanks for your repsonse. It is really useful.

Before actually sending my enquiry to this list, I had done some searchig for a while on google, and I understood that the only way to send sms message to recepints is by going through an SMS Centre for the dsetination network.

In your reply, you mentioned as an option:

Application -> Kannel -> GSM modem

Can it really be done that way - *bypassing* the SMS centre?

And if yes, what is considered as "low volume"? Would 1000 messages per day be 'OK' with a sim card provider?

And of course, it all depends on the destination network. Real SS7 connections may not be an option.

I would appreciate your advice.

Best regards

David

--- On Thu, 26/11/09, Nikos Balkanas <nbal@...> wrote:

From: Nikos Balkanas <nbal@...>
Subject: Re: Two Basic Questions, Please?
To: "David Halliday" <tetrahall@...>, "Kannel Users" <users@...>
Date: Thursday, 26 November, 2009, 1:27

Hi,

1) To push SMS you will need:

Application -> Kannel -> GSM modem

-or-

Application -> Kannel -> SMSc link

Application is some kind of web interface to facilitate and schedule pushes. Optionally you can substitute one of kannel's components, smsbox, with SQLbox for sending bulk.

GSM modem provides for a low volume, cheaper usually interface using a SIM card. But volume is restricted else SIM maybe disabled. SMSc provides for a more reliable interface, however, throughput is restricted according to your contract. Volume is unlimited (of course you are charged for each SMS). You can also shop around to get the lowest price globally, whereas with a SIM you are restricted by what your operator gives you.

2) Cost depends on your volume and destination. If Clickatell is an aggeragator, ie routes SMS to other SMScs, you can do better than them. If, however, they have real SS7 connections, given their volume, it is unlikely.

BR,

Nikos

----- Original Message -----

From: David Halliday

To: Kannel Users

Sent: Wednesday, November 25, 2009 9:54 PM

Subject: Two Basic Questions, Please?

Hello,

I have windows xp on my pc, and am very interested in Kannel.

Before installing Linux and going through the whole process, I would like to know, if possible, please:-

1. To send sms messages, what else would one need apart from:-

Kannel + GSM modem + SMSC connectivity (for recepients' network)

Anything else apart from the above 3 'components'?

2. Would that arrangement be actually cheaper than to go through some bulk SMS suppliers like Clickatell, for example? I think it should, but I am not sure.

I would greatly appreciate an answer.

Best regards,

David

From forum: Kannel - User

Re: Kannel special sharacters encodig problem

2009-11-26T14:44:17Z

Hi Franco from the other side of the "charco"!!! :)

Did you check with the carrier what character encoding they are using?
You should set alt-charset on your SMSC config to the one that the
carrier is using.

Besides that, I would not recommend supporting accents... not only
some carriers may not support them, but also some phones may not
support them either... even there are phones that configured in
English language don't show accents and in Spanish they do, so there
are lots of factors that could end up with a bad user experience...

Moreover, when you use accents and "ñ" or others, the message is sent
using unicode, so the MT will be able to use less than 160 characters

I always stick to English characters

Hope it helps,

Regards,

Juan

On Thu, Nov 26, 2009 at 2:38 PM, pogui <poguijuaz@...> wrote:

> Hi im Franco from Argentina,
> I have a big problem with the words in incomming SMS's that have "tildes"
> (for example: á é í ó ú )
> Kannel breaks the entire SMS this way:
>
> Original SMS: "TEST acá"
> Message get: "żTżEżSżTż żażcżaż?"
>
> Then i activate the "mo-rencode" option, and the message got was: "TEST
> żażcżaż?". This way the keyword is ok.
> Any ideas?
>
> thx
>
>

--
Juan Nin
3Cinteractive / Mobilizing Great Brands
http://www.3cinteractive.com

From forum: Kannel - User

Kannel special sharacters encodig problem

2009-11-26T08:38:37Z

Hi im Franco from Argentina,
I have a big problem with the words in incomming SMS's that have
"tildes" (for example: á é í ó ú )
Kannel breaks the entire SMS this way:

Original SMS: "TEST acá"
Message get: "¿T¿E¿S¿T¿ ¿a¿c¿a¿?"

Then i activate the "mo-rencode" option, and the message got was: "TEST
¿a¿c¿a¿?". This way the keyword is ok.
Any ideas?

thx

From forum: Kannel - User

Re: DLR counters on the status page

2009-11-26T05:06:33Z

From a discussion on Tera-WURFL on the wmlprogramming mailing list I
know that since PHP 5.3.0 short_open_tag is disabled by default

On Thu, Nov 26, 2009 at 8:25 AM, Alejandro Guerrieri
<aguerrieri@...> wrote:

> I guess what Vincent means is that short_open_tag may be removed completely
> at future versions, and in fact right now it's not recommended at all
> because it might be disabled on some installations.
>
> I'll commit a patch with those fixes and also a couple color changes Vincent
> also suggested.
>
> Regards,
> --
> Alejandro Guerrieri
> aguerrieri@...
>
>
>
> On 26/11/2009, at 11:00, Andreas Fink wrote:
>
>> php version >= 6.0??
>> thats not existing yet.
>>
>>
>> On 25.11.2009, at 14:37, Vincent CHAVANIS wrote:
>>
>>> Hi,
>>>
>>> You have short_open_tag "<?" on index.php & xmltoarray.php
>>> And *shouldn't* be like this as described in the php guidelines
>>> for further php releases (eg. >= php 6.0)
>>>
>>> Could you please fix this asap?
>>>
>>> Then, i think we have to make a default working config
>>> for people who just want to quickly test this contrib.
>>>
>>> $configs = array(
>>> array( "base_url" => "http://127.0.0.1:13000",
>>> "status_passwd" => "foo",
>>> "admin_passwd" => "bar",
>>> "name" => "Kannel default"
>>> ),
>>> );
>>>
>>> Also, you can also credit yourself ;-)
>>> as you re-wrote the script.
>>>
>>> Thanks
>>>
>>> Vincent.
>>>
>>>
>>> Alejandro Guerrieri a écrit :
>>>>
>>>> Commited to CVS.
>>>> Regards,
>>>> --
>>>> Alejandro Guerrieri
>>>> aguerrieri@...
>>>> On 24/11/2009, at 12:14, Alexander Malysh wrote:
>>>>>
>>>>> Alex, could you please commit this patch?
>>>>>
>>>>> Thanks,
>>>>> Alexander Malysh
>>>>>
>>>>> Am 17.11.2009 um 20:40 schrieb Alejandro Guerrieri:
>>>>>
>>>>>> Please find a zip with the full folder attached.
>>>>>>
>>>>>> It's almost a full code rewrite, with lots of changes on the code
>>>>>> structure and UI as well, apart from support for the dlr fields.
>>>>>>
>>>>>> I'm working on a completely new, "ajaxified" version as well, stay
>>>>>> tuned ;)
>>>>>>
>>>>>> Regards,
>>>>>> --
>>>>>> Alejandro Guerrieri
>>>>>> aguerrieri@...
>>>>>>
>>>>>> <kannel-monitor.zip>
>>>>>> On 15/11/2009, at 15:44, Alexander Malysh wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> @Alex: any news about kannel-monitor patch?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Alexander Malysh
>>>>>>>
>>>>>>> Am 11.11.2009 um 19:47 schrieb Alejandro Guerrieri:
>>>>>>>
>>>>>>>> Working on it already, it'll be ready for tomorrow probably.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> --
>>>>>>>> Alejandro Guerrieri
>>>>>>>> aguerrieri@...
>>>>>>>>
>>>
>>>
>>
>>
>>
>
>
>

--
Juan Nin
3Cinteractive / Mobilizing Great Brands
http://www.3cinteractive.com

From forum: Kannel - Dev

Re: How to Make URL based Carrier Server using Kannel like jatayu

2009-11-26T02:36:06Z

I have implemented what you are asking.

Third parties, or users having respective usernames and password connects to my proxy via HTTP (XML), inserting their sms to my db. After, I pick them up from db and push through kannel http interface. THis is applied for both MO and MT.

For sure you need to develop some extra interface.

On Wed, Nov 18, 2009 at 2:08 PM, Henri Hovi <henri.hovi@...> wrote:

Or use the sqlbox to inject the messages instead of the HTTP
connection from script to Kannel...

On Wed, Nov 18, 2009 at 3:06 PM, Henri Hovi <henri.hovi@...> wrote:
> Hi,
>
> now Your question has some sense...
>
> If You must use database, the easiest way would be to do some
> front-end script which receives the messages, authenticates the users
> and manages the statistics, then one common account to Kannel where
> the messages are forwarded. Anyhow, this ight be too much overhead if
> You have a lot of traffic.
>
> Another option requires You to change Kannel to use database to store
> and collect such information and that can be pretty big job.
>
> --
> Henri
>
>
>
> On Wed, Nov 18, 2009 at 2:58 PM, Amritesh Rachelwar
> <amriteshsmsc@...> wrote:
>> Dear,
>>
>> Actually we are interested to make one URL, using which any one can send SMS
>> having a specific username and password using internet. We need to maintain
>> database for them all that how many SMS they have sent and time, destination
>> no etc. So i need to configure the kannel for a no of username and password
>> and need to maintain database separately according to username.
>>
>> Thanks and Regards
>> Amritesh Deepak Rachelwar
>>
>>
>> 2009/11/18 Nikos Balkanas <nbal@...>
>>>
>>> Hi,
>>>
>>> I presume you are talking about push SMS (MT) messages. Sendsms users are
>>> not kept in a database, but in the configuration guide. Please read about
>>> group sendsms-user in the User Guide.
>>>
>>> BR,
>>> Nikos
>>>
>>> ----- Original Message -----
>>> From: Amritesh Rachelwar
>>> To: users
>>> Sent: Wednesday, November 18, 2009 1:51 PM
>>> Subject: How to Make URL based Carrier Server using Kannel like jatayu
>>> Dear,
>>>
>>> We want to make a URL (HTTP) based Server using kannel gateway. We have
>>> one SMPP connectivity with SMSC and a Static IP. How can we create
>>> different username and passwords for all users and how to manage there data
>>> bases accordingly.
>>>
>>> Thanks and Regards
>>> Amritesh Deepak Rachelwar
>>>
>>
>>
>
>
>
> --
> Henri Hovi
> http://www.patidure.com
> http://patidure.blogspot.com
>

--
Henri Hovi
http://www.patidure.com
http://patidure.blogspot.com

From forum: Kannel - User

Re: DLR counters on the status page

2009-11-26T02:25:09Z

I guess what Vincent means is that short_open_tag may be removed
completely at future versions, and in fact right now it's not
recommended at all because it might be disabled on some installations.

I'll commit a patch with those fixes and also a couple color changes
Vincent also suggested.

Regards,
--
Alejandro Guerrieri
aguerrieri@...

On 26/11/2009, at 11:00, Andreas Fink wrote:

> php version >= 6.0??
> thats not existing yet.
>
>
> On 25.11.2009, at 14:37, Vincent CHAVANIS wrote:
>
>> Hi,
>>
>> You have short_open_tag "<?" on index.php & xmltoarray.php
>> And *shouldn't* be like this as described in the php guidelines
>> for further php releases (eg. >= php 6.0)
>>
>> Could you please fix this asap?
>>
>> Then, i think we have to make a default working config
>> for people who just want to quickly test this contrib.
>>
>> $configs = array(
>> array( "base_url" => "http://127.0.0.1:13000",
>> "status_passwd" => "foo",
>> "admin_passwd" => "bar",
>> "name" => "Kannel default"
>> ),
>> );
>>
>> Also, you can also credit yourself ;-)
>> as you re-wrote the script.
>>
>> Thanks
>>
>> Vincent.
>>
>>
>> Alejandro Guerrieri a écrit :
>>> Commited to CVS.
>>> Regards,
>>> --
>>> Alejandro Guerrieri
>>> aguerrieri@...
>>> On 24/11/2009, at 12:14, Alexander Malysh wrote:
>>>> Alex, could you please commit this patch?
>>>>
>>>> Thanks,
>>>> Alexander Malysh
>>>>
>>>> Am 17.11.2009 um 20:40 schrieb Alejandro Guerrieri:
>>>>
>>>>> Please find a zip with the full folder attached.
>>>>>
>>>>> It's almost a full code rewrite, with lots of changes on the
>>>>> code structure and UI as well, apart from support for the dlr
>>>>> fields.
>>>>>
>>>>> I'm working on a completely new, "ajaxified" version as well,
>>>>> stay tuned ;)
>>>>>
>>>>> Regards,
>>>>> --
>>>>> Alejandro Guerrieri
>>>>> aguerrieri@...
>>>>>
>>>>> <kannel-monitor.zip>
>>>>> On 15/11/2009, at 15:44, Alexander Malysh wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> @Alex: any news about kannel-monitor patch?
>>>>>>
>>>>>> Thanks,
>>>>>> Alexander Malysh
>>>>>>
>>>>>> Am 11.11.2009 um 19:47 schrieb Alejandro Guerrieri:
>>>>>>
>>>>>>> Working on it already, it'll be ready for tomorrow probably.
>>>>>>>
>>>>>>> Regards,
>>>>>>> --
>>>>>>> Alejandro Guerrieri
>>>>>>> aguerrieri@...
>>>>>>>
>>
>>
>
>
>

From forum: Kannel - Dev

Re: DLR counters on the status page

2009-11-26T02:00:32Z

php version >= 6.0??
thats not existing yet.

On 25.11.2009, at 14:37, Vincent CHAVANIS wrote:

> Hi,
>
> You have short_open_tag "<?" on index.php & xmltoarray.php
> And *shouldn't* be like this as described in the php guidelines
> for further php releases (eg. >= php 6.0)
>
> Could you please fix this asap?
>
> Then, i think we have to make a default working config
> for people who just want to quickly test this contrib.
>
> $configs = array(
> array( "base_url" => "http://127.0.0.1:13000",
> "status_passwd" => "foo",
> "admin_passwd" => "bar",
> "name" => "Kannel default"
> ),
> );
>
> Also, you can also credit yourself ;-)
> as you re-wrote the script.
>
> Thanks
>
> Vincent.
>
>
> Alejandro Guerrieri a écrit :
>> Commited to CVS.
>> Regards,
>> --
>> Alejandro Guerrieri
>> aguerrieri@...
>> On 24/11/2009, at 12:14, Alexander Malysh wrote:
>>> Alex, could you please commit this patch?
>>>
>>> Thanks,
>>> Alexander Malysh
>>>
>>> Am 17.11.2009 um 20:40 schrieb Alejandro Guerrieri:
>>>
>>>> Please find a zip with the full folder attached.
>>>>
>>>> It's almost a full code rewrite, with lots of changes on the code structure and UI as well, apart from support for the dlr fields.
>>>>
>>>> I'm working on a completely new, "ajaxified" version as well, stay tuned ;)
>>>>
>>>> Regards,
>>>> --
>>>> Alejandro Guerrieri
>>>> aguerrieri@...
>>>>
>>>> <kannel-monitor.zip>
>>>> On 15/11/2009, at 15:44, Alexander Malysh wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> @Alex: any news about kannel-monitor patch?
>>>>>
>>>>> Thanks,
>>>>> Alexander Malysh
>>>>>
>>>>> Am 11.11.2009 um 19:47 schrieb Alejandro Guerrieri:
>>>>>
>>>>>> Working on it already, it'll be ready for tomorrow probably.
>>>>>>
>>>>>> Regards,
>>>>>> --
>>>>>> Alejandro Guerrieri
>>>>>> aguerrieri@...
>>>>>>
>
>

From forum: Kannel - Dev

Re: Two Basic Questions, Please?

2009-11-25T17:27:44Z

Hi,

1) To push SMS you will need:

Application -> Kannel -> GSM modem

-or-

Application -> Kannel -> SMSc link

Application is some kind of web interface to facilitate and schedule pushes. Optionally you can substitute one of kannel's components, smsbox, with SQLbox for sending bulk.

GSM modem provides for a low volume, cheaper usually interface using a SIM card. But volume is restricted else SIM maybe disabled. SMSc provides for a more reliable interface, however, throughput is restricted according to your contract. Volume is unlimited (of course you are charged for each SMS). You can also shop around to get the lowest price globally, whereas with a SIM you are restricted by what your operator gives you.

2) Cost depends on your volume and destination. If Clickatell is an aggeragator, ie routes SMS to other SMScs, you can do better than them. If, however, they have real SS7 connections, given their volume, it is unlikely.

BR,

Nikos

----- Original Message -----

From: tetrahall@...

To: users@...

Sent: Wednesday, November 25, 2009 9:54 PM

Subject: Two Basic Questions, Please?

Hello,

I have windows xp on my pc, and am very interested in Kannel.

Before installing Linux and going through the whole process, I would like to know, if possible, please:-

1. To send sms messages, what else would one need apart from:-

Kannel + GSM modem + SMSC connectivity (for recepients' network)

Anything else apart from the above 3 'components'?

2. Would that arrangement be actually cheaper than to go through some bulk SMS suppliers like Clickatell, for example? I think it should, but I am not sure.

I would greatly appreciate an answer.

Best regards,

David

From forum: Kannel - User

Two Basic Questions, Please?

2009-11-25T11:54:01Z

Hello,

I have windows xp on my pc, and am very interested in Kannel.

Before installing Linux and going through the whole process, I would like to know, if possible, please:-

1. To send sms messages, what else would one need apart from:-

Kannel + GSM modem + SMSC connectivity (for recepients' network)

Anything else apart from the above 3 'components'?

2. Would that arrangement be actually cheaper than to go through some bulk SMS suppliers like Clickatell, for example? I think it should, but I am not sure.

I would greatly appreciate an answer.

Best regards,

David

From forum: Kannel - User

Re: WARNING: SIGHUP received, catching and re-opening logs

2009-11-25T11:42:52Z

When in doubt, sources never lie. Manuals need updating.

You probably mean logrotate, and the one you have on your server is the
correct one. However, neither version is related to your problem.

BR,
Nikos
----- Original Message -----
From: "Stephane Bruno" <mysubscriptions74@...>
To: "Nikos Balkanas" <nbal@...>
Cc: "Eduardo Anuel" <eanuel@...>; <users@...>
Sent: Wednesday, November 25, 2009 8:56 PM
Subject: Re: WARNING: SIGHUP received, catching and re-opening logs

So, what is the right version to use? The one that is in the manual
online, or the one I see installed on my server? The one I have
currently on my server says:

postrotate
killall -HUP bearerbox smsbox wapbox > /dev/null 2> /dev/null ||
true

Regards,
StΓ©phane

2009/11/24 Nikos Balkanas <nbal@...>:

> Hi,
>
> it does, but unrelated to your problem. However, the manual needs
> updating,
> sources are correct.
>
> BR,
> Nikos
> ----- Original Message ----- From: "Stephane Bruno"
> <mysubscriptions74@...>
> To: "Eduardo Anuel" <eanuel@...>
> Cc: <users@...>
> Sent: Wednesday, November 25, 2009 12:32 AM
> Subject: Re: WARNING: SIGHUP received, catching and re-opening logs
>
>
> Hello,
>
> I effectively run Debian/Lenny. But, I did apt-get install psmisc and
> I saw that it is already installed. However, when I look at my
> logrotate file for kannel, I see a difference compared to what is
> suggested in the user guide. Here is what I see in the user guide :
>
> postrotate
> Β Β Β Β Β Β Β Β Β killall -HUP bearerbox smsbox wapbox || true >
> /dev/null 2> /dev/null
>
> Here is what I have in my file:
>
> postrotate
> Β Β Β Β Β Β Β Β Β killall -HUP bearerbox smsbox wapbox > /dev/null
> 2> /dev/null || true
>
> Does that make a difference? Is it the reason of my problem?
>
> Regards,
> StΞΉphane
>
> On Tue, Nov 24, 2009 at 10:42 AM, Eduardo Anuel <eanuel@...> wrote:
>>
>> I don't know if this will help but are you sure your linux has killall
>> installed?
>> I use Debian GNU/Linux and since a few years ago Debian doesn't have
>> killall in the base installation,
>> you have to install the psmisc package after you install to get it
>> (http://www.ducea.com/2008/08/18/killall-in-debian/).
>> If killall isn't installed the SIGHUP signal is not received by kannel
>> and the logs will remain being written
>> to the file logrotate renamed instead of the new one.
>>
>> This happens to me every time I install a new server with kannel, just
>> check and see if it helps you.
>>
>> Greetings
>>
>> --
>> Think for yourself...Question Authority
>>
>>
>
>

From forum: Kannel - User

Re: WARNING: SIGHUP received, catching and re-opening logs

2009-11-25T10:56:39Z

So, what is the right version to use? The one that is in the manual
online, or the one I see installed on my server? The one I have
currently on my server says:

postrotate
killall -HUP bearerbox smsbox wapbox > /dev/null 2> /dev/null || true

Regards,
Stéphane

2009/11/24 Nikos Balkanas <nbal@...>:

> Hi,
>
> it does, but unrelated to your problem. However, the manual needs updating,
> sources are correct.
>
> BR,
> Nikos
> ----- Original Message ----- From: "Stephane Bruno"
> <mysubscriptions74@...>
> To: "Eduardo Anuel" <eanuel@...>
> Cc: <users@...>
> Sent: Wednesday, November 25, 2009 12:32 AM
> Subject: Re: WARNING: SIGHUP received, catching and re-opening logs
>
>
> Hello,
>
> I effectively run Debian/Lenny. But, I did apt-get install psmisc and
> I saw that it is already installed. However, when I look at my
> logrotate file for kannel, I see a difference compared to what is
> suggested in the user guide. Here is what I see in the user guide :
>
> postrotate
> killall -HUP bearerbox smsbox wapbox || true >
> /dev/null 2> /dev/null
>
> Here is what I have in my file:
>
> postrotate
> killall -HUP bearerbox smsbox wapbox > /dev/null
> 2> /dev/null || true
>
> Does that make a difference? Is it the reason of my problem?
>
> Regards,
> Stιphane
>
> On Tue, Nov 24, 2009 at 10:42 AM, Eduardo Anuel <eanuel@...> wrote:
>>
>> I don't know if this will help but are you sure your linux has killall
>> installed?
>> I use Debian GNU/Linux and since a few years ago Debian doesn't have
>> killall in the base installation,
>> you have to install the psmisc package after you install to get it
>> (http://www.ducea.com/2008/08/18/killall-in-debian/).
>> If killall isn't installed the SIGHUP signal is not received by kannel
>> and the logs will remain being written
>> to the file logrotate renamed instead of the new one.
>>
>> This happens to me every time I install a new server with kannel, just
>> check and see if it helps you.
>>
>> Greetings
>>
>> --
>> Think for yourself...Question Authority
>>
>>
>
>

From forum: Kannel - User

Re: DLR counters on the status page

2009-11-25T05:37:44Z

Hi,

You have short_open_tag "<?" on index.php & xmltoarray.php
And *shouldn't* be like this as described in the php guidelines
for further php releases (eg. >= php 6.0)

Could you please fix this asap?

Then, i think we have to make a default working config
for people who just want to quickly test this contrib.

$configs = array(
array( "base_url" => "http://127.0.0.1:13000",
"status_passwd" => "foo",
"admin_passwd" => "bar",
"name" => "Kannel default"
),
);

Also, you can also credit yourself ;-)
as you re-wrote the script.

Thanks

Vincent.

Alejandro Guerrieri a écrit :

> Commited to CVS.
>
> Regards,
> --
> Alejandro Guerrieri
> aguerrieri@...
>
>
>
> On 24/11/2009, at 12:14, Alexander Malysh wrote:
>
>> Alex, could you please commit this patch?
>>
>> Thanks,
>> Alexander Malysh
>>
>> Am 17.11.2009 um 20:40 schrieb Alejandro Guerrieri:
>>
>>> Please find a zip with the full folder attached.
>>>
>>> It's almost a full code rewrite, with lots of changes on the code
>>> structure and UI as well, apart from support for the dlr fields.
>>>
>>> I'm working on a completely new, "ajaxified" version as well, stay
>>> tuned ;)
>>>
>>> Regards,
>>> --
>>> Alejandro Guerrieri
>>> aguerrieri@...
>>>
>>> <kannel-monitor.zip>
>>> On 15/11/2009, at 15:44, Alexander Malysh wrote:
>>>
>>>> Hi,
>>>>
>>>> @Alex: any news about kannel-monitor patch?
>>>>
>>>> Thanks,
>>>> Alexander Malysh
>>>>
>>>> Am 11.11.2009 um 19:47 schrieb Alejandro Guerrieri:
>>>>
>>>>> Working on it already, it'll be ready for tomorrow probably.
>>>>>
>>>>> Regards,
>>>>> --
>>>>> Alejandro Guerrieri
>>>>> aguerrieri@...
>>>>>

From forum: Kannel - Dev

Re: memory leak in octstr_imm

2009-11-25T04:55:55Z

Yeap. But be careful. Immutables are not released before the end. It is a
very bad idea to use them in recurring functions. That's why the only place
they are used is in initialization & configuration.

BR,
Nikos
----- Original Message -----
From: "Alejandro Guerrieri" <aguerrieri@...>
To: "Dilan Anuruddha" <dilanmrt@...>
Cc: <devel@...>
Sent: Wednesday, November 25, 2009 1:23 PM
Subject: Re: memory leak in octstr_imm

>I don't think so, immutables are kept in memory until the process
>finishes. That's by design.
>
> Read the comments on gwlib/octstr.h, there's an explanation about it
> there.
>
> Regards,
> --
> Alejandro Guerrieri
> aguerrieri@...
>
>
>
> On 25/11/2009, at 12:04, Dilan Anuruddha wrote:
>
>> Hi all,
>> I've been using kannel libraries for a campus project. When we
>> create Octstr objects using octstr_imm (e.g. when we pass arguments to a
>> function), we don't release the memory.... Isn't this leaking memory???
>> So do we have to explicitly release memory inside the function????
>>
>> thanks in advance,
>> Dilan
>

From forum: Kannel - Dev