The following are examples of IP Office SMDR records for common call scenarios.
Lost incoming Call
In this record, the Call duration is zero and the Continuation field is 0, indicating that the call was never connected. The Ring Time shows that it rang for 9 seconds before ending.
2008/06/28 09:28:41,00:00:00,9,8004206,I,4324,4324,,0,1000014155,0,E4324,Joe Bloggs,T9161,LINE 5.1,0,0
Call Answered by Voicemail
In this example, 15 has made a call to 11. However the Party2Device and Party2Name show that the call was answered by voicemail.
2008/10/20 06:43:58,00:00:10,21,15,O,11,11,,I,28,0,E15,Extn15,V9051,VM Channel 1,0,0
Call Transferred to Voicemail
In this example, the Continuation field in the first record tells us that it wasn't the end of the call. The matching Call ID identifies the second record as part of the same call. The change in Party 1 details between the two records show that the call was transferred to voicemail.
2008/06/28 09:30:57,00:00:13,7,01707392200,I,299999,299999,,0,1000014160,1,E4750,John Smith,T9002,LINE 1.2,11,0
2008/06/28 09:30:57,00:00:21,0,01707392200,I,299999,299999,,0,1000014160,0,V9502,VM Channel 2,T9002,LINE 1.2,0,0
The Is Internal field being 0 shows this to be a external call. The Direction field as I shows that it was an incoming call. The Ring Time was 7 seconds and the total Connected Time was 5 seconds.
2008/08/01 15:14:19,00:00:05,7,01707299900,I,23,390664,,0,1000013,0,E23,Extn23,T9001,Line 1.2,0,0,,,,,,,,,,,,,,
The Is Internal field being 1 shows this to be a internal call. The Ring Time was 4 seconds and the total Connected Time was 44 seconds.
2008/06/26 10:27:44,00:00:44,4,4688,O,4207,4207,,1,1000013898,0,E4688,Joe Bloggs,E4207,John Smith,0,0
The combination of the Direction field being outbound and the Is Internal field be 0 show that this was a outgoing external call. The line (and in this case channel) used are indicated by the Party2 Name and being a digital channel the Ring Time before the call was answered is also shown.
2008/06/28 08:55:02,00:08:51,9,4797,O,08000123456,08000123456,,0,1000014129,0,E4797,Joe Bloggs,T9001,LINE 1.1,0,0
The two records below show calls to voicemail. The first shows the Dialed Number as*17, the default short code for voicemail access. The second shows the Dialed Number as VoiceMail, indicating some other method such as the Message key on a phone was used to initiate the call.
2008/06/28 09:06:03,00:00:19,0,4966,O,*17,*17,,1,1000014131,0,E4966,John Smith,V9501,VM Channel 1,0,0
2008/06/28 09:06:03,00:00:19,0,4966,O,VoiceMail,VoiceMail,,1,1000014134,0,E4966,John Smith,V9501,VM Channel 1,0,0
In this example the first record has a Park Time showing that the call was parked. The Continuation field indicates that the call did not end this way and there are further records. The second record has the same Call ID and shows a change in the Party2Name , indicating that party unparked the call. Note also that both records share the same call start time.
Incoming call with Account Code
In this example, at some stage as the call was made or during the call, an Account Code has been entered. In this specific case it is a text account code which can be selected and entered by the user using IP Office Phone Manager.
2008/06/28 11:29:12,00:00:02,2,5002,I,1924,1924,Support,0,1000014169,0,E1924,Extn1924,T9620,LINE 8.20,0,0
Conference Using Conference Button
In this example, an extension user answers a call and then brings in another user by using the Conference button on their phone. Again we see records for the initial call, the conference proposal call and then for the 3 parties in the conference that is created.
2008/07/09 15:05:41,00:00:08,0,,O,,,,1,1000009,0,E11,Extn11,V11001,CO Channel 100.1,0,0
2008/07/09 15:05:50,00:00:10,0,13,O,11,11,,1,1000010,0,E13,Extn13,V11002,CO Channel 100.2,0,0
2008/07/09 15:05:26,00:00:10,0,17,O,13,13,,1,1000008,0,E17,Extn17,V11003,CO Channel 100.3,0,0
Adding a Party to a Conference
This example is a variant on that above. Having started a conference, extension 13 adds another party.
2008/07/09 15:08:45,00:00:02,4,13,O,403,13,,0,1000016,1,E13,Extn13,E403,Libby Franks,0,0
2008/07/09 15:08:02,00:00:24,0,17,O,13,13,,1,1000013,0,E17,Extn17,V11003,CO Channel 100.3,0,0
2008/07/09 15:08:39,00:00:17,0,13,O,11,11,,1,1000015,0,E13,Extn13,V11002,CO Channel 100.2,8,0
2008/07/09 15:08:31,00:00:26,0,,O,,,,1,1000014,0,E11,Extn11,V11001,CO Channel 100.1,0,0
2008/07/09 15:08:45,00:00:12,0,,O,403,403,,0,1000016,0,E403,Libby Franks,V11004,CO Channel 100.4,0,0
In this example 2126 has called 2102. The record (1) for this has the Continuation set a 1 indicating that it has further records. In the following record (3) with the same Call ID it can be seen that the Party 2 Device and Party 2 Name fields have changed, indicating that the call is now connected to a different device, in this example 2121. We can infer the blind transfer from the intermediate record (2) which shows a call of zero Connected Time between the original call destination 2102 and the final destination 2121.
In this second example, extension 22 answers an external call and then transfers it to extension 23. Again the two legs of the external call have the same time/date stamp and same call ID.
2008/08/01 15:23:37,00:00:04,7,01707299900,I,4001,390664,,0,1000019,1,E22,Extn22,T9001,Line 1.1,6,0,,,,,,,,,,,,,,
2008/08/01 15:23:37,00:00:04,4,01707299900,I,4001,390664,,0,1000019,0,E23,Extn23,T9001,Line 1.1,0,0,,,,,,,,,,,,,,
Busy/Number Unavailable Tone
In this example 2122 calls 2123 who is set to DND without voicemail. This results in 2122 receiving busy tone.
The record shows a call with a Connected Time of 0. The Call Number field shows 2123 as the call target but the Party 2 Device and Party 2 Name fields show that the connection is to a virtual device.
2008/07/09 17:59,00:00:00,0,2122,O,2123,2123,,1,1000033,0,E2122,Extn2122,V8000,U1 0.0,0,0
The first record shows a call from 2122 to 2124 with a Connected Time of zero but a Ring Time of 8. The Continuation field indicates that the call has further records.
The second record has the same Call ID but the Party 2 Device and Party 2 Name details show that the call has been answered by 2121.
Park and Unpark
Parking and unparking of a call at the same extension is simply shown by the Park Time field of the eventual SMDR record. Similarly calls held and unheld at the same extension are shown by the Held Time field of the eventual SMDR record for the call. The records below however show a call parked at one extension and then unparked at another.
The records show a call from 17 to 13. 13 then parks the call shown by the Park Time. The call is unparked by 11, hence the first record is indicated as continued in its Continuation field. The matching Call ID indicates the subsequent record for the call.
Outgoing External Call
The External Targeting Cause indicates that the external call was caused by a user. The lack of specific reason implies that it was most likely dialed. The External Targeter ID is the user name in this example
… 16:23:06,00:00:04,5,13,O,9416,9416,,0,1000035,0,E13,Extn13,T9005,Line 5.1,0,0,,,Extn13,,,,,,,,U,Extn13,,
Rerouted External Call
In this example an incoming external call has been rerouted back off switch, shown by the Party 1 fields and the Party 2 fields being external line details. The External Targeter Cause shows that rerouting of the incoming call was done by an incoming call route (ICR). The External Targeter ID in this case is the Tag set on the incoming call route. The External Targeted Number is the actual external number call.
… 08:14:27,00:00:03,5,392200,I,9416,200,,0,1000073,0,T9005,Line 5.1,T9005,Line 5.2,0,0,,,,0000.00,,0000.00,0,0,618,0.01,
In this example the internal user transfers a call to an external number. The External Targeting Cause in the first record indicates that this external call is the result of a user (U) transfer proposal (XfP) call. The Continuation field indicates that another record with the same Call ID will be output.
The additional records are output after the transferred call is completed. The first relates to the initial call prior. The second is the transferred call with the External Targeting Cause now indicating user (U) transferred (Xfd).
… 16:33:19,00:00:05,3,13,O,9416,9416,,0,1000044,1,E13,Extn13,T9005,Line 5.1,0,0,,,,,,,,,,,U XfP,Extn17,,
… 16:33:19,00:00:04,0,17,O,9416,9416,,0,1000044,0,E17,Extn17,T9005,Line 5.1,0,0,,,Extn17,,,,,,,,U Xfd,Extn13,,
External Conference Party
This is similar to internal conferencing (see examples above) but the conference setup and progress records include External Targeting Cause codes for user (U) conference proposal (CfP) and user (U) conferenced (Cfd).
… 16:48:58,00:00:02,2,13,O,9416,9416,,0,1000066,1,E13,Extn13,T9005,Line 5.1,0,0,,,,,,,,,,,U CfP,Extn13,,
… 16:49:04,00:00:08,0,13,O,9416,9416,,1,1000067,0,E13,Extn13,V11002,CO Channel 100.2,0,0,,,,,,,,,,,,,,
… 16:48:37,00:00:13,0,,O,,,,1,1000064,0,E207,Extn17,V11003,CO Channel 100.3,0,0,,,,,,,,,,,,,,
… 16:48:58,00:00:13,0,,O,9416,9416,,0,1000066,0,V11001,CO Channel 100.1,T9005,Line 5.1,0,0,,,Extn13,,,,,,,,U Cfd,Extn13,
Two Outgoing External Calls Transferred Together
This scenario shows an outgoing call which is then transferred to another outgoing call.
2009/02/19 11:13:26,00:00:06,0,13,O,9403,9403,,0,1000012,1,E13,Extn13,T9001,Line 1.0,8,0,n/a,0,,,,,,,,,U,Extn13,,
2009/02/19 11:13:36,00:00:02,0,13,O,8404,8404,,0,1000013,0,E13,Extn13,T9002,Line 2.0,0,0,n/a,0,,,,,,,,,U XfP,Extn13,,
2009/02/19 11:13:26,00:00:11,0,8404,I,404,,,0,1000012,0,T9002,Line 2.0,T9001,Line 1.0,0,0,n/a,0,,,,,,,,,LINE Xfd,
0.1038.0 13 Alog Trunk:2,,