gsm - Getting an error while trying to send SS command using USAT application -


text after "itemprop =" text ">

I'm trying to perform a USIM call forwarding (say aka redirection) Send active command SS (ts 31.111 sections Using: 6.4.11, 8.14, etc.). Unfortunately I'm getting an error from the network I can not understand

I'm trying the following sequence:

  ME-> USIM: 8012000018 (FETCH 12 (process byte) USIM-> UICC towards MEIM MEIM- & gt; D01681030411008202818305000909FFAA120A25556777B49000D0 (active order) 16 (length) 81 (Order Details) 03 (length) 04 ( Order Number 11 (Send SS) 00 (RFU) 82 (Device Identification) 02 (Length) 81 (UICC) 83 (Network) 05 (Alpha Identifier) ​​00 (Length) 90 9 FFA1 20A 25556777 B4 (SS string = ** 21 * 0525576774 #) 9000 (OK) ME- & Gt; USIM: 801400000D (Terminal Rejection of Size 0x0 D) USIM- & gt; ME: 14 (process byte) ME- & gt; USIM: 81030411000202828103023424 81 (Command) 03 (Length) 04 (Command Number) 11 (Send SMS) 00 (RFU) 02 (Device Identification) 02 (Length) 82 (m) 81 (UIC) 03 (Results) 02 (Length ) 34 (SS return error) 24 (???)   

I can not understand what '24' means.

Just to make sure that I am using the correct SS string, I activated the call on the USOM in ROL and dial in the keypad ** 21 * 0525576774 # 80C200001C (length envelope 0x1C) UICC- & gt; ME: C2 (process byte) ME- & gt; UICC: D41A020282810909FFAA120A25556777B4130924F51027D078CF0013 D4 (envelope; UICC

  the result was as follows: 1A (Length) 02 (Device ID) 02 (Length) 82 (ME) 81 (UICC) 09 (SS) 09 (length) FFAA 120A 25556777 B4 (SS string) 13 (location information) 09 (length) 24F 51027D80CF003 (not relevant) USIM- & gt; ME: 9000 (OK)   

As you can see, the SS string is the same. It sends me this work seems to be working (call forwarding is active) so far when I try to send it to UICC from network I get '3424' error.

I have searched through glasses (TS 31.111, TS 22.030 and even TS 24.080) but still I did not get the most tiny leadership in the form of what is wrong.

Any help would be appreciated:.)

Cheers,

P.

I think the problem arises due to timer management (action in the contradiction with the current timer state ) becouse 0x34-> This means SS return error is 0x24-> The current timer position means action in contradiction.

Comments

Popular posts from this blog

Pass DB Connection parameters to a Kettle a.k.a PDI table Input step dynamically from Excel -

multithreading - PhantomJS-Node in a for Loop -

c++ - MATLAB .m file to .mex file using Matlab Compiler -