<br><br><div class="gmail_quote">2010/3/9 Harald Welte <span dir="ltr"><<a href="mailto:laforge@gnumonks.org">laforge@gnumonks.org</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Hopsing K,<br>
<div class="im"><br>
On Mon, Mar 01, 2010 at 10:48:39PM +0100, Hopsing K wrote:<br>
<br>
> I was preparsing the TS M30g smStack a bit and<br>
> came out with something like this:<br>
> <a href="http://netplugin.sourceforge.net/" target="_blank">http://netplugin.sourceforge.net/</a> ++append+next++<br>
> htmltag/CC/cc_act.c.pinfo.main.php<br>
> (please concat the two url parts).<br>
<br>
</div>Thanks for sharing this.<br>
<br>
However, please consider that even while the TSM30 code has been<br>
available online for some 5 years now (and thus the information<br>
contained in it can no longer be considered a trade secret): The code<br>
still has copyright, i.e. without the explicit approval of the copyright<br>
holders you cannot redistribute it and make copies (like now on<br>
<a href="http://netplugin.sf.net" target="_blank">netplugin.sf.net</a>).<br></blockquote><div><br>I know. <br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br>
> I wondered weather I could support this project a<br>
> bit by processing some more of the TS M30 files.<br>
<br>
</div>Thanks a lot for your offer. I suppose those people who look at the<br>
TSM30 code so far (including myself) are using non-networked tools like<br>
'ctags' / 'etags' for source navigation.<br>
<div class="im"><br></div></blockquote><div><br>I could generate file-based versions that could be run locally. <br>Still a local webserver is needed. If I pack all info in a single html <br>file it will be overloaded and you cant navigate...<br>
ctags might be good however you cannot just click on macros to<br>expand and at the same time see the definition position, similary<br>you cannot click open a include position.<br><a href="http://netplugin.sourceforge.net/htmltag/CC/cc_act.c.pinfo.main.php">http://netplugin.sourceforge.net/htmltag/CC/cc_act.c.pinfo.main.php</a><br>
is kind of easier to handle. (When opening the above link it'll <br>take a while until it gets started, first the main page has to be fetched and <br>inserted using ajax).<br><br>To be true, even if I can freely navigate the source I still cannot<br>
understand it. Problem is well that GSM is too complex and <br>no documents availabe that describe a simple setup.<br><br>What I would like to have is:<br><br> - For a minimal setup for a voicecall I'd want <br> a flow diagram (the kind of diagram where time runs from top to bottom and<br>
calls/replies between i.e. Cellphone and BTS are shown a arrows left/right ) <br> - Then in that flow diagram I'd need html links that pinpoint<br> the location where the call is done in the TSM30 stack (using the <br>
prorocessed html) and be able to quickly jump to it.<br> - At the same time have a link to the etsi standard page where<br> the call/replies is specified.<br><br>That way I could visualize in practice how it works. There is no chance<br>
I guess for someone to understand it otherwise. There are 100 of <br>etsi standards pages, at the same time you intuitively guess that it <br>cannot be that complex if it is a simple setup.<br> <br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">
> Also some hint:<br>
> Isnt there a software only way to run the stack:<br>
> Put even Layer1 on the PC ? Then connect<br>
> directly to BTC software? Kind off skip the messy<br>
> embedded thing altogether for development.<br>
<br>
</div>this is something I've been thinking about in the past. but then you<br>
need to<br>
<br>
1) implement a 'fake BTS' that implements at least the Layer2 (possibly<br>
also Layer1) over e.g. multicast IP<br>
2) Connect this 'fake BTS' to OpenBSC<br>
3) implement a 'fake layer1' for the MS side implementing the same<br>
"Um over multicast IP" approach.<br>
<br>