API: Incorrect participant duration

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m (1 revision)
Line 1: Line 1:
-
== Incorrect participant duration ==
+
== Incorrect participant duration ==
{| border="1"
{| border="1"
|-
|-
-
! '''Problem Summary'''
+
! '''Problem Summary'''  
| The far-end participant duration for the Session Query and Session Event APIs is incorrect.
| The far-end participant duration for the Session Query and Session Event APIs is incorrect.
|-
|-
-
! '''Error Message'''
+
! '''Error Message'''  
| None.
| None.
|-
|-
-
! '''Possible Cause'''
+
! '''Possible Cause'''  
| If a far-end participant is not present for the entire duration of a recording session, the duration response for that participant is incorrect.
| If a far-end participant is not present for the entire duration of a recording session, the duration response for that participant is incorrect.
|-
|-
-
! '''Recommended Action'''
+
! '''Recommended Action'''  
| At any time, a recording session can only have two participants: a near-end participant (identified by Track Number 0) and a far-end participant (any non-zero track number). Even in a conference scenario, only the conference bridge number is available to Cisco MediaSense. Consequently, if multiple participants are available in a bridge, Cisco MediaSense only displays one participant(identified by the isConference flag).  
| At any time, a recording session can only have two participants: a near-end participant (identified by Track Number 0) and a far-end participant (any non-zero track number). Even in a conference scenario, only the conference bridge number is available to Cisco MediaSense. Consequently, if multiple participants are available in a bridge, Cisco MediaSense only displays one participant(identified by the isConference flag).  
-
 
The only way a participant list can be changed in a recording session is if the far-end participant performs a transfer or has a conference. If the near-end participant drops off or initiates a conference, the existing recording session terminates.  
The only way a participant list can be changed in a recording session is if the far-end participant performs a transfer or has a conference. If the near-end participant drops off or initiates a conference, the existing recording session terminates.  
-
So the workaround is to use the start time of a new far-end participant as the end time of the previous far-end participant and calculate the duration.
+
So the workaround is to use the start time of a new far-end participant as the end time of the previous far-end participant and calculate the duration.  
-
               
+
 
Also use this workaround for SessionEvent to determine if a far-end participant (was) dropped from a recording session (and if so, at what time).
Also use this workaround for SessionEvent to determine if a far-end participant (was) dropped from a recording session (and if so, at what time).
 +
|-
|-
-
! '''Release'''
+
! '''Release'''  
| Release 8.5(1).
| Release 8.5(1).
|-
|-
-
! '''Associated CDETS #'''
+
! '''Associated CDETS #'''  
-
|[http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtl47917 CSCtl47917]
+
| [http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtl47917 CSCtl47917]
-
|-
+
|}
|}
 +
[[Category:Cisco_MediaSense,_Release_8.5]]
-
[[Category:Cisco MediaSense, Release 8.5]]
+
[[Category:Cisco_MediaSense,_Release_8.5]]

Revision as of 21:16, 25 August 2011

Incorrect participant duration

Problem Summary The far-end participant duration for the Session Query and Session Event APIs is incorrect.
Error Message None.
Possible Cause If a far-end participant is not present for the entire duration of a recording session, the duration response for that participant is incorrect.
Recommended Action At any time, a recording session can only have two participants: a near-end participant (identified by Track Number 0) and a far-end participant (any non-zero track number). Even in a conference scenario, only the conference bridge number is available to Cisco MediaSense. Consequently, if multiple participants are available in a bridge, Cisco MediaSense only displays one participant(identified by the isConference flag).

The only way a participant list can be changed in a recording session is if the far-end participant performs a transfer or has a conference. If the near-end participant drops off or initiates a conference, the existing recording session terminates.

So the workaround is to use the start time of a new far-end participant as the end time of the previous far-end participant and calculate the duration.

Also use this workaround for SessionEvent to determine if a far-end participant (was) dropped from a recording session (and if so, at what time).

Release Release 8.5(1).
Associated CDETS # CSCtl47917

Rating: 0.0/5 (0 votes cast)

Personal tools