Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

UCA Clients not working after upgrade to V5.1.27.0 1

Status
Not open for further replies.
danramirez

danramirez

Programmer
Oct 25, 2009
1,136
ES
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

 
Sort by date Sort by votes
Dont think the docs mention it but you need MBG 7.1 to get it working
 
Upvote 0 Downvote
We are running the version of UCA client that you are but I am still waiting for our comms department to setup me up in teleworker mode and going to SIP. Sucks I can't access our in-house system but can access all our customers. I like the 5.1 otherwise but can't wait to test the SIP.

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.
 
Upvote 0 Downvote
A couple of things to note:

1. The T-UCA-5.1-IM-UP-SS.pdf (UCA 5.1 Update Course) says

Configure the following fields:
• Directory Number: The user’s remote softphone or desk phone IP extension. This
must be a number ranging from 1 to 99999999.
• Teleworker Gateway IP: MBG IP Address. The IP address should be in the form of
xxx.xxx.xxx.xxx.
• UC Advanced Server Port: The port number on the MBG mapped to the UC Server.
This must be a number between 1 and 65535. The default value is 36005.
• Voice Mail Server Port: The port number on the MBG mapped to the Voice Mail
server. This must be a number between 1 and 65535. The default value is 36006.
• Collaboration Server Port: This is the port number on the MBG that is mapped to the
collaboration server you are using. This must be a number between 1 and 65535.
Unified Communicator Advanced– I&M Update - Module 2: New Features and Functionality
a. When the collaboration server is MCA, the hostname of the MCA server must resolve
from the public network.
b. When the collaboration server is the YA Collaboration module, the default value is
37000.
• Presence Server Port: The port number on the MBG mapped to the UC Server. This
must be a number between 1 and 65535. The default value is 36007.

However, when configuring the client I only see the Presence Port, none of the other ports mentioned are shown...

2. While trying to connect UCA client as teleworker, I have been monitoring 36005, 36006... etc at out WAN interface of firewall and nothing comes trhoug those ports. It seems that the UCA client is not reaching our WAN interface.

3. Somewhere in the Help on line I read that if UCA client is unable to connect it will start in off-line mode (Same as it did last version of UCA). This does not happen, UCA client does not start in off-line mode and it keeps saying Unable to connect to UCA Server.

I think something is wrong with this version or something is wrong with me. What wonders me is: It was working before, why it does not now?

Regards,

Daniel

 
Upvote 0 Downvote
I have seen my V5.1.27 come up and try to run in off line mode. However this was as I have said not in teleworker mode. Did you get a new certificate when the client updated i.e clear it in the MBG and have the client ask for a new one?

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.
 
Upvote 0 Downvote
We are having the same problem. I managed to get it to work locally but not teleworker. MBG was updated to the latest and so was UCA.

 
Upvote 0 Downvote
Yes we do have a FQDN registered for our UCA and MCA products.

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.
 
Upvote 0 Downvote
I have a FQDN and it does not work. What did you put in for a sip password on MBG?
 
Upvote 0 Downvote
Webmany, I haven't tried with sip yet, I was first trying to make the Minet client to work but...

That's a good question, what would the password be...??

Documentation is very poor... I have downloaded the update course but to be honest I don't find it that useful...

 
Upvote 0 Downvote
What are you setting in the uca.exe.config file


we Have a MAS in Server gateway running this version with Teleworker UCA clients and smart phone clients.
With the deskclients , it seems to work best with the full public routable dns name in place
The mas server name is awc.company.com.au
we use awc.company.com.au in the uca.exe.config file and it connects fine.

I think because you have vmas that you will need to setup webproxy on the MBG to proxy external requests from the UCA to the MAS


If I never did anything I'd never done before , I'd never do anything.....
 
Upvote 0 Downvote
Still waiting for our comms guys to set me up as a teleworker. Will know if they ever get back to me.

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.
 
Upvote 0 Downvote
I have this set up with webproxy, FQDN etc and it doesnt work, I logged with Mitel and was told I needed MBG 7.1 which I have been unable to get upgraded but abyway doesnt look like this is the cause. The case was then closed so I am interested to hear your outcome.

What does work is the SIP client on an Ipad, Android etc fine, UCA Client connects locally fine and blackberrys work fine, Its only Minet through teleworker that doesnt.
 
Upvote 0 Downvote
We have the same issue....since upgrading to 5.1.27, found UCA in softphone Teleworker mode on the PC won't maintain a stable connection ...connects then drops all the time. UCA Mobile on the iPad seems to be working fine in Teleworker mode using Sip UC endpoints as softphones, seems they broke the PC UCA in Teleworker mode to get this app working.
 
Upvote 0 Downvote
Guys,

I finally made UCA Client (Minet) to work. (Support guys gave a hand as well)

A FQDN is definitely needed, ours is vmas.ourcompany.com.

Our firewall if forwarding ports to MBG (all ports are specified in Eng. Guidelines), then MBG is web proxing to vMAS as well as approving certificate request from UCA Client.

As we don't have a Domain Controller in the lab, nor a Corporate DNS, I had to play around with the Domains and addresses. In MBG I specified the vMAS as the corporate DNS Server so everything was resolved by vMAS. I also enabled remote web proxy in MBG.

I am waiting for some licenses so I can test sofphone on smart devices.

Regards,

Daniel

 
Upvote 0 Downvote
There was a new update to the client today. Now has a little box when the connection drops with the option to connect or cancel.



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.
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

NICnamed
  • Locked
  • Question
problems after upgrading to MiV Connect 22.24.7100.0 19.3 sp3 hf2
Replies
0
Views
152
NICnamed
NICnamed
DMilden
  • Locked
  • Question
MiVoice Connect Upgrade Paths
Replies
4
Views
193
DMilden
DMilden
vtxcore
  • Locked
  • Question
Mitel System Upgrade
Replies
15
Views
342
esoare
esoare
kwbMitel
  • Locked
  • Question
Need help getting IMAT working
Replies
8
Views
260
dirtcheap
dirtcheap
bojo3871
  • Question
MBG not reflecting correct Teleworker License in use
Replies
0
Views
186
bojo3871
bojo3871

Part and Inventory Search

Sponsor

Back
Top