Vjacheslav Chekushin wrote:
>
> Hi, Igor.
> I think, first of all, panic must be eliminated.
yep, agreed. Panics do stop wapbox service. Hence a download of a "too
large" file kills wapbox, which is not the way we want it in an
operational environment.
If something can't be done, then other cli
Hi, Igor.
I think, first of all, panic must be eliminated.
So reduce client sdu size to SAR_SEGM_SIZE*255 is Ok.
I'm not sure about changing SAR_SEGM_SIZE. If nokia gw uses value 576,
may be some nokia models doesn't work stable with large SAR_SEGM_SIZE?
Any way, current values are tested already,
Title: RE: SAR panic
Dear Slava,
While ESAR is not implemented I think a graceful way to hanlde it is
to reduce client sdu size sent to wsp to SAR_SEGM_SIZE*255.
Also I can change SAR_SEGM_SIZE to be let's say 1300.
it will change the maximum file size to 331K from 146K.
But it may ca
