MMS-Ind: Ports and expiry date

2003-02-10 Thread Friedrich, Jason Brian
Hi list, 

could somebody tell me more about the ports section in the mms 
notification? Why is there a source and destination port? I thought
that only a destination port is necessary. (Nokia has different ports
for different applications). 

How can the relative expiry date be calculated and how do i have
to sepcify the absolute expiry date?

Thanks in advance, 
 Jason Brian
-- 
. / j a s o n  

Jason-Brian Friedrich[EMAIL PROTECTED]
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
LINUX is user friendly, its just picky about who its friends are!




[Fwd: Removing WTP-SAR limit 32768 B]

2003-02-10 Thread Stipe Tolj
Hi list,

forwarded.

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
---BeginMessage---
Stipe,

Could you please advise how to remove limit 32768 B for downloading files with larger 
sizes. I have Kannel 1.3.0 with WTP-SAR (Debian package) but when I try to download 
.jar file I get a message:

WARNING: WSP: Entity at http://my_site/file.jar too large (size 69885 B, limit 32768 
B) 

Best regards,

Max



---End Message---


RE: [Fwd: Removing WTP-SAR limit 32768 B]

2003-02-10 Thread Igor Ivoilov
Title: RE: [Fwd: Removing WTP-SAR limit 32768 B]





This is not a WTP-SAR limit, this is what the phone reports about itself with Client SDU size
Out of curiosity, what is the model of the phone?


Igor


 -Original Message-
 From: Stipe Tolj [mailto:[EMAIL PROTECTED]]
 Sent: Monday, February 10, 2003 1:42 PM
 To: [EMAIL PROTECTED]
 Subject: [Fwd: Removing WTP-SAR limit 32768 B]
 
 
 Hi list,
 
 forwarded.
 
 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
 





T68i incorrect support of CNMI

2003-02-10 Thread Alex Judd
RE: [Fwd: Removing WTP-SAR limit 32768 B]Anyone else noticed that the T68i
appears to break the rules of the CNMI command in smsc_at2.c?

AT+CNMI=?
+CNMI: (3),(0,1,3),(0,2),(0),(0)

which default setting to =3,3,2,0,0 means that no messages should be stored
in memory, and even if they are they will be flushed through once read.

However.. the phone stores them in memory even though it says that the
memories are empty.

Anyone else worked around this?

Alex





Re: connection of bearerbox with GSM modem

2003-02-10 Thread Stipe Tolj
Anupama R wrote:
 
 Hello,
 I work with the cygwin installation of kannel on a win2k machine.
 I have a peculiar problem with the bearerbox.
 When I start bearerbox utility and try and connect to the modem, the speed
 in the conf file does not seem to match and the connection fails.
 
 But if I try to connect to the modem thru the HyperTerminal (developed by
 Hilgraeve for microsoft)
 to the modem with the same speed, the connection comes through correctly.
 
 Consequently if I try the bearerbox connection with the same conf file, the
 bearerbox is up
 and running fine.
 
 Any idea why this would happen?

so do you get a valid connection to the device or not? I didn't get
the point, sorry.

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: MMS-Ind: Ports and expiry date

2003-02-10 Thread Stipe Tolj
Friedrich, Jason Brian wrote:
 
 could somebody tell me more about the ports section in the mms
 notification? Why is there a source and destination port? I thought
 that only a destination port is necessary. (Nokia has different ports
 for different applications).

MMS notifications are pushed via WAP Push, which may also been
utilaized over IP, hence source addresses are of possible relevance.

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: Does Kannel log support logrotation

2003-02-10 Thread Stipe Tolj
Alan,

please do not patch configure itself. It's the autoconf output out of
configure.in. If you have to change something, please try to patch
configure.in and provide a patch to it.

After that we can run autoconf and commit an auto-generated configure
script.

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: Does Kannel log support logrotation

2003-02-10 Thread Stipe Tolj
Alan,

can you provide the userguide.xml patch in diff -u (unified) format,
that should be easier to read and to apply.

Thanks in advance.

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: connection of bearerbox with GSM modem

2003-02-10 Thread Anupama R
Hello Stipe,
I'll put it down in points, yes I get the connection, but I'll explain where
the problem is.

1) connect the gsm modem to usb port
2) start bearerbox to connect to modem at 115200 (speed set in conf file)
3) bearerbox fails to connect, because after opening port at that speed, at
command fails
4) connect the modem through hyperterminal (Hilgraeve product, comes with
win 2k) at 115200
5) disconnect the modem from hyperterminal
6) reconnect with the same configuration file from bearerbox, this time
connection will succeed.

This is not sporadic behaviour.  I run through this process everytime I
connect the gsm modem.
I wanted to know if there are any workarounds for this.

Best Regards
Anu

 -Original Message-
 From: Stipe Tolj [mailto:[EMAIL PROTECTED]]
 Sent: Tuesday, February 11, 2003 7:33 AM
 To: Anupama R
 Cc: [EMAIL PROTECTED]
 Subject: Re: connection of bearerbox with GSM modem
 
 
 Anupama R wrote:
  
  Hello,
  I work with the cygwin installation of kannel on a win2k machine.
  I have a peculiar problem with the bearerbox.
  When I start bearerbox utility and try and connect to the 
 modem, the speed
  in the conf file does not seem to match and the connection fails.
  
  But if I try to connect to the modem thru the HyperTerminal 
 (developed by
  Hilgraeve for microsoft)
  to the modem with the same speed, the connection comes 
 through correctly.
  
  Consequently if I try the bearerbox connection with the 
 same conf file, the
  bearerbox is up
  and running fine.
  
  Any idea why this would happen?
 
 so do you get a valid connection to the device or not? I didn't get
 the point, sorry.
 
 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: Does Kannel log support logrotation (userguide patch)

2003-02-10 Thread Alan McNatty
Here you go ... in unified format.

On Tue, 2003-02-11 at 15:15, Stipe Tolj wrote:
 Alan,
 
 can you provide the userguide.xml patch in diff -u (unified) format,
 that should be easier to read and to apply.
 
 Thanks in advance.
 
 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
 
 


Index: doc/userguide/userguide.xml
===
RCS file: /home/cvs/gateway/doc/userguide/userguide.xml,v
retrieving revision 1.201
diff -u -r1.201 userguide.xml
--- doc/userguide/userguide.xml	4 Feb 2003 16:52:20 -	1.201
+++ doc/userguide/userguide.xml	11 Feb 2003 06:24:06 -
@@ -7414,6 +7414,43 @@
   /informaltable
 
 /sect1
+sect1
+titleLog rotation/title
+
+	paraIf Kannel is configured so that the bearerbox, wapbox and/or smsbox 
+log to file each of these log files will continue to grow unless administered
+in some way (this is especially true if access logs are created and/or the 
+log level is set to debug). /para
+
+para
+A typical way of administering log files is to 'rotate' the logs on a regular 
+basis using a tool such as logrotate.  A sample logrotate script (to be added 
+to /etc/logrotate.d) is shown below. In this example the Kannel log files found 
+in /var/log/kannel are rotated and compressed daily over 365 days.  See the 
+documentation for logrotate for more details.  Of particular note however is the 
+postrotate command, this killall -HUP issues a HUP command to each kannel
+box running. The HUP signal has the effect of reopening the log file, without this 
+command Kannel will continue to write to the rotated log file.
+/para
+
+screen
+userinput
+/var/log/kannel/*.log {
+  daily
+  missingok
+  rotate 365
+  compress
+  delaycompress
+  notifempty
+  create 640 root adm
+  sharedscripts
+  postrotate
+killall -HUP bearerbox smsbox wapbox  /dev/null 2 /dev/null
+  endscript
+}
+/userinput
+/screen
+/sect1
 
 /appendix
 
@@ -7471,12 +7508,3 @@
 /bibliography
 
 /book
-
-
-
-
-
-
-
-
-