MiCollab Server - Deployment Config Issue

[Martin]

Hi all,

Had quite a bit of experience installing MiCollab in various environments along with MiVoice Business but came across an issue today which is numbing my brain..

I am at the stage where the networking has been configured along with all of the MiCollab integration, sharing between MSL and MiVB, licensing is done etc. The MiCollab server has also had a valid SSL cert installed for the new MiCollab client to be deployed.

Using a MiCollab VA and making use of the embedded Mitel Border Gateway. This is currently setup with a custom network profile with a LAN address which matches the ICP side streaming, and the Set side streaming is the public IP used on the edge router. The public IP for the system is configured via a 1:1 NAT rule on the router.

At the moment the server is accessible externally, the external DNS resolves to the correct IP, all connectivity diagnostic tests pass on the MBG and I have also tested outbound connectivity via the root of the MSL and logging in to the MSL sever manager using the internet connection test.

However MiCollab Client Deployment tests keep failing, it passes the "Connection test from the MiCollab Client Deployment to the Redirect Server" but then fails with the following tests:

MiCollab Client Deployment test from public internet
ERROR: ETIMEDOUT (400 Bad Request) from host x.x.x.x

Connection test from public internet to MiCollab Client Service
Error: connect ETIMEDOUT

This would suggest to me like there are packets being dropped or some form of networking issue before its hitting the MiCollab server, however other tests would prove otherwise. All restrictions have been removed on the firewall it is behind to this server for the mean time and there has been no change.

I have tried messing with the deployment profile but havent been successful so far.

Just wondered if anyone had any ideas..

Cheers

[Magpye]

Have you set up the hostname for Micollab in remote proxy services on the MBG?
Have you ge tthe hostname / IP address in Hostnames and Addresses on the MBG? (If you aren't using a corporate DNS server)

[Martin]

Hi Magpye

Im using the embedded MBG in the MiCollab virtual appliance, so there are no remote proxy services or additional hostnames to configure.

Thanks

[mark.vanderheijden]

Have you programmed the FQDN under application integration tab off the MBG.

You can test if firewall is set correct with the Teleworker Analyzer.

[Martin]

Yes, tried both the FQDN and the IP address, no change.

Required ports are available externally, ran test with the teleworker analyzer.

[rfh23]

Yes, tried both the FQDN and the IP address, no change.

Required ports are available externally, ran test with the teleworker analyzer.

Hello Martin,

Did you ever find a solution to this issue, running into a similiar problem although we ARE using a remote proxy MBG. So slightly different setup from what you had.

Thanks,
Ron