Hi all,
I've sent an e-mail for this mailing list a few weeks ago, reporting
a bug regarding a misbehaviour in the packet retransmission at WSP
level.
The problem takes place when the network between the terminal and the
kannel
loses some packets in a fragmented request (e.g. transmission of a
trying to play with the priority is NOT the solution.
You can easily run into the same issue again. Even a end user sending
a long message from a phone will eventually hit this problem.
Think of having a weak coverage and the first part gets lost and the
second one sent and then the phone
install ar is the solution.
If you dont have ar, you can not make libraries.
you probably dont have gcc properly installed or maybe your path is
not correct.
I remember solaris sometimes has weird paths. On my solaris 8 systems
I find
fire1:~ afink$ grep /ar$ /allfiles
Carlos Parada wrote:
Hi all,
I've sent an e-mail for this mailing list a few weeks ago, reporting
a bug regarding a misbehaviour in the packet retransmission at WSP
level.
The problem takes place when the network between the terminal and the
kannel
loses some packets in a fragmented request
Hi Stipe,
I made the stress test again with my operator. This time I set loglevel to
0, I changed throughput and max-pending-submits; but this did not resolve
the issue, the only difference is the problem takes place in different
messages, for example:
sequence number: 17074
sequence number:
