# Processing Each Call Type

Following are the relevant fields and expected values for you to use in processing each call type.

## Call Type 1 (Local Message Delivery)

Call Type 1 is used for transmitting messages to mailbox users from other users. See Call Types 12-17 for handling messages received from an outside caller.

CAUTION:

Call Type 1 creates numerous CDR records, which are the details of Call Types 8 though 17. In particular, enabling Call Type 1 creates a CDR record for every mailbox in a distribution list or broadcast mailbox. Unless you need the specifics of Call Type 1, do not enable it in the Configuration Menu.

Field Values for Call Type 1
CDR Field, # | Successful Delivery | Failed Delivery
--- | --- | ---
AT (14) | 08 (delivery) 14 (passcode broadcast) | 08 (delivery)
TT (15) | 01 (success) | 03 (failure)
EC (23) | 01 (no error) | 09(mailbox bad or does not exist) 12(destination mailbox can’t receive msg) 17(message denied: wrong FCOS) 21(cannot allocate msg for destination mbox) 22(mailbox is full)

Other useful fields:

FMBX (8) Mailbox originating the message TMBX (9) Destination mailbox to which the message is delivered to MSG (12) The server’s speech message number MS (18) Number of messages sent (usually 1)

## Call Type 2 (Outgoing Auto-Wakeup)

This is an outgoing call made by the server. You can determine whether the outgoing number involves long-distance charges in processing this call type.

Field Values for Call Type 2
CDR Field, # | Successful Delivery | Failed Delivery
--- | --- | ---
AT (14) | 08 (delivery) | 08 (delivery)
TT (15) | 01 (success) | 03 (failure)
EC (23) | 01 (no error) | 06(destination telephone was busy) 07(call was not answered) 10(bad destination telephone number)

Other useful fields:

TMBX (9) Mailbox number of the message originator TNUM (11) Destination telephone number dialed by server MS (18) Number of messages sent (usually 1)

## Call Type 3 (Telephone Call Placement)

Call Type 3 indicates a message sent to an outside telephone number. While this is similar to a Call Type 2, additional Termination Types are possible on call failure. There are also more possible resulting Error Codes.

Field Values for Call Type 3
CDR Field, # | Successful Delivery | Failed Delivery
--- | --- | ---
AT (14) | 08 (delivery) | 08 (delivery)
TT (15) | 01 (success) | 03 (failure) 04(disconnected) 08(delayed)
EC (23) | 01 (no error) | 03(excess invalid passcode attempts) 06(destination telephone was busy) 07(call was not answered) 09(originating mailbox is bad) 10(bad destination telephone number) 12(rejected by recipient) 21(message is bad or no longer exists)

Other useful fields:

TMBX (9) Mailbox number of the message originator TNUM (11) Destination telephone number dialed by the server MSG (12) The server’s speech message number

## Call Type 5 (Paging or Message Delivery)

Call Type 5 can be either a paging or a message delivery call. Both types involve the server calling a telephone number specified by the user. Any field not specified below as specifically paging or message delivery applies to any Call Type 5 record. In the Error Code field, the first three errors apply to paging and message delivery, and the last three errors only to message delivery.

The paging portion of Call Type 5 is similar to Call Type 2. Fields vary for the Message Delivery portion. Message delivery is also similar to Call Type 2, but since the called party has to log into a mailbox and enter a passcode, the resulting field values are different.

Field Values for Call Type 5
CDR Field, # | Successful Delivery | Failed Delivery
--- | --- | ---
AT (14) | 08 (delivery) Paging 02(user logged in, got msg) Message Delivery 15(user logged in, got msg, bill flag set) Message Delivery | 08 (delivery) Paging 01(call received by non-subscriber) Message Delivery
TT (15) | 01 (success) | 03 (failure) Paging 04(disconnected) Message Delivery
EC (23) | 01 (no error) | 06(destination telephone was busy) 07(call was not answered) 09(mailbox is bad or doesn’t exist) 10(bad destination telephone number) 03(excess invalid passcodes) Message Delivery 04(timeout or no response) Message Delivery

Other useful fields for both Paging and Message Delivery:

TMBX (9) Mailbox number of the message originator TNUM (11) Destination telephone number dialed by the server MSG (12) The server’s speech message number

These fields are only used in Message Delivery calls:

MP (19) Number of messages played or received

If a paging message is unsuccessful, any retry of the message creates an additional Type 5 record.

You can tell the difference between a Paging and a Message Delivery record by checking if any of the above four fields are greater than zero. Look for the Messages Played (MP) field, as the purpose of Message Delivery is to notify a user that there are unplayed messages in the mailbox.

## Call Type 7 (Outgoing NP Net)

Call Type 7 is similar to Call Type 2, except it involves networking. This call should be preceded by a header record of Call Type 18 or another Call Type 7. It should be followed by another Call Type 7 or a disconnect of Call Type 22. Verify that these calls occurred on the same line number by checking the PORT field.

Field Values for Call Type 7
CDR Field, # | Successful Delivery | Failed Delivery
--- | --- | ---
AT (14) | 08 (delivery) | 08 (delivery)
TT (15) | 01 (success) | 03 (failure)
EC (23) | 01 (no error) | 04(timeout occurred) 08(invalid destination node) 23(bad link)

Other useful fields:

FMBX (8) Mailbox number of the message originator TMBX (9) Destination mailbox number TNUM (11) Network node number of destination mailbox MSG (12) Message number of the message sent

## Call Type 8 (Cut-Through Paging)

Call Type 8 is similar to Call Type 5 (paging). You should examine the telephone number called to determine long-distance charges, if any.

Field Values for Call Type 8
CDR Field, # | Successful Delivery | Failed Delivery
--- | --- | ---
AT (14) | 08 (delivery) | 08 (delivery)
TT (15) | 01 (success) | 03 (failure)
EC (23) | 01 (no error) | 04(timeout or no response) 06(destination telephone was busy) 07(call was not answered) 10(bad destination telephone number)

Other useful fields:

TMBX (9) Mailbox number of the message originator. TNUM (11) Destination telephone number dialed by the server.

## Call Type 10 (Incoming NP Net)

Call Type 10 is similar to Call Type 1, except it involves networking. This call should be preceded by a header record of Call Type 19 or another Call Type 10. It should be followed by another Call Type 10 or a disconnect of Call Type 23. Verify that these calls occurred on the same line number by checking the PORT field.

Field Values for Call Type 10
CDR Field, # | Successful Delivery | Failed Delivery
--- | --- | ---
AT (14) | 08 (delivery) 11(receipt update) 12(name broadcast) 13(greet broadcast) 14(passcode broadcast) | 08 (delivery) 11(receipt update) 12(name broadcast) 13(greet broadcast) 14(passcode broadcast)
TT (15) | 01 (success) | 03 (failure)
EC (23) | 01 (no error) | 04(timeout occurred) 09(mailbox bad or no longer exists) 17(delivery of msg to destination mbox denied) 22(destination mbox was full)

Other useful fields:

FMBX (8) Mailbox number of the message originator TMBX (9) Destination mailbox number FNUM (10) Message originator’s network node number TNUM (11) Network node number of destination mailbox MSG (12) Received message’s number, created by the server

## Call Type 11 (Mailbox Delete on Purge)

Call Type 11 is not really a call type, but a status update. A CDR record with a Call Type 11 indicates that the mailbox associated with it (FMBX) was purged either because its messages were played or because its unplayed messages retention limit (in its LCOS) had expired. This is associated with the NP OnDemand optional feature, where mailboxes are only created as callers request them.

See "Call Types 12 Through 17" for additional information on how CDR handles the NP OnDemand feature. For more information on NP OnDemand, refer to its documentation.

Field Values for Call Type 11
CDR Field, # | Successful Delivery | Failed Delivery
--- | --- | ---
AT (14) | 08 (delivery) | 08 (delivery)
TT (15) | 01 (success) | 03 (failure)
EC (23) | 01 (no error) |

Other useful fields:

FMBX (8) Mailbox number deleted

## Call Types 12 Through 17 (Incoming)

Call Types 12 through 17 produce the same field results, so they are presented as one type in this section. Table 6-12 shows the distinction between these six Call Types.

Call Types 12 Through 17
Call Type | Definition
--- | ---
12 | Incoming directly to mailbox
13 | Incoming directly to mailbox with no passcode required
14 | Incoming hard-forwarded to mailbox
15 | Incoming busy-forwarded to mailbox
16 | Incoming forwarded to mailbox on Ring No Answer
17 | Incoming indirect (tree/chain, recycle to another mailbox)

Note: In most other call types, the standard result for the access type field (AT, 14) is 08 (delivery. This result should not occur with the Incoming call types.

These call types have a number of possible results for access type and termination type. Use the error code to determine call success or failure.

The field values for Call Types 12-17 are listed in Table 6-16. Other useful fields for Call Types 12 through 17 are:

FMBX (8) Mailbox number (if available) of mailbox accessed/entered TMBX (9) Mailbox number of mailbox accessed or destination mailbox TNUM (11) Mailbox/extension number transferred to after TMBX MSG (12) Message number of the last message recorded or accessed ME (16) Invalid mailbox entries PE (17) Invalid passcode entries MS (18) Number of messages sent MP (19) Number of messages played/received MD (20) Number of messages deleted MK (21) Number of messages kept TA (22) Number of failed transfer attempts P S (26) Number of cut-through pages initiated by the caller

Field Values for Call Types 12-17
CDR Field, # | Successful Delivery | Failed Delivery
--- | --- | ---
AT (14) | 01(outside caller) 02(mailbox user/subscriber) 03(mobile DID user) 04(template mailbox caller) 05 This value no longer used 07(outside caller to Receptionist ) 09(user accessed Admin-by-phone) 10 This value no longer used | 01(outside caller) 02(mailbox user/subscriber) 03(mobile DID user) 04(template mailbox caller) 05 This value no longer used 07(outside caller to Receptionist ) 09(user accessed Admin-by-phone) 10 This value no longer used
| 40(mailbox on demand) | 40(mailbox on demand)
TT (15) | 01 (success) 02(caller/user hang up) 04(NuPoint Voice disconnected call) 05(caller/user transfer to extension) 06(caller/user transfer to attendant) 07(caller/user transfer to E-mail) 08(transfer to another mailbox) | 02(caller/user hang up) 03 (failure) 04(Server disconnected call) 05(caller/user transfer to extension) 06(caller/user transfer to attendant) 07(caller/user transfer to E-mail) 08(transfer to another mailbox)
EC (23) | 01 (no error) | 02(too many bad mailbox entries) 03(too many bad passcode entries) 04(time out occurred) 05(too many bad access code entries) 13(mailbox in use when user called) 14(could not transfer to extension) 15(could not transfer to attendant) 16(could not transfer to E-mail) 17(access to mailbox was denied) 20(time limit reached) 22(destination mailbox was full)

NP OnDemand is an Optional Feature. When a mailbox is created, the access type is 40, with an error code of 0 showing successful creation. The first record for an NP OnDemand mailbox contains the first message sent. Subsequent messages to this mailbox have access types used for existing messages. When the mailbox is purged, the server creates a CDR record showing Access Type 40 and Call Type 11.

For more information on the feature, refer to the NP OnDemand documentation.

## Call Type 18 (Outgoing NP Net Setup)

Call Type 18 is similar to Call Type 2, except for the network node number. However, it is used as a header record, and should be followed by one or more Call Type 7 (Outgoing NP Net call) records, and finally a Call Type 22 (Outgoing NP Net disconnect). Your billing application should log all such records on the same line number, so check the PORT field.

Field Values for Call Type 18
CDR Field, # | Successful Call Setup | Failed Call Setup
--- | --- | ---
AT (14) | 08 (delivery) | 08 (delivery)
TT (15) | 01 (success) | 03 (failure)
EC (23) | 01 (no error) | 04(timeout occurred) 06(destination server was busy) 07(destination server did not answer) 08(invalid destination node) 23(could not establish network link with destination server)

Other useful fields:

TNUM (11) Network node number of destination mailbox

## Call Type 19 (Incoming NP Net setup)

Call Type 19 is similar to Call Type 1, except for the network node number. However, it is used as a header record, and should be followed by one or more Call Type 10 (Incoming NP Net call) records, and finally a Call Type 23 (Incoming NP Net disconnect).

Field Values for Call Type 19
CDR Field, # | Successful Call Setup | Failed Call Setup
--- | --- | ---
AT (14) | 08 (delivery) | 08 (delivery)
TT (15) | 01 (success) | 03 (failure)
EC (23) | 01 (no error) | 04(timeout occurred) 23(could not establish network link with remote server)

Other useful fields:

FNUM (10) Network node number of message originator (if available)

## Call Types 22, 23 (Outgoing/Incoming NP Net disconnect)

Call Types 22 and 23 always report a successful disconnect. The fields should yield the standard results. Call Type 22 should be preceded by a Call Type 18 (Outgoing NP Net call setup) record and one or more Call Type 7 (Outgoing NP Net call) records. Call Type 23 should be preceded by a Call Type 19 (Incoming NP Net call setup) record and one or more Call Type 10 (Incoming NP Net call) records. In tracking these call chains, verify that they all occurred on the same line number (PORT field).

Field Values for Call Types 22-23
CDR Field, # | Successful Disconnect
--- | ---
AT (14) | 08 (delivery)
TT (15) | 01 (success)
EC (23) | 01 (no error)

Other useful fields:

TNUM (11) Network node number of dest. mailbox (for outgoing calls) FNUM (10) Network node number of originator (for incoming calls)

## Call Types 24 Through 27 (E-Mail)

Call Types 24 through 27 are used with e-mail applications. CDR records for e-mail applications are generated by specific applications, with format specific to the application. Refer to the documentation for e-mail applications for more information. Additional call types are reserved to allow for future and custom e-mail applications. Contact your support representative for more information on using CDR with e-mail.

Field Values for Call Type 24-27
CDR Field, # | Success | Failure
--- | --- | ---
AT (14) | 05 This value no longer used 10 This value no longer used 16-22 These values no longer used | 00 (unknown error)
TT (15) | 07(Caller transferred to e-mail) | 03 (failure)
EC (23) | 01 (no error) | 16(E-mail access failed) 19 This value no longer used

Other useful fields:

TNUM (11) Network node number of dest. mailbox (for outgoing calls) FNUM (10) Network node number of originator (for incoming calls)

## Call Type 28 (NP View)

Call Type 28 shows a call made through the NP View application. Here are the possible values.

Field Values for Call Type 28
CDR Field, # | Success | Failure
--- | --- | ---
AT (14) | 06 (session over TCP/IP) |
TT (15) | 01 (success) | 04 (disconnect)
EC (23) | 00 (unknown error) |

Other useful fields:

TMBX (9) Destination mailbox FNUM (10) Network node number of originator (for incoming calls)

Note: The PORT field should contain the low-word of the IP address instead of a triplet.
Parent topic: Analyzing CDR Data