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
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 <justin.repollo@entropysolution.com> Sent: 21 October 2021 16:18 To: OpenBSC@lists.osmocom.org <OpenBSC@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@lists.osmocom.org <OpenBSC@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
Hi Justin. I already told you what is wrong. Maybe you somehow missed my mail?
Hi Keith, I don't receive any email from you. Can you please send it again? Hi Neels, I've tried the shared config but still encountered the Missing Contact Header error. Regards, Justin ________________________________ From: Keith Whyte <keith@rhizomatica.org> Sent: Wednesday, November 3, 2021 7:26:52 AM To: Justin <justin.repollo@entropysolution.com>; OpenBSC@lists.osmocom.org <OpenBSC@lists.osmocom.org> Subject: Re: OSMO-MSC External MNCC integration with FeeSwitch Hi Justin. I already told you what is wrong. Maybe you somehow missed my mail?
On 02/11/2021 17:39, Justin wrote:
Hi Keith,
I don't receive any email from you. Can you please send it again?
http://lists.osmocom.org/pipermail/openbsc/2021-October/013562.html
Hi @Keith<mailto:keith@rhizomatica.org>, Thank you for your input. I was able to make it work now using v1.8.5 of FreeSwicth. Hi @Neels Hofmeyr<mailto:nhofmeyr@sysmocom.de>, I'm trying to work out using half rate channel in my testbed setup but unfortunately, I'm getting an error message Originate Failed. Cause: INCOMPATIBLE_DESTINATION. Do I need to adjust some configurations in OSMO to make it work? Regards, Justin Mark Repollo | System Engineer | Entropy Solution Philippines 09066150436 | justin.repollo@entropysolution.com<mailto:dennis.diamsay@entropysolution.com> Unit 2103 Antel Corporate Centre 121 Valero St. Salcedo Village Makati City Philippines 1227 [cid:32433c32-f5df-412c-ada3-fe379d895ebf] Singapore | Philippines Products: Gridloc | Overwatch | Hive | eReach | ReachNet | Intelle | Hype | Lighthouse | Telco Services | Software Development This email (including any attachment to it) is confidential and intended only for the use of the individual named above and may contain information that is privileged. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify us immediately by return email or telephone and destroy the original message (including any attachment to it). Thank you. ________________________________ From: Keith <keith@rhizomatica.org> Sent: 04 November 2021 03:32 To: Justin <justin.repollo@entropysolution.com>; OpenBSC@lists.osmocom.org <OpenBSC@lists.osmocom.org> Subject: Re: OSMO-MSC External MNCC integration with FeeSwitch On 02/11/2021 17:39, Justin wrote:
Hi Keith,
I don't receive any email from you. Can you please send it again?
http://lists.osmocom.org/pipermail/openbsc/2021-October/013562.html
I'm trying to work out using half rate channel in my testbed setup but unfortunately, I'm getting an error message Originate Failed. Cause: INCOMPATIBLE_DESTINATION. Do I need to adjust some configurations in OSMO to make it work?
Codec negotiation is quite broken in OsmoMSC. Patches to fix that are tested and have been almost-ready for years now, unfortunately there was not sufficient human resource available to fully finish and merge them. To use proper codec negotiation from MS thru SIP, you may try using: osmo-msc branch neels/mncc_codecs3 osmo-sip-connector branch neels/codecs3 (The last actually tested versions were neels/mncc_codecs2 and neels/codecs2, I just now rebased those onto current master and resolved some conflicts, however don't have the time to also test them. So if 3 fails, you may also try 2.) Without above patches, the codec in osmo-sip-connector is actually hard coded and you will be able to use only that single codec, chosen by actually patching the source code of osmo-sip-connector. *With* above patches, a) codec selection is based on more information in osmo-msc, and b) the codec is properly transported through to the SDP that ends up in the SIP and back from SIP to the MSC. Feedback would be appreciated! If these patches help you, then it confirms (again) that someone should fund us to work on merging them... Thanks! ~N
Hi Neels, Thank you for your suggestions. I'll try this and feedback once I've simulate this on my test setup. Regards, Justin Get Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: Neels Hofmeyr <nhofmeyr@sysmocom.de> Sent: Friday, November 5, 2021 6:17:26 PM To: Justin <justin.repollo@entropysolution.com> Cc: openbsc@lists.osmocom.org <openbsc@lists.osmocom.org> Subject: Re: OSMO-MSC External MNCC integration with FeeSwitch
I'm trying to work out using half rate channel in my testbed setup but unfortunately, I'm getting an error message Originate Failed. Cause: INCOMPATIBLE_DESTINATION. Do I need to adjust some configurations in OSMO to make it work?
Codec negotiation is quite broken in OsmoMSC. Patches to fix that are tested and have been almost-ready for years now, unfortunately there was not sufficient human resource available to fully finish and merge them. To use proper codec negotiation from MS thru SIP, you may try using: osmo-msc branch neels/mncc_codecs3 osmo-sip-connector branch neels/codecs3 (The last actually tested versions were neels/mncc_codecs2 and neels/codecs2, I just now rebased those onto current master and resolved some conflicts, however don't have the time to also test them. So if 3 fails, you may also try 2.) Without above patches, the codec in osmo-sip-connector is actually hard coded and you will be able to use only that single codec, chosen by actually patching the source code of osmo-sip-connector. *With* above patches, a) codec selection is based on more information in osmo-msc, and b) the codec is properly transported through to the SDP that ends up in the SIP and back from SIP to the MSC. Feedback would be appreciated! If these patches help you, then it confirms (again) that someone should fund us to work on merging them... Thanks! ~N
On 05/11/2021 04:17, Neels Hofmeyr wrote:
just now rebased those onto current master and resolved some conflicts,
Brilliant! Thanks for finding time to do that, I had started a rebase a couple of weeks ago before taking some time off, but I had problems, I think mostly with getting the make check tests to pass, it was enough to take the wind out of my sails.
Without above patches, the codec in osmo-sip-connector is actually hard coded and you will be able to use only that single codec
I don't mean to contradict you, but I don't see that is actually true anymore. not that the actual state is the important thing, the important thing is moving forward with these patches. All the same, Justin. for the sake of getting you running, you said:
I'm trying to work out using half rate channel in my testbed setup but unfortunately, I'm getting an error message *Originate Failed. **Cause: INCOMPATIBLE_DESTINATION. *Do I need to adjust some configurations in OSMO to make it work?
Would be interesting to see the pcap of the SIP signalling here. What codec(s) is Freeswitch offering? Is this a mobile to mobile call, or originating at some other SIP endpoint? When you say half rate, you do mean using the AMR codec, or GSM-HR? Maybe attach your FreeSwitch configs, at least vars.xml and the sip_profile.xml for the sip profile that is facing the osmo-sip-connector. Looking at the osmo configs you attached before, you have no explicit codec-list in the BSC msc section, so you should be supporting all, and you have codec-support in the bts, so that looks good. Maybe best to just attach your entire osmo config again for your half-rate channel setup. But please don't let that distract you from testing on Neels' branches! Neels, Without or without any rhizomatica hats on, I don't personally have any funding. But without any hats on at all, I will do some (manual, as in with BTS and phones) testing and can then theoretically push this to CR. I might have to beg help for any ttcn3 work required. BTW, Justin, It's always nice to have a (brief) introduction about what you do with the osmocom software. I don't see any mails from you on the mailing list previous to last month. I see you have a product called ReachNet http://www.entropysolution.com/reachnet.html but I don't see anything concrete about any hardware there, just the usual "connectivity improve lives" rhetoric which I know after 10 years in this game, is usually vapour-ware designed to pull down funding. I also see you have something called HEALTH-E which ethically would prevent me from offering you any further unpaid support. But I assume you are not using osmocom in that particular product, correct? I'd be very interested to know what hardware you are using for Reachnet. Also please do consider if at all possible, to try to fund the completion of the codec work. Many thanks. Keith.
Hi Neels, Sorry for the late response. I'm still out of the office due to medical conditions. I was not able to test the mncc2 and mncc3. I'll let you know once I've test those. Hi Keith, I'm using B210 on my test setup. HEALTH-E is a mobile app specifically for covid tracker. Regards, Justin Mark Repollo ________________________________ From: Neels Hofmeyr <nhofmeyr@sysmocom.de> Sent: 05 November 2021 18:17 To: Justin <justin.repollo@entropysolution.com> Cc: openbsc@lists.osmocom.org <openbsc@lists.osmocom.org> Subject: Re: OSMO-MSC External MNCC integration with FeeSwitch
I'm trying to work out using half rate channel in my testbed setup but unfortunately, I'm getting an error message Originate Failed. Cause: INCOMPATIBLE_DESTINATION. Do I need to adjust some configurations in OSMO to make it work?
Codec negotiation is quite broken in OsmoMSC. Patches to fix that are tested and have been almost-ready for years now, unfortunately there was not sufficient human resource available to fully finish and merge them. To use proper codec negotiation from MS thru SIP, you may try using: osmo-msc branch neels/mncc_codecs3 osmo-sip-connector branch neels/codecs3 (The last actually tested versions were neels/mncc_codecs2 and neels/codecs2, I just now rebased those onto current master and resolved some conflicts, however don't have the time to also test them. So if 3 fails, you may also try 2.) Without above patches, the codec in osmo-sip-connector is actually hard coded and you will be able to use only that single codec, chosen by actually patching the source code of osmo-sip-connector. *With* above patches, a) codec selection is based on more information in osmo-msc, and b) the codec is properly transported through to the SDP that ends up in the SIP and back from SIP to the MSC. Feedback would be appreciated! If these patches help you, then it confirms (again) that someone should fund us to work on merging them... Thanks! ~N
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
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
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 <nhofmeyr@sysmocom.de> Sent: 28 October 2021 04:21 To: Justin <justin.repollo@entropysolution.com> Cc: OpenBSC@lists.osmocom.org <OpenBSC@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
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 <end transmission>
On Oct 27, 2021, at 16:21, Neels Hofmeyr <nhofmeyr@sysmocom.de> 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
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 <end transmission>
On Oct 27, 2021, at 16:21, Neels Hofmeyr <nhofmeyr@sysmocom.de> 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
On Wed, Oct 27, 2021 at 11:26:30PM -0400, Paul Atreides wrote:
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.
Here are the dmi commands that we commonly use: https://osmocom.org/projects/cellular-infrastructure/wiki/Configuring_the_ip... AFAIK the dmi.init file is just these telnet commands put in a file.
Excellent thank you Neels! <end transmission>
On Nov 1, 2021, at 12:06, Neels Hofmeyr <nhofmeyr@sysmocom.de> wrote:
On Wed, Oct 27, 2021 at 11:26:30PM -0400, Paul Atreides wrote:
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.
Here are the dmi commands that we commonly use: https://osmocom.org/projects/cellular-infrastructure/wiki/Configuring_the_ip... AFAIK the dmi.init file is just these telnet commands put in a file.
participants (5)
-
Justin -
Keith -
Keith Whyte
-
Neels Hofmeyr -
Paul Atreides