Partner Plus (without VMI)

Manufacturer: AT&T

Model: Partner Plus

Software Version: Release 3

Hardware Requirements: Must have Release 3 software to retrieve messages from Partner phones

VoiceTrak Parameter Settings:

Important: All other VoiceTrak parameters must be set to Default.

Use Tone/Cadence file: PARTNER.ATT

Notes

General -

The AT&T Partner is a good phone system with many features to make integration simple. Be aware of the lack of station hunt groups!

Tone/Cadence Files -

Use the file PARTNER.ATT or develop a new file using ACCUCALL. Use only R type mailboxes as the Partner has no forward to VM scheme. Do not use N type mailboxes.

Message Waiting Lights - When an outside caller leaves a new message, the message light on the multibutton sets will light. When the subscriber calls the mailbox to retrieve messages, the light will go off. The LAST VoiceTrak port should be used ONLY as a utility port and not accessed by internal users or outside callers. If the last port is always busy, the lights won't operate properly.

Software Version

Release 2 software does not include 'end to end' DTMF. This means that messages can't be retrieved from proprietary multibutton AT&T sets unless you dial out on one outside line and call back in to the VoiceTrak system using a second outside line. Messages may also be retrieved on an intercom call if a standard single line telephone is used. Release 3 corrects this problem and messages can be retrieved from any telephone on an intercom call. We strongly recommend that the customer upgrade to Release 3 software.

Disconnect Tone

The Partner system does not provide a disconnect tone, which could be either a loop current drop or some other signal. Since the Partner returns silence on a disconnect it's necessary for VoiceTrak to time out and test for a valid caller using the grunt feature. Do not deactivate the VoiceTrak grunt feature when connected to an AT&T Partner!

Camp On

If the Partner multibutton phones have multiple line appearance keys the Call Processing portion of VoiceTrak can send more than one call to the extension at the same time. Therefore, even if the extension is actually busy VoiceTrak won't hear the busy tone and will ring the extension. The system user can place the first call and hold and answer the second, or just let the second call go to the voice mail box. VoiceTrak will ring the extension the number of times set on the mailbox setup screen and perform a no answer return sequence if the call is not answered. VoiceTrak will only hear a busy signal on a single line set which is busy, or a multibutton proprietary set if all the line appearances have been occupied. This is a frequently requested feature on other phone systems.

Non Blocking

The Partner Release 3 documentation states the Partner is non blocking so it's not necessary to be concerned about adequate intercom paths for the voice mail system. We're not sure if this is true.

Programming

Programming must be done from a display set at the attendant station.

Automatic Line Selection

The VoiceTrak ports must be set for automatic line selection of an intercom path. If this is not programmed properly the message waiting lights will not operate with VoiceTrak. To program from the attendant console: Press <Feature> <0> <0> <System Program> <System Program> <Central Tel Prog> <(Extension to be programmed)> <*> <*> <(Press the intercom button)> <*> <*>. Repeat this process for each desired extension or use the copy function.

Automated Attendant

It is possible to use VoiceTrak as an automated attendant but there are a few complications due to the lack of station hunt groups on this phone system. Most modern phone systems employ a station hunt group feature, or at the least a 'busy forward' option on extension ports. As an example, assume that 20-24 are voice mail ports. On most phone systems you may program a station hunt group for 20-24 so that if 20 and 21 are busy, and a call is placed to 20, extension 23 will ring. On most phone systems you can direct any or all CO trunks to ring at extension 20, providing 4 ports available to answer CO line calls.

Since the Partner does not provide this feature it is necessary to ring individual CO lines to individual VoiceTrak ports. A customer with 6 CO lines should actually have 8 VoiceTrak ports available. VoiceTrak ports 1-6 would be available to answer CO lines 1-6, while ports 7 and 8 would be available for message retrieval and message light operation. If the customer does not wish to purchase an 8 port system it is possible to direct more than one CO line to one VoiceTrak port. For example, CO lines 1 and 5 could ring at VoiceTrak port 1, CO lines 2 and 6 could ring at VoiceTrak port 2, CO 3 could ring at VoiceTrak 3, and CO 4 could ring at VoiceTrak 4. The problem with this implementation is that during message retrieval one or more CO ports will not be answered by the automated attendant.

As a backup, the attendant console rings on all incoming lines. The attendant will hear one ring only if VoiceTrak answers the call, but if the VoiceTrak port is busy the attendant console will continue to ring.

It is highly recommended that one VoiceTrak port be reserved exclusively for each CO line, and that two or more VoiceTrak ports be available exclusively for message retrieval and message light activation.

It is unfortunate that AT&T did not add this very basic feature to the Partner system and that AT&T forces Partner customers to needlessly waste thousands of dollars, but there is no other solution.

Note that Call Coverage should not be used because this will cause all VoiceTrak ports to ring for each call. All ports will attempt to answer the call. Only one port will actually connect, but the others will be forced to time out before releasing.