Hi Aaron,

In CMShell you can enable a request-trace to inspect which messages are being sent by the client:

    $cm.EnableRequestTrace = $true

This should tell us if CMShell is actually sending a request for RIS-Data.

Could you also do a device search for a registered phone in the Cisco RTMT? This should tell us if the RIS-Data service is actually functioning.

Sincerely,

Foxnet Helpdesk

Hi Aaron,

It appears that CMShell is formulating a correct request that somehow doesn't reach the RIS-Port.

To dig down a little deeper into this communication failure we would like you to run this PowerShell-script:

#------------------------ RISTest.ps1 ------------------------

param ($cm, $sep = "SEP40F4ECEE98CE")

$ris = $cm.APIServices[[Foxnet.cmservices.CMServiceName]::RIS]
$sc = New-Object foxnet.cmservices.cm85.ris.cmselectioncriteria
$si = New-Object foxnet.cmservices.cm85.ris.selectitem
$state = ""

$sc.SelectBy = "Name"
$sc.Class = "Any"
$sc.Status = "Any"
$sc.Model = [uint32]255
$sc.MaxReturnedDevices = [uint32]200
$si.Item = $sep
$sc.SelectItems = , $si

$ris.SelectCmDevice([ref]$state, $sc)

#-------------------------------------------------------------

If you save this as "RISTest.ps1", for example, you can then run

.\RISTest.ps1 $cm

to retrieve realtime information for SEP40F4ECEE98CE, or

.\RISTest.ps1 $cm <Device-Name>

for any other device. However, in the current situation we would expect the operation to fail. Please reply to us with any error messages the script generates.

Sincerely,

Foxnet Helpdesk

Hi Aaron,

We're glad you were able to solve this problem. We will include these requirements in the next version of the manual.

Sincerely,

Foxnet Helpdesk