RE: SAR

2002-11-13 Thread Igor Ivoilov 
Title: RE: SAR





Hi Denzel,


Nack reaction was not implemented in early version of sar.patch. But version that's come to cvs has this feature.
Did you experience nack problems with this version?


Igor


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 13, 2002 10:20 PM
To: kannel-mailing-list
Subject: SAR



Hi list!


Here's a SAR patch we made ( diffrent to Igore's). We tested this with an earlier CVS ( may be in sync with gateway1.2.0 ). Nack's are implemented. And we had a problem with igore's patch, cause sometimes the nacks failed .


patch for earlier CVS - my-patch.diff




Any way, I created a patch with the current CVS. Didn't test it with new CVS though.


( cvs diff -u gateway-cvs/wap  csv.patch ) == cvs.patch



Send ur comments.





urs,
denzel.

RE: Can't talk HTTP to cygwin build

2002-11-13 Thread Schaich, Peter 
Are you really sure you using the 1.2.1 version?

I have built and run the 1.2.1 version on Windows 2000
without any problems and it works.
But my log output looks totally different than yours,
for example (anonymized):


2002-11-12 14:24:02 [0] INFO: Debug_lvl = 0, log_file = none, log_lvl = 0
2002-11-12 14:24:02 [0] DEBUG: Kannel smsbox version `1.2.1'.
System CYGWIN_NT-5.0, release 1.3.12(0.54/3/2), version 2002-07-06 02:16,
machin
e i686.
Hostname xxx, IP xx.xxx.xxx.xxx.
Libxml version 20423.
Using OpenSSL 0.9.6g 9 Aug 2002.
Using native malloc.

2002-11-12 14:24:02 [0] INFO: Starting to log to file smsbox.log level 0
2002-11-12 14:24:02 [0] INFO: Added logfile `smsbox.log' with level `0'.
2002-11-12 14:24:02 [0] INFO: Service global sender set as '+49xxx'
2002-11-12 14:24:02 [0] DEBUG: HTTP: Opening server at port 13013.
2002-11-12 14:24:02 [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller)
2002-11-12 14:24:02 [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread)
2002-11-12 14:24:02 [0] INFO: Set up send sms service at port 13013
2002-11-12 14:24:02 [0] DEBUG: Started thread 3 (gw/smsbox.c:sendsms_thread)
2002-11-12 14:24:02 [0] DEBUG:
--
2002-11-12 14:24:02 [0] DEBUG: Kannel smsbox version 1.2.1 starting
2002-11-12 14:24:02 [0] DEBUG: Started thread 4
(gw/smsbox.c:obey_request_thread
)
2002-11-12 14:24:02 [0] DEBUG: Started thread 5
(gw/smsbox.c:url_result_thread)
2002-11-12 14:24:02 [0] DEBUG: Started thread 6
(gw/smsbox.c:http_queue_thread)
2002-11-12 14:24:02 [0] INFO: Connected to bearerbox at localhost port
13001.
2002-11-12 14:24:02 [0] DEBUG: Started thread 7
(gw/heartbeat.c:heartbeat_thread
)
2002-11-12 14:49:42 [2] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'.
2002-11-12 14:49:43 [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms
from 
127.0.0.1
2002-11-12 14:49:43 [3] INFO: sendsms used by x
2002-11-12 14:49:43 [3] INFO: sendsms sender:xxx:+49
(127.0.0.1) to:
+49xxx msg:Hello
2002-11-12 14:49:43 [3] DEBUG: message length 5, sending 1 messages
2002-11-12 14:49:44 [3] DEBUG: Status: 202 Answer: Sent.
2002-11-12 14:49:44 [3] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'.
2002-11-12 14:49:44 [1] DEBUG: HTTP: Destroying HTTPClient area 0x100dba50.
2002-11-12 14:49:44 [1] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'.

-Original Message-
From: Ben Blaukopf [mailto:bblaukopf;3glab.com]
Sent: Dienstag, 12. November 2002 18:38
To: [EMAIL PROTECTED]
Subject: Can't talk HTTP to cygwin build 


Code is 1.2.1 and I built on cygwin running on windows 2000 (SP2). Not
entirely sure
how to get the version, but I downloaded and installed on 28/10/02. When I
run
bearerbox and smsbox with smskannel.conf I can't use the HTTP interface for
sending SMSes, because I get no output from it.

Having built with a simple
./configure
make

I then took smskannel.conf and edited the section

# SMSC CONNECTIONS

group = smsc
smsc = at
modemtype = wavecom
device = /dev/ttyS0

This runs fine on linux.

I then
cd gw
./bearerbox -v 1 smskannel.conf

This starts up fine, including configuring the modem

Then (in a separate bash shell)

./smsbox - v 1 smskannel.conf

Again, this works fine, and connects to the bearerbox.

On my linux build I can now connect with a webbrowser to
http://localhost:13013/

and get an appropriate error message. However, if I connect
to the windows build I get nothing at all.

I tried using gdb on the smsbox but it crashed as soon as
I tried to 'run'. However strace worked.

strace shows that before I 'telnet localhost 13013' the smsbox
is doing a select on the port with a timeout of 30 seconds.
1367 145735859 [unknown (0x5CC)] smsbox 832 select_stuff::cleanup: calling
cle
nup routines
 3528 145739387 [unknown (0x5CC)] smsbox 832 select_stuff::~select_stuff:
delet
ng select records
 3547 145742934 [unknown (0x5CC)] smsbox 832 time: 1037121707 = time (0)
 1589 145744523 [unknown (0x5CC)] smsbox 832 cygwin_select: 20, 0x227BF2C4,
0x2
7BF2B4, 0x227BF2A4, 0x227BF314
 3637 145748160 [unknown (0x5CC)] smsbox 832 dtable::select_read: /dev/piper
fd
19
 3394 145751554 [unknown (0x5CC)] smsbox 832 cygwin_select: to-tv_sec 30,
to-
v_usec 0, ms 3
 3267 145754821 [unknown (0x5CC)] smsbox 832 cygwin_select: sel.always_ready
0
 2218 145757039 [unknown (0x5CC)] smsbox 832 select_stuff::wait: m 2, ms
3

Immediately after the telnet command is made, the strace output
then shows the smsbox doing lots of select calls. These continue even after
I have closed the telnet connection - having left the strace session going
for
several minutes it doesn't appear to be an issue of taking a long time
to display that amount of text on screen. I'll follow up if it does stop -
I'll
leave it overnight.  So what's going on? Why doesn't it just accept the
connection,
and handle my GET request? Any ideas gratefully received!

 2204 461753655 [unknown (0xD4)] smsbox 832 socket_cleanup: si 0x100D4B78
si-th
read 0x610C67DC
 3528

RE: kannel 1.2.1 crashes then dlr in use

2002-11-13 Thread GAksenov 

Hello!

It's fantastic!
then i set
dlrmsg-sms.msgdata = octstr_create(); without any checkin
(i think emimsg-fields[E50_AMSG] not defined in 51 type ACK/NAK messages)
all work now.
admittedly, emimsg-fields[E50_AMSG] not initialize previously and may
point to incorrect place.
not NULL but undefined.

p.s. may be somebody check this part code and fix it.

with best wishes
 German Aksenov
phone: (095)258-7258 ext. 7836


   

  Oded Arbel 

  [EMAIL PROTECTED]To:   [EMAIL PROTECTED], 
[EMAIL PROTECTED]
  cc: 

   Subject:  RE: kannel 1.2.1 crashes then 
dlr in use  
  10.11.2002 10:27 

   

   






 -Original Message-
 From: [EMAIL PROTECTED] [mailto:GAksenov;imbank.ru]

 Today i set up some check code into smsc_emi2.c:

 --- smsc_emi2.orig  Wed Sep  4 21:08:52 2002
 +++ smsc_emi2.c Sun Nov 10 10:00:12 2002
 @@ -976,7 +976,11 @@ static int emi2_handle_smscreq (SMSCConn
   * Recode the msg structure with the given msgdata.
   * Note: the DLR URL is delivered in msg-sms.dlr_url
 already.
   */
 -dlrmsg-sms.msgdata =
 octstr_duplicate(emimsg-fields[E50_AMSG]);
 +   dlrmsg-sms.msgdata =
 octstr_duplicate(emimsg-fields[E50_AMSG]);
 +if (dlrmsg-sms.msgdata == NULL) {
 + dlrmsg-sms.msgdata =
 octstr_create();
 + info(0, EMI2[%s]: msgdata is NULL,
 octstr_get_cstr(privdata-name));
 +}
  octstr_hex_to_binary(dlrmsg-sms.msgdata);

You can do it far easier with

dlrmsg-sms.msgdata = emimsg-fields[E50_AMSG] != NULL ?
octstr_duplicate(emimsg-fields[E50_AMSG]) : octstr_create();

and allow the compile to do some more optimizations if it likes to. you
don't really need to log the fact that the message is empty : it gets
sufficiently logged at other places.

--
Oded Arbel
m-Wise mobile solutions
[EMAIL PROTECTED]

+972-9-9581711 (116)
+972-67-340014

::..
If you sell diamonds, you cannot expect to have many customers.
But a diamond is a diamond even if there are no customers.
 -- Swami Prabhupada

Re: delivery reports and EMI [known bug issue]

2002-11-13 Thread Stipe Tolj 
 the problem here is that the number now became suddendly a national number by 
removing the 00 and 41 (country code) and replace it with a national long distance 
prefix 0.
 to fix this is easy. We re-internationalize the number again. However, some users 
might not want to have it this way. So another config variable has to be added maybe 
which I really want to avoid.

can't we use 'unified-prefix' directive with the normalization rules
in it?! This would mean we call normalize_number() somewhere in the
smsc_emi2.c processing before doing the dlr_find()?

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 PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are

Re: Can't talk HTTP to cygwin build

2002-11-13 Thread Ben Blaukopf 

- Original Message -
From: Schaich, Peter [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, November 13, 2002 8:25 AM
Subject: RE: Can't talk HTTP to cygwin build

 Are you really sure you using the 1.2.1 version?
Yes.

 I have built and run the 1.2.1 version on Windows 2000
 without any problems and it works.
 But my log output looks totally different than yours,
 for example (anonymized):
I quoted some sections of strace output, not debug output.

However, here is my debug output, which I should have provided previously
(with debug level 0, not 1 as before). Interposed with yours, with my
commentary
in square brackets.

2002-11-13 09:01:19 [0] INFO: Debug_lvl = 0, log_file = none, log_lvl = 0
2002-11-13 09:01:19 [0] DEBUG: Kannel smsbox version `1.2.1'.
System CYGWIN_NT-5.0, release 1.3.13(0.62/3/2), version 2002-10-13 23:15,
machin
e i686.
Hostname xxx, IP xxx.
Libxml version 20423.
Using OpenSSL 0.9.6g 9 Aug 2002.
Using native malloc.

[ As you'll note, my version of cygwin is slightly different ]
 2002-11-12 14:24:02 [0] INFO: Debug_lvl = 0, log_file = none, log_lvl =
0
 2002-11-12 14:24:02 [0] DEBUG: Kannel smsbox version `1.2.1'.
 System CYGWIN_NT-5.0, release 1.3.12(0.54/3/2), version 2002-07-06 02:16,
 machin
 e i686.
 Hostname xxx, IP xx.xxx.xxx.xxx.
 Libxml version 20423.
 Using OpenSSL 0.9.6g 9 Aug 2002.
 Using native malloc.

2002-11-13 09:01:19 [0] INFO: Service global sender set as '13013'
2002-11-13 09:01:19 [0] DEBUG: HTTP: Opening server at port 13013.
2002-11-13 09:01:19 [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller)
2002-11-13 09:01:19 [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread)
2002-11-13 09:01:19 [0] INFO: Set up send sms service at port 13013
2002-11-13 09:01:19 [0] DEBUG: Started thread 3 (gw/smsbox.c:sendsms_thread)
2002-11-13 09:01:19 [0]
DEBUG: --
2002-11-13 09:01:19 [0] DEBUG: Kannel smsbox version 1.2.1 starting
2002-11-13 09:01:19 [0] DEBUG: Started thread 4
(gw/smsbox.c:obey_request_thread
)
2002-11-13 09:01:19 [0] DEBUG: Started thread 5
(gw/smsbox.c:url_result_thread)
2002-11-13 09:01:19 [0] DEBUG: Started thread 6
(gw/smsbox.c:http_queue_thread)
2002-11-13 09:01:19 [0] INFO: Connected to bearerbox at localhost port
13001.
2002-11-13 09:01:19 [0] DEBUG: Started thread 7
(gw/heartbeat.c:heartbeat_thread

[ These bits are obviously driven by differences in our conf file]
 2002-11-12 14:24:02 [0] INFO: Starting to log to file smsbox.log level 0
 2002-11-12 14:24:02 [0] INFO: Added logfile `smsbox.log' with level `0'.
 2002-11-12 14:24:02 [0] INFO: Service global sender set as
'+49xxx'

 2002-11-12 14:24:02 [0] DEBUG: HTTP: Opening server at port 13013.
 2002-11-12 14:24:02 [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller)
 2002-11-12 14:24:02 [0] DEBUG: Started thread 2
(gwlib/http.c:server_thread)
 2002-11-12 14:24:02 [0] INFO: Set up send sms service at port 13013
 2002-11-12 14:24:02 [0] DEBUG: Started thread 3
(gw/smsbox.c:sendsms_thread)
 2002-11-12 14:24:02 [0] DEBUG:
 --
 2002-11-12 14:24:02 [0] DEBUG: Kannel smsbox version 1.2.1 starting
 2002-11-12 14:24:02 [0] DEBUG: Started thread 4
 (gw/smsbox.c:obey_request_thread
 )
 2002-11-12 14:24:02 [0] DEBUG: Started thread 5
 (gw/smsbox.c:url_result_thread)
 2002-11-12 14:24:02 [0] DEBUG: Started thread 6
 (gw/smsbox.c:http_queue_thread)
 2002-11-12 14:24:02 [0] INFO: Connected to bearerbox at localhost port
 13001.
 2002-11-12 14:24:02 [0] DEBUG: Started thread 7
 (gw/heartbeat.c:heartbeat_thread
 )

[ So effectively identical up to this point. Now I connect to port 13013 by
telnet, web browser,
anything. But I never get any more debug output lines ]

 2002-11-12 14:49:42 [2] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'.
 2002-11-12 14:49:43 [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms
 from 
 127.0.0.1
 2002-11-12 14:49:43 [3] INFO: sendsms used by x
 2002-11-12 14:49:43 [3] INFO: sendsms sender:xxx:+49
 (127.0.0.1) to:
 +49xxx msg:Hello
 2002-11-12 14:49:43 [3] DEBUG: message length 5, sending 1 messages
 2002-11-12 14:49:44 [3] DEBUG: Status: 202 Answer: Sent.
 2002-11-12 14:49:44 [3] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'.
 2002-11-12 14:49:44 [1] DEBUG: HTTP: Destroying HTTPClient area
0x100dba50.
 2002-11-12 14:49:44 [1] DEBUG: HTTP: Destroying HTTPClient for
`127.0.0.1'.

 -Original Message-
 From: Ben Blaukopf [mailto:bblaukopf;3glab.com]
 Sent: Dienstag, 12. November 2002 18:38
 To: [EMAIL PROTECTED]
 Subject: Can't talk HTTP to cygwin build


 Code is 1.2.1 and I built on cygwin running on windows 2000 (SP2). Not
 entirely sure
 how to get the version, but I downloaded and installed on 28/10/02. When I
 run
 bearerbox and smsbox with smskannel.conf I can't use the HTTP interface
for
 sending SMSes, because I get no output from it.

 Having built with a simple
 ./configure
 make

 I then took smskannel.conf and edited the

Re: delivery reports and EMI [known bug issue]

2002-11-13 Thread Andreas Fink 

On Mittwoch, November 13, 2002, at 10:08  Uhr, Stipe Tolj wrote:

the problem here is that the number now became suddendly a national number by removing the 00 and 41 (country code) and replace it with a national long distance prefix 0.
to fix this is easy. We re-internationalize the number again. However, some users might not want to have it this way. So another config variable has to be added maybe which I really want to avoid.

can't we use 'unified-prefix' directive with the normalization rules
in it?! This would mean we call normalize_number() somewhere in the
smsc_emi2.c processing before doing the dlr_find()?



Well we would to have to use it the other way around.
and it would have to be SMSC specific. Imagine you have one EMI link to germany and one to switzerland and you get "country specific" numbers on each of them.

My approach would simply to specify international and national prefixes and country codes on the SMSC link. This would also help on the sending side where a + currently is replaced hardcoded with 00 which is not really always true.

Andreas Fink
Global Networks, Inc.

--
Tel: +41-61-333  Fax: +41-61-6932729   Mobile: +41-79-2457333
Global Networks, Inc. Clarastrasse 3, 4058 Basel, Switzerland
Web: http://www.global-networks.ch/  [EMAIL PROTECTED]
--
Member of the GSM Association

Re: delivery reports and EMI [known bug issue]

2002-11-13 Thread Stipe Tolj 
 That would not be good enough in most cases.

why? I think a primary key consisting of 8 digits of the receiver
number and the timestamp is a pretty unique thing in the DLR table?!

Ok, if you push several messages in the same second to the same
number, then you clash up again to the same situation where you can't
distinguish the messages for the inbound dlr.

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 PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are

Re: Can't talk HTTP to cygwin build

2002-11-13 Thread Ben Blaukopf 

- Original Message -
From: Schaich, Peter [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, November 13, 2002 9:46 AM
Subject: RE: Can't talk HTTP to cygwin build


 Hi,

 how did your URL to connect exactly look like?
My canonical test is:

http://localhost:13013/

Which ought to return an error message like 'unknown service' - I forget
what it is exactly. Similarly if I

telnet localhost 13013
GET /

I ought to get at least something back.

I have tried a properly formed submit of
http://localhost:13013/cgi-bin/sendsms?to=%2B447786916043username=testerpa
ssword=foobartext=blah

tester and foobar being the default username/password for the sendsms-user
group.

 Otherwise, you should try a new Cygwin library.
That does seem to be the best thing to try. I'm going to try and get the
version
you have. Will advise of success/failure.

Ben

Re: Kannel blocking connect again.

2002-11-13 Thread Stipe Tolj 
patch applied, thanks!

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 PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are

[FYI] non-blocking connect() patch applied

2002-11-13 Thread Stipe Tolj 
Hi list,

I just commited Vjacheslav's non-blocking patch to cvs HEAD. The patch
works for me. Please do try this out in test environments and report
problems to the list.

BTW, I'd like to add the smsbox-routing patch too today and make a
development branch release. Should be scale the version number to
1.3.0 for that?! Because of the major improbements, including WTP-SAR,
smsbox-routing, non-blocking, etc.

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 PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are

incoming originator on SMPP

2002-11-13 Thread Andreas Fink 
scenario:

you have

global-sender = "123"

so all your outgoing SMS which dont have from=... set will be from 123
you got one SMPP link. no "my-number" stuff defined.

you get an incoming SMS from that SMPP link and it will be always "to 123" even the sender might have used another short ID.

The problem seems to come from gw/smsc/smsc_smpp.c line 738ff

/* Replace MO destination number with my-number */
if (octstr_len(smpp->my_number)) {
octstr_destroy(msg->sms.receiver);
msg->sms.receiver = octstr_duplicate(smpp->my_number);
}

Removing this, makes it work. However its supposed to be there for a particular reason.
whats the best way to fix this?

Andreas Fink
Global Networks, Inc.

--
Tel: +41-61-333  Fax: +41-61-6932729   Mobile: +41-79-2457333
Global Networks, Inc. Clarastrasse 3, 4058 Basel, Switzerland
Web: http://www.global-networks.ch/  [EMAIL PROTECTED]
--
Member of the GSM Association

Re: Problems with large wap-push?

2002-11-13 Thread Aarno Syvänen 
Notifications worked for me, too, until I send one having only a few
letters in its second segment. This did not work.

Aarno

On Monday, November 11, 2002, at 08:28 PM, Stipe Tolj wrote:


Yes, there is indeed is a bug in wapbox (ppg) sms splitting.
You should
  remove gw/wapbox.c, line

max_msgs = (msg_len/MAX_SMS_OCTETS) + 1;



Are you sure about this ? - it's working OK for me...


yep, our PPG doing MMS notifications works too.

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 PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are

Kannel CDMP

2002-11-13 Thread igor 

What about CDMP (Cellular Digital Messaging Protocol by Motorola)
support in Kannel ? Somebody know projects like Kannel with CDMP 
implementation ?

mailing list downtime

2002-11-13 Thread David Holland 
Hi,

just a heads-up: I'll be upgrading the software (Mailman) on the list
server later today. There'll be a short period when messages don't
immediately get sent out to the list; they'll get queued and sent later.

Cheers,
Dave
-- 
:: David Holland :: Systems Manager :: 3G Lab :: +44 01223 478900 ::

Re: Can't talk HTTP to cygwin build

2002-11-13 Thread Stipe Tolj 
I have similiar effect with even more recent Cygwin builds.

I suppose Cygwin's socket things are somehow broken. If you guys have
the time and interest to test this:

1. pick kannel's test/test_http_server as http server
2. use cygwin 1.3.10 and do a wget to the http server
2. use cygwin 1.3.12, .13, .14, etc. and see what happens.

For me it currently works only with the older cygwin 1.3.10 DLL.

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 PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are

DLRs

2002-11-13 Thread Martin Quevedo 
Hi all !

Is this line,

pdu-u.submit_sm.registered_delivery = 1;

enough to request SMSC to send back a DLR ? or is there any other thing 
to set up ?

Thanks
Martin

Re: delivery reports and EMI [known bug issue]

2002-11-13 Thread Stipe Tolj 
 Well we would to have to use it the other way around.
 and it would have to be SMSC specific. Imagine you have one EMI link to germany and 
one to switzerland and you get country specific numbers on each of them.

I have commited (long time ago, in a galaxy far far away :)) the smsc
specific unified-prefix things.

We use this already in production environment to sync numbering
formats.

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 PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are

Re: delivery reports and EMI [known bug issue]

2002-11-13 Thread Stipe Tolj 
 The point is that in some areas 8 digits would interfear already on the
 areacode level.
 Its better than doing nothing though but its still not really unique.
 
 What happens if you deliver to a short ID which is 3-4 digits only?

yep, that's through, messing things up.

 Well the world is not perfect.
 Maybe we should simply go for 8 digits now until we find a better
 solution.
 Got a patch?

yep, I'd like to look into this too. please.

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 PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are

Re: wapbox crashes

2002-11-13 Thread Stipe Tolj 
 Why is the wapbox crashing when the host requested is not reachable??!
 See log below:
 (After this the wapbox just dies)
 
 /Peter Lofman
 
 2002-11-13 09:29:00 [0] INFO: Added logfile `/var/log/kannel/wapbox-wap.log'
 with level `1'.
 2002-11-13 09:29:00 [0] INFO: Starting to log to file
 /var/log/kannel/wapbox-wap.log level 1
 2002-11-13 09:29:00 [0] INFO:
 
 2002-11-13 09:29:00 [0] INFO: Kannel wapbox version 1.2.0 starting up.
 2002-11-13 09:29:00 [0] INFO: Connected to bearerbox at localhost port
 13002.
 2002-11-13 09:29:19 [17] ERROR: connect failed
 2002-11-13 09:29:19 [17] ERROR: System error 111: Connection refused
 2002-11-13 09:29:19 [17] ERROR: error connecting to server
 `imps.amt.aland.fi' at port `8090'
 2002-11-13 09:29:19 [17] ERROR: Couldn't send request to
 http://hostname.domain.com:8090/
 2002-11-13 09:29:19 [8] ERROR: WSP: http lookup failed, oops.

there is no PANIC here, so does wapbox do crash via segmentation
fault?!

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 PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are

RE: Can't talk HTTP to cygwin build

2002-11-13 Thread Schaich, Peter 
Hello,

hm, for me, Cygwin 1.3.12 works fine
(also with wget)

Regards,

Peter


-Original Message-
From: Stipe Tolj [mailto:tolj;wapme-systems.de]
Sent: Mittwoch, 13. November 2002 13:07
To: Ben Blaukopf
Cc: Schaich, Peter; [EMAIL PROTECTED]
Subject: Re: Can't talk HTTP to cygwin build


I have similiar effect with even more recent Cygwin builds.

I suppose Cygwin's socket things are somehow broken. If you guys have
the time and interest to test this:

1. pick kannel's test/test_http_server as http server
2. use cygwin 1.3.10 and do a wget to the http server
2. use cygwin 1.3.12, .13, .14, etc. and see what happens.

For me it currently works only with the older cygwin 1.3.10 DLL.

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 PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are




Schaich, Peter.vcf
Description: Binary data

Re: DLRs

2002-11-13 Thread Martin Quevedo 




The thing is I am writing a perl script that connects to the smsbox-port
to deliver sm though the kannel. I am setting the dlr_mask =1 and the dlr_ulr
to a local script. However I only get the submit_sm_resp DLR. But the DLR
that comes as a deliver_sm never arrives. 

Any ideas? I could send you the script if you want.

Martin

Andreas Fink wrote:

  
On Mittwoch, November 13, 2002, at 01:08  Uhr, Martin Quevedo wrote: 
  
  Hi all ! 

Is this line, 

pdu-u.submit_sm.registered_delivery = 1; 

enough to request SMSC to send back a DLR ? or is there any other thing to
set up ? 

  
 
this is already implemented in kannel. so you simply request the DLR from
the HTTP interface. That's all. 
  
in fact the above line is what triggers the request. 
  
  Andreas Fink 
Global Networks, Inc. 
  
-- 
Tel: +41-61-333  Fax: +41-61-6932729   Mobile: +41-79-2457333 
Global Networks, Inc. Clarastrasse 3, 4058 Basel, Switzerland 
Web: http://www.global-networks.ch/ [EMAIL PROTECTED] 
-- 
Member of the GSM Association

Re: wapbox crashes

2002-11-13 Thread Peter Löfman 
Attached is a more detailed (debug) printout from wapbox.

/Peter Lofman



From: Stipe Tolj [EMAIL PROTECTED]
To: Peter Löfman [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Subject: Re: wapbox crashes
Date: Wed, 13 Nov 2002 13:15:27 +0100

 Why is the wapbox crashing when the host requested is not reachable??!
 See log below:
 (After this the wapbox just dies)

 /Peter Lofman

 2002-11-13 09:29:00 [0] INFO: Added logfile 
`/var/log/kannel/wapbox-wap.log'
 with level `1'.
 2002-11-13 09:29:00 [0] INFO: Starting to log to file
 /var/log/kannel/wapbox-wap.log level 1
 2002-11-13 09:29:00 [0] INFO:
 
 2002-11-13 09:29:00 [0] INFO: Kannel wapbox version 1.2.0 starting up.
 2002-11-13 09:29:00 [0] INFO: Connected to bearerbox at localhost port
 13002.
 2002-11-13 09:29:19 [17] ERROR: connect failed
 2002-11-13 09:29:19 [17] ERROR: System error 111: Connection refused
 2002-11-13 09:29:19 [17] ERROR: error connecting to server
 `imps.amt.aland.fi' at port `8090'
 2002-11-13 09:29:19 [17] ERROR: Couldn't send request to
 http://hostname.domain.com:8090/
 2002-11-13 09:29:19 [8] ERROR: WSP: http lookup failed, oops.

there is no PANIC here, so does wapbox do crash via segmentation
fault?!

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 PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are


_
Senaste nytt från motormarknaden http://motor.msn.se/



wapbox.log
Description: Binary data

Kannel crashes when dlrmask = 8 requested (EMI2 protocol) patch

2002-11-13 Thread GAksenov 

Hello!

In function emi2_handle_smscreq we have dlrmsg-sms.msgdata =
octstr_duplicate(emimsg-fields[E50_AMSG]); what may be incoreect
because in OT == 51 reply message dosn't contain E50_AMSG field and emimsg
= get_fields(str, privdata-name); (called before) dosn't initialize this
field to any value.
This patch helps...

--- smsc_emi2.c.origWed Nov 13 15:06:39 2002
+++ smsc_emi2.c Wed Nov 13 15:08:25 2002
 -976,7 +976,7  static int emi2_handle_smscreq (SMSCConn
  * Recode the msg structure with the given msgdata.
  * Note: the DLR URL is delivered in msg-sms.dlr_url
already.
  */
-dlrmsg-sms.msgdata =
octstr_duplicate(emimsg-fields[E50_AMSG]);
+   dlrmsg-sms.msgdata = octstr_create();
 octstr_hex_to_binary(dlrmsg-sms.msgdata);
 dlrmsg-sms.sms_type = report;


any comments? May be better to fix get_fields(...) function (in emimsg.c)
to initialize all fields to NULL before use.

with best wishes
 German Aksenov
phone: (095)258-7258 ext. 7836

Re: Kannel crashes when dlrmask = 8 requested (EMI2 protocol) patch

2002-11-13 Thread GAksenov 

Hello!

I can't see where is memory leak. :(

if we change octstr_duplicate(emimsg-fields[E50_AMSG]) to  octstr_create
()?
or then we initialize all fields to NULL in get_fields(...), before use,
like

for (fieldno = 0; fieldno  SZ50; fieldno++) {
  result-fields[fieldno] = NULL;
}
and change patch to check mimsg-fields[E50_AMSG] with NULL and if NULL
make octstr_create() .
second help to avoid use variables with unknown content in future.

with best wishes
 German Aksenov
phone: (095)258-7258 ext. 7836


   

  Andreas Fink 

  [EMAIL PROTECTED]To:   [EMAIL PROTECTED]

  cc: 

   Subject:  Re: Kannel crashes when 
dlrmask = 8 requested (EMI2 protocol) 
  13.11.2002 17:30  patch  

   

   






On Mittwoch, November 13, 2002, at 03:27  Uhr, [EMAIL PROTECTED] wrote:


 Hello!

 In function emi2_handle_smscreq we have dlrmsg-sms.msgdata =
 octstr_duplicate(emimsg-fields[E50_AMSG]); what may be incoreect
 because in OT == 51 reply message dosn't contain E50_AMSG field and
 emimsg
 = get_fields(str, privdata-name); (called before) dosn't initialize
 this
 field to any value.
 This patch helps...

 --- smsc_emi2.c.origWed Nov 13 15:06:39 2002
 +++ smsc_emi2.c Wed Nov 13 15:08:25 2002
 @@ -976,7 +976,7 @@ static int emi2_handle_smscreq (SMSCConn
   * Recode the msg structure with the given msgdata.
   * Note: the DLR URL is delivered in msg-sms.dlr_url
 already.
   */
 -dlrmsg-sms.msgdata =
 octstr_duplicate(emimsg-fields[E50_AMSG]);
 +   dlrmsg-sms.msgdata =
 octstr_create();
  octstr_hex_to_binary(dlrmsg-sms.msgdata);
  dlrmsg-sms.sms_type = report;



this creates a memory leak...
no good.

 any comments? May be better to fix get_fields(...) function (in
 emimsg.c)
 to initialize all fields to NULL before use.

 with best wishes
  German Aksenov
 phone: (095)258-7258 ext. 7836

Re: Kannel crashes when dlrmask = 8 requested (EMI2 protocol) patch

2002-11-13 Thread GAksenov 

Hello!

I look into the code and it's looks as not good idea.

emimsg = get_fields(str, privdata-name);

create emimsg with size where E50_AMSG point to beyond the bounds emimsg
structure (for 51 type of reply message, emimsg_create_reply_s(ot, trn, 1,
whoami) function in get_fields ) and set it to NULL can destroy other data.


with best wishes
 German Aksenov
phone: (095)258-7258 ext. 7836


   

  Andreas Fink 

  [EMAIL PROTECTED]To:   [EMAIL PROTECTED]

  cc: 

   Subject:  Re: Kannel crashes when 
dlrmask = 8 requested (EMI2 protocol) 
  13.11.2002 17:49  patch  

   

   






On Mittwoch, November 13, 2002, at 03:38  Uhr, [EMAIL PROTECTED] wrote:


 Hello!

 that about patch?
 how avoid condition then used variable which not was initialized?


well initialize it with NULL

Re: mailing list downtime

2002-11-13 Thread David Holland 
I wrote:
 just a heads-up: I'll be upgrading the software (Mailman) on the list
 server later today.

If this message makes it out to the list, then the upgrade went OK. :-)

Dave
-- 
:: David Holland :: Systems Manager :: 3G Lab :: +44 01223 478900 ::

SAR patch and segfaults

2002-11-13 Thread Matias Lahti 
Hi - the SAR patch applied to CVS works nice with smaller files, but with
bigger files it segfaults.
Here's the log of wapbox before it dies:
---
2002-11-13 19:21:21 [1] DEBUG: User-Agent: Nokia7650/1.0 SymbianOS/6.1
Series60/0.9
2002-11-13 19:21:21 [1] DEBUG: WSP: End of decoded headers.
2002-11-13 19:21:21 [1] DEBUG: WSP 1: New state CONNECTING
2002-11-13 19:21:21 [6] DEBUG: WTP 2: New state INVOKE_RESP_WAIT
2002-11-13 19:21:21 [6] DEBUG: WTP: resp_machine 2, state INVOKE_RESP_WAIT,
event TR-Invoke.res.
2002-11-13 19:21:21 [6] DEBUG: WTP 2: New state RESULT_WAIT
2002-11-13 19:21:21 [1] DEBUG: WSP: machine 0x80cfc58, state CONNECTING,
event S-Connect.res
2002-11-13 19:21:21 [1] DEBUG: WSP 1: New state CONNECTING_2
2002-11-13 19:21:21 [6] DEBUG: WTP: resp_machine 2, state RESULT_WAIT, event
TR-Result.req.
2002-11-13 19:21:21 [6] DEBUG: WTP: begin_sar_result(): data len = 23
2002-11-13 19:21:21 [6] DEBUG: WTP: dispath_to_wdp(): psn = 0
2002-11-13 19:21:21 [6] DEBUG: WTP 2: New state RESULT_RESP_WAIT
2002-11-13 19:21:22 [6] DEBUG: WTP: resp_machine 2, state RESULT_RESP_WAIT,
event RcvAck.
2002-11-13 19:21:22 [1] DEBUG: WSP: machine 0x80cfc58, state CONNECTING_2,
event TR-Result.cnf
2002-11-13 19:21:22 [1] DEBUG: WSP 1: New state CONNECTED
2002-11-13 19:21:22 [6] DEBUG: WTP 2: New state LISTEN
2002-11-13 19:21:22 [6] DEBUG: WTP: Destroying WTPRespMachine 0x80d0b50 (2)
2002-11-13 19:21:23 [6] DEBUG: WTP: Created WTPRespMachine 0x80d0cb0 (3)
2002-11-13 19:21:23 [6] DEBUG: SAR event received, wait for continue
2002-11-13 19:21:24 [6] DEBUG: SAR event received, wait for continue
2002-11-13 19:21:25 [6] DEBUG: SAR event received, wait for continue
2002-11-13 19:21:25 [4] DEBUG: Timeout-R elapsed.
2002-11-13 19:21:25 [6] DEBUG: WTP: resp_machine 1, state RESULT_RESP_WAIT,
event Timeout-R.
2002-11-13 19:21:25 [6] DEBUG: WTP 1: New state RESULT_RESP_WAIT
2002-11-13 19:21:25 [6] DEBUG: SAR event received, wait for continue
---
strace log:
---
2940  --- SIGRTMIN (Real-time signal 0) ---
2940  ... rt_sigsuspend resumed ) = -1 EINTR (Interrupted system call)
2940  sigreturn()   = ? (mask now [HUP INT QUIT TERM
RTMIN])
2940  time([1037208085])= 1037208085
2940  write(2, 2002-11-13 19:21:25 [6] DEBUG: S..., 69) = 69*** here
are the last log messages
2940  write(5, 2002-11-13 19:21:25 [6] DEBUG: S..., 69) = 69
2940  time(NULL)= 1037208085
2940  rt_sigprocmask(SIG_SETMASK, NULL, [HUP INT QUIT TERM RTMIN], 8) = 0
2940  rt_sigsuspend([HUP INT QUIT TERM] unfinished ...
2934  ... poll resumed [{fd=7, events=POLLIN}], 1, 2000) = 0
2934  getppid() = 2933
2934  poll( unfinished ...
2933  ... poll resumed [{fd=3, events=POLLIN}, {fd=38, events=POLLIN,
revents=POLLIN}], 2, -1) = 1
2933  read(38, \0\0\5\205\0\0\0\4\0\0\0\r213.161.41.93\0\0\22\327\0\0...,
4096) = 1417
2933  brk(0x80e2000)= 0x80e2000
2933  kill(2940, SIGRTMIN)  = 0
2933  read(38, 0xbfffe82c, 4096)= -1 EAGAIN (Resource temporarily
unavailable)
2933  poll( unfinished ...
2940  --- SIGRTMIN (Real-time signal 0) ---
2940  ... rt_sigsuspend resumed ) = -1 EINTR (Interrupted system call)
2940  sigreturn()   = ? (mask now [HUP INT QUIT TERM
RTMIN])
2940  write(38, \0\0\0001\0\0\0\4\0\0\0\0070.0.0.0\0\0#\361\0\0\0\r213...,
53) = 53
2940  --- SIGSEGV (Segmentation fault) ---   this seems to
be the point of the crash?
2934  ... poll resumed [{fd=7, events=POLLIN}], 1, 2000) = -1 EINTR
(Interrupted system call)
2934  --- SIGRT_1 (Real-time signal 1) ---
2934  sigreturn()   = ? (mask now ~[TRAP KILL STOP])
2934  getppid() = 2933
2934  wait4(-1, [WIFSIGNALED(s)  WTERMSIG(s) == SIGSEGV],
WNOHANG|__WCLONE, NULL) = 2940
2934  munmap(0xbec0, 2097152)   = 0
2934  kill(2950, SIGSEGV)   = 0
2934  kill(2948, SIGSEGV)   = 0
2948  --- SIGSEGV (Segmentation fault) ---
2934  --- SIGRT_1 (Real-time signal 1) ---
2934  sigreturn()   = ? (mask now ~[TRAP KILL STOP])
2934  kill(2947, SIGSEGV)   = 0
2947  --- SIGSEGV (Segmentation fault) ---
2934  --- SIGRT_1 (Real-time signal 1) ---
2934  sigreturn()   = ? (mask now ~[TRAP KILL STOP])
2934  kill(2946, SIGSEGV)   = 0
2946  --- SIGSEGV (Segmentation fault) ---
2934  --- SIGRT_1 (Real-time signal 1) ---
2934  sigreturn()   = ? (mask now ~[TRAP KILL STOP])
2934  kill(2945, SIGSEGV)   = 0
2945  ... poll resumed [{fd=30, events=POLLIN}, {fd=27, events=POLLIN}],
2, -1) = -1 EINTR (Interr
upted system call)
2945  --- SIGSEGV (Segmentation fault) ---
2934  --- SIGRT_1 (Real-time signal 1) ---
2934  sigreturn()   = ? (mask now ~[TRAP KILL STOP])
2934  kill(2944, SIGSEGV)   = 0
2944  ... poll resumed [{fd=28, events=POLLIN}], 1, -1) = -1 EINTR
(Interrupted system call)
2944  --- SIGSEGV

Re: wapbox crashes

2002-11-13 Thread Stipe Tolj 
ups, ok this may be caused by some code I put in for adding the
referer HTTP header.

Please check what happens before calling the get_referer_url() when
the http lookup fails. The asserion should prevent that empty referer
strings are added. Maybe I'm not handling non-possible http lookup
properly.

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 PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are

Re: Kannel CDMP

2002-11-13 Thread Stipe Tolj 
 What about CDMP (Cellular Digital Messaging Protocol by Motorola)
 support in Kannel ? Somebody know projects like Kannel with CDMP
 implementation ?

If you have the specification or know where we can download one, we'd
like to invite you to write an Kannel module for it and we'll add it
to Kannel.

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 PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are

Re: DLRs

2002-11-13 Thread Stipe Tolj 
Martin Quevedo wrote:
 
 The thing is I am writing a perl script that connects to the
 smsbox-port to deliver sm though the kannel. I am setting the
 dlr_mask =1 and the dlr_ulr to a local script. However I only get
 the submit_sm_resp DLR. But the DLR that comes as a deliver_sm never
 arrives.
 
 Any ideas? I could send you the script if you want.

ok, so you simulate an smsbox in some sense with your perl script,
right?! You should check how smsbox is building Kannel's internation
message represenation structure and addopt this.

If you like we can put such a script (when finished and working) to
the contrib/ directory.

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 PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are

Re: incoming originator on SMPP

2002-11-13 Thread Nisan Bloch 

Hi
surely just not setting my-number in the config will sort that
out.
Nisan
At 11:46 AM 11/13/02 +0100, Andreas Fink wrote:
scenario: 
you have 
global-sender = 123 
so all your outgoing SMS which dont have from=... set will be from
123 
you got one SMPP link. no my-number stuff defined. 
you get an incoming SMS from that SMPP link and it will be always
to 123 even the sender might have used another short ID.

The problem seems to come from gw/smsc/smsc_smpp.c line 738ff 

/* Replace MO destination number with my-number */ 

if (octstr_len(smpp-my_number)) { 

octstr_destroy(msg-sms.receiver); 

msg-sms.receiver = octstr_duplicate(smpp-my_number); 

} 
Removing this, makes it work. However its supposed to be there for a
particular reason. 
whats the best way to fix this? 
Andreas Fink 
Global Networks, Inc. 
-- 
Tel: +41-61-333 Fax: +41-61-6932729 Mobile:
+41-79-2457333 
Global Networks, Inc. Clarastrasse 3, 4058 Basel, Switzerland 
Web:
http://www.global-networks.ch/
 [EMAIL PROTECTED] 
-- 
Member of the GSM Association 
/blockquote/x-html

Re: delivery reports and EMI [known bug issue]

2002-11-13 Thread Nisan Bloch 
Hi

snips from all the postings
At 07:59 AM 11/13/02 +0100, Andreas Fink wrote:


We have a work around, which is a bit hacky but works for us. We use the 
8 right most digits of the number to match the DLR in the db/store.

That would not be good enough in most cases.



why? given that there is a timestamp and destination  in the dlr tables. 
one would need multiple messages in quick succession, within 1 second to 
the same nmber, to end up with a clash. This is not ideal but works in most 
cases.


My approach would simply to specify international and national prefixes 
and country codes on the SMSC link.

I am not convinced that we can make a unified prefix work in all cases, and 
allow us to still have applications routing dynamically to Kannel. I have 
seen quite diverse numbers comming back from some EMI connections. It might 
also make the Kannel configs quite messy if one has many international and 
national prefixes and country codes on one SMSC link. Upstream providers 
also tend to change coverage patterns quite regularly and this would mean 
restarting Kannel.


This would also help on the sending side where a + currently is replaced 
hardcoded with 00 which is not really always true.

The unified-prefix on an SMSC basis can be used to overcome this. I have a 
small patch for EMI2 module to do this.

I agree on this but a delivery of the first message makes it very likely 
that the second message gets delivered too. So you would expect to have 
two identical deliveries or failures.

Not so.. The destination network may bar multiple quick submission of 
messages from the same src to the same destination, the SIM may become full 
etc..

Nisan

Re: incoming originator on SMPP

2002-11-13 Thread Andreas Fink 

On Mittwoch, November 13, 2002, at 08:27  Uhr, Nisan Bloch wrote:

Hi

surely just not setting my-number in the config will sort that out.

thats just the point. I have NOT set it.
The only thing set was "global-sender" and that has to be there for outgoing messages without from...

Re: delivery reports and EMI [known bug issue]

2002-11-13 Thread Nisan Bloch 
At 08:38 PM 11/13/02 +0100, Andreas Fink wrote:


On Mittwoch, November 13, 2002, at 08:25  Uhr, Nisan Bloch wrote:


Hi

snips from all the postings
At 07:59 AM 11/13/02 +0100, Andreas Fink wrote:


We have a work around, which is a bit hacky but works for us. We use 
the 8 right most digits of the number to match the DLR in the db/store.

That would not be good enough in most cases.



why? given that there is a timestamp and destination  in the dlr tables. 
one would need multiple messages in quick succession, within 1 second to 
the same nmber, to end up with a clash. This is not ideal but works in 
most cases.

Ok. lets at least add the last 8 digits of the phone number to the 
timestamp to make it unique.
I think thats a good compromize which solves 99.9% of the problems. Stipe, 
got your patch ready or shall I upgrade cvs?


the way we did it is not to add the 8 digits to the timestamp, but to have 
an alternative to the dlr_find_mysql function that uses the 8 digits from 
the dest in the SQL select. I am not using the latest CVS, so still have 
the older dlr functionality, but I can send u the relevant cuts from the code.

nisan

Re: incoming originator on SMPP

2002-11-13 Thread Nisan Bloch 
At 08:38 PM 11/13/02 +0100, Andreas Fink wrote:


On Mittwoch, November 13, 2002, at 08:27  Uhr, Nisan Bloch wrote:


Hi

surely just not setting my-number in the config will sort that out.


thats just the point. I have NOT set it.
The only thing set was global-sender and that has to be there for 
outgoing messages without from...

aah..yes i see..but then i dont understand the problem. The code you 
mention removing wont have any affect if the my-number config is not set.

Nisan

Re: delivery reports and EMI [known bug issue]

2002-11-13 Thread Stipe Tolj 
 Ok. lets at least add the last 8 digits of the phone number to the
 timestamp to make it unique.
 I think thats a good compromize which solves 99.9% of the problems.
 Stipe, got your patch ready or shall I upgrade cvs?

go for it. I'm working on other Kannel brackets currently, including
the wapbox crashes that have been reported.`

You may prepare the patch and post it to the list for votes anyway. We
should keep the formalism, so as soon as noone does heavily veto we
can commit changes.

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 PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are

Re: wapbox crashes

2002-11-13 Thread Stipe Tolj 
same for Linux here:

...
2002-11-14 02:26:54 [2] DEBUG: User-Agent: Nokia7210/1.0 (2.01)
Profile/MIDP-1.0 Configuration/CLDC-1.0
2002-11-14 02:26:54 [2] DEBUG: X-WAP.TOD: ?
2002-11-14 02:26:54 [2] DEBUG: WSP: End of decoded headers.
2002-11-14 02:26:55 [10] ERROR: gethostbyname failed
2002-11-14 02:26:55 [10] ERROR: System error 2: No such file or
directory
2002-11-14 02:26:55 [10] ERROR: error connecting to server
`wapme.neta' at port `80'
2002-11-14 02:26:55 [10] DEBUG: HTTP: Opening connection to
`wapme.neta:80' (fd=0).
2002-11-14 02:26:55 [10] ERROR: Couldn't send request to
http://wapme.neta
2002-11-14 02:26:55 [7] ERROR: WSP: http lookup failed, oops.
2002-11-14 02:26:55 [2] WARNING: WSP: Missing Content-Type header in
response, guessing application/octet-stream
...

are you using latest cvs HEAD tree? AFAIK you were using 1.2.0, but
there was no change in the referer handling logic, hmmm

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 PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are

[FYI] smsbox routing patch commited

2002-11-13 Thread Stipe Tolj 
Hi list,

I commited now Wapme's smsbox routing patch to Kannel's cvs HEAD tree.

The basic idea behind the smsbox routing is that we can now route
inbound messages to specific smsbox instances.

bearerbox may be connected to several smsboxes, mainly for
load-balancing purposes. Now as smsboxes do send MT messages
everything is pretty easy and Kannel has been desgined mainly for this
direction.

If you write own boxes that use Kannels internal message
representation and communication layer between bearerbox and smsbox,
like EMI/UCP and SMPP proxys that simulare the behaviour of a real
smsbox you will get into heavy problem for MO messages. bearerbox gets
an message and passes it by default to a random (non
identified/registered smsbox connection). 

Via smsbox-route groups you can tell bearerbox where you want certain
messages to be routed to. I.e. you have an smppbox that is an SMPP
server. It handles all the SMPP specific communication to your
clients. Now you assign your clients some shortcuts numbers in certain
networks, like 1 for 4 different netwoks. Now bearerbox gets the
MO messages and you need to implement a switch in bearerbox that makes
bearerbox know that messages with receiver number 1 should be
passed to the smppbox instead of it's standard smsbox in order that
smppbox may transcode the message to an deliver_sm PDU.

I thing that this smsbox routing concept is very powerfull, espacially
if you want to use Kannel as SMS proxying system, where you write your
own protocoll boxes and use bearerbox as smsc handling aggregator.

We use this at Wapme to provide customers SMPP v3.4 and EMI/UCP 4.0
server connections via our smppbox.

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 PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are