Prime Collaboration and Assurance issue - Medianet

[khorheesoo]

Dear All,

Our Topology -

Devices

-----------

1) 2x ISR g2 routers [15.3.(1)T]

2) Switch 3560 [15.0(2)SE4]

3) 2x 7965 IP Phones,

4) WAN emulator

5) Cisco VCS 7.2.2

6) 2x Jabber Movi running on Windows 7 Virtual Machines

7) Cisco Unified Communication Manager 9.1

8)Cisco Prime Collaboration and Assurance 9.5 with Analytics

All the above listed devices and components has been configured and connected as per the topology diagram attached with this post.

Our Issue - We discovered the Cisco VCS and added in to our Prime Collaboration, but when attempting to see our VCS registered endpoints (Jabber Movi) under 'Endpoints Diagnostics --> Endpoints', the device status shows 'Not In Use'.

Our Expected Outcome - We would like to see the status of our endpoints as 'In Use' rather than 'Not in Use'. And as next step, we would like to get some outputs under 'Media Path Analysis - Media Path Details and Status'. Since the endpoints status are negative, we could not able to progress further more.

Workarounds attempted so far - Used CUCM registered endpoints (Cisco Jabber) to get detected inside the Prime Collaboration to monitor the RTP traffic, that one failed by not even getting detected under 'Device Work Center --> Endpoints'. Since this option failed, we decided to use Cisco VCS and Jabber for Movi endpoints. This option gave us a little positive way to a certain extent to see the Movi endpoints listed under Endpoints Diagnostics.

Regards

Khorheesoo

[Philippe Beaupied]

Hi.

A few comments:

1. Please check that the visibility status of your MOVI client is set to "limited visibility". If set to "no visibility" please change the status in Device Work Center. The MOVI client should then show "in use" when in a session.

2. I see on your diagram that Jabber clients are shown with MSI. MSI today only implements metadata, not the media monitoring features. Because of this There will be no way today to get the five-tuple from a Jabber client, which is necessary to initiate mediatrace.

3. New in PC 10.0 is an ability to draw the media path, even if the endpoints/MCU are not able to run the traceroute function that is needed to get the list of network devices that are used to carry the flow.

4. Be aware that VCS 7.2.2 is not yet supported by PCA (even PCA 10.0) and I have not yet tryied that release on my lab.

Thanks

/Phil