MiCollab Unable to play Visual Voice Mail via web proxy

[ucsenoi79]

Hello,

I have an issue with MiCollab Mobile Client or MiCollab desktop Client that will not playing messages on Teleworker environment (WAN side).
I have no problem in LAN environment, and no any other problems.
MiCollab 6.0 and its applications on the LAN, and MBG 8.1 is clustered (DMZ) with Proxy services. Nupoint is VM server and MCD CX our ICP.

Any help will be appreciating, as we’ve checked the firewall ports without any success.

Thx

[ucsenoi79]

Apparently, a DNS problem is the source, MBG (DMZ) is not able to resolve name for NuPoint (LAN) when stream or download is required.
Now, my MBG server has an INTERNET DNS SERVER to resolve ServiceLink subscription.
Is there any chance to configure split DNS to have in this situation, or any other option?

Thx.

[johnp]

I usually let my servers do name resolution. I add host names if necessary to point to other Mitel servers. I also put a true FQDN on them.

[ucsenoi79]

Domain DNS servers resolve locally for my MBG (DMZ), on the other side, Micollab (LAN) resolve locally also or Corporate DNS servers. On LAN side, we have added A record on our DNS server to point the right direction (DMZ ip).
None of these options makes possible resolving name properly,   

Failed to download message https://nupoint.xxx.xxx.ca:443/npm-pwg/
The name cannot be resolved: nupoint.xxx.xx.ca

Mitel tech belive that i should add FQDN to my internet provider, but i never see that on any Eng. Guide, which I was sceptic.


Any ideas will be helpful, I’ll try next week few other options.


Thx

[ralph]

If the name doesn't resolve then you'll need to add it to a DNS server.
A way to test this is to edit your host file and add nupoint.<name>.<name>.ca to it.


Ralph

[ucsenoi79]

Ralph,

I’ve done modify host file on both server, MBG and Micollab , and from SSH instance, both resolve the name to  same IP destination.
Lan side i have Ping responding, DMZ side none. I will talk to network admin next week to check if there is an issue in path.
As MItel tech confirm, i need only 443 to authentification WAN side and 36006 on application web proxy.

Thx. Dan

[ucsenoi79]

Well, not happy with Mitel tech. partener , I find the way myself.
There was 443 blocking on roundtrip between NuPoint and DMZ;  FQDN Nupoint HOSTNAME SERVER has to be resolve on public IP pointing to MBG (WAN ),then create new LAN server PROXY , with server type MiCollab Unified Messaging.
Both clients mobiel@desktop now playing messages.

Thx.