101. Data Privacy [HTML]
... ) have highlighted the need to keep personal data – that is, information that can be traced back to an individual – under a high degree of control. IP Office can under certain conditions process and save personal data. Some examples are: Call Detail Records (SMDR) may contain an individual's personal telephone number Call Recordings might contain personal information spoken by a caller Responsibility to keep such data protected is ultimately the responsibility of the Data Controller' For IP Office the Data Controller typically would be the company using the system. that is ...
... external calls CQ41470 9630 and other IP phones may restart when logging on with multiple buttons programmed. CQ41511 External calls transferred through embedded voice mail Auto Attendant Auto Answer when they should not CQ46556 Missed Call not indicated or populated in Call Log when calling busy telephone. CQ46617 SMDR: Call Park duration is deducted from Connected Time field when first SMDR record is output CQ46640 SMDR: Connected Time field of second record is zero when outgoing call is cleared after being parked and unparked CQ107322 Fast start failing on H323 calls from Asterisk system CQ107707 IP ...
103. Locally Upgrade the SD System Card Using Manager [HTML]
... recreating the SD card . This process will overwrite the software files on the card with the files available to IP Office Manager. This process takes approximately 20 minutes. • The process does not affect any current configuration file, Embedded Voicemail announcements and messages, or temporary SMDR data files. • The process deletes any current PLDS license file. The file needs to be restored after the SD card is recreated. 3.When the recreate process has completed, reinsert the card into the control unit's System SD card slot. 4.Using IP Office Manager ...
104. Announcements [HTML]
... call is presented. Note: Call Billing and Logging A call becomes connected when the first announcement is played to it. That connected state is signaled to the call provider who may start billing at that point. The call will also be recorded as answered within the SMDR output once the first announcement is played. If a call is rerouted, for example forwarded, the announcement plan of the original user is still applied until the call is answered. The exception is calls rerouted to a hunt group at which point the hunt group ...
... reporting on multiple numbers within the Incoming Pilot Summary' report. • Some report descriptions were not translated correctly. • The Lost Call tab in Callback Requests may not display lost calls correctly. • VoiceMail Pro Callflow reports may not present all available data. • The SMDR COM port may still be used by the Delta Server after is disabled. • An agent may appear to be in an incorrect state in CCV when receiving a supervised transfer. • CCV does not display "Comms Failure" when the connection to the Delta Server ...
106. System Alarm Output [HTML]
... Alarm Output You can configure the IP Office system to generate a system alarm for any call that uses a Dial Emergency short code. In addition to reporting connected calls, the alarms also report emergency call attempts that fail for reasons such as no available trunks. Unlike SMDR call records which the IP Office system generates at the end of a call, the IP Office generates emergency call system alarms immediately a call matches a Dial Emergency short code. This is important, as the PSAP emergency operator can stay on the line until the ...
107. Recreate IP Office SD Card [HTML]
... card with the version of those files installed with the Manager application. It includes the binary files for the system, external expansion modules and phones. The command also copies all language prompt sets used by Embedded Voicemail. If the card contains dynamic system files such as SMDR records, they are temporarily backed up by Manager and then restored after the card is recreated. For the card to be used in a system's System SD slot the card must be Avaya SD Feature Key card. The card must be correctly formatted, however a ...
108. Add Authorization Code [HTML]
... Code When a user dials an external number that matches a short code set to Force Authorization Code, the IP Office system will prompt the user to enter their associated Authorization Code before allowing the call to continue. Valid/invalid authorization code entry is recorded in the SMDR output. The code used is not recorded. These settings are mergeable. Changes to these settings do not require a reboot of the system. Note: For Release 9.1 and higher, you can no longer associate Authorization Code entries with User Rights. Authorization Code ...
109. Recording Caller Consent [HTML]
... or requirement. It may also be a requirement to keep a record of the caller's consent. When using embedded voicemail, this can be done using the Consent Directive settings of each auto-attendant action. These cause a consent value to be included in the system's SMDR output for the call (0 = consent not requested, 2 = consent given, 6 = consent denied) . The consent value is also included in available to the system's DevLink3 CTI output. Example The customer has a sales group. If the group is ...
110. IP Office Technical Bulletin 109: R5.0 [PDF]
... T3 Telephones and one-X Portal only) ..... 9 2.15 Call Coverage to Operator Group (Coverage Group) .... 12 2.16 Button Label Printing (16xx Series Telephones Only) .... 13 2.17 Embedded Voicemail Enhancement – Dial By Name .... 13 2.18 SMDR to replace CDR .... 14 2.19 Manager / Hunt Group Configuration .... 14 2.20 Short Code Feature "Busy" is renamed "Barred" .... 15 2.21 Automatic Codec Preference .... 15 2.22 Advanced Codec Selection .... 16 2.23 Simplification of VoIP Settings ...
111. Locally Upgrade the SD System Card Using Manager [HTML]
... recreating the SD card . This process will overwrite the software files on the card with the files available to IP Office Manager. This process takes approximately 20 minutes. • The process does not affect any current configuration file, Embedded Voicemail announcements and messages, or temporary SMDR data files. 3.When the recreate process has completed, reinsert the card into the control unit's System SD card slot. 4.Using IP Office Manager select File | Advanced | Reboot. 5.In the Select IP Office menu, select the IP500 V2 system and click OK. ...
112. Changing the rejected call responses [HTML]
... by default the rejection is done using the response code 666 and the string "Unwanted" . However, if required by the ISP, a different code and/or string can be used, configured using the process below. Rejected calls are included in the system's SMDR and CDR outputs. Rejected calls are not included in the individual user's call logs and call histories. Procedure Open the SIP line's settings and select SIP Engineering. Click Add and enter one of the following custom strings: To change the reject code, enter SLIC_STIR_REJECT_CODE ...
113. System Alarm Output [HTML]
... Alarm Output You can configure the IP Office system to generate a system alarm for any call that uses a Dial Emergency short code. In addition to reporting connected calls, the alarms also report emergency call attempts that fail for reasons such as no available trunks. Unlike SMDR call records which the IP Office system generates at the end of a call, the IP Office generates emergency call system alarms immediately a call matches a Dial Emergency short code. This is important, as the PSAP emergency operator can stay on the line until the ...
114. Announcements [HTML]
... call is presented. Note: Call Billing and Logging A call becomes connected when the first announcement is played to it. That connected state is signaled to the call provider who may start billing at that point. The call will also be recorded as answered within the SMDR output once the first announcement is played. If a call is rerouted, for example forwarded, the announcement plan of the original user is still applied until the call is answered. The exception is calls rerouted to a hunt group at which point the hunt group ...
115. Private Calls [HTML]
... be disabled for the user. Use of private calls can be changed during a call. Enabling privacy during a call will stop any current recording, intrusion or monitoring. Privacy only applies to the speech part of the call. Call details are still recorded in the SMDR output and other system call status displays. Button Programming The button programming action Advanced | Call | Private Call can be used to switch privacy on/off. Unlike the short code features it can be used during a call to apply or remove privacy from current ...
... for ISDN is not populated when making a second call out of a single line set CQ68165 T3IP phone with 1 x BLF/DSS module locks up when calling Collective H/G (DSS monitoring all H/G members) CQ68539 IP Office 4.2.4 & 4.2.101110 - SMDR Output. Fowarded call not shown (see also CQ67029) CQ69306 System restart running 4.2.4 (PB 47001) - Exception error. CQ69600 Conference calls made via TAPI are not releasing all parties CQ70446 Manager - incorrect restart mode selected when modifying IP extension gains CQ70719 Dial ...
117. System Date and Time [HTML]
... Office servers can obtain their date and time either automatically from a time server or have it set manually. How Does the System Use the Date and Time For files stored on memory cards the system uses the UTC time. For other activities such as call logs, SMDR records, time display on phones; the local system time (UTC+ any offsets) is used. ...
118. Announcements [HTML]
... flow should be used before the call is presented. A call becomes connected when the first announcement is played to it. That connected state is signaled to the call provider who may start billing at that point. The call will also be recorded as answered within the SMDR output once the first announcement is played. If a call is rerouted to a hunt group's Night Service Group or Out of Service Fallback Group, the announcements of the new group are applied. If a call overflows, the announcements of the original group are still ...
119. Authorization Codes [HTML]
... Codes When a user dials an external number that matches a short code set to Force Authorization Code, the IP Office system will prompt the user to enter their associated Authorization Code before allowing the call to continue. Valid/invalid authorization code entry is recorded in the SMDR output. The code used is not recorded. These settings are mergeable. Changes to these settings do not require a reboot of the system. Note: For Release 9.1 and higher, you can no longer associate Authorization Code entries with User Rights. Authorization Code ...
120. Authorization codes [HTML]
... restrictions; this may grant the user greater or fewer privileges than the normal owner of the extension they use. Authorization codes are independent of account codes, so the user has to enter both if the required by the system configuration. All entered codes are logged in SMDR. ...
121. IP Office Technical Bulletin 105: [PDF]
... in IP Office CCC 5.0.65 software CQ Number Description of Issue CQ39796 1899/12/30 00 date in Delta Server reports after an outbound call is joined to an internal conf call CQ39813 PC Wallboard shows 2 I/C calls when caller drops CQ66378 Conference representation in SMDR is inconsistent when an external party is involved CQ68692 "Incoming Call By Target" reports 2 calls against a group when call is answered by Forwarded number CQ70801 The number of Hunt Group Calls Waiting displayed on CCV and PC Wallboards is incorrect. CQ64854 Incoming DDI Summary ...
122. IP Office Technical Bulletin 096 [PDF]
... POTS CQ39435 Large SCN configs cause audio to distort during merge of central site CQ39481 5400 Users are logged off when changing VoiceMail passwords for the first time at a remote location. CQ53286 No CLI displayed on C450 when connected to a port of a POTS30V2 CQ53843 CCC - SMDR record missing on a trunk to trunk transfer CQ54697 POTS phones do not show CLI. Works on POTS+ but not on POTSv2 or IP500 POTS8. CQ55270 SMDR does not show record of trunk to Trunk transfers on SMDR screen and output logs 5.2.16 delta server CQ55988 ...
123. Monitoring the IP Office Platform [HTML]
... unusual activity, for example: New VoIP extensions Forwarding set Phones dialling unexpectedly Unable to make outgoing calls Unusual call destinations Unusual call volumes or time of day/week High phone bill Unable to login to phones or applications Unable to use voicemail The string Barred' in SMDR reports The syslog tag of IPTables-Rejected' in Linux server syslog events. Review Avaya Security advisories Review Avaya IP Office application notes, technical bulletins and tips Ensure the latest IP Office service packs are applied Monitor telephony provider communications Conduct periodic security reassessment ...
124. IP Office Technical Bulletin 102 [PDF]
... variable doesn't increment if you end a call after the queue messages. CQ63882 Delta Server - 2 x CCC Report Viewer licenses are shown in License info CQ66995 Incorrect agent states agent logs off during system wrap-up timer and then logs on again. CQ67292 Cannot change SMDR COM PORT CQ68121 CCC - Force Agent Status should not operate when logged on with access level of Supervisor. CQ68164 CCC - French characters é,e^ and ç are not displayed correctly on 2 reports 4 Upgrade instructions If upgrading from a previous release of CCC to version ...
125. Survivability for centralized users [HTML]
... (MWI) Automated Attendant Survivability mode indication on the phone screen Local telephone features: redial, mute, audio selection (speaker / headset / handset) , Call Logs, Volume Control, local contacts, speed-dials, auto dials Station Message Detail Recording (SMDR) records stored on the IP Office for retrieval after WAN recovery Hunt groups IP Office can be configured with Centralized hunt groups for which IP Office processing is in effect only in the Rainy day mode. The IP Office administrator must configure the hunt groups on the ...
