From laforge at gnumonks.org Sun Mar 7 15:20:32 2021 From: laforge at gnumonks.org (Harald Welte) Date: Sun, 7 Mar 2021 16:20:32 +0100 Subject: [osmocom-analog] test, please ignore Message-ID: test if the mailing list works as expected -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From atmega at wp.pl Sun Mar 7 20:09:24 2021 From: atmega at wp.pl (=?UTF-8?Q?atmega=40wp=2Epl?=) Date: Sun, 07 Mar 2021 21:09:24 +0100 Subject: [osmocom-analog] =?utf-8?q?Hello_to_all!_let=27s_make_NMT_call_t?= =?utf-8?q?o_public_over_SIP?= Message-ID: Hey there ! I am excited that this topic started ;-) I am 40 yo guy from Poznan, Poland, about 2 decades ago I had pleasure to work with NMT Centertel Dealer. It brings for me great memories. Recently I managed to collect some NMT phones - at the moment I have more than 10 fully functional NMT phones: Nokia 250, 350, 440, 450, 540, 550, 650,? Benefon Delta, Benefon Sigma, Benefon Spica, Motorola Associate 2000. I have four Baofeng radios, buils Linux based pc, bought 2 USB cards and managed to compile, run and work Osmocom - Analog and called phone to phone. Also Computer to phone over headphones. I was also trying to launch LCR, bought ISDN card Fritz, and was attempting to use FritzBox with built - in VOIP - Isdn gate and try to make my NMT phone call PSTN over Voip and mISDN/LCR router. So far no succes. I am not a specialist - self learned electronic - hobbyst. If I could afford it I would buy LimeSDR but for the moment it is a bit expensive for me. Anyway - I have tried OSMO-CC-ENDPOINT as I realised that I will not need any LCR / mISDN / asterisk anymore. I did try many times but all I can get is an update about authentication error with my SIP provider. here is log : osmocom-analog connects to osmo-cc-sip-endpoint, but it looks like SIP-Endpoint does not connects to my SIP provider. I did forward 5060 ports to my linux pc, what could I do wrong: sip.c:1430 debug : Event 29 from SIP stack received (handle=0x55cb861d7980) sip.c: 921 info : Received REGISTER response: 401 Unauthorized (registration) sip.c: 943 debug : Register challenge received sip.c: 178 debug : challenge order received sip.c: 194 notice : No authentication header found sip.c: 954 debug : Register failed, starting register timer sip.c: 956 debug : destroying nua_handle 0x55cb861d7980 (register) using this command line: osmo-cc-sip-endpoint -r mysipnumber at mysipserverip -l localIPosmocom-analog -A SipAccountUser SipAccountPass --remote-auth --register SIPAccountUser at SipServerIp --cc 'screen-called-in "" "myNMTphone"' -P myPublicIP -v 0 Any ideas what do I do wrong? Many greetings for All people in osmocom-analog subjects. I am fascinated about this historical technology. Would be very happy if I could call somebody from my NMT phone ! Regards for all people who work with osmocom-analog subject. Respect to all! Jacek -------------- next part -------------- An HTML attachment was scrubbed... URL: From andreas at eversberg.eu Sat Mar 20 10:59:51 2021 From: andreas at eversberg.eu (Andreas Eversberg) Date: Sat, 20 Mar 2021 11:59:51 +0100 Subject: [osmocom-analog] Osmo-CC documentation Message-ID: Hi, Osmo-CC endpoints are still work in progress. I? have seen that people are already started to play with it, so I started a documentation for all endpoints, which is also work in progress. This document will help to set up different endpoints. One example is interfacing an endpoint (osmocom-analog) with SIP. See attachment. The osmo-cc-alsa-endpoint that is also described in the doc is not yet available on git.osmocom.org. Temporarily you can download it here: http://download.eversberg.eu/temp/osmo-cc-alsa-endpoint.tar.gz (@Harald: Can you add this repository?) Also it would be nice to have Osmo-CC as project page at: http://osmocom.org/projects/ There I can upload the latest documentation. Regards, Andreas -------------- next part -------------- A non-text attachment was scrubbed... Name: osmo-cc-guide_3.pdf Type: application/pdf Size: 187558 bytes Desc: not available URL: From andreas at eversberg.eu Sat Mar 20 17:34:36 2021 From: andreas at eversberg.eu (Andreas Eversberg) Date: Sat, 20 Mar 2021 18:34:36 +0100 Subject: [osmocom-analog] Osmo-CC documentation In-Reply-To: References: Message-ID: Attached the new version od Osmo-CC documentation. On 20.03.21 11:59, Andreas Eversberg wrote: > Hi, > > Osmo-CC endpoints are still work in progress. I? have seen that people > are already started to play with it, so I started a documentation for > all endpoints, which is also work in progress. This document will help > to set up different endpoints. One example is interfacing an endpoint > (osmocom-analog) with SIP. See attachment. > > The osmo-cc-alsa-endpoint that is also described in the doc is not yet > available on git.osmocom.org. Temporarily you can download it here: > http://download.eversberg.eu/temp/osmo-cc-alsa-endpoint.tar.gz > (@Harald: Can you add this repository?) > > Also it would be nice to have Osmo-CC as project page at: > http://osmocom.org/projects/ There I can upload the latest documentation. > > Regards, > > Andreas -------------- next part -------------- A non-text attachment was scrubbed... Name: osmo-cc-guide_4.pdf Type: application/pdf Size: 282258 bytes Desc: not available URL: From andreas at eversberg.eu Sun Mar 21 13:12:55 2021 From: andreas at eversberg.eu (Andreas Eversberg) Date: Sun, 21 Mar 2021 14:12:55 +0100 Subject: [osmocom-analog] Osmo-CC documentation In-Reply-To: References:

Message-ID: <37525cbf-4281-fb19-4654-556f06f06bde@eversberg.eu> Below is a link to a new Osmo-CC documentation (still unfinished) including osmo-cc-sip-endpoint description. It is now complete for SIP with all examples I wanted to put in there. Be sure to install the latest version from GIT (osmo-cc-sip-endpoint), because I just fixed incoming registration, which I never tested before. http://download.eversberg.eu/temp/osmo-cc-guide_6.pdf From markus at stamm.nu Sun Mar 21 14:38:47 2021 From: markus at stamm.nu (Markus Stamm) Date: Sun, 21 Mar 2021 15:38:47 +0100 Subject: [osmocom-analog] Osmo-CC documentation In-Reply-To: <37525cbf-4281-fb19-4654-556f06f06bde@eversberg.eu> References:

<37525cbf-4281-fb19-4654-556f06f06bde@eversberg.eu> Message-ID: <9e38de44-44b8-ce42-5ad3-9b5a1441fa76@stamm.nu> Hi Andreas, this is really very helpful, thank you so much. I was able to understand how some of the options work from looking at the source code, but I still feel I lack some basic knowledge of how the different Osmo-CC components interact, and this documentation should help close those gaps quickly. For instance, using osmo-cc-sip-endpoint with a SipGate account and osmocom-analog's C-Netz module, I was able to make incoming calls from the PSTN to mobile C-Netz devices registered against osmocom-analog. I was not able to make outgoing calls, though, as I seem to be unable to make either osmocom-analog understand it needs to route the outbound call to osmo-cc-sip-endpoint, or make osmo-cc-sip-endpoint understand it must seize the call attempt and connect the call through the SIP provider. Also, I was unable to make the speaking-clock Zeitansage example work with osmocom-analog so I could call 1191 from the C-Netz mobiles registered against osmocom-analog, and I assume this is due to my lack of understanding on how to ensure calls to 1191 are properly routed from osmocom-analog to the Zeitansage module. Since the Zeitansage, in effect, is just another endpoint, I should be able to gain helpful insight from the documentation in that respect as well. Also, the OsmoCC-Router looks quite powerful and should allow for very flexible routing between a multitude of endpoints, based on routing scripts, so a documentation on this, as foreseen here for future additions, will also be extremely helpful. Thank you very much for this work. BR, Markus -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5718 bytes Desc: not available URL: From atmega at wp.pl Sun Mar 21 17:52:07 2021 From: atmega at wp.pl (=?UTF-8?Q?atmega=40wp=2Epl?=) Date: Sun, 21 Mar 2021 18:52:07 +0100 Subject: [osmocom-analog] =?utf-8?q?Odp=3A_Re=3A__Osmo-CC_documentation?= In-Reply-To: <> References: Message-ID: I wonder ... is there any chance to personalize - replace announcement tones in NMT system... like unacaliable message, instead of current music... regards Jacek Dnia 20 marca 2021 18:34 Andreas Eversberg <andreas at eversberg.eu> napisa?(a): Attached the new version od Osmo-CC documentation. On 20.03.21 11:59, Andreas Eversberg wrote: Hi, Osmo-CC endpoints are still work in progress. I? have seen that people are already started to play with it, so I started a documentation for all endpoints, which is also work in progress. This document will help to set up different endpoints. One example is interfacing an endpoint (osmocom-analog) with SIP. See attachment. The osmo-cc-alsa-endpoint that is also described in the doc is not yet available on git.osmocom.org. Temporarily you can download it here: download.eversberg.eu download.eversberg.eu (@Harald: Can you add this repository?) Also it would be nice to have Osmo-CC as project page at: osmocom.org osmocom.org There I can upload the latest documentation. Regards, Andreas -- osmocom-analog mailing list osmocom-analog at lists.osmocom.o lists.osmocom.org lists.osmocom.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at gnumonks.org Mon Mar 22 18:04:47 2021 From: laforge at gnumonks.org (Harald Welte) Date: Mon, 22 Mar 2021 19:04:47 +0100 Subject: [osmocom-analog] Osmo-CC documentation In-Reply-To: References: Message-ID: Hi Andreas, On Sat, Mar 20, 2021 at 11:59:51AM +0100, Andreas Eversberg wrote: > available on git.osmocom.org. Temporarily you can download it here: > http://download.eversberg.eu/temp/osmo-cc-alsa-endpoint.tar.gz (@Harald: Can > you add this repository?) the repository has just been created. > Also it would be nice to have Osmo-CC as project page at: > http://osmocom.org/projects/ There I can upload the latest documentation. see https://osmocom.org/projects/osmo-cc I've currently created it as sub-project to osmoocm-analog in the project hierarchy. If / once other project start using it, we can move it to another place in the hierarchy. This doesn't change any URLs / links, just where it appears in the project list. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From andreas at eversberg.eu Sun Mar 28 11:34:00 2021 From: andreas at eversberg.eu (Andreas Eversberg) Date: Sun, 28 Mar 2021 13:34:00 +0200 Subject: [osmocom-analog] Osmo-CC documentation In-Reply-To: References: Message-ID: Hi Harald, On 22.03.21 19:04, Harald Welte wrote: > the repository has just been created. Thanks for that. I pushed the 'alsa' endpoint. > see https://osmocom.org/projects/osmo-cc I just added two documents. One is the unfinished protocol specification and one the unfinished user's guide. For one that wants to try endpoints, pull latest version from their git repositories. Best regards, Andreas From markus at stamm.nu Mon Mar 29 21:25:19 2021 From: markus at stamm.nu (Markus Stamm) Date: Mon, 29 Mar 2021 23:25:19 +0200 Subject: [osmocom-analog] PBX sends PRACK during call progress which osmo-cc-sip-endpoint rejects In-Reply-To: References: Message-ID: On 07.03.2021 21:09, atmega at wp.pl wrote: > Hey there ! I am excited that this topic started ;-) > > I am 40 yo guy from Poznan, Poland, about 2 decades ago I had pleasure > to work with NMT Centertel Dealer. > > It brings for me great memories. Recently I managed to collect some NMT > phones - at the moment I have more than 10 fully functional NMT phones: > > Nokia 250, 350, 440, 450, 540, 550, 650, > > Benefon Delta, Benefon Sigma, Benefon Spica, Motorola Associate 2000. > > I have four Baofeng radios, buils Linux based pc, bought 2 USB cards and > managed to compile, run and work Osmocom - Analog and called phone to > phone. Also Computer to phone over headphones. > > I was also trying to launch LCR, bought ISDN card Fritz, and was > attempting to use FritzBox with built - in VOIP - Isdn gate and try to > make my NMT phone call PSTN over Voip and mISDN/LCR router. > > So far no succes. I am not a specialist - self learned electronic - > hobbyst. If I could afford it I would buy LimeSDR but for the moment it > is a bit expensive for me. > > Anyway - I have tried OSMO-CC-ENDPOINT as I realised that I will not > need any LCR / mISDN / asterisk anymore. > > I did try many times but all I can get is an update about authentication > error with my SIP provider. > > here is log : > > osmocom-analog connects to osmo-cc-sip-endpoint, but it looks like > SIP-Endpoint does not connects to my SIP provider. I did forward 5060 > ports to my linux pc, what could I do wrong: > > sip.c:1430 debug : Event 29 from SIP stack received (handle=0x55cb861d7980) > sip.c: 921 info : Received REGISTER response: 401 Unauthorized > (registration) > sip.c: 943 debug : Register challenge received > sip.c: 178 debug : challenge order received > sip.c: 194 notice : No authentication header found > sip.c: 954 debug : Register failed, starting register timer > sip.c: 956 debug : destroying nua_handle 0x55cb861d7980 (register) > > using this command line: > > osmo-cc-sip-endpoint -r mysipnumber at mysipserverip -l > localIPosmocom-analog -A SipAccountUser SipAccountPass --remote-auth > --register SIPAccountUser at SipServerIp --cc 'screen-called-in "" > "myNMTphone"' -P myPublicIP -v 0 > > Any ideas what do I do wrong? > > Many greetings for All people in osmocom-analog subjects. I am > fascinated about this historical technology. Would be very happy if I > could call somebody from my NMT phone ! > > Regards for all people who work with osmocom-analog subject. Respect to all! > > Jacek > -- Markus Stamm Beethovenstr. 31 91126 Schwabach Tel (09122) 81855 Mobil (0172) 8901780 Fax (09122) 81856 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5718 bytes Desc: not available URL: From markus at stamm.nu Mon Mar 29 21:34:30 2021 From: markus at stamm.nu (Markus Stamm) Date: Mon, 29 Mar 2021 23:34:30 +0200 Subject: [osmocom-analog] PBX sends PRACK during call progress which osmo-cc-sip-endpoint rejects In-Reply-To: References:

Message-ID: <9cccd0d9-8d0c-8474-c9f6-c025a5e223e2@stamm.nu> Dear all, please disregard my fist message in this thread - I was being a fast-fingered Freddy. What I wanted to post is this: With the help of the great examples on the mailinglist, I am able to successfully make incoming and outgoing C-Net/PSTN calls via Sipgate, a German SIP provider. As my PBX is SIP-capable (it is an Auerswald Compact 5000R), I wanted to attach osmo-cc-sip-endpoint to an extension of my PBX. The registration is successful, but when I receive a call, C-Netz (or Zeitansage) registers and accepts the incoming call, but the PBX does not understand the call is connected and keeps ringing the extension. Using SNGREP, I believe I found the cause. Following a 183 Session Progress message from osmo-cc-sip-endpoint to the PBX, the PBX transmits PRACK, and osmo-cc-sip endpoint responds with a message 504 Method Not Allowed. The PBX ignores this message 504 and keeps ringing the extension until I disconnect the call. Sipgate, by contrast, responds by sending ACK, not PRACK, and the call connects successfully. I'm considering opening a ticket with Auerswald on this and would greatly appreciate your expert views. To my understanding, a 504 Method Not Allowed should prompt the PBX to fall back to ACK, or at least realise there is an issue, and yet it seems to ignore the Method Now Allowed response from osmo-cc-sip-endpoint. Does this appear correct, or might there be an issue with Sofia-SIP? I'm attaching the capture file in case this were useful. Thank you so much in advance for your insights. BR, Markus -------------- next part -------------- A non-text attachment was scrubbed... Name: auerswald.pcap Type: application/octet-stream Size: 12233 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5718 bytes Desc: not available URL: