Avaya IP DECT Tips
August 28th, 2008Installing an Avaya IP DECT system can be tricky at times. This article will explain a few common problems when installing an IP DECT system and some tips about DECT Monitor.
Read the rest of this entry »
Installing an Avaya IP DECT system can be tricky at times. This article will explain a few common problems when installing an IP DECT system and some tips about DECT Monitor.
Read the rest of this entry »
The embedded voicemail on IP Office offers multiple auto attendants (4 in 4.0- or 40 in 4.1+) each with multiple greetings. These recordings seem to cause some confusion. Essentially, for each auto attendant there are 3 time based recordings and 1 generic recording. In theory the time based recordings would give a caller a relevant greeting based on the time of day. Then immediately after the time based recording plays, the generic ‘Menu Options’ recording would play listing the available options. That is in theory, in practice these are typically used a bit different.
This is the upgrade path for 4.2 per Compas ID 136708 (TB 97).
This is per Compas ID 136708 (TB 97).
The following are a list of applications and supported operating systems.
Scenario: DHCP is needed to assign IP phones IP address. The ports the phones will be plugged into will connect the IP phone and the PC, which will be plugged in to the back of the IP phone.
DEFCON 16 and Black Hat are security centric conferences recently held in Las Vegas where Aruba Networks provided the wireless infrastructure. In a self descriptive FAQ of the environment to be expected (quoting from the FAQ site)
Q: Is there a free network at DEFCON?
A: Yes. It would be fair to describe the network as ‘hostile’. It has been described as ‘the worlds most hostile network’, but such descriptions are just attempts at flattery. It is recommended that if you want to connect to the DEFCON network pretend that you are sharing out your entire hard drive to 5,000 hackers. You may want to bring a ‘clean’ computer that you don’t mind being infected/hacked/etc…
In light of the environment Aruba reported some statistics:
Well I had to come off the excitement of serving on jury duty to write about what is likely some of the best news to hit Avaya IP Office users this year. Firmware version 4.2(4) was just released on Monday, Aug 11th. Now, in the past the knee jerk reaction was if the release was less than (10) it was not worth messing with. I have to say that with the new Avaya System Verification and all the testing that went into this new code train, the 4.2 release looks very stable. Combine that with the above par feature set, and IP Office is the best option for any small or medium business. Read more to look at some of the new features and links to downloads…
This morning Aruba issued a press release announcing that it is the first wireless LAN supplier to be awarded a Common Criteria certificate for its Wi-Fi solutions. Common Criteria - also known as ISO standard 15408 - addresses the protection of assets from unauthorized disclosure, modification, or loss of use arising from both intentional and unintentional causes. High security users typically require a combination of Common Criteria certification, Federal Information Processing Standard (FIPS) 140-2 validation for cryptographic security, and compliance with Department of Defense (DoD) Directive 8100.2 security policies for wireless technologies. Aruba now satisfies all three criteria, allowing the company to meet a wide range of new domestic and international government, financial, and commercial applications.
With the new proliferation of Vista on desktops in the marketplace, some traditional practices like fixing firewall permissions can get hung up. The easiest way to ensure that firewall permissions are correct is the AvayaFW.bat script. The script checks the registry to see what programs are installed then writes the ports associated into the exceptions in the firewall. On Windows XP, this batch file runs with a double click. On Vista and Server 2008 the batch file requires elevation to run properly. Right click on the AvayaFW.bat icon and choose ‘Run as Administrator…’. This action will require administrator level access or password.
Occasionally when changing names, or swapping users in IP Office, the Voicemail Pro server will get confused and corrupt it’s table correlating Extensions with Names. This results in messages delivered to the wrong mailbox, message waiting lights incorrectly turned on, and a few other issues. To clear the issue, simple clear the user from both systems and restart. See below for a step by step…