UCA Clients not working after upgrade to V5.1.27.0 1

[danramirez]

Hi again,

Last week I upgraded one of our customers vMAS to latest load available on MOL. The UCA application upgraded to V5.1.27 and since then none of the UCA clients are working as Teleworkers. UCA clients were upgraded as well.

Configuration includes a vMBG in the DMZ port of a firewall and vMAS is at the LAN side.

As I said, it was working fine in previous versions of UCA.

Teleworker Minet and SIP phones have no issues, it's only the UCA clinets that don't work.

They do work when in the LAN.

Have any of you experienced this as well? I have a ticket opened with the support guys, let's see what they say on Monday.

Regards,

Daniel

http://www.hatkana.com

http://www.wtelecom.com

 

[Billz66]

Just for any watching this thread
if you have MAS 4.0.223.0 in lan mode and MBG and want to run UCA as teleworker , UCA clients must have a routable FQDN and this should be directed to the MBG and the Web proxy must be setup.

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

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

 

[boycey9]

I have also been told by Mitel that the FQDN is needed, however the issue I have with this is that this is no longer working as teleworker mode, Yes it works when I turn off teleworker mode and use a FQDN with split DNS but Mitel have not announced that this is now the correct method officially and that teleworker mode is not supported.
Teleworker mode created a secure vpn to the MBG and tunnelled through that, I dont believe this is happening if you use the FQDN.

Any Views?

 

[Mitelmatt]

Sorry I'm missing something , you can't put in a fqdn on the teleworker setup in the client, has to be an ip?

 

[Billz66]

The fqdn is used when installing the UCA client , tis must be resolvable

if you dont know what was used , check the program files mitel unified communicator advanced xx folder and edit teh uca.exe.config file with notepad

about half way down there will be 2 entries that have the fqdn that was entered when the client was installed.

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

 

[Mitelmatt]

Ah already done that, but still have the issue of connecting then disconnecting straight away.

 

[danramirez]

MitelMatt,

Please confirm you are using FQDN for initial Client set up. Then, also remember you need an internal DNS to reslve your FQDN into the IP address of your UCA server, and last, remember to enable WEB Proxy in your MBG.

Do you meet all the above?

Regards,

Daniel

http://www.hatkana.com

http://www.wtelecom.com

 

[Mitelmatt]

Hi Dan

Yes mate, I use an fqdn of mas.mycompany.co.uk in client. Externally this resolves to mbg external ip. The mbg then uses it's internal dns to route mas.mycompany.co.uk to mas server internally.

Plus I have the proxy enabled

In the uca.log from the client I'm getting something about authentication issue?

 

[danramirez]

So extrange... I can't think what can be going wrong. What support guys say about it?

http://www.hatkana.com

http://www.wtelecom.com

 

[Billz66]

Mitelmatt , what dn have you entered in the teleworker setup.

I have seen documents that this should not be a real number but a made up extension number .
Im my case i used the real DN of the deskphone , requested certificate and added a mitel device for it that was enabled and had the virtual mac address

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

 

[boycey9]

If you are using FQDN the teleworker settings are doing nothing, you may as well disable the UCA connector as you are bypassing it all togehther and no certificate is needed.