On Saturday 04 November 2006 09:10, Ivan Mitev wrote:
>
> when restarting asterisk, the sim card status of each module go from
>
> INITIALIZING
>
> to
>
> Status: FAILED
> Reason: Unexpected error: 'SIM busy

Okay, this is what happens:

During power-on the modules keep the SIM busy for some time, when and for how 
much depends on several variables, so, I try to be polite and I leave some 
time to the module to do what he needs to do with the SIM.

Sometimes, that time is not enough so I continue the initialization phase and 
find the SIM busy. The initialization fails, the module goes in FAILED state 
and the initialization is attempted again after some time (30 seconds) and 
goes fine.

So, it turns out to be just a cosmetic issue, if you want to enable 
AT-commands debugging *before* the initialization and paste me the trace, I 
can see where the SIM busy happens and try to figure out how to better wait 
for it to be released.

> i guess the "null" thing is because of changes in vgsm_operators.conf:
> from what i see in samples/, the country information of
> vgsm_operators.conf has moved to a new file, vgsm_countries.conf, and
> vgsm_operators now has "short_name" tags.

There has been some confusion with vgsm_operators.conf, in the latest version 
you will find the correct files, the variable name is "name_short", not 
short_name.

> btw, at each module initialization i get the following warnings (with
> both versions), but everything is working perfectly
>
> WARNING[19597]: comm.c:695 vgsm_match_urc: vivatel-1: Unhandled URC
> 'AT+COLP=1
> WARNING[19597]: comm.c:625 vgsm_match_urc: vivatel-1: Unexpected char 0x4f
> WARNING[19597]: comm.c:625 vgsm_match_urc: vivatel-1: Unexpected char 0x4b
> NOTICE[19597]: comm.c:1031 vgsm_comm_timed_out: vivatel-1: Serial lost
> synchronization

This is cosmetic too, it happens when there is some garbage left on the serial 
line. You shouldn't worry unless messages like those appear often and 
repeatedly.

Bye,

-- 
  Daniele "Vihai" Orlandi
  Espia S.r.l.
_______________________________________________
Visdn-hackers mailing list
[email protected]
https://mailman.uli.it/mailman/listinfo/visdn-hackers

Reply via email to