14 Jun
2017
14 Jun
'17
12:47 p.m.
Hi,
Is it possible to perform end-to-end testing like voice calls, sms etc with current
osmo-gsm-tester version.
I do not see any suites for voice call testing in the suites directory.
Thanks
Sudhanthiradasan R
::DISCLAIMER::
----------------------------------------------------------------------------------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and intended for the
named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information could be
intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e
mail and its contents
(with or without referred errors) shall therefore not attach any liability on the
originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the author and may
not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, dissemination,
copying, disclosure, modification,
distribution and / or publication of this message without the prior written consent of
authorized representative of
HCL is strictly prohibited. If you have received this email in error please delete it and
notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and other
defects.
----------------------------------------------------------------------------------------------------------------------------------------------------
14 Jun
14 Jun
2:25 p.m.
Hi Sudhanthiradasan,
On 14/06/17 12:47, Sudhanthiradasan R wrote:
Hi,
Is it possible to perform end-to-end testing like voice calls, sms etc
with current osmo-gsm-tester version.
I do not see any suites for voice call testing in the suites directory.
end-to-end sms between MS is already working and a test is being run in
osmocom's jenkins instance. See [1] and [2].
A first version of a patch adding support to test SMPP (ESME->SMSC->MS)
has been submited and waiting for review.
Voice is not there yet but it's definetly in the roadmap and we plan to
start working on it soon, probably we will have something there over
next weeks.
[1] test:
http://git.osmocom.org/osmo-gsm-tester/tree/suites/sms/mo_mt_sms.py
[2] jenkins job:
http://jenkins.osmocom.org/jenkins/view/osmo-gsm-tester/job/osmo-gsm-tester…
Regards,
Pau
--
- Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
3:03 p.m.
Hi Pau Espin Pedrol,
Thanks for your quick reply.
1)Just for the confirmation.. for the end-to-end testing with the current version of
osmo-gsm-tester we can use only the sms suite?
2)In the suites directory, I can see aoip_debug, aoip_sms, debug, netreg, sms suites. What
are all the tests that I can do with these suits? Is there any documentation?
3)If we want to create new suites, is there any document to help us?
Thanks,
Sudhanthiradasan R
-----Original Message-----
From: Pau Espin Pedrol [mailto:pespin@sysmocom.de]
Sent: Wednesday, June 14, 2017 5:56 PM
To: Sudhanthiradasan R <sudhanthiradasan.r(a)hcl.com>om>; openbsc(a)lists.osmocom.org
Subject: Re: osmo-gsm-tester - voice call
Hi Sudhanthiradasan,
On 14/06/17 12:47, Sudhanthiradasan R wrote:
Hi,
Is it possible to perform end-to-end testing like voice calls, sms etc
with current osmo-gsm-tester version.
I do not see any suites for voice call testing in the suites directory.
end-to-end sms between MS is already working and a test is being run in osmocom's
jenkins instance. See [1] and [2].
A first version of a patch adding support to test SMPP (ESME->SMSC->MS) has been
submited and waiting for review.
Voice is not there yet but it's definetly in the roadmap and we plan to start working
on it soon, probably we will have something there over next weeks.
[1] test:
http://git.osmocom.org/osmo-gsm-tester/tree/suites/sms/mo_mt_sms.py
[2] jenkins job:
http://jenkins.osmocom.org/jenkins/view/osmo-gsm-tester/job/osmo-gsm-tester…
Regards,
Pau
--
- Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
::DISCLAIMER::
----------------------------------------------------------------------------------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and intended for the
named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information could be
intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e
mail and its contents
(with or without referred errors) shall therefore not attach any liability on the
originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the author and may
not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, dissemination,
copying, disclosure, modification,
distribution and / or publication of this message without the prior written consent of
authorized representative of
HCL is strictly prohibited. If you have received this email in error please delete it and
notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and other
defects.
----------------------------------------------------------------------------------------------------------------------------------------------------
3:38 p.m.
Hi,
On 14/06/17 15:03, Sudhanthiradasan R wrote:
1)Just for the confirmation.. for the end-to-end testing with the current version of
osmo-gsm-tester we can use only the sms suite?
aoip_sms should be working too. It's basically the same as "sms" suite
but using the AoverIP version of OpenBSC which will soon deprecate
current OsmoNITB platform.
2)In the suites directory, I can see aoip_debug,
aoip_sms, debug, netreg, sms suites. What are all the tests that I can do with these
suits? Is there any documentation?
You can find the latest manual with general documentation in [1].
Feel free to ask if something is not clear or missing. If you want to
improve it, the sources of the manual can be found in [2], patches welcome.
* debug: A few minimal tests used during development of osmo-gsm-tester.
You may find interesting the "interactive.py" one, which let's you start
a test and set-up all the network + modems, then wait in a cmdline
prompt waiting for you so you can debug whatever is going on.
* aoip_debug: Same as debug, but using AoIP
* netreg: A pair of minimal tests which check that the modems
(ofono_client.py) can automatically/manually register with the network.
It's a subset of what sms.py test is doing, but it's nice to have when
willing to specifically test the register part.
* sms: Starts the network, starts and registers 2 ofono modems (MS),
sends an SMS from one MS to the other and then check's the sms arrived
correctly and that the content is correct.
* aoip_sms: Same as sms, but using AoIP.
3)If we want to create new suites, is there any document to help us?
You can have an idea of the current roadmap but checking at the tasks
listed in the issue tracker of the project [3]. If you have any specific
interest feel free to add tickets there (check similar ones don't exist
before doing so). Incoming patches are welcome too.
To know how to write new tests, the best is to check existing tests
(sms.py), and you can find the API exported and available for tests in
[4]. We extend the API when we implement new features which we see are
required for new tests.
[1] http://ftp.osmocom.org/docs/latest/osmo-gsm-tester-manual.pdf
[2] http://git.osmocom.org/osmo-gsm-manuals/tree/OsmoGSMTester
[3] https://osmocom.org/projects/osmo-gsm-tester/issues
[4] http://git.osmocom.org/osmo-gsm-tester/tree/src/osmo_gsm_tester/test.py
--
- Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
5:07 p.m.
Welcome Sudhanthiradasan,
On Wed, Jun 14, 2017 at 01:03:20PM +0000, Sudhanthiradasan R wrote:
2)In the suites directory, I can see aoip_debug,
aoip_sms, debug, netreg, sms suites. What are all the tests that I can do with these
suits? Is there any documentation?
We don't have specific documentation for the different suites yet. They aren't
structured as clearly as I would like, either, given the still early stage of
what osmo-gsm-tester is capable of. The 'sms' and 'aoip_sms' can be
considered
the production parts tested in our jenkins
http://jenkins.osmocom.org/jenkins/view/osmo-gsm-tester/job/osmo-gsm-tester…
where the others are more for our own manual testing and debugging.
Also as Pau pointed out the roadmap is to drop the 'sms' suite completely,
since that is using the OsmoNITB, which will "soon" be discontinued for the
benefit of a separate OsmoBSC and OsmoMSC.
3)If we want to create new suites, is there any
document to help us?
If you create new tests and suites, we would appreciate if you share your
efforts with the community: i.e. instead of creating your separate private
project containing test suites, rather submit them back to us with the goal of
having a complete collection of test suites upstream at git.osmocom.org. There
are two points to this: one of course is that we are spending a rather large
amount of effort to make this infrastructure available for free, for which we
still need to get support and funding. The other point is that any tests we
incorporate in our upstream codebase will be maintained by the community and
will be considered in new developments, without you having to catch up with us
constantly. If you are willing to provide funding to help us push things
forward, that is very welcome. But just as welcome is your support in the form
of sharing your own test suites and other patches with us.
Same goes for the documentation: the manual can certainly use more/better
content, which may also be contributed by anyone.
In turn feel free to also share your questions regarding the tester and Osmocom
in general, and we will help you find answers to the best of our abilities.
Professional support is also available, e.g. from my employer sysmocom.
Check out the OsmoGSMTester manual, part of the osmo-gsm-manuals:
http://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Manuals
Also be aware of numerous issues still open in our tracker, many of which ask
for clarification of the structures and extending the features of the tester:
http://osmocom.org/projects/osmo-gsm-tester/issues
You are welcome to help out with those and/or let us know which of those are of
interest to you and/or create new issues.
Any feedback from you in form of patches is highly welcome, using our Gerrit
patch management; for instructions, see:
http://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit
Thank you for your interest, and hoping that you will join the Osmocom
community!
~N
--
- Neels Hofmeyr <nhofmeyr(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschäftsführer / Managing Directors: Harald Welte
2531
days inactive
2531
days old
4 comments
3 participants
participants (3)
-
Neels Hofmeyr -
Pau Espin Pedrol -
Sudhanthiradasan R