Reports 209
CDR example scenarios
The conference call was booked using the BUI by a user whose billing account is 9134513, on July 19, 1999 at 06:15 p.m., for July 20, 1999 from 08:00 a.m. to 09:00 a.m. The number of ports booked is six.
The conference call was started as scheduled on July 20, 1999 two minutes before 08:30 a.m. During the call at 08:36 a.m. (after eight minutes), the chairperson calls out once to a long distance number and brings a user into the call. After 47 minutes the dialed out person drops off. No record is stored in the ICB card in relation to this event.The following record appears in the CS 1000 CDR:
C 040 00 5211 T095019 20/07 08:36 00913451312340000000007 & 0000 0000
N 041 00 5211 T095019 20/07 09:23 00:47:08 A 333 & 0000 0000
At 08:55 a.m. the chairperson calls out to a long distance number and after two minutes returns to the meeting without the dialed party. The following record appears in the CS 1000 CDR:
C 040 00 5215 T095019 20/07 08:55 00913451312340000000007 & 0000 0000
N 041 00 5215 T095019 20/07 08:57 00:02:12 A 333 & 0000 0000
Maintenance (Error) Report
BUI Maintenance (Error) Report
Figure 91 shows how the BUI Maintenance Report.
Figure 91
Maintenance (Error) Report BUI example
|
|
|
|
| report to your computer |
|
|
|
|
|
|
| |
| No. | Severity Err code | Timestamp | Message |
| |
| 0001 | Minor | BBF050 | 10:00:03 | BBF_GetConfigVar: failed fs_open_f for filename: a:user\schedule.ini,rc = 200b |
|
| 0002 | Info | PH603 | 10:22:43 | Time and Date update - OLD: |
|
| 0003 | Minor | BBF050 | 11:30:08 | BBF_GetConfigVar: failed fs_open_f for filename: a:user\schedule.ini,rc = 200b |
|
| 0004 | Minor | BBF050 | 12:15:00 | BBF_GetConfigVar: failed fs_open_f for filename: a:user\schedule.ini,rc = 200b |
|
| 0005 | Info | PH000 | 12:43:20 | Midnight |
|
| 0006 | Minor | BBF050 | 14:01:22 | BBF_GetConfigVar: failed fs_open_f for filename: a:user\schedule.ini,rc = 200b |
|
|
|
|
|
|
|
|
Nortel Integrated Conference Bridge Service Implementation Guide
