Teleworker setup for UCA

[TDressel]

Hi folks,

Saw a good set of tips on how to get UCA working in teleworker mode from a post from middle of last month, I'm closer but still don't have it working yet.

As a background, I can take my desk phone home, convert to teleworker mode and point at my MBG and it works. On the MBG I had to add a MiNet device for my phone (actually, I think all I had to do was approve it, it was a while ago actually), but it works well outside the firewall.

Inside, the UCA client works well,,, normally we are connecting across a router from the business network to the UC server directly.

Outside the firewall I have pointed the UCA in teleworker mode to the MBG, did the certificate request, went in approved it, and then the UCA client "sees" the certificate as approved. I then went in and added a MiNet device as per the MAC address in the certificate, gave it a friendly description and left everything else as default. It actually doesn't look much different from my MiNet device for my desk phone when I take it away from here.

However when I try to connect ((I've set the presence server port for 36007 which was the default), I get a quick 2 second login, but then I get a connection lost message. I'm sure I'm missing a step somewhere, a checkmark in a box, etc.

Relevant versions are:

MBG: 7.1.32.0
UC Server: 5.1.27.0
MCA: 4.0.2.14

Cheers,

Tim

 

[TDressel]

Oh yeah, UCA version is 5.1.27.0.

Tim

 

[Billz66]

the fqdn for the uca client MUST be the FQDN of the UCA server and that must be resolvable

how this is achieved will depend on your topology

if you have a standalone ( not MAS) UCA server , then get a public name for the fqdn of the uca server and point it at the MBG server
setup webproxy on the MBG to pass it through



If I never did anything I'd never done before , I'd never do anything.....

 

[TDressel]

I'm just heading out of town for a couple of days, back in the office on Tuesday so I'll try this then.

I've already got external DNS pointing the FQDN of the UC server to the MBG, so I think I can check that box. I haven't looked at the webproxy section in MBG, is it reasonably straight forward to do that, or do you have a couple of examples?

Cheers,

Tim

 

[Billz66]

its pretty easy
The MBG must be able to find the inetrnal FQDN for the UCA server and then it just works

We are Field trialling the next version of UCA at the moment and the requirement for the dummy minet entry / certificate has been removed

If I never did anything I'd never done before , I'd never do anything.....

 

[LoopyLou]

Anything new in for UCA in the field trial? That would be 6 I guess?

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[TDressel]

OK, so I can confirm that the the MBG can resolve the FQDN of the internal address of the UCA server.

The Teleworker settings on the UCA client are pointing to the public IP of the UCA server, and the FQDN is also resolving to the same IP.

But I still get the same connect, then instantly drop.

Any other settings I can check?

Cheers,

Tim