Nortel Meridian Meridian 1 Implementation Manual page 177

Meridian integrated conference bridge
Hide thumbs Also See for Meridian Meridian 1:
Table of Contents

Advertisement

Table 48
Event examples (Part 2 of 2)
Example
Meeting Ended – In these examples, the time stamp, card ID, meeting ID, and billing account
information was available. Examples report this event for three different cases:
The meeting was cancelled before it began.
10,05,00,05,1234,7,999,00
The active meeting was cancelled after it began.
12,48,00,06,1234,7,999,06
The meeting's scheduled time elapsed.
13,28,00,07,1234,7,999,10
Card Restarted – In this example, the time stamp, and card ID information was available.
16,08,30,08,1234,
Succession 1000M, Succession 1000, and Meridian 1 Call Detail
Recording
The Call Detail Recording (CDR) feature enables the MICB to charge
users for out-going calls based on CDR reports the system generates.
The reports are generated even if the call is unanswered. The system
must have the following software packages: Call Detail Recording
(CDR) package 4; and CDR with Charge Account (CHG) package 23.
Note: CDR is not available on the Meridian SL-100.
To enable the CDR feature, select "Billing and CDR Reports" from the
Billing options pull-down menu in the MICB Dashboard – General
Settings window (see
Meridian Integrated Conference Bridge
Description
This record indicates that a user cancelled the
meeting reservation at 10:05 am from the BUI,
before the scheduled start time. The number of
ports is 0, because none of participants entered
the meeting.
This record indicates that the meeting ended at
12:48 pm from the BUI, before the scheduled
meeting time elapsed. The number of ports
shows how many participants entered the
conference. This number can be greater than the
number of ports booked for the meeting, because
the meeting person booking the meeting enabled
the option for expansion.
This record indicates that the meeting ended at
01:28 pm, because the scheduled time elapsed.
The number of ports shows how many
participants entered the conference. This number
is greater than the number of ports booked for the
meeting, because of expansion during the
meeting.
This record indicates that there was a card restart
at 16:08:30. The event ID appears in bold letters.
1234 is the card's ID, 7 is the meeting's ID, and
999 is the customer's billing ID.
Figure 48 on page
Service Implementation Guide
Page 177 of 208
101).

Advertisement

Table of Contents
loading

This manual is also suitable for:

Meridian 1Succession 1000m1000 con?guration guide

Table of Contents