RE: Sample App for MediaSense 9.0

RE: Sample App for MediaSense 9.0 Issue

2013-04-03T20:45:00Z

The jquery.jqGrid.min.js is a standard jquery package and the errors you are seeing could be related to the eclipse plugin. Please provide the details about eclipse version and the plugins you are using. You can also try to extract the same file from the war file packaged with the sample code and use that js file instead.

Sample App for MediaSense 9.0 Issue

2013-03-30T15:28:53Z

[b][b]Hi Team, I just donwloaded Sample App for MediaSense 9.0.zip file and imported the content to an eclipse application. However most of the js files under WebContent/js folder gives an error which states "-Missing semicolon". Please see the attached screenshot that is taken from eclipse. Any comment appriciated. Regards. [/b][/b]

RE: The mediasense sample application is corrupted and files are deleted by

2013-02-28T17:35:12Z

Rico, We have updated the zip file on CDN and addressed the missing js files. Sorry for the inconvenience.

RE: The mediasense sample application is corrupted and files are deleted by

2013-02-27T23:19:26Z

We'll post a new sample s&p app zip file in the CDN soon.

RE: The mediasense sample application is corrupted and files are deleted by

2013-02-26T21:18:13Z

Hi. Let me repeat. I dont have mcafee antivirus. It's the file that is on the web that is corrupted. if you download the file from the url, unzip it. unzip the war file, (that is done by apache-tomcat when you move it to the webapps dir, then look in the folders where the js files are supposed to be. instead of the .js files there is a warning text for each .js file that is missing. And yes, it's possible to copy the .js files from the Mediasense-source.zip file. But the file on the web is still corrupted.

RE: The mediasense sample application is corrupted and files are deleted by

2013-02-26T21:10:05Z

Just want to make sure you have the latest code. Not sure what that "Filter binaries and Executables" rule is. If you use a windows machine, a simple workaround would be manually copy all .js files from WebContent directory (js, and jquery/js) to your webapp directory. The zip file can be scp/sftp to a liinux webserver, and unzip over there, which is also a workaround. I use Mac and I don't see this problem. I'll engage the eng team to figure out what really causes this.

RE: The mediasense sample application is corrupted and files are deleted by

2013-02-26T20:48:18Z

A few weeks ago. Try downloading the file : open the .war file navigate to the js subdirs you will find files called warning_xxx.txt containing like this : BLOCKED FILE ALERT A file has been blocked due to the 'Filter Binaries and Executables' rule. Context: 'grid.base.js' Disallowed due to Ticket Number: '0c18-50bd-23aa-0005' See your system administrator for further information. Copyright 1999-2011 McAfee, Inc.All Rights Reserved.http://www.mcafee.com

RE: The mediasense sample application is corrupted and files are deleted by

2013-02-26T20:44:19Z

Hi Rico, When did you download the app? The latest app posted in http://developer.cisco.com/web/mediasense/home is dated Jan 2nd, 2013. Please confirm. Thanks, Bruce

RE: Correlation

2013-02-21T17:43:55Z

Amit, How you correlate the call depends on your deployment and call flow scenarios. Here are the two most common scenarios: 1) You are forking media from CUBE, and these are inbound calls using CVP to UCCE. In this case, CUBE generates an identifier known as Cisco-GUID, which is passed to both MediaSense and CVP. In MediaSense it is known as CCID (Call Correlation ID), and you can both find the call in MediaSense if you know the ID, as well as discover the ID from MediaSense if you know the call info through some other means. In UCCE, it can be found in the active routing script as Call.CallGUID, or in the ECC variable user.media.id, or in the TCD as TCD.CallReferenceID. You can also find it in the CTIOS event stream as ECC variable user.media.id. 2) You are forking media from a CUCM phone. Without a JTAPI link, these calls are difficult to correlate in real time. If real time correlation is required, for live monitoring for example, then one way is to match on caller ANI or agent extension, both of which are stored in their respective deviceRef fields in MediaSense. Matching on ANI might not always be easy due to the usual vaguaries of ANI, such as masking, non-uniqueness, or digit manipulation. Matching on agent extension could also be difficult because in CUCM, recording profiles are defined on a per-line basis, and there could be shared lines or muti-line phones. Also remember that in UCCE a given agent may have a different extension each time she logs in. After the call terminates and CUCM has had time to write the CDR record, the call can be correlated using either of the two xRefCi fields in MediaSense. These identifiers can be found in the CDR as origLegCallIdentifier and destLegCallIdentifier. Once you have the proper CDR record you can find the call in UCCE via several means. The most reliable is to concatenate global_CallID_call-ManagerId + global_CallID_callId (A.K.A. UCM GCID) from the CDR, and search for the resulting value as TCD.PeripheralCallKey. If these scenarios aren't what you are looking for, please write back with additional information: - Are you forking from CUBE or from CUCM phones? - Are you looking for real time or historical correlation? - Does your software have a JTAPI link? - Does your deployment even use CUCM agents? (I ask because you used the term ICM rather than UCCE, and speaking formally, ICM could mean any ACD) - Are you looking at inbound calls or outbound calls? And if outbound, do agents initiate them through a UCCE routing script, or do they directly dial outbound phone numbers? Or are you using an outbound dialer product? Thanks, Jeff W.

Correlation

2013-02-21T06:57:32Z

HI , I need to correlate a recording session with ICM call details, in order to retrevce Skillgroup, Call type and agent name. Can someone provide some tips, directions in this regard? thanks.

The mediasense sample application is corrupted and files are deleted by AV

2013-02-20T20:13:43Z

The version 9.0 sample application dont work and all the .js files have been removed by mcafee antivirus before uploading to the website.

RE: Raw tracks not in sync

2013-02-07T17:36:25Z

That's the difference between the tracks, I haven't actually compared them to session duration.

RE: Raw tracks not in sync

2013-02-07T15:56:55Z

Dan, Are you saying that the track durations are 3-6 and in some cases 20 seconds off from each other, or from the duration reported by the session data? In either case, we will need some logs to investigate this. I will contact you outside the forum. Thanks, Jeff W.

RE: New Message from Daniel Hatch in Cisco MediaSense (MediaSense) - Techni

2013-02-06T20:14:27Z

[quote=Jeffrey Wolfeld]How far off are the tracks from one another? [/quote] I most egregious example I have found was about 20 seconds. Usually they are more in the range of 3-6 seconds. [quote=Jeffrey Wolfeld]I want to make sure that you are actually receiving some SILENCE= tags, right? Most normal HTTP 1.1 clients automatically combine chunks and in doing so, they lose these inter-chunk tags. You probably need to code your HTTP client at the TCP level in order to capture these tags. You've probably gotten that, but I just want to make sure. [/quote] We're using our own code to parse the HTTP response and I've been over it/stepped thru it a few times making sure that it appropriately inserts silence and is reading the tags. I doubt the bug is there. Thanks, Dan

RE: New Message from Daniel Hatch in Cisco MediaSense (MediaSense) - Techni

2013-02-06T17:51:30Z

Daniel, How far off are the tracks from one another? The timings reported in the MediaSense session data are based on SIP messaging, not on actual RTP media flow. There is likely to be a small mismatch, but it shouldn't be very much. I want to make sure that you are actually receiving some SILENCE= tags, right? Most normal HTTP 1.1 clients automatically combine chunks and in doing so, they lose these inter-chunk tags. You probably need to code your HTTP client at the TCP level in order to capture these tags. You've probably gotten that, but I just want to make sure. I will check on the start and end silence periods and get back to you. Thanks, Jeff W. From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com] Sent: Wednesday, February 06, 2013 7:36 AM To: cdicuser@developer.cisco.com Subject: New Message from Daniel Hatch in Cisco MediaSense (MediaSense) - Technical Discussion: Raw tracks not in sync Daniel Hatch has created a new message in the forum "Technical Discussion": -------------------------------------------------------------- I'm having a problem where one of the raw tracks provided by MediaSense is not the same length as the other one. Therefore when I mux the tracks together into a single call track people are talking over each other and it is difficult/impossible to follow the call. Because the metadata provided by MediaSense makes me expect the tracks to be of the same length (track duration is the same, track start timestamp is the same) I have no way of knowing to which end of the shorter track I need to add silence, the end or beginning. Calls are in G711 mu-law if that makes any difference. My suspicion is that when MediaSense is sending the raw tracks using HTTP chunk transfer coding as described in the API docs it is not appropriately including an initial or terminal “SILENCE=x” chunk extension which would pad out the shorter track and make the tracks align when muxed, but I cannot prove that. I appreciate your feedback, thanks in advance! -- To respond to this post, please click the following link: http://developer.cisco.com/web/mediasense/forums/-/message_boards/view_message/11617085 or simply reply to this email.

Raw tracks not in sync

2013-02-06T15:35:35Z

I'm having a problem where one of the raw tracks provided by MediaSense is not the same length as the other one. Therefore when I mux the tracks together into a single call track people are talking over each other and it is difficult/impossible to follow the call. Because the metadata provided by MediaSense makes me expect the tracks to be of the same length (track duration is the same, track start timestamp is the same) I have no way of knowing to which end of the shorter track I need to add silence, the end or beginning. Calls are in G711 mu-law if that makes any difference. My suspicion is that when MediaSense is sending the raw tracks using HTTP chunk transfer coding as described in the API docs it is not appropriately including an initial or terminal “SILENCE=x” chunk extension which would pad out the shorter track and make the tracks align when muxed, but I cannot prove that. I appreciate your feedback, thanks in advance!

RE: Sample App for MediaSense 9.0

2013-02-04T21:00:55Z

Hi Bruce, After doing that, the page would not give the error anymore when trying to login, instead it would just reload like it was not accepting my credentials. I then checked the tomcat logfiles and noticed that it was expeciting the xml file in this location : C:\Program Files\apache-tomcat-6.0.32\bin After copying it there, I can login. Thanks for all the help, Jeroen

RE: Sample App for MediaSense 9.0

2013-02-04T20:51:45Z

copy the classes directory under the build folder to webapps\mediasense\WEB-INF as well, then follow my previous post for Mediasense.properties and mediasenserequest.xml. -Bruce

RE: Sample App for MediaSense 9.0

2013-02-04T20:15:29Z

Hi Bruce, I don't have a Mediasense.properties file in that directory. I only have a web.xml file and a lib folder in that directory.When I downloaded the original Sample App for MediaSense 9.0.zip file, I extracted it and only copied the contents of the WebContent folder to a newly created Mediasense folder on my apache server. When I check that original zip file, I can see there is a build folder which has a classes folder inside. In that folder I can see the mediasense.properties, but as said that file is not on my apache server. Should I have copied more than just the webcontent folder? Thanks again for your help. Rgds, jeroen

RE: Sample App for MediaSense 9.0

2013-02-04T20:07:41Z

the instruction is for linux based servers. try the following * go to webapps\mediasense\WEB-INF\classes, and open Mediasense.properties. change the XMLPATH to just mediasenserequest.xml, like this XMLPATH=mediasenserequest.xml * copy or move the mediasenserequest.xml to tomcat directory. In your environement, it'd be [url=http://developer.cisco.com/web/mediasense/community/-/message_boards/message/11523315?p_p_auth=GynpP0yQ]c:\Program[/url] Files\apache-tomcat-6.0.32\ * the baseurl in the mediasenserequest.xml should be https://192.168.12.14:8440/ora/ give it a try. if it still doesn't work, try to use Tomcat 7. That's what I'm using.. -Bruce