Osmocom Analog

I cannot seem to get -x working either, using the AMPS software. Seems to be a bug.

aldude999 wrote:

I cannot seem to get -x working either, using the AMPS software. Seems to be a bug.

Perhaps there are additional components needed? I don't believe this is the case as no such dependencies are mentioned anywhere in the documentation. Are the issues you are experiencing similar to mine?

mstamm wrote:

aldude999 wrote:

I cannot seem to get -x working either, using the AMPS software. Seems to be a bug.

Perhaps there are additional components needed? I don't believe this is the case as no such dependencies are mentioned anywhere in the documentation. Are the issues you are experiencing similar to mine?

Same issue, it just plays the default music. It doesn't seem to cause any issues with the osmocc-sock capability though.

Just pushed a fix to master branch. It should work now.

any chance to hear in my subject from you Jolly ? Greetings from Poland :)

jolly wrote:

Just pushed a fix to master branch. It should work now.

I'm extremely happy to confirm it works. Mobiles I have tested are AEG Telecar CD 452, Nokia C-130, Philips MiniPorty. Signalling works in both directions, and calls connect. A big thank-you to jolly for this fast fix!

mstamm wrote:

jolly wrote:

Just pushed a fix to master branch. It should work now.

I'm extremely happy to confirm it works. Mobiles I have tested are AEG Telecar CD 452, Nokia C-130, Philips MiniPorty. Signalling works in both directions, and calls connect. A big thank-you to jolly for this fast fix!

I have tried on NMT - it sounds like when are two channesl and two cards selected :

nmt -k 1 -k 4 -a hw:1,0 -a hw:2,0 -T CC/TC -T CC/TC -0 1 -0 1 -Y pl,1 -x

then in second card are strange sounds - from example here - i could hear strange sound in channel 4 in my case, but when I launch one channel :

nmt -k 1 -Y pl,2 -a hw:1,0 or nmt -k 1 -Y pl,2 -a hw:2,0 the transmitting channels are clear ... any reason for that when I enable both channels with -x command ?

FYI, we just created the osmocom-analog mailinglist for general discussion unrelated to bugs/issues here: https://lists.osmocom.org/mailman/listinfo/osmocom-analog

For the record:

There is one issue perhaps related: I cannot use a locally connected headset as a sound device to place a call from the console to a mobile. Compiling osmocom-analog from the eversberg.eu repository, ALSA support was shown as active, and alsamixer can configure the headset (a Jabra USB headset), and I can use the headset for all other applications. However, when I start cnetz with the associated parameter, I get the message that sound support is not compiled in. I did not investigate this issue further as my first goal was and is mobile-to-mobile calls, and eventually mobile-to-sip and sip-to-mobile calls, but perhaps this may be a related issue or point to a common cause? I greatly appreciate any help.

is also resolved but was quite unrelated. It turns out I had to run make clean, then make, as I had already previously compiled osmocom-analog without sound support, and after a make clean and make, the sound adapter also works using the -c option.

aldude999, atmega, mstamm I also gave all of you some more permissions here, so you can now create/edit wiki pages, if you want to share some of your findings on how to get osmocom-analog working, or the like.

laforge wrote:

aldude999, atmega, mstamm I also gave all of you some more permissions here, so you can now create/edit wiki pages, if you want to share some of your findings on how to get osmocom-analog working, or the like.

laforge - Cool, thank you. Actually, creating one or more Wiki pages is exactly what I had in mind. When it comes to LimeSDR operations and specifically osmocom-analog, I feel like I'm the new kid on the block. I have been playing with openSUSE Tumbleweed occasionally with a view to perhaps eventually replacing my Windows-based infrastructure with Linux, and I had to learn using LimeSDR and setting up osmocom-analog from scratch (including some learning on using alsa, compiling, identifying missing components, differentiating between distribution-based components and myriadrf-provided ones, resolving conflicts, etc etc) since I got my hardware on 01 March. I found the documentation provided by jolly very helpful, and believe a collection of "HOWTO" recipes in the Wiki will help others. Now that I have mobile-to-mobile calls and console-to-mobile calls sorted out, the next agenda item will be getting the osmo-cc-sip-endpoint to work, and then later calls between C-Netz and AMPS and/or TACS mobiles. Undoubtedly, this will take me along another steep learning curve, and I'll be happy to share the results.

The issue has been identified and remedied, so I'm closing this issue.