Hi Romeu, Wow! It’s amazing. I can’t thank you enough for your effort. Best Regards, Sukchan 2019년 7월 17일 (수) 오전 1:33, Romeu Medeiros <medeiros(a)medeiros.eng.xn--br>-n54x791j 작성:

Hi Romeu, On Tue, Jul 16, 2019 at 07:45:02PM -0300, Romeu Medeiros wrote: and feel free to share some pcap files, we're also happy to review them from the osmocom point of view. -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

Harald, I some situations, when the MME lost connection with the OSMO-MSC and return this connection if I try send a MT-CSFB the OSMO-MSC is crashing. I get this error in the log: <0006> sgs_iface.c:470 XXXXXXXXXX state == 1 conf_by_radio_contact_ind == 1 <0011> sgs_iface.c:251 (sub IMSI-724210000000003:MSISDN-5544912340003:TMSI-0x8E44F269) Tx PAGING-REQUEST suitable MME found, but no SGS connection present! <0005> sgs_iface.c:480 SGs-UE(imsi:724210000000003)[0x563949b08fc0]{SGs-ASSOCIATED}: Will not Page (no MME) <0005> paging.c:101 Paging: IMSI-724210000000003:MSISDN-5544912340003:TMSI-0x8E44F269 for MNCC: establish call: Starting paging failed (rc=-22) <0001> gsm_04_08_cc.c:1922 trans(CC IMSI-724210000000003:MSISDN-5544912340003:TMSI-0x8E44F269 callref-0x1396 tid-255) Failed to allocate paging token. Segmentation fault (core dumped) I'll try why this happened, but I'm not getting used to it in the OSMO source code. Can you tell me (if you have time) how identify where this crash is occouring? In the attach have the PCAP of the SGS between the OSMO and NextEPC-MME. Thanks Romeu Medeiros On Wed, Jul 17, 2019 at 6:40 AM Harald Welte &lt;laforge(a)gnumonks.org&gt; wrote:

Hi Romeu, On Wed, Jul 17, 2019 at 06:17:31PM -0300, Romeu Medeiros wrote: that obviously shouldn't happen. == 1 Page Thanks. I created a bug at https://osmocom.org/issues/4117 It's the same as any other C program: * compile with "-g" * run it in gdb * provoke the setfault * take a "backtrace full" after the crash It would be great if you could amend the bugtracker with that information, but I would guess the information you provided is already sufficient for Philipp, the implementor of the SGs support in OsmoMSC. -- - Harald Welte &lt;laforge(a)gnumonks.org&gt; http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

Hello Sukchan, I found something stranger, When the VLR try to Pagging the UE, the NextEPC-MME make the pagging correctly. But when this UE is not reachable the NextEPC it not sending to VLR the SGsAP-UE-UNREACHABLE, like is necessary in the documentation: [image: image.png] I will try to fix it. In attached I'm sending a pcap from this case. The IMSI unreachable in this case is 724210000000002. Thanks Romeu Medeiros On Tue, Jul 16, 2019 at 7:45 PM Romeu Medeiros &lt;medeiros(a)medeiros.eng.br&gt; wrote: > Sukchan, > > We can't thank you enough for the nextepc. > > I think that in some situations the msc is losing the sgs registrations > and can't forward the sms. But I will more tests before to disturb you > there. > > Thanks and success! > > Romeu Medeiros > > Em ter, 16 de jul de 2019 às 19:35, Sukchan Lee &lt;acetcom(a)gmail.com&gt; > escreveu: > >> Hi Romeu, >> >> Wow! It’s amazing. >> I can’t thank you enough for your effort. >> >> Best Regards, >> Sukchan >> >> >> >> 2019년 7월 17일 (수) 오전 1:33, Romeu Medeiros &lt;medeiros(a)medeiros.eng.xn--br&gt;-n54x791j >> 작성: >> >>> Hello guys and @Sukchan Lee &lt;acetcom(a)gmail.com&gt; >>> >>> I tested with sucess the send and receive SMS in new version of NextEPC >>> running together with OSMO-MSC/HLR (SGS). >>> >>> Thanks >>> >>> Romeu Medeiros >>> >>