IPCC Express 3.5(2)sr1 / RTR Problems

[jmujica]

Hi.

I have IPCC express up and running but when I tried to see statistics using the real-time reporting tool the pluging comes up but no matter what I selected it comes with a "Unable to Connect to the Server" message. On the real-time reporting plugin it has the right server ip address on the "Data Host" and using port 1099. There is no firewall in between..

Any ideas?

-Jose

[jmujica]

I think my problem is related with the 2nd nic card that I'm using for VoIP monitoring and recording. I put a bogus IP address on it and when I go to the CRA Administrator web page from the server itself it is shown the bogus ip address on the URL. Also seeing the java logs on the PC running the RTR I'm seeing traffic source from that bogus IP Address.

How do I force the server to use the real IP address? Can I safely removed the bogus ip address from the TCP/IP Properties of the 2nd nic card without breaking the VoIP Monitor and Recording function?

Thanks in advanced,

-Jose

[cbelcher]

Jose, I think your right! I implimented the Monitoring/Recording functions this weekend and now RTR is broken. Did you ever figure out how to resolve this issue?

Thanks

Craig

[selcukd]

I had the same problem. After giving additional permissions in the java.policy file, the problem is solved.

[jdiegmueller]

I realize this post is quite old, but perhaps it will help the next person to have problems. The common reason this would be problematic ("monitoring/recording enabled, suddenly RTR is busted") is that it seems the Cisco MCS Windows 2000 images are shipped with the second NIC ahead of the first NIC in the binding order. However, since the second NIC is disabled out of the box, it never seems to cause anyone grief until that second NIC is enabled.

Try this:

* Start->Settings->Network & Dial-Up Connections

* Click on Advanced->Advanced Settings

* Verify that the primary NIC is "on top of" (listed first) the secondary NIC

Also, make sure (if you're RDC/VNCd in to the server) you're accessing it by name or IP. For example, http://localhost/appadmin seems to work fine for AppAdmin, but once you try RTR, it will fail. Instead, use http://1.2.3.4/appadmin or http://servername/appadmin (where 1.2.3.4 and servername are the server's IP address or hostname, respectively).

Good luck.

-jd