Hello Team, Is there any way to fetch the DN(Dialed Number) that customer actually dialed which was on later routed to some agent based upon skill? Currently, mediasense doesn't share any such information as we just get info about the agent we actually attended the call but we need information about the service DN dialed by the customer. If this is not supported by mediasense, then how can we actually fetch this info from TCD (termination Call Data)? Can xRefci or Recording Id help us in this regard (after making an association with TCD table)? Thanks for your support. anilve
... View more
We are working on UCCX 11.0. after writing the script when we upload it on the UCCX server, it doesn't run, we get error prompt either. In the script we are using custom objects and we have uploaded a JAR file on UCCX server.
In Cisco Unified UCCX Serviceability, ''Cisco Unified CCX Engine =>> Application Manager" service being shown as "Partial Service". But when we unload JAR file it turns back into "IN SERVICE" state. Which mean there is something wrong with JAR.
Please consider the following updates:
JAR uploading process has been thoroughly followed
When we upload some other simple JAR file it works fine
We tried many times by restarting services (Engine and Administrator) and even also by restarting the whole box
We are unable to find out why our JAR file is not working in CCX server while I can access its custom objects in the Unified CCX Editor. Apparently, Everything seems fine with JAR file as we tested it separately as well. We looked into the logs and found this:
16755: Dec 06 18:13:35.490 PKT %MIVR-SS_TEL-3-EXCEPTION:com.cisco.app.InvalidApplicationException: failed to load script; nested exception is:
16756: Dec 06 18:13:35.491 PKT %MIVR-SS_TEL-3-EXCEPTION: com.cisco.script.ScriptIOException: Failed to load script: play_prompt1. aef ; nested exception is:
16757: Dec 06 18:13:35.491 PKT %MIVR-SS_TEL-3-EXCEPTION: com.cisco.io.StreamCorruptedException: invalid type code: 04; unable to load expression; ensure all custom classes are available; nested exception is:
16758: Dec 06 18:13:35.491 PKT %MIVR-SS_TEL-3-EXCEPTION: java.io.StreamCorruptedException: invalid type code: 04
Can anyone please explain that what's wrong going on? How may I troubleshoot the issue? thanks
... View more
Hi ambdev After applying solution provided by you, we are getting 1000 records after the query. But we are observing one thing that when we apply limit and offset parameters we just get 'ACTIVE' calls while we should get all types of call as we have not applied any such filter. While before, we were getting calls with all statuses (Active, Recorded, Error) during specified period mentioned in the query. So, It would be a great favor if you verify this scenario at your end too that if this happens at your end as well or not. Thanks for your usual support and coordination.
... View more
Hi Ambrose, Thanks for your useful reply. We just successfully executed the query with offset: 0 and limit: 1000. But, when we increased the limit to 2000 we got failure response with error code: 4064 and according to the documentation this means that Failure: The limit parameter is invalid. And according to the documentation of parameter 'limit', By default, it returns the first 100 records. Any positive value greater than zero (0). Maximum possible value for this parameter is 1000. So, It's quite clear now that why it's working with the maximum of 1000 as limit. Thanks for your support and all the efforts.
... View more
anilve ambdev It would really be a great favor if you please take it on priority and reply at your earliest. thanks for your support and coordination.
... View more
Hi Ambrose, We need clarification on one more point. When mediasense archives the recording into SFTP server then it still remains accessible in mediasense to play? A recording has been archived but it still can be played directly from mediasense with mp4Url.
... View more
Hi Ambrose, Thanks for the all the clarifications. So, mediasense can't help us on recordings distinction based upon it's current state. anilve can you please note this point for future mediasense release to include this as a new feature that when a recording is archived by mediasense, subscribed application should get the notification.
... View more
Hi Ambrose, Thanks for all the efforts, appreciate that. We aren't sure aboutmediasense strategy of returning results against queries as its conflicting with what's mentioned in the documents. Looking forward to hear from you soon. Thanks for your support and coordination.
... View more
We can configure automatic archival feature in the mediasense. So, recordings meeting the specified archival criteria would be archived at specified locations. So, how our application would be notified that particular recording has been archived or not. For example, Mediasense archived recording 'A'. After that our application query to mediasense to fetch recording 'A' (for example with sessionId) then which parameter in recording metadata sent back as a response would define recording's current state? According to my current understanding, it always sends 'CLOSED_NORMAL' irrespective of either recording has been archived or not. So, how may we actually decide recording's current state? P.S. I want to avoid manual check at our application side to check with same criteria that we mentioned in mediasense archival configuration. anilve imandal nitinsi dlender manisgu3 pnijhawa hariskum anilv ambdev
... View more
Hi Ambrose, Thanks for your reply. We already reviewed this document. As mentioned in the description of this post, we are already using custom queries by specifying the range to be applied on sessionStartDate to fetch recordings. But the issue is that we aren't getting all recordings which are fulfilling our custom query. We are getting the maximum of 100 records while we want to get all the recordings which fulfills our query. So, what's the possibility for us? Is this the limitation that we can't get more than 100 records at mediasense side or would we have to shorten our query? We simply want to fetch recordings within the particular date range (1 day). Thanks for your support and coordination.
... View more
We are trying to implement a recording fetching mechanism if missed due to any reason. We have date range and will fetch recordings between this. To make this more scalable I divided this date range into the interval of one day so We send a query for each day separately. But I'm not getting records more than 100. While in the documentation it's mentioned that its default value. So how may we increase this limit? Currently, these are the request parameters we are sending:
{
"requestParameters": [
{
"fieldName" : "sessionStartDate",
"fieldConditions": [
{
"fieldOperator" : "between",
"fieldValues" : [
"1476817200000",
"1476900000000"
]
} ] } ] }
We tried by adding below attributes as well in the above parameters, but not worked still return max 100 records
,
"pageParameters": {"offset": "0" ,
"limit": "1000" }
And also tried this: /queryService/query/getSessions?limit=1000 Would we have to further divide query (in 4 ,6 or 8 hours) ? What's THE BEST approach as mediasense also discards query if it takes more than 2 minutes (btw what is the maximum number of recordings which can be filtered in these 2 minutes with sessionStartDate constraint with between operator?) sessionStartDate Thanks for your time and support. anilve imandal nitinsi dlender manisgu3 pnijhawa hariskum anilv
... View more
Dear Singh, thanks for coming back and your assistance. We are using v10.5 of Mediasense. We observed this scenario with FFMPEG for now, as we were unable to stream with VLC or Quick Time as it gives stream with a lot of distortions. And we will share packet capture with you in a while. But, if we are not mentioning any track then it should play both and as I described here that it was working fine before.
... View more
Hello Everyone, I am working with Live Monitoring of Active Calls. I am facing an issue while using RTSP Url for live streaming. When I play RTSP Url with some tool I am hearing just Agent's voice (just one stream) while I am unable to hear customer's voice (one on other end). Here is sample streaming URL:
rtsp://username:password@machine_ip/42331536059e9f21
With this I should be able to hear both strems becuase I am not using any particular track at the end of this url. We normally get one track when we mention it in Url like this:
rtsp://username:password@machine_ip/42331536059e9f21-TRACK0/1
So, when I am not specifying any track then why I am getting just one stream? Please consider the following important points: When I play the same active call from Mediasense Search & Play application, I hear the stream of both participants I am using FFMPEG (ffplay) library to play active call using RTSP url. Note: We were able to hear the both streams but I think, after deploying secondary mediasense server with first one we started getting this scenario (but still, after cluster deployment live monitoring is working fine in mediasense search and play application) Is there any well-known bug? Or I am missing something? thanks dadawes dlender manisgu3 pnijhawa anilv hariskum
... View more