Messages

1

Mitel Software Applications / Re: UCA Softphone with MBG connections are flakey

« on: March 24, 2014, 10:37:16 AM »

Thanks for the document, I will pass it along.

I agree, it would make sense for the UCA client to use the FQDN rather than the public IP, but unfortunately it will not accept the FQDN in the Teleworker field.  It does accept the FQDN for the "server name" during setup, which is of course what we used.  If we enter an IP, any IP, the teleworker box turns from red to green and the Apply & OK buttons become available.  If we enter the FQDN (in fact any FDQN) the teleworker box remains red, and the OK and Apply buttons remain grayed-out.

I tried editing C:\Users\snelson\AppData\Roaming\Mitel\UC\snelson@mydomain.com\user.config to include the FQDN, which did get the field to populate correctly, however if I go to the config screen, the box remained red with no way to click OK or Apply.

Is there some setting in MBG, MAS, etc. that can effect the client in this way?  The client is v6.0.120.0 .

We do have split DNS setup correctly so the FQDN will result in a LAN IP when in the office, and the public IP when outside the LAN.  I can't say if the DNS is set up correctly on MGB though, as the vendor set that up.  I poked aroind some and while I did find references to our ISP's DNS server, the "corporate DNS" settings were not utilized.  Instead "internal DNS" was in use to supply the LAN IP resolution.  I'm not sure if that's correct or best practice. 

2

Mitel Software Applications / Re: UCA Softphone with MBG connections are flakey

« on: March 20, 2014, 11:15:59 AM »

Thanks for the response.

 Correct, the system is deployed as a single network edge server.

 If I'm reading this correctly, you're saying that once the Teleworker box is checked, and the public IP entered (The UCA client will not accept the FQDN for some reason - should it?), the softphone should work seamlessly regardless if the user changes locations/networks be it home, office, Starbucks, or on a cellular hotspot (all assuming appropriate bandwidth is available).

 "The SIP Teleworker service is not available with MBG for the 5000 CP" for Remote SIP IP Phones is a little confusing to me (sorry for my ignorance, we outsource most of our phone system work to this vendor).  This sounds like they're just talking about the physical IP phone handsets, not for SoftPhones, correct?

 Also it sounds like call recording won't work as this is a 5000 CP - Disappointing, but not a deal breaker. I wish I could disable the button in the UI, as it does currently crash UCA if it's pressed.

 I'll go back to the vendor with this information.

Thanks,

Simon

3

Mitel Software Applications / UCA Softphone with MBG connections are flakey

« on: March 19, 2014, 05:30:18 PM »

Hi,

 We recently had an MSL system added to our 5000 by our vendor to enable us to run UCA with the ultimate goal being to eliminate the need for our remote staff to be on a VPN all the time to run an IP phone.  We plan to replace their IP phones with softphones.  We will have a mix of deskphone-only, softphone-only and desk+softphone users.

 We're at the point now where the vendor believes everything to be configured correctly, but I'm not so sure it is. (this seemed to be their first UCA + 5000 install.)  I'm hoping some of you could tell me if the following is normal behavior for a 5000 with MBG running UCA with Softphone:

 * When configured to work remotely the "Use teleworker for softphone" setting must be enabled. However, if we shut down a machine that had been working remotely and start it up at a different location (and thus on a different network) the softphone fails to connect.  The only "fix" seems to be to disable the Teleworker setting, shut down UCA, start UCA back up, re-enable Teleworker.  Not the most user-friendly process.

 * When in the office on the same LAN as the 5000, the softphone fails to connect until the teleworker setting is disabled, and UCA restarted.

 * If a remote user happens to be connected to the VPN when the UCA client is started, the softphone fails to connect until Teleworker mode is disabled and UCA restarted.  Also, in this situation, if UCA is shut down without making any changes, the VPN connection is then shut down, and UCA started, the softphone remains unable to connect[!] until teleworker is disabled, UCA restarted and teleworker re-enabled.

 * Video calling seems to have been disabled when the vendor switched us from "SIP softphone" to "UC softphone"

 I'm really hoping we can find a way to have UCA softphone work seamlessly both in and out of the office, as we were told it would.  I'm wondering if each user shouldn't actually have both a "UC Softphone and a SIP softphone configured?"  SIP for in the office, UC for out?  I'm still not sure that would solve it.

 Thanks for any help,

Simon