MakeAvayaRedGreatAgain

Banned
  • Content count

    36
  • Joined

  • Last visited

  • Days Won

    2

MakeAvayaRedGreatAgain last won the day on April 16

MakeAvayaRedGreatAgain had the most liked content!

Community Reputation

-2 Noobie

About MakeAvayaRedGreatAgain

  • Rank
    H4x0r

Profile Information

  • Country
    United States
  • Location
    NH.US
  1. Good luck for a clear answer. Step by step directions is kinda DIY implenetation in this thread for sure. I believe the idea is not to have a vintage Linux box completely exposed to the Internet, like plugging your broadband modem into the Ethernet port, kinda thing. Here's what I would i recommend. I forget you have CLAN card and it's connector? You can program the PBX via ASA over IP, on your network and via ASA. The process is a bit complicated on MY part to explain in a few seconds, it's relatively easy. Check out this site and find the Section "Configuring TN-799 C-LAN [his spelling not mine] Card for Remote Administration". Sadly the plain-jane ASCII site is not loaded with screenies, but if you have a general idea (which I think you do) this shouldn't be too hard, just follow the steps carefully (speaking from experience) The other trick, if one is paranoid that a vintage operating system will break the internet worse than Kim Kardashian* you could have a different IP address range for your PBX. I have complex network at home, one safety measure other than firewalls, is to have my common network at 192.12.1.0/24 and a private, semi exposed/but more isolated network at 172.0.0.0/24, and only that latter network I use for management access. I have a PC on a static IP that shares the latter subnet, that I can get into my PBX from anywhere on the LAN. I don't do the routing here at the moment, so everything is "static" - a very LONG story. In your case, just assign the PBX to like 172.0.0.x, and if say for an example you have your home network on 192.168.1.0, you plug it in to that network; go to your network settings, and add a secondary IP address of 172.0.0.10/255.255.0.0 and go from there. (you would have to go through the walkthrough of setting it up on the ASA, make sure you use IPv4 and no DNS, etc. Hope this helps you get somewhere to your goal without much panic and fear. I'm so sorry if I went over your head for a simple question. (* Sidenote: In my opinion those claims a load of FUD BS - in fact no rank and file users are supposed to know what Linux kernel its running on by the minds of Avaya or any proprietary vendor. And if anyone here on the forums think it's perfectly OK to tamper with a "Linux" type of system designed for this context for voicemail, that's totally not cool and if you were attempting to patch it, that would void the warranty if you did this on a production system. This patching on semi proprietary systems have been brought up on listserves with telecom people debating that with nitwit server admins. It drives me NUTS... ) EDIT ADD: OK, I've spoke to some Avaya experts and let's be clear, anything greater than 10 or even R13 (as noted in an earlier commenter) would be very hard to do to reverse engineer. Why? Because at this point, it's the early days of the Communication Manager, the licensing moved to a server based platform (further away from the PBX and living on a private label HP or IBM server for the use of their PBX system moving softswitches...Kinda a linux instance in a VMware type of setup. The expert I spoke to used the System Platform service to move the license file from one system to another with R12 being the processor of interest. I think when by the time R12 was released, it was more dependent on server based management tools to handle the licensing, that was separate to the PBX and needed the IPSIs and CLANs to connect and register. I think it's safe to say anything past R10 that required this license management, and local/CLAN or serial transfers would really a hopeless cause unlike my earlier message because of the move from the hardware to the software platforms. By 2004 to 08, sure a CMC could run up to CM 4, but it was for you know sites that was still legacy based, but had a HQ that was more VOIP/CM based/server orientated/upgraded etc. and the CMC was the outskirts of the enterprise voice network. I felt there was a need to update and let the community know how the newer PPNs worked in the mind for the time in the real world installed base.
  2. What does that mean? How does that get achieved? I mean, such vague language can't run away under my eyes.
  3. From having basic exp with UNIX, it's trying to run a window program to function the GUI. In this case it would be Xwindows. When I installed it I entered "root" and I got into the prompt. Entered setup to get a static IP configuration, and tried to configure the Xwindows so I could use the GUI. Because i have this on a VMware vmachine, I don't know what driver it could take, so it would test then say it failed.
  4. what's "sa"? I suspect a problem with the Xwindows. I'm thinking there is a driver conflict. This has happened when I've used other Linux distros.
  5. If you work for a living, Linux is not for you. I am not a fan of Microsoft, Apple has lost it, somedays Apple is just as bad as MS in reliability, and MS tries to be a Google (of which they aren't). I'm enslaved to Microsoft because I have a living. And many of the Linux apps do not play well in the Microsoft world. Open Office/Libre Office is a joke if you have to send a multi hundred page RFP to an enterprise that reads things off MS Office for an example. I know most BinRev users are not in professional work environment, but you're talking to one, so I have to defend Microsoft over my dead body. When Linux can start using vanity names instead of the raw app/process name to describe them and actually lay off case sensitive file systems (so people can start writing proper English again because they forget when they reply/respond to something as if they're still coding/compiling/etc.) - then I would take Linux more seriously.
  6. ^ I can see the slight frustration. I've tried to install it on a virtual instance, and I'm able to get the thing up, but when I access the Web URL, it goes a default Apache page. I installed it on a SFF OptiPlex GX240 (for the sake of it despite the small PCI slots) and tried to plug in a serial cable to the serial port, to see if I had to serial in that way, like the traditional Definity Audix card. Pointers with some maturity and screengrabs, and other visual documentation would be great for all. Update on any R10 or greater PPN/processor board. I've done research on this and basically you're SOL if you do not have an active relationship (support contract or otherwise) with Avaya. Beginning in 2001, starting with the Definity R10 required a very difficult activation process, and I have personally tried before with Avaya a couple years ago. The process basically starts at the purchase order. The Business Partner (their version of VAR) or Avaya themselves would enter the order of the new PBX on their system, with "SAP Codes" (formerly known as the Comcodes from the Bell System days; SAP meaning their ERP of choice for enterprise accounting) and match the customer information on another database. Another common numerical ID is the "Sold To" number, that identifies the customer, and it's physical address and location. At that point the information had to be plugged in by sales and or other reps before the install. If you ran into the PLDS system that Avaya uses on their extranet, this is how that certificate comes into play. The certificate would come from Avaya's servers and be fed directly to the INADS port via a dial in modem coming out of Denver (or probably India more now than back in the day.) If the CLAN was programmed and had a direct link to the WAN, the certificate could be fed through over IP. This system appears to be an in house app (this PLDS system) and in fact it bears a patent, and such reversed engineering from smaller BPs and non BPs have been in the center of DMCA clams (please gag me with such trolls!) Avaya has no intention to give these licenses without any contracts to users that have no intention to make millions of dollars and keeping these from being thrown into a dumpster! and when I inquired Avaya 2 years ago, they basically showed me the door with a trail of emails to lawyers. Oh yeah legal counsel had to look into this. (such a #laywermagnet!) Given Avaya's current state of financial instability, and whatever happens in the coming years, I would be safe to say that if you do not have any certificates on any "Definity" past Release 10 would be a nice paperweight forever. I felt it was important to share to anyone who has ran into something similar to my experiences with a post R10 board. tried? user: cust password: custpw I thought it used similar handles/passwords similar to the PBX side.
  7. I am unable to ground the PBX because of it's location and the lack of any ground where it's recommended tie to. For the AC power (I think you mean) I have an UPS (obviously for the DA module since UNIX is like dealing with a male asshole (i.e. unforgiving nature of an improper shutdown)) and I think I should be all set. Thanks for the feedback.
  8. Question: how is your G3 box setup at home for grounding and lightning protection? My G3 CMC is tied to a Comcast analog trunk and there is no protection on the CO card. However I used to have a couple IP Office units that took direct hits and almost burned down the house. I have had Cisco gateways that I put CO trunks in and it survived, and the CMC carrier looks pretty grounded unlike the IPO units. Has anyone had problems with their systems at home with limited to zero protection? Avaya unlike other vendors tend to get really anal about protection. Unlike the others here, I protect this as if it was my child. Thanks.
  9. Oh so you're experienced on the Key systems. They are pretty less open than a proprietary PBX. I am no nerd and these hex codes and cracking and stuff is way over my head. (hence please create a sticky with a walkthrough! A lot of us in tech do love visual documentations!) Also my G3 R9 is back on a production system - another VOIP fail in the house - don't have time anymore to deal with these finkeny systems. In re to the ASA - PM'd you. Check your inbox. This licensing thing someone with a bigger brain than I have should really look into it beyond the Definity but in the Aura world too. A source had contacted me recently of having a G250 at home and had the ability to get find a S8500 server to run Aura and was talking to their Business Partner (Avaya's =/ VARs) of trying to get some license and the BP had basically went silent and gave a half answer if it could be possible. It's apparently cheaper to not acquire a new license and just copy the crypto from one PPN or server to another when it's done by Avaya or a BP; and that's why mine had the 30 day countdown. I'd rather not go into details of why I am not a genius in hex and TLAs, and other nerdy things because to be honest it goes over my head when it's spitted out randomly, especially when some will use vague language. (Basically I should just disclose, my IQ level on technology is at the "management" level. It's the differences that makes the world go 'round right?) I also feel a little pushed to be honest by some of the replies. I'm known to be a clutz and been taught to not be risky with "expensive" gear.
  10. I have a technical question about the Definity type of PBX systems (not the softswitch Auras) Can a PPN run a release that is lower to the what's on the card? I have that finicky R12 PPN board, and I was wondering if I could take my R9 translations and "restore" them onto that board? And run R9 as a backup in case my other board decides to give up. (You never know.) I'm surprised what's missing in this thread is about the "Sold to" number. This Avaya's answer to a serial number specific to a customer and site location. I should check with the individual, but both cards were from the same site, most likely with the same "Sold To number". I believe these numbers have to match in order to do something like this. If the sold to number is important, is it easy to insert it at some point of a hard reset and all that complex hex cracking and stuff like that, or is this actually pretty trivial?
  11. When I received my CMC box, it came with the disc from the individual who had given it to me.
  12. I'm lucky to have ASA, but like Putty works too if you don't have access to a copy. I have not had issues with function keys when I had to Putty it for another situation. In any situation, I try to use AT&T's 513 or 4410 to get in because the switch revolved around AT&T's own dummy terminals. Safe to be native if you can! It looks you've gotten the hang of it!
  13. It dumps the entire RAM contents - so theres going to a lot of lines. For me I tried to get the contents using HyperTerminal (was using an XP laptop) and checked the screen logging before logging in and performed the specific commands ThoughtPhreaker instructed. Procomm and Avaya are typically not the best marriage in heaven to manage.
  14. I recommend a sticky or a blog post or something where it's concise because I think many who have came here from a Google search are not Tier 3 admins. I would ask CJ from PBX How Tos (since he was a Tier 3 Avaya guy) since he flaunted that he "defaulted his PBX" in a YouTube video a few years back; but I think he's ether dead or playing possum.
  15. So I am going to try tonight to read some of @ThoughtPhreaker's advice both here on thread and in a private message to finish trying to default my R12 board. I have not had the time to sit down in my wiring closet and follow the instructions. I did get the PAM dump from using HyperTerminal (using a Windows XP VM) and download it (sorry to the folks here, I do not use Linux and while I hate Microsoft, I'm one of those "real world" dudes who doesn't have time to play with non enterprise software/amateur apps.) Actually the problem was finding how to get the entire dump to export. That took some time and I got it done in the spring, again the only available app that was able to do so was HyperTerminal. I feel safe to say I got the entire strings of hexes. I gotta finish through the various stuff ThoughtPhreaker helped me with. I'll let everyone know if I got somewhere. Has anyone tried to default an R12 PPN to the point where it can run 30 days without a license? (as if Avaya was installing it?) I clearly know this is the biggest hurdle for anything greater than R10. Also could I provision the system after a massive default, save to translations (again w/out a license) and like on the 30th day, default, reload the translations and make it appear it was running like on Day 1? This is my ideal goal, and will try to see what I can do tonight. For fun: can someone tell me what the PAM stands for and what's it's purpose other than trying to max out the fan speeds? (Hope no IP atty comes after this post!) Is that for sure? VxWorks is something I am not familiar Avaya Red using at all. Avaya Blue (NES) had VxWorks behind M1 and all the Meridian class PBX systems. I thought on the Red side when they moved to Mod Messaging and the S-line of media servers they ported Oryx/Pecos and AUDIX to Linux code... Don't feed to the SV legal trolls! Eff them! Avaya is dead. (Sorry folks to rain on your parade) but since their Ch 11, more and more customers have dumped Avaya like crazy and who cares if their code is on the net? Quite honestly, Avaya has been really rude to any non commercial customers outside the small end systems (that doesn't need craftsman intervention) as I previously stated. In other tech, there are hobbyist licenses, so why couldn't Avaya during these rough times where they are making it harder for ANYONE to pay for their wares? It's a "public service" to preserve the history of a generation of enterprise telephony! We must teach "the children" and the IT hotshots what an "office phone system" really was! This might be OT, but I wonder if anyone is willing to reverse engineer the Avaya Red components to make an Asterisk distro similar to Avaya Blue's fork of the Asterisk known as the UCx system. (AFIK former Nortel engineers are behind the UCx platform.) I still have my DCP terminals, and a pre SIP era 4606 set just in case someone is willing to do the same to the Avaya Red world. Avaya Red had more customers, more users than Nortel had, and there is still squat of a community that would be willing to build something. It's like Nortel has been dead for years, and there is still tribute tours kinda thing in that part of the telephony world. :/