Re: AT sendmsg failing with error = 4

[Pawel Kot]

On Fri, 31 May 2002, Pawel Kot wrote:

> On Fri, 31 May 2002, Pavel Machek wrote:
>
> > Hi!
> >
> > > > I'm experiencing random (?) errors 4 (IIRC) on AT message send. What
> > > > is neccessary to work around that?
> > >
> > > It takes much time to send an SMS larger then 160 chars (Multipart
> > > Messages). Time between the request and the response from the SMSC. Active
> > > waiting here is just wrong. But I think we should leave it rught now
> > > as it
> >
> > ?? I though message > 160 chars is spliced into chunks by gnokii and
> > each sent to SMS alone ??
>
> Think of sending Multipart Message by hand.

Ehhh... Bullshit. In this case it is also sent as concatenated messages.

Think other way (and forget the above as well). You probably also have
some Big Brother or other reality show where you vote with SMS for
something. There are really *lots* of SMS sent in the prime time. SMSC is
some black box that only forward messages. There's some logic behind it to
check the correctness (database or something). It has the limited
throughtput. And it can take a couple tens of the seconds before you got
the reply from the SMSC. I think I'm going to know on Monday what's the
possible timeout.

Markus showed me the solution from mygnokii on this. And I'm not really
impressed. It is the timeout implemented in the other way. And it may loop
forever.
If the phone can handle the next request (I don't think it can) before
replying with the SMSC answer we don't have to wait actively for the
response. Anyway, at the moment I don't think that solution implemented in
gnokii is a bad way to do it.

pkot
-- 
mailto:address@hidden :: mailto:address@hidden
http://kt.linuxnews.pl/ :: Kernel Traffic po polsku