Search results for: SMDR in all categories

195 results .

8 pages.
... SMDR Example: Call Answered by Voicemail In this example, 215 has made a call to 211. However, the Party2Device and Party2Name fields show that the call was answered by voicemail. 2014/10/20 06:43:58,00:00:10,21,215,O,211,211, I,28,0,E215,Extn215, V9051 , VM Channel 1 ,0,0,. ...
URL: ../mergedProjects/manager/SMDR_Example_Call_Answered_by_Voicemail.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,. ...
URL: ../mergedProjects/manager/SMDR_Example_Internal_Call.html
... SMDR Example: 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. 2014/07/09 15:05:41,00:00:04,3,203,O,201,201, 1,1000009, 1 ,E203,Extn203,E201,Extn201,0,0,. 2014/07/09 15:05:26,00:00:09,3,207,O,203,203, 1,1000008, 1 ,E207,Extn207,E203,Extn203,10,0,. 2014/07/09 ...
URL: ../mergedProjects/manager/SMDR_Example_Conference_Using_a_Conf_Button.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,. ...
URL: ../mergedProjects/manager/SMDR_Example_External_Call.html
... SMDR Example: Distributed Hunt Group Call An incoming call to site A is targeted to a distributed hunt group member on site B. They transfer the call back to a hunt group member on site A. 2014/08/01 15:32:52,00:00:10,19,01707299900,I,4002,390664, 0,1000024,1,E209,Luther-209,T9001,Line 1.2,0,0,. 2014/08/01 15:33:19,00:00:00,2,209,I,403,403, 0,1000025,0,E209,Luther-209,E403,Extn403,0,0,. 2014/08/01 15:32:52,00:00:03,3,01707299900,I,4002,390664, 0,1000024,0,E403,Extn403,T9001,Lin 1.2,0,0,. ...
URL: ../mergedProjects/manager/SMDR_Example_Distributed_Hunt_Group_Call.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,. ...
URL: ../mergedProjects/manager/SMDR_Example_Busy_NU_Tone.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, ...
URL: ../mergedProjects/manager/SMDR_Example_External_Conference_Party.html
... SMDR Example: External Forward Unconditional In this example, user 203 has a forward unconditional number set for calls. This is indicated by the External Targeting Cause showing user and forward unconditional. The External Targeter ID shows the source of the call being forwarded, in this example user 207. The External Targeted Number shows the actual external number called by the system. 2014/08/01 16:22:41,00:00:02,5,207,O,203,203, 0,1000034,0,E207,Extn207,T9005,Lin 5.1,0,0,,Extn203,0000.00, 0000.00,0,0,618,1.00, U fu , Extn207 , 9416 ,. ...
URL: ../mergedProjects/manager/SMDR_Example_External_Forward_Unconditional.html
... SMDR Example: Call 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 ...
URL: ../mergedProjects/manager/SMDR_Example_Call_Transferred_Manually.html
... SMDR Example: Transfer In this example, 2126 has called 2102. The 1st record has the Continuation set a 1, indicating that it the call has further records. The 3rd record has the same Call ID but the Party 2 Device and Party 2 Name fields have changed, indicating that the call is now connected to a different device. We can infer the blind transfer from the 2nd record which shows a call of zero Connected Time between the original call destination 2102 and the final destination 2121. 2014/07/ ...
URL: ../mergedProjects/manager/SMDR_Example_Call_Transfer.html
... SMDR Example: Call Pickup 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. 2014/07/09 18:00, 00:00:00 , 8 ,2122,O,2124,2124, 1, 1000038 , 1 ,E2122,Extn2122,E2124,Extn2124,0,0 ,.. 2014/07/09 18: ...
URL: ../mergedProjects/manager/SMDR_Example_Call_Pickup.html
... IP Office Technical Tip No: 23 Issued: 2nd June 2003 SMDR logging tandem calls When making an external call that has been account coded, if the user places that first call on hold and makes a second outgoing call to an external number, the user will also need to account code the second call they make in order for the SMDR logger to log both calls correctly with account codes. The reason for this is that the SMDR call logging application is based upon the CCC Delta Server, when this kind of scenario ...
URL: ../mergedProjects/bulletins/techtips/emea/emea_techtip_023.pdf
... show as busy until connected. CQ27828 CCV Agents show "Ready" instead of BWU after 1st activity of the day if left in BWU overnight CQ28440 Historical Times in State do not match when users are logging in and out at same time. CQ28558 Not creating correct SMDR entries when transferring two outgoing external calls together. CQ26360 PC Wallboard does not update immediately when logged on in a certain scenario CQ23383 Archiver - Windows Authentication not working CQ25964 Agent Activity Trace report does not show full data set. CQ26021 Users with very similar names may ...
URL: ../mergedProjects/bulletins/techbulls/tb081.pdf
... integration • Reporting – Additional/Custom Reports • Reporting – Reporting package runs as a service on the CCC server PC • Reporting – Client connection to server is made through a web browser • Delta Server – Now runs as a single service with an integral Archiver and SMDR built in • Delta Server – Administered via a thin client through a web browser • CCV – Minimum Lost Call threshold for reporting • CCV – Agent log off at close • CCV – Selective Alarm messaging • CCV – New Refused Call alarm • CCV – Force ...
URL: ../mergedProjects/bulletins/techbulls/tb032.pdf
... shown in Incoming DDI Summary Report 17305 CCV - Individual Agent screen displays incorrect stats 20139 Delta server displays an Interaction result error "Call Result Not Found for Call Flow" 21065 PhoneManager Pro in Agent Mode - CCV displays Busy Wrap up when the Agent is ready 18196 SMDR: Internal Conference Calls Misreport times 19497 When using Callback Request via PC Wallboard, incorrect states are reported on CCV 19498 Agent calls reporting as Callback Requests when they are not Callback Requests 19541 Callback Request from Voicemail to CCV displays incorrect Original Target 19633 Account codes not ...
URL: ../mergedProjects/bulletins/techbulls/tb031.pdf
... VMPro routes the call 19497 When using Callback Request via PC Wallboard, incorrect states are reported 19498 Agent calls reporting as Callback Requests when not Callback Request's 19541 Callback Request from Voicemail to CCV displays incorrect Original Target 21070 Dialled numbers greater then 10 digits, report incorrectly in SMDR 19633 Account codes not shown in SMDR output 19890 Agent shows "Ringing" in CCV instead of "Incoming" after transfer from SoftConsole 20696 SMDR displays incorrect details on a call to a busy extension 20860 SMDR only logging 4 digits for 5-digit extensions 21000 ...
URL: ../mergedProjects/bulletins/techbulls/tb033.pdf
... and Australia/New-Zealand • Additional locales: Korea, Greece and Poland • Toggling features on DSS keys • Voicemail Pro 1.3 (1.2.12) • Compact Contact Centre 1.3 (3.0.33) • User CD 1.3 (1.3.10) including Phone Manager agent mode • New SMDR Call Logging application • DECT CTI integration • Windows XP Operating System Support. 2 Communication without boundaries 2. IP Office 1.3 Hardware 2.1 IP412 Office The IP412 provides a more powerful call processing engine and greater internal data transfer capabilities, and is ideally suited for the ...
URL: ../mergedProjects/bulletins/techbulls/tb008.pdf
68. Account Code [HTML]
... > Supervisor Settings) . They then need to enter an account code for any outgoing external calls. Incoming calls can also be associated with an account code by matching the Caller ID stored with the account code settings. That account code is then included in the call's SMDR call log. When an account code is entered during a call: The IP Office checks the code entered for a match against those account codes set in its configuration. For Forced Account Code calls, the call is not allowed until a valid code is entered ...
URL: ../mergedProjects/manager/Account_Code_Settings.html
... IP500 V2 IP Office Subscription: IP500 V2 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. ...
URL: ../mergedProjects/subscription/call_center_applications.htm
70. Call Records [HTML]
... Call Records The authentication level ( A , B or C ) provided by the ISP is included in the SMDR call logging records output by the system. If no authentication level is provided, N/A is shown instead. An SMDR call record is produced even for calls which are rejected by the system based on the calling number verification settings. ...
URL: ../mergedProjects/manager/SIP_STIR_SMDR.html
... misreporting call waiting CQ76454 Abandoned Calls are not able to reported on in CCC "ICLID" report using CCC 5.0.61 CQ76687 DID (DDI) Summary Report does not show calls lost when the call is targeted direct to the Agent CQ39902 Invalid Lost Call reflected in CCV CQ78881 SMDR called and dialed numbers are different - caused by simultaneous call to number that has ring time=0 . CQ79196 DDI calls direct to agents - Lost calls not shown in report CQ79900 SMDR does not show the "Dialed" access code, when POT phone redials ...
URL: ../mergedProjects/bulletins/techbulls/tb108.pdf
72. Account Code [HTML]
... > Supervisor Settings) . They then need to enter an account code for any outgoing external calls. Incoming calls can also be associated with an account code by matching the Caller ID stored with the account code settings. That account code is then included in the call's SMDR call log. When an account code is entered during a call: The IP Office checks the code entered for a match against those account codes set in its configuration. For Forced Account Code calls, the call is not allowed until a valid code is entered ...
URL: ../mergedProjects/webmanager/SysSettingsAccountCode.html
73. Advice of Charge [HTML]
... The system supports advice of charge (AOC) on outgoing calls to ISDN exchanges that provide AOC information. It supports AOC during a call (AOC-D ) and at the end of a call (AOC-E ) . This information is included in the SMDR output. AOC is only supported on outgoing ISDN exchange calls. It is not supported on incoming calls, reverse charge calls, QSIG and non-ISDN calls. Provision of AOC signalling will need to be requested from the ISDN service provider and a charge may ...
URL: ../mergedProjects/manager/Html_Advice_of_Charge.html
... for IP 500 BRI... 21 3.10 Restrict Network Interconnect ... 22 3.11 T3 Telephone Enhancements ... 23 3.12 Embedded VoiceMail to E-Mail ... 25 3.13 Telephone Messages' button goes to Visual Voice... 25 3.14 Reversal of Operation Dialled Digits' From 4.0/4.1 ... 26 3.15 SMDR Output from IP Office Core ... 26 3.16 Voice over IP Enhancements... 27 3.17 Hunt Group Queuing Option ... 29 3.18 Set Hunt Group Fall Back ... 29 3.19 Call Initiation Timeout... 30 3.20 User Logout Enhancement ... 30 3.21 Base Extension Merge ... 31 3.22 User BLF Enhancements ...
URL: ../mergedProjects/bulletins/techbulls/tb097.pdf
... IP Office 5.0(18) and Manager 7.0(18) CQ Number Description of Issue CQ40078 Phone does not display VMail if a user button is defined and the user is busy. 5420/5410 CQ40087 SIP caller ID is no longer displayed on the phone CQ40164 SMDR records are output with additional line breaks CQ83052 IP DECT R4 with one-X Portal - Place a call on Hold - it cannot be retrieved CQ84319 S-Bus Overlap Call will not dial out off switch to another ETSI trunk when Dial Delay Count set to ...
URL: ../mergedProjects/bulletins/techbulls/tb113.pdf
<< 1 2 3 4 5 6 7 8 >>


Search took 0.442 seconds