CatalystTech

All servers will crash at some point. Failures can result from hardware failing over time or from software malfunctions. Most commonly experienced are failures from human interaction. Upgrades, patches, or common procedures that were not successful are the cause of a majority of failures. These situations can also occur when a proper back up is made of a corrupt or improper file. Automatic and incremental backups are important for protecting against these type errors. Without incremental versions there is only one backup copy. It could be corrupt as well. Without automatic backups the chance of skipping a revision is high.
(continue reading…)

Avaya has posted a series of how to videos on Brainshark.  These videos can be accessed an played back from any standard browser.  Hit the link for the list of videos.

(continue reading…)

The command netstat is a handy tool for displaying the active ports and addresses on a Windows or *nix machine. For the Windows environment often the output scrolls past the buffer for the command prompt window, thus loosing important information about lower port numbers.

(continue reading…)

IP Office Tech Tip 212 seems to be causing a little confusion, due wording used at the time of release.  The Tech Tip was released to address feature that resolves an issue on PRI circuits where the field that defines the number format may need to be changed. The ISDN protocol allows the switches involved in call setup to define the number formats for both Calling Party and Called Party numbers.  Most carriers want to see these fields formatted as National numbering plan.  International calls, Toll Free calls, and even some Local calls may need to be set for Unknown numbering plan on various carriers.

This Tech Tip was released to announce a new option to change the Called Party Numbering Plan.  The announcement was made prior to the 4.2(11) GA code release and did not take into account future release schedules.  This feature has now been permanently implemented, and there is no longer any need for a Private Build.  Simply add the source number of “NI2_CALLED_PARTY_TYPE=UNKNOWN” to the NoUser profile on any IP Office running firmware 4.2(11)+ experiencing calls failing for an invalid numbering plan. (continue reading…)

IP Office can some times hick-up while loading new firmware. This can be a PC problem, a network problem, or a sun spot firing an intergalactic event. Despite the cause, the resulting RED status light can be quite disturbing, but don’t loose hope.  By performing the below procedure a control unit can be brought back to life.  This will not clear a blinking RED status light, or a looping reboot as these two conditions are configuration related.

(continue reading…)

UPS sizing can be confusing to say the least.  Starting with Volts, Amps, Watts then converting to kVA and adjusting for longer hold over times, it may take a Math major to get correct.  Volts are easy, most systems in the SMB space are 120V and some Enterprises mix in some 220V for efficiency.  Amps are a bit more confusing.  Read more for links to configuration tools..

(continue reading…)

Synchronize Calls was introduced in 4.0+ with the addition of the Announcements Tab for Hunt Group.  The theory behind this option is to conserve voicemail resources used for announcements while a caller is queued in a hunt group.  Enabling this feature allows all callers in the queue to hear the same message, at the same time, thus only using one voicemail resource.   Read more for limitations and documentation..

(continue reading…)

Avaya has released new RSS feeds to help Business Partners better keep up with new information on the IP Office knowledge base and the Application notes.  The feeds are a part of a series of enhancements to the IP Office knowledge base site that provides documentation to IP Office users.

(continue reading…)

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.
(continue reading…)

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.

(continue reading…)