Re: sendota problems - SOLVED

2009-06-09 Thread Julien Buratto 
Patch from Nikos has been committed to CVS.

2009/6/8 Nikos Balkanas :
> No, you are not complaining. As usual you make unsubstantiated claims while
> being clueless. Have you bothered to check cvs to substantiate your words? I
> didn't think so.
>
> Well, don't loose your sleep over it. What you say hasn't happenned.
>
> - Original Message - From: "Julien Buratto"
> 
> To: "Nikos Balkanas" 
> Cc: ; ; "Pai Peng"
> 
> Sent: Monday, June 08, 2009 7:59 PM
> Subject: Re: sendota problems
>
>
> Hi Nikos,
>
> I'm not complaining, I'm just concerned how this was dropped and where :-)
>
> Julien
>
> 2009/6/8 Nikos Balkanas :
>>
>> Interesting... Although it has been stressed to you, by 2 core developers
>> (well actually 1.5 ;-) that kannel never supported wap-provisioningdoc,
>> you
>> skip thread, and restate that it is kannel who has dropped this feature.
>> When in fact, it is yourself who has been feeding kannel with a different
>> xml all these years and suddenly decide to change.
>>
>> Kannel supports legacy devices, and doesn't drop proven features no matter
>> how old. New devices, however, like wap 2.0 are an issue.
>>
>> I am happy that you can work with characteristic-list.
>>
>> BR,
>> Nikos
>> - Original Message - From: "Julien Buratto"
>> 
>> To: "Nikos Balkanas" 
>> Cc: ; ; "Pai Peng"
>> 
>> Sent: Monday, June 08, 2009 1:54 PM
>> Subject: Re: sendota problems
>>
>>
>> I think I will have no choice and I will try to convert it to
>> characteristic-list ..
>>
>> Julien
>>
>> 2009/6/8 Julien Buratto :
>>>
>>> Hi Nikos,
>>>
>>> I've been happily using wap-provisioningdoc for a long time on
>>> 1.4.1... quite strange the implementation has been removed from
>>> 1.4.3..
>>>
>>> Julien
>>>
>>> 2009/6/8 Nikos Balkanas :

 Oops! Forgot to ask.

 Can't you use a characteristic-list xml document to do your job? Kannel
 fully supports those!

 BR,
 Nikos
 - Original Message - From: "Nikos Balkanas"
 
 To: "Julien Buratto" 
 Cc: ; ; "Pai Peng"
 
 Sent: Monday, June 08, 2009 6:11 AM
 Subject: Re: sendota problems


> Hi Julien,
>
> I looked it up and it is not trivial.
>
> As it stands kannel supports only the Nokia OTA characteristic-list
> specs.
> It doesn't support the wap-provisioningdoc specs. As such a complete
> reworking of the ota-compiler would be needed to accomodate it.
>
> Since I am lacking ota development/testing environment, and is only of
> marginal interest to me, I am sorry but I cannot pursue it further.
> What
> I
> can do is, to make a patch, so that kannel prints an error when it
> detects
> such a document and drops it.
>
> BR,
> Nikos
> - Original Message - From: "Nikos Balkanas"
> 
> To: "Julien Buratto" 
> Cc: ; 
> Sent: Saturday, June 06, 2009 9:19 AM
> Subject: Re: sendota problems
>
>
>> Not, unfortunately. I was going crazy all this time at work, but I
>> just
>> finished. I will look at it over this weekend.
>>
>> BR,
>> Nikos
>> - Original Message - From: "Julien Buratto"
>> 
>> To: "Nikos Balkanas" 
>> Cc: ; 
>> Sent: Thursday, May 28, 2009 3:16 PM
>> Subject: Re: sendota problems
>>
>>
>> Hi Nikos, where you able to fix the issue ?
>>
>> 2009/3/17 Nikos Balkanas :
>>>
>>> Hi,
>>>
>>> There seems to be an incombatibility between kannel's wbxml and
>>> Nokia's.
>>> I
>>> intend to fix it, but in a month or so. In the meantime you might
>>> want
>>> to
>>> compile the message manually, as described by Pai Peng.
>>>
>>> BR,
>>> Nikos
>>> - Original Message - From: "Tomas Verbaitis"
>>> 
>>> To: 
>>> Sent: Monday, March 16, 2009 1:24 PM
>>> Subject: sendota problems
>>>
>>>
>>> Hello,
>>>
>>> I want to configure synchronization for Nokia 6070 mobile phone. My
>>> program generates this XML provisioning document:
>>>
>>> 
>>> >> "http://www.wapforum.org/DTD/prov.dtd";>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> http://megalogika.stp.lt/funambol/ds"/>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> "
>>>
>>> When i send it via Kannel's /sendota, via this request:
>>>
>>>
>>>
>>>
>>> /cgi-bin/sendota?password=##&username=##&type=oma-settings&sec=USERPIN&pin=1234&to=%2B37069953201&text=%3C%3Fxml+version%3D%221.0%22%3F%3E%0A%3C%21DOCTYPE+wap-provisioningdoc+PUBLIC+%22-%2F%2FWAPFORUM%2F%2FDTD+PROV+1.0%2F%2FEN%22%0A%22http%3A%2F%2Fwww.wapforum.org%2FDTD%2Fprov.dtd%22%3E%0A%3Cwap-provisioningdoc%3E%0A%3Ccharacteristic+type%3D%22BOOTSTRAP%22%3E%0A%3Cparm+name%3D%22NAME%22+value%3D%22SK

Re: Get notification if SMS has been discarded from SMSC

2009-06-09 Thread Beatrice Tamburrino 
My Provider has confirmed: the smsc sends notification for discarded messages. 
So Im going to try something.. I let you know... 

xox beatrice


 Original-Nachricht 
> Datum: Tue, 9 Jun 2009 10:31:32 +0200
> Von: Falko Ziemann 
> An: Alejandro Guerrieri 
> CC: users@kannel.org
> Betreff: Re: Get notification if SMS has been discarded from SMSC

> No it doesn't. The information isn't even delivered to the mobile, so  
> you can't see on your mobile, if the message had a defined validity  
> period.
> 
> BTW: some SMSCs don't send you a notification if a message is  
> discarded, even when you request all notifications. Because "no  
> positive notification" + "validity period is over" = "message  
> discarded, no notification needed"
> 
> Regards
> Falko
> 
> Am 08.06.2009 um 20:25 schrieb Alejandro Guerrieri:
> 
> > afaik, no. It could lead to undesired results, specially if your  
> > phone's clock is misconfigured ;)
> >
> > 2009/6/8 Nikos Balkanas 
> > Of course not the SMSc! I was wondering if the mobiles have validity  
> > support built in. I.e. Do not display an expired SMS.
> > - Original Message -
> > From: Alejandro Guerrieri
> > To: Nikos Balkanas
> > Cc: Beatrice Tamburrino ; users@kannel.org
> > Sent: Monday, June 08, 2009 9:13 PM
> > Subject: Re: Get notification if SMS has been discarded from SMSC
> >
> > afaik, the smsc only knows if the message has been _delivered_ to  
> > the phone, it cannot tell if you _really_ looked into it (how could  
> > it do that?), so the validity period is only relevant while the  
> > message is waiting at the smsc.
> >
> > Regards,
> >
> > Alejandro
> >
> > 2009/6/8 Nikos Balkanas 
> > Does the validity period affect only retention at the SMSc, or does  
> > it also affect display on the mobile? I.e. if an sms is delivered  
> > OK, but not viewed in the mobile until later.
> >
> > Nikos
> > - Original Message -
> > From: Alejandro Guerrieri
> > To: Beatrice Tamburrino
> > Cc: users@kannel.org
> > Sent: Monday, June 08, 2009 6:56 PM
> > Subject: Re: Get notification if SMS has been discarded from SMSC
> >
> > No idea about the EMI protocol (I'm mostly an SMPP guy). The  
> > validity period works on SMPP (assuming the SMSC honors it, of  
> > course).
> >
> > Regards,
> >
> > Alejandro
> >
> > On Mon, Jun 8, 2009 at 5:26 PM, Beatrice Tamburrino
>  > > wrote:
> > Or sending a validity period flag with the OT-53 String.. ?
> >
> >
> >
> >
> >
> >  Original-Nachricht 
> > > Datum: Mon, 08 Jun 2009 17:19:39 +0200
> > > Von: "Beatrice Tamburrino" 
> > > An: Alejandro Guerrieri 
> > > CC: users@kannel.org
> > > Betreff: Re: Get notification if SMS has been discarded from SMSC
> >
> > > My provider just told me that the max. validity time is 48 hours.  
> > And the
> > > SMSC sends me an OT-53.
> > >
> > > It would be nice if I could delete the SMS (in the SMSC) after about
> > > 15minutes..
> > >
> > > mmhh... headache..
> > >
> > >  Original-Nachricht 
> > > > Datum: Mon, 8 Jun 2009 17:07:52 +0200
> > > > Von: Alejandro Guerrieri 
> > > > An: Beatrice Tamburrino 
> > > > CC: Nikos Balkanas , users@kannel.org
> > > > Betreff: Re: Get notification if SMS has been discarded from SMSC
> > >
> > > > Are you sure the SMSC is actually notifying you when it discards a
> > > > message?
> > > > Regards,
> > > >
> > > > Alejandro
> > > >
> > > > On Mon, Jun 8, 2009 at 5:03 PM, Beatrice Tamburrino <
> > > > beatrice.tamburr...@gmx.ch> wrote:
> > > >
> > > > > hi,
> > > > >
> > > > > thanks, this seem to be a different mask?
> > > > >
> > > > > I set the dlr-mask = 31? ??
> > > > >
> > > > > I think I need more help here..
> > > > >
> > > > >  Original-Nachricht 
> > > > > > Datum: Mon, 8 Jun 2009 17:46:23 +0300
> > > > > > Von: "Nikos Balkanas" 
> > > > > > An: "Beatrice Tamburrino" ,
> > > > users@kannel.org
> > > > > > Betreff: Re: Get notification if SMS has been discarded from  
> > SMSC
> > > > >
> > > > > > Sure it does:
> > > > > >
> > > > > > #define DLR_SMSC_FAIL   0x10
> > > > > >
> > > > > > Just use the right dlr-mask
> > > > > >
> > > > > > BR,
> > > > > > Nikos
> > > > > > - Original Message -
> > > > > > From: "Beatrice Tamburrino" 
> > > > > > To: 
> > > > > > Sent: Monday, June 08, 2009 4:34 PM
> > > > > > Subject: Get notification if SMS has been discarded from SMSC
> > > > > >
> > > > > >
> > > > > > > Hi!
> > > > > > >
> > > > > > > I've almost finished my SMS Application which sends SMS to a
> > > Kannel
> > > > > > Server
> > > > > > > and waits on a Port for dlr's. Im facing only one problem  
> > right
> > > now,
> > > > I
> > > > > > > hope somebody can help me on that..
> > > > > > >
> > > > > > > Im using the emi protocol to a provider. The provider  
> > supports the
> > > > > > > extended operations OT 51-58, where OT-56 is: Delete Message
> > > > operation.
> > > > > > >
> > > > > > > So the problem is, that if I receive a dlr code=4, the  
> > message
>

Re: nokia 6230 SMSC

2009-06-09 Thread Jovan Kostovski 
On Tue, Jun 9, 2009 at 3:28 PM, Pietro Guerrieri wrote:
> I just sent SMS, and now i have to receive SMS and forward to WEB
> application
>
> How i can do this!?!

You have to setup sms-service, read the userguide
http://kannel.org/download/1.4.3/userguide-1.4.3/userguide.html#AEN3309

BR, Jovan

nokia 6230 SMSC

2009-06-09 Thread Pietro Guerrieri 
My scenario is:
1) through HTTP one WEB application call  Kannel and send SMS
2) Kannel receive a SMS and forward message to WEB application


so i have installed kannel and connect it to a mobile phone (nokia 6230)

I just sent SMS, and now i have to receive SMS and forward to WEB
application

How i can do this!?!


this is my configuration:
group = smsc
smsc = at
smsc-id = "nokia6230"
modemtype = nokiaphone
device = /dev/ttyACM0
#my-number = 7
speed = 9600
connect-allow-ip = 127.0.0.1
log-level = 0
sim-buffering = true
include = /kannel/gateway-1.4.1/doc/examples/modems.conf

And modem.conf:
group = modems
id = nokiaphone
name = "Nokia Phone"
detect-string = "Nokia Mobile Phone"
need-sleep = true
message-storage = "SM"
init-string = "AT+CNMI=1,2,0,1,0;+CMEE=1"
keepalive-cmd = "AT+CBC;+CSQ"

thanx to all

Re: getting message-id in resp of send request

2009-06-09 Thread Alejandro Guerrieri 
Yes it will. In fact, it doesn't make sense to define the dlr-url on the
conf file, since you'll obviously need to use a custom dlr-url on each and
every request.
Regards,

Alejandro

On Tue, Jun 9, 2009 at 1:18 PM, Latitude Berlin
wrote:

> If I have DLR-URL defined in my kannel.conf, it will be overwritten by the
> provided one in the HTTP SEND-REQ)
>
>
>
> On Tue, Jun 9, 2009 at 1:12 PM, Falko Ziemann  wrote:
>
>>
>> $msgid=123;
>> $myurl=url_encode("http://myfunnyhost.com/dlr-receive.php?msgid=$msgid";)
>>
>> Then you post to kannel:
>> http://mykannelhost/sendsms?to=004917...&dlr-mask=31&dlr-url=$myurl
>>
>> Regards
>> Falko
>>
>> Am 09.06.2009 um 13:03 schrieb Latitude Berlin:
>>
>> Hi Falko,
>>
>> I assume that the id will be sent in send-sms URL request and that whould
>> be put in DLR URL to have the mapping. Is this correct? How to send id in
>> send-sms req and do the mapping?
>>
>> Thanks.
>>
>> On Tue, Jun 9, 2009 at 12:21 PM, Falko Ziemann  wrote:
>>
>>> Generate your own ID and add it to the DLR-URL.
>>> When you give the DLR-URL to kannel inside the sendsms add &id=12345 to
>>> the dlr-url.
>>>
>>> Regards
>>> Falko
>>>
>>> Am 09.06.2009 um 12:12 schrieb Latitude Berlin:
>>>
>>> If my application is sending a lot me SMS messages, then on receiving
>>> DLR, how may I know for which SMS message this DLR is for? I know message-id
>>> will be there but how can I decide which message-id is for which sent
>>> message?
>>>
>>>
>>>
>>> On Tue, Jun 9, 2009 at 12:05 PM, Alejandro Guerrieri <
>>> alejandro.guerri...@gmail.com> wrote:
>>>
 Not directly, you need DLR's for that.
 This is because the sending is asynchronous, so kannel might not be able
 to give back a message id until the external smsc accepts the message 
 (which
 may happen an hour later, for example).

 Regards,

 Alejandro


 On Tue, Jun 9, 2009 at 11:56 AM, Latitude Berlin >>> googlemail.com> wrote:

> Hi,
>
> I need to store message-ids of SMS messages in my application. Is it
> possible that when I send send-sms request to Kannel (via HTTP), Kannel
> reports the message-id of the sms to my application through a Servlet?
>
> Thanks a lot.
>
> Cheers
>


>>>
>>>
>>
>>
>

Re: getting message-id in resp of send request

2009-06-09 Thread Latitude Berlin 
If I have DLR-URL defined in my kannel.conf, it will be overwritten by the
provided one in the HTTP SEND-REQ)


On Tue, Jun 9, 2009 at 1:12 PM, Falko Ziemann  wrote:

>
> $msgid=123;
> $myurl=url_encode("http://myfunnyhost.com/dlr-receive.php?msgid=$msgid";)
>
> Then you post to kannel:
> http://mykannelhost/sendsms?to=004917...&dlr-mask=31&dlr-url=$myurl
>
> Regards
> Falko
>
> Am 09.06.2009 um 13:03 schrieb Latitude Berlin:
>
> Hi Falko,
>
> I assume that the id will be sent in send-sms URL request and that whould
> be put in DLR URL to have the mapping. Is this correct? How to send id in
> send-sms req and do the mapping?
>
> Thanks.
>
> On Tue, Jun 9, 2009 at 12:21 PM, Falko Ziemann  wrote:
>
>> Generate your own ID and add it to the DLR-URL.
>> When you give the DLR-URL to kannel inside the sendsms add &id=12345 to
>> the dlr-url.
>>
>> Regards
>> Falko
>>
>> Am 09.06.2009 um 12:12 schrieb Latitude Berlin:
>>
>> If my application is sending a lot me SMS messages, then on receiving DLR,
>> how may I know for which SMS message this DLR is for? I know message-id will
>> be there but how can I decide which message-id is for which sent message?
>>
>>
>>
>> On Tue, Jun 9, 2009 at 12:05 PM, Alejandro Guerrieri <
>> alejandro.guerri...@gmail.com> wrote:
>>
>>> Not directly, you need DLR's for that.
>>> This is because the sending is asynchronous, so kannel might not be able
>>> to give back a message id until the external smsc accepts the message (which
>>> may happen an hour later, for example).
>>>
>>> Regards,
>>>
>>> Alejandro
>>>
>>>
>>> On Tue, Jun 9, 2009 at 11:56 AM, Latitude Berlin >> googlemail.com> wrote:
>>>
 Hi,

 I need to store message-ids of SMS messages in my application. Is it
 possible that when I send send-sms request to Kannel (via HTTP), Kannel
 reports the message-id of the sms to my application through a Servlet?

 Thanks a lot.

 Cheers

>>>
>>>
>>
>>
>
>

Re: getting message-id in resp of send request

2009-06-09 Thread Falko Ziemann 


$msgid=123;
$myurl=url_encode("http://myfunnyhost.com/dlr-receive.php?msgid=$msgid";)

Then you post to kannel:
http://mykannelhost/sendsms?to=004917...&dlr-mask=31&dlr-url=$myurl

Regards
Falko

Am 09.06.2009 um 13:03 schrieb Latitude Berlin:


Hi Falko,

I assume that the id will be sent in send-sms URL request and that  
whould be put in DLR URL to have the mapping. Is this correct? How  
to send id in send-sms req and do the mapping?


Thanks.

On Tue, Jun 9, 2009 at 12:21 PM, Falko Ziemann   
wrote:

Generate your own ID and add it to the DLR-URL.

When you give the DLR-URL to kannel inside the sendsms add &id=12345  
to the dlr-url.


Regards
Falko

Am 09.06.2009 um 12:12 schrieb Latitude Berlin:

If my application is sending a lot me SMS messages, then on  
receiving DLR, how may I know for which SMS message this DLR is  
for? I know message-id will be there but how can I decide which  
message-id is for which sent message?




On Tue, Jun 9, 2009 at 12:05 PM, Alejandro Guerrieri > wrote:

Not directly, you need DLR's for that.

This is because the sending is asynchronous, so kannel might not be  
able to give back a message id until the external smsc accepts the  
message (which may happen an hour later, for example).


Regards,

Alejandro


On Tue, Jun 9, 2009 at 11:56 AM, Latitude Berlin > wrote:

Hi,

I need to store message-ids of SMS messages in my application. Is  
it possible that when I send send-sms request to Kannel (via HTTP),  
Kannel reports the message-id of the sms to my application through  
a Servlet?


Thanks a lot.

Cheers

RE: Re[2]: 7bit encoded messages

2009-06-09 Thread Remon 
Yes it works now. Thanks Guys J.

 

From: Thomas Göttgens [mailto:tho...@ist.schuldig.de] 
Sent: Tuesday, June 09, 2009 1:10 PM
To: Remon
Cc: us...@vm1.kannel.org
Subject: Re[2]: 7bit encoded messages

 

Hello Remon,

 

try

 

http://XX.XX.XX.XX:13013/cgi-bin/sendsms?user=test&pass=test&from=111&to=XXX
&udh=%05%00%03%AD%02%02&text=5678

 

the % in front of 05 is missing.

 

Tuesday, June 9, 2009, 11:55:32 AM, you wrote:

 


Hi I tried this but it says UDH is not correct L

 

http://XX.XX.XX.XX:13013/cgi-bin/sendsms?user=test&pass=test&from=111&to=XXX
&udh=05%00%03%AD%02%01&text=1234

 

http://XX.XX.XX.XX:13013/cgi-bin/sendsms?user=test&pass=test&from=111&to=XXX
&udh=05%00%03%AD%02%02&text=5678

 

Regards,

Remon

 

From: Falko Ziemann [mailto:fal...@gmail.com] 

Sent: Tuesday, June 09, 2009 12:32 PM

To: Remon

Cc: 'Nikos Balkanas'; users@kannel.org

Subject: Re: 7bit encoded messages

 

Just add the field UDH.

So send the text als normal:

sms=I+am+messagepart+1

udh=%00%AB%02%01

 

then:

sms=I+am+messagepart+2

udh=%00%AB%02%02

 

I could not test this currently, but should work.

 

Regards

Falko

 

Am 09.06.2009 um 11:12 schrieb Remon:

 

 

Thanks Falko,

 

I will tell you my problems, I need to send long concatenated messages from
kannel, I found that I should encode the messages to 7bit and add the header
before sending them, have been searching a while on this point with no
success, I need a working example to follow but unfortunately I’m unable to
find any.

 

Please note that I need to handle text message fragmentation from my
application and not from Kannel.

 

Regards,

Remon

 

 

From: Falko Ziemann [  mailto:fal...@gmail.com] 

Sent: Tuesday, June 09, 2009 11:40 AM

To: Nikos Balkanas

Cc: Remon;   users@kannel.org

Subject: Re: 7bit encoded messages

 

Nikos: use lynx for suspicious URLs ;-)

 

I think you (remon) make a major mistake in your thoughts how kannel works.
When you set coding=0 kannels _output_ is 7bit. The charset of the _input_
is defined in the HTTP-header of the client triggering kannel. So you can
use, let's say, UTF-16 in the URL and when you set coding=0 kannel makes it
7bit. But when you send something like "%E8%32%" and you client claims "this
is UTF-8" and then kannel tries to translate it to 7bit you get
strange results.

 

Regards

Falko

 

Am 09.06.2009 um 01:07 schrieb Nikos Balkanas:

 

 

 

Hi,

 

I am very sceptic when using unknown URLs. Could you please describe in
mail?

 

BR,

Nikos

- Original Message -

From:   Remon

To:   'Nikos Balkanas'

Cc:   users@kannel.org

Sent: Tuesday, June 09, 2009 1:49 AM

Subject: RE: 7bit encoded messages

 

The below URL is an example of 7bit encoded text, when I send it using
coding=0 I receive trash on my phone. I think I’m missing something here.

 

 
http://www.dreamfabric.com/sms/hello.html

 

 

From: Nikos Balkanas [ 
mailto:nbalka...@gmail.com] 

Sent: Monday, June 08, 2009 3:30 AM

To: Remon

Cc:   users@kannel.org

Subject: Re: 7bit encoded messages

 

Hi,

 

Use &coding=0 in your URL.

 

BR,

Nikos

- Original Message -

From:   Remon

To:   users@kannel.org

Sent: Monday, June 08, 2009 1:32 AM

Subject: 7bit encoded messages

 

Hi,

 

How can I send 7bit encoded text messages using Kannel’s http send
interface?

 

Thanks,

 

 

 

 

 

 

 

 

-- 

Best regards,

 Thomas 
mailto:tho...@ist.schuldig.de

Re: getting message-id in resp of send request

2009-06-09 Thread Latitude Berlin 
Hi Falko,

I assume that the id will be sent in send-sms URL request and that whould be
put in DLR URL to have the mapping. Is this correct? How to send id in
send-sms req and do the mapping?

Thanks.

On Tue, Jun 9, 2009 at 12:21 PM, Falko Ziemann  wrote:

> Generate your own ID and add it to the DLR-URL.
> When you give the DLR-URL to kannel inside the sendsms add &id=12345 to the
> dlr-url.
>
> Regards
> Falko
>
> Am 09.06.2009 um 12:12 schrieb Latitude Berlin:
>
> If my application is sending a lot me SMS messages, then on receiving DLR,
> how may I know for which SMS message this DLR is for? I know message-id will
> be there but how can I decide which message-id is for which sent message?
>
>
>
> On Tue, Jun 9, 2009 at 12:05 PM, Alejandro Guerrieri <
> alejandro.guerri...@gmail.com> wrote:
>
>> Not directly, you need DLR's for that.
>> This is because the sending is asynchronous, so kannel might not be able
>> to give back a message id until the external smsc accepts the message (which
>> may happen an hour later, for example).
>>
>> Regards,
>>
>> Alejandro
>>
>>
>> On Tue, Jun 9, 2009 at 11:56 AM, Latitude Berlin > googlemail.com> wrote:
>>
>>> Hi,
>>>
>>> I need to store message-ids of SMS messages in my application. Is it
>>> possible that when I send send-sms request to Kannel (via HTTP), Kannel
>>> reports the message-id of the sms to my application through a Servlet?
>>>
>>> Thanks a lot.
>>>
>>> Cheers
>>>
>>
>>
>
>

Re: getting message-id in resp of send request

2009-06-09 Thread Falko Ziemann 

Generate your own ID and add it to the DLR-URL.

When you give the DLR-URL to kannel inside the sendsms add &id=12345  
to the dlr-url.


Regards
Falko

Am 09.06.2009 um 12:12 schrieb Latitude Berlin:

If my application is sending a lot me SMS messages, then on  
receiving DLR, how may I know for which SMS message this DLR is for?  
I know message-id will be there but how can I decide which message- 
id is for which sent message?




On Tue, Jun 9, 2009 at 12:05 PM, Alejandro Guerrieri > wrote:

Not directly, you need DLR's for that.

This is because the sending is asynchronous, so kannel might not be  
able to give back a message id until the external smsc accepts the  
message (which may happen an hour later, for example).


Regards,

Alejandro


On Tue, Jun 9, 2009 at 11:56 AM, Latitude Berlin > wrote:

Hi,

I need to store message-ids of SMS messages in my application. Is it  
possible that when I send send-sms request to Kannel (via HTTP),  
Kannel reports the message-id of the sms to my application through a  
Servlet?


Thanks a lot.

Cheers

Re: getting message-id in resp of send request

2009-06-09 Thread Benaiad 
AFAIK it's not possible, when you do a HTTP request, Kannel puts your
message into a queue and responds with "accepted for delivery", after that
Kannel try to send the queued message.
to do a relation between your sent message and It's DLR, add an  auto
increment ID column and for every insert get the generated id and add it to
the dlr-url.

On Tue, Jun 9, 2009 at 11:56 AM, Latitude Berlin  wrote:

> Hi,
>
> I need to store message-ids of SMS messages in my application. Is it
> possible that when I send send-sms request to Kannel (via HTTP), Kannel
> reports the message-id of the sms to my application through a Servlet?
>
> Thanks a lot.
>
> Cheers
>

Re: getting message-id in resp of send request

2009-06-09 Thread Latitude Berlin 
If my application is sending a lot me SMS messages, then on receiving DLR,
how may I know for which SMS message this DLR is for? I know message-id will
be there but how can I decide which message-id is for which sent message?



On Tue, Jun 9, 2009 at 12:05 PM, Alejandro Guerrieri <
alejandro.guerri...@gmail.com> wrote:

> Not directly, you need DLR's for that.
> This is because the sending is asynchronous, so kannel might not be able to
> give back a message id until the external smsc accepts the message (which
> may happen an hour later, for example).
>
> Regards,
>
> Alejandro
>
>
> On Tue, Jun 9, 2009 at 11:56 AM, Latitude Berlin  googlemail.com> wrote:
>
>> Hi,
>>
>> I need to store message-ids of SMS messages in my application. Is it
>> possible that when I send send-sms request to Kannel (via HTTP), Kannel
>> reports the message-id of the sms to my application through a Servlet?
>>
>> Thanks a lot.
>>
>> Cheers
>>
>
>

Re: 7bit encoded messages

2009-06-09 Thread Falko Ziemann 

Hehe,

ok, ok, my UDH was junk. And you are missing one "%":

udh=05%00



udh=%05%00


Regards
Falko

Am 09.06.2009 um 11:55 schrieb Remon:


Hi I tried this but it says UDH is not correct L

http://XX.XX.XX.XX:13013/cgi-bin/sendsms?user=test&pass=test&from=111&to=XXX&udh=05%00%03%AD%02%01&text=1234
http://XX.XX.XX.XX:13013/cgi-bin/sendsms?user=test&pass=test&from=111&to=XXX&udh=05%00%03%AD%02%02&text=5678

Regards,
Remon

From: Falko Ziemann [mailto:fal...@gmail.com]
Sent: Tuesday, June 09, 2009 12:32 PM
To: Remon
Cc: 'Nikos Balkanas'; users@kannel.org
Subject: Re: 7bit encoded messages

Just add the field UDH.
So send the text als normal:
sms=I+am+messagepart+1
udh=%00%AB%02%01

then:
sms=I+am+messagepart+2
udh=%00%AB%02%02

I could not test this currently, but should work.

Regards
Falko

Am 09.06.2009 um 11:12 schrieb Remon:


Thanks Falko,

I will tell you my problems, I need to send long concatenated  
messages from kannel, I found that I should encode the messages to  
7bit and add the header before sending them, have been searching a  
while on this point with no success, I need a working example to  
follow but unfortunately I’m unable to find any.


Please note that I need to handle text message fragmentation from my  
application and not from Kannel.


Regards,
Remon


From: Falko Ziemann [mailto:fal...@gmail.com]
Sent: Tuesday, June 09, 2009 11:40 AM
To: Nikos Balkanas
Cc: Remon; users@kannel.org
Subject: Re: 7bit encoded messages

Nikos: use lynx for suspicious URLs ;-)

I think you (remon) make a major mistake in your thoughts how kannel  
works. When you set coding=0 kannels _output_ is 7bit. The charset  
of the _input_ is defined in the HTTP-header of the client  
triggering kannel. So you can use, let's say, UTF-16 in the URL and  
when you set coding=0 kannel makes it 7bit. But when you send  
something like "%E8%32%" and you client claims "this is UTF-8" and  
then kannel tries to translate it to 7bit you get strange  
results.


Regards
Falko

Am 09.06.2009 um 01:07 schrieb Nikos Balkanas:



Hi,

I am very sceptic when using unknown URLs. Could you please describe  
in mail?


BR,
Nikos
- Original Message -
From: Remon
To: 'Nikos Balkanas'
Cc: users@kannel.org
Sent: Tuesday, June 09, 2009 1:49 AM
Subject: RE: 7bit encoded messages

The below URL is an example of 7bit encoded text, when I send it  
using coding=0 I receive trash on my phone. I think I’m missing  
something here.


http://www.dreamfabric.com/sms/hello.html


From: Nikos Balkanas [mailto:nbalka...@gmail.com]
Sent: Monday, June 08, 2009 3:30 AM
To: Remon
Cc: users@kannel.org
Subject: Re: 7bit encoded messages

Hi,

Use &coding=0 in your URL.

BR,
Nikos
- Original Message -
From: Remon
To: users@kannel.org
Sent: Monday, June 08, 2009 1:32 AM
Subject: 7bit encoded messages

Hi,

How can I send 7bit encoded text messages using Kannel’s http send  
interface?


Thanks,

Re: getting message-id in resp of send request

2009-06-09 Thread Alejandro Guerrieri 
Not directly, you need DLR's for that.
This is because the sending is asynchronous, so kannel might not be able to
give back a message id until the external smsc accepts the message (which
may happen an hour later, for example).

Regards,

Alejandro

On Tue, Jun 9, 2009 at 11:56 AM, Latitude Berlin  wrote:

> Hi,
>
> I need to store message-ids of SMS messages in my application. Is it
> possible that when I send send-sms request to Kannel (via HTTP), Kannel
> reports the message-id of the sms to my application through a Servlet?
>
> Thanks a lot.
>
> Cheers
>

RE: 7bit encoded messages

2009-06-09 Thread Remon 
With NowSMS I send a long message and From logs I can see

 

UDH=050003AD0201;Data=62B219AD66BBE172B0986C46ABD96EB81C2C269BD16AB61B2E078B
C966B49AED86CBC162B219AD66BBE172B0986C46ABD96EB81C2C269BD16AB61B2E078BC966B4
9AED86CBC162B219AD66BBE172B0986C46ABD96EB81C2C269BD16AB61B2E078BC966B49AED86
CBC162B219AD66BBE172B0986C46ABD96EB81C2C269BD16AB61B2E078BC966

UDH=050003AD0202;Data=6835DB0D9783C564335ACD76C3E560

 

My message is

1234567890123456789012345678901234567890123456789012345678901234567890123456
7890123456789012345678901234567890123456789012345678901234567890123456789012
345678901234567890

 

Which is 170 characters

Any clue?

 

Regards,

Remon

 

 

From: Nikos Balkanas [mailto:nbalka...@gmail.com] 
Sent: Tuesday, June 09, 2009 12:36 PM
To: Remon; 'Falko Ziemann'
Cc: users@kannel.org
Subject: Re: 7bit encoded messages

 

Hi,

 

I just read your encoding scheme (sorry Falko for budding in). If you encode
yourself the text message, then you need to use coding=1 or coding=2, else
kannel wiil try to recode it as 7bit. 

 

BR,

Nikos

- Original Message - 

From: Remon   

To: 'Falko Ziemann'   ; 'Nikos Balkanas'
  

Cc: users@kannel.org 

Sent: Tuesday, June 09, 2009 12:12 PM

Subject: RE: 7bit encoded messages

 

Thanks Falko,

 

I will tell you my problems, I need to send long concatenated messages from
kannel, I found that I should encode the messages to 7bit and add the header
before sending them, have been searching a while on this point with no
success, I need a working example to follow but unfortunately I'm unable to
find any.

 

Please note that I need to handle text message fragmentation from my
application and not from Kannel.

 

Regards,

Remon

 

 

From: Falko Ziemann [mailto:fal...@gmail.com] 
Sent: Tuesday, June 09, 2009 11:40 AM
To: Nikos Balkanas
Cc: Remon; users@kannel.org
Subject: Re: 7bit encoded messages

 

Nikos: use lynx for suspicious URLs ;-)

 

I think you (remon) make a major mistake in your thoughts how kannel works.
When you set coding=0 kannels _output_ is 7bit. The charset of the _input_
is defined in the HTTP-header of the client triggering kannel. So you can
use, let's say, UTF-16 in the URL and when you set coding=0 kannel makes it
7bit. But when you send something like "%E8%32%" and you client claims "this
is UTF-8" and then kannel tries to translate it to 7bit you get
strange results.

 

Regards

Falko

 

Am 09.06.2009 um 01:07 schrieb Nikos Balkanas:

 

Hi,

 

I am very sceptic when using unknown URLs. Could you please describe in
mail?

 

BR,

Nikos

- Original Message -

From: Remon  

To: 'Nikos Balkanas'  

Cc: users@kannel.org

Sent: Tuesday, June 09, 2009 1:49 AM

Subject: RE: 7bit encoded messages

 

The below URL is an example of 7bit encoded text, when I send it using
coding=0 I receive trash on my phone. I think I'm missing something here.

 

http://www.dreamfabric.com/sms/hello.html

 

 

From: Nikos Balkanas [mailto:nbalka...@gmail.com] 
Sent: Monday, June 08, 2009 3:30 AM
To: Remon
Cc: users@kannel.org
Subject: Re: 7bit encoded messages

 

Hi,

 

Use &coding=0 in your URL.

 

BR,

Nikos

- Original Message -

From: Remon  

To: users@kannel.org

Sent: Monday, June 08, 2009 1:32 AM

Subject: 7bit encoded messages

 

Hi,

 

How can I send 7bit encoded text messages using Kannel's http send
interface?

 

Thanks,

getting message-id in resp of send request

2009-06-09 Thread Latitude Berlin 
Hi,

I need to store message-ids of SMS messages in my application. Is it
possible that when I send send-sms request to Kannel (via HTTP), Kannel
reports the message-id of the sms to my application through a Servlet?

Thanks a lot.

Cheers

RE: 7bit encoded messages

2009-06-09 Thread Remon 
Hi I tried this but it says UDH is not correct L

 

http://XX.XX.XX.XX:13013/cgi-bin/sendsms?user=test&pass=test&from=111&to=XXX
&udh=05%00%03%AD%02%01&text=1234

http://XX.XX.XX.XX:13013/cgi-bin/sendsms?user=test

&pass=test&from=111&to=XXX&udh=05%00%03%AD%02%02&text=5678

 

Regards,

Remon

 

From: Falko Ziemann [mailto:fal...@gmail.com] 
Sent: Tuesday, June 09, 2009 12:32 PM
To: Remon
Cc: 'Nikos Balkanas'; users@kannel.org
Subject: Re: 7bit encoded messages

 

Just add the field UDH.

So send the text als normal:

sms=I+am+messagepart+1

udh=%00%AB%02%01

 

then:

sms=I+am+messagepart+2

udh=%00%AB%02%02

 

I could not test this currently, but should work.

 

Regards

Falko

 

Am 09.06.2009 um 11:12 schrieb Remon:





Thanks Falko,

 

I will tell you my problems, I need to send long concatenated messages from
kannel, I found that I should encode the messages to 7bit and add the header
before sending them, have been searching a while on this point with no
success, I need a working example to follow but unfortunately I'm unable to
find any.

 

Please note that I need to handle text message fragmentation from my
application and not from Kannel.

 

Regards,

Remon

 

 

From: Falko Ziemann [mailto:fal...@gmail.com] 
Sent: Tuesday, June 09, 2009 11:40 AM
To: Nikos Balkanas
Cc: Remon; users@kannel.org
Subject: Re: 7bit encoded messages

 

Nikos: use lynx for suspicious URLs ;-)

 

I think you (remon) make a major mistake in your thoughts how kannel works.
When you set coding=0 kannels _output_ is 7bit. The charset of the _input_
is defined in the HTTP-header of the client triggering kannel. So you can
use, let's say, UTF-16 in the URL and when you set coding=0 kannel makes it
7bit. But when you send something like "%E8%32%" and you client claims "this
is UTF-8" and then kannel tries to translate it to 7bit you get
strange results.

 

Regards

Falko

 

Am 09.06.2009 um 01:07 schrieb Nikos Balkanas:






Hi,

 

I am very sceptic when using unknown URLs. Could you please describe in
mail?

 

BR,

Nikos

- Original Message -

From: Remon  

To: 'Nikos Balkanas'  

Cc: users@kannel.org

Sent: Tuesday, June 09, 2009 1:49 AM

Subject: RE: 7bit encoded messages

 

The below URL is an example of 7bit encoded text, when I send it using
coding=0 I receive trash on my phone. I think I'm missing something here.

 

http://www.dreamfabric.com/sms/hello.html

 

 

From: Nikos Balkanas [mailto:nbalka...@gmail.com] 
Sent: Monday, June 08, 2009 3:30 AM
To: Remon
Cc: users@kannel.org
Subject: Re: 7bit encoded messages

 

Hi,

 

Use &coding=0 in your URL.

 

BR,

Nikos

- Original Message -

From: Remon  

To: users@kannel.org

Sent: Monday, June 08, 2009 1:32 AM

Subject: 7bit encoded messages

 

Hi,

 

How can I send 7bit encoded text messages using Kannel's http send
interface?

 

Thanks,

Re: 7bit encoded messages

2009-06-09 Thread Nikos Balkanas 
Hi,

I just read your encoding scheme (sorry Falko for budding in). If you encode 
yourself the text message, then you need to use coding=1 or coding=2, else 
kannel wiil try to recode it as 7bit. 

BR,
Nikos
  - Original Message - 
  From: Remon 
  To: 'Falko Ziemann' ; 'Nikos Balkanas' 
  Cc: users@kannel.org 
  Sent: Tuesday, June 09, 2009 12:12 PM
  Subject: RE: 7bit encoded messages


  Thanks Falko,

   

  I will tell you my problems, I need to send long concatenated messages from 
kannel, I found that I should encode the messages to 7bit and add the header 
before sending them, have been searching a while on this point with no success, 
I need a working example to follow but unfortunately I’m unable to find any.

   

  Please note that I need to handle text message fragmentation from my 
application and not from Kannel.

   

  Regards,

  Remon

   

   

  From: Falko Ziemann [mailto:fal...@gmail.com] 
  Sent: Tuesday, June 09, 2009 11:40 AM
  To: Nikos Balkanas
  Cc: Remon; users@kannel.org
  Subject: Re: 7bit encoded messages

   

  Nikos: use lynx for suspicious URLs ;-)

   

  I think you (remon) make a major mistake in your thoughts how kannel works. 
When you set coding=0 kannels _output_ is 7bit. The charset of the _input_ is 
defined in the HTTP-header of the client triggering kannel. So you can use, 
let's say, UTF-16 in the URL and when you set coding=0 kannel makes it 7bit. 
But when you send something like "%E8%32%" and you client claims "this is 
UTF-8" and then kannel tries to translate it to 7bit you get strange 
results.

   

  Regards

  Falko

   

  Am 09.06.2009 um 01:07 schrieb Nikos Balkanas:





  Hi,

   

  I am very sceptic when using unknown URLs. Could you please describe in mail?

   

  BR,

  Nikos

- Original Message -

From: Remon

To: 'Nikos Balkanas'

Cc: users@kannel.org

Sent: Tuesday, June 09, 2009 1:49 AM

Subject: RE: 7bit encoded messages

 

The below URL is an example of 7bit encoded text, when I send it using 
coding=0 I receive trash on my phone. I think I’m missing something here.

 

http://www.dreamfabric.com/sms/hello.html

 

 

From: Nikos Balkanas [mailto:nbalka...@gmail.com] 
Sent: Monday, June 08, 2009 3:30 AM
To: Remon
Cc: users@kannel.org
Subject: Re: 7bit encoded messages

 

Hi,

 

Use &coding=0 in your URL.

 

BR,

Nikos

  - Original Message -

  From: Remon

  To: users@kannel.org

  Sent: Monday, June 08, 2009 1:32 AM

  Subject: 7bit encoded messages

   

  Hi,

   

  How can I send 7bit encoded text messages using Kannel’s http send 
interface?

   

  Thanks,

Re: 7bit encoded messages

2009-06-09 Thread Nikos Balkanas 
No, please don't do that. Kannel does this for you transparently. Doing it 
twice would be bad. You just make sure that the characters fed to kannel are 
true 7bit ASCII, when using coding=0, i.e. no accents, no unicode.

How kannel will encode & transmit that information over the network is kannel's 
problem.

BR,
Nikos
  - Original Message - 
  From: Remon 
  To: 'Nikos Balkanas' 
  Cc: users@kannel.org 
  Sent: Tuesday, June 09, 2009 12:07 PM
  Subject: RE: 7bit encoded messages


  Sure

   

  This is the procedure described in the URL

   

  Coding 7-bit data (septets) into octets

  The message "hellohello" consists of 10 characters, called septets when 
represented by 7 bits each. These septets need to be transformed into octets 
for the SMS transfer. 

h
   e
   l
   l
   o
   h
   e
   l
   l
   o
   
104
   101
   108
   108
   111
   104
   101
   108
   108
   111
   
1101000
   1100101
   1101100
   1101100
   110
   1101000
   1100101
   1101100
   1101100
   110
   
  1101000
  
   110010
 1
 
   11011
 00
 
   1101
 100
 
   110
 
 
   11
 01000
 
   1
 100101
 
1101100
 
   1101100
  
   110111
 1
 
   




  The first septet (h) is turned into an octet by adding the rightmost bit of 
the second septet. This bit is inserted to the left which yields 1 + 1101000 = 
11101000 ("E8"). The rightmost bit of the second character is then consumed, so 
the second character (septet) needs two bits (yellow) of the third character to 
make an 8bit octet. This process goes on and on yielding the following octets: 

  1
 1101000
 
   00
 110010
 
   100
 11011
 
   
 1101
 
   01000
 110
 
   100101
 11
 
   1101100
 1
 
 
   1
 1101100
 
 

110111
   
E8
   32
   9B
   FD
   46
   97
   D9
 
   EC
   37
   


  The 9 octets from "hellohello" are E8 32 9B FD 46 97 D9 EC 37

   

   

  So I need to send the above Hex String “E8 32 9B FD 46 97 D9 EC 37”  via 
Kannel and receive it correctly.

   

  Regards,

  Remon

   

   

  From: Nikos Balkanas [mailto:nbalka...@gmail.com] 
  Sent: Tuesday, June 09, 2009 2:07 AM
  To: Remon
  Cc: users@kannel.org
  Subject: Re: 7bit encoded messages

   

  Hi,

   

  I am very sceptic when using unknown URLs. Could you please describe in mail?

   

  BR,

  Nikos

- Original Message - 

From: Remon 

To: 'Nikos Balkanas' 

Cc: users@kannel.org 

Sent: Tuesday, June 09, 2009 1:49 AM

Subject: RE: 7bit encoded messages

 

The below URL is an example of 7bit encoded text, when I send it using 
coding=0 I receive trash on my phone. I think I’m missing something here.

 

http://www.dreamfabric.com/sms/hello.html

 

 

From: Nikos Balkanas [mailto:nbalka...@gmail.com] 
Sent: Monday, June 08, 2009 3:30 AM
To: Remon
Cc: users@kannel.org
Subject: Re: 7bit encoded messages

 

Hi,

 

Use &coding=0 in your URL.

 

BR,

Nikos

  - Original Message - 

  From: Remon 

  To: users@kannel.org 

  Sent: Monday, June 08, 2009 1:32 AM

  Subject: 7bit encoded messages

   

  Hi,

   

  How can I send 7bit encoded text messages using Kannel’s http send 
interface?

   

  Thanks,

Re: 7bit encoded messages

2009-06-09 Thread Falko Ziemann 

Just add the field UDH.
So send the text als normal:
sms=I+am+messagepart+1
udh=%00%AB%02%01

then:
sms=I+am+messagepart+2
udh=%00%AB%02%02

I could not test this currently, but should work.

Regards
Falko

Am 09.06.2009 um 11:12 schrieb Remon:


Thanks Falko,

I will tell you my problems, I need to send long concatenated  
messages from kannel, I found that I should encode the messages to  
7bit and add the header before sending them, have been searching a  
while on this point with no success, I need a working example to  
follow but unfortunately I’m unable to find any.


Please note that I need to handle text message fragmentation from my  
application and not from Kannel.


Regards,
Remon


From: Falko Ziemann [mailto:fal...@gmail.com]
Sent: Tuesday, June 09, 2009 11:40 AM
To: Nikos Balkanas
Cc: Remon; users@kannel.org
Subject: Re: 7bit encoded messages

Nikos: use lynx for suspicious URLs ;-)

I think you (remon) make a major mistake in your thoughts how kannel  
works. When you set coding=0 kannels _output_ is 7bit. The charset  
of the _input_ is defined in the HTTP-header of the client  
triggering kannel. So you can use, let's say, UTF-16 in the URL and  
when you set coding=0 kannel makes it 7bit. But when you send  
something like "%E8%32%" and you client claims "this is UTF-8" and  
then kannel tries to translate it to 7bit you get strange  
results.


Regards
Falko

Am 09.06.2009 um 01:07 schrieb Nikos Balkanas:


Hi,

I am very sceptic when using unknown URLs. Could you please describe  
in mail?


BR,
Nikos
- Original Message -
From: Remon
To: 'Nikos Balkanas'
Cc: users@kannel.org
Sent: Tuesday, June 09, 2009 1:49 AM
Subject: RE: 7bit encoded messages

The below URL is an example of 7bit encoded text, when I send it  
using coding=0 I receive trash on my phone. I think I’m missing  
something here.


http://www.dreamfabric.com/sms/hello.html


From: Nikos Balkanas [mailto:nbalka...@gmail.com]
Sent: Monday, June 08, 2009 3:30 AM
To: Remon
Cc: users@kannel.org
Subject: Re: 7bit encoded messages

Hi,

Use &coding=0 in your URL.

BR,
Nikos
- Original Message -
From: Remon
To: users@kannel.org
Sent: Monday, June 08, 2009 1:32 AM
Subject: 7bit encoded messages

Hi,

How can I send 7bit encoded text messages using Kannel’s http send  
interface?


Thanks,

RE: 7bit encoded messages

2009-06-09 Thread Remon 
Thanks Falko,

 

I will tell you my problems, I need to send long concatenated messages from
kannel, I found that I should encode the messages to 7bit and add the header
before sending them, have been searching a while on this point with no
success, I need a working example to follow but unfortunately I'm unable to
find any.

 

Please note that I need to handle text message fragmentation from my
application and not from Kannel.

 

Regards,

Remon

 

 

From: Falko Ziemann [mailto:fal...@gmail.com] 
Sent: Tuesday, June 09, 2009 11:40 AM
To: Nikos Balkanas
Cc: Remon; users@kannel.org
Subject: Re: 7bit encoded messages

 

Nikos: use lynx for suspicious URLs ;-)

 

I think you (remon) make a major mistake in your thoughts how kannel works.
When you set coding=0 kannels _output_ is 7bit. The charset of the _input_
is defined in the HTTP-header of the client triggering kannel. So you can
use, let's say, UTF-16 in the URL and when you set coding=0 kannel makes it
7bit. But when you send something like "%E8%32%" and you client claims "this
is UTF-8" and then kannel tries to translate it to 7bit you get
strange results.

 

Regards

Falko

 

Am 09.06.2009 um 01:07 schrieb Nikos Balkanas:





Hi,

 

I am very sceptic when using unknown URLs. Could you please describe in
mail?

 

BR,

Nikos

- Original Message -

From: Remon  

To: 'Nikos Balkanas'  

Cc: users@kannel.org

Sent: Tuesday, June 09, 2009 1:49 AM

Subject: RE: 7bit encoded messages

 

The below URL is an example of 7bit encoded text, when I send it using
coding=0 I receive trash on my phone. I think I'm missing something here.

 

http://www.dreamfabric.com/sms/hello.html

 

 

From: Nikos Balkanas [mailto:nbalka...@gmail.com] 
Sent: Monday, June 08, 2009 3:30 AM
To: Remon
Cc: users@kannel.org
Subject: Re: 7bit encoded messages

 

Hi,

 

Use &coding=0 in your URL.

 

BR,

Nikos

- Original Message -

From: Remon  

To: users@kannel.org

Sent: Monday, June 08, 2009 1:32 AM

Subject: 7bit encoded messages

 

Hi,

 

How can I send 7bit encoded text messages using Kannel's http send
interface?

 

Thanks,

RE: 7bit encoded messages

2009-06-09 Thread Remon 
Sure

 

This is the procedure described in the URL

 

Coding 7-bit data (septets) into octets

The message "hellohello" consists of 10 characters, called septets when
represented by 7 bits each. These septets need to be transformed into octets
for the SMS transfer. 


h

e

l

l

o

h

e

l

l

o


104

101

108

108

111

104

101

108

108

111


1101000

1100101

1101100

1101100

110

1101000

1100101

1101100

1101100

110



1101000



110010

1


11011

00


1101

100


110




11

01000


1

100101


1101100


1101100



110111

1







The first septet (h) is turned into an octet by adding the rightmost bit of
the second septet. This bit is inserted to the left which yields 1 + 1101000
= 11101000 ("E8"). The rightmost bit of the second character is then
consumed, so the second character (septet) needs two bits (yellow) of the
third character to make an 8bit octet. This process goes on and on yielding
the following octets: 



1

1101000


00

110010


100

11011




1101


01000

110


100101

11


1101100

1



1

1101100



110111


E8

32

9B

FD

46

97

D9


EC

37


The 9 octets from "hellohello" are E8 32 9B FD 46 97 D9 EC 37

 

 

So I need to send the above Hex String "E8 32 9B FD 46 97 D9 EC 37"  via
Kannel and receive it correctly.

 

Regards,

Remon

 

 

From: Nikos Balkanas [mailto:nbalka...@gmail.com] 
Sent: Tuesday, June 09, 2009 2:07 AM
To: Remon
Cc: users@kannel.org
Subject: Re: 7bit encoded messages

 

Hi,

 

I am very sceptic when using unknown URLs. Could you please describe in
mail?

 

BR,

Nikos

- Original Message - 

From: Remon   

To: 'Nikos Balkanas'   

Cc: users@kannel.org 

Sent: Tuesday, June 09, 2009 1:49 AM

Subject: RE: 7bit encoded messages

 

The below URL is an example of 7bit encoded text, when I send it using
coding=0 I receive trash on my phone. I think I'm missing something here.

 

http://www.dreamfabric.com/sms/hello.html

 

 

From: Nikos Balkanas [mailto:nbalka...@gmail.com] 
Sent: Monday, June 08, 2009 3:30 AM
To: Remon
Cc: users@kannel.org
Subject: Re: 7bit encoded messages

 

Hi,

 

Use &coding=0 in your URL.

 

BR,

Nikos

- Original Message - 

From: Remon   

To: users@kannel.org 

Sent: Monday, June 08, 2009 1:32 AM

Subject: 7bit encoded messages

 

Hi,

 

How can I send 7bit encoded text messages using Kannel's http send
interface?

 

Thanks,

Re: 7bit encoded messages

2009-06-09 Thread Falko Ziemann 

Nikos: use lynx for suspicious URLs ;-)

I think you (remon) make a major mistake in your thoughts how kannel  
works. When you set coding=0 kannels _output_ is 7bit. The charset of  
the _input_ is defined in the HTTP-header of the client triggering  
kannel. So you can use, let's say, UTF-16 in the URL and when you set  
coding=0 kannel makes it 7bit. But when you send something like  
"%E8%32%" and you client claims "this is UTF-8" and then kannel tries  
to translate it to 7bit you get strange results.


Regards
Falko

Am 09.06.2009 um 01:07 schrieb Nikos Balkanas:


Hi,

I am very sceptic when using unknown URLs. Could you please describe  
in mail?


BR,
Nikos
- Original Message -
From: Remon
To: 'Nikos Balkanas'
Cc: users@kannel.org
Sent: Tuesday, June 09, 2009 1:49 AM
Subject: RE: 7bit encoded messages

The below URL is an example of 7bit encoded text, when I send it  
using coding=0 I receive trash on my phone. I think I’m missing  
something here.


http://www.dreamfabric.com/sms/hello.html


From: Nikos Balkanas [mailto:nbalka...@gmail.com]
Sent: Monday, June 08, 2009 3:30 AM
To: Remon
Cc: users@kannel.org
Subject: Re: 7bit encoded messages

Hi,

Use &coding=0 in your URL.

BR,
Nikos
- Original Message -
From: Remon
To: users@kannel.org
Sent: Monday, June 08, 2009 1:32 AM
Subject: 7bit encoded messages

Hi,

How can I send 7bit encoded text messages using Kannel’s http send  
interface?


Thanks,

Re: Get notification if SMS has been discarded from SMSC

2009-06-09 Thread Falko Ziemann 
No it doesn't. The information isn't even delivered to the mobile, so  
you can't see on your mobile, if the message had a defined validity  
period.


BTW: some SMSCs don't send you a notification if a message is  
discarded, even when you request all notifications. Because "no  
positive notification" + "validity period is over" = "message  
discarded, no notification needed"


Regards
Falko

Am 08.06.2009 um 20:25 schrieb Alejandro Guerrieri:

afaik, no. It could lead to undesired results, specially if your  
phone's clock is misconfigured ;)


2009/6/8 Nikos Balkanas 
Of course not the SMSc! I was wondering if the mobiles have validity  
support built in. I.e. Do not display an expired SMS.

- Original Message -
From: Alejandro Guerrieri
To: Nikos Balkanas
Cc: Beatrice Tamburrino ; users@kannel.org
Sent: Monday, June 08, 2009 9:13 PM
Subject: Re: Get notification if SMS has been discarded from SMSC

afaik, the smsc only knows if the message has been _delivered_ to  
the phone, it cannot tell if you _really_ looked into it (how could  
it do that?), so the validity period is only relevant while the  
message is waiting at the smsc.


Regards,

Alejandro

2009/6/8 Nikos Balkanas 
Does the validity period affect only retention at the SMSc, or does  
it also affect display on the mobile? I.e. if an sms is delivered  
OK, but not viewed in the mobile until later.


Nikos
- Original Message -
From: Alejandro Guerrieri
To: Beatrice Tamburrino
Cc: users@kannel.org
Sent: Monday, June 08, 2009 6:56 PM
Subject: Re: Get notification if SMS has been discarded from SMSC

No idea about the EMI protocol (I'm mostly an SMPP guy). The  
validity period works on SMPP (assuming the SMSC honors it, of  
course).


Regards,

Alejandro

On Mon, Jun 8, 2009 at 5:26 PM, Beatrice Tamburrino > wrote:

Or sending a validity period flag with the OT-53 String.. ?





 Original-Nachricht 
> Datum: Mon, 08 Jun 2009 17:19:39 +0200
> Von: "Beatrice Tamburrino" 
> An: Alejandro Guerrieri 
> CC: users@kannel.org
> Betreff: Re: Get notification if SMS has been discarded from SMSC

> My provider just told me that the max. validity time is 48 hours.  
And the

> SMSC sends me an OT-53.
>
> It would be nice if I could delete the SMS (in the SMSC) after about
> 15minutes..
>
> mmhh... headache..
>
>  Original-Nachricht 
> > Datum: Mon, 8 Jun 2009 17:07:52 +0200
> > Von: Alejandro Guerrieri 
> > An: Beatrice Tamburrino 
> > CC: Nikos Balkanas , users@kannel.org
> > Betreff: Re: Get notification if SMS has been discarded from SMSC
>
> > Are you sure the SMSC is actually notifying you when it discards a
> > message?
> > Regards,
> >
> > Alejandro
> >
> > On Mon, Jun 8, 2009 at 5:03 PM, Beatrice Tamburrino <
> > beatrice.tamburr...@gmx.ch> wrote:
> >
> > > hi,
> > >
> > > thanks, this seem to be a different mask?
> > >
> > > I set the dlr-mask = 31? ??
> > >
> > > I think I need more help here..
> > >
> > >  Original-Nachricht 
> > > > Datum: Mon, 8 Jun 2009 17:46:23 +0300
> > > > Von: "Nikos Balkanas" 
> > > > An: "Beatrice Tamburrino" ,
> > users@kannel.org
> > > > Betreff: Re: Get notification if SMS has been discarded from  
SMSC

> > >
> > > > Sure it does:
> > > >
> > > > #define DLR_SMSC_FAIL   0x10
> > > >
> > > > Just use the right dlr-mask
> > > >
> > > > BR,
> > > > Nikos
> > > > - Original Message -
> > > > From: "Beatrice Tamburrino" 
> > > > To: 
> > > > Sent: Monday, June 08, 2009 4:34 PM
> > > > Subject: Get notification if SMS has been discarded from SMSC
> > > >
> > > >
> > > > > Hi!
> > > > >
> > > > > I've almost finished my SMS Application which sends SMS to a
> Kannel
> > > > Server
> > > > > and waits on a Port for dlr's. Im facing only one problem  
right

> now,
> > I
> > > > > hope somebody can help me on that..
> > > > >
> > > > > Im using the emi protocol to a provider. The provider  
supports the

> > > > > extended operations OT 51-58, where OT-56 is: Delete Message
> > operation.
> > > > >
> > > > > So the problem is, that if I receive a dlr code=4, the  
message

> will
> > be
> > > > > buffered on the SMSC. After a while (I suppose that  
configurations

> > is
> > > > made
> > > > > by the provider) the buffered message will be descarded  
from the

> > SMSC.
> > > > But
> > > > > my application dosn't get any notification (or the kannel  
client

> is
> > not
> > > > > getting any notification).
> > > > >
> > > > > Is kannel able to handle that information from SMSC with  
the EMI

> > > > protocol?
> > > > > Any ideas?
> > > > >
> > > > > xox beatrice
> > > > > --
> > > > > GMX FreeDSL mit DSL 6.000 Flatrate und Telefonanschluss  
nur 17,95

> > > > > Euro/mtl.!
> > > > >
> > > >
> > >
> >
> http://dslspecial.gmx.de/freedsl-aktionspreis/?ac=OM.AD.PD003K11308T4569a
> > > > >
> > >
> > > --
> > > GMX FreeDSL mit DSL 6.000 Flatrate und Telefonanschluss nur  
17,95

> > > Euro/mtl.!
> > >
> >
> http://dslspecial.gmx.de/freedsl-aktionspreis

Re: DLR but could not find message...

2009-06-09 Thread Latitude Berlin 
Thanks Benaiad.
It works now.


On Tue, Jun 9, 2009 at 3:12 AM, Benaiad  wrote:

> try the smsc group parameter "msg-id-type = 0x01".
>
>
>
> On Mon, Jun 8, 2009 at 8:05 PM, Latitude Berlin  googlemail.com> wrote:
>
>> Hi,
>>
>> I am having problems with DLR. I read few threads on this but didn't find
>> the right answer. Please go through he following log:
>>
>> ...
>> DEBUG: DLR[internal]: Adding DLR smsc=test, ts=3B98186D, src=ABCDEF,
>> dst=, mask=7, boxc=dlrbox
>> ...
>> DEBUG: DLR[internal]: Looking for DLR smsc=test, ts=0999823469,
>> dst=, type=1
>> WARNING: DLR[internal]: DLR for DST not found.
>> ERROR: SMPP[test]: got DLR but could not find message or was not
>> interested in it id<0999823469> dst, type<1>
>> ...
>>
>> When SMS is sent, message id we get (in SM_DELIVER_RESP) is encoded in 8
>> hex digits
>> message-id in the received DLR is encoded as 10 decimal digits
>>
>> How to handle this?
>>
>> Thanks a lot.
>>
>> Cheers
>>
>>
>>
>

Re: optional parameters

2009-06-09 Thread narendra reddy 
HI Nikos,

 thanks for giving reply .
  there is no way to handle TLV parameters.because for
me atleast i want to sar_total_segments.

pls give me any idea.

2009/6/8 Nikos Balkanas 

>  Hi,
>
> For command line parameters, you should use gwlib/utils.c:
> get_and_set_debugs. For configuration variables define them in
> gwlib/cfg.def.
>
> Then you have to support them from the code.
>
> Note that if you do that, you will branch off cvs, and updates will require
> merging, which is much more difficult to do. You will also need to be
> experienced in C and kannel. Else do not attempt it.
>
> BR,
> Nikos
>
> - Original Message -
> *From:* narendra reddy 
> *To:* users@kannel.org
> *Sent:* Monday, June 08, 2009 10:34 AM
> *Subject:* optional parameters
>
>
> Hi list,
>
>
>  according  to my requirement  i want to use some optional parameters in my
> project. how can i add the optional parameters in the config file .pls give
> me some guidence regarding on optional parameters.
>
>
>
> Best Regards,
> K.narendra
>
>


-- 
Best Regards,
narendra Reddy.