35c3 feedback

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Max msuraev at sysmocom.de
Wed Jan 2 12:46:31 UTC 2019


Hi.

Thanks for write-up.

Comments are inline below, here's another (unrelated) issue observed 
during 35c3: https://osmocom.org/issues/3741

02.01.19 13:11, Keith пишет:
> 1) SIP Connector handling of TON GSM340_TYPE_INTERNATIONAL
>
> Apparently at least one person was frustrated at the congress by not
> being able to call out using the numbers stored in their GSM handset
> using the form +CountryCode.
>
> As we know this appears at Call Control with TON intl, which sip
> connector then prefixes with '+' before sending to SIP
>
> The reason for lack of service at ccc was that the Yate pbx does not
> support this number scheme and needed the 00 prefix.

The *+12345... format is defined in **ITU-T E.123 so the lack of support 
for this format looks like a bug in Yate.*

*What about 00 prefix? Unless it's defined in some spec, I don't think 
it make sense to introduce options just to work around bug in particular 
PBX.
*

> 2) 3G data instabilities
>
> ( Just a quick observation note, no pcap! )
>
> I happened to notice that pinging a 3G handset from the network side
> (default ping: 1 sec internal, 64 ICMP bytes) keeps the connection
> "alive" and using 3G data is then a pleasant experience, IM, email,
> browsing, SIP call all working nicely. peak max download speed of 16Mbps
> was reported at one time by m.speedof.me
>
> However, stopping the ping results in loss of data conex within a few
> seconds, and the behaviour from users point of view is then strikingly
> similar to what's observed on 2G; and I am more or less convinced has to
> do with the unknown Timing Advance issues in the PCU.

Is there bug for this already? If both 2G and 3G have similar issues in 
the absence of MT traffic than there might be something wrong in the 
core components (SGSN/GGSN?).

-- 
- Max Suraev <msuraev at 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 Directors: Harald Welte




More information about the OpenBSC mailing list