From acetcom at gmail.com Tue Mar 3 07:05:18 2020 From: acetcom at gmail.com (=?UTF-8?B?7J207ISd7LCs?=) Date: Tue, 3 Mar 2020 16:05:18 +0900 Subject: Get all debug info possible In-Reply-To: <24268fa2-91d4-1e08-f8f5-ad798c1e7f7d@rhizomatica.org> References: <9a8d778f-9ea0-774d-81c0-487a6311e4bf@rhizomatica.org> <445C6E6E-F4BC-491C-BBF7-5D2C186DC3C9@cs.washington.edu> <24268fa2-91d4-1e08-f8f5-ad798c1e7f7d@rhizomatica.org> Message-ID: Hi rafael, See as below. (Referred from https://open5gs.org/open5gs/docs/guide/04-troubleshooting/) Thanks! You can modify the configuration file to record more logs. diff -u /etc/open5gs/mme.yaml.old /etc/open5gs/mme.yaml--- mme.yaml.old 2018-04-15 18:28:31.000000000 +0900+++ mme.yaml 2018-04-15 19:53:10.000000000 +0900@@ -2,6 +2,7 @@ logger: file: /var/log/open5gs/mme.log+ level: debug parameter: After changing conf files, please restart Open5GS daemons. $ sudo systemctl restart open5gs-mmed$ sudo systemctl restart open5gs-sgwd 2020? 2? 29? (?) ?? 2:53, Rafael Diniz ?? ??: > Thanks Spencer! > > I'm willing if I should use the "-e", "-m", "-d" and "-t" in the systemd > open5gs-* service files for a more verbose output. > > juba > > On 2/28/20 1:40 PM, Spencer Sevilla wrote: > > Hi Juba! > > > > If open5gs is running as a systemd service (the default if you installed > with apt-get) you should use journalctl. The relevant systemd service names > are open5gs-hssd, open5gs-mmed, open5gs-sgwd, open5gs-pgwd, and > open5gs-pcrfd. If you built them from source, they will output all > information in the terminal window you?re running them in, and will also > write to log files located in {installation_directory}/var/log/open5gs/. > > > > To see all the journalctl logs in one terminal: ?sudo journalctl -f -u > open5gs-hssd -u open5gs-mmed -u open5gs-pgwd -u open5gs-sgwd -u > open5gs-pcrfd" > > > >> On Feb 28, 2020, at 06:58, Rafael Diniz wrote: > >> > >> Hi all, > >> > >> Which cmd line should I use to get all the debug information possible > >> from the EPC components? > >> > >> Thanks, > >> Rafael Diniz > >> > >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafael at rhizomatica.org Fri Mar 6 13:36:38 2020 From: rafael at rhizomatica.org (Rafael Diniz) Date: Fri, 6 Mar 2020 10:36:38 -0300 Subject: Get all debug info possible In-Reply-To: References: <9a8d778f-9ea0-774d-81c0-487a6311e4bf@rhizomatica.org> <445C6E6E-F4BC-491C-BBF7-5D2C186DC3C9@cs.washington.edu> <24268fa2-91d4-1e08-f8f5-ad798c1e7f7d@rhizomatica.org> Message-ID: <021b3079-9728-13ab-cbce-ff04a435e6e3@rhizomatica.org> Thanks, that is what I wanted! Rafael On 3/3/20 4:05 AM, ??? wrote: > Hi rafael, > > See as below. (Referred from? > https://open5gs.org/open5gs/docs/guide/04-troubleshooting/) > > Thanks! > > > You can modify the configuration file to record more logs. > > |diff -u /etc/open5gs/mme.yaml.old /etc/open5gs/mme.yaml --- > mme.yaml.old 2018-04-15 18:28:31.000000000 +0900 +++ mme.yaml > 2018-04-15 19:53:10.000000000 +0900 @@ -2,6 +2,7 @@ logger: file: > /var/log/open5gs/mme.log + level: debug parameter: | > > After changing conf files, please restart Open5GS daemons. > > |$ sudo systemctl restart open5gs-mmed $ sudo systemctl restart > open5gs-sgwd | > > > > 2020? 2? 29? (?) ?? 2:53, Rafael Diniz >?? ??: > > Thanks Spencer! > > I'm willing if I should use the "-e", "-m", "-d" and "-t" in the > systemd > open5gs-* service files for a more verbose output. > > juba > > On 2/28/20 1:40 PM, Spencer Sevilla wrote: > > Hi Juba! > > > > If open5gs is running as a systemd service (the default if you > installed with apt-get) you should use journalctl. The relevant > systemd service names are open5gs-hssd, open5gs-mmed, > open5gs-sgwd, open5gs-pgwd, and open5gs-pcrfd. If you built them > from source, they will output all information in the terminal > window you?re running them in, and will also write to log files > located in {installation_directory}/var/log/open5gs/. > > > > To see all the journalctl logs in one terminal: ?sudo journalctl > -f -u open5gs-hssd -u open5gs-mmed -u open5gs-pgwd -u open5gs-sgwd > -u open5gs-pcrfd" > > > >> On Feb 28, 2020, at 06:58, Rafael Diniz > wrote: > >> > >> Hi all, > >> > >> Which cmd line should I use to get all the debug information > possible > >> from the EPC components? > >> > >> Thanks, > >> Rafael Diniz > >> > >> > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From david at ispsupplies.com Fri Mar 6 13:58:45 2020 From: david at ispsupplies.com (david at ispsupplies.com) Date: Fri, 6 Mar 2020 08:58:45 -0500 Subject: PCRF Message-ID: <05c301d5f3bf$5b26a4e0$1173eea0$@ispsupplies.com> Does anyone have any experience or knowledge on using Open5gs with an external MVNO? David Peterson Senior Engineer 855-947-7776 ext. 9214 d 979-314-1305 c 419-706-7355 https://www.ispsupplies.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 19638 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 701 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 420 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 444 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 441 bytes Desc: not available URL: From sevilla at cs.washington.edu Fri Mar 6 18:49:52 2020 From: sevilla at cs.washington.edu (Spencer Sevilla) Date: Fri, 6 Mar 2020 10:49:52 -0800 Subject: PCRF In-Reply-To: <05c301d5f3bf$5b26a4e0$1173eea0$@ispsupplies.com> References: <05c301d5f3bf$5b26a4e0$1173eea0$@ispsupplies.com> Message-ID: <9D0581E6-1922-455C-89AA-1CF76079738F@cs.washington.edu> I don?t, but I would love to hear what you find out. Also, to my understanding right now the PCRF is a bit of a stub process and simply says ?OK? to all requests right now. > On Mar 6, 2020, at 05:58, david at ispsupplies.com wrote: > > Does anyone have any experience or knowledge on using Open5gs with an external MVNO? > > > > David Peterson > Senior Engineer > 855-947-7776 ext. 9214 > d 979-314-1305 > c 419-706-7355 > https://www.ispsupplies.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From medeiros at medeiros.eng.br Tue Mar 10 23:15:01 2020 From: medeiros at medeiros.eng.br (Romeu Medeiros) Date: Tue, 10 Mar 2020 20:15:01 -0300 Subject: Fwd: Open5GS Traffic Accounting In-Reply-To: References: Message-ID: Hello all and @Sukchan Lee , I was thinking about one way to generate traffic accounting from the LTE users of the Open5GS. I'm rearching something using the iptables (in Linux), in this link we can check a way to generate some traffic account in the linux: https://catonmat.net/traffic-accounting-with-iptables I'm thinking about writing a code, where the PGW adds a new line in iptables with the IP/IPv6 address (TRAFFIC_ACCT_IN and TRAFFIC_ACCT_OUT) when a new session is added and remove the same line when the session is ended, with this the counter will restart, being able to use an external program to get this information about the traffic sent and received by a given user. The bad from this idea is that this code only will work correctly in a Linux box. Does anyone have any other suggestions? Thanks Romeu Medeiros -------------- next part -------------- An HTML attachment was scrubbed... URL: From david at ispsupplies.com Tue Mar 10 23:56:06 2020 From: david at ispsupplies.com (david at ispsupplies.com) Date: Tue, 10 Mar 2020 19:56:06 -0400 Subject: Open5GS Traffic Accounting In-Reply-To: References: Message-ID: <0f4301d5f737$77c99820$675cc860$@ispsupplies.com> Freediameter should be able to provide accounting so long as the ENB supports it. David Peterson Senior Engineer 855-947-7776 ext. 9214 c 419-706-7355 d 979-314-1305 https://www.ispsupplies.com From: nextepc On Behalf Of Romeu Medeiros Sent: Tuesday, March 10, 2020 7:15 PM To: nextepc at lists.osmocom.org Subject: Fwd: Open5GS Traffic Accounting Hello all and @Sukchan Lee , I was thinking about one way to generate traffic accounting from the LTE users of the Open5GS. I'm rearching something using the iptables (in Linux), in this link we can check a way to generate some traffic account in the linux: https://catonmat.net/traffic-accounting-with-iptables I'm thinking about writing a code, where the PGW adds a new line in iptables with the IP/IPv6 address (TRAFFIC_ACCT_IN and TRAFFIC_ACCT_OUT) when a new session is added and remove the same line when the session is ended, with this the counter will restart, being able to use an external program to get this information about the traffic sent and received by a given user. The bad from this idea is that this code only will work correctly in a Linux box. Does anyone have any other suggestions? Thanks Romeu Medeiros -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 19638 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 701 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 420 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 444 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 441 bytes Desc: not available URL: From david at ispsupplies.com Wed Mar 11 16:26:03 2020 From: david at ispsupplies.com (david at ispsupplies.com) Date: Wed, 11 Mar 2020 12:26:03 -0400 Subject: Open5GS Traffic Accounting In-Reply-To: <20200311155313.GF1762325@nataraja> References: <0f4301d5f737$77c99820$675cc860$@ispsupplies.com> <20200311155313.GF1762325@nataraja> Message-ID: <10ac01d5f7c1$c360d6b0$4a228410$@ispsupplies.com> Sorry yeah I meant the EPC. I am not sure if the Open5GS software supports it but Freediameter would be the Accounting portion in AAA from what I can tell. David Peterson Senior Engineer 855-947-7776 ext. 9214 c 419-706-7355 d 979-314-1305 https://www.ispsupplies.com??? -----Original Message----- From: Harald Welte Sent: Wednesday, March 11, 2020 11:53 AM To: david at ispsupplies.com Cc: 'Romeu Medeiros' ; nextepc at lists.osmocom.org Subject: Re: Open5GS Traffic Accounting Hi David, On Tue, Mar 10, 2020 at 07:56:06PM -0400, david at ispsupplies.com wrote: > Freediameter should be able to provide accounting so long as the ENB supports it. in which way is the eNB involved in traffic accounting in LTE? Normally, AFAICT, accounting is implemented within the P-GW, potentially interacting via Radios/Diameter or some other protocol with some external entity that decides whether or not there is credit/budget remaining or not. If not, the PGW would stop firwarding packets of the related session/subscriber. -- - Harald Welte https://linkprotect.cudasvc.com/url?a=http%3a%2f%2flaforge.gnumonks.org%2f&c =E,1,yb6SFWcoxXKtp0qClHpv4V936cQS_cFUx9dFgqORnwJ6yRCOhax7GulxJjjPLVsGkCe2ioB ew6hlBJnFYR1mBgD0-WojRnKxjbM4dQK9xQ,,&typo=1 ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From sevilla at cs.washington.edu Wed Mar 11 16:39:37 2020 From: sevilla at cs.washington.edu (Spencer Sevilla) Date: Wed, 11 Mar 2020 09:39:37 -0700 Subject: Open5GS Traffic Accounting In-Reply-To: <10ac01d5f7c1$c360d6b0$4a228410$@ispsupplies.com> References: <0f4301d5f737$77c99820$675cc860$@ispsupplies.com> <20200311155313.GF1762325@nataraja> <10ac01d5f7c1$c360d6b0$4a228410$@ispsupplies.com> Message-ID: +1 to Harald. Doing traffic accounting at the PGW and then reporting these statistics over Diameter is probably the most architecturally correct way to do this. I'm definitely a fan of using IPTables for this kind of stuff, since it?s all just packets anyways. For our networks, we wrote a completely separate tool called haulage (https://github.com/uw-ictd/haulage) that uses IPTables and does something very similar. Basically logs packets that are forwarded from the virtual interface, draws them down against a user?s prepaid quota, and cuts them off when they hit zero. We wrote this as a separate app (in go) mainly to keep things simpler and let us move faster. Spencer > On Mar 11, 2020, at 09:26, wrote: > > Sorry yeah I meant the EPC. I am not sure if the Open5GS software supports > it but Freediameter would be the Accounting portion in AAA from what I can > tell. > > > > David Peterson > Senior Engineer > 855-947-7776 ext. 9214 > c 419-706-7355 > d 979-314-1305 > https://www.ispsupplies.com > > > -----Original Message----- > From: Harald Welte > Sent: Wednesday, March 11, 2020 11:53 AM > To: david at ispsupplies.com > Cc: 'Romeu Medeiros' ; nextepc at lists.osmocom.org > Subject: Re: Open5GS Traffic Accounting > > Hi David, > > On Tue, Mar 10, 2020 at 07:56:06PM -0400, david at ispsupplies.com wrote: >> Freediameter should be able to provide accounting so long as the ENB > supports it. > > in which way is the eNB involved in traffic accounting in LTE? > > Normally, AFAICT, accounting is implemented within the P-GW, potentially > interacting via Radios/Diameter or some other protocol with some external > entity that decides whether or not there is credit/budget remaining or not. > If not, the PGW would stop firwarding packets of the related > session/subscriber. > > -- > - Harald Welte > https://linkprotect.cudasvc.com/url?a=http%3a%2f%2flaforge.gnumonks.org%2f&c > =E,1,yb6SFWcoxXKtp0qClHpv4V936cQS_cFUx9dFgqORnwJ6yRCOhax7GulxJjjPLVsGkCe2ioB > ew6hlBJnFYR1mBgD0-WojRnKxjbM4dQK9xQ,,&typo=1 > ============================================================================ > "Privacy in residential applications is a desirable marketing option." > (ETSI EN 300 175-7 Ch. A6) > From medeiros at medeiros.eng.br Wed Mar 11 17:05:59 2020 From: medeiros at medeiros.eng.br (Romeu Medeiros) Date: Wed, 11 Mar 2020 14:05:59 -0300 Subject: Open5GS Traffic Accounting In-Reply-To: References: <0f4301d5f737$77c99820$675cc860$@ispsupplies.com> <20200311155313.GF1762325@nataraja> <10ac01d5f7c1$c360d6b0$4a228410$@ispsupplies.com> Message-ID: Hello Spencer, Harald and all. I really appreciated all infos, this saves me a lot of time! Spencer, I'm seeing your tool, I think that is exactly like I need. My environment is small (10 endbs). I will try to use your tool here, In our github page you inform that the code is migrating to open5gs. It's working with the open5gs? Thanks Romeu Medeiros On Wed, Mar 11, 2020 at 1:39 PM Spencer Sevilla wrote: > +1 to Harald. Doing traffic accounting at the PGW and then reporting these > statistics over Diameter is probably the most architecturally correct way > to do this. I'm definitely a fan of using IPTables for this kind of stuff, > since it?s all just packets anyways. > > For our networks, we wrote a completely separate tool called haulage ( > https://github.com/uw-ictd/haulage) that uses IPTables and does something > very similar. Basically logs packets that are forwarded from the virtual > interface, draws them down against a user?s prepaid quota, and cuts them > off when they hit zero. We wrote this as a separate app (in go) mainly to > keep things simpler and let us move faster. > > Spencer > > > On Mar 11, 2020, at 09:26, < > david at ispsupplies.com> wrote: > > > > Sorry yeah I meant the EPC. I am not sure if the Open5GS software > supports > > it but Freediameter would be the Accounting portion in AAA from what I > can > > tell. > > > > > > > > David Peterson > > Senior Engineer > > 855-947-7776 ext. 9214 > > c 419-706-7355 > > d 979-314-1305 > > https://www.ispsupplies.com > > > > > > -----Original Message----- > > From: Harald Welte > > Sent: Wednesday, March 11, 2020 11:53 AM > > To: david at ispsupplies.com > > Cc: 'Romeu Medeiros' ; > nextepc at lists.osmocom.org > > Subject: Re: Open5GS Traffic Accounting > > > > Hi David, > > > > On Tue, Mar 10, 2020 at 07:56:06PM -0400, david at ispsupplies.com wrote: > >> Freediameter should be able to provide accounting so long as the ENB > > supports it. > > > > in which way is the eNB involved in traffic accounting in LTE? > > > > Normally, AFAICT, accounting is implemented within the P-GW, potentially > > interacting via Radios/Diameter or some other protocol with some external > > entity that decides whether or not there is credit/budget remaining or > not. > > If not, the PGW would stop firwarding packets of the related > > session/subscriber. > > > > -- > > - Harald Welte > > > https://linkprotect.cudasvc.com/url?a=http%3a%2f%2flaforge.gnumonks.org%2f&c > > > =E,1,yb6SFWcoxXKtp0qClHpv4V936cQS_cFUx9dFgqORnwJ6yRCOhax7GulxJjjPLVsGkCe2ioB > > ew6hlBJnFYR1mBgD0-WojRnKxjbM4dQK9xQ,,&typo=1 > > > ============================================================================ > > "Privacy in residential applications is a desirable marketing option." > > (ETSI EN 300 175-7 Ch. > A6) > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sevilla at cs.washington.edu Wed Mar 11 17:22:09 2020 From: sevilla at cs.washington.edu (Spencer Sevilla) Date: Wed, 11 Mar 2020 10:22:09 -0700 Subject: Open5GS Traffic Accounting In-Reply-To: References: <0f4301d5f737$77c99820$675cc860$@ispsupplies.com> <20200311155313.GF1762325@nataraja> <10ac01d5f7c1$c360d6b0$4a228410$@ispsupplies.com> Message-ID: Our migration is *almost* done. We had to rewrite a lot of database code because we used to integrate with OAI, but now have moved our systems over to open5gs. I?ll respond back to this thread once we?ve finally migrated everything (should be by the end of the week). > On Mar 11, 2020, at 10:05, Romeu Medeiros wrote: > > Hello Spencer, Harald and all. > > > I really appreciated all infos, this saves me a lot of time! > > Spencer, I'm seeing your tool, I think that is exactly like I need. My environment is small (10 endbs). > > I will try to use your tool here, In our github page you inform that the code is migrating to open5gs. It's working with the open5gs? > > Thanks > > Romeu Medeiros > > On Wed, Mar 11, 2020 at 1:39 PM Spencer Sevilla > wrote: > +1 to Harald. Doing traffic accounting at the PGW and then reporting these statistics over Diameter is probably the most architecturally correct way to do this. I'm definitely a fan of using IPTables for this kind of stuff, since it?s all just packets anyways. > > For our networks, we wrote a completely separate tool called haulage (https://github.com/uw-ictd/haulage ) that uses IPTables and does something very similar. Basically logs packets that are forwarded from the virtual interface, draws them down against a user?s prepaid quota, and cuts them off when they hit zero. We wrote this as a separate app (in go) mainly to keep things simpler and let us move faster. > > Spencer > > > On Mar 11, 2020, at 09:26, > > wrote: > > > > Sorry yeah I meant the EPC. I am not sure if the Open5GS software supports > > it but Freediameter would be the Accounting portion in AAA from what I can > > tell. > > > > > > > > David Peterson > > Senior Engineer > > 855-947-7776 ext. 9214 > > c 419-706-7355 > > d 979-314-1305 > > https://www.ispsupplies.com > > > > > > -----Original Message----- > > From: Harald Welte > > > Sent: Wednesday, March 11, 2020 11:53 AM > > To: david at ispsupplies.com > > Cc: 'Romeu Medeiros' >; nextepc at lists.osmocom.org > > Subject: Re: Open5GS Traffic Accounting > > > > Hi David, > > > > On Tue, Mar 10, 2020 at 07:56:06PM -0400, david at ispsupplies.com wrote: > >> Freediameter should be able to provide accounting so long as the ENB > > supports it. > > > > in which way is the eNB involved in traffic accounting in LTE? > > > > Normally, AFAICT, accounting is implemented within the P-GW, potentially > > interacting via Radios/Diameter or some other protocol with some external > > entity that decides whether or not there is credit/budget remaining or not. > > If not, the PGW would stop firwarding packets of the related > > session/subscriber. > > > > -- > > - Harald Welte > > > https://linkprotect.cudasvc.com/url?a=http%3a%2f%2flaforge.gnumonks.org%2f&c > > =E,1,yb6SFWcoxXKtp0qClHpv4V936cQS_cFUx9dFgqORnwJ6yRCOhax7GulxJjjPLVsGkCe2ioB > > ew6hlBJnFYR1mBgD0-WojRnKxjbM4dQK9xQ,,&typo=1 > > ============================================================================ > > "Privacy in residential applications is a desirable marketing option." > > (ETSI EN 300 175-7 Ch. A6) > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at osmocom.org Wed Mar 11 15:53:13 2020 From: laforge at osmocom.org (Harald Welte) Date: Wed, 11 Mar 2020 16:53:13 +0100 Subject: Open5GS Traffic Accounting In-Reply-To: <0f4301d5f737$77c99820$675cc860$@ispsupplies.com> References: <0f4301d5f737$77c99820$675cc860$@ispsupplies.com> Message-ID: <20200311155313.GF1762325@nataraja> Hi David, On Tue, Mar 10, 2020 at 07:56:06PM -0400, david at ispsupplies.com wrote: > Freediameter should be able to provide accounting so long as the ENB supports it. in which way is the eNB involved in traffic accounting in LTE? Normally, AFAICT, accounting is implemented within the P-GW, potentially interacting via Radios/Diameter or some other protocol with some external entity that decides whether or not there is credit/budget remaining or not. If not, the PGW would stop firwarding packets of the related session/subscriber. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From laforge at osmocom.org Wed Mar 11 16:00:03 2020 From: laforge at osmocom.org (Harald Welte) Date: Wed, 11 Mar 2020 17:00:03 +0100 Subject: Fwd: Open5GS Traffic Accounting In-Reply-To: References: Message-ID: <20200311160003.GG1762325@nataraja> Dear Romeo, On Tue, Mar 10, 2020 at 08:15:01PM -0300, Romeu Medeiros wrote: > I was thinking about one way to generate traffic accounting from the LTE > users of the Open5GS. great! > I'm rearching something using the iptables (in Linux), Please don't. iptables is mroe than 20 years old by now, and for any new development you should consider using nftables. It is much more powerful, efficient nad also (contrary to iptables) has nice library API by which rules can be installed from programs without fork+exec of an "iptables" binary with command line arguments. In Debian 10 (and presumably other distributions) nftables is alredy the default. Based on the fact that there's an iptables compatibility layer on top, you may not even know that. The fundamental question is whether or not you want to do this in the external packet filter of the OS or inside the PGW itself. I would argue for the latter, because: > The bad from this idea is that this code only will work correctly in a > Linux box. that, and also because the open5gs PGW already contains a (stripped down) BSD firewall code base if you want to do filtering or the like. In general, the question is what kind of throughput in terms of bandwidth and pps you are looking for. Implementing GTP-U encap/decap, accounting, filtering etc. inside a userspace process behind RAW sockets and a tun device is not going to scale very far. For a single-eNB lab setup: Fine. But do you need accounting there? For anything bigger, I would consider looking at other P-GW implementations out there, such as ergw or the OMEC implementation. They both do CUPS (control / user plane split) and have DPDK and/or VPP accelerated user plane implementations. Given they talk standard GTP, you should be able to inter-operate them with open5gs. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From david at ispsupplies.com Tue Mar 17 22:39:24 2020 From: david at ispsupplies.com (david at ispsupplies.com) Date: Tue, 17 Mar 2020 18:39:24 -0400 Subject: Reject message Message-ID: <010d01d5fcac$ea022040$be0660c0$@ispsupplies.com> Does anyone know why I am getting this reject reason for network entry on a UE? 03/17 16:56:55.026: [mme] DEBUG: [EMM] Authentication request (../src/mme/nas-path.c:180) 03/17 16:56:55.026: [mme] DEBUG: IMSI[311980000033212] (../src/mme/nas-path.c:181) 03/17 16:56:55.026: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.026: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.026: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.189: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.189: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.189: [mme] DEBUG: [MME] Uplink NAS transport (../src/mme/s1ap-handler.c:330) 03/17 16:56:55.189: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:347) 03/17 16:56:55.189: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:354) 03/17 16:56:55.189: [mme] DEBUG: mme_state_operational(): MME_EVT_EMM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.189: [emm] DEBUG: emm_state_authentication(): MME_EVT_EMM_MESSAGE (../src/mme/emm-sm.c:488) 03/17 16:56:55.189: [emm] DEBUG: [EMM] Authentication response (../src/mme/emm-sm.c:512) 03/17 16:56:55.189: [emm] DEBUG: IMSI[311980000033212] (../src/mme/emm-sm.c:513) 03/17 16:56:55.189: [emm] DEBUG: emm_state_authentication(): EXIT (../src/mme/emm-sm.c:488) 03/17 16:56:55.189: [emm] DEBUG: emm_state_security_mode(): ENTRY (../src/mme/emm-sm.c:649) 03/17 16:56:55.189: [mme] DEBUG: [EMM] Security mode command (../src/mme/nas-path.c:207) 03/17 16:56:55.189: [mme] DEBUG: IMSI[311980000033212] (../src/mme/nas-path.c:208) 03/17 16:56:55.190: [emm] DEBUG: Replayed UE SEC[LEN:2 EEA:0xe0 EIA:0xe0 UEA:0x0 UIA:0x0 GEA:0x0] (../src/mme/emm-build.c:287) 03/17 16:56:55.190: [emm] DEBUG: Selected[Integrity:0x1 Encrypt:0x0] (../src/mme/emm-build.c:289) 03/17 16:56:55.190: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.190: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.190: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.229: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.230: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.230: [mme] DEBUG: [MME] Uplink NAS transport (../src/mme/s1ap-handler.c:330) 03/17 16:56:55.230: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:347) 03/17 16:56:55.230: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:354) 03/17 16:56:55.230: [mme] DEBUG: mme_state_operational(): MME_EVT_EMM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.230: [emm] DEBUG: emm_state_security_mode(): MME_EVT_EMM_MESSAGE (../src/mme/emm-sm.c:649) 03/17 16:56:55.230: [emm] DEBUG: [EMM] Security mode complete (../src/mme/emm-sm.c:676) 03/17 16:56:55.230: [emm] DEBUG: IMSI[311980000033212] (../src/mme/emm-sm.c:677) 03/17 16:56:55.230: [mme] DEBUG: [MME] Update-Location-Request (../src/mme/mme-fd-path.c:444) 03/17 16:56:55.231: [emm] DEBUG: emm_state_security_mode(): EXIT (../src/mme/emm-sm.c:649) 03/17 16:56:55.231: [emm] DEBUG: emm_state_initial_context_setup(): ENTRY (../src/mme/emm-sm.c:817) 03/17 16:56:55.234: [mme] DEBUG: [MME] Update-Location-Answer (../src/mme/mme-fd-path.c:610) 03/17 16:56:55.234: [mme] DEBUG: Result Code: 2001 (../src/mme/mme-fd-path.c:651) 03/17 16:56:55.234: [mme] DEBUG: From 'hss.localdomain' (../src/mme/mme-fd-path.c:680) 03/17 16:56:55.234: [mme] DEBUG: ('localdomain') (../src/mme/mme-fd-path.c:693) 03/17 16:56:55.234: [mme] DEBUG: mme_state_operational(): MME_EVT_S6A_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.234: [mme] DEBUG: mme_state_operational(): MME_EVT_ESM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.234: [mme] DEBUG: mme_bearer_find_or_add_by_message() [PTI:8, EBI:0] (../src/mme/mme-context.c:2847) 03/17 16:56:55.234: [esm] DEBUG: esm_state_initial(): ENTRY (../src/mme/esm-sm.c:38) 03/17 16:56:55.234: [esm] DEBUG: esm_state_inactive(): ENTRY (../src/mme/esm-sm.c:61) 03/17 16:56:55.234: [mme] INFO: Added a session. Number of sessions is now 1 (../src/mme/mme-context.c:79) 03/17 16:56:55.234: [esm] DEBUG: esm_state_inactive(): MME_EVT_ESM_MESSAGE (../src/mme/esm-sm.c:61) 03/17 16:56:55.234: [esm] DEBUG: [ESM] PDN Connectivity request (../src/mme/esm-sm.c:82) 03/17 16:56:55.234: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] (../src/mme/esm-sm.c:84) 03/17 16:56:55.234: [esm] DEBUG: EIT(ESM information transfer)[1] (../src/mme/esm-handler.c:59) 03/17 16:56:55.234: [esm] DEBUG: [ESM] ESM information request (../src/mme/esm-build.c:75) 03/17 16:56:55.234: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] (../src/mme/esm-build.c:77) 03/17 16:56:55.235: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.235: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.235: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.269: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.270: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.270: [mme] DEBUG: [MME] Uplink NAS transport (../src/mme/s1ap-handler.c:330) 03/17 16:56:55.270: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:347) 03/17 16:56:55.270: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:354) 03/17 16:56:55.270: [mme] DEBUG: mme_state_operational(): MME_EVT_ESM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.270: [mme] DEBUG: mme_bearer_find_or_add_by_message() [PTI:8, EBI:0] (../src/mme/mme-context.c:2847) 03/17 16:56:55.270: [esm] DEBUG: esm_state_inactive(): MME_EVT_ESM_MESSAGE (../src/mme/esm-sm.c:61) 03/17 16:56:55.270: [esm] DEBUG: [ESM] ESM information response (../src/mme/esm-sm.c:93) 03/17 16:56:55.270: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] (../src/mme/esm-sm.c:95) 03/17 16:56:55.270: [mme] DEBUG: [EMM] Attach reject (../src/mme/nas-path.c:134) 03/17 16:56:55.270: [mme] DEBUG: IMSI[311980000033212] Cause[8] (../src/mme/nas-path.c:135) 03/17 16:56:55.270: [esm] DEBUG: [ESM] PDN connectivity reject (../src/mme/esm-build.c:39) 03/17 16:56:55.270: [esm] DEBUG: IMSI[311980000033212] PTI[8] Cause[27] (../src/mme/esm-build.c:41) 03/17 16:56:55.271: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.271: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.271: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.271: [esm] DEBUG: esm_state_inactive(): EXIT (../src/mme/esm-sm.c:61) 03/17 16:56:55.271: [esm] DEBUG: esm_state_exception(): ENTRY (../src/mme/esm-sm.c:345) 03/17 16:56:55.271: [mme] DEBUG: [MME] UE Context release command (../src/mme/s1ap-path.c:285) 03/17 16:56:55.271: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-path.c:287) 03/17 16:56:55.271: [mme] DEBUG: Group[3] Cause[0] Action[3] Delay[0] (../src/mme/s1ap-path.c:306) 03/17 16:56:55.271: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.275: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.275: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.275: [mme] DEBUG: [MME] UE Context release complete (../src/mme/s1ap-handler.c:919) 03/17 16:56:55.276: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:933) 03/17 16:56:55.276: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:950) 03/17 16:56:55.276: [mme] DEBUG: Action: UE context remove() (../src/mme/s1ap-handler.c:963) 03/17 16:56:55.276: [mme] INFO: Removed a UE. Number of UEs is now 0 (../src/mme/mme-context.c:63) 03/17 16:56:55.276: [emm] DEBUG: emm_state_initial_context_setup(): EXIT -------------- next part -------------- An HTML attachment was scrubbed... URL: From acetcom at gmail.com Fri Mar 27 15:56:44 2020 From: acetcom at gmail.com (Sukchan Lee) Date: Fri, 27 Mar 2020 11:56:44 -0400 Subject: Reject message In-Reply-To: <010d01d5fcac$ea022040$be0660c0$@ispsupplies.com> References: <010d01d5fcac$ea022040$be0660c0$@ispsupplies.com> Message-ID: Hi david, If pcap is provided, it is more easier to analyze your problem. BTW, from your log, I've found PDN connectivity reject with ESM_CAUSE:27. It means that UE APN is unknown in HSS. So, you need to match APN name between UE and HSS. Thanks and regards, Sukchan On Tue, Mar 17, 2020 at 6:47 PM wrote: > Does anyone know why I am getting this reject reason for network entry on > a UE? > > > > 03/17 16:56:55.026: [mme] DEBUG: [EMM] Authentication request > (../src/mme/nas-path.c:180) > > 03/17 16:56:55.026: [mme] DEBUG: IMSI[311980000033212] > (../src/mme/nas-path.c:181) > > 03/17 16:56:55.026: [mme] DEBUG: [MME] DownlinkNASTransport > (../src/mme/s1ap-build.c:186) > > 03/17 16:56:55.026: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-build.c:231) > > 03/17 16:56:55.026: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-path.c:79) > > 03/17 16:56:55.189: [mme] DEBUG: mme_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.189: [mme] DEBUG: s1ap_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/s1ap-sm.c:60) > > 03/17 16:56:55.189: [mme] DEBUG: [MME] Uplink NAS transport > (../src/mme/s1ap-handler.c:330) > > 03/17 16:56:55.189: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-handler.c:347) > > 03/17 16:56:55.189: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-handler.c:354) > > 03/17 16:56:55.189: [mme] DEBUG: mme_state_operational(): > MME_EVT_EMM_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.189: [emm] DEBUG: emm_state_authentication(): > MME_EVT_EMM_MESSAGE > > (../src/mme/emm-sm.c:488) > > 03/17 16:56:55.189: [emm] DEBUG: [EMM] Authentication response > (../src/mme/emm-sm.c:512) > > 03/17 16:56:55.189: [emm] DEBUG: IMSI[311980000033212] > (../src/mme/emm-sm.c:513) > > 03/17 16:56:55.189: [emm] DEBUG: emm_state_authentication(): EXIT > > (../src/mme/emm-sm.c:488) > > 03/17 16:56:55.189: [emm] DEBUG: emm_state_security_mode(): ENTRY > > (../src/mme/emm-sm.c:649) > > 03/17 16:56:55.189: [mme] DEBUG: [EMM] Security mode command > (../src/mme/nas-path.c:207) > > 03/17 16:56:55.189: [mme] DEBUG: IMSI[311980000033212] > (../src/mme/nas-path.c:208) > > 03/17 16:56:55.190: [emm] DEBUG: Replayed UE SEC[LEN:2 EEA:0xe0 > EIA:0xe0 UEA:0x0 UIA:0x0 GEA:0x0] (../src/mme/emm-build.c:287) > > 03/17 16:56:55.190: [emm] DEBUG: Selected[Integrity:0x1 Encrypt:0x0] > (../src/mme/emm-build.c:289) > > 03/17 16:56:55.190: [mme] DEBUG: [MME] DownlinkNASTransport > (../src/mme/s1ap-build.c:186) > > 03/17 16:56:55.190: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-build.c:231) > > 03/17 16:56:55.190: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-path.c:79) > > 03/17 16:56:55.229: [mme] DEBUG: mme_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.230: [mme] DEBUG: s1ap_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/s1ap-sm.c:60) > > 03/17 16:56:55.230: [mme] DEBUG: [MME] Uplink NAS transport > (../src/mme/s1ap-handler.c:330) > > 03/17 16:56:55.230: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-handler.c:347) > > 03/17 16:56:55.230: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-handler.c:354) > > 03/17 16:56:55.230: [mme] DEBUG: mme_state_operational(): > MME_EVT_EMM_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.230: [emm] DEBUG: emm_state_security_mode(): > MME_EVT_EMM_MESSAGE > > (../src/mme/emm-sm.c:649) > > 03/17 16:56:55.230: [emm] DEBUG: [EMM] Security mode complete > (../src/mme/emm-sm.c:676) > > 03/17 16:56:55.230: [emm] DEBUG: IMSI[311980000033212] > (../src/mme/emm-sm.c:677) > > 03/17 16:56:55.230: [mme] DEBUG: [MME] Update-Location-Request > (../src/mme/mme-fd-path.c:444) > > 03/17 16:56:55.231: [emm] DEBUG: emm_state_security_mode(): EXIT > > (../src/mme/emm-sm.c:649) > > 03/17 16:56:55.231: [emm] DEBUG: emm_state_initial_context_setup(): ENTRY > > (../src/mme/emm-sm.c:817) > > 03/17 16:56:55.234: [mme] DEBUG: [MME] Update-Location-Answer > (../src/mme/mme-fd-path.c:610) > > 03/17 16:56:55.234: [mme] DEBUG: Result Code: 2001 > (../src/mme/mme-fd-path.c:651) > > 03/17 16:56:55.234: [mme] DEBUG: From 'hss.localdomain' > (../src/mme/mme-fd-path.c:680) > > 03/17 16:56:55.234: [mme] DEBUG: ('localdomain') > (../src/mme/mme-fd-path.c:693) > > 03/17 16:56:55.234: [mme] DEBUG: mme_state_operational(): > MME_EVT_S6A_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.234: [mme] DEBUG: mme_state_operational(): > MME_EVT_ESM_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.234: [mme] DEBUG: mme_bearer_find_or_add_by_message() > [PTI:8, EBI:0] (../src/mme/mme-context.c:2847) > > 03/17 16:56:55.234: [esm] DEBUG: esm_state_initial(): ENTRY > > (../src/mme/esm-sm.c:38) > > 03/17 16:56:55.234: [esm] DEBUG: esm_state_inactive(): ENTRY > > (../src/mme/esm-sm.c:61) > > 03/17 16:56:55.234: [mme] INFO: Added a session. Number of sessions is now > 1 (../src/mme/mme-context.c:79) > > 03/17 16:56:55.234: [esm] DEBUG: esm_state_inactive(): MME_EVT_ESM_MESSAGE > > (../src/mme/esm-sm.c:61) > > 03/17 16:56:55.234: [esm] DEBUG: [ESM] PDN Connectivity request > (../src/mme/esm-sm.c:82) > > 03/17 16:56:55.234: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] > (../src/mme/esm-sm.c:84) > > 03/17 16:56:55.234: [esm] DEBUG: EIT(ESM information transfer)[1] > (../src/mme/esm-handler.c:59) > > 03/17 16:56:55.234: [esm] DEBUG: [ESM] ESM information request > (../src/mme/esm-build.c:75) > > 03/17 16:56:55.234: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] > (../src/mme/esm-build.c:77) > > 03/17 16:56:55.235: [mme] DEBUG: [MME] DownlinkNASTransport > (../src/mme/s1ap-build.c:186) > > 03/17 16:56:55.235: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-build.c:231) > > 03/17 16:56:55.235: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-path.c:79) > > 03/17 16:56:55.269: [mme] DEBUG: mme_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.270: [mme] DEBUG: s1ap_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/s1ap-sm.c:60) > > 03/17 16:56:55.270: [mme] DEBUG: [MME] Uplink NAS transport > (../src/mme/s1ap-handler.c:330) > > 03/17 16:56:55.270: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-handler.c:347) > > 03/17 16:56:55.270: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-handler.c:354) > > 03/17 16:56:55.270: [mme] DEBUG: mme_state_operational(): > MME_EVT_ESM_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.270: [mme] DEBUG: mme_bearer_find_or_add_by_message() > [PTI:8, EBI:0] (../src/mme/mme-context.c:2847) > > 03/17 16:56:55.270: [esm] DEBUG: esm_state_inactive(): MME_EVT_ESM_MESSAGE > > (../src/mme/esm-sm.c:61) > > 03/17 16:56:55.270: [esm] DEBUG: [ESM] ESM information response > (../src/mme/esm-sm.c:93) > > 03/17 16:56:55.270: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] > (../src/mme/esm-sm.c:95) > > 03/17 16:56:55.270: [mme] DEBUG: [EMM] Attach reject > (../src/mme/nas-path.c:134) > > 03/17 16:56:55.270: [mme] DEBUG: IMSI[311980000033212] Cause[8] > (../src/mme/nas-path.c:135) > > 03/17 16:56:55.270: [esm] DEBUG: [ESM] PDN connectivity reject > (../src/mme/esm-build.c:39) > > 03/17 16:56:55.270: [esm] DEBUG: IMSI[311980000033212] PTI[8] > Cause[27] (../src/mme/esm-build.c:41) > > 03/17 16:56:55.271: [mme] DEBUG: [MME] DownlinkNASTransport > (../src/mme/s1ap-build.c:186) > > 03/17 16:56:55.271: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-build.c:231) > > 03/17 16:56:55.271: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-path.c:79) > > 03/17 16:56:55.271: [esm] DEBUG: esm_state_inactive(): EXIT > > (../src/mme/esm-sm.c:61) > > 03/17 16:56:55.271: [esm] DEBUG: esm_state_exception(): ENTRY > > (../src/mme/esm-sm.c:345) > > 03/17 16:56:55.271: [mme] DEBUG: [MME] UE Context release command > (../src/mme/s1ap-path.c:285) > > 03/17 16:56:55.271: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-path.c:287) > > 03/17 16:56:55.271: [mme] DEBUG: Group[3] Cause[0] Action[3] Delay[0] > (../src/mme/s1ap-path.c:306) > > 03/17 16:56:55.271: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-path.c:79) > > 03/17 16:56:55.275: [mme] DEBUG: mme_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.275: [mme] DEBUG: s1ap_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/s1ap-sm.c:60) > > 03/17 16:56:55.275: [mme] DEBUG: [MME] UE Context release complete > (../src/mme/s1ap-handler.c:919) > > 03/17 16:56:55.276: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-handler.c:933) > > 03/17 16:56:55.276: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-handler.c:950) > > 03/17 16:56:55.276: [mme] DEBUG: Action: UE context remove() > (../src/mme/s1ap-handler.c:963) > > 03/17 16:56:55.276: [mme] INFO: Removed a UE. Number of UEs is now 0 > (../src/mme/mme-context.c:63) > > 03/17 16:56:55.276: [emm] DEBUG: emm_state_initial_context_setup(): EXIT > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From david at ispsupplies.com Fri Mar 27 16:10:34 2020 From: david at ispsupplies.com (david at ispsupplies.com) Date: Fri, 27 Mar 2020 12:10:34 -0400 Subject: Reject message In-Reply-To: References: <010d01d5fcac$ea022040$be0660c0$@ispsupplies.com> Message-ID: <025e01d60452$40a73e60$c1f5bb20$@ispsupplies.com> I figured out what was going on, so perhaps there is a solution already in place. By default the Baicells UE do not request a specific APN. That causes the EPC to reject the request. David Peterson Senior Engineer 855-947-7776 ext. 9214 c 419-706-7355 d 979-314-1305 https://www.ispsupplies.com From: Sukchan Lee Sent: Friday, March 27, 2020 11:57 AM To: david at ispsupplies.com Cc: nextepc at lists.osmocom.org Subject: Re: Reject message Hi david, If pcap is provided, it is more easier to analyze your problem. BTW, from your log, I've found PDN connectivity reject with ESM_CAUSE:27. It means that UE APN is unknown in HSS. So, you need to match APN name between UE and HSS. Thanks and regards, Sukchan On Tue, Mar 17, 2020 at 6:47 PM > wrote: Does anyone know why I am getting this reject reason for network entry on a UE? 03/17 16:56:55.026: [mme] DEBUG: [EMM] Authentication request (../src/mme/nas-path.c:180) 03/17 16:56:55.026: [mme] DEBUG: IMSI[311980000033212] (../src/mme/nas-path.c:181) 03/17 16:56:55.026: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.026: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.026: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.189: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.189: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.189: [mme] DEBUG: [MME] Uplink NAS transport (../src/mme/s1ap-handler.c:330) 03/17 16:56:55.189: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:347) 03/17 16:56:55.189: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:354) 03/17 16:56:55.189: [mme] DEBUG: mme_state_operational(): MME_EVT_EMM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.189: [emm] DEBUG: emm_state_authentication(): MME_EVT_EMM_MESSAGE (../src/mme/emm-sm.c:488) 03/17 16:56:55.189: [emm] DEBUG: [EMM] Authentication response (../src/mme/emm-sm.c:512) 03/17 16:56:55.189: [emm] DEBUG: IMSI[311980000033212] (../src/mme/emm-sm.c:513) 03/17 16:56:55.189: [emm] DEBUG: emm_state_authentication(): EXIT (../src/mme/emm-sm.c:488) 03/17 16:56:55.189: [emm] DEBUG: emm_state_security_mode(): ENTRY (../src/mme/emm-sm.c:649) 03/17 16:56:55.189: [mme] DEBUG: [EMM] Security mode command (../src/mme/nas-path.c:207) 03/17 16:56:55.189: [mme] DEBUG: IMSI[311980000033212] (../src/mme/nas-path.c:208) 03/17 16:56:55.190: [emm] DEBUG: Replayed UE SEC[LEN:2 EEA:0xe0 EIA:0xe0 UEA:0x0 UIA:0x0 GEA:0x0] (../src/mme/emm-build.c:287) 03/17 16:56:55.190: [emm] DEBUG: Selected[Integrity:0x1 Encrypt:0x0] (../src/mme/emm-build.c:289) 03/17 16:56:55.190: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.190: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.190: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.229: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.230: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.230: [mme] DEBUG: [MME] Uplink NAS transport (../src/mme/s1ap-handler.c:330) 03/17 16:56:55.230: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:347) 03/17 16:56:55.230: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:354) 03/17 16:56:55.230: [mme] DEBUG: mme_state_operational(): MME_EVT_EMM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.230: [emm] DEBUG: emm_state_security_mode(): MME_EVT_EMM_MESSAGE (../src/mme/emm-sm.c:649) 03/17 16:56:55.230: [emm] DEBUG: [EMM] Security mode complete (../src/mme/emm-sm.c:676) 03/17 16:56:55.230: [emm] DEBUG: IMSI[311980000033212] (../src/mme/emm-sm.c:677) 03/17 16:56:55.230: [mme] DEBUG: [MME] Update-Location-Request (../src/mme/mme-fd-path.c:444) 03/17 16:56:55.231: [emm] DEBUG: emm_state_security_mode(): EXIT (../src/mme/emm-sm.c:649) 03/17 16:56:55.231: [emm] DEBUG: emm_state_initial_context_setup(): ENTRY (../src/mme/emm-sm.c:817) 03/17 16:56:55.234: [mme] DEBUG: [MME] Update-Location-Answer (../src/mme/mme-fd-path.c:610) 03/17 16:56:55.234: [mme] DEBUG: Result Code: 2001 (../src/mme/mme-fd-path.c:651) 03/17 16:56:55.234: [mme] DEBUG: From 'hss.localdomain' (../src/mme/mme-fd-path.c:680) 03/17 16:56:55.234: [mme] DEBUG: ('localdomain') (../src/mme/mme-fd-path.c:693) 03/17 16:56:55.234: [mme] DEBUG: mme_state_operational(): MME_EVT_S6A_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.234: [mme] DEBUG: mme_state_operational(): MME_EVT_ESM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.234: [mme] DEBUG: mme_bearer_find_or_add_by_message() [PTI:8, EBI:0] (../src/mme/mme-context.c:2847) 03/17 16:56:55.234: [esm] DEBUG: esm_state_initial(): ENTRY (../src/mme/esm-sm.c:38) 03/17 16:56:55.234: [esm] DEBUG: esm_state_inactive(): ENTRY (../src/mme/esm-sm.c:61) 03/17 16:56:55.234: [mme] INFO: Added a session. Number of sessions is now 1 (../src/mme/mme-context.c:79) 03/17 16:56:55.234: [esm] DEBUG: esm_state_inactive(): MME_EVT_ESM_MESSAGE (../src/mme/esm-sm.c:61) 03/17 16:56:55.234: [esm] DEBUG: [ESM] PDN Connectivity request (../src/mme/esm-sm.c:82) 03/17 16:56:55.234: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] (../src/mme/esm-sm.c:84) 03/17 16:56:55.234: [esm] DEBUG: EIT(ESM information transfer)[1] (../src/mme/esm-handler.c:59) 03/17 16:56:55.234: [esm] DEBUG: [ESM] ESM information request (../src/mme/esm-build.c:75) 03/17 16:56:55.234: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] (../src/mme/esm-build.c:77) 03/17 16:56:55.235: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.235: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.235: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.269: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.270: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.270: [mme] DEBUG: [MME] Uplink NAS transport (../src/mme/s1ap-handler.c:330) 03/17 16:56:55.270: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:347) 03/17 16:56:55.270: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:354) 03/17 16:56:55.270: [mme] DEBUG: mme_state_operational(): MME_EVT_ESM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.270: [mme] DEBUG: mme_bearer_find_or_add_by_message() [PTI:8, EBI:0] (../src/mme/mme-context.c:2847) 03/17 16:56:55.270: [esm] DEBUG: esm_state_inactive(): MME_EVT_ESM_MESSAGE (../src/mme/esm-sm.c:61) 03/17 16:56:55.270: [esm] DEBUG: [ESM] ESM information response (../src/mme/esm-sm.c:93) 03/17 16:56:55.270: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] (../src/mme/esm-sm.c:95) 03/17 16:56:55.270: [mme] DEBUG: [EMM] Attach reject (../src/mme/nas-path.c:134) 03/17 16:56:55.270: [mme] DEBUG: IMSI[311980000033212] Cause[8] (../src/mme/nas-path.c:135) 03/17 16:56:55.270: [esm] DEBUG: [ESM] PDN connectivity reject (../src/mme/esm-build.c:39) 03/17 16:56:55.270: [esm] DEBUG: IMSI[311980000033212] PTI[8] Cause[27] (../src/mme/esm-build.c:41) 03/17 16:56:55.271: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.271: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.271: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.271: [esm] DEBUG: esm_state_inactive(): EXIT (../src/mme/esm-sm.c:61) 03/17 16:56:55.271: [esm] DEBUG: esm_state_exception(): ENTRY (../src/mme/esm-sm.c:345) 03/17 16:56:55.271: [mme] DEBUG: [MME] UE Context release command (../src/mme/s1ap-path.c:285) 03/17 16:56:55.271: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-path.c:287) 03/17 16:56:55.271: [mme] DEBUG: Group[3] Cause[0] Action[3] Delay[0] (../src/mme/s1ap-path.c:306) 03/17 16:56:55.271: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.275: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.275: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.275: [mme] DEBUG: [MME] UE Context release complete (../src/mme/s1ap-handler.c:919) 03/17 16:56:55.276: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:933) 03/17 16:56:55.276: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:950) 03/17 16:56:55.276: [mme] DEBUG: Action: UE context remove() (../src/mme/s1ap-handler.c:963) 03/17 16:56:55.276: [mme] INFO: Removed a UE. Number of UEs is now 0 (../src/mme/mme-context.c:63) 03/17 16:56:55.276: [emm] DEBUG: emm_state_initial_context_setup(): EXIT -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 19638 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 701 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 420 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 444 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 441 bytes Desc: not available URL: From acetcom at gmail.com Sat Mar 28 23:57:47 2020 From: acetcom at gmail.com (Sukchan Lee) Date: Sat, 28 Mar 2020 19:57:47 -0400 Subject: Reject message In-Reply-To: <025e01d60452$40a73e60$c1f5bb20$@ispsupplies.com> References: <010d01d5fcac$ea022040$be0660c0$@ispsupplies.com> <025e01d60452$40a73e60$c1f5bb20$@ispsupplies.com> Message-ID: Even though UE try to connect without APN, if you set the first APN(default APN) to the mongoDB, open5gs won't reject the UE request. If the problem is still not resolved, I need your pcap file to fix the issue. On Fri, Mar 27, 2020 at 12:10 PM wrote: > I figured out what was going on, so perhaps there is a solution already in > place. By default the Baicells UE do not request a specific APN. That > causes the EPC to reject the request. > > > > [image: ISP Supplies] > > [image: cid:image002.jpg at 01D5B005.DEE3BE10] > > *David Peterson* > Senior Engineer > 855-947-7776 ext. 9214 > c 419-706-7355 > d 979-314-1305 > https://www.ispsupplies.com *[image: Facebook]* > *[image: Twitter]* > *[image: LinkedIn]* > > > > > > > *From:* Sukchan Lee > *Sent:* Friday, March 27, 2020 11:57 AM > *To:* david at ispsupplies.com > *Cc:* nextepc at lists.osmocom.org > *Subject:* Re: Reject message > > > > Hi david, > > > > If pcap is provided, it is more easier to analyze your problem. > > > > BTW, from your log, I've found PDN connectivity reject with ESM_CAUSE:27. > > It means that UE APN is unknown in HSS. So, you need to match APN name > between UE and HSS. > > > > Thanks and regards, > > Sukchan > > > > On Tue, Mar 17, 2020 at 6:47 PM wrote: > > Does anyone know why I am getting this reject reason for network entry on > a UE? > > > > 03/17 16:56:55.026: [mme] DEBUG: [EMM] Authentication request > (../src/mme/nas-path.c:180) > > 03/17 16:56:55.026: [mme] DEBUG: IMSI[311980000033212] > (../src/mme/nas-path.c:181) > > 03/17 16:56:55.026: [mme] DEBUG: [MME] DownlinkNASTransport > (../src/mme/s1ap-build.c:186) > > 03/17 16:56:55.026: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-build.c:231) > > 03/17 16:56:55.026: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-path.c:79) > > 03/17 16:56:55.189: [mme] DEBUG: mme_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.189: [mme] DEBUG: s1ap_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/s1ap-sm.c:60) > > 03/17 16:56:55.189: [mme] DEBUG: [MME] Uplink NAS transport > (../src/mme/s1ap-handler.c:330) > > 03/17 16:56:55.189: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-handler.c:347) > > 03/17 16:56:55.189: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-handler.c:354) > > 03/17 16:56:55.189: [mme] DEBUG: mme_state_operational(): > MME_EVT_EMM_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.189: [emm] DEBUG: emm_state_authentication(): > MME_EVT_EMM_MESSAGE > > (../src/mme/emm-sm.c:488) > > 03/17 16:56:55.189: [emm] DEBUG: [EMM] Authentication response > (../src/mme/emm-sm.c:512) > > 03/17 16:56:55.189: [emm] DEBUG: IMSI[311980000033212] > (../src/mme/emm-sm.c:513) > > 03/17 16:56:55.189: [emm] DEBUG: emm_state_authentication(): EXIT > > (../src/mme/emm-sm.c:488) > > 03/17 16:56:55.189: [emm] DEBUG: emm_state_security_mode(): ENTRY > > (../src/mme/emm-sm.c:649) > > 03/17 16:56:55.189: [mme] DEBUG: [EMM] Security mode command > (../src/mme/nas-path.c:207) > > 03/17 16:56:55.189: [mme] DEBUG: IMSI[311980000033212] > (../src/mme/nas-path.c:208) > > 03/17 16:56:55.190: [emm] DEBUG: Replayed UE SEC[LEN:2 EEA:0xe0 > EIA:0xe0 UEA:0x0 UIA:0x0 GEA:0x0] (../src/mme/emm-build.c:287) > > 03/17 16:56:55.190: [emm] DEBUG: Selected[Integrity:0x1 Encrypt:0x0] > (../src/mme/emm-build.c:289) > > 03/17 16:56:55.190: [mme] DEBUG: [MME] DownlinkNASTransport > (../src/mme/s1ap-build.c:186) > > 03/17 16:56:55.190: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-build.c:231) > > 03/17 16:56:55.190: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-path.c:79) > > 03/17 16:56:55.229: [mme] DEBUG: mme_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.230: [mme] DEBUG: s1ap_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/s1ap-sm.c:60) > > 03/17 16:56:55.230: [mme] DEBUG: [MME] Uplink NAS transport > (../src/mme/s1ap-handler.c:330) > > 03/17 16:56:55.230: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-handler.c:347) > > 03/17 16:56:55.230: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-handler.c:354) > > 03/17 16:56:55.230: [mme] DEBUG: mme_state_operational(): > MME_EVT_EMM_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.230: [emm] DEBUG: emm_state_security_mode(): > MME_EVT_EMM_MESSAGE > > (../src/mme/emm-sm.c:649) > > 03/17 16:56:55.230: [emm] DEBUG: [EMM] Security mode complete > (../src/mme/emm-sm.c:676) > > 03/17 16:56:55.230: [emm] DEBUG: IMSI[311980000033212] > (../src/mme/emm-sm.c:677) > > 03/17 16:56:55.230: [mme] DEBUG: [MME] Update-Location-Request > (../src/mme/mme-fd-path.c:444) > > 03/17 16:56:55.231: [emm] DEBUG: emm_state_security_mode(): EXIT > > (../src/mme/emm-sm.c:649) > > 03/17 16:56:55.231: [emm] DEBUG: emm_state_initial_context_setup(): ENTRY > > (../src/mme/emm-sm.c:817) > > 03/17 16:56:55.234: [mme] DEBUG: [MME] Update-Location-Answer > (../src/mme/mme-fd-path.c:610) > > 03/17 16:56:55.234: [mme] DEBUG: Result Code: 2001 > (../src/mme/mme-fd-path.c:651) > > 03/17 16:56:55.234: [mme] DEBUG: From 'hss.localdomain' > (../src/mme/mme-fd-path.c:680) > > 03/17 16:56:55.234: [mme] DEBUG: ('localdomain') > (../src/mme/mme-fd-path.c:693) > > 03/17 16:56:55.234: [mme] DEBUG: mme_state_operational(): > MME_EVT_S6A_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.234: [mme] DEBUG: mme_state_operational(): > MME_EVT_ESM_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.234: [mme] DEBUG: mme_bearer_find_or_add_by_message() > [PTI:8, EBI:0] (../src/mme/mme-context.c:2847) > > 03/17 16:56:55.234: [esm] DEBUG: esm_state_initial(): ENTRY > > (../src/mme/esm-sm.c:38) > > 03/17 16:56:55.234: [esm] DEBUG: esm_state_inactive(): ENTRY > > (../src/mme/esm-sm.c:61) > > 03/17 16:56:55.234: [mme] INFO: Added a session. Number of sessions is now > 1 (../src/mme/mme-context.c:79) > > 03/17 16:56:55.234: [esm] DEBUG: esm_state_inactive(): MME_EVT_ESM_MESSAGE > > (../src/mme/esm-sm.c:61) > > 03/17 16:56:55.234: [esm] DEBUG: [ESM] PDN Connectivity request > (../src/mme/esm-sm.c:82) > > 03/17 16:56:55.234: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] > (../src/mme/esm-sm.c:84) > > 03/17 16:56:55.234: [esm] DEBUG: EIT(ESM information transfer)[1] > (../src/mme/esm-handler.c:59) > > 03/17 16:56:55.234: [esm] DEBUG: [ESM] ESM information request > (../src/mme/esm-build.c:75) > > 03/17 16:56:55.234: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] > (../src/mme/esm-build.c:77) > > 03/17 16:56:55.235: [mme] DEBUG: [MME] DownlinkNASTransport > (../src/mme/s1ap-build.c:186) > > 03/17 16:56:55.235: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-build.c:231) > > 03/17 16:56:55.235: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-path.c:79) > > 03/17 16:56:55.269: [mme] DEBUG: mme_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.270: [mme] DEBUG: s1ap_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/s1ap-sm.c:60) > > 03/17 16:56:55.270: [mme] DEBUG: [MME] Uplink NAS transport > (../src/mme/s1ap-handler.c:330) > > 03/17 16:56:55.270: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-handler.c:347) > > 03/17 16:56:55.270: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-handler.c:354) > > 03/17 16:56:55.270: [mme] DEBUG: mme_state_operational(): > MME_EVT_ESM_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.270: [mme] DEBUG: mme_bearer_find_or_add_by_message() > [PTI:8, EBI:0] (../src/mme/mme-context.c:2847) > > 03/17 16:56:55.270: [esm] DEBUG: esm_state_inactive(): MME_EVT_ESM_MESSAGE > > (../src/mme/esm-sm.c:61) > > 03/17 16:56:55.270: [esm] DEBUG: [ESM] ESM information response > (../src/mme/esm-sm.c:93) > > 03/17 16:56:55.270: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] > (../src/mme/esm-sm.c:95) > > 03/17 16:56:55.270: [mme] DEBUG: [EMM] Attach reject > (../src/mme/nas-path.c:134) > > 03/17 16:56:55.270: [mme] DEBUG: IMSI[311980000033212] Cause[8] > (../src/mme/nas-path.c:135) > > 03/17 16:56:55.270: [esm] DEBUG: [ESM] PDN connectivity reject > (../src/mme/esm-build.c:39) > > 03/17 16:56:55.270: [esm] DEBUG: IMSI[311980000033212] PTI[8] > Cause[27] (../src/mme/esm-build.c:41) > > 03/17 16:56:55.271: [mme] DEBUG: [MME] DownlinkNASTransport > (../src/mme/s1ap-build.c:186) > > 03/17 16:56:55.271: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-build.c:231) > > 03/17 16:56:55.271: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-path.c:79) > > 03/17 16:56:55.271: [esm] DEBUG: esm_state_inactive(): EXIT > > (../src/mme/esm-sm.c:61) > > 03/17 16:56:55.271: [esm] DEBUG: esm_state_exception(): ENTRY > > (../src/mme/esm-sm.c:345) > > 03/17 16:56:55.271: [mme] DEBUG: [MME] UE Context release command > (../src/mme/s1ap-path.c:285) > > 03/17 16:56:55.271: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-path.c:287) > > 03/17 16:56:55.271: [mme] DEBUG: Group[3] Cause[0] Action[3] Delay[0] > (../src/mme/s1ap-path.c:306) > > 03/17 16:56:55.271: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-path.c:79) > > 03/17 16:56:55.275: [mme] DEBUG: mme_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.275: [mme] DEBUG: s1ap_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/s1ap-sm.c:60) > > 03/17 16:56:55.275: [mme] DEBUG: [MME] UE Context release complete > (../src/mme/s1ap-handler.c:919) > > 03/17 16:56:55.276: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-handler.c:933) > > 03/17 16:56:55.276: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-handler.c:950) > > 03/17 16:56:55.276: [mme] DEBUG: Action: UE context remove() > (../src/mme/s1ap-handler.c:963) > > 03/17 16:56:55.276: [mme] INFO: Removed a UE. Number of UEs is now 0 > (../src/mme/mme-context.c:63) > > 03/17 16:56:55.276: [emm] DEBUG: emm_state_initial_context_setup(): EXIT > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 19640 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 701 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 420 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 444 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 441 bytes Desc: not available URL: From david at ispsupplies.com Sun Mar 29 00:25:44 2020 From: david at ispsupplies.com (david at ispsupplies.com) Date: Sat, 28 Mar 2020 20:25:44 -0400 Subject: Reject message In-Reply-To: References: <010d01d5fcac$ea022040$be0660c0$@ispsupplies.com> <025e01d60452$40a73e60$c1f5bb20$@ispsupplies.com> Message-ID: <001301d60560$97477410$c5d65c30$@ispsupplies.com> I will get you a pcap. The UE actually don?t have an APN listed by default. David Peterson Senior Engineer 855-947-7776 ext. 9214 c 419-706-7355 d 979-314-1305 https://www.ispsupplies.com From: Sukchan Lee Sent: Saturday, March 28, 2020 7:58 PM To: david at ispsupplies.com Cc: nextepc at lists.osmocom.org Subject: Re: Reject message Even though UE try to connect without APN, if you set the first APN(default APN) to the mongoDB, open5gs won't reject the UE request. If the problem is still not resolved, I need your pcap file to fix the issue. On Fri, Mar 27, 2020 at 12:10 PM > wrote: I figured out what was going on, so perhaps there is a solution already in place. By default the Baicells UE do not request a specific APN. That causes the EPC to reject the request. David Peterson Senior Engineer 855-947-7776 ext. 9214 c 419-706-7355 d 979-314-1305 https://www.ispsupplies.com From: Sukchan Lee > Sent: Friday, March 27, 2020 11:57 AM To: david at ispsupplies.com Cc: nextepc at lists.osmocom.org Subject: Re: Reject message Hi david, If pcap is provided, it is more easier to analyze your problem. BTW, from your log, I've found PDN connectivity reject with ESM_CAUSE:27. It means that UE APN is unknown in HSS. So, you need to match APN name between UE and HSS. Thanks and regards, Sukchan On Tue, Mar 17, 2020 at 6:47 PM > wrote: Does anyone know why I am getting this reject reason for network entry on a UE? 03/17 16:56:55.026: [mme] DEBUG: [EMM] Authentication request (../src/mme/nas-path.c:180) 03/17 16:56:55.026: [mme] DEBUG: IMSI[311980000033212] (../src/mme/nas-path.c:181) 03/17 16:56:55.026: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.026: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.026: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.189: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.189: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.189: [mme] DEBUG: [MME] Uplink NAS transport (../src/mme/s1ap-handler.c:330) 03/17 16:56:55.189: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:347) 03/17 16:56:55.189: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:354) 03/17 16:56:55.189: [mme] DEBUG: mme_state_operational(): MME_EVT_EMM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.189: [emm] DEBUG: emm_state_authentication(): MME_EVT_EMM_MESSAGE (../src/mme/emm-sm.c:488) 03/17 16:56:55.189: [emm] DEBUG: [EMM] Authentication response (../src/mme/emm-sm.c:512) 03/17 16:56:55.189: [emm] DEBUG: IMSI[311980000033212] (../src/mme/emm-sm.c:513) 03/17 16:56:55.189: [emm] DEBUG: emm_state_authentication(): EXIT (../src/mme/emm-sm.c:488) 03/17 16:56:55.189: [emm] DEBUG: emm_state_security_mode(): ENTRY (../src/mme/emm-sm.c:649) 03/17 16:56:55.189: [mme] DEBUG: [EMM] Security mode command (../src/mme/nas-path.c:207) 03/17 16:56:55.189: [mme] DEBUG: IMSI[311980000033212] (../src/mme/nas-path.c:208) 03/17 16:56:55.190: [emm] DEBUG: Replayed UE SEC[LEN:2 EEA:0xe0 EIA:0xe0 UEA:0x0 UIA:0x0 GEA:0x0] (../src/mme/emm-build.c:287) 03/17 16:56:55.190: [emm] DEBUG: Selected[Integrity:0x1 Encrypt:0x0] (../src/mme/emm-build.c:289) 03/17 16:56:55.190: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.190: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.190: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.229: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.230: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.230: [mme] DEBUG: [MME] Uplink NAS transport (../src/mme/s1ap-handler.c:330) 03/17 16:56:55.230: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:347) 03/17 16:56:55.230: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:354) 03/17 16:56:55.230: [mme] DEBUG: mme_state_operational(): MME_EVT_EMM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.230: [emm] DEBUG: emm_state_security_mode(): MME_EVT_EMM_MESSAGE (../src/mme/emm-sm.c:649) 03/17 16:56:55.230: [emm] DEBUG: [EMM] Security mode complete (../src/mme/emm-sm.c:676) 03/17 16:56:55.230: [emm] DEBUG: IMSI[311980000033212] (../src/mme/emm-sm.c:677) 03/17 16:56:55.230: [mme] DEBUG: [MME] Update-Location-Request (../src/mme/mme-fd-path.c:444) 03/17 16:56:55.231: [emm] DEBUG: emm_state_security_mode(): EXIT (../src/mme/emm-sm.c:649) 03/17 16:56:55.231: [emm] DEBUG: emm_state_initial_context_setup(): ENTRY (../src/mme/emm-sm.c:817) 03/17 16:56:55.234: [mme] DEBUG: [MME] Update-Location-Answer (../src/mme/mme-fd-path.c:610) 03/17 16:56:55.234: [mme] DEBUG: Result Code: 2001 (../src/mme/mme-fd-path.c:651) 03/17 16:56:55.234: [mme] DEBUG: From 'hss.localdomain' (../src/mme/mme-fd-path.c:680) 03/17 16:56:55.234: [mme] DEBUG: ('localdomain') (../src/mme/mme-fd-path.c:693) 03/17 16:56:55.234: [mme] DEBUG: mme_state_operational(): MME_EVT_S6A_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.234: [mme] DEBUG: mme_state_operational(): MME_EVT_ESM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.234: [mme] DEBUG: mme_bearer_find_or_add_by_message() [PTI:8, EBI:0] (../src/mme/mme-context.c:2847) 03/17 16:56:55.234: [esm] DEBUG: esm_state_initial(): ENTRY (../src/mme/esm-sm.c:38) 03/17 16:56:55.234: [esm] DEBUG: esm_state_inactive(): ENTRY (../src/mme/esm-sm.c:61) 03/17 16:56:55.234: [mme] INFO: Added a session. Number of sessions is now 1 (../src/mme/mme-context.c:79) 03/17 16:56:55.234: [esm] DEBUG: esm_state_inactive(): MME_EVT_ESM_MESSAGE (../src/mme/esm-sm.c:61) 03/17 16:56:55.234: [esm] DEBUG: [ESM] PDN Connectivity request (../src/mme/esm-sm.c:82) 03/17 16:56:55.234: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] (../src/mme/esm-sm.c:84) 03/17 16:56:55.234: [esm] DEBUG: EIT(ESM information transfer)[1] (../src/mme/esm-handler.c:59) 03/17 16:56:55.234: [esm] DEBUG: [ESM] ESM information request (../src/mme/esm-build.c:75) 03/17 16:56:55.234: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] (../src/mme/esm-build.c:77) 03/17 16:56:55.235: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.235: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.235: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.269: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.270: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.270: [mme] DEBUG: [MME] Uplink NAS transport (../src/mme/s1ap-handler.c:330) 03/17 16:56:55.270: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:347) 03/17 16:56:55.270: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:354) 03/17 16:56:55.270: [mme] DEBUG: mme_state_operational(): MME_EVT_ESM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.270: [mme] DEBUG: mme_bearer_find_or_add_by_message() [PTI:8, EBI:0] (../src/mme/mme-context.c:2847) 03/17 16:56:55.270: [esm] DEBUG: esm_state_inactive(): MME_EVT_ESM_MESSAGE (../src/mme/esm-sm.c:61) 03/17 16:56:55.270: [esm] DEBUG: [ESM] ESM information response (../src/mme/esm-sm.c:93) 03/17 16:56:55.270: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] (../src/mme/esm-sm.c:95) 03/17 16:56:55.270: [mme] DEBUG: [EMM] Attach reject (../src/mme/nas-path.c:134) 03/17 16:56:55.270: [mme] DEBUG: IMSI[311980000033212] Cause[8] (../src/mme/nas-path.c:135) 03/17 16:56:55.270: [esm] DEBUG: [ESM] PDN connectivity reject (../src/mme/esm-build.c:39) 03/17 16:56:55.270: [esm] DEBUG: IMSI[311980000033212] PTI[8] Cause[27] (../src/mme/esm-build.c:41) 03/17 16:56:55.271: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.271: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.271: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.271: [esm] DEBUG: esm_state_inactive(): EXIT (../src/mme/esm-sm.c:61) 03/17 16:56:55.271: [esm] DEBUG: esm_state_exception(): ENTRY (../src/mme/esm-sm.c:345) 03/17 16:56:55.271: [mme] DEBUG: [MME] UE Context release command (../src/mme/s1ap-path.c:285) 03/17 16:56:55.271: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-path.c:287) 03/17 16:56:55.271: [mme] DEBUG: Group[3] Cause[0] Action[3] Delay[0] (../src/mme/s1ap-path.c:306) 03/17 16:56:55.271: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.275: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.275: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.275: [mme] DEBUG: [MME] UE Context release complete (../src/mme/s1ap-handler.c:919) 03/17 16:56:55.276: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:933) 03/17 16:56:55.276: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:950) 03/17 16:56:55.276: [mme] DEBUG: Action: UE context remove() (../src/mme/s1ap-handler.c:963) 03/17 16:56:55.276: [mme] INFO: Removed a UE. Number of UEs is now 0 (../src/mme/mme-context.c:63) 03/17 16:56:55.276: [emm] DEBUG: emm_state_initial_context_setup(): EXIT -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 19638 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 701 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 420 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 444 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 441 bytes Desc: not available URL: From ganiyuabiolaaminat at gmail.com Sun Mar 29 18:24:54 2020 From: ganiyuabiolaaminat at gmail.com (Abiola Ganiyu) Date: Sun, 29 Mar 2020 19:24:54 +0100 Subject: Reject message In-Reply-To: <001301d60560$97477410$c5d65c30$@ispsupplies.com> References: <010d01d5fcac$ea022040$be0660c0$@ispsupplies.com> <025e01d60452$40a73e60$c1f5bb20$@ispsupplies.com> <001301d60560$97477410$c5d65c30$@ispsupplies.com> Message-ID: Hi David, Baicells CPE has "internet" set as APN by default. And you can make changes to the APN name under APN management field. On Sun, Mar 29, 2020, 01:25 wrote: > I will get you a pcap. The UE actually don?t have an APN listed by > default. > > > > [image: ISP Supplies] > > [image: cid:image002.jpg at 01D5B005.DEE3BE10] > > *David Peterson* > Senior Engineer > 855-947-7776 ext. 9214 > c 419-706-7355 > d 979-314-1305 > https://www.ispsupplies.com *[image: Facebook]* > *[image: Twitter]* > *[image: LinkedIn]* > > > > > > > *From:* Sukchan Lee > *Sent:* Saturday, March 28, 2020 7:58 PM > *To:* david at ispsupplies.com > *Cc:* nextepc at lists.osmocom.org > *Subject:* Re: Reject message > > > > Even though UE try to connect without APN, if you set the first > APN(default APN) to the mongoDB, open5gs won't reject the UE request. If > the problem is still not resolved, I need your pcap file to fix the issue. > > > > On Fri, Mar 27, 2020 at 12:10 PM wrote: > > I figured out what was going on, so perhaps there is a solution already in > place. By default the Baicells UE do not request a specific APN. That > causes the EPC to reject the request. > > > > [image: ISP Supplies] > > > [image: cid:image002.jpg at 01D5B005.DEE3BE10] > > *David Peterson* > Senior Engineer > 855-947-7776 ext. 9214 > c 419-706-7355 > d 979-314-1305 > https://www.ispsupplies.com > > *[image: Facebook]* *[image: Twitter]* > *[image: LinkedIn]* > > > > > > > *From:* Sukchan Lee > *Sent:* Friday, March 27, 2020 11:57 AM > *To:* david at ispsupplies.com > *Cc:* nextepc at lists.osmocom.org > *Subject:* Re: Reject message > > > > Hi david, > > > > If pcap is provided, it is more easier to analyze your problem. > > > > BTW, from your log, I've found PDN connectivity reject with ESM_CAUSE:27. > > It means that UE APN is unknown in HSS. So, you need to match APN name > between UE and HSS. > > > > Thanks and regards, > > Sukchan > > > > On Tue, Mar 17, 2020 at 6:47 PM wrote: > > Does anyone know why I am getting this reject reason for network entry on > a UE? > > > > 03/17 16:56:55.026: [mme] DEBUG: [EMM] Authentication request > (../src/mme/nas-path.c:180) > > 03/17 16:56:55.026: [mme] DEBUG: IMSI[311980000033212] > (../src/mme/nas-path.c:181) > > 03/17 16:56:55.026: [mme] DEBUG: [MME] DownlinkNASTransport > (../src/mme/s1ap-build.c:186) > > 03/17 16:56:55.026: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-build.c:231) > > 03/17 16:56:55.026: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-path.c:79) > > 03/17 16:56:55.189: [mme] DEBUG: mme_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.189: [mme] DEBUG: s1ap_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/s1ap-sm.c:60) > > 03/17 16:56:55.189: [mme] DEBUG: [MME] Uplink NAS transport > (../src/mme/s1ap-handler.c:330) > > 03/17 16:56:55.189: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-handler.c:347) > > 03/17 16:56:55.189: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-handler.c:354) > > 03/17 16:56:55.189: [mme] DEBUG: mme_state_operational(): > MME_EVT_EMM_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.189: [emm] DEBUG: emm_state_authentication(): > MME_EVT_EMM_MESSAGE > > (../src/mme/emm-sm.c:488) > > 03/17 16:56:55.189: [emm] DEBUG: [EMM] Authentication response > (../src/mme/emm-sm.c:512) > > 03/17 16:56:55.189: [emm] DEBUG: IMSI[311980000033212] > (../src/mme/emm-sm.c:513) > > 03/17 16:56:55.189: [emm] DEBUG: emm_state_authentication(): EXIT > > (../src/mme/emm-sm.c:488) > > 03/17 16:56:55.189: [emm] DEBUG: emm_state_security_mode(): ENTRY > > (../src/mme/emm-sm.c:649) > > 03/17 16:56:55.189: [mme] DEBUG: [EMM] Security mode command > (../src/mme/nas-path.c:207) > > 03/17 16:56:55.189: [mme] DEBUG: IMSI[311980000033212] > (../src/mme/nas-path.c:208) > > 03/17 16:56:55.190: [emm] DEBUG: Replayed UE SEC[LEN:2 EEA:0xe0 > EIA:0xe0 UEA:0x0 UIA:0x0 GEA:0x0] (../src/mme/emm-build.c:287) > > 03/17 16:56:55.190: [emm] DEBUG: Selected[Integrity:0x1 Encrypt:0x0] > (../src/mme/emm-build.c:289) > > 03/17 16:56:55.190: [mme] DEBUG: [MME] DownlinkNASTransport > (../src/mme/s1ap-build.c:186) > > 03/17 16:56:55.190: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-build.c:231) > > 03/17 16:56:55.190: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-path.c:79) > > 03/17 16:56:55.229: [mme] DEBUG: mme_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.230: [mme] DEBUG: s1ap_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/s1ap-sm.c:60) > > 03/17 16:56:55.230: [mme] DEBUG: [MME] Uplink NAS transport > (../src/mme/s1ap-handler.c:330) > > 03/17 16:56:55.230: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-handler.c:347) > > 03/17 16:56:55.230: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-handler.c:354) > > 03/17 16:56:55.230: [mme] DEBUG: mme_state_operational(): > MME_EVT_EMM_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.230: [emm] DEBUG: emm_state_security_mode(): > MME_EVT_EMM_MESSAGE > > (../src/mme/emm-sm.c:649) > > 03/17 16:56:55.230: [emm] DEBUG: [EMM] Security mode complete > (../src/mme/emm-sm.c:676) > > 03/17 16:56:55.230: [emm] DEBUG: IMSI[311980000033212] > (../src/mme/emm-sm.c:677) > > 03/17 16:56:55.230: [mme] DEBUG: [MME] Update-Location-Request > (../src/mme/mme-fd-path.c:444) > > 03/17 16:56:55.231: [emm] DEBUG: emm_state_security_mode(): EXIT > > (../src/mme/emm-sm.c:649) > > 03/17 16:56:55.231: [emm] DEBUG: emm_state_initial_context_setup(): ENTRY > > (../src/mme/emm-sm.c:817) > > 03/17 16:56:55.234: [mme] DEBUG: [MME] Update-Location-Answer > (../src/mme/mme-fd-path.c:610) > > 03/17 16:56:55.234: [mme] DEBUG: Result Code: 2001 > (../src/mme/mme-fd-path.c:651) > > 03/17 16:56:55.234: [mme] DEBUG: From 'hss.localdomain' > (../src/mme/mme-fd-path.c:680) > > 03/17 16:56:55.234: [mme] DEBUG: ('localdomain') > (../src/mme/mme-fd-path.c:693) > > 03/17 16:56:55.234: [mme] DEBUG: mme_state_operational(): > MME_EVT_S6A_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.234: [mme] DEBUG: mme_state_operational(): > MME_EVT_ESM_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.234: [mme] DEBUG: mme_bearer_find_or_add_by_message() > [PTI:8, EBI:0] (../src/mme/mme-context.c:2847) > > 03/17 16:56:55.234: [esm] DEBUG: esm_state_initial(): ENTRY > > (../src/mme/esm-sm.c:38) > > 03/17 16:56:55.234: [esm] DEBUG: esm_state_inactive(): ENTRY > > (../src/mme/esm-sm.c:61) > > 03/17 16:56:55.234: [mme] INFO: Added a session. Number of sessions is now > 1 (../src/mme/mme-context.c:79) > > 03/17 16:56:55.234: [esm] DEBUG: esm_state_inactive(): MME_EVT_ESM_MESSAGE > > (../src/mme/esm-sm.c:61) > > 03/17 16:56:55.234: [esm] DEBUG: [ESM] PDN Connectivity request > (../src/mme/esm-sm.c:82) > > 03/17 16:56:55.234: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] > (../src/mme/esm-sm.c:84) > > 03/17 16:56:55.234: [esm] DEBUG: EIT(ESM information transfer)[1] > (../src/mme/esm-handler.c:59) > > 03/17 16:56:55.234: [esm] DEBUG: [ESM] ESM information request > (../src/mme/esm-build.c:75) > > 03/17 16:56:55.234: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] > (../src/mme/esm-build.c:77) > > 03/17 16:56:55.235: [mme] DEBUG: [MME] DownlinkNASTransport > (../src/mme/s1ap-build.c:186) > > 03/17 16:56:55.235: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-build.c:231) > > 03/17 16:56:55.235: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-path.c:79) > > 03/17 16:56:55.269: [mme] DEBUG: mme_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.270: [mme] DEBUG: s1ap_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/s1ap-sm.c:60) > > 03/17 16:56:55.270: [mme] DEBUG: [MME] Uplink NAS transport > (../src/mme/s1ap-handler.c:330) > > 03/17 16:56:55.270: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-handler.c:347) > > 03/17 16:56:55.270: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-handler.c:354) > > 03/17 16:56:55.270: [mme] DEBUG: mme_state_operational(): > MME_EVT_ESM_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.270: [mme] DEBUG: mme_bearer_find_or_add_by_message() > [PTI:8, EBI:0] (../src/mme/mme-context.c:2847) > > 03/17 16:56:55.270: [esm] DEBUG: esm_state_inactive(): MME_EVT_ESM_MESSAGE > > (../src/mme/esm-sm.c:61) > > 03/17 16:56:55.270: [esm] DEBUG: [ESM] ESM information response > (../src/mme/esm-sm.c:93) > > 03/17 16:56:55.270: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] > (../src/mme/esm-sm.c:95) > > 03/17 16:56:55.270: [mme] DEBUG: [EMM] Attach reject > (../src/mme/nas-path.c:134) > > 03/17 16:56:55.270: [mme] DEBUG: IMSI[311980000033212] Cause[8] > (../src/mme/nas-path.c:135) > > 03/17 16:56:55.270: [esm] DEBUG: [ESM] PDN connectivity reject > (../src/mme/esm-build.c:39) > > 03/17 16:56:55.270: [esm] DEBUG: IMSI[311980000033212] PTI[8] > Cause[27] (../src/mme/esm-build.c:41) > > 03/17 16:56:55.271: [mme] DEBUG: [MME] DownlinkNASTransport > (../src/mme/s1ap-build.c:186) > > 03/17 16:56:55.271: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-build.c:231) > > 03/17 16:56:55.271: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-path.c:79) > > 03/17 16:56:55.271: [esm] DEBUG: esm_state_inactive(): EXIT > > (../src/mme/esm-sm.c:61) > > 03/17 16:56:55.271: [esm] DEBUG: esm_state_exception(): ENTRY > > (../src/mme/esm-sm.c:345) > > 03/17 16:56:55.271: [mme] DEBUG: [MME] UE Context release command > (../src/mme/s1ap-path.c:285) > > 03/17 16:56:55.271: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-path.c:287) > > 03/17 16:56:55.271: [mme] DEBUG: Group[3] Cause[0] Action[3] Delay[0] > (../src/mme/s1ap-path.c:306) > > 03/17 16:56:55.271: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-path.c:79) > > 03/17 16:56:55.275: [mme] DEBUG: mme_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.275: [mme] DEBUG: s1ap_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/s1ap-sm.c:60) > > 03/17 16:56:55.275: [mme] DEBUG: [MME] UE Context release complete > (../src/mme/s1ap-handler.c:919) > > 03/17 16:56:55.276: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-handler.c:933) > > 03/17 16:56:55.276: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-handler.c:950) > > 03/17 16:56:55.276: [mme] DEBUG: Action: UE context remove() > (../src/mme/s1ap-handler.c:963) > > 03/17 16:56:55.276: [mme] INFO: Removed a UE. Number of UEs is now 0 > (../src/mme/mme-context.c:63) > > 03/17 16:56:55.276: [emm] DEBUG: emm_state_initial_context_setup(): EXIT > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 19640 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 701 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 420 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 444 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 441 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 444 bytes Desc: not available URL: From ganiyuabiolaaminat at gmail.com Sun Mar 29 18:26:20 2020 From: ganiyuabiolaaminat at gmail.com (Abiola Ganiyu) Date: Sun, 29 Mar 2020 19:26:20 +0100 Subject: Reject message References: <010d01d5fcac$ea022040$be0660c0$@ispsupplies.com> <025e01d60452$40a73e60$c1f5bb20$@ispsupplies.com> <001301d60560$97477410$c5d65c30$@ispsupplies.com> Message-ID: I have used baicells CPE and it got attached having used the default "internet" APN setting . On Sun, Mar 29, 2020, 19:24 Abiola Ganiyu wrote: > Hi David, > Baicells CPE has "internet" set as APN by default. > And you can make changes to the APN name under APN management field. > > > > > On Sun, Mar 29, 2020, 01:25 wrote: > >> I will get you a pcap. The UE actually don?t have an APN listed by >> default. >> >> >> >> [image: ISP Supplies] >> >> [image: cid:image002.jpg at 01D5B005.DEE3BE10] >> >> *David Peterson* >> Senior Engineer >> 855-947-7776 ext. 9214 >> c 419-706-7355 >> d 979-314-1305 >> https://www.ispsupplies.com *[image: Facebook]* >> *[image: Twitter]* >> *[image: LinkedIn]* >> >> >> >> >> >> >> *From:* Sukchan Lee >> *Sent:* Saturday, March 28, 2020 7:58 PM >> *To:* david at ispsupplies.com >> *Cc:* nextepc at lists.osmocom.org >> *Subject:* Re: Reject message >> >> >> >> Even though UE try to connect without APN, if you set the first >> APN(default APN) to the mongoDB, open5gs won't reject the UE request. If >> the problem is still not resolved, I need your pcap file to fix the issue. >> >> >> >> On Fri, Mar 27, 2020 at 12:10 PM wrote: >> >> I figured out what was going on, so perhaps there is a solution already >> in place. By default the Baicells UE do not request a specific APN. That >> causes the EPC to reject the request. >> >> >> >> [image: ISP Supplies] >> >> >> [image: cid:image002.jpg at 01D5B005.DEE3BE10] >> >> *David Peterson* >> Senior Engineer >> 855-947-7776 ext. 9214 >> c 419-706-7355 >> d 979-314-1305 >> https://www.ispsupplies.com >> >> *[image: Facebook]* *[image: >> Twitter]* *[image: LinkedIn]* >> >> >> >> >> >> >> *From:* Sukchan Lee >> *Sent:* Friday, March 27, 2020 11:57 AM >> *To:* david at ispsupplies.com >> *Cc:* nextepc at lists.osmocom.org >> *Subject:* Re: Reject message >> >> >> >> Hi david, >> >> >> >> If pcap is provided, it is more easier to analyze your problem. >> >> >> >> BTW, from your log, I've found PDN connectivity reject with ESM_CAUSE:27. >> >> It means that UE APN is unknown in HSS. So, you need to match APN name >> between UE and HSS. >> >> >> >> Thanks and regards, >> >> Sukchan >> >> >> >> On Tue, Mar 17, 2020 at 6:47 PM wrote: >> >> Does anyone know why I am getting this reject reason for network entry on >> a UE? >> >> >> >> 03/17 16:56:55.026: [mme] DEBUG: [EMM] Authentication request >> (../src/mme/nas-path.c:180) >> >> 03/17 16:56:55.026: [mme] DEBUG: IMSI[311980000033212] >> (../src/mme/nas-path.c:181) >> >> 03/17 16:56:55.026: [mme] DEBUG: [MME] DownlinkNASTransport >> (../src/mme/s1ap-build.c:186) >> >> 03/17 16:56:55.026: [mme] DEBUG: ENB_UE_S1AP_ID[41] >> MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) >> >> 03/17 16:56:55.026: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] >> (../src/mme/s1ap-path.c:79) >> >> 03/17 16:56:55.189: [mme] DEBUG: mme_state_operational(): >> MME_EVT_S1AP_MESSAGE >> >> (../src/mme/mme-sm.c:129) >> >> 03/17 16:56:55.189: [mme] DEBUG: s1ap_state_operational(): >> MME_EVT_S1AP_MESSAGE >> >> (../src/mme/s1ap-sm.c:60) >> >> 03/17 16:56:55.189: [mme] DEBUG: [MME] Uplink NAS transport >> (../src/mme/s1ap-handler.c:330) >> >> 03/17 16:56:55.189: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] >> (../src/mme/s1ap-handler.c:347) >> >> 03/17 16:56:55.189: [mme] DEBUG: ENB_UE_S1AP_ID[41] >> MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:354) >> >> 03/17 16:56:55.189: [mme] DEBUG: mme_state_operational(): >> MME_EVT_EMM_MESSAGE >> >> (../src/mme/mme-sm.c:129) >> >> 03/17 16:56:55.189: [emm] DEBUG: emm_state_authentication(): >> MME_EVT_EMM_MESSAGE >> >> (../src/mme/emm-sm.c:488) >> >> 03/17 16:56:55.189: [emm] DEBUG: [EMM] Authentication response >> (../src/mme/emm-sm.c:512) >> >> 03/17 16:56:55.189: [emm] DEBUG: IMSI[311980000033212] >> (../src/mme/emm-sm.c:513) >> >> 03/17 16:56:55.189: [emm] DEBUG: emm_state_authentication(): EXIT >> >> (../src/mme/emm-sm.c:488) >> >> 03/17 16:56:55.189: [emm] DEBUG: emm_state_security_mode(): ENTRY >> >> (../src/mme/emm-sm.c:649) >> >> 03/17 16:56:55.189: [mme] DEBUG: [EMM] Security mode command >> (../src/mme/nas-path.c:207) >> >> 03/17 16:56:55.189: [mme] DEBUG: IMSI[311980000033212] >> (../src/mme/nas-path.c:208) >> >> 03/17 16:56:55.190: [emm] DEBUG: Replayed UE SEC[LEN:2 EEA:0xe0 >> EIA:0xe0 UEA:0x0 UIA:0x0 GEA:0x0] (../src/mme/emm-build.c:287) >> >> 03/17 16:56:55.190: [emm] DEBUG: Selected[Integrity:0x1 Encrypt:0x0] >> (../src/mme/emm-build.c:289) >> >> 03/17 16:56:55.190: [mme] DEBUG: [MME] DownlinkNASTransport >> (../src/mme/s1ap-build.c:186) >> >> 03/17 16:56:55.190: [mme] DEBUG: ENB_UE_S1AP_ID[41] >> MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) >> >> 03/17 16:56:55.190: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] >> (../src/mme/s1ap-path.c:79) >> >> 03/17 16:56:55.229: [mme] DEBUG: mme_state_operational(): >> MME_EVT_S1AP_MESSAGE >> >> (../src/mme/mme-sm.c:129) >> >> 03/17 16:56:55.230: [mme] DEBUG: s1ap_state_operational(): >> MME_EVT_S1AP_MESSAGE >> >> (../src/mme/s1ap-sm.c:60) >> >> 03/17 16:56:55.230: [mme] DEBUG: [MME] Uplink NAS transport >> (../src/mme/s1ap-handler.c:330) >> >> 03/17 16:56:55.230: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] >> (../src/mme/s1ap-handler.c:347) >> >> 03/17 16:56:55.230: [mme] DEBUG: ENB_UE_S1AP_ID[41] >> MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:354) >> >> 03/17 16:56:55.230: [mme] DEBUG: mme_state_operational(): >> MME_EVT_EMM_MESSAGE >> >> (../src/mme/mme-sm.c:129) >> >> 03/17 16:56:55.230: [emm] DEBUG: emm_state_security_mode(): >> MME_EVT_EMM_MESSAGE >> >> (../src/mme/emm-sm.c:649) >> >> 03/17 16:56:55.230: [emm] DEBUG: [EMM] Security mode complete >> (../src/mme/emm-sm.c:676) >> >> 03/17 16:56:55.230: [emm] DEBUG: IMSI[311980000033212] >> (../src/mme/emm-sm.c:677) >> >> 03/17 16:56:55.230: [mme] DEBUG: [MME] Update-Location-Request >> (../src/mme/mme-fd-path.c:444) >> >> 03/17 16:56:55.231: [emm] DEBUG: emm_state_security_mode(): EXIT >> >> (../src/mme/emm-sm.c:649) >> >> 03/17 16:56:55.231: [emm] DEBUG: emm_state_initial_context_setup(): ENTRY >> >> (../src/mme/emm-sm.c:817) >> >> 03/17 16:56:55.234: [mme] DEBUG: [MME] Update-Location-Answer >> (../src/mme/mme-fd-path.c:610) >> >> 03/17 16:56:55.234: [mme] DEBUG: Result Code: 2001 >> (../src/mme/mme-fd-path.c:651) >> >> 03/17 16:56:55.234: [mme] DEBUG: From 'hss.localdomain' >> (../src/mme/mme-fd-path.c:680) >> >> 03/17 16:56:55.234: [mme] DEBUG: ('localdomain') >> (../src/mme/mme-fd-path.c:693) >> >> 03/17 16:56:55.234: [mme] DEBUG: mme_state_operational(): >> MME_EVT_S6A_MESSAGE >> >> (../src/mme/mme-sm.c:129) >> >> 03/17 16:56:55.234: [mme] DEBUG: mme_state_operational(): >> MME_EVT_ESM_MESSAGE >> >> (../src/mme/mme-sm.c:129) >> >> 03/17 16:56:55.234: [mme] DEBUG: mme_bearer_find_or_add_by_message() >> [PTI:8, EBI:0] (../src/mme/mme-context.c:2847) >> >> 03/17 16:56:55.234: [esm] DEBUG: esm_state_initial(): ENTRY >> >> (../src/mme/esm-sm.c:38) >> >> 03/17 16:56:55.234: [esm] DEBUG: esm_state_inactive(): ENTRY >> >> (../src/mme/esm-sm.c:61) >> >> 03/17 16:56:55.234: [mme] INFO: Added a session. Number of sessions is >> now 1 (../src/mme/mme-context.c:79) >> >> 03/17 16:56:55.234: [esm] DEBUG: esm_state_inactive(): MME_EVT_ESM_MESSAGE >> >> (../src/mme/esm-sm.c:61) >> >> 03/17 16:56:55.234: [esm] DEBUG: [ESM] PDN Connectivity request >> (../src/mme/esm-sm.c:82) >> >> 03/17 16:56:55.234: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] >> (../src/mme/esm-sm.c:84) >> >> 03/17 16:56:55.234: [esm] DEBUG: EIT(ESM information transfer)[1] >> (../src/mme/esm-handler.c:59) >> >> 03/17 16:56:55.234: [esm] DEBUG: [ESM] ESM information request >> (../src/mme/esm-build.c:75) >> >> 03/17 16:56:55.234: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] >> (../src/mme/esm-build.c:77) >> >> 03/17 16:56:55.235: [mme] DEBUG: [MME] DownlinkNASTransport >> (../src/mme/s1ap-build.c:186) >> >> 03/17 16:56:55.235: [mme] DEBUG: ENB_UE_S1AP_ID[41] >> MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) >> >> 03/17 16:56:55.235: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] >> (../src/mme/s1ap-path.c:79) >> >> 03/17 16:56:55.269: [mme] DEBUG: mme_state_operational(): >> MME_EVT_S1AP_MESSAGE >> >> (../src/mme/mme-sm.c:129) >> >> 03/17 16:56:55.270: [mme] DEBUG: s1ap_state_operational(): >> MME_EVT_S1AP_MESSAGE >> >> (../src/mme/s1ap-sm.c:60) >> >> 03/17 16:56:55.270: [mme] DEBUG: [MME] Uplink NAS transport >> (../src/mme/s1ap-handler.c:330) >> >> 03/17 16:56:55.270: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] >> (../src/mme/s1ap-handler.c:347) >> >> 03/17 16:56:55.270: [mme] DEBUG: ENB_UE_S1AP_ID[41] >> MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:354) >> >> 03/17 16:56:55.270: [mme] DEBUG: mme_state_operational(): >> MME_EVT_ESM_MESSAGE >> >> (../src/mme/mme-sm.c:129) >> >> 03/17 16:56:55.270: [mme] DEBUG: mme_bearer_find_or_add_by_message() >> [PTI:8, EBI:0] (../src/mme/mme-context.c:2847) >> >> 03/17 16:56:55.270: [esm] DEBUG: esm_state_inactive(): MME_EVT_ESM_MESSAGE >> >> (../src/mme/esm-sm.c:61) >> >> 03/17 16:56:55.270: [esm] DEBUG: [ESM] ESM information response >> (../src/mme/esm-sm.c:93) >> >> 03/17 16:56:55.270: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] >> (../src/mme/esm-sm.c:95) >> >> 03/17 16:56:55.270: [mme] DEBUG: [EMM] Attach reject >> (../src/mme/nas-path.c:134) >> >> 03/17 16:56:55.270: [mme] DEBUG: IMSI[311980000033212] Cause[8] >> (../src/mme/nas-path.c:135) >> >> 03/17 16:56:55.270: [esm] DEBUG: [ESM] PDN connectivity reject >> (../src/mme/esm-build.c:39) >> >> 03/17 16:56:55.270: [esm] DEBUG: IMSI[311980000033212] PTI[8] >> Cause[27] (../src/mme/esm-build.c:41) >> >> 03/17 16:56:55.271: [mme] DEBUG: [MME] DownlinkNASTransport >> (../src/mme/s1ap-build.c:186) >> >> 03/17 16:56:55.271: [mme] DEBUG: ENB_UE_S1AP_ID[41] >> MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) >> >> 03/17 16:56:55.271: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] >> (../src/mme/s1ap-path.c:79) >> >> 03/17 16:56:55.271: [esm] DEBUG: esm_state_inactive(): EXIT >> >> (../src/mme/esm-sm.c:61) >> >> 03/17 16:56:55.271: [esm] DEBUG: esm_state_exception(): ENTRY >> >> (../src/mme/esm-sm.c:345) >> >> 03/17 16:56:55.271: [mme] DEBUG: [MME] UE Context release command >> (../src/mme/s1ap-path.c:285) >> >> 03/17 16:56:55.271: [mme] DEBUG: ENB_UE_S1AP_ID[41] >> MME_UE_S1AP_ID[17] (../src/mme/s1ap-path.c:287) >> >> 03/17 16:56:55.271: [mme] DEBUG: Group[3] Cause[0] Action[3] Delay[0] >> (../src/mme/s1ap-path.c:306) >> >> 03/17 16:56:55.271: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] >> (../src/mme/s1ap-path.c:79) >> >> 03/17 16:56:55.275: [mme] DEBUG: mme_state_operational(): >> MME_EVT_S1AP_MESSAGE >> >> (../src/mme/mme-sm.c:129) >> >> 03/17 16:56:55.275: [mme] DEBUG: s1ap_state_operational(): >> MME_EVT_S1AP_MESSAGE >> >> (../src/mme/s1ap-sm.c:60) >> >> 03/17 16:56:55.275: [mme] DEBUG: [MME] UE Context release complete >> (../src/mme/s1ap-handler.c:919) >> >> 03/17 16:56:55.276: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] >> (../src/mme/s1ap-handler.c:933) >> >> 03/17 16:56:55.276: [mme] DEBUG: ENB_UE_S1AP_ID[41] >> MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:950) >> >> 03/17 16:56:55.276: [mme] DEBUG: Action: UE context remove() >> (../src/mme/s1ap-handler.c:963) >> >> 03/17 16:56:55.276: [mme] INFO: Removed a UE. Number of UEs is now 0 >> (../src/mme/mme-context.c:63) >> >> 03/17 16:56:55.276: [emm] DEBUG: emm_state_initial_context_setup(): EXIT >> >> >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 19640 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 701 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 420 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 444 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 441 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 19640 bytes Desc: not available URL: From david at ispsupplies.com Sun Mar 29 18:28:51 2020 From: david at ispsupplies.com (david at ispsupplies.com) Date: Sun, 29 Mar 2020 14:28:51 -0400 Subject: Reject message In-Reply-To: References: <010d01d5fcac$ea022040$be0660c0$@ispsupplies.com> <025e01d60452$40a73e60$c1f5bb20$@ispsupplies.com> <001301d60560$97477410$c5d65c30$@ispsupplies.com> Message-ID: <007c01d605f7$e660c190$b32244b0$@ispsupplies.com> I have used internet as the default and some of the UE still do not come online. Logging into the web interface it shows no APN listed. I am looking to not have to touch each UE if possible. David Peterson Senior Engineer 855-947-7776 ext. 9214 c 419-706-7355 d 979-314-1305 https://www.ispsupplies.com From: Abiola Ganiyu Sent: Sunday, March 29, 2020 2:25 PM To: david at ispsupplies.com Cc: Sukchan Lee ; nextepc at lists.osmocom.org Subject: Re: Reject message Hi David, Baicells CPE has "internet" set as APN by default. And you can make changes to the APN name under APN management field. On Sun, Mar 29, 2020, 01:25 > wrote: I will get you a pcap. The UE actually don?t have an APN listed by default. David Peterson Senior Engineer 855-947-7776 ext. 9214 c 419-706-7355 d 979-314-1305 https://www.ispsupplies.com From: Sukchan Lee > Sent: Saturday, March 28, 2020 7:58 PM To: david at ispsupplies.com Cc: nextepc at lists.osmocom.org Subject: Re: Reject message Even though UE try to connect without APN, if you set the first APN(default APN) to the mongoDB, open5gs won't reject the UE request. If the problem is still not resolved, I need your pcap file to fix the issue. On Fri, Mar 27, 2020 at 12:10 PM > wrote: I figured out what was going on, so perhaps there is a solution already in place. By default the Baicells UE do not request a specific APN. That causes the EPC to reject the request. David Peterson Senior Engineer 855-947-7776 ext. 9214 c 419-706-7355 d 979-314-1305 https://www.ispsupplies.com From: Sukchan Lee > Sent: Friday, March 27, 2020 11:57 AM To: david at ispsupplies.com Cc: nextepc at lists.osmocom.org Subject: Re: Reject message Hi david, If pcap is provided, it is more easier to analyze your problem. BTW, from your log, I've found PDN connectivity reject with ESM_CAUSE:27. It means that UE APN is unknown in HSS. So, you need to match APN name between UE and HSS. Thanks and regards, Sukchan On Tue, Mar 17, 2020 at 6:47 PM > wrote: Does anyone know why I am getting this reject reason for network entry on a UE? 03/17 16:56:55.026: [mme] DEBUG: [EMM] Authentication request (../src/mme/nas-path.c:180) 03/17 16:56:55.026: [mme] DEBUG: IMSI[311980000033212] (../src/mme/nas-path.c:181) 03/17 16:56:55.026: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.026: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.026: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.189: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.189: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.189: [mme] DEBUG: [MME] Uplink NAS transport (../src/mme/s1ap-handler.c:330) 03/17 16:56:55.189: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:347) 03/17 16:56:55.189: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:354) 03/17 16:56:55.189: [mme] DEBUG: mme_state_operational(): MME_EVT_EMM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.189: [emm] DEBUG: emm_state_authentication(): MME_EVT_EMM_MESSAGE (../src/mme/emm-sm.c:488) 03/17 16:56:55.189: [emm] DEBUG: [EMM] Authentication response (../src/mme/emm-sm.c:512) 03/17 16:56:55.189: [emm] DEBUG: IMSI[311980000033212] (../src/mme/emm-sm.c:513) 03/17 16:56:55.189: [emm] DEBUG: emm_state_authentication(): EXIT (../src/mme/emm-sm.c:488) 03/17 16:56:55.189: [emm] DEBUG: emm_state_security_mode(): ENTRY (../src/mme/emm-sm.c:649) 03/17 16:56:55.189: [mme] DEBUG: [EMM] Security mode command (../src/mme/nas-path.c:207) 03/17 16:56:55.189: [mme] DEBUG: IMSI[311980000033212] (../src/mme/nas-path.c:208) 03/17 16:56:55.190: [emm] DEBUG: Replayed UE SEC[LEN:2 EEA:0xe0 EIA:0xe0 UEA:0x0 UIA:0x0 GEA:0x0] (../src/mme/emm-build.c:287) 03/17 16:56:55.190: [emm] DEBUG: Selected[Integrity:0x1 Encrypt:0x0] (../src/mme/emm-build.c:289) 03/17 16:56:55.190: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.190: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.190: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.229: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.230: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.230: [mme] DEBUG: [MME] Uplink NAS transport (../src/mme/s1ap-handler.c:330) 03/17 16:56:55.230: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:347) 03/17 16:56:55.230: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:354) 03/17 16:56:55.230: [mme] DEBUG: mme_state_operational(): MME_EVT_EMM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.230: [emm] DEBUG: emm_state_security_mode(): MME_EVT_EMM_MESSAGE (../src/mme/emm-sm.c:649) 03/17 16:56:55.230: [emm] DEBUG: [EMM] Security mode complete (../src/mme/emm-sm.c:676) 03/17 16:56:55.230: [emm] DEBUG: IMSI[311980000033212] (../src/mme/emm-sm.c:677) 03/17 16:56:55.230: [mme] DEBUG: [MME] Update-Location-Request (../src/mme/mme-fd-path.c:444) 03/17 16:56:55.231: [emm] DEBUG: emm_state_security_mode(): EXIT (../src/mme/emm-sm.c:649) 03/17 16:56:55.231: [emm] DEBUG: emm_state_initial_context_setup(): ENTRY (../src/mme/emm-sm.c:817) 03/17 16:56:55.234: [mme] DEBUG: [MME] Update-Location-Answer (../src/mme/mme-fd-path.c:610) 03/17 16:56:55.234: [mme] DEBUG: Result Code: 2001 (../src/mme/mme-fd-path.c:651) 03/17 16:56:55.234: [mme] DEBUG: From 'hss.localdomain' (../src/mme/mme-fd-path.c:680) 03/17 16:56:55.234: [mme] DEBUG: ('localdomain') (../src/mme/mme-fd-path.c:693) 03/17 16:56:55.234: [mme] DEBUG: mme_state_operational(): MME_EVT_S6A_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.234: [mme] DEBUG: mme_state_operational(): MME_EVT_ESM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.234: [mme] DEBUG: mme_bearer_find_or_add_by_message() [PTI:8, EBI:0] (../src/mme/mme-context.c:2847) 03/17 16:56:55.234: [esm] DEBUG: esm_state_initial(): ENTRY (../src/mme/esm-sm.c:38) 03/17 16:56:55.234: [esm] DEBUG: esm_state_inactive(): ENTRY (../src/mme/esm-sm.c:61) 03/17 16:56:55.234: [mme] INFO: Added a session. Number of sessions is now 1 (../src/mme/mme-context.c:79) 03/17 16:56:55.234: [esm] DEBUG: esm_state_inactive(): MME_EVT_ESM_MESSAGE (../src/mme/esm-sm.c:61) 03/17 16:56:55.234: [esm] DEBUG: [ESM] PDN Connectivity request (../src/mme/esm-sm.c:82) 03/17 16:56:55.234: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] (../src/mme/esm-sm.c:84) 03/17 16:56:55.234: [esm] DEBUG: EIT(ESM information transfer)[1] (../src/mme/esm-handler.c:59) 03/17 16:56:55.234: [esm] DEBUG: [ESM] ESM information request (../src/mme/esm-build.c:75) 03/17 16:56:55.234: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] (../src/mme/esm-build.c:77) 03/17 16:56:55.235: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.235: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.235: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.269: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.270: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.270: [mme] DEBUG: [MME] Uplink NAS transport (../src/mme/s1ap-handler.c:330) 03/17 16:56:55.270: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:347) 03/17 16:56:55.270: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:354) 03/17 16:56:55.270: [mme] DEBUG: mme_state_operational(): MME_EVT_ESM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.270: [mme] DEBUG: mme_bearer_find_or_add_by_message() [PTI:8, EBI:0] (../src/mme/mme-context.c:2847) 03/17 16:56:55.270: [esm] DEBUG: esm_state_inactive(): MME_EVT_ESM_MESSAGE (../src/mme/esm-sm.c:61) 03/17 16:56:55.270: [esm] DEBUG: [ESM] ESM information response (../src/mme/esm-sm.c:93) 03/17 16:56:55.270: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] (../src/mme/esm-sm.c:95) 03/17 16:56:55.270: [mme] DEBUG: [EMM] Attach reject (../src/mme/nas-path.c:134) 03/17 16:56:55.270: [mme] DEBUG: IMSI[311980000033212] Cause[8] (../src/mme/nas-path.c:135) 03/17 16:56:55.270: [esm] DEBUG: [ESM] PDN connectivity reject (../src/mme/esm-build.c:39) 03/17 16:56:55.270: [esm] DEBUG: IMSI[311980000033212] PTI[8] Cause[27] (../src/mme/esm-build.c:41) 03/17 16:56:55.271: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.271: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.271: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.271: [esm] DEBUG: esm_state_inactive(): EXIT (../src/mme/esm-sm.c:61) 03/17 16:56:55.271: [esm] DEBUG: esm_state_exception(): ENTRY (../src/mme/esm-sm.c:345) 03/17 16:56:55.271: [mme] DEBUG: [MME] UE Context release command (../src/mme/s1ap-path.c:285) 03/17 16:56:55.271: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-path.c:287) 03/17 16:56:55.271: [mme] DEBUG: Group[3] Cause[0] Action[3] Delay[0] (../src/mme/s1ap-path.c:306) 03/17 16:56:55.271: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.275: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.275: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.275: [mme] DEBUG: [MME] UE Context release complete (../src/mme/s1ap-handler.c:919) 03/17 16:56:55.276: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:933) 03/17 16:56:55.276: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:950) 03/17 16:56:55.276: [mme] DEBUG: Action: UE context remove() (../src/mme/s1ap-handler.c:963) 03/17 16:56:55.276: [mme] INFO: Removed a UE. Number of UEs is now 0 (../src/mme/mme-context.c:63) 03/17 16:56:55.276: [emm] DEBUG: emm_state_initial_context_setup(): EXIT -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 19638 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 701 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 420 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 444 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 441 bytes Desc: not available URL: From david at ispsupplies.com Sun Mar 29 18:37:26 2020 From: david at ispsupplies.com (david at ispsupplies.com) Date: Sun, 29 Mar 2020 14:37:26 -0400 Subject: Reject message In-Reply-To: References: <010d01d5fcac$ea022040$be0660c0$@ispsupplies.com> <025e01d60452$40a73e60$c1f5bb20$@ispsupplies.com> <001301d60560$97477410$c5d65c30$@ispsupplies.com> Message-ID: <009101d605f9$197b39b0$4c71ad10$@ispsupplies.com> I believe the issue is with some UE not all of them. Unfortunately there are a lot out there I have to deal with. David Peterson Senior Engineer 855-947-7776 ext. 9214 c 419-706-7355 d 979-314-1305 https://www.ispsupplies.com From: Abiola Ganiyu Sent: Sunday, March 29, 2020 2:26 PM To: david at ispsupplies.com Cc: Sukchan Lee ; nextepc at lists.osmocom.org Subject: Re: Reject message I have used baicells CPE and it got attached having used the default "internet" APN setting . On Sun, Mar 29, 2020, 19:24 Abiola Ganiyu > wrote: Hi David, Baicells CPE has "internet" set as APN by default. And you can make changes to the APN name under APN management field. On Sun, Mar 29, 2020, 01:25 > wrote: I will get you a pcap. The UE actually don?t have an APN listed by default. David Peterson Senior Engineer 855-947-7776 ext. 9214 c 419-706-7355 d 979-314-1305 https://www.ispsupplies.com From: Sukchan Lee > Sent: Saturday, March 28, 2020 7:58 PM To: david at ispsupplies.com Cc: nextepc at lists.osmocom.org Subject: Re: Reject message Even though UE try to connect without APN, if you set the first APN(default APN) to the mongoDB, open5gs won't reject the UE request. If the problem is still not resolved, I need your pcap file to fix the issue. On Fri, Mar 27, 2020 at 12:10 PM > wrote: I figured out what was going on, so perhaps there is a solution already in place. By default the Baicells UE do not request a specific APN. That causes the EPC to reject the request. David Peterson Senior Engineer 855-947-7776 ext. 9214 c 419-706-7355 d 979-314-1305 https://www.ispsupplies.com From: Sukchan Lee > Sent: Friday, March 27, 2020 11:57 AM To: david at ispsupplies.com Cc: nextepc at lists.osmocom.org Subject: Re: Reject message Hi david, If pcap is provided, it is more easier to analyze your problem. BTW, from your log, I've found PDN connectivity reject with ESM_CAUSE:27. It means that UE APN is unknown in HSS. So, you need to match APN name between UE and HSS. Thanks and regards, Sukchan On Tue, Mar 17, 2020 at 6:47 PM > wrote: Does anyone know why I am getting this reject reason for network entry on a UE? 03/17 16:56:55.026: [mme] DEBUG: [EMM] Authentication request (../src/mme/nas-path.c:180) 03/17 16:56:55.026: [mme] DEBUG: IMSI[311980000033212] (../src/mme/nas-path.c:181) 03/17 16:56:55.026: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.026: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.026: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.189: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.189: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.189: [mme] DEBUG: [MME] Uplink NAS transport (../src/mme/s1ap-handler.c:330) 03/17 16:56:55.189: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:347) 03/17 16:56:55.189: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:354) 03/17 16:56:55.189: [mme] DEBUG: mme_state_operational(): MME_EVT_EMM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.189: [emm] DEBUG: emm_state_authentication(): MME_EVT_EMM_MESSAGE (../src/mme/emm-sm.c:488) 03/17 16:56:55.189: [emm] DEBUG: [EMM] Authentication response (../src/mme/emm-sm.c:512) 03/17 16:56:55.189: [emm] DEBUG: IMSI[311980000033212] (../src/mme/emm-sm.c:513) 03/17 16:56:55.189: [emm] DEBUG: emm_state_authentication(): EXIT (../src/mme/emm-sm.c:488) 03/17 16:56:55.189: [emm] DEBUG: emm_state_security_mode(): ENTRY (../src/mme/emm-sm.c:649) 03/17 16:56:55.189: [mme] DEBUG: [EMM] Security mode command (../src/mme/nas-path.c:207) 03/17 16:56:55.189: [mme] DEBUG: IMSI[311980000033212] (../src/mme/nas-path.c:208) 03/17 16:56:55.190: [emm] DEBUG: Replayed UE SEC[LEN:2 EEA:0xe0 EIA:0xe0 UEA:0x0 UIA:0x0 GEA:0x0] (../src/mme/emm-build.c:287) 03/17 16:56:55.190: [emm] DEBUG: Selected[Integrity:0x1 Encrypt:0x0] (../src/mme/emm-build.c:289) 03/17 16:56:55.190: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.190: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.190: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.229: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.230: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.230: [mme] DEBUG: [MME] Uplink NAS transport (../src/mme/s1ap-handler.c:330) 03/17 16:56:55.230: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:347) 03/17 16:56:55.230: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:354) 03/17 16:56:55.230: [mme] DEBUG: mme_state_operational(): MME_EVT_EMM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.230: [emm] DEBUG: emm_state_security_mode(): MME_EVT_EMM_MESSAGE (../src/mme/emm-sm.c:649) 03/17 16:56:55.230: [emm] DEBUG: [EMM] Security mode complete (../src/mme/emm-sm.c:676) 03/17 16:56:55.230: [emm] DEBUG: IMSI[311980000033212] (../src/mme/emm-sm.c:677) 03/17 16:56:55.230: [mme] DEBUG: [MME] Update-Location-Request (../src/mme/mme-fd-path.c:444) 03/17 16:56:55.231: [emm] DEBUG: emm_state_security_mode(): EXIT (../src/mme/emm-sm.c:649) 03/17 16:56:55.231: [emm] DEBUG: emm_state_initial_context_setup(): ENTRY (../src/mme/emm-sm.c:817) 03/17 16:56:55.234: [mme] DEBUG: [MME] Update-Location-Answer (../src/mme/mme-fd-path.c:610) 03/17 16:56:55.234: [mme] DEBUG: Result Code: 2001 (../src/mme/mme-fd-path.c:651) 03/17 16:56:55.234: [mme] DEBUG: From 'hss.localdomain' (../src/mme/mme-fd-path.c:680) 03/17 16:56:55.234: [mme] DEBUG: ('localdomain') (../src/mme/mme-fd-path.c:693) 03/17 16:56:55.234: [mme] DEBUG: mme_state_operational(): MME_EVT_S6A_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.234: [mme] DEBUG: mme_state_operational(): MME_EVT_ESM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.234: [mme] DEBUG: mme_bearer_find_or_add_by_message() [PTI:8, EBI:0] (../src/mme/mme-context.c:2847) 03/17 16:56:55.234: [esm] DEBUG: esm_state_initial(): ENTRY (../src/mme/esm-sm.c:38) 03/17 16:56:55.234: [esm] DEBUG: esm_state_inactive(): ENTRY (../src/mme/esm-sm.c:61) 03/17 16:56:55.234: [mme] INFO: Added a session. Number of sessions is now 1 (../src/mme/mme-context.c:79) 03/17 16:56:55.234: [esm] DEBUG: esm_state_inactive(): MME_EVT_ESM_MESSAGE (../src/mme/esm-sm.c:61) 03/17 16:56:55.234: [esm] DEBUG: [ESM] PDN Connectivity request (../src/mme/esm-sm.c:82) 03/17 16:56:55.234: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] (../src/mme/esm-sm.c:84) 03/17 16:56:55.234: [esm] DEBUG: EIT(ESM information transfer)[1] (../src/mme/esm-handler.c:59) 03/17 16:56:55.234: [esm] DEBUG: [ESM] ESM information request (../src/mme/esm-build.c:75) 03/17 16:56:55.234: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] (../src/mme/esm-build.c:77) 03/17 16:56:55.235: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.235: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.235: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.269: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.270: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.270: [mme] DEBUG: [MME] Uplink NAS transport (../src/mme/s1ap-handler.c:330) 03/17 16:56:55.270: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:347) 03/17 16:56:55.270: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:354) 03/17 16:56:55.270: [mme] DEBUG: mme_state_operational(): MME_EVT_ESM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.270: [mme] DEBUG: mme_bearer_find_or_add_by_message() [PTI:8, EBI:0] (../src/mme/mme-context.c:2847) 03/17 16:56:55.270: [esm] DEBUG: esm_state_inactive(): MME_EVT_ESM_MESSAGE (../src/mme/esm-sm.c:61) 03/17 16:56:55.270: [esm] DEBUG: [ESM] ESM information response (../src/mme/esm-sm.c:93) 03/17 16:56:55.270: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] (../src/mme/esm-sm.c:95) 03/17 16:56:55.270: [mme] DEBUG: [EMM] Attach reject (../src/mme/nas-path.c:134) 03/17 16:56:55.270: [mme] DEBUG: IMSI[311980000033212] Cause[8] (../src/mme/nas-path.c:135) 03/17 16:56:55.270: [esm] DEBUG: [ESM] PDN connectivity reject (../src/mme/esm-build.c:39) 03/17 16:56:55.270: [esm] DEBUG: IMSI[311980000033212] PTI[8] Cause[27] (../src/mme/esm-build.c:41) 03/17 16:56:55.271: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.271: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.271: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.271: [esm] DEBUG: esm_state_inactive(): EXIT (../src/mme/esm-sm.c:61) 03/17 16:56:55.271: [esm] DEBUG: esm_state_exception(): ENTRY (../src/mme/esm-sm.c:345) 03/17 16:56:55.271: [mme] DEBUG: [MME] UE Context release command (../src/mme/s1ap-path.c:285) 03/17 16:56:55.271: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-path.c:287) 03/17 16:56:55.271: [mme] DEBUG: Group[3] Cause[0] Action[3] Delay[0] (../src/mme/s1ap-path.c:306) 03/17 16:56:55.271: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.275: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.275: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.275: [mme] DEBUG: [MME] UE Context release complete (../src/mme/s1ap-handler.c:919) 03/17 16:56:55.276: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:933) 03/17 16:56:55.276: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:950) 03/17 16:56:55.276: [mme] DEBUG: Action: UE context remove() (../src/mme/s1ap-handler.c:963) 03/17 16:56:55.276: [mme] INFO: Removed a UE. Number of UEs is now 0 (../src/mme/mme-context.c:63) 03/17 16:56:55.276: [emm] DEBUG: emm_state_initial_context_setup(): EXIT -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 19638 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 701 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 420 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 444 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 441 bytes Desc: not available URL: From ganiyuabiolaaminat at gmail.com Sun Mar 29 18:40:24 2020 From: ganiyuabiolaaminat at gmail.com (Abiola Ganiyu) Date: Sun, 29 Mar 2020 19:40:24 +0100 Subject: Reject message In-Reply-To: <009101d605f9$197b39b0$4c71ad10$@ispsupplies.com> References: <010d01d5fcac$ea022040$be0660c0$@ispsupplies.com> <025e01d60452$40a73e60$c1f5bb20$@ispsupplies.com> <001301d60560$97477410$c5d65c30$@ispsupplies.com> <009101d605f9$197b39b0$4c71ad10$@ispsupplies.com> Message-ID: Have you tried to upgrade the firmware of the CPE. I have known baicells CPE to work better after upgrade. You can use any CPE for your test. Just to be sure that it's not a CPE issue. I can recommend blinQ and Airspan CPEs On Sun, Mar 29, 2020, 19:37 wrote: > I believe the issue is with some UE not all of them. Unfortunately there > are a lot out there I have to deal with. > > > > [image: ISP Supplies] > > [image: cid:image002.jpg at 01D5B005.DEE3BE10] > > *David Peterson* > Senior Engineer > 855-947-7776 ext. 9214 > c 419-706-7355 > d 979-314-1305 > https://www.ispsupplies.com *[image: Facebook]* > *[image: Twitter]* > *[image: LinkedIn]* > > > > > > > *From:* Abiola Ganiyu > *Sent:* Sunday, March 29, 2020 2:26 PM > *To:* david at ispsupplies.com > *Cc:* Sukchan Lee ; nextepc at lists.osmocom.org > *Subject:* Re: Reject message > > > > I have used baicells CPE and it got attached having used the default > "internet" APN setting . > > > > On Sun, Mar 29, 2020, 19:24 Abiola Ganiyu > wrote: > > Hi David, > > Baicells CPE has "internet" set as APN by default. > > And you can make changes to the APN name under APN management field. > > > > > > > > > > On Sun, Mar 29, 2020, 01:25 wrote: > > I will get you a pcap. The UE actually don?t have an APN listed by > default. > > > > [image: ISP Supplies] > > > [image: cid:image002.jpg at 01D5B005.DEE3BE10] > > *David Peterson* > Senior Engineer > 855-947-7776 ext. 9214 > c 419-706-7355 > d 979-314-1305 > https://www.ispsupplies.com > > *[image: Facebook]* *[image: Twitter]* > *[image: LinkedIn]* > > > > > > > *From:* Sukchan Lee > *Sent:* Saturday, March 28, 2020 7:58 PM > *To:* david at ispsupplies.com > *Cc:* nextepc at lists.osmocom.org > *Subject:* Re: Reject message > > > > Even though UE try to connect without APN, if you set the first > APN(default APN) to the mongoDB, open5gs won't reject the UE request. If > the problem is still not resolved, I need your pcap file to fix the issue. > > > > On Fri, Mar 27, 2020 at 12:10 PM wrote: > > I figured out what was going on, so perhaps there is a solution already in > place. By default the Baicells UE do not request a specific APN. That > causes the EPC to reject the request. > > > > [image: ISP Supplies] > > > [image: cid:image002.jpg at 01D5B005.DEE3BE10] > > *David Peterson* > Senior Engineer > 855-947-7776 ext. 9214 > c 419-706-7355 > d 979-314-1305 > https://www.ispsupplies.com > > *[image: Facebook]* *[image: Twitter]* > *[image: LinkedIn]* > > > > > > > *From:* Sukchan Lee > *Sent:* Friday, March 27, 2020 11:57 AM > *To:* david at ispsupplies.com > *Cc:* nextepc at lists.osmocom.org > *Subject:* Re: Reject message > > > > Hi david, > > > > If pcap is provided, it is more easier to analyze your problem. > > > > BTW, from your log, I've found PDN connectivity reject with ESM_CAUSE:27. > > It means that UE APN is unknown in HSS. So, you need to match APN name > between UE and HSS. > > > > Thanks and regards, > > Sukchan > > > > On Tue, Mar 17, 2020 at 6:47 PM wrote: > > Does anyone know why I am getting this reject reason for network entry on > a UE? > > > > 03/17 16:56:55.026: [mme] DEBUG: [EMM] Authentication request > (../src/mme/nas-path.c:180) > > 03/17 16:56:55.026: [mme] DEBUG: IMSI[311980000033212] > (../src/mme/nas-path.c:181) > > 03/17 16:56:55.026: [mme] DEBUG: [MME] DownlinkNASTransport > (../src/mme/s1ap-build.c:186) > > 03/17 16:56:55.026: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-build.c:231) > > 03/17 16:56:55.026: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-path.c:79) > > 03/17 16:56:55.189: [mme] DEBUG: mme_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.189: [mme] DEBUG: s1ap_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/s1ap-sm.c:60) > > 03/17 16:56:55.189: [mme] DEBUG: [MME] Uplink NAS transport > (../src/mme/s1ap-handler.c:330) > > 03/17 16:56:55.189: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-handler.c:347) > > 03/17 16:56:55.189: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-handler.c:354) > > 03/17 16:56:55.189: [mme] DEBUG: mme_state_operational(): > MME_EVT_EMM_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.189: [emm] DEBUG: emm_state_authentication(): > MME_EVT_EMM_MESSAGE > > (../src/mme/emm-sm.c:488) > > 03/17 16:56:55.189: [emm] DEBUG: [EMM] Authentication response > (../src/mme/emm-sm.c:512) > > 03/17 16:56:55.189: [emm] DEBUG: IMSI[311980000033212] > (../src/mme/emm-sm.c:513) > > 03/17 16:56:55.189: [emm] DEBUG: emm_state_authentication(): EXIT > > (../src/mme/emm-sm.c:488) > > 03/17 16:56:55.189: [emm] DEBUG: emm_state_security_mode(): ENTRY > > (../src/mme/emm-sm.c:649) > > 03/17 16:56:55.189: [mme] DEBUG: [EMM] Security mode command > (../src/mme/nas-path.c:207) > > 03/17 16:56:55.189: [mme] DEBUG: IMSI[311980000033212] > (../src/mme/nas-path.c:208) > > 03/17 16:56:55.190: [emm] DEBUG: Replayed UE SEC[LEN:2 EEA:0xe0 > EIA:0xe0 UEA:0x0 UIA:0x0 GEA:0x0] (../src/mme/emm-build.c:287) > > 03/17 16:56:55.190: [emm] DEBUG: Selected[Integrity:0x1 Encrypt:0x0] > (../src/mme/emm-build.c:289) > > 03/17 16:56:55.190: [mme] DEBUG: [MME] DownlinkNASTransport > (../src/mme/s1ap-build.c:186) > > 03/17 16:56:55.190: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-build.c:231) > > 03/17 16:56:55.190: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-path.c:79) > > 03/17 16:56:55.229: [mme] DEBUG: mme_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.230: [mme] DEBUG: s1ap_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/s1ap-sm.c:60) > > 03/17 16:56:55.230: [mme] DEBUG: [MME] Uplink NAS transport > (../src/mme/s1ap-handler.c:330) > > 03/17 16:56:55.230: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-handler.c:347) > > 03/17 16:56:55.230: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-handler.c:354) > > 03/17 16:56:55.230: [mme] DEBUG: mme_state_operational(): > MME_EVT_EMM_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.230: [emm] DEBUG: emm_state_security_mode(): > MME_EVT_EMM_MESSAGE > > (../src/mme/emm-sm.c:649) > > 03/17 16:56:55.230: [emm] DEBUG: [EMM] Security mode complete > (../src/mme/emm-sm.c:676) > > 03/17 16:56:55.230: [emm] DEBUG: IMSI[311980000033212] > (../src/mme/emm-sm.c:677) > > 03/17 16:56:55.230: [mme] DEBUG: [MME] Update-Location-Request > (../src/mme/mme-fd-path.c:444) > > 03/17 16:56:55.231: [emm] DEBUG: emm_state_security_mode(): EXIT > > (../src/mme/emm-sm.c:649) > > 03/17 16:56:55.231: [emm] DEBUG: emm_state_initial_context_setup(): ENTRY > > (../src/mme/emm-sm.c:817) > > 03/17 16:56:55.234: [mme] DEBUG: [MME] Update-Location-Answer > (../src/mme/mme-fd-path.c:610) > > 03/17 16:56:55.234: [mme] DEBUG: Result Code: 2001 > (../src/mme/mme-fd-path.c:651) > > 03/17 16:56:55.234: [mme] DEBUG: From 'hss.localdomain' > (../src/mme/mme-fd-path.c:680) > > 03/17 16:56:55.234: [mme] DEBUG: ('localdomain') > (../src/mme/mme-fd-path.c:693) > > 03/17 16:56:55.234: [mme] DEBUG: mme_state_operational(): > MME_EVT_S6A_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.234: [mme] DEBUG: mme_state_operational(): > MME_EVT_ESM_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.234: [mme] DEBUG: mme_bearer_find_or_add_by_message() > [PTI:8, EBI:0] (../src/mme/mme-context.c:2847) > > 03/17 16:56:55.234: [esm] DEBUG: esm_state_initial(): ENTRY > > (../src/mme/esm-sm.c:38) > > 03/17 16:56:55.234: [esm] DEBUG: esm_state_inactive(): ENTRY > > (../src/mme/esm-sm.c:61) > > 03/17 16:56:55.234: [mme] INFO: Added a session. Number of sessions is now > 1 (../src/mme/mme-context.c:79) > > 03/17 16:56:55.234: [esm] DEBUG: esm_state_inactive(): MME_EVT_ESM_MESSAGE > > (../src/mme/esm-sm.c:61) > > 03/17 16:56:55.234: [esm] DEBUG: [ESM] PDN Connectivity request > (../src/mme/esm-sm.c:82) > > 03/17 16:56:55.234: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] > (../src/mme/esm-sm.c:84) > > 03/17 16:56:55.234: [esm] DEBUG: EIT(ESM information transfer)[1] > (../src/mme/esm-handler.c:59) > > 03/17 16:56:55.234: [esm] DEBUG: [ESM] ESM information request > (../src/mme/esm-build.c:75) > > 03/17 16:56:55.234: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] > (../src/mme/esm-build.c:77) > > 03/17 16:56:55.235: [mme] DEBUG: [MME] DownlinkNASTransport > (../src/mme/s1ap-build.c:186) > > 03/17 16:56:55.235: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-build.c:231) > > 03/17 16:56:55.235: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-path.c:79) > > 03/17 16:56:55.269: [mme] DEBUG: mme_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.270: [mme] DEBUG: s1ap_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/s1ap-sm.c:60) > > 03/17 16:56:55.270: [mme] DEBUG: [MME] Uplink NAS transport > (../src/mme/s1ap-handler.c:330) > > 03/17 16:56:55.270: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-handler.c:347) > > 03/17 16:56:55.270: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-handler.c:354) > > 03/17 16:56:55.270: [mme] DEBUG: mme_state_operational(): > MME_EVT_ESM_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.270: [mme] DEBUG: mme_bearer_find_or_add_by_message() > [PTI:8, EBI:0] (../src/mme/mme-context.c:2847) > > 03/17 16:56:55.270: [esm] DEBUG: esm_state_inactive(): MME_EVT_ESM_MESSAGE > > (../src/mme/esm-sm.c:61) > > 03/17 16:56:55.270: [esm] DEBUG: [ESM] ESM information response > (../src/mme/esm-sm.c:93) > > 03/17 16:56:55.270: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] > (../src/mme/esm-sm.c:95) > > 03/17 16:56:55.270: [mme] DEBUG: [EMM] Attach reject > (../src/mme/nas-path.c:134) > > 03/17 16:56:55.270: [mme] DEBUG: IMSI[311980000033212] Cause[8] > (../src/mme/nas-path.c:135) > > 03/17 16:56:55.270: [esm] DEBUG: [ESM] PDN connectivity reject > (../src/mme/esm-build.c:39) > > 03/17 16:56:55.270: [esm] DEBUG: IMSI[311980000033212] PTI[8] > Cause[27] (../src/mme/esm-build.c:41) > > 03/17 16:56:55.271: [mme] DEBUG: [MME] DownlinkNASTransport > (../src/mme/s1ap-build.c:186) > > 03/17 16:56:55.271: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-build.c:231) > > 03/17 16:56:55.271: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-path.c:79) > > 03/17 16:56:55.271: [esm] DEBUG: esm_state_inactive(): EXIT > > (../src/mme/esm-sm.c:61) > > 03/17 16:56:55.271: [esm] DEBUG: esm_state_exception(): ENTRY > > (../src/mme/esm-sm.c:345) > > 03/17 16:56:55.271: [mme] DEBUG: [MME] UE Context release command > (../src/mme/s1ap-path.c:285) > > 03/17 16:56:55.271: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-path.c:287) > > 03/17 16:56:55.271: [mme] DEBUG: Group[3] Cause[0] Action[3] Delay[0] > (../src/mme/s1ap-path.c:306) > > 03/17 16:56:55.271: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-path.c:79) > > 03/17 16:56:55.275: [mme] DEBUG: mme_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/mme-sm.c:129) > > 03/17 16:56:55.275: [mme] DEBUG: s1ap_state_operational(): > MME_EVT_S1AP_MESSAGE > > (../src/mme/s1ap-sm.c:60) > > 03/17 16:56:55.275: [mme] DEBUG: [MME] UE Context release complete > (../src/mme/s1ap-handler.c:919) > > 03/17 16:56:55.276: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] > (../src/mme/s1ap-handler.c:933) > > 03/17 16:56:55.276: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] > (../src/mme/s1ap-handler.c:950) > > 03/17 16:56:55.276: [mme] DEBUG: Action: UE context remove() > (../src/mme/s1ap-handler.c:963) > > 03/17 16:56:55.276: [mme] INFO: Removed a UE. Number of UEs is now 0 > (../src/mme/mme-context.c:63) > > 03/17 16:56:55.276: [emm] DEBUG: emm_state_initial_context_setup(): EXIT > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 19640 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 701 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 420 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 444 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 441 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 441 bytes Desc: not available URL: From david at ispsupplies.com Sun Mar 29 18:45:07 2020 From: david at ispsupplies.com (david at ispsupplies.com) Date: Sun, 29 Mar 2020 14:45:07 -0400 Subject: Reject message In-Reply-To: References: <010d01d5fcac$ea022040$be0660c0$@ispsupplies.com> <025e01d60452$40a73e60$c1f5bb20$@ispsupplies.com> <001301d60560$97477410$c5d65c30$@ispsupplies.com> <009101d605f9$197b39b0$4c71ad10$@ispsupplies.com> Message-ID: <00a401d605fa$2bfb7130$83f25390$@ispsupplies.com> Yeah no luck there. Other operators have mentioned this to me in the past. David Peterson Senior Engineer 855-947-7776 ext. 9214 c 419-706-7355 d 979-314-1305 https://www.ispsupplies.com From: Abiola Ganiyu Sent: Sunday, March 29, 2020 2:40 PM To: david at ispsupplies.com Cc: Sukchan Lee ; nextepc at lists.osmocom.org Subject: Re: Reject message Have you tried to upgrade the firmware of the CPE. I have known baicells CPE to work better after upgrade. You can use any CPE for your test. Just to be sure that it's not a CPE issue. I can recommend blinQ and Airspan CPEs On Sun, Mar 29, 2020, 19:37 > wrote: I believe the issue is with some UE not all of them. Unfortunately there are a lot out there I have to deal with. David Peterson Senior Engineer 855-947-7776 ext. 9214 c 419-706-7355 d 979-314-1305 https://www.ispsupplies.com From: Abiola Ganiyu > Sent: Sunday, March 29, 2020 2:26 PM To: david at ispsupplies.com Cc: Sukchan Lee >; nextepc at lists.osmocom.org Subject: Re: Reject message I have used baicells CPE and it got attached having used the default "internet" APN setting . On Sun, Mar 29, 2020, 19:24 Abiola Ganiyu > wrote: Hi David, Baicells CPE has "internet" set as APN by default. And you can make changes to the APN name under APN management field. On Sun, Mar 29, 2020, 01:25 > wrote: I will get you a pcap. The UE actually don?t have an APN listed by default. David Peterson Senior Engineer 855-947-7776 ext. 9214 c 419-706-7355 d 979-314-1305 https://www.ispsupplies.com From: Sukchan Lee Sent: Saturday, March 28, 2020 7:58 PM To: david at ispsupplies.com Cc: nextepc at lists.osmocom.org Subject: Re: Reject message Even though UE try to connect without APN, if you set the first APN(default APN) to the mongoDB, open5gs won't reject the UE request. If the problem is still not resolved, I need your pcap file to fix the issue. On Fri, Mar 27, 2020 at 12:10 PM wrote: I figured out what was going on, so perhaps there is a solution already in place. By default the Baicells UE do not request a specific APN. That causes the EPC to reject the request. David Peterson Senior Engineer 855-947-7776 ext. 9214 c 419-706-7355 d 979-314-1305 https://www.ispsupplies.com From: Sukchan Lee Sent: Friday, March 27, 2020 11:57 AM To: david at ispsupplies.com Cc: nextepc at lists.osmocom.org Subject: Re: Reject message Hi david, If pcap is provided, it is more easier to analyze your problem. BTW, from your log, I've found PDN connectivity reject with ESM_CAUSE:27. It means that UE APN is unknown in HSS. So, you need to match APN name between UE and HSS. Thanks and regards, Sukchan On Tue, Mar 17, 2020 at 6:47 PM wrote: Does anyone know why I am getting this reject reason for network entry on a UE? 03/17 16:56:55.026: [mme] DEBUG: [EMM] Authentication request (../src/mme/nas-path.c:180) 03/17 16:56:55.026: [mme] DEBUG: IMSI[311980000033212] (../src/mme/nas-path.c:181) 03/17 16:56:55.026: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.026: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.026: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.189: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.189: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.189: [mme] DEBUG: [MME] Uplink NAS transport (../src/mme/s1ap-handler.c:330) 03/17 16:56:55.189: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:347) 03/17 16:56:55.189: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:354) 03/17 16:56:55.189: [mme] DEBUG: mme_state_operational(): MME_EVT_EMM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.189: [emm] DEBUG: emm_state_authentication(): MME_EVT_EMM_MESSAGE (../src/mme/emm-sm.c:488) 03/17 16:56:55.189: [emm] DEBUG: [EMM] Authentication response (../src/mme/emm-sm.c:512) 03/17 16:56:55.189: [emm] DEBUG: IMSI[311980000033212] (../src/mme/emm-sm.c:513) 03/17 16:56:55.189: [emm] DEBUG: emm_state_authentication(): EXIT (../src/mme/emm-sm.c:488) 03/17 16:56:55.189: [emm] DEBUG: emm_state_security_mode(): ENTRY (../src/mme/emm-sm.c:649) 03/17 16:56:55.189: [mme] DEBUG: [EMM] Security mode command (../src/mme/nas-path.c:207) 03/17 16:56:55.189: [mme] DEBUG: IMSI[311980000033212] (../src/mme/nas-path.c:208) 03/17 16:56:55.190: [emm] DEBUG: Replayed UE SEC[LEN:2 EEA:0xe0 EIA:0xe0 UEA:0x0 UIA:0x0 GEA:0x0] (../src/mme/emm-build.c:287) 03/17 16:56:55.190: [emm] DEBUG: Selected[Integrity:0x1 Encrypt:0x0] (../src/mme/emm-build.c:289) 03/17 16:56:55.190: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.190: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.190: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.229: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.230: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.230: [mme] DEBUG: [MME] Uplink NAS transport (../src/mme/s1ap-handler.c:330) 03/17 16:56:55.230: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:347) 03/17 16:56:55.230: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:354) 03/17 16:56:55.230: [mme] DEBUG: mme_state_operational(): MME_EVT_EMM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.230: [emm] DEBUG: emm_state_security_mode(): MME_EVT_EMM_MESSAGE (../src/mme/emm-sm.c:649) 03/17 16:56:55.230: [emm] DEBUG: [EMM] Security mode complete (../src/mme/emm-sm.c:676) 03/17 16:56:55.230: [emm] DEBUG: IMSI[311980000033212] (../src/mme/emm-sm.c:677) 03/17 16:56:55.230: [mme] DEBUG: [MME] Update-Location-Request (../src/mme/mme-fd-path.c:444) 03/17 16:56:55.231: [emm] DEBUG: emm_state_security_mode(): EXIT (../src/mme/emm-sm.c:649) 03/17 16:56:55.231: [emm] DEBUG: emm_state_initial_context_setup(): ENTRY (../src/mme/emm-sm.c:817) 03/17 16:56:55.234: [mme] DEBUG: [MME] Update-Location-Answer (../src/mme/mme-fd-path.c:610) 03/17 16:56:55.234: [mme] DEBUG: Result Code: 2001 (../src/mme/mme-fd-path.c:651) 03/17 16:56:55.234: [mme] DEBUG: From 'hss.localdomain' (../src/mme/mme-fd-path.c:680) 03/17 16:56:55.234: [mme] DEBUG: ('localdomain') (../src/mme/mme-fd-path.c:693) 03/17 16:56:55.234: [mme] DEBUG: mme_state_operational(): MME_EVT_S6A_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.234: [mme] DEBUG: mme_state_operational(): MME_EVT_ESM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.234: [mme] DEBUG: mme_bearer_find_or_add_by_message() [PTI:8, EBI:0] (../src/mme/mme-context.c:2847) 03/17 16:56:55.234: [esm] DEBUG: esm_state_initial(): ENTRY (../src/mme/esm-sm.c:38) 03/17 16:56:55.234: [esm] DEBUG: esm_state_inactive(): ENTRY (../src/mme/esm-sm.c:61) 03/17 16:56:55.234: [mme] INFO: Added a session. Number of sessions is now 1 (../src/mme/mme-context.c:79) 03/17 16:56:55.234: [esm] DEBUG: esm_state_inactive(): MME_EVT_ESM_MESSAGE (../src/mme/esm-sm.c:61) 03/17 16:56:55.234: [esm] DEBUG: [ESM] PDN Connectivity request (../src/mme/esm-sm.c:82) 03/17 16:56:55.234: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] (../src/mme/esm-sm.c:84) 03/17 16:56:55.234: [esm] DEBUG: EIT(ESM information transfer)[1] (../src/mme/esm-handler.c:59) 03/17 16:56:55.234: [esm] DEBUG: [ESM] ESM information request (../src/mme/esm-build.c:75) 03/17 16:56:55.234: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] (../src/mme/esm-build.c:77) 03/17 16:56:55.235: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.235: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.235: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.269: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.270: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.270: [mme] DEBUG: [MME] Uplink NAS transport (../src/mme/s1ap-handler.c:330) 03/17 16:56:55.270: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:347) 03/17 16:56:55.270: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:354) 03/17 16:56:55.270: [mme] DEBUG: mme_state_operational(): MME_EVT_ESM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.270: [mme] DEBUG: mme_bearer_find_or_add_by_message() [PTI:8, EBI:0] (../src/mme/mme-context.c:2847) 03/17 16:56:55.270: [esm] DEBUG: esm_state_inactive(): MME_EVT_ESM_MESSAGE (../src/mme/esm-sm.c:61) 03/17 16:56:55.270: [esm] DEBUG: [ESM] ESM information response (../src/mme/esm-sm.c:93) 03/17 16:56:55.270: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] (../src/mme/esm-sm.c:95) 03/17 16:56:55.270: [mme] DEBUG: [EMM] Attach reject (../src/mme/nas-path.c:134) 03/17 16:56:55.270: [mme] DEBUG: IMSI[311980000033212] Cause[8] (../src/mme/nas-path.c:135) 03/17 16:56:55.270: [esm] DEBUG: [ESM] PDN connectivity reject (../src/mme/esm-build.c:39) 03/17 16:56:55.270: [esm] DEBUG: IMSI[311980000033212] PTI[8] Cause[27] (../src/mme/esm-build.c:41) 03/17 16:56:55.271: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.271: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.271: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.271: [esm] DEBUG: esm_state_inactive(): EXIT (../src/mme/esm-sm.c:61) 03/17 16:56:55.271: [esm] DEBUG: esm_state_exception(): ENTRY (../src/mme/esm-sm.c:345) 03/17 16:56:55.271: [mme] DEBUG: [MME] UE Context release command (../src/mme/s1ap-path.c:285) 03/17 16:56:55.271: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-path.c:287) 03/17 16:56:55.271: [mme] DEBUG: Group[3] Cause[0] Action[3] Delay[0] (../src/mme/s1ap-path.c:306) 03/17 16:56:55.271: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.275: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.275: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.275: [mme] DEBUG: [MME] UE Context release complete (../src/mme/s1ap-handler.c:919) 03/17 16:56:55.276: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:933) 03/17 16:56:55.276: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:950) 03/17 16:56:55.276: [mme] DEBUG: Action: UE context remove() (../src/mme/s1ap-handler.c:963) 03/17 16:56:55.276: [mme] INFO: Removed a UE. Number of UEs is now 0 (../src/mme/mme-context.c:63) 03/17 16:56:55.276: [emm] DEBUG: emm_state_initial_context_setup(): EXIT -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 19638 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 701 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 420 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 444 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 441 bytes Desc: not available URL: From ganiyuabiolaaminat at gmail.com Tue Mar 31 18:18:31 2020 From: ganiyuabiolaaminat at gmail.com (Abiola Ganiyu) Date: Tue, 31 Mar 2020 19:18:31 +0100 Subject: Connect OCS to PCRF Message-ID: Hi Everyone, I would like to know if anyone has been able to connect an OCS to open5gs PCRF. I know OCS talks to the PCRF using the Sy interface and the Gy interface to connect to the PCEF Lastly, how do I define these interfaces? Regards, -------------- next part -------------- An HTML attachment was scrubbed... URL: