Search results for: SMDR in all categories

248 results .

10 pages.
... 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,. ...
URL: ../mergedProjects/webmanager/SMDR_Example_Voicemail_Supervised_Transfer.html
... SMDR Example: Call Transferred to Voicemail In this example, the Continuation field being 1 in the first record tells us that it was not the end of the call. The matching Call ID identifies the second record as part of the same call. The change in Party 1 details between the two records show that the call was transferred to voicemail. 2014/06/28 09:30:57,00:00:13,7,01707392200,I,299999,299999, 0, 1000014160 , 1 , E4750 , John Smith ,T9002,LINE 1.2,11,0,. 2014/06/28 09: ...
URL: ../mergedProjects/webmanager/SMDR_Example_Call_Transferred_to_Voicemail.html
... 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 ...
URL: ../mergedProjects/webmanager/SMDR_Example_Mobile_Twin_Answered_at_Twin.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/webmanager/SMDR_Example_External_Conference_Party.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/webmanager/SMDR_Example_Call_Transfer.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/webmanager/SMDR_Example_Distributed_Hunt_Group_Call.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/webmanager/SMDR_Example_Call_Transferred_Manually.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/webmanager/SMDR_Example_External_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,. ...
URL: ../mergedProjects/webmanager/SMDR_Example_Lost_Incoming_Call.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/webmanager/SMDR_Example_External_Forward_Unconditional.html
... SMDR Example: Authorization code In this example, an authorization code was used and the 0 indicates that it is invalid. 2014/02/20 11:04:59,00:00:00,0,319,O,, 0,1000009,0,E319,Alice,V8000,U1 0.0,0,0, 0 , n/a U,Alice,. In this example, the authorization code is valid. 2014/02/20 11:04:59,00:00:00,0,319,O,, 0,1000009,0,E319,Alice,V8000,U1 0.0,0,0, 1 , n/a U,Alice,. ...
URL: ../mergedProjects/webmanager/SMDR_Example_Authorization_Code.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/webmanager/SMDR_Example_Conference_Using_a_Conf_Button.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,. ...
URL: ../mergedProjects/webmanager/SMDR_Example_Outgoing_Call.html
... SMDR Example: Call Routed by Incoming Call Route Call from external number 403 rerouted by incoming call route (ICR) for incoming line group 701 back out to 404. 2014/08/01 11:45:36,00:00:01,2,403,I,9404,,0,1000007,0,T9001 ,Line 1.0,T9010,Line 10.0,0,0,0,n/a,,,, ICR , ICR701 ,404,. ...
URL: ../mergedProjects/webmanager/SMDR_Example_Call_Routed_by_ICR.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/webmanager/SMDR_Example_Busy_NU_Tone.html
... 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/webmanager/SMDR_Example_Call_Answered_by_Voicemail.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 ...
URL: ../mergedProjects/webmanager/SMDR_Example_Parked_Call.html
... 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 ...
URL: ../mergedProjects/webmanager/SMDR_Example_Pickup_Using_Twinning_Button.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 ...
URL: ../mergedProjects/webmanager/SMDR_Example_Add_a_Party_to_a_Conference.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/webmanager/SMDR_Example_Call_Pickup.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/webmanager/SMDR_Example_Internal_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 ...
URL: ../mergedProjects/webmanager/SMDR_Example_Rerouted_External_Call.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: 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,. ...
URL: ../mergedProjects/manager/SMDR_Example_Outgoing_Call.html
... 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 ( ...
URL: ../mergedProjects/manager/SMDR_Example_Mobile_Twin_Answered_Internally.html
<< 1 2 3 4 5 6 7 8 9 10 >>


Search took 0.456 seconds