CuCM doesn't reach our lab

[dada]

Hi Joseph,

I’m configuring our lab for testing on UCCE.

I installed TSSOVA01 having IP address 192.168.204.20.

I did a ping from TSS to CuCM 10.10.20.1 and I received packets.

I did a ping from CuCM 10.10.20.1 using ssh to TSS and I didn’n receive any packets.

Is there a rule on your router avoiding to reach our lab?

Could you please solved this issue because it’s blocking for our testing?

Thanks,

Milo Maio

[mihaicodrean]

We too are very much interested in having the CUCM reach our server in the VPN, to test the SIP traffic etc. We currently get the same behavior as Milo reported, using the Collab Plus lab, and installing our entire suite of software in an app-server VM would be time consuming.

Any suggestions on what to do about the routing tables?

[jokearns1]

Hi Mihai,

The collaboration Plus lab is not affected by this issue. You can get to the remote Anyconnect IP address from that lab.

Joe

[mihaicodrean]

Hi Joe,

Please allow me to reply here, to provide context. Do you know if there are restrictions now to reach the AnyConnect client from the labs? I can't seem to be able to do that from the PCCE Lab, e.g. ping the AnyConnect client IP address from the Windows VM there. I actually want to setup a SIP trunk to a service running on my workstation, but first checks first.

Thanks!

[jokearns1]

Hi,

The routing issue is resolved. you can you ping the 192.168.204.x addresses from inside the lab.

I have tested it from a lab machine. please verify on you application.

Joe