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/baseband-devel@lists.osmocom.org/.
Kurtis Heimerl kheimerl at cs.berkeley.eduThey're programmable as 'sysmosim-gr1' with pysim, that's all I really know. I bought them programmed from a vendor in China, who promptly screwed up the SMSC on 1000 sim cards. I'll take a look at the branch, seems very similar to what I need. Thanks! On Saturday, January 5, 2013, Sylvain Munaut <246tnt at gmail.com> wrote: > Hi, > > > I've got a stock of SIMs I bought and programmed already, but I > > unfortunately (and stupidly) forgot to set the SMSC. > > What type of SIMs exactly and how did you program them ? > > pySIM sets a default SMSC if you don't set one ... > > > > Looking at the pySim-prog, it looks like this probably isn't possible; > all > > of the data seems to get bundled together and so changing the SMSC length > > will cause other data to be corrupted. Is that right? I just wanted to > see > > what ya'll think would be the best way for me to remedy my particular > > stupidity. > > If you look in the ccc branch of pySIM, there is a ccc-fix.py script > that was written during 27C3 for fixing SMSC on cards we wrote (at the > time pysim was creating a corrupt smsc entry). > > It won't work "as-is", but you can look at the internal logic and > adapt ... essentially it read the personalization file, fix it and > rewrites it entirely. > > > Cheers, > > Sylvain > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20130105/94ba15b7/attachment.htm>