BEST FREE PDF TOOLS

Source: techsupportalert.com/

BEST FREE PDF TOOLS

By: Jojo Yee

Introduction

A PDF tool comes in handy when you need to deal with PDF files such as to merge or split pages, add a header, footer or watermark, highlight or annotate PDF documents, or convert from other files to PDFs or vice versa. In this review, multipurpose programs offering general features for merging PDF files, splitting or re-ordering pages, etc within a single application are discussed under General Tools. Those designed for a more specific task are grouped under Specific Tools.

General Tools - Merge, Split, Reorder & More

PDFill PDF Tools is my favorite with its nice, clean user interface covering most  functions, including merge pdf files, split or reorder pages, rotate or crop pdf pages, add headers and footers complete with page numbers, etc.

Watermarks can be added either by typing in some text (such as ‘DRAFT’ for documents to be reviewed), or by inserting a background image in PDF format.

Some additional features are supported, such as encrypt and decrypt with security options; reformat multiple pages into one page; delete, flatten or list PDF form fields; convert PDF to images or vice versa; and convert a PostScript file to PDF.

Note that PDFill PDF Tools comes bundled with PDFill PDF Editor, which is not free. However, you can run PDFill PDF Tools separately after installation. The free software part of the package does not support functions such as converting PDF to text, making annotations, etc. But those features are all available in the Specific Tools listed in the next section.

PDFTK Builder is a useful alternative. The big advantage of PDFTK Builder is that it can merge or reorder selected pages of PDF files at one go, which is much simpler if you have a lot to do.

PDFTK Builder also supports split, rotate, background/stamp and encrypt features. Besides these, it has no other additional features.

It's worth noting that PDFTK Builder lacks a basic function (available in PDFill PDF Tools) for watermarking PDF documents with background text—this can be important if you need to mark your documents as 'Confidential', 'Draft', etc.

If your priority is to get the maximum number of features from a single freeware package, then jPDF Tweak will be a good choice. However, its user interface is not as straightforward as in either of the two applications reviewed above. Its merge, split and reorder functions are available under the ‘input’ tab, and a new filename has to be entered in the ‘output’ tab.

This feature rich program allows you to rotate, watermark and format multiple pages. You can change page numbers and chapter bookmarks. And jPDF Tweak also offers encryption functions and lets you add attachments to PDF documents.

Additionally, jPDF Tweak enables you to set viewer preferences and document properties, including title, author, subject and keywords.

PDFsam (PDF Split and Merge) is well worth trying if you need to visually re-order or recompose multiple pages of PDF files.

You can mix, merge or extract, split and rotate pages by specifying the page numbers. However, PDFsam also lets you re-organize PDF pages in a thumbnail view. In this mode, you can easily work with thumbnails to merge, delete, rotate or re-order PDF pages and save the results as another PDF file.

Since PDFsam is a Java application, it will run on any operating system that supports Java. The basic version of PDFsam is free for use. The installer is bundled with an advertising program OpenCandy but you can get from here a standalone zip file with no such bundle.

For Linux users, PDF Shuffler should make it much easier for you to re-arrange pages in a pdf document, or merge and split pdf files.

After importing one or more pdf files to PDF Shuffler, the various pages appear as thumbnails, making it easy to merge, re-order or delete. You can right-click a thumbnail to rotate or crop a page before exporting to a new pdf file.

PDFShuffler is a small application running on Linux. Some distros, such as Ubuntu, include PDF Shuffler in the repository for ease of download and setup.

Specific Tools

The free applications reviewed in this section are helpful for their specific functions mostly not covered by theGeneral Tools.

Edit a PDF File

Oracle PDF Import Extension (formerly Sun PDF Import Extension) allows you create a hybrid pdf file with LibreOffice or OpenOffice Writer. A hybrid pdf file is basically a pdf file containing an embedded odf source file. The beauty of this type of file is that not only can it be viewed with a normal PDF viewer, it can also be opened for full text editing with LibreOffice or OpenOffice Writer in 100% layout accuracy. See this article A PDF File Allows Editing in 100% Layout Accuracy for details.

If you need to edit a normal or non-hybrid pdf file, LibreOffice or OpenOffice Draw is one of the free options available. You can use it to edit small portions of text, add or remove images and so on with no layout adjustments.

Convert PDF to Text

Balanced Transmitter and Receiver II - Sound.Westhost.com

Source: sound.westhost.com (Elliot Sound Products)

Elliott Sound Products

Project 87

Balanced Transmitter and Receiver II
Rod Elliott (ESP) / Uwe Beis *
Updated 01 April 2002

---

  Please Note:  PCBs are available for this project (P87A & P87B). Click the image for details.

---

Introduction

This is essentially an update to the original article on the subject, and includes some ideas to stimulate further thought on the subject. This is especially true of the last section (Hey! That's Cheating) - everyone wants balanced outputs free, well you can have them free (well, near enough anyway).

The balanced transmitter and receiver described in Project 51 work very well, but both are less than optimum under difficult conditions. Uwe has written an article (published on The Audio Pages) describing an active balanced transmitter that has performance almost equivalent to a transformer. There are ICs available that (almost) manage the same thing, and the principle uses feedback to equalise the levels from each transmitter opamp.

While Uwe has gone to a great deal of trouble to get his circuit to match a transformer as well as possible, this is not an easy circuit to get working well, and it requires 0.1% tolerance resistors and wide bandwidth opamps.

Enter ESP and the 'simplification methodology' that I tend to use wherever I can. The result is a transmitter (in particular) that is extremely good, and matches the performance of a transformer to a quite acceptable degree. It's not perfect, but it's stable, and requires no adjustments or close tolerance parts (1% resistors will provide a maximum error of 1/100, or 40dB common mode rejection and balance).

Use of closer tolerance resistors - and good or premium opamps - will give a circuit with excellent performance, and it will come very close to that of a transformer balanced circuit with none of the associated cost. Response is flat to at least 50kHz, with a low frequency limit of DC (as shown). Capacitors can be used to limit the low frequency limit if desired.

---

P87A - Mk II Receiver

The receiver is shown in Figure 1, and as shown does not have any RF protection. This configuration is somewhat better behaved than that shown in the original article, and presents exactly the same impedance to each of the balanced lines in the cable. This is also the case with the original version shown, but only if the source is also balanced.

Figure 1 - Active Balanced Receiver

The resistor marked * (R7) may be left out, and the circuit will have a gain of 2. Installing this resistor will increase gain, but will have no effect on the input impedances or balance performance. The minimum gain for this circuit is 1.5 (if R6 and R7 are omitted), and this increases to 2 with R6 installed. The gain setting resistor R7 still works if R6 is omitted, with a value of 10k providing a gain of 3.5, and 1k giving a gain of 21 (26dB).

---

The standard pinouts for a dual opamp are shown (top view of device). It is suggested that a bypass capacitor (typically a 100nF ceramic or polyester) be connected between pins 4 and 8, as close to each opamp package as possible. Even with 'slow' opamps, it is always a good idea to use a bypass cap to prevent possible instability at high frequencies.

---

The exact same scheme as shown in the original project could be used for the inputs on this version. One possible connection is shown in Figure 2. This is virtually identical to the configuration shown in Project 51, and will provide a very high noise rejection.

Figure 2 - Optional Input Filter Circuit for Receiver

The 10k resistors (R1 and R2) to ground are still needed, and this arrangement will reduce the gain by a little over 7db. Use lower value resistors for less attenuation, but remember that as the attenuation is reduced, so is noise immunity. 1k resistors would be the lowest value I'd recommend, and will cause minimum attenuation (about 1.6dB). C1 may be increased if desired, but if too high may cause rolloff of the signal source.

Note that this network is not included on the PCB, because if used, it should be mounted directly to the XLR connector. Ideally, the XLR and filter network will be in a shielded enclosure if a very noisy environment is expected.

---

Mk II Transmitter

This transmitter is quite a bit more complex than the Project 51 version, but this is the price one pays for higher performance. The input is unbalanced, and has an input impedance of 11k. This must be driven from a low impedance source (such as an opamp's output) or performance will be degraded.

With the values shown, the circuit has a gain of 6dB when measured from the input, and between +Out and -Out. R13 and R14 are not absolutely essential in this version, but are recommended. They enforce a balance on the circuit, and prevent the possibility of "latch-up" where the outputs get stuck to a supply rail. This is extremely unlikely with the values shown, but the precaution is worth the very minor effort.

Figure 3 - Active Balanced Transmitter

If either output is shorted to ground by connection to an unbalanced input, the output voltage is only 0.4dB less than when operating in fully balanced mode. When one output is shorted, the feedback path to the other opamp is removed, so it provides (almost) the full swing that would normally be available between both opamps. This is the way a transformer (without centre tap) works, so the behaviour of this design is much closer to that of a transformer than the "standard" balanced output circuit.

1 Apr 2002 - I tested the circuit shown using 1458 dual opamps and 5% resistors. If the circuit is reliable and shows no bad habits with very basic opamps (basically dual 741s) and ordinary carbon resistors then I know that it will work when you use better components (however, see note below). Indeed, my test version is both stable and surprisingly accurate, despite the lowly parts used to test the circuit's operation. Because the crossed feedback paths are reduced from the optimum (by virtue of making R5 and R9 1.2 times the "correct" value), the overall stability and frequency response is much less dependent on the component values and opamp quality. I was able to verify that even using 741 type opamps, frequency response is less than 1dB down at 75kHz.

Somewhat surprisingly, output impedance is 100 ohms, and not the 200 ohms one would expect - there are 100 ohm resistors in series with each output after all. The crossed feedback paths make the difference here, and both simulation and measurement confirm that this is the case.

Although the above circuit does work exactly as described, in general it cannot be recommended for normal use. With high speed opamps, the circuit can (and likely will) oscillate, especially if there is a capacitive load (such as a cable) connected to the outputs. While it has been used commercially, the results have often been less than successful, and few commercial products use the scheme. While it is a very interesting arrangement, it actually fails to emulate a transformer anywhere near as well as might be imagined. The PCB version of the balanced transmitter does not use this scheme, for the simple reason that stability cannot be assured. In addition, the impedance balance is sensitive to component tolerance, and impedance balance is far more important than signal balance. P87B - PCB Version The circuit diagram for the PCB version is shown below. There is no attempt to simulate a transformer, because the circuit shown in Figure 3 is simply not stable enough with typical cables (which represent a capacitive load) and is too complex for general purpose use. Figure 3A - PCB Version of Active Balanced Transmitter As you can see, this is much more straightforward than the 'real' version shown in Figure 3. Only one channel is shown, and the other uses the second half of each dual opamp. While this may be seen as a fairly serious compromise, it's in line with almost all commercial products that offer a balanced line output. It also has the advantage that it is ideal to use as a power amplifier bridging adapter. Construction Hints Both the transmitter and receiver circuits require at least 1% tolerance resistors, or common mode rejection will be unacceptable. Even with 1% tolerance, the worst case rejection is only 40dB, and if you can use your multimeter to match the resistors to closer tolerance this will improve the performance. Although the transmitter and receiver are shown with (mainly) 33k and 10k resistors respectively, these may be changed if desired. Any value between 10k and 100k could be used, but remember that higher value resistors create more thermal noise. R5 and R9 in the Figure 3 transmitter are approximately 1.2 times the other resistors - the next E12 value up. For example, if you elected to use 22k resistors throughout, then R5 and R9 would be 27k. Also remember that for the transmitter's input, the impedance is 1/3 of the resistor value used - 10k resistors would therefore give an input impedance of about 3k. The Figure 3A transmitter has an input impedance of 10k as shown (R102), but this can be increased as required. Both circuits require a balanced +/-12V or +/-15V supply (Project 05 or similar power supply), and it must be free of noise. Make sure that 100nF ceramic caps are placed between the supplies as close as possible to the supply pins of the opamps. This is especially important if you use high speed opamps. Naturally I recommend that you use the PCBs that I have available (Projects 87A and 87B - see the ESP price list). These are fully tested, have been built successfully by many constructors and are known to perform exactly as described. Hey! That's Cheating Finally, for those who want a balanced output that is really simple, try the circuit shown in Figure 4. Now look at it again - it's not balanced at all ... or is it? Figure 4 - Simplest Possible Balanced Output Now, before you get all horrified, let's have a proper look at what is happening. The main trick with a balanced circuit is that the receiver should "see" the same impedance on each input. It doesn't actually care that much if there is signal on either or both wires (indeed, that is merely an expectation on our part), but even if the wanted signal is only on one wire, any induced noise will still be common mode, and will still be in phase across both wires. The noise gets cancelled either way, and the signal gets amplified, which is just what we want. Yes, it's cheating - but it works. Apparently, this trick is used on some of the popular stage mixers, as well as some very well regarded phantom feed microphones (although as far as I know they don't use the Zobel network - this is optional BTW). There is less signal than one would expect (most balanced transmitter circuits have an effective gain of 6dB), but this is generally not an issue. In the case of a microphone, the signal is the same as it would normally be anyway, and with a line output, 6dB of additional gain is usually not a problem to achieve. The amplifier as shown in Figure 4 only needs 2 x 10k resistors in the feedback path to achieve this (10k from output to -ve input (i.e. -in, not -ve supply pin), and 10k from -ve input to ground). In most cases, this will work just as well as a true balanced output circuit, for the simple reason that it is a true balanced circuit. From the perspective of the balanced input circuit (the receiver), this arrangement provides exactly the same signal quality as if the circuit were fully (signal) balanced, but the signal is -6dB compared to a circuit with a balanced signal. This is rarely a limitation. Although 150 ohm resistors are shown for the balancing network, these can be changed if desired (I suggest a minimum of ~100 ohms though). Normally, I would expect that the values shown will be fine for almost all applications (effective output impedance is 300 ohms). Somewhat predictably, the signal is only on one lead, so the cables had better be wired correctly if it is feeding an unbalanced input (but this is something that should be regarded as essential for all stage and studio work anyway). The resistors must be of sufficiently high value to ensure that the opamp output impedance is swamped. This ensures that the impedances on each leg are as closely matched as possible. Caveats - the output impedance of the opamp should be flat to a suitable high frequency, and this will not often be the case. Although I have shown a TL072 (or half thereof), I suggest that a better opamp should be used. In general, the output opamp should be as good as you can afford. A cheap opamp will most likely give a cheap result. The optional Zobel network will help ensure that the line appears properly balanced at all frequencies including RF, but cannot guarantee perfect results with any opamp. The venerable NE5534 (or the dual NE5532) is a very good choice. These opamps are still popular for a very good reason - they have excellent performance. Resistor tolerances are just as important here as with any of the more complex versions - 1% is the minimum acceptable tolerance. With all balanced interfaces, the impedance balance is the thing that counts. There is not (and never was) any requirement for the signal to be balanced. It doesn't matter if the signal levels are the same or radically different (including having one line with no signal at all). In contrast, an impedance mismatch of only a few ohms is enough to reduce the common mode rejection quite dramatically. Inspiration This new project article was inspired by Uwe Beis, and his article on the (almost) perfect balanced transmitter is published on these pages. Although the material here is somewhat 'off topic' from his approach, the inspiration to experiment and try the various techniques came from his submission. I recommend that you read the full article, as it explains the operation of the balanced transmitter shown in Figure 3 very well, and will give you an idea of the dedication of some people (Uwe in this case) to the advancement of their understanding of analogue electronics.

Technical Note: Enable Telnet Support in the Axis Camera Servers

Source: Axis Communications

Technical Note: Enable Telnet Support in the Axis Camera Servers

---

The information in this article applies to:

• AXIS 2100/2120/2420 from F/W version 2.12

---

Summary

This article shows how to enable Telnet support in those Network Camera Servers this isn't enabled by default.

More information

For development it might be useful to connect to the Network Camera by Telnet. Depending on what product is used, this is either enabled by default and have authentication or can be enabled by editing the /etc/inittab. If the product require editing of the /etc/inittab, there will be no authentication for the Telnet connection and no password will be required for access.

You should enable this option for experimental use only. Never leave the Telnet access enabled when having the Network Camera installed on a public site. 

Example

Open an ftp session towards the Network Camera and type the command viewed in bold below:

C:\Axis >ftp <ip address of camera>Connected to <ip address of camera>
220 Axis 2100 Network Camera 2.12 Feb 05 2001 ready.
User (<ip address of camera>:(none)): root331 User name okay, need password.
Password: pass  (if not changed from default)
230 User logged in, proceed.
ftp> asciiftp> cd /etcftp> get inittab200 Command okay.
150 Opening data connection.
226 Transfer complete.
ftp: 1380 bytes received in 0,01Seconds 138,00Kbytes/sec.

At this stage, open the downloaded inittab file in an editor and find the following line:
#telnetd:3:respawn:/bin/telnetdRemove the preceding ”#”:
telnetd:3:respawn:/bin/telnetdSave the file

Go back to the ftp session and continue:
ftp> put inittab200 Command okay.
150 Opening data connection.
226 Transfer complete.
ftp: 1414 bytes sent in 0,00Seconds 1414000,00Kbytes/sec.
250 Command successful.
ftp> by221 Goodbye.
Restart the camera and it will be possible to access with Telnet.

---

Axis does not take any responsibility for how these configuration changes may affect your system. If the modification fails or if you get other unexpected results, you may have to restore the factory default settings as described in the User’s Manual. 

AVAYA IP OFFICE QUICK GUIDE

Source: http://www.datacomsolutions.ca/

AVAYA IP OFFICE QUICK GUIDE

Avaya IP Office 500 V2 Platform

IP500 and IP500 V2 Front View

IP500 Back View

IP500 V2 Back View

IP Office V2 Control Unit

The IP500 V2 control unit is compatible with all IP500 base extension and Voice Compression Modules (VCM) cards as well as all external IP500 expansion modules. IP500 V2 is a stackable unit with an optional 19" rack mounting kit and an optional wall mounting kit for smaller configurations. The control unit provides the following functionality:

4 slots to house a mixture of extension cards, VCM cards & the Unified Communications Module:

• Digital Station 8 card. Supporting IP Office digital telephones.

• TCM8 Station card supporting select Nortel digital telephones (IP500 V2 control unit only)

• Phone 2 and Phone 8 cards

• VCM32 and VCM64 cards

• 4-Port Expansion card

• ETR6 port phone card (IP500 V2 only, North America only)

• Combination Card with 10 VCM channels, 4 analog trunks, 6 Digital Station (DS) and 2 Phone ports (IP500 V2 only)

Optional trunk card support:

Analog trunk Module 4 card
BRI4 and BRI8 cards (2 x 2B+D and 4 x 2B+D channels respectively)
Single and Dual Universal PRI cards
IP500 Legacy Card Carrier: this card allows up to two IP400 Trunk or VCM Cards to be used with the IP500 control unit
IP500 V2: 2 Slots for SD cards (System and optional) – System SD card is required for system operation as well as licensing of optional features and storage for embedded voicemail in Essential Edition
9-pin RS232 DTE Port for maintenance

Support for up to 12 IP500 Expansion Modules:

• Digital Phone modules (16, 30)

• Digital Station modules (16, 30) supporting IP Office telephones with RJ45 connector

• Digital Station modules (16A, 30A) supporting Nortel telephones with RJ21 connector (IP500 V2 control unit only)

• Analog Trunk Module 16

• IP500 So8 module

• IP400 expansion modules (not WAN3 10/100 or Network Alchemy modules)

• External output socket supporting two relay on/off switch ports, e.g. for door entry systems

• Audio input port for external music on hold source

• 48 Data channels

• Up to 40 voicemail ports

• Two 10/100 switched Ethernet ports (Layer 3)

• Partner Version • IP Office Manager • Licenses • Telephone Support

• Telephony Features • SIP Trunk Enhancements • DECT R4 Changes • Customer Call Reporter

• one-X Portal for IP Office • Voicemail Pro • Operating System Support • Features No Longer Supported

IP500v2

The IP500v2 control unit is similar to the existing IP500 control unit with 4 slots for IP500 base cards. Key differences are:

SD Memory Card and Feature Key Dongle The Feature Key dongle used is an Avaya SD memory card with a unique serial number on which the IP500v2 systems licenses are based. This card must be present for the correct operation of the control unit.

The cards are supplied with a set of core software and phone binary files. When a system is started, it will compare its current software (plus that of phones and expansion modules) and if necessary will upgrade the IP Office system using the files on the card. In addition the card can contain a license file which will be merged with the systems current configuration during a restart.

The card provides embedded voicemail. It provides 2 channels by default but can be licensed for up to 6 channels total.

The IP Office System Status application is present on the card and can be run from the card.

An additional SD card slot on the control unit can be used for an additional memory card to or from which files can be copied to the system card.

Various commands within IP Office Manager, System Status and on system phones can be used to perform memory card management function such as backing up the System card to an Optional card.

Partner Version Mode In addition to A-Law and Mu-Law variants of the Feature Key, a Partner Version variant exists. IP500v2 systems using this card run in Partner Version mode, see below.

IP500v2 Combination Cards  These cards are a pre-built pairing of IP500 base card and daughter card. They provide 6 digital station ports, 2 analog phone ports, 10 VCM channels and either 4 analog trunk ports or 4 BRI channels. A maximum of 2 combination cards can be installed in an IP500v2 control unit. The cards will not operate if the trunk daughter card is removed or change for one of another type.

ETR6 Cards  This card supports 6 Partner ETR phones (ETR 6/18/34D, 3910 and 3920). The card can only be used in IP500v2 systems running in Partner Version mode. A maximum of 3 ETR6 cards can be installed.

Partner Version Mode

IP500v2 systems run in Partner Version mode by fitting them with a Partner Feature Key. In this mode the operation of the system and the telephones supported closely emulate Partner ACS systems.

IP Office Partner Version systems support the following equipment.

	Maximum	Variants Supported
IP500 Base Cards	4	• Digital Station 8 (Max 3) • Phone 2 • Phone 8 • ETR6 (Max 3) • Combination Card ATM4
IP500 Daughter Cards	4	• ATM4 Uni • PRI 1 Uni (Max 1)
Expansion Modules	1	• Digital Station 16 • Phone 16
Phones	40	• 1403, 1408 and 1416 Phones • ETR 6, ETR 6D. • ETR 18, ETR 18D. • ETR 34D (Max 4 total. Max 2 per base card) • Analog phones

•	The Feature Key dongle provides voicemail services for the system.

•	In addition to emulating Partner ACS operation, SIP trunks and mobile twinning can be licensed.

•	IP Office Partner Version systems cannot be included in IP Office Small Community Networks.

Manager

•

Auto Connect at Start Up By default, when started Manager will automatically performed IP Office system discover and display a list of IP Office systems found. If only when system is found it will start login to the system. Manager will also do this when an existing configuration open in Manager is closed. Auto connect can be switched off through the Manager's preferences.

•	Partner Version Administration Mode When a configuration from an IP500v2 running in Partner Version mode is loaded, Manager will switch to displaying Partner Administration menus.

•	Memory Card Commands  Manager can be used to perform a range of memory card commands. For IP500 and IP500v2 systems it can shutdown and restart memory card operation. For IP500v2 systems it can be used to copy, create and upgrade memory cards.

•	System Shutdown  Manager can be used to issue a shutdown command to an IP Office Release 6.0 IP Office system. The shutdown can be for a specified duration in minutes or permanent until the control unit power is switched off and on again.

Features No Longer Supported

In addition to the ending of Voicemail Lite support in IP Office Release 5, the following applications are no longer supported in IP Office Release 6.0.

•	Delta Server

•	Customer Contact Center (CCC)

•	Compact Business Center (CBC)

•	Conferencing Center

•	Feature Key Server

Licenses

For full details of licenses used by IP Office Release 6.0 refer to Licenses.

•

Feature Key Dongle Support The IP Office Feature Key Server application is not supported for systems running IP Office Release 6.0 and newer, meaning that the use of parallel port and USB port Feature Key dongles attached to a server PC is not supported. Therefore IP406 V2 and IP412 systems being upgraded to IP Office Release 6.0 or higher must also be upgraded to using a serial port feature key.

•	System Edition Licenses IP Office systems can be upgraded from the unlicensed Essential Edition mode to Preferred Edition mode and then to Advanced Edition mode using Preferred Edition and Advanced Edition licenses. Each license enables a range of additional features.

•	Preferred Edition Enables support for Voicemail Pro with 4 voicemail ports and licensable for additional ports. Preferred Edition voicemail features include announcements, customizable call flows, campaigns and generic TTS email reading for licensed users.

•	Advanced Edition Enables support for Customer Call Reporter and advance Voicemail Pro features (voicemail database interactions, voicemail speak text actions (8 ports generic TTS), visual basic scripting and ContactStore for IP Office).

•	Software Upgrade Licenses Existing IP Office systems being upgraded to IP Office Release 6.0 and higher require a Software Upgrade license. If the license is not present following an upgrade, phones will display an unlicensed message and can only be used for emergency calls.

User Profiles and Profile Licenses For IP Office Release 6.0, each user has a profile setting; Basic User, Office Worker, Teleworker, Mobile Worker or Power User. A user's profile controls whether they can be enabled for other functions. Profiles other than Basic User require appropriate licenses.

	Basic User	Office Worker	Teleworker	Mobile Worker	Power User
one-X Portal for IP Office	Yes[1]	Yes	Yes	–	Yes
Telecommuter options	Yes[1]	–	Yes	–	Yes
UMS Web Services	Yes[1]	Yes	Yes	–	Yes
Mobility Features	Yes[1]	–	–	Yes	Yes
TTS for Email Reading	–	–	–	Yes	Yes
IP Office SIP SoftPhone	–	–	Yes	–	Yes

1.	These features are supported for Basic User users on systems with the appropriate pre-IP Office Release 6.0 legacy licenses.

•	Teleworker Profile License These licenses set the number of users who can have their profile set as Teleworker. For user with this optional, additional settings are enabled in the IP Office configuration for the following services: one-X Portal for IP Office and UMS Web Services.

•	Mobile Worker Profile License  These licenses set the number of users who can have their profile set as Mobile Worker. For user with this optional, additional settings are enabled in the IP Office configuration for the following services: Mobility Features and TTS for Email Reading.

•

Office Worker Profile License These licenses set the number of users who can have their profile set as Office Worker. For user with this optional, additional settings are enabled in the IP Office configuration for the following services: one-X Portal for IP Office (no telecommuter features) and UMS Web Services. If no Office Worker Profile licenses are present, existing legacy Phone Manager Pro licenses can also be used to enable users for the Office Worker Profile.

•	Power User Profile License These licenses set the number of users who can have their profile set as Power User. For user with this optional, the same additional services as for Teleworker and Mobile Worker are enabled for the user in the IP Office configuration plus the following service: SoftPhone.

•	Pre-IP Office Release licenses for individual features now controlled by profile licenses can still be used by users set to the Basic User profile. Changes to the licensing for TTS and user profiles mean that on systems being upgraded to IP Office Release 6.0, users currently enabled for TTS email reading may find that function not longer enabled.

•

Avaya IP Phone Licenses On IP500 and IP500v2 systems, Avaya 1600, 4600, 5600, 9600, IP DECT, DECT R4, T3 IP, Spectralink and VPN phones are licensed by Avaya IP Endpoint licenses. These licenses are consumed by each phone as it registers with the IP Office system. Existing VCM channel resources and VCM Channel licenses enable a number of unlicensed phone registrations.

•	Existing VPN Remote licenses are no longer used. Phones using VPNremote client software require an Avaya IP Phones license.

•	Licenses are used on a first come first served basis as phones register with the IP Office system. Phones that register but cannot get a license will only be able to make emergency calls. Through the IP Office configuration, it is possible to pre-allocate available license capacity to selected extensions.

•	Text to Speech Licensing  The licenses for Voicemail Pro text to speech functions, TTS email reading and the call flow speak text actions, have now been separated.

•	TTS email reading is now licensed and enabled by a combination of the Preferred Edition system license and the Mobile Worker Profile or Power User Profile user licenses.

•	8 ports of generic TTS usage for use of the Voicemail Pro Speak Text action are enabled by the Advanced Edition system license. Additional ports can be enabled using the existing legacy TTS licenses.

Telephone Support

•

Avaya IP Endpoint Licenses On IP500 and IP500v2 systems, Avaya 9500,1600, 4600, 5600, 9600, IP DECT, DECT R4, T3 IP, Spectralink and VPN phones are licensed by Avaya IP Endpoint licenses. These licenses are consumed by each phone as it registers with the IP Office system. Existing VCM channel resources and VCM Channel licenses enable a number of unlicensed phone registrations.

•	Additional Phones  The following additional phones are supported by IP Office Release 6.0 and higher
•	1400 Series Phones  Using digital station ports, IP Office Release 6.0 supports the Avaya 1400 Series phones; 1403, 1408 and 1416. To the user they provide the same range of features are the equivalent 1600 Series phones on IP Office. Each 1416 can support up to 3 DBM32 buttons modules.

•	1600-I Series Phones The 1600-I variants of the 1603, 1603SW, 1608 and 1616 phones are supported.
•	9600 Series Phones  The following Avaya H323 IP phones are supported: 9620L, 9620C, 9630G, 9640, 9640G, 9650 and 9650C. All except the 9620s can support up to 3 SMB24 button modules. These phones are supported by IP Office Release 6.0 on IP500 and IP500v2 systems only. The voice activated dialing and USB features are not supported.

•	ETR Phones and 3900 Series Phones Using the ETR ports provided by the ETR6 base card, the IP500v2 control unit can support the ETR 6D, ETR 18D and ETR 34D phones plus the 3910 and 3920 wireless phones.

•	Avaya IP Office SIP SoftPhone IP Office Release 6.0 supports the IP Office SIP SoftPhone application. This application is licensed by a SoftPhone IP Endpoint license.

Telephony Features

•

Mobile Callback This feature is an enhancement to the existing mobile call control features. Mobile callback allows the user to call the IP Office and then hang up. The IP Office will then make a call to the user's CLI and when answered, provide the user with dial tone from the IP Office to make calls.

•	SMDR Buffer Persistence For IP Office Release 6.0, the operation of SMDR on IP500 and IP500v2 control units has been enhanced to store any buffered SMDR records during any controlled IP Office power downs or reboots. The current buffer is also stored at approximately midnight and midday.

•

Embedded Voicemail Dial by Number Enhancement The new auto attendant setting Direct Dial-by-Number can be used to select how keys set to the Dial By Number operate. If selected, the key press for the action is included in any following digits dialed by the caller for IP Office extension matching. For example, if 2 is set in the actions to Dial by Number, a caller can dial 201 for extension 201. If not selected, the key press for the action is not included in any following digits dialed by the caller for IP Office extension matching. For example, if 2 is set in the actions to Dial by Number, a caller must dial 2 and then 201 for extension 201.

•	Twinned Caller Number  Where supported by the ISDN provider, on ISDN trunks the IP Office can pass through the caller ID to the twinned call destination.

•	ISDN Redirected Caller Number For twinned calls routed out on ISDN trunks, the original number of the caller can be displayed on the twinned call destination. This function is only supported on IP500 and IP500v2 systems.

•	Telephone Features  For 1400, 1600 and 9600 Series phones, the following features have been added:
•	En-bloc Dialing Users can select en-bloc dialing mode through the phone's own menus. In en-bloc mode the user can compose and edit the number to dial while on-hook. This is similar to the method of dialing supported by mobile cell phones and wireless handsets. The number composed is dialed from the phone when the user goes off hook or presses an appearance button.

•	Call Park Button Enhancement  The operation of the Call Park button has been enhanced to display details of parked calls. This allows the user to select whether to unpark a call or to cancel the action.

•	Phone Inactivity Timers - Auto Return and Auto Lock  The phones now support two inactivity timers. These can be adjusted by the user through the phone's menus. For 9600 Series phones these are in addition to the phone screen saver options.

•	Auto Return  When this timer expires, the phone will exit any menu and return to it normal idle phone display.
•	Auto Lock When this timer expires, the phone will be automatically locked.
•	Name Display (1400 and 1600 Series only)  Through the phone's menus the user can select to have their name displayed rather than the extension number when the phone is idle.

•	Visual Voice  The operation of visual voice has been enhanced. After selecting a messages category (New, Old or Saved) playback no longer starts automatically. Instead the user can scroll through a listing of the messages and select which message to play or delete.
•	Small Community Networking  The Small Community network user limit has been increased from 500 to 1000.

DECT R4

The following features are support for DECT R4 systems upgraded to the new firmware supplied with IP Office Release 6.0.

•	Compact Base Station This is a 4 channel base station with internal aerials. Up to 5 compact base stations can be include in a system, in conjunction with existing 8 channel base stations.

•	Directory Integration IP Office directory integration can now be done without needing a AIWS unit on the LAN. An AIWS is still required for over the air firmware upgrades to the phones.

SIP Trunk Enhancements

•

SIP Trunk Prefixes The SIP line settings now include fields for defining the prefixes to be added to the caller's number. This is similar to the prefix fields used by other external line types supported by IP Office.  On systems where a prefix is required to make external calls, adding the prefix to the number received on incoming calls allows the call records shown in call logs and other areas to be used for return calls.

•	SIP URI Parameters for Hunt Groups and Voicemail SIP URI information can now be configured the hunt groups and for the Voicemail Pro voicemail server.
•	SIP Session Timers  Conforming to RFC4028, the IP Office uses SIP session timers to detect whether a call is no longer connected.

•	Multiple SIP Accounts per Trunk  Previously only two sets of ITSP account details could be configured for each SIP line to a particular ITSP IP address. IP Office Release 6.0 allows up to 30 sets of account details to be added to the line settings.

•

SIP Trunk Out of Service Detection The IP Office can regularly check if a SIP trunk is in service. Checking that SIP trunks are in service ensures that outgoing call routing is not delayed waiting for response on a SIP trunk that is not currently useable. For both UDP and TCP trunks, the OPTIONS message will be regularly sent. If no reply is received the trunk is taken out of service. For TCP trunks, if the TCP connection is disconnected the trunk will be taken out of service.For trunks using DNS, if the IP address is not resolved or the DNS resolution has expired, the trunk is taken out of service.

•	SIP Trunk Registration Using DNS Domain Names  If the IP Office is a DHCP client in a network with a DNS server, the SIP trunks can be configured to use the ITSPs domain name rather than requiring the ITSPs IP address.

one-X Portal for IP Office

For IP Office Release 6.0, the one-X Portal for IP Office application has been enhanced as follows:

•	Conference Display and Conference Functions The display of conference calls has been changed and can now be used to drop parties from a conference and to mute parties in the conference including muting all.

•	Profiles  The user can now add and configure profiles. Each profile contains a range of telephone settings. The user can then use the one-X Portal to select which of their profiles is active. Profiles contain settings for mobility (forwarding, mobile twinning and telecommuting), voicemail (on/off, ringback, outcalling on/off and playback destination) and call pickup.

•	Instant Messaging  one-X Portal for IP Office Workers can use the application to launch instant messaging sessions between each other.

•	Language Support In addition to English and German, the one-X Portal for IP Office also supports French, Italian, Dutch, Brazilian Portuguese and Russian.

•	Personal Directory Tabs  In addition to the default Personal tab, users can now add additional tabs onto which they can add personal contacts.

•	Call Pickup  Users can now enable call pickup for their calls by other one-X Portal users. When enabled, the user's directory entry in other user's directories will indicate when they have unanswered calls waiting and allow those calls to be picked up.

•	Telecommuter Mode  The one-X Portal for IP Office can be used in telecommuter mode
•	Voicemail Features The following additional options are supported with one-X Portal and Voicemail Pro 6.
•	Browser Playback Using one-X Portal profiles (see above), the user can select to playback messages through their phone or through their browser.
•	Voicemail Greeting Users can upload mailbox greeting files using one-X Portal and select which greeting is active.

Customer Call Reporter

Version 1.2 of the Customer Call Reporter is supported by IP Office Release 5 and IP Office Release 6.0.

•	Windows 2008 Server Support  Support for installation on Windows Server 2008 systems. That includes both 32-bit and 64-bit systems.
•	IP Office Switch Configuration  IP Office switch discovery and selection is no longer part of the Customer Call Reporter software installation. Instead the IP Office switch details can be edited manually by the Customer Call Reporter administrator after software installation.

•	Maximum Database Size Configuration The maximum MS-SQL database size can now be set by the Customer Call Reporter administrator. The Customer Call Reporter will then provide warnings and take housekeeping actions when the actual database size approaches the configured maximum size.

•	Supervisor Scheduled Housekeeping Tasks  Through the scheduler tab previous used for historical reports, supervisors with Self Administer rights can now also configure a number of house keeping tasks. Housekeeping tasks configured by one supervisor can be seen by other supervisors. Each task can be configured to run with a specified frequency or just once. The housekeeping tasks include:

•	Reset Realtime Statistic  Reset the statistics shown in all supervisor, agent and wallboard views.
•	Backup Database  The backup database is placed into the default MS-SQL backups folder with a date and time prefix to the file name.

•	Re-Index Database By default this task is already scheduled and occurs at 1:30am. Re-indexing the database allows reports to run faster, however during the actual re-indexing the response of Customer Call Reporter is slowed.

•	Reset Web Services By default this task is already scheduled and occurs at 11:00pm.
•	Wallboard Display Mode  In addition to creating supervisor accounts, the administrator can also add wallboard accounts. When a browser is logged in using a wallboard account it displays real-time data on queues and agents in a style intended for display on large screen monitors being used as wallboards.

•	Each Customer Call Reporter supervisor license instance enables one supervisor login and also one wallboard login.

•	The wallboard display mode requires the web browser being used to support Microsoft Silverlight.

•	The wallboard display can include combinations of queue and agents statistics from all Customer Call Reporter queues and agents. For each statistic displayed, alarm and warning settings can be applied and, where appropriate, inclusion of internal and or external calls can be selected.

•	In addition to Customer Call Reporter statistics, a number of other items can be selected for the wallboard display such as:

•	Title - A customizable text title can be added to the wallboard display.
•	Logo - A logo picture file can be uploaded for display in the wallboard.
•	Agent League Table - A dynamic table showing the top, the bottom or a combination of the top and bottom agents for a selected queue and statistic.
•	Graph - Display a graph of a selected queue statistic over time.
•	Supervisor Messages - Customer Call Reporter supervisors can configure scheduled messages which appear in the message bar of selected wallboards.
•	Report Changes The following changes have been made to the historical report templates:
•	IP Office Connection Loss Reporting If the data analyzer component of Customer Call Reporter is unable to connect to the IP Office system, it will record details in the Customer Call Reporter database. Any reports run that cover the same period as a lose of connection will include details of the connectionless period in the report.

•	Call Summary Report Template Changes  In the Call Summary Report template, the Total Calls column is now Call Interactions and does not include No Answer calls. An additional column, Customer Calls, which is the number of unique calls has been added.

•	Call Details Report Template Change  In the Call Details Report template, the summary sections now include totals for Customer Calls and Call Interactions.

Voicemail Pro

The following is a summary of the new features in the IP Office Voicemail Pro 6.0 release. For details of previous releases refer to the Appendix. Voicemail Pro 6.0 is supported with systems running IP Office Release 6.0. That includes IP406 V2, IP412, IP500 and IP500v2 systems.

Centralized Voicemail

In addition to the support for IP Office control fallback added in IP Office Release 5, the following additional options are now supported within a Small Community Network using IP Office Release 6.0 and Voicemail Pro 6.0:

Backup Voicemail Server  An additional Voicemail Pro server can be installed. The address of this server is entered in the configuration of the central IP Office. During normal operation; messages, call flows and other settings on the backup voicemail server are synchronized with those on the central voicemail server. If the central voicemail server becomes unavailable, the central IP Office will switch to using the backup voicemail server for voicemail services. When the central voicemail server is restored, the central IP Office will switch back to using it for voicemail services and any new messages on the backup server are synchronized with it. The backup voicemail server operates using the existing voicemail licenses held by the central IP Office for normal operation.

Distributed Voicemail Servers Multiple Voicemail Pro servers can be installed within a Small Community Network. These are referred to as distributed voicemail servers. Within the configuration of the IP Offices in the network (other than the central IP Office and its fallback if any), you can specify that the IP Office uses a particular distributed voicemail server for its voicemail services. This requires the IP Office to have licenses for voicemail operation and the voicemail features it requires. Multiple distributed servers can be supported and several IP Offices can share the same distributed server, each using their own license set. The distributed server is used for all services apart from message collection and message waiting indication, those services are still performed by the central voicemail server. Messages recording is done by the distributed servers with the messages then being forwarded to the central voicemail server.

Voicemail Operation Features

•	Alarm Action Enhancements The alarms provided by the voicemail server using the Alarm Set action and the alarms queue panel have been enhanced to allow alarm repetition and to require an dialed response to clear an alarm in order to prevent it repeating.

•	Alarm Duration and Retries  The ring duration for an unanswered alarm call can be adjusted. In addition, a number of retries and the interval between retries can be specified for an unanswered alarm.

•	Alarm Clearing  Normally the alarm and any repeats are cleared once the alarm call is answered. For Voicemail Pro 6.0, a cancel code of up to 4 digits can be specified and must be dialed to stop the alarm from using any further retries.

•	Alarms Administrator  A new type of client account has been added. The Basic account user can only edit alarm settings shown in the Alarms queue panel.

•	Administration of Mailbox User Settings for Outcalling and Personal Distribution Lists  User mailbox settings such as outcalling settings and personal distribution lists can be accessed and edited through the Voicemail Pro client.

•	TTS Prompt Generation On voicemail servers licensed for text to speech (TTS), the prompts used for call flow actions can be generated using TTS. The text entered in the action's Description field is used as the script for the recording.

•	Voicemail Configuration Backup and Restore  The Voicemail Pro client can be used to configure daily, weekly and monthly automatic backups or to run an immediate manual backup. Each backup type can be individual configured for the types of files and settings it should include including messages. The client can also be used to restore the files from a previous backup.

•	Get Mail Action - Advanced Personal Options For systems running in Intuity mode, a Get Mail action can be used in call flows to provide the user with access to a range of mailbox control actions. These actions become part of the mailbox telephone user interface. The options that become available are:

• Voicemail on/off. • Voicemail email mode. • DND on/off.

• Follow Me. • Forwarding. • Edit Voicemail.

• Edit Callback Number. • Edit Mobile Twinning.

•	Personal Options Menu Action  The Play Configuration Menu action has been replaced by the Personal Options Menu action. This action can operate in one of two modes. The legacy mode
•	Generic Action - Set Interdigit Delay The delay that the voicemail server allows between the dialing of digits in numbers (by default 5 seconds) can be adjusted for a call flow using a Generic action.

•	Recording Auto Deletion  System wide automatic deletion delays can now be specified for new and old recordings. These are separate settings from those used for new and old messages. In addition the playback order for recordings (first in-first out or last in-first out) can also be specified.

•

Voicemail Server Shut Down and Suspend Controls  The Voicemail Pro client can be used to shut down or suspend voicemail server operation. In either mode, voicemail is treated as no longer available by the IP Office. Suspend mode can be canceled using the Voicemail Pro client, after which normal voicemail server operation is resumed. Shut down mode can only be canceled by restarting the voicemail service or the server PC. The shut down and suspend processes are polite processes, allowing existing calls to be completed while stopping new calls. However if required the shut down process can be turned from a polite shut down to an immediate shut down.

Application Support

This sections summarizes the support for IP Office applications by IP Office Release 6.0. Some specific features of applications may have additional requirements. Those requirements will be details in the appropriate application installation manual.

Windows Operating System Support

The following table gives a summary of the operating systems on which the IP Office applications that are part of the IP Office Release 6.0 have been tested and are supported. While the applications may function of other operating systems, they have not been tested by Avaya and are not supported.

IP Office Application	Windows Clients						Windows Servers
	XP Pro		Vista		Windows 7		2003	2008
	32	64	32	64	32	64	32	32	64
Voicemail Pro server		–		–
... plus UMS	–	–	–	–	–	–
... plus campaigns	–	–	–	–	–	–
Voicemail Pro client
ContactStore	–	–		–	–	–			–
one-X Portal for IP Office	–	–	–	–	–	–
Customer Call Reporter	–	–	–	–	–	–
SoftConsole		–					–	–	–
IP Office Manager
System Monitor
System Status Application
TAPI - 1st Party
TAPI - 3rd Party
Phone Manager Lite/Pro		–		–			–	–	–
Phone Manager PC SoftPhone		–		–			–	–	–

•	Vista support is only on Business, Enterprise and Ultimate versions.

•	Windows 7 support is only on Professional, Enterprise and Ultimate versions.

Virtual Server Support

For IP Office Release 6.0, all applications supported on Windows server operating systems are supported while running on the following virtual servers:

•	VMWare Server.

•	Microsoft Virtual Server 2005 R2.

•	Microsoft Server Hyper-V.

Browser Application Support

The following applications are accessed using web browsers. The table below details the browsers tested by Avaya.

Application	Windows				Mac
	Internet Explorer	Firefox	Opera	Safari	Safari
Voicemail Pro UMS	7+	3+	2+	3.2+	3.2+
one-X Portal for IP Office	7+	3+	2+	3.2+	3.2+
Customer Call Reporter	7+	3+	2+	3.2+	3.2+
ContactStore 7.8	7+	–	–	–	–

Microsoft Outlook Support

Where IP Office applications interact with Microsoft Outlook, for IP Office Release 6.0, the version of Outlook supported are Outlook 2003 and Outlook 2007.

Licences

Note that this section covers just the licensing for IP Office Release 6.0 systems.

Various IP Office features and applications require entry of license keys into the system's configuration. The license keys are unique 32-character codes based on the feature being activated and the serial number of the Feature Key dongle being used by the IP Office system.

The serial number is printed on the feature key dongle and prefixed with SN (FK for IP500v2 SD card dongles). It can also be viewed in the system configuration by selecting System | System | Dongle Serial Number.

For IP406 V2 and IP412 systems, the Feature Key dongle takes the form of a device attached to the serial port of the control unit. This key is only required if licensed features are needed.

For IP500 and IP500v2 systems, the Feature Key dongle takes the form of a card (smart media or SD card respectively) inserted into the control unit. The card is a mandatory item for these systems even if they use no licensed features.

•

Example 1: Enabling Features  In the example above, the IP Office system has a valid Power User Profile license. In this case the license is for 20 instances. That means that up to 20 IP Office Workers can have their Profile set to Power User. This allows them to be configured for a range of features not available to other users.

•

Example 2: Enabling Applications and Features  The example above the IP Office also has a Preferred Edition (Voicemail Pro) license. This licenses enables a range of features including support for the IP Office Voicemail Pro application and 4 ports between the IP Office system and the voicemail server. Additional ports have also been added using an Preferred Edition Additional Voicemail Ports license.

When a license key is entered into the IP Office configuration, the following information is shown.

•	Status The status, which is Unknown until the configuration file is sent back to the IP Office system.
•	Unknown This status is shown for licenses that have just been added to the configuration shown in IP Office Manager. Once the configuration has been sent back to the IP Office and then reloaded, the status will change to one of those below.

•	Valid The features licensed can be configured and used.
•	Invalid The license was not recognized. It did not match the serial number of the Feature Key.
•	Dormant The license is valid but is conditional on some other pre-requisite licenses.
•	Obsolete The license is valid but is one no longer used by the level of software running on the IP Office system.
•	License The name of the licensed feature. This may differ from the ordered RFA name
•	Instances Depending on the license, this may be the number of ports enabled or number of simultaneous users of the licensed feature. Sometime the number of instances is specified in the license name.

•	Expires Most purchased licenses have no expiry setting. For some features, trial licenses may be available which will have an expiry date.