osmo-msc/openbsc/src/gprs/osmo_gbproxy.cfg

!
! OpenBSC configuration saved from vty
!   !
!
line vty
 no login
!
gbproxy
  nsip bss local port 23000
  nsip sgsn remote ip 127.0.0.1
  nsip sgsn remote port 7777
  nsip sgsn nsei 101
  nsip sgsn nsvci 101
[gprs] Build the SGSN stand-alone and not as part of bsc_hack Instead of continuing to add more and more functionality to the bsc_hack binary, we should have the new SGSN code run as a separate executable. After this commit we now build a 'osmo_sgsn' executable, using its own osmo_sgsn.cfg config file. However, the SGSN is not yet functional, mainly due to the fact that the BSSGP and GMM code are written with the assumption that there is a msgb->trx->bts and the according 'sturct gsm_bts' data model around - which clearly is no longer the case outside of bsc_hack. 2010-05-01 14:48:27 +00:00			`!`
			`! OpenBSC configuration saved from vty`
			`! !`
			`!`
			`line vty`
			`no login`
			`!`
			`gbproxy`
			`nsip bss local port 23000`
NS: Add support for persistent NS-VC configuration With persistent NS-VC configuration (configured through VTY), we can respond properly to BSS with a somewhat strange NS implementation Such as the BSplus. It enables us to respond with a proper NS-RESET (including NSVCI/NSEI) when receiving a NS-ALIVE or other PDU for a BLOCKED/DEAD NS-VC after our end of the connection is rebooted. 2010-05-12 15:55:23 +00:00			`nsip sgsn remote ip 127.0.0.1`
			`nsip sgsn remote port 7777`
			`nsip sgsn nsei 101`
			`nsip sgsn nsvci 101`