SMDR Fields

Last Updated : Aug 30, 2026 |
Prolog information
The format used for the SMDR record output is:
  • Each SMDR record contains call information in a comma-separated format (CSV), that is a byte stream of variable width fields delimited by commas (0x2C).
  • Each record is terminated by carriage-return (0x0D), newline (0x0A) sequence. There is no quoting or escaping currently defined as fields do not include ',' or 'newline' characters.
Each SMDR record can contain the following fields.
  • Note that time values are rounded up to the nearest second.
  • Empty fields are shown if the field is not applicable to the call.
No.
Field
Description
1.
Call Start Time
The call start time in the format YYYY/MM/DD HH:MM:SS. This is based on the system time including any DST offset.
  • All records relating to the same call, that is having the same Call ID, have the same Call Start Time.
  • If the system has Call Splitting for Diverts enabled, the Call Start Time is changed to the time the forward occurred for all records following that stage of the call. However, the records for the externally forwarded call retain the original Call ID.
2.
Connected Time
Duration of the connected part of the call in HH:MM:SS format. This does not include ringing, held and parked time. A lost or failed call will have a duration of 00:00:00. The total duration of a record is calculated as Connected Time + Ring Time + Hold Time + Park Time.
3.
Ring Time
Duration of the ring part of the call in seconds.
  • For inbound calls, this represents the interval between the call arriving at the switch and it being answered. It does not match the time a call rang at an individual extension.
  • For outbound calls, this indicates the interval between the call being initiated and being answered at the remote end if supported by the trunk type. Analog trunks are not able to detect remote answer and therefore cannot provide a ring duration for outbound calls.
4.
Caller
The caller’s number. If the call originated at an extension, this is the extension number. If the call originated externally, this is the CLI of the caller if available, otherwise blank. For SIP trunks, the field can contain the number plus IP address. For example, 12345@192.0.2.123.
5.
Direction
The direction of the call ; I for inbound, O for outbound. This value can be used in conjunction with the Is Internal value below to determine the call type.
6.
Called Number
This is the number called by the system. For a call that is transferred, this field shows the original called number, not the number of the party who transferred the call.
  • Internal calls – The extension, group or short code called
  • Inbound calls – The target extension number for the call
  • Outbound calls – The dialed digits
  • Voice Mail – Calls to a user's own voicemail mailbox
7.
Dialed Number
For internal calls and outbound calls, this is identical to the Called Number above. For inbound calls, this is the DDI of the incoming caller.
8.
Account Code
The last account code attached to the call.
9.
Is Internal
This field indicates whether both parties on the call are internal (1) or not (0). Note that calls to destinations on other switches in a network are treated as internal. This value can be used in conjunction with the Direction value above to determine the call type as follows:
Direction
Is Internal
Call Type
I
0
Incoming external call.
O
1
Internal call.
O
0
Outgoing external call.
10.
Call ID
This is a numerical identifier, which is incremented for each unique call. If the call has generates several SMDR records, each record has the same Call ID. Note that the Call ID is restarted from 1,000,000 following any system restart.
11.
Continuation
This value indicates if the call has any further records with the same Call ID. It is 1 if there is a further record, otherwise 0.
12.
Party1 Device
The device 1 number. This is usually the call initiator though in some scenarios, such as conferences, this may vary. If an extension/hunt group is involved in the call, its details have priority over any trunk. That includes remote network destinations.
Type
Party Device
Party Name
Internal Number
E<extension number>
<name>
Voicemail
V<9500 + channel number>
VM Channel <channel number>
Conference
V<1><conference number>+<channel number>
CO Channel <conference number.channel number>
Line
T<9000+line number>
Line <line number>.<channel if applicable>
Other
V<8000+device number>
U<device class> <device number>.<device channel>
Unknown/Tone
V8000
U1 0.0
13.
Party1 Name
The name of the device. For an extension or agent, this is the user name encoded in UTF-8.
14.
Party2 Device
The other party for the call segment. Encoded as per Party1 Device above. For barred calls, this field shows Barred.
15.
Party2 Name
The other parties name. See Party1 Name above. For barred calls, this field shows Barred.
16.
Hold Time
The number of seconds the call has been held during this call segment.
17.
Park Time
The number of seconds the call has been parked during this call segment.
18.
Authorization Valid
This field is used for authorization codes. This field shows 1 for valid authorization or 0 for invalid authorization. This is Blank, no code is used.
19.
Authorization Code
For security, this field shows n/a regardless of the authorization code used. This is blank, no code is used.
20.
User Charged
This and fields 21 to 27 are used for ISDN Advice of Charge (AoC). If blank, AoC is not being used. This field indicates the user to which the call charge has been assigned. This is not necessarily the user involved in the call.
21.
Call Charge
The total call charge calculated using the line cost per unit and user markup.
22.
Currency
The currency. This is a system wide setting set in the system configuration.
23.
Amount at Last User Change
The current AoC amount at user change.
24.
Call Units
The total call units.
25.
Units at Last User Change
The current AoC units at user change.
26.
Cost per Unit
This value is set in the system configuration against each line on which AoC signalling is set. The values are 1/10,000th of a currency unit. For example, if the call cost per unit is £1.07, a value of 10700 should be set on the line.
27.
Mark Up
Indicates the mark up value set in the system configuration for the user to which the call is being charged. The field is in units of 1/100th, for example an entry of 100 is a markup factor of 1 .
28.
External Targeting Cause
This field indicates who or what caused the external call and a reason code. For example U FU indicates that the external call was caused by the Forward Unconditional settings of a User.
Targeted by
Reason Code
HG
Hunt Group.
fb
Forward on Busy.
U
User.
fu
Forward unconditional.
LINE
Line.
fnr
Forward on No Response.
AA
Auto Attendant.
fdnd
Forward on DND.
ICR
Incoming Call Route.
CfP
Conference proposal (consultation) call.
RAS
Remote Access Service.
Cfd
Conferenced.
?
Other.
MT
Mobile Twinning.
TW
Teleworker.
XfP
Transfer proposal (consultation) call.
Xfd
Transferred call.
29.
External Targeter ID
The associated name of the targeter indicated in the External Targeting Cause field.
  • For hunt groups and users, this is their name in the system configuration.
  • For an incoming call route, this is the route’s Tag value if set, otherwise ICR.
30.
External Targeted Number
This field is used for forwarded, Incoming Call Route targeted and mobile twin calls to an external line. It shows the external number called by the system as a result of the off-switch targeting whereas other called fields give the original number dialled.
31.
Calling Party Server IP Address
This IP address identifies the server where the calling extension is logged in.
32.
Unique Call ID for the Caller Extension
Numerical value that is a unique identifier of the call on the server where the call was initiated.
33.
Called Party Server IP Address
This IP address identifies the server where the called extension is logged in. If the field does not contain an IP address, then the call is to a trunk outside the IP Office network.
34.
Unique Call ID for the Called Extension
Numerical value that is a unique identifier of the call on the server where the called extension is logged in.
35.
SMDR Record Time
The system date and time, not including any DST offset, at which the SMDR record was generated. It uses the format YYYY/MM/DD HH:MM:SS.
36.
Caller Consent Directive
This field is used for calls going through an auto-attendant service that is configured to ask for caller consent to some choice.
  • 0 = Consent Not Requested
  • 2 = Consent Given
  • 6 = Consent Denied
37.
Calling Number Verification
Show the authentication level provided by the ISP on SIP lines configured to use calling number verification. Shows A, B, C or N/A is not authentication level information provided. A record is still shown for calls which the system rejects due to failed authentication. For more details, see SIP Calling Number Verification (STIR/SHAKEN).