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/.
Keith keith at rhizomatica.orgOn 02/01/2019 13:46, Max wrote: > Hi. > > > 02.01.19 13:11, Keith пишет: > > 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. > * > It's probably not a BUG as such, but rather a (lack of) implementation in the configured dialplan. I'm not so familiar with YATE, but I would imagine it is probably something that would have also been fixed by a simple regex modification in some yate config file. '^(+|00)' or something.. you make a good point though, and I glad I asked before submitting a patch. all the same, maybe it might be a nice thing for users to have, just as a convenience? Without a config option, for a user faced with a non compliant upstream SIP UA over which they have no control, they would have no choice but to patch and recompile the sip connector. >> 2) 3G data instabilities >> >> >> >> 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" > 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?). I don't know if there's a specific issue for this as such, there are a number of issues that would seem related, but most of them filed under OsmoPCU. I believe there is something(s) wrong in the core components, and that was indeed the local feedback I got in the GSM room.. :)) but I don't know what to file. I'd need to get 3G setup at home to contribute anything useful, hence the simple note. k/