This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Keith keith at rhizomatica.orgOn 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20211105/d25daeed/attachment.htm>