From keith at rhizomatica.org Tue Oct 5 20:44:52 2021 From: keith at rhizomatica.org (Keith) Date: Tue, 5 Oct 2021 15:44:52 -0500 Subject: LCLS Message-ID: Hi All, I was again looking at advancing with LCLS support. I've made a couple of proposals, which at least get it to the stage where the global call reference it consistent from the A leg to B leg of a call, with both the internal mncc and external,? and therefore osmo-bsc can make use of either the lcls-mode (mgw|bts)-loop. The implementation in the osmo-sip-connector doing nothing more than passing the GCR from leg to leg, but it's more complicated than this. We need to allow the PBX to have the audio streams until the PBX itself decides to remove itself from the stream. (as it is you won't even hear ringback) I know all this is spec-ed somewhere in LCLS, I'm just not sure where/how this SIP re-INVITE processing should be implemented, in the sip conn, or the MSC - which I guess, takes us back again to neels' long standing proposals for parsing SDP inside the MSC. Maybe it' s time to get that merged. Anyway.. I have some time scheduled to try to move this forward towards a definitive solution, just writing here in case anyone else can help. Thanks. k/ From keith at rhizomatica.org Wed Oct 6 02:42:21 2021 From: keith at rhizomatica.org (Keith) Date: Tue, 5 Oct 2021 21:42:21 -0500 Subject: LCLS In-Reply-To: References: Message-ID: After looking at this a little more today, I think we need to: * write a FSM for lcls in the MSC, correct? * have the msc change lcls states in the bsc in response to INVITES on the sip side, (as well as signal it's MGW to change IP/Port) * when using the external mncc, always start lcls in STS_NOT_YET_LS The thing that I not seeing right now is how the SIP PBX would signal to change lcls state, the only thing occuring to me is to always run the PBX on a different IP to the MGW and then the condition when reacting to reINVITES would be: if the sdp mediaip != my ip then STS_NO_LONGER_LS , otherwise conditional on all the other conditions for LCLS.... That is to say, if 172.16.0.0/16 is the RTP subnet, then bind the MGWs to 172.16.0.1 and Freeswitch to 172.16.0.2. So (leaving the ports our of it) initially our MO call would have c=IN IP4 172.16.0.1 FS would repond c=IN IPV 172.16.0.2 then INVITE the MT call with 172.16.0.2 to which sipconn/msc/mgw responds with 172.16.01 When the B leg answered, FS invites itself out of the audio stream, with a re-INVITE with c=172.16.0.1, this would be our trigger to send ST_LOCALLY_SWITCHED on the BSS so that bts-loop can kick into action. when FS wants to intervene (to playback "your credit is about to expire", for example), then it reINVITES itself back into the stream with c=172.16.0.2, this would trigger STS_NO_LONGER_LS (or something) Then the BSC comes out of LCLS bts-loop, informs the BTS to sendrecv to the MGW, and at the same time the MSC has told the MGW to start sending and to expect from FS. ?a bit hacky? From nhofmeyr at sysmocom.de Wed Oct 6 11:20:00 2021 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Wed, 6 Oct 2021 13:20:00 +0200 Subject: LCLS In-Reply-To: References: Message-ID: <20211006111959.GB4096@my.box> On Tue, Oct 05, 2021 at 03:44:52PM -0500, Keith wrote: > sip conn, or the MSC - which I guess, takes us back again to neels' long > standing proposals for parsing SDP inside the MSC. Maybe it' s time to > get that merged. +1 :) The one outstanding point there that I remember is making my SDP handling on sipcon not undo your call-hold handling patch. The osmo-msc patch should be ready for merge as-is. > Anyway.. I have some time scheduled to try to move this forward towards > a definitive solution, just writing here in case anyone else can help. I can help as soon as sysmocom is able to fund my hours spent... Too time stricken ATM to even consider doing it in my free time. ~N From ivan.babanov at gmail.com Fri Oct 8 08:04:41 2021 From: ivan.babanov at gmail.com (Ivan Babanov) Date: Fri, 8 Oct 2021 11:04:41 +0300 Subject: Question about Virtual-Um implementation Message-ID: Hello all, We trying to bring up set of BTS with virtual Um with different configurations: 1 BTS -> 1 TRX -> 1 MS works fine as expected 1 BTS -> 1 TRX -> 2 MS works fine as well But I see some unpredictable behaviour when I have 1 BTS -> 2 TRX(872,873) -> 1 MS MS can attach on one ARFCN (872) but when it tries to attach on 873 looks like PRACH does not reach BTS and I do not see Channel Request on BSC side. So, the question is it workable configuration: Several TRX to 1 MS with different power level to allow MS to choose a best cell to attach? I have just one idea: to have several virtphy instances for MS connected to different UDP ports. Thank you Vania From beepimpact at yahoo.it Mon Oct 4 09:59:20 2021 From: beepimpact at yahoo.it (Americo Colella) Date: Mon, 4 Oct 2021 09:59:20 +0000 (UTC) Subject: Nano 3G Femtocell request References: <1005197676.2716198.1633341560635.ref@mail.yahoo.com> Message-ID: <1005197676.2716198.1633341560635@mail.yahoo.com> Hello everyone,I would like to play eith the nano 3g femtocell, Is there anybody who want to give it away /sell one ? Thanks a lot, Americo -------------- next part -------------- An HTML attachment was scrubbed... URL: From hncaga at gmail.com Mon Oct 18 23:03:43 2021 From: hncaga at gmail.com (Henry Caga) Date: Tue, 19 Oct 2021 07:03:43 +0800 Subject: Amplifier Settings Message-ID: Hello, im Using a default configuration for my osmo-bsc setup using B210. I managed to get a working amplifier with specifications below. My question is, what should be the best config that i should use in order to maximize tge power and range of my amplifier? What are the best configs for osmo-trx, osmo-bts, and other applications related to osmo-bsc. Proper settings such as osmotrx tx-attenuation, nominal power, ms max power and other related configurations that are valid or matched for my amplifier. Listed below is my amplifier's specification. AMPLIFIER SPECS: band: uplink 885-915MHz / downlink 930-960MHz Max output power: downlink 47?1dBm Max allow input power: uplink -10dBm / downlink +10dBm gain: Uplink 25?2dB Downlink 28 to 53?1dB ALC: Uplink ?10dB Downlink ?10dB SWR: Uplink ?1.5 Downlink ?1.5 Passband ripple: Uplink ?2dB Downlink ?2dB Noise floor: uplink ?2dB third order intermodulation: Uplink ?-55dBc at -8dBm/ch/2ch Downlink ?-36dBc at 2ch Voltage: 28V Currency: ?4.5A Thanks a lot! Henry -------------- next part -------------- An HTML attachment was scrubbed... URL: From justin.repollo at entropysolution.com Tue Oct 19 11:05:40 2021 From: justin.repollo at entropysolution.com (Justin) Date: Tue, 19 Oct 2021 11:05:40 +0000 Subject: Subscriber Auto Provision in new split stack OSMO-NITB version Message-ID: Hi Osmocom, May I ask if we have similar feature of auto provisioning of subscribers who are trying to camp to the network similar to auth-policy accept-all in osmo-nitb? Is the new version supports also the auto provisioning of subscribers? Regards, Justin Mark Repollo -------------- next part -------------- An HTML attachment was scrubbed... URL: From keith at rhizomatica.org Wed Oct 20 23:02:22 2021 From: keith at rhizomatica.org (Keith) Date: Wed, 20 Oct 2021 18:02:22 -0500 Subject: Subscriber Auto Provision in new split stack OSMO-NITB version In-Reply-To: References: Message-ID: <9f85eddc-a13f-7f45-ec1b-92f48cd522e1@rhizomatica.org> On 19/10/2021 06:05, Justin wrote: > > May I ask if we have similar feature of auto provisioning of > subscribers who are trying to camp to the network similar to > *auth-policy accept-all* in osmo-nitb? Is the new version supports > also the auto provisioning of subscribers? > Hi Justin, Yes. There is something similar. In osmo-hlr you need: hlr ?subscriber-create-on-demand 5 none or similar. Check inline help for what "5" and "none" mean. These are options. -------------- next part -------------- An HTML attachment was scrubbed... URL: From justin.repollo at entropysolution.com Thu Oct 21 08:14:22 2021 From: justin.repollo at entropysolution.com (Justin) Date: Thu, 21 Oct 2021 08:14:22 +0000 Subject: OSMO-MSC External MNCC integration with FeeSwitch Message-ID: Hi Osmocom, I'm trying to integrate the FreeSwitch as my external MNCC in my test lab using split stack. Currently, I'm getting an error message on FreeSwitch SIP/2.0 400 Missing Contact Header. I'm little bit confused with the error and I don't know where to troubleshoot this. I've attached my osmo configurations and pcap trace for your reference. Hoping for your reply. Thank you. Regards, Justin Mark Repollo -------------- next part -------------- An HTML attachment was scrubbed... URL: From keith at rhizomatica.org Thu Oct 21 14:02:43 2021 From: keith at rhizomatica.org (Keith) Date: Thu, 21 Oct 2021 09:02:43 -0500 Subject: OSMO-MSC External MNCC integration with FeeSwitch In-Reply-To: References: Message-ID: On 21/10/2021 03:14, Justin wrote: > Hi Osmocom, Hello Justin. > Currently, I'm getting an error message on FreeSwitch SIP/2.0 400 > Missing Contact Header. > > Freeswitch devs broke libsofia-sip in their current development track. However, your (linux?) distro probably has a working libsofia-sip package. There was an issue somewhere, not sure if it was on osmocom or github. or some other place. I can't find it right now, sorry. You need to uninstall the libsofia that was installed along with freeswitch from the freeswitch repos. (I'm guessing you installed from their packages) and install the version supplied with your distro. I'm not sure what will happen nowadays with your package manager dependencies if you try to uninstall libsofia, it may insist on removing freeswitch. You might have to do some package manager wizardry, or download the libsofia-sip packages from the distro and extract them and then copy the libs into place. Or build it all yourself from Freeswitch 1.8 or someting. I am not aware of any new feature added to the current freeswitch master that you might need to use FS as a PBX (it's not really correct to say an "external MNCC") 1.8 or even 1.6 is fine. I have: Package: libsofia-sip* Pin: release a=oldstable Pin-Priority: 510 in /etc/apt/preferences.d/pinning.pref I think, that is to say, IIUC freeswitch decided the handle Contact headers in the freeswitch code and therefore imposed that onto libsofia.? This is all unfortunate, but a good example of "works for me" thinking. k -------------- next part -------------- An HTML attachment was scrubbed... URL: From maud.dib1984 at gmail.com Sun Oct 24 00:09:51 2021 From: maud.dib1984 at gmail.com (Paul Atreides) Date: Sat, 23 Oct 2021 20:09:51 -0400 Subject: nano3g 237BA Message-ID: I just picked up this IPAccess model which supports band 2/5 and has the same housing as the other units on the accelerate3g5 project docs. I've been pouring over docs and trying a lot of network configurations in my home lab. I have the login information for the factory reset and can access the web gui on port 8089 during the reset process, but ssh and telnet DMI seem to be disabled. I've been fuzzing ports and i've tried static as well as DHCP for IP addresses. My thought was that if i point the nano3G to the IP of my osmo-hNodeB machine that it would at least stimulate the device and maybe i'd see some log messages in the HNodeB gateway, but so far i haven't seen anything in the logs. i've also tried abisip-find and that doesn't find anything. Wireshark shows basic 'who has' Layer 2 messages and also DHCP requests sent to 0.0.0.0, both from the nano3g. The nano3g does get an ip from my lab router and i can ping it. The LAN behind that router can also access the 0.ipaccess ntp server, but again no telnet DMI or ssh so i'm unsure where to go from here. Layer 1 seems to show nothing on the uarfcn in the web gui, so it seems that its not crossing all the right bridges. I will admit, i haven't run any other osmo network components for the network, but as far as i was reading the home nodeb and ntp should be the only things necessary to at least start the process. Any insight on what to try next would be very helpful. Does anyone have experience with this model? thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From maud.dib1984 at gmail.com Tue Oct 26 02:48:19 2021 From: maud.dib1984 at gmail.com (Paul Atreides) Date: Mon, 25 Oct 2021 22:48:19 -0400 Subject: nano3g 237A Message-ID: Not sure if this is a repost, i just joined the list and i don't think i had confirmed my account when i sent it (the confirmation was in my spam). Anyways, not trying to be a bad list member. I just picked up this IPAccess model which supports band 2/5 and has the same housing as the other units on the accelerate3g5 project docs. I've been pouring over docs and trying a lot of network configurations in my home lab. I have the login information for the factory reset and can access the web gui on port 8089 during the reset process, but ssh and telnet DMI seem to be disabled. I've been fuzzing ports and i've tried static as well as DHCP for IP addresses. My thought was that if i point the nano3G to the IP of my osmo-hNodeB machine that it would at least stimulate the device and maybe i'd see some log messages in the HNodeB gateway, but so far i haven't seen anything in the logs. i've also tried abisip-find and that doesn't find anything. Wireshark shows basic 'who has' Layer 2 messages and also DHCP requests sent to 0.0.0.0, both from the nano3g. The nano3g does get an ip from my lab router and i can ping it. The LAN behind that router can also access the 0.ipaccess ntp server, but again no telnet DMI or ssh so i'm unsure where to go from here. Layer 1 seems to show nothing on the uarfcn in the web gui, so it seems that its not crossing all the right bridges. I will admit, i haven't run any other osmo network components for the network, but as far as i was reading the home nodeb gateway and ntp should be the only things necessary to at least start the process. Any insight on what to try next would be very helpful. Does anyone have experience with this model? thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From lynxis at fe80.eu Tue Oct 26 19:29:37 2021 From: lynxis at fe80.eu (Alexander 'lynxis' Couzens) Date: Tue, 26 Oct 2021 21:29:37 +0200 Subject: nano3g 237A In-Reply-To: References: Message-ID: <20211026212937.31c7ed62@lazus.yip> Hi Paul, depending on your firmware your device will either use bmis or tr069 as configuration. If you have a tr069 firmware you can use this "simple" tr069 https://git.sysmocom.de/sysmocom/femto-acs to configure and connect to the osmo-hnbgw. Over the provisioning webui you can set the tr069 server. So you would need to setup osmo-hnbgw, osmo-msc, osmo-mgw, osmo-sgsn, osmo-ggsn, osmo-hlr, osmo-stp. depending on your voice setup you would also need osmo-sip-connector to a pbx (e.g. asterisk, freeswitch, ..). You should read https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_In_The_Box for further information. Best, lynxis -- Alexander Couzens mail: lynxis at fe80.eu jabber: lynxis at fe80.eu gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From maud.dib1984 at gmail.com Wed Oct 27 05:03:36 2021 From: maud.dib1984 at gmail.com (Paul Atreides) Date: Wed, 27 Oct 2021 01:03:36 -0400 Subject: nano3g 237A In-Reply-To: <20211026212937.31c7ed62@lazus.yip> References: <20211026212937.31c7ed62@lazus.yip> Message-ID: <52CAD0DB-CE19-4574-9EE3-465EDABC1252@gmail.com> Thank you so much. I?m going to give this a try. > On Oct 26, 2021, at 15:29, Alexander 'lynxis' Couzens wrote: > > ?Hi Paul, > > depending on your firmware your device will either use bmis or tr069 as > configuration. > > If you have a tr069 firmware you can use this "simple" tr069 > https://git.sysmocom.de/sysmocom/femto-acs to configure and connect to > the osmo-hnbgw. > Over the provisioning webui you can set the tr069 server. > > So you would need to setup osmo-hnbgw, osmo-msc, osmo-mgw, osmo-sgsn, > osmo-ggsn, osmo-hlr, osmo-stp. depending on your voice setup you would > also need osmo-sip-connector to a pbx (e.g. asterisk, freeswitch, ..). > > You should read > https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_In_The_Box > for further information. > > Best, > lynxis > -- > Alexander Couzens > > mail: lynxis at fe80.eu > jabber: lynxis at fe80.eu > gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604 From laforge at osmocom.org Wed Oct 27 18:33:03 2021 From: laforge at osmocom.org (Harald Welte) Date: Wed, 27 Oct 2021 20:33:03 +0200 Subject: Osmocom redmine upgrade / Let me know if something broke Message-ID: Dear Osmocom community, today we finally upgraded our redmine installation from the unmaintained 3.4.x to the latest 4.2.3. The upgrade had been overdue for years, but today we (actually, Kevin) finally managed to find out how to make the openid_provider plugin to work with modern rails 5.x. In any case, I'm just informing you in case there is some unexpected fallout. I've verified that at least the following appears working: * logging into redmine * openid authentication from gerrit.osmocom.org (also after logout/relogin) * graphviz rendering * mscgen rendering There could however still be unexpected problems, particularly in features such as * e-mail notifications from redmine * updating redmine issues via e-mail * git integration ("Closes: OS#xxxx") If you run into any troubles, pleas report to https://osmocom.org/projects/osmocom-servers or if that also fails, feel free to send e-mails. 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 nhofmeyr at sysmocom.de Wed Oct 27 20:21:28 2021 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Wed, 27 Oct 2021 22:21:28 +0200 Subject: OSMO-MSC External MNCC integration with FeeSwitch In-Reply-To: References: Message-ID: <20211027202128.GF2275@my.box> Just to mention it, the FreeSwitch configs that worked for me at some point in time are available at https://git.osmocom.org/osmo-dev/tree/net (you need to run fill_config.py to render the templates) Haven't used those in a while, just saying. ~N From justin.repollo at entropysolution.com Thu Oct 28 00:35:35 2021 From: justin.repollo at entropysolution.com (Justin) Date: Thu, 28 Oct 2021 00:35:35 +0000 Subject: OSMO-MSC External MNCC integration with FeeSwitch In-Reply-To: <20211027202128.GF2275@my.box> References: <20211027202128.GF2275@my.box> Message-ID: Hi Neels, Thank you for the feedback. Will try the given files and config and will update you on this. Regards, Justin Mark Repollo ________________________________ From: Neels Hofmeyr Sent: 28 October 2021 04:21 To: Justin Cc: OpenBSC at lists.osmocom.org Subject: Re: OSMO-MSC External MNCC integration with FeeSwitch Just to mention it, the FreeSwitch configs that worked for me at some point in time are available at https://git.osmocom.org/osmo-dev/tree/net (you need to run fill_config.py to render the templates) Haven't used those in a while, just saying. ~N -------------- next part -------------- An HTML attachment was scrubbed... URL: From maud.dib1984 at gmail.com Thu Oct 28 02:00:04 2021 From: maud.dib1984 at gmail.com (Paul Atreides) Date: Wed, 27 Oct 2021 22:00:04 -0400 Subject: OSMO-MSC External MNCC integration with FeeSwitch In-Reply-To: <20211027202128.GF2275@my.box> References: <20211027202128.GF2275@my.box> Message-ID: Neels! Thanks so much for this. I had another question, I did a reverse lookup on the public IP address that the nano3G was set to when I got it, so I know the MNC and presumably the MCC as well. Do you think that information is mandatory for the firmware? Like, did they do custom firmware builds for specific telcos? Thanks > On Oct 27, 2021, at 16:21, Neels Hofmeyr wrote: > > ?Just to mention it, the FreeSwitch configs that worked for me at some point in > time are available at https://git.osmocom.org/osmo-dev/tree/net > (you need to run fill_config.py to render the templates) > > Haven't used those in a while, just saying. > > ~N -------------- next part -------------- An HTML attachment was scrubbed... URL: From maud.dib1984 at gmail.com Thu Oct 28 03:26:30 2021 From: maud.dib1984 at gmail.com (Paul Atreides) Date: Wed, 27 Oct 2021 23:26:30 -0400 Subject: OSMO-MSC External MNCC integration with FeeSwitch In-Reply-To: <20211027202128.GF2275@my.box> References: <20211027202128.GF2275@my.box> Message-ID: <8BA04012-AA2A-4247-9D1C-3ECB0DB9F8C4@gmail.com> OK, one more piece of critical information (I?m realizing how silly it was for me to not mention this). In the config menu there is an ?enable telnet? button. The description says that it will enable telnet on 8090 but to be enabled, it is dependent on ?dmi.init? being on the device AND there is a section on the UI to upload to the DMI file! I?ve tried the obvious things (like clicking the enable telnet button!), rebooting and seeing if it works. It did not. After that I tried uploading a blank file called ?dmi.init? To see if that would initialize the telnet interface by the presence of the file name alone. That did not work either. Does anyone have a dmi.init file from another device that could possibly work? I?ve only found a tiny bit of information online referencing DMI.init files but what I have found indicates that dmi.init is in fact a script not a blank file. Anyways, I probably should have included this in my original post. As always, any insight would be fantastic. Thanks > On Oct 27, 2021, at 16:21, Neels Hofmeyr wrote: > > ?Just to mention it, the FreeSwitch configs that worked for me at some point in > time are available at https://git.osmocom.org/osmo-dev/tree/net > (you need to run fill_config.py to render the templates) > > Haven't used those in a while, just saying. > > ~N From vyanitskiy at sysmocom.de Fri Oct 29 22:40:38 2021 From: vyanitskiy at sysmocom.de (Vadim Yanitskiy) Date: Sat, 30 Oct 2021 01:40:38 +0300 Subject: Catching missing #include of Message-ID: <739a4397-5d7e-4fff-12cd-341a47c67f96@sysmocom.de> Hi list, today I fixed a header file in libosmocore: https://gerrit.osmocom.org/c/libosmocore/+/26044 TL;DR, using OSMO_IS_{LITTLE,BIG}_ENDIAN macros without including the header leads to empty struct definitions, and thus weird compiler warnings like 'struct `foo` has no member `bar`'. We may want to catch missing #include of the automatically, so I wrote a simple script to check whether it is absent: https://gerrit.osmocom.org/c/osmo-ci/+/26045 Below is an example of using it: $ cd libosmocore/ $ verify_endian_header.sh $(find . -name "*.[hc]") File './include/osmocom/gsm/protocol/gsm_44_004.h' does not #include What's still missing is the actual integration into the build verification process. I guess there is currently no easy way other than calling this script from 'contrib/jenkins.sh' of each project? P.S. I found out that we also have 'scripts/verify_log_statements.py' in osmo-ci.git, but we don't seem to call it anywhere? Best regards, Vadim. -- - Vadim Yanitskiy http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte From mariolucas75 at mail.ru Sat Oct 30 06:53:27 2021 From: mariolucas75 at mail.ru (=?UTF-8?B?TWFyaW8gTHVjYXM=?=) Date: Sat, 30 Oct 2021 09:53:27 +0300 Subject: =?UTF-8?B?R1NNVEFQIG1lc3NhZ2VzIG5vdCBnZW5lcmF0ZWQ=?= Message-ID: <1635576807.898139746@f387.i.mail.ru> ? Dear All, ? I am running a GSM stack: ? osmo-stp smo-msc osmo-hlr osmo-bsc osmo-bts-trx osmo-trx-lms ? It seems that my transmitter is emitting radio-waves into air (osmo-bts-trx and osmo-trx-lms communicate with each other through ports 5702 / 5802 ? pls see attached printscreen), however i could not make GSMTAP tracing. Osmo-bts-trx does not send GSMTAP messages to port 4729. ? In most recent version of osmo-bts, GSMTAP tracing is arranged through config file: ? bts 0 ? gsmtap-remote-host 127.0.0.1 ??gsmtap-sapi ccch ? ? I could not run the GSMTAP tracing even in previous verions of osmo-bts where you have to specify in synopsis when you call a program: ? /usr/bin/osmo-bts-trx -s -c /etc/osmocom/osmo-bts-trx.cfg --gsmtap-ip 127.0.0.1 ? ? I thought may be i am having some issues in stack components behind osmo-bts for example in osmo-bsc or behind and i tried to run virtual bts. When i tried to run osmo-bts-virtual GSMTAP messages were visible in wireshark (please see attached file osmo-bts-virtual), therefore bts-bsc communication is good. ? However I still could not figure out why my osmo-bts-trx does not send GSMTAP messages. Or would you advise what log might be helpful to see what i am doing wrong ?. ? Thank you for your always helpful assistance ? -- Mario Lucas ? ---------------------------------------------------------------------- ? -- Mario Lucas ? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: osmo-bts-trx.jpg Type: image/jpeg Size: 125776 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: osmo-bts-virtual.jpg Type: image/jpeg Size: 118948 bytes Desc: not available URL: From justin.repollo at entropysolution.com Thu Oct 21 08:19:55 2021 From: justin.repollo at entropysolution.com (Justin) Date: Thu, 21 Oct 2021 08:19:55 +0000 Subject: OSMO-MSC External MNCC integration with FeeSwitch In-Reply-To: References: Message-ID: Resending with attachment. Hi Osmocom, I'm trying to integrate the FreeSwitch as my external MNCC in my test lab using split stack. Currently, I'm getting an error message on FreeSwitch SIP/2.0 400 Missing Contact Header. I'm little bit confused with the error and I don't know where to troubleshoot this. I've attached my osmo configurations and pcap trace for your reference. Hoping for your reply. Thank you. Regards, Justin Mark Repollo ________________________________ From: Justin Sent: 21 October 2021 16:18 To: OpenBSC at lists.osmocom.org Subject: Re: OSMO-MSC External MNCC integration with FeeSwitch Resending with attachment. Hi Osmocom, I'm trying to integrate the FreeSwitch as my external MNCC in my test lab using split stack. Currently, I'm getting an error message on FreeSwitch SIP/2.0 400 Missing Contact Header. I'm little bit confused with the error and I don't know where to troubleshoot this. I've attached my osmo configurations and pcap trace for your reference. Hoping for your reply. Thank you. Regards, Justin Mark Repollo ________________________________ From: Justin Sent: 21 October 2021 16:14 To: OpenBSC at lists.osmocom.org Subject: OSMO-MSC External MNCC integration with FeeSwitch Hi Osmocom, I'm trying to integrate the FreeSwitch as my external MNCC in my test lab using split stack. Currently, I'm getting an error message on FreeSwitch SIP/2.0 400 Missing Contact Header. I'm little bit confused with the error and I don't know where to troubleshoot this. I've attached my osmo configurations and pcap trace for your reference. Hoping for your reply. Thank you. Regards, Justin Mark Repollo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: osmo-FS.pcap.zip Type: application/zip Size: 1334286 bytes Desc: osmo-FS.pcap.zip URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Archive.zip Type: application/zip Size: 4467 bytes Desc: Archive.zip URL: