Newbie questions: Kc thru vty and CHAN_REQ

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/baseband-devel@lists.osmocom.org/.

David Ortega kktmp1 at gmail.com
Sun Mar 6 10:52:58 UTC 2011


Hi list !!
Three newbie questions:

1.- What is the correct way to put Kc in the the sim-test ?

the help command says:
ki             Set Key (Kc) on test card

there are two options:
   - ki comp128 HEX HEX HEX HEX HEX HEX HEX HEX HEX HEX HEX HEX HEX HEX HEX
HEX
   (i think this is to fix the Ki value - 16bytes)
   - ki xor HEX HEX HEX HEX HEX HEX HEX HEX HEX HEX HEX HEX
   (this one need 12 bytes, when Kc it's only 8)

2.- In both calls type MOC and MTC i can't see the CHAN_REQ frame from MS in
wireshark. I only get the RR IMM_ASS_CMD from BTS and the rest of the
traffic:

    (from wireshark)
    to_MS    12:34:38.411650             GSMTAP   (CCCH) (RR) Immediate
Assignment
    from-MS 12:34:38.411675             LAPDm    U, func=UI(DTAP) (RR)
Measurement Report
    from-MS 12:34:38.411695             LAPDm    U P, func=SABM(DTAP) (MM)
CM Service Request
    to-MS     12:34:38.431273             GSMTAP   (CCCH) (RR) Immediate
Assignment

    (from my mobile app logs)
    Sun Mar  6 12:34:38 2011 <0001> gsm48_rr.c:363 new state idle ->
connection pending
    Sun Mar  6 12:34:38 2011 <0001> gsm48_rr.c:1313 CHANNEL REQUEST: e0
(Orig TCH/F)
    (but i don't see this one in wireshark)
    Sun Mar  6 12:34:38 2011 <0004> gsm48_mm.c:887 new state MM IDLE, normal
service -> wait for RR connection (MM connection)

3.- How must I activate the timestamp in the logs ?

    I'm using:
       //target->print_timestamp = 0;
        target->print_timestamp = 1;
    But i guess that there is an easy way without recompile...

Thanx in advance !!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110306/dac31b81/attachment.htm>


More information about the baseband-devel mailing list