Re: Bug in Kannel Response Status codes

[Kirti Mandwade]

Hi Andreas,

Thanks for your response .

I have allowed all smsc that are used in the allowed-smsc-id parameter,
there are no entries in denied-smsc-id.

For example for fake smsc I am using :
smsc = fake
smsc-id = fake1

and allowed that smsc  in the kannel configuration.
allowed-smsc-id = fake1


Please suggest me what else should be done in this case.
Regards
Kirti

On Mon, Sep 28, 2015 at 2:48 PM, Andreas Fink <af...@list.fink.org> wrote:

> one possible reason for this is that kannel has an alternate route.
> how does your allowed-smsc-id / denied-smsc-id entries look like?
>
> On 28 Sep 2015, at 11:07, Kirti Mandwade <kirti.mandw...@gmail.com> wrote:
>
>
> Hello All,
>
> Kannel does not give expected status codes when an smsc is down, stopped
> or removed.
>
> Here is what I did.
> 1) I ran smsc-stop command :
> lynx -dump "
> http://localhost:13000/stop-smsc?password=admin-password=smsc-name;
>
> 2)Then i tried sending SMS and it gave me
>
> 202 Accepted status from Kannel
>
> 3) In the bearer box it gave :
> WARNING: Cannot find SMSCConn for message to <27800...>, rejected.
> 2015-09-09 15:38:42 [20697] [13] DEBUG: SMSC[UNKNOWN]: creating DLR message
> 2015-09-09 15:38:42 [20697] [13] WARNING: Message rejected by bearerbox,
> no router!
>
>
> Then tried smsc-remove command
>   lynx -dump "
> http://localhost:13000/remove-smsc?password=admin-password=smsc-name;
>
> and sent message.
>
> According to Kannel
> Kannel svn-r5114 User's Guide.
>
>
> http://www.kannel.org/download/kannel-userguide-snapshot/userguide.html#AEN910
>
> I should have got -  202 3: Queued for later delivery
>
> but I got 202 Accepted status with the same error in the bearerbox
>
> After that I tried removing confirguration for the smsc from directory
> that Kannel looks for from the include statement and restarted kannel and
> sent SMS
>
> Even after that i got the same results 202 Accepted status from Kannel and
> error in bearerbox.
>
>
> Kannel should not give Accepted status if that SMSC is stopped, removed or
> does not exist but Kannel accepts it and rejects the message in bearerbox.
> If Kannel will not respond with any other status then no one can find out
> that messages were not sent and smsc was down or does not exist.
>
> Here is my redmine link
> https://redmine.kannel.org/issues/744
>
> Please look into this issue.
>
> Regards
> Kirti
>
>
>

Re: patch to allow data_coding to be set to 3

[Kirti Mandwade]

Hi Andreas,

Thanks for the quick response.

Even if i use utf8 charset then also all special characters allowed by GSM
7 are not getting sent properly.
I am url encoding everything before sending as per kannel document.
Can you suggest me how to send all GSM7 allowed special characters properly.

Regards



On Wed, Oct 7, 2015 at 6:54 PM, Andreas Fink  wrote:

> theres no need for having the SMSC do the latin1 to GSM transcoding as
> kannel already does this.
> you feed kannel with latin1 or utf8 and kannel will make GSM out of it
> automatically.
>
> What matters at the end is what the handset receives and the GSM character
> set is hardcoded in billions of phones. You can not send latin1 to phones
> but you can send the GSM character set to phones which has a few more chars
> than IA5 by now (by the use of some escape sequence they added things like
> | { } if I remember correctly). And in GSM things are slightly differnet as
> @ for example is encoded as 0x00.
>
> Kannel does the conversion from whatever you feed it with to the GSM
> character set. There is no need to set coding value for this. This is only
> needed if you want to send raw bytes to kannel (and thus disable the
> internal conversion) for example when you send binary data.
>
> So the key is to have your character set properly set in your http request
> header. Kannel defaults to UTF8. So when you feed latin1 characters to
> kannel, they should be translated already correctly to GSM and have the DCS
> values set correctly.
>
> Its nice that Vodacom's SMSC has a *_proprietary_* extension to do the
>  conversion in the SMSC but Kannel doesn't need it to operate correctly.
>
> On 07 Oct 2015, at 15:12, hbil...@ecommunicate.biz wrote:
>
> Hi Alex,
>
> From this thread that you responded to see
> http://www.kannel.org/pipermail/users/2012-April/017611.html and the
> current
> user guide, it seems Kannel has never allowed data_coding to be set to 3.
> See  the coding parameter in the current spec
>
> http://www.kannel.org/download/kannel-userguide-snapshot/userguide.html#AEN5
> 058
> Coding Accepts values 0 to 2, for 7bit, 8bit or UCS-2.
> 0 causes data_coding 0 (for 7bit), 1 causes data_coding 4 (for 8bit) and 2
> causes data_coding 8 (for UCS-2).
>
> Vodacom SA which has the largest mobile network in SA, has said to send the
> Extended GSM characters, we need to use Latin-1 characters and set our
> data_coding field to 3 to tell the SMSC to translate the characters from
> Latin-1 to GSM. (Note that standard ASCII and IA5 is a sub set of Latin-1.)
> However, need to be able to send the extended GSM characters using 7 bits
> without using Unicode as otherwise each SMS would then only be 70
> characters
> and our clients would require many more SMSs to send the same message.
>
> Do you have a patch, that will allow Kannel users to set the coding
> parameter to 3?
> If not, would you be open to someone committing a patch for this?
>
> Thanks for all the amazing work you do for Kannel.
>
> Kind Regards
>
> Hillel Bilman
> Manager eCommunicate
> mailto: hbil...@ecommunicate.co.za
> Cell: 083-232
> Landline: 011-443-6164
> Fax: 088-011-443-6164
>
> Mobile Wallets  - .mobi Sites – Mobile Apps(Android, iPhone, Blackberry,
> Nokia) -  Premium Rated SMSs and short codes - SMS competitions and
> campaigns – Lead Generation - opt-in subscription Billing – MMS campaigns -
> USSD campaigns - WAP - Outlook SMS – Bulk SMS and Bulk Email – Email 2 SMS
> 2
> Email - Developer Kit for Mobile Services integration - Voice Over IP
> services
>
>
>
>
>

Fwd: Bug in Kannel Response Status codes

[Kirti Mandwade]

Hello All,

Kannel does not give expected status codes when an smsc is down, stopped or
removed.

Here is what I did.
1) I ran smsc-stop command :
lynx -dump "
http://localhost:13000/stop-smsc?password=admin-password=smsc-name;

2)Then i tried sending SMS and it gave me

202 Accepted status from Kannel

3) In the bearer box it gave :
WARNING: Cannot find SMSCConn for message to <27800...>, rejected.
2015-09-09 15:38:42 [20697] [13] DEBUG: SMSC[UNKNOWN]: creating DLR message
2015-09-09 15:38:42 [20697] [13] WARNING: Message rejected by bearerbox, no
router!


Then tried smsc-remove command
  lynx -dump "
http://localhost:13000/remove-smsc?password=admin-password=smsc-name;

and sent message.

According to Kannel
Kannel svn-r5114 User's Guide.

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

I should have got -  202 3: Queued for later delivery

but I got 202 Accepted status with the same error in the bearerbox

After that I tried removing confirguration for the smsc from directory that
Kannel looks for from the include statement and restarted kannel and sent
SMS

Even after that i got the same results 202 Accepted status from Kannel and
error in bearerbox.


Kannel should not give Accepted status if that SMSC is stopped, removed or
does not exist but Kannel accepts it and rejects the message in bearerbox.
If Kannel will not respond with any other status then no one can find out
that messages were not sent and smsc was down or does not exist.

Here is my redmine link
https://redmine.kannel.org/issues/744

Please look into this issue.

Regards
Kirti

Bug in Kannel Response Status codes

[Kirti Mandwade]

Hello All,

Kannel does not give expected status codes when an smsc is down, stopped or
removed.

Here is what I did.
1) I ran smsc-stop command :
lynx -dump "
http://localhost:13000/stop-smsc?password=admin-password=smsc-name;

2)Then i tried sending SMS and it gave me

202 Accepted status from Kannel

3) In the bearer box it gave :
WARNING: Cannot find SMSCConn for message to <27800...>, rejected.
2015-09-09 15:38:42 [20697] [13] DEBUG: SMSC[UNKNOWN]: creating DLR message
2015-09-09 15:38:42 [20697] [13] WARNING: Message rejected by bearerbox, no
router!


Then tried smsc-remove command
  lynx -dump "
http://localhost:13000/remove-smsc?password=admin-password=smsc-name;

and sent message.

According to Kannel
Kannel svn-r5114 User's Guide.

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

I should have got -  202 3: Queued for later delivery

but I got 202 Accepted status with the same error in the bearerbox

After that I tried removing confirguration for the smsc from directory that
Kannel looks for from the include statement and restarted kannel and sent
SMS

Even after that i got the same results 202 Accepted status from Kannel and
error in bearerbox.


Kannel should not give Accepted status if that SMSC is stopped, removed or
does not exist but Kannel accepts it and rejects the message in bearerbox.
If Kannel will not respond with any other status then no one can find out
that messages were not sent and smsc was down or does not exist.

Please look into this issue.

Regards
Kirti

X-kannel Headers not working.

[Kirti Mandwade]

Hello,

Is support to X-kannel Headers removed as when I try sending SMS with
X-kannel Headers using HTTP POST it gives me Authorization failed.
Here is what I am doing.

 String url = http://u.v.w.x:13003/cgi-bin/sendsms;;

  CloseableHttpClient httpClient = HttpClients.createDefault();
  HttpPost httpPost = new HttpPost(url);
  httpPost.setHeader(content-type, text/plain);
  CloseableHttpResponse response = null;
  StringEntity entity = null;
  List NameValuePair headers = new ArrayList NameValuePair();
  headers.add(new BasicNameValuePair(X-Kannel-Username, abc));
  headers.add(new BasicNameValuePair(X-Kannel-Password, 123));
  headers.add(new BasicNameValuePair(X-Kannel-From, abc123abc));
  headers.add(new BasicNameValuePair(X-Kannel-To, 27813234));
  headers.add(new BasicNameValuePair(X-Kannel-SMSC, send));

entity = new StringEntity(hello, ContentType.create(
text/plain));


httpPost.setEntity(new UrlEncodedFormEntity(headers));
httpPost.setEntity(entity);




   response = httpClient.execute(httpPost);
 System.out.println(response.getStatusLine());

  EntityUtils.consume(entity);



I have set accept-x-kannel headers to true in sms-service group of kannel
configuration

group = sms-service
accept-x-kannel-headers = true


Sending SMS using POST method with XML is working perfectly I am using
Kannel svn-r5114 User's Guide.Please let me know if this feature has been
removed or there is something wrong in the way i am doing it.Thanks
Kirti

Re: Bug in admin interface for parameter remove-message

[Kirti Mandwade]

Hi Alex,


Thankyou for that correction its working now by using UUID of each message.

But is there any way by which we can remove messages sent to one smsc for
example

http://127.0.0.1:13000/remove-message?smsc=xyz?password=

 http://127.0.0.1:13000/remove-message?id=UUID?password=

Or deleting messages in queue regarding one smsc

kannel_admin/delete-queue?smsc=XX

There must be some criteria or conditions to delete different messages
rather then deleting all at once or removing one by one.

Kindly look into this issue

Thanks,

Kirti



On Tue, Jun 9, 2015 at 8:54 PM, Alexander Malysh amal...@kannel.org wrote:

 Hi,

 see comment in redmine and try to fix your URL.

 Alex

 Am 28.05.2015 um 11:26 schrieb Kirti Mandwade kirti.mandw...@gmail.com:

 Hello,

 From the latest user guide 
 http://www.kannel.org/download/kannel-userguide-snapshot/userguide.html#AEN926
 remove-message Removes the message with the give id (an UUID) from the local 
 storage
 subsystem.

 But this is not working.
 I need to remove specific message from kannel queue and i am testing it by
 using fakesmsc.

 Here is my redmine link:
 *https://redmine.kannel.org/issues/718
 https://redmine.kannel.org/issues/718*

 Thanks
 Kirti

Bug in admin interface for parameter remove-message

[Kirti Mandwade]

Hello,

From the latest user guide
http://www.kannel.org/download/kannel-userguide-snapshot/userguide.html#AEN926
remove-message Removes the message with the give id (an UUID) from
the local storage
subsystem.

But this is not working.
I need to remove specific message from kannel queue and i am testing it by
using fakesmsc.

Here is my redmine link:
*https://redmine.kannel.org/issues/718
https://redmine.kannel.org/issues/718*

Thanks
Kirti

Fwd: How to remove messages from Kannel local subsystem using UUID

[Kirti Mandwade]

Hello,

I need to remove specific message from kannel queue and i am testing it by
using fakesmsc.

So far what i did is:
1) I used this command to check the status of various smsc.This works fine

lynx -dump http://127.0.0.1:xxx/status?password=;

2) I took down fakesmsc and sent 10 sms.

3) I used the following command to check the queue.
lynx -dump http://127.0.0.1:xxx/store-status.xml?password=;

And got the following output
91fc3583-761a-4e1f-8493-3f47a01e628a MT-PUSH 2015-05-18 12:33:35
   1950 1876052832 fake1 dlrbox hello
   f8c68792-7d95-4d14-9a84-276a25aba8e4 MT-PUSH 2015-05-18 12:33:35
   1950 1126022293 fake1 dlrbox hello
   c9f5d10e-861d-48b4-a5ae-c6a743dcff21 MT-PUSH 2015-05-18 12:33:35
   1950 1638362136 fake1 dlrbox hello
   202f331a-6c5a-4120-a0de-f20bf71f1da9 MT-PUSH 2015-05-18 12:33:35
   1950 1903556200 fake1 dlrbox hello
   0924eb0d-7a98-4e58-9fbe-e549227f93f5 MT-PUSH 2015-05-18 12:33:35
   1950 1156234781 fake1 dlrbox hello
   a91495f9-f48f-4b2d-8c6b-3b3872bde40b MT-PUSH 2015-05-18 12:33:35
   1950 1039133110 fake1 dlrbox hello
   d5b14df4-2025-4176-97a6-d8f034d2c024 MT-PUSH 2015-05-18 12:33:35
   1950 1295345287 fake1 dlrbox hello



4) I wanted to remove these messages from the queue using the UUID's. So i
tried doing

lynx -dump 
http://127.0.0.1:13000/remove-message?id=91fc3583-761a-4e1f-8493-3f47a01e628a


This gave me Denied error


5) Then i tried removing using password
http://127.0.0.1:13000/remove-message?id=91fc3583-761a-4e1f-8493-3f47a01e628a?password=


Still it gave me error Denied.

It should work as its given in Kannel svn-r5114 doc that we can use
remove-message command for removing messages.

remove-message - Removes the message with the give id (an UUID) from the
local storage subsystem.
Can someone explain me about how to make this to work.


Also please check the following link.
https://redmine.kannel.org/issues/567

I want to know is this working i cant find any related documents. Its
posted a long time ago so it should be implemented till now.

Thanks
Kirti