... aurenz GmbH UC-Analytics with Avaya IP Office to collect Call Detail Records (CDR) – Issue 1.0 Abstract These Application Notes describe the configuration steps necessary for provisioning aurenz GmbH's product UC-Analytics v13.0 to successfully interoperate with Avaya IP Office R11.1 to collect CDR/SMDR. Readers should pay attention to Section 2, in particular the scope of testing as outlined in Section 2.1 as well as the observations noted in Section 2.2, to ensure that their own use cases are adequately covered by this scope and results. Information in these ...
... SMDR Example: Conference Using Conference Add Short Code In this example, a user conferences 2 calls. This creates 5 SMDR records; 2 initial 2 – party calls and then 3 calls connected to a system's conference. First 2101 has made a call and 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 their held calls (record 3) . The records for the first two calls have the Continuation ...
... updated components: Delta Server v4.0.41 ServerU.Dll v4.0.40 2. Resolved issues The following issues were resolved in this release of CCC v4.0: • iPhone Manager does not display Busy NA and Busy Wrap states in CCV. • Dialed numbers greater then 10 digits, report incorrectly in SMDR. • Delta Server not showing 5 digit extension numbers in SMDR output of incoming ALOG calls. • SMDR displays incorrect details on a call to a busy extension. • Account codes are not being registered in the SMDR. • SMDR listing internal park/ride ...
... Abstract These Application Notes describe the configuration steps required for FCS Gateway 2.0 to interoperate with Avaya IP Office Release 11.1. FCS Gateway provides PMS integration, call billing, and 3rd party interfacing solution. In the compliance testing, FCS Gateway used Station Message Detail Reporting (SMDR) , and Management API interfaces from Avaya IP Office Server to provide room status, call billing, as well as name and user profile template change, outgoing call barring and do not disturb features. Readers should pay attention to Section 2, in particular the ...
... -tasking, seamless interface between the hotel exchange and the hotel front office system. It comprises two main components, FCS Voice and FCS Gateway, which includes call billing and interface solution. In the compliance testing, FCS WinExpress used SIP Users, Short Codes, SMDR, and Configuration Web Service interfaces from Avaya IP Office Server Edition to provide voicemail, wake-up call, room status, mini- bar posting, call billing, as well as name and user profile template change, and Do Not Disturb features. Readers ...
31. Checking SMDR Generation [HTML]
... Checking SMDR Generation Having enabled SMDR output, the generation of records can be view by enabling the Call trace option Call Logging in System Monitor. Note that this causes any records displayed to be removed from the buffer. ...
32. global_techtip_209.pdf [PDF]
... IP Office Technical Tip Tip No: 209 Release Date: 29 August 2008 Region: GLOBAL IP Office 4.2 Direct SMDR Output This Technical Tip is to advise customers about a potential issue with the direct output of SMDR records introduced in IP Office 4.2 software. In some call scenarios there is a possibility that the correct end of line characters may not be sent at the end of an SMDR record, therefore posing a potential issue for any software application that is collecting the data. If the correct end of line character is not ...
33. Computer Telephony Integration [HTML]
... interface, defined by Microsoft in TAPI 3.0. This functionality will only work in conjunction with CTI Link Pro and also requires TAPI-WAV licenses. Each license enables 4 ports of voice processing. DevLink Pro Provides a real-time event stream in addition to the SMDR interface provided in IP Office SMDR. The real-time event stream takes the form of a call record, which is issued whenever the state of any endpoint of a call changes (typically there are two end points on a call, but for some circumstances ...
34. SMDR Example: Lost Incoming Call [HTML]
... SMDR Example: Lost Incoming Call In this record, the Connected Time 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. 2014/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,. ...
35. SMDR Example: Internal Call [HTML]
... SMDR Example: Internal Call The Is Internal field being 1 indicates that this is an internal call. The Ring Time was 4 seconds and the Connected Time was 44 seconds. 2014/06/26 10:27:44, 00:00:44 , 4 ,4688,O,4207,4207, 1 ,1000013898,0,E4688,Joe Bloggs,E4207,John Smith,0,0,. ...
36. SMDR Example: Parked Call [HTML]
... SMDR Example: Parked Call In this example the first record has a Park Time showing that the call was parked for 7 seconds. The Continuation field indicates that the call did not end yet and there are further records. The second record has the same Call ID and shows a change in the Party2Name, indicating that another party unparked the call. Note also that both records share the same call start time. 2014/10/20 07:18:31 ,00:00:12,3,215,O,210,210, 1, 1000038 , 1 ,E215,Extn215 ...
37. SMDR Example: Outgoing Call [HTML]
... SMDR Example: Outgoing Call The combination of the Direction field being outbound and the Is Internal field being 0 show that this was a outgoing external call. The line or channel used is indicated by the Party2 Name and being a digital channel the Ring Time before the call was answered is also shown. 2014/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,. ...
38. SMDR Example: Outgoing External Call [HTML]
... SMDR Example: 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 2014/08/01 16:23:06,00:00:04,5,203,O,9416,9416, 0,1000035,0,E203,Extn203,T9005,Lin 5.1,0,0,,Extn203,,,, U , Extn203 ,. ...
... SMDR Example: Mobile Twinned Call Answered Internally For this example, user 203 has mobile twining enabled to the external number 9416 as their 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 Time for this record differs due to the user's Mobile Dial Delay setting. The External Targeting Cause indicates the external call was the result of user ( ...
... SMDR Example: Mobile Twinned Call Picked Up Using the Twinning Button This is the same scenario as the example above, however after answering the call on the external twinned device, the user has picked it up internally by using a twinning button. The first two records are for the answered external call and are output when that call is picked up by the internal extension. The third record is output when the call is ended internally. 2014/08/01 16:19:18,00:00:05,11,207,O,203,203, 1, 1000029 ...
41. SMDR Example: Internal Twinning [HTML]
... SMDR Example: Internal Twinning The records for scenarios such as internal call forwarding or follow me indicate the rerouting in a single record by having Caller and Called Number details that differ from the final Party 1 and Party 2 details. Internal twinning differs is showing a call answered at the twin exactly the same as having been answered at the primary. 203 is internally twinned to 201. Call from 207 to 203 but answer at 201. 2014/07/09 16:25:26,00:00:03,7,207,O,203,203, 1,1000037,0,E207,Extn207,E203,Extn 03,0,0,. ...
42. SMDR Example: Rerouted External Call [HTML]
... SMDR Example: 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. 2014/08/01 08:14:27,00:00 ...
43. SMDR Example: External Conference Party [HTML]
... SMDR Example: 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) . 2014/08/01 16:48:58,00:00:02,2,203,O,9416,9416, 0,1000066,1,E203,Extn203,T9005,Lin 5.1,0,0,,,, U CfP ,Extn203,. 2014/08/01 16:48:37,00:00:04,3,203,O,207,207, 1,1000064,1,E203,Extn203,E207,Extn 07,7,0,. 2014/08/01 16:49:04,00:00:08,0,203,O,9416,9416, ...
44. SMDR Example: Voicemail Supervised Transfer [HTML]
... SMDR Example: Voicemail Supervised Transfer A call is routed to a voicemail module that performs a supervised transfer. 2014/08/01 16:36:04,00:00:09,0,01707299900,I,xfer,390664, 0,1000061,1,T9001,Line 1.1,V9508,VM Channel 8,0,0,. 2014/08/01 16:36:07,00:00:03,4, I,402,402, 0,1000062,0,E402,Extn402,V8000,U12 0.8,0,0,. 2014/08/01 16:36:04,00:00:09,0,01707299900,I,402,390664, 0,1000061,0,E402,Extn402,T9001,Lin 1.1,0,0,. ...
... SMDR Example: 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,203,O,9403,9403, 0, 1000012 , 1 ,E203,Extn203,T9001,Line 1.0,8,0,0,n/a,,, U,Extn203,. 2009/02/19 11:13:36,00:00:02,0,203,O,8404,8404, 0,1000013,0,E203,Extn203,T9002,Lin 2.0,0,0,0,n/a,,,, U XfP ,Extn203,. 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,0,n/a,,,, LINE Xfd ,0.1038.0 13 Alog Trunk: ...
46. SMDR Record Buffering [HTML]
... SMDR Record Buffering The system generates a record at the end of a call or each call leg. It attempts to send the record at the time it is generated. However, if not possible, it buffers records up to the limit set for the system. By default that is 500 records. Whilst buffering, it still attempts to send a record when that new record is generated. If successful, it will also send any buffered records. If the buffer limit is reached, the system deletes the oldest record each ...
47. SMDR Example: External Call [HTML]
... SMDR Example: External Call The Is Internal field being 0 indicates that this is an external call. The Direction field being I shows that it was an incoming call. The Ring Time was 7 seconds and the total Connected Time was 5 seconds. 2014/08/01 15:14:19, 00:00:05 , 7 ,01707299900, I ,403,390664, 0 ,1000013,0,E403,Extn403,T9001,Line 1.2,0,0,. ...
... SMDR Example: Mobile Twinned Call Answered at the Mobile Twin This is the same scenario as the example above except that the call is answered at the external mobile twinning destination. Unlike the previous example, the external call record has a non-zero Connected Time, showing that the call was also answered externally. 2014/08/01 16:17:04 , 00:00:06 , 9,O,9416,9416, 0,1000026,0,E203,Extn203,T9005,Lin 5.1,0,0,,,, U MT , Extn203 , 9416 ,. 2014/08/01 16:17:02 ...
49. SMDR Example: Busy/Number Unavailable Tone [HTML]
... SMDR Example: 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 that is generating the audio tone. 2014/07/09 17:59,00:00:00,0,2122,O,2123,2123, 1,1000033,0,E2122,Extn2122, V8000 , U1 0.0 ,0,0,. ...
50. SMDR Example: Adding a Party to a Conference [HTML]
... SMDR Example: Adding a Party to a Conference This example is a variant on that above. Having started a conference, extension 203 adds another party. 2014/07/09 15:08:31,00:00:03,3,203,O,201,201, 1,1000014,1,E203,Extn203,E201,Extn 01,0,0,. 2014/07/09 15:08:02,00:00:22,6,207,O,203,203, 1,1000013,1,E207,Extn207,E203,Extn 03,9,0,. 2014/07/09 15:08:45,00:00:02,4,203,O,403,403, 0,1000016,1,E203,Extn203,E403,Libb Franks,0,0,. 2014/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,. 2014/07/09 ...
