machtudong / asterisk-chan-dongle

Automatically exported from code.google.com/p/asterisk-chan-dongle
Other
0 stars 0 forks source link

lack of PIN enabled cards handling #79

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Trying to use card that's PIN-locked. Unfortunately it's not possible to 
disable PIN verification on this SIM card.

Operator blocked this functionality on their all sim cards.

at
OK
AT+CPIN?
+CPIN: SIM PIN

OK
AT+CPIN="11111"
OK
AT+CLCK="SC",0,"11111"
+CME ERROR: SIM failure
AT+CLCK="SC",2
+CLCK: 1

OK

What is the problem with pin handling actually?

Could AT+CPIN simply be added into at_enque_initialization() ?

Original issue reported on code.google.com by a.miskie...@gmail.com on 7 May 2012 at 9:16

GoogleCodeExporter commented 9 years ago
Started playing with this and I wonder why initialization is not being done in 
parallel with reading responses?

Right now it is impossible to make any action based on initialization responses.

Tried to make initialization going in parallel with responses but things don't 
work well yet.

Original comment by a.miskie...@gmail.com on 8 May 2012 at 10:10

Attachments:

GoogleCodeExporter commented 9 years ago
Hacky way but working. It should check if pin is required by doing AT+CPIN? in 
non hacky version.

Original comment by a.miskie...@gmail.com on 9 May 2012 at 12:54

Attachments:

GoogleCodeExporter commented 9 years ago
I not understand where chan_dongle must get PINs?
And what will be is PIN is not correct?
I think 3 times of bad PIN and crd blocked to PUK1.

You are really want this behaviour?

Original comment by bg_...@mail.ru on 13 May 2012 at 7:44

GoogleCodeExporter commented 9 years ago
The sim card I have is PIN protected. There is no way to disable this PIN 
protection - it's not possible (blocked by sim hardware itself).

So I need chan_dongle to send pin to the sim and enable it for use.

3 times of bad PIN is a problem indeed, so I'm careful in my setup.

GSM phones tell how many PIN requests left, so the solution would be to do the 
same check in chan_dongle and avoid sending PIN if only 1 request left for 
example + log big fat warning to the user. That would prevent blocking card to 
PUK1.

(note that trying to enable PIN in a sim card which is not pin protected 
doesn't cause any harm at least with mine other sim card, from different 
provider)

Original comment by a.miskie...@gmail.com on 21 May 2012 at 10:08

GoogleCodeExporter commented 9 years ago
you free to use udev with external scripts for pin verification.

I'm not going to load the module unnecessary functionality

Original comment by bg_...@mail.ru on 19 Jul 2012 at 10:24