| class MLtsyDispatchSecurityVerifySecurityCode : public MLtsyDispatchInterface |
| Public Member Functions | |
|---|---|
| TInt | HandleVerifySecurityCodeReqL ( RMobilePhone::TMobilePhoneSecurityCode , const RMobilePhone::TCodeAndUnblockCode &) |
| Public Attributes | |
|---|---|
| const TInt | KLtsyDispatchSecurityVerifySecurityCodeApiId |
| TInt | HandleVerifySecurityCodeReqL | ( | RMobilePhone::TMobilePhoneSecurityCode | aSecCode, |
| const RMobilePhone::TCodeAndUnblockCode & | aCodes | |||
| ) | [pure virtual] | |||
The CTSY Dispatcher shall invoke this function on receiving the EMobilePhoneVerifySecurityCode request from the CTSY.
It is a request call that is completed by invoking CCtsyDispatcherCallback::CallbackSecurityVerifySecurityCodeComp()
Implementation of this interface should send a security code requiring verification to the phone.
If the security code required is one of the unblock codes (either PUK1 or PUK2), then the user must supply a new PIN1 or PIN2 code as well as the associated unblocking code. In this case, aUnblockCode will contain the unblocking code and aCode will contain the new PIN1 or PIN2 value. If the security code required is NOT one of the unblock codes, then the user only has to supply the one security code. In this case, aUnblockCode will be invalid and aCode will contain the required security code (PIN1, PIN2 or Phone Password).
| RMobilePhone::TMobilePhoneSecurityCode aSecCode | The type of code that is to be verified. |
| const RMobilePhone::TCodeAndUnblockCode & aCodes | The actual code and if a PUK1 or PUK2 is specified, the PUK code. |
| const TInt | KLtsyDispatchSecurityVerifySecurityCodeApiId | [static] |
Copyright ©2010 Nokia Corporation and/or its subsidiary(-ies).
All rights
reserved. Unless otherwise stated, these materials are provided under the terms of the Eclipse Public License
v1.0.