HI Neels, Thanks for provided answers and tips. Femto wich I plane to use is Alcatel. My primary target is Packet core, so femto-osmohnbgw-osmosgsn(osmo-hlr)-osmoggsn. Alredy know this want be easy task, But I will try, I expect also problem with SIM authentication. In past I did protocol simulators in Python (Gb, S11, Gn, Gx, Gy), wich were used in production for testing. When I hopfuly install osmo-iuh, I wll conect femto to it and try to configure it, will sniff trafic via wireshark between and check whats happening, Now I will try to rebulid IuH again. BR Goran The information contained in this e-mail message is privileged and confidential and is for the exclusive use of the addressee. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof, and is kindly asked to notify the sender and delete the e-mail immediately.
Hi, I tried this time from the scratch with git://git.osmocom.org/osmo-dev Curently stucked with # ------------------------------------ ## ## osmo-msc 1.0.1.138-4e7ec test suite. ## ## ------------------------------------ ## Regression tests. 1: smpp ok 2: sms_queue_test FAILED (testsuite.at:16) 3: msc_vlr_test_no_authen FAILED (testsuite.at:23) 4: msc_vlr_test_gsm_authen FAILED (testsuite.at:30) 5: msc_vlr_test_gsm_ciph FAILED (testsuite.at:37) 6: msc_vlr_test_umts_authen FAILED (testsuite.at:44) 7: msc_vlr_test_hlr_reject FAILED (testsuite.at:51) 8: msc_vlr_test_hlr_timeout FAILED (testsuite.at:58) 9: msc_vlr_test_ms_timeout FAILED (testsuite.at:65) 10: msc_vlr_test_reject_concurrency FAILED (testsuite.at:72) 11: msc_vlr_test_rest FAILED (testsuite.at:79) Thanks Goran The information contained in this e-mail message is privileged and confidential and is for the exclusive use of the addressee. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof, and is kindly asked to notify the sender and delete the e-mail immediately.
On 29. Sep 2017, at 23:11, Popovic Goran <Goran.Popovic@kapsch.net> wrote:
Hi,
Hi!
I tried this time from the scratch with git://git.osmocom.org/osmo-dev
Curently stucked with
I haven't looked at the test results but the pretty first idea is that you installed the Osmocom libraries in a nonstandard path and need to set LD_LIBRARY_PATH. Have you considered looking at the test failure and reason about it? holger
Hi Holger, Thanks for response,
From tesfailure log this error is seen
+/home/popovicg/osmo-dev/make-3G+2G-default+iu/osmo-msc/tests/sms_queue/sms_queue_test: error while loading shared libraries: libsmpp34.so.0: cannot open shared object file: No such file or directory I haven't looked at the test results but the pretty first idea is that you installed the Osmocom libraries in a nonstandard path and need to set LD_LIBRARY_PATH. Have you considered looking at the test failure and reason about it? holger The information contained in this e-mail message is privileged and confidential and is for the exclusive use of the addressee. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof, and is kindly asked to notify the sender and delete the e-mail immediately.
On 29. Sep 2017, at 23:27, Popovic Goran <Goran.Popovic@kapsch.net> wrote:
Hi Holger,
Hi,
Thanks for response, From tesfailure log this error is seen
+/home/popovicg/osmo-dev/make-3G+2G-default+iu/osmo-msc/tests/sms_queue/sms_queue_test: error while loading shared libraries: libsmpp34.so.0: cannot open shared object file: No such file or directory
I haven't looked at the test results but the pretty first idea is that you installed the Osmocom libraries in a nonstandard path and need to set LD_LIBRARY_PATH. Have you considered looking at the test failure and reason about it?
and a fix was already quoted. As you are doing professional work and you might not be proficient with GNU/Linux, have you considered getting professional help for you and your team at Kapsch? holger
Hi Holger, Apretiate for answer. Profesional help is not option for me because this is not done as my bussines project, this is for my pleasure, but I understand that lot of GNU/Linux answers can be found by ckecking logs and google, before raising question on mail group Thanks Goran
I haven't looked at the test results but the pretty first idea is that you installed the Osmocom libraries in a nonstandard path and need to set LD_LIBRARY_PATH. Have you considered looking at the test failure and reason about it?
and a fix was already quoted. As you are doing professional work and you might not be proficient with GNU/Linux, have you considered getting professional help for you and your team at Kapsch? holger The information contained in this e-mail message is privileged and confidential and is for the exclusive use of the addressee. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof, and is kindly asked to notify the sender and delete the e-mail immediately.
On Fri, Sep 29, 2017 at 03:11:23PM +0000, Popovic Goran wrote:
I tried this time from the scratch with
git://git.osmocom.org/osmo-dev
I agree with Holger. I added some hints to the readme file there: note that the makefiles by default install to /usr/local/*, so if your system doesn't have this by default, you should probably add export LD_LIBRARY_PATH="/usr/local/lib" and export PKG_CONFIG_PATH="/usr/local/lib/pkgconfig" to your environment. To use the installed binaries after installation, also export PATH="$PATH:/usr/local/bin" ~N
On Fri, Sep 29, 2017 at 07:09:44AM +0000, Popovic Goran wrote:
The information contained in this e-mail message is privileged and confidential and is for the exclusive use of the addressee. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof, and is kindly asked to notify the sender and delete the e-mail immediately.
For the record, it is more than pointless to send disclaimers like this to open mailing lists. These mails will obviously be sent to all subscribers as well as be publicly available in our mail archives. We will not delete the e-mail. If possible, please don't send void legalese to our public mailing lists. Thanks! ~N
participants (3)
-
Holger Freyther -
Neels Hofmeyr -
Popovic Goran