Re: [Openbts-discuss] OpenBTS-UMTS registration failure

[Tom T. <to...@ts...>]

On Mon, Feb 2, 2015 at 12:45 PM, Jon w <no...@ho...> wrote:
> Hello, I am curious if there has been able to get a phone to register on an
> OpenBTS-UMTS network. I have tried several different SIM types, 2G and 3G,
> all with known KI values. These values have been uploaded are showing in the
> SIP_BUDDIES db but during the registration process the phone never gets
> authorized to access the network. I have captured the SIP traffic on the
> network and analyzed it in wireshark. The responses is always unauthorized.
> Are there any additional configurations needed on UMTS to allow phones on
> the network other than adding Ki to the subscriber database using the
> nmcli.py tool?

Check the sipauthserve log for any irregularities. Also look at the
database file itself and make sure that subscriber registry is
properly populated.

Using your favorite sqlite browser, make sure the following fields in
/var/lib/asterisk/sqlite3dir/sqlite3.db exist for your appropriate
SIM. Listed are the values that I manually set to match 2G-only
writable sysmoSIM-GR2 cards.

username: IMSI001010123456789 (prepended 'IMSI' required)
ki: 00112233445566778899AABBCCDDEEFF
a3_a8: /OpenBTS/comp128
callerid: 1234567 (may not required, but setting a value avoids an
empty column error)

At the moment, it seems that USIM's supporting Milenage or XOR will
fail on the GSM triplet style authentication. I don't know if this is
a 3GPP specification issue or just convention. Eventually we should
get the pertinent information on the wiki, but most of us are still
trying to figure out what works and what doesn't. Additional
information on this topic would be helpful.

  -TT