26. IP Office Technical Bulletin 94: Compact Contact Center (CCC) v5.0.56 Q1 2008 Maintenance Release [PDF]
... Report description amended that it does not include unanswered transferred calls. CQ35357 Internet Explorer 7 issues trying to access CCC Reporter CQ34977 Using blind Transfer from the "Leave" call flow does not carry caller ID CQ34742 CCC Reporter drop down menus for Agent reports CQ34654 Delta Server SMDR no longer logs auth codes after switch restart, even though option enabled. CQ34513 RAS Ports viewed on CCV don't show as busy on a 406v2 CQ34185 CCV shows wrong agent status when 2 or more users enter DND using default *08 short code CQ33487 When the ...
27. SMDR Examples [HTML]
... SMDR Examples The following are examples of system SMDR records for common call scenarios. In the following examples, the underlined fields indicate key values in the interpretation of the scenario. .. is used to indicate that further fields have been omitted for clarity as they are not relevant to the example. ...
28. SMDR Fields [HTML]
... SMDR Fields The format used for the SMDR record output is: Each SMDR record contains call information in a comma-separated format (CSV) , that is a byte stream of variable width fields delimited by commas (0x2C) . Each record is terminated by carriage-return (0x0D) , newline (0x0A) sequence. There is no quoting or escaping currently defined as fields do not include' or newline' characters. Each SMDR record can contain the following fields. Note that time values are rounded up to the ...
29. SMDR Fields [HTML]
... SMDR Fields The format used for the SMDR record output is: Each SMDR record contains call information in a comma-separated format (CSV) , that is a byte stream of variable width fields delimited by commas (0x2C) . Each record is terminated by carriage-return (0x0D) , newline (0x0A) sequence. There is no quoting or escaping currently defined as fields do not include' or newline' characters. Each SMDR record can contain the following fields. Note that time values are rounded up to the ...
30. SMDR Examples [HTML]
... SMDR Examples The following are examples of system SMDR records for common call scenarios. In the following examples, the underlined fields indicate key values in the interpretation of the scenario. .. is used to indicate that further fields have been omitted for clarity as they are not relevant to the example. ...
31. 156: Authorization Codes [HTML]
... and Delta Server. To see Authorization Code settings in Manager, you need to set the following registry setting to 1: HKEY_CURRENT_USER\Software\Avaya\IP400\Manager\EnableAuthorizationCodes For call logging purposes, the authorization code field will not be displayed under the recent SMDR view, but they will be added to the following SMDR outputs: SMDR via COM port SMDR.csv file To enable authorization code logging in SMDR, two registry entries must be added: allowauthorization ShowAllowAuthorization These two values must exist in the registry table and set to one ...
... SMDR Example: Incoming Call with Account Code 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. During a call, another account code can be entered. The SMDR record shows the last account code used before the record was generated. 2014/06/28 11:29:12,00:00:02,2,5002,I,1924,1924, 123456789 ,0,1000014169,0,E1924,Extn1924,T96 0,LINE 8.20,0,0,. ...
33. 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. ...
... AlwinPro UC-Edition 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 AlwinPro UC-Edition 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: Incoming Call with Account Code 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. During a call, another account code can be entered. The SMDR record shows the last account code used before the record was generated. 2014/06/28 11:29:12,00:00:02,2,5002,I,1924,1924, 123456789 ,0,1000014169,0,E1924,Extn1924,T96 0,LINE 8.20,0,0,. ...
... 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 ...
... 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 ...
39. 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. ...
... 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 ...
43. 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 ...
44. Call Logging Applications [HTML]
... IP500 V2A IP Office Subscription: IP500 V2A Overview > IP Office Software Applications Call Logging Applications A wide range of 3rd -party applications exist to provide call logging and accounting for telephone systems. In addition, the IP Office provides an SMDR output. • SMDR Output The IP Office control unit can be configure to output SMDR records for each call to a specified IP address. ...
45. Call Logging Applications [HTML]
... IP500 V2A IP Office Essential Edition: IP500 V2A Overview > IP Office Software Applications Call Logging Applications A wide range of 3rd -party applications exist to provide call logging and accounting for telephone systems. In addition, the IP Office provides an SMDR output. • SMDR Output The IP Office control unit can be configure to output SMDR records for each call to a specified IP address. ...
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: 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: 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: ...
50. 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,. ...
