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/UmTRX@lists.osmocom.org/.
Alexander Chemeris alexander.chemeris at gmail.comHi Stephane, On Wed, Mar 6, 2013 at 4:20 AM, <stephane at shimaore.net> wrote: >> Thank you for your patch to make it working with OpenSIPS :) Looking >> forward for more contributions to the SIP side of things. > > My line of thought is to use OpenSIPS as registrar, with a Redis > backend. Then use OpenSIPS to route calls, SMS, .. based on the IMSI. It seems that using OpenSIPS as much as possible is a good way for scalability, instead of trying to get Freeswitch to scale. At least that's what I was suggested. So I wonder what we could actually offload to OpenSIPS. Do you think we could use OpenSIPS not only as a registrar, but also as an authentication server? And what do you think about routing calls with it? I was told that the best way to get it to scale is to use static routing, i.e. without an access to an external DB. But now the problem is that subscribers move from a BTS to a BTS and it can't be completely static. One solution is to actually have Location Areas as in GSM and use broadcasted SIP INVITEs in them. Or alternatively we could do some "virtual LA" on SIP level by creating a layered set of OpenSIPS instances. SMS is another issue, because it requires a "store and forward" server. Did you know an existing solution for that? Or is it easier to just write the thing from scratch :) -- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ООО УмРадио http://fairwaves.ru