# Conditions

The following are conditions for the Record-A-Call (RAC) feature on the NuPoint Unified Messaging system when using a MiVoice Business or a MiVoice Office 250:

Note: Record-A-Call should only be used in conjunction with the laws of the jurisdiction where the call is placed from, and/or the laws of the jurisdiction of the place being called. Mitel is not liable for use of this feature in a manner that does not conform with the applicable law (for example, laws involving wiretapping, eavesdropping, electronic surveillance, call recording, etc.). Dealers should warn customers in writing that they are responsible for the of use this feature in accordance with the law and that in many jurisdictions, both parties must be made aware that the call is being recorded in order.

## Conditions for Record-A-Call on a MiVoice Business System

- Tones are not given to either party to indicate that the call is being recorded.

- Record-A-Call does not work with PIMG integrations.

- For best performance, Record-A-Call requires softkey event capability. However, if Record-A-Call is purchased without the Superset Softkey feature option, and is implemented on a MiVoice Business Release 5.1.3 or later, Record-A-Call is fully supported.

- Record-A-Call is limited to calls involving one trunk party and one RAC-enabled desk telephone. Record-A-Call softkeys are only functional when the telephone is connected to a trunk.

- The voice mailbox and telephone must be on the same network node.

- In order to receive Record-A-Call softkey events, NuPoint must register its telephones as 5240 devices, except the lines that are used for MWI, which must always be registered as 5020 devices. However, if the Record-A-Call feature is not installed, all telephones must remain registered as 5020 devices.

- In order for Record-A-Call to function, the COV/ONS/E&M Voice Mail Port feature must not be enabled in the Class of Service on incoming trunks. If the COV/ONS/E&M Voice Mail Port feature is enabled on the trunk of incoming calls, Record-A-Call will not work.

- Unlike regular voice mail sessions, Record-A-Call sessions do not time out after five seconds of silence in the conversation. In RAC sessions, 60 seconds of silence will cause automatic saving and termination of the Record-A-Call session.

- If the system goes out of service while a message is being recorded (that is, before the user saves the message), the message will not be available once the system is rebooted.

- A backup of voice mail messages will back up RAC messages just as it backs up regular voice mail messages. A backup and restore of the database will back up and restore the RAC option as well as any RAC FCOSs previously assigned to mailboxes. However, in an upgrade scenario where the previous software version is pre-release 9.0, the RAC licensable option is set to disabled by default. In this scenario, the RAC FCOS is also unassigned to any mailbox by default.

- If the Start Recording Automatically COS option is set to YES and the Record-A-Call user wishes to save the recording, the user must manually save by pressing the Save softkey before hanging up. If the Save Recording on Hang-up COS option is set to YES by the system administrator, the user's recording is saved automatically when the user hangs up. To avoid filling up the user's mailbox, the system administrator should use the Save Recording on Hang-up COS option with discretion.

- During the recording, if the Record-A-Call user presses the pause softkey, the recording stops. The recording can be paused for a maximum of ten minutes. At any time during this ten minute period, the user can resume the recording of the conversation.

- During the recording, if the Record-A-Call user places the call on hold, the recording stops. The recording does not automatically continue when the user retrieves the call from hold. If the user wishes to continue recording, the user must manually re-start the recording. Note that retrieving a call from hold, and restarting the recording generates two recordings for the call.

- During the recording, if the called party places the Record-A-Call user on hold, the recording continues.

- Record-A-Call has a 60-minute recording limit. When the recorded conversation reaches this limit, NuPoint saves the conversation and hangs up the call. The Record-A-Call softkeys disappear on the telephone (if the telephone supports softkeys) of the user who activated the recording session; however, the user remains in a two-way call with the called party. The user may start another Record-A-Call session, which is saved as another message, not appended to the previous message.

- If disk space runs out during a Record-A-Call session, NuPoint will stop the recording and save the message. If a Record-A-Call user's mailbox is full, the user will not be able to initiate a Record-A-Call session.

- Each Record-A-Call session requires three conference resources of the available 64 on the MiVoice Business ICP.

## Conditions for Record-A-Call on a MiVoice Office 250 System

- Record-A-Call on the MiVoice Office 250 requires MiVoice Office 250 Release 3.2 or higher and NuPoint Unified Messaging 4.0 or higher.

- MiVoice Office 250 users are automatically assigned the MiCollab FCOS (14) which does not have the required feature bits. Add the following feature bits to the MiCollab FCOS:

  - 007 Pause in record or play

  - 022 Make to multiple destinations

  - 023 Make and mark confidential

  - 027 Give and mark confidential