Hi All,
While running Kannel 1.3.1 in Cygwin the following error message was
printed to screen by the bearerbox:
7 [unknown (0x74C)] bearerbox 1960 pthread_cond::Signal: Released too
many threads - 1 now 1 originally
Any ideas what might have caused this and what the implications are?
Regards,
Thanks Nisan,
BTW, you patch (TLV, receipted_message_id, message_state) works well for
me. Do you know if this patch will go to official CVS tree?
Nisan Bloch wrote:
At 12:34 PM 4/4/03 +0500, David Chkhartishvili wrote:
Nope,
I'm getting message:
INFO: NOTE: sender and receiver same number <
At 12:34 PM 4/4/03 +0500, David Chkhartishvili wrote:
Nope,
I'm getting message:
INFO: NOTE: sender and receiver same number <520>, ignoring!
mm.. this is a bug we found the other day.. i cannot get to the code now,
will pull patch later.
nisan
Nisan Bloch wrote:
Hi
At 11:09 AM 4/4/03 +0
Nope,
I'm getting message:
INFO: NOTE: sender and receiver same number <520>, ignoring!
Nisan Bloch wrote:
Hi
At 11:09 AM 4/4/03 +0500, David Chkhartishvili wrote:
Hi Bruno,
I didn't followed to cvs tree for a bit, and I was suprised that my
mo doesn't come to smsbox (same config works well
Hi,
for smsc, pushes are just another binary message. Only the phone
know the difference between say ringtone and mms notification.
Aarno
On Friday, April 4, 2003, at 03:44 AM, Guanghua Hou wrote:
Hi,
UDH header is WDP header, not SMPP header. SMSC system will treate WDP
PDU
as a short message
Hi
At 11:09 AM 4/4/03 +0500, David Chkhartishvili wrote:
Hi Bruno,
I didn't followed to cvs tree for a bit, and I was suprised that my mo
doesn't come to smsbox (same config works well with older versions).
Do you get a message "No sender/reciever" in your smsbox logs?
Nisan
I've read cvs doc
Hi Bruno,
I also tested it with current CVS tree, same result.
And one more question,
I didn't followed to cvs tree for a bit, and I was suprised that my mo
doesn't come to smsbox (same config works well with older versions).
I've read cvs documantation, and I didn't find any big changes in
sms-
Hi,
UDH header is WDP header, not SMPP header. SMSC system will treate WDP PDU
as a short message and transfer it to mobile terminal transparently. SMSC
won't parse WDP header. So only SMPP header can be used to distinguish
different application by SMSC.
BR,
Guanghua Hou
> Guanghua Hou wrote:
>
Citando David Chkhartishvili <[EMAIL PROTECTED]>:
> Here is smsbox log. original message I've sent was: 99182418*t t t t
> and curillic letter on the end. You can see that '@' sign was added
> before all characters.
>
>
> 2003-03-28 18:16:02 [4] INFO: Starting to service <@[EMAIL PROTECTED]@[EM
Charlie Clark wrote:
>
> just started playing with Kannel - the main installation is on a machine I
> don't have access to and I've a couple of questions. I'll be setting up my
> own test intall under Cygwin but it seems to need a crypto library which I
> don't have. Anybody know which package I n
Enzo dell'Aquila wrote:
>
> Hi Aarno,
>
> Sharp GX10 works well if you don't send AF, so Kannel PPG should have no
> problem with Sharp. Other Openwave browsers should work too.
so there is no problem here? is this right?
Stipe
[EMAIL PROTECTED]
Hi,
just started playing with Kannel - the main installation is on a machine I
don't have access to and I've a couple of questions. I'll be setting up my
own test intall under Cygwin but it seems to need a crypto library which I
don't have. Anybody know which package I need to install to use it
Aarno Syvänen wrote:
> > To which group should this go? wapbox?
>
> To ppg core, i think, because ppg does the parsing.
yep, agreed.
Stipe
[EMAIL PROTECTED]
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf
Tel: +49-211-7
On Thursday, April 3, 2003, at 04:58 PM, Stipe Tolj wrote:
Paul Keogh wrote:
My understanding is that the MIME RFCs specify a canonical encoding of
a "blank line" or separator of . The obvious use of this is
to get around differences across operating systems in this regard.
(Think UNIX vs. Microso
Actually, currently, Kannel does not send AF at all. This, according to
the specs, means that 'wml.ua' is assumed.
Do Openvawe browsers require AF 82, or do they work without ? Adding
this would not broke anything.
Aarno
On Thursday, April 3, 2003, at 05:00 PM, Stipe Tolj wrote:
Enzo dell'Aqui
if you think this is a bug, please submit a bug report to
http://bugs.kannel.org/
Stipe
[EMAIL PROTECTED]
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf
Tel: +49-211-74845-0
Fax: +49-211-74845-299
E-Mail: [EMAIL PROTECTE
Enzo dell'Aquila wrote:
>
> Hi,
>
> I don't know how PPG in Kannel sends Wap Push SMS, so please check. I
> read previous mails of this mailing-list and various examples on internet
> and I found that PDU WSP part is generally encoded so:
> ..
> ..
> AF : X-Wap-Application-ID
> 80
Paul Keogh wrote:
>
> My understanding is that the MIME RFCs specify a canonical encoding of
> a "blank line" or separator of . The obvious use of this is
> to get around differences across operating systems in this regard.
> (Think UNIX vs. Microsoft).
>
> So accepting a as a MIME separator may
> Hi Paul,
>
> Paul Keogh wrote:
>
> > -1.
> >
> > IMHO, this badly breaks MIME handling. If you have to override
> > the MIME separator, it should at least be configurable.
>
> can you point this out a bit more, please?
>
My understanding is that the MIME RFCs specify a canonical encoding of
Hi,
I don't know how PPG in Kannel sends Wap Push SMS, so please check. I
read previous mails of this mailing-list and various examples on internet
and I found that PDU WSP part is generally encoded so:
..
..
AF : X-Wap-Application-ID
80 : x-wap-application:*
..
..
This DON'T w
Crlf would work, as I said before. Mime parsing would look after
two kind of separators. But, yes, configuration directive like
mime-parsing = strict/sloppy would be nice.
Aarno
On Thursday, April 3, 2003, at 02:58 PM, Paul Keogh wrote:
I changed mime parsing to that Kannel would accept lf as a
s
Dziugas Baltrunas wrote:
>
> thank you VERY much.
>
> Stipe, I think this DLR issue is "special" for CIMD2 connections because
> they are violating logics, i.e. they don't accept that 0 ("zero") means
> nothing, i.e. not to request a delivery report. I haven't heard similar
> issue with SMPP.
hm
Hi Paul,
Paul Keogh wrote:
> -1.
>
> IMHO, this badly breaks MIME handling. If you have to override
> the MIME separator, it should at least be configurable.
can you point this out a bit more, please?
Stipe
[EMAIL PROTECTED]
---
On Thu, Apr 03, 2003 at 02:25:25PM +0200, Stipe Tolj wrote:
> Hi list,
> this is a pending patch from "Rene Kluwen" <[EMAIL PROTECTED]>.
> It's a bit older, so don't blame me if it does not apply cleanly ;)
> Can somebody who uses AT2 module a lot check this and vote for
> commitment please?! Ode
thank you VERY much.
Stipe, I think this DLR issue is "special" for CIMD2 connections because
they are violating logics, i.e. they don't accept that 0 ("zero") means
nothing, i.e. not to request a delivery report. I haven't heard similar
issue with SMPP.
regards,
Dziugas Baltrunas
On Thu, 3 Apr
I changed mime parsing to that Kannel would accept lf as a
separator. This should help Ritesh, and lots of use lf as a
separator anyway. Will commit this, if there is interest.
Crlf separator still works, of course.
-1.
IMHO, this badly breaks MIME handling. If you have to override
the MIME se
--- Begin Message ---
ok, this has been commited to cvs now.
But we *SHOULD* abstract this to the upper SMSCConn layer, so that the
new config directive is available for all SMSC module types.
Stipe
[EMAIL PROTECTED]
---
Wapme
Aarno Syvänen wrote:
>
> I changed mime parsing to that Kannel would accept lf as a
> separator. This should help Ritesh, and lots of use lf as a
> separator anyway. Will commit this, if there is interest.
>
> Crlf separator still works, of course.
+1, go ahead!
Stipe
[EMAIL PROTECTED]
---
Hi list,
this is a pending patch from "Rene Kluwen" <[EMAIL PROTECTED]>.
It's a bit older, so don't blame me if it does not apply cleanly ;)
Can somebody who uses AT2 module a lot check this and vote for
commitment please?! Oded, how about you?!
Stipe
[EMAIL PROTECTED]
---
I changed mime parsing to that Kannel would accept lf as a
separator. This should help Ritesh, and lots of use lf as a
separator anyway. Will commit this, if there is interest.
Crlf separator still works, of course.
Aarno
On Thursday, April 3, 2003, at 01:30 PM, Ritesh Shah wrote:
Hi Aarno,
p
ok, this has been commited to cvs now.
But we *SHOULD* abstract this to the upper SMSCConn layer, so that the
new config directive is available for all SMSC module types.
Stipe
[EMAIL PROTECTED]
---
Wapme Systems AG
Vogelsanger Weg
Clean patch, my vote is +1 for this.
It does minimal changes, and does not modify the default behaviour if the
new directive is not used.
Angel Fradejas
Mediafusion Espana, S.A.
[EMAIL PROTECTED]
www.mediafusion.es
Tel. +34 91 252 32 00
Fax +34 91 572 27 08
-Mensaje original-
De: [EMAIL
Guanghua Hou wrote:
>
> When push message is sent through SMSC. SMPP v3.4 'submit_sm' is used by
> kannel. Kannel sets 'service_type'as NULL and 'protocol-id' as zero.The
> short message is WDP/WSP encoded PDU.
>
> When this message is sent to Terminal, how does the terminal distinguish
> applica
Hi Vijay,
Vijay Patwari wrote:
>
> Hello All,
> i hve an smil file cats.smil( which contains text
> "cat" image & audio) , i wnt it to be represented it
> into mms (.mms), hw this possible.., can u say me.
> hw to create mms message. say me.
first I'd like to ask you an counter-question
Hi,
When push message is sent through SMSC. SMPP v3.4 'submit_sm' is used by
kannel. Kannel sets 'service_type'as NULL and 'protocol-id' as zero.The
short message is WDP/WSP encoded PDU.
When this message is sent to Terminal, how does the terminal distinguish
application type of short message? Ho
35 matches
Mail list logo
