What's the SAR status ??

2003-02-26 Thread denzel
hi all !

We've seen some of SAR patches moving around. I think newer kannel
version(1.2.1) supports it. Has anybody tested this functionality with newer
gateways ? Or are they still developing SAR ? Does anyone have a new patch ?

urs,
denzel.




Re: SAR

2002-12-09 Thread denzel
Title: RE: SAR




Hi Damir,

According to the SAR specification, it says 
the Acknowledgement is sent when the GTR is ON. When the TTR is ON, it doesn't 
send an Ack, instead the Result_Response is sent. But if there're missing 
packets, a Nack is sent even if it's a TTR packet.

I'm not sure if that has a bug like that (delay to 
send Ack). I'll check.

Denzel



  
  - Original Message - 
  From: Damir Salantic 
  To: 'kannel-mailing-list' 
  Cc: 'Igor Ivoilov' ; [EMAIL PROTECTED] 
  
  Sent: Monday, December 09, 2002 4:38 AM
  Subject: RE: SAR
  
  Hi to all
  
  I need an opinion of anyone 
  familiar with WTP and SAR handling.
  Here is the excerption from 
  WTP specs. (WAP-224-WTP-20010710-a.pdf) :
  " The missing packets are re-transmitted with the 
  original Packet Sequence Numbers. When the sender has re-transmitted the 
  requested packets, it reverts to wait for the original acknowledgement (for 
  the GTR or TTR packet). When the receiver has received all packets it 
  acknowledges the GTR or TTR packet according to the normal procedure,using the 
  Ack PDU. ".
  
  It seems to me that recevier 
  (WAP gateway) must acknowledge resent packets even if they don't have GTR/TTR 
  set. Or maybe sender mustset GTRon last resent packet of a 
  group?
  
  Denzel, 
  seems that your version of 
  SAR patch acknowledges resent packets not imediatelly, but after 4-5 seconds. 
  Is that an expected behaviour?
  
  Thanks for you 
  answers
  
  Best 
  regards
  Damir 
  Salantic
  
  


SMS nokia

2002-12-08 Thread denzel



hi! 
I'm experiencing sms problems with nokia 
phones. I send sms using the folowing cgi command,

links -dump 
'http://127.0.0.1:15013/cgi-bin/sendsms?coding=2username=testpassword=testfrom=8877smsc=CELLSMPPto=9472324327text=test'

Note here that I'm using a coding=2 parameter to force 
8bit encoding. This works fine for ericsson phones. But with 
two different Nokia phones I received an error, 
"Unreadable". I've included the dumped pdu. Any ideas 
?


SMPP PDU 0x810a8f8 dump:2002-12-09 12:52:04 [5] 
DEBUG: type_name: submit_sm2002-12-09 12:52:04 [5] 
DEBUG: command_id: 4 = 0x00042002-12-09 12:52:04 [5] 
DEBUG: command_status: 0 = 0x2002-12-09 12:52:04 [5] 
DEBUG: sequence_number: 126 = 0x007e2002-12-09 12:52:04 [5] 
DEBUG: service_type: NULL2002-12-09 12:52:04 [5] 
DEBUG: source_addr_ton: 2 = 0x00022002-12-09 12:52:04 [5] 
DEBUG: source_addr_npi: 1 = 0x00012002-12-09 12:52:04 [5] 
DEBUG: source_addr: "8877"2002-12-09 12:52:04 [5] 
DEBUG: dest_addr_ton: 2 = 0x00022002-12-09 12:52:04 [5] 
DEBUG: dest_addr_npi: 1 = 0x00012002-12-09 12:52:04 [5] 
DEBUG: destination_addr: "9472324327"2002-12-09 12:52:04 [5] 
DEBUG: esm_class: 0 = 0x2002-12-09 12:52:04 [5] 
DEBUG: protocol_id: 0 = 0x2002-12-09 12:52:04 [5] 
DEBUG: priority_flag: 0 = 0x2002-12-09 12:52:04 [5] 
DEBUG: schedule_delivery_time: NULL2002-12-09 12:52:04 [5] 
DEBUG: validity_period: NULL2002-12-09 12:52:04 [5] 
DEBUG: registered_delivery: 0 = 0x2002-12-09 12:52:04 
[5] DEBUG: replace_if_present_flag: 0 = 0x2002-12-09 
12:52:04 [5] DEBUG: data_coding: 4 = 0x00042002-12-09 
12:52:04 [5] DEBUG: sm_default_msg_id: 0 = 0x2002-12-09 
12:52:04 [5] DEBUG: sm_length: 0 = 0x2002-12-09 12:52:04 
[5] DEBUG: short_message: "test"


urs,
denzel.


Re: SAR

2002-12-06 Thread denzel
Title: RE: SAR




Hi Damir,

I checked your log dump. As I can see, the SAR part 
has successfully worked. Igor is right, your device has sent more than 6 packets 
in one group and from that 6had failed, and the NACK was sent sucessfully 
with the missing PDU Numbers.

The problem has occured in the next incoming PDU. 
For some reason that has got errors (RcvErrorPDU). I've also seen that error 
earlier, but still I didn't find a time to look details into that. As I suspect, 
this error has occured prior to the SAR part, where PDU's are unpacked and as I 
suspect it's happened at the place where the Server looks for a WTP Machine 
(resp_machine_find_or_create). If you can submit us more of your logs, I may be 
able to see more into this.

Igor, any ideas?

Rgds,
Denzel

ps: this still doesn't support ESAR. But since I'm 
using a DICT structure to host segments, it can grow upto any 
amount.




  - Original Message - 
  From: 
  Damir Salantic 
  To: 'kannel-mailing-list' 
  Cc: [EMAIL PROTECTED] ; 'Igor Ivoilov' 
  
  Sent: Friday, December 06, 2002 2:14 
  AM
  Subject: RE: SAR
  
  Hi 
  Igor.
  
  We 
  are experimenting witha wap stack. 
  That's probably the reason ofunexpected 
  behaviour.
  Anyway, wap gateway should accept up to 256 packets in a group (or more 
  with ESAR).
  
  
  Damir S
  
  
  
-Original Message-From: Igor Ivoilov 
[mailto:[EMAIL PROTECTED]]Sent: 6. prosinac 2002 
10:21To: '[EMAIL PROTECTED]'; 
'kannel-mailing-list'Cc: [EMAIL PROTECTED]Subject: RE: 
SAR
Hi Damir, 
What was the device your wap gw communicated with? 
Looks like it send more than 6 packets in a group, 
maximum that I saw by myself was 3. 
Igor 
 -Original Message-  
From: Damir Salantic [mailto:[EMAIL PROTECTED]] 
 Sent: Friday, December 06, 2002 10:28 AM 
 To: 'kannel-mailing-list'  
Cc: [EMAIL PROTECTED]; Igor Ivoilov  Subject: 
RE: SAR   
 Hi Denzel, hi Igor  
 I don't know if this is related, but here is 
the part of  wapbox.log, after  my wapbox crashed.  Note that this 
is a kannel with Danzel's patch applied.  If you 
want, I can send you more data from log.  Note 
that this happened after few hours of normal operation.   bye  
Damir   
-Original Message- 
 From: [EMAIL PROTECTED]  [mailto:[EMAIL PROTECTED]]On 
 Behalf Of [EMAIL PROTECTED]  Sent: 6. prosinac 2002 21:26  To: 
Igor Ivoilov; [EMAIL PROTECTED]  Cc: 
kannel-mailing-list  Subject: Re: SAR 
   Hi Damir/Igor,   As you have seen, my implementation is done based on State 
 Machine in WTP  
Response Layer. Also to my knowledge, I implemented all the  functionalities  in SAR 
(Segmentation/Re-Assembly/NACK/ACK).  
 One thing I like to ask from Igor is is there 
any efficiency  problem or  anything when you do it using the Sate Machines? 
  The problem was with my 
implementation is little funny one.  Actually 
I'm not  sure if that's cause of a bug in the 
SAR implementation or  related to some 
 other part. The problem was, when a phone initiate a 
WAP  session, WTP state  changes to INVOKE_RESP_WAIT and waits for a Response from WSP 
 layer. And  this 
continues for a long time or indefinitely. Also this  problem occurs  only occationally. 
The funny thing here is, this happens  prior to 
the start  of SAR packets, so I guess this 
couldn't be because of my  coding. Igor, 
I  know you are in a much greater level to 
understand what this  problem can be. 
 Please help me to sort this.   If any other person has tried my 
coding please give me your comments.  
 Thanks,  
Denzel   
  


Re: SAR

2002-12-05 Thread denzel
Title: RE: SAR



Hi Damir/Igor,

As you have seen, my implementation is done based 
on State Machine in WTP Response Layer. Also to my knowledge, I implemented all 
the functionalities in SAR (Segmentation/Re-Assembly/NACK/ACK). 

One thing I like to ask from Igor is is there any 
efficiency problem or anything when you do it using the Sate 
Machines?

The problem was with my implementation is little 
funny one. Actually I'm not sure if that's cause of a bug in the SAR 
implementation or related to some other part. The problem was, when a phone 
initiate a WAP session, WTP state changes to INVOKE_RESP_WAIT and waits for a 
Response from WSP layer. And this continues for a long time or indefinitely. 
Also this problem occurs only occationally. The funny thing here is, this 
happens prior to the start of SAR packets, so I guess this couldn't be because 
of my coding. Igor, I know you are in a much greater level to understand what 
this problem can be. Please help me to sort this.

If any other person has tried my coding please give 
me your comments.

Thanks,
Denzel


  - Original Message - 
  From: 
  Igor Ivoilov 
  
  To: '[EMAIL PROTECTED]' 
  ; [EMAIL PROTECTED] 
  Sent: Thursday, December 05, 2002 4:53 
  AM
  Subject: RE: SAR
  
  Hi Damir, 
  You're right, this thing is not implemented, but the implementation is coming soon 
  Igor 
   -Original Message-  
  From: Damir Salantic [mailto:[EMAIL PROTECTED]] 
   Sent: Thursday, December 05, 2002 12:06 PM 
   To: [EMAIL PROTECTED] 
   Subject: SAR  
Hi to all. 
I started to work with 
  kannel recently, so excuse me for my  ignorance, 
  if  I'm wrong.  I'm 
  refering to "SAR" thread one month ago.  
   Denzel wrote on Nov. 13.:  "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 ."   Igor wrote on Nov. 13.:  "Nack 
  reaction was not implemented in early version of sar.patch. But 
   version  that's come to cvs 
  has this feature."   
  Now I'm looking on both versions: one with Denzel's patch and  the one from  CVS.  What I see is that in CVS version there is implemented only 
   response to NACK  and 
  not a NACK request. In another words, CVS Kannel doesn't  take care about  lost wtp segments and 
  never sends NACK to the sender, but only ACK.  
  This can be seen in following code:  
   wtp_resp.c line 722:  
   
  if (orig_event-u.RcvSegInvoke.gtr == 1) { /* Need to  acknowledge */  
  e = wtp_pack_sar_ack(ACKNOWLEDGEMENT, machine-tid,  machine-addr_tuple,  
  orig_event-u.RcvSegInvoke.psn);  
  dispatch_to_wdp(e);  }   and when receives incomplete packet 
  it just reports debug info:   wtp_resp.c line 793:  for (i = 1; i = last_psn; i++) 
  {  
  if ((sar_info = list_search(machine-sar_info, i,  is_wanted_sar_data)) != NULL) {  
   
  octstr_append(e-u.RcvInvoke.user_data,sar_info-sar_data); 
   } else 
  {  
  debug("wap.wtp", 0, "Packet with psn %d not found", i);  
  return e;  }  }  
   In Denzel's implementation it seems to be solved 
  correctly  (wtp_check_segments).   Igor, can you confirm that, so I 
  should use Danzel's patch  instead of CVS. 
   Do you plan to implement that also?  Maybe some part from Denzel's patch can be integrated to 
  CVS?   Thanks 
   Damir Salantic  
 


garbled SMS

2002-12-02 Thread denzel





Hi list!
When I send sms using the kannel 
gateway the message is received garbled. i.e. The message is encrypted except 
every 8th character.
For example when I send the 
message,
 
1234567823456782345678
the result on the phone 
is,
 
 1dL!SFM8dL!SFM8dL!SFM8
Note here that every 8th 
character appears correctly. 
This is my smsc 
configuration,



group = smscsmsc = smpphost 
= 192.168.119.112port = 5017receive-port = 5017smsc-username = 
"xxx"smsc-password = xaddress-range = "1234"system-type = 
""smsc-id = DIALSMPPpreferred-smsc-id = DIALSMPP

Any 
thougts!!!.
urs,
denzel.


Re: garbled SMS

2002-12-02 Thread denzel



hi!
 I sent the sms using the 
sendsmsCGI script,like ...

links -dump 
'http://127.0.0.1:15013/cgi-bin/sendsms?username=smsuserpassword=testfrom=1234smsc=CELLSMPPto=9472423353text=1234567823456782345678'

smsc is some version of SMPP( As given in kannel 
userguide). How do I set the encoding mechanism?



  - Original Message - 
  From: 
  Andreas Fink 
  
  To: [EMAIL PROTECTED] 
  Sent: Monday, December 02, 2002 4:48 
  AM
  Subject: Re: garbled SMS
  On Dienstag, Dezember 3, 2002, at 03:25 Uhr, [EMAIL PROTECTED] wrote:
  Hi list!When I send 
sms using the kannel gateway the message is received garbled. i.e. The 
message is encrypted except every 8th character.For example when I 
send the message, 
1234567823456782345678the result on the phone 
is,  
1dL!SFM8dL!SFM8dL!SFM8Note here that every 8th character 
appears correctly.you got 
  7bit/8bit encoding wrong. how did you submit the message and what kind of SMSC 
  do you use there?


Re: garbled SMS

2002-12-02 Thread denzel



Thanks Man I just found the answer,
coding=2 worked.!!! Really 
Thankyou

  - Original Message - 
  From: 
  Andreas Fink 
  
  To: [EMAIL PROTECTED] 
  Sent: Monday, December 02, 2002 5:48 
  AM
  Subject: Re: garbled SMS
  On Dienstag, Dezember 3, 2002, at 04:50 Uhr, [EMAIL PROTECTED] wrote:
  hi!links -dump 
'http://127.0.0.1:15013/cgi-bin/sendsms?coding=0username=smsuserpassword=testfrom=1234smsc=CELLSMPPto=9472423354text=test'didn't 
work(same result).not coding=0 but coding= 1!
  urs,denzel.- Original Message 
-From: Andreas FinkTo: 
[EMAIL PROTECTED]Sent: 
Monday, December 02, 2002 5:37 AMSubject: Re: garbled 
SMSOn Dienstag, Dezember 3, 2002, at 04:16 Uhr, [EMAIL PROTECTED] 
wrote:hi! I sent the sms using the 
sendsmsCGI script,like ...links -dump 
'http://127.0.0.1:15013/cgi-bin/sendsms?username=smsuserpassword=testfrom=1234smsc=CELLSMPPto=9472423353text=1234567823456782345678'smsc 
is some version of SMPP( As given in kannel userguide). How do I set the 
encoding mechanism?try adding 
coding=1


Fw: SAR

2002-11-12 Thread denzel



hi !

I downloaded the new 
CVS code and created this patch. Try it.






urs,
denzel.


cvs.patch
Description: Binary data


Fw: wap

2002-10-25 Thread denzel
Hi everyone!

As you can see in the below debug output, response machine is in LISTEN
state. A RcvInvoke event is occurred. Since the TCL is 0 (class 0),
transaction doesn't have any acknowledgement, so the state again goes back
to LISTEN and the response machine is destroyed. But as I can see, even
though it's destroyed WSP's trying to do something and complains the PDU is
unknown type. And the main WAP application is get terminated.


2002-10-25 20:38:24 [0] DEBUG: XXX: wap_dispatch_datagram
2002-10-25 20:38:24 [0] DEBUG: XXX: wtp_unpack_wdp_datagram
2002-10-25 20:38:24 [0] DEBUG: XXX: unpack_wdp_datagram_real
2002-10-25 20:38:24 [0] DEBUG: XXX: truncated_datagram
2002-10-25 20:38:24 [0] DEBUG: XXX: unpack_invoke
2002-10-25 20:38:24 [0] DEBUG: XXX: wtp_event_is_for_responder
2002-10-25 20:38:24 [0] DEBUG: XXX:
wap_dispatch_datagram---
2002-10-25 20:38:24 [0] DEBUG: Dumping WAPEvent 0x810ce90
2002-10-25 20:38:24 [0] DEBUG:   type = RcvInvoke
2002-10-25 20:38:24 [0] DEBUG: user_data =
2002-10-25 20:38:24 [0] DEBUG:  Octet string at 0x81120b0:
2002-10-25 20:38:24 [0] DEBUG:len:  2
2002-10-25 20:38:24 [0] DEBUG:size: 3
2002-10-25 20:38:24 [0] DEBUG:immutable: 0
2002-10-25 20:38:24 [0] DEBUG:data: 05 00 ..
2002-10-25 20:38:24 [0] DEBUG:  Octet string dump ends.
2002-10-25 20:38:24 [0] DEBUG:   tcl = 0
2002-10-25 20:38:24 [0] DEBUG:   tid = 24299
2002-10-25 20:38:24 [0] DEBUG:   tid_new = 0
2002-10-25 20:38:24 [0] DEBUG:   rid = 0
2002-10-25 20:38:24 [0] DEBUG:   up_flag = 1
2002-10-25 20:38:24 [0] DEBUG:   no_cache_supported = 0
2002-10-25 20:38:24 [0] DEBUG:   version = 0
2002-10-25 20:38:24 [0] DEBUG:   gtr = 0
2002-10-25 20:38:24 [0] DEBUG:   ttr = 1
2002-10-25 20:38:24 [0] DEBUG: WAPAddrTuple 0x810e948 =
192.168.223.61:49200 - 0.0.0.0:9201
2002-10-25 20:38:24 [0] DEBUG: WAPEvent dump ends.
2002-10-25 20:38:24 [0] DEBUG: XXX: wtp_event_is_for_responder
2002-10-25 20:38:24 [0] DEBUG: XXX: wtp_resp_dispatch_event
2002-10-25 20:38:24 [6] DEBUG: XXX: resp_machine_find_or_create
2002-10-25 20:38:24 [6] DEBUG: XXX: erroneous_field_in
2002-10-25 20:38:24 [6] DEBUG: XXX: resp_machine_find
2002-10-25 20:38:24 [6] DEBUG: XXX: resp_machine_create
2002-10-25 20:38:24 [6] DEBUG: WTP: Created WTPRespMachine 0x810edb0 (2)
2002-10-25 20:38:24 [6] DEBUG: XXX: name_resp_state
2002-10-25 20:38:24 [6] DEBUG: WTP: resp_machine 2, state LISTEN, event
RcvInvoke.
2002-10-25 20:38:24 [6] DEBUG: XXX: create_tr_invoke_ind
2002-10-25 20:38:24 [1] DEBUG: WSP: machine 0x810cee0, state CONNECTED,
event TR-Invoke.ind
2002-10-25 20:38:24 [1] DEBUG: WSP 0: New state NULL_SESSION
2002-10-25 20:38:24 [1] DEBUG: Destroying WSPMachine 0x810cee0
2002-10-25 20:38:24 [6] DEBUG: WTP 2: New state LISTEN
2002-10-25 20:38:24 [6] DEBUG: XXX: resp_machine_destroy
2002-10-25 20:38:24 [6] DEBUG: WTP: Destroying WTPRespMachine 0x810edb0 (2)
2002-10-25 20:41:56 [0] DEBUG: XXX: wap_dispatch_datagram
2002-10-25 20:41:56 [2] WARNING: WSP PDU with unknown type -1
2002-10-25 20:41:56 [7] DEBUG: Thread 7 (gw/wap-appl.c:main_thread)
terminates.
2002-10-25 20:41:57 [0] DEBUG: XXX: wap_dispatch_datagram
2002-10-25 20:41:57 [2] WARNING: WSP PDU with unknown type -1
2002-10-25 20:42:00 [0] DEBUG: XXX: wap_dispatch_datagram
2002-10-25 20:42:00 [2] WARNING: WSP PDU with unknown type -1
2002-10-25 20:42:06 [0] DEBUG: XXX: wap_dispatch_datagram
2002-10-25 20:42:06 [2] WARNING: WSP PDU with unknown type -1


Please throw some light in here.!!!


urs,
denzel.





Re: WSP TO HTTP SLOW !!

2002-09-05 Thread denzel








  
  Hi!
  
  We try to receive 16k message. WTP successfully receives all the 
  segments (we hacked the code) and then passes the full message to WSP. WSP 
  selects a http connection from the pool and after going through various 
  functions in the octstr.c-octstr_write_data, it writes the buffer to 
  the http socket. But the problem is, after writing to the socket, it takes 
  about 30 second to transmit all the data comes to the other side. 
  Also I have noticed that even I try to write 16856 bytes of data it 
  send only 13032 bytes of data first (every time I tried) and then sends 
  the rest (3823 bytes) (goes 2 times through 
  octstr.c-octstr_write_data). As I read on the Kannel architecture, 
  after that function it writs buffers to the operating system network 
  buffers. Is that delay occur from the OS?
  
  urs,
  denzel.
  
  
  
  ---Original Message---
  
  
  From: Stipe Tolj
  Date: Thursday, 
  September 05, 2002 02:21:17 AM
  To: denzel
  Cc: [EMAIL PROTECTED]
  Subject: Re: WSP TO 
  HTTP SLOW !!
  we have currently a problem with large objects transfer 
  in the WTP/WSPstack, yes. Can you check the wapbox log if you see some 
  Timeout-Revents occuring while the transfer takes 
  place?!Stipe[EMAIL PROTECTED]---Wapme 
  Systems AGVogelsanger Weg 8040470 DüsseldorfTel: 
  +49-211-74845-0Fax: +49-211-74845-299E-Mail: [EMAIL PROTECTED]Internet: 
  http://www.wapme-systems.de---wapme.net 
  - wherever you are.





	
	
	
	
	
	
	




 IncrediMail - 
Email has finally evolved - Click 
Here



WSP TO HTTP SLOW !!

2002-09-04 Thread denzel








  HI all !
  
  We sent a large messege ( 16k ) from the phone to 
  the kannel wap gateway (posting large message content toa url). The 
  message was posted ok. But it took a lot time to complete (around a 
  minute ).Debug output showsthat the bottleneck 
  is withthe wsptrying to write the content to 
  http socket.Does anyone know why ? 
  
  urs,
  DenZel.
  





	
	
	
	
	
	
	




 IncrediMail - 
Email has finally evolved - Click 
Here



state table for segmentaion and reassembly

2002-08-21 Thread denzel








  Hi all !
   Does any body havefigured out the state 
  table for 'segmentation and reassemebly' function ? The wtp 
  spec doesn't include the "state table" for 
  "segmentation and reassembly". 
      
  urs
  denzel





	
	
	
	
	
	
	




 IncrediMail - 
Email has finally evolved - Click 
Here