Reference7:Call Detail Record CDR PBX
Jump to navigation
Jump to search
There are also other versions of this article available:
Reference | Reference7 (this version) | Reference8 | Reference10
If enabled the PBX generates Call Detail Records (CDR) for each call and each object, which means if a call is made from one user to another a CDR for an outgoing call is generated at the first user object and a CDR for an incoming call is generated at the other user object. The CDRs are generated at the end of the call and sent via the CDR0 and CDR1 interfaces. XML is used for the content of the CDRs.
Version
This feature is availabe starting with version 7.00.
Content
Top-Level Tag <cdr>
Each CDR uses the top-level tag <cdr>. The following attributes are used with this tag:
guid | The GUID identifying the object this call belongs to. |
cn | The cn (Long Name) of the object |
e164 | The Number of the object |
h323 | The H.323 Id (Name) of the object |
dir | Indicates the direction of the call. For a call originating from this object this attribute is set to from. For calls sent to this object this attribute is set to to |
utc | The time when this call was started as UTC time. This is an integer with the standard ctime semantic. |
local | The local time the call was started. |
The Tag <event>
For each state a call goes thru a tag <event> is added to the CDR. The following attributes are used with this tag:
msg | A string identifying the message which caused the state change of the call |
time | The time in seconds from the beginning of the call |
e164 | The number of the other party of the call if available |
h323 | The H.323 Id (Name) of the other party of the call if available |
conf | A GUID identifying the call (conferenceID). This GUID can be used to associated CDRs from outgoing calls to the CDRs of incoming calls even across different PBXs. The first event within a CDR always contains this attribute. The conferenceID may change during a call (e.g. because of a call transfer). In this case another conf attribute is present containing the new conferenceID. |
Available messages (values of msg)
setup-from | A call originating from the object was initiated |
setup-to | A call to the object was initiated |
alert-from | The endpoint for this object is alerting |
alert-to | The other party is alerting |
conn-from | The endpoint for this object has connected the call |
conn-to | The other party has connected the call |
rel-from | The endpoint for this object has released the call |
rel-to | The other party has released the call |
transfer-from | The endpoint for this call has transfered the call. The call should be released shortly after this event. |
transfer-to | The other party has transfered the call. |
cf-from | The endpoint for this object has forwarded the call. The call should be released shortly after this event. |
cf-to | The other party has forwarded the call. |