• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About MakeAvayaRedGreatAgain

  • Rank
    SCRiPT KiDDie

Profile Information

  • Gender
  • Country
    United States
  • Location
  1. 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.
  2. 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.
  3. 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.
  4. 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?
  5. You just blew your cover!
  6. When I received my CMC box, it came with the disc from the individual who had given it to me.
  7. 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!
  8. 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.
  9. 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.
  10. I'd appreciate that, hit me up via PM. Going into the Definity was a little intimidating, but that was just at the surface level. I get that point about the phones being dumb (that's why it was called "Voice Terminals" in the first place!). Yeah the parts are cheap, easy to repair (allegedly), there are other reasons why using virtualization and modern gateways could be argued. I got my CMC box only because that individual was moving there wasn't a location where the thing could be in a proper location without a fan being blared at all times. That individual had gotten a Mitel 3300 box (from another cutover) and actually unplugged the fan modules and given the light traffic of it, it isn't a problem. But what for other folks? I don't think you can unlock CM 4x+ for say a virtual appliance and tie it to a G250/G350, etc... see use case? I guess that case could can quickly go nowhere. And this is where I kinda not agree. I think given the very nerdy nature of "Avaya", that was how the UCx was born. If they turn things down on such ideas because one doesn't know how to code... I think they should be taught sensitivity as a mandate and learn that the rest of the world don't think like them and have to respect it. I find people with engineering/coding backgrounds to have a very low respect for the moderate technical people (to your point above.) There needs to be a balance between the nerds and the geeks, and the nether folks too. The rest could be going off topic, so if anyone inferred that I would be the lead developer/leader of said project, it would be way up my IQ and pay scale! (Apologies for misspelling "assemble" earlier)
  11. When someone tells you "Avaya" - they think the old Nortel. And I am freckin jealous they have all the fun. Any familiar with the UCx phone system? Some Nortel alums left and took some Asterisk distro (not sure what one) since FreePBX supported the UniSTIM protocol and guess what? You can put more than just Nortel VOIP terminals. All their digital terminals since 1988 and present (including the Norstar) can connect just fine. All you need is a gateway that has an Ethernet board and the gateway will link up with the UCx. Again why does Nortel have all the fun? I don't want to see CLAN boards just disappear, as well as the legacy DCP and IP sets. This has been an assault to the original Avaya community. Has anyone taken the challenge of reverse-engineering the Avaya stuff to make their own UCx killer? Protocols are totally different, and all I know is their H323 IP port is 1709. And I hate coding, so I can't assumable such thing. Despite the FUD, Nortel systems will for many years to come be "alive and well". Avaya? Not so much. Since Cisco has outpaced Avaya in 95% of the Fortune 500 and given how Avaya will emerge from bankruptcy other than their call center software that they will market, I think Avaya is really dead. So has anyone gotten deeper (other than the classic Definity thread) with the internals of any of their "Avaya Red"/Lucent/AT&T systems?
  12. I think to quote myself again... Meaning it's a POTS phone that connects to an IP network. Oh so I can check my weather, Oh I can put my "stupid dog" as a backdrop. I guess call appearances, features can't be programmed to a button with lamps is not their priority years later? Why should my DND be an icon or words on the screen, why can't I have it as a button with a lamp? It's the nerds way of pushing "their way is the only way and if you don't like it - you're old"... This was kinda off topic to be honest. Too technical on a simple narrative. And also real guys do NOT use Cisco for VOIP routing. I mean really...
  13. I'm going to leave profanity out of my reply, but I guess there is a disconnect between the enterprise and carrier. I'd strongly would be carefully mixing VOIP and TDM thoughts together. You can use VOIP-enabled systems (in the enterprise) without using VOIP. Or VOIP enable systems through a private network. A lot of the rack and stack carriers say the Avaya and Nortel connect in the similar fashion to their legacy counter parts, and for Avaya Red, I believe the G700s could be tied on the back with straight cables. The IP Office too in older models, with separate units being tied WITHOUT IP. I guess it makes sense it's packet based, but it's not the packets that I dunno say the ISP side of carriers. In regards to a softswitch, I'm not going to it's bull from marketing. Theoretically the software that makes and receive calls are software based. Most of the CPU of the ESS is software anyways as well. It's just down to an app. If we are going to derail the subject with Cisco, well Cisco is hypocritical - they have their own standards. I'm in the process of decommissioning a Cisco network and put ABC - that is Anythng But Cisco solutions. Let me tell you I regained 20 years of my IT/IS lifespan back. I would refrain from comparing Cisco to Ma Bell. I am not sure if you know the history that well (my museum site is currently down for a long time) but I am working on writing up that history for another outlet.) The 7900s are built well, but they do hog a lot of power and it's almost a 2/564 just with an IP stack. It can't compare to an Avaya, heck even a Nortel set in terms of features, lamp indicators - or even line appearances more than the buttons on the set themselves. Cisco is basic telephony with an IP stack over it.
  14. I don't get if this topic got derailed or someone doesn't understand the telco language or the language is being used very loosely. I thought hybrid setups on the carrier side were called "softswitches" and newer hardware were on "gateways". I don't get how it can be "packet [switching if that's the case - vague language]" unless its all tied on it's own network connecting the gateways to the IP or server side.
  15. Awesome, Reading posts here about the ESS and the long rumors of the death of landlines are apparently exaggerated. I guess it's playing possum! I'm quite surprised that the IT-types didn't force the Lucent engineers to cave into rack mount carriers like the other guys and (obviously) in the PBX world.