UCA Client Issues connecting at first run

[jherlitz]

Okay so since we did the last big update, to 5.1 we have been having an issue.  User boots up their computer, eventually fires up their UCA client and attempts to make a phone call.  They get a message failed to dial.  They have to exit the application 1 to 3 times before it will actually dial.

I am working with our Vendor on this who is working with Mitel.

I just wanted to put a post out here to see if anyone else is having this issue.  Two reasons, A: see if you found a resolution for it, or B: you might want to know the fix once it is found. 

Thank you,

[LoopyLou]

Do not have that issue at all

[ralph]

Haven't seen this at any of our clients.

Ralph

[jherlitz]

I am wondering if it has a lot to do with our Trendmicro AV software then?  I have a ton of exceptions in for it, but maybe something is missing.  Anyone else using Trendmicro and the UCA client?

[martyn]

Yep have the Trend client here and can't say that I have noticed the issue.

[LoopyLou]

When you are making the call are you telling the softphone client to do the dailing or having the UCA client tell the desk phone to do the dialing?

[jherlitz]

The client is making the call.  Our softphone users are full-time softphone users no deskphone.

I uninstalled TrendMicro from a couple computers and tried again, but still had the issue, so guess it is not the AV software.

One thing I noticed with the latest update of this client, there is two process running UCA.exe and UCASoftphoneManager.exe.  I have watched them during boot up and if the UCASoftphoneManager.exe disappears is when the client doesn't work.  But when it sticks around, it works fine.  That was one reason I was thinking maybe AV, but that wasn't it.

[LoopyLou]

What OS is the client using? Think you say in your first post but does the user manually launch the client? Are you running the app with administrative privledges?

[jherlitz]

All the workstations are Win7 64bit and all users have local admin rights.  I do have the clients manually starting it now.  I made that change hoping that it was just too much starting up at once.