I have some questions:
1) When I start bsc_hack bsc_init.c first establishes OML link and
initializes the bts then it establishes RSL link and bts starts
broadcasting. However, it takes so much time to start the bts. Instead of
this I want to do the following: it establishes OML link at the beginning
and only once, then when i want to start broadcasting it establishes just
the RSL link and bts will start faster since i don't have to wait for OML
link. What should be done for this?
2) If i send one or two word messages from telnet interface it is okay. But
if i send a longer message the phone could't receive the end of the message
correctly(last words may be incomplete). Did any one encounter with this
problem? What is wrong with me?
3) Could I send SMS in which extension of the sender is text not integer.
For example, i want to send an information SMS that this is a test network.
For this purpose i want to send an SMS from 'OpenBSC'. I set the extension
of the first subscriber in database as text and tried to send the SMS but
SMS wasn't delivered. What should i do?
4) Can i add SMS externally to SMS table of database?
Thanks.
Jason
Hello
Our goal was to send status sms via the vty interface. But all of our
sms were cropped. In contrast sms from one MS to another MS are
displayed correctly (despite the fact, that the text at the database
contains several '@' at the end / the user_data contains several
zero-octets). Therefore i have inspect the code and found several bugs.
The main problem is that the "user_data_len" is not correctly used. As
per GSM 03.40, 9.2.3.16 TP‑User‑Data‑Length (TP‑UDL):
"If the TP‑User‑Data is coded using the GSM 7 bit default alphabet, the
TP‑User‑Data‑Length field gives an integer representation of the number
of septets within the TP‑User‑Data field to follow."
Currently the "user_data_len" contains the number of octets (returned
from gsm_7bit_encode(...) at gsm_utils.c (libosmocore)).
The big problem here is that this information is not unique, e.g.:
1.) 46 non-extension characters + 1 extension character => (46 * 7 bit +
(1 * (2 * 7 bit))) / 8 bit = 42 octets
2.) 47 non-extension characters => (47 * 7 bit) / 8 bit = 41,125 = 42 octets
3.) 48 non-extension characters => (48 * 7 bit) / 8 bit = 42 octects
But the MS has to know the correct "user_data_len" to decode the correct
number of characters.
For this reason i updated the gsm_7bit_encode() function to return the
correct number of septets. However sometimes it is needed to know the
correct number of octets (e.g. at gsm_04_11.c: gsm340_gen_tpdu(...)) =>
i added a function to gsm_utils.c named:
uint8_t get_octet_len(const uint8_t sept_len)
I have also fixed the problem, that the sms are wrongly stored /
displayed on the database. But the solution on the function
*sms_from_result(...) (at db.c) is not really "beautiful". This is
because there exists no "user_data_len" field at the database. To store
the right value for "user_data_len" (which is further needed) i have to
get the length from the "text" field. Unfortunately this is not enough.
If the text contains extension characters like {[]} etc. then the
"user_data_len" has to be bigger because these characters needs two
septets. Therefore i use a switch statement so search for these
characters. A better solution for that is to store the right
"user_data_len" to the database (on the encoding / decoding procedure).
But i don't know if this is a suitable solution for all of you (because
you have to change your database structure etc.).
Best Regards
Dennis Wehrle
Hi all,
so far we do not have any statement about the licensing of the content on
our wiki. This means the default copyright rules apply: All the content is
copyrighted, and nobody has any rgiht to reproduce it at all.
I would like to propose an official license for the content in the wiki:
Create Commons CC-BY-SA. The alternative would be to go for CC-BY-NC-SA,
disallowing commercial use of the content.
I'm not certain if NC is really what we want. After all, even somebody
using OpenBSC in a commercial environment should be able to make copies
of the reference documentation we have available - as long as he will
releas the result again (which the SA part already covers).
If the major contributors to the wiki would agree to a license, I would
update the wiki accordingly.
Thanks,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
From: Pablo Neira Ayuso <pablo(a)gnumonks.org>
Hi!
This patchset adds new VTY commands that allows to route IPA flows.
Patch 3/3 includes one feature that changes the current default
behaviour of OpenBSC since you explicity have to make a "ipa setup"
to enable OML and RSL links. If you like it, I can make a similar
patch for HSL femto, so the only initial open socket is the one at
port 4242 for telnet configuration.
BTW, the original command syntax was proposed by Harald.
Successfully tested bootstrapping the nanoBTS. See the patches for
more details.
Comments welcome!
Pablo Neira Ayuso (3):
libcommon: add make_sock_stream_connect()
libabis: add VTY commands to route IPA flows
libabis: add IPA VTY command to setup ip.access nanoBTS OML and RSL
links
openbsc/include/openbsc/ipaccess.h | 3 +
openbsc/include/openbsc/socket.h | 2 +
openbsc/include/openbsc/vty.h | 1 +
openbsc/src/ipaccess/Makefile.am | 4 +-
openbsc/src/libabis/Makefile.am | 2 +-
openbsc/src/libabis/e1_input.c | 2 +
openbsc/src/libabis/input/ipaccess.c | 962 +++++++++++++++++++++++++++++-
openbsc/src/libbsc/bsc_vty.c | 1 +
openbsc/src/libcommon/socket.c | 54 ++
openbsc/src/openbsc.cfg.ipa-proxy | 18 +
openbsc/src/openbsc.cfg.nanobts | 3 +
openbsc/src/openbsc.cfg.nanobts.multitrx | 3 +
openbsc/tests/db/Makefile.am | 5 +-
13 files changed, 1043 insertions(+), 17 deletions(-)
create mode 100644 openbsc/src/openbsc.cfg.ipa-proxy
--
1.7.2.3
Hi Pablo!
I've recently received a bug report that somehow the config-file-stored
configuration of which log levels/subsystems to enable on stderr don't work.
This may be related to the legacy "-d DINP:DNM:... style log level
specifications, e.g. we first read the config file and then set some default
logging options usign the legacy version.
Maybe you can find some time to investigate and fix the issue.
Thanks in advance,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hi!
I'm experiencing problems with pysim-prog. Using the example available
in the README file.
# ./pySim-prog.py -n 26C3 -c 49 -x 262 -y 42 -z lila -j 0
Insert card now (or CTRL-C to cancel)
I get stuck here forever. The same message shows if I remove the
supersim card from the reader.
Running pysim inside strace shows:
write(1, "Insert card now (or CTRL-C to cancel)\n", 38) = 38
ioctl(3, TIOCMBIS, [TIOCM_RTS]) = 0
select(0, NULL, NULL, NULL, {0, 100000}) = 0 (Timeout)
ioctl(3, TCFLSH, 0) = 0
ioctl(3, TIOCMBIC, [TIOCM_RTS]) = 0
select(4, [3], [], [], {1, 0}) = 0 (Timeout)
select(0, NULL, NULL, NULL, {0, 500000}) = 0 (Timeout)
ioctl(3, TIOCMBIS, [TIOCM_RTS]) = 0
select(0, NULL, NULL, NULL, {0, 100000}) = 0 (Timeout)
ioctl(3, TCFLSH, 0) = 0
ioctl(3, TIOCMBIC, [TIOCM_RTS]) = 0
... [and so on]
The pl2303 module is loaded correctly, and I have used it before to
access some embedded devices via serial line:
pl2303 2-2:1.0: pl2303 converter detected
usb 2-2: pl2303 converter now attached to ttyUSB0
usb 2-2: USB disconnect, device number 11
pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
Any clue on what's wrong?
Thanks!
Hi "Mr. Unknown",
it has come to my attention that you are running a copy of our OpenBSC
website (http://openbsc.osmocom.org/) at http://openbsc.microembedded.com/
We appreciate your enthusiasm for OpenBSC and like to thank you for
your work on the Chinese translation.
However, it would have been good to coordinate about this with us. Making
a copy of the website as a sub-domain to your company "MicroEmbedded" may
seem to some people as if you were representing the OpenBSC project (which
you are not), or that OpenBSC is somehow a work of your MicroEmbedded company.
After some checking, it seems that the final line on each page "注: BscHack (英文原文出 处,以上翻译整理仅供 OpenBSC 爱好者参考! email: support(a)microembedded.com )"
provides a link to the orignal page at bs11-abis.gnumonks.org.
Once again in this link you provide your e-mail address, followed by the
company footer of your web-page.
The contents of the OpenBSC website has copyright, and we do not think it is
appropriate for you to associate your company in this way with OpenBSC. You
are not a member of the project, you have not contributed to the OpenBSC
software, and you have not contacted us about obtainign permission to make
such a translated copy.
Furthermore, there are several problems with your website:
1) it is out of date, as you have used a very old version of the OpenBSC
website to translate. As a result, quite some of your links back to
the original OpenBSC site are broken.
2) You have introduced capitalization changes like "$ Sqlite" which will not
work, as the command is "$ sqlite"
If your intentions in running a translated OpenBSC site are honest, I would
like to invite you to do so in working together with us. We can provide
you with the respective space on the official homepage, and you can contribute
your translated content there.
In return, we may put a "thank you" link to microembedded.com in the Thanks
section at http://openbsc.osmocom.org/trac/wiki#Thanks
We hope this is acceptable to you. In any case, we hope you can understand
that we will not tolerate you putting your company name next to a copy of the
OpenBSC wiki.
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Dear List,
I'm a long time listener, first time caller - but have been enjoying
experimenting with OpenBSC for a little while now.
I've come across a new (to me) nanoBTS with some strange behavior: it seems
to come up normally and pull an IP over DHCP, and interacts as expected with
the ipaccess-find and ipaccess-config tools, but *never* attempts to
establish an OML link.
After provisioning the correct settings with ipaccess-config, the unit
reboots and slow-flashes the orange light (no OML) and there is *no* network
traffic initiated by the nanoBTS past the DHCP exchange; however, I can ping
the unit using ipaccess-find and ping.
After running a reset with the dongle and a repeat of the above, I get the
same results.
Any ideas?
Thank You,
-MM
Hello all,
I want a confirmation.
I 've seen in openBSC features that openBSC handles handover between cells
inside one BSC. So I think it's possible to connect several nanoBTS to
openBSC and move from one cell to another without losing the outgoing call.
Am I right ?
Thank you.
Chris
All -
I am looking for a full-card SIM programmer to use with pySim and GR-Card SIMs. By full-card I mean it accepts a full-size smart-card with the SIM still attached. I have tried the Bludrive II unit provided by GR-Card under both Mac OS X and Ubuntu with no luck. (And yes, I tried downloading and installing the drivers.) Can anyone recommend something that is known to work with pySim under Linux or OS X? Or is there some other driver that I need to install or configure?
-- David
Hi everyone,
I have successfully compiled and installed openBSC-0.9.13, but there isn't
the program bsc_hack. However, in src/osmo-nitb, there's bsc_hack source
code and object (.c and .o) and an executable osmo-nitb. Has bsc_hack been
replaced by osmo-nitb ?
Thanks.
Christopher Hénard
Hi, List!
Just a question, does OpenBSC block the connection to special number
such 112?
I connected OpenBSC to Asterisk and in Asterisk I have an extension 112
(now just as test), an 110 and an 115.
If I call the 110 or 115 I can see that Asterisk will be asked to
connect the phone and the VoIP-phone with the number will be called.
If I call the 112 the connection terminates and I can't see OpenBSC
sending any signal to Asterisk.
Could you confirm me, that OpenBSC blocks this number?
And, maybe, suggest me how to delete this block... :)
Thanks a lot!
Luca Bertoncello
--
_______________________________________________________________________
Luca Bertoncello
Entwicklung Mail: bertoncello(a)netzing.de
NETZING Solutions AG Tel.: 0351/41381 - 23
Fröbelstr. 57, 01159 Dresden Fax: 0351/41381 - 12
_______________________________________________________________________
Impressum:
NETZING Solutions AG - Fröbelstraße 57 - 01159 Dresden
Sitz der Gesellschaft Amtsgericht Dresden HRB 18926
Vorstand Dieter Schneider - Aufsichtsratsvorsitzender Volker Kanitz
USt.Id DE211326547 Mail: netzing.ag(a)netzing.de
> Does it mean, that it is not possible for me to have a 112 number b
> called in my network?
No, it's not possible.
You should avoid anything starting by '1' and anything starting by '9' in
your dialplan ...
Cheers,
Sylvain
Dear All,
Is it possible to use openbsc as MSC, VLR and HLR without using nanBTS as i'm trying to develop an SMSC.In other words, to make it work as MSC,HLR emulator with dummy subscribers?
Regards,
Ammar
Hello Konrad,
On Wed, 13 Apr 2011 16:16:01 +0200, "Konrad Meier" <meierk(a)informatik.uni-freiburg.de> wrote:
>
> Any idea what the NWL connector is for?
Its the Rx Antenna for the "Network Listen" feature of the nanoBTS,
its used for receiving the downlink of other basestations.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello Konrad,
On Wed, 13 Apr 2011 13:10:54 +0200, "Konrad Meier" <meierk(a)informatik.uni-freiburg.de> wrote:
>
> 1. What is the purpose of the "RF cable"?
> Is the TX port of the master BTS looped through the second BTS? Or hase
> every nanoBTS his own TRX/RX?
The RF cable is used to route TX from the rear unit to the AUX connector
of the front unit. The SMB socket at the back and AUX are directly connected,
there is nothing special about them. So in a stacked two-units assembly
the front unit also has the TRX antenna of the rear unit at the AUX connector.
Most certainly the idea is to improve transmission of the rear unit or to
better separate the two TRX antennas.
So TX is looped through one unit but the two TX signals are not combined.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
How can I calibrate the clock of the nanobts?
I looked through the mailing list and all I have found is that it is not implemented....
Sent from my iPhone
Hi all,
I was just reading the wiki page about the nanoBTS multi-TRX setup.
Two things are not clear to me.
1. What is the purpose of the "RF cable"?
Is the TX port of the master BTS looped through the second BTS? Or hase
every nanoBTS his own TRX/RX?
I am asking because I would like to use a nanoBTS-Booster with the
multi-TRX setup and therefore require a combined RF signal.
2. The example example "openbsc.cfg" configures the trx 1 as follows:
timeslot 0
phys_chan_config CCCH+SDCCH4
timeslot 1
phys_chan_config SDCCH8
Is this really needed? My first idea was to configure the second trx to
TCH/F only.
Best regards
Konrad Meier
Hi all,
this email don't want to be a provocative email but just an opinion
related to the creation of value for GSM TLC stack into the opensource
environment.
As we know currently there are several different projects growing into
the GSM (then tetra and in future 3G?) opensource ecosystem.
The first "pratical" base has been OpenBTS as a simplified GSM um
interface for VoIP.
The second major implementations was around the osmocom project that
build-up a complete and well designed GSM stack with all the modular
interfaces and protocols for communications between BTS and BSC, with
MSC, HLR, GGSN, SGSN and major GSM network components.
Additionally, if i understood correctly osmocom is much more advanced
with broad scope and better design than OpenBTS.
It seems to me that OpenBTS it's almost stalled due to the "commercial
fork" of the OpenSource project and only fairwaves is contributing to
the opensource branch.
I personally really dislike the "Commercial fork" approach where the
community is used only in the early phase of the project to improve it
and from a certain point the community doesn't get almost any added value.
I like much more the dual-licensed approach like AGPL/Commercial (like
http://pjsip.org) where all the value of the code is publicly released.
However, my post was related to a question:
- How complex would be, leveraging existing public OpenBTS code, to
integrate into the Osmocom project?
I mean, having a sort of lightweight BTS component speaking A-Bis over
IP to OpenBSC like the cheap nano ip.access BTS does.
For what i read now Osmocom have 2 software BTS (Osmo-BTS and Soft-BTS),
communicating with the A-BIS over IP interface to OpenBSC:
http://lists.gnumonks.org/pipermail/openbsc/2011-March/002529.htmlhttp://lists.gnumonks.org/pipermail/openbsc/2010-April/001508.html
I've read that only a lot of time ago (2009) there was a discussion
about OpenBTS to OpenBSC integration:
http://lists.gnumonks.org/pipermail/openbsc/2009-October/000955.html
At the current stage of development (2011), with Osmocom finally getting
a Software-BTS part communicating to the Software-BSC side, how really
complex it would be to integrate the GSM-um related part of OpenBTS into
the project?
With that approach the 'GSM-um' interface would be a very simplified
module of the overall system and osmocom would completely replace
OpenBTS all-in-one project.
Am i right?
-naif
p.s. Sorry for the cross-posting, i just wanted to explain the idea and
get the communities feedbacks to understand 'at which point' we are in
order to think 'what would be required to be done' to achieve that goal.
From: Pablo Neira Ayuso <pablo(a)gnumonks.org>
This patchset is the third in the series to cleanup code in
ipaccess tools and drivers.
They have been tested by bootstraping the nanoBTS successfully in
a small setup with two laptops, one acting as proxy and another with
osmo-nitb.
They are available in the pablo/cleanups branch in openbsc git tree.
BTW: I'm going to stop a bit with cleanups to add a VTY interface
for ipaccess-proxy, as Harald suggested.
Please, merge it!
Thanks.
Pablo Neira Ayuso (7):
libabis: ipaccess: more robust ipaccess_idtag_name()
src: more robust ipaccess_idtag_parse()
libabis: ipaccess: use log instead of debug under errors in
ipaccess_send()
ipaccess-find: get rid of ipac_idtag_name()
ipaccess-proxy: more robust option parsing and checking
ipaccess-proxy: remove leftover option `--udp'
ipaccess-proxy: get rid of make_gprs_sock()
openbsc/include/openbsc/ipaccess.h | 2 +-
openbsc/src/ipaccess/Makefile.am | 6 +++
openbsc/src/ipaccess/ipaccess-find.c | 22 +------------
openbsc/src/ipaccess/ipaccess-proxy.c | 56 +++++++++++++--------------------
openbsc/src/libabis/input/ipaccess.c | 18 ++++++----
openbsc/src/osmo-bsc_nat/bsc_nat.c | 8 ++++-
openbsc/src/osmo-bsc_nat/bsc_ussd.c | 8 ++++-
7 files changed, 55 insertions(+), 65 deletions(-)
--
1.7.2.3
From: Pablo Neira Ayuso <pablo(a)gnumonks.org>
This patch includes some updates for the wireshark RSL dissector.
See patch for details.
This changes are available in the pablo/wireshark-rsl branch of
openBSC.
Please, merge it.
Pablo Neira Ayuso (1):
wireshark: update extension of RSL dissector with ip.access nanoBTS
support
wireshark/0004-rsl-ipaccess.patch | 228 ++++++++++++++++++++++---------------
1 files changed, 134 insertions(+), 94 deletions(-)
--
1.7.2.3
Hi all
Just to let everyone know about an auction that people may like to look into.
Online Auction Closes 3pm* on Tuesday 19th April 2011
Extensive Electronic Test and Measurment Equipment to include Agilent
/HP Telecom test, Spectrum Analysers, Frequency generators, Optical
Test, Oscilloscopes, Programmable Power Supplies, Inspection Scopes,
19in Test rack syetems Equipment Transport, IT equipment and more.
http://www.sweeney-kincaid.com/Sales/SaleDescription.aspx?SaleId=1640
guy
Hi Harald,
I bisected this and I end at the commit that moves bsc_init.c code around and
moves things to signals. Out of your head would you know if ipaccess-config
needs to call some other init function or do something special? If not I will
dig a bit more and come back with more details.
holger
hello,
one abis_rsl-massage is: CONNECTION FAIL: RELEASE CAUSE=0x18(Siemens: T_MSRFPCI Expired) 01
and handover always ends in a segfault error
what does that mean and how can i fix it?
T.
From: Pablo Neira Ayuso <pablo(a)gnumonks.org>
This patchset is the second in the series to cleanup redundant code
in ipaccess tools.
They have been tested by bootstraping the nanoBTS successfully in
a small setup with two laptops, one acting as proxy and another with
osmo-nitb.
They are available in the pablo/cleanups branch in openbsc git tree.
Please, merge it!
Thanks.
Pablo Neira Ayuso (6):
ipaccess-proxy: get rid of make_listen_sock() and use make_sock()
instead
libabis: ipaccess: conclude new ipaccess_send_*() functions and use
them
libabis: ipaccess: export ipaccess_idtag_name()
ipaccess-proxy: get rid of ipac_idtag_parse()
libabis: ipaccess: export ipaccess_parse_unitid
ipaccess-proxy: remove hardcoded IP for options `-l' and `-b'
openbsc/include/openbsc/ipaccess.h | 3 +
openbsc/src/ipaccess/Makefile.am | 7 +-
openbsc/src/ipaccess/ipaccess-proxy.c | 188 ++++++---------------------------
openbsc/src/libabis/input/ipaccess.c | 75 +++++++++----
4 files changed, 94 insertions(+), 179 deletions(-)
--
1.7.2.3
hello
to enable handover function, do i have to change in data field msg_3 the corresponding values form 0x00h to 0x01h?
does 0x01h enable where 0x00h disables?
T.
From: Pablo Neira Ayuso <pablo(a)gnumonks.org>
This patchset is the first in the series to cleanup redundant code
in ipaccess tools.
They are available in the pablo/cleanups branch in openbsc git tree.
Please, merge it!
Thanks.
Pablo Neira Ayuso (3):
ipaccess-config: exit if no network interface is specified
libcommon: socket: extend make_sock() prototype
ipaccess-proxy: get rid of internal make_sock() implementation
openbsc/include/openbsc/socket.h | 5 ++-
openbsc/src/ipaccess/ipaccess-find.c | 1 +
openbsc/src/ipaccess/ipaccess-proxy.c | 42 ++------------------------------
openbsc/src/libabis/input/hsl.c | 4 +-
openbsc/src/libabis/input/ipaccess.c | 8 +++---
openbsc/src/libcommon/socket.c | 10 ++++---
openbsc/src/libgb/gprs_ns.c | 2 +-
openbsc/src/libgb/gprs_ns_frgre.c | 2 +-
openbsc/src/osmo-bsc_nat/bsc_ussd.c | 2 +-
9 files changed, 22 insertions(+), 54 deletions(-)
--
1.7.2.3
Hi all,
A thread on the asterisk mailing list re-triggerd my memory.
Last november or so i asked if it might be possible to use a
gsm/umts-dongle as a bts. afaicr the general consensus was that it was
not possible because the proximity of TX and RX hardware.
I have been discussing it with my colleges today and wonder where we
were making the obvious thinking-mistake...
1) i know, that certainly at higher powers, the receiver becomes deaf in
the vincinity of a (high powered) transmitter, due to cirtuit overload,
but in our case we only needs a single miliwatt or even less....
2) scanning for multiple devices/frequencies is not needed.
[the idea is to connect to a single hand-held-device, that is only one
meter away, and feed voice through an existing IP-connection]
3) if a dongle is not usable for above reasons as a BTS, why is that
same dongle (more-or-less) capable as working as a handheld? Same
problems should occur as such, not?
http://wiki.e1550.mobi/doku.php
If they can tap in the device for audio/sms-client, it should also be
possible to do it the other way round, as a single-thread bts....
still puzzled, Hans
Hi, list!
I'm trying to understand how the options "nominal power" and
"max_power_red" work...
Last Friday I tried to place 4 BTS in a rectangle of about 100x20 meter
and then I examined the measurement reports of a mobile. They are very
very bad, and oft it cannot see a cell.
Then I tried to change the value of "nominal power" (max_power_red did
not changed) and retry to check the measurement reports.
No changes... :(
Now I'm here in my office with a spectrum analyzer and try to change
these values, but what I see in the spectrum analyzer is always the
same...
I restart OpenBSC after any change, of course!
Could you please help me to understand what these values mean and how
can I boost the signal?
Thanks a lot in advance for your help!
--
_______________________________________________________________________
Luca Bertoncello
Entwicklung Mail: bertoncello(a)netzing.de
NETZING Solutions AG Tel.: 0351/41381 - 23
Fröbelstr. 57, 01159 Dresden Fax: 0351/41381 - 12
_______________________________________________________________________
Impressum:
NETZING Solutions AG - Fröbelstraße 57 - 01159 Dresden
Sitz der Gesellschaft Amtsgericht Dresden HRB 18926
Vorstand Dieter Schneider - Aufsichtsratsvorsitzender Volker Kanitz
USt.Id DE211326547 Mail: netzing.ag(a)netzing.de