Problem with UCA teleworkers after upgrade of MAS and MBG 1

[Billz66]

I have redeployed new ova templates for 2 virtual servers
MBG was using ova 7.0.12 but had had its MBG blades upgraded to 7.1.31.0
- This has been upgraded to ova 7.1.31.0 and its MBG blade upgraded to 7.1.32.0
MAS was using ova 4.0.113.0 and has been upgraded to 4.0.223.0

By upgrading the MAS to the latest we have also upgraded the UCA from 5.0.27.0 to 5.1.27.0.

MBG is in DMZ mode and had all the required ports open for UCA connectivity
MAS is in Lan mode and also has all the required ports open to the MBG

Before the upgrade I had 2 teleworker users that were also using UCA to control their Deskphones.
These clients were functioning correctly.

The clients have been started and have been prompted to upgrade to the latest version.
The upgrade was successfull but the clients will now not stay connected .
It will start , login and then the connection drops .

Does anyone know if there are additional ports required?

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

 

[danramirez]

quetion 1: Are you using FQDN? With this new version you DO need to set a FQDN as well as the IP Address for the Telewrker.

You DO need a Domain i.e. ourcompany.com

You need to purchase a domain so you can the set up a FQDN for your mas server i.e. mas.ourcompany.com

you also need to set up WEB proxy on your MBG (There is an online course on MOL that teaches you how to set up the web proxy to access UCA user applications)

Of course you will need an internal DNS to resolve mas.ourcompany.com into a local IP. Your MBG and your MAS need to be aware of your DNS

Follow my recomendations and you'll get it to work, I had exactly the same problem when upgraded MAS.

It is adviceable to renew client certificates on MBG. You may need to uninstall UCA clients and reinstall so it asked me again to enter the FQDN

Give us some feed back how it goes.

Regards,
Daniel

http://www.hatkana.com

http://www.wtelecom.com

 

[danramirez]

http://www.tek-tips.com/viewthread.cfm?qid=1703497

http://www.hatkana.com

http://www.wtelecom.com

 

[Billz66]

Ok so previously our mas had a fqdn pointed at an address that was natted to the MAS server

Are you saying that i need to route this towards the Public address of the MBG and use webproxy from here forward ?

I have setup webproxy on other sites .

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

 

[LoopyLou]

Think I have seen some other posting on an issue with UCA and teleworker sets not being able to stay connected. There was a recent upgrade to UCA to 5.1.27.2 and it had some bug fixes. Not sure if there was anything regarding teleworker.

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.

 

[danramirez]

Loopy, where can i download that version, i don't see that on MOL
Cheers

http://www.hatkana.com

http://www.wtelecom.com

 

[Billz66]

2 Star for you danramirez

I can confirm that changing the dns entries for the MCA ( also the fqdn of the mas server) to point at the Public Ip address of the MBG and configuring the web proxy was the fix for this , thanks danramirez , its all good now.

I dont think that version ( 5.1.27.2) is publicly available yet , there was a KB released regarding problems with UCA console on 5.1.27.0.

Next step to change the softphones to sip and test that part

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

 

[danramirez]

Bill, i'm glad to hear that
Regards,
Daniel

http://www.hatkana.com

http://www.wtelecom.com

 

[danramirez]

Also, MBG must be running latest software version available on MOl

http://www.hatkana.com

http://www.wtelecom.com