osmo-nitb and osmo-bts-trx problems with voice, no connection

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/OpenBSC@lists.osmocom.org/.

Rafael Diniz rafael at riseup.net
Fri Feb 23 03:26:13 UTC 2018


Worked - I have voice! Thanks Pau.

But GPRS is not ok yet. I'm running osmo-bts-lc15 and osmo-pcu in the
LC15, and the core network in my development pc.

osmo-sgsn gives me:

20180223001319967 DMM <0002> gprs_sgsn.c:726
MM(724056406933460/ccb930f7) Subscriber data update
20180223001319967 DMM <0002> sgsn_auth.c:219
MM(724056406933460/ccb930f7) Updating authorization (unknown ->
authenticate)
20180223001319967 DMM <0002> sgsn_auth.c:236
MM(724056406933460/ccb930f7) Missing auth tuples, authorization not possible
20180223001319967 DMM <0002> sgsn_auth.c:248
MM(724056406933460/ccb930f7) Got authorization update: state unknown ->
rejected
20180223001319967 DMM <0002> gprs_gmm.c:1140
MM(724056406933460/ccb930f7) Not authorized, rejecting ATTACH REQUEST
with cause 'IMSI unknown in HLR' (2)
20180223001319967 DMM <0002> gprs_gmm.c:489 MM(724056406933460/ccb930f7)
<- GPRS ATTACH REJECT: IMSI unknown in HLR

But I added the IMSIs in HLR with
subscriber imsi 724056406933460 create
subscriber imsi 724056406933460 update msisdn 12345678

I run (nightly builds):
osmo-stp -c osmo-stp.cfg
osmo-bsc -c osmo-bsc-lc15.cfg
osmo-msc -c osmo-msc.cfg
osmo-hlr -l hlr.db -c osmo-hlr.cfg
osmo-mgw -c osmo-mgw-msc.cfg
osmo-mgw -c osmo-mgw-bsc.cfg
osmo-sgsn -c osmo-sgsn.cfg
sudo osmo-ggsn -c osmo-ggsn.cfg

Attached goes my configuration files.

Cheers,
Rafael Diniz

On 02/21/2018 12:36 PM, Pau Espin Pedrol wrote:
> 
> 
> On 21/02/18 14:09, Rafael Diniz wrote:
>> Hi Pau,
>> Can I use loopback addresses or should I use local network addresses?
>>
> 
> Unless I'm forgetting some detail, it shuld be fine to run everything
> with loopback addresses.
> 
>> Btw, osmo-bsc_mgcp still need to be called together with current git
>> osmo-msc and osmo-mgw, right?
> 
> As far as I know latest osmo-msc already requires osmo-mgw.
> 
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmocom_configs.tar.gz
Type: application/gzip
Size: 2738 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20180223/ac12e569/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20180223/ac12e569/attachment-0001.bin>


More information about the OpenBSC mailing list