Dosproul: 1 revision

2013-02-06T19:52:44Z

1 revision

← Older revision

Revision as of 19:52, 6 February 2013

Jwolfeld at 21:57, 24 January 2013

2013-01-24T21:57:42Z

Show changes

Karrande: 1 revision

2012-04-11T19:42:11Z

1 revision

← Older revision

Revision as of 19:42, 11 April 2012

Rshroyer at 22:48, 9 April 2012

2012-04-09T22:48:07Z

Show changes

Jkratky: 1 revision

2011-10-17T18:23:20Z

1 revision

← Older revision

Revision as of 18:23, 17 October 2011

Jwolfeld at 23:44, 12 October 2011

2011-10-12T23:44:55Z

← Older revision		Revision as of 23:44, 12 October 2011
Line 256:		Line 256:
	! scope="col" \| MediaSense<br>		! scope="col" \| MediaSense<br>
	! scope="col" \| Ingress Gateway or CUBE<br>		! scope="col" \| Ingress Gateway or CUBE<br>
-	! scope="col" \| AAA RADIUS CDR<br>	+	! scope="col" \| AAA RADIUS CDR<br>
	! scope="col" \| UCM CDR<br>		! scope="col" \| UCM CDR<br>
	! scope="col" \| TAPI/JTAPI field<br>		! scope="col" \| TAPI/JTAPI field<br>
Line 266:		Line 266:
	\| (1)<br>		\| (1)<br>
	\| Cisco-Guid<br>		\| Cisco-Guid<br>
-	\| <br>	+	\| <br>
	\| IncomingProtocolCallRef<br>		\| IncomingProtocolCallRef<br>
	\| CiscoConnection.UniqueID<br>		\| CiscoConnection.UniqueID<br>
Line 276:		Line 276:
	\| NearEnd xRefCi<br>		\| NearEnd xRefCi<br>
	\| <br>		\| <br>
-	\| <br>	+	\| <br>
	\| destLegCallIdentifier<br>		\| destLegCallIdentifier<br>
	\| Terminal.ConnectionID<br>		\| Terminal.ConnectionID<br>
Line 286:		Line 286:
	\| FarEnd xRefCi<br>		\| FarEnd xRefCi<br>
	\| <br>		\| <br>
-	\| <br>	+	\| <br>
	\| origLegCallIdentifier<br>		\| origLegCallIdentifier<br>
	\| Terminal.ConnectionID<br>		\| Terminal.ConnectionID<br>
Line 296:		Line 296:
	\| <br>		\| <br>
	\| <br>		\| <br>
-	\| <br>	+	\| <br>
	\| global_CallID_call-ManagerId + global_CallID_callId<br>(A.K.A. UCM GCID)<br>		\| global_CallID_call-ManagerId + global_CallID_callId<br>(A.K.A. UCM GCID)<br>
	\| CiscoCall.CallID<br>		\| CiscoCall.CallID<br>
Line 306:		Line 306:
	\| deviceId<br>		\| deviceId<br>
	\| <br>		\| <br>
-	\| <br>	+	\| <br>
	\| <br>		\| <br>
	\| <br>		\| <br>
Line 316:		Line 316:
	\| deviceRef<br>		\| deviceRef<br>
	\| <br>		\| <br>
-	\| <br>	+	\| <br>
	\| <br>		\| <br>
	\| <br>		\| <br>
Line 332:		Line 332:
	! scope="col" \| MediaSense<br>		! scope="col" \| MediaSense<br>
	! scope="col" \| Ingress Gateway or CUBE<br>		! scope="col" \| Ingress Gateway or CUBE<br>
-	! scope="col" \| AAA RADIUS CDR<br>	+	! scope="col" \| AAA RADIUS CDR<br>
	! scope="col" \| UCM CDR<br>		! scope="col" \| UCM CDR<br>
	! scope="col" \| TAPI/JTAPI field<br>		! scope="col" \| TAPI/JTAPI field<br>
Line 342:		Line 342:
	\| CCID<br>		\| CCID<br>
	\| Cisco-Guid<br>		\| Cisco-Guid<br>
-	\| Cisco-Guid<br>	+	\| Cisco-Guid<br>
-	\| <br>	+	\| IncomingProtocolCallRef<br>
-	\| <br>	+	\| UniqueCallRefID<br>
	\| TCD.CallReferenceID<br>		\| TCD.CallReferenceID<br>
	\| Call.CallGUID<br>		\| Call.CallGUID<br>
Line 352:		Line 352:
	\| deviceRef<br>		\| deviceRef<br>
	\| Called or calling party extn<br>		\| Called or calling party extn<br>
-	\| <br>	+	\| <br>
	\| <br>		\| <br>
	\| <br>		\| <br>

Cchetty: 1 revision

2011-10-08T20:19:33Z

1 revision

← Older revision

Revision as of 20:19, 8 October 2011

Jwolfeld at 20:51, 28 September 2011

2011-09-28T20:51:29Z

Show changes

Cchetty: /* How do you correlate reference call IDs for different call scenarios? */

2011-07-07T22:29:08Z

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

Ccosenti: 1 revision

2011-04-29T17:31:55Z

1 revision

← Older revision

Revision as of 17:31, 29 April 2011

← Older revision		Revision as of 22:29, 7 July 2011
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  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  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  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  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  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  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

FAQs for Cisco MediaSense - Revision history

Dosproul: 1 revision

Jwolfeld at 21:57, 24 January 2013

Karrande: 1 revision

Rshroyer at 22:48, 9 April 2012

Jkratky: 1 revision

Jwolfeld at 23:44, 12 October 2011

Cchetty: 1 revision

Jwolfeld at 20:51, 28 September 2011

Cchetty: /* How do you correlate reference call IDs for different call scenarios? */

Ccosenti: 1 revision