User's Manual

Avaya Branch Gateway Manager 10.0 Page 857
15-601011 Issue 29r (Friday, November 02, 2012)B5800 Branch Gateway
Appendix: SMDR: SMDR Examples
Transferred Manually
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,203,O,9416,9416,,0,1000044,1,E203,Extn203,T9005,Line 5.1,0,0,,,,,,,,,,,U XfP,Extn207,,
… 16:33:09,00:00:02,2,207,O,203,203,,1,1000043,0,E207,Extn207,E203,Extn203,11,0,,,,,,,,,,,,,,
… 16:33:19,00:00:04,0,207,O,9416,9416,,0,1000044,0,E207,Extn207,T9005,Line 5.1,0,0,,,Extn207,,,,,,,,U Xfd,Extn203,,
Mobile Twinned Call Answered Internally
For this example user 203 has mobile twining enabled to the external number 9416 as twin. Their mobile dial delay is set
to 2 seconds. The call is answered at the user's internal extension.
In this scenario the record for the external call part of twinning is output immediately the call is answered internally. The
Call Start for this record differs dues to the user's Mobile Dial Delay setting. The External Targeting Cause indicates the
external call was the result of user (U) mobile twinning (MT) settings. If the call had been answered before the mobile
dial delay expired, no external call and therefore no record would be produced. When the call is completed the second
record is output.
… 16:17:59,00:00:00,7,,O,9416,9416,,0,1000028,0,E203,Extn203,T9005,Line 5.1,0,0,,,,,,,,,,,U MT,Extn203,9416,
… 16:17:58,00:00:07,9,207,O,203,203,,1,1000027,0,E207,Extn207,E203,Extn203,0,0,,,,,,,,,,,,,,