hi harald,
i know that you talked about before so maybe you can give me a hint. i like to make osmo-sgsn allow roaming (different PLMN of the phone than the one in the RAI of the BTS).
regards,
andreas
http://git.osmocom.org/openbsc/commit/?id=eafe22ca7290280fca0f8d31d70239fd0b 0dbb9d
You can comment that line out.
Regards, Pierre
-----Original Message----- From: openbsc-bounces@lists.osmocom.org [mailto:openbsc-bounces@lists.osmocom.org] On Behalf Of Andreas Eversberg Sent: Wednesday, July 17, 2013 2:58 AM To: Harald Welte; OpenBSC Mailing List Subject: GPRS roaming
hi harald,
i know that you talked about before so maybe you can give me a hint. i like to make osmo-sgsn allow roaming (different PLMN of the phone than the one in the RAI of the BTS).
regards,
andreas
Pierre Kim wrote:
http://git.osmocom.org/openbsc/commit/?id=eafe22ca7290280fca0f8d31d70239fd0b 0dbb9d
You can comment that line out.
hi pierre,
thanks for this hint. i just remove the return statement and it works.
best regards,
andreas
17.07.2013 13:14, Andreas Eversberg пишет:
Pierre Kim wrote:
http://git.osmocom.org/openbsc/commit/?id=eafe22ca7290280fca0f8d31d70239fd0b 0dbb9d
You can comment that line out.
hi pierre,
thanks for this hint. i just remove the return statement and it works.
Should we make that configurable perhaps?
Dear Andreas,
On Tue, Jul 16, 2013 at 07:58:17PM +0200, Andreas Eversberg wrote:
i know that you talked about before so maybe you can give me a hint. i like to make osmo-sgsn allow roaming (different PLMN of the phone than the one in the RAI of the BTS).
I've cleaned up and merged some patches that make this vty configurable in git commit 3dfb549a6f31ea2252014db1075a7195da2d4ff7. Please also see the ACL mode, which is safer than running a completely open GPRS network that accepts any IMSI.
Hi Harald,
On Sun, Jul 21, 2013 at 11:47 AM, Harald Welte laforge@gnumonks.org wrote:
On Tue, Jul 16, 2013 at 07:58:17PM +0200, Andreas Eversberg wrote:
i know that you talked about before so maybe you can give me a hint. i like to make osmo-sgsn allow roaming (different PLMN of the phone than the one in the RAI of the BTS).
I've cleaned up and merged some patches that make this vty configurable in git commit 3dfb549a6f31ea2252014db1075a7195da2d4ff7. Please also see the ACL mode, which is safer than running a completely open GPRS network that accepts any IMSI.
Thank you for fixing this, as we often use open SGSN roaming in our testing environment.
Just as an idea for making this simple ACL better - it could be a regexp on IMSI. Then you could easily specify ranges of IMSIs with a short and clear command. This works very well in OpenBTS for example.
-- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ООО УмРадио http://fairwaves.ru
On Sun, Jul 21, 2013 at 10:44:34PM +0400, Alexander Chemeris wrote:
Just as an idea for making this simple ACL better - it could be a regexp on IMSI. Then you could easily specify ranges of IMSIs with a short and clear command. This works very well in OpenBTS for example.
patches welcome. There are quite some regexp examples in the nat
Linking a regular expression matching library seems excessive and an additional dependency for no good reason. Feel free to implement a simple prefix match, possibly by reusing code from the smpp route matching.
Also, rather than that a real async hlr interface is needed. There are many areas where contributions are welcome. So far I yet have to see anyone else making any reasonably sized contribution to the sgsn. This always makes me sad. Not even the past and current llc sequence number / tlli problems which should have been visible to any user seem to have encouraged much in terms of submitting fixes :/
On Mon, Jul 22, 2013 at 05:00:12PM +0800, Harald Welte wrote:
Hi,
Also, rather than that a real async hlr interface is needed. There are many areas where contributions are welcome. So far I yet have to see anyone else making any reasonably sized contribution to the sgsn. This always makes me sad. Not even the past and current llc sequence number / tlli problems which should have been visible to any user seem to have encouraged much in terms of submitting fixes :/
we see an increased use of OpenBSC while the amount of devs mostly stay the same. I wondered about ways to handle or improve this. The below is a list of random thoughts.
* I started with specifying simple tasks and offering guidance when someone wants to implement that. One could go to Universities and hacker spaces to find people motivated to try it. So if there is 1/10 success rate on such projects it would already be positive.
* Obstacles. One needs to have access to a base station to do meaningful work. Now thanks to you there are plenty of individuals with a BS11, and then there are Nokia/Ericsson/nanoBTS and sysmoBTS out there. We also have public events like the XXC3, Camp, OHM. So maybe we should be more active in announcing that we want implementers at these events? Or maybe even hold a two day event in Berlin to ask interested people to implement things?
* Seek for monetary support. Sure some of our commercial users, use the software because it is of zero cost and would never pay a dime for anything. But maybe there are others that want to contribute some money for features? We could do some more ads that companies like sysmocom offer high class, cost-effective customisations to OpenBSC.
* Adopt a more shiny/structured website. On the one hand the wiki is a manifestation that users don't even correct content after they found a solution but maybe we can do things to make the entry for developers/contributors more easy. In fact I had already set-up the software powers a book like this[1]. Maybe we can start with a couple of 'unreliable' guides to {GSM, OpenBSC, Testing}. I had also planned to create such material for the employee's of sysmocom.
* Adopt a model like it is/was(?) used by PackageKit. Contributors do get direct access.. the public needs to wait a penalty time to see the code. It makes it clear that value contributors more than users.
Linking a regular expression matching library seems excessive and an additional dependency for no good reason. Feel free to implement a simple prefix match, possibly by reusing code from the smpp route matching.
man regcomp, it is part of posix.
Hi Holger,
On Mon, Jul 22, 2013 at 12:36:44PM +0200, Holger Hans Peter Freyther wrote:
- I started with specifying simple tasks and offering guidance when
someone wants to implement that. One could go to Universities and hacker spaces to find people motivated to try it. So if there is 1/10 success rate on such projects it would already be positive.
Good idea.
- Obstacles. One needs to have access to a base station to do meaningful
work. Now thanks to you there are plenty of individuals with a BS11, and then there are Nokia/Ericsson/nanoBTS and sysmoBTS out there. We also have public events like the XXC3, Camp, OHM. So maybe we should be more active in announcing that we want implementers at these events?
Or maybe even hold a two day event in Berlin to ask interested people to implement things?
Might be worth trying, but I don't think there will be many people whom we don't already know that would travel to Berlin just to work on some code.
- Seek for monetary support. Sure some of our commercial users, use
the software because it is of zero cost and would never pay a dime for anything. But maybe there are others that want to contribute some money for features? We could do some more ads that companies like sysmocom offer high class, cost-effective customisations to OpenBSC.
I don't like that option. If at all, it would be the business interest of such companies to do so (and they are free to do so), but not something that should be advertised on / in relation to the OpenBSC project and/or websites.
If at all, we could have a wiki page that contains a simple list of businesses who are able to provide commercial customization / support / R&D related to openbsc.
- Adopt a model like it is/was(?) used by PackageKit. Contributors
do get direct access.. the public needs to wait a penalty time to see the code. It makes it clear that value contributors more than users.
I dislike that even more.
man regcomp, it is part of posix.
ok, thanks.
Harald Welte wrote:
If at all, we could have a wiki page that contains a simple list of businesses who are able to provide commercial customization / support / R&D related to openbsc.
I think this is a good approach. I've seen it work well in other projects.
//Peter
On Mon, Jul 22, 2013 at 1:00 PM, Harald Welte laforge@gnumonks.org wrote:
Linking a regular expression matching library seems excessive and an additional dependency for no good reason. Feel free to implement a simple prefix match, possibly by reusing code from the smpp route matching.
Ok. Thanks for the suggestion.
Also, rather than that a real async hlr interface is needed. There are many areas where contributions are welcome. So far I yet have to see anyone else making any reasonably sized contribution to the sgsn. This always makes me sad. Not even the past and current llc sequence number / tlli problems which should have been visible to any user seem to have encouraged much in terms of submitting fixes :/
Well, that's not surprising, given the (low) number of users of OpenBSC in general and (negligible) number of people willing to have GPRS. As I said, we need to do more work on making Osmocom more visible and increasing community. So far Osmocom is far behind OpenBTS in terms of visibility, community size, number of paying clients, etc. You may disagree, but IMHO the way to improve situatioin is to have support for cheaper hardware (hello SDR) and easy to use support for SIP.
-- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ООО УмРадио http://fairwaves.ru
Alexander Chemeris wrote:
So far I yet have to see anyone else making any reasonably sized contribution to the sgsn.
Well, that's not surprising, given the (low) number of users of OpenBSC in general and (negligible) number of people willing to have GPRS.
Do you mean "wanting" ? In that case my experience disagrees with you; henever I've run a network with OpenBSC there was always at least one person asking for data.
As I said, we need to do more work on making Osmocom more visible and increasing community. So far Osmocom is far behind OpenBTS in terms of visibility, community size, number of paying clients, etc.
Community is what it is. There seem to be very few competent developers in both projects.
Paying clients have nothing to do with the open source projects as such, since the projects are not a company. Companies which want to market products and solutions based on osmocom projects are free to do so.
You may disagree, but IMHO the way to improve situatioin is to have support for cheaper hardware (hello SDR) and easy to use support for SIP.
No - that is just the way to increase the number of paying clients for your particular company.
And besides, I find lcr quite easy to use. With literally no telco background other than two years of playing with SIP I managed to learn it in about a day at the camp in 2011. I taught lcr to one other person in about two hours some months ago. It is not very complicated.
Really, what osmocom needs is IMNSHO competent contributions. How you pay for them is your problem, if you want to contribute something.
//Peter
On Sun, Jul 21, 2013 at 03:47:00PM +0800, Harald Welte wrote:
I've cleaned up and merged some patches that make this vty configurable in git commit 3dfb549a6f31ea2252014db1075a7195da2d4ff7. Please also see the ACL mode, which is safer than running a completely open GPRS network that accepts any IMSI.
Thank you for noticing the doctest errors (I will need to figure out why the build doesn't fail with them) and fixing them!
-
Alexander Chemeris -
Andreas Eversberg -
Harald Welte -
Holger Hans Peter Freyther -
Peter Stuge -
Pierre Kim -
☎