The difference that it makes is this:

 

struct tm gw_gmtime(time_t t)

{

    struct tm tm;

 

#ifndef HAVE_GMTIME_R

    lock(GWTIME);

    tm = *gmtime(&t);

    unlock(GWTIME);

#else

    gmtime_r(&t, &tm);

#endif

 

    return tm;

}

 

But since I have the same value, I guess this is not the issue that I was
looking for.

 

== Rene

 

From: Alexander Malysh [mailto:malys...@gmail.com] On Behalf Of Alexander
Malysh
Sent: zondag 24 februari 2013 21:22
To: Rene Kluwen
Cc: '[Digital^Dude] R'; users@kannel.org
Subject: Re: Long Messages using httpsmsc

 

#define HAVE_GMTIME_R 1

 

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

 

Alex

 

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





What is your value of HAVE_GMTIME_R in gw-config.h?

 

== Rene

 

From: Alexander Malysh [mailto:malys...@gmail.com] On Behalf Of Alexander
Malysh
Sent: zondag 24 februari 2013 12:44
To: Rene Kluwen
Cc: '[Digital^Dude] R'; users@kannel.org
Subject: Re: Long Messages using httpsmsc

 

Rene,

 

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

 

Alex

 

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






Please, Alexander.

Fix this bug. Because I've got other clients with the same issue.

I haven't had time myself to look into it.

 

== Rene

 

From:  <mailto:users-boun...@kannel.org> users-boun...@kannel.org
[mailto:users- <mailto:boun...@kannel.org> boun...@kannel.org] On Behalf
Of[Digital^Dude] R
Sent: vrijdag 22 februari 2013 10:03
To: Alexander Malysh
Cc:  <mailto:users@kannel.org> users@kannel.org
Subject: Re: Long Messages using httpsmsc

 

Hi,

 

sar support has been commited yesterday, enjoy :-)

I tried my best to enjoy but the latest svn revision throws up:
"SMSC returned error code 0x00000062 (Invalid message validity period) in
response to submit_sm"

 

Alex

 

Am 22.02.2013 um 08:48 schrieb [Digital^Dude] R <
<mailto:millennium....@gmail.com> millennium....@gmail.com>:







Hi,

 

sar_ within HTTP SMSC???

 

Obviously its not in the http smsc! ! !
So can I assume that when kannel tells me that "MO concatenated message
handling is enabled", I should only think of the UDH mode? If yes, is there
a patch for kannel that makes the 'sar' method available?
I found a patch that was committed by Stipe at:
<http://www.mail-archive.com/devel@kannel.org/msg11322.html>
http://www.mail-archive.com/devel@kannel.org/msg11322.html
however, I am unable to get the patch applied on any of the 50xx svn
revisions.
Thanks for the help!

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

 

Alex

 

Am 21.02.2013 um 13:06 schrieb [Digital^Dude] R <
<mailto:millennium....@gmail.com> millennium....@gmail.com>:







On Fri, Feb 8, 2013 at 3:36 PM, Ali Kashif <
<mailto:syedalikas...@gmail.com> syedalikas...@gmail.com> wrote:

 

try adding following in CORE section.

 

sms-combine-concatenated-mo = true

sms-combine-concatenated-mo-timeout = "1800"

 

 

 

and in your httpSMSC 

 

max-sms-octets= 1260

 


I guess the only way to do this is via 
sar_segment_seqnum
and
sar_total_segments

Any implementation for that already done?

 

 

 

 

 

Reply via email to