Interpreting Your Results

Your billing software can evaluate certain CDR fields in order to determine which of several possible mailbox transactions occurred. See the CDR Record Field Relationships table below for the values these fields can take. Explanations are abbreviated somewhat, but each field has a cross-reference back to its full table if you need more explanation. Refer to this field relationship table as you follow the examples listed below.

For example, there is a clear relationship between the TIME (call start time) and STIM (call stop time) fields, along with the CDUR (call duration) field. If STIM minus TIME is not equal to CDUR, this suggests either a problem or other user actions on the server. FMBX and TNUM are related when using a tree or chain mailbox; FMBX is the one dialed into, and TNUM is the mailbox transferred to.

The examples in this section show how you can use CDR for your billing application. Refer to each call type and the possible field values for successful and failed calls. Your application should examine these fields when creating bills for your customers.

Useful fields for processing call types are shown in the table below. Other recommended fields are listed within each call type’s section.

CDR Record Field Relationships

CDR Field 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26

CDR Field Abbreviation

(Table 2-1)

C S N DAT E T I ME S T I M PORT S Y I D CDUR FMB X TMB X FNUM TNUM M S G C T A T T T M E P E M S M P M D M K T A E C F S F P P S
Value Call Type(Field 13) Access Type(Field 14) Termination Type(Field 15) Error Code(Field 23)
01 Local message delivery Outside caller Call completed Call successfully completed
02 Outgoing NP WakeUp call Mailbox user Caller/user hung up Excess entry attempts
03 Telephone call placement Mobile DID user Call failed Excess passcode attempts
04 This call type no longer used Outside caller to template mbox Disconnected by the server Timeout on waiting for input
05 Paging call This access type no longer used Transferred to an extension Excess bad access code entries
06 This call type no longer used NP View session over TCP/IP Transferred to attendant Destination was busy
07 Outgoing NP Net call Outside caller to AutoAttendant Caller/user transferred to E-mail Destination did not answer
08 Cut-through paging call Message delivery, non-billed Message delayed by recipient Network node does not exist
09 This call type no longer used Accessed Admin-by-Phone Tree/chain mbox xfer to mailbox Mailbox does not exist
10 Incoming NP Net call This access type no longer used Caller/user recycled Invalid telephone number
11 Mailbox Purge NP Net receipt update   Invalid extension number
12 Incoming direct call Name broadcast   Message rejected by destination
13 Incoming direct call-no passcode Greeting broadcast   Mailbox in use when user called
14 Incoming call-forwarded Passcode broadcast   Could not transfer to extension
15 Incoming busy-forwarded Message delivery, billed   Could not transfer to attendant
16 Incoming no answer-forwarded This access type no longer used   Could not transfer to E-mail
17 Incoming indirect This access type no longer used   Access (to mailbox) denied
18 Outgoing NP Net call setup This access type no longer used   This error code no longer used
19 Incoming NP Net call setup This access type no longer used   This error code no longer used
20 This call type no longer used This access type no longer used   Time limit reached
21 This call type no longer used This access type no longer used   Message is bad or does not exist
22 Outgoing NP Net disconnect This access type no longer used   Destination mailbox is full
23 Incoming NP Net disconnect     This error code no longer used
24 This call type no longer used      
25 This call type no longer used      
26 This call type no longer used      
27 NuPoint Voice resource access      
28 NP View network access      
40   NP OnDemand    

Abbreviations: xfer=transfer mbox = mailbox VM=NuPoint Voice

Useful Fields for Processing All Call Types
CDR Field Field # CDR Field Description
CSN 1 Call sequence number
DATE 2 Call start date
TIME 3 Call start time
STIM 4 Call stop time
PORT 5 Port number (module and line)
CDUR 7 Call duration
CT 13 Call type
AT 14 Access type
TT 15 Termination type
EC 23 Error code

Each call type has a table of values for successful completion or failure to complete the call. In most cases, the access type, termination type, and error code always contain the same values, regardless of the call type. These values are listed here:

Standard Field Values for Most Call Types
CDR Field, # Success Failure
AT (14) 08 (delivery) 08 (delivery)
TT (15) 01 (success) 03 (failure)
EC (23) 01 (no error) varies

If a call type generates different values than listed in this table, these values are shown in bold type. Error code values for call failure vary with the call type, so check each call type’s table for a list of expected error code values.

Example of CDR Results

Here is a sample call.

An outside caller reached chain/tree mailbox 2000, then logged into mailbox 2001, made a message, logged out of mailbox 2001, then pressed a key to recycle to another NuPoint Voice session. The resulting CDR output is shown here:

275284 071892 025236 025422 0401 0000 0106 00000000000 00000002000 00000000000 00000002001 0000000 17 02 09 00 00 00 00 00 00 00 01 00 00 00

275285 071892 025423 025830 0401 0000 0247 00000002000 00000002001 00000000000 00000000000 0622073 17 02 10 00 00 01 00 00 00 00 01 00 00 00

The bold type shows Call Type 17 (Incoming), with Access Type 02 (Mailbox User), Termination Types 09 (Tree/chain mailbox transfer) and 10 (Recycle).

In addition, the first record shows no FMBX (outside caller), a TMBX of 2000 and a TNUM of 2001. The second record shows a FMBX of 2000 and a TMBX of 2001, indicating that the caller accessed 2001 through a chain or tree (2000).