MakeAvayaRedGreatAgain

Members
  • 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

  • Gender
  • Country
    United States
  • Location
    NH.US
  1. I didn't come here to be verbally abused by some knowitall to someone whose not as smart as you. Please treat others with respect and not bash people like on your last 'graph. Have a good life.
  2. 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.
  3. 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... )
  4. What does that mean? How does that get achieved? I mean, such vague language can't run away under my eyes.
  5. 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.
  6. 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.
  7. 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.
  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. 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.
  10. 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.
  11. 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.
  12. 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.
  13. 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?
  14. You just blew your cover!
  15. When I received my CMC box, it came with the disc from the individual who had given it to me.