MakeAvayaRedGreatAgain

Members
  • Content count

    33
  • Joined

  • Last visited

Community Reputation

0 Neutral

About MakeAvayaRedGreatAgain

  • Rank
    H4x0r

Profile Information

  • Gender
  • Country
    United States
  • Location
    NH.US
  1. What does that mean? How does that get achieved? I mean, such vague language can't run away under my eyes.
  2. 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.
  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.
  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. tried? user: cust password: custpw I thought it used similar handles/passwords similar to the PBX side.
  7. 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.
  8. ^ 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.
  9. post removed by the poster.
  10. 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.
  11. 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.
  12. Oh already I have that, and had to go to my State Library to find it locally. I had been trying to digitize it over the last couple of years and life got in the way. I had Avaya sources contact on my site that the DCP was an ISDN varient before the ISDN was finalized (a comment still is there). But some boards are harder to find. I take that to be an insult. I'm not an engineer but a professional, so I don't go and insult systems other than calling Nortel Nerdtel. That's the only line I cross.. Easy to say when this information wasn't around a few years ago. And the individual who gave me his CMC is a sever administrator with already a high stress job. And the system couldn't be put into a decent location. I believe he lives in some townhouse. He doesn't apparently have the time like you folks just creeping around the internals. It's within the realm of the topic. You do know that the UCX supports Meridian 1 (the PBX line) sets, right? So your argument is actually counterproductive. Yes the Avaya PBX boxes was most often found in midline setups, but again, I think you missed my point of what the UCx can do, the ability to add IP sets without worrying about licenses, and I just see the resistance because I am not a technical person and no one else is interested...whatever. I see you folks more interested in resuscitating old TDM boxes and questionable PPNs that are sadly becoming more and more rare. Fair point and understand your counter.
  13. 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.
  14. 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.
  15. 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?