The Call Detail Recording (CDR) Subscriber Detail report provides
traffic information about the voice messages sent by and received
by subscribers. This report, which can be used for monitoring, marketing,
and billing purposes, can provide information about:
- All the messages a particular subscriber sent during a specified
report period
- Messages that a particular subscriber sent to a particular recipient
- All messages sent to a particular recipient
- All messages sent from all subscribers to all recipients
To access the CDR Subscriber Detail report:
- Start at the Administration menu, and select Message Networking Administration
> Call Detail Recording > Subscriber Detail
Report.
The system displays the Subscriber Detail Report page.
- Complete the fields on the page.
For information on completing the fields, click the field names
or Help on the Web-based administration page.
- Click Display.
The system displays the Subscriber Detail Report. The following
table provides a description of each field contained in the report.
Field |
Description |
Sending |
Sending network address or mailbox ID specified for reporting.
All messages sent by this subscriber during the date and
hour range specified are displayed. |
Receiving |
Receiving network address or mailbox ID specified for
reporting. All messages received by this subscriber during
the date and hour range specified are displayed. |
Message ID |
Unique numeric identifier assigned by the Message Networking for this
message. |
Receiving
Date/Time |
Date (mm/dd/yy)
and time (hh:mm)
that the message was received (for example, 10/01/96 15:35).
|
Sending
Date/Time |
Date (mm/dd/yy)
and time (hh:mm) that
the message was sent (for example, 10/01/96 12:00). |
Size
(sec) |
Length of the received or delivered list:
- 1 - no list received
- 2 to 999 - length (in seconds) of a list received
by or delivered to Message Networking; includes the
Message Networking recipient or sender
|
! |
Indicates whether this message was sent as a priority
message. |
P |
Indicates whether this message was sent as a private message. |
Status |
Indicates the status of the message.
- ok: successful
- compo: message component delivery failure (reserved)
- conn: failed message because of a connection failure
- dfull: insufficient disk capacity
- dup: duplicate subscriber
- eag_b: subscriber has extended absence greeting block
- eag_w: extended absence greeting warning
- erfu: destination that is not accepting calls
- full: failed message because mailbox is full
- futuex: future expire (reserved)
- fwd: forwarded message (reserved)
- inval: failed message because message contains invalid
message attributes (message header corrupted, and so
on.)
- futur: failed future delivery
- II-II: upstream Message Networking error
- >len: message size is too large
- Len: AMIS message length too long
- misc: failed message because of a miscellaneous error
- mmed: failed message because subscriber does not support
message media type
- mmfail2: failed message due to an unknown media type
- nosub: failed message because subscriber does not
exist
- nosup: feature not supported (annotation only to AMIS,
and so on)
- perm: failed message because
of a permissions failure
- prm: permanent failure
- refu: destination is not accepting calls
- reply: reply to previous message (reserved)
- rest: sending restrictions (community IDs)
- restr: failed message because of sending restrictions
- tmp: temporary failure
|
-
Click Return to Main to return to the Administration menu.
Top of page
|