El día Wednesday, March 07, 2012 a las 11:36:24AM +0100, Radek Polak escribió:
> On Monday 05 March 2012 20:26:29 Denis Kenzior wrote:
>
> > You can always try ignoring CME ERROR 100 and re-try the CLCC poll.
> > Maybe the modem is in a transitional period (e.g. call being released)
> > and it ca
Matthias Apitz writes:
>> ofonod[1188]: App: < \r\n+CLCC: 1,1,4,0,0,"+420608828973",145\r\n\r\nOK\r\n
>> ofonod[1188]: App: > AT+CLCC\r
>> ofonod[1188]: App: < \r\n+CME ERROR: 100\r\n
>> ofonod[1188]: We are polling CLCC and received an error, retrying...
>> ofonod[1188]: App: > AT+CLCC\r
>> ofon
Hi Matthias,
> > > You can always try ignoring CME ERROR 100 and re-try the CLCC poll.
> > > Maybe the modem is in a transitional period (e.g. call being released)
> > > and it can't answer the CLCC properly. In other words, there's a bug
> > > related to timing of call state changes & CLCC imple
Hi Radek,
On 03/06/2012 03:30 PM, Radek Polak wrote:
> On Tuesday 06 March 2012 20:17:32 Dr. H. Nikolaus Schaller wrote:
>
>> @Radek: is it possible to manually contact the AT interface in this state
>> and try if it is still operational and another AT+CLCC would succeed?
>
> It seems after few
On Tuesday 06 March 2012 20:17:32 Dr. H. Nikolaus Schaller wrote:
> @Radek: is it possible to manually contact the AT interface in this state
> and try if it is still operational and another AT+CLCC would succeed?
It seems after few errors it starts working again - if i understand it right
(see
