All of 9006, PhoneMail, Models 10, 40, 50 and 70 were put on end of life on March 31, 2011. That was not the end of service or support, and parts can still be gotten on an as-available basis until inventory runs out. No new software features or additions will be done.
That's straight off the memo I was sent in early 2011.
They're listed on the same memo, which actually states they are going end of life with "Legacy" equipment, and then has a list of stuff that was included in that term.... They pretty much ran out of parts to do 9006.6 upgrades even before that memo came out, because I was denied one in 2010 already due to lack of parts. In that case I just went and bought an 80 from a nearby bank that was already on 9006.6 and they had pulled all the station cards out of it when they upgraded to something else - then they just did an SMR upgrade and a reconfig on it before we put it in service.
There's many large companies that still have the Siemens 9006 and even the Rolm 9005 systems. NBC's headquarters I believe has or had either a Rolm 9005 or Siemens 9006 - on the nightly news I've seen RP6XX series phones. I think for now they can get service from a business partner. As you've said - parts getting harder to come by. In fact right now I'm in the process of building a hard drive for yet another 9006 that the local tech reported as getting loud. I did that same system 3 years ago. I do have a hard drive from a retired 9006, I'm in the process of copying the database of the one with the noisy hard drive with a DAT backup to it. I've done it a few times before - I keep the existing Unix and copy RMX only. But in the beginning of the script I have to keep going into Debug mode to skip to the next command, activate the drive etc. so commands will run. A lot of manual intervention. Sometimes I think it would be easier to just format the HD and do a 'normal' recovery with the ISYAP tape the the RMX backup. The way I've done it is just from an RMX backup. If this neither works, such as the case of a bad DAT, it will all have to be done a command at a time to configure everything manually, I hope not.
I'm naughty - usually if I get stuck building a new drive I will take the newest release of that same version I have lying around and build it to that. I've actually gained a few features that way in the last - like one of my older 6.4 systems lost a drive and I built that back to a new enough version that I can actually use LC-Win on it now! It can get risky with 6.5 though because there were 2 versions that were ba$tard children of each other (kind of like Windows ME - they made it, said "oops" and quick released something else). I'm not sure if the databases are compatible between 6.5 and 6.5A - I know LC-Win isn't....
Nothing wrong with that - and being able to use LC-Win is nice. Of course I can't on the 9006.3. The recovery went fine - you know you're in the clear when the script asks you if daylight savings time applies to your area. I have a script for that, ADD-SONUS but at first wasn't actually adding the line. I then realized the script was for Direct Amo while I was still in RMX. I just copied everything to Wordpad and changed ^M (enter) to ^C, added dates to 2018 (if the 9006s last that long) copied it back and compiled it into the script specifically for RMX. I remember a customer that at times couldn't use LC-Win, I'd need to deactivate and activate something. LCT maybe? Or - since the customer would use both EMML and LC-Win (I heard that's n/g) I'd see 'error writing amo DEST into the database..' and others similar. That's when I'd have to do a generate station database. Would take a few hours on that Mod 80. LC-Win was good - I remember there was one thing that couldn't be added in LC-Win, something to do with ACD, a pilot number that referenced an RCG? I never charged customers if they put in a MAC order for that.
If you use both EMML and LC-Win you will need to go in and do the Regen Database function (in EMML if your version is old enough) because LC-Win makes changes that EMML doesn't know about and vice versa. If you build a station or something and then go in to edit it and the system tells you it doesn't exist then it's time to regen the database.
First regen the database (all of them) and then go into Direct AMO and do this:
exe-xapc:a1,deact.LCT;
I think that's the syntax. Otherwise do exe-xapc, and if it asks for server it's A1, and the next command is deact.LCT
Give that a few seconds to settle and then do the same thing with act.LCT
When you reactivate LC-Win it reindexes its own database to what the EMML database is - that's why it's best to regen the EMML stuff first.
I have a SONUS script around someplace - I have 7 systems and I got sick of doing them all by hand!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.