11 Jul
2019
11 Jul
'19
5:14 p.m.
Dear Osmocom & NextEPC Community,
Today I've added CS Fallback and released NextEPC v0.5.0
So, I'd just like to test this part with Osmocom project, but it seems to
be a difficult task. The reason is why I have little knowledge about 2G/3G.
Nevertheless, I will try to do it
BTW, I don't know if there is anyone who wants to integrate this big thing.
Even though I'm not sure if this will help, but let me introduce the
configuration of the NextEPC.
To use SGsAP, change the mme.conf as follows:
#
# <sgsap>
#
# o Single MSC/VLR
# sgsap:
# addr: 127.0.0.2
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4130
# lac: 43690
#
# o Multiple MSC/VLR
# sgsap:
# - addr: 127.0.0.2
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4131
# lac: 43692
# - addr
# - 127.0.0.3
# - fe80::2%lo0
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4132
# lac: 43692
# - name: msc.open5gs.org
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4133
# lac: 43693
#
FYI, I also attach the pcap that I run with nextepc simulator as below.
$ ./tests/testcsfb
mo-idle-test : SUCCESS
mt-idle-test : SUCCESS
mo-active-test : SUCCESS
mt-active-test : SUCCESS
All tests passed.
Feel free to raise any questions about this things.
Best Regards,
Sukchan
11 Jul
11 Jul
6:47 p.m.
Hi Sukchan,
On Fri, Jul 12, 2019 at 12:14:51AM +0900, Sukchan Lee wrote:
Today I've added CS Fallback and released NextEPC
v0.5.0
Thanks a lot!
So, I'd just like to test this part with Osmocom
project, but it seems to
be a difficult task. The reason is why I have little knowledge about 2G/3G.
Nevertheless, I will try to do it
I advise you to not spend too much time on it until we can provide you
with a set of configuration and instructions on how to configure this,
instead of spending a lot of time in trial and error. I think we can
save you some time there.
A good starting point would be to use the nightly builds for Ubuntu or Debian,
(see https://osmocom.org/projects/cellular-infrastructure/wiki/Nightly_Builds)
and try to follow the general instructions of
https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_I…. The
goal would be to create a network with two phones/IMSIs
where you can have a 2G-to-2G voice call first. Only once that works, the
LTE neighbor cell information and SGs configuration can be added.
You will need the following parts for a minimal 2G setup:
* osmo-trx + osmo-bts-trx (if using SDR like B2x0)
* osmo-bsc (RR)
* osmo-msc (MM + CC)
* osmo-hlr
* osmo-stp (for SS7/SIGTRAN between BSC and MSC)
* osmo-mgw (for RTP audio streams; one instance can be shared between BSC and MSC)
All of the above can run on a single machine
BTW, I don't know if there is anyone who wants to
integrate this big thing.
For sure we want to, and we also know there are users out there who want to.
Even though I'm not sure if this will help, but
let me introduce the
configuration of the NextEPC.
Thanks, this is useful. We'll try to to set this up accordingly, but it may
take some time.
Philipp (Cc) has been developing most of the SGs interface on the Osmocom
side, he can help you (here on this list and by direct e-mail) with any related
issues.
FYI, I also attach the pcap that I run with nextepc
simulator as below.
Thanks, I'd like to ask Philipp to review this and report if it reflects his
expectations about the SGs interface procedures.
btw/unrelated: I've been hacking a lot on TTCN-3 tests for the MME, and
I've managed to get the way into NAS (EMM/ESM) and am getting all the
way up to a Attach Reject (see attached pcap). As I'm only simulating
S1AP and SGsAP so far (and not diameter), it's expected that the attach
will be rejected. I guess I'll start with using nextepc-hss first, and
add diameter support to the tests only in a later step.
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
10:16 p.m.
Rhizomatica is very much interested in testing such setup with CS voice
fallback for LTE to GSM.
Cheers!
Rafael Diniz
On 7/11/19 1:47 PM, Harald Welte wrote:
Hi Sukchan,
On Fri, Jul 12, 2019 at 12:14:51AM +0900, Sukchan Lee wrote:
Today I've added CS Fallback and released
NextEPC v0.5.0
Thanks a lot!
So, I'd just like to test this part with
Osmocom project, but it seems to
be a difficult task. The reason is why I have little knowledge about 2G/3G.
Nevertheless, I will try to do it
I advise you to not spend too much time on it until we can provide you
with a set of configuration and instructions on how to configure this,
instead of spending a lot of time in trial and error. I think we can
save you some time there.
A good starting point would be to use the nightly builds for Ubuntu or Debian,
(see https://osmocom.org/projects/cellular-infrastructure/wiki/Nightly_Builds)
and try to follow the general instructions of
https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_I…. The
goal would be to create a network with two phones/IMSIs
where you can have a 2G-to-2G voice call first. Only once that works, the
LTE neighbor cell information and SGs configuration can be added.
You will need the following parts for a minimal 2G setup:
* osmo-trx + osmo-bts-trx (if using SDR like B2x0)
* osmo-bsc (RR)
* osmo-msc (MM + CC)
* osmo-hlr
* osmo-stp (for SS7/SIGTRAN between BSC and MSC)
* osmo-mgw (for RTP audio streams; one instance can be shared between BSC and MSC)
All of the above can run on a single machine
BTW, I don't know if there is anyone who
wants to integrate this big thing.
For sure we want to, and we also know there are users out there who want to.
Even though I'm not sure if this will help,
but let me introduce the
configuration of the NextEPC.
Thanks, this is useful. We'll try to to set this up accordingly, but it may
take some time.
Philipp (Cc) has been developing most of the SGs interface on the Osmocom
side, he can help you (here on this list and by direct e-mail) with any related
issues.
FYI, I also attach the pcap that I run with
nextepc simulator as below.
Thanks, I'd like to ask Philipp to review this and report if it reflects his
expectations about the SGs interface procedures.
btw/unrelated: I've been hacking a lot on TTCN-3 tests for the MME, and
I've managed to get the way into NAS (EMM/ESM) and am getting all the
way up to a Attach Reject (see attached pcap). As I'm only simulating
S1AP and SGsAP so far (and not diameter), it's expected that the attach
will be rejected. I guess I'll start with using nextepc-hss first, and
add diameter support to the tests only in a later step.
Regards,
Harald
12 Jul
12 Jul
12:19 a.m.
Hi Harald,
There is no pcap file. Could you attach it?
Thanks!
Best Regards,
Sukchan
2019. 7. 12. 오전 1:47, Harald Welte <laforge(a)gnumonks.org> 작성:
Hi Sukchan,
On Fri, Jul 12, 2019 at 12:14:51AM +0900, Sukchan
Lee wrote:
Today I've added CS Fallback and released NextEPC v0.5.0
Thanks a lot!
So, I'd just like to test this part with
Osmocom project, but it seems to
be a difficult task. The reason is why I have little knowledge about 2G/3G.
Nevertheless, I will try to do it
I advise you to not spend too much time on it until we can provide you
with a set of configuration and instructions on how to configure this,
instead of spending a lot of time in trial and error. I think we can
save you some time there.
A good starting point would be to use the nightly builds for Ubuntu or Debian,
(see https://osmocom.org/projects/cellular-infrastructure/wiki/Nightly_Builds)
and try to follow the general instructions of
https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_I…. The
goal would be to create a network with two phones/IMSIs
where you can have a 2G-to-2G voice call first. Only once that works, the
LTE neighbor cell information and SGs configuration can be added.
You will need the following parts for a minimal 2G setup:
* osmo-trx + osmo-bts-trx (if using SDR like B2x0)
* osmo-bsc (RR)
* osmo-msc (MM + CC)
* osmo-hlr
* osmo-stp (for SS7/SIGTRAN between BSC and MSC)
* osmo-mgw (for RTP audio streams; one instance can be shared between BSC and MSC)
All of the above can run on a single machine
BTW, I don't know if there is anyone who
wants to integrate this big thing.
For sure we want to, and we also know there are users out there who want to.
Even though I'm not sure if this will help,
but let me introduce the
configuration of the NextEPC.
Thanks, this is useful. We'll try to to set this up accordingly, but it may
take some time.
Philipp (Cc) has been developing most of the SGs interface on the Osmocom
side, he can help you (here on this list and by direct e-mail) with any related
issues.
FYI, I also attach the pcap that I run with
nextepc simulator as below.
Thanks, I'd like to ask Philipp to review this and report if it reflects his
expectations about the SGs interface procedures.
btw/unrelated: I've been hacking a lot on TTCN-3 tests for the MME, and
I've managed to get the way into NAS (EMM/ESM) and am getting all the
way up to a Attach Reject (see attached pcap). As I'm only simulating
S1AP and SGsAP so far (and not diameter), it's expected that the attach
will be rejected. I guess I'll start with using nextepc-hss first, and
add diameter support to the tests only in a later step.
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
5:36 a.m.
New subject: TTCN3 tests for MME (was Re: CS Fallback in NextEPC)
Hi Sukchan,
On Fri, Jul 12, 2019 at 07:19:35AM +0900, 이석찬 wrote:
2019. 7. 12. 오전 1:47, Harald Welte
<laforge(a)gnumonks.org> 작성:
Sorry, please find it attached. It's not much, but it shows that the basic
S1AP and NAS infrastructure for emulating eNB and UE works. I sill have
to write quite a bit of code to actually perform the authentication
successful, as well as to implement at least integrity protection on the
NAS layer.
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
btw/unrelated: I've been hacking a lot on
TTCN-3 tests for the MME, and
I've managed to get the way into NAS (EMM/ESM) and am getting all the
way up to a Attach Reject (see attached pcap). As I'm only simulating
S1AP and SGsAP so far (and not diameter), it's expected that the attach
will be rejected. I guess I'll start with using nextepc-hss first, and
add diameter support to the tests only in a later step.
There is no pcap file. Could you attach it?
Thanks! 
13 Jul
13 Jul
11:35 p.m.
Hello Sukchan and friends.
I'm trying to use the CSFB in test lab, and every time that nextepc send
the UEContextModificationRequest, the UE respond with an
UEContextModificationFaliure [ Protocol-cause=semantic-error ].
[image: image.png]
I'm looking why I'm getting this. Someone have any idea?
Thanks
Romeu Medeiros
On Thu, Jul 11, 2019 at 12:15 PM Sukchan Lee <acetcom(a)gmail.com> wrote:
Dear Osmocom & NextEPC Community,
Today I've added CS Fallback and released NextEPC v0.5.0
So, I'd just like to test this part with Osmocom project, but it seems to
be a difficult task. The reason is why I have little knowledge about 2G/3G.
Nevertheless, I will try to do it
BTW, I don't know if there is anyone who wants to integrate this big thing.
Even though I'm not sure if this will help, but let me introduce the
configuration of the NextEPC.
To use SGsAP, change the mme.conf as follows:
#
# <sgsap>
#
# o Single MSC/VLR
# sgsap:
# addr: 127.0.0.2
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4130
# lac: 43690
#
# o Multiple MSC/VLR
# sgsap:
# - addr: 127.0.0.2
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4131
# lac: 43692
# - addr
# - 127.0.0.3
# - fe80::2%lo0
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4132
# lac: 43692
# - name: msc.open5gs.org
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4133
# lac: 43693
#
FYI, I also attach the pcap that I run with nextepc simulator as below.
$ ./tests/testcsfb
mo-idle-test : SUCCESS
mt-idle-test : SUCCESS
mo-active-test : SUCCESS
mt-active-test : SUCCESS
All tests passed.
Feel free to raise any questions about this things.
Best Regards,
Sukchan
11:50 p.m.
I found this in the 3GPP documentations [1]:
[image: image.png]
I will change the code to send only the CSFallback indicator in this case
to see if can solve the problem.
Thanks
Romeu Medeiros
1.
https://www.etsi.org/deliver/etsi_ts/136400_136499/136413/09.10.00_60/ts_13…
On Sat, Jul 13, 2019 at 6:35 PM Romeu Medeiros <medeiros(a)medeiros.eng.br>
wrote:
Hello Sukchan and friends.
I'm trying to use the CSFB in test lab, and every time that nextepc send
the UEContextModificationRequest, the UE respond with an
UEContextModificationFaliure [ Protocol-cause=semantic-error ].
[image: image.png]
I'm looking why I'm getting this. Someone have any idea?
Thanks
Romeu Medeiros
On Thu, Jul 11, 2019 at 12:15 PM Sukchan Lee <acetcom(a)gmail.com> wrote:
> Dear Osmocom & NextEPC Community,
>
> Today I've added CS Fallback and released NextEPC v0.5.0
>
> So, I'd just like to test this part with Osmocom project, but it seems to
> be a difficult task. The reason is why I have little knowledge about 2G/3G.
> Nevertheless, I will try to do it
>
> BTW, I don't know if there is anyone who wants to integrate this big
> thing.
> Even though I'm not sure if this will help, but let me introduce the
> configuration of the NextEPC.
>
> To use SGsAP, change the mme.conf as follows:
>
> #
> # <sgsap>
> #
> # o Single MSC/VLR
> # sgsap:
> # addr: 127.0.0.2
> # plmn_id:
> # mcc: 001
> # mnc: 01
> # tac: 4130
> # lac: 43690
> #
> # o Multiple MSC/VLR
> # sgsap:
> # - addr: 127.0.0.2
> # plmn_id:
> # mcc: 001
> # mnc: 01
> # tac: 4131
> # lac: 43692
> # - addr
> # - 127.0.0.3
> # - fe80::2%lo0
> # plmn_id:
> # mcc: 001
> # mnc: 01
> # tac: 4132
> # lac: 43692
> # - name: msc.open5gs.org
> # plmn_id:
> # mcc: 001
> # mnc: 01
> # tac: 4133
> # lac: 43693
> #
>
> FYI, I also attach the pcap that I run with nextepc simulator as below.
>
> $ ./tests/testcsfb
> mo-idle-test : SUCCESS
> mt-idle-test : SUCCESS
> mo-active-test : SUCCESS
> mt-active-test : SUCCESS
> All tests passed.
>
> Feel free to raise any questions about this things.
>
> Best Regards,
> Sukchan
>
>
14 Jul
14 Jul
1:04 a.m.
Hello Sukchan,
Now after remove this everything run correctly.
[image: image.png]
I will made the change more beatiful and pull the modification to the git
to you aprove.
Thanks
Romeu Medeiros
On Sat, Jul 13, 2019 at 6:50 PM Romeu Medeiros <medeiros(a)medeiros.eng.br>
wrote:
I found this in the 3GPP documentations [1]:
[image: image.png]
I will change the code to send only the CSFallback indicator in this case
to see if can solve the problem.
Thanks
Romeu Medeiros
1.
https://www.etsi.org/deliver/etsi_ts/136400_136499/136413/09.10.00_60/ts_13…
On Sat, Jul 13, 2019 at 6:35 PM Romeu Medeiros <medeiros(a)medeiros.eng.br>
wrote:
> Hello Sukchan and friends.
>
> I'm trying to use the CSFB in test lab, and every time that nextepc send
> the UEContextModificationRequest, the UE respond with an
> UEContextModificationFaliure [ Protocol-cause=semantic-error ].
>
> [image: image.png]
>
> I'm looking why I'm getting this. Someone have any idea?
>
> Thanks
>
> Romeu Medeiros
>
> On Thu, Jul 11, 2019 at 12:15 PM Sukchan Lee <acetcom(a)gmail.com> wrote:
>
>> Dear Osmocom & NextEPC Community,
>>
>> Today I've added CS Fallback and released NextEPC v0.5.0
>>
>> So, I'd just like to test this part with Osmocom project, but it seems
>> to be a difficult task. The reason is why I have little knowledge about
>> 2G/3G. Nevertheless, I will try to do it
>>
>> BTW, I don't know if there is anyone who wants to integrate this big
>> thing.
>> Even though I'm not sure if this will help, but let me introduce the
>> configuration of the NextEPC.
>>
>> To use SGsAP, change the mme.conf as follows:
>>
>> #
>> # <sgsap>
>> #
>> # o Single MSC/VLR
>> # sgsap:
>> # addr: 127.0.0.2
>> # plmn_id:
>> # mcc: 001
>> # mnc: 01
>> # tac: 4130
>> # lac: 43690
>> #
>> # o Multiple MSC/VLR
>> # sgsap:
>> # - addr: 127.0.0.2
>> # plmn_id:
>> # mcc: 001
>> # mnc: 01
>> # tac: 4131
>> # lac: 43692
>> # - addr
>> # - 127.0.0.3
>> # - fe80::2%lo0
>> # plmn_id:
>> # mcc: 001
>> # mnc: 01
>> # tac: 4132
>> # lac: 43692
>> # - name: msc.open5gs.org
>> # plmn_id:
>> # mcc: 001
>> # mnc: 01
>> # tac: 4133
>> # lac: 43693
>> #
>>
>> FYI, I also attach the pcap that I run with nextepc simulator as below.
>>
>> $ ./tests/testcsfb
>> mo-idle-test : SUCCESS
>> mt-idle-test : SUCCESS
>> mo-active-test : SUCCESS
>> mt-active-test : SUCCESS
>> All tests passed.
>>
>> Feel free to raise any questions about this things.
>>
>> Best Regards,
>> Sukchan
>>
>>
19 Jul
19 Jul
6:29 p.m.
Hi all,
I'd also like to test SMS and CSFB in LTE. I have some experience with
the Osmocom GSM stack, but not much with the NextEPC LTE. Could you
point me which fields should I set in the configuration files?
Thanks,
Rafael Diniz
On 7/13/19 6:35 PM, Romeu Medeiros wrote:
Hello Sukchan and friends.
I'm trying to use the CSFB in test lab, and every time that nextepc send
the UEContextModificationRequest, the UE respond with an
UEContextModificationFaliure [ Protocol-cause=semantic-error ].
image.png
I'm looking why I'm getting this. Someone have any idea?
Thanks
Romeu Medeiros
On Thu, Jul 11, 2019 at 12:15 PM Sukchan Lee <acetcom(a)gmail.com
<mailto:acetcom@gmail.com>> wrote:
Dear Osmocom & NextEPC Community,
Today I've added CS Fallback and released NextEPC v0.5.0
So, I'd just like to test this part with Osmocom project, but it
seems to be a difficult task. The reason is why I have little
knowledge about 2G/3G. Nevertheless, I will try to do it
BTW, I don't know if there is anyone who wants to integrate this big
thing.
Even though I'm not sure if this will help, but let me introduce the
configuration of the NextEPC.
To use SGsAP, change the mme.conf as follows:
#
# <sgsap>
#
# o Single MSC/VLR
# sgsap:
# addr: 127.0.0.2
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4130
# lac: 43690
#
# o Multiple MSC/VLR
# sgsap:
# - addr: 127.0.0.2
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4131
# lac: 43692
# - addr
# - 127.0.0.3
# - fe80::2%lo0
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4132
# lac: 43692
# - name: msc.open5gs.org <http://msc.open5gs.org>
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4133
# lac: 43693
#
FYI, I also attach the pcap that I run with nextepc simulator as below.
$ ./tests/testcsfb
mo-idle-test : SUCCESS
mt-idle-test : SUCCESS
mo-active-test : SUCCESS
mt-active-test : SUCCESS
All tests passed.
Feel free to raise any questions about this things.
Best Regards,
Sukchan
9:58 p.m.
Hello Rafael
I just configure the NextEPC to connect via SGS to OSMO-MSC, like this:
sgsap:
addr: 127.0.0.1
port: 29118
name: vlr.example.net
tai:
plmn_id:
mcc: 724
mnc: 21
tac: 12345
lai:
plmn_id:
mcc: 724
mnc: 4
lac: 51544
And the configuration in the MSC:
sgs
local-port 29118
local-ip 0.0.0.0
vlr-name vlr.example.net
And configure the IMSI in the Osmo-HLR and NextEPC-HSS
If you need more help tell me.
Thanks
Romeu Medeiros
And
On Fri, Jul 19, 2019 at 1:31 PM Rafael Diniz <rafael(a)rhizomatica.org> wrote:
Hi all,
I'd also like to test SMS and CSFB in LTE. I have some experience with
the Osmocom GSM stack, but not much with the NextEPC LTE. Could you
point me which fields should I set in the configuration files?
Thanks,
Rafael Diniz
On 7/13/19 6:35 PM, Romeu Medeiros wrote:
Hello Sukchan and friends.
I'm trying to use the CSFB in test lab, and every time that nextepc send
the UEContextModificationRequest, the UE respond with an
UEContextModificationFaliure [ Protocol-cause=semantic-error ].
image.png
I'm looking why I'm getting this. Someone have any idea?
Thanks
Romeu Medeiros
On Thu, Jul 11, 2019 at 12:15 PM Sukchan Lee <acetcom(a)gmail.com
<mailto:acetcom@gmail.com>> wrote:
Dear Osmocom & NextEPC Community,
Today I've added CS Fallback and released NextEPC v0.5.0
So, I'd just like to test this part with Osmocom project, but it
seems to be a difficult task. The reason is why I have little
knowledge about 2G/3G. Nevertheless, I will try to do it
BTW, I don't know if there is anyone who wants to integrate this big
thing.
Even though I'm not sure if this will help, but let me introduce the
configuration of the NextEPC.
To use SGsAP, change the mme.conf as follows:
#
# <sgsap>
#
# o Single MSC/VLR
# sgsap:
# addr: 127.0.0.2
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4130
# lac: 43690
#
# o Multiple MSC/VLR
# sgsap:
# - addr: 127.0.0.2
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4131
# lac: 43692
# - addr
# - 127.0.0.3
# - fe80::2%lo0
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4132
# lac: 43692
# - name: msc.open5gs.org <http://msc.open5gs.org>
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4133
# lac: 43693
#
FYI, I also attach the pcap that I run with nextepc simulator as
below.
$ ./tests/testcsfb
mo-idle-test : SUCCESS
mt-idle-test : SUCCESS
mo-active-test : SUCCESS
mt-active-test : SUCCESS
All tests passed.
Feel free to raise any questions about this things.
Best Regards,
Sukchan
10:51 p.m.
Obrigado Romeu!
On 7/19/19 4:58 PM, Romeu Medeiros wrote:
Hello Rafael
I just configure the NextEPC to connect via SGS to OSMO-MSC, like this:
sgsap:
addr: 127.0.0.1
port: 29118
name: vlr.example.net <http://vlr.example.net>
tai:
plmn_id:
mcc: 724
mnc: 21
tac: 12345
lai:
plmn_id:
mcc: 724
mnc: 4
lac: 51544
And the configuration in the MSC:
sgs
local-port 29118
local-ip 0.0.0.0
vlr-name vlr.example.net <http://vlr.example.net>
And configure the IMSI in the Osmo-HLR and NextEPC-HSS
If you need more help tell me.
Thanks
Romeu Medeiros
And
On Fri, Jul 19, 2019 at 1:31 PM Rafael Diniz <rafael(a)rhizomatica.org
<mailto:rafael@rhizomatica.org>> wrote:
Hi all,
I'd also like to test SMS and CSFB in LTE. I have some experience with
the Osmocom GSM stack, but not much with the NextEPC LTE. Could you
point me which fields should I set in the configuration files?
Thanks,
Rafael Diniz
On 7/13/19 6:35 PM, Romeu Medeiros wrote:
Hello Sukchan and friends.
I'm trying to use the CSFB in test lab, and every time that
nextepc send
the UEContextModificationRequest, the UE respond
with an
UEContextModificationFaliure [ Protocol-cause=semantic-error ].
image.png
I'm looking why I'm getting this. Someone have any idea?
Thanks
Romeu Medeiros
On Thu, Jul 11, 2019 at 12:15 PM Sukchan Lee <acetcom(a)gmail.com
<mailto:acetcom@gmail.com>
<mailto:acetcom@gmail.com
<mailto:acetcom@gmail.com>>> wrote:
Dear Osmocom & NextEPC Community,
Today I've added CS Fallback and released NextEPC v0.5.0
So, I'd just like to test this part with Osmocom project, but it
seems to be a difficult task. The reason is why I have little
knowledge about 2G/3G. Nevertheless, I will try to do it
BTW, I don't know if there is anyone who wants to integrate
this big
thing.
Even though I'm not sure if this will help, but let me
introduce the
configuration of the NextEPC.
To use SGsAP, change the mme.conf as follows:
#
# <sgsap>
#
# o Single MSC/VLR
# sgsap:
# addr: 127.0.0.2
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4130
# lac: 43690
#
# o Multiple MSC/VLR
# sgsap:
# - addr: 127.0.0.2
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4131
# lac: 43692
# - addr
# - 127.0.0.3
# - fe80::2%lo0
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4132
# lac: 43692
# - name: msc.open5gs.org <http://msc.open5gs.org>
<http://msc.open5gs.org>
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4133
# lac: 43693
#
FYI, I also attach the pcap that I run with nextepc simulator
as below.
$ ./tests/testcsfb
mo-idle-test : SUCCESS
mt-idle-test : SUCCESS
mo-active-test : SUCCESS
mt-active-test : SUCCESS
All tests passed.
Feel free to raise any questions about this things.
Best Regards,
Sukchan
2 Aug
2 Aug
11:45 p.m.
Hi all,
Just a small question - what is the meaning of the "name" field in the
sgsap configuration?
Thanks,
Rafael Diniz
On 7/19/19 5:51 PM, Rafael Diniz wrote:
Obrigado Romeu!
On 7/19/19 4:58 PM, Romeu Medeiros wrote:
Hello Rafael
I just configure the NextEPC to connect via SGS to OSMO-MSC, like this:
sgsap:
addr: 127.0.0.1
port: 29118
name: vlr.example.net <http://vlr.example.net>
tai:
plmn_id:
mcc: 724
mnc: 21
tac: 12345
lai:
plmn_id:
mcc: 724
mnc: 4
lac: 51544
And the configuration in the MSC:
sgs
local-port 29118
local-ip 0.0.0.0
vlr-name vlr.example.net <http://vlr.example.net>
And configure the IMSI in the Osmo-HLR and NextEPC-HSS
If you need more help tell me.
Thanks
Romeu Medeiros
And
On Fri, Jul 19, 2019 at 1:31 PM Rafael Diniz <rafael(a)rhizomatica.org
<mailto:rafael@rhizomatica.org>> wrote:
Hi all,
I'd also like to test SMS and CSFB in LTE. I have some experience with
the Osmocom GSM stack, but not much with the NextEPC LTE. Could you
point me which fields should I set in the configuration files?
Thanks,
Rafael Diniz
On 7/13/19 6:35 PM, Romeu Medeiros wrote:
Hello Sukchan and friends.
I'm trying to use the CSFB in test lab, and every time that
nextepc send
the UEContextModificationRequest, the UE respond
with an
UEContextModificationFaliure [ Protocol-cause=semantic-error ].
image.png
I'm looking why I'm getting this. Someone have any idea?
Thanks
Romeu Medeiros
On Thu, Jul 11, 2019 at 12:15 PM Sukchan Lee <acetcom(a)gmail.com
<mailto:acetcom@gmail.com>
<mailto:acetcom@gmail.com
<mailto:acetcom@gmail.com>>> wrote:
Dear Osmocom & NextEPC Community,
Today I've added CS Fallback and released NextEPC v0.5.0
So, I'd just like to test this part with Osmocom project, but it
seems to be a difficult task. The reason is why I have little
knowledge about 2G/3G. Nevertheless, I will try to do it
BTW, I don't know if there is anyone who wants to integrate
this big
thing.
Even though I'm not sure if this will help, but let me
introduce the
configuration of the NextEPC.
To use SGsAP, change the mme.conf as follows:
#
# <sgsap>
#
# o Single MSC/VLR
# sgsap:
# addr: 127.0.0.2
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4130
# lac: 43690
#
# o Multiple MSC/VLR
# sgsap:
# - addr: 127.0.0.2
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4131
# lac: 43692
# - addr
# - 127.0.0.3
# - fe80::2%lo0
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4132
# lac: 43692
# - name: msc.open5gs.org <http://msc.open5gs.org>
<http://msc.open5gs.org>
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4133
# lac: 43693
#
FYI, I also attach the pcap that I run with nextepc simulator
as below.
$ ./tests/testcsfb
mo-idle-test : SUCCESS
mt-idle-test : SUCCESS
mo-active-test : SUCCESS
mt-active-test : SUCCESS
All tests passed.
Feel free to raise any questions about this things.
Best Regards,
Sukchan
3 Aug
3 Aug
12:05 a.m.
Hi Rafael,
In the NextEPC, there are two ways to specify peers. 'addr' sets the IP
address, and 'name' sets the hostname.
So, if your network is configured to look up the VLR as a hostname, you can
use 'name'.
'port' was just made for testing. If you want to use a different port
without using standard 29118, you can put 'port' number.
By the way, I've changed how to configure CS Fallback & SMS as below.
# o Single MSC/VLR(127.0.0.2)
sgsap:
addr: 127.0.0.2
map:
tai:
plmn_id:
mcc: 001
mnc: 01
tac: 4130
lai:
plmn_id:
mcc: 001
mnc: 01
lac: 43690
map:
tai:
plmn_id:
mcc: 002
mnc: 02
tac: 4132
lai:
plmn_id:
mcc: 002
mnc: 02
lac: 43692
# o Multiple MSC/VLR
sgsap:
- addr: 127.0.0.2
port: 29119
map:
tai:
plmn_id:
mcc: 001
mnc: 01
tac: 4131
lai:
plmn_id:
mcc: 001
mnc: 01
lac: 43691
map:
tai:
plmn_id:
mcc: 002
mnc: 02
tac: 4132
lai:
plmn_id:
mcc: 002
mnc: 02
lac: 43692
- addr
- 127.0.0.3
- fe80::2%lo
map:
tai:
plmn_id:
mcc: 001
mnc: 01
tac: 4132
lai:
plmn_id:
mcc: 002
mnc: 02
lac: 43692
- name: msc.open5gs.org
map:
tai:
plmn_id:
mcc: 001
mnc: 01
tac: 4133
lai:
plmn_id:
mcc: 002
mnc: 02
lac: 43693
Thanks a lot!
Best Regards,
Sukchan
On Sat, Aug 3, 2019 at 6:45 AM Rafael Diniz <rafael(a)rhizomatica.org> wrote:
Hi all,
Just a small question - what is the meaning of the "name" field in the
sgsap configuration?
Thanks,
Rafael Diniz
On 7/19/19 5:51 PM, Rafael Diniz wrote:
Obrigado Romeu!
On 7/19/19 4:58 PM, Romeu Medeiros wrote:
> Hello Rafael
>
> I just configure the NextEPC to connect via SGS to OSMO-MSC, like this:
>
> sgsap:
> addr: 127.0.0.1
> port: 29118
> name: vlr.example.net <http://vlr.example.net>
> tai:
> plmn_id:
> mcc: 724
> mnc: 21
> tac: 12345
> lai:
> plmn_id:
> mcc: 724
> mnc: 4
> lac: 51544
>
> And the configuration in the MSC:
>
> sgs
> local-port 29118
> local-ip 0.0.0.0
> vlr-name vlr.example.net <http://vlr.example.net>
>
> And configure the IMSI in the Osmo-HLR and NextEPC-HSS
>
> If you need more help tell me.
>
>
> Thanks
>
> Romeu Medeiros
>
>
> And
>
> On Fri, Jul 19, 2019 at 1:31 PM Rafael Diniz <rafael(a)rhizomatica.org
> <mailto:rafael@rhizomatica.org>> wrote:
>
> Hi all,
>
> I'd also like to test SMS and CSFB in LTE. I have some experience
with
> the Osmocom GSM stack, but not much with
the NextEPC LTE. Could you
> point me which fields should I set in the configuration files?
>
> Thanks,
> Rafael Diniz
>
> On 7/13/19 6:35 PM, Romeu Medeiros wrote:
> > Hello Sukchan and friends.
> >
> > I'm trying to use the CSFB in test lab, and every time that
> nextepc send
> > the UEContextModificationRequest, the UE respond with an
> > UEContextModificationFaliure [ Protocol-cause=semantic-error ].
> >
> > image.png
> >
> > I'm looking why I'm getting this. Someone have any idea?
> >
> > Thanks
> >
> > Romeu Medeiros
> >
> > On Thu, Jul 11, 2019 at 12:15 PM Sukchan Lee <acetcom(a)gmail.com
> <mailto:acetcom@gmail.com>
> > <mailto:acetcom@gmail.com <mailto:acetcom@gmail.com>>>
wrote:
> >
> > Dear Osmocom & NextEPC Community,
> >
> > Today I've added CS Fallback and released NextEPC v0.5.0
> >
> > So, I'd just like to test this part with Osmocom project, but
it
seems to be a difficult task. The reason is why I
have little
knowledge about 2G/3G. Nevertheless, I will try to do it
BTW, I don't know if there is anyone who wants to integrate
this big
thing.
Even though I'm not sure if this will help, but let me
introduce the
configuration of the NextEPC.
To use SGsAP, change the mme.conf as follows:
#
# <sgsap>
#
# o Single MSC/VLR
# sgsap:
# addr: 127.0.0.2
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4130
# lac: 43690
#
# o Multiple MSC/VLR
# sgsap:
# - addr: 127.0.0.2
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4131
# lac: 43692
# - addr
# - 127.0.0.3
# - fe80::2%lo0
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4132
# lac: 43692
# - name: msc.open5gs.org <http://msc.open5gs.org>
<http://msc.open5gs.org>
# plmn_id:
# mcc: 001
# mnc: 01
# tac: 4133
# lac: 43693
#
FYI, I also attach the pcap that I run with nextepc simulator
as below.
$ ./tests/testcsfb
mo-idle-test : SUCCESS
mt-idle-test : SUCCESS
mo-active-test : SUCCESS
mt-active-test : SUCCESS
All tests passed.
Feel free to raise any questions about this things.
Best Regards,
Sukchan
5 Aug
5 Aug
9:42 p.m.
Thanks a lot Sukchan,
I'll test this week!
Rafael Diniz
On 8/2/19 7:05 PM, Sukchan Lee wrote:
Hi Rafael,
In the NextEPC, there are two ways to specify peers. 'addr' sets the
IP address, and 'name' sets the hostname.
So, if your network is configured to look up the VLR as a hostname,
you can use 'name'.
'port' was just made for testing. If you want to use a different port
without using standard 29118, you can put 'port' number.
By the way, I've changed how to configure CS Fallback & SMS as below.
# o Single MSC/VLR(127.0.0.2)
sgsap:
addr: 127.0.0.2
map:
tai:
plmn_id:
mcc: 001
mnc: 01
tac: 4130
lai:
plmn_id:
mcc: 001
mnc: 01
lac: 43690
map:
tai:
plmn_id:
mcc: 002
mnc: 02
tac: 4132
lai:
plmn_id:
mcc: 002
mnc: 02
lac: 43692
# o Multiple MSC/VLR
sgsap:
- addr: 127.0.0.2
port: 29119
map:
tai:
plmn_id:
mcc: 001
mnc: 01
tac: 4131
lai:
plmn_id:
mcc: 001
mnc: 01
lac: 43691
map:
tai:
plmn_id:
mcc: 002
mnc: 02
tac: 4132
lai:
plmn_id:
mcc: 002
mnc: 02
lac: 43692
- addr
- 127.0.0.3
- fe80::2%lo
map:
tai:
plmn_id:
mcc: 001
mnc: 01
tac: 4132
lai:
plmn_id:
mcc: 002
mnc: 02
lac: 43692
- name: msc.open5gs.org <http://msc.open5gs.org>
map:
tai:
plmn_id:
mcc: 001
mnc: 01
tac: 4133
lai:
plmn_id:
mcc: 002
mnc: 02
lac: 43693
Thanks a lot!
Best Regards,
Sukchan
On Sat, Aug 3, 2019 at 6:45 AM Rafael Diniz <rafael(a)rhizomatica.org
<mailto:rafael@rhizomatica.org>> wrote:
Hi all,
Just a small question - what is the meaning of the "name" field in the
sgsap configuration?
Thanks,
Rafael Diniz
On 7/19/19 5:51 PM, Rafael Diniz wrote:
Obrigado Romeu!
On 7/19/19 4:58 PM, Romeu Medeiros wrote:
> Hello Rafael
>
> I just configure the NextEPC to connect via SGS to OSMO-MSC,
like this:
>
> sgsap:
> addr: 127.0.0.1
> port: 29118
> name: vlr.example.net <http://vlr.example.net>
<http://vlr.example.net>
> tai:
> plmn_id:
> mcc: 724
> mnc: 21
> tac: 12345
> lai:
> plmn_id:
> mcc: 724
> mnc: 4
> lac: 51544
>
> And the configuration in the MSC:
>
> sgs
> local-port 29118
> local-ip 0.0.0.0
> vlr-name vlr.example.net <http://vlr.example.net>
<http://vlr.example.net>
>
> And configure the IMSI in the Osmo-HLR and NextEPC-HSS
>
> If you need more help tell me.
>
>
> Thanks
>
> Romeu Medeiros
>
>
> And
>
> On Fri, Jul 19, 2019 at 1:31 PM Rafael Diniz
<rafael(a)rhizomatica.org
<mailto:rafael@rhizomatica.org>
> <mailto:rafael@rhizomatica.org
<mailto:rafael@rhizomatica.org>>> wrote:
>
> Hi all,
>
> I'd also like to test SMS and CSFB in LTE. I have some
experience
with
> the Osmocom GSM stack, but not much with
the NextEPC LTE.
Could you
> point me which fields should I set in the
configuration files?
>
> Thanks,
> Rafael Diniz
>
> On 7/13/19 6:35 PM, Romeu Medeiros wrote:
> > Hello Sukchan and friends.
> >
> > I'm trying to use the CSFB in test lab, and every time that
> nextepc send
> > the UEContextModificationRequest, the UE respond with an
> > UEContextModificationFaliure [
Protocol-cause=semantic-error ].
> >
> > image.png
> >
> > I'm looking why I'm getting this. Someone have any idea?
> >
> > Thanks
> >
> > Romeu Medeiros
> >
> > On Thu, Jul 11, 2019 at 12:15 PM Sukchan Lee
<acetcom(a)gmail.com <mailto:acetcom@gmail.com>
> <mailto:acetcom@gmail.com
<mailto:acetcom@gmail.com>>
> > <mailto:acetcom@gmail.com <mailto:acetcom@gmail.com>
<mailto:acetcom@gmail.com <mailto:acetcom@gmail.com>>>> wrote:
> >
> > Dear Osmocom & NextEPC Community,
> >
> > Today I've added CS Fallback and released NextEPC v0.5.0
> >
> > So, I'd just like to test this part with Osmocom
project,
but it
> > seems to be a difficult task.
The reason is why I
have little
> > knowledge about 2G/3G.
Nevertheless, I will try to do it
> >
> > BTW, I don't know if there is anyone who wants to
integrate
> this big
> > thing.
> > Even though I'm not sure if this will help, but let me
> introduce the
> > configuration of the NextEPC.
> >
> > To use SGsAP, change the mme.conf as follows:
> >
> > #
> > # <sgsap>
> > #
> > # o Single MSC/VLR
> > # sgsap:
> > # addr: 127.0.0.2
> > # plmn_id:
> > # mcc: 001
> > # mnc: 01
> > # tac: 4130
> > # lac: 43690
> > #
> > # o Multiple MSC/VLR
> > # sgsap:
> > # - addr: 127.0.0.2
> > # plmn_id:
> > # mcc: 001
> > # mnc: 01
> > # tac: 4131
> > # lac: 43692
> > # - addr
> > # - 127.0.0.3
> > # - fe80::2%lo0
> > # plmn_id:
> > # mcc: 001
> > # mnc: 01
> > # tac: 4132
> > # lac: 43692
> > # - name: msc.open5gs.org
<http://msc.open5gs.org>
<http://msc.open5gs.org>
> <http://msc.open5gs.org>
> > # plmn_id:
> > # mcc: 001
> > # mnc: 01
> > # tac: 4133
> > # lac: 43693
> > #
> >
> > FYI, I also attach the pcap that I run with nextepc
simulator
as
below.
$ ./tests/testcsfb
mo-idle-test : SUCCESS
mt-idle-test : SUCCESS
mo-active-test : SUCCESS
mt-active-test : SUCCESS
All tests passed.
Feel free to raise any questions about this things.
Best Regards,
Sukchan
2018
days inactive
2043
days old
13 comments
5 participants
participants (5)
-
Harald Welte -
Rafael Diniz -
Romeu Medeiros -
Sukchan Lee -
이석찬