cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
573
Views
0
Helpful
2
Replies

Mediasense AgentInfo Gadget for MS 10.5 SU1

Tony Duran
Level 1
Level 1

Hi,

 

Does anyone know how to configure new AgentInfo Gadget in MS 10.5 SU1.

Release notes state to configure in Finesse but thats all...

Customer Has Finesse 10.5 with PCCE

 

Any info on this would be greatly appreciated

 

 

 

2 Replies 2

philiphagan
Level 1
Level 1

Hi Tony,

 

Did you ever get an answer back for this? We have the exact same issue

 

Thanks

 

Hello Tony,

Regarding AgentInfo.gadget for Finesse 10.5 will not work due to new bug CSCut70483.

https://tools.cisco.com/bugsearch/bug/CSCut70483/?reffering_site=dumpcr

Here's the Finesse web service dev guide:

https://developer.cisco.com/fileMedia/download/90f66367-13f0-41a9-aadd-84df32057afe

It says on page 6 that in UCCE deployment, it should send the request to port 80 and on UCCX it sends a request on port 8082

We are facing this issue on UCCE Finesse because it is forwarding to port 8082, which is for UCCX Finesse.

As  Finesse standalone is installed on Platform Tomcat instance so it listens on port 80.

On upcoming Finesse version 11, it will have a separate instance and will listen on port 8082 and it will be resolved.

There is nothing which can be done in Mediasense to change the request  to port 80.

Either you can follow the workaround for the bug and add all agents to API users or wait for Finesse 11 as the fix will be in Finesse.

Workaround:

As a workaround , if the number of users who would need to be authenticated in that way is manageable, the customer can try AXL authentication instead of the Finesse authentication at the moment with MediaSense 10.5 for AgentInfo gadget on Finesse standalone10.5.

Following are the steps that can be performed to do the same.
1. Login on MediaSense Administration Page.
2. Go to Administration > MediaSense API User Configuration and add Finesse agent/Supervisor as an API user

 

Regards,

Lobsang Phuntsok