User's Manual
Avaya Branch Gateway Manager 10.0 Page 855
15-601011 Issue 29r (Friday, November 02, 2012)B5800 Branch Gateway
Appendix: SMDR: SMDR Examples
Conference Using Conference Add Short Code
In this example 2101 has made a call and put put it on hold (record 2), then made another call and put it on hold (record
1) and then dialled the default short code *47 to conference all their held calls (record 3). The records for the first two
calls have the Continuation field set as 1 indicating that the calls continued in further records.
Record 3 shows 2101 making a new call in which they dial *47, which places them and their held calls into a conference.
This is shown by the Party Device and Party Name details as being a conference (100) and the conference channel used
for each.
For both the Continuation fields show that the calls do not end but rather have subsequent records.
2008/07/09 17:55,00:00:03,3,2101,O,8262623#,8262623#,,0,1000024,1,E2101,Extn2101,T9002,Line 2.1,8,0,,,,,,,,,,,,,
2008/07/09 17:54,00:00:29,7,2101,O,2121,2121,,1,1000023,1,E2101,Extn2101,E2121,Extn2121,23,0,,,,,,,,,,,,,
2008/07/09 17:55,00:00:46,0,2101,O,*47,*47,,1,1000026,0,E2101,Extn2101,V11001,CO Channel 100.1,0,0,,,,,,,,,,,,,
2008/07/09 17:54,00:00:49,0,,O,71234567890,71234567890,,1,1000023,0,E2121,Extn2121,V11003,CO Channel 100.3,0,0,,,,,,,,,,,,,
2008/07/09 17:55,00:00:49,0,,O,8262623#,8262623#,,0,1000024,0,V11002,CO Channel 100.2,T9002,Line 2.1,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:04,3,203,O,201,201,,1,1000009,1,E203,Extn203,E201,Extn201,0,0,,,,,,,,,,,,,
2008/07/09 15:05:26,00:00:09,3,207,O,203,203,,1,1000008,1,E207,Extn207,E203,Extn203,10,0,,,,,,,,,,,,,
2008/07/09 15:05:41,00:00:08,0,,O,,,,1,1000009,0,E201,Extn201,V11001,CO Channel 100.1,0,0,,,,,,,,,,,,,
2008/07/09 15:05:50,00:00:10,0,203,O,201,201,,1,1000010,0,E203,Extn203,V11002,CO Channel 100.2,0,0,,,,,,,,,,,,,
2008/07/09 15:05:26,00:00:10,0,207,O,203,203,,1,1000008,0,E207,Extn207,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 203 adds another party.
2008/07/09 15:08:31,00:00:03,3,203,O,201,201,,1,1000014,1,E203,Extn203,E201,Extn201,0,0,,,,,,,,,,,,,
2008/07/09 15:08:02,00:00:22,6,207,O,203,203,,1,1000013,1,E207,Extn207,E203,Extn203,9,0,,,,,,,,,,,,,
2008/07/09 15:08:45,00:00:02,4,203,O,403,403,,0,1000016,1,E203,Extn203,E403,Libby Franks,0,0,,,,,,,,,,,,,
2008/07/09 15:08:02,00:00:24,0,207,O,203,203,,1,1000013,0,E207,Extn207,V11003,CO Channel 100.3,0,0,,,,,,,,,,,,,
2008/07/09 15:08:39,00:00:17,0,203,O,201,201,,1,1000015,0,E203,Extn203,V11002,CO Channel 100.2,8,0,,,,,,,,,,,,,
2008/07/09 15:08:31,00:00:26,0,,O,,,,1,1000014,0,E201,Extn201,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,,,,,,,,,,,,,
Transfer
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.
2008/07/09 17:51,00:00:38,18,2126,O,2102,2102,,1,1000019,1,E2126,Extn2126,E2102,Extn2102,19,0,,,,,,,,,,,,,
2008/07/09 17:52,00:00:00,7,2102,O,2121,2121,,1,1000020,0,E2102,Extn2102,E2121,Extn2121,0,0,,,,,,,,,,,,,
2008/07/09 17:51,00:00:39,16,2126,O,2102,2102,,1,1000019,0,E2126,Extn2126,E2121,Extn2121,0,0,,,,,,,,,,,,,
In this second example extension 402 answers an external call and then transfers it to extension 403. 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,E402,Extn402,T9001,Line 1.1,6,0,,,,,,,,,,,,,,
2008/08/01 15:23:46,00:00:00,3,402,O,403,403,,1,1000020,0,E402,Extn402,E403,Extn403,0,0,,,,,,,,,,,,,,
2008/08/01 15:23:37,00:00:04,4,01707299900,I,4001,390664,,0,1000019,0,E403,Extn403,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 records 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,,,,,,,,,,,,,