From lynxis at fe80.eu  Mon Oct 21 01:03:41 2019
From: lynxis at fe80.eu (Alexander 'lynxis' Couzens)
Date: Mon, 21 Oct 2019 03:03:41 +0200
Subject: [osmocom-event-orga] 36c3 ticket voucher
Message-ID: <20191021030341.3edc29ee@lazus.yip>

hi,

the 36c3 ticket shop is opening in a couple of hours.
Some already have an angel voucher.
If you need a voucher, please write me a mail, so I can ask for
vouchers.

best,
lynxis

-- 
Alexander Couzens

mail: lynxis at fe80.eu
jabber: lynxis at fe80.eu
gpg: 390D CF78 8BF9 AA50 4F8F  F1E2 C29E 9DA6 A0DF 8604
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.osmocom.org/mailman/private/osmocom-event-orga/attachments/20191021/f042a1cf/attachment.bin>

From lynxis at fe80.eu  Mon Oct 21 22:10:33 2019
From: lynxis at fe80.eu (Alexander 'lynxis' Couzens)
Date: Tue, 22 Oct 2019 00:10:33 +0200
Subject: [osmocom-event-orga] 36c3 ticket voucher
In-Reply-To: <20191021030341.3edc29ee@lazus.yip>
References: <20191021030341.3edc29ee@lazus.yip>
Message-ID: <20191022001033.69837a8e@lazus.yip>

> the 36c3 ticket shop is opening in a couple of hours.
> Some already have an angel voucher.
> If you need a voucher, please write me a mail, so I can ask for
> vouchers.

We've received a small bunch of vouchers.

best,
lynxis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.osmocom.org/mailman/private/osmocom-event-orga/attachments/20191022/da054e9c/attachment.bin>

From lynxis at fe80.eu  Mon Oct 21 22:14:21 2019
From: lynxis at fe80.eu (Alexander 'lynxis' Couzens)
Date: Tue, 22 Oct 2019 00:14:21 +0200
Subject: [osmocom-event-orga] 36c3 - who is helping?
Message-ID: <20191022001421.0646d71d@lazus.yip>

Hi,

the 36c3 is coming closer.
Can you add yourself to the wiki page, if you're coming to the congress?
And most important, when are you there?

E.g. If you want to help to build it up and tear down, but can't while
the congress, it would be nice to add it to the comment row.

https://code.fe80.eu/congressgsm/eventgsm/wikis/36c3/Overview

Best,
lynxis

ps: If you don't have an account yet, please write me a mail.
-- 
Alexander Couzens

mail: lynxis at fe80.eu
jabber: lynxis at fe80.eu
gpg: 390D CF78 8BF9 AA50 4F8F  F1E2 C29E 9DA6 A0DF 8604
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.osmocom.org/mailman/private/osmocom-event-orga/attachments/20191022/00ab9bd7/attachment.bin>

From laforge at osmocom.org  Tue Oct 22 07:09:59 2019
From: laforge at osmocom.org (Harald Welte)
Date: Tue, 22 Oct 2019 09:09:59 +0200
Subject: [osmocom-event-orga] 36C3 vouchers for Osmocom developers
Message-ID: <20191022070959.GH4389@nataraja>

Dear Osmocom developer community,

we have received a couple of replicating vouchers for 36C3, please
let me know if you'd like to receive one.

AFAIK, the team operating GSM/3G networks at the event has a separate
allocation available via Lynxis.

Regards,
	Harald
-- 
- Harald Welte <laforge at osmocom.org>            http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)


From keith at rhizomatica.org  Thu Oct 24 13:51:56 2019
From: keith at rhizomatica.org (Keith)
Date: Thu, 24 Oct 2019 15:51:56 +0200
Subject: [osmocom-event-orga] SMS
Message-ID: <4b91c3c9-2ad8-60dd-d3c2-0237f5c499fc@rhizomatica.org>

Hi All,

I've recently been experimenting with some Instant Message to SMS
gatewaying possibilities and so it occurs to me that maybe we could do
something more than previously with SMS at 36c3?

First off, two questions, maybe somebody here on this list has the answers.

1) Is there an external SMS Queue yet?, (or will there be)

2) At previous congress, i remember there was a possibility to dial
directly to any eventphone extension from the PSTN, I assume that
eventphone/poc had a large block of PSTN numbers routed, where the last
four digits was belonging to POC. I'm not sure this still exists? I know
there is outgoing to PSTN possibility, but that's not related. The
question is, if this incoming block still exists, is there any chance it
supports SMS?

3) I understand outgoing (to PSTN) capacity was donated.. I wonder would
also some SMS termination donation be possible?

Each extension registered with POC via the GURU3 is available as
sip:XXXX at voip.eventphone.de. correct? We could at least, (and with
minimum effort), support SIP MESSAGE here and forward to a GSM
extension. The other way around not so easy, unless the src is also a
POC registered extension. - that is to say, it would be trivial to do
SMS to sip extensions, but then.. would the SIP UAs support MESSAGE? If
they don't we can just queue the message, and wait (eternally?) for a
REGISTER from a SIP UA that does.
As for DECT, I do not know much about it. does DECT have messaging?

OK I'll now rant a little about some other ideas i am playing with,
regarding Telegram.

First, telegram, yes.. ugh.. centralised services.. etc.. and the rest,
let's not go into it.

The vaguely interesting thing about is that the TD Library allows
connecting an automated script as an account. Yes, there are also bots
but I don't want to talk about bots. (bots cannot initiate conversations
with random people, of course)

So here's an idea:

One registers a telegram account number for an event, then fire up a
script with this account.

GSM user sends SMS to PSTN number. We look it up and try to add it as a
contact on Telegram, if it exists we add an entry with src,destination,
and a converstation_id to a local datbase? - er like a..... IM-NAT :-)

Then send the message on to the telegram user. They'll get it as an
incoming message from an unknown (to them) telegram user (assuming they
do not magically have our event number in their contacts)

We prefix the message with an explanation of WTF is happening.

If they reply we forward the reply, using our nat table.. for a time..
(10 mins since last message seen?). after that the "NAT" expires and we
respond to anything further coming from telegram side with a message
saying we don't know who to forward to.

Telegram users could initiate conversations with some kind of message to
our NUMBER, like:

<--- "chat 3363"

----> "OK any further messages will be forwarded to GSM extension 3363,
go ahead and message..."


pitfalls:

1) telegram users could report us as spam, if this happens enough we
probably loose the ability to lookup contacts and send messages to
contacts that don't know us. Telegram also has privacy setting that
reject incoming messages from unknown contacts. I have no idea what
enough is, but if that happens then the whole system is screwed.

2) it's far too confusing and far away from the IM UX that people are
used to and it's wide open to people making a mistake and sending a
message to the wrong person.

3) if we don't use secret chats, any further login to this telegram
account can see the record of all messages (unless we delete them, I
think we could delete them immediatly after sending - I think we could
also use secret chats)

4) It's probably kind of pointless at congress??

thoughts?

Thanks!





From peter at stuge.se  Thu Oct 24 16:26:16 2019
From: peter at stuge.se (Peter Stuge)
Date: Thu, 24 Oct 2019 16:26:16 +0000
Subject: [osmocom-event-orga] SMS
In-Reply-To: <4b91c3c9-2ad8-60dd-d3c2-0237f5c499fc@rhizomatica.org>
References: <4b91c3c9-2ad8-60dd-d3c2-0237f5c499fc@rhizomatica.org>
Message-ID: <20191024162616.6025.qmail@stuge.se>

Keith wrote:
> 2) At previous congress, i remember there was a possibility to dial
> directly to any eventphone extension from the PSTN, I assume that
> eventphone/poc had a large block of PSTN numbers routed, where the last
> four digits was belonging to POC. I'm not sure this still exists?

It does.


> I know there is outgoing to PSTN possibility, but that's not related.

It's the same trunk.


> The question is, if this incoming block still exists, is there any
> chance it supports SMS?

Good question. I'm not sure who would know. At some point of course
it does, but I don't know if SMS would arrive at POC.


> Each extension registered with POC via the GURU3 is available as
> sip:XXXX at voip.eventphone.de. correct?

AFAIK that's not correct, I think only the extensions explicitly
registered as SIP extensions are available via SIP.


> would the SIP UAs support MESSAGE?

Some do, many (hardphones in particular) don't.


> So here's an idea:

I'd like to suggest starting with something a bit simpler. It's
relatively easy to create an XMPP message bridge. I'd try to do
that instead.


//Peter


From miaoski at gmail.com  Thu Oct 24 22:39:55 2019
From: miaoski at gmail.com (Miao~)
Date: Fri, 25 Oct 2019 06:39:55 +0800
Subject: [osmocom-event-orga] SMS
In-Reply-To: <20191024162616.6025.qmail@stuge.se>
References: <4b91c3c9-2ad8-60dd-d3c2-0237f5c499fc@rhizomatica.org>
 <20191024162616.6025.qmail@stuge.se>
Message-ID: <CAG9n-i4KprteeehRHY21WOhQ-LmZJWAMMaoDWcBhp_E7aot5qw@mail.gmail.com>

Keith,

There are quite a lot of Telegram bot doing protocol forwarding, but no
SMS.  I like this idea.  I can help coding if you have a working SMS-C.
However, there are three phones in CCC: GSM, DECT, SIP.  I'm not sure if
DECT phone does SMS...


Miaoski.

2019?10?25?(?) 0:33 Peter Stuge <peter at stuge.se>:

> Keith wrote:
> > 2) At previous congress, i remember there was a possibility to dial
> > directly to any eventphone extension from the PSTN, I assume that
> > eventphone/poc had a large block of PSTN numbers routed, where the last
> > four digits was belonging to POC. I'm not sure this still exists?
>
> It does.
>
>
> > I know there is outgoing to PSTN possibility, but that's not related.
>
> It's the same trunk.
>
>
> > The question is, if this incoming block still exists, is there any
> > chance it supports SMS?
>
> Good question. I'm not sure who would know. At some point of course
> it does, but I don't know if SMS would arrive at POC.
>
>
> > Each extension registered with POC via the GURU3 is available as
> > sip:XXXX at voip.eventphone.de. correct?
>
> AFAIK that's not correct, I think only the extensions explicitly
> registered as SIP extensions are available via SIP.
>
>
> > would the SIP UAs support MESSAGE?
>
> Some do, many (hardphones in particular) don't.
>
>
> > So here's an idea:
>
> I'd like to suggest starting with something a bit simpler. It's
> relatively easy to create an XMPP message bridge. I'd try to do
> that instead.
>
>
> //Peter
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.osmocom.org/mailman/private/osmocom-event-orga/attachments/20191025/95a8edf6/attachment.htm>

From marcus at hostalia.de  Fri Oct 25 08:24:09 2019
From: marcus at hostalia.de (Marcus =?ISO-8859-1?Q?M=FCller?=)
Date: Fri, 25 Oct 2019 10:24:09 +0200
Subject: [osmocom-event-orga] SMS
In-Reply-To: <CAG9n-i4KprteeehRHY21WOhQ-LmZJWAMMaoDWcBhp_E7aot5qw@mail.gmail.com>
References: <4b91c3c9-2ad8-60dd-d3c2-0237f5c499fc@rhizomatica.org>
 <20191024162616.6025.qmail@stuge.se>
 <CAG9n-i4KprteeehRHY21WOhQ-LmZJWAMMaoDWcBhp_E7aot5qw@mail.gmail.com>
Message-ID: <47078d71cb353b45be06253abf20caebeef68fee.camel@hostalia.de>

Hey Miaoski, 

I remember a couple Gigaset phones having a setting where you could
configure an SMSC to use.

ETSI [1, p. 63ff] suggests that it's standardized, and that they stick
to GSM mechanisms for anything that's not between handset and the FP.

General cheering in your direction,
Marcus

[1] https://www.etsi.org/deliver/etsi_en/300700_300799/300757/01.03.01_60/en_300757v010301p.pdf

On Fri, 2019-10-25 at 06:39 +0800, Miao~ wrote:
> Keith,
> 
> There are quite a lot of Telegram bot doing protocol forwarding, but
> no SMS.  I like this idea.  I can help coding if you have a working
> SMS-C.  However, there are three phones in CCC: GSM, DECT, SIP.  I'm
> not sure if DECT phone does SMS...
> 
> 
> Miaoski.
> 
> 2019?10?25?(?) 0:33 Peter Stuge <peter at stuge.se>:
> > Keith wrote:
> > > 2) At previous congress, i remember there was a possibility to
> > dial
> > > directly to any eventphone extension from the PSTN, I assume that
> > > eventphone/poc had a large block of PSTN numbers routed, where
> > the last
> > > four digits was belonging to POC. I'm not sure this still exists?
> > 
> > It does.
> > 
> > 
> > > I know there is outgoing to PSTN possibility, but that's not
> > related.
> > 
> > It's the same trunk.
> > 
> > 
> > > The question is, if this incoming block still exists, is there
> > any
> > > chance it supports SMS?
> > 
> > Good question. I'm not sure who would know. At some point of course
> > it does, but I don't know if SMS would arrive at POC.
> > 
> > 
> > > Each extension registered with POC via the GURU3 is available as
> > > sip:XXXX at voip.eventphone.de. correct?
> > 
> > AFAIK that's not correct, I think only the extensions explicitly
> > registered as SIP extensions are available via SIP.
> > 
> > 
> > > would the SIP UAs support MESSAGE?
> > 
> > Some do, many (hardphones in particular) don't.
> > 
> > 
> > > So here's an idea:
> > 
> > I'd like to suggest starting with something a bit simpler. It's
> > relatively easy to create an XMPP message bridge. I'd try to do
> > that instead.
> > 
> > 
> > //Peter



From keith at rhizomatica.org  Fri Oct 25 15:49:32 2019
From: keith at rhizomatica.org (Keith)
Date: Fri, 25 Oct 2019 17:49:32 +0200
Subject: [osmocom-event-orga] SMS
In-Reply-To: <20191024162616.6025.qmail@stuge.se>
References: <4b91c3c9-2ad8-60dd-d3c2-0237f5c499fc@rhizomatica.org>
 <20191024162616.6025.qmail@stuge.se>
Message-ID: <64083a12-ac96-73ed-c0a7-02fde25fce38@rhizomatica.org>


On 24/10/2019 18:26, Peter Stuge wrote:
> Keith wrote:
>
> The question is, if this incoming block still exists, is there any
> chance it supports SMS?
> Good question. I'm not sure who would know. At some point of course
> it does, but I don't know if SMS would arrive at POC.

Ok, so according to [1] this trunk may be generously supplied by nexmo?

I used nexmo for our SMS over ShortWave relay to the amazon experiment.
incoming SMS is forwarded to a "webhook endpoint" [2]

Maybe this service is active?


>
>> Each extension registered with POC via the GURU3 is available as
>> sip:XXXX at voip.eventphone.de. correct?
> AFAIK that's not correct, I think only the extensions explicitly
> registered as SIP extensions are available via SIP.

Ah. let me clarify "available" One can of course place a call to a GSM/
DECT extension from a SIP extension. that's done with an
INVITE sip:GSM_EXT at voip.eventphone.de

The question is, and i think this is what you refer to, that eventphone
probably replies with a 401 Unauthorized so you need to send your SIP
extension credentials to complete the call, that is, you need to hace
registered a SIP extension to make calls via voip.eventphone.de

An IP could be whitelisted to allow sending of SIP MESSAGEs from a
gatewaying service.

>
>> would the SIP UAs support MESSAGE?
> Some do, many (hardphones in particular) don't.

Correct, I didn't phrase well what I was saying. It was more a pondering
over how many MESSAGE supporting UAs would be present.

>
>> So here's an idea:
> I'd like to suggest starting with something a bit simpler. It's
> relatively easy to create an XMPP message bridge. I'd try to do
> that instead.

I considered implementing an XMPP <-> SMS some time ago for rhizomatica.
In the end I never did it, I stopped when the main(stream) IM suppliers
on the corporate internet finally de-federalized themselves. Not
relevant to congress of course, but there is an interesting question
about how to compose a message (initiate a conversation) to an XMPP
account from an SMS phone.



[1] https://eventphone.de/blog/2018/08/31/emf-dialout-restrictions/

[2] https://developer.nexmo.com/api/sms#inbound-sms




From keith at rhizomatica.org  Sat Oct 26 13:05:42 2019
From: keith at rhizomatica.org (Keith)
Date: Sat, 26 Oct 2019 15:05:42 +0200
Subject: [osmocom-event-orga] 36c3 ticket voucher
In-Reply-To: <20191022001033.69837a8e@lazus.yip>
References: <20191021030341.3edc29ee@lazus.yip>
 <20191022001033.69837a8e@lazus.yip>
Message-ID: <ebb7d854-4c7e-4bfa-16d1-962b6e898660@rhizomatica.org>


On 22/10/2019 00:10, Alexander 'lynxis' Couzens wrote:
>> the 36c3 ticket shop is opening in a couple of hours.
>> Some already have an angel voucher.
>> If you need a voucher, please write me a mail, so I can ask for
>> vouchers.
> We've received a small bunch of vouchers.

hi lynxis

I got a angel voucher which replicated,? that replication is now also
consumed.

I was asked (again) yesterday if a voucher can be obtained.

not related to GSM orga, not related to anything really, just somebody
who wants to go. (stammtisch person)

I'm not sure how best to respond when people ask me about vouchers.

sorry for OT noise on list.




From keith at rhizomatica.org  Sat Oct 26 13:09:52 2019
From: keith at rhizomatica.org (Keith)
Date: Sat, 26 Oct 2019 15:09:52 +0200
Subject: [osmocom-event-orga] SMS
In-Reply-To: <CAG9n-i4KprteeehRHY21WOhQ-LmZJWAMMaoDWcBhp_E7aot5qw@mail.gmail.com>
References: <4b91c3c9-2ad8-60dd-d3c2-0237f5c499fc@rhizomatica.org>
 <20191024162616.6025.qmail@stuge.se>
 <CAG9n-i4KprteeehRHY21WOhQ-LmZJWAMMaoDWcBhp_E7aot5qw@mail.gmail.com>
Message-ID: <5bca900b-2d08-a560-64dc-27180e5b0112@rhizomatica.org>


On 25/10/2019 00:39, Miao~ wrote:
> Keith,
>
> There are quite a lot of Telegram bot doing protocol forwarding, but
> no SMS.? I like this idea.? I can help coding if you have a working
> SMS-C.? However, there are three phones in CCC: GSM, DECT, SIP.? I'm
> not sure if DECT phone does SMS...
>
>
>
hi Miaoski!

I took a look at some possibilities for Telegram bot coding. Seems for
sure there is quite a lot out there already and also there are a few
frameworks for writing telegram bots, for example in python, nodeJS (I
have reservations about node) and one can do quite a lot with them. I
think the best example of that I have seen is a ride sharing bot.

I thought about doing a bot that allows a conversation initiation from
bot side. something along the lines of

/start

/chat 3363 or whatever..

That should be pretty easy to do for sure. The "working SMS-C" is for
the moment, the SMS-C that exists inside osmo-msc.

One thing about telegram bots is that they cannot (good thing!) initiate
conversations to telegram users, or lookup telegram users by phone
number. so that is why I thought about using an actual account to be
able to do that, but like I said, it's wide open to a SPAM reporting
attack.






From xro at realraum.at  Sat Oct 26 13:50:07 2019
From: xro at realraum.at (Bernhard Tittelbach)
Date: Sat, 26 Oct 2019 15:50:07 +0200
Subject: [osmocom-event-orga] 36c3 ticket voucher
In-Reply-To: <ebb7d854-4c7e-4bfa-16d1-962b6e898660@rhizomatica.org>
References: <20191021030341.3edc29ee@lazus.yip>
 <20191022001033.69837a8e@lazus.yip>
 <ebb7d854-4c7e-4bfa-16d1-962b6e898660@rhizomatica.org>
Message-ID: <cabdde21-d217-3747-c0f7-638853fe221a@realraum.at>

On 10/26/19 3:05 PM, Keith wrote:
> On 22/10/2019 00:10, Alexander 'lynxis' Couzens wrote:
>>> the 36c3 ticket shop is opening in a couple of hours.
>>> Some already have an angel voucher.
>>> If you need a voucher, please write me a mail, so I can ask for
>>> vouchers.
>> We've received a small bunch of vouchers.
> hi lynxis
>
> I got a angel voucher which replicated,? that replication is now also
> consumed.
>
> I was asked (again) yesterday if a voucher can be obtained.
>
> not related to GSM orga, not related to anything really, just somebody
> who wants to go. (stammtisch person)
>
> I'm not sure how best to respond when people ask me about vouchers.
>
> sorry for OT noise on list.
>
Hi Keith,

I'm coordinating the voucher distribution for our hackerspace and Graz,
so maybe my experience is helpful.(?)

CCCV specifially told us:

**Please spread those vouchers in your community and its surroundings** (both socially and geographically). The vouchers are explicitly **not only for your members**, but are meant for people who belong (or should belong) in the Chaos community, and to bring the community closer. Please invite people to 36C3 whom *you*'d like to see there.


Thus for our vouchers we create a list of people who want a ticket AND make sure that all vouchers generated from those are returned to us.
Then everyone in the queue gets a voucher and we forward the generated vouchers to the next person in the queue.
We prioritize members and people who went last year and are known to pay quickly.
Basically, anybody who asks and got the information via our hackerspace information channels and is interested, can have a place on the queue.
If the vouchers don't run out and everybody is quick, she/he will get a ticket.


GSM-group is not a geographically local group, but once you ensured that GMS-core can go to congress :-) (we want GSM after all),
I think it's ok to give people a voucher if you think they are suited for congress and if you trust them you send the generated voucher
back to you.

cheers,
Bernhard





From keith at rhizomatica.org  Sat Oct 26 16:41:25 2019
From: keith at rhizomatica.org (Keith)
Date: Sat, 26 Oct 2019 18:41:25 +0200
Subject: [osmocom-event-orga] 36c3 ticket voucher
In-Reply-To: <cabdde21-d217-3747-c0f7-638853fe221a@realraum.at>
References: <20191021030341.3edc29ee@lazus.yip>
 <20191022001033.69837a8e@lazus.yip>
 <ebb7d854-4c7e-4bfa-16d1-962b6e898660@rhizomatica.org>
 <cabdde21-d217-3747-c0f7-638853fe221a@realraum.at>
Message-ID: <cf2df86f-1778-da4c-b185-352ddf24a342@rhizomatica.org>

OK, given what

On 26/10/2019 15:50, Bernhard Tittelbach wrote;

hereby goes a shout out to the GSM community that if there's a voucher
about, I know somebody not related to this community and I would like
them to go to congress...

I think this person will pay quickly, so if the voucher replicates, I
think we'll get it back quick.


thanks :)




From keith at rhizomatica.org  Sat Oct 26 16:42:29 2019
From: keith at rhizomatica.org (Keith)
Date: Sat, 26 Oct 2019 18:42:29 +0200
Subject: [osmocom-event-orga] SMS/USSD/maybe other issues.
Message-ID: <9e93016b-9a76-221b-9204-55ef47eb7b18@rhizomatica.org>

couple of other things I wanted to flag, and this might be best
continued as issues on code.fe80.eu?

USSD API - We spoke about this last year, but did anything happen on
getting it working?

How about an SMS Shortcodes API? Has that been done before?


k/





From nhofmeyr at sysmocom.de  Tue Oct 29 13:57:51 2019
From: nhofmeyr at sysmocom.de (Neels Hofmeyr)
Date: Tue, 29 Oct 2019 14:57:51 +0100
Subject: [osmocom-event-orga] SMS
In-Reply-To: <4b91c3c9-2ad8-60dd-d3c2-0237f5c499fc@rhizomatica.org>
References: <4b91c3c9-2ad8-60dd-d3c2-0237f5c499fc@rhizomatica.org>
Message-ID: <20191029135751.GA27918@my.box>

On Thu, Oct 24, 2019 at 03:51:56PM +0200, Keith wrote:
> 2) At previous congress, i remember there was a possibility to dial
> directly to any eventphone extension from the PSTN, I assume that
> eventphone/poc had a large block of PSTN numbers routed, where the last
> four digits was belonging to POC. I'm not sure this still exists? I know
> there is outgoing to PSTN possibility, but that's not related. The
> question is, if this incoming block still exists, is there any chance it
> supports SMS?

You should definitely also talk to the POC directly, I suggest thomasDOTwtf,
he's fun to deal with and he would probably be a good support there.

He's at least on the IRC hackint #c3-gsm, or I'm pretty sure he doesn't mind me
sending you his nr, which I'm doing now.

~N
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.osmocom.org/mailman/private/osmocom-event-orga/attachments/20191029/28c556a5/attachment.bin>

From keith at rhizomatica.org  Tue Oct 29 16:34:40 2019
From: keith at rhizomatica.org (Keith)
Date: Tue, 29 Oct 2019 17:34:40 +0100
Subject: [osmocom-event-orga] SMS
In-Reply-To: <20191029135751.GA27918@my.box>
References: <4b91c3c9-2ad8-60dd-d3c2-0237f5c499fc@rhizomatica.org>
 <20191029135751.GA27918@my.box>
Message-ID: <e0c0fb9f-3df1-699d-beda-c2696f41c122@rhizomatica.org>


On 29/10/2019 14:57, Neels Hofmeyr wrote:
> On Thu, Oct 24, 2019 at 03:51:56PM +0200, Keith wrote:
>>  if this incoming block still exists, is there any chance it
>> supports SMS?
> You should definitely also talk to the POC directly, I suggest thomasDOTwtf,
> he's fun to deal with and he would probably be a good support there.
Yes, we met last year.. maybe thomasDOTwtf is on this list?
>
> He's at least on the IRC hackint #c3-gsm, or I'm pretty sure he doesn't mind me
> sending you his nr, which I'm doing now.

Thanks!

I'm going to be getting back to ccc preps 3rd week november, as i'm now
out of time before then.

k.




From arne at nerdkeller.org  Thu Oct 31 11:08:20 2019
From: arne at nerdkeller.org (Arne Zachlod)
Date: Thu, 31 Oct 2019 12:08:20 +0100
Subject: [osmocom-event-orga] BnetzA regional and local networks
Message-ID: <23242db5-2747-f0a3-a77b-c87e8099eed9@nerdkeller.org>

Hi,

the BnetzA just published the scale of charges for local networks 
operation in 3.7 to 3.8 GHz [1]. While not immediately interesting for 
us, this could be a cheap enough method to have our own LTE frequencies 
(bands 42 and 43 if I'm not missing something).

The formula for Leipzig Messe (800 by 500 meters) would look like this 
(for a 10 Year lease of 20 MHz):

Pay = 1000 + 20 * 10 * 5 (6 * (800 * 500)/1000^2)
Pay = 3400 (totally possibile I did an oopsie here)

Maybe this can spark a discussion and a more solid plan to roll out LTE 
in the future.

bye
Arne

[1] 
https://www.bundesnetzagentur.de/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Frequenzen/OeffentlicheNetze/LokaleNetze/lokalenetze-node.html