Mitel My Assistant and Network Connect

[ssl_boy_]

Hi,

I've had various Voip Clients working across Network connect including Cisco, but I'm having a mare with the Mitel Softclient,

Has anyone had this working? It seems to hang the client workstation A LOT if it connects at all, it goes offline immediatly. It works across the Cisco VPN client annoyingly, but I can't get it anywhere near stable.

Any ideas/experience? We are using Your Assistant 4.0.

Thanks Kendal

[Jickfoo_]

Hi Kendal,

What version of IVE code are you running ? Could you share a TCP dump of a failed conversation ?

I'm assuming that VOIP traffic is UDP.

Justin

[ssl_boy_]

Hi, 6.2 r1 at the moment but I've just upgraded to 62R2.1.1 but have yet to test...

Yes, it is mostly UDP, difficult to do as the workstation hangs when the tunnel is up, A LOT. Will try again with the new build and have another at a packet capture, I assume you mean from the client end?

Thanks

Kendal

[tvman_]

Make sure that you can access YA server and Mitel controller. Are you using Teleworker solution for YA? Are you using split tunnel? TW is a solution specificaly designed for softphones and deskphones connectivity from the Internet without any sort of tunnels.

[dennis_]

Hi Kendal,

It is working here; we are using NC with split tunnel and check that all traffic is enabled to the Your Assistant Server. (both tcp and udp, please use wildcard). Actually pretty easy!

Kind regards,

Dennis

[dennis_]

Kendal,

We are using v4.1.0.99

Be sure that's it working on the Lan, before you try NC.

Let me know what setup you have further on.

Dennis

[ssl_boy_]

Hi Chaps

Thanks for your responses, I will try and work through your questions!

1) When the VPN is up, you can definatly ping/RDP to the YA server and the PBX
2) There is no Teleworker in the environment (is this a requirement?)
3) I've tried split tunnel enabled/disabled
4) I've tried ACLS that say *:* and named the subnets, same effect!
5) Works on the LAN and Via Cisco VPN Client

A little more about the environment.

Basically the YA and PBX and internet firewall are located at site A). The IVE is located at Site B). These two sites are connected by a fast, routed connection but are obviously on different subnets in the same 192.168.x.x Class B. Example:

Site A:

Subnet: 192.168.0.0/24
DG: 192.168.1.1
YA 192.168.1.10
PBX: 192.168.1.11
Cisco VPN: 192.168.1.100

Site B:

Subnet: 192.168.1.0/24
DG: 192.168.1.1
IVE 192.168.1.10
NC Clients: 192.168.1.100-110

Basically For reasons I won't bore you with, the NC clients are terminated at site B. Obviously the IVE at Site B there is a route from the IVE to the YA,PBX. I suspect the issue is something to do with that once the connection is made to the NC network, the traffic still has to be forward routed across the WAN. If the IVE was on the same subnet (as the Cisco VPN is) then I think it would work properly. I think that the Mitel client assumes that it will always will be on the same subnet and the YA server and can't deal with the fact there is more routing/forwarding that needs to happen once the connection is up.

Thanks for your help guys, much appreciated..

Regards

Kendal

[ssl_boy_ · Accepted solution]

Hi,

My customer came back to me today and after your collective assistance, we have a resolution. Here is the customers mail (reproduced with his permission)

"I've got it working with YA 5.0.

5.0 seems quite different to 4.0 as it requires changes to the extension type on the PBX as well. Instead of the extension being of type "6600 YA Softphone" it needs to be of type "Server Application Port". The release notes say that this is also the case in version 4.1.

After making this change it works just as you would expect.

Looking under the hood there now doesn't seem to be the IP Phone Emulation applet in Control Panel.

This just left a very annoying problem: it flatly refused to install on XP 64bit as it say it wasn't support. So I hacked the MSI to remove the install conditions and it then installed like a charm. After tweaking the flags to force .Net to run it in 32bit mode it works fine - and what's more it even works over Windows PPTP VPN!"

So, it would appear that:

YA 4.0 Might Work

YA 4.1 Definatly Works

YA 5.0 Definalty Works and Without a Teleworker in the environment.

The other thing he mentions above is about the YA refusing to install under 64bit Windows, helpfully he has included how he worked around it. We know that 64bit edition was NOT the reason for the issues as we have tried on standard 32bit and it had exactly the same issues.

So we have a resolution chaps, thanks for everything!

Regards

Kendal

[lboucher_]

Kendall, could you please provide me with more information on the customer was able to get Mitel Your Assistant 5.0 to install and working properly on a Windows 64 bit operating system?

Thanks,

Leo