IP SMDR

Overview

If licensed, the server is capable of providing an IP based real-time SMDR server function for external applications such as call logging/call accounting software and tracks inbound and outbound trunk based calls.

The feature can work in two different modes. Push mode where the Communication Service connects to an application running on a remote computer and sends the SMDR information and Local mode where the remote application connects to the Communication Service.

Configuration

To configure the IP SMDR feature:

Access the Communication Service -> IP SMDR section.
Check the General -> Enabled option to enable the IP SMDR.
Set the Local Port to the TCP port number that the Communication Service will accept connections on, the default is 2007.
This port will need to be opened on any firewall software running on the server.
Configure the Item padding character to use to pad out any blank entries in the SMDR record to ensure that all records are provided in a fixed length, the default character is "0".
To enable push mode check the Push connections -> Enabled option.
Both push and local modes can operate the same time.
Enter the Remote port and Remote IP address that the Communication Service will try to connect to the remote application on.
Click on Save.

SMDR Format

Each SMDR line received over IP will contain the following fixed length elements in the order below:

A line of data ends with carriage return and line feed characters. Each element is separated with a space, this means that each line will be 162 characters long

Event Types The following event types can be received on the IP SMDR connection.

RINGING - Received when a call alerts a device. This can happen when the call first starts ringing on the system or when a call is transferred to ringing or when a call is put on hold and then recalls.

ANSWERED - This event occurs when a call first enters the CONNECTED state on the system. This message is effectively the first "CONNECTED" events - Any further events of this type will be reported as CONNECTED.

HOLD - Occurs when a call is placed on hold on the telephone system. This event will be followed by a CONNECTED event when the call is retrieved.

CALLCONNECTED - Occurs when a call enters the CONNECTED state at a device. This can occur after a transfer or after a call is put on hold and the retrieved.

DIVERTED - Occurs when a call moves from one extension to another when following a forwarding path. In this event the Source Extension will be populated.

TRANSFERRED - Occurs when a call is transferred by a user to another destination. Depending on the method of transfer this event may be preceded by a HOLD event and will be followed by a RINGING and / or CONNECTED event. In this event the Source Extension will be populated.

QUEUED - Occurs when a call enters a QUEUING state at a device. This occurs when a call is waiting at a hunt group.

CALLMODIFIED - Occurs when any of the following details of the call have changed: - Account Code - Caller ID - Contact Name

DISCONNECTED - Occurs when a call clears down from the telephone system.

Example Messages

Inbound Call Scenario

Outbound Call Scenario

2012-03-09 12:46:59 |OUT| 2012030900465982190047 0092808 0001843 0000000 0000079XXXXXXXX | | 000000000000000 000000000000 |RINGING |

2012-03-09 12:47:06 |OUT| 2012030900465982190047 0092808 0001843 0000000 0000079XXXXXXXX | | 000000000000000 000000000000 |ANSWERED |

2012-03-09 12:47:10 |OUT| 2012030900465982190047 0092808 0001843 0000000 0000079XXXXXXXX | | 000000000000000 000000000000 |DISCONNECTED|

Inbound Call Scenario – Call Held Then Retrieved

2012-03-09 01:21:00 |IN | 2012030901205303270264 0092108 0001843 0000000 000007968543537 |CHRIS R MOBILE| 00044161XXXXXXX |CHRIS DID | 000000000000 |DISCONNECTED|

Inbound Call Scenario – Call Transferred