Flash [mclass = 1] not working
Hi regarding the following mail, I just compiled and tried kannel Dec 12 cvs release, when I tried to send flash sms to SH 888 it dodn't recognize it and message could not be flashed but when I tried it on Ericsson A2618s the message was flash one. What I don't understand is why this patch which I applied to 1.1.5 worked forevery mobile and the latest release is not capable of sending flash to every mobile? Ihtink the mclass implementatin is different from this dcs patch, and in my opinion dcs patch should be implemented in stead of current one because it supports every mobile regards Steve - Original Message - From: "SMS" <[EMAIL PROTECTED]> To: "kannel Support" <[EMAIL PROTECTED]> Sent: Thursday, December 13, 2001 11:11 AM Subject: Fw: DCS support [patch] > please someone guide me on this > > regards > Steve > > - Original Message - > From: "SMS" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, November 26, 2001 11:42 AM > Subject: Fw: DCS support [patch] > > > > I'm attaching the email which for reference, it has a patch to send flash > > messages and this works for every phone ncluding Ericsson SH 888. I > applied > > this patch to 1.1.5 release and it worked fine, I wanna know if the > > implementaion in urrent cvs for flash messages is different from this? > > > > and whats the actual problem I can't send flash sms through the smae SMSC > > with current release, which works with this patch > > > > regards > > Steve > > - Original Message - > > From: "Andreas Fink" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Wednesday, May 16, 2001 9:37 PM > > Subject: DCS support [patch] > > > > > > > Here's a patch to make DCS supported in emi2 and http SMSC protocols. > > > Could someone adapt it for the other SMSC types? I'm no familiar with > > > cimd or smpp nor can I test it. > > > > > > How does it work? > > > > > > I've added a new Kannel header called > > > > > > X-Kannel-DCS > > > > > > if set, the value is added to the XSer fields as it is done with UDH. > > > You can omit the XSer type (which is 2) and length fields as with UDH > > > as well. If a message from the mobile arrives, the XSer2 field is now > > > also read out and passed along to the HTTP server serving the > > > request. For example to send a flash SMS as return to a request > > > coming from a user, your webserver has to return: > > > > > > X-Kannel-DCS: F0 > > > > > > while forcing a sending of a message, add &dcs=%F0. For example: > > > > > > > > > http://yourhost:8001/cgi-bin/sendsms?&user=xxx&pass=xxx&to=12345&text=hello% > > 20world&dcs=%F0 > > > > > > To be tested and commited to the CVS if no serious problems are found. > > > > > > -- > > > > > > Andreas Fink > > > Fink-Consulting > > > > > > -- > > > Tel: +41-61-6932730 Fax: +41-61-6932729 Mobile: +41-79-2457333 > > > Address: A. Fink, Schwarzwaldallee 16, 4058 Basel, Switzerland > > > E-Mail: [EMAIL PROTECTED] Homepage: http://www.fink.org/ > > > -- > > > Something urgent? Try http://www.smsrelay.com/ Nickname afink > > > > > > > > > > > > > > > > > > > dcs_support.diff Description: Binary data
Re: Open problem with WAPPush routing
Hi List, Jörg Pommnitz wrote: > > Hi Aarno, > some time ago we discussed the problems with routing PAP-requests > through IPv4 or SMS bearers. Do you have a proper fix or should > I provide a band aid? Fix to this (amongst other things) is in CVS. Aarno
RE: varargs problem and PPC
Hi Again
There was an error in the last file I sent for non-ppc or s390
platforms.
Here is the new one.
Jacob
-Original Message-
From: Jacob Vennervald Madsen
Sent: 12. december 2001 16:53
To: 'Jörg Pommnitz'
Cc: '[EMAIL PROTECTED]'
Subject: RE: varargs problem and PPC
Hi List
I got some help from a guy called Kevin on the SuSE PPC mailing list to
solve this problem.
Here is Kevins explanation of the problem:
Hi Jacob,
Arrgghh! They are passing addresses of va_lists all over the place.
Under ppc linux and s390 linux, va_list is actualy based on an array
type.
So they are trying to pass the address of the array (which itself is a
pointer) and all hell breaks loose.
They then assume the *args is a va_list argument everyplace.
Passing addresses of a va_list is not portable in any way AFAIK.
I have no idea if what I did even compiles but you should get the
general
idea. Just think that va_list is an array. Taking the address of an
array makes no sense (you pass the array and it is automatically a
pointer)
and then taking the contents of that also can be an issue.
Whereas passing the address of an element of the array is perfectly
fine.
I tried something using macros that may do the trick.
Hope this helps.
Kevin
***
After minor corrections in the files he sent me I finally got it
working.
It works with both version 1.1.5 and the cvs version.
I've attached the new octstr.c file.
Jacob
-Original Message-
From: Jörg Pommnitz [mailto:[EMAIL PROTECTED]]
Sent: 12. december 2001 12:35
To: Jacob Vennervald Madsen
Cc: '[EMAIL PROTECTED]'
Subject: varargs problem and PPC
Hi Jacob,
I did a quick Google search for varargs and PPC and it seems
that this is really special on this architecture. I suspect
that the current Kannel code is incompatible with the PPC
varags ABI. Since I do not have access to such hardware I'm afraid
I cannot help you. Your best bet would be to upgrade your
glibc. If this still fails, you might want to try Darwin
on this machine. Andreas Fink reports that Kannel works
just fine with MacOSX on PPC, so Darwin should be OK as well.
I don't know whether Darwin runs on IBM hardware. Alternatively
one of the other BSD ports to the PPC should be fine, too. After
all, Darwin is BSD based.
Regards
Jörg
-Original Message-
From: Jacob Vennervald Madsen
To: Jörg Pommnitz
Sent: 12/12/01 10:10 AM
Subject: RE: Ref-Counted octstr
I've done that and I've left out -lssl as well.
When i try to run it I get a Segmentation fault again.
The backtrace from debugging gives me this:
#0 0x10010728 in convert (os=0x10150eb0, format=0x7678,
fmt=0x7698, args=0x769c) at gwlib/octstr.c:1841
#1 0x10010e94 in octstr_format_valist (fmt=0x1001721f "d\", a String
\"%s\" and an Octstr \"%S\"", args=0x7730) at gwlib/octstr.c:1989
#2 0x10010d0c in octstr_format (fmt=0x0) at gwlib/octstr.c:1960
#3 0x10001760 in main ()
#4 0x0fda7680 in __libc_start_main () from /lib/libc.so.6
Jacob
-Original Message-
From: Jörg Pommnitz [mailto:[EMAIL PROTECTED]]
Sent: 12. december 2001 09:43
To: Jacob Vennervald Madsen
Subject: RE: Ref-Counted octstr
Leave -lcrypto out of the compile command.
Regards
Jörg
-Original Message-
From: Jacob Vennervald Madsen
To: Jörg Pommnitz
Sent: 12/12/01 9:21 AM
Subject: RE: Ref-Counted octstr
This is what I get when trying to compile the code you sent me:
/usr/powerpc-suse-linux/bin/ld: cannot find -lcrypto
collect2: ld returned 1 exit status
Jacob
-Original Message-
From: Jörg Pommnitz [mailto:[EMAIL PROTECTED]]
Sent: 11. december 2001 17:21
To: Jacob Vennervald Madsen
Subject: RE: Ref-Counted octstr
Yes, I saw it. I'm unsure what's going on. The gdb
backtrace you posted did show that a pointer was NULL that
should not be.
Please run the following program:
#include "gwlib/gwlib.h"
int
main (int argc, char*argv[])
{
Octstr *result;
gwlib_init();
result = octstr_format("A number \"%d\", a String \"%s\" and an
Octstr
\"%S\"",
123,
"the C string",
octstr_imm("the Octstr"));
debug ("debug", 0, "Result: %s", octstr_get_cstr(result));
octstr_destroy (result);
gwlib_shutdown();
return 0;
}
Compile it with
gcc -I ../gateway -o bug bug.c ../gateway/libgwlib.a -lcrypto -lssl
-lpthread -lxml2
Regards
Jörg
-Original Message-
From: Jacob Vennervald Madsen
To: Jörg Pommnitz
Sent: 12/11/01 5:00 PM
Subject: RE: Ref-Counted octstr
Did you se the warnings I get when I compile?
I posted them earlier today.
Jacob
-Original Message-
From: Jörg Pommnitz [mailto:[EMAIL PROTECTED]]
Sent: 11. december 2001 16:50
To: Jacob Vennervald Madsen
Subject: RE: Ref-Counted octstr
It should not hurt, but it is completely unrelated to your problem.
Regards
Jörg
-
mutex failure?
Can someone tell me what this message is exactly all about? 2001-12-13 15:13:38 [16] PANIC: mutex_unlock: Mutex failure! 2001-12-13 15:13:38 [16] PANIC: System error 22: Invalid argument I get it in my app while using gwlib. I'm not using any mutexes. I'm using octstr stuff, http stuff, lists, config and thats about it. the odd thing is that this only happens if running memory=native but not with memory=checked. I dont have an idea why any of those areas would need to unlock a mutex. -- Andreas Fink Fink-Consulting -- Tel: +41-61-6932730 Fax: +41-61-6932729 Mobile: +41-79-2457333 Address: A. Fink, Schwarzwaldallee 16, 4058 Basel, Switzerland E-Mail: [EMAIL PROTECTED] Homepage: http://www.finkconsulting.com -- Something urgent? Try http://www.smsrelay.com/ Nickname afink
RE: mutex failure?
The things you are using are thread safe, so they lock their
inner state against concurrent access. You might want to add
a wrapper around mutex_unlock in the following way:
#define mutex_unlock(mtx)
mutex_unlock_inline(mtx,__FILE__,__LINE__,__PRETTY_FUNCTION__)
static inline mutex_unlock_inline(Mutex mtx, const char *file, int line,
const char *func) {
debug("mutex", 0, "mutex_unlock called from %s: %d in function %s", file,
line, func);
mutex_unlock_real(mtx);
}
and rename the real mutex_unlock call to mutex_unlock_real.
This should give you an idea what mutex calls misbehave.
BTW.: Did you test the EMI2 code from todays CVS? I think your problems
should be fixed now.
Regards
Jörg
-Original Message-
From: Andreas Fink
To: [EMAIL PROTECTED]
Sent: 12/13/01 4:29 PM
Subject: mutex failure?
Can someone tell me what this message is exactly all about?
2001-12-13 15:13:38 [16] PANIC: mutex_unlock: Mutex failure!
2001-12-13 15:13:38 [16] PANIC: System error 22: Invalid argument
I get it in my app while using gwlib. I'm not using any mutexes. I'm
using octstr stuff, http stuff, lists, config and thats about it. the
odd thing is that this only happens if running memory=native but not
with memory=checked.
I dont have an idea why any of those areas would need to unlock a mutex.
--
Andreas Fink
Fink-Consulting
--
Tel: +41-61-6932730 Fax: +41-61-6932729 Mobile: +41-79-2457333
Address: A. Fink, Schwarzwaldallee 16, 4058 Basel, Switzerland
E-Mail: [EMAIL PROTECTED] Homepage: http://www.finkconsulting.com
--
Something urgent? Try http://www.smsrelay.com/ Nickname afink
Re: AW: charset_latin1_to_gsm in msg_to_pdu
Jörg Pommnitz <[EMAIL PROTECTED]> writes: > It's probably a bug. The call should be made when coding is 1 > (e.g. GSM 7bit character set). > How is it possible to deduce the character set in that function (msg_to_pdu)? There is no field for it in SMPP or Msg. Or am I missing something? Worik > Regards > Jörg > > > -Ursprüngliche Nachricht- > > Von: Worik Macky Turei Stanton [mailto:[EMAIL PROTECTED]] > > Gesendet am: Dienstag, 11. Dezember 2001 00:12 > > An: kannel-devel > > Betreff: charset_latin1_to_gsm in msg_to_pdu > > > > Friends > > > > Whhat is the purpose of the call to charset_latin1_to_gsm in > > msg_to_pdu? > > > > It is only called if the udhdata length is not 0. > > > > Worik > > -- > > Worik > > Macky Turei Stanton > > Whew! > > [EMAIL PROTECTED] > > > > Aotearoa > > > > > > > -- Worik Macky Turei Stanton Whew![EMAIL PROTECTED] Aotearoa
Re: SMSBox PANIC
> Oh no. There's still a bug in smsbox.c with msgdata == NULL ? > > g.. I'll take a look at it. Great, thanks Bruno! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
