Hi Gozde, This could probably be because of the war files not be deployed correctly after Upgrade. Just a speculation, too early to confirm right now. We haven't ever observed anything like this for 10.5 -> 11.0 Upgrades till now. The new output seems to be a mix of 11.0 and 10.5 HTML layouts on the Search & Play. We can try re-deploy the Webapp to see if it resolves the issue. I am checking further for other possibilities and will get back to you. Is there a TAC case opened already for this issue ? Though I don't think the issue is browser related but have you checked on IE or other versions of Firefox as well ? Thanks Nitin Singh ... View more

Hi Trinnachart, I am from the MediaSense team. I believe you are talking about the Event Subscription APIs that you can use to monitor Call Recording Start & End. You can use the API's in the following way. At first the 3rd party application needs to register for required Events using subscribeToEvents  API. In the response to subscribeToEvents  API, MediaSense will respond with the outcome + Events registered + Event Subscription ID. MediaSense will now send events using the above Subscription-Id to the 3rd party application whenever the event is observed. There are 3 ways by which you can verify - You can confirm the triggers from the 3rd party application by searching for the events observed from the Subscription-Id  which MediaSense provided in response. You can also test the current state of the earlier Subscription-Id using the MediaSense API  verifyEventSubscription. This will provide a response whether the Subscription-Id is still ACTIVE or has it gone INACTIVE. You can also get it confirmed the following from the MediaSense logs ( ORA module ) and see if there is any START event triggered from the ORA logs when the recording starts. You may involve Cisco TAC if there are any any doubts while accessing MediaSense logs or we can have a WebEx if required to gather and confirm the same. You will get all the API details and the responses from MediaSense side in the Developer Guide. please have a look at the "Event Subscription APIs" section - Chapter 3. Let me know in case of any doubts in the above said. Thanks Nitin Singh ... View more

Hi Mike, (mikemaas ) You along with the other evangelists were so dedicated in not letting the usage of various Cisco technologies itself be a challenge, that all teams reached the demo phase like breeze. You were the first mentor with whom we discussed our idea and the approach to the demo. Thanks for all the valuable inputs on the 'The Day'. Regards Nitin Singh Team - Smart Connected World (Smart Lifts) - Aricent ... View more

Hi Tessa  (tmero ) You along with the other evangelists were so dedicated in not letting the usage of various Cisco technologies itself be a challenge, that all teams reached the demo phase like breeze. Regards Nitin Singh Team - Smart Connected World (Smart Lifts) - Aricent ... View more

Hi Jesus M, As this case is of BiB forking and in case of BiB forking, MediaSense always creates new session after call transfer. Let’s take one example to explain the correlation between the xRefCI fields. A – Calls -> B                            (xRefCI-A, xRefCI-B) B – Consultive Call -> C        (xRefCI-B,  xRefCI-C) A – B Transferred Call -> C (xRefCI-A’, xRefCI-C) So xRefCI of originator changes from xRefCI-A to xRefCI-A’ because of a transfer in the final call. Which is represented in JSON as well. Same thing is represented by CDR as well. For same XREFCI, you getting two entries in CDR. Moreover, XRefCI are managed by CUCM, and MediaSense just receive them from SIP signaling. You can make make a search combination of XRefCI and the right extension (other party) to get the exact recording you wish to get hold of. You can try this search from our Search & Play portal as well. Let us know if you face any issue. If you do, we will check this again at out end after reproducing this scenario. Thanks Nitin Singh ... View more

Hi, This issue relates to MediaSense when Jabber endpoints are used to make Video calls. Here MediaSense cut shorts the video at 5 min 30 sec because of lack of I-Frames generated by Jabber in the media stream as part of existing design. All Cisco devices that were used till now used to periodically send I-Frames w hich MediaSense is currently expecting which broke the functionality since Jabber does not send any I-Frames usually after few initial I-Frames at the beginning of the call. Following defect was raised to fix the issue and an official ES on 10.5 Release will be available on May 8 as per plan. CSCut59398 (MediaSense recording cuts off video recording when using Jabber). Thanks Nitin Singh ... View more