Topics

76

Mitel Software Applications / Red X on UCA Client for Softphone and external usage

« on: December 22, 2011, 02:51:28 PM »

I am in the process of rolling out the UCA client for our new virtualized MAS/UCA server paired with our 5000 series InterTel system.  Of the 70 or so UCA clients, I only have 5 with softphone licenses, myself being one of them.   90% of my softphone use is in my office with my PC being on the same subnet as my UCA Server.  It is working pretty well.  I can call from my pc or my deskphone.  And receive calls as well on either.

Using the UCA engineering guide, page 26 lists the following ports used for the UC Server:

Ports used by UC Server
?
TCP Ports 5060, 6015, 5090, 5070, 6010, 1099, 5106, 5085, and 5269
SSL ports 5061, 6016, 5091, 5071, 6011, and 5086 (for SIP TLS support)
SSL port 36008 for Web socket support

UDP ports 6015, 5090, 5070, 6010, 5085, and 18100

I throw in web services for good measure.

Since SonicWall does not recognize anything called an "SSL Port" and since the numbers are conveniently +1 from the TCP ports, I took this to mean that the "SSL Ports" were really "TCP Ports." 

If I logout of my UCA at work and remote into my home machine, I can successfully login to my UCA from outside of the office.  I can change statuses.  I can even make my deskphone dial.  But I cannot dial from the softphone remotely.  There is a red X on the icon portraying a headset.

Any thoughts on how I can get this to work?  I was able to get the older InterTel softphone client to work (NON UCA) externally but it was a lot of troubleshooting with the firewall and ports.

Thanks for your suggestions.

Adam in DC

77

Mitel Software Applications / AWC - Yet another software client to roll out...or not?

« on: December 16, 2011, 12:05:16 PM »

In process with Mitel to roll out big upgrades to our InterTel 5000.  New UC.  New AWC.  New MultiTech fax.  Mobile Apps.  Etc.

I've figured out how to push the fax client out via GPO.

I've even figured out how to push the UC out via GPO.

But now I see that the AWC has it's own "CC" or "Collaboration Client."  There are actually two clients one could install:

Collaboration_Client-M.exe
or
Collaboration_Client-admin-M.exe (an admin version ostensibly for Citrix environments)

File sizes of both are exactly the same, but there are some differences in the installation routine.

It appears that this app was designed to be user installed via joining a web conference.  However, I see it as working hand-in-hand with the UC as part of an internal working environment and creating video and web calls on the fly.  To do that I think that the CC should be rolled out along with the UC.

There appears to be no documentation on this and no MSI file that one can roll out via GPO.  Not even sure if you can use /switches with these files.

What do you think of this approach and has anyone attempted to do this?

Thanks.

78

Mitel Software Applications / Android App - First thoughts

« on: November 22, 2011, 04:29:33 PM »

Loaded the Android UCA app. 

It drained my battery in 4 hours.  There was no way to exit the app.  It starts on bootup and runs until your phone dies.

Uninstalled it.  Back to normal.

Anyone else play with it?

79

Mitel Software Applications / Deploy UnifiedCommunicatorAdvanced.MSI via GPO / Group Policy

« on: November 21, 2011, 04:52:23 PM »

Is there a readme with an argument / switch list so I can pass through the name of my UCA server to the MSI install? 

My GPO works flawlessly, but UCA installs without the server name of the UCA Server and comes up off-line.  Furthermore, you cannot enter the server name after the install.  At best, you need to go to Programs&Features and select "Change" and then enter your UCA Server name.

This ruins the whole point of an MSI file install. 

For those looking at the .Net deploy that is a pre-requisite of this install, you can use WSUS.

Thanks for your suggestions.

Adam in DC