FAQs for Cisco MediaSense

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m (1 revision)
(How do you correlate reference call IDs for different call scenarios?)
Line 18: Line 18:
== How do you correlate reference call IDs for different call scenarios?  ==
== How do you correlate reference call IDs for different call scenarios?  ==
-
In Cisco MediaSense, the meta data for each call only provides the xrefci (reference call ID) and the device ref of the forking device and the far-end device (can be a conference bridge or any other phone).  
+
In Cisco MediaSense, the meta data for each call only provides the xRefCi (reference call ID) and the device ref of the forking device and the far-end device (can be a conference bridge or any other phone).  
-
The xrefci parameter is Unified CM's identifier for a particular media stream. They do not always correspond 1-to-1 with the recorded tracks.  
+
The xRefCi parameter is Unified CM's identifier for a particular media stream. They do not always correspond 1-to-1 with the recorded tracks.  
=== Agent Hold/Resume Scenario  ===
=== Agent Hold/Resume Scenario  ===
Line 30: Line 30:
There are 2 recording sessions for this scenario:  
There are 2 recording sessions for this scenario:  
-
*Session with sessionId = S1 with following 2 tracks, for the time period /segment&nbsp; before agent puts call on hold.<br>trackNumber=0 with participant A ( deviceRef=1000, XRefCi = aaaa) <br>trackNumber=1 with participant B (deviceRef=2000, XRefCi = cccc)  
+
*Session with sessionId = S1 with following 2 tracks, for the time period /segment&nbsp; before agent puts call on hold.<br>trackNumber=0 with participant A ( deviceRef=1000, xRefCi = aaaa) <br>trackNumber=1 with participant B (deviceRef=2000, xRefCi = cccc)  
-
*Session with sessionId = S2 with following 2 tracks, for the time period / segment after agent resumes the call. <br>trackNumber=0 with participant A( deviceRef=1000, XRefCi = aaaa) <br>trackNumber=1 with participant B (deviceRef=2000, XRefCi = cccc)
+
*Session with sessionId = S2 with following 2 tracks, for the time period / segment after agent resumes the call. <br>trackNumber=0 with participant A( deviceRef=1000, xRefCi = aaaa) <br>trackNumber=1 with participant B (deviceRef=2000, xRefCi = cccc)
MediaSense does not record the the segment of the call while agent has put the call on hold.  
MediaSense does not record the the segment of the call while agent has put the call on hold.  
Line 43: Line 43:
The entire call is recorded in one session for this scenario:  
The entire call is recorded in one session for this scenario:  
-
*Session with sessionId = S1 with following 2 tracks<br>trackNumber=0 with participant A ( deviceRef=1000, XRefCi = aaaa) <br>trackNumber=1 with participant B ( deviceRef=2000, XRefCi = cccc)
+
*Session with sessionId = S1 with following 2 tracks<br>trackNumber=0 with participant A ( deviceRef=1000, xRefCi = aaaa) <br>trackNumber=1 with participant B ( deviceRef=2000, xRefCi = cccc)
In this scenario MediaSense also records the the segment of the call while customer has put the call on hold.  
In this scenario MediaSense also records the the segment of the call while customer has put the call on hold.  
Line 56: Line 56:
There are 3 recording sessions for this scenario  
There are 3 recording sessions for this scenario  
-
*Session with sessionId = S1 with following 2 tracks, for the time period /segment&nbsp; before agent transfers call. As soon as A initiates transfer, S1 is marked as CLOSED_NORMAL<br>trackNumber=0 with participant ( deviceRef=1000, XRefCi = a1) <br>trackNumber=1 with participant (deviceRef=2000, XRefCi = c1)  
+
*Session with sessionId = S1 with following 2 tracks, for the time period /segment&nbsp; before agent transfers call. As soon as A initiates transfer, S1 is marked as CLOSED_NORMAL<br>trackNumber=0 with participant ( deviceRef=1000, xRefCi = a1) <br>trackNumber=1 with participant (deviceRef=2000, xRefCi = c1)  
*For the time period / segment A and B are consulting with each other, 2 new sessions will get created.
*For the time period / segment A and B are consulting with each other, 2 new sessions will get created.
-
:*Session with sessionId = S2 with following 2 tracks,<br>trackNumber=0 with participant ( deviceRef=1000, XRefCi = a2) <br>trackNumber=1 with participant(deviceRef=3000, XRefCi = b2)  
+
:*Session with sessionId = S2 with following 2 tracks,<br>trackNumber=0 with participant ( deviceRef=1000, xRefCi = a2) <br>trackNumber=1 with participant(deviceRef=3000, xRefCi = b2)  
-
:*Session with sessionId = S3 with following 2 tracks,<br>trackNumber=0 with participant ( deviceRef=3000, XRefCi = b2) <br>trackNumber=1 with participant(deviceRef=1000, XRefCi = a2)
+
:*Session with sessionId = S3 with following 2 tracks,<br>trackNumber=0 with participant ( deviceRef=3000, xRefCi = b2) <br>trackNumber=1 with participant(deviceRef=1000, xRefCi = a2)
*Once A completes transfer
*Once A completes transfer
:*Session S2 is marked as closed_normal  
:*Session S2 is marked as closed_normal  
-
:*Session S3 gets updated with farend changing from A to C<br>trackNumber=0 with participant ( deviceRef=3000, XRefCi = b2) <br>trackNumber=1 with participant C (deviceRef=1000, XRefCi = c2) <br>Note that trackNumber 1 has 2 participants. Participant A before the transfer and participant C after tranbsfer
+
:*Session S3 gets updated with farend changing from A to C<br>trackNumber=0 with participant ( deviceRef=3000, xRefCi = b2) <br>trackNumber=1 with participant C (deviceRef=1000, xRefCi = c2) <br>Note that trackNumber 1 has 2 participants. Participant A before the transfer and participant C after tranbsfer
*After B and C end the call
*After B and C end the call
Line 81: Line 81:
There are 3 recording sessions for this scenario  
There are 3 recording sessions for this scenario  
-
*Session with sessionId = S1 with following 2 tracks, for the time period /segment&nbsp; before agent conferences call. As soon as A initiates conference, S1 is marked as CLOSED_NORMAL<br>trackNumber=0 with participant ( deviceRef=1000, XRefCi = a1) <br>trackNumber=1 with participant (deviceRef=2000, XRefCi = c1)
+
*Session with sessionId = S1 with following 2 tracks, for the time period /segment&nbsp; before agent conferences call. As soon as A initiates conference, S1 is marked as CLOSED_NORMAL<br>trackNumber=0 with participant ( deviceRef=1000, xRefCi = a1) <br>trackNumber=1 with participant (deviceRef=2000, xRefCi = c1)
*For the time period / segment A and B are consulting with each other, 2 new sessions will get created.
*For the time period / segment A and B are consulting with each other, 2 new sessions will get created.
-
:*Session with sessionId = S2 with following 2 tracks,<br>trackNumber=0 with participant ( deviceRef=1000, XRefCi = a2) <br>trackNumber=1 with participant(deviceRef=3000, XRefCi = b2)  
+
:*Session with sessionId = S2 with following 2 tracks,<br>trackNumber=0 with participant ( deviceRef=1000, xRefCi = a2) <br>trackNumber=1 with participant(deviceRef=3000, xRefCi = b2)  
-
:*Session with sessionId = S3 with following 2 tracks,<br>trackNumber=0 with participant ( deviceRef=3000, XRefCi = b2) <br>trackNumber=1 with participant(deviceRef=1000, XRefCi = a2)
+
:*Session with sessionId = S3 with following 2 tracks,<br>trackNumber=0 with participant ( deviceRef=3000, xRefCi = b2) <br>trackNumber=1 with participant(deviceRef=1000, xRefCi = a2)
*Once A completes conference
*Once A completes conference
:*Session S2  gets marked as CLOSED_NORMAL
:*Session S2  gets marked as CLOSED_NORMAL
-
:*Session S3 gets updated with farend changing from A to Conference bridge (CFB)<br>trackNumber=0 with participant ( deviceRef=2000, XRefCi = b2)<br>trackNumber=1 with participant C (deviceRef=b number of CFB,, XRefCi = cfb1)<br>Note that trackNumber 1 has 2 participants. Participant A before the conference and participant CFB after conference  
+
:*Session S3 gets updated with farend changing from A to Conference bridge (CFB)<br>trackNumber=0 with participant ( deviceRef=2000, xRefCi = b2)<br>trackNumber=1 with participant C (deviceRef=b number of CFB,, xRefCi = cfb1)<br>Note that trackNumber 1 has 2 participants. Participant A before the conference and participant CFB after conference  
-
:*Session S4  gets created with <br>trackNumber=0 with participant ( deviceRef=1000, XRefCi = a1 , this is original xrefci when A and C were talking)<br>trackNumber=1 with participant CFB (deviceRef=b number of CFB, XRefCi = cfb2)
+
:*Session S4  gets created with <br>trackNumber=0 with participant ( deviceRef=1000, xRefCi = a1 , this is original xRefCi when A and C were talking)<br>trackNumber=1 with participant CFB (deviceRef=b number of CFB, xRefCi = cfb2)
*After C drops the call
*After C drops the call
-
:*S4 is updated with farend from Conference bridge (CFB) to B <br> trackNumber=1 with participant(deviceRef=3000, XRefCi = b2)
+
:*S4 is updated with farend from Conference bridge (CFB) to B <br> trackNumber=1 with participant(deviceRef=3000, xRefCi = b2)
-
:*S3 is updated with farend changing from Conference bridge (CFB) to A. <br> trackNumber=1 with participant ( deviceRef=1000, XRefCi = a1)  
+
:*S3 is updated with farend changing from Conference bridge (CFB) to A. <br> trackNumber=1 with participant ( deviceRef=1000, xRefCi = a1)  
*After A and B end the call
*After A and B end the call

Revision as of 22:29, 7 July 2011

Introduction

This page lists frequently asked questions about Cisco MediaSense.

If you want to ask a question, post a comment, or discuss an issue regarding a specific article, then follow this procedure:
  1. Log in
  2. Navigate to the article in question
  3. Click the Discussion tab at the top of the page
  4. Edit the Discussion page as described above under Editing
  5. To start a different thread under a new subheading on the Discussion page, click the + tab at the top of the page instead of the Edit tab.

Contents

How do you correlate reference call IDs for different call scenarios?

In Cisco MediaSense, the meta data for each call only provides the xRefCi (reference call ID) and the device ref of the forking device and the far-end device (can be a conference bridge or any other phone).

The xRefCi parameter is Unified CM's identifier for a particular media stream. They do not always correspond 1-to-1 with the recorded tracks.

Agent Hold/Resume Scenario

  1. Agent A (extn 1000) and Caller C (extn 2000) are talking to each other
  2. Agent A puts call on hold
  3. Agent A resumes call

There are 2 recording sessions for this scenario:

  • Session with sessionId = S1 with following 2 tracks, for the time period /segment  before agent puts call on hold.
    trackNumber=0 with participant A ( deviceRef=1000, xRefCi = aaaa)
    trackNumber=1 with participant B (deviceRef=2000, xRefCi = cccc)
  • Session with sessionId = S2 with following 2 tracks, for the time period / segment after agent resumes the call.
    trackNumber=0 with participant A( deviceRef=1000, xRefCi = aaaa)
    trackNumber=1 with participant B (deviceRef=2000, xRefCi = cccc)

MediaSense does not record the the segment of the call while agent has put the call on hold.

Customer Hold/Resume Scenario

  1. Agent A (extn 1000) and Caller C (extn 2000) are talking to each other
  2. Customer C puts call on hold
  3. Customer C resumes call

The entire call is recorded in one session for this scenario:

  • Session with sessionId = S1 with following 2 tracks
    trackNumber=0 with participant A ( deviceRef=1000, xRefCi = aaaa)
    trackNumber=1 with participant B ( deviceRef=2000, xRefCi = cccc)

In this scenario MediaSense also records the the segment of the call while customer has put the call on hold.

Agent Transfer to Another Agent Scenario 

  1. Agent A (extn 1000) and Caller C (extn 2000) are talking to each other
  2. Agent A transfers call to another agent B (extn 3000). Both A and B's devices are set up for forking
  3. B and C are talking.
  4. After some time B and C end call

There are 3 recording sessions for this scenario

  • Session with sessionId = S1 with following 2 tracks, for the time period /segment  before agent transfers call. As soon as A initiates transfer, S1 is marked as CLOSED_NORMAL
    trackNumber=0 with participant ( deviceRef=1000, xRefCi = a1)
    trackNumber=1 with participant (deviceRef=2000, xRefCi = c1)
  • For the time period / segment A and B are consulting with each other, 2 new sessions will get created.
  • Session with sessionId = S2 with following 2 tracks,
    trackNumber=0 with participant ( deviceRef=1000, xRefCi = a2)
    trackNumber=1 with participant(deviceRef=3000, xRefCi = b2)
  • Session with sessionId = S3 with following 2 tracks,
    trackNumber=0 with participant ( deviceRef=3000, xRefCi = b2)
    trackNumber=1 with participant(deviceRef=1000, xRefCi = a2)
  • Once A completes transfer
  • Session S2 is marked as closed_normal
  • Session S3 gets updated with farend changing from A to C
    trackNumber=0 with participant ( deviceRef=3000, xRefCi = b2)
    trackNumber=1 with participant C (deviceRef=1000, xRefCi = c2)
    Note that trackNumber 1 has 2 participants. Participant A before the transfer and participant C after tranbsfer
  • After B and C end the call
  • session S3 is marked closed_normal
    MediaSense does not record the the segment of the call while agent has put the call on hold.

Agent Conference with Another Agent Scenario 

  1. Agent A (extn 1000) and Caller C (extn 2000) are talking to each other
  2. Agent A conferences caller with another agent B (extn 3000). Both A and B's devices are set up for forking
  3. A, B and C are talking.
  4. A drops the call
  5. After some time B and C end call

There are 3 recording sessions for this scenario

  • Session with sessionId = S1 with following 2 tracks, for the time period /segment  before agent conferences call. As soon as A initiates conference, S1 is marked as CLOSED_NORMAL
    trackNumber=0 with participant ( deviceRef=1000, xRefCi = a1)
    trackNumber=1 with participant (deviceRef=2000, xRefCi = c1)
  • For the time period / segment A and B are consulting with each other, 2 new sessions will get created.
  • Session with sessionId = S2 with following 2 tracks,
    trackNumber=0 with participant ( deviceRef=1000, xRefCi = a2)
    trackNumber=1 with participant(deviceRef=3000, xRefCi = b2)
  • Session with sessionId = S3 with following 2 tracks,
    trackNumber=0 with participant ( deviceRef=3000, xRefCi = b2)
    trackNumber=1 with participant(deviceRef=1000, xRefCi = a2)
  • Once A completes conference
  • Session S2 gets marked as CLOSED_NORMAL
  • Session S3 gets updated with farend changing from A to Conference bridge (CFB)
    trackNumber=0 with participant ( deviceRef=2000, xRefCi = b2)
    trackNumber=1 with participant C (deviceRef=b number of CFB,, xRefCi = cfb1)
    Note that trackNumber 1 has 2 participants. Participant A before the conference and participant CFB after conference
  • Session S4 gets created with
    trackNumber=0 with participant ( deviceRef=1000, xRefCi = a1 , this is original xRefCi when A and C were talking)
    trackNumber=1 with participant CFB (deviceRef=b number of CFB, xRefCi = cfb2)
  • After C drops the call
  • S4 is updated with farend from Conference bridge (CFB) to B
    trackNumber=1 with participant(deviceRef=3000, xRefCi = b2)
  • S3 is updated with farend changing from Conference bridge (CFB) to A.
    trackNumber=1 with participant ( deviceRef=1000, xRefCi = a1)
  • After A and B end the call
  • session S3 and S4 are marked CLOSED_NORMAL

Rating: 5.0/5 (2 votes cast)

Personal tools