topic Can't connect from the labs to the AnyConnect client workstation in DevNet Sandbox

Can't connect from the labs to the AnyConnect client workstation

mihaicodrean — Fri, 29 Mar 2024 09:56:29 GMT

I recall that this used to be possible back in the IVT days, but it doesn't seem to work now, at least not from the PCCE Lab that I need to be using. The goal is to setup a SIP trunk to a server running on my own workstation, for testing purposes.

Thoughts?

Tagging @jokearns1, @bigevilbeard

Re: Can't connect from the labs to the AnyConnect client workstation

bigevilbeard — Fri, 29 Mar 2024 13:57:26 GMT

Sadly outside my domain this one buddy. Hopefully someone else knows.

Re: Can't connect from the labs to the AnyConnect client workstation

mihaicodrean — Fri, 29 Mar 2024 17:26:35 GMT

Thanks for jumping in. Even Internet access would do, and I'll use port forwarding, but only DNS works.

Re: Can't connect from the labs to the AnyConnect client workstation

dstaudt — Fri, 29 Mar 2024 20:32:43 GMT

If you can sign into the standard Jabber client successfully and see/control devices, then it should work in the SDK - if you don't yet have a working Jabber client user/device setup, then that's a good baseline target to shoot for first, for which there is lots of help (including TAC) available. There are a number of moving pieces involved in a Jabber deployment, so hard to offer any immediate solution without lots more details.
If your user works fine with Jabber but not the SDK, then I would focus on the things related to authentication, discovery and server endpoints. There are many ways to skin those multiple cats, and it's not always obvious how to approach each using the SDK. Again, lots more detail helps.

Re: Can't connect from the labs to the AnyConnect client workstation

mihaicodrean — Mon, 01 Apr 2024 08:49:32 GMT

Thanks for the suggestion, but I fail to see how setting up a Jabber client would help to confirm the possibility of lab outbound connectivity.

Again, what I'm after is to set up a CUCM SIP trunk to a server running on my own workstation, and that's to try out automatic call recording. Then the plan is to also experiment with NBR using the CUBE from the lab.

Just for an outbound connectivity test, I've tried to telnet from the Windows VM (10.10.20.21) to 192.168.254.11 - which is the AnyConnect client-side IP address -, port 5070, but got no connection attempts in WireShark running on my workstation.

Thoughts?

Re: Can't connect from the labs to the AnyConnect client workstation

dstaudt — Tue, 02 Apr 2024 16:14:50 GMT

Hmm...my response above should have been to another post - perhaps I misclicked something...
Re your issue, I believe that sandbox network configuration does not allow outbound connections from sandbox hosts - even towards the VPN-connected client. I recall some discussions with the team on this before (IMHO this should be allowed, at least for some sandboxes) - will see if I can get more light shed.
Unfortunately for now I think there is no quick solution...perhaps someone from the sandbox team might be able to modify the config for your reservation instance as a one-off (and ideally extend your reservation).

Re: Can't connect from the labs to the AnyConnect client workstation

mihaicodrean — Wed, 03 Apr 2024 10:07:10 GMT

will see if I can get more light shed.

Thanks!

perhaps someone from the sandbox team might be able to modify the config for your reservation instance as a one-off (and ideally extend your reservation).

That could work.

Re: Can't connect from the labs to the AnyConnect client workstation

mihaicodrean — Fri, 05 Apr 2024 09:00:42 GMT

someone from the sandbox team

Who would be on that team, to try to ping them?

Re: Can't connect from the labs to the AnyConnect client workstation

jokearns1 — Mon, 08 Apr 2024 19:38:06 GMT

Hi,

Do you have a current running PCCE reservation? if so send me on your username and the link to your reservation link.
Thanks,

Joe

Re: Can't connect from the labs to the AnyConnect client workstation

mihaicodrean — Tue, 09 Apr 2024 11:21:21 GMT

Hi Joe,

Thanks for jumping in. I've made a new reservation and shared the details in a private message.

Thanks in advance,
Mihai